I am S-ON and was on the JB OTA and was going to relock and run the RUU and get back to stock and take the latest update. I know i should have been S-OFF but was uncomfortable. OK now I am stuck on the white bootloader screen and I cant get into recovery or restart or even power down the phone just restarts. All i did was relocked and now im stuck like this. What do I do next? Run the RUU? I downloaded the RUU 3.15.651.16 - HBOOT 2.09 zip off the DirtyRacun site but it keeps telling me windowns cannot open the folder to let me run it as administrator. Any help would be much appreciated I have done this before and didnt have this problem.
xbmoyx said:
I am S-ON and was on the JB OTA and was going to relock and run the RUU and get back to stock and take the latest update. I know i should have been S-OFF but was uncomfortable. OK now I am stuck on the white bootloader screen and I cant get into recovery or restart or even power down the phone just restarts. All i did was relocked and now im stuck like this. What do I do next? Run the RUU? I downloaded the RUU 3.15.651.16 - HBOOT 2.09 zip off the DirtyRacun site but it keeps telling me windowns cannot open the folder to let me run it as administrator. Any help would be much appreciated I have done this before and didnt have this problem.
Click to expand...
Click to collapse
I am currently downloading the 3.15 RUU and am watching QBKing77's video on unrooting. He runs the RUU with the phone turned on. I cannot turn my phone on can I run this RUU with the phone in bootloader/Fastboot USB?
Steps 6, 7, 8, and 9 on the unlimited Io website have you relock and RUU from fastboot. You can stop there if you don't feel confident going for full s-off. Their Dirty racoon zip for windows has adb and fastboot in it. Just put the RUU.zip in there and run the commands from that directory.
Or wait for someone who knows more than me and be completely sure.
tilltheend714 said:
Steps 6, 7, 8, and 9 on the unlimited Io website have you relock and RUU from fastboot. You can stop there if you don't feel confident going for full s-off. Their Dirty racoon zip for windows has adb and fastboot in it. Just put the RUU.zip in there and run the commands from that directory.
Or wait for someone who knows more than me and be completely sure.
Click to expand...
Click to collapse
OK so I am currently downloading the RUU_PLUS_ROOT.zip from BigDaddy619's sig. Do I open a command prompt in the location of the download and type...
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU.zip
???? Sorry kinda noob at this and havent had this problem before. I am not trying to S-OFF just get back to Jellybean stock to take the latest OTA.
I'm not sure what that zip contains so I can't help with that.
On your first post you said you downloaded the RUU from the dirty racun site. It should be called "RUU.zip". That can be flashed through fastboot with those commands. Do you still have that file?
Edit: And steps 1-9 of the S-off procedure are to get you locked and RUU so you can be completely stock for the procedure. So you can stop there if you don't want to attempt s-off.
tilltheend714 said:
I'm not sure what that zip contains so I can't help with that.
On your first post you said you downloaded the RUU from the dirty racun site. It should be called "RUU.zip". That can be flashed through fastboot with those commands. Do you still have that file?
Edit: And steps 1-9 of the S-off procedure are to get you locked and RUU so you can be completely stock for the procedure. So you can stop there if you don't want to attempt s-off.
Click to expand...
Click to collapse
Yes I still have it on my desktop. It wont let me open it or extract it its a Zip file.
Ok. Leave it as a zip file, confirm that the md5 matches, and put it in your adb, fastboot directory. Since you said you relocked, I think you know where that is. Make sure you're locked, then run those commands one by one. And pay special attention to step 9:
"If you get the following after you run RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" then you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Especially this part
"you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
tilltheend714 said:
Ok. Leave it as a zip file, confirm that the md5 matches, and put it in your adb, fastboot directory. Since you said you relocked, I think you know where that is. Make sure you're locked, then run those commands one by one. And pay special attention to step 9:
"If you get the following after you run RUU: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" then you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Especially this part
"you need to rerun the fastboot flash zip RUU.zip command again. Press the up arrow and enter."
Click to expand...
Click to collapse
Got it! Thanks for all your help man.
Sent from my EVO using xda premium
No problem.
Are you back up and running?
tilltheend714 said:
No problem.
Are you back up and running?
Click to expand...
Click to collapse
Yup! I'll stay unrooted until the new update for Viper rolls out, hopefully soon!
Sent from my EVO using xda premium
Can't wait for that update.
If you ever want to s-off and have questions send a pm. It's not as scary as it sounds.
tilltheend714 said:
Can't wait for that update.
If you ever want to s-off and have questions send a pm. It's not as scary as it sounds.
Click to expand...
Click to collapse
It just sucks that the only computer I have is a 64bit windows laptop. All that ubuntu talk confuses the hell outta me. I appreciate it though man ill keep that in mind if I ever want to s-off. :thumbup:
Sent from my EVO using xda premium
I'm still getting data disconnected even on the latest OTA man I was hoping it got fixed. Having to cycle airplane mode to get data to turn back on
I only have 64bit windows. I just used a live disc. Easy as downloading an iso from ubuntus website and burning it to a disc. 10 minutes to get familiar with ubuntu and download the files, and a couple fastboot commands. You were pretty much done with the procedure today . Then just eject the disc and store it for next time you need ubuntu.
Did you try updating prl and profile?
Nope but just did and am on a new PRL. Hopefully this helps.
Sent from my EVO using xda premium
Doesn't matter that the system is 64 bit, just download a 32 bit iso of Ubuntu. It's really not as hard as it seems. I would say it's actually more reliable on Ubuntu then windows
om4 said:
Doesn't matter that the system is 64 bit, just download a 32 bit iso of Ubuntu. It's really not as hard as it seems. I would say it's actually more reliable on Ubuntu then windows
Click to expand...
Click to collapse
Well seeing how long it takes for an update on this phone I may not need to S-OFF. I just flashed the latest OTA so I'm 100% up to date. As long as the S-ON support continues regarding ROMs I should be good. Maybe the next phone ill look into getting S-OFF out the gate.
Sent from my EVO using xda premium
Well its getting to be more of a hassle with each update. The first update disabled flashing kernels and radios, the next update blocked you from writing to the system, this one has an update to the touch panel which breaks more then a few roms. Add to that the hassle of having to flash stock rom/recovery to update firmware or flashing a ruu which can cause more problems then it solves.
om4 said:
Well its getting to be more of a hassle with each update. The first update disabled flashing kernels and radios, the next update blocked you from writing to the system, this one has an update to the touch panel which breaks more then a few roms. Add to that the hassle of having to flash stock rom/recovery to update firmware or flashing a ruu which can cause more problems then it solves.
Click to expand...
Click to collapse
Wow jeez didn't hear about any cons with the latest update. I pray Viper is still going to be OK.
Sent from my EVO using xda premium
I think so far only aosp roms and mean bean (and twrp of course) are affected by the touch panel update
Related
I've looked around so far and can't really find any topics with updated radios for the Rezound. Can anyone point me In The right direction? Sorry if I just happened to miss any threads on this issue. And if it matters I'm running CleanROM ICS 2.3
Sent from my ADR6425LVW using xda premium
YoU need to relock it, ruu and then take the Verizon OTA update.
jmorton10 said:
YoU need to relock it, ruu and then take the Verizon OTA update.
Click to expand...
Click to collapse
Ah..... I see..... Guess we gotta wait for S-Off to do it with the phone itself. When you say ruu what do you mean. I have no clue what that is.
Sent from my ADR6425LVW using xda premium
dalvear88 said:
Ah..... I see..... Guess we gotta wait for S-Off to do it with the phone itself. When you say ruu what do you mean. I have no clue what that is.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
RUU will return you to stock. It's an exe file you run on your pc. Here's a lengthy post I made for someone else earlier today with instuctions:
p.s. I looked up that ICS Rom and it says "Updated: Mainver to 2.01.605.11" so you should run the RUU with that mainver number in the file name.
feralicious said:
Everything you need can be found in these Rezound forums.
So you can get into fastboot. That's good.
Do you still have your computer set up from when you unlocked the phone? If not, download the mini sdk that MrSmith317 made that I've attached and place that in the C: directory of your computer and name it something easy, mine is named android-flasher. Then just always keep it there as you will need to use it often when modding your phone.
1) get the sdk working on your computer
2) On your phone, do a battery pull, then boot it into fastboot and then connect it to your computer.
3) Type the following at your computer's cmd prompt:
fastboot getvar all
and find out what mainver you are on.
* If you are on a mainver that starts with 3.x then you cannot run the RUUs. I will try to find out what you should do in that case. If your mainver starts with 1.x or 2.x then continue onto step 4.
4) Relock your phone by typing the following:
fastboot oem lock
5) Download the RUU for your mainver to your computer. Use the file from here that corresponds to your mainver:
http://www.filefactory.com/f/c2e320ee1d5c7886/
This is an exe file so just run it on your pc with your phone attached. I know you need to be locked, I think you need HTC Sync installed, so if it's not working search for those answers, it will work, others have done it. Now you are back to stock.
5) Unlock your phone again using the same unlock bin file you got before by putting it in the same folder you are now using for sdk. Type the following command:
fastboot flash unlocktoken Unlock_code.bin
If you don't have it obtain a new one by following the same steps you did before to get it originally. Here is a guide for that:
http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
Now you should be stock and unlocked.
6) Flash Amon Ra in fastboot. Get the lateset version, 3.13. here:
http://www.mediafire.com/?chpoxzb8bl4nn2b
Type the following command to flash it:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Now you should have Amon Ra on your phone.
7) Root your phone by installing su using Amon Ra. Go to the developer menu and find the option in there.
Now you should be stock, unlocked and rooted.
8) MAKE A NANDROID BACK UP NOW AND LABEL IT.
9) Flash a new ROM.
*** If your mainver is 3.x try this thread to see if you can come up with a method to go back to stock. I haven't looked into this since I have not ventured into ICS land as of yet.
http://forum.xda-developers.com/showthread.php?t=1459347
There are also some threads about getting back to stock from ICS I think so here are my search results for "stock ics" in the thread title and you can probably find an answer in there somewhere.
Hope this helps you get back up and running.
Click to expand...
Click to collapse
My Evo has been completely trashed and I have no clue what to do.
I have hboot 1.19 s-on and I did the HTCdev unlock, and I rooted it and have the latest version TWRP (i think 2.3.something) with SuperSU installed. I tried to flash a ROM that was supposed to be compatible with with I had but i guess not. Everything was going great but I was stuck on the CM boot screen. After about 30 min of it sitting in that screen I figured something was wrong so i reset it and went back into TWRP. Someone told me to download MeanRom and flash that because its kernel and rom would fix everything. Here's where things get weird. I download MeanRom to my computer and mount my phone in TWRP to move the file over to the phone and when i went to factory reset before flashing it it kept saying unable to mount SD card and Internal Storage. I tried to do a restore my phone to an old back up and that wouldnt even work. So I wipe both caches and try to flash MeanRom anyway. i got a failed error and my phone shut off. Now my phone will only go into the Fastboot thing on the white screen and when i try to go into recovery, it just stays on the TWRP loading screen, not even letting me into the recovery program.
Is there anyway to fix this? My best buy insurance has expired because i missed 3 payments since I'm away at school and not working a whole bunch. So my whole smash it to pieces and get a new one solution is no longer an option.
I'm on a mac by the way so is there something I can enter into terminal to fix this? I don't care about losing any files or anything I'll do whatever I have to, to fix this.
Thanks in advance
- Josh
Read om4's guide don't panic...hboot 119 s-on you have to flash kernels separately.
Sent from my EVO using xda premium
I ran into the same problem. Word for word, really. I use a Mac, too. I went through HTCdev unlock, tried to flash a CM10 nightly and ran into a boot loop. No matter what I did, it was stuck. I couldn't restore to a nandroid backup because internal storage wouldn't mount. Couldn't do anything. All I had access to was bootloader and TWRP recovery.
I don't know the specifics of how this fixed it (I'm nothing close to a developer), but this is what I did to get out of it. You will need access to a Windows machine onto which you can download things.
1) If you still have access to fastboot, unroot your phone to stock. Completely stock.
2) Use DirtyRacun S-OFF (you'll need a Windows computer for this). Go through the whole process.
3) Re-root.
Nothing I tried fixed it until I started fresh. I couldn't tell you how it worked, but if you're desperate you really have nothing to lose but a little bit of time by doing the same thing I did.
Hope you get this figured out.
falconoble said:
I ran into the same problem. Word for word, really. I use a Mac, too. I went through HTCdev unlock, tried to flash a CM10 nightly and ran into a boot loop. No matter what I did, it was stuck. I couldn't restore to a nandroid backup because internal storage wouldn't mount. Couldn't do anything. All I had access to was bootloader and TWRP recovery.
I don't know the specifics of how this fixed it (I'm nothing close to a developer), but this is what I did to get out of it. You will need access to a Windows machine onto which you can download things.
1) If you still have access to fastboot, unroot your phone to stock. Completely stock.
2) Use DirtyRacun S-OFF (you'll need a Windows computer for this). Go through the whole process.
3) Re-root.
Nothing I tried fixed it until I started fresh. I couldn't tell you how it worked, but if you're desperate you really have nothing to lose but a little bit of time by doing the same thing I did.
Hope you get this figured out.
Click to expand...
Click to collapse
How would i unroot if I cant get into SuperSU since i cant boot up my phone? Do I need to do that first or can i just run the RUU without Going into SuperSU and hitting Unroot?
Also what do I need windows for? Getting S-OFF? Or unrooting?
Also thank you! I really hope this work!
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Shahal said:
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
I'm sorry if this is a stupid question. But how do i re-lock it from fastboot?
U have to use the cmd window on your windows computer. I did it with mine before I ran dirty racun. It is a simple command but u have to be in the right directory ind the cmd line. Go through and look at the dirty racun guide and it tells u how to re-lock word for word I believe.
Sent from my EVO using xda app-developers app
Shahal said:
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
Okay so I found a video on how to re-lock my phone in fastboot but when i type the command "fastboot oem lock"
it just says ' <waiting for device >
any suggestions on what to do? It's been stuck like this for about 5 min now.. in the video it took less than a second.
jklatt747 said:
Okay so I found a video on how to re-lock my phone in fastboot but when i type the command "fastboot oem lock"
it just says ' <waiting for device >
any suggestions on what to do? It's been stuck like this for about 5 min now.. in the video it took less than a second.
Click to expand...
Click to collapse
Turn on USB debug in devopleper options
Sent from a lens flare powered EVO LTE
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
Yeah i couldn't figure out how to do that. I would ask a question on how to do that and i just kept on getting the response of "google it" "look it up on youtube" or look in the forums. and I wasn't ever sure really where to find it because all my searches for it came up useless.
I just did the RUU on my phone and its finally back up and running! What a relief!!!
Now I'm going to try to get DirtyRacun s-off. How do I put a Custom Rom on my phone with S-off?
With s-off you just flash it in twrp..no extra steps
Sent from my EVO using xda premium
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
I only have windows 7 64bit. So this means i cannot go the dirtyracun route. Is there any other way to get S-OFF?
if not.. How do i fastboot flash the boot.IMG from the ROM manually?
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
I wish I'd ran into you when I had the same problem. I wasn't trying to make things more complicated for him, just telling him that when it happened to me, I went back to stock, went with S-OFF, and everything worked fine. At the very least I figured he probably would have just wanted his phone back.
falconoble said:
I wish I'd ran into you when I had the same problem. I wasn't trying to make things more complicated for him, just telling him that when it happened to me, I went back to stock, went with S-OFF, and everything worked fine. At the very least I figured he probably would have just wanted his phone back.
Click to expand...
Click to collapse
No. You helped me soooooo much! I was literally about to sell my phone for parts or something because everything went wrong that could go wrong and on top of that I couldn't find anything at all on how to fix it. I just did what you said and my phone is fixed! I want to go s-off now but dirtyracun doesn't support windows 7 with 64 bit, it only supports windows 7 with 32bit which I don't have access to. So i'm trying to find another way that is reliable to go S-OFF. It seems like S-OFF is the way to go and it makes everything easier.
If I cant find out how to go S-OFF with the windows 7 64 bit computer, then I guess i'll go S-on HTCdev unlock again and hopefully figure out how to manually flash the ROM or whatever it is that you do with S-ON.
jklatt747 said:
No. You helped me soooooo much! I was literally about to sell my phone for parts or something because everything went wrong that could go wrong and on top of that I couldn't find anything at all on how to fix it. I just did what you said and my phone is fixed! I want to go s-off now but dirtyracun doesn't support windows 7 with 64 bit, it only supports windows 7 with 32bit which I don't have access to. So i'm trying to find another way that is reliable to go S-OFF. It seems like S-OFF is the way to go and it makes everything easier.
If I cant find out how to go S-OFF with the windows 7 64 bit computer, then I guess i'll go S-on HTCdev unlock again and hopefully figure out how to manually flash the ROM or whatever it is that you do with S-ON.
Click to expand...
Click to collapse
Most sense roms come with a kernel installer for people that are S-ON and there have been reports of success using Win7 64bit and running DirtyRacun but.... if you run into problems they will not help you
bigdaddy619 said:
Most sense roms come with a kernel installer for people that are S-ON and there have been reports of success using Win7 64bit and running DirtyRacun but.... if you run into problems they will not help you
Click to expand...
Click to collapse
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
jklatt747 said:
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
Click to expand...
Click to collapse
It's included in the script just flash it like any other rom it takes a little longer to boot because it's writing the kenel so don't freak out
jklatt747 said:
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
Click to expand...
Click to collapse
There is an app in the market called Flash Image GUI to use it all you have to do is click on browse in the app search where ever you downloaded your Rom or kernel select it and it will extract and flash the boot.IMG for you. So if you are s on and wanna flash a aosp Rom you can first flash the kernel using the app then it gives you the option to boot directly in to recovery then install as usual wipe system ,data, both caches and flash your Rom that you extracted the kernel from. You can also just flash just a kernel if you want to OC.
Sent from my EVO using xda premium
bigdaddy619 said:
It's included in the script just flash it like any other rom it takes a little longer to boot because it's writing the kenel so don't freak out
Click to expand...
Click to collapse
dandan2980 said:
There is an app in the market called Flash Image GUI to use it all you have to do is click on browse in the app search where ever you downloaded your Rom or kernel select it and it will extract and flash the boot.IMG for you. So if you are s on and wanna flash a aosp Rom you can first flash the kernel using the app then it gives you the option to boot directly in to recovery then install as usual wipe system ,data, both caches and flash your Rom that you extracted the kernel from. You can also just flash just a kernel if you want to OC.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Okay so here's whats happens for me.
When i go bigdaddy's way: I put the MeanRom zip on my phone from my computer (MeanRom v64 or what ever the latest one is) I factory reset, wipe cache, wipe dalvic chache, and then go to install find the app and swipe to flash.. everything seems fine until i get an error and fail. It also says there is no MD5 file when i do this.
When I go dandan's way: I have the MeanRom zip on my phone (i've tried this with v64 *or whatever the latest one is* and v34) then i go into flash image GUI and go through finding it and everything. Then i get an error right above the Flash Image button saying "zip file must contain only one of the following: recovery.img, zimage, or a type of boot.img!" On my computer I unzipped the file and looked inside and all I see the boot.img and some folders but no recover or zimage so i dont know what it is talking about.
I really dont want to go through the processes of unrooting and relocking my phone again so i want to do this right. Any help from here on out would be greatly appreciated!
If someone could give me a step by step to follow or something for putting the Latest version of MeanRom on my phone that would be great!! I think i read somewhere that you have to put on the old version of MeanRom first. If that is so, could you also include how i would go about updating from the old version to the new one?
(If you're going to help me please make sure your method supports the HTC EVO 4G LTE on hBoot 1.19 Software v. 2.13.651.1 71ORD HTCdev Unlocked and Rooted with SuperSU and TWRP. (GooManager, and Flash Image GUI are installed to)
I dont know if this matters but it also says under Kernel Version:
3.0.8-01680-gb6402b4
[email protected] #1
SMP PREEMPT
Other info:
Baseband v: 1.12.11.0809
Android Version: 4.04
HTC Sense: 4.1
HTC SDK API level: 4.24
I know this post is really long and I probably put waaayyy more information then I actually needed to but I just want to be safe. It seems like everything I try for putting any Roms on my phone goes wrong with an error or failed message and I really want to do this.
I'm on the 3.15 RUU with 2.09 HBOOT. I used dirty racun for s-off and am HTCdev unlocked obviously. I know I can't undo the HTCdev unlock.
In what order do I need to do these things to relock bootloader/unroot and restore to stock 3.15?
I'm thinking:
1.) Flash stock recovery image then flash stock 3.15 RUU.
2.) Relock bootloader
3.) profit?
4.) skip like a fairy
If I flash the stock RUU that will restore S-ON correct?
BTW, is there an active link for the stock JB 3.15? HTCruu is no more and that was the only place I knew.
Bueller?
Any feedback on where I can get the stock 3.15 RUU?
Stock Rooted 3.15.651 rom
heroisnotdead said:
Any feedback on where I can get the stock 3.15 RUU?
Click to expand...
Click to collapse
This is all I know for now, a stock, rooted rom. I'm trying to find the full RUU dot exe file. I have the link around here somewhere.
I was trying to post the link, and didn't notice at first, that I'm too new. I was going to spell out the URL, but didn't want to offend the moderators. I guess you can send me private message, if you want it. The link was sent to me by a senior member of xda, and member of dev team for a well-known rom.
See here for zips which include the files for rooting + the RUU exe's:
http://forum.xda-developers.com/showthread.php?t=2026938
When I was HTCdev unlocked and wanted to get back to stock ICS and take the OTA to get Jellybean, I followed the Youtube link at the bottom of that post to relock the bootloader. After that, I then ran the RUU from my computer. That brought my phone back to stock. (Then I took the OTA to Jellybean, unlocked again, and installed a new ROM, but that's not what you're looking to do, it sounds like)
1. Reboot into bootloader
2. Set phone to fastboot option
3. Connect phone to pc with adb folder already setup on computer (htc drivers etc).
4. Make sure computer says "fastboot usb"
5. Open command prompt from your adb folder
6. Type "fastboot oem lock"
7. Run 3.15.651.16 RUU exe file on computer and sit back.
Since you have 2.09 hboot then you're stuck using the 3.15 ruu file....hope that helps...let us know how it ended up.
Sent from my EVO using xda app-developers app
Thanks
Damn I'm blind. I've had that file the whole time and kept looking right over it due to the way I had files displaying. These RUU files will overwrite everything, including the recovery image, correct?
How I miss doing this stuff on nexus device, oh well.
heroisnotdead said:
Damn I'm blind. I've had that file the whole time and kept looking right over it due to the way I had files displaying. These RUU files will overwrite everything, including the recovery image, correct?
How I miss doing this stuff on nexus device, oh well.
Click to expand...
Click to collapse
Yea the ruu will overwrite EVERYTHING...it'll basically make your phone as if you just opened the box....only thing is to make absolutely sure you have the correct one that matches your current hboot....
Sent from my EVO using xda app-developers app
[Q] Getting "Error [140]: Bootloader Version Error" when I try to downgrade my HBoot
Okiedoke. So, I've got a little experience with the Evo 3D, but my last one was shoddily done and I don't think I ever even attained S-OFF on it, so when I had to get mine replaced by Sprint, I figured I'd follow a guide and do this thing right.
I first followed the HTC method of unlocking my bootloader and rooting the device, and then installed TWRM. I was using my phone for about a week before I just today decided I had enough time to look at these instructions and follow them. I successfully used this PG86IMG file (from this thread) to brick my device, followed the instructions from the original thread up to 27, and then realized I might have a problem on my hands. I can't boot my phone into the OS anymore (I get a sudden slowdown and then freeze of the boot animation before it restarts itself), but I can still get into the bootloader and Fastboot. So, I figured, why not just run the 1.13 RUU EXE in Fastboot? So I tried, but every time I try to run an RUU EXE (I've tried several, both 1.13 and 2.17 versions), after the RUU pushes the file to the phone and checks signatures I get error 140. I saw that Unknownforce said here that these instructions are "extremely dated" and to use the new ones in his newer thread, but I'm not sure where to pick up.
In short, I would love it if someone could recognize what the next step I need to take is. Ask me for any further information I haven't provided, I'll be more than glad to help you guys help me!
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Macadamia Daze said:
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Click to expand...
Click to collapse
Well this probably won't help with my issue, but this guy seems to have found a solution for yours.
Macadamia Daze said:
I'm having a similar issue, the only difference between our issues being that I get Error 131: CUSTOMER ID ERROR. Still working on how to fix it.
Click to expand...
Click to collapse
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Sent from my SPH-L720 using xda app-developers app
Unknownforce said:
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I tried this two different ways:
Got a 1.13 PG86IMG ZIP from Shipped ROMs, renamed to PG86IMG and put on my SD card, but my phone didn't want anything to do with it (it would load and check it, but then kick me back out to the main bootloader screen). Then I downloaded a 1.13 RUU EXE and extracted the "rom" file from it, renamed and slapped on card. Phone loads and checks correctly, but then returns the "Main version is older!" error.
DavisJ3608 said:
I tried this two different ways:
Got a 1.13 PG86IMG ZIP from Shipped ROMs, renamed to PG86IMG and put on my SD card, but my phone didn't want anything to do with it (it would load and check it, but then kick me back out to the main bootloader screen). Then I downloaded a 1.13 RUU EXE and extracted the "rom" file from it, renamed and slapped on card. Phone loads and checks correctly, but then returns the "Main version is older!" error.
Click to expand...
Click to collapse
Then your misc version didn't downgrade as it should have. Go to the main thread and flash the firmware zip file that's listed there, it will put you up to 1.58 hboot, then start that process from scratch.
Unknownforce said:
Then your misc version didn't downgrade as it should have. Go to the main thread and flash the firmware zip file that's listed there, it will put you up to 1.58 hboot, then start that process from scratch.
Click to expand...
Click to collapse
Okiedoke. Just to verify (sorry for being thick), when you say "Main Thread" you're talking about this one, right? I ask because the only firmware I see there is for Virgin, and I'd rather keep Sprint firmware on my phone (unless it really, truly doesn't change anything but the name).
Also, your method requires launching a Linux distro, yes? Is it OK if it's off a live USB, like the Ubuntu installer OS? For some reason I can't get my machine to cooperate when I try to install a permanent Linux OS (something to do with UEFI settings, I think).
DavisJ3608 said:
Okiedoke. Just to verify (sorry for being thick), when you say "Main Thread" you're talking about this one, right? I ask because the only firmware I see there is for Virgin, and I'd rather keep Sprint firmware on my phone (unless it really, truly doesn't change anything but the name).
Also, your method requires launching a Linux distro, yes? Is it OK if it's off a live USB, like the Ubuntu installer OS? For some reason I can't get my machine to cooperate when I try to install a permanent Linux OS (something to do with UEFI settings, I think).
Click to expand...
Click to collapse
That thread yes, but I mean the PG86IMG file from the downgrade section there, use that to update the hboot and firmware, then start that section from scratch.
And yes any linux will work USB or not.
Unknownforce said:
That thread yes, but I mean the PG86IMG file from the downgrade section there, use that to update the hboot and firmware, then start that section from scratch.
And yes any linux will work USB or not.
Click to expand...
Click to collapse
I actually ended up pulling an old laptop out from storage and putting Ubuntu on that so I can have an actual workstation. I ran the PG86IMG you mentioned, which got my phone back up and running with HBOOT 1.58. Then I followed all of your instructions to the letter, down to where you say to run the 1.13 RUU EXE. I tried running that on Ubuntu using WINE, but I kept getting an error. Then I tried running it on Windows 8, but I can't seem to get the EXE to detect my phone is connected. Then I even tried running the RUU in a WinXP virtual machine, but I can't seem to get that to work either. I then tried simply using the 1.13 ZIP as PG86IMG, but I'm getting the same error where after it loads and scans the file, it kicks me out to the main bootloader screen with no warnings or error messages.
At this point, what would be the better option? Should I attempt Revolutionary and get S-Off, then redo the instructions? Or should I do something else? Do I even need to install the 1.13 RUU? I assume I do, because my phone is unusable if I don't...
DavisJ3608 said:
I actually ended up pulling an old laptop out from storage and putting Ubuntu on that so I can have an actual workstation. I ran the PG86IMG you mentioned, which got my phone back up and running with HBOOT 1.58. Then I followed all of your instructions to the letter, down to where you say to run the 1.13 RUU EXE. I tried running that on Ubuntu using WINE, but I kept getting an error. Then I tried running it on Windows 8, but I can't seem to get the EXE to detect my phone is connected. Then I even tried running the RUU in a WinXP virtual machine, but I can't seem to get that to work either. I then tried simply using the 1.13 ZIP as PG86IMG, but I'm getting the same error where after it loads and scans the file, it kicks me out to the main bootloader screen with no warnings or error messages.
At this point, what would be the better option? Should I attempt Revolutionary and get S-Off, then redo the instructions? Or should I do something else? Do I even need to install the 1.13 RUU? I assume I do, because my phone is unusable if I don't...
Click to expand...
Click to collapse
If the bootloader is not saying anything about the zip file it's not a valid signed zip. Find another copy of it or extract it from the ruu exe. Run the exe and open up the temp folder and search for rom.zip then rename to PG86IMG(.zip) and put on sdcard. Then try again. You need special drivers for windows 8, which is why that didn't work, the other two are emulated versions of Windows, and don't have the proprietary drivers to work properly either. So unless you have access to another windows pc that isn't 8, your only option is to get the sdcard the correct file.
Sent from my SPH-L720 using xda app-developers app
DavisJ3608 said:
Well this probably won't help with my issue, but this guy seems to have found a solution for yours.
Click to expand...
Click to collapse
No dice. I can't change my CID without getting an error, presumably because I can't HTCDev unlock (when I get to the final step, I get success on fastboot but never the prompt on the phone).
Unknownforce said:
Put the PG86IMG(.zip) on the sdcard and boot to bootloader and update that way. The ruu exe checks the Cid, the bootloader flash doesn't.
Click to expand...
Click to collapse
Hboot just checked my CID and kicked me out.
Macadamia Daze said:
No dice. I can't change my CID without getting an error, presumably because I can't HTCDev unlock (when I get to the final step, I get success on fastboot but never the prompt on the phone).
Hboot just checked my CID and kicked me out.
Click to expand...
Click to collapse
Uhhh... Pretty sure that is to super cid a gsm phone
I don't think it's meant for CDMA!!
Unknownforce said:
If the bootloader is not saying anything about the zip file it's not a valid signed zip. Find another copy of it or extract it from the ruu exe. Run the exe and open up the temp folder and search for rom.zip then rename to PG86IMG(.zip) and put on sdcard. Then try again. You need special drivers for windows 8, which is why that didn't work, the other two are emulated versions of Windows, and don't have the proprietary drivers to work properly either. So unless you have access to another windows pc that isn't 8, your only option is to get the sdcard the correct file.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Oh my god, I feel like a dumbass for not pulling the rom from the EXE before saying anything o.o
Anywho, I pushed the 1.13 PG86IMG correctly, then ran Revolutionary on Ubuntu, and now my phone's S-Off and 1.40! Thanks so much! Hand to god, when I get paid I'm sending you beer money.
DavisJ3608 said:
Oh my god, I feel like a dumbass for not pulling the rom from the EXE before saying anything o.o
Anywho, I pushed the 1.13 PG86IMG correctly, then ran Revolutionary on Ubuntu, and now my phone's S-Off and 1.40! Thanks so much! Hand to god, when I get paid I'm sending you beer money.
Click to expand...
Click to collapse
Haha, glad it worked :highfive:
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.