Ok, did have my phone rooted but one of the ROM's on here managed to cause problems so installed one of the factory HTC ROM's to unroot it and put it back should I need to send it to HTC to fix.
So after putting the stock HTC ROM on when I enter recovery mode it is now teling me that the handset is locked (bootloader is presume) also the it is still showing S-OFF.
It is showing the following so if someone can explain to a noob how to re-root it that would be fantastic.
SHOOTER_U PUT SHIP S-OFF RL
HBOOT - 1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011,15:03:01
Any help is really appreciated as there is some really cool looking ROM's that I would like to try.
So, over 80 views and no-one has an answer for this?!
ratedr75 said:
Ok, did have my phone rooted but one of the ROM's on here managed to cause problems so installed one of the factory HTC ROM's to unroot it and put it back should I need to send it to HTC to fix.
So after putting the stock HTC ROM on when I enter recovery mode it is now teling me that the handset is locked (bootloader is presume) also the it is still showing S-OFF.
It is showing the following so if someone can explain to a noob how to re-root it that would be fantastic.
SHOOTER_U PUT SHIP S-OFF RL
HBOOT - 1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011,15:03:01
Any help is really appreciated as there is some really cool looking ROM's that I would like to try.
Click to expand...
Click to collapse
ratedr75 said:
So, over 80 views and no-one has an answer for this?!
Click to expand...
Click to collapse
Wow .. so originally you had an older hboot and used revolutionary to set s-off. Then you loaded a newer RUU which contained an hboot that was patched against revolutionary's s-off method.
Now you're on a newer hboot patched against revolutionary's s-off method, but you're still set s-off from previously using their method.
Don't see this situation very often. According to the theory, of how unrevoked set s-off and how I assume revolutionary is similar, you should still be s-off, as your bootloader shows, meaning your internal memory is NOT write protected.
In order to root your device, you should be able to fastboot flash a custom recovery. Boot into the custom recovery and load the normal superuser .zip or manually over adb push an su binary (I prefer aosp for developers) and chmod 4755 /system/bin/su . Both of those methods should give you root!
Hope that helps!
So if I install another ROM and try to goto recovery mode (which at the moment I am getting the triangle when I enter) I should be able to re-root this?
joeykrim said:
Wow .. so originally you had an older hboot and used revolutionary to set s-off. Then you loaded a newer RUU which contained an hboot that was patched against revolutionary's s-off method.
Now you're on a newer hboot patched against revolutionary's s-off method, but you're still set s-off from previously using their method.
Don't see this situation very often. According to the theory, of how unrevoked set s-off and how I assume revolutionary is similar, you should still be s-off, as your bootloader shows, meaning your internal memory is NOT write protected.
In order to root your device, you should be able to fastboot flash a custom recovery. Boot into the custom recovery and load the normal superuser .zip or manually over adb push an su binary (I prefer aosp for developers) and chmod 4755 /system/bin/su . Both of those methods should give you root!
Hope that helps!
Click to expand...
Click to collapse
ratedr75 said:
So if I install another ROM and try to goto recovery mode (which at the moment I am getting the triangle when I enter) I should be able to re-root this?
Click to expand...
Click to collapse
I've quoted my previous post to highlight the steps outlined. I never mentioned anything about another ROM.
If the theory holds, as it was true for unrevoked's method of s-off and some members of unrevoked are now part of AlphaRevX releasing the revolutionary tool, you only need to flash a custom recovery through fastboot or bootloader.
If you have adb setup, it would literally take you 10 seconds to issue the fastboot command and another 10 seconds to reboot into recovery to see if t worked.
Currently, when you boot into recovery and you see the triangle, that is the stock recovery. Sometimes on the stock recovery screen, if you want to activate the menu, pressing vol up + pwr *should* work in stock recovery but sometimes manf like HTC change this function in the version of recovery they distribute.
Once you use the command: fastboot flash recovery c:\android\cwm-recovery.img , you should be able to boot into recovery and see the custom recovery load.
If that method doesnt work, the other method to attempt is loading a PG86IMG.zip file on the root of the sdcard with the custom recovery inside the PG86IMG.zip. Upon booting into the bootloader, it should scan this file and ask to update. If you select yes to update, the bootloader should flash and you should have a custom recovery.
If neither of those two methods work, you'll likely have to use the HTC unlock method. But I think those methods should work as your device still shows S-OFF.
Good luck!
Have tried all your methods and various other ones.
None of them work at all, a lot of the people on here seem to think that eveyrone has their abilities.
I could get an ADB shell up, the CMD prompt didn't work either.
The phone is going in its box and i'd rather spend some money on a phone that is easier to work with a windows 7 laptop.
ratedr75 said:
Have tried all your methods and various other ones.
None of them work at all, a lot of the people on here seem to think that eveyrone has their abilities.
I could get an ADB shell up, the CMD prompt didn't work either.
The phone is going in its box and i'd rather spend some money on a phone that is easier to work with a windows 7 laptop.
Click to expand...
Click to collapse
The issues you're experiencing are due to HTC's complex locking method to deter root access. There are many Android devices which come stock with no locking protection or must less sophisticated locking protection.
If you're not able to properly setup adb, then the PG86IMG.zip method should be more convenient for you. All you need to do is put a PG86IMG.zip file onto the root (main dir) of your sdcard and holding vol down + pwr (boot into the bootloader). From here, it will scan the PG86IMG.zip and prompt if you want to load. Choose yes and this will flash the custom recovery.
Once the custom recovery is loaded, you should be able to flash a rooted ROM from, flash superuser .zip file or adb push su binary to restore root.
HTC intentionally makes this process difficult and it is relatively more difficult than other Android devices. All the resources are here at your disposal but HTC requires a bit more work/effort/learning to accomplish what is easier on some other Android devices. Although, even the Google Nexus S requires using fastboot to unlock t he device.
Nobody wants to see anybody give up and abandon. Hope that helps!
for whatever reason on the evo 3D, fastboot commands for things like flashing a recovery don't seem to work even with s-off. You need to put the custom recovery in a zip and name it PG86IMG then flash it from the bootloader and it will work.
fyi you should always be able to run a stock RUU (even new ones) because Revolutionary for the evo 3D gave you actual radio s-off and not just fake s-off with a patched hboot which is how Revolutionary worked on most phones. radio s-off pretty much means your phone will never go back to s-on even with a stock RUU. that is why you were able to upgrade the hboot and still keep s-off.
Thanks for the help guys. I'm going to give this one last try before I got and invest in an xperia arc s.
Does anyone have a decent download for the PG86IMG.zip file?
Ill try this at lunch, if not its away it goes.
patrick92260 said:
for whatever reason on the evo 3D, fastboot commands for things like flashing a recovery don't seem to work even with s-off.
Click to expand...
Click to collapse
fastboot commands don't work on the EVO 3D? even for recovery?
I haven't seen this complaint on the Q&A board. Majority of users seem to have plenty of success using fastboot to flash kernels and custom recoveries. Although, majority of people posting on the Q&A board recently have the latest hboot and can only use HTC's unlock method. Perhaps this is only an issue on revolutionary s-off devices?
ratedr75 said:
Thanks for the help guys. I'm going to give this one last try before I got and invest in an xperia arc s.
Does anyone have a decent download for the PG86IMG.zip file?
Ill try this at lunch, if not its away it goes.
Click to expand...
Click to collapse
I went to google.com and typed in the phrase, "twrp PG86IMG.zip" and the second link looks to be the quickest to obtaining the file:
http://teamw.in/project/twrp/67
I have heard pretty decent reports of Sony being fairly support of developers and allowing their devices to be unlocked and rooted.
Good Luck!
Thanks guys. Again. Now would anyone be interested in purchasing the EVO 3D GSM sim free from myself?
hi I am in the same position as the OP, just got my phone 2nd hand..want to flash LeeDroids Rom, my phone is GSM version, please advise how to get custom recovery..thanks
Related
So from what i've been reading is that we cant root yet because of the locked bootloader. Is this what s-on, s-off is? Because my htc hero is s-on right now and its rooted and flashed to cyanogen. So what am i missing that i dont understand? Thanks for all the help
bavman said:
So from what i've been reading is that we cant root yet because of the locked bootloader. Is this what s-on, s-off is? Because my htc hero is s-on right now and its rooted and flashed to cyanogen. So what am i missing that i dont understand? Thanks for all the help
Click to expand...
Click to collapse
There are a couple of different ways to root.....As was the case with our beloved heros we had temp root, which allowed us to flash recovery and custom roms and only after that were we able to get access to the bootloader.
The other way of rooting is to go through the bootloader and use it to flash recovery, and then flash a pre-rooted rom.
2 Methods, same result.
Cool thanks for clarifying.
I remember when i was rooting my hero i had to push some files to my phone using command prompt in windows. And we cant us that for our evos? Is it just a case of someone actually coming along and making an image to flash?
A boot loader is a little section of code that starts up and will load a section of the software that loads other sections of software and so on..now..this boot loader is encrypted and has a certain electronic signature that must be there to let it go on and load the rest of the program..kernel..drivers....and so on. Root is different..it is elevation of privileges to parts of the programs. We can still have root even with a locked boot loader. It just means we cannot flash custom roms with different items on it.
bavman said:
Cool thanks for clarifying.
I remember when i was rooting my hero i had to push some files to my phone using command prompt in windows. And we cant us that for our evos? Is it just a case of someone actually coming along and making an image to flash?
Click to expand...
Click to collapse
We could if we had temporary root access....That would allow us to make the /system files read/write. Then you would be able to push the recovery files from ADB as you did with the Hero.
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
I feel your pain and I've try the HTC dev. unlock with no luck I'm coming from the OG evo which was really easy to root ..
Sent from my PG86100 using XDA Premium App
go to htcevohacks.com i hace hboot 1.5 and it worked perfectly if u have the newest upgrade tho i dont think they have a root method out yet
Htcevohacks is easiest . And with the newest ota its still hboot 1.5
Sent from my PG86100 using XDA App
brandonaspencer said:
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
Click to expand...
Click to collapse
It would help us if you told us exactly what problems you are having.
Cool!! thanks!!
Sent from my PG86100 using XDA Premium App
Look at the roll up stickies. The directions are pretty clear. HTC method is going to be your only option
Sent from my Galaxy Nexus using XDA App
Rooting phone
brandonaspencer said:
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
Click to expand...
Click to collapse
have kinda problems have you had with rooting your phone.
HTC evohacks is very easy thanks !! For the help : )
Sent from my PG86100 using XDA Premium App
yami951 said:
Look at the roll up stickies. The directions are pretty clear. HTC method is going to be your only option
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I agree
Sent from my PG86100 using xda premium
Trying to root using HTC 1.5 with no success.
Hi to all I have tried to root using the HTC boot unlocker with no success. I was using the step by step instructions from HTC evo hacks. I got to the step at the command prompt where I put in the unlock code and I got this : C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.161s
The phone screen asking me to unlock the bootloader never came up. Any help would be appreciated. BTW I have rooted at least 7 EVO 3D's. with no problems.
I'm stumped.
lilal100 said:
The phone screen asking me to unlock the bootloader never came up. Any help would be appreciated. BTW I have rooted at least 7 EVO 3D's. with no problems.
Click to expand...
Click to collapse
See the Guide/flashing Notes in my signature. You need to rerun the currently installed "FULL" Ruu or the the Latest RUU, then the unlock will work.
I did the HTCDev and unlocked it went to thread on downgrade from 1.5 hboot to 1.4 tried that and it did not work. I went to try the wire trick and this is what I get when I try to use the controlbear. the phone connects and goes through process but says the following...
======== ControlBear 0.6 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....but device has no root!!
Press ENTER to exit.....
Any help would be helpful I have tried superuser but wont install, tried rootevo3dnew, temproot sensation Ect. everything says I need to be rooted.
I am running stock rom that shipped with phone and yes I did updates. I am Sprint CDMA 2.17 rom shipped, 1.5 Hboot. I have flashed roms and modded before but dont consider myself to be advanced. I have done flashing and installing roms with my old HTC Touch pro2 but alot easier on touch pro2 LOL... Please point me in the correct place I have beeen all over from this thread to that one and back and forth and yes I have search threads and I have tried them but still come back to the one with wire trick.. I am 1.5 with S-ON
inkjammer said:
I did the HTCDev and unlocked it went to thread on downgrade from 1.5 hboot to 1.4 tried that and it did not work. I went to try the wire trick and this is what I get when I try to use the controlbear. the phone connects and goes through process but says the following...
======== ControlBear 0.6 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....but device has no root!!
Press ENTER to exit.....
Any help would be helpful I have tried superuser but wont install, tried rootevo3dnew, temproot sensation Ect. everything says I need to be rooted.
I am running stock rom that shipped with phone and yes I did updates. I am Sprint CDMA 2.17 rom shipped, 1.5 Hboot. I have flashed roms and modded before but dont consider myself to be advanced. I have done flashing and installing roms with my old HTC Touch pro2 but alot easier on touch pro2 LOL... Please point me in the correct place I have beeen all over from this thread to that one and back and forth and yes I have search threads and I have tried them but still come back to the one with wire trick.. I am 1.5 with S-ON
Click to expand...
Click to collapse
Ok, let's make sure we know where you are at to start with. When you use the vol and power button to boot to fastboot, does the phone show "unlocked". If not, I think you need to do the htc method again. I have not kept up recently, but I am not sure there is any method other than the HTC method that works every time for 1.5. I have used the HTC method on two phones without a problem, so that is the method I use.
Once you get that far, I used adb to push or flash the twrp image into the recovery section of the phone. Then you should be able to flash superuser via the install menu of twrp. There are threads that have detailed explanations on how this is done.
Yea, I had a bit of a learning curve from my TP2 also, but love this phone!
sonza said:
Ok, let's make sure we know where you are at to start with. When you use the vol and power button to boot to fastboot, does the phone show "unlocked". If not, I think you need to do the htc method again. I have not kept up recently, but I am not sure there is any method other than the HTC method that works every time for 1.5. I have used the HTC method on two phones without a problem, so that is the method I use.
Once you get that far, I used adb to push or flash the twrp image into the recovery section of the phone. Then you should be able to flash superuser via the install menu of twrp. There are threads that have detailed explanations on how this is done.
Yea, I had a bit of a learning curve from my TP2 also, but love this phone!
Click to expand...
Click to collapse
I am unlocked I did the HTC Dev and unlocked it. I have a stock rom (the one shipped on phone) all I have done is unlock it... I did try the controlbear and got what I posted on last post. I am Hboot 1.5 S-ON and stock rom is 2.17.651.5 HTC Sense 3.0 ANDROID Ver. 2.3.4... Like I said all I have done is Unlock and installed TWRP 2.2 and created a restore point and created a recovery and backed up my phone. All through Goo Manager. That is all I have done.
inkjammer said:
I am unlocked I did the HTC Dev and unlocked it. I have a stock rom (the one shipped on phone) all I have done is unlock it... I did try the controlbear and got what I posted on last post. I am Hboot 1.5 S-ON and stock rom is 2.17.651.5 HTC Sense 3.0 ANDROID Ver. 2.3.4... Like I said all I have done is Unlock and installed TWRP 2.2 and created a restore point and created a recovery and backed up my phone. All through Goo Manager. That is all I have done.
Click to expand...
Click to collapse
In my post Ive included a flashable SuperSU zip. What youll need to do is boot to recovery and install this zip. Then reboot. You should have superuser access then.
Still learning this forum so excuse any errors I make. I've spent the last 10 hours trying to fix the mess I created on my wife's Evo 3d. I was able to root my phone and it was relatively easy so I tackled hers as well and have gotten a bootloop I cannot figure out, 10 hours later. I'm on hboot 1.5. I unlocked the phone (using a pretty reliable video), loaded 4EXT Recovery then tried to load roms. Everything worked fine until the rom-loading portion. Since then, the phone loops, but once or twice it made it all the way to the main screen and before I could slide the ring, a read error message appeared next to the bars of service then the phone just completely reboots. Right now, the only thing I can get into is the bootloader and the clockworkmod v4.0.1.4, somehow I lost my 4EXT Recovery. I'm stuck and in dire straights as my wife is going out of town and will KILL me if I don't fix her phone. Please help! BTW, somehow I managed to NOT back anything up (stupidity on my part). Will I be able to get this thing back to stock at least or is it now a paperweight?
user22410 said:
Still learning this forum so excuse any errors I make. I've spent the last 10 hours trying to fix the mess I created on my wife's Evo 3d. I was able to root my phone and it was relatively easy so I tackled hers as well and have gotten a bootloop I cannot figure out, 10 hours later. I'm on hboot 1.5. I unlocked the phone (using a pretty reliable video), loaded 4EXT Recovery then tried to load roms. Everything worked fine until the rom-loading portion. Since then, the phone loops, but once or twice it made it all the way to the main screen and before I could slide the ring, a read error message appeared next to the bars of service then the phone just completely reboots. Right now, the only thing I can get into is the bootloader and the clockworkmod v4.0.1.4, somehow I lost my 4EXT Recovery. I'm stuck and in dire straights as my wife is going out of town and will KILL me if I don't fix her phone. Please help! BTW, somehow I managed to NOT back anything up (stupidity on my part). Will I be able to get this thing back to stock at least or is it now a paperweight?
Click to expand...
Click to collapse
Your not bricked by any means. And Im going to guess you tried to boot an ICS rom.. dont. They dont work with hboot 1.5. If you really want to go back to stock run the 2.17 RUU and youll be back to where you started. Another option is to download a GB rom and flash that. Not ICS. If your able to get to the bootloader than you can still load up 4ext recovery so you can flash the GB rom.
Edit: some hboot 1.5 users are lucky and can flash them if they used the correct VM firmware but majority of users have problems.
NineInchNails said:
Your not bricked by any means. And Im going to guess you tried to boot an ICS rom.. dont. They dont work with hboot 1.5. If you really want to go back to stock run the 2.17 RUU and youll be back to where you started. Another option is to download a GB rom and flash that. Not ICS. If your able to get to the bootloader than you can still load up 4ext recovery so you can flash the GB rom.
Edit: some hboot 1.5 users are lucky and can flash them if they used the correct VM firmware but majority of users have problems.
Click to expand...
Click to collapse
Thanks, I just tried flashing a rom that has taken it back to stock but I'm still in the bootloop. Should I stop flashing and simply locate the RUU?
22410,
It sounds like the kernel did not flash correctly with 4ext Recovery (next time, make sure u indicat S-on in its settings). I'm not sure if you were just stock 2.17 rooted or not, but use 7zip on your pc to open & extract/copy out the "boot.img" file from the rom, zip, etc you were using and copy it to your fastboot pc folder. Still have the Cwm 4.0.1.4 recovery.IMG file there too right (or the 4ext recovery.img file)? Ok...
- put phone in fastboot usb mode
From PC's fastboot command prompt type:
- " fastboot flash boot boot.img "
(this will reflash the kernel/boot image extracted from a rom)
If your recovery is screwed up:
- " fastboot flash recovery YourRecoveryFilename.img "
(ie: cwm_4.0.1.4_recovery.img or recovery.img, etc as listed in fastboot folder, to reflash a recovery to your phone).
With S-on, to properly enter a recovery for flashing ANYTHING you must:
- " fastboot boot YourRecoveryFilename.img "
(doesn't apply if using 4ext's Smartflash or TWRP's Dumlock settings. But you must have a bootable android OS/kernel first, once the flash is screwed it won't work).
If u have a Sprint CDMA EVO3D/HTC Unlocked & S-on (not Jbear s-Off), then the guide in my signature has more info.
Edit: as NIN said you will likely have problems flashing ICS roms with S-on (hboot version doesn't matter). If u are still unlocked & have a working recovery u can flash any gb Rom successfully after wiping system, data, & cache (or run superwipe zip). Meanrom GB v4.5 recommended.
Sent from my "Up all night, Sleep all day" EVO3D!
Building on the Framework of my other apps, I present to you my easy, quick and efficient Rooting solution for ANY HTC Device.
Check out the link for more info and Download:
http://forum.xda-developers.com/showthread.php?t=1870652
Sent from my HTC Desire S using Tapatalk 2
this works for all htc phones?what about if my bootloader is unlocked but not rooted.
Sent from my HTCEVOV4G using xda premium
ddurb said:
this works for all htc phones?what about if my bootloader is unlocked but not rooted.
Sent from my HTCEVOV4G using xda premium
Click to expand...
Click to collapse
Try it and see!
Need some help!
I decided to give this a try since it sounds like it has some potential to help get users rooted from stock configurations, or after flashing an OTA or RUU, even though I have been S-OFF via JuopunutBear for a while now. I figured I would try the rooting with an insecure boot.img first since that works for S-OFF, but got an error saying I didn't have the right boot.img installed. I had just flashed the latest Sprint ICS RUU.exe from Windows and wanted to see how this tool would work in that scenario.
So since it wanted a boot.img that I didn't have, I tried the universal exploit option but that gave me an error at the Windows level. The phone rebooted into recovery and I had to pull the battery and reboot into the stock ROM, which was fine.
I have attached screenshots of the info I got when I first started the app, the error I got when I tried to root with the exploit (I'm on Windows 7 Ultimate, Service Pack 1) and a text file containing the contents of the message in the scrollable details text box.
I'm also curious what bootloader gets flashed if that option is selected.
Please advise.
Edit: Just noticed that the version went from 1.1.10 that I downloaded yesterday to 1.1.12 today so I will reload the RUU and try that version.
ramjet73
ramjet73 said:
I decided to give this a try since it sounds like it has some potential to help get users rooted from stock configurations, or after flashing an OTA or RUU, even though I have been S-OFF via JuopunutBear for a while now. I figured I would try the rooting with an insecure boot.img first since that works for S-OFF, but got an error saying I didn't have the right boot.img installed. I had just flashed the latest Sprint ICS RUU.exe from Windows and wanted to see how this tool would work in that scenario.
So since it wanted a boot.img that I didn't have, I tried the universal exploit option but that gave me an error at the Windows level. The phone rebooted into recovery and I had to pull the battery and reboot into the stock ROM, which was fine.
I have attached screenshots of the info I got when I first started the app, the error I got when I tried to root with the exploit (I'm on Windows 7 Ultimate, Service Pack 1) and a text file containing the contents of the message in the scrollable details text box.
I'm also curious what bootloader gets flashed if that option is selected.
Please advise.
ramjet73
Click to expand...
Click to collapse
You need htcdev unlock so you can get Su. Then it should work
Sent from my PG86100 using Tapatalk 2
VictoriousShooter said:
You need htcdev unlock so you can get Su. Then it should work
Click to expand...
Click to collapse
With S-OFF? That's strange, since the OP says that both options work with S-OFF. Also, I couldn't find any mention of htcdev unlock in either the OP or the application when it was running.
I'm not going to htcdev unlock since my bootloader is locked after JuopunutBear and I don't want to have to deal with the ***RELOCKED*** status. I guess I could try flashing a custom bootloader after running the RUU that will allow the fastboot commands, but that can only be done by S-OFF users and by the time that's done it's probably faster to go into fastboot and flash the custom recovery, then the superuser .zip or a rooted ROM from recovery.
I'm not sure where this tool fits exactly, but it sounds like it's mostly useful for people that have done the htcdev unlock but are still S-ON and want to root more easily. If that's the case, they can run this, then boot into Android and flash a custom recovery from an app like 4EXT or Flash Image GUI without having to use fastboot for either superuser or the recovery. Is that the gist of it?
BTW, my results with version 1.1.12 are attached. I got farther this time, but it failed on the temp root.
ramjet73
The errors seem to be causing confusion. If everything else says okay but the Universal Exploit says Failed then this means the exploit has been patched on the stock Rom you are trying to run it on.
Also only rooting via insecure boot.img requires s-off. Universal root will work with s-on if the exploit hasn't been patched.
Sent from my HTC Desire S using Tapatalk 2
lyriquidperfection said:
The errors seem to be causing confusion. If everything else says okay but the Universal Exploit says Failed then this means the exploit has been patched on the stock Rom you are trying to run it on.
Also only rooting via insecure boot.img requires s-off. Universal root will work with s-on if the exploit hasn't been patched.
Click to expand...
Click to collapse
So in other words, this tool won't work using the "universal exploit" (in quotes because I guess it's not really universal) on the official Sprint ICS build (2.89.651.2) for the Evo 3D, which is what I flashed via RUU.exe right before running it, regardless of the S-ON or S-OFF status? Would it work with an "insecure boot.img" if we are S-OFF and if so how would we set that up?
Assuming someone wanted to root the latest Sprint GB build (2.17.651.5) for the Evo 3D, what advantages does this tool provide over flashing a custom recovery and superuser .zip file from fastboot on a PC?
I'm not trying to be negative, just want to be clear on when someone on our device would benefit from using it.
ramjet73
ramjet73 said:
So in other words, this tool won't work using the "universal exploit" (in quotes because I guess it's not really universal) on the official Sprint ICS build (2.89.651.2) for the Evo 3D, which is what I flashed via RUU.exe right before running it, regardless of the S-ON or S-OFF status? Would it work with an "insecure boot.img" if we are S-OFF and if so how would we set that up?
Assuming someone wanted to root the latest Sprint GB build (2.17.651.5) for the Evo 3D, what advantages does this tool provide over flashing a custom recovery and superuser .zip file from fastboot on a PC?
I'm not trying to be negative, just want to be clear on when someone on our device would benefit from using it.
ramjet73
Click to expand...
Click to collapse
Ramjet, I have tried it too and end up where you are at. I have done the HTC unlock too.
Can someone show the step by step because I hate to presume I'm doing it right.
I have the phone set and on home screen. I run the program and fails.
I reboot the fone into the boot screen (pwr/vol dn) and select fastboot (pwr press once) then the program works and then fails at the temp thingy..
Hello all, I tried searching but if I missed the thread please point me to it. I was able to unlock the bootloader using HTC Dev but I cant seem to install TWRP. Am I missing a step or something? I am running an HTC Evo 4G LTE on 3.17. I tried putting the PJ75IMG.zip in the root of the sd card but when restarted in the bootloader it read it and said main version is older. I tried using goomanager to download and install but that didnt work either. Am i doing something wrong here? Thanks in advance guys (and girls)!
fastboot flash it PJ75IMG.zip will only work if you are S-OFF
Put the .img file in the folder you are using to run the commands from.
fastboot flash recovery nameofrecovery.img
OK. So fastboot is the best method. Then I can install super user correct? I dont HAVE to install a ROM if i dont want to correct? I can just run stock root? If I wanted to install a ROM would I need to be S-OFF? or could I install one while still being S-ON? It has been quite some time since I rooted a phone. Last phone was the Samsung Epic 4G. What a terrible phone. Thanks and sorry for so many questions.
quattroa430 said:
OK. So fastboot is the best method. Then I can install super user correct? I dont HAVE to install a ROM if i dont want to correct? I can just run stock root? If I wanted to install a ROM would I need to be S-OFF? or could I install one while still being S-ON? It has been quite some time since I rooted a phone. Last phone was the Samsung Epic 4G. What a terrible phone. Thanks and sorry for so many questions.
Click to expand...
Click to collapse
I personally use fastboot to install twrp then when you want/need to update twrp you can fastboot flash again or use goomanager from the playstore.
You can install SuperSU and run stock rooted or flash a custom rom which has superuser added
As for flashing roms you can flash them while s-on it's just more work because you have to fastboot flash the kernel/boot.img then flash the rom.
I always recommend S-OFF as it will save you the extra steps in flahing roms and also if you mess something up you can flash an older RUU if the most current RUU is not available.
@FinZ28 has a great guide explaining how to flash the kernel/boot.img
OK, so now the question becomes what method for S-OFF should I use? I would like to be able to make it look like I never rooted the phone if need be if at all possible. I heard good things about rumrunner for 3.17. am i correct that this would be the best method or is there a better one? again sorry its been too long and this is my first HTC root.
quattroa430 said:
OK, so now the question becomes what method for S-OFF should I use? I would like to be able to make it look like I never rooted the phone if need be if at all possible. I heard good things about rumrunner for 3.17. am i correct that this would be the best method or is there a better one? again sorry its been too long and this is my first HTC root.
Click to expand...
Click to collapse
Since you are on 3.17 rumrunner is the only method you can use
OK so first install TWRP then SU then S-OFF? also i factory reset my phone the other day and now on some apps I have this weird menu bar at the bottom. it happens on my facebook app and bank app. it doesnt show up in Kik or play or sms apps. any ideas? i would like to remove that
quattroa430 said:
OK so first install TWRP then SU then S-OFF? also i factory reset my phone the other day and now on some apps I have this weird menu bar at the bottom. it happens on my facebook app and bank app. it doesnt show up in Kik or play or sms apps. any ideas? i would like to remove that
Click to expand...
Click to collapse
Yes unlock your bootloader if you have not already
Install twrp
Flash SU
Then S-OFF(make sure you read all the pre-requisetes before starting rumrunner
As fo the weird menu it may disappear if you flash a custom rom
Ok so I came across another issue. I cant seem to get busybox to install. I would like to install cyanogenmod 10 and qbking mentions needing s-off to do so. Is that correct? It is a bit of a pain being on 3.17 but I guess there isnt much I can do. Any advice for installing busybox? Thanks again
I successfully installed Busybox on 3.17 last night. As far as having to be S-off to flash CM, no, you don't have to be, but it makes life easier. Hit the top link in my sig and read my Hboot guide if you haven't already done so.
Sent from my HTC EVO 4G LTE
I read your hboot guide. Very informative. Rumrunner requires busybox and for whatever reason I cannot install busybox. Could you possibly eexplain what choices you made that worked? I tried installing to bin and xbin. Should I install to a custom location instead? If so where should I? I would like to be s-off and have cyanogen lol. Thanks again guys!
quattroa430 said:
I read your hboot guide. Very informative. Rumrunner requires busybox and for whatever reason I cannot install busybox. Could you possibly eexplain what choices you made that worked? I tried installing to bin and xbin. Should I install to a custom location instead? If so where should I? I would like to be s-off and have cyanogen lol. Thanks again guys!
Click to expand...
Click to collapse
I'm not really sure what to tell you since I was already S-off when I installed it. Where did you read that it was required prior to running Rumrunner?
Sent from my HTC EVO 4G LTE
It was on the pocketables website. search "rumrunner HTC EVO 4g LTE" everytime I seem to try to install busybox my phone crashes.
Are you running just the stock rooted factory rom?
You could try Captain_Throwbacks 3.17 rooted rom or SharkieRom 3.17
Try this. Its a TWRP flashable zip of the latest Busybox (v1.20.2). See if that straightens things out with your issue. Make sure you have a backup handy just in case.
https://www.dropbox.com/s/g16xuqbzbmzz8yz/busybox-signed.zip
You can use a file manager like Root Explorer and go to /system/xbin/ and look to make sure you see the Busybox file. If it's there you're good to go:thumbup: (I did not develop the Busybox file-I simply took the file and make it into a flashable zip. Big thanks to Rootlinux for showing me how it's done).
Sent from my HTC EVO 4G LTE
FinZ28 said:
Try this. Its a TWRP flashable zip of the latest Busybox (v1.20.2). See if that straightens things out with your issue. Make sure you have a backup handy just in case.
https://www.dropbox.com/s/g16xuqbzbmzz8yz/busybox-signed.zip
You can use a file manager like Root Explorer and go to /system/xbin/ and look to make sure you see the Busybox file. If it's there you're good to go:thumbup:
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Worked like a charm. Busybox is installed right where you said it should be. Now to run rumrunner and gain s-off. Thank you guys for all the help and support thus far!
quattroa430 said:
Worked like a charm. Busybox is installed right where you said it should be. Now to run rumrunner and gain s-off. Thank you guys for all the help and support thus far!
Click to expand...
Click to collapse
Glad it worked for you:thumbup:
Sent from my HTC EVO 4G LTE
S-OFF Issue
Ok now I can't seem to gain S-OFF using rumrunner. I downloaded the correct version for the EVO 4G LTE and I am running native Ubuntu 13.10 32bit. It works for a while until it gets to the pouring stages
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
YesDo you understand the implications of this warning?
(Yes/No)
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
yes
Type 'Yes' or 'No'
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (21/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (21/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)...
WTF: What are you doing?
Idk what I am doing wrong here. I couldnt even get it to work right using windows so I had to break out the laptop.
It gets to that point every time then fails and reboots the phone.
Software version: 3.17.651.4
Android Version: 4.1.1
Kernal Version: 3.4.10-gf5d846c
Is there anything else needed to help figure this out? Tis getting a wee bit frustrating. Can I S-OFF off if i flash cyanogen or any other rom?
Tried running Captain_Throwbacks stock rooted 3.17 and got the same result at the same exact point while running rumrunner. Going to try Sharkie next. Any tips are greatly welcomed!
Don't have much to offer since I haven't used Rumrunner. Having said that, make sure you're using a USB 2.0 port and not 3.0, and that you're using a fairly stock Sense ROM. Also make sure that you're phone is recognized with both ADB & Fastboot. Seems most of the issues I've seen have to do with the connection. If it fails, try try again. You also might want to check out the Rumrunner thread in original development.
Just a thought, but have you looked at your bootloader and made sure that you're still S-on? Reason I ask is because on Moonshine the "WTF: What are you doing?" message actually meant that the process was successful. Not sure if Rumrunner is the same.
Sent from my HTC EVO 4G LTE
Please help. I have unlocked this phone through HTC Dev. I have flashed a custom recovery. Somewhere through this process, the original installation of the factory rom from VM was deleted. That doesn't bother me because I was never going back to it anyway, but If I had it right now, I wouldn't be here. I have tried to use the RUU exe in fastboot and the RUU zip in recovery from here. Neither will install, exe throws errors and the zip returns [bad]. I have also tried the [ROM] NegaLite-BluRom-JCFunk | 2.95 | Sprint/VM | Sense/Apex/Nova | 03/25/2014. This eventually installed, but will not boot even with installing boot.img separately. I followed all directions to the best of my ability, but by no means am I saying I did correctly, but I am pretty sure I did. So to recap - I have whats in the title, but no rom whatsoever installed that can be accessed. Any takers?
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Click to expand...
Click to collapse
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
oD33z said:
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
D33z
Click to expand...
Click to collapse
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Click to expand...
Click to collapse
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
oD33z said:
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
Click to expand...
Click to collapse
here's the thread
http://forum.xda-developers.com/showthread.php?t=2831444
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I am great with linux, but was under the assumption it needed to be burned to cd and that USB was not an option, please advise if not the case. I have read a ton and I remember reading about Unknownforce, but cant remember if thats the case or not.
Off topic: I learned from you that it has to be locked to go stock, but does it need to be unlocked to flash your rom or locked as well?
Unlocked for custom, locked for stock.
Here is unknownforce ultimate tool,
there was a live cd version made for windows users scared of linux.
I use tiny core linux for this, Ubuntu tries to mount all the partitions and you only have a 5 second window when they are writeable. I have used Ubuntu, at first, but preferred tinycore.
But first you are going to need to get stock.zip to install.
http://forum.xda-developers.com/showthread.php?t=1653777
I would do fastboot boot recovery.img
Then install negalite, so atless you can boot the phone
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
here is 4ext recovery I would use this one first until you get used to things, best recovery for 3d.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
oD33z said:
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
Click to expand...
Click to collapse
did you fastboot boot?
There are several custom recoveries out there.
Here is thread for 4ext
http://forum.xda-developers.com/showthread.php?t=1408936
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
What I meant was, in your opinion, is the 4ext a better recovery than the unofficial TWRP?
During the install of Negalite at the point of -Setting Up Kernel Over-Clock Settings
under this it reads: assert failed: write_raw_image("/tmp/newboot.img","boot")
Is this a red flag of something not going right in any way?
After this I click Next>Recovery>Wipe Dalvik>Reboot and it boots into Fastboot. Whats happening at this point?
Since I am basically starting from scratch and the end goal is to have a kitkat rom and possibly S-OFF(if its a must to do so).
What all needs to be done as far as formatting, tweaks, or anything else to achieve the best performance, space, or anything you can think of?
Thats if you dont mind sharing. I appreciate your time and if I can be of service to you in any way, I will.
I am currently on the 4ext recovery with 1GB sd-ext 0 swap and formatted Ext4.
fastboot boot recovery.img
flashrom.zip from recovery
reboot, wipe dalvik, reboot
Negalite.zip installed with no errors whatsoever.
Thank You.
Beautiful smooth running rom btw.
Does all that above sound like I did the right things as for setting up and installing?
4ext is most stable, the unofficial has new features like f2fs and selinux, but 95% stable.
fastboot boot recovery.img is an old work around, also used to flash boot.img with fastboot. That is ok with roms that include a whole boot.img but roms like mine use a dynamic boot.img. Basically the installer makes the boot.img using your choices.
From what I know about Kitty kat I think you need to downgrade hboot or be s-off. Not sure I've stayed on ics for stability because I still use this phone. Also there is a new version of negalite on svn, just takes hours for me to upload a zip version.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Revision 7
Are you sure this is the latest?
oD33z said:
Revision 7
Are you sure this is the latest?
Click to expand...
Click to collapse
Lol, yes since I updated it a few weeks ago
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
I should have worded that different really, the revision numbers threw me, I honestly was just making sure I was in the right place. 48mb smaller, anything stripped?
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Click to expand...
Click to collapse
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
oD33z said:
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
Click to expand...
Click to collapse
Here. Try this
https://www.androidfilehost.com/?fid=23578570567720169
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer