Related
hi guys,
system win7x64, moto g retail uk
in order to root i unlocked the bootloader from motorola page. successfully unlocked and rooted but...
problem nr 1 - from that day i was unable to access recovery by any means. every time i accessed it the withe screen with the motorola warning after unlocking came and nothing happened. i discovered this thread forum.xda-developers.com/showthread.php?t=2585755 and was able to change the boot logo from that screen to a regular one, but the problem persisted. tried to solve the problem and came to this thread forum.developers.com/showthread.php?t=2037808. "There's a file in /system/etc/ called install_recovery.sh that may need to be deleted for the custom recovery to stick. You need root to remove it."
converted that install_recovery.sh to bak and rebooted.
problem nr 2 - no access to recovery. lost root privileges. no acess to bootloader. the phone does a full reboot everytime (goes on reding every android app).
tried to upload an new "install_recovery.sh" (the same but renamed) but have no privileges through airdroid.
any suggestions highly appreciated. can i push the file through adb or sanything else?
after opening /system/etc/install-recovery.sh with notepad it reads like this. i guess it was changing the name from .sh to .bak that broke rooting
#!/system/bin/sh
# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc
# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.
/system/etc/install-recovery-2.sh
install-recovery.sh is altered by superSU. You lost root as this file is required for root.
The original file does flash stock recovery on boot (or at least after an OTA AFAIK)
Sounds to me like your original problem of not accessing recovery was maybe due to you using the power button to select recovery option in bootloader rather than volume UP which is the button used to select an option.
No idea why you can't now get to the bootloader at all, just renaming that file would not cause that. I guess altering the boot logo has caused an unknown issue somehow.
Putting back the install-recovery.sh file won't help at all with not being able to boot to bootloader. In actual fact I find it hard to believe you can't get to the bootloader, as if the bootloader was messed up you wouldn't even be able to boot the phone.
Anyway - without root the only way to get the file back in place is to flash the file (ie as a flashable zip) from custom recovery AFAIK. ADB won't work as you can't push a file to /system without using 'insecure ADB' which needs a rooted device.
Maybe search XDA and see if there is some other key combination to access bootloader.
scott_doyland said:
install-recovery.sh is altered by superSU. You lost root as this file is required for root. RIGHT! I altered its extension to .bak, rebooted and lost root access
The original file does flash stock recovery on boot (or at least after an OTA AFAIK)
Sounds to me like your original problem of not accessing recovery was maybe due to you using the power button to select recovery option in bootloader rather than volume UP which is the button used to select an option. Really dont know if that was the mistake. I lost recovery access (but not bootloader) immediately after unlocking the bootloader, when i saw the screen turning blue/violet i took the usb cable and it might have been the mistake.
No idea why you can't now get to the bootloader at all, just renaming that file would not cause that. I guess altering the boot logo has caused an unknown issue somehow. I altered the boot logo because everytime i tried to acess recovery the phone gave me the motorola warning and didn't go to recovery, just booted, after altering the logo the behaviour stayed the same, no recovery, juts normal booting.
Putting back the install-recovery.sh file won't help at all with not being able to boot to bootloader. In actual fact I find it hard to believe you can't get to the bootloader, as if the bootloader was messed up you wouldn't even be able to boot the phone. Yes, no bootloader by any means, the phoe just cold boots and checks every app (it takes a lot of time)
Anyway - without root the only way to get the file back in place is to flash from custom recovery AFAIK. ADB won't work as you can't push a file to /system without using 'insecure ADB' which needs a rooted device.
Click to expand...
Click to collapse
Right. Already tried different forms of adb (mount, remount, su, push, but NADA). Didint go for the custom recovery because i'm noob and dunno what it is (yet) but i'll try to find out. If you can guide me i any direction i really appreciate :good:
Despite all this mess, at least i hope this knowledge serves the community.
If you can't access bootloader and no longer rooted I don't think you are going to be able to flash a custom recovery anyway (custom recovery allows you to backup/restore entire device and flash ROMS).
Without bootloader access you are in a mess as can't access recovery and can't root.
You can't even reflash entire stock ROM inc recovery etc.
Basically unless you get bootloader access you are screwed AFAIK.
Hopefully someone else may have an idea.
As I mentioned before - search XDA and see if there are some button combos that may get you to bootloader rather than normal combos. Or any button combos to hard reset bootloader etc. It doesn't look good though.
screwed is the word scott. at least its a "normal phone", for now, it works normally, the only drag is the slow booting everytime i shut it down, oh and it doesnt shutdown, just reboots
scott
i have bootloader again, dontt know how but i do. can you point me how to root the phone again?
Have a read through this link, my posts in it should explain what to do
http://forum.xda-developers.com/showthread.php?t=2612195
scott_doyland said:
Have a read through this link, my posts in it should explain what to do
http://forum.xda-developers.com/showthread.php?t=2612195
Click to expand...
Click to collapse
Thanks Scott.
The situation got a little worse. Now SO (w7x64 and x32 i have both) do not recognize moto g. I connect usb cable and it only charges.
- if i connect it while off it reboots (every time rebuilds dalvik cache)
- if i connect it while on it only charges but windows doesn't make any sound (nothing at device manager)
- if i connect usb cable (while in bootloder screen) windows recognizes it only as android adb but not as media player (drivers installed). when i do 'adb devices' nothing comes although the phone says usb connected.
at settings i have USB-MTP, USB debugging enabled.
i can power off and acess bootloader screen but at that screen if i choose any option it just cold reboots. no recovery acess, nada! no adb acess.
In bootloader ADB doesn't work by design. Its fastboot you need.
So do in bootloader
fastboot devices
When booted to android AND if you turn on USB debugging in dev options you can do
adb devices
So one you have 'fastboot devices' working, ie PC recognizes device, then you are OK as if need be you can even download and flash complete stock images for everything inc /system, recovery etc to get it back to how it was out of the box.
scott_doyland said:
In bootloader ADB doesn't work by design. Its fastboot you need.
So do in bootloader
fastboot devices
When booted to android AND if you turn on USB debugging in dev options you can do
adb devices
So one you have 'fastboot devices' working, ie PC recognizes device, then you are OK as if need be you can even download and flash complete stock images for everything inc /system, recovery etc to get it back to how it was out of the box.
Click to expand...
Click to collapse
It was a good tip Scott, it kept me walking and this morning i was about to give up :good:
Below you can see what happened. I flashed cwm (for 4.4.2) successfully but when trying to access it phone cold reboots as usual. Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it?
...\root motorola>fastboot devices
TA8830L7VY fastboot
...\root motorola>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7604 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.461s]
finished. total time: 0.728s
>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.267s]
booting...
OKAY [ 0.504s]
finished. total time: 0.772s After this it does a cold reboot
you said i could re-flash a stock image. the phone came with 4.3 but in the meanwhile upgraded to 4.4.2. can i flash 4.3 after having unlocked the bootloader and updated to 4.4.2?. i managed to download both firmwares.
Having read that 4.4.2 bootloader is having trouble with accessing recovery (my case also) i tried to upload 4.3 bootloader. this was the result
...>fastboot-moto-windows.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.836s]
finished. total time: 1.934s
...>fastboot-moto-windows.exe reboot-
bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
i guess everything went right. the phone didnt a cold reboot and went right away to the bootloader. after selecting recovery in this new bootloader i finally managed to have acess to the last CWM 6.0.4.6 recovery. UFFFF!!!
After that i did a wipe cache partition and rebooted. Phone did a cold reboot. after that i follwed the post you mentioned and flashed SUper SU.through CWM
As seen before after renaming install-recovery.sh to .bak root was lost I checked and the file is there again along with the bak so i guess super su created it again.
Check list: Have bootloader. have recovery. have root, i'm on 4.4.2 with 4.3 bootloader. one thing thats not ok, everytime phone reboots android goes on with the following message "android is upgrading --- optimising app x of y" which takes a lot of time. even if i ask for a fast reboot. that was not the usual procedure, the phone just did a fast reboot and nothing more. any advice on this one?
What a enormous trip for someone that didnt knew much about this. Kudos to you for keeping the help!
Sounds like its pretty OK then apart from the 'android is upgrading' message. I would wipe dalvik cache from CWM. Im not 100% sure but I *think* 'android is upgrading' indicates its rebuilding the dalvik cache, although as I say Im not sure. Anyway wiping dalvik cache wont hurt. I'd wipe, reboot and you *may* still get the messages on first reboot, once all complete and phone is fully operational then reboot again and see if messages are gone.
You said you already wiped cache via CWM but may as well wipe that again as well.
If you still get the error go to 'settings/storage and click on 'cached data' and chose to wipe it (this is different from a cache wipe in CWM).
If messages still happen them Im afraid I dont know what else to do (factory reset of course is last resort).
To attempt to answer your other questions:
***************
** can i flash 4.3 after having unlocked the bootloader and updated to 4.4.2? **
I think so, if you have the entire firmware it includes recovery, bootlloader, android, radio images, kernel etc so flashing it in the correct sequence as can be found in other threads should give you complete 4.3 as it was out of the box. However please read other posts related to this as its not something I have done or have read much about.
If you have an entire 4.4.2 firmware (rather than just a 4.4.2 update) then same applies as above, ie flashing it will give you 4.4.2 entirely inc bootloader, recovery etc.
***************
Re bootloaders and recoveries - I havet followed the threads much regarding 4.4.2 and recoveries as its not that relevant to me right now but if 4.3 bootloader is working, ie you can get to recovery etc, I'd be inclined to stick with it.
fastboot boot recovery.img - all this does it boot the recovery.img direct from your PC, works for some people and not others - dont know why. Its not actually booting CWM from your phone.
When on 4.4.2 bootloader after flashing CWM (the 4.4.2 one I assume) did you try booting the recovery that was actually on the phone, eg booting up android then using ADB to issue
adb reboot recovery
OR just try selecting recovery from bootloader using VOL UP
or did you just 'fastboot boot recovery.img'
However as you have CWM on 4.3 bootloader and its working its irrelevant really, was just interested.
** Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it? **
root and/or unlocked bootloader makes no difference to booting into recovery. Booting into recovery should work, Im assuming you did a 'fastboot boot recovery.img' and this is what failed (as I said just above) as opposed to actually booting into the recovery on the phone itself?
Hope the above makes some sense. And I hope wiping dalvik cache etc does the trick.
If you get any other 'funnies' I'd personally install 4.3 images entirely so its out of the box stock and start from there, ie flash 4.3, allow kitkat to do OTA, then flash CWM for 4.4.2 and hope it works, then root.
If CWM for 4.4.2 doesnt work then downgrade bootloader and flash CWM then root.
Im a bit OCD about these things so I'd probably start from scratch anyway to ensure its all 100% nice and clean but thats up to you
Good morning Steve, thanks for your helpful info, once again.
scott_doyland said:
Sounds like its pretty OK then apart from the 'android is upgrading' message. I would wipe dalvik cache from CWM. Im not 100% sure but I *think* 'android is upgrading' indicates its rebuilding the dalvik cache, although as I say Im not sure. Anyway wiping dalvik cache wont hurt. I'd wipe, reboot and you *may* still get the messages on first reboot, once all complete and phone is fully operational then reboot again and see if messages are gone. Again, the same messages.
You said you already wiped cache via CWM but may as well wipe that again as well.
At CWMR there's also these options besides dalvik cache, a) wipe data/factory reset and wipe cache partition. factory reset is pretty obvious, it cleans all your data but does not fully restore 4.4.2 functionality (or does it? and it goes back to 4.3). Wipe cache partition is the same as settings/storgae/cached data?
If you still get the error go to 'settings/storage and click on 'cached data' and chose to wipe it (this is different from a cache wipe in CWM).
If messages still happen them Im afraid I dont know what else to do (factory reset of course is last resort). Does it go back to 4.3?
To attempt to answer your other questions:
***************
If you have an entire 4.4.2 firmware (rather than just a 4.4.2 update) then same applies as above, ie flashing it will give you 4.4.2 entirely inc bootloader, recovery etc. It might not be "entire". What i have 4.3 is 400MB, 4.4.2 is 180 MB, might be an upgrade.
***************
Re bootloaders and recoveries - I havet followed the threads much regarding 4.4.2 and recoveries as its not that relevant to me right now but if 4.3 bootloader is working, ie you can get to recovery etc, I'd be inclined to stick with it.
fastboot boot recovery.img - all this does it boot the recovery.img direct from your PC, works for some people and not others - dont know why. Its not actually booting CWM from your phone. it didint in 4.4.2, now it does.
When on 4.4.2 bootloader after flashing CWM (the 4.4.2 one I assume) did you try booting the recovery that was actually on the phone, eg booting up android then using ADB to issue. I did, but without sucess.
adb reboot recovery
OR just try selecting recovery from bootloader using VOL UP
or did you just 'fastboot boot recovery.img'
However as you have CWM on 4.3 bootloader and its working its irrelevant really, was just interested.
** Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it? **
root and/or unlocked bootloader makes no difference to booting into recovery. Booting into recovery should work, Im assuming you did a 'fastboot boot recovery.img' and this is what failed (as I said just above) as opposed to actually booting into the recovery on the phone itself? Both things failed, the phone just rebooted.
Hope the above makes some sense. And I hope wiping dalvik cache etc does the trick. it did not.
If you get any other 'funnies' I'd personally install 4.3 images entirely so its out of the box stock and start from there, ie flash 4.3, allow kitkat to do OTA, then flash CWM for 4.4.2 and hope it works, then root. I probably will take that road.
If CWM for 4.4.2 doesnt work then downgrade bootloader and flash CWM then root. Yes, at least i know that works.
Im a bit OCD about these things so I'd probably start from scratch anyway to ensure its all 100% nice and clean but thats up to you
Click to expand...
Click to collapse
In brief: Rebooting problem persists even when wiping dalvik cache twice. Now the device is not recognized in windows. Neither on desktop pc w7x64 nor laptop w7x32. have motorola drivers on both. It used to recognize device as mtp (media player xt1032) but not anymore. When connected in bootloader device manager recognizes as android adb. I feel the problem is from the phone and not SO. I'll try to fix it this morning.
If i reflash 4.3 do i have to do anything before? Wipe something? Do a nandroid backup? Do a normal backup? I have a few backup apps but never used any of them.
Great appreciation for your help Steve. Have a nice Sunday.
About the phone not being recognized as mtp, after a brief search it has to do with locking. If it's locked then windows explorer is denied any access for security reasons. As soon as i unlocked it windows recognized the device immediately. -1 problem. only the rebooting stuff now.
:good:
rebooting ptoblem
wyped dalvik and cache data several times
also wiped odex files
fixed permissions in rom manager
behaviour persists. after wiping, the phone goes "upgrading android - optimising 225 apps" after that when rebooting the phone goes "android is upgrading... - optimising 103 apps". factory reset as last resort sigh... i hate that :crying:
I am having the same issue with the phone being boot loader unlocked and when I try to get into recovery through fastboot it just reboots.
Do you have the stock files that you used along the way?
Thanks. I have never had a phone give me this much hassle before ??:'(
I have been trying to unbrick my phone for 2 days now. So right now when I boot it goes through the boot screens then it goes black and just says
"process system ins't responding" , so if i press wait that error will just pop up again. Otherwise all I get is a black screen and have to force reboot.
So here is what I have done so far:
When bought phone I did S-OFF and have it unlocked "I believe it was with firewater, but that was months ago",
Installed CWM 6.0.4.8 <--im pretty sure thats the one.
Created nandroid
Then I installed SKYFALL and used that ever since.
Decided I wanted ViperOne.
Read many post and here is where the fun started.
Restored my origional nandroid.
fastboot flashed stock recovery then erase cache
booted nandroid. and installed downloaded 4.4.3 OTA
phone rebooted just fine.
fastboot flashed twrp recovery (openrecovery-twrp-2.8.0.3-m8_wlv.img) then erase cache
booted recovery and installed ViperOne.
then error process system isn't responding.
Since then I have repeated those steps. I have also tried CleanRom and RKDN and those get stuck in loading loops. I have tried the RUU options, and tried RUU and fastboot to get back to the 1.55.605.2 completely stock as it can be with a stock image or the nandroid and nothing seems to work. Just get the same errors. Now I am stuck and unsure what to do or how to go about fixing this....
Not sure if you've already tried this, but might help.
Load the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
After that, go into the stock recovery and do a factory reset.
dab1414 said:
I have been trying to unbrick my phone for 2 days now. So right now when I boot it goes through the boot screens then it goes black and just says
"process system ins't responding" , so if i press wait that error will just pop up again. Otherwise all I get is a black screen and have to force reboot.
So here is what I have done so far:
When bought phone I did S-OFF and have it unlocked "I believe it was with firewater, but that was months ago",
Installed CWM 6.0.4.8 <--im pretty sure thats the one.
Created nandroid
Then I installed SKYFALL and used that ever since.
Decided I wanted ViperOne.
Read many post and here is where the fun started.
Restored my origional nandroid.
fastboot flashed stock recovery then erase cache
booted nandroid. and installed downloaded 4.4.3 OTA
phone rebooted just fine.
fastboot flashed twrp recovery (openrecovery-twrp-2.8.0.3-m8_wlv.img) then erase cache
booted recovery and installed ViperOne.
then error process system isn't responding.
Since then I have repeated those steps. I have also tried CleanRom and RKDN and those get stuck in loading loops. I have tried the RUU options, and tried RUU and fastboot to get back to the 1.55.605.2 completely stock as it can be with a stock image or the nandroid and nothing seems to work. Just get the same errors. Now I am stuck and unsure what to do or how to go about fixing this....
Click to expand...
Click to collapse
I can team viewer with you and checkout what's up. What error do you get on RUU flashing?
jsaxon2 said:
Not sure if you've already tried this, but might help.
Load the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
After that, go into the stock recovery and do a factory reset.
Click to expand...
Click to collapse
I had this ruu already, and the MD5 matched up. So I downloaded a new copy anyways, However I am unable to flash it. On another note I did try other non 443 rru's that did flash but factory reset did not work.
dottat said:
I can team viewer with you and checkout what's up. What error do you get on RUU flashing?
Click to expand...
Click to collapse
when trying to flash
Code:
C:\Users\balddav\My Documents\M8\ruu\443>fastboot oem rebootRUU
C:\Users\balddav\My Documents\M8\ruu\443>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
error: cannot load '0P6BIMG.zip'
Then I push file to root of external sd card:
once boot to HBOOT
Loading...[0P6BIMG.zip]
and after 1 hour still loading. then I tried to load 442 ruu and this:
Code:
C:\Users\balddav\My Documents\M8\ruu\442>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (825739 KB)...
OKAY [ 35.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 36.033s
I can ruu the 443 firmware from this post http://forum.xda-developers.com/showthread.php?t=2723159with no issues.
dab1414 said:
I had this ruu already, and the MD5 matched up. So I downloaded a new copy anyways, However I am unable to flash it. On another note I did try other non 443 rru's that did flash but factory reset did not work.
when trying to flash
Code:
C:\Users\balddav\My Documents\M8\ruu\443>fastboot oem rebootRUU
C:\Users\balddav\My Documents\M8\ruu\443>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
error: cannot load '0P6BIMG.zip'
Then I push file to root of external sd card:
once boot to HBOOT
Loading...[0P6BIMG.zip]
and after 1 hour still loading. then I tried to load 442 ruu and this:
Code:
C:\Users\balddav\My Documents\M8\ruu\442>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (825739 KB)...
OKAY [ 35.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 36.033s
I can ruu the 443 firmware from this post http://forum.xda-developers.com/showthread.php?t=2723159with no issues.
Click to expand...
Click to collapse
Flash the firmware and then go right to RUU flashing via sd.
dottat said:
Flash the firmware and then go right to RUU flashing via sd.
Click to expand...
Click to collapse
I have tried that and it hangs on loading. But I will try it again.
When I woke up I noticed my phone actually booted up normally. I think what I did different was reformat external drive. Copy the 442 RUU to it. I flashed the 442 firmware, then reboot to hboot it loaded the RUU, went to sleep and it worked.
So when I get a chance today I will make sure I have a good copy of the 443 firmware and try it the same way I just did 442, and post my steps.
Thanks for your help so far.
removed
So I was just trying something out and downloaded the OTA update and installed it. Everything looked like it updated fine so I just rebooted and the error process system isn't responding came back when rebooting. So I am trying the 443 firmware and RUU.
One thing I noticed from this post http://forum.xda-developers.com/showthread.php?t=2723159 is there is no boot or recovery, so after flashing the 443 firmware, I flashed the boot and recovery images found on the same thread. then I inserted the sd card with the RUU from here http://forum.xda-developers.com/verizon-htc-one-m8/development/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144 and this time HBOOT loaded the file and installed with no errors.
Now on booting up it still says Process system isn't responding.
dab1414 said:
So I was just trying something out and downloaded the OTA update and installed it. Everything looked like it updated fine so I just rebooted and the error process system isn't responding came back when rebooting. So I am trying the 443 firmware and RUU.
One thing I noticed from this post http://forum.xda-developers.com/showthread.php?t=2723159 is there is no boot or recovery, so after flashing the 443 firmware, I flashed the boot and recovery images found on the same thread. then I inserted the sd card with the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144 and this time HBOOT loaded the file and installed with no errors.
Now on booting up it still says Process system isn't responding.
Click to expand...
Click to collapse
You did not need to flash boot and recovery. In fact, the ruu will do that automatically for you.
Did your phone calm down? Sometimes on boot if blinkfeed and other apps try to update it can crash. . Reboot once more after that and see what happens.
dottat said:
You did not need to flash boot and recovery. In fact, the ruu will do that automatically for you.
Click to expand...
Click to collapse
I realized that shortly after I typed it, I looked in the zip files.
dottat said:
Did your phone calm down? Sometimes on boot if blinkfeed and other apps try to update it can crash. . Reboot once more after that and see what happens.
Click to expand...
Click to collapse
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo%20Oct%2016%2C%2023%2039%2048.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video%20Oct%2016%2C%2023%2042%2033.mov?dl=0
I have tried rebooting several times with the same results.
dab1414 said:
I realized that shortly after I typed it, I looked in the zip files.
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo Oct 16, 23 39 48.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video Oct 16, 23 42 33.mov?dl=0
I have tried rebooting several times with the same results.
Click to expand...
Click to collapse
I'm at a loss, the only other thing I could tell you to try would be to remove the sdcard and try rebooting.
I have a few comments. Go back and flash the 4.4.3 RUU from fastboot. Make sure your SDK is up to date with the latest and greatest. Your firmware is ok. In looking through your log from the fastboot attempt, you got error - Failed (remote: 32 header error). This means the zip couldn’t be read and unzipped properly. Something is borked. Make sure you have lots of room on your internal SD card too.
dab1414 said:
I realized that shortly after I typed it, I looked in the zip files.
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo Oct 16, 23 39 48.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video Oct 16, 23 42 33.mov?dl=0
I have tried rebooting several times with the same results.
Click to expand...
Click to collapse
You could have hosed partitions. I can team viewer and try a couple things to see if we can get it fixed.
jsaxon2 said:
I'm at a loss, the only other thing I could tell you to try would be to remove the sdcard and try rebooting.
Click to expand...
Click to collapse
Irieone said:
I have a few comments. Go back and flash the 4.4.3 RUU from fastboot. Make sure your SDK is up to date with the latest and greatest. Your firmware is ok. In looking through your log from the fastboot attempt, you got error - Failed (remote: 32 header error). This means the zip couldn’t be read and unzipped properly. Something is borked. Make sure you have lots of room on your internal SD card too.
Click to expand...
Click to collapse
dottat said:
You could have hosed partitions. I can team viewer and try a couple things to see if we can get it fixed.
Click to expand...
Click to collapse
Finally!!! Thank you all for the help.
So I removed my sdcard, then installed twrp, then went and advanced wipe and selected every box ( all i did before was factory resets). Then flashed firmware through ruu mode. Then reinserted sdcard with the 0P6BIMG file. rebooted to bootloader selected hboot, then when done rebooted and it was working fine. then reinstalled twrp and installed viperone, and rolling through just fine. Guess there was something floating around the factory reset didnt wipe.
Again thank you all for your time and help to resolve my screwup!!
dab1414 said:
Finally!!! Thank you all for the help.
So I removed my sdcard, then installed twrp, then went and advanced wipe and selected every box ( all i did before was factory resets). Then flashed firmware through ruu mode. Then reinserted sdcard with the 0P6BIMG file. rebooted to bootloader selected hboot, then when done rebooted and it was working fine. then reinstalled twrp and installed viperone, and rolling through just fine. Guess there was something floating around the factory reset didnt wipe.
Again thank you all for your time and help to resolve my screwup!!
Click to expand...
Click to collapse
Yeah....I think your partition was wonked. Twrp even has a repair option built in now for ext4 partitions under advanced wipe.
Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.
Sneddy32 said:
Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.
Click to expand...
Click to collapse
What is the output of fastboot flash cache cache.img ?
You may need to flash cache.img and stock recovery.inmg and then try a manual wipe of /cache via stock recovery.
Sneddy32 said:
Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.
Click to expand...
Click to collapse
Try what rootSU said to do and avoid using toolkits in the future. It seems that about 95% of the "help I bricked my phone!" threads stem from using toolkits.
Sent from my iPhone 6 using Tapatalk
In the past I've never used toolkits but figured by now they might be fairly reliable. Big mistake.
rootSU said:
What is the output of fastboot flash cache cache.img ?
You may need to flash cache.img and stock recovery.inmg and then try a manual wipe of /cache via stock recovery.
Click to expand...
Click to collapse
Is this what you mean?
Code:
c:\android-sdk\platform-tools>fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.577s]
sending 'cache' <13348 KB>...
OKAY [ 0.639s]
writing 'cache'...
OKAY [ 1.086s]
finished. total time: 2.305s
Booted into stock recovery - cache wipe complete. Rebooted and phone went into the Android Updating graphic (wiggly ears & cog). Just a cache partition wipe or factory reset?
Should I now attempt flashall.bat??
I'm using the LRX21o from the Google Dev website. I'm guessing at this point it makes no difference?
Yeah that's what I meant. Looks successful.
Next I guess flashing everything is next step.
So nothing changed, and I decided to give flash-all.bat another go. Same thing. Stalled on 'erasing cache'.
When I forced reboot the error "Too many links" came up.
I went back in and flashed cache.img thinking I might be able to finish off the job. No love. Back to the updating graphic.
Now when I try to go into recovery to start again it just goes into the upgrading graphic.
Bump...?
Return it.
Nexus 5 stuck on 'formatting /data' screen after factory image flashing
Sorry for the long post. I just want to ensure I am providing all relevant history.
I have a Nexus 5 (Hammerhead) 32gb device, stock with no rooting. I mean, I had never done anything special on it ever.
1. Recently I started getting Google Play Store related problems, first 194 error and then couple of days back 495 (I think). After trying switching on/off, clearing cache and some other similar ways to fix this, I decided to do a factory reset :crying:
2. I backed up all my data, and followed the documented steps for factory reset. The phone got stuck on 'erasing'. After waiting for over 24 hours, I finally figured out that this 'erasing' is not going to complete, ever.
3. So I again did some research and figured that I should do a fastboot recovery. Tried that with no difference. Recovery again took me to 'erasing' screen.
4. Some more research and then I decided to flash a factory image using ADB. I was (and still am) a complete newbie, so first I figured out what was ADB and how to get to it. After completing the installation, I found out Nexus 5 factory images. There was no mention of which ones to chose, so I just picked up the latest one.
This is what I really followed:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
https://www.youtube.com/watch?v=DRp5jJO34PE
5. Having learnt my lessons, I read the flashing instructions many times and also watched some videos 3-4 times. Once I was confident that no more information was going to be had, and the phone was unlocked (fastboot oem unlock) I went ahead with the flashing. I did it step by step - bootloader, radio and they recovery image. The last one failed.
6. I did some more research and found a method which told me to unzip the last image and flash the component images one by one. I did. Success! However, the phone did not reboot by itself as the guide said it would. So I tried to boot it manually.
7. I did not get the dead android with red exclamation mark. Instead, I got an alive android with gears whirring on its tummy and back. Pressing power + vol-up button told me that this was the 'formatting /data' screen. I am unable to get past this screen. I am supposed to get to a screen where I can wipe data and cache etc. But I cannot get to it.
8. I have tried to wait it out (16 hours) and tried flashing the images again. Ultimately, I end up here.
9. I am unable to find any answers on what to do if stuck on this screen. So this is the end? Is my phone bricked? Is there anything else I can try? Will trying TWRP way help or is that just another way to same failure?
I would appreciate if there is anybody out there who can help me get my phone working again, or point me to a thread which helps me do it. Thanks!
Just wait it took me 5 hours of waiting
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
dicecuber said:
Just wait it took me 5 hours of waiting
Click to expand...
Click to collapse
I doubt it. 12 more hours have passed with no change.
eross said:
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
Click to expand...
Click to collapse
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Tom2403 said:
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Click to expand...
Click to collapse
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
try this: fastboot format cache
matt1515 said:
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
Click to expand...
Click to collapse
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
Glad to hear you got it up and running! No problem at all feels great to bring something f'd back to life.
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
dmuml10 said:
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
Click to expand...
Click to collapse
Go into bootloader and format the cache: fastboot format cache
inimaitimepass said:
Go into bootloader and format the cache: fastboot format cache
Click to expand...
Click to collapse
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
dmuml10 said:
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
Click to expand...
Click to collapse
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
inimaitimepass said:
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
Click to expand...
Click to collapse
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
dmuml10 said:
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
Click to expand...
Click to collapse
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
inimaitimepass said:
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
Click to expand...
Click to collapse
Thanks for help.
I flashed philz_touch recovery. From there I did factory reset and after that I executed this commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Now my phone works.:victory:
dmuml10 said:
Now my phone works.:victory:
Click to expand...
Click to collapse
Good to hear. Weren't you using a custom recovery before philz'?
inimaitimepass said:
Good to hear. Weren't you using a custom recovery before philz'?
Click to expand...
Click to collapse
No. I only used stock recovery before philz.
Hi everyone!
I’m having a soft bootloop of my OnePlus 8t 12/256, KB2005, OOS 13, F13, International or EU firmware.
No root, locked bootloader, native unmodified recovery.
The phone reboots in 1-2 seconds after OOS13 is loaded, disregard the activity I try to do.
The issue started after I have rebooted the phone. Before reboot, it was running normally, no significant glitches.
Some time before this reboot/issue I have potentially:
had an issue with the OTA update installation,
have installed oneplus dialer and sms (to replace the google’s), installed modified launcher to get rid of the google shelf on the left.
I can enter the fastboot and recovery, and I have used ADB in the past on the device, but cannot get it running now since it restarts before connected.
Tried to no avail:
fastboot set_active other
fastboot erase cache
Both are failing on the locked device:
Setting current slot to 'a'
FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Erasing 'cache'
FAILED (remote: 'Erase is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
The same goes for fastboot boot twrp.img.
Sadly I don’t have a backup of my personal files on the device, that’s why I try to either fix it, or at least recover the data from it before I go to factory reset/unbricking options.
I was trying to fetch the userdata partition (225gb) via MsmDownloadTool – it reported that the file successfully downloaded within 15s, but no file was even created. It worked with boot.img though (~96mb).
I have also tried to return the default system apps to google phone and sms, create a guest user (unable to fully switch to it before reboot), stay in airplane mode, on/off wifi, etc. Still it reboots every few seconds which makes it almost impossible to navigate in the menu (2-3 clicks are possible max).
I’m unable to check if I have “install updates automatically” in the developer options (I bet it is disabled), also unable to navigate to clearing cache of the system launcher.
Any help in trying to fix/recover the data from the device is appreciated.
atomaniac said:
Hi everyone!
I’m having a soft bootloop of my OnePlus 8t 12/256, KB2005, OOS 13, F13, International or EU firmware.
No root, locked bootloader, native unmodified recovery.
The phone reboots in 1-2 seconds after OOS13 is loaded, disregard the activity I try to do.
The issue started after I have rebooted the phone. Before reboot, it was running normally, no significant glitches.
Some time before this reboot/issue I have potentially:
had an issue with the OTA update installation,
have installed oneplus dialer and sms (to replace the google’s), installed modified launcher to get rid of the google shelf on the left.
I can enter the fastboot and recovery, and I have used ADB in the past on the device, but cannot get it running now since it restarts before connected.
Tried to no avail:
fastboot set_active other
fastboot erase cache
Both are failing on the locked device:
The same goes for fastboot boot twrp.img.
Sadly I don’t have a backup of my personal files on the device, that’s why I try to either fix it, or at least recover the data from it before I go to factory reset/unbricking options.
I was trying to fetch the userdata partition (225gb) via MsmDownloadTool – it reported that the file successfully downloaded within 15s, but no file was even created. It worked with boot.img though (~96mb).
I have also tried to return the default system apps to google phone and sms, create a guest user (unable to fully switch to it before reboot), stay in airplane mode, on/off wifi, etc. Still it reboots every few seconds which makes it almost impossible to navigate in the menu (2-3 clicks are possible max).
I’m unable to check if I have “install updates automatically” in the developer options (I bet it is disabled), also unable to navigate to clearing cache of the system launcher.
Any help in trying to fix/recover the data from the device is appreciated.
Click to expand...
Click to collapse
Try to boot OOS in safe mod and see if it working good or not.
If it's working good, delete modifications you've made to the system (oneplus apps or smth else if you did it).
It it's still rebooting in safe mod, you can try to change slots, to boot partition which was active before OTA update, it can be working good.
Rootk1t said:
Try to boot OOS in safe mod and see if it working good or not.
If it's working good, delete modifications you've made to the system (oneplus apps or smth else if you did it).
It it's still rebooting in safe mod, you can try to change slots, to boot partition which was active before OTA update, it can be working good.
Click to expand...
Click to collapse
Thanks for your suggestions. Unfortunately, the issue is exactly the same in the Safe Mode. 1-2 seconds that the system is running are hardly enough to uninstall anything, but I've tried my best about it.
As for changing the slots - it does not work as the bootloader is locked.