Database Users

unbricking issue?

I tried to finally root my phone and install CM5.0.8. The rooting went fine, but getting CM to work, well it didn't. After repeated attempts, I decided to follow the instructions to get my phone back to stock so that I had a functional phone.
The result is that when powering on, it goes to the bootloader in less than a second. I have followed the instructions for downgrading/unbricking repeatedly, and it keeps booting to the bootloader. I have even tried to manually update to r33 and it seems to go fine, reboots a couple of times installing a new radio image I assume, but goes right back to the bootloader afterwards. The times I've tried the r33 update, when its all said and done, the bootloader reports the original radio version even though a new one is supposedly installed. Its like the installs goes fine, but nothing sticks.
I can still get to the bootloader(obviously) and recovery, so I know there's hope for my phone. Does anyone know whats going on and how to fix it?
EDIT: It seems that the radio image is changing, but its still booting straight to the bootloader. In case its not clear, DREAIMG.nbh flashing says that its successful every time and its still doing this.

Anyone?
I've now tried DREAIMG.nbh files from multiple places, every time they say that they're successful and yet it still boots to the bootloader. I'm almost at my wits end with this.

Your description is inaccurate.
You say that it is going to bootloader, but you are also saying that you can access recovery....
What RADIO is installed on it *right now*?
What SPL is installed on it *right now*?
What RECOVERY is installed on it *right now*?
Do you have ROOT?
HOW did you try to install CM?
At what point did it start booting straight to bootloader?
Note: boot to bootloader means one of two things;
1) The boot image it is trying to boot is somehow invalid,
2) The BACK or CAMERA button is broken or stuck (try pressing these buttons a few times to see if that fixes it).
DO NOT install 1.33.2005 SPL. It is REDUNDANT, and judging by the things you say you've done, I suspect that it will be EXTREMELY DANGEROUS for you.
This thread to install CM5 withOUT needing the deathSPL: http://forum.xda-developers.com/showthread.php?t=704560

You say that it is going to bootloader, but you are also saying that you can access recovery....
Click to expand...
Click to collapse
Correct. Just hitting power, I get the G1 logo screen for about a second and then the boot loader. If I start it while holding down home, it goes to the recovery mode. Camera + Power, bootloader checking for firmware on SD card. The other combinations you can use booting up also work as intended.
Radio - 1.22.12.29
SPL - 0.95.0000
Recovery - Stock that is installed by DREAIMG.nbh.4 options, reboot, toggle text, apply update.zip, and wipe data/factory reset
Root - not anymore
HOW did you try to install CM?
Click to expand...
Click to collapse
I followed the instructions on CM's wiki for starting from a vanilla G1, and then followed the instructions for DangerSPL and CM 5.0.8 that are linked from that page.
At what point did it start booting straight to bootloader?
Click to expand...
Click to collapse
After following the instructions to get the phone back to stock.
Note: boot to bootloader means one of two things;
1) The boot image it is trying to boot is somehow invalid,
2) The BACK or CAMERA button is broken or stuck (try pressing these buttons a few times to see if that fixes it).
Click to expand...
Click to collapse
I don't think that its #2, the buttons work since I can use them to boot into different modes, and I've pressed the buttons repeatedly trying to see if they're stuck. It seems that its #1, even though every time I try to flash the firmware, it says that its successful.

[Q] How to reboot into recovery?

I rooted my G2 about two months ago. I'm currently using MIUI, not the latest but the one before it. Somehow, my phone got turned off and when I tried to turn it back on, it was stuck in a bootloop. I have a custom recovery image so I don't know if that affects anything. I tried to reboot into recovery by pressing volume down and power, nothing happened. I then did volume up and power. It vibrated three times and the orange light started flashing. I pulled the battery and now when I try to turn it on, nothing happens. So how do I reboot into recovery and so I can restore my backup? Any help/suggestions would be greatly appreciated.

Never pull the battery during something like that. It sounds like your bricked. Someone else confirm?

I don't think it's bricked. I plugged it up and then Clockwork came up so I selected reboot now. Clockwork came up again so I tried to restore my latest backup and the screen went black. I'm going to let it charge and then give it another try.

Ok good. That's lucky because whenever you pull on a boot like that, it usually bricks. If you have the option, try to re-flash your ROM. Maybe even try stock. If you were getting a black screen, it's most likely you flashed incorrectly.

Ok, I was able to boot into recovery and now I'm restoring my backup. I don't think I had a custom recovery image with this one so hopefully I won't get stuck in a bootloop. When you say stock, do you mean before I flashed MIUI (it was the first rom I flashed)? Thank you for your suggestions and all of your help.

first install adb on you PC, it helps a lot in these kind of cases.
1. try "adb logcat", it would tell you about what's going on in your machine.
2. once you get your adb working, try "adb reboot recovery" to see if it could boot your phone in recovery.
3. if after doing everything you fail to boot either your phone or in recovery then try using PC10IMG to boot a stock rom and then re-root your phone.

I got it back working. For some reason, I'm just starting to think that it needed charging (the battery had been out for about a day or two). I do have adb installed and configured on my computer since I needed it to root. Thank you for your suggestions, I will definitely rember them if this happens again.

lol of course when you get black screen and led blnking means your battery begging for juice, you're lucky that when the phone booted back in recovery and you tried to restore a backup the phone went off before actually starting to restore, that would've bricked your phone
DO NOT FLASH ANYTHING WITHOUT AT LEAST 40% OF JUICE LEFT

[Q] Issue after flashing stock

So basically, from running PA, i decided to try stock 4.4.2, so using the nexus root toolkit, i tried to do it, however once it said it was all done and ready, my nexus 7 remained on the bootloader screen, and when i clicked start from that, it said boot failed. So in the bootloader menu i pressed restart to see if that'd do anything, but now it won't boot up at all, not even to the google screen and there is no charge screen when plugged in. It was running the 4.13 bootloader and i think i needed the 4.23 or 4.19 for 4.4.2, but i don't see how that would have caused a failure because doesn't the bootloader get flashed and therefore updated when flashing stock?
If anyone could help that'd be truly great

Can you at least get into the recovery of your device?

I can't get it to turn on at all
Happy christmas by the way :laugh:

Youve held down your power button and used other button configs? I had an issue almost like that, but I wiped everything. I was able to reflash with under fastboot. If you can at least get the boot loader up you can use the NRT to get back to stock.

i can't seem to, its completely blank, i'll give it another go for longer

Hard brick? Can't boot to recovery

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!

Nexus 10 boot stuck on google logo... bootloader ok, but recovery does same thing.

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.