Related
Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?
One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...
give a try to omap flash
Good Luck
samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus
Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
Hi
My GNex (Unlocked GSM variant) is rebooting continuously. I'm on Resurrection Remix rom (not blaming the rom, just mentioning it), TWRP: 2.8.5.0
The phone boots up, shows the lock screen and reboots within 10 seconds. This is happening continuously....
I booted into Recovery and did a restore(of existing nandroid)/wiped/repaired/re-partitioned but nothing works, it'd just say successful but the ROM/Data doesnt change at all.
Tried flashing via ODIN, but it fails after transmitting system.img to the device. Tried using pit also. Used different cables/USB ports/machines just to be sure.
Once after the phone booted up, I somehow managed to disable the Wifi (in 10 seconds that the phone was ON)and it got disconnected. And after the auto-reboot the wifi somehow was still ON.
I assume that the memory blocks have gone to read-only mode.
Similar thread: http://forum.xda-developers.com/general/xda-assist/galaxy-nexus-restarting-continuously-t3046586
I'm posting it here for visibility. Please help
Regards,
sasuketobi
Have you tried installing the latest factory image from Google?
If not, just download it (I cannot post links now, because I have less than 10 posts, but you can google it by yourself - galaxy nexus factory image)
For GSM maguro, use yakju or takju with Google Wallet support.
Extract zip somewhere to your PC, connect your Nexus with your PC in bootloader mode and run flash-all.bat.
After this, you will have fully working 4.3 stock Android.
Then you should try again flashing recovery, custom rom and kernel.
LamarrCZ said:
Have you tried installing the latest factory image from Google?
If not, just download it (I cannot post links now, because I have less than 10 posts, but you can google it by yourself - galaxy nexus factory image)
For GSM maguro, use yakju or takju with Google Wallet support.
Extract zip somewhere to your PC, connect your Nexus with your PC in bootloader mode and run flash-all.bat.
After this, you will have fully working 4.3 stock Android.
Then you should try again flashing recovery, custom rom and kernel.
Click to expand...
Click to collapse
Hi,
I've tried this and also using the flashboot commands separately but with no luck. Thanks for your suggestion though.
sasuketobi said:
Hi
My GNex (Unlocked GSM variant) is rebooting continuously. I'm on Resurrection Remix rom (not blaming the rom, just mentioning it), TWRP: 2.8.5.0
The phone boots up, shows the lock screen and reboots within 10 seconds. This is happening continuously....
I booted into Recovery and did a restore(of existing nandroid)/wiped/repaired/re-partitioned but nothing works, it'd just say successful but the ROM/Data doesnt change at all.
Tried flashing via ODIN, but it fails after transmitting system.img to the device. Tried using pit also. Used different cables/USB ports/machines just to be sure.
Once after the phone booted up, I somehow managed to disable the Wifi (in 10 seconds that the phone was ON)and it got disconnected. And after the auto-reboot the wifi somehow was still ON.
I assume that the memory blocks have gone to read-only mode.
Similar thread: http://forum.xda-developers.com/general/xda-assist/galaxy-nexus-restarting-continuously-t3046586
I'm posting it here for visibility. Please help
Regards,
sasuketobi
Click to expand...
Click to collapse
If every attempt to revive your phone fails, then I'm afraid that you will have to replace the motherboard in your phone
Wish39 said:
If every attempt to revive your phone fails, then I'm afraid that you will have to replace the motherboard in your phone
Click to expand...
Click to collapse
Yeah, I've been thinking the same. Tried everything that I can and it's still in the same state.
Hi,
today my Galaxy Nexus started doing the same things you described. All trys to factory reset the phone or to flash a new rom were worthless. Did you get a solution for the Problem or did you change the motherboard?
Thank you for your help
Jochen
Even my keeps on rebooting continuously.. did any one find any solution...Please help..Thanks in anticipation of your cooperation..
same here, if anyone could help I would appreciate
followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?
I have an unrooted Pixel 3 XL and am unable to install the December update. Each time I try, my phone reboots and sits on the updating screen with the progress bar for several minutes, then reboots and tries again two more times, then finally boots back to the home screen with a notification saying "Couldn't install system update." If I click on this notification I can "Try Again" but it always does the same thing.
Does anyone know what could be causing my phone not to update, or how to look at logs that would tell me what's going on?
Jinded said:
I have an unrooted Pixel 3 XL and am unable to install the December update. Each time I try, my phone reboots and sits on the updating screen with the progress bar for several minutes, then reboots and tries again two more times, then finally boots back to the home screen with a notification saying "Couldn't install system update." If I click on this notification I can "Try Again" but it always does the same thing.
Does anyone know what could be causing my phone not to update, or how to look at logs that would tell me what's going on?
Click to expand...
Click to collapse
unrooted and bootloader locked?
Jinded said:
I have an unrooted Pixel 3 XL and am unable to install the December update. Each time I try, my phone reboots and sits on the updating screen with the progress bar for several minutes, then reboots and tries again two more times, then finally boots back to the home screen with a notification saying "Couldn't install system update." If I click on this notification I can "Try Again" but it always does the same thing.
Does anyone know what could be causing my phone not to update, or how to look at logs that would tell me what's going on?
Click to expand...
Click to collapse
Could you be using the wrong image?
Sent from my iPad using Tapatalk
ptn107 said:
unrooted and bootloader locked?
Click to expand...
Click to collapse
Yes I have the Verizon variant so unrooted and bootloader locked.
zebradude said:
Could you be using the wrong image?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I'm just running the regular system update process through Settings > System > Update, so unless my phone got confused about what phone it is I'm not sure how this would happen haha.
The only "non-regular" modification I've made to my phone is that I use Tasker and have granted it several system-level permissions through ADB, but this has never impacted a system update in the past...
Jinded said:
I'm just running the regular system update process through Settings > System > Update, so unless my phone got confused about what phone it is I'm not sure how this would happen haha.
Click to expand...
Click to collapse
I see. Sorry I thought you were side loading the image. OTA wow weird.
I've thought about trying to sideload the OTA, but on the OTA download site the first prerequisite listed is that there are currently no pending system updates, which is clearly not the case for me. Anyone know if there's actually a risk in attempting this?
https://developers.google.com/android/ota
Jinded said:
I've thought about trying to sideload the OTA, but on the OTA download site the first prerequisite listed is that there are currently no pending system updates, which is clearly not the case for me. Anyone know if there's actually a risk in attempting this?
https://developers.google.com/android/ota
Click to expand...
Click to collapse
There is no risk sideloading an OTA via recovery. What do you have to lose?
v12xke said:
There is no risk sideloading an OTA via recovery. What do you have to lose?
Click to expand...
Click to collapse
Well worst case I'd have to wipe and flash factory image, but I really don't want to go through that right now, especially this being the first time I don't have Titanium to restore everything haha
Jinded said:
Well worst case I'd have to wipe and flash factory image, but I really don't want to go through that right now, especially this being the first time I don't have Titanium to restore everything haha
Click to expand...
Click to collapse
I think you misunderstand. You cannot flash the factory image because you are BL locked. Sideloading an OTA image via recovery is also called a "rescue OTA". Don't worry...your bootloader is locked so you're not going to hose anything. You are stuck now... cannot use system update. Flashing the OTA is not going to wipe your data, or render your phone unbootable. It MAY however get you "unstuck". Just follow Google's detailed instructions on the page you linked. Good luck! :good:
v12xke said:
I think you misunderstand. You cannot flash the factory image because you are BL locked. Sideloading an OTA image via recovery is also called a "rescue OTA". Don't worry...your bootloader is locked so you're not going to hose anything. You are stuck now... cannot use system update. Flashing the OTA is not going to wipe your data, or render your phone unbootable. It MAY however get you "unstuck". Just follow Google's detailed instructions on the page you linked. Good luck! :good:
Click to expand...
Click to collapse
Hmm so it seems I can't even sideload the OTA, I'm guessing cause of the locked bootloader. When I reboot to recovery the screen just says "No command" and no buttons on the phone do anything, I see no option on the phone to sideload via ADB. Running "adb devices" on my connected laptop shows the active device in host mode, but I think it has to be in sideload mode for it to work. I've also tried clearing cache and data from the Google app before trying the regular update method again, but that didn't help either.
Jinded said:
Hmm so it seems I can't even sideload the OTA, I'm guessing cause of the locked bootloader. When I reboot to recovery I see no option on the phone to update via ADB, and "adb devices" shows no active devices. I've also tried clearing cache and data from the Google app but that didn't help either...
Click to expand...
Click to collapse
1) You do not need an unlocked bootloader to sideload an OTA.
2) Everyone with P2/P3/P4 stock recovery can sideload an OTA via adb. You don't even have to have USB debugging enabled in Developer settings. It is hard coded into recovery.
3) You probably aren't in recovery mode. Youtube a video on how to get into recovery mode, or Google "rescue OTA" or "sideload OTA via adb".
4) Upload a photo of your recovery screen
5) Double check you are using the latest adb/fastboot binaries
6) Report back
v12xke said:
1) You do not need an unlocked bootloader to sideload an OTA.
2) Everyone with P2/P3/P4 stock recovery can sideload an OTA via adb. You don't even have to have USB debugging enabled in Developer settings. It is hard coded into recovery.
3) You probably aren't in recovery mode. Youtube a video on how to get into recovery mode, or Google "rescue OTA" or "sideload OTA via adb".
4) Upload a photo of your recovery screen
5) Double check you are using the latest adb/fastboot binaries
6) Report back
Click to expand...
Click to collapse
You're right on #3, I didn't properly enter recovery mode - after getting to the "No Command" screen I was pressing and holding power and vol+ together (which didn't do anything) instead of holding power and then pressing vol+ to enter the menu. Anyway, once I got in I pressed "Apply update from ADB," confirmed via "adb sideload" that the phone was in the right mode, and started the OTA sideload (see picture for the PowerShell output). Once this completed successfully, I rebooted the phone but it did the same thing as before - 3 bootloops then boot into the home screen with an "update failed" notification.
Jinded said:
You're right on #3, I didn't properly enter recovery mode - after getting to the "No Command" screen I was pressing and holding power and vol+ together (which didn't do anything) instead of holding power and then pressing vol+ to enter the menu. Anyway, once I got in I pressed "Apply update from ADB," confirmed via "adb sideload" that the phone was in the right mode, and started the OTA sideload (see picture for the PowerShell output). Once this completed successfully, I rebooted the phone but it did the same thing as before - 3 bootloops then boot into the home screen with an "update failed" notification.
Click to expand...
Click to collapse
I would have expected a more verbose output but have not personally had to do a rescue OTA (my phones are all BL unlocked), so I don't know what the correct output looks like... but note there are no errors. Are you positive you are using the latest binaries I linked to? My version is 29.0.5 (October 2019). "adb version"
You stated you were unrooted, but are you BL unlocked? If not, you only have one option left that I am aware of. That is to to a factory data reset from recovery (or settings). If you were to contact Google Support and let them know where you are now and what you have done so far, they are going to have you FDR. The full OTA you flashed via adb is more complete than an incremental OTA and should have corrected your issue. If you are not BL locked yet, but have an unlockable phone you would still have to wipe data during the unlocking process, so go ahead and start backing your stuff up anyway. Good luck! :good:
v12xke said:
I would have expected a more verbose output but have not personally had to do a rescue OTA (my phones are all BL unlocked), so I don't know what the correct output looks like... but note there are no errors. Are you positive you are using the latest binaries I linked to? My version is 29.0.5 (October 2019). "adb version"
You stated you were unrooted, but are you BL unlocked? If not, you only have one option left that I am aware of. That is to to a factory data reset from recovery (or settings). If you were to contact Google Support and let them know where you are now and what you have done so far, they are going to have you FDR. The full OTA you flashed via adb is more complete than an incremental OTA and should have corrected your issue. If you are not BL locked yet, but have an unlockable phone you would still have to wipe data during the unlocking process, so go ahead and start backing your stuff up anyway. Good luck! :good:
Click to expand...
Click to collapse
I have the Verizon variant, so bootloader cannot be unlocked (OEM unlocking is disabled in Developer Options).
adb version shows me:
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
I think at this point I'm gonna wait for the January update and see if that one takes. Thanks for all the help!
Jinded said:
I have the Verizon variant, so bootloader cannot be unlocked (OEM unlocking is disabled in Developer Options).
adb version shows me:
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
I think at this point I'm gonna wait for the January update and see if that one takes. Thanks for all the help!
Click to expand...
Click to collapse
Well, you learned something here anyway. I believe incremental OTA's need to be applied sequentially, but since I always flash the full image I'm admittedly not very versed on OTA's. You may want to research that point further so you don't end up waiting two weeks for naught. Also would not hurt to make sure to manually sync backups, verify photos is backing to the cloud, and in TiBu do a "force redo of your backups" then zip that entire folder, transferring it safely off the phone. Best of luck and Merry Christmas!
v12xke said:
Well, you learned something here anyway. I believe incremental OTA's need to be applied sequentially, but since I always flash the full image I'm admittedly not very versed on OTA's. You may want to research that point further so you don't end up waiting two weeks for naught. Also would not hurt to make sure to manually sync backups, verify photos is backing to the cloud, and in TiBu do a "force redo of your backups" then zip that entire folder, transferring it safely off the phone. Best of luck and Merry Christmas!
Click to expand...
Click to collapse
Well that's the issue - I don't have the option to use an app like TiBu because I can't have root, so as far as I know I basically have to rely on Google's automatic backups/restores during initial phone setup, if I end up doing a factory reset. Before this phone I've always had a rooted phone with TiBu doing nightly backups to the cloud, so not having that has already been giving me anxiety the entire time I've had this phone haha.
I think the biggest thing I learned is to never buy a Verizon model phone again.
Jinded said:
Well that's the issue - I don't have the option to use an app like TiBu because I can't have root, so as far as I know I basically have to rely on Google's automatic backups/restores during initial phone setup, if I end up doing a factory reset. Before this phone I've always had a rooted phone with TiBu doing nightly backups to the cloud, so not having that has already been giving me anxiety the entire time I've had this phone haha.
Click to expand...
Click to collapse
Ah, ok. Well the Google backup has improved dramatically with 9 & 10 and works quite well. Hope you get it sorted soon. :good:
@Jinded, what happens if you try to sideload the OTA for the same version you currently have?
I have been wondering in a different thread, if the Goggle OTAs will work well on Verizon devices. It used to be there were device specific releases on the Google site as well as the general releases. Things like vendor and modem would likely be different.
Edit:
Reading through the forum, this post suggests that settings that are enabled in November are not available in December, preventing the update. Booting to safe mode will probably reset the ROM settings without factory resetting. Less to set back up.
So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?
banshee28 said:
So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?
Click to expand...
Click to collapse
Try Android Flash Tool and leave all the boxes unchecked.
Alternatively, since you can get into fastboot you could flash the factory image, but beforehand modify the flash-all.bat file by removing the -w (this will allow you to keep data).
Lughnasadh said:
Try Android Flash Tool and leave all the boxes unchecked.
Alternatively, since you can get into fastboot you could flash the factory image, but beforehand modify the flash-all.bat file by removing the -w (this will allow you to keep data).
Click to expand...
Click to collapse
So I should have mentioned this... I used both Pixel Flasher and Android Flash Tool with same results on each. I have also used both tools successfully to update previous months updates with NO issues.
banshee28 said:
So I should have mentioned this... I used both Pixel Flasher and Android Flash Tool with same results on each. I have also used both tools successfully to update previous months updates with NO issues.
Click to expand...
Click to collapse
I'm not sure about OTA as I've always used the full image but the full image version (if I'm not mistaken) needs a certain amount of storage to unpack everything it needs to install. There might not be enough room.
banshee28 said:
So I may have caused this by filling up the storage taking some family videos, but here is what happened:
P6P working great for months now, unlocked boot-loader, rooted with latest Magisk, flashed May OTA images last moth and updated to Jun the other day. NO issues after the flash and phone ran fine even after several reboots.
The other day after I filled up the storage, I connected to PC and moved off some videos to make space. Pretty sure this worked and when done, I decided to do a reboot. After that, it never booted fully and after animation rebooted continuously.
I have since flashed on both slots (a/b), May and June OTA images, and it still will not boot. I am pretty sure IF I WIPE DATA, this will work, but my goal here is to try everything possible to not have to do that this time. I know it would have been best to have a backup, but that's another discussion.
Goals would be:
1) Full boot into OS w/o wipe
2) ADB access so I could at least pull some files off before resorting to wiping data.
Fastboot of course works fine, and adb connects for 10 seconds or so while animation is going, but not sure what I can do during this quick time?
Could that camera filling up storage have caused these issues?
I think if we had something like TWRP like back in the days, I could use adb, but dont think thats around these days.
Any advise?
Click to expand...
Click to collapse
Have you tried booting into safe mode? This is what I would do:
Flash the latest OTA in recovery mode. Then during restart, as soon as you see Google Boot animation, hold volume down.
Is your Bootloader unlocked? (When you boot into fastboot mode, does it say unlocked?).
Alekos said:
Have you tried booting into safe mode? This is what I would do:
Flash the latest OTA in recovery mode. Then during restart, as soon as you see Google Boot animation, hold volume down.
Is your Bootloader unlocked? (When you boot into fastboot mode, does it say unlocked?).
Click to expand...
Click to collapse
Yes bootloader is unlocked. Tried volume down right after animation and it took me into fastboot?
Tulsadiver said:
I'm not sure about OTA as I've always used the full image but the full image version (if I'm not mistaken) needs a certain amount of storage to unpack everything it needs to install. There might not be enough room.
Click to expand...
Click to collapse
Actually I am flashing the factory images I think they are called from here: Images
So maybe these are not OTA. I have only used these images.
banshee28 said:
Yes bootloader is unlocked. Tried volume down right after animation and it took me into fastboot?
Click to expand...
Click to collapse
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
banshee28 said:
Actually I am flashing the factory images I think they are called from here: Images
So maybe these are not OTA. I have only used these images.
Click to expand...
Click to collapse
Correct, those are not the OTA files, those are the full factory images. For reference, the OTAs are here Full OTA Images for Nexus and Pixel Devices, although I, too, prefer the full factory image, but the OTA as suggested by @Alekos above would be worth a try.
roirraW edor ehT said:
Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
Correct, those are not the OTA files, those are the full factory images. For reference, the OTAs are here Full OTA Images for Nexus and Pixel Devices, although I, too, prefer the full factory image, but the OTA as suggested by @Alekos above would be worth a try.
Click to expand...
Click to collapse
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.
banshee28 said:
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.
Click to expand...
Click to collapse
Safe Mode is definitely a challenge to get into until you get used to it. So you followed these directions for it exactly?
Press your phone's power button.
When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
You'll see "Safe mode" at the bottom of your screen.
As far as I know, the animation is after it's possible to get into fastboot mode, but maybe something else is going on here.
Good luck!
roirraW edor ehT said:
Safe Mode is definitely a challenge to get into until you get used to it. So you followed these directions for it exactly?
Press your phone's power button.
When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
You'll see "Safe mode" at the bottom of your screen.
As far as I know, the animation is after it's possible to get into fastboot mode, but maybe something else is going on here.
Good luck!
Click to expand...
Click to collapse
Yep, tried it many times, same way, it originally just rebooted and most recently reboots into fastboot each time.
I just successfully flashed the OTA image via sideload. Everything seemed to work and flash properly. Someone mentioned full factory image could require more space, so was hoping OTA was the answer....
Unfortunately it gets to animation, then eventually reboots.
Never had this many issues with a phone before, what could cause this while each image flashes "successfully"?
banshee28 said:
Yep, tried it many times, same way, it originally just rebooted and most recently reboots into fastboot each time.
I just successfully flashed the OTA image via sideload. Everything seemed to work and flash properly. Someone mentioned full factory image could require more space, so was hoping OTA was the answer....
Unfortunately it gets to animation, then eventually reboots.
Never had this many issues with a phone before, what could cause this while each image flashes "successfully"?
Click to expand...
Click to collapse
I wish I knew what else to suggest. About the only option left seems to be to use the Android Flash Tool including a full wipe. I would allow it to force flash all partitions and just untick the option to re-lock the bootloader so it stays unlocked.
banshee28 said:
Yea I tried to enter safemode many times, unfortunately it never works. Each time I try now, hit the vol down when animation starts, it takes me to fastboot!
I will try the OTA next, maybe these will work!! Thanks.
Click to expand...
Click to collapse
When your phone is rebooting/bootlooping, start holding the Volume down button when the screen is blank, before any logos start to appear. That should put you in safe mode.
Lughnasadh said:
When your phone is rebooting/bootlooping, start holding the Volume down button when the screen is blank, before any logos start to appear. That should put you in safe mode.
Click to expand...
Click to collapse
Appreciate all the help guys, but nothing is working. This did get me into fastboot quicker, skipping the animation but that's about it.
I tried flashing A side only, B side only, both sides, and both factory and OTA images, same. I can get to Animation each time, but eventually reboots. Amazing how filling up space from camera could have caused this!?
Will of coruse have a backup next time, but will also look for a phone with SD card for data so this would most likely never be an issue.
I think as edor has stated not sure there is much left to try.
banshee28 said:
Appreciate all the help guys, but nothing is working. This did get me into fastboot quicker, skipping the animation but that's about it.
I tried flashing A side only, B side only, both sides, and both factory and OTA images, same. I can get to Animation each time, but eventually reboots. Amazing how filling up space from camera could have caused this!?
Will of coruse have a backup next time, but will also look for a phone with SD card for data so this would most likely never be an issue.
I think as edor has stated not sure there is much left to try.
Click to expand...
Click to collapse
If you're bootloader is unlocked, just downloaded the full factory image (non ota), remove the " -w " command (which wipes data) in the flash-all.bat file and flash away. This will keep your data intact.
The flash tool should do the same thing but doing it manually, you can keep an eye on the progress in the command terminal window to make sure there are no errors.
The data and system partitions are different. Filling up your data partition won't cause corruption like this. They are completely separated partition tables.
Also you tried the flash tool and unchecked wipe and re-lock options?
I used the PixelFlahser app as well as the online official Android Flash Tool, with all those options unchecked, yes.
Both flashed with no errors although the phone never booted. I will try using ADB directly now and see if that helps!
So i used adb cli, and it did exactly the same. I am getting some errors though saying
Code:
"archive does not contain" and lists several items such as boot.sig, vendor_boot.sig, boot_other.img, odm_dlkm.img, product.sig, system.sig, etc....
Are these important??
I have flashed just using the zip files before with no special unzipping and they have always worked fine.
banshee28 said:
So i used adb cli, and it did exactly the same. I am getting some errors though saying
Code:
"archive does not contain" and lists several items such as boot.sig, vendor_boot.sig, boot_other.img, odm_dlkm.img, product.sig, system.sig, etc....
Are these important??
Click to expand...
Click to collapse
That is normal. That happens with every month's update.
Would installing a CUSTOM ROM or 13 Beta make any difference???
banshee28 said:
Would installing a CUSTOM ROM or 13 Beta make any difference???
Click to expand...
Click to collapse
No. Don't go down that road. If you can't get Stable working, then there's something deeper wrong. So you've tried the Android Flash Tool with all default options checked (to wipe, flash all partitions) except not to lock the bootloader? i.e. letting it wipe all your data?