A Moto G4 Play xt1609 Verizon phone. Locked bootloader.
What I can do:
Boot into bootloader (From now on will be known as BL)
This is actually the default boot. It doesn't loop (anymore). Instead, it goes straight to this. The same goes for recovery. Attempting a Vol up or 'recovery mode' from BL. Turning the phone off will have itself turn right back on.
What I've done:
Taken it off the side of the road caked in mud
Bag of rice
Taken it apart and gotten dirt out
Sodded a connector for the battery to make contact with
I am physically attached to this phone by now
Got it into a boot loop
Got into BL
Flashed STOCK rom files (nothing else as BL is locked by Verizon)
Before the stock flash, it would default into a bootloop. Same for recovery. Now it defaults into BL, so I know I've made progress. I can't tell you what the previous owners did to get it here. I can only tell you what I'm working with.
Again, both normal and recovery boots into BootLoader. Phone auto reboots into Loader.
PLEASE tell me theres a thing to do next. I want this thing to live again!
Does fastboot recognize the device?
Related
So i don't know exactly what has happened to get here. I have a new Verizon Galaxy S5 that I Towel Rooted and installed Safestrap. Things were going fine and I made a nandroid backup of my Stock slot. I decided to try Alliance rom in slot 1 which all went fine and i booted into Alliance. I was customizing my phone with colors and clock position etc. Some of the icons weren't there anymore so I decided to reboot to get everything loaded back in. Well when i hit reboot the screen went black and nothing came back on. Now when I turn it on I get the Galaxy S5 splash screen and blue words at the top saying "RECOVERY BOOTING...." then it shows the Android with it's chest door open and the globe spinning, then it goes to the Android laying down with a red triangle over its chest door, and then reboots. It just loops like this. Does this mean my bootloader is corrupt? Or can I Odin flash the stock firmware and PIT?
If your bootloader was corrupt, you'd either end up on the secondary bootloader page or have a nonresponsive, brick for a phone.
So corrupt bootloader was just your guess? Because I don't see any evidence for that yet. You've ended up on the Recovery mode page or at least that is what your description sounds like (a screenshot or photo would have been good). More than likely something is just messed up in your Safestrap or custom recovery configuration.
The most obvious options would be to either check and/or reinstall Safestrap /your custom recovery. Or if you prefer, revert to full stock, then proceed from there.
The last part that you wrote is unclear.. but you imply that you can't do a normal boot at this point? Can you boot to download mode then? Pull your phone battery for ten seconds.. then press and hold the volume down key, then the home key also and then the power key. You should boot to the black download screen that shows your Knox status. If this works, then you can flash a full stock firmware from there with Odin to stabilize your system.
.
Thanks fffft for your response.
As it turns out you are correct in that the bootloader is not corrupt because I can get to download mode. I tried flashing the stock firmware back on through Odin, but that didn't work, it still just looped. What finally did work is this thread http://forum.xda-developers.com/showthread.php?t=2784880 Thanks to Misterxtc. It must have needed the PIT as well.
So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!
After installing Lineage for att (h910) and flashing gapps, which didnt work, I'm stuck and getting a bootloop into twrp. So, twrp is easily accessible. The actual operating system is failing to load.
Considering going tinto the bootloader and running step3 fastboot flash boot boot2.img from the dirtysanta root files.
My thinking is this might give me another shot at a boot image that works.
Any ideas to help? I have a Skype interview tomorrow afternoon and I need this fixed asap.
cwis said:
After installing Lineage for att (h910) and flashing gapps, which didnt work, I'm stuck and getting a bootloop into twrp. So, twrp is easily accessible. The actual operating system is failing to load.
Considering going tinto the bootloader and running step3 fastboot flash boot boot2.img from the dirtysanta root files.
My thinking is this might give me another shot at a boot image that works.
Any ideas to help? I have a Skype interview tomorrow afternoon and I need this fixed asap.
Click to expand...
Click to collapse
If is TWRP loop then .... there are countless threads here with the same question and an answer for it. First, flash a rom (any rom compatible with your variant) then completely power off the device. Then go into recovery mode by doing the appropiated gesture (which means leave pressed volume down an power button until the lg logo shows, right whent he lg logo shows , quickly remove your finger from the power button and press and hold it once again (do not remove your finger from the volume down at any moment) Then you will see the white screen where you have to press yes in both. and then you will be out of the loop. ) If you didnt understand my guide, follow this: http://www.recovery-mode.com/android/lg-v20.html . :good: This should take you out of the TWRP loop.
Thanks for the reply, but heres the thing: the LG logo doesnt show. It goes right into the izarre red triangles thing. Then goes to the white factory reset choices. I tap yes twice and the it gives me the LG logo. Several times I've held the button combo down after the logo appears but it ignores it and goes right to twrp.
cwis said:
Thanks for the reply, but heres the thing: the LG logo doesnt show. It goes right into the izarre red triangles thing. Then goes to the white factory reset choices. I tap yes twice and the it gives me the LG logo. Several times I've held the button combo down after the logo appears but it ignores it and goes right to twrp.
Click to expand...
Click to collapse
But wait.... are you explicitly turning off the device? Like off off? (remove the battery if you must). ? if not then you will be booted into twrp. Now, if that doesnt work... hmm kdz would be the ideal , if and only if you had a kdz file. Now, i see that there is a kdz file but it is for the h910pr and not h910. ... Sorry. Hope someone else can help :good:
h910pr kdz
I flashed the h910pr kdz to recover from a severe brick. worked a charm. it has a claro boot logo and i occasionally receive a notification in Spanish but it saved my butt. i have seen a report of someone doing it and their cellular service not working, but i did not have this issue. if the h910pr rom could be rooted id say its a safe kdz to fix bricked phones with. once its on the h910 it could be rooted and used to reinstall twrp and then reinstall the proper firmware.
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Did you hold the power button down until your phone completely powered off? I'm assuming you did. What you described isn't supposed to happen on a dual partition phone. If an update goes bad the phone is supposed to recover by booting from the other partition. If powering the phone down completely and then turning it back on doesn't allow you to boot I would honestly go straight to Essential Support since you didn't mod your phone or unlock the bootloader. I dealt with support via email and if nothing else they are definitely very responsive. They answer emails so promptly it was almost like being in a chat.
devon4786 said:
So, pretty much what the title says...I got the prompt to update to Oreo. Clicked install and left it. It does whatever it needs to do and after 2 hours of leaving it there it was just stuck on the boot screen. Tried to boot into recovery and no luck, it just remains on boot screen. I can access fastboot mode though.
Because the boot loader is locked, I can't install a custom recovery or anything. I tried everything I could in my own power before resorting to here. Any suggestions?
Click to expand...
Click to collapse
Hello
Tell us the status of your phone Did you solve the problem? Tell us the way I'm stuck in the same problem
I replaced my GNEX10 battery last january. Aside from the battery calibration being off... (which eventually corrected itself!) it's been working fine. As of late it had rebooted itself while I was using it a few times. A few days ago, it had enough battery such that I left it on overnight. I picked it up the next morning and the notification lamp was flashing so I knew it was still on. I tried to wake it up without success. Usually a quick tap on the power button should do it. Nothing. So I rebooted... and on the google logo it stuck. I knew that a factory reset was probably in order since I didn't do it when I replaced the batter... I got it into the recovery screen... but I could not get the menu. I likely didn't press the right volume rocker. Then I tried again... booted to the bootloader, and selected recovery. This time, and since, only the google logo comes up. No andy on his back with "no command". It just tries to boot into something. I can't do a factory reset this way.
I tried the Nexus Root Toolkit. I can only get it to recognize the device if it's in the bootloader... when I try to use it to boot to recovery, same thing and the NRT says waiting for device... and gets no further. I tried to use it to flash (stock?) recovery but the N10 just sits there on the twrp logo screen and nothing more after temporarily booting into twrp. Just keeps saying "waiting for device"
Anyone have any suggestions! Getting seriously bummed!
So one more data point... I manually rebooted into the bootloader after trying to flash the stock recovery using the NRT. Then it appeared to flash the recovery image.... here is the bit of the log where it ended up:
Checking Fastboot Connectivity
fastboot devices
R32CB04GHGT fastboot
+ Fastboot Device Connected
Flashing Stock Recovery to RECOVERY partition...
fastboot flash recovery "C:\usr\NRT\data\Recovery_Stock\recovery_stock_mantaray_5.1.1_LMY49J.img"
Temporarily Booting TWRP...
fastboot boot "C:\usr\NRT\data\Recovery_Custom\TWRP\twrp-3.0.2-0-manta.img"
Flashing 'undo-perm-recovery-signed.zip'...
Waiting for your device...
That's where it ended up... not getting any further. Once again, attempting to boot into recovery gets it stuck on the Google logo.
How screwed am I? Is there a thread somewhere in the forum anyone can point me at?
Well, in spite of the crickets... I understand. I've managed to resurrect my Nexus 10. Alas there are no good contemporary replacements. The last so-called nexus table google put out there was too damn expensive in the first place and they seem to have abandoned the tablet market to others.
So the key question here: So long as I can get this tablet into the bootloader is it generally possible to reflash a stock image? I'd like to know of any types of caveats etc. The mystery I have still though is: How or why did my N10 get into this state (of of only being able to get to the Google screen) in the first place? I didn't have any questionable apps installed etc. I was totally on stock. One thing that did happen a week or two prior to my tablet going belly up... was somehow the thing lost my google account info and gmail had none of my accounts in place... it was very odd.
I did have to wipe the system because evidently you can't flash anything onto a locked bootloader (the Nexus Root Toolkit by wugfresh is up to date so far as the N10 is concerned at least). I know I could have resorted to using fastboot.exe and the adb directly but this was a touch easier. Alas the backup options for it say you need an unlocked bootloader which seems to be a chicken/egg issue if you've always been on stock.... so it goes.