Database Info

Damn！Reboot again and again after flash the RADIO!

I flashed the new RADIO and SPL,but forgot to flash a new recovery in HBOOT model. The flash was totally succeed (because after fashing,I tap "fastboot reboot-bootloader" command in HBOOT and it could reboot automatically into hboot model and I can see the new RADIO and SPL had been fashed.
But here comes the problem, I try to reboot my phone into recovery model to flash the new ROM, but no matter I press HOME+POWER or BACK+POWER this time, it reboots again and again at first boot screen, and donnot have any response with the key I tapped!
God! is that bricked? No please don't tell me it's true!

so to clarify, you didn't flash a recovery image and now you don't know why you can't boot to recovery?
boot to fastboot, flash the recovery only, reboot to recovery, flash the rom of your choice and enjoy

Of course, but I cannot boot into fastboot or recovery model now.

nabor said:
Of course, but I cannot boot into fastboot or recovery model now.
Click to expand...
Click to collapse
*facepalm*
if you can't get into fastboot and you can't get into recovery you just bricked your phone.

while it's bootlooping, can you adb devices and tell us what you get?
i'm surprised that it's bricked because you forgot to flash a recovery, would have thought you could still access fastboot...

I was surprised too.
I don't know why,but I can boot into fastboot model now, but my recovery and rom are still broken.
So I tried to type "fastboot boot recovery.img" on my computer, so that I can enter recovery temporary, but here comes another trouble, it can't mount sdcard now! Display "Can't mount /dev/block/mmcblk0p1(or /dev/block/mmcblk0)(No such file or directroy) E:Can't mount SDCARD
!"
So can I use adb shell to install a ROM???

calm down bro....
you didn't brick your phone...
i've same problem after I flashed the new radio SPL HBOOT and recovery...
I've used Hero Recovery...
after u flashed your handset with new radio SPL HBOOT and Recovery, the ROM file DELETED....
so, u just download new rom (that have SAME RADIO HBOOT and Recovery with your handset)
after finished the download, put the file into ROOT SDCard... and then flash it from your RECOVERY....
I've used HERO RECOVERY....
my handset is HTC MAGIC 32A
just do that, if the problem same with me....
BRAVO
nabor said:
I flashed the new RADIO and SPL,but forgot to flash a new recovery in HBOOT model. The flash was totally succeed (because after fashing,I tap "fastboot reboot-bootloader" command in HBOOT and it could reboot automatically into hboot model and I can see the new RADIO and SPL had been fashed.
But here comes the problem, I try to reboot my phone into recovery model to flash the new ROM, but no matter I press HOME+POWER or BACK+POWER this time, it reboots again and again at first boot screen, and donnot have any response with the key I tapped!
God! is that bricked? No please don't tell me it's true!
Click to expand...
Click to collapse

the command is
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
read from this thread
http://forum.xda-developers.com/showthread.php?t=605239
download all files you need....
better use last recovery.... (1.5.2 isn't last recovery)

I don't recall the OP mentioning what handset they have. If its the MyTouch 3G Limited Edition or 1.2 (has headphone jack on top) a new user to rooting may confuse that with a Magic 32A in which case your instructions without clarifying would surely brick his phone. (Though he's on Fido, so not likely to be a MyTouch, but he didn't even mention of it was a Magic, Hero, G1, or if it was a DVT board instead of a PVT)
LoGaY said:
the command is
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
read from this thread
http://forum.xda-developers.com/showthread.php?t=605239
download all files you need....
better use last recovery.... (1.5.2 isn't last recovery)
Click to expand...
Click to collapse

LoGaY said:
the command is
fastboot flash radio Radio_HTC_PVT_32A_6.35.10.18.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery-RA-hero-v1.5.2.img
fastboot erase system -w
fastboot reboot-bootloader
read from this thread
http://forum.xda-developers.com/showthread.php?t=605239
download all files you need....
better use last recovery.... (1.5.2 isn't last recovery)
Click to expand...
Click to collapse
You shouldn't offer instructions like this. You have no idea what phone he's using. You offer such a high risk of bricking the phone since most members here fail to read instructions before running a bunch of commands.
He's fido like the above guy said which could mean he's using a rogers magic, but it's also unlikely. Fido doesn't have Magic, so he definitely got it off someone. And since it's rootable (it is unlikely that he could get a hands on a rooted magic here since their lame update) it has a high chance that its from tmo or something which = 32B board.

my phone is htc magic with 32A and it's ENG S-ON so I can't flash a recovery through fastboot, so I have to use "fastboot boot recovery.img" to use a recovery temporary just I said above. I do know that I can put a rom into a sdcard to flash it, but it can't mount sdcard now

Try waiting 30-60 seconds before accessing the SD card. Some recovery images take a while to mount the card.

[Q] Xoom stuck on starting RSD mode 2?

Flashed Build HWI69 for US Retail on a Canadian wifi MZ604 xoom..tired of
waiting for 3.1 update.
adb reboot bootloader
fastboot oem unlock
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
fastboot reboot
It is stuck on Starting RSD mode 2.
I can not get it to fastboot protocol...device does not turn off.
Any solutions?

Fastboot OEM lock is where you went wrong. Anyway see this thread.

OK I did this procedure yesterday but did not relock (I know it says to on the moto site but the guide I read said not to).
Anyway, pressing power and vol up will force a reboot. Unsure what will happen when it boots back up though...!

You should be fine. Only trying to relock will cause this error.

To get back to fastboot after a bad lock do this.
Power button and volume up, this will reboot the device.
As soon as the screen turns back on holds down power and volume down. In about 60 seconds your device should go to fastboot. Do not let go until it gets there.
Sent From My Evo

Thanks for the reply . It now says Failed to boot LNX 0X0004
Starting Fastboot protocol support
However it will not connect to xoom.
<wait for device> when issue fastboot command.
What the hell is going on?

you need to read this thread
http://forum.xda-developers.com/showthread.php?t=1108518

The exact thread I linked to...(-__-)'

I followed instruction from motorla dev support site.
"h**p://developer.motorola.com/products/software/?pubid=987654"
It uses command "fastboot oem lock"! So why did locking brick the device?
here it is:
Device Software Images
Select the appropriate device software image to download and re-lock your device. If you need to find your build number on your Motorola device go to Settings and About Phone or About Tablet.
The commands to flash and re-lock your device are as follows:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata

The Moto instructions are for locking the device back to it's own image. You are not using your device's own image. Every guide I've seen on here tells you not to relock, regardless of what Moto say. Believe the devs.

Thanxs
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.

tfx1 said:
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
Click to expand...
Click to collapse
Try making or obtaining a factory cable which its different from an OTG cable. Start with the two links below. This might save the day.
http://forum.xda-developers.com/showthread.php?t=1077414
http://forum.xda-developers.com/showthread.php?t=1108518

[Q] Hard keys in cm9 or recovery do not work. please help!

The power and volume keys refuse to work in recovery or rom. They work in bootloader but as soon as I get into recovery, nothing. This is after flashing cm9.1. (I did manually flash the boot.img prior to installing the zip as instructed with s-on devices) Also, trackpad and the front four buttons dont work either. Any way I can access my sd through adb to flash a backup image? I dont have a card reader.. or any other solutions? Much appreciated, as I have no back up phone or the means to replace it. I'm unlocked with s-on btw.

fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Sent from my SGH-T839 using Tapatalk 2

Can't get past Google Screen

I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!

bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
You flashed the factory images?

bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
Do a data factory reset and wipe the cache both in recovery and reboot bro.

gee2012 said:
Do a data factory reset and wipe the cache both in recovery and reboot bro.
Click to expand...
Click to collapse
Thinking the same thing. But.. I can admit getting in a hurry and flashing the wrong image! :laugh:

I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?

bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
Click to expand...
Click to collapse
Long press the power button force it to reboot. As soon as the screen goes black hold down the volume down button. That will boot you into the bootloader, from there you can get to recovery. Factory reset, wipe cache.
You flashed stock recovery?
If you have stock recovery go to the bootloader like I said earlier. Choose recovery. Then you will see android laying down. Press volume up and power button at the same time. Do a factory reset.

bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
Click to expand...
Click to collapse
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?

gee2012 said:
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
Click to expand...
Click to collapse
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?

bobyum said:
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
Click to expand...
Click to collapse
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt

maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk

gee2012 said:
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
Click to expand...
Click to collapse
Unfortunately, it didnt help Still stuck at writing bootloader...

beaver2233 said:
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup, that might work better maybe

hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?

bobyum said:
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
Click to expand...
Click to collapse
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot

Thanks all for the help! Will try it tomorrow. Hopefully it works

wantabe said:
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Click to expand...
Click to collapse
I'd go one better and look to do a COMPLETE reflash - userdata and all! I'd also rename bootloader-hammerhead-hhz11k.img to bootloader.img and radio-hammerhead-m8974a-1.0.25.0.23.img to radio.img as it means there's less to get wrong! SO, to recap:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot format cache
I'd then boot into the stock recovery and perform a factory reset to make sure everything is in order and then reboot. I've done this exact method a number of times on my Nexus 5 and it works every time

EddyOS said:
I'd go one better and rename bootloader-hammerhead-hhz11k.img and radio-hammerhead-m8974a-1.0.25.0.23.img to just bootloader.img and radio.img to make it easier - less to type out and get wrong!
Click to expand...
Click to collapse
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!

wantabe said:
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
Click to expand...
Click to collapse
As I hardly have any data to backup bar some custom ring tones I always reflash the userdata partition to be thorough. As for the reboots, I've just done it from habit, again just to be thorough. If it still doesn't work after that then it's goosed!

Try using the backup bootloader. Press and hold both volume buttons with the power button. That will take you into the backup bootloader.

Thanks to everyone for helping but I could not even get past writing the bootloader to the phone. I honestly think the flash storage and failed so will be RMAing. Hopefully they will accept it...

Accidently typed fastboot boot boot.img

what do i do the phone doesn't boot at all

This command tells the bootloader to immediately boot the image you have sent. It's quite useful if you want to run something without actually flashing it to the boot partition - such as TWRP on devices that don't have a recovery partition, or testing patched boot images.
What do you mean "the phone doesn't boot at all"? What device? What were you trying to do?

Khalyl22 said:
what do i do the phone doesn't boot at all
Click to expand...
Click to collapse
That's okay, you only boot(temporary) into boot.img. Try to press and hold your power button to force reboot

V0latyle said:
This command tells the bootloader to immediately boot the image you have sent. It's quite useful if you want to run something without actually flashing it to the boot partition - such as TWRP on devices that don't have a recovery partition, or testing patched boot images.
What do you mean "the phone doesn't boot at all"? What device? What were you trying to do?
Click to expand...
Click to collapse
Oppo a5s i was trying to flash gsi rom but i started
fastboot erase boot
fastboot erase system
fastboot flash system system.img
fastboot boot boot.img by mistake (i was going to fastboot flash boot boot.img)
and now it keeps vibrating

khusika said:
That's okay, you only boot(temporary) into boot.img. Try to press and hold your power button to force reboot
Click to expand...
Click to collapse
didn't work :'(

Khalyl22 said:
Oppo a5s i was trying to flash gsi rom but i started
fastboot erase boot
fastboot erase system
fastboot flash system system.img
fastboot boot boot.img by mistake (i was going to fastboot flash boot boot.img)
and now it keeps vibrating
Click to expand...
Click to collapse
Have you tried to flash all image again?

fastboot erase command is dangerous and (in most cases) useless. do not follow any tutorial that still suggest this.

khusika said:
Have you tried to flash all image again?
Click to expand...
Click to collapse
i actually found out what happened
i erased boot.img and forgot to flash it again because i wanted to patch the file