Related
I have a completely stock 3D with hboot 1.5, s-on, software 2.17. I want to gain root access in order to flash custom roms and such.
I saw a walk through on how to do this via HTCdev bootloader. I've also read about downgrading to hboot 1.4 and achieving s-off.
What are the advantages of downgrading to 1.4 and achieving s-off vs. sticking with 1.5 and s-on by using the HTCdev method?
Well fort you want be registered as having messed with your device to prevent a void in your warranty. The others are you can flash without any programs needed to install a kernel also you can flash splash screens. Flashing radios is also a benefit of soff. But soff will allow you to actually brick your device vs having just bootloader unlocked.
Sent from my SPH-D710 using Tapatalk 2
patrao_n said:
Well fort you want be registered as having messed with your device to prevent a void in your warranty. The others are you can flash without any programs needed to install a kernel also you can flash splash screens. Flashing radios is also a benefit of soff. But soff will allow you to actually brick your device vs having just bootloader unlocked.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
So s-off is going to give me more access. Essentially the better option if I'm willing to take the risk?
Everything I've read about downgrading to 1.4 and getting s-off is via Linux... Is there a way to do this from Windows 7 instead?
AmbrosiaLyn07 said:
So s-off is going to give me more access. Essentially the better option if I'm willing to take the risk?
Everything I've read about downgrading to 1.4 and getting s-off is via Linux... Is there a way to do this from Windows 7 instead?
Click to expand...
Click to collapse
not yet...windows devices will not recognize the eMMC in the device...only linux does it,... which is not hard...just download a usb version of linux...run it from your flash drive and it works just fine....did it with my puter successfully ...and yes it is better...like you said though...IF youre willing to take the risk
wloftus said:
not yet...windows devices will not recognize the eMMC in the device...only linux does it,... which is not hard...just download a usb version of linux...run it from your flash drive and it works just fine....did it with my puter successfully ...and yes it is better...like you said though...IF youre willing to take the risk
Click to expand...
Click to collapse
Alright, sounds like a plan. I will probably wait until my roommate gets home. I don't have any spare flash drives lying around
Thank you for your help!
AmbrosiaLyn07 said:
Alright, sounds like a plan. I will probably wait until my roommate gets home. I don't have any spare flash drives lying around
Thank you for your help!
Click to expand...
Click to collapse
Keep this in mind... S-off is great but you can fully permabrick your device with s-off, hard to do but it can be done. S-on blows but I'm pretty sure you can fix anything but a hardware failure with the unbrick method.
AmbrosiaLyn07 said:
Alright, sounds like a plan. I will probably wait until my roommate gets home. I don't have any spare flash drives lying around
Thank you for your help!
Click to expand...
Click to collapse
If I might suggest, take a look at the CD in my signature. There is a guide in post #3. It should help to ease the process a bit.
~co~
wikdNoob said:
Keep this in mind... S-off is great but you can fully permabrick your device with s-off, hard to do but it can be done. S-on blows but I'm pretty sure you can fix anything but a hardware failure with the unbrick method.
Click to expand...
Click to collapse
I'm willing to take the risk. I've done a lot of reading and my roommate is familiar with what he's doing.
Now, I just have to wait for him to come home... I'm tired of waiting, I just want it to be done already!
closeone said:
If I might suggest, take a look at the CD in my signature. There is a guide in post #3. It should help to ease the process a bit.
~co~
Click to expand...
Click to collapse
Thank you so much for your help! I really appreciate it.
AmbrosiaLyn07 said:
I have a completely stock 3D with hboot 1.5, s-on, software 2.17. I want to gain root access in order to flash custom roms and such.
I saw a walk through on how to do this via HTCdev bootloader. I've also read about downgrading to hboot 1.4 and achieving s-off.
What are the advantages of downgrading to 1.4 and achieving s-off vs. sticking with 1.5 and s-on by using the HTCdev method?
Click to expand...
Click to collapse
You don't need to achieve root access to flash ROMs or kernels.....unlocking your bootloader via HTC dev or revolutionary is just fine
My vote to hboot 1.4 S-OFF
mnomaanw said:
You don't need to achieve root access to flash ROMs or kernels.....unlocking your bootloader via HTC dev or revolutionary is just fine
My vote to hboot 1.4 S-OFF
Click to expand...
Click to collapse
Since my roommate is doing it for me (his computers and computer knowledge are way more capable than mine) I let him decide which way he was going to do it. We ended up going with the HTC bootloader unlock.
We got it successfully unlocked through the bootloader but it still doesn't have root access. Like, apps that require root won't work and he can't get anything to flash on it. Suggestions?
AmbrosiaLyn07 said:
Since my roommate is doing it for me (his computers and computer knowledge are way more capable than mine) I let him decide which way he was going to do it. We ended up going with the HTC bootloader unlock.
We got it successfully unlocked through the bootloader but it still doesn't have root access. Like, apps that require root won't work and he can't get anything to flash on it. Suggestions?
Click to expand...
Click to collapse
Do you have a custom recovery installed on it after you rooted htc dev method? Also did you flash superusers on it?
reaper24 said:
Do you have a custom recovery installed on it after you rooted htc dev method? Also did you flash superusers on it?
Click to expand...
Click to collapse
I think he's trying to get a custom recovery on it now (twrp). And he's mentioned something about superuser.
But he seems frustrated like something went wrong :-/
reaper24 said:
Do you have a custom recovery installed on it after you rooted htc dev method? Also did you flash superusers on it?
Click to expand...
Click to collapse
Now he's talking about cwm but doesn't seem to be able to find a file that works.
AmbrosiaLyn07 said:
Now he's talking about cwm but doesn't seem to be able to find a file that works.
Click to expand...
Click to collapse
clockworkmod 4.0.1.4 -------> http://db.tt/hm3wkw1q
clockworkmod touch 5.8.0.2 --------> http://db.tt/yKUegldi
TWRP 1.1.1 -------> http://db.tt/ZrIEWf2B
TWRP touch 2.0 -------> http://db.tt/qHgIUljj
Recoveries versions other than these doesn't seem to work with hboot 1.5
CWM touch have a few bugs in this version , they may have fixed in the latest....
I suggest to try the 4ext recovery....
If you want to root your phone first flash any of these recovery using fastboot or flash image gui
then go to recovery flash this zip if you want SuperSU by Chainfire----------> http://forum.xda-developers.com/showthread.php?t=1538053
OR
this one if you want Superuser by ChainsDD---->
http://forum.xda-developers.com/showthread.php?t=1312971
and your stock Rom will be rooted...
you can always flash custom ROMs , they come pre rooted , so after flashing any recovery just flash any ROMs zip. file.....then you will have custom Rom with root access....
mnomaanw said:
clockworkmod 4.0.1.4 -------> http://db.tt/hm3wkw1q
clockworkmod touch 5.8.0.2 --------> http://db.tt/yKUegldi
TWRP 1.1.1 -------> http://db.tt/ZrIEWf2B
TWRP touch 2.0 -------> http://db.tt/qHgIUljj
Recoveries versions other than these doesn't seem to work with hboot 1.5
CWM touch have a few bugs in this version , they may have fixed in the latest....
I suggest to try the 4ext recovery....
If you want to root your phone first flash any of these recovery using fastboot or flash image gui
then go to recovery flash this zip if you want SuperSU by Chainfire----------> http://forum.xda-developers.com/showthread.php?t=1538053
OR
this one if you want Superuser by ChainsDD---->
http://forum.xda-developers.com/showthread.php?t=1312971
and your stock Rom will be rooted...
you can always flash custom ROMs , they come pre rooted , so after flashing any recovery just flash any ROMs zip. file.....then you will have custom Rom with root access....
Click to expand...
Click to collapse
Go for the CWM 4.0 never had any issues .. The lateset CWM has funky issues..
mnomaanw said:
clockworkmod 4.0.1.4 -------> http://db.tt/hm3wkw1q
clockworkmod touch 5.8.0.2 --------> http://db.tt/yKUegldi
TWRP 1.1.1 -------> http://db.tt/ZrIEWf2B
TWRP touch 2.0 -------> http://db.tt/qHgIUljj
Recoveries versions other than these doesn't seem to work with hboot 1.5
CWM touch have a few bugs in this version , they may have fixed in the latest....
I suggest to try the 4ext recovery....
If you want to root your phone first flash any of these recovery using fastboot or flash image gui
then go to recovery flash this zip if you want SuperSU by Chainfire----------> http://forum.xda-developers.com/showthread.php?t=1538053
OR
this one if you want Superuser by ChainsDD---->
http://forum.xda-developers.com/showthread.php?t=1312971
and your stock Rom will be rooted...
you can always flash custom ROMs , they come pre rooted , so after flashing any recovery just flash any ROMs zip. file.....then you will have custom Rom with root access....
Click to expand...
Click to collapse
Thank you so much! That is awesome! I really appreciate you getting those all in one place for me.
I finally have root access and am currently running infected rom eternity and am super stoked!
reaper24 - Thank you for your input as well. I got the cwm 4... my roommate just tried to do something by going to one of the newer versions... Whatever it was he was trying to do didn't work and he went back to 4, so I'll definitely be sticking with that for now.
Next order of business... unlocking my friends' phone. She got hers in January (preloaded with hboot1.5 and 2.17). Can't get it to unlock via HTC bootloader unlock. I did read that there is a problem getting the newer ones that shipped with the updated software to unlock. I understand you need the 2.08 RUU. I found an active link and downloaded the file... Now what do I do with the thing?
Where did you find the working ruu I need one. I honestly think you just rename it to pg86img put it on the root of your sd card and hold down vol down and power. Once it loads into bootloafer it will scan the file and ask you if you want to flash it over.
Sent from my PG86100 using XDA
AmbrosiaLyn07 said:
Thank you so much! That is awesome! I really appreciate you getting those all in one place for me.
I finally have root access and am currently running infected rom eternity and am super stoked!
reaper24 - Thank you for your input as well. I got the cwm 4... my roommate just tried to do something by going to one of the newer versions... Whatever it was he was trying to do didn't work and he went back to 4, so I'll definitely be sticking with that for now.
Next order of business... unlocking my friends' phone. She got hers in January (preloaded with hboot1.5 and 2.17). Can't get it to unlock via HTC bootloader unlock. I did read that there is a problem getting the newer ones that shipped with the updated software to unlock. I understand you need the 2.08 RUU. I found an active link and downloaded the file... Now what do I do with the thing?
Click to expand...
Click to collapse
If her phone has 2.17 then you can't run the 2.08. You need to run the 2.17 and then you can unlock it. I had to do that too.
For those of you going for the HTC Unlock (vs downgrade) i think maany of your questions & detailed walkthru can be found in the guide in my signature.
Sent from my PG86100 using Tapatalk
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.
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.
Question to anyone, I have a Inc 4g phone that is s-Off, I ran a stock RUU and lost root. I'm still s-off HBoot 1.15, I tried to fastboot flash a recovery and also a unsecured boot.img. I get a error when trying this "failed remote not allowed. Can any help with this?
NAU420 said:
Question to anyone, I have a Inc 4g phone that is s-Off, I ran a stock RUU and lost root. I'm still s-off HBoot 1.15, I tried to fastboot flash a recovery and also a unsecured boot.img. I get a error when trying this "failed remote not allowed. Can any help with this?
Click to expand...
Click to collapse
If you are sure that you are s-off, then follow the manual instruction very carefully to install recovery (twrp for example). If it fails, report back with the recovery image used and exact command typed to try and flash it.
And for verification. does your HBOOT screen give you any indication that you actually are S-OFF? Or are you taking someone's word for it?
mdmower said:
If you are sure that you are s-off, then follow the manual instruction very carefully to install recovery (twrp for example). If it fails, report back with the recovery image used and exact command typed to try and flash it.
And for verification. does your HBOOT screen give you any indication that you actually are S-OFF? Or are you taking someone's word for it?
Click to expand...
Click to collapse
Yes the screen says S-Off, the phone was my bothers phone and it was a test phone. I had to run a stock RUU to remove all the HTC test software. I'm going to make the phone a google voice only phone for one of my kids.
The only thing I don't get is, I'm s-off and should be able to flash a unsecure boot.img. after that I should then flash a recovery. But for some reason I can't flash a boot.
Command: fastboot flash boot boot.img
Boot.img is in my Android file and I do see the device using: fastboot device.
Sent from my HTC6500LVW using xda app-developers app
NAU420 said:
The only thing I don't get is, I'm s-off and should be able to flash a unsecure boot.img. after that I should then flash a recovery. But for some reason I can't flash a boot.
Command: fastboot flash boot boot.img
Boot.img is in my Android file and I do see the device using: fastboot device.
Click to expand...
Click to collapse
Not a lot of this made sense. You don't need to flash a boot image to be able to flash recovery and I don't understand "Boot.img is in my Android file" at all. Like I mentioned previously, follow the manual instruction to flash recovery. If it doesn't work, either you're not S-OFF or you're not using an HTC DROID Incredible 4G LTE. If, after successfully installing a custom recovery, you want to flash boot images through recovery, you'll need the engineered HBOOT by team unlimited.
mdmower said:
Not a lot of this made sense. You don't need to flash a boot image to be able to flash recovery and I don't understand "Boot.img is in my Android file" at all. Like I mentioned previously, follow the manual instruction to flash recovery. If it doesn't work, either you're not S-OFF or you're not using an HTC DROID Incredible 4G LTE. If, after successfully installing a custom recovery, you want to flash boot images through recovery, you'll need the engineered HBOOT by team unlimited.
Click to expand...
Click to collapse
Got it, I flash a Hboot and then I was able to flash recovery. Thanks for your help!!!
Lemme get this straight
NAU420 said:
Got it, I flash a Hboot and then I was able to flash recovery. Thanks for your help!!!
Click to expand...
Click to collapse
SO.......If I have a HTC VZN Incredible 4G LTE I can not root this phone ? Or did I loose something in the thread?
DaWolf2010 said:
SO.......If I have a HTC VZN Incredible 4G LTE I can not root this phone ? Or did I loose something in the thread?
Click to expand...
Click to collapse
No you can root it, I had a test device from my brother and it was alittle hard for me to root it. My Hboot was not the same as everyone else.
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