Related
I'm trying to install CM11 to my Ouya. ADB recognizes it as a device but when I "adb reboot boot loader" the device reboots, screen goes black for several minutes and then it just boots right to Ouya OS.
I had the device rooted a while back and I think CWM was installed. I did a factory reset though a few months ago. Could I have bricked this thing?
I have also tried a usb keyboard and hitting alt+print+i but get the same result.
christanya99 said:
I'm trying to install CM11 to my Ouya. ADB recognizes it as a device but when I "adb reboot boot loader" the device reboots, screen goes black for several minutes and then it just boots right to Ouya OS.
I had the device rooted a while back and I think CWM was installed. I did a factory reset though a few months ago. Could I have bricked this thing?
I have also tried a usb keyboard and hitting alt+print+i but get the same result.
Click to expand...
Click to collapse
I had similar issues a rooted ouya with CWM Recovery on but I could not boot into recovery, I got the black screen and if I hit the home key I just got the standard android recovery not CWM. I read that this could be due to an OUYA update. As hard as I tried I could not reload CWM. I finally fixed my issue by reloading Superuser. For some reason I was then able to run one click recovery and it reloaded CWM Recovery for me. Since then I have upgraded recovery and loaded CM11. Only issue I have is now I don't get the boot menu just straight to CM11.
I am just a user not a programmer but I believe the issue may be that your recovery was overwritten by the ouya update and then you are unable to load CWM because permission issues.
Try hitting the home key when you have the blank screen, if you get Andriod Recovery then you seem to be where I was.
Good Luck.
newbyp said:
I had similar issues a rooted ouya with CWM Recovery on but I could not boot into recovery, I got the black screen and if I hit the home key I just got the standard android recovery not CWM. I read that this could be due to an OUYA update. As hard as I tried I could not reload CWM. I finally fixed my issue by reloading Superuser. For some reason I was then able to run one click recovery and it reloaded CWM Recovery for me. Since then I have upgraded recovery and loaded CM11. Only issue I have is now I don't get the boot menu just straight to CM11.
I am just a user not a programmer but I believe the issue may be that your recovery was overwritten by the ouya update and then you are unable to load CWM because permission issues.
Try hitting the home key when you have the blank screen, if you get Andriod Recovery then you seem to be where I was.
Good Luck.
Click to expand...
Click to collapse
Thanks for the advice.
I managed to make it into stock recovery but can't seem to get to CWM still. I reloaded Superusuer and the tried Oneclickrecovery. ADB shows success and say's I should be in CWM but I just get a blank screen.
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
fxbill said:
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Have you tried connecting a usb keyboard and entering the keyboard command: Alt + i + PrntScreen
You have to enter all three keys at once and repeat as many times as it takes for the screen to maybe boot in clockworkod.
TROJAN4EVR said:
Have you tried connecting a usb keyboard and entering the keyboard command: Alt + i + PrntScreen
You have to enter all three keys at once and repeat as many times as it takes for the screen to maybe boot in clockworkod.
Click to expand...
Click to collapse
Hi,
Yes.... I stumbled across that today on searching. I tried with a little iPazzport usb keyboard/mouse that I use to program with, but I'm going to try another keyboard as well just in case it is the keyboard. I tried at least 20 times over and over again with nothing at all happening. I appreciate the suggestion though and will try again with the different keyboard tomorrow. I'm a little burned out on it tonight! I'm afraid what I might have done is to change from the CWM bootloader to that one when I did it. Hopefully not, but there's no way to tell since all I can get now is the loop when I boot the unit up. I tried not only when I got the failed update message, but at all different times during the boot operation just to see if i got any response at all, but nothing so far seems to break into that cycle.
Thank you!
fxbill,
Sometimes you just have to walk away and then get back to it later. I use a low cost dell usb keyboard and what I found out is that you have to do press all three keys at once in unison and at a steady rate until you get a response. Just try to press all three at once and I guarantee you'll get it done. Try it when you're ready to get back to it. Have a good night!!!
fxbill said:
I mistakingly...( at 3AM!) installed the Rbox boot menu. It was not intentional....just late at night and I hit the wrong button! In any case I am now stuck in a loop the boots to the Rbox boot menu with 2 options....load kernal or boot to recovery. Load kernal just reboots to the same menu screen and boot to recovery gives me a failed update message after which in several minutes the unit boots back to the original Rbox boot menu. This particular unit had been previously rooted, updates blocked and loaded. The bootloader was unlocked with the FTV utility and that's when I hit the wrong button and loaded the Rbox boot menu.
I have tried connecting to the internet directly....( my router blocks updates) with no success. Is there anyway to get out of this even if it means updating and losing root or do I now have an extra boat anchor on my hands?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
If you get failed update when selecting recovery that means you didn't install CWM. If you did a full unlock, you can use fastboot to boot into CWM. If you didn't do a full unlock, then you're pretty much screwed.
rbox said:
If you get failed update when selecting recovery that means you didn't install CWM. If you did a full unlock, you can use fastboot to boot into CWM. If you didn't do a full unlock, then you're pretty much screwed.
Click to expand...
Click to collapse
Well.... CWM was in.... I got the install from zip screen, but at that late hour and as tired as I was it's possible that I somehow removed it when installing your boot program. If so then I can live with it and yet I will try again tomorrow to see if I can fast boot or use a different keyboard for trying to alt/pnt scrn/i and see if that works.
I did do another unit tonight and installed your boot program before installing CWM,,,,again in error, but this time it booted to the same screen and then rebooted back into the preloaded unit! I then installed CWM and everything else went smoothly. I'm assuming your program is still in there, but is there a way to verify that it's still there? I updated to the newer 4.0 firmware with no issues and Netflix is again working and the firmware shows 4.0 installed. Is there really any reason to update any father than that? Is there anything new in the latest rooted firmware that justifies updating any more than I already have? If not I'll leave it as is...everything works extremely well at present.
Thanks so much for the advice and help!
@fxbill, so were you able finally to get this fixed? i'm in same situation when my device constantly reboots after counting down to 0 in rboxes menu . tomorrow i will by trying to find an USB keyboard and see whether im in luck of getting to recovery. hopefuly that works. i'll keep you posted.
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!
My Galaxy Tab S prompted me for an update last night. I was at 5.0.2, so I'm not certain what I was getting upgraded to but it was about a 190MB download. The download went fine and the install seemed to go OK. However, at the end of the update install, the tablet rebooted, and that's when everything screwed up. It went through a normal reboot sequence but, when it started to come up like it was going to take me to the home screen, I got hundreds of error windows popping up one on top of the other. They all said "Unfortunately, this has stopped." or that has stopped, basically running through pretty much every default pre-installed and me-installed app on my tablet. And they kept appearing faster than I could press OK. I have just a black screen with these white error boxes. I'm never able to get to the home screen at all. I've rebooted. I've completely powered down and waited for several minutes before booting. Nothing seems to help. I keep getting a normal boot sequence, right up until the point that it would relinquish control to me, and then these same hundreds of error boxes and no home screen or any sort of control over my tablet. I have no idea what to do.
Has anyone ever heard of any behavior like this or know what I should do?
Thanks.
try to enter the recovery mode by pressing home+vol up+power button. and reset your device
or you can download your full firmware and flash it using odin.
edan1979 said:
try to enter the recovery mode by pressing home+vol up+power button. and reset your device
or you can download your full firmware and flash it using odin.
Click to expand...
Click to collapse
Just got up for the day and saw your response. I'm on nights right now, sorry.
Thank you very much for your reply. I was able to get into recovery mode. Just to clarify, when you say "reset", are you saying a reboot (the first option) or wipe data/factory reset (the fourth option)?
EDIT:
You can disregard. I went ahead and rebooted, and that did what I figured; pretty much nothing. Basically just rebooted, got out of recovery mode, and booted right back into the state that it was in before, which was screwed up. Factory resetting now.
Thanks.
OK, system wiped OK and it's restoring from a Google Backup right now. So, I guess we'll see how it goes the next time I try to update. I have the Wi-Fi version, just standard SM-T800. Isn't Marshmallow available as an update now? I'll see how things go I guess and see what updates are available.
Gotta remember recovery mode, for when all seems darkest!
Thanks again for your help.
OK, so, my tablet is back up and running, but that update won't install. It isn't causing the same problems as before, but it still won't install. I'm at 5.02 and the update is 190MB. It downloads and it starts to install after I accept the EULA. The screen goes black, the little Samsung logo pops up, then the little Android guy comes up and it says installing update 0%, waits for about two seconds, then the little Android guys is on his side with his cover plate up and it says error, then reboots. I can still use my tablet, I just can't install this update, whatever it is. I'm pretty sure it isn't the Marshmallow update, because I'd heard that was up over 1GB. Still, if I can't get this update, whatever it is, I doubt I'll ever be able to get the Marshmallow update.
Now I'm happy I have my tablet back, but frustrated because it won't update.
definitely it already has MM update. you could go to Odin way. Update it manually. can download the firmware here.
http://updato.com/firmware-archive-select-model?q=T800&order=date&dir=desc&exact=1
edan1979 said:
definitely it already has MM update. you could go to Odin way. Update it manually. can download the firmware here.
http://updato.com/firmware-archive-select-model?q=T800&order=date&dir=desc&exact=1
Click to expand...
Click to collapse
Yeah, I was thinking the same thing. It doesn't seem too hard. I'm reading up on it now. I'll download everything I need and possibly try it this weekend. I intentionally haven't reinstalled a lot on my tablet yet, thinking I was going to go that route.
Hopefully, that will take care of my issues.
Thanks again for the advice.
Well, updating with Odin went off without a hitch. After it had updated, I performed a factory reset, just to be safe, and reinstalled everything. It's running great now and I sitting pretty with 6.0.1.
Thanks again for your help.
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
I would fastboot latest factory image.
Just hold vol- when a reboot comes it will go into bootloader.
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Just started with me today too.
I cannot get into recovery or boot loader
rebooting using the hard button just brings up this Dump to EXT4 and then into the ROM that is havnig a ish ton of force closes.
My plan is to back up some stuff I need to copy off the phone and then start factory reset from within settings.
EDIT:
I was rooted running stock
All i did was run a backup in TWRP
issues started after reooting.
Once i factory reset and re Root i will see if I can restore backup, maybe
sb1893 said:
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
Click to expand...
Click to collapse
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April. How do I revert the bootloader?
Also, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful so far. Thanks!
Click to expand...
Click to collapse
They flashing all the parts of the image manually. Something like this happened to a buddy of mine and using the flash all wouldn't fix. He couldn't get the device to boot until he did all the images manually.
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
Click to expand...
Click to collapse
Glad you got it working. I checked and I did link the thread I intended to. Starting at post #57 onward from that thread has the information on how to update to the May update and leverage Chainfire's VerifiedBootSigner.zip.
Thx,
S
Pixel bootloop
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
rosendomurilo said:
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
Click to expand...
Click to collapse
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Phalanx7621 said:
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Click to expand...
Click to collapse
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
rosendomurilo said:
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
Click to expand...
Click to collapse
Can you get to recovery ?
Phalanx7621 said:
Can you get to recovery ?
Click to expand...
Click to collapse
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
rosendomurilo said:
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
Click to expand...
Click to collapse
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Phalanx7621 said:
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Click to expand...
Click to collapse
Perfect! Just as I expected... Probably i will do an youtube guide if it works... Thanks bro!