So while in process of s-off once I got to the part when you "fastboot oem rebootRUU" that went through. But right after trying to flash a zip im stuck looking at the blk HTC screen. I was given a "<Failed <remote: 99 unknown fail>". Now its just stuck.
I've been trying to figure out what happened but just have no where else to turn. Please lend a hand.
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
aarsyl said:
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
It's not a full RUU in the normal sense. It's the one for Facepalm.
To the OP, did you gain SuperCID prior to running those commands? If not, then the process will fail. You should simply be able to hold the power button down & reboot your phone. Also, as stated above, list your device info so we can make sure you're using the right S-off exploit.
Sent from my HTC EVO 4G LTE
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
z3r0t0l0rEnCe said:
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
Click to expand...
Click to collapse
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
aarsyl said:
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
Click to expand...
Click to collapse
This is odd to me, because I ran rumrunner at least 3 times using just my stock ROM (no custom kernel or anything), and it worked fine every time. I guess the new version of rumrunner added some limitations to make it more generic.
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
z3r0t0l0rEnCe said:
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
Click to expand...
Click to collapse
No, don't. If it fails, don't force it. Reflash TWRP 2.6.3 (not the kit kat version), and try to flash again.
@Captain_Throwback: Yes, I didn't remember needing a custom kernel when I used Dirty Racun, but rumrunner needs it now. Keep in mind that rumrunner isn't for this device exclusively. Maybe that's the purpose of the custom kernel.
i'd wager you're trying to flash files that aren't recovery flashable, then lying to the people who are trying to help you.
i got it running again using capt stock rooted rom. attempting rumrunners s-off again now that i got this part working.
Are you using a custom kernel?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
now s-off and updated rumrunners hboot. now onto flashing roms finally.
Thank you all that helped me with my stupidness and not reading directions.
Last post. I can't say it enough that you must read read read when it comes to directions. If I would of followed directions as directed I would of never ran into the issues I did. It was a learning experience.
One thing for sure that I took from this experience is adb and directions. I've learned a lot in the last 24hrs alone.
I'd like to thank Capain_throwback and everyone in the irc for the help and you all here that assisted me.
Sent from my EVO using XDA Premium 4 mobile app
Related
Forgive me for starting a new thread; I've utilized the search here and some Google-fu, but still have questions for the community.
I recently upgraded to an HTC Rezound from a Thunderbolt, and have accepted the stock OTA ICS update last weekend.
This has not stopped me from Rooting the device, however. Using an All-In-One Toolkit downloaded here, I was able to Unlock the Bootloader, Install custom Recovery (ClockWorkMod Touch), and have SU flashed. All signs point to root, but I would like to know a few things.
- Is there currently any method of acquiring S-OFF, other than the juopunutBear "Wire Trick"? It sounds incredibly risky, and I feel a bit hesitant to try it connecting pins on the back of my phone with insulated wire... I would like to have S-OFF, in case I want to roll back using a PH98IMG.zip
After rooting, I noticed that the text ****TAMPERED**** appears above the UNLOCKED line when I power on into HBOOT. Is this normal? Or have I messed things up? The best answer I have gleaned so far is from another device's forum, and that this simply indicates that I have root.
Would love to hear some feedback. This is my 5th Smartphone starting with the G1, and I have rooted every single one within days. Only the Rezound seems to be the trickiest for me.
Let me know your thoughts, thanks.
The hboot says tampered after you install a custom recovery so that's normal. I was the same way about s-off it seemed to risky and complicated but in all honesty it is very simple. It's our only way to get s-off and the main thing is getting the timing right for the wire trick. I got it on my second try. I would say just read up on it and gain as much info until you feel comfortable to do it.
Sent From My HTC Rezound
big_mike_2k6 said:
The hboot says tampered after you install a custom recovery so that's normal. I was the same way about s-off it seemed to risky and complicated but in all honesty it is very simple. It's our only way to get s-off and the main thing is getting the timing right for the wire trick. I got it on my second try. I would say just read up on it and gain as much info until you feel comfortable to do it.
Sent From My HTC Rezound
Click to expand...
Click to collapse
Thanks, that confirms a number of suspicions. & As I understand it, I need to be S-OFF in order to flash a custom ROM, correct?
And this is due to the fact that I not only have to flash the ROM in recovery, but also flash a Kernel through HBOOT?
I want to start flashing custom ROMs, but in the meantime, I'm fairly happy with rooted ICS. Got Google Now working, removed 'App Associations' menu, and removed the VZW crapware, so root is working out rather well
deadsoulboy said:
Thanks, that confirms a number of suspicions. & As I understand it, I need to be S-OFF in order to flash a custom ROM, correct?
And this is due to the fact that I not only have to flash the ROM in recovery, but also flash a Kernel through HBOOT?
I want to start flashing custom ROMs, but in the meantime, I'm fairly happy with rooted ICS. Got Google Now working, removed 'App Associations' menu, and removed the VZW crapware, so root is working out rather well
Click to expand...
Click to collapse
You don't need to be s-off to flash a Rom but you do need to flash the kernel separate in hboot when you're s-on. When you're s-off you don't have to. I myself usually stay fairly close to stock with a few tweaks here and there and of course Verizons crap long gone.
Sent From My HTC Rezound
One more thing... Given my software version, etc, if I S-OFF now, would I bork my device?
Also, it looks like at the unlimited.io site, there is only a Windows version of juopunutbear for Gingerbread, and early ICS versions. My phone's software is on version is 3.14.605.12; does this mean I should abandon attempting to S-OFF ?
deadsoulboy said:
One more thing... Given my software version, etc, if I S-OFF now, would I bork my device?
Also, it looks like at the unlimited.io site, there is only a Windows version of juopunutbear for Gingerbread, and early ICS versions. My phone's software is on version is 3.14.605.12; does this mean I should abandon attempting to S-OFF ?
Click to expand...
Click to collapse
No you'll be fine doing it on your current version. You can use the file from the unlimited.io site for the 3.14.605.05 ics leak it works with the official ics update.
Sent From My HTC Rezound
i know clockwork will bork your device im not sure if the touch version does the same thing.
I recommend installing Amon Ra recovery or TWRP.
If i helped thanks me
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
Hey guys i gota semi bricked EVO LTE on the 3.16 SW i was wondering if anyone can help me fix. I tried to root it and thats what caused this issue. I did the bootloader unlocked, loaded TWRP recovery, then installed SU, then it wouldn't turn on, would only flash to sprint screen.
I have tried to to a full wipe / factory - didn't work
i have tried to load the 3.15 RUU - does not work (it just shows loading the rom forever)
i have tried to load it through fastboot via Ulimited.IO (it just freezes during the loading of the SW)
what else can i try? I seems like everytime the phone tries to take a ROM it will just not respond.
thanks
OK your on the latest firmware I think 3.16 and if your s-on that means you have the new touch panel driver which limits what ROMs will work on your device.
You need to download a ROM with a s-on installer included or pull the boot IMG from the ROM and flash via fast boot because you can't flash kernels easily when your S-ON .You also will need a rom that's compatible with the latest fw. AFAIK most of the sense ROMs will be good to go, I really don't know which ones cause I'm s-off and don't have the tp driver problem.
If you need more info there's s thread stickied in Q&A called "don't panic" that will answer most of questions
Once your up and running you should go about getting S-Off.
SENT FROM MY LTEVO
corcgaigh said:
OK your on the latest firmware I think 3.16 and if your s-on that means you have the new touch panel driver which limits what ROMs will work on your device.
You need to download a ROM with a s-on installer included or pull the boot IMG from the ROM and flash via fast boot because you can't flash kernels easily when your S-ON .You also will need a rom that's compatible with the latest fw. AFAIK most of the sense ROMs will be good to go, I really don't know which ones cause I'm s-off and don't have the tp driver problem.
If you need more info there's s thread stickied in Q&A called "don't panic" that will answer most of questions
Once your up and running you should go about getting S-Off.
SENT FROM MY LTEVO
Click to expand...
Click to collapse
thanks for the info. So i need to get a rom with s-on installer and flash it via fastboot flash zip xxxxxx.zip? But i'm not even sure if i'm rooted. I did install the SU in there, it said okay, but now i cant access the recovery. only fastboot. would this damage the phone in anyways?
thanks
right now its showing
**tampered***
** relocked **
** security warning**
Jewel PVT SHIP S-ON RL
HBOOT - 2.09
RADIO - 1.12.11.1210
OpenDSP - V31.1.0.45.0815
emmc- Boot
oct 18 2012
I just tried to flash MeanBean v309 on it via fastboot and it didn't work? is it because the file is too big? I am pretty sure the bean mean is a S-on ROM
Looks like u need to unlock again. Use the same command as the last time
"Fast boot OEM unlock" or whatever it is. Flash twrp recovery thru fast boot. Once you have twrp installed flash a rooted ROM to gain root.
SENT FROM MY LTEVO
corcgaigh said:
Looks like u need to unlock again. Use the same command as the last time
"Fast boot OEM unlock" or whatever it is. Flash twrp recovery thru fast boot. Once you have twrp installed flash a rooted ROM to gain root.
SENT FROM MY LTEVO
Click to expand...
Click to collapse
took your advice, re-unlocked it and installed TWRP recovery on it, and now i get recovery, but i cant use it because the touch screen does not work so i'm in the process of trying to find a CMW recovery instead and try to install a newer rom.
truwrxtacy said:
took your advice, re-unlocked it and installed TWRP recovery on it, and now i get recovery, but i cant use it because the touch screen does not work so i'm in the process of trying to find a CMW recovery instead and try to install a newer rom.
Click to expand...
Click to collapse
Do not use CMW. It was abandoned a long time ago for our phones. Something about it screwing up partitions. Install a new version of TWRP. 2.4 or higher. And Venom rom has an s-on installer for sure. Other roms might have one but I'm not sure which ones. Stay away from CMW.
The s-on installer is just an installer added to the ROM zip so that you don't have to flash the boot.img seperately. Just get a working version of TWRP and flash Venom (or other s-on friendly rom). That should work.
tilltheend714 said:
Do not use CMW. It was abandoned a long time ago for our phones. Something about it screwing up partitions. Install a new version of TWRP. 2.4 or higher. And Venom rom has an s-on installer for sure. Other roms might have one but I'm not sure which ones. Stay away from CMW.
Click to expand...
Click to collapse
ahh okay thanks, i'll give it a shot and report back.
truwrxtacy said:
ahh okay thanks, i'll give it a shot and report back.
Click to expand...
Click to collapse
thanks guys so i got it working! i appreciate everyones help! I ended up loading a new TWRP recovery, and loading the new Meanbean and it works now.
I have one last question, does this mean i can only install roms compatible with 3.16 now? The only reason i went through all of this was because i wanted ICS on it. The new JB diag drivers dont work, and the only way i can make the diag drivers work is to downgrade to ICS. If i try to downgrade will i mess it up again?
thanks
truwrxtacy said:
thanks guys so i got it working! i appreciate everyones help! I ended up loading a new TWRP recovery, and loading the new Meanbean and it works now.
I have one last question, does this mean i can only install roms compatible with 3.16 now? The only reason i went through all of this was because i wanted ICS on it. The new JB diag drivers dont work, and the only way i can make the diag drivers work is to downgrade to ICS. If i try to downgrade will i mess it up again?
thanks
Click to expand...
Click to collapse
Yes, you are stuck on 3.16 roms. Anything below and your touchscreen won't work. I highly recommend going for s-off. Makes everything so much easier. The only other option is to use babyracun from unlimited.io then ruu to 3.15. But if you're doing that you might as well go for s-off.
tilltheend714 said:
Yes, you are stuck on 3.16 roms. Anything below and your touchscreen won't work. I highly recommend going for s-off. Makes everything so much easier. The only other option is to use babyracun from unlimited.io then ruu to 3.15. But if you're doing that you might as well go for s-off.
Click to expand...
Click to collapse
Agreed. I did babyracun and then Facepalm afterwards. Worked great on Windows 7 64bit of which isn't supported by the developers, of course
Delakit said:
Agreed. I did babyracun and then Facepalm afterwards. Worked great on Windows 7 64bit of which isn't supported by the developers, of course
Click to expand...
Click to collapse
Which is what this guy should do since he doesn't have ubuntu and probably doesn't want to use a live disc.
thanks alot guys, i was not aware of the babyracoon. I'll give that a shot.
thanks
i have a question about baby racoon, as it does not have a separate thing for it.
So do i download baby racoon and run all the adb commands, and then run face palm, then ruu?
or do i download baby racoon and run all the adb commands, and ruu then face palm?
sorry i'm a noob
truwrxtacy said:
thanks alot guys, i was not aware of the babyracoon. I'll give that a shot.
thanks
i have a question about baby racoon, as it does not have a separate thing for it.
So do i download baby racoon and run all the adb commands, and then run face palm, then ruu?
or do i download baby racoon and run all the adb commands, and ruu then face palm?
sorry i'm a noob
Click to expand...
Click to collapse
Do steps 6-9 on unlimited io. That will leave your phone at stock 3.15. Then go and find out what facepalm requires and continue with that.
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