I was wondering if there was an alternative way to unlock the bootloader for my HTCevo3D. I'm on hboot 1.58(ICS Stock OTA Update)
I've tried the HTCDev method about 50 times in total. Used 3 systems. iMac running Windows 7/XP, Ubuntu, and Mac OS X.
My Lenovo X61 laptop running Ubuntu, Windows 7/XP, and my custom-built desktop pc running Windows 7(ASRock990FXExtreme3 Motherboard)
So I've come to the conclusion that something is wrong with the phone itself.
Again, is there an alternative method for unlocking the bootloader so I can install a custom kernel?
SkyChotik said:
I was wondering if there was an alternative way to unlock the bootloader for my HTCevo3D. I'm on hboot 1.58(ICS Stock OTA Update)
I've tried the HTCDev method about 50 times in total. Used 3 systems. iMac running Windows 7/XP, Ubuntu, and Mac OS X.
My Lenovo X61 laptop running Ubuntu, Windows 7/XP, and my custom-built desktop pc running Windows 7(ASRock990FXExtreme3 Motherboard)
So I've come to the conclusion that something is wrong with the phone itself.
Again, is there an alternative method for unlocking the bootloader so I can install a custom kernel?
Click to expand...
Click to collapse
There's a known problem flashing the unlock .bin file if you've upgraded to ICS using the OTA, causing the phone to hang instead of prompting for confirmation. Try flashing the RUU and then flashing the unlock .bin file again after that.
If that doesn't work you can try unknownforce's downgrade method in the stickies of the development forum to go straight to S-OFF, and you will need the RUU for that as well.
ramjet73
ramjet73 said:
There's a known problem flashing the unlock .bin file if you've upgraded to ICS using the OTA, causing the phone to hang instead of prompting for confirmation. Try flashing the RUU and then flashing the unlock .bin file again after that.
If that doesn't work you can try unknownforce's downgrade method in the stickies of the development forum to go straight to S-OFF, and you will need the RUU for that as well.
ramjet73
Click to expand...
Click to collapse
Where can I get the RUU?
SkyChotik said:
Where can I get the RUU?
Click to expand...
Click to collapse
Here.
ramjet73
Related
So I've been following the progress of the Evo 3D for a bit, decided ok I'll get one, and now am at a loss. I've tried every method posted on this site to try and unlock my phone, the TWRP method, Revolution, HTCDEV method, all of them, and none of them are working for me. With the HTC DEV method, I flash the unlock code.bin and there it stops. Tried running the RUU and I get errors, Revolution doesn't even support my hboot version and TWRP is also for older hboot versions. The only one I haven't tried is a method listed in the Express rom thread, there is supposedly a file called reboot3d.zip but the file isn't there anymore for me to try. I'm at my wits end. All I want is to flash a new rom and recovery, unlock my wifi tether and remove some bloatware, why is this so difficult? Has anyone had any success with an unlockable phone by any means? Please, any help would be appreciated.
Fltblkvic
fltblkvic said:
So I've been following the progress of the Evo 3D for a bit, decided ok I'll get one, and now am at a loss. I've tried every method posted on this site to try and unlock my phone, the TWRP method, Revolution, HTCDEV method, all of them, and none of them are working for me. With the HTC DEV method, I flash the unlock code.bin and there it stops. Tried running the RUU and I get errors, Revolution doesn't even support my hboot version and TWRP is also for older hboot versions. The only one I haven't tried is a method listed in the Express rom thread, there is supposedly a file called reboot3d.zip but the file isn't there anymore for me to try. I'm at my wits end. All I want is to flash a new rom and recovery, unlock my wifi tether and remove some bloatware, why is this so difficult? Has anyone had any success with an unlockable phone by any means? Please, any help would be appreciated.
Fltblkvic
Click to expand...
Click to collapse
the htc device method should work are you sure youre typing in the command this way
fastboot flash unlocktoken Unlock_code.bin
and are you using linux mac or windows as your computer operating system to do this
I assume u are getting stuck at step 13 with Hboot 1.50 unlocking. Htcdev method is the only method.
What is ur current Sw version. 2.08.651.3, 2.17.651.5, etc?
You need to run the matching full Sw Ruu or a more current one (exe or zip version), then the code will work. The Guide/flashing notes in my signature may help u.
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
I assume u are getting stuck at step 13 with Hboot 1.50 unlocking. Htcdev method is the only method.
What is ur current Sw version. 2.08.651.3, 2.17.651.5, etc?
You need to run the matching full Sw Ruu or a more current one (exe or zip version), then the code will work. The Guide/flashing notes in my signature may help u.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
A few of these pop up everyday huh?
[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:
Okay, here's the biz. My wife's phone needs updated, and I'm not sure of the best way to do it. She's rooted and I want to keep it that way, as she needs her wifi-tether.
She's not s-off. I tried using moonshine and rumrunner to no avail, even though I had met all pre-requisites. rumrunner recommended I flashed a less-stable kernel and try it again. I'm not real interested in doing that.
I was trying to s-off so i could flash the OTAs that are on xda.
I have studied posts on here for about 4 hours now and have not come up with a solid answer.
The only things we need are root and the newest 3.17- firmware and possibly radios. Can anyone send me to the right place?
Can I just ruu the newest software?
Please. Thanks will be given.
Phone specs:
freshly ruu android 4.0.4
sense 4.1
software 2.13.651.1
s-on
bootloader unlocked
hboot 1.19.000
radio 1.12.11.0803
Check the top link in my sig. There is a link to all applicable RUU's at the bottom of the first post (I recommend reading the entire thread), including the 3.17 RUU and the newer 4.13 RUU. Running the RUU will update your software, firmware, HBOOT, etc. The RUU is probably the quickest way to get everything up to date, in my opinion. Just download whichever RUU you want to install to your computer, connect your phone to your computer while the phone is booted to the OS, double-click the RUU file and follow the on-screen instructions on your computer. You may also want to install HTC Sync to your computer, as well. After running the RUU you'll need to unlock your bootloader again, install a custom recovery and SuperSU for root access. If you want to S-off the phone once it's updated, again, check the top link in my sig for further info.
Sent from my HTC device
I tried using the ruu for the newest 4.XX and it wouldn't work. I guess I should just use 3.17.xxx?
NVM, I forgot to relock the bootloader before I tried the ruu.... now it's working. Thanks
btyking said:
NVM, I forgot to relock the bootloader before I tried the ruu.... now it's working. Thanks
Click to expand...
Click to collapse
Glad you got it going:thumbup:
Sent from my HTC device
Hey I'm trying to use windroid to unlock the bootloader again, but it's not recognizing the phone's status.. any help on unlocking that bloader?
Again, NVM I had to authorize the debugging on my phone.
Okay, I've ruu to the newest ota, which is 4.XX- and I have TWRP 2.7.0 but I can't figure out how to root it. I have tried flashing both of the super user files from the linked page in your sig, to no avail. I tried to flash them from twrp. Nothing. One app says it needs binaries, and the other one doesn't open. Not sure how to root at this point? I tried to push the superuser.zip files through adb shell and that didn't work either. stumped...
btyking said:
Okay, I've ruu to the newest ota, which is 4.XX- and I have TWRP 2.7.0 but I can't figure out how to root it. I have tried flashing both of the super user files from the linked page in your sig, to no avail. I tried to flash them from twrp. Nothing. One app says it needs binaries, and the other one doesn't open. Not sure how to root at this point? I tried to push the superuser.zip files through adb shell and that didn't work either. stumped...
Click to expand...
Click to collapse
You need to use the TWRP from Captain's thread.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Okay, thanks, got it. Do I need a different kernel to s-off with rumrunner?
It's been a long time since I flashed a RUU.
If my phone is S-OFF can I flash a RUU to put the device back to stock, including stock recovery but still retain S-OFF?
or will it switch it back to S-ON
thanks,
S-off is not affected by an RUU install
DanGeorges said:
S-off is not affected by an RUU install
Click to expand...
Click to collapse
Hi, not to hijack the thread, but I had a question about the RUU install. I downloaded the install from the HTC website and backed up my phone. However, when I go to run the RUU install, it brings up the original window but when I get to the Terms and conditions, I select ok and hit next and it closes and nothing happens. Any suggestions?
kmac212 said:
Hi, not to hijack the thread, but I had a question about the RUU install. I downloaded the install from the HTC website and backed up my phone. However, when I go to run the RUU install, it brings up the original window but when I get to the Terms and conditions, I select ok and hit next and it closes and nothing happens. Any suggestions?
Click to expand...
Click to collapse
I've seen this mentioned by some other users.
What build of Windows? I think Win8 might have been the culprit, if I recall correctly.
redpoint73 said:
I've seen this mentioned by some other users.
What build of Windows? I think Win8 might have been the culprit, if I recall correctly.
Click to expand...
Click to collapse
I'm having the same exact problem. I'm running Windows 7 Pro x64. Phone is htcdev unlocked and running stock ROM.
srpeters18 said:
I'm having the same exact problem. I'm running Windows 7 Pro x64. Phone is htcdev unlocked and running stock ROM.
Click to expand...
Click to collapse
Win7 64bit is fine (its what I use). If you are s-on, you need to relock your bootloader to RUU. Although that should give you an error message (if the bootlaoder is unlocked with s-on), not just exit the RUU program after the Terms & Conditions.
redpoint73 said:
Win7 64bit is fine (its what I use). If you are s-on, you need to relock your bootloader to RUU. Although that should give you an error message (if the bootlaoder is unlocked with s-on), not just exit the RUU program after the Terms & Conditions.
Click to expand...
Click to collapse
I am S-ON and bootloader relocked. I'm going to try another PC (same OS) to see if there is any difference.
srpeters18 said:
I am S-ON and bootloader relocked. I'm going to try another PC (same OS) to see if there is any difference.
Click to expand...
Click to collapse
Is the phone booted into OS when you run the RUU? Try booting into bootloader-fastboot before running the RUU, and see if that makes a difference (if you haven't tried already).
If you just relocked, you are probably already in bootloader-fastboot.
redpoint73 said:
Is the phone booted into OS when you run the RUU? Try booting into bootloader-fastboot before running the RUU, and see if that makes a difference (if you haven't tried already).
If you just relocked, you are probably already in bootloader-fastboot.
Click to expand...
Click to collapse
I tried both and had no luck on my PC. Moving to a different PC worked fine however. Not sure what the difference was, as both are running the same version of our Windows image.
I've got hboot 1.57, 4.4.4., and the latest CM11 nightly. Unlocked bootloader, S-ON. I'm trying to flash the RUU_M7_UL_L50_SENSE60_MR_Cingular_US_7.23.502.1_Radio_4M.32.3218.06_10.46.1718.01L_release_424933_signed_2 rom update from the HTC website. I keep getting an error 155 that it isn't the right rom image for my phone. I'm assuming I need to relock my bootloader for the update to take? Do I need to go back to full stock? I've googled a ton and cannot find an easy way to relock my bootloader. I'm not sure if it matters, but I no longer have the stock HTC usb cable so i'm using one that came with a dell windows tablet. Thanks for any help.
dihnekis said:
I've got hboot 1.57, 4.4.4., and the latest CM11 nightly. Unlocked bootloader, S-ON. I'm trying to flash the RUU_M7_UL_L50_SENSE60_MR_Cingular_US_7.23.502.1_Radio_4M.32.3218.06_10.46.1718.01L_release_424933_signed_2 rom update from the HTC website. I keep getting an error 155 that it isn't the right rom image for my phone. I'm assuming I need to relock my bootloader for the update to take? Do I need to go back to full stock? I've googled a ton and cannot find an easy way to relock my bootloader. I'm not sure if it matters, but I no longer have the stock HTC usb cable so i'm using one that came with a dell windows tablet. Thanks for any help.
Click to expand...
Click to collapse
S on u need to lock the bootloader . Google adb command to lock bootloader or use a tool that does it for you.
Sent from my HTC One using Tapatalk
grigoriisi said:
S on u need to lock the bootloader . Google adb command to lock bootloader or use a tool that does it for you.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks, i got the bootloader locked. I tried to flash the rom and it got stuck at step 1/6 Sending for over an hour. I'm going to retry after uninstalling htc sync and running in xp compatibility mode. If that doesn't work I'll try extracting the rom.zip and manually flashing it with fastboot.