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
<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.
* I love the color orange.HTC Evo 2.3.3 Gingerbread Root Collaboration
The Lowdown on Everything
FASTBOOT
HTC's RUU releases basically run the adb reboot bootloader code, reconnect to the phone, verify the version and run a series of fastboot commands to install the contents of the PC36IMG (detailed below). In the same way it may be possible to run fastboot commands from command prompt with the SDK installed if you can time it just right in the flashing process, or not. The bootloader can be quite picky when it comes to letting anyone or anything flash anything lower than the version on the phone, or unsigned.
Click to expand...
Click to collapse
PC36IMG
The PC36IMG is what is flashed in the bootloader. The contents of the zip include the radio, system, and more. As long as S-ON is present the bootloader won't flash any PC36IMG that isn't signed by HTC themeselves, however with S-OFF you can flash custom PC36IMGs as well as downgrade, because the bootloader doesn't check the firmware version to see if it's newer or not. If someone was however to be a sneaky awesome ninja and steal HTC's secret sauce then we could simply sign any PC36IMG we wanted to and fake a newer version in the android info txt.
Click to expand...
Click to collapse
RECOVERY
From my understanding the stock recovery references alot with the bootloader to check for most of the same checks it looks for in the PC36IMG, but in the update.zip HTC includes for updates. The stock recovery won't flash anything but signed HTC update.zips either, which again you need the special sauce to sign. Custom recoveries like Amon RA or Clockwork remove the security and don't reference with the bootloader (since your phone has to be S-OFF anyways to flash a custom recovery.) A custom recovery is the key in flashing customs roms and kernels, if you can achieve it with the security on (S-ON) the you won't even have to worry about achieving S-OFF. However, that's near impossible due to the security in the bootloader HTC implements with updates. Which is why the bootloader has to be cracked to install anything.
Click to expand...
Click to collapse
RUU
The RUU is an official tool HTC puts out so people can reflash there phone with a stock firmware just like if it is brand new and your turning it on for the first time. The files included inside of the RUU frontend include the PC36IMG which is essentially what is flashed in the process, but in a fancy way I guess you could put it. The same security applies to the RUU, you can't downgrade versions without S-OFF because the bootloader still checks the version on the phone currently to see if it can flash the PC36IMG or not (when security is on [S-ON] )
Click to expand...
Click to collapse
APKS
I'm sure alot of you know of applications such as Visionary or Z4Root, they both use common exploits to root your phone in a simple application, first temp root then permanent root. They push the approiate resources, Superuser, su, busybox, set the permissions for everything to run, and clean up everything in the blink of an eye thanks to simple scripts. The same thing is still quite possible with any exploit, the exploit just has to be found in the software. You find the exploit you gain root. You have root you can do almost anything to your phone, but S-OFF still plays a role in everything with what you can and cannot flash. Sigh. I know right..
Click to expand...
Click to collapse
Our Mission
The whole purpose of this thread is to collaborate on possible ways to obtain S-OFF and/or root on 2.3.3, either update. We are community, thus we must act like one, and not bash each other for trying. If you have a truthful idea or any questions feel free to post them. You never know, you could very well help with rooting the latest update. This has gone on far to long it's been almost 2 months and no root. This is our time to free each other from the chains of security because we all like to be dangerous sometimes.
Click to expand...
Click to collapse
Possible Rooting Ideas
What Works What Doesn't
I encourage everyone to try previous rooting methods, and methods to obtain S-OFF and experiment as much as they feel comfortable with, you never know what you might find. We could be overlooking something.
Click to expand...
Click to collapse
There is no right or wrong answer only better ones than others. Please do not bash users, or slander them for there ideas, everyone has a right to post, but please stay on topic. /end
Am I missing something?
Sent from my PC36100 using XDA Premium App
lil_bono said:
Am I missing something?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Just give me a few, I'm still typing.
<done></done>
<words>I'll be back on tomorrow, I'm going to go lay down and talk to my friend. Feel free to comment with any ideas. I, myself, am looking into and working very hard to achieve S-OFF and root for the 2.3.3 update, it will come in time. That's just the key; time.</words>
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
ill jsut post a small snippet of thanks for thaking this initiative, i dont know about android os myself one bit, so i can hardly contribute, but would there be a way to "fool" the hboot or Ruu version number ?
either fooling the hboot into thinking the ruu one is trying to flash ( to downgrade of course) is a higher version one, or to somehow change the RUU itself to report a different version number? i realize this may sound incredibly stupid as my programming knowledge is very limited, but jst throwing it out there...
once again, thanks for taking this initiative for the evo 4g community
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
This should take off
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
skatrwannabe3 said:
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
Click to expand...
Click to collapse
Hey, great idea. Just so you know, there is no "bounty" on rooting the ota. I dont even know where that term came from. I just started a thread to say that I am desperate for root, I will pay for someone to figure it out. I never asked anyone or expected anyone else to throw money in on it too. It has since grown into a 600+ dollar pot, and I think that its a good thing. The people that take the time to root it should get a pat on the back.
On topic: I see a bunch of people saying to downgrade, isnt temp root gonna come before that? Shouldnt temp root be the thing to focus on first?
I'm not much of a programmer but ill brick my phone as many times as needed lol
Sent from my PC36100 using XDA App
github said:
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
Click to expand...
Click to collapse
I've personally never been the leader of a rooting or S-OFF project before, but my knowledge of Android on a whole is pretty vast. I do develop roms and kernels as well as themes and apps for Android in general, so I guess I'm pretty qualified?
fldash said:
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
Click to expand...
Click to collapse
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Who rated the thread bad?
bubby323 said:
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Click to expand...
Click to collapse
but does the RUU update the hboot itself?
the point is , older hboots and android software are already rooted, if we can get back to those , the end result is the same, we get root, then upgrade using a stock rooted rom, problem solved
bubby323 said:
What Works What Doesn't
Click to expand...
Click to collapse
My recent failures attempts while on 4.24 S-On:
Amon_Ra Recovery PC36IMG.zip flashed from Hboot
Signed 3.70 PC36IMG.zip flashed from Hboot
Signed 4.24 PC36IMG.zip flashed from Hboot (it loads/updates, but is basically a factory reset)
3.70 RUU exe
UnrEVOked3
some chucklehead
bubby323 said:
Who rated the thread bad?
Click to expand...
Click to collapse
Eh, I put in a 5 star vote to make it up, also to show the uselessness of voting.
Has anyone looked at the contents of a PC36IMG.zip? I am still decompliling one, but its a fun task to decipher all of the code. Another thing I need is for someone to tell me which files I should be looking for as far as HTC signing. What I would like to do is maybe strip it from the stock one, and insert it into a custom image.
Sent from the land of motorcycles!
Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Issues:*
1. If you update you will get a newer hboot, you may not be able to use other older ruu's such as 1.85, etc. Recommend immediately making a backup once rooted, unlocked, etc.*
2. Updating results in boot.IMG from custom roms not being flashed again. Have to flash the boot.IMG of custom Rom in fastboot as before.*
3. Radio.img will not flash on new hboot either must be done in fastboot same as boot.img.
HTC One X for AT&T ROM Update | 8.02.2012
Starting August 2nd 2012, HTC will be rolling out a system update for the HTC One X.
This update will only be available for AT&T HTC One X customers and will be sent to the device over the air. Once the release is ready, users will receive a notification on their device advising them of this update and provide instructions to receive and install it. Users can proactively check for this update by going to Home > All Apps > Settings > AT&T Software Update > Check for updates.
As an alternative solution, the system update can be downloaded to a PC and manually applied to the device. See the section at the bottom of these instructions for more information.
This system update includes:
New features:
NFC Capabilities
Additional content added to HTC Hub
Third party music applications accessible from the Car application.
Fixes/Updates:
Wi-Fi connectivity fixes
Improved Bluetooth automobile compatibility
3G/4G connectivity improvements
HTC Sense fixes
Contacts synchronization fix
Network time fix (clock displays 30 minutes off)
WARNING: During the upgrade process the device will reboot multiple times and show software upgrade screens. Do not remove the battery as this will stop the update and your device may be rendered inoperable!
Getting Started
Before you proceed with the update, make sure you have done the following:
Set aside approximately 20 minutes to allow the device to update, possibly longer based on Wi-Fi network speed
Connect the device to a charger
Ensure the battery is charged to at least 30%
Connect to a stable Wi-Fi network to download the software file.
Installation instructions
To manually perform the update, follow these steps below:
From the Home screen, tap All apps and then tap Settings.
Tap AT&T Software Update.
Tap Check for updates.
Tap OK to download the update.
After you select your method of download, you will be prompted with a Wi-Fi or Data fee warning message. If this is acceptable, tap OK to start the upgrade process.
Status of the download can be viewed in the Notifications pull down.
Once the download is complete, the user will be prompted to install from the Notifications pull down. Tap the System update to begin the upgrade process.
Tap OK to begin the update process to software version 2.20.502.7.
Device will reboot and begin installation. Users will not be able to use their device during the installation process (approximately 10 minutes).
System update complete. Tap OK to continue
Manual system update instructions:
If you are outside of AT&T/Wi-Fi coverage, or the update is not found, you may perform a manual system update.
Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
Download and save the HTC One X™ for AT&T ROM update to your PC.
Connect your device to your PC via the supplied USB cable. NOTE: You must have HTC Sync Manager installed on your PC in order to run the update.
NOTE: If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/us/support/.
Ensure the device is properly recognized on the PC, then locate the HTC One X™ for AT&T ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
Follow all of the system update wizard instructions shown on your PC.
Once the update is complete, click Finish in the Wizard and the device will reboot.
Once the device reboots, the initial setup wizard will appear.
Once the initial setup process is complete, the device is ready for use.
Download
portions of this post copyright HTC 2012. All rights reserved to them.
kewl
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
.
Third party music applications accessible from the Car application.
Click to expand...
Click to collapse
WOOT.
Thank you for not using File Factory haha
"NFC capabilities"????
Sent from my HTC One X
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yeah if you know what you're doing, but damn I'm going to miss the one stop flashing we used to have.
eraste said:
Here is the RUU for the OTA ATT 2.20 update.
Warning if you use this RUU you cannot go back to a lower RUU ( 1.85, etc ) or lower firmware as the HbOOTS are different! This is more for us that have already done the update. This will help us get back to stock if something goes foul.
There is no benefit for anyone to run this RUU as of now until root, etc is sorted out. Like I said for now mainly for us that already updated.
Thanks to scrolser for the link and DvineLord for initial find
Click to expand...
Click to collapse
I thought that was good?
XsMagical said:
OP really needs to post the warnings that come with the new RUU! Do not flash if you run custom roms
Click to expand...
Click to collapse
This was to be helpful for us that already did OTA. I agree tho if one isint literate in the world of android wait to use this until all the things above are worked out.
scribed on my 2.20 HOX
slippers67 said:
Well, it's not that bad really. As long as you have supercid you can unlock your bootloader again, install twrp recovery, and go back to flashing custom roms. You simply lose the ability to flash kernels within recovery, instead having to revert to doing it in fastboot. Honestly it isn't that much of an inconvenience.
Click to expand...
Click to collapse
yea thats fine if you know how, but why make everyones life harder when this upgrade is older then the asia 2.23.
its just going to make a lot of un needed posts to developers asking why the rom dont boot and so on. Run this ruu and it will cause more problems then anyone needs. As well as set you back from any S-Off development.
But that is my warning. Just saying, i cant see it from my house, my phone flashes
kernels just fine and always will. One Stop flashing.
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I know i am, Ive been down this road several times in the past and i know what to flash and not to flash. That being said, I,m just trying to warn anyone that thinks the ruu is better then the rom alone...
gunnyman said:
I just hope you dev guys are extra super careful with your phones. Get a replacement with 2.20 on it and you're screwed.
Click to expand...
Click to collapse
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Nrod0784 said:
To be honest I jumped on the update. It fixed a lot of the issues I had with 4.0.3 sense. I still have my unlock and I'm rooted. These times are like mini vacations from flashing. I also happen to have confidence in you devs, and also know that sooner or later (probably later) HTC will release source for this updated kernel and the dev will kick off again.
Although I don't envy you devs having to deal with people who don't read.
Thanks eraste for posting this as well as the guide for updating safely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Anytime
scribed on my 2.20 HOX
eraste said:
I prefer ATT based things, not racist lol just prefer the ATT stuff it works better for me as I'm in America. I would like to think root, mount points, etc will be available so everyone can benefit. This is important because of your statement. Anyone needing a new phone now for some reason be it broken, screen etc will get this build. Not 1.85 anymore. I definitely don't think it needs to be backseated just because asia is 2.23. Us in America will be screwed as new phones ship with 2.20 not 2.23. I have faith lol who knows new hboot may have a flaw that finally allows s off.
scribed on my 2.20 HOX
Click to expand...
Click to collapse
Well I'm in america too! but i thought a warning would be nice, But what do i know
i think his warning was sufficient enough. he stated no benefits of flashing. unless you already did it prior. plus there are other threads who state warnings as well. people dont care or dont read and will flash anyway :laugh:
not taking sides i see what people do here that go against there better judgments or even when told not too :laugh:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
eraste said:
Drop box just suspended my public links for excessive traffic lol lame. Changing hosts now sorry guys.
Click to expand...
Click to collapse
whoa and i just downloaded too lol. just in time add to the RUU collection lol
I've been out of the scene for years and have long since moved away from my Sensation 4G. Its sitting here collecting dust and although probably not worth a helluva lot I'd like to sell it while someone can get some decent use out of it still.
My question is, how do I return it to stock so I can sell it to the "average Joe". I'll keep it unlocked and rootable but how can I put the original HTC rom back on so I can advertise it as "stock"? Currently running an old v4.1 version of MIUI with 4EXT Touch Recovery, and honestly I dont even know where the HTC updates stop; or if its still supported.
I'd like to just get this phone to a sellable "stock" condition and give the user the choice to tweak it (or not).
OKors said:
I've been out of the scene for years and have long since moved away from my Sensation 4G. Its sitting here collecting dust and although probably not worth a helluva lot I'd like to sell it while someone can get some decent use out of it still.
My question is, how do I return it to stock so I can sell it to the "average Joe". I'll keep it unlocked and rootable but how can I put the original HTC rom back on so I can advertise it as "stock"? Currently running an old v4.1 version of MIUI with 4EXT Touch Recovery, and honestly I dont even know where the HTC updates stop; or if its still supported.
I'd like to just get this phone to a sellable "stock" condition and give the user the choice to tweak it (or not).
Click to expand...
Click to collapse
If your device is S-Off then you can install and ICS RUU which can be downloaded from here
http://forum.xda-developers.com/showthread.php?t=1661591
Thanks,
Couple more questions;
-Once installed and returned to factory will this allow OTA updates from HTC?
-The filename mentions Europe, I'm U.S., does it matter?
-Is it really an .exe file? What is it designed to do?
-Do I run it from 4EXT (off the sim card) or from PC?
-It says "Firmware is the same as earlier firmware included in 3.32 RUUs". Which FW is that? I'm on 1.17 still
I should also mention: T-Mobile USA with S-Off
Thanks, and sorry in advance for the noob questions. Like I said, I've been out of the loop for years and have no desire to tweak my phone again.
I just wanna get this back to stock and sell it!
OKors said:
Thanks,
Couple more questions;
-Once installed and returned to factory will this allow OTA updates from HTC?
-The filename mentions Europe, I'm U.S., does it matter?
-Is it really an .exe file? What is it designed to do?
-Do I run it from 4EXT (off the sim card) or from PC?
-It says "Firmware is the same as earlier firmware included in 3.32 RUUs". Which FW is that? I'm on 1.17 still
I should also mention: T-Mobile USA with S-Off
Thanks, and sorry in advance for the noob questions. Like I said, I've been out of the loop for years and have no desire to tweak my phone again.
I just wanna get this back to stock and sell it!
Click to expand...
Click to collapse
you run the exe directly from pc connected the device to it in fastboot mode
and another thing you have to know is when installing ruu.exe
you are forgeting 4ext recovery
it restores completely everything back to stock
but i suggest to use a t-mobile usa ruu.exe
also you will have OTA updates.but this device is discontinued
the latest official update is to ics android
rzr86 said:
you run the exe directly from pc connected the device to it in fastboot mode
and another thing you have to know is when installing ruu.exe
you are forgeting 4ext recovery
it restores completely everything back to stock
but i suggest to use a t-mobile usa ruu.exe
also you will have OTA updates.but this device is discontinued
the latest official update is to ics android
Click to expand...
Click to collapse
Great, thanks. I'll look for a Tmob US ruu.
Firmware, do I need to flash to the required FW in Hboot first or will the installer take care of that for me? If so where did HTC leave off?
I'm looking at 3.33 being the most current ICS FW. But that's based on this thread:
http://forum.xda-developers.com/showthread.php?t=1459767
OKors said:
Great, thanks. I'll look for a Tmob US ruu.
Firmware, do I need to flash to the required FW in Hboot first or will the installer take care of that for me? If so where did HTC leave off?
I'm looking at 3.33 being the most current ICS FW. But that's based on this thread:
http://forum.xda-developers.com/showthread.php?t=1459767
Click to expand...
Click to collapse
forget that thread
it is not for you
ruu restores official firmware too
the latest firmware from HTC is 3.33
note: after ruu installation only S-OFF will remain as it is but i suggest to leave on S-OFF
Hi,
I'm still on 4.4.2 and wish to backup, S-OFF, root, and upgrade to 5.x (open to trying a custom ROM). I'm completely new to this and have a couple questions:
In what order should things be done? My guess is the order listed above?
Can I just follow the instructions in the stickies (firewater, etc), or are they out of date?
If upgrading to a non-Sense ROM, will software (camera, sound, etc) work as well?
If you have any tips/suggestions/advice/things you wish you'd known, I'd greatly appreciate it. Thanks!
1.Go here.
Download APP/EXE version (which i did).
Follow the instruction & flash the exe ruu.If you encounter problem when flashing,just flash this latest hboot & reflash the app exe ruu.Do this only if you encount with any flashing error.
Let it reboot.That's all .
2.No matter which rom you are flasing SENSE or SENSLESS,just flash the latest firmware first.Then you can flash any rom.
Before you go loading RUUs I would recommend turning s-off first. For that you have to use sunshine. Firewater is discontinued and won't work even if you have the files. You would have to run sunshine BEFORE upgrading to lollipop because it hasn't (yet) been updated to work on the lollipop update. Hope this isn't too late of advice.
Caspid said:
Hi,
I'm still on 4.4.2 and wish to backup, S-OFF, root, and upgrade to 5.x (open to trying a custom ROM). I'm completely new to this and have a couple questions:
Can I just follow the instructions in the stickies (firewater, etc), or are they out of date?
If upgrading to a non-Sense ROM, will software (camera, sound, etc) work as well?
If you have any tips/suggestions/advice/things you wish you'd known, I'd greatly appreciate it. Thanks!
Click to expand...
Click to collapse
Hi,
Follow this xda thread to root http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-10-5-1-0-283-t2872873.
After rooting, install NUT's dual recovery. Then download pre-rooted zip for Android 5.0.2 from development section and flash through revovery.
Sent from my C6602 using xda Forums PRO
SurenderK said:
Hi,
Follow this xda thread to root http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-10-5-1-0-283-t2872873.
After rooting, install NUT's dual recovery. Then download pre-rooted zip for Android 5.0.2 from development section and flash through revovery.
Sent from my C6602 using xda Forums PRO
Click to expand...
Click to collapse
These instructions are for a different phone. It's the same for the M8?
cntryby429 said:
Before you go loading RUUs I would recommend turning s-off first. For that you have to use sunshine. Firewater is discontinued and won't work even if you have the files. You would have to run sunshine BEFORE upgrading to lollipop because it hasn't (yet) been updated to work on the lollipop update. Hope this isn't too late of advice.
Click to expand...
Click to collapse
What, really? Even for 4.4.2? I thought sunshine was only required for later versions.
Caspid said:
These instructions are for a different phone. It's the same for the M8?
What, really? Even for 4.4.2? I thought sunshine was only required for later versions.
Click to expand...
Click to collapse
So I don't know what that guy is talking about. Steer clear of that advice.
The only way to unlock the bootloader of a Verizon m8 is sunshine and it also turns s-off which is sweet. Firewater worked for older versions, I actually used it myself many months ago. Shortly after sunshine released for the m8 they turned off the online part of Firewater. Sunshine does cost $25 but I donated more than that as a thanks for Firewater, it seems fair.
Once s-off you will be able to do pretty much whatever you want, flash recovery (which can then flash custom roms), upgrade firmware, downgrade firmware, flash radios, etc. However this also means that you can brick your phone if you don't know what you're doing. Definitely don't go following instructions instructions for another phone.
It you don't mind sense, flashing doddat's stock rooted RUU is a one step process and you're done.
If you want bloat removed, the ability to make nandroid, and the many features of custom roms then you need to flash TWRP recovery and you can go to town. If you want bloat removed then there are some pretty good sense based roms. I ran viper Rom for a while and was pretty happy. Then there's gpe and cm based roms. As far as I know most are pretty bug free.
Just be careful. Like I said, s-off allows you to do both awesome and detrimental things to your phone. Know what you're doing, how to do it, and most importantly how to undo it before you do anything.
cntryby429 said:
So I don't know what that guy is talking about. Steer clear of that advice.
The only way to unlock the bootloader of a Verizon m8 is sunshine and it also turns s-off which is sweet. Firewater worked for older versions, I actually used it myself many months ago. Shortly after sunshine released for the m8 they turned off the online part of Firewater. Sunshine does cost $25 but I donated more than that as a thanks for Firewater, it seems fair.
Once s-off you will be able to do pretty much whatever you want, flash recovery (which can then flash custom roms), upgrade firmware, downgrade firmware, flash radios, etc. However this also means that you can brick your phone if you don't know what you're doing. Definitely don't go following instructions instructions for another phone.
It you don't mind sense, flashing doddat's stock rooted RUU is a one step process and you're done.
If you want bloat removed, the ability to make nandroid, and the many features of custom roms then you need to flash TWRP recovery and you can go to town. If you want bloat removed then there are some pretty good sense based roms. I ran viper Rom for a while and was pretty happy. Then there's gpe and cm based roms. As far as I know most are pretty bug free.
Just be careful. Like I said, s-off allows you to do both awesome and detrimental things to your phone. Know what you're doing, how to do it, and most importantly how to undo it before you do anything.
Click to expand...
Click to collapse
So instead of making a new thread my question is similar to the guys above. I am on 4.4.2 but already have S-off and root, TWRP installed etc. I have had the phone since launch and have been happy enough to not worry about updating or changing anything too much.
Anyhow, I am now interested in updated, I read a few months ago that 4.4.2 should update to 4.4.3 before going to 4.4.4. Is this still the case if I only want to go to 4.4.4? Still the case if I go all the way up to 5.0.1?
Second, apologies if the answer is the same as above but I just want to be sure I am clear, I am s-off already, will I need sunshine moving forward for after I updated? Or since I am s-off already will I stay that way and be able to root without any additional steps after updating?
Resputan said:
So instead of making a new thread my question is similar to the guys above. I am on 4.4.2 but already have S-off and root, TWRP installed etc. I have had the phone since launch and have been happy enough to not worry about updating or changing anything too much.
Anyhow, I am now interested in updated, I read a few months ago that 4.4.2 should update to 4.4.3 before going to 4.4.4. Is this still the case if I only want to go to 4.4.4? Still the case if I go all the way up to 5.0.1?
Second, apologies if the answer is the same as above but I just want to be sure I am clear, I am s-off already, will I need sunshine moving forward for after I updated? Or since I am s-off already will I stay that way and be able to root without any additional steps after updating?
Click to expand...
Click to collapse
I recall that idea of necessary incremental upgrades being passed around for my previous HTC device, the Rezound. I suspect that it's not true although I certainly don't know enough to support that statement. My suspicion is that if you were to flash any of the RUUs which were posted by dottat you will successfully boot any of our official software versions regardless of what version you're coming from. This presumes the prerequisite that you're s-off in order to permit downgrading (if you choose) and/or use of some of his s-off-required RUUs. With as full-proof as those RUUs seem to be, the worst case scenario is that your device bootloops requiring another RUU. I don't know that you're at all too much risk of bricking your phone provided you are flashing files that are meant for your exact model (be weary of flashing international/AT&T RUUs and such to a verizon phone) and are following instructions.
Regarding sunshine, as long as you don't issue specific fastboot commands to relock the bootloader or turn s-on, then you should have no further use for Sunshine. The only reason I can see someone taking updates incrementally is if they want to take them OTA. However, if you're s-off then I would highly recommend just using an RUU. None of the RUUs or firmware update zips will relock the bootloader or turn s-on. I can think of very few reasons to do either of those with the exception of returning to full stock for a warranty return. I believe that all of the RUUs will restore stock recovery, but since they don't relock the bootloader, you can always just flash back your custom recovery via fastboot or bootloader and re-root your stock rom. Alternatively, once you have a custom recovery you can flash any one of the many custom roms which will almost certainly come pre-rooted.