Please use this new guide to flash a new radio
http://forum.xda-developers.com/showthread.php?t=1684477
We are glad we have our unlocked devices and can happily flash Custom ROM`s, backup and restore nandroids or flash mods. Nevertheless there are still some restrictions, since we still have no S-Off. This week the latest 1.78 OTA update arrived and devs are working hard to upgrade their ROM`s to the new One S ROM base.
BUT...
assuming you already use a Custom ROM and you want to flash latest stuff, in any of these ROM`s built on latest base you will still use your old Radio, which was shipped initially. Since 1.78 OTA brought a new Radio (baseband), with S-Off it would be painless to flash it via fastboot or recovery, but we still aren`t there.
BUT...
there is a way to use latest ROM base with latest Radio. You just need to be willing to go that extra route.
What`s the benefit of upgrading a Radio?
The baseband is responsible for:
Signal quality
WiFi and Bluetooth connectivity
GPS / aGPS
Can improve battery due to improved signal quality
Can even improve camera
and more...
Who needs this?
Everyone who flashed first Custom Rom BEFORE OTA 1.78 arrived and wants to enjoy latest Baseband. Please check first, whether OTA for your region / provider is already available.
This is how you can upgrade your RADIO without S-Off
Step 1:
Make an nandroid in recovery
Step 2:
Download my stock 1.53 nandroid (maybe someone can upload to a faster mirror), unzip it and copy the folder in sdcard/clockworkmod/backup folder
http://minus.com/mquC9WDG6/4
Dropbox mirror - thx @ angelsanges
https://www.dropbox.com/s/av1w0aip9a...3_original.rar
Step 3:
Restore my Stock153Clean.zip nandroid in recovery
Step 4:
Download my fastboot folder (in case you haven`t installed SDK) and copy stock recovery image and clockwork recovery image in the unpacked fastboot folder
Fastboot folder: http://minus.com/mIA3OFkYq/3
Stock recovery: http://minus.com/mIA3OFkYq/18
Clockwork Recovery (or use another CWM version, whatever you prefer): http://minus.com/mIA3OFkYq/4
Step 5:
Boot in Bootloader (with adb reboot bootloader or Power and Vol. down) and connect your device. Navigate in cmd to your fastboot folder and flash stock recovery with:
fastboot flash recovery recovery_signed.img
Step 6:
Reboot and check for system updates in settings info (that can last a while, sometimes you need to try several times), download and install when prompted. Wait a few minutes for your device to install the update and reboot.
Step 7:
Boot in Bootloader and connect your device. Navigate in cmd to your fastboot folder and flash Clockwork recovery with:
fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
Step 8:
Restore your own nandroid (which does not backup and restore radio images) and now you have upgraded your Radio
Screenshot from my device running Virtuous ROM with latest Radio from 1.78 OTA Update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
???????
tks, but if i have s-off ,i don't need to this way....
And Sorry, but you have the old Rom 1.70.666.1...
cosmic76 said:
tks, but if i have s-off ,i don't need to this way....
And Sorry, but you have the old Rom 1.70.666.1...
Click to expand...
Click to collapse
There's no s-off yet for One S.
Sent from my HTC One S using xda premium
cosmic76 said:
tks, but if i have s-off ,i don't need to this way....
And Sorry, but you have the old Rom 1.70.666.1...
Click to expand...
Click to collapse
I lol'd.
Some people had luck and got a device with S-OFF..
Just to let you know
yup !!! lucky b**tards!
Theres a couple people on these forums with the One S developer phone too !! Ive seen pics as proof !
Retracts Statement in Shame. Hangs head. Sorry, My bad bro. Lolz @ Self.
Thx!! Exactly what I needed But your stock ROM has such a slow download
he_stheone64 said:
Step 8:
Restore your own nandroid (which does not backup and restore radio images) and now you have upgraded your Radio
Click to expand...
Click to collapse
Sorry for the noob question,
But if I don't want to restore mi old nandroid, but i want install new ROM..I can do that by simply putting the zip in sd?
Thanks
Ivan
he_stheone64, I guess I am out of luck again and this won't work with CID T-MOB101?
any one got a mirror for the 1.53 nandroid ? got a estimated time of 5 hours left !!, also, couldnt i just use a 1.53 rom ?? its clean, untouched stock, from RUU, no root or nothing...
will i also get this update with vodafone UK CID ? VODAP100 i think it is
EDIT, The update isnt even available !! yet according to my provider it is !
i have stock ROM and stock recovery ! still no bloody update
nice, probably this will fix the umts<>hspa toggling problem i am experiencing ...
since the download of the nandroid backup takes hours i tried restoring my own backup of stock 1.53. only difference is root. the update was detected immediately after i rebooted from cwr. sadly the update process did not succeed. the progress bar stopped after ~25% and then i just got a red triangle with an exclamation mark in it. after 1-2 minutes the phone rebooted and it's still stock 1.53 with old radio. any ideas what could be missing?
i did revert to stock recovery and there was ~2gb of space left on /sdcard/
probably root?!
//edit: found the problem. i changed 3 lines in build.prop which gets patched in the update process ... removed changes (and unrooted) and now the update works.
link for the stock rom is very very slow
ZeppeMan said:
Thx!! Exactly what I needed But your stock ROM has such a slow download
Click to expand...
Click to collapse
That`s why I asked for a mirror in OP
ivyn87 said:
sorry for the noob question,
but if i don't want to restore mi old nandroid, but i want install new rom..i can do that by simply putting the zip in sd?
Thanks
ivan
Click to expand...
Click to collapse
yes you can...
AndrewSM said:
he_stheone64, I guess I am out of luck again and this won't work with CID T-MOB101?
Click to expand...
Click to collapse
As fas a I now, T-Mobile hasn`t released an update yet, so in that case you still need to be patient.
azzledazzle said:
any one got a mirror for the 1.53 nandroid ? got a estimated time of 5 hours left !!, also, couldnt i just use a 1.53 rom ?? its clean, untouched stock, from RUU, no root or nothing...
will i also get this update with vodafone UK CID ? VODAP100 i think it is
EDIT, The update isnt even available !! yet according to my provider it is !
i have stock ROM and stock recovery ! still no bloody update
Click to expand...
Click to collapse
As mentioned in the OP, check FIRST whether your provider already delivers an update. If you have a matching RUU for your device, you can flash back also with the RUU. This certainly requires some extra steps, but does the job.
he_stheone64 said:
As mentioned in the OP, check FIRST whether your provider already delivers an update. If you have a matching RUU for your device, you can flash back also with the RUU. This certainly requires some extra steps, but does the job.
Click to expand...
Click to collapse
according to my provider, its already out, but i cannot find the update.. i went back to stock rom, stock recovery, still couldnt find it...
i have downloaded the OTA update.. someone extracted it and uploaded it, but as for how to flash it.....ive no idea lol
ZeppeMan said:
Thx!! Exactly what I needed But your stock ROM has such a slow download
Click to expand...
Click to collapse
Any improvement with this new radio?
he_stheone64 said:
As fas a I now, T-Mobile hasn`t released an update yet, so in that case you still need to be patient.
Click to expand...
Click to collapse
Thanks. Well I flashed the genuine ROM 1.53 over the stock Tmobile bloatware ROM. The OTA will work anyways when Tmo releases it? Because I've read that OTA doesn't work if the system partition has been modified...
azzledazzle said:
according to my provider, its already out, but i cannot find the update.. i went back to stock rom, stock recovery, still couldnt find it...
i have downloaded the OTA update.. someone extracted it and uploaded it, but as for how to flash it.....ive no idea lol
Click to expand...
Click to collapse
This is info I got from the guy who posted the OTA zip:
Need stock recovery to install. And you may loose root.
Root Keeper from market is said to work for keeping root. The "one click-tool" here in the development section can easily flash stock recovery for you. You can always re-flash CWM after update is installed.
And this is how you would install OTA zip file for sensation, guess it works the same way. You can give it a try, I can't since I don't have matching CID (the list of supported CIDs is in the OTA zip file in firmware.zip): http://forum.xda-developers.com/showpost.php?p=16862231&postcount=1
Related
I wrote this guide do to the general lack of information for users about the Jellybean update. This guide is basic in nature and will provide you with all the tools and links you need to update from an ICS based ROM to the official JB ROM then re-root or prepare for custom ROM.
If you already have the Official JB Update simply unlock it and proceed to Section #2. This guide was intially intended for those who cannot update because of Asus stupid lock out program once you unlock.
Warning
I have tested this guide on my device multiple times and never have one single issue. I cannot say it will work perfect for you! I am not responsible for anything that goes wrong including but not limited to; A $500 brick! The economy imploding worse, Nuclear war, End of the world on 12/12/12!
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
Windows 7 or Windows 8 PC
General Overview
Flash Asus JB update
Flash TWRP 2.2.3
Flash SuperSU or Custom ROM
Profit!
Please do not be afraid to ask for help!
This guide was written for people who need help. I didint write it for myself because I already know how to do it, lol
Donations gratefully accepted but never expected!
Please hit Thanks and Rate the thread 5 Stars
Click to expand...
Click to collapse
-Scott
Section 1 - Flash Asus JB update
Obtain the appropriate Jellybean update from the Asus Support Site HERE
Go to Downloads and pick the local / region specific update file for your device. For the intent of this guide I will focus on the US Based variant but all other devices will follow the exact same steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After you download the Jellybean update you must extract the zip file in the zip (I dont know why they did this!). The name of the first zip file will be "US_epad_user_10_4_4_16_UpdateLauncher.zip"
The zip file inside of that will be "US_epad-user-10.4.4.16.zip" This is the file we will flash to update to JB!
To do this open the first zip file with your zip [rogram of choice, (as you can see I use 7zip) and pull out the only other zip file in there (US_epad-user-10.4.4.16.zip).
Once you have that file copy it to you internal SD card. Although, untested, external SD should work too.
Now.... Reboot to recovery. To do this power down the device, and then Hold Volume Down and then press power untill you get a menu that says press XX key to boot to recvoery.
Once in recovery you MUST wipe data before you continue!
Now flash the ROM file you just copied like it was a plain old fashioned custom ROM or Root.zip. Just select it and flash!
Once the flash is done reboot. Dont be scared... This will take a LONG time... Maybe in upwards of 3 to 5 minutes. This is normal. Its completely rebuilding the device!
Once the device is all booted up and you are at your desktop we can proceed to Section 2.
Section 2 - Flash TWRP 2.2.2.3
First we need to obtain TWRPREcovery. You are free to use any version you want, including ClockworkMod (although I highly discourage CWM and recomend TWRP).
You can find TWRP HERE. Remember I recommend the 2.2.2.3 version. 2.3.0.0 gave me some issues.
Now that you have the file download you need to rename it to "recovery.blob" for use with my tool!
Now download the attached tool and unzip it. It contains the fastboot and ADB files you will need to flash the recovery.
Next place the recovery.blob in the folder
Turn on USB Degging in the developer menu of the device. This is very important otherwise you will be just sitting there forever, lol
Now initiate the "Recovery Install Tool.bat" file. This will reboot you to bootloader and flash the recovery for you ;c)
Done!
Section 3 - Flash SuperSU or Custom ROM
Needless to say I am partial to custom ROMS ;c) But I know some may be content with just flashing root so I will show you how to obtain the correct root file and or ROM and give a brief over view on how to flash them. This section will be pretty routine and will not contain a lot of new info for most of you!
Obtain my favorite root app, SuperSU, from HERE
Copy to storage
Reboot to recovery
Flash and Be rooted!
Same steps for a custom ROM. The best Custom ROM can be found HERE! ;c)
Section 4 - Thanks!
Thanks to Dess_troy for making TWRP for our devices!
Thanks to Chainfire for the root app!
Thanks to all the Developers on XDA that have taught me (in one way or another) everything I know!
Special Thanks to all the CleanROM users who have inspired me to push CleanROM to be the premier custom ROM for your Android Device!
Please feel free to rebuild this for the Linux or Mac platform and re-distrubute!
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
scrosler said:
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
-Scott
Click to expand...
Click to collapse
A number of people have asked and I have usually replied that it is possible to use the Asus provided UnLock tool - the one on the website that says is only compatible with ICS - with a tablet that has been updated to JB.
In short the Unlock tool works in Jellybean!
You might want to add this as an addendum to your original post.
Cheers,
Eric
i apologize for my beligerant question but if i want to try the new cwm touch recovery, do i just rename it to recovery.blob? when i downloaded it it was the usual iso. when renamed it didnt change anything so i dont wanna brick my tab. figured id ask first. thanks for the awesome walk through tho man. i really apreciate it. loving your roms. have 2.0 downloaded already. also can you pm the link to your tf300 kernel you used? i need to show off some high quadrant numbers lol
Confused...
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
BlastTyrantKM said:
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
Click to expand...
Click to collapse
BlastTyrantKM said:
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This guide is for people who have already unlocked there device any may have had a custom ROM installed pre-JB.
You fall into a unique and rather off situation. I have never heard of some one not getting the OTA.
You could follow these steps but as a pre-step...
Download and unlock with the Asus unlock tool. Its on the same download page.
Download an ICS based recovery and use that in in place of the one noted for now. And then just start at Section 2. Then start back over at Section 1.
Basically we will put a recovery on your device in Section 2. Then start over at step 1 by applying the JB build then put a recovery back on, as it gets wiped off by Asus builds and your all set.
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
The stock recovery will only flash firmware zips with a certain name. Rename the zip to EP201_768_SDUPDATE.ZIP and try again.
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
yes you lose root. this will make your tf700 like the factory jellybean firmware which is not rooted. go back to op and keep reading. each section builds on the previous. first get the jellybean firmware. im still playing with mine stock its so damn smooth. then you flash a custom recovery using his tool. then you flash the zip which gives you root. then i would make a back up so you can always get back to that point. then you can look into custom roms like scotts sweet clean rom for tf700 series
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
To me it looks like you are trying to run the batch file without extracting the contents.
Thank you for this guide! Although it took me some time to understand it as I was on non-rooted/locked JB stock rom.
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually had similar problem as this guy. I was already on JB and the guide is made for people that are on ICS.
scrosler said:
To me it looks like you are trying to run the batch file without extracting the contents.
Click to expand...
Click to collapse
I am using a borrowed PC. I am a Mac user so forgive my ignorance. But when I look at the folder with Scott's Tool in it it looks like everything is extracted.
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually tried this last night with no luck. I guess it was something funny with my desktop in that it couldn't connect using fast boot. Anyway I brought it in to work and ran it here and everything is fine. I am going to throw your stock/root rom on it now. Thanks for your help!
CWM-SuperSU-v0.96.zip
Hello,
thanks a lot for the guide, it is really clear and detailed.
My question is something I did not find on the previous question and it is more a double check to be sure I am not doing something I should not.
You say to install SU with the package copied on the internal SD, and you added a link to the SU thread. in this thread, the only SU as a package you can find is CWM-SuperSU-v0.96.zip, as it is CWM, will it work if I install it with TWRP? or there is special settings in this package that will not be recognised by TWRP?
Thanks in advance for your help
Regards
hello, hope you guys can help me out:
everytime i try to flash trickdroid, viperones or zenROMplus i get the same similar error in TWRP which looks like this:
Updating parition details...
Formatting Cache using mke2fs...
Done.
Formatting Data using mke2fs...
Wiping Internall SDcard
Updating parition details...
Installing '/sdcard/TrickDroid_9.0.0.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
=======================
|Welcome to TrickDroid!|
|by torxx |
=======================
Formatting paritions...
E:Error executing updater binary in zip '/sdcard/Trick
Error flashing zip '/sdcard/TrickDroid_9.0.0.zip'
Updating partition details...
i have no problems flashing CM10 or CM10.1 nightly.
whats wrong with that?
Ville (s4) (o2 branding)
unlocked
s-off
hboot 2.13.0000
radio 1.11.50.05.28
TWRP v2.5.0.0
Flashing the Sense ROMs like TrickDroid or zenROM+ doesn't work in TWRP versions above 2.3.3.0.
Don't ask me why, but it doesn't work. You can temporarily flash it in an older recovery
fastboot boot recoveryname.img
Aah ok thanks! Didnt know that this was a well known problem with twrp v2.5+, because i didnt find such an error on google. Could u tell which recovery i should use? CWM or better lower twrp version? Is a twrp version lower than 2.3 buggy or fine?
turnschuh said:
Aah ok thanks! Didnt know that this was a well known problem with twrp v2.5+, because i didnt find such an error on google. Could u tell which recovery i should use? CWM or better lower twrp version? Is a twrp version lower than 2.3 buggy or fine?
Click to expand...
Click to collapse
TWRP 2.3.3.0 is the beat IMO. It works fine for me and is very stable.
Sent from my One S using Tapatalk 2
Ah, that explains the issue I've been having recently. Thanks for the help! I reverted to 2.3.3 and was able to get viper to flash again. I haven't noticed any difference between 2.3.3 and 2.5 on this device. Are there any downsides to keeping 2.3.3 for the foreseeable future?
HOSer_hut said:
Ah, that explains the issue I've been having recently. Thanks for the help! I reverted to 2.3.3 and was able to get viper to flash again. I haven't noticed any difference between 2.3.3 and 2.5 on this device. Are there any downsides to keeping 2.3.3 for the foreseeable future?
Click to expand...
Click to collapse
It's quicker to wipe on the newer one, but other than that it's the same. (Save for a few UI elements)
Sent from my One S using Tapatalk 2
The major change is the addition of otg in versions above 2.4
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Thank you guys. i was able to flash it with CWM Now i want twrp 2.3.3.0 but didnt find any download link on the official site nor on trusted sites like this forum. Can someone help me out again? (last question from me in this thread^^) thanks in advance!
turnschuh said:
Thank you guys. i was able to flash it with CWM Now i want twrp 2.3.3.0 but didnt find any download link on the official site nor on trusted sites like this forum. Can someone help me out again? (last question from me in this thread^^) thanks in advance!
Click to expand...
Click to collapse
On the TWRP website, search for Ville and you'll find all the previous versions (not the goo.im app link)
oh lol yea found it thanks, think im blind sometimes..
Yes!! Back in action
Awesome! So glad I stumbled onto this thread. The Google searches were all coming up with nothing until this one. I was using 2.6.1.0 when I initially had this issue then upgraded to 2.6.3.0 hoping that would resolve but nothing. Rolled back to 2.3.3.0 and now I'm good to go :good:
Just FYI, to anyone else that comes after me this fix worked for me and I'm using a T-Mo Galaxy S2 so this fix is not device-specific.
The issue I'm running into is that I can't figure out how to revert to 2.3.3.0. I'm using 2.6.0.0 and in the cmd prompt I type "fastboot erase cache" and then "fastboot flash recovery xxxxxx.zip". But when I do that I'm forever stuck in fastboot until I flash 2.6.0.0 again. It's like my HOX+ is married to that version and can't use anything else. Any help would be greatly appreciated.
aaron79att said:
The issue I'm running into is that I can't figure out how to revert to 2.3.3.0. I'm using 2.6.0.0 and in the cmd prompt I type "fastboot erase cache" and then "fastboot flash recovery xxxxxx.zip". But when I do that I'm forever stuck in fastboot until I flash 2.6.0.0 again. It's like my HOX+ is married to that version and can't use anything else. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Fasboot flashing needs to be .img not .zip
extract your 2.33 zip so that you can flash the .img
fastboot flash recovery recovery.img (typing the name of recovery.img)
or download the img file from twrp website
http://teamw.in/project/twrp2
click on the "get twrp for your device" on the right and follow the links to the version you want for your particular brand of phone.
tivofool said:
Fasboot flashing needs to be .img not .zip
extract your 2.33 zip so that you can flash the .img
fastboot flash recovery recovery.img (typing the name of recovery.img)
or download the img file from twrp website
click on the "get twrp for your device" on the right and follow the links to the version you want for your particular brand of phone.
Click to expand...
Click to collapse
Thanks for the reply, tivo. My mistake on the .zip. I meant .img. I made sure to download the correct version, but still have the same issue. I just get stuck on the white HTC development screen. So, I can get into bootloader and TWRP (2.6.0.0 only), but can't flash ROMs. I'm just stuck with no OS and can't seem to find a work-around. My bootloader says Tampered and Unlocked/S-On. I did, however, use an unlock guide for the One X by accident, instead of the X+. That is the only thing I can think that would cause my troubles...
charliearthur said:
Awesome! So glad I stumbled onto this thread. The Google searches were all coming up with nothing until this one. I was using 2.6.1.0 when I initially had this issue then upgraded to 2.6.3.0 hoping that would resolve but nothing. Rolled back to 2.3.3.0 and now I'm good to go :good:
Just FYI, to anyone else that comes after me this fix worked for me and I'm using a T-Mo Galaxy S2 so this fix is not device-specific.
Click to expand...
Click to collapse
sorry how to revert back? I have TWRP 2.5.0.0
Edit:Nevermind I found out, but that wasn't the case for me I'm trying to flash liquid jb v2.37 and after I downgraded twrp ,I've still got an error (error 7)...
How do i get 2.3.3 when the goo.im page only goes back to 2.5 for my device? Also is this solution still relevant for flashing an AOKP 4.4 kit kat nightly rom on the Sprint HTC One (m7wls/m7spr)
usaff22 said:
TWRP 2.3.3.0 is the beat IMO. It works fine for me and is very stable.
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
tried to find this on the link for a T-Mobile phone, but it only has nexus 7. So I googled it and every carrier seems to have the previous versions on techerrata EXCEPT T-Mobile.
Any help would be appreciated
Learnerspermit said:
tried to find this on the link for a T-Mobile phone, but it only has nexus 7. So I googled it and every carrier seems to have the previous versions on techerrata EXCEPT T-Mobile.
Any help would be appreciated
Click to expand...
Click to collapse
If you just search [ville] on the TWRP website, it should have the One S recovery you need. It doesn't matter if you have the T-Mobile of the International version.
usaff22 said:
If you just search [ville] on the TWRP website, it should have the One S recovery you need. It doesn't matter if you have the T-Mobile of the International version.
Click to expand...
Click to collapse
Sorry for not mentioning that part as well.
Went to the TWRP site and see NO SEARCH ENGINE, nor anything there that says Ville. Nor Googling TWRP ville.
Learnerspermit said:
Sorry for not mentioning that part as well.
Went to the TWRP site and see NO SEARCH ENGINE, nor anything there that says Ville. Nor Googling TWRP ville.
Click to expand...
Click to collapse
On the TWRP site, look for the "Get TWRP for your device" button in the upper right hand corner. Then that should bring up the search function:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is happening since i rooted my htc with the supersu zip method .
so here is the problem:
when the htc's battery dies and i connect it to the wall charger or usb so it boots into recovery and then when i press reboot system now it reboots normally. (running clockworkmod touch recovery)
how do i make it boot straight into the rom without booting into recovery?
Install TWRP- 2.3.0.0 , and stay away wrom clockwork. And install custom rom, they all are properly rooted, and busybox installed.
Still have the problem
Your phone isn't properly rooted, as this zip method fails some time.
Simply grab Su_Bbox* from here and flash it in recovery. If CWM recovery fails to flash that, download TWRP recovery from the same linked folder and 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' in fastboot mode of your phone.
SU and Busybox need to be properly installed for working root. It's not only (any) SU making it!
rootrider said:
Your phone isn't properly rooted, as this zip method fails some time.
Simply grab Su_Bbox* from here and flash it in recovery. If CWM recovery fails to flash that, download TWRP recovery from the same linked folder and 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' in fastboot mode of your phone.
SU and Busybox need to be properly installed for working root. It's not only (any) SU making it!
Click to expand...
Click to collapse
i saw you have a file called ville recovery signed is it the stock recovery?
LSGio said:
i saw you have a file called ville recovery signed is it the stock recovery?
Click to expand...
Click to collapse
Yes!
rootrider said:
Yes!
Click to expand...
Click to collapse
is it compatible with the s4 or s3 htc one s?
S4
--- edit ---
Whatever device you have, SU_Bbox will work on any phone, as it is device unindependant!!!
rootrider said:
S4
Click to expand...
Click to collapse
now im flashing the bbox file and gonna see how it goes
didn't fix my problem
did this happened to you and then after flashing bbox its gone?
LSGio said:
did this happened to you and then after flashing bbox its gone?
Click to expand...
Click to collapse
I had that reboot into recovery problem some time ago... But I'm not shure about the solution now...
Well, I'd need to know a few things now.
Device? S3 S4?
Rom? Stock or custom, if custom, which rom?
Recovery? TWRP or CWM and which version?
Kernel? Custom or stock?
Bootloader version and CID?
rootrider said:
I had that reboot into recovery problem some time ago... But I'm not shure about the solution now...
Well, I'd need to know a few things now.
Device? S3 S4?
Rom? Stock or custom, if custom, which rom?
Recovery? TWRP or CWM and which version?
Kernel? Custom or stock?
Bootloader version and CID?
Click to expand...
Click to collapse
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery
LSGio said:
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery
Click to expand...
Click to collapse
if you have skype it would be easier mine is:
lior_shvartz2
LSGio said:
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery
Click to expand...
Click to collapse
Ok, stock JB would mean that there is a write protection, invented with HTCs JB update (as long as you're using the stock kernel...).
To solve this, you'd need to flash any sense custom kernel (bricked, bulletproof, ElementalX). I'd recommend bulletproof (close to stock so).
BL and CID can be checked by starting bootloader mode. You'll see it below the tampered flag.
As Fanagoreca already mentioned, you should flash TWRP recovery (the one from my link above is 2.3.3.0, working good and for S4) by booting into fastboot mode and entering 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from terminal/command window.
After that you should flash a custom kernel to remove write protection, either in recovery or fastboot mode ('fastboot flash boot boot.img'). But through recovery should work.
Then flash SU_Bbox again from TWRP. The point is, I don't know if your version of CWM works as it should. Since the time this phone came out, CWM always had bugs and wasn't working in some ways. TWRP was pretty good to go with up to 2.3.3.0, after that version it started to become buggy for some things.
So just give it a try. I think it's not a big problem.
--- edit ---
Sorry, don't have skype.
---------- Post added at 09:50 AM ---------- Previous post was at 09:38 AM ----------
...
BL version comes into game, if you're s-on. Versions > 1.09 make it necessary to flash the kernel separately from your rom in fastboot mode. Else your system won't start, as there is no kernel...
Usually you'd unzip the kernel (aka boot.img) from your rom.zip and flash it with: 'fastboot flash boot boot.img' in fastboot mode.
CID will be relevant for receiving OTA updates or gaining s-off. So it's not that important this time.
rootrider said:
Ok, stock JB would mean that there is a write protection, invented with HTCs JB update (as long as you're using the stock kernel...).
To solve this, you'd need to flash any sense custom kernel (bricked, bulletproof, ElementalX). I'd recommend bulletproof (close to stock so).
BL and CID can be checked by starting bootloader mode. You'll see it below the tampered flag.
As Fanagoreca already mentioned, you should flash TWRP recovery (the one from my link above is 2.3.3.0, working good and for S4) by booting into fastboot mode and entering 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from terminal/command window.
After that you should flash a custom kernel to remove write protection, either in recovery or fastboot mode ('fastboot flash boot boot.img'). But through recovery should work.
Then flash SU_Bbox again from TWRP. The point is, I don't know if your version of CWM works as it should. Since the time this phone came out, CWM always had bugs and wasn't working in some ways. TWRP was pretty good to go with up to 2.3.3.0, after that version it started to become buggy for some things.
So just give it a try. I think it's not a big problem.
--- edit ---
Sorry, don't have skype.
---------- Post added at 09:50 AM ---------- Previous post was at 09:38 AM ----------
...
BL version comes into game, if you're s-on. Versions > 1.09 make it necessary to flash the kernel separately from your rom in fastboot mode. Else your system won't start, as there is no kernel...
Usually you'd unzip the kernel (aka boot.img) from your rom.zip and flash it with: 'fastboot flash boot boot.img' in fastboot mode.
CID will be relevant for receiving OTA updates or gaining s-off. So it's not that important this time.
Click to expand...
Click to collapse
im using ics right now (4.0.3) so i want to unroot and relock BL to update but firsst i want so solve this problem.
if i'll update will it fix my problem?
one more question:
the bootloader version is the HBOOT version? if it does so mine is 1.13
LSGio said:
im using ics right now (4.0.3) so i want to unroot and relock BL to update but firsst i want so solve this problem.
if i'll update will it fix my problem?
one more question:
the bootloader version is the HBOOT version? if it does so mine is 1.13
Click to expand...
Click to collapse
The update won't fix your problem. I think it's recovery related. So changing the recovery might solve it. You still should try that first. For running RUUs or OTA update you will need to flash custom recovery and relock bootloader. The tampered flag can only be removed when you s-off your device.
HBOOT version is bootloader version, here 1.13.
Which country you are living in? Be warned, that when you flash the latest OTA update (JB) from TMO US your partition for writing CID will be locked. And if you can't superCID your phone anymore, you will not be able to get s-off!
You should consider superCID'ing and getting s-off first. Once being s-off you can do anything with your phone.
rootrider said:
The update won't fix your problem. I think it's recovery related. So changing the recovery might solve it. You still should try that first. For running RUUs or OTA update you will need to flash custom recovery and relock bootloader. The tampered flag can only be removed when you s-off your device.
HBOOT version is bootloader version, here 1.13.
Which country you are living in? Be warned, that when you flash the latest OTA update (JB) from TMO US your partition for writing CID will be locked. And if you can't superCID your phone anymore, you will not be able to get s-off!
You should consider superCID'ing and getting s-off first. Once being s-off you can do anything with your phone.
Click to expand...
Click to collapse
i fixed my problem by updating trough OTA to JB (im from israel)
and btw you said that i should install custom recovery and relock to update but it failed so i flashed the stock recovery and than relocked and i achieved success.
do you have an idea when sense 5 is coming out to our device ?
LSGio said:
i fixed my problem by updating trough OTA to JB (im from israel)
and btw you said that i should install custom recovery and relock to update but it failed so i flashed the stock recovery and than relocked and i achieved success.
Click to expand...
Click to collapse
oops, sorry, you're right. I meant stock recovery but wrote custom.
LSGio said:
do you have an idea when sense 5 is coming out to our device ?
Click to expand...
Click to collapse
The first thing going on will be 4.2.2 and sense 5 for the m7 (one) in may or june. The One X will get updated to that as well around one month later, including blinkfeed and zoe. The One S will also be updated to Sense 5 but if there will be blinkfeed and zoe might be doubted. I personally think that this will be 4.2.2 as well.
I can't find the sources for that anymore, but I was reading about that yesterday or the day before.
rootrider said:
oops, sorry, you're right. I meant stock recovery but wrote custom.
The first thing going on will be 4.2.2 and sense 5 for the m7 (one) in may or june. The One X will get updated to that as well around one month later, including blinkfeed and zoe. The One S will also be updated to Sense 5 but if there will be blinkfeed and zoe might be doubted. I personally think that this will be 4.2.2 as well.
I can't find the sources for that anymore, but I was reading about that yesterday or the day before.
Click to expand...
Click to collapse
ok thank you for all this info now what is the proccess to S-OFF'ing my device
these are my device's stats:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And Hboot version is 2.15
CPU: S4
And i'm also using the latest hasoon2000's toolkit which looks like this:
UP!!
Go Here for instructions to S-Off
Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.
Chris95X8 said:
Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.
Click to expand...
Click to collapse
Why not flash the boot.img from the New Build.zip as you are S-ON?
khan.orak said:
Why not flash the boot.img from the New Build.zip as you are S-ON?
Click to expand...
Click to collapse
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.
Chris95X8 said:
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.
Click to expand...
Click to collapse
Aahhh yess
Can you just run an RUU from your carrier? That's a one-stop solution: will upgrade your firmware and HBOOT and you should be good to go.
Sent from my HTC One S using Tapatalk 4 Beta
Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4
Chris95X8 said:
Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Okay. Sure.
First, You will have to tell me your CID. You can find that out by getting CID GETTER from play store. It should tell you your CID in RED color.
Also, you run the RUU, it will upgrade you plus get you on stock, afterwards, IF it is locked again, you can unlock it and flash CM latest nightlies again. So no biggie there.
Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4
Chris95X8 said:
Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
I suppose that is Three (3) UK .
Okay, I found that there is no JellyBean RUU for your carrier. Same as they did with HTC One X.
But here's the deal, after relocking your bootloader, you can use This RUU which is an ICS RUU.
It will bring you to Stock ICS without changing your HBOOT and firmware. Afterwards, you should check for System Updates and receive JellyBean OTA. So that will take you to JellyBean + 2.15.0000 HBOOT + Newer Firmware.
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Yeah, that's right.
Yes, udpdate through WiFi as it is a big update to JB OTA. works everywhere.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
khan.orak said:
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?
Chris95X8 said:
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?
Click to expand...
Click to collapse
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff (unlocking, rooting etc), make nandroid backups of the new JB ROM. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.
khan.orak said:
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff, make nandroid backups. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.
Click to expand...
Click to collapse
That's how I did it :laugh:
Chris95X8 said:
That's how I did it :laugh:
Click to expand...
Click to collapse
Great. shouldn't be a problem then.
khan.orak said:
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.
Chris95X8 said:
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.
Click to expand...
Click to collapse
what recovery do you have right now?
khan.orak said:
what recovery do you have right now?
Click to expand...
Click to collapse
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?
Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Click to expand...
Click to collapse
If you want to root your device, just flash a flashable SuperSU.zip from recovery. Instant root.
---------- Post added at 03:44 PM ---------- Previous post was at 03:39 PM ----------
Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?
Click to expand...
Click to collapse
actually, I have been having issues with 2.6.0.0 flashing Carbon ROM. PACman worked fine. Can't say anything. Both worked okay with 2.3.3.0. You may give the latest a try.
Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Chris95X8 said:
Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
Click to expand...
Click to collapse
Oh. Just yesterday, some folks reported unsuccessful and corrupt RUU downloads from androidruu site.
You may use this one Here
If you are still S-On (or S-off but lazy or tentative) and want a simple way to return to the stock ROM and also be able flash back the stock radio and recovery then this may be for you.
XDA member migascalp gave me the idea of packaging stock ROM's with the aroma installer and include the ability to flash the stock recovery also as sort of a poor mans RUU since so many still are S-on and cannot properly run a RUU.
I have been making these for a few different versions depending on if we have the stock recovery, so mainly only major versions with a full stock dump or RUU.
See here: http://www.htc1guru.com/downloads/stock-rom-downloads/
While you can flash these roms on any M7_U or M7_UL, they are made to match the version base.
Also note that these packages do not update any firmware. However when you choose to install the stock recovery you will then be able to get OTA updates after locking your bootloader.
Many have already used these packages to get back to stock and get OTA's or for returning for service, but I never got around to making a post for them, so here it is. Also before using you can check out the full collection of return to stock items in the Collection Thread and Return To Stock Guide Thread.
I have also created a flashable tool for you to be able to remove Tampered and Lock and Unlock your bootloader. This may be useful for those returning to stock. Thread is located HERE.
You simply flash these in recovery like installing any other rom.
Here is a video Demo of the install. This demo is of the new AT&T OTA but the install and procedure is the same. I will update this video for the roms in the this thread later:
Here are the screen shots of the Aroma Installer. Sorry for some the bad edits, its really hard to get a good pic taken manually at bootloader or recovery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
I test each of these packages myself thoroughly before posting. However I make no guarantee's on the subject of OTA's because I do not use them, but many of the users of these packages report on the success of that aspect.
You should re-lock your bootloader to get OTA updates.
Here are the instructions.
As long as you chose to install the stock recovery and didn't add root, all you should have to do is re-lock your bootloader after this and you will be almost out of the box stock. You can re-lock your bootloader with this fastboot command:
Code:
fastboot oem lock
If you are S-on and that doesn't work you may have to use this:
Code:
fastboot oem relock
Remember that if you are S-On and re-lock your bootloader, it will say RELOCKED instead of LOCKED.
If you are S-Off then you should be able to get to Locked with this ADB Shell command from scotty1223's thead:
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
Or if using an older hboot this revone command:
Code:
revone -l
Also if you chose to flash the stock recovery during the rom install, and your phone doesn't boot or you experience any other issues remember you will have to reload your custom recovery via fastboot:
Code:
fastboot flash recovery twrp.img
I will continue to make more of these and I would prefer to keep it to roms for which we have a full stock dump, but the requests are overwhelming for just about everything, so I may start with some popular carrier versions based off of user submitted backups or stock rom only dumps.
Here are the Download Links:
Guru Reset M7 2.24.401.8
md5: b576ec69ff7ea86d4be2dbc3a8e15cc0
Guru Reset M7 2.24.401.1
md5: a5e4b3f512a6aa6b9acf2e9a4b6ee995
Guru Reset M7 3.22.1540.1
md5: 21325c8a7737b4521ee392d7af9333e1
Guru Reset M7 3.62.401.1
md5: 6444b41a1f332f31345d5ead674382d7
Guru Reset M7 3.63.707.4
md5: 6aba67e56889124c4ab5188bba15a569
Guru Reset M7 3.22.661.1
md5: ba876502d7311955d5e6e839b0af74d0
Guru Reset M7 2.24.707.1
md5: e9f6aba0e6cd997899382cbda2da1ebe
Guru Reset M7 2.24.709.1
md5: d4c3eee1a5ddc6d5903d98e48f93c6f0
Guru Reset M7 2.24.163.2
md5: ce009d2262fa1f98f7800ec69680180a
Guru Reset M7 2.24.111.3
md5: bf991f8a4767249da5238502befcc627
Guru Reset M7 2.24.161.1
md5: f3d237594e8c21c63da51ba4ae4988f1
Guru Reset M7 2.24.771.3
md5: 4226b81cb1dfd483f36b6d4a75e1474e
Guru Reset M7 2.24.73.1
md5: cdc043cd7941f8157e1e16aa3d549a9a
Guru Reset M7 2.24.841.1
md5: ca37c13808ba61bd48b91ac1cd25e480
Guru Reset M7 2.24.980.2
md5: d530dcef4cf842e3ba87457da5226e2c
Guru Reset M7 2.24.1020.1
md5: 9cfb71bdb6919521a459211e80f63cf5
Guru Reset M7 1.29.401.13
md5: 92987058e9e8c83cd4d88b2f523e359f
AT&T Versions:
Guru Reset M7 1.26.502.12
md5: 30c0072fb5a02ca75a609bc57a3f34e9
Guru Reset M7 1.26.502.15
md5: 79d290ec018ea3761e8ad35f62476c5a
T-Mobile Version:
Guru Reset M7 T-Mobile 1.27.531.11
md5: f7bd2e1e2e89fab44d8713eda693c0a3
Sprint Versions:
Guru Reset M7 Sprint 1.31.651.2
md5: f3d055dea52b60674833c2cbb87893fb
Guru Reset M7 Sprint 1.29.651.10
md5: 29a4b3cd30a848a8e6c9e1e7bd079740
........Credits........Thanks to baadnewz for most of the stock dumps
Thanks to V6-Maniac for the 3.22.1540.1 Dump
Thanks to Indirect for the 1.31.651.2 Stock ROM
Thanks to migascalp for the 2.24.73.1 and 2.24.1020.1 Stock Dumps
Thanks to Mike1986 for the 3.62.401.1 Stock Dump
If these helped you out please consider a small donation or just a thanks would be great.
Enjoy! :good:
THANKS FOR THIS CRUSHALOT BUT ONE QUICK QUESTION PLEASE I UPDATED MY M7 TO 2.24.709.1 CAN I USE THE Guru Reset M7 3.22.1540.1 TO UPDATE TO STOCK THANKS FOR YOUR TIME
will earlier s-off untouched ? or what will change, was it :-
- hboot = as per rom zip
- radio = as per rom zip
- boot = relocked or unlocked
- pvt ship = s-off or s-on
- cid = will reset or what
sorry for noob ..
I installed without problems 2.24.401.8 but the camera is worse now, well known problem with purple dots, but I never had it before, stock or custom rom, it is the first time with this problem, I hope that HTC will release soon international version of 4.3 rom hoping for changing firmware via OTA.
Interesting.will test and advise tomorrow
SULEY1 said:
THANKS FOR THIS CRUSHALOT BUT ONE QUICK QUESTION PLEASE I UPDATED MY M7 TO 2.24.709.1 CAN I USE THE Guru Reset M7 3.22.1540.1 TO UPDATE TO STOCK THANKS FOR YOUR TIME
Click to expand...
Click to collapse
Well you can flash and run that 3.22.1540 rom but you won't able to get OTA's but that stock rom is much newer than your base anyway and you could always change back.
wzu7 said:
will earlier s-off untouched ? or what will change, was it :-
- hboot = as per rom zip
- radio = as per rom zip
- boot = relocked or unlocked
- pvt ship = s-off or s-on
- cid = will reset or what
sorry for noob ..
Click to expand...
Click to collapse
Not sure what you are asking.
This is just a rom install and it won't change any firmware items. No change to hboot and it won't change your s-on/s-off status.
GelullaBarr said:
I installed without problems 2.24.401.8 but the camera is worse now, well known problem with purple dots, but I never had it before, stock or custom rom, it is the first time with this problem, I hope that HTC will release soon international version of 4.3 rom hoping for changing firmware via OTA.
Click to expand...
Click to collapse
Yes, I think the firmware is the key to fixing the camera issue. The full RUU for 3.xx versions seems to be the best option, however that only help those with S-off.
Also some of the cameras will never see a great improvement and simply need to exchange the device for a replacement.
Will this work with hboot 154 thanks.
Sent from my HTC One using XDA Premium 4 mobile app
ipmanwck said:
Will this work with hboot 154 thanks.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This will run on any hboot version. There is no firmware, this is rom software only.
Thanks man. So if I flash this will I go back to 100% stock and be able to receive OTA updates from HTC ? I was hoping to trade this phone but can't as it shows it's tampered in recovery.
Sent from my HTC One using XDA Premium 4 mobile app
ipmanwck said:
Thanks man. So if I flash this will I go back to 100% stock and be able to receive OTA updates from HTC ? I was hoping to trade this phone but can't as it shows it's tampered in recovery.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are currently running the matching firmware (shows 2.24.401.x on your bootloader screen for OS) then you run the matching version rom and recovery then yes the Tampered will be removed. However when you lock the bootloader if you are s-on it will show Relocked instead of Locked.
However you should be able to get OTA updates.
2 More Reset's Posted
Uploaded 2 more Stock ROM Reset's and added to the OP.
Here are the new ones:
Guru Reset M7 3.18.709.2
md5: 70d2512605b3942786f0f7436d9042b2
Guru Reset M7 2.24.163.2
md5: ce009d2262fa1f98f7800ec69680180a
Enjoy
More to come, but it takes me a while to do these. It would help if I had a second One to use for development. I am working on getting one when my funds will allow.
EDIT - I have pulled the 3.18.709.2 Reset file. The more I test with it I realize something is wrong. Hope to have that version back online soon.
crushalot said:
Uploaded 2 more Stock ROM Reset's and added to the OP.
Here are the new ones:
Guru Reset M7 3.18.709.2
md5: 70d2512605b3942786f0f7436d9042b2
Guru Reset M7 2.24.163.2
md5: ce009d2262fa1f98f7800ec69680180a
Enjoy
More to come, but it takes me a while to do these. It would help if I had a second One to use for development. I am working on getting one when my funds will allow.
EDIT - I have pulled the 3.18.709.2 Reset file. The more I test with it I realize something is wrong. Hope to have that version back online soon.
Click to expand...
Click to collapse
could you make an AT&T version please?
JEANRIVERA said:
could you make an AT&T version please?
Click to expand...
Click to collapse
So AT&T has RUU's, so why exactly would you want one of these?
If you are S-on and want to run the latest AT&T leak, you can flash it in fastboot.
If you just want to run the the leaked AT&T 4.3 software but keep your current firmware version, I could make one, but I am not sure how the 4.3 software will run on the older firmware.
Please clarify what you want.
Thanks
crushalot said:
So AT&T has RUU's, so why exactly would you want one of these?
If you are S-on and want to run the latest AT&T leak, you can flash it in fastboot.
If you just want to run the the leaked AT&T 4.3 software but keep your current firmware version, I could make one, but I am not sure how the 4.3 software will run on the older firmware.
Please clarify what you want.
Thanks
Click to expand...
Click to collapse
I want to be able to return to stock Rom and recovery flashing and not running an ruu
Sent from my HTC One using Tapatalk 4
JEANRIVERA said:
I want to be able to return to stock Rom and recovery flashing and not running an ruu
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
OK, but what version of the stock rom? If I make a stock rom package for the 4.1.2 version, then your touchscreen won't work because AT&T has already pushed out 4.2.2. However we don't have a 4.2.2 RUU for AT&T, so I can't build a 4.2.2 stock rom.
I could build a stock AT&T rom for 3.10.502.2 but that was only a leak so I can't guarantee you would be able to get future OTA updates, nor could I verify that the 4.3 rom works perfectly on the older 4.2.2 firmware.
Given this, do you want a stock rom installer for 3.10.502.2? If so let me know and I will try to get one together within 24 hours.
Thanks
crushalot said:
OK, but what version of the stock rom? If I make a stock rom package for the 4.1.2 version, then your touchscreen won't work because AT&T has already pushed out 4.2.2. However we don't have a 4.2.2 RUU for AT&T, so I can't build a 4.2.2 stock rom.
I could build a stock AT&T rom for 3.10.502.2 but that was only a leak so I can't guarantee you would be able to get future OTA updates, nor could I verify that the 4.3 rom works perfectly on the older 4.2.2 firmware.
Given this, do you want a stock rom installer for 3.10.502.2? If so let me know and I will try to get one together within 24 hours.
Thanks
Click to expand...
Click to collapse
Ok I have one idea lets wait till 1 or 2 weeks more since HTC said the update for AT&T it is just around the corner and the you can make it from official RUU probably
Sent from my HTC One using Tapatalk 2
Will 1.29 work on my o2_102 (deutsch o2)? I need to get back to stock, I am on fw 3.22, I'd try to flash firmware 1.29, restore nand o2 backup found online (thank you BugsyLawson, God bless you), and have "your" 1.29 package at hand in case of problems...shall it work, right (i'm s-off)?
Is it possible to have a zip of O2 UK 2.24.206.7? Or even an earlier version 4.1.2? I would just love to get rid of the tampered message on the bootloader