Related
UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....
Thanks op.
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!
Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!
Well, worry even less! Special thanks to Calkulin!
thankssssss
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
I'm getting error 155 running Ava Froyo and trying to go back.
blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.
tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.
Yes. I have .79, thanks!
Sent from my PC36100 using XDA App
Hey guys. I recently purchased a used One X on the MP here. The seller let me know the phone is rooted and running a custom ROM. In my searching for how to restore it to completely stock, I've hit a wall and I need some help.
The only return-to-stock methods I can find are designed for rooted phones running the stock ROM. It seems there's a different method for a phone on a custom ROM? Maybe I'm just plain wrong, but if there is a different method, could someone point me in the right direction please?
While this isn't my first rodeo with rooting/unrooting, it is on anything other than a Samsung device. I'd like to start from scratch on this new phone so returning it to stock is the first step.
Any help would be greatly appreciated.
Sent from my Galaxy Nexus using xda premium
KentuckyHouse said:
Hey guys. I recently purchased a used One X on the MP here. The seller let me know the phone is rooted and running a custom ROM. In my searching for how to restore it to completely stock, I've hit a wall and I need some help.
The only return-to-stock methods I can find are designed for rooted phones running the stock ROM. It seems there's a different method for a phone on a custom ROM? Maybe I'm just plain wrong, but if there is a different method, could someone point me in the right direction please?
While this isn't my first rodeo with rooting/unrooting, it is on anything other than a Samsung device. I'd like to start from scratch on this new phone so returning it to stock is the first step.
Any help would be greatly appreciated.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Wrong section, this should really be in the Q and A section.
I'm assuming this is your first HTC device. We have something called RUUs, or ROM Update Utilities.
This is what you will need to do when you get your phone:
1. Download the RUU for 1.85 (found in the development forums)
2. Install the fastboot tool (google on how to do that)
3. Connect your device in fastboot mode (boot into the bootloader)
4. Run this command:
fastboot oem lock
5. Then from there start up the RUU's .exe file
6. Follow the RUU instructions.
At the end of the RUU you will have a stock phone with one exception, the bootloader will say "relocked" instead of "locked" as it does on stock phones. There is no way to currently get back to it saying "locked" untill we get S-OFF (security off, a "feature" on HTC phones that we are currently working on achieving)
However, your experience with the phone will then be 100% stock.
Sorry about sticking this in the wrong section. I'm usually better than that!
Thank you so much for the info. That's extremely helpful. This is my first HTC device and I'm feeling a little lost so far. Some things seem to translate across devices, but others don't (such as S-off…I could not figure out what that meant, so again, thanks for that!)
I'll have the phone in my hands sometime next week, so I'm trying to do as much research before it arrives as I can.
5. Then from there start up the RUU's .exe file?
rohan32 said:
Wrong section, this should really be in the Q and A section.
I'm assuming this is your first HTC device. We have something called RUUs, or ROM Update Utilities.
This is what you will need to do when you get your phone:
1. Download the RUU for 1.85 (found in the development forums)
2. Install the fastboot tool (google on how to do that)
3. Connect your device in fastboot mode (boot into the bootloader)
4. Run this command:
fastboot oem lock
5. Then from there start up the RUU's .exe file
6. Follow the RUU instructions.
At the end of the RUU you will have a stock phone with one exception, the bootloader will say "relocked" instead of "locked" as it does on stock phones. There is no way to currently get back to it saying "locked" untill we get S-OFF (security off, a "feature" on HTC phones that we are currently working on achieving)
However, your experience with the phone will then be 100% stock.
Click to expand...
Click to collapse
Hello, I am also trying to install the factory rom on my HTC One X and I have completed step 4 in the instructions that you put up above. I am stuck on step 5. There are no .exe files from the download i got. These are the only files I got:
evita_readme.txt
evita-ics-crc-3.0.8-271616b.tar
So I am confused when you say to start up the RUU's.exe file
Your help would be greatly appreciated and thank you in advance for your response.
http://forum.xda-developers.com/showthread.php?t=1671237 the ruu files can be found there
Hey Guys!!!
I've been looking around for a straightforward tutorial on how to flash back to stock.
If anyone could point me to the right thread that would be helpful, I'd would just like to set everything back to normal since I need to send the phone back.
I just want to know what the process is, like 1. Relock Bootloader 2. Flash Stock T-Mobile ROM 3. Flash Stock Recovery, something to that effect, so if any of you can point me to the right direction that would be greatly appreciated.
Thanks in advance guys:fingers-crossed:
!!!!!!--UPDATE---!!!!!!!!
So it worked everyone like a charm, so much thanks to baseballfanz, jdizzle316, and Senzune
So here's the breakdown on what I did, and again !!! This is for TMOUS and I tested with the 1.84.531.2 software !!!!
1. Re-locked the bootloader
- You can use the All in one tool from http://forum.xda-developers.com/showthread.php?t=1604677
- Or boot into fastboot and enter fastboot oem lock
2. Reboot the phone, check everything is ok
- no need to go back to bootloader or recovery
3. Boot back into bootloader
4. Go into fastboot
5. Run TMOUS RUU, go through the process and then just let it run, don't touch anything
- I found it from this forum http://forum.xda-developers.com/showthread.php?t=1744177&page=3
- If anyone needs another dropbox link let me know
6. Once it's all set you'll be back in the bootloader and all you have to do is just reboot the phone
And again thanks everyone for the help :fingers-crossed::fingers-crossed:
Are you on stock but rooted ROM or a custom ROM?
baseballfanz said:
Are you on stock but rooted ROM or a custom ROM?
Click to expand...
Click to collapse
I'm on Trickdroid like you are it seems, so I think that's considered custom no?
Just lock the bootloader and run the T mobile RUU
Use the all in one root kit in order to lock your bootloader(this can be found in the development section)
Once you bootloader is locked, download the TMOUS RUU, also found in the development section. This is an exe file you run on your pc.
Boot your phone into bootloader, then choose fast boot. Attach your phone to the USB connected to your PC and then run the ruu and from then it will take your device to completely stock.
Sent from my EVO using xda app-developers app
jdizzle316 said:
Use the all in one root kit in order to lock your bootloader(this can be found in the development section)
Once you bootloader is locked, download the TMOUS RUU, also found in the development section. This is an exe file you run on your pc.
Boot your phone into bootloader, then choose fast boot. Attach your phone to the USB connected to your PC and then run the ruu and from then it will take your device to completely stock.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Ok great
Now not sure if either you or baseballfanz have read anything about this on the forums, but I've downloaded both:
- RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
- RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed
Which one of these RUUs would allow for regular OTA updates, I'm not sure if either of you would know but I'm just curious
Thanks again guys for you help by the way:laugh::victory:
dbo87 said:
Ok great
Now not sure if either you or baseballfanz have read anything about this on the forums, but I've downloaded both:
- RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
- RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed
Which one of these RUUs would allow for regular OTA updates, I'm not sure if either of you would know but I'm just curious
Thanks again guys for you help by the way:laugh::victory:
Click to expand...
Click to collapse
You need to check in your settings which one applies to your device - at least I hope that's the way to decide which one to use. I have an RUU downloaded myself, just incase I ever do decide to get a custom ROM (waiting for a JB one which actually works). I found the proper one by checking which one has the same Baseband version, which in the stock ROM is found under About > Software information > More.
Since you seem to be on a TMOUS version of the One S, I believe it to be highly likely the 1.84 one is the way to go, as most updated to that version, including custom ROMs. You'd have to check that at Software number, I believe, if that's not altered by the custom ROM.
Senzune said:
You need to check in your settings which one applies to your device - at least I hope that's the way to decide which one to use. I have an RUU downloaded myself, just incase I ever do decide to get a custom ROM (waiting for a JB one which actually works). I found the proper one by checking which one has the same Baseband version, which in the stock ROM is found under About > Software information > More.
Since you seem to be on a TMOUS version of the One S, I believe it to be highly likely the 1.84 one is the way to go, as most updated to that version, including custom ROMs. You'd have to check that at Software number, I believe, if that's not altered by the custom ROM.
Click to expand...
Click to collapse
Yeah, I think you're right my build number is 1.84.531.2 so I assuming that I have to use the 1.84RUU, we'll see what the others have to say, but I'll be sure to keep you all posted once I run through the process.
1.84 is the latest and has latest radio
1.53 was previous version
I have my at&t htc one x on 4.0.4, bootloader locked, hboot 1.14.0002 S-on
evita pvt ship. i bought from amazon used, how can i update from 4.0.4 to a higher firmware and if i try use software update it searches for a bit then i get error what can i do?
Do you want to stay stock or install custom ROMs? The two processes will be very different so I need to know which way you want to go before advising you.
Sent from my Evita
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
Also, do you have adb/fastboot installed on your PC? If not you're going to need that, Google search "xda minimal adb and fastboot" and the first result should be a thread that details how to install it easily.
Sent from my Evita
If you want to update to the latest "official" firmware, you can download the RUU at the following webpage, and follow the directions where it says "Manual system update instructions":
http://www.htc.com/us/support/htc-one-x-att/news/
This will update you to Jellybean 4.1.1, which is the latest that has been released for the AT&T version.
Be aware this will wipe any date on the phone, so backup anything you want to keep.
EDIT: As timmaaa advised below, CID needs to be verified before running the above RUU. If SuperCID is present with s-on, running the RUU will brick the device.
Hang on, we need to check his SuperCID status before he runs a jb RUU, the phone is used. We don't want a brick on our hands.
Sent from my Evita
timmaaa said:
Hang on, we need to check his SuperCID status before he runs a jb RUU, the phone is used. We don't want a brick on our hands.
Click to expand...
Click to collapse
Very true. I assumed that since the phone is still bootloader LOCKED, that its bone stock (I also missed the word "used" when I read the OP). But its possible the previous owner changed the CID, but either botched the BL unlocking or didn't get that far.
I've edited my previous post accordingly, to make sure the OP doesn't damage his phone.
Yeah, previous owner could have also spoofed the bootloader text to say locked instead of relocked.
OP, get adb/organised as per my first reply and then we can check out your situation before proceeding.
Sent from my Evita
htc one x
how do u get pass the sid lock to get the slock off
DaShadow14 said:
how do u get pass the sid lock to get the slock off
Click to expand...
Click to collapse
Huh? That makes absolutely no sense. If you want help please do the following:
1- Don't hijack this thread, we're already helping someone else here. Please repost your question in my q&a thread.
2- Tell me exactly what you want to achieve.
3- Tell me your bootloader details.
4- Tell me any other relevant information.
5- Do all this in clear and legible English, and be specific.
PS. There are no such things as a 'sid lock' or 'sloff', as I've said above please post in clear English using terms that actually exist.
Sent from my Evita
ok im going to try super cid do i need to root my phone 1st and i want stock unless custom is more better and stable.
Stock ROM is stable but so are custom ROMs, plus you get better features with custom ROMs. Before you do anything though you need to decide whether you want to use a stock ROM or a custom ROM. The two processes will vary greatly. Have you installed adb/fastboot like I suggested earlier?
Sent from my Evita
no i didnt get get adb or fastboot i dont know were to get it and ok i'll do custom rom.
ok im roothing and it says * daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
its been like this for 5mins now?
What method are you using?
Sent from my Evita
i was using a one click rooting software i deleted it i now have
onexrootattnew.zip but that doesnt want to root it either really and truly i jus wanted to update my software cuz my phone wifi range is seriously low to the point that i have to be right new to a router or 5ft away to catch signal and my bluetooth range basically is 1ft so i wanted to update to fix my problem
There's only one way you can get root. The first thing you need to do is stop getting information from other sites, they don't properly distinguish between firmware versions, and even phone models. Everything you need is here on XDA, it's the only comprehensive Android modification site available.
Click the Everything Evita link in my signature and bookmark that thread, everything you need is compiled in that thread. In that thread navigate to the root section, find the 2.20 root method. Follow the instructions in that thread and you'll have SuperCID. Then you can go to htcdev and unlock your bootloader. Once you have an unlocked bootloader you can install Superuser to root your current ROM, or you can install a custom ROM. If you need help installing a recovery or ROM just click the How-To Guide For Beginners link in my signature.
Sent from my Evita
thanks man i will try it out will get back to u by 2morrow.
my bootloader is unlocked so i can get any custom rom?
Technically, yes. But your phone still needs some updating before you can stay on a custom ROM. Your steps will be as follows:
1. Install TWRP recovery.
2. Install root via SuperSU.
3. Get s-off via Facepalm.
4. Run the 3.18 RUU (this returns your phone to stock but it's essential because this is the step that updates everything)
5. Install TWRP recovery again (official TWRP 2.6 for Sense 5 ROMs and aosp ROMs lower than 4.4, or modified TWRP 2.6.3.0 for 4.4 aosp ROMs).
6. Update firmware via 2.15 firmware package (this step is only necessary if you're planning on installing a Sense 5 ROM). You'll find it in the first post of this thread along with instructions.
7. Install whatever ROM you like.
8. Enjoy.
If you have any questions don't be afraid to ask.
Sent from my Evita
ok ill let u know when im done
Have a look at my How-To Guide For Beginners thread in my signature for detailed instructions on some of those processes.
Sent from my Evita
So, i was here back when the phone came out, unlocked the bootloader and got a few Roms in the start, and ended up with Paranoid Android V2.54 i believe, and never really cared about looking for anything new since i thought it was pretty good, and i enjoy as close to stock as possible. But now my phone is getting really slow, and i need a change. And getting back onto the forums here im just really intimidated by the amount of Roms, the term S-OFF and Kernel. I generally know the basics i suppose, but when i was installing Roms back in the early days of the HTC one S it was as easy as getting the rom on the SD card an flashing it. Im probably coming off as a bit stupid here, but i dont wanna brick this phone just because i did one thing wrong.
So where im getting at is, what Rom should i go for? I just need something easy to install, and nothing super flashy. As said earlier, i enjoy the stock android, and i wouldnt mind getting the newer version of android aswell. So give me some pointers, and feel free to give me the details on how to flash it as i havent done this in a while
Jahrern said:
So, i was here back when the phone came out, unlocked the bootloader and got a few Roms in the start, and ended up with Paranoid Android V2.54 i believe, and never really cared about looking for anything new since i thought it was pretty good, and i enjoy as close to stock as possible. But now my phone is getting really slow, and i need a change. And getting back onto the forums here im just really intimidated by the amount of Roms, the term S-OFF and Kernel. I generally know the basics i suppose, but when i was installing Roms back in the early days of the HTC one S it was as easy as getting the rom on the SD card an flashing it. Im probably coming off as a bit stupid here, but i dont wanna brick this phone just because i did one thing wrong.
So where im getting at is, what Rom should i go for? I just need something easy to install, and nothing super flashy. As said earlier, i enjoy the stock android, and i wouldnt mind getting the newer version of android aswell. So give me some pointers, and feel free to give me the details on how to flash it as i havent done this in a while
Click to expand...
Click to collapse
First thing you should tell us some more info about your phone, just to know better what guides and adices we should give you:
1. Phone model: S4 or S3 (is it with dual core krait 1.5 Ghz or with older dual core 1.7 Ghz processor?)
2. What hboot/firmware do you have, what radio, are your bootloader locked or not (at HTC Dev site)...in fact we need all the info that you have on your bootloader screen (power off phone then keep pressed VOLUME DOWN while pressing POWER)
3. What recovery do you use (CWM or TWRP) and what version?
4. Finally but not least....WHAT DO YOU WANT? A Sense ROM, an AOSP ROM, do you want latest Android version (4.4.2 KitKat) or it doesn't matter to you...things like this. You said something about this but maybe give more details
Then we might have some guides for you and some advices and you could choose among them based on your pers preference :good:
Rapier said:
First thing you should tell us some more info about your phone, just to know better what guides and adices we should give you:
1. Phone model: S4 or S3 (is it with dual core krait 1.5 Ghz or with older dual core 1.7 Ghz processor?)
2. What hboot/firmware do you have, what radio, are your bootloader locked or not (at HTC Dev site)...in fact we need all the info that you have on your bootloader screen (power off phone then keep pressed VOLUME DOWN while pressing POWER)
3. What recovery do you use (CWM or TWRP) and what version?
4. Finally but not least....WHAT DO YOU WANT? A Sense ROM, an AOSP ROM, do you want latest Android version (4.4.2 KitKat) or it doesn't matter to you...things like this. You said something about this but maybe give more details
Then we might have some guides for you and some advices and you could choose among them based on your pers preference :good:
Click to expand...
Click to collapse
1. According to Quadrant i have a CPU Frequency of 1512MHz, so by definition that should make it a S4
2. For recovery, im almost 100 percent sure its SuperSU, and heres the details from my bootloader:
VLE PVT SHIP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.315018.19
OpenDSP-v21.1.0.32.0314
eMMC boot
Mar 15 2012.23:37;23
And yes i used HTC Dev website to unlock it. got some sort of key and everything.
3. The recovery i use atm is CWM 5.8.3.1 the none touch version. Tried the touch version a few times, but it doesnt seem to work for me.
4. For ROM as i mentioned i really like AOSP, and can't really see myself going for a Sense ROM unless there's something really awesome out there. Ive used CM 9 and 10, AOKP, ParanoidAndroid and one of those Pac-man ROMs before, and they have all been decent. But now i want something newer. Preferably something over 4.1.2 as ive had that for probably a year now, and i need SOMETHING new. I dont particularly want anything that isn't as complete as possible. The ROM im rocking now reboots my phone ATLEAST 1-2 times a day, and have some minor Wi-Fi issues. (not really that bad anymore after buying an expensive new ASUS Router)
So those are like my only things when it comes to ROMs. Doesnt need to be as flashy as coming with a completly themed interface and that sorts
I like CM11. It seems to running ok, but better check the latest in the thread.
http://forum.xda-developers.com/showthread.php?t=2528113&page=367
Jahrern said:
1. According to Quadrant i have a CPU Frequency of 1512MHz, so by definition that should make it a S4
2. For recovery, im almost 100 percent sure its SuperSU, and heres the details from my bootloader:
VLE PVT SHIP S-ON RL
HBOOT-1.06.0000
RADIO-0.15.315018.19
OpenDSP-v21.1.0.32.0314
eMMC boot
Mar 15 2012.23:37;23
And yes i used HTC Dev website to unlock it. got some sort of key and everything.
3. The recovery i use atm is CWM 5.8.3.1 the none touch version. Tried the touch version a few times, but it doesnt seem to work for me.
4. For ROM as i mentioned i really like AOSP, and can't really see myself going for a Sense ROM unless there's something really awesome out there. Ive used CM 9 and 10, AOKP, ParanoidAndroid and one of those Pac-man ROMs before, and they have all been decent. But now i want something newer. Preferably something over 4.1.2 as ive had that for probably a year now, and i need SOMETHING new. I dont particularly want anything that isn't as complete as possible. The ROM im rocking now reboots my phone ATLEAST 1-2 times a day, and have some minor Wi-Fi issues. (not really that bad anymore after buying an expensive new ASUS Router)
So those are like my only things when it comes to ROMs. Doesnt need to be as flashy as coming with a completly themed interface and that sorts
Click to expand...
Click to collapse
OK, I got more info now, maybe some others will step in and give you their opinions and advices. What I can tell
1. SuperSU is not a recovery (you already said you're using CWM)...it's the root program.
2. You have hboot 1.06 the same I had on my device some time ago (not too long ago). It has some advantages and some disadvantages. I'll try to be brief and prsent you all and you can decide what you wanna do.
First some background: S-Of basically means you are able to write to certain partitions on your device, partitions that are normally locked. Most important are the firmware/hboot partition, radio partition and kernel partition. If you are S-On, you cannot write/flash radio or firmware and you MUST flash any kernel via a separate command in fastboot.
Now what makes 1.06 hboot so special...it is behaving like a partial S-Off device even if you are not S-Off. What does this mean? You will be able to flash radios and kernels as any other S-Off user. Only thing you won't be able to flash is the firmware/hboot. On the other hand, all new ROMs require hboot 2.13/2.15 or the leaked 2.16. That means that IF your current hboot allows you to run such a ROM, you won't be able to flash it unless you're editting EVERY TIME the updater-script in the ROM ZIP you're flashing to bypass the hboot check. So things will become little bit complicated.
To avoid all these you should first S-Off then you should upgrade to hboot 2.15. This is the last official firmware and it is supported by all new KitKat ROMs. DO NOT flash 2.16 firmware unless you would like to flash and use Sense based ROMs like MaximusHD.
I made S-Off by using Rummrunner because I found it the simplest way to do it...it's like a one-press-S-Off. If that doesn't work for you, you can try other methods like Facepalm or Moonshine. You can find separate threads for each in Dev section and I'll also link them below
Rummrunner
Facepalm
Moonshine
After you made S-Off, next step will be to upgrade your hboot/firmware to 2.15. You can use the flashable ZIP from THIS thread and you'll find info on how to do it in the thread. I would suggest you to choose the Unbranded 2.15 hboot and that has also the red warning gone (the one you see when start up the device with "This device is for development purposes only...bla bla bla")
For all the above you might also want to check/try a tool that incorporates most of them. You can find it in THIS thread.
Now that you have S-Off and upgraded your hboot, you might want to flash a newer radio. Hint:If you're satisfied with your current signal strength, mobile data and so on, don't flash another radio. Even if in a ROM thread it is recommended or mandatory a certain radio, my advice is to first try the ROM with your current one and only if performance is not satisfactory, flash another radio.You can find radios in tecardo's thread HERE or if you want the newer radios you can find radio 1.20 HERE or 1.35a HERE. One more note regarding tecardo's thread with the radio collection...that thread is old and some info is not updated. Just remember that you must flash ONLY the V6 Sense Radio installer for any ROM you'll be using, being it sense based or AOSP. Also ignore that warning that the procedure is only for hboots below 1.3...at that time there was no S-Off (remember what I've said about the particularities of 1.06 hboot earlier). Now things are different, you're S-Off so you will just need to flash it
Before flashing, you might consider upgrading to a newer recovery. I would recommend you the latest official TWRP 2.7.0.0 that will support flashing anything made for hboot 2.15. If and only if you decide to try sense ROMs based on hboot 2.16, you'll need a different recovery specific for 2.16 and that you'll get from that specific ROM thread. Official TWRP downloads for Ville S4 are HERE
Now youre almost done. You just need to pick your ROM and flash it...pretty difficult task considering how many they are. I tested most of AOSP ones and also some Sense based ones (not the ones for hboot 2.16 tho). I don't want to advice too much here since it could be considered I favour one or another...the truth is I do and that's normal, but I'd like to be objective
First, all KitKat ROMs are pretty stable. On CM11 there are regular nightlies and there are also less stable or bugged builds but this is expected. So you might try several ROMs to see which suits you most and you can decide by reading each ROM's thread. I'll list some ROMs (not all), the ones that are updated most often and I've tested, in no particular order...in fact I'll list them alphabetically to avoid interpretations
AOSP based
Beanstalk
CandyKat
CM11
Infamous (IOAP)
PAC-Man
TwistedKat
Vanir
Sense based
Viper ROM 3.1.3
Liberty ROM
Sorry for the long post but I wanted to get most in a single place and if you'll have more questions we'll detail them later. Just try something... READ READ READ...each thread contains valuable info about each procedure and step and also the experience of the users. I know it is easier to ask but don't forget it's YOUR PHONE and YOUR INTEREST to see things working on it. So you should make some effort to read and search also
Good luck
I've read the entirety of your post now, and it's definetly helpful!
As it's pretty late here atm, i will come back to the tread tomorrow and S-Off and all that jazz. Im not a complete moron on this area, allthough thats what it probably seemed like Im glad i asked before i did anything, cause this was alot more complicated then when i was flashing ROMs when the phone came out.
I will definetly try to hold on to my current Radio as i have had no complaints ever on connection and service. So thanks for telling me about that, otherwise i would probably have flashed a new one each time.
Ill be sure to keep you posted on my progress tomorrow, just incase i totally **** up or something, or just cant get myself to understand something. If it is as easy to flash ROMs as it used to be once im ready to flash again, ill figure out my Next ROM, so im grateful that you listed a few of them that i can try out.
Again i wanna thank you for taking the time to explain a total Noob how to go about doing this, i really appreciate it!
rapier's post just about expresses all the basic info you need, couldnt have been put better!!
as far as going on to the newer sense based roms i'd suggest not to take that road yet as they require hboot 2.16 and it can get fairly tricky to go back to the previous hboot.
also for hboot 2.15 also you have more choice for roms available... just a point of view!!
happy flashing!!
So, now im totally lost. did the S-off, and now im trying to do the firmware, but im clueless here as i cant find the folder adb/fastboot in my platfomr-tools sdk folder or whatever you wanna call it. It wants me to place the firmware inside the adb folder, and i cant find any folder with that name.
I followed a guide on how to get adb working on my computer as i did not have that anymore on my PC, so had to redo it.
was following the guide, and did not see this "2. Now place the Firmware_named_something.zip into your adb/fastboot folder" at first, and tried to flash and was welcomed with cannot open "named file here" for obvious reasons when i saw step 2.
but this step 2 is what is confusing me, as ive mentioned, there is no adb/fastboot folder. is this a folder i make somewhere in my sdk? or what am i missing here. to give you the full info, i used this guide:
http://forum.xda-developers.com/showthread.php?t=1752270
the second post.
i remember having fastboot in that sdk folder on my old PC, but did not get it this time around when following these instructions, maybe thats what im missing
Jahrern said:
So, now im totally lost. did the S-off, and now im trying to do the firmware, but im clueless here as i cant find the folder adb/fastboot in my platfomr-tools sdk folder or whatever you wanna call it. It wants me to place the firmware inside the adb folder, and i cant find any folder with that name.
I followed a guide on how to get adb working on my computer as i did not have that anymore on my PC, so had to redo it.
was following the guide, and did not see this "2. Now place the Firmware_named_something.zip into your adb/fastboot folder" at first, and tried to flash and was welcomed with cannot open "named file here" for obvious reasons when i saw step 2.
but this step 2 is what is confusing me, as ive mentioned, there is no adb/fastboot folder. is this a folder i make somewhere in my sdk? or what am i missing here. to give you the full info, i used this guide:
http://forum.xda-developers.com/showthread.php?t=1752270
the second post.
i remember having fastboot in that sdk folder on my old PC, but did not get it this time around when following these instructions, maybe thats what im missing
Click to expand...
Click to collapse
ADB/fastboot are not folders, are commands. What that instruction meant was to place the firmware zip in the same folder where your ADB/fastboot executable is. Usually this is in "android-sdk/platform-tools". You'll notice there the ADB and fastboot executables
Rapier said:
ADB/fastboot are not folders, are commands. What that instruction meant was to place the firmware zip in the same folder where your ADB/fastboot executable is. Usually this is in "android-sdk/platform-tools". You'll notice there the ADB and fastboot executables
Click to expand...
Click to collapse
OMG! That makes more sense, still that sentence he used in the guide was pretty misleading though. literally tried making a fastboot folder with the .exe in alot of different folders xD
Will try that one out and see if it works! Thanks, AGAIN!
EDIT:
Just tried to put the firmware inside C:/android/sdk/platform-tools/ folder, but still i got
"Error: Can not open 'Fuu_Downgrade2.15_Unbranded.zip'
EDIT:
Turns out there was a program instead of a .exe :s just tried though, and it failed.
"FAILED (rempote: 99 unknown fail)
EDIT:
Apparently the S-OFF didnt work. Tried Rumrunner, as i didnt understand jack **** about the alternatives
EDIT:
Tried Facepalm aswell, not 100 percent sure if i did it right though, as there was no confirmation anywhere, but still no S-OFF