I just helped a buddy (this never happened before) and his mytouch is rooted. He upgraded his SPL to Haykuro's and then, through fastboot, he flashed Amon_Ra's 1.2.2 recovery image. Now, we can't get it past the mytouch screen, but can get into fastboot. Any ideas?
Try flashing another rom?
If you can get into fastboot, you can send a new image to the phone.
I don't recall the exact commands, but if you're in fastboot, you're still good.
cursordroid said:
If you can get into fastboot, you can send a new image to the phone.
I don't recall the exact commands, but if you're in fastboot, you're still good.
Click to expand...
Click to collapse
Great man...does anyone know the commands?
Fastboot the recovery image, and then from the recovery, you can flash the new rom.
xyzulu said:
Fastboot the recovery image, and then from the recovery, you can flash the new rom.
Click to expand...
Click to collapse
the recovery image is there. We cant into to recovery to apply the rom.
Get yourself the proper recovery.img for that phone. Not sure what it is, but a quick search will find it. Search for 'mytouch recovery' or 'mt3g recovery'.
Then with the recovery image in your SDK tools folder, run:
Code:
fastboot boot recovery.img
That should at least get you to a point where you can flash a new ROM and commit the proper recovery image to flash using adb commands.
I can't hold your hand through the whole thing, I don't have that phone, but I've been in your situation before.
Ok we tried it, now it says... FAILED(remote: partition does not exist!)
anyone have an idea?
Try to erase Cache
fastboot erase cache
fastboot erase recovery
then flash recovery:
fastboot flash recovery recoveryxxxxxx***.img (***I'm not sure of the version you use...)
antonram said:
fastboot erase cache
fastboot erase recovery
then flash recovery:
fastboot flash recovery recoveryxxxxxx***.img (***I'm not sure of the version you use...)
Click to expand...
Click to collapse
Yeah that's exactl what we did and it worked.
The thing is, we erased the recovvery image and reinstalled it, but now again, it won't go into recovery. I have a feeling he downloaded the wrong Amos_Ra recovery. Probably one for the 32a.
Related
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.
Dear all, I need your help ASAP.
My phone (rooted) doesn't boot now, adb does not recognizes, fastboot still ok. And I don't know what to do.
Recently I rooted my Desire S and succeeded with the stock ROM. After a coupe of days I dicided to flash Endymion, from here: http://forum.xda-developers.com/showthread.php?t=1310845
I downloaded Endymion 3.1 into SD, then used Rom Manager to flash it. But then it was not be able to reboot (stucked on splash screen).
After that I rebooted into recovery (4EXT) and formated system, data, cache, boot and retried to install Endymion 3.1.
But then it became worse, now I can't use adb (always says: device not found), normal boots always stucks at splash screen (with green "HTC"). No hard button can be used, I need to reboot by take off the battery, then put it back on.
fastboot still seems working fine if I reboot to fastboot mode, but when I try "fastboot erase ...", I get "remote: not allowed". But other commands (fastboot flash...) still ok.
4EXT recovery is also still working.
Please help me to install some ROM at least. A lot of thanks.
Not quite sure, but could it be a faulty eMMC chip? Since you did mention you pulled out the battery.
http://forum.xda-developers.com/showthread.php?t=1314629
I did have a similar problem before myself.
So can you get into the boot loader? I'm assuming so since u got into fast boot. I would try flashing an update.zip through there, such as a stock from containing recovery.img,system.img...etc.
Sent from my HTC Desire HD using xda premium
Thank you for replies.
@microlah: I think my problem is not eMMC because I did not get those errors.
@stumpyz9: Before trying to flash Endymion 3.1, I made a backup of the rooted Sense 3.0 through Rom Manager -> a collection of *.img files.
I have tried to boot into fastboot, and executed these commands:
fastboot erase boot -> Error: remote not allowed
fastboot erase recovery -> Error: remote not allowed
fastboot flash system system.img -> OK
fastboot flash boot boot.img -> OK
fastboot flash userdata data.img -> OK
fastboot flash recovery recovery.img -> OK
but after this, the phone still does not boot normally.
Please tell me if I did something wrong or not. I dont know how to make update.zip from *.img files, and dont know where to get and choose the right stock rom for my phone.
d_t_kien said:
Dear all, I need your help ASAP.
My phone (rooted) doesn't boot now, adb does not recognizes, fastboot still ok. And I don't know what to do.
Recently I rooted my Desire S and succeeded with the stock ROM. After a coupe of days I dicided to flash Endymion, from here: http://forum.xda-developers.com/showthread.php?t=1310845
I downloaded Endymion 3.1 into SD, then used Rom Manager to flash it. But then it was not be able to reboot (stucked on splash screen).
Click to expand...
Click to collapse
Are you S-OFF or htcdev unlocked ? If you're still S-on you have to manually flash boot.img with fastboot to get Endymion or others custom roms working.
d_t_kien said:
Thank you for replies.
@microlah: I think my problem is not eMMC because I did not get those errors.
@stumpyz9: Before trying to flash Endymion 3.1, I made a backup of the rooted Sense 3.0 through Rom Manager -> a collection of *.img files.
I have tried to boot into fastboot, and executed these commands:
fastboot erase boot -> Error: remote not allowed
fastboot erase recovery -> Error: remote not allowed
fastboot flash system system.img -> OK
fastboot flash boot boot.img -> OK
fastboot flash userdata data.img -> OK
fastboot flash recovery recovery.img -> OK
but after this, the phone still does not boot normally.
Please tell me if I did something wrong or not. I dont know how to make update.zip from *.img files, and dont know where to get and choose the right stock rom for my phone.
Click to expand...
Click to collapse
No font flash the backup .imgs flash a whole update zip through the boot loader. Use a stock rom that contains a bunch of .imgs. reflashing the ones u already have won't help
Sent from my HTC Desire HD using xda premium
Are you on hboot 2.00.002? If yes, did you flash the boot.img from Endymion via fastboot??
Sent from my iPod touch using Tapatalk
I used htcdev to unlock, it's still S-ON and HBOOT 2.00.002.
I did not flash boot.img of Endymion. Can I do that with "fastboot flash..." ?
Does it matter if "fastboot erase boot" makes error? (as I posted above)
Could you give me instructions step-by-step what I need to do, thank you.
hi all,
i have some problem like a d_t_kien (i have htcdev unlock dev. and HBOOT 2.00.002, 4EXT Recovery).... so after flash ROM (i try Reaper V2.0 - CM7mod) device has freeze on white HTC screen....
Please help us... how correctly flash Endymion ROM via fastboost..
Thanks
For both of you, here's the procedure. First, flash the ROM normally. Then, enter fastboot mode and flash the boot.img that came in the ZIP of your ROM.
Reference - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
thx for your answer, its my bad, because i dont use search button... so i finf solution in this thread: http://forum.xda-developers.com/showthread.php?t=1314629
thx again .)
shrome99 said:
For both of you, here's the procedure. First, flash the ROM normally. Then, enter fastboot mode and flash the boot.img that came in the ZIP of your ROM.
Reference - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Click to expand...
Click to collapse
Many thanks. That solved my problem.
Edmyrion works great now on my phone.
Glad i helped
Solved
Please marked this thread as solved. Thanks moderator.
d_t_kien said:
Please marked this thread as solved. Thanks moderator.
Click to expand...
Click to collapse
You'll have to do it yourself.... As OP, that's one of your privileges... Just go to the first post, select EDIT, then ADVANCED, and then you can edit the title of your thread and add "SOLVED" to the title.
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...
I posted this on reddit...but didn't get much help...i hope the geniuses at xda can help me
As the title says, the camera app (any camera app) won't work because as you start any of them, it asks to insert the sd card, but this is a 2013 Nexus 5...so it doesn't have an sd card.
I've done a fair amount of research and the only thing that seems to be mentioned is factory reset. I've done that...both through the settings and twrp. The phone has a stock marshmallow rom.
I tried to download any other file and it won't let me download anything becauase the "sd card" is not available. So it's as if the internal sd card isn't mounted? how do I fix this? I don't have a computer nearby to do anything with adb...any help would be GREATLY appreciated...
The amount of storage according to the settings is correct (3gb used of 12 gb..16gb nexus 5)...all app permissions are correct. I've reflashed two different stock firmwares with the exact same result.
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
audit13 said:
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
Click to expand...
Click to collapse
I'll try that tonight or tomorrow morning. Where do you suggest I download recovery.img (the stock recovery)?
Thanks for the help one way or another.. Hehe
The stock Google images are here: https://developers.google.com/android/nexus/images?hl=en
I assume the phone has an unlocked bootloader since you were able to flash stock ROMs.
What did you do between all being fine and now this problem?
Sent from my Xperia z5 using Tapatalk
Ben36 said:
What did you do between all being fine and now this problem?
Sent from my Xperia z5 using Tapatalk
Click to expand...
Click to collapse
I sold the phone to someone I know. I had a rom (i can't remember which)...so before i sold the phone, i encrypted it, wiped it clean, flashed the stock rom (and radio)....and did a factory reset.
audit13 said:
Try this:
boot into fastboot;
run this fastboot command: fastboot erase recovery (to erase existing recovery);
run this fastboot command: fastboot flash recovery recovery.img (to flash stock recovery from stock ROM)
run this fastboot command: fastboot erase userdata;
run this fastboot command to flash the usedata img from the stock ROM: fastboot flash userdata userdata.img;
boot into stock recovery and perform a factory wipe/reset and wipe cache;
reboot.
Click to expand...
Click to collapse
Thanks! I used the factory images and flashed everything from the compressed archive and it worked..you're a lifesaver. I guess I had to go further and reset everything..but thanks again!
Hi, so I was messing with the recovery mode on my phone when trying to install a new rom and somehow ended up wiping the os. I actually managed to install the rom, but I don't know what possessed me to start tapping random buttons and that's how it got messed up. Now my phone is stuck in fastboot mode and I don't know how to get it back to normal. Any advice on how would be a great help, thanks in advance.
sara_ said:
Hi, so I was messing with the recovery mode on my phone when trying to install a new rom and somehow ended up wiping the os. I actually managed to install the rom, but I don't know what possessed me to start tapping random buttons and that's how it got messed up. Now my phone is stuck in fastboot mode and I don't know how to get it back to normal. Any advice on how would be a great help, thanks in advance.
Click to expand...
Click to collapse
Fastboot flash recovery, then try using adb commands to boot into recovery and flash your ROM again. Or, try extracting the system.img from your ROM, place the system.img(rename the file to system.img if it is labeled by another name) in your fastboot folder on PC, open a terminal and flash the system.img via fastboot using the following command:
fastboot flash system system.img
Droidriven said:
Fastboot flash recovery, then try using adb commands to booting recovery and flash your ROM again. Or, try extracting the system.img from your ROM, place the system.img(rename the file to system.img if it is labeled by another name) in your fastboot folder on PC, open a terminal and flash the system.img via fastboot using the following command:
fastboot flash system system.img
Click to expand...
Click to collapse
Thank you so much. I was able to install the ROM via flash recovery, it was pretty easy. THANKS A LOT!!