Timeline for Is wiping the data partition totally unnecessary after this adb fail and stock restore?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:47 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jul 9, 2016 at 8:12 | comment | added | Fiksdal | Yeah, that sounds plausible. Although the latter didn't supply any recovery option at all. | |
| Jul 9, 2016 at 8:11 | comment | added | Grimoire | @Fiksdal This cannot really be answered, since an eventual answer would be mere speculation. My guess is that most people uses the recovery method, than the adb one. As for the .bat scripts being the same, I reckon that the authors may have shared them with each other. | |
| Jul 9, 2016 at 8:11 | comment | added | Fiksdal | That is so weird. Although I agree with your observation, since I have edited the script and experienced the difference first hand. What I don't understand is that I encountered exactly the same situation with this one (for which I ended up using the recovery option.) I'm just curious, how could they possibly both release this with such a serious bug? (I'm not disagreeing with your answer, I'm just dumbfounded.) Also, why is nobody in the XDA comments mentioning it? | |
| Jul 9, 2016 at 7:34 | comment | added | Grimoire | @Fiksdal Unless one has a weird su binary, then yes, this script won't work for anyone. | |
| Jul 9, 2016 at 7:32 | comment | added | Fiksdal | Thanks! By the way, does this mean that the script would have hung for everyone who tried it? (I'm referring to the script itself, not the bootloop that happened due to the incompatible Xposed.) | |
| Jul 9, 2016 at 6:31 | vote | accept | Fiksdal | ||
| Jul 9, 2016 at 6:29 | history | answered | Grimoire | CC BY-SA 3.0 |