I recently tried to install a ROM on my HTC one and it seems to have soft bricked my device. I don't seem to have a recovery anymore so I tried to flash TWRP using fastboot. But everytime I try the command flash recovery, I get an error that says cannot open recovery.img. I have searched and found a few tutorials and i seem to be doing everything right but the recovery wont flash. Any help? My phone will not boot at all. Fastboot works but thats about it. When i click reboot it just goes blank then goes to the exact same screen. When I click on recovery it does the exact same thing.
Is recovery in the same folder you open the terminal in? If so make sure to type in "fastboot flash recovery recovery.img"
Sent from my HTC One Max using Tapatalk!
Yeah. Its in the same folder. It gives me an error every time. I can't figure out why it doesn't work.
Sent from my SPH-D710 using Tapatalk
Did you happen to use the CM Installer to unlock,root, ect?
If you did you won't be able to flash any other roms or recoveries without running an RUU.
2ndaccord said:
Yeah. Its in the same folder. It gives me an error every time. I can't figure out why it doesn't work.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
what recovery are you tring to install
if it's for sprint it should be: fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
the recovery img should be in your fastboot folder
you phone in bootloader fastboot usb.
Aldo101t said:
what recovery are you tring to install
if it's for sprint it should be: fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
the recovery img should be in your fastboot folder
you phone in bootloader fastboot usb.
Click to expand...
Click to collapse
hmmmm... fastboot folder? This person needs a bit more than that, seemingly.
So, first, there is some folder (directory) in which your "fastboot" program exists -- let's call that "FastbootDir" for this discussion. Do this:
1) Download the latest TWRP (2.7.0.x), you can use mine, or the standard release, your choice: my build (with enhancements) or the standard;
2) copy that file *exactly* as it is (quit the renaming game -- fastboot does not need that -- it could care less what the file name is) to your *FastbootDir* folder;
3) Open your file explorer and browse to that same directory (your FastbootDir folder);
4) Right click in the file area and open a command terminal *as administrator*;
5) now type this in the command window:
dir openrecovery*.img
If that says "file not found" or similar -- you either failed to copy the downloaded file to that directory, or, well, you renamed it (don't do that!);
If it tells you file name, *that* is the exact file name you must enter into the flash command. Let's say you chose my build, which will say "openrecovery-m7wls-2.7.0.2-03-13-2014.img" -- then to flash that you will type:
fastboot flash recovery openrecovery-m7wls-2.7.0.2-03-13-2014.img
If on the other hand you chose the standard build from TeamWin:
fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img
That should do it. Report back if you have troubles.
I finally got it flashed. Thanks for all the help. I am a newb with HTC devices. I installed the ROM that I had on the device but now it won't boot up. All i get is a white HTC screen and "process com.htc.htcdialer isn't responding". I have wiped several times and tried to install 2 different roms but i never get past the HTC screen. I can get to the lock screen but as soon as I unlock it the phone just reboots and I get stuck again. Any suggestions?
2ndaccord said:
I finally got it flashed. Thanks for all the help. I am a newb with HTC devices. I installed the ROM that I had on the device but now it won't boot up. All i get is a white HTC screen and "process com.htc.htcdialer isn't responding". I have wiped several times and tried to install 2 different roms but i never get past the HTC screen. I can get to the lock screen but as soon as I unlock it the phone just reboots and I get stuck again. Any suggestions?
Click to expand...
Click to collapse
Suggest you flash a such rooted ROM just to start at a place of sanity.
Did you check all of your md5, and using your exact ROM? Are you m7spr or m7wls?
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
M7 wls. In not sure how to check the md5 sum. I was already on the bad boys rom so I know the rom was a good download. It just won't get past the htc screen.
Sent from my SPH-D710 using Tapatalk
2ndaccord said:
I finally got it flashed. Thanks for all the help. I am a newb with HTC devices. I installed the ROM that I had on the device but now it won't boot up. All i get is a white HTC screen and "process com.htc.htcdialer isn't responding". I have wiped several times and tried to install 2 different roms but i never get past the HTC screen. I can get to the lock screen but as soon as I unlock it the phone just reboots and I get stuck again. Any suggestions?
Click to expand...
Click to collapse
Sounds like you flashed a GSM rom at one point and messed up your partitions.
I would suggest running an RUU and starting fresh.
If he tried to flash ANYTHING gsm you pretty much have to RUU... Are you trying to go GSM or stay CDMA? I would suggest viper ROM flashing in twrp 2.7.0 just to see what that does and if you can get past screen
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
BD619 said:
Sounds like you flashed a GSM rom at one point and messed up your partitions.
I would suggest running an RUU and starting fresh.
Click to expand...
Click to collapse
Why do people do that? Lol. Just ask our sanity keeper @BD619 before running down crazy paths .
tdhite said:
Why do people do that? Lol. Just ask our sanity keeper @BD619 before running down crazy paths .
Click to expand...
Click to collapse
Not trying to sound like a jerk or a know it all but....most folks don't take the time to read the OP
BD619 said:
Not trying to sound like a jerk or a know it all but....most folks don't take the time to read the OP
Click to expand...
Click to collapse
Very, very, very, VERY true. I go through xda on my phone through my "unread" section and see how many people are asking for help, then click on it and it has a link to the same exact problem plus like a hundred others lol, but op, try viper ROM great ROM, one of my friends with the wls is using it, great ROM make sure you're flashing a wls ROM and not a spr..... I've seen posts like that to....
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
I had to ruu back because no Rom would boot. I tried different roms but they all would get to a blank HTC screen. I could unlock the phone but the HTC screen would be there. The the HTC dialer would force close a few times then the phone would reboot. That happened on 2 different roms. Bad boys and on viper Rom. But thanks to everyone for the help.?
Sent from my HTCONE using Tapatalk
tdhite said:
hmmmm... fastboot folder? This person needs a bit more than that, seemingly.
So, first, there is some folder (directory) in which your "fastboot" program exists -- let's call that "FastbootDir" for this discussion. Do this:
1) Download the latest TWRP (2.7.0.x), you can use mine, or the standard release, your choice: my build (with enhancements) or the standard;
2) copy that file *exactly* as it is (quit the renaming game -- fastboot does not need that -- it could care less what the file name is) to your *FastbootDir* folder;
3) Open your file explorer and browse to that same directory (your FastbootDir folder);
4) Right click in the file area and open a command terminal *as administrator*;
5) now type this in the command window:
dir openrecovery*.img
If that says "file not found" or similar -- you either failed to copy the downloaded file to that directory, or, well, you renamed it (don't do that!);
If it tells you file name, *that* is the exact file name you must enter into the flash command. Let's say you chose my build, which will say "openrecovery-m7wls-2.7.0.2-03-13-2014.img" -- then to flash that you will type:
fastboot flash recovery openrecovery-m7wls-2.7.0.2-03-13-2014.img
If on the other hand you chose the standard build from TeamWin:
fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img
That should do it. Report back if you have troubles.
Click to expand...
Click to collapse
I have the same exact problem and applied your advices. Nothing helps. I am frustrated because I have done this before an dnow I can't get it done. If you please can help me?
nossman said:
I have the same exact problem and applied your advices. Nothing helps. I am frustrated because I have done this before an dnow I can't get it done. If you please can help me?
Click to expand...
Click to collapse
See if this helps: http://forum.xda-developers.com/showpost.php?p=55452567&postcount=527
Don't respond there -- that's a dev thread, but honestly it's pretty easy. My suspect is you don't have the SDK (fastboot, adb, etc. properly setup). The fastboot program needs to be on your PATH, or you need to open a command window ***as administrator*** and make sure you are in the directory in which fastboot exists (e.g., type "dir fastboot*.*") and if it doesn't come back with something, you're not in the correct directory.
deleted, wrong thread.
QUOTE=nossman;55476580]Thank you! I have just installed brand new ADB tools etc. rebooted . . .[/QUOTE]
First -- could you *please* go delete the post you laid down in my TWRP development thread -- I specifically asked you *not* to do that. Dev threads are not support or Q&A threads and that post takes up a bunch of space totally unnecessarily. Sigh ...
Second -- if the command fails like that it means you have the wrong path to the file you downloaded. Do a file search for openrecovery*.* starting in C:\ and use the path it finds.
Related
Hi guys!
I received my Nexus yesterday en immediately rooted and unlocked the device. No problems so far.
I want to install a the cyanogen custom rom on my nexus but get stuck in the recovery step.
I have used the tutorial from Theunlockr . com (unfortunately I cant insert a link here because Im a new member)
Because I already rooted and unlocked my Nexus I started with ''III. Flash the Custom ROM''. I managed to start up the bootloader and click on 'Recovery'. Here the problems start, after clicking on 'recovery' a screen with a yellow exclamation shows up. (see attachment for screenshot)
Can somebody help me with flashing my Nexus with a custom rom? Thanks in advance!
Try to run "fastboot boot recovery.img" and see if that works. (Something like that anyway)
This was what I did for all my time using Amon's 1.5.3 recovery. Now that I'm on 1.6.0, I can use the normal recovery. That worked perfectly for me anyway. I also would always boot to that screen when attempting the normal recovery via the phone.
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' on my Mac?
I am quite an android-noob.
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' ?
I am quite an android-noob.
Click to expand...
Click to collapse
So am I
To run fastboot, you should simply go find the Android SDK download. Once you've downloaded that, make your way to the tools folder. Place the recovery image in that folder and then Shift+Right Click in the window. You click the option to bring up a command prompt.
In that Command prompt, type flashboot devices and verify the PC sees your phone. If so, then you can do the Flashboot command. Though you may need USB drivers. If you do need them, they're somewhere in this forum, but I've completely lost track of them.
P.S. if my initial command doesn't work... You might need to try "fastboot boot recovery recovery.img"
(Note... Don't try "Flashboot".. That was a typo )
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' ?
I am quite an android-noob.
Click to expand...
Click to collapse
got this info from the same site you posted, you just skipped the step before you started to flash the rom altogether.
II. Flash a Custom Recovery Image
1. Download the Nexus One Amon Ra Recovery Image below:
Nexus One Recovery Image (Link under Download in the first Post)
2. Save the recovery image file inside the superboot folder you used to root the phone.
3. Turn the phone off and then plug it in via USB cable.
4. Turn it on by holding down Power and the Trackball to get into fastboot mode.
5. Open a command prompt and type the following with hitting enter at the end of each line:
cd\
cd c:\superboot
fastboot-windows devices
*this is to check that the computer can see the phone (a serial should pop up if it can)
6. Then type:
fastboot-windows flash recovery recovery-RA-nexus-v1.5.3.img
7. This should flash the recovery image onto the phone.
Click to expand...
Click to collapse
The recovery img is in this thread
http://forum.xda-developers.com/showthread.php?t=611829
Click to expand...
Click to collapse
Also, you don't really need the android sdk for flashing the recovery img, but it's a good idea to download it for future use.
Can ANYONE just stop answering threads that are in wrong sections?
lazinase said:
Can ANYONE just stop answering threads that are in wrong sections?
Click to expand...
Click to collapse
Why? So that it gets moved and answered anyway? The sooner the guy gets helped out... The sooner the post gets buried.
A mod will be by to do their duty later. As the community, we may as well help in the mean time.
Man, oh man. Niceness has really lost some popularity in the virtual world, hasn't it...
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' on my Mac?
I am quite an android-noob.
Click to expand...
Click to collapse
If you use a Mac, you don't deserve help. Bootcamp Windows and we'll talk.
grainysand said:
If you use a Mac, you don't deserve help. Bootcamp Windows and we'll talk.
Click to expand...
Click to collapse
great help!
for a mac just use ./fastboot-mac in the terminal
Like they said, sounds like you are missing recovery. Just do the step two, you skipped it. Why flame people? He is new, might as well help, instead of making this thread longer by telling him to post in right section.
Besides, he did find tutorials and followed them, he didn't come here completely unprepared and expecting people to walk him through. We all make mistakes sometimes, specially when dealing with something we are new to, he simply skipped a step.
MOD EDIT - Thread moved to Q&A
Hey all, completely lost as to where I am with my g1 haha, let me explain:
I installed v4.2.15.1 cyanogen mod a few months ago.
Then today I wanted to try and upgrade it, or just reset to standard android, didn't mind.
So I pressed camera/power button, and then installed the DREAIMG.nbh as I guessed this would reset it to RC7 (Which it did).
Then I tried gaining root access through telnetd, then using telnet to try and use a new recovery.img... this is where my problem starts.
I typed: "flash_image recovery /sdcard/recovery.img" (recovery-RA-dream-v1.7.0.img or better for CM5) and got a file not found error.
Tried it a number of different ways, but just wouldn't work.
Then tried booting into recovery mode (using home and power) but just got a white triangle/orange !.
From here I have no clue what to do, I'm just stumped as I can't use the recovery mode, and can't seem to do anything in telnet?
My phone is still useable, just stuck with android 1.0...
Any help please how i can either just get it back to a completely standard 1.5, or the newest cyanogen mod ?
P.s, this is what my about phone status are:
model number: T-mobile G1
firmware version: 1.0
baseband version: 62.33.20.08U_1.22.12.29
kernel version: 2.6.25-01843-gfea26b0android-build(at symbol)apa27 #6
build number; kila_uk-user 1.0 TC5-RC7 112931 ota-rel-keys,release-keys
Try to fastboot it. The triangle screen is the stock recovery.
Btw, why would you unroot just to install CM5?
r3s-rt said:
Try to fastboot it. The triangle screen is the stock recovery.
Btw, why would you unroot just to install CM5?
Click to expand...
Click to collapse
Will give the fastboot a go.
And uhh.. not sure why I "unrooted" it really, did this as a spur of the moment thing, and from what I read you couldn't upgrade directly from 4.x cyan to a 5 version :/
Thanks for the help so far though .
Wow, not a clue where to start with this fastboot thing, think I'll have to wait till tomorrow when I can have a proper sit down and do it.
Wigster said:
Will give the fastboot a go.
And uhh.. not sure why I "unrooted" it really, did this as a spur of the moment thing, and from what I read you couldn't upgrade directly from 4.x cyan to a 5 version :/
Thanks for the help so far though .
Click to expand...
Click to collapse
Yes, you can directly update with nothing more than a simple wipe and reflash.
Wigster said:
Wow, not a clue where to start with this fastboot thing, think I'll have to wait till tomorrow when I can have a proper sit down and do it.
Click to expand...
Click to collapse
Well, when fastbooting recovery, about the worse I've ever pulled off is fastbooting the H recovery instead of the G recovery (I'm on a myTouch) and had to fo back and reflash the G recovery to be able to get into recovery. Not to mention its a quick hop from bootloader to recovery to see if it worked and doesn't require a working ROM.
I need a rooted phone for fastboot though, do I not? and as I couldn't load the recovery, I do not think my phone is rooted?
Wigster said:
I typed: "flash_image recovery /sdcard/recovery.img" (recovery-RA-dream-v1.7.0.img or better for CM5) and got a file not found error.
Click to expand...
Click to collapse
I don't want to insult your intelligence, but you did place the file on the root of the sdcard and rename it to recovery.img didn't you..? If you didn't rename it, you'd obviously have to type "flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img"
goldenarmZ said:
I don't want to insult your intelligence, but you did place the file on the root of the sdcard and rename it to recovery.img didn't you..? If you didn't rename it, you'd obviously have to type "flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img"
Click to expand...
Click to collapse
Yes I did rename it, and checked and double checked, even reformatted card and tried again, but to no avail.
Thanks for asking though .
Was the sd definitely mounted? If you didn't unmount it from the PC after copying the file, it wouldn't be accessible to android..
goldenarmZ said:
Was the sd definitely mounted? If you didn't unmount it from the PC after copying the file, it wouldn't be accessible to android..
Click to expand...
Click to collapse
Yup, just double checked says:
"error opening /sdcard/recovery.img: No such file or directory"
Also, when I try "su", it says: "su:not found".
Utterly baffled .
Wigster said:
Yup, just double checked says:
"error opening /sdcard/recovery.img: No such file or directory"
Also, when I try "su", it says: "su:not found".
Utterly baffled .
Click to expand...
Click to collapse
Sounds to me exactly like the sdcard isn't mounted.
Mounting has to do with being joined with the running filesystem.
Provide the output of "mount".
As for fastboot... you will need to install the SPL 0.95.3000, or even better 1.33.2003 (that ends in a *THREE* --- very important).
Wigster said:
Will give the fastboot a go.
And uhh.. not sure why I "unrooted" it really, did this as a spur of the moment thing, and from what I read you couldn't upgrade directly from 4.x cyan to a 5 version :/
Thanks for the help so far though .
Click to expand...
Click to collapse
I lol'd at that part.
Thinking now that possibly my sdcard is b0rked somehow. My phone can see it and everything and I can read/write on my pc to it. But whatever I try the phone just keeps saying "error opening ########: No such file or directory" (Where ###= file name)
FAIL.
I renamed recovery.img, literally "recovery.img" and obviously it didn't need the .img tag in the filename.
Please disregard/lock this thread .
I think I may have bricked my phone. It's a rooted htc hero cdma. I'm running cyogenmod on it and it was working fine, until using metamorph to apply some changes to the theme.
I went to reboot, and it now it won't load past the htc screen. Even when i try the key combination to put it into recover mode. I didn't install a nandroid backup, and i'd be fine with just completely wiping my phone. can someone please help me?
Have you tried flashing the ROM back over itself without wiping? Try that first, and if that won't work, do a full format and reflash the ROM and you should be good to go.
And just an FYI, you really can't fully brick your phone by flashing a ROM or theme. You can always get it back.
Do what ranger suggested.
To elaborate, I *think* as long as your phone turns on, it is not bricked. Specifically, as long as you can boot to recovery you can do whatever you need to do, be it make fixes or start from scratch again. (I think even if you can't boot to recovery, but it turns on, you can run the RUU ). The only way to brick is to flash a wrong/corrupt radio or anything below the radio level.
Wipe then reboot and wait. When you change the framework, initial boot takes longer.
Sent from my HERO200 using XDA Premium App
I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.
What key combination are you using? Hold home then depress end key/power key until phone vibrates.
Sent from my HERO200 using XDA Premium App
Load the fast boot ruu flash
Done
zbach said:
I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.
Click to expand...
Click to collapse
Sent from my HTC Hero CDMA using XDA App
mahalocat said:
Load the fast boot ruu flash
Done
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?
zbach said:
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?
Click to expand...
Click to collapse
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968
il Duce said:
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I don't see the command to run "fastboot oem rebootRUU"
zbach said:
I don't see the command to run "fastboot oem rebootRUU"
Click to expand...
Click to collapse
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.
il Duce said:
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.
Click to expand...
Click to collapse
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.
zbach said:
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.
Click to expand...
Click to collapse
did you do the adb command first, like it says?
il Duce said:
did you do the adb command first, like it says?
Click to expand...
Click to collapse
yeah, it won't recognize that either. i'm selecting the right path to my C drive too. the driver just isnt recognized :/
You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.
wild1z said:
You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.
Click to expand...
Click to collapse
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.
zbach said:
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.
Click to expand...
Click to collapse
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.
okay, i found and am currently downloading the file. so i should just have to root it to my SD, then flash it, right?
I'm really hoping this works.
il Duce said:
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.
Click to expand...
Click to collapse
still nothing. it only tells me its and error, and cannot load the .zip file.
zbach said:
still nothing. it only tells me its and error, and cannot load the .zip file.
Click to expand...
Click to collapse
I don't know where the file should be located, but your posts in the other thread will yield better answers, jason knows the way better than me, given he started the thread. Wait for his response. I assume the error has something to do with where you have the ruu and what path you need to specify in the cmd. Wish I could be of more help. Once you fix it and get back to rooted and such, I HIGHLY recommend you get s-off, its basically like idiot-proofing your phone (no offense) so you can fix anything.
sent from a series of tubes.
tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!
leppricon said:
tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!
Click to expand...
Click to collapse
Try the 4.0.0.2-pr1 again and again until it goes through. DO NOT REBOOT YOUR PHONE UNTIL IT SUCCEEDS, IT WILL RESULT IN YOU BEING STUCK IN FASTBOOT!!!!!
Try deleting mlk file and reinstalling recovery
Sent from my VS910 4G using XDA App
Installed rom manager
I installed rom manager to use to back up phone it rebooted to run the back up and it got stuck in fast boot, so i did some searching and found the page on fixing that. i used the second posters method instead of thecubed (because he said it was easier and thecubed agreed) and now all i get is an lg start screen. do not follow the other guys post it is for another phone completely i had to find it out the hard way. so any ideas on how i can get back to working phone?
The file you deleted was the mmcbik0p8 backup found on your ext card. When reinstalling the recovery CWM should have rewritten it with the correct version.
Try removing your card and mounting it on a pc go in and manually delete file and try to boot the phone. I had to do this to make my revolution boot.
This is how i fixed it
adrenaline_rush said:
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
http://www.mediafire.com/?eb3219cy0lbc71m
Android SDK
Java JDK
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
Click to expand...
Click to collapse
Don't work
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.
leppricon said:
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.
Click to expand...
Click to collapse
You tried the volume up + power to get to the recovery?
Tried that too.
The only way the Vol. up and power button works if I have the battery out and the usb hooked up, and then the screen says do not detach download in progress. I left it this way for about two hours thinking it would magically fix it self but it didn't. Called Verizon about an hour ago and I going to get my new phone in the afternoon tomorrow. they over-nighting it to me, they said any new tech with 4g they try to get it fixed as fast as possible. I then asked when 4g would be coming to my area he said spring of 2013... lol
Oh, you could have flashed the .tot system file over, but I guess it does take some time to get the program set up, and they're already replacing it..
Tried
I had all the above programs installed and working properly, that is how i got to a non-working phone, I flashed it with the wrong firmware which bricked it. Its not detected in any of the programs because all the programs are looking for a revo and i flashed to something else.
This was posted in the revo fastboot fix thread, I followed it and it bricked my phone.
hello everyone, im pretty sure i was the first one to run into this issue since it happened twice on two different phones. but for an extremely easy fix just look here, believe me it doesn't get any easier than this. this is another way it was explained, but both are pretty much the same. im only posting this in case someone doesn't understand the directions posted by thecubed, not saying the ones i post it are better, just explained differently, not trying to step on anyone's shoes here http://forum.xda-developers.com/show....php?t=1088046
Last edited by zr0ko0l; 23rd June 2011 at 03:03 AM.
this is the reply from thecubed: Dont' worry about my toes
If you've got a better explanation, go for it! I'm not the best at writing instructions.
Still no CWM
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
Why run V6 when V7 (aka GingerBread) is out?
meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
DId you manually use adb and Zergrush or use a different method? Did you use my all in one package with the root.bat? More info would be greatly appreciated.
Issues activating 4G LTE
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama
cantibot said:
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama
Click to expand...
Click to collapse
Was 4g turned on when you flashed? If nothing else you can flash the zv7 tot file through lgnspt.
Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.
cantibot said:
Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.
Click to expand...
Click to collapse
What version were you on before you flashed Gingervolt? If you were on v4 or v6 it will do that.
Sent from my Gingervolt-ed VS910 4G using xda premium
I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
This is a response to post #14. I meant to post this with a quote. Instead, I posted a quick reply. Sorry.
meandmine said:
I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
Click to expand...
Click to collapse
Not a permission problem, there are a couple of files in there that have to be removed otherwise it blocks it from booting into cwm with the key press combo. You have to boot into cwm using quick boot or the reboot into recovery option in the revotoolkit menu. If you flash GingerVolt you will then have reboot and recovery in the power menu, but also will be able to enter recovery through the button combo.
You will have to push the recovery image again first though.
I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
cburch85 said:
I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
Click to expand...
Click to collapse
donwload the all in one toolkit use it to erase cache then install recovery. after that either mount usb otg and copy rom to sd or sideload a rom. all in one toolkit automates everything you need to do:good::good:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
cburch85 said:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
Click to expand...
Click to collapse
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
skinsfanbdh said:
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
Click to expand...
Click to collapse
Thanks for getting me this far. Mounting didn't work, so I sideloaded rom. it is showing up on the phone as "sideload.zip" i try to run and it fails. Any ideas?
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Guich said:
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Click to expand...
Click to collapse
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
im guessing your using twrp but just select no dont root the rom is already rooted and it should boot. may take getting through a few aroma freezes but it will boot
cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Guich said:
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Click to expand...
Click to collapse
OK, so I didn't say yes to the question this time after sideloading android revolution. same thing. goes blank then reboots to bootloader menu. So I tried sideloading viperrom 1.04. This time after it finished sideloading it randomly installed instelfl, and now viperrom is installed, its booting up to the phone now finally, yet before anything can initialize, it just reboots again. It's been caught in this boot loop about ten minutes now. No end in sight. Any ideas?
ViperRom from Sprint or AT&T one forum?
Your phone is branded or no-brand?
However, boot into recovery, and use this command:
Code:
adb push name_of_rom.zip /sdcard
, then flash it
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
cburch85 said:
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
Click to expand...
Click to collapse
Have you tried to flash the boot.img from fastboot?
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
cburch85 said:
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
Click to expand...
Click to collapse
Where did you find the RUU for sprint? I cant seem to find one that works with my CID: SPCS_001.
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
zach832 said:
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
Click to expand...
Click to collapse
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Can't detect SD Card
Guich said:
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Click to expand...
Click to collapse
Hi, I'm having sort of the same problem. My phone is stuck on a bootloop, I flashed a new recovery because the previous TWRP stopped working. When I try to wipe data/factory reset, It says that it can't detect E:\ or the SD Card. I can't even mount it. Any ideas? Please help. Thanks