I'm trying to confirm a few things before I try to get CyanogenMod 10.1 on my Evo3D. (GSM)
The recommendation on their thread in their dev thread states: (http://forum.xda-developers.com/showthread.php?t=2147742)
-Do not use superwipes
-Required HBOOT : 1.49.xxxx
-S-OFF
-Radio/baseband : 11.77.3504.00P_11.25.3504.06_M get it from HERE
-4ext recovery
I'm just curious if all of this still applies.
1. In the http://forum.xda-developers.com/showthread.php?t=1535987 thread: It states: "Those people who are trying to gain S-off to flash ICS ROMs with sense 4.0... Youdo not have to flash the new firmware as a compulsion. The older Radio works well with the sense 4 ROMs. It is not an absolute necessity to upgrade the firmware. You can skip that. And you can flash any ROM in 4ext touch recovery even with S-ON."
Does this apply for CM10.1? Since it has JB and JB > ICS do I or do I not need S-OFF? (cuz it sounds like a pain in the ass to do)
2. In the bootloader for my Evo3d it says I have HBOOT 1.53.0007, do I need to downgrade? If so how? I can't seem to find a thread about downgrading.
3. Same with #1, it states the older radio works well, so should I change the radioband? if so, how? Do I just install the zip in Clockwork Recovery? Nevermind I should have checked which one I had first, I already have the right band,
4. 4ext recovery, isn't this an image for recover? because they're website links to an app on google play for 3$. Do I need to purchase this app? I'm getting a little confused.
5. I'm guessing super wipes doesn't apply to me?
- for sense 4.1 you may not require s-off but for cm10.2 you certainly do, or any aosp rom for that matter.
- as for 4ext, go to their site and download the free recovery updater and run it on your phone(make sure you are rooted) and it will flash 4ext recovery for you.
- you dont need super wipes
- you must the latest firmware to run aosp or ics roms. people get stuck in bootloop with the old firmware. just make sure you radio/baseband is 11.77.3504.00P_11.25.3504.06_M or 11.77.3504.00U_11.25.3504.06_M and you'll be good to go
if you list your current hboot/rom etc i could guide you how to gain s-off
Hboot is 1.53.0007
I'm not running a custom rom.
Just regular android 4.0.3
HTC sense 3.6
Software 3.28.631.1
And my radio band is 11.77.3504.00P_11.25.3504.06_M
First you have unlock bootloader from htcdev
then follow the instructions at http://unlimited.io/juopunutbear.htm to get s-off. it requires linux ubuntu or a livecd
then you to flash recovery manually using fastboot. you can get 4EXT recovery.img file from here
EM|NEM said:
First you have unlock bootloader from htcdev
Click to expand...
Click to collapse
Done already.
EM|NEM said:
then follow the instructions at http://unlimited.io/juopunutbear.htm to get s-off. it requires linux ubuntu or a livecd
Click to expand...
Click to collapse
I get that I can do it with livecd but is there no windows solution to getting s-off?
Does this method not work:
http://forum.xda-developers.com/showpost.php?p=23379815&postcount=3
http://forum.xda-developers.com/showpost.php?p=23379815&postcount=4
???
I have no idea if it will work. Changing cid w/o s-off may not be successful but you can try.
As for the wire trick, it used to be supported on windows platform as well but due to reasons mentioned on their site, they dropped support for it. Someone here might have the files required for windows and ics. I only have the linux and windows/GB files.
Its your choice but i would recommend you try livecd method
Related
Hello,
i have a T-Mobile flyer 3G 32gb with original HC
Build-number 3.55.111.1
baseband 20.4803.30.0822U_3822.11.08.07M2
HBoot 1.11.0011
Radio 3822.11.08.07M2
CID T-MOB101
I want to S-off and flash a custom rom but i don't know the best, the right, way to do this. So it's possible to have S-Off with this device?
I downloaded the T-Mobile RUU but with this RUU i can't downgrade to GB.
The RUU updater say Error 140 and stopped.
So what can i do for S-Off?
devil-77 said:
Hello,
i have a T-Mobile flyer 3G 32gb with original HC
Build-number 3.55.111.1
baseband 20.4803.30.0822U_3822.11.08.07M2
HBoot 1.11.0011
Radio 3822.11.08.07M2
CID T-MOB101
I want to S-off and flash a custom rom but i don't know the best, the right, way to do this. So it's possible to have S-Off with this device?
I downloaded the T-Mobile RUU but with this RUU i can't downgrade to GB.
The RUU updater say Error 140 and stopped.
So what can i do for S-Off?
Click to expand...
Click to collapse
Hey man...
I have the EXACT same flyer, everything the same... Did you manage to get it s-off and rooted back to Honeycomb?? I have read all the forums, but I actually can't find a clear solution! Lemme know please or if anybody can put it simple! Thanks!
custom rom for flyer with stock hc
These steps would help :
- unlock boot loader over htcdev
- flash cwm with fastboot
- with cwm you're able to flash any custom rom (zip files)
It worked at least on my htc evo 3D.
Hey,
I have somewhat of the same question - but remain puzzled... I unlocked the Flyer's bootloader yesterday through HTCdev, flashed a Revolutionary recovery (based on CWM) through fastboot and could then install SuperUser through an update.zip in the stock ROM.
I have mode some development on other devices, so I'm familiar with bootloaders and stuff. The forums are mostly talking about S-OFF and I don't really understand how that concerns me, because now that my stock ROM is rooted, I can do whatever I like (remove bloat etc.). I may not understand all implications of S-ON, but I know that my bootloader tells me my Flyer is S-ON.
Now, is there any problem to flash another ROM through CW Recovery? Will, for example, LeeDroid's ROM replace anything connected to 3G (I have the model running on AWS frequencies, which are quite unusual). Could I simply flash LeeDroid's ROM, then get back to my stock backup without any problem?
I guess the question is; since my bootloader is unlocked, does S-ON or OFF concern me in any way? Or is S-OFF only important for those who can't unlock their bootloaders through HTCdev?
Thanks!
(I do promise to write something up for the wiki if ever I understand
S-On means you can't flash a custom ROM through recovery or ROM Manager. You can only flash using fastboot.
Thanks!
So considering that I just tried to downgrade to Gingerbread in Windows and that I got Error 155 (which seems to be undocumented - the message was à la 'something went wrong - I don't know what'), can I restore CW recoveries through fastboot as well?
I wouldn't mind to plug the cable, and S-OFF seems like an unnecessary hassle to me... (I just want OpenVPN and from here I took as much time trying to figure that out than I would need to compile the module myself).
I guess what puzzles me is this (from the LeeDroid thread): "If you have acheived S-Off via HTCDev, you will need to extract the boot.img from the Kernel.zip and flash it via fastboot"
I don't have S-OFF. I have an unlocked bootloader.
Does that mean that if I want to switch to LeeDroid I first have to fastboot flash boot.img and then install the rest through CW recovery?
Similarly, if I want to get back to stock, I fastboot flash the boot.img from my backup and apply the rest through CW recovery?
Thus: S-ON actually only prevents the boot partition to be changed outside from fastboot?
Thanks again!
redpoint73 said:
S-On means you can't flash a custom ROM through recovery or ROM Manager. You can only flash using fastboot.
Click to expand...
Click to collapse
Hm. I just did full restore with CW recovery.
And I had already applied update.zip's with the recovery.
ADD: SOLVED. What I wrote in the post above was right. I can apply any zip file, but CW can't write boot.img. Solution: fastboot flash boot boot.img.
All the rest works. In order to get back to a backup I guess it's the same way - flash boot.img, apply the restore.
cid: TMOB010 and HBoot 1.11.0011 Please Help Soff this thing.
I have the exact same problem and I assume I need s-off to make this work like a phone. Yes? Has anybody figured this out yet?
bud.
This is going to be a short and simple guide for S-OFF users that want to update to the current RUU level or refresh their phone because they are having issues like being unable to boot certain ROM's. You will not lose S-OFF by flashing the RUU.
1. Do a nandroid backup of your current ROM if you want to restore it later.
2. Download the current version of the RUU for your phone in exe or zip format from this page.
3. Run the exe version of the RUU in Windows or the zip version as a PG86IMG.zip file through the bootloader. If using the bootloader method make sure the file is named exactly "PG86IMG.zip" and placed in the root of your SD card before starting the bootloader.
There is no need to unlock the bootloader before running it if you are S-OFF and there is troubleshooting information in this post if you have problems. It may be necessary to run the RUU twice if you have a custom bootloader installed when it is run the first time. If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
I recommend downloading and installing the OTA(s) immediately after flashing the RUU to get the most current firmware while still 100% stock, but the OTA firmware update(s) can be downloaded as a separate PG86IMG.zip file if you forget or can't do that for some reason.
4. Flash a custom hboot using the instructions in this post. My recommendation for a good general purpose hboot is the JBear GB 1.50.5050 version unless you are running an ICS Sense ROM like stock or Cool ICS that requires an ICS bootloader (1.57.xxxx or 1.58.xxxx).
5. Connect your phone to a PC and start the bootloader in "fastboot USB " mode, then issue the following command to flash your favorite recovery:
fastboot flash recovery recovery.img (where "recovery.img" is the name of the recovery file in your ADB/fastboot directory)
6. Boot into recovery and restore a nandroid or flash another custom ROM. You may have to wipe cache+dalvik and restart recovery if you get any error messages from the recovery program.
That's it. You're now updated or re-synced with the current firmware, the hboot that meets your requirements and your favorite recovery.
Here are some additional links that might be helpful:
4EXT Recovery OP for the Evo 3D CDMA thread with a direct link to recovery.img in the download section (not the most current version)
Current TeamWin (TWRP2) touch recovery for the CDMA Evo 3d.
Virgin Mobile OTA firmware only in PG86IMG.zip format.
Sprint OTA firmware only in PG86IMG.zip format.
ramjet73
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
3volution said:
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
Click to expand...
Click to collapse
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
3volution said:
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
Click to expand...
Click to collapse
You're welcome.
It's not really that difficult if you are familiar with rooting and flashing HTC devices but I can understand how it might be for users coming from other brands. Samsung in particular is definitely less complicated.
ramjet73
Thanks!
Thanks for this great post ramjet. Really a great concise How-to.
Nevermind, fixed.
ramjet73 said:
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
Click to expand...
Click to collapse
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
I also tried updating via the bootloader method as well..... runs well....updates like four of the ten check offs and then bootloops as well.
Edit: turns out I was flashing the wrong version, oops
Hedied4me said:
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
Click to expand...
Click to collapse
From experience I've discovered that the RUU.exe utility will sometimes stop after flashing the stock bootloader if it is run with a custom hboot installed, which is why I put this comment in the OP:
If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
Click to expand...
Click to collapse
I've had no problem completing the RUU.exe flash if I just cancel the utility in the Windows task manager and restart it.
Others have reported that re-flashing the RUU.zip file through the bootloader also works if the original flash is incomplete.
Also, make sure that you downgrade your hboot after flashing the RUU since the stock hboot won't boot GB or AOSP based ROM's.
ramjet73
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Sent from my HTCEVOV4G using Tapatalk 2
Hedied4me said:
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Click to expand...
Click to collapse
Try removing/replacing the battery and then use the Power+VolumeDown buttons together to enter the bootloader.
The stock ROM has the "fast boot" option turned on in the power settings by default and that will interfere if you try to enter the bootloader after powering down from the stock ROM.
ramjet73
Thank you very much for your patience and help Ramjet. Everything went well.
Sent from my Evo V 4G using Tapatalk 2
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
El Queson said:
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
Click to expand...
Click to collapse
I honestly don't know.
There is a post by a cricket user in my rooting and S-OFF guide that says the customization is not lost for that carrier but I've never used Boost and can't speak to that.
Perhaps another Boost user on these forums has experience with flashing the RUU.
ramjet73
++sorry++
Using the bootloader procedure is, by far, the easiest way of doing the RUU process that I've encountered. From custom ROM, to stock, back to a custom ROM in less than 45 minutes.
ramjet, thank you for your contributions to our platform.
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
GAPO said:
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
Click to expand...
Click to collapse
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
ramjet73 said:
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
Click to expand...
Click to collapse
Yes she is S-off. She also already has 4ext recovery installed.
Does this negate my need to flash recovery in the downloader?
Since she is S-off, this should be pretty easy.
I will still need to access the bootloader via Windows cmd, yes? Or can I accomplish all of this using only the handset?
Sent from my PG86100 using xda premium
---------- Post added at 07:07 PM ---------- Previous post was at 06:52 PM ----------
Her hboot is:
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-0.97.10.0530
eMMC-boot
Jun 8 2011, 17:20:22
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Sent from my PG86100 using xda premium
GAPO said:
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Click to expand...
Click to collapse
That's a stock hboot so you should be fine. You can still update using the RUU if a custom hboot is installed, but it might take a restart to complete after the stock hboot is installed.
ramjet73
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.
So, I have a 3d that's totally stock and taken every OTA released. I'm at android 4.03, sense 3.6, and software 2.95.651.5. I want to downgrade my hboot (current S-ON and 1.58) to 1.50 so I can flash CM10.1, and I'm using this guide to do so. Problem is, in the first step (bricking), none of the RUU .zips I've tried (2.17, 2.89) allow me to even attempt the update (and, then, brick the phone) - they come up as 'Main version older' or something, and that I just have to reboot the phone. Which RUU do I need to download to start this process? Appreciate the help.
gaan kak said:
So, I have a 3d that's totally stock and taken every OTA released. I'm at android 4.03, sense 3.6, and software 2.95.651.5. I want to downgrade my hboot (current S-ON and 1.58) to 1.50 so I can flash CM10.1, and I'm using this guide to do so. Problem is, in the first step (bricking), none of the RUU .zips I've tried (2.17, 2.89) allow me to even attempt the update (and, then, brick the phone) - they come up as 'Main version older' or something, and that I just have to reboot the phone. Which RUU do I need to download to start this process? Appreciate the help.
Click to expand...
Click to collapse
I believe there is no RUU for hboot 1.58. I think you need to perform S-Off first to get around this.
http://forum.xda-developers.com/showpost.php?p=39748093&postcount=363
Taken from this thread: http://forum.xda-developers.com/showthread.php?t=1889438
I've done what you are trying to do with the same settings
Hi,
I have the HTC evo 3d CDMA
I would use this guide in order to get S-OFF and unlocked: http://forum.xda-developers.com/showthread.php?t=1889438
change hboot to hboot 1.5. instructions for how to do this: http://unlimited.io/jbhboots.htm
NOTE: commands are for ubuntu 12.04 or greater! Also to get s-off, follow the instructions on their website and don't use the windows version of juopunutbear.
then put your rom.zip and gapps on the sdcard of your phone.
reboot into 4ext recovery, wipe cache, dalvik, system, and data.
instal from sdcard the rom.zip
install from sdcard the gapps
reboot. Done. you should now be on 10.1!
good luck.:good:
So I have the my EVO is unlocked, but S-ON. I'm Ruu 3.16 and HBOOT 2.09
I'm running a buggy Cyanogenmod 10.3 alpha or something.
I've tried to Moonshine, I've tried flashing roms S-ON way with CMD prompt but touchscreen only works on the Cyanogenmod 10.3.
My next attempt was to try the Dirty Racun, but I don't want to go through the whole not having a phone situation. So I might try over the weekend.
I seen this post http://forum.xda-developers.com/showthread.php?t=2089509
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily.
I wanted to try it, but I'm not sure if it will work. I'm pretty computer savvy but custom roms and stuff is so new to me. So my question is how can I either go back to stock Android which I would prefer or go S-Off to dl stable ROMS. Can anyone help?
Thanks to all that reply.
mixtkid said:
So I have the my EVO is unlocked, but S-ON. I'm Ruu 3.16 and HBOOT 2.09
I'm running a buggy Cyanogenmod 10.3 alpha or something.
I've tried to Moonshine, I've tried flashing roms S-ON way with CMD prompt but touchscreen only works on the Cyanogenmod 10.3.
My next attempt was to try the Dirty Racun, but I don't want to go through the whole not having a phone situation. So I might try over the weekend.
I seen this post http://forum.xda-developers.com/showthread.php?t=2089509
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily.
I wanted to try it, but I'm not sure if it will work. I'm pretty computer savvy but custom roms and stuff is so new to me. So my question is how can I either go back to stock Android which I would prefer or go S-Off to dl stable ROMS. Can anyone help?
Thanks to all that reply.
Click to expand...
Click to collapse
You have a few choices: Stay rooted, S-on & understand the limitations of being S-on means that you have to flash the kernel separately from the ROM. Click on the top link in my sig to understand more. Or you can go for S-off, as many of us already have.
Your touchscreen issue is due to an updated touch panel driver that was included in the 3.16 update. You can only use Sense ROM's based on software version 3.16 & 3.17, or AOSP ROM's with the 3.4 kernel. You can downgrade the driver if you're S-off, which will allow you to run older ROM's.
You ultimately have to decide what you want to do with your phone. If you want to flash ROM's while S-on, that's not a problem, just understand that there is a little more work involved to get the ROM up & running. S-off makes life much easier. Remember, there is an entire community here to help you, too:thumbup:
Sent from my HTC EVO 4G LTE
FinZ28 said:
You have a few choices: Stay rooted, S-on & understand the limitations of being S-on means that you have to flash the kernel separately from the ROM. Click on the top link in my sig to understand more. Or you can go for S-off, as many of us already have.
Your touchscreen issue is due to an updated touch panel driver that was included in the 3.16 update. You can only use Sense ROM's based on software version 3.16 & 3.17, or AOSP ROM's with the 3.4 kernel. You can downgrade the driver if you're S-off, which will allow you to run older ROM's.
You ultimately have to decide what you want to do with your phone. If you want to flash ROM's while S-on, that's not a problem, just understand that there is a little more work involved to get the ROM up & running. S-off makes life much easier. Remember, there is an entire community here to help you, too:thumbup:
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
So I think I'd probably just Flash a ROM S-ON version like I already have done. I've tried the S-Off stuff before and failed with Moonshine, and Facepalm i think its called. Could you tell me a good ROM that will confirmed work with 3.16 S-ON. Also I have TWRP recovery if that makes a difference. Thanks for the fast reply by the way.
MeanBean is S-on friendly. Flash the ROM zip once and reboot. The phone will boot to the HTC splash screen and then reboot to recovery. Flash the ROM zip again and reboot. Don't forget to wipe properly in TWRP prior to flashing.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You have a few choices: Stay rooted, S-on & understand the limitations of being S-on means that you have to flash the kernel separately from the ROM. Click on the top link in my sig to understand more. Or you can go for S-off, as many of us already have.
Your touchscreen issue is due to an updated touch panel driver that was included in the 3.16 update. You can only use Sense ROM's based on software version 3.16 & 3.17, or AOSP ROM's with the 3.4 kernel. You can downgrade the driver if you're S-off, which will allow you to run older ROM's.
You ultimately have to decide what you want to do with your phone. If you want to flash ROM's while S-on, that's not a problem, just understand that there is a little more work involved to get the ROM up & running. S-off makes life much easier. Remember, there is an entire community here to help you, too:thumbup:
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
FinZ28 said:
MeanBean is S-on friendly. Flash the ROM zip once and reboot. The phone will boot to the HTC splash screen and then reboot to recovery. Flash the ROM zip again and reboot. Don't forget to wipe properly in TWRP prior to flashing.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thank you for the help. I'm going to give it a try after work. I'll let you know how it goes.