SERIOUSLY STUMPED!!
I was in the process of flashing the 24a ROM when i realized i had to put one more file in the storage in order to flash the ROM completely,but only after i wiped my "laf.img" so i got stuck in fastboot mode ..ended up using fastboot commands to recover my download mode but now I cannot get my device to be recognized by either laptop i tried re-installing drivers and unplugging re plugging,restarting both laptops..i just really don't know what else to do somebody please help ((
To anyone who took the time to read this and help out I also have team viewer available and thank you, any help is given thanks in advance i just need my phone back guys :/
TTMBeats said:
SERIOUSLY STUMPED!!
I was in the process of flashing the 24a ROM when i realized i had to put one more file in the storage in order to flash the ROM completely,but only after i wiped my "laf.img" so i got stuck in fastboot mode ..ended up using fastboot commands to recover my download mode but now I cannot get my device to be recognized by either laptop i tried re-installing drivers and unplugging re plugging,restarting both laptops..i just really don't know what else to do somebody please help ((
To anyone who took the time to read this and help out I also have team viewer available and thank you, any help is given thanks in advance i just need my phone back guys :/
Click to expand...
Click to collapse
I had to install 4 different items under Device Manager to get mine working, when you open it up, are there any icons with the yellow flag on them in the device manager tree?
mjones73 said:
I had to install 4 different items under Device Manager to get mine working, when you open it up, are there any icons with the yellow flag on them in the device manager tree?
Click to expand...
Click to collapse
no...? I restored mine to stock earlier today but mine was from 12b to 11a so I could take the OTA....
TheOriginalKyle said:
no...? I restored mine to stock earlier today but mine was from 12b to 11a so I could take the OTA....
Click to expand...
Click to collapse
I was just pointing out to the person having issues with the flash tool to make sure they have all the drivers installed...
Solved!!
mjones73 said:
I was just pointing out to the person having issues with the flash tool to make sure they have all the drivers installed...
Click to expand...
Click to collapse
Update : Guys I figured out what was wrong with some help of XDABBEB (the dev of the custom 24a ROM) he actually helped me step by step... turns out I lost my recovery somehow SOOOOO I was stuck with fastboot. Had to push a new recovery via fastboot from there I had to fix a lovely driver issue (courtesy of windows) which in the end I couldn't get it to work so I went with KOUSH universal adb driver which is a LIFESAVER! From there had to adb push the bootstack zip and the ROM file itself installed via TWRP 2.7.0.0 and did a clean install...... As you can see it was a fun night/day for me.. But as of now I am running 24a rooted and with all of XDABBEB'S mods.. And it is beautiful. Lol I know you alot of people won't take the time to read this whole thing but just in case anyone has the same problem there you are!
mjones73 said:
I was just pointing out to the person having issues with the flash tool to make sure they have all the drivers installed...
Click to expand...
Click to collapse
Sorry thought you were the op
TTMBeats said:
Update : Guys I figured out what was wrong with some help of XDABBEB (the dev of the custom 24a ROM) he actually helped me step by step... turns out I lost my recovery somehow SOOOOO I was stuck with fastboot. Had to push a new recovery via fastboot from there I had to fix a lovely driver issue (courtesy of windows) which in the end I couldn't get it to work so I went with KOUSH universal adb driver which is a LIFESAVER! From there had to adb push the bootstack zip and the ROM file itself installed via TWRP 2.7.0.0 and did a clean install...... As you can see it was a fun night/day for me.. But as of now I am running 24a rooted and with all of XDABBEB'S mods.. And it is beautiful. Lol I know you alot of people won't take the time to read this whole thing but just in case anyone has the same problem there you are!
Click to expand...
Click to collapse
i think this is the problem i am having but i don't know how you did any of that to fix it!?!?!? I am going out of town in 2 days and i desperately need my phone. Got any help for me?
First thing first see if you can get into recovery
Sent from my VS980 4G using XDA Premium 4 mobile app
TTMBeats said:
Update : Guys I figured out what was wrong with some help of XDABBEB (the dev of the custom 24a ROM) he actually helped me step by step... turns out I lost my recovery somehow SOOOOO I was stuck with fastboot. Had to push a new recovery via fastboot from there I had to fix a lovely driver issue (courtesy of windows) which in the end I couldn't get it to work so I went with KOUSH universal adb driver which is a LIFESAVER! From there had to adb push the bootstack zip and the ROM file itself installed via TWRP 2.7.0.0 and did a clean install...... As you can see it was a fun night/day for me.. But as of now I am running 24a rooted and with all of XDABBEB'S mods.. And it is beautiful. Lol I know you alot of people won't take the time to read this whole thing but just in case anyone has the same problem there you are!
Click to expand...
Click to collapse
Can you please give us step by step instructions?
Earlier I have updated my phone to 24A. Then rooted and tried to install irobot25 to install the TWRP and ended with the fastboot mode on the phone. Currently the phone is just recognized as Android phone but not as LG VS980. I am in the same situation as you are earlier.
I really appreciate your help. My phone is in this state from the past 2 weeks and really getting frustated with it.
Download the koush USB driver Google search it first then let me know when that's done
Sent from my VS980 4G using XDA Premium 4 mobile app
TTMBeats said:
Update : Guys I figured out what was wrong with some help of XDABBEB (the dev of the custom 24a ROM) he actually helped me step by step... turns out I lost my recovery somehow SOOOOO I was stuck with fastboot. Had to push a new recovery via fastboot from there I had to fix a lovely driver issue (courtesy of windows) which in the end I couldn't get it to work so I went with KOUSH universal adb driver which is a LIFESAVER! From there had to adb push the bootstack zip and the ROM file itself installed via TWRP 2.7.0.0 and did a clean install...... As you can see it was a fun night/day for me.. But as of now I am running 24a rooted and with all of XDABBEB'S mods.. And it is beautiful. Lol I know you alot of people won't take the time to read this whole thing but just in case anyone has the same problem there you are!
Click to expand...
Click to collapse
I'm in the exact same position as you, if you could help me out with what you did the unbrick this thing that would be great. Thanks
Even KOUSH drivers don't work
Digging up this thread ...
I have a bricked G2.. Flashing a ROM via LGFLASHTOOL 2014 went bad at 50%.. Now all it does is Firmware Update Mode.
Before the G2 was recognized and accessible, but now even the KOUSH drivers don't recognize the phone.
I tried reinstalling, uninstalling, rebooting, etc but keep getting the error: "This device cannot start. (Code 10)"
Command prompt ADB commands don't work either because the phone just isn't recognized.
Where do I go from here please?
elwnvd said:
Digging up this thread ...
I have a bricked G2.. Flashing a ROM via LGFLASHTOOL 2014 went bad at 50%.. Now all it does is Firmware Update Mode.
Before the G2 was recognized and accessible, but now even the KOUSH drivers don't recognize the phone.
I tried reinstalling, uninstalling, rebooting, etc but keep getting the error: "This device cannot start. (Code 10)"
Command prompt ADB commands don't work either because the phone just isn't recognized.
Where do I go from here please?
Click to expand...
Click to collapse
Same. I have bricked a L70.
Related
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.
Hello folks,
During update from Revolution HD 3.4 to 3.5 something went wrong and process stopped before it got finished. Now I ended up in bootloop, even recovery is not working. I've tried to use RUU but failed on CID verification as I'm having the phone from 3 IE. Is any chance to bring it back to life or i just got very expensive paper weight ?
Or if anyone can provide RUU for 3 IE I'm willing to pay for it.
Bad day, bad day...
Thank you for any advice.
megahafo said:
Hello folks,
During update from Revolution HD 3.4 to 3.5 something went wrong and process stopped before it got finished. Now I ended up in bootloop, even recovery is not working. I've tried to use RUU but failed on CID verification as I'm having the phone from 3 IE. Is any chance to bring it back to life or i just got very expensive paper weight ?
Or if anyone can provide RUU for 3 IE I'm willing to pay for it.
Bad day, bad day...
Thank you for any advice.
Click to expand...
Click to collapse
What is happening when you enter recovery?
MacHackz said:
What is happening when you enter recovery?
Click to expand...
Click to collapse
I can see the recovery screen (clockworkmod) for about 0.1 second and it reboots again.
megahafo said:
I can see the recovery screen (clockworkmod) for about 0.1 second and it reboots again.
Click to expand...
Click to collapse
try reflashing it and wiping cache etc
MacHackz said:
try reflashing it and wiping cache etc
Click to expand...
Click to collapse
Thanks, for hint. Got recovery working again
What I have done.
1.) Unlocked, re-locked bootloader.. (i think this did the trick, full wipe ?)
2.) Wiped cache
3.) Re-flash clockworkmod
4.) Upload ROM using sideload.
Now the phone is back. I hope i will not break something again.
Hi, I am having the same issue with my phone as of right now. I tried re-locking bootloader and then unlocking again and also reflashing clockwork and I am still getting the bootloop and cannot access recovery (flashes for 0.1 secs and then disappears).
What exactly did you do to fix the issue?
tokenwoken said:
Hi, I am having the same issue with my phone as of right now. I tried re-locking bootloader and then unlocking again and also reflashing clockwork and I am still getting the bootloop and cannot access recovery (flashes for 0.1 secs and then disappears).
What exactly did you do to fix the issue?
Click to expand...
Click to collapse
The cue there if wiping the cache partition.
Riyal said:
The cue there if wiping the cache partition.
Click to expand...
Click to collapse
Hi Riyal,
I have fixed that issue with fastboot erase cache. Now, I am having a problem loading a ROM because it states in recovery that it "can't mount SD card"?
Figured it out, I just had to ADB push a stock rom and then re-wipe/re-flash
tokenwoken said:
Hi Riyal,
I have fixed that issue with fastboot erase cache. Now, I am having a problem loading a ROM because it states in recovery that it "can't mount SD card"?
Click to expand...
Click to collapse
I had the same problem, going to try to sideload this stock de-odexed rom (didn't work the first few times) and CHILL THE PHUCK out until AOKP.
scared me lol first HTC device, brand new, and I thought I broke it.
P.S I realized that REVOHD uses AROMA, that's why it wouldn't sideload.... Am I Rite?
Similar issue
tokenwoken said:
Figured it out, I just had to ADB push a stock rom and then re-wipe/re-flash
Click to expand...
Click to collapse
My HTC One device is actually suffering the same problem.
I bought my HTC One Sprint(Sim-Free Edition) in the US and got it to India.
But after I inserted my Indian Sim it said ''SIM LOCK ENABLED''.....I just got frustrated and
rooted the device and tried to install ''Android RevolutionHD (Odexed)'' Stock ROM with the help of TWRP.
But after I installed the stock rom, my device is just showing the HTC symbol and hanging there itself.
It Hangs there for around 6-7mins and reboots and the same happens again.
The only thing I can do is to get in to the bootloader and Power OFF the Device.
Any Help???? Please..... just having a costly paper weight since 2 weeks.
Please need help urgently....!!!
Hi
Greetings,
Did you flashed boot.IMG if no
Extract the boot.img from the Rom
Copy that file to abd/fastboot folder
Now connect you phone with pc with your phone booted in fastboot/bootloader,
Later flash boot.img by following command
"Fastboot flash boot boot.img"
Reboot and your done
If you do not know how to use abd search for it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
thanks but....
shrex said:
Hi
Greetings,
Did you flashed boot.IMG if no
Extract the boot.img from the Rom
Copy that file to abd/fastboot folder
Now connect you phone with pc with your phone booted in fastboot/bootloader,
Later flash boot.img by following command
"Fastboot flash boot boot.img"
Reboot and your done
If you do not know how to use abd search for it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
thanks for your advice but how do i extract boot.img when the phone is not even switching on to connect to the pc.
suhazgummadi said:
thanks for your advice but how do i extract boot.img when the phone is not even switching on to connect to the pc.
Click to expand...
Click to collapse
You have the zip file of ARHD in your pc extract the boot.img using winrar thats it and you have to put that file in abd/fastboot folder in pc
and everything what i said its to be done in pc
excpet putting phone in fastboot mode
suhazgummadi said:
My HTC One device is actually suffering the same problem.
I bought my HTC One Sprint(Sim-Free Edition) in the US and got it to India.
But after I inserted my Indian Sim it said ''SIM LOCK ENABLED''.....I just got frustrated and
rooted the device and tried to install ''Android RevolutionHD (Odexed)'' Stock ROM with the help of TWRP.
But after I installed the stock rom, my device is just showing the HTC symbol and hanging there itself.
It Hangs there for around 6-7mins and reboots and the same happens again.
The only thing I can do is to get in to the bootloader and Power OFF the Device.
Any Help???? Please..... just having a costly paper weight since 2 weeks.
Please need help urgently....!!!
Click to expand...
Click to collapse
The Sprint version is never going to work on any carrier other than Sprint. It's a CDMA device. The sim slot if for connecting to Sprint's LTE network, but requires a CDMA connection first and foremost to work at all.
Sent from my HTC One using xda premium
Thanks, this actually worked for me. I have HTC One TMO edition, i did a sdcard format and things went very bad from there and i was not able to flash anything and recovery kept rebooting.. after i tried this below, it worked like a charm..
megahafo said:
Thanks, for hint. Got recovery working again
What I have done.
1.) Unlocked, re-locked bootloader.. (i think this did the trick, full wipe ?)
2.) Wiped cache
3.) Re-flash clockworkmod
4.) Upload ROM using sideload.
Now the phone is back. I hope i will not break something again.
Click to expand...
Click to collapse
Quickest and easiest way to fix this issue is...
'fastboot erase cache'
'fastboot reboot recovery'
hnt20 said:
Thanks, this actually worked for me. I have HTC One TMO edition, i did a sdcard format and things went very bad from there and i was not able to flash anything and recovery kept rebooting.. after i tried this below, it worked like a charm..
Click to expand...
Click to collapse
I'm stuck on the same boat :\
I was able to finally boot into CWM recovery but I'm getting write errors all over the place.
I used the AIO Kit to re-lock the bootloader and unlock it - Reflashed CWM - Tried to sideload ARHD 10.0 but the DOS prompt errors out saying that it cannot find my device.
Little help?
HumorousMaximus said:
I'm stuck on the same boat :\
I was able to finally boot into CWM recovery but I'm getting write errors all over the place.
I used the AIO Kit to re-lock the bootloader and unlock it - Reflashed CWM - Tried to sideload ARHD 10.0 but the DOS prompt errors out saying that it cannot find my device.
Little help?
Click to expand...
Click to collapse
i was going through the same thing yesterday and i thought i had bricked my phone. what i did that finally worked, was unplugging the usb, restarting the computer, reinstalling htc drivers, then restarting the computer, then using a different usb port. i was finally able to sideload ARHD whereas before i could do fastboot commands, but it wasn't responding to the sideload, and wasn't able to mount the sdcard, so i thought i was screwed. :good:
mky4b11 said:
i was going through the same thing yesterday and i thought i had bricked my phone. what i did that finally worked, was unplugging the usb, restarting the computer, reinstalling htc drivers, then restarting the computer, then using a different usb port. i was finally able to sideload ARHD whereas before i could do fastboot commands, but it wasn't responding to the sideload, and wasn't able to mount the sdcard, so i thought i was screwed. :good:
Click to expand...
Click to collapse
Thanks for the tip, I was able to get back into AROMA but the original issue that got me to this point came up again. Aroma installer runs and during the install it kicks itself out and sends me back to recovery, so the installer doesn't complete. It gets to about 30% and craps out just after it writes system data and starts to install the .apk's. Screen goes black and it reboots itself and sends me to recovery.
thoughts?
Hi all.
I have CWM Touch installed, but I can't run ADB Sideload to flash a ROM. I just keep getting an error that the device can't be found. I have no OS installed, so my phone won't boot up. I can't access the phone's memory as that doesn't work with the One. I also can't flash a RUU to return to factory settings as I have S-ON and am on HBOOT 1.54.Is there anything I can do to fix this and get my phone back working?
Many thanks.
alanzo27 said:
Hi all.
I have CWM Touch installed, but I can't run ADB Sideload to flash a ROM. I just keep getting an error that the device can't be found. I have no OS installed, so my phone won't boot up. I can't access the phone's memory as that doesn't work with the One. I also can't flash a RUU to return to factory settings as I have S-ON and am on HBOOT 1.54.Is there anything I can do to fix this and get my phone back working?
Many thanks.
Click to expand...
Click to collapse
First try to reinstall you Drives for ADB and HTC so you know it's not a Driver issue. If that doesn't work try using a different PC and see if you still get the same issues.
And also try using HTC One AIO to flash TWRP or something to see if you can Sideload a rom then. Because AIO toolkit uses the fastboot menu to flash Recovery images.
If you can flash a different Recovery then try to flash a rom and see if that works.
If not let me know what the results are
gazlufc said:
First try to reinstall you Drives for ADB and HTC so you know it's not a Driver issue. If that doesn't work try using a different PC and see if you still get the same issues.
And also try using HTC One AIO to flash TWRP or something to see if you can Sideload a rom then. Because AIO toolkit uses the fastboot menu to flash Recovery images.
If you can flash a different Recovery then try to flash a rom and see if that works.
If not let me know what the results are
Click to expand...
Click to collapse
Got it! Thank you. I reinstalled the drivers. Weird though because ADB was working fine before. The drivers must have corrupted or maybe it's a Windows 8 issue. Sideloading the ROM now, will let you know if it is a success.
alanzo27 said:
Got it! Thank you. I reinstalled the drivers. Weird though because ADB was working fine before. The drivers must have corrupted or maybe it's a Windows 8 issue. Sideloading the ROM now, will let you know if it is a success.
Click to expand...
Click to collapse
No problem man, Glad to hear you got it working again
Ok so how do I start this? Well I got an htc one for christmas and I wanted to root it. Everything was fine until I decided to flash a custom kit kat rom. The rom was stuck in a boot loop so I went back to twrp and flashed my recovery. I thought I fixed everything but then I stopped getting phone service. It kept saying looking for service. I thought it was a bad recovery so I downloaded cm from rom manager. While it was downloading, the phone just randomly rebooted. It kept doing this and still is.so then, being the idiot I am, flashed clockwork recovery to see if it would change anything. I tried downloading cm from rom manager again and finally finished downloading before it started rebooting again. I went into clockwork recovery and flashed cm and now it keeps rebooting and I have no phone service. I have no idea what to do. By switching from twrp to clockwork, I lost my recovery. Im totally screwed. I need help please!What do I do!!!!????
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
BD619 said:
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
Click to expand...
Click to collapse
Thanks a bunch! I'll check this out and see if it works
Rom Update Utility
It will get you back to 100% stock
If you need help PM me I'll be happy to help
roflcopter1212 said:
Ok so how do I start this? Well I got an htc one for christmas and I wanted to root it. Everything was fine until I decided to flash a custom kit kat rom. The rom was stuck in a boot loop so I went back to twrp and flashed my recovery. I thought I fixed everything but then I stopped getting phone service. It kept saying looking for service. I thought it was a bad recovery so I downloaded cm from rom manager. While it was downloading, the phone just randomly rebooted. It kept doing this and still is.so then, being the idiot I am, flashed clockwork recovery to see if it would change anything. I tried downloading cm from rom manager again and finally finished downloading before it started rebooting again. I went into clockwork recovery and flashed cm and now it keeps rebooting and I have no phone service. I have no idea what to do. By switching from twrp to clockwork, I lost my recovery. Im totally screwed. I need help please!What do I do!!!!????
Click to expand...
Click to collapse
Try this tutorial from BD619 http://forum.xda-developers.com/showthread.php?t=2503646&highlight=tutorial
roflcopter1212 said:
Thanks a bunch! I'll check this out and see if it works
Click to expand...
Click to collapse
I tried it with your tut. but when I try to reboot into RUU it says fastboot isnt a valid win. 32bit application. What now?
BD619 said:
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
Click to expand...
Click to collapse
I put in the failed 90 hboot.... command and it says its an invalid command
roflcopter1212 said:
I put in the failed 90 hboot.... command and it says its an invalid command
Click to expand...
Click to collapse
You *have* to get your Android SDK setup properly. All the commands your run end up on "command not found" of "invalid exe" and that suggests a few things:
First -- make *sure* you install the correct SDK for your computer. If you can't find them, let us know what your computer is (32-bit, 64-bit, windows, etc.). Further, it seem possible:
1) You did not yet install the Android SDK (or ADT bundle if that's what you grab);
2) If just the SDK, you did not run the 'android' app and let it update all the platform-tools apps (that's adb, fastboot, etc);
3) You did not open a command shell in the <sdk>/platform-tools directory, or you did not add your <sdk>/tools and <sdk>/platform-tools to your path. Further:
Finally -- make sure you have your USB drivers loaded if you're using Windows.
Don't run 300 miles per hour trying to fix things -- it'll kill your phone. Relax, take a breath and get the SDK setup. That will solve most of your problems (if not all). At least that's what it looks like from afar.
Before you run any of the RUU, you should be able to type either of:
adb devices
or
fastboot devices
The latter works only when you are at the bootloader with your USB plugged in and you selected 'fastboot'; the former runs only when your phone is booted fully.
The Sprint 3.05.651.5 RUU is available here: http://www.htc.com/us/support/htc-one-sprint/news/ (Install at your own risk!)
Hello
Currently my phone is useless, I am blaming myself but somewhat of the ROM I used before this all happened.
For starters, my bootloader is unlocked and s-on. I successfully installed TWRP and rooted using SuperSU. I wanted to try out the custom ROM ViperOne. It installed perfectly fine without any errors. But when I rebooted the phone I am greeted with the lockscreen with no service (x by the bars) and when I go to unlock the phone it goes to a white screen with the HTC logo in the center. It will continue to stay at this screen till it reboots again and does the same thing.
At this point I am frustrated and followed this guide http://forum.xda-developers.com/showthread.php?t=2503646 to revert back to Stock. I was able to do every step correctly besides the flashing of the radio and pushing the Stock_Rom on the phone.
I was able to install the stock rom by putting it on my internal storage and flashing it that way, but still no luck with the radio. But now the Stock_Rom is doing the exact same thing as the Viper, Whitescreen with HTC. Plus it is constantly saying "Unfortunately Phone has stopped" making it unusable.
If someone could please help me out or direct me to another tut to follow I will appreciate it very much. Because at this point I am to believe that I bricked my device and I am unaware if I am able for an upgrade anytime soon.
Thank you for you time.
A little update.
I am not starting to think this whole problem has to do with my radio, simply I do not have 1. How do I get this working again?
Another update.
I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=2250904 (Very helpful btw :good
But still no luck, it froze me at the black screen with HTC and no loading bar.
I just want to be able to use my phone again :crying:
Everything you need is in the first link you posted.
BD619 said:
Everything you need is in the first link you posted.
Click to expand...
Click to collapse
Thank you for your response.
Like I sad, I tried that link already but with no luck. I could be doing something wrong, but I am following word for word.
kavinsky_ep said:
Thank you for your response.
Like I sad, I tried that link already but with no luck. I could be doing something wrong, but I am following word for word.
Click to expand...
Click to collapse
Latest radio can be found HERE
BD619 said:
Latest radio can be found HERE
Click to expand...
Click to collapse
I've downloaded 1.00.20.1108 and I am trying to flash it using fastboot flash zip radio.zip (I renamed it to type it in easier).
But every time I press enter it does signature checking... then it says FAILD (remote: 12 signature verify fail)
Any ideas?
kavinsky_ep said:
I've downloaded 1.00.20.1108 and I am trying to flash it using fastboot flash zip radio.zip (I renamed it to type it in easier).
But every time I press enter it does signature checking... then it says FAILD (remote: 12 signature verify fail)
Any ideas?
Click to expand...
Click to collapse
Flash in recovery like the instructions say lol
BD619 said:
Flash in recovery like the instructions say lol
Click to expand...
Click to collapse
Ok, thank you again. I will try this. I hope to god it works
Sigh. Another problem
After performing the wipe with TWRP and then i type in the cmd adb push nameofrom.zip /sdcard/ but I get the following error in cmd.
adb server is out of date. killing...
* daemon started successfully *
I am confused by this because my drivers are up to date, unless this is a different problem. Any ideas?
kavinsky_ep said:
Sigh. Another problem
After performing the wipe with TWRP and then i type in the cmd adb push nameofrom.zip /sdcard/ but I get the following error in cmd.
adb server is out of date. killing...
* daemon started successfully *
I am confused by this because my drivers are up to date, unless this is a different problem. Any ideas?
Click to expand...
Click to collapse
It's normal for it to say that.
Do you get your serial number returned when you type
adb devices
BD619 said:
It's normal for it to say that.
Do you get your serial number returned when you type
adb devices
Click to expand...
Click to collapse
Hey! I fixed it, I was able to quickly put the radio.zip into my internal storage before the phone could freak out. Went into TWRP and flashed that *****! IT WORKS!
No more custom ROMS for me, I'll just stick to rooting and keeping stock rom.
I would like to thank you for helping me throughout this, I really appreciate this. :good:
btw, if I were unable to do it the way I did, how would I fix it to work with the adb push command?
kavinsky_ep said:
Hey! I fixed it, I was able to quickly put the radio.zip into my internal storage before the phone could freak out. Went into TWRP and flashed that *****! IT WORKS!
No more custom ROMS for me, I'll just stick to rooting and keeping stock rom.
I would like to thank you for helping me throughout this, I really appreciate this. :good:
btw, if I were unable to do it the way I did, how would I fix it to work with the adb push command?
Click to expand...
Click to collapse
Depends what is causing the adb to be wonky most likely it's a driver issue.
Drivers install while booted to OS,Recovery,and fastboot.
BTW when you were doing the adb push romname.zip /sdcard/ were you in recovery or OS?
You are very welcome btw
BD619 said:
Depends what is causing the adb to be wonky most likely it's a driver issue.
Drivers install while booted to OS,Recovery,and fastboot.
BTW when you were doing the adb push romname.zip /sdcard/ were you in recovery or OS?
You are very welcome btw
Click to expand...
Click to collapse
I was in my recovery, TWRP. and using my computer with the CMD. Or by OS do you mean my phone OS. Because I was unable to use my Phone due to the radio not being there.
kavinsky_ep said:
I was in my recovery, TWRP. and using my computer with the CMD. Or by OS do you mean my phone OS. Because I was unable to use my Phone due to the radio not being there.
Click to expand...
Click to collapse
Most likely the drivers were not installed properly while booted to twrp...there are instructions in my guide that will show you how to install them properly.
I was wondering if the phone was booted to OS.
Get yourself S-OFF, and many flashing woes disappear. I have soft-bricked my phone with a Viper myself. You have to be sure you install the correct carrier version and think twice about installing kernels in ViperHub (or whatever they call it). If you install a GSM anything to your Sprint phone, your radio will go away. An RUU will fix this though. Windows 8 does not play well with ADB on our phones, either.
Sent from my One using Tapatalk
I'm having the SAME exact problems as you. Went to flash Viper rom and just get stuck on the white screen with the HTC logo. Glad I'm not the only one!
Hopefully I'll be able to fix mine as well!