Hi, I tried to root my GSM Hero using adb, however I messed up, and managed to use a wrong rom/image (for another HTC model). Obviously, my phone now doesn't boot, but I am still able to boot into bootloader mode by pressing volume down + power on.
This is probably a n00b question which has been asked before, but I've been searching for hours now with no luck. Can anyone tell me, or point me in the right direction, how to fix the bootimage on my phone, so that I am able to boot again, if possible? I've read something about creating a gold card, is this necessary to save my phone?
What exactly were you trying to flash through adb?
Have you put on a custom recovery yet? If not,.... put AmonRa1.6.2 onto your sd, go into fast boot (vol- +Power) and then
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot
Then hold HOME + POWER to power on into recovery, then flash new rom from there.
I wasn't able to get adb working after flashing and using the wrong ROM, however, I was able to solve the problem after all. I had tried the HBOOT/rom.zim/HEROIMG.zip way of flashing, but HBOOT did not find the HEROIMG.zip-file. I then tried to format my SD-card, wiping it completely, and partitioning it with FAT32, not FAT. After that, HBOOT found the HEROIMG.zip, and I was able to "reinstall" my phone. I will now give rooting it another go, this time without ****ing it up
Problem solved.
Good man. Just put [SOLVED] into your thread title. Thanx
Related
I've searched everywhere i can thing and havn't found quite the answer for my problem:
My wife's stock, fully updated photon crapped out the other day and we just got the refurb replacement. The problem is that i can't get adb access to the phone so i can't pull the pictures off of it. I did find one way to pull it for a rooted GNex but before i try it i'd like to check if it will work on a stock, unrooted, mopho.
"Boot up CWM and then pull the files. Step-by-step:
1) Download CWM, rename it to cwm.img and place it in the same directory as your fastboot executable;
2) Reboot you device into fastboot mode and connect to your computer;
3) Make sure your computer sees your device by typing: fastboot devices
4) Boot CWM by typing: fastboot boot cwm.img
5) Pull all the files from /sdcard by typing: adb pull /data/media"
Any and all help would be appreciated and thank you in advance!
my GF has a moto phone and to get into fsstboot i power off, hold volume down, then you'll see fastboot. plug your phone into your computer, then press volume up. i don't know if ADB will be able to pull out the files you want without rooting, but it's worth a try.
good luck!!
Sent from my HTC Glacier using xda premium
I can access fastboot, and control the phone thru fastboot, but I don't know how to get access to the internal memory. I guess i'll try to boot a stock recovery and ADB from there?
cruxanyra said:
I've searched everywhere i can thing and havn't found quite the answer for my problem:
My wife's stock, fully updated photon crapped out the other day and we just got the refurb replacement. The problem is that i can't get adb access to the phone so i can't pull the pictures off of it. I did find one way to pull it for a rooted GNex but before i try it i'd like to check if it will work on a stock, unrooted, mopho.
"Boot up CWM and then pull the files. Step-by-step:
1) Download CWM, rename it to cwm.img and place it in the same directory as your fastboot executable;
2) Reboot you device into fastboot mode and connect to your computer;
3) Make sure your computer sees your device by typing: fastboot devices
4) Boot CWM by typing: fastboot boot cwm.img
5) Pull all the files from /sdcard by typing: adb pull /data/media"
Any and all help would be appreciated and thank you in advance!
Click to expand...
Click to collapse
Without unlocking the bootloader your not going to be able to use cwm.
cruxanyra said:
I've searched everywhere i can thing and havn't found quite the answer for my problem:
My wife's stock, fully updated photon crapped out the other day and we just got the refurb replacement. The problem is that i can't get adb access to the phone so i can't pull the pictures off of it. I did find one way to pull it for a rooted GNex but before i try it i'd like to check if it will work on a stock, unrooted, mopho.
"Boot up CWM and then pull the files. Step-by-step:
1) Download CWM, rename it to cwm.img and place it in the same directory as your fastboot executable;
2) Reboot you device into fastboot mode and connect to your computer;
3) Make sure your computer sees your device by typing: fastboot devices
4) Boot CWM by typing: fastboot boot cwm.img
5) Pull all the files from /sdcard by typing: adb pull /data/media"
Any and all help would be appreciated and thank you in advance!
Click to expand...
Click to collapse
When you say "crapped out" I'm guessing you mean it won't boot at all? What is the phone that you need the pictures off of capable of doing at the moment?
celloevan said:
When you say "crapped out" I'm guessing you mean it won't boot at all? What is the phone that you need the pictures off of capable of doing at the moment?
Click to expand...
Click to collapse
I'm sorry, yes. By crapped out I mean wont boot. I can get it to "Failed to boot 1" and "Failed to boot 1-Fastboot" I can control it with Fastboot from my Ubuntu 12.04 laptop but can't get ADB to take hold or use fastboot to load the internal storage as UMS.
Recovering the phone isn't an issue, we have an insurance policy. But I can't unlock it and then send it in b/c they might charge us for the phone.
A few ideas I've had are:
Boot into stock recovery.img using fastboot and ADB from there
Use a script using fastboot -c to mount the internal storage as UMS
I just read something about getting into recovery from fastboot using the down volume but I haven't tried it yet
Failed to boot 1 is a issue with the bootloader.
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
reaper90 said:
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
Click to expand...
Click to collapse
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
JustinBieber said:
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
Click to expand...
Click to collapse
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
reaper90 said:
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
JustinBieber said:
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
Click to expand...
Click to collapse
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
reaper90 said:
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
Click to expand...
Click to collapse
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
JustinBieber said:
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
Click to expand...
Click to collapse
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
reaper90 said:
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
Click to expand...
Click to collapse
After command prompt has successfully listed my device with its code, I typed in adb sideload (therom).zip and it says * cannot read 'sideload' * The tutorial that you posted doesnt have sideloading a rom
Edit: Okay, I installed SDK Manager did those things and this link really helped me on pushing files through adb. I will test to see if dirty flashing the rom will allow the phone to boot
Edit 2: Damn.. had to wipe everything and do a clean install. Never replace a bootanimation from another phone cause it ****s up your phone and time
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Addicted2xda said:
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Click to expand...
Click to collapse
Yep, I downloaded SDK manager and opened the folder in command prompt, that was the only way I could sideload any files into my phone. I sideloaded the rom, reset everything (including system) and fresh install of the rom. Idk what went wrong the only thing I changed was the boot animation zip, which is very peculiar
But I have to thank reaper90 for helping me tons though
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
VivaSativa said:
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Click to expand...
Click to collapse
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Danny Samuel said:
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Click to expand...
Click to collapse
well i tried that before and it still didnt want to work, like it was priorotizing the first one i put in there or something.. but now i came to a wall... since i waited so long to find a sulution i had the device completely empty and just in bootloader.. it seems i dont have the driver or such for it to charge.. so i plugged it into the wall for a while whilst in fastboot thinking it was charging which it was not..
Now it is completely dead i cannot charge it and my computor cant detect it anymore.. seems i found the meaning of a bricked device
i have a linsay 7-xhd that got stuck after using the above command have no adb access from the boot screen and it will not boot into recovery. any ideas to get to recovery or fix? there is no roms firmware or anything available for this device?
I let the battery drain all the way (thankfully the battery isn't great and wasn't fully charged) and i was able to boot into the os. i still wish to access the bootloader any ideas why it would cause a boot loop?
This won't really help, but next time make sure the device is recognized first. That way you know the computer sees it. I start a terminal session with adb devices command first. If nothing comes up( if the phone's on, I get the serial number, if it's on twrp, I get the dev name as in the one in build prop) adb doesn't see it. I go from there, and do what I am trying to do, then use adb reboot bootloader to reboot. The good thing about using twrp is that internal storage shows up, plus sdcard access is shown on the computer, when adb is working right. I don't use windows though, seems that things work better with ubuntu.
Hey guys, I just got LG l9 from my friend but it is (I am afraid, not knowing much about mobiles) bricked.
When I turn it on it says:
-------------------------------------
Secure booting unsuccessful!
Cause:
-------------------------------------
and after that it turns off. If I charge it it turns on and shows battery charging. At combination of Volume+, power button it goes in Recovery mode.
It shows "This mode is for data backup service center. After removing and reattaching battery, press power key to reboot and keep using phone" and from there I can't do anything, just able to take out battery.
If I try combination of Volume-, power button it shows little android and loading bar, after few sec it restarts and shows booting unsuccessful.
I am not sure what he did with it, but pretty sure he rooted it. Is it possible to fix it, hope someone will provide me some help
Thanks !
It is possible to fix, you need to unbrick it. Find the stock rom for your device and find a good tutorial on how to flash em. Good luck!
Thanks for the reply ! I found everything I need, but I got problem - cant enter download mode. On combination of Volume+ and plugging cable I get S/W Upgrade, and on combination Volume+&- and plugging cable I get nothing. Any ideas how to get in that download mode? Thanks!
Infam12 said:
Thanks for the reply ! I found everything I need, but I got problem - cant enter download mode. On combination of Volume+ and plugging cable I get S/W Upgrade, and on combination Volume+&- and plugging cable I get nothing. Any ideas how to get in that download mode? Thanks!
Click to expand...
Click to collapse
www.hardreset.info/devices/lg/lg-p760-optimus-l9/emergency-mode
Try that, then in adb, type adb devices and see if your pops up, if not, try fastboot devices. If it popped up in adb, you can sideload the zip file, if on fastboot, you can flash it.
Try that, then in adb, type adb devices and see if your pops up, if not, try fastboot devices. If it popped up in adb, you can sideload the zip file, if on fastboot, you can flash it.
Click to expand...
Click to collapse
Thanks for your patience and answers! Problem is I cant reach emergency-mode. I always get S/W Update. Under adb devices I can see my phone in recovery mode (was thinking maybe emergency=recovery mode). I tried sideload, it starts loading but after some time I get error:closed. I tried doing adb usb before as well but gave no results.: . Any other ideas? Is there any way to "make" phone run ROM from SD card (in recovery mode can't navigate anywhere like I can on my other phone).
Again thanks for your help and time!
Infam12 said:
Thanks for your patience and answers! Problem is I cant reach emergency-mode. I always get S/W Update. Under adb devices I can see my phone in recovery mode (was thinking maybe emergency=recovery mode). I tried sideload, it starts loading but after some time I get error:closed. I tried doing adb usb before as well but gave no results.: . Any other ideas? Is there any way to "make" phone run ROM from SD card (in recovery mode can't navigate anywhere like I can on my other phone).
Again thanks for your help and time!
Click to expand...
Click to collapse
If it sees your phone as recovery, you can be rescued! Run adb shell and once the shell has popped up, type ls and if you see the phone structure of directories, you can exit the shell and push the file from your pc to your phone. But before you push, I want you to try to run adb reboot-bootloader and see if fastboot recognises it.
RAZERZDAHACKER said:
If it sees your phone as recovery, you can be rescued! Run adb shell and once the shell has popped up, type ls and if you see the phone structure of directories, you can exit the shell and push the file from your pc to your phone. But before you push, I want you to try to run adb reboot-bootloader and see if fastboot recognises it.
Click to expand...
Click to collapse
I think I am making some progress. First on adb reboot-bootloader my phone reboots into secure booting unsuccessful, same as before. On the adb shell/ls I get to see cache, charger, data, default.prop, dev, etc, system, temp and lots of other things. I guess that are directories we are looking for. But when I go adb push filename.zip /data/media I get failed to copy filename.zip: Permission denied. Guess nothing can work at first, sorry
https://forum.xda-developers.com/showthread.php?t=2216896 Have you tried this?
RAZERZDAHACKER said:
https://forum.xda-developers.com/showthread.php?t=2216896 Have you tried this?
Click to expand...
Click to collapse
This gets complicated, I found xloader and uboot, but problem occurs when I try to install fastboot drivers, says third party doesn't contain digital signature information?? I think I was close with shell from adb, just how to get privilege to push files? Tried so many methods.. Thanks again on help.
Hi all, I wonder if anybody can help with this.
my volume buttons are not working (hardware issue) and I was trying to install TWRP and a custom rom but, after installing TWRP the phone now always boots in recovery mode (at least this is what adb tells me) but TWRP does not really start, I keep seeing only "honor, powered by android" black screen.
adb is working but not fastboot. I tried to reboot to bootloader but it always go to recovery instead. I have no su, and I am stuck just with adb in recovery.
any idea?
If you have full adb access maybe you can restore your backup directly from it
Thanks Rayan
how? what do you mean by "full adb access"?
I tried to run adb sideload but it does not work (it says "closed" shortly after without doing anything)
I don't really understand what the issue is, do you have access to TWRP menu or not at all? And when you say that you can use adb, is the device recognized when you type adb devices ? And what happens when you try to boot in bootloader and use fastboot? Can you try to the command "adb reboot bootloader"?
Rayan19997 said:
I don't really understand what the issue is, do you have access to TWRP menu or not at all? And when you say that you can use adb, is the device recognized when you type adb devices ? And what happens when you try to boot in bootloader and use fastboot? Can you try to the command "adb reboot bootloader"?
Click to expand...
Click to collapse
Thanks Rayan, I finally solved replacing the volume buttons (found cheap ones). However adb was working but no matter which command I was sending (adb reboot bootloader) the phone was always rebooting in recovery mode but TWRP was not starting properly (could not see anything)
with volume buttons I managed to enter into bootloader, reflash TWRP and do everything I needed
Thanks