Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
ab1009 said:
Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
Click to expand...
Click to collapse
Do you want to get back to stock Sense? Download and run this RUU while in fastboot
https://docs.google.com/file/d/0B32gqnbh2ZecSHM2VXJoY2tFUU0/edit?usp=sharing
Or you can sideload a ROM .zip from CWM and install it.
Thank you duffman for reply, I downloaded the RUU and excute it but I got error 155, I tried other RUU also I got the same error, how to avoid this error?
br
ab1009 said:
Thank you duffman for reply, I downloaded the RUU and excute it but I got error 155, I tried other RUU also I got the same error, how to avoid this error?
br
Click to expand...
Click to collapse
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
ibsk8 said:
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
Click to expand...
Click to collapse
Exactly. Download the DNA toolkit. http://forum.xda-developers.com/showthread.php?t=2219175
Use it to flash the 3.06 hboot
After that, try the 3.06 RUU again.
ibsk8 said:
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
Click to expand...
Click to collapse
duffman452001 said:
Exactly. Download the DNA toolkit. http://forum.xda-developers.com/showthread.php?t=2219175
Use it to flash the 3.06 hboot
After that, try the 3.06 RUU again.
Click to expand...
Click to collapse
thank you ibsk8 and duffman,
I treid what you wrote but I got this error: FAILED (remote: 99 unknown fail) what is my mistake??
br
ab1009 said:
thank you ibsk8 and duffman,
I treid what you wrote but I got this error: FAILED (remote: 99 unknown fail) what is my mistake??
br
Click to expand...
Click to collapse
Hmmm I just realized you're s-on. When you say you tried the other RUU, did you try the alternate 3.06 RUU or the 1.15 RUU?
1.15 RUU: https://docs.google.com/file/d/0B32gqnbh2ZecSHM2VXJoY2tFUU0/edit?usp=sharing
That really should work since you're on the 1.15 hboot and radio. If not, can you send a screenshot of the error?
Hi duffman,
I tried to Flash the 1.15 RUU but I got 155 error. please see my pics.
br
looks like you may have been trying to s-off? which did not complete.
rerun s-off and try different usb port
Thank You DJ_MiX for reply,
I used Moonshine to S-Off, I puted the Droid DNA in "Fastboot USB" mode, I did all as in instruction, I got Error: run distiller again and READ.
I used Rumrunner and I see now: "no ADB connection to device, Debugging on?" but I cannot boot the device in normal android and choose "USB debugging". I can boot to HBoot/Fastboot or Recovery Mode.
can you help me to s-off this phone (can I use RUU with s-off phone??)
br
Error 155 is due to attempting to RUU while unlocked. To apply an RUU you must be locked. In order to lock your device connect to your pc and enter fastboot usb mode. use the command "fastboot oem lock". Once you are locked you can RUU using the current version as reported by the RUU utility or a higher version.
After this is successful you should obtain s-off, as this will save you in the future from the current issue you created for yourself. Alternatively you can apply all the OTAs and fully update to kit-kat firmware.
Note: once you are locked again you will not be able to boot (no change there) and you will not be able to enter recovery due to the non-factory recovery.
Thank you all espcially TheRealDeadApe,
My phone is now alive again. I have flashed it with RUU 1.15 but with RUU 3.06 I get ERROR (158) IMAGE ERROR. now I have Android 4.1.1 can I upgrade to 4.4.2 if I live outside USA?
br
Bump. I'm in the exact same situation.
ab1009 said:
Thank you all espcially TheRealDeadApe,
My phone is now alive again. I have flashed it with RUU 1.15 but with RUU 3.06 I get ERROR (158) IMAGE ERROR. now I have Android 4.1.1 can I upgrade to 4.4.2 if I live outside USA?
br
Click to expand...
Click to collapse
As for the OTAs you can apply them anywhere you are if you download the zip files and flash them using the stock recovery. Search this forum.
Personally I would s-off. I used moonshine on the 1.15 firmware when I did it. Then you can flash RUUs without restrictions so you can update easier or update the firmware only and flash a custom rom.
For Flashing Custom ROM to Dead DNA
ab1009 said:
Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
Click to expand...
Click to collapse
This is for future reference since this has been solved. This method is from my own experiences and will work if you absolutely need functionality as soon as humanly possible.
What you can do is plug your phone while it is in recovery and select install zip from sideload.
find a custom rom you want with the corresponding GAPPS if needed,
put the rom.zip and your gapps.zip (if applicable) at the root directory of your adb. (rightclick adb on desktop click go to file location)
Rename your rom.zip to literally just rom.zip (makes it a lot easier later) and the gapps.zip to gapps.zip
check to see if your pc sees your device after selecting install zip from sideload by running "adb devices". you should see a long id number with SIDELOAD to the right.
If your device shows up, then run "adb sideload rom.zip", once finished do not hit reboot system until you flash gapps if needed.
for gapps run 'adb sideload gapps.zip" then reboot your phone. Your phone should now have functionality restored. :good:
Related
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
drknrgy said:
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
Click to expand...
Click to collapse
you can pull the rom.zip from the ruu, and run that in hboot.. or just unlock the bootloader again
drknrgy said:
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
Click to expand...
Click to collapse
Yes, you can run the RUU via pc in fastboot. That's how I ran it . Just as long as it says fastbootusb , it will work.
I was stuck in Hboot as well.. so not sure how you avoid it. Easy enough to run the RUU out of fastboot though.
andybones said:
you can pull the rom.zip from the ruu, and run that in hboot.. or just unlock the bootloader again
Click to expand...
Click to collapse
Can I run the RUU.exe directly on pc while in fastboot usb?
"you can pull the rom.zip from the ruu, and run that in hboot." not sure what that means if you run RUU.exe on pc How could I "pull the rom.zip from the ruu" if I cant run recovery??
Never ran RUU
Ok Just to make sure then.. Am I running the correct RUU? Will this further effect me if trying to run the wrong RUU file ? I guess my question is, to be more specific, does my listed RADIO in hboot need the correct RUU file ??
drknrgy said:
Ok Just to make sure then.. Am I running the correct RUU? Will this further effect me if trying to run the wrong RUU file ? I guess my question is, to be more specific, does my listed RADIO in hboot need the correct RUU file ??
Click to expand...
Click to collapse
It won't let you run the wrong RUU.. if you havent taken the OTA yet, the correct RUU is 1.06.xxxxx
Yes, you run the exe on the PC while in fastboot.
mjh68 said:
It won't let you run the wrong RUU.. if you havent taken the OTA yet, the correct RUU is 1.06.xxxxx
Yes, you run the exe on the PC while in fastboot.
Click to expand...
Click to collapse
Is there a way to determine the correct RUU? This one>>>>
WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_ 8k_1.12_9k_1.83_V_APT_release_2215<<<<
FAILED
"ERROR [140] BOOTLOADER VERSION ERROR"
Would the latest > new RUU for 2.01.605.11 < WorK?
drknrgy said:
Is there a way to determine the correct RUU? This one>>>>
WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_ 8k_1.12_9k_1.83_V_APT_release_2215<<<<
FAILED
"ERROR [140] BOOTLOADER VERSION ERROR"
Would the latest > new RUU for 2.01.605.11 < WorK?
Click to expand...
Click to collapse
Did you update with the OTA or have your main ver updated ? Sounds like you had a partial update with the bootloader being updated to 2.11 maybe.
Try the new RUU see if it will run it.
mjh68 said:
Did you update with the OTA or have your main ver updated ? Sounds like you had a partial update with the bootloader being updated to 2.11 maybe.
Try the new RUU see if it will run it.
Click to expand...
Click to collapse
I do not have the new OTA. I was root/unlocked. I tried doing wipe from ra and then run CleanRom GBE 1.6OTA zip from sd. Then I think I ran fastboot boot.img...
I have lost track of my steps at this point but the bootloader still states HBOOT-2.10.0000 on the white security warning screen w/3 droids at the bottom
BTW...Is there a direct link for new RUU available? DpBox??
drknrgy said:
I do not have the new OTA. I was root/unlocked. I tried doing wipe from ra and then run CleanRom GBE 1.6OTA zip from sd. Then I think I ran fastboot boot.img...
I have lost track of my steps at this point but the bootloader still states HBOOT-2.10.0000 on the white security warning screen w/3 droids at the bottom
BTW...Is there a direct link for new RUU available? DpBox??
Click to expand...
Click to collapse
It is in the developement forum.. Sticky thread for the Vigor rom collection. It was on the last page.. might have been bumped back a page or so.
Hmm , not sure why it is giving you that error if you still have hboot 2.10 , let me check and make sure that first RUU was the right one. Yes, you quoted the same RUU I used when I did the process.
mjh68 said:
It is in the developement forum.. Sticky thread for the Vigor rom collection. It was on the last page.. might have been bumped back a page or so.
Hmm , not sure why it is giving you that error if you still have hboot 2.10 , let me check and make sure that first RUU was the right one. Yes, you quoted the same RUU I used when I did the process.
Click to expand...
Click to collapse
Thanks for the D/L on the latest RUU.. almost finished. If I run this one via .exe and still get a failure re: bootloader what are my other options? I have other options don't I? Can I use a cmd to "push"? Any ideas? Thanks for all the help!
before running the RUU...
current image Version:
2.01.605.11
(same as latest RUU) crossing fingers now..
drknrgy said:
Thanks for the D/L on the latest RUU.. almost finished. If I run this one via .exe and still get a failure re: bootloader what are my other options? I have other options don't I? Can I use a cmd to "push"? Any ideas? Thanks for all the help!
before running the RUU...
current image Version:
2.01.605.11
(same as latest RUU) crossing fingers now..
Click to expand...
Click to collapse
Looks like somehow your mainver did get updated so the newest RUU should work. If this one fails I am out of ideas, I am fairly new to this myself so learning as I go. RUU's are similar to SBF's from motorla to return phone to stock out of the box condition. The way they work I don't think you can force push it to restore as far as I know.
This one worked perfectly and included the OTA . I am however complete stock now, lost root. My mind is a bit warped from all this confusion. How do I get root back again..? Flash amon ra ? go into Developer and install su. ?
drknrgy said:
This one worked perfectly and included the OTA . I am however complete stock now, lost root. My mind is a bit warped from all this confusion. How do I get root back again..? Flash amon ra ? go into Developer and install su. ?
Click to expand...
Click to collapse
Yes, just go into amon ra install su and superuser , then reboot. Might have to still download superuser from the market and install ,but then you should be good to go.
mjh68 said:
Yes, just go into amon ra install su and superuser , then reboot. Might have to still download superuser from the market and install ,but then you should be good to go.
Click to expand...
Click to collapse
Thanks for the great advice. I am back up and running w/OTA and root. Just need to nan-restore now. Bring on ICS!
i have read this post and my problem is somewhat similar. i can't seem to get my computer to read my phone. my sd port isn't coming up. i have my phone connected and using hasoon2000 all in one tool kit. my hboot version is 20225.0000 and radio is 1.22.10.0421r/1.22.10.042r. how can i get my phone off this white screen and also how can i get my phone and computer to read each other??? im also relocked i tried to unlock it using hasoon 2000 all in one tool kit but can't get it to kick in. and when i go into the cmd command prompt it tells me device error. the phone isn't reading.
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
demayod said:
Hello Everyone,
I know this probably isn't the best place to post this question. I'm limited to not posting in the dev section.
I'm going to post my question and hope someone can help anyway.
I have an HTC One (M7) that seemed to have reception problems. I always thought I just needed to flash a new radio. So I went ahead and S-OFF'd my phone as well as Super CID. I then flashed a new radio & my reception problem seemed to go away. (or so i thought).
I then went ahead and turned my AT&T One into a Google Edition.
I have noticed that my reception problems never really went away. (When I am at home I have full bars. The conversation starts out fine, but about 10 seconds in, the person at the other end can no longer hear me.)
I now suspect this is a problem with the antenna & I have to get my phone back to stock so that I can hopefully switch out for a new one.
I'm just wondering which step I should do first. S-On again (I used REVONE to S-OFF) , CID back to AT&T, or switch back from the GE rom?
Any help would be appreciated.
Thank you,
Dan
Click to expand...
Click to collapse
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Thanks so much for the response! I appreciate the help. Very informative. I'll read through & hopefully I report back with good news tomorrow morning. :cyclops:
Yay! All done!
Thanks so much for the guide! and the help!
-Dan
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
demayod said:
I guess I spoke too soon. After completion, I realized that TWRP was still installed, so I flashed the stock recovery. At this point everything seemed fine, but I noticed that the supersu icon was still there. I also noticed that wifi will no longer turn on. Clearly I've done something wrong.
The first time I had used a nandroid backup to restore to stock, then lock, s-on, remove tampered. That is when I realized TWRP was still installed and SuperSu was still there.
This is when I downloaded an RUU that matched my phone, but it errors saying something like "wrong boot version" (I'm not near my home pc to look)
I tried the process again & somehow SuperSu lost binaries. So I unlocked my bootloader again through HTCDev.com This gave me working SuperSu again. And this is where I am stuck.
I wonder if the GE rom changed something so that this process wont work?
Click to expand...
Click to collapse
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
clsA said:
when you run the RUU did you use the exe or Rom.zip /?
I use the rom.zip and flash in fastboot...
Click to expand...
Click to collapse
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
demayod said:
I used the ruu. I didn't realize you can access a Rom.zip. how can I try that? Thanks!
Click to expand...
Click to collapse
This is the instructions posted by Scotty85
I'm just re-posting it for you
http://androidforums.com/t-one-all-things-root/723061-t-ruu-1-26-502-12-a.html#post5864243
Click to expand...
Click to collapse
here is how you extract rom.zip:
Quote:
the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
here are some directions to flash "rom.zip"
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
clsA said:
This is the instructions posted by Scotty85
I'm just re-posting it for you
Click to expand...
Click to collapse
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
demayod said:
Thank you for the help, but still no good. I end up with FAILED (remote: 43 main version check fail) after I try to flash the zip.
Click to expand...
Click to collapse
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
My mid is PN0712000. I think that was always my mid. Don't recall changing it.
My cid is currently CW__001
I've tried: RUU_M7_UL_JB_50_Cingular_1.26.502.12.exe
also tried: RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2.exe
I'm currently S-On (could that be an issue?)
I'm unlocked.
clsA said:
change your CID back to 11111111 and try again
Did you change you MID ?
What is the name of the RUU your using ?
Click to expand...
Click to collapse
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Yep that should do it
Sent from my HTC One using Tapatalk 4
It did! I'm completely back to stock. I decided to update to the latest RUU that AT&T has released. Just to avoid AT&T wanting me to update to see if it fixes the problem. I know for a fact that it wouldn't fix the problem anyway.
Oddly, my phone told me I was up to date while on the .12 RUU even though I knew the .15 RUU exists. I downloaded the RUU for .15 and it ran fine once I went back to stock after running the .12 rom.zip.
In summary, you saved me from a huge headache! Thanks so much for all the help & kindness.
demayod said:
It worked once I set CID to 11111111 !!
So now I just have to change CID back, reverse S-Off again and change the unlocked and tampered flags?
Click to expand...
Click to collapse
How did you change our CID if you were S-On?
clsA said:
If I were returning my phone to Stock, this is the process I would use
Change CID to Stock fastboot oem writecid CWS__001
Run the latest RUU for my phone
then use Revone to lock the bootloader and s-on
I think that's the correct order .. if anyone knows different please chime in
Here's a definitive Guide
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
larrydadz said:
Hi guys this might be the wrong platform for this question ...but can anyone pls help me with the stock cidnum for sprint htc one M8..thanks
Click to expand...
Click to collapse
Comments: Sprint
modelid:
cid: SPCS_001
Situation:
TWRP works. TWRP reports no OS and phone will not boot. Looking to reload/recover this phone. Everything I've tried has failed. Is there a step by step easy way out of this? All help GREATLY Appreciated!!
Some more info would be helpful. Are you S-on or S-off? What is your Hboot version? What ROM are you trying to install? What version of TWRP do you have installed?
Magnum_Enforcer said:
Some more info would be helpful. Are you S-on or S-off? What is your Hboot version? What ROM are you trying to install? What version of TWRP do you have installed?
Click to expand...
Click to collapse
S- ON
Hboot 1.19.00
Trying to install any ROM that might work
TRWP Version 2.3.1.0
Thank you for your help
If I were you I'd run the RUU for the Android 4.3 update. Hit the top link in my sig and read the RUU section. Then download the RUU for Android 4.3, which can be found at the bottom of the first post of my bootloader guide. Afterwards, reinstall TWRP with the latest version. The version you have is very outdated, as is your bootloader version & firmware. You can download the latest version of TWRP from the link below.
http://techerrata.com/file/twrp2/jewel/openrecovery-twrp-2.8.4.0-jewel.img
I tried the RUU 4.3 and got the following message:
Error [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Sxottie said:
I tried the RUU 4.3 and got the following message:
Error [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse
Relock your bootloader and try again, being s-on your bootloader needs to be locked to ruu.
Fastboot oem lock I believe it is
gstanke said:
Relock your bootloader and try again, being s-on your bootloader needs to be locked to ruu.
Fastboot oem lock I believe it is
Click to expand...
Click to collapse
That was the piece of the puzzle I was missing. After downloading the Android-SDK to run ADB I'm all set now. The RUU worked flawlessly!!! Thank you everyone for your help!!!