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.

G1 Reverted to RC29 stuck at "Android system recovery utility"

I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?

Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)

There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).

A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.

ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.

I just had this exact experience; have you made any progress, goatlordbob?

same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?

why doesnt there seem to b any help for this matter, smh

bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?

try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html

ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.

Anyone bothered booting using home + power?

shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.

HD2 Stuck in bootloop

Hey guys,
I have my sisters HD2 here, which I equipped with Android 2 years ago.
It is stuck in a bootloop and I can only access CotullaHSPL. Longpressing the power-button doesn't bring me anywhere. Any way to fix it up again? I just have a Mac here and think it's not possible to install a new recovery without installing Magldr again?
Cheers,
elmo108

If it's stuck in a bootloop, we can assume that you still have your android bootloader working. Now if you don't see Magldr's header at the top when booting up, then you have cLK, otherwise it's MAGLDR.
If you have MAGLDR, hold the end button when you see magldr's header. (Does this also take you nowhere?)
If you have cLK, boot up the device and immediately hold the back button. This should bring up cLK's interface.
From there, check that you have cwm installed. If it is installed, then just copy the same ROM and flash it again. (Or resize partitions then flash the rom if you want to install another one)
If it's not installed, just follow one of the guides available on this forum to install the recovery.
You said you've installed Android two years ago, so I'm assuming you're familiar with all of those stuff.
Good luck.

New/Stock Oneplus Two, unable to boot into recovery

Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!

redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?

Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!

You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!

Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue

Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk

redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:

redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.

Nexus 6P - the locked bootloader and bootloop paradox

Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.

Hey!
Thanks for your fast reply and your helpful tone.
However, when I choose Recovery mode it once again stucks in bootloop resulting in me never accessing recovery mode

npjohnson said:
Super easy to fix.
Download the newest Full OTA image for angler: https://developers.google.com/android/ota
Then reboot to recovery by holding VOL-DOWN and powering on, then selecting recovery from the boot menu. Then choose "Apply Update from ADB", and use adb sideload /path/to/filenameofotaimage.zip to revive it.
Click to expand...
Click to collapse
I am not sure my first reply was sent (having an unstable connection) so trying again:
When in bootloader and pressing recovery mode it goes straight back to bootloop. Hence, I cannot access recovery mode. Feels like a catch-22.

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
maybe if you posted it in the correct forum, you would get an answer...

Moved to the correct board...

If you can't boot the phone and you can't boot to recovery and Android debugging and oem unlocking are not enabled, there isn't much (read anything) you can do. Maybe take it to a local repair shop and see if they can replace the motherboard for you.

robruu said:
Hello!
I recently got a hold of a Nexus 6P which has the bootloop error. The previous owner never rooted it or hacked it in any way.
Meaning OEM is locked
Bootloader locked
No TWRP
My question is:
Is there any way to save this phone? I searched for almost an hour and some people claimed its doable whilst others said to give up.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6p/general/confirmed-hardware-defects-nexus-6p-t3610405
Heating the phone temporarily boots the phone. (You can also check videos for saving data in bootlooped LG phones)