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
Related
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
--->**Discontinued** HTC One S USA T-Mobile JellyBean Update * Sense 4+* Rooted * Deodexed * Aroma Installer * APM <---
* Awesome battery life
* This Rom is based off the TMOUS_3.14.531.17.70rd RUU
* Root, BusyBox, Zipalign, Unsecure boot.img, APM, Deodexed,
* Busybox, Busybox-run-parts supported, /data/app-enabled, and Bash-shell support
* Added a few startup scripts
* Added WWE Languages
* HTC ONE Sounds
* Please Read Change Log For Further Fixes, Changes, Additions.
-> I am not responsible for any phone that may become bricked. <-
** This ROM is not to be used for a base ROM **
{
"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"
}
Wallpaper Download
---------------------------------------------------------------------------
Installation Instructions
----------------------------------
Working Folders
SkyDrive
Google Drive
Android File Host Dev Account
-----------------------------------
* Download your ROM
* Put on the sdcard / Internal storage
* Fastboot flash boot boot.img (only if you are S-ON)
* Flash in recovery and use the Aroma Installer
* Done!
* If your WiFi isn't working and you are S-OFF Flash WiFi Fix S-OFF. If you are S-ON try Htc_on_s_wifi_fix-S-ON
--------------------------------------------------------
* How to backup your WiFi Partition
Code:
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Next type "dd if=/dev/block/mmcblk0p19 of=/sdcard/mmcblk0p19" and hit enter. This will dump the partition to your sdcard.
4. Next type "dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18" and hit enter. This will dump the partition to your sdcard.
5. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.
Now the partition's are backed up, to restore them do the following.
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Type "dd if=/sdcard/mmcblk0p19 of=/dev/block/mmcblk0p19"
4. Type "dd if=/sdcard/mmcblk0p18 of=/dev/block/mmcblk0p18"
Now they are restored.
Please click thanks if this helped you.
--------------------------------------------------------------------------------------
* How To Root, Update Firmware, & Flash A Custom ROM
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/showthread.php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/showthread.php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.3.3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery.
--> Intermission
Your current phone status
Bootloader = Unlocked
S-OFF
HBOOT = 2.15
CID = T-MOB010
Custom Recovery = TWRP 2.3.3
You are now ready to flash any Jelly bean ROM / OR my ROM
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Add-On / Mods
SkyDrive // Google Drive
Advanced Power Menu (Thanks Behold_this)
Open APN
Open APN With UnKnown_AutoBrightness MOD
Removed Carrier from Default Lockscreen
Autobrightness Mod
Lower Autobrightness Mod
Ridiculosly Low Autobrightness Mod
Stock Green Battery
1% Blue Battery Mod (Thanks he_stheone64)
Volume Wake With Advanced Power Menu
Volume Long Press To Skip Tracks
Long Press Back To Kill 3rd Party Apps
Modified Roise With Menu
Transparent Rosie with Clear NavBar
Better WiFI Calling Icons
Green Power Saver Leaf LOL
Blue Power Saver Leaf LOL
Transparent Rosie (Thanks Flashalot for the Tutorial)
Transparent Notification Pull Down (Thanks Flashalot for the Tutorial)
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Custom Recovery
TWRP 2.3.3 Recovery.img (Must be Unlocked)
--------------------------------------------------------------------------
---> Change Log <---
HTML:
V2.0 ***CURRENT***
* Aroma interactive installer
* App removal
* Added Open VPN support
* Added SQL3lite support
* Added memory enhancer script
* EXT4 write back
* Sense 5 icons by default
* Updated all mods with the Sense 5 icons
________________________________________
V1.9
* Re-based from 3.14.531.17.70rd RUU
* Uploaded a complete firmware.zip ( S-OFF & CID 11111111, S-ON TRY AT YOUR OWN RISK )
* Added Languages from WWE
* Added HTC ONE sounds
__________________________________
V1.8.1 FULL ROM
*Fixed Missing Permissions
*Fixed ADB
*Updated SU
*Updated WP_MOD.KO for Updated Kernel
(( MUST INSTALL AS A FULL ROM TO FIX MISSING PERMISSIONS ))
(( THERE IS A NO WIPE FULL ROM SO YOU WONT LOSE ANYTHING ))
____________________________________
V1.8 FULL ROM *******REMOVED**********
*Re-based from 3.14.531.17.70rd OTA
* (( Please also Flash the v1.8 firmware.zip ))
V1.8 Update Only *****REMOVED******
Update includes
* New Boot.img from OTA
* Patched files from 3.14.531.17.70rd OTA To Fix Battery Drain
* (( Please also Flash the v1.8 firmware.zip ))
_________________________________________
V1.7.1 FULL ROM
* Added A few Power Saving tweaks to build.prop
* Added WWE Languages
// For best battery life - change WiFi sleep policy to NEVER - Make sure Best WiFi Performance is UN-Checked.
V1.7.1 Update
* Added A few Power Saving tweaks to build.prop
// For best battery life - change WiFi sleep policy to NEVER - Make sure Best WiFi Performance is UN-Checked.
____________________________________
V1.7
* Updated to fix WiFI Calling Battery Drain :)
* Also added some AGPS stuff in as well
* Some Kernel Tweaks
* Stopped debugger icon from showing up every time you plug in your phone to your computer.
--> Go to --> WiFi --> advanced settings and change [B]keep Wi-Fi on during sleep[/B] to [B]Never [/B]or [B]Only when plugged in[/B].
[COLOR="Red"]// I DO NOT GIVE PERMISSION TO USE THIS ON ANY OTHER ROM // I WILL FIND OUT [/COLOR]
____________________________________
V1.6A
REMOVED
____________________________________
V 1.6
* Migrated over updates from EU 3.16.401.9
* Modified Rosie with transparent dock and landscape mode
* Updated boot.img (kernel) 3.16.401.9 based
* 1% Battery Mod by default
____________________________________
V1.5A
* Removed the /DATA/ wipe from the Updater-Script
-------------------------------------------------------
V1.5
* Added WiFi setup in system setup
-------------------------------------------------------
--> V1.4
* Added Start Up Scripts
* Fixed sys/read_write issue (thanks [URL="http://forum.xda-developers.com/showthread.php?t=2059411"]flar2[/URL])
* Updated to latest SuperSU
* Added Secure Box and Block Box to message app
* Cleaned up a few things
--------------------------------------------------------
--> V1.3
* Removed T-Mobile Bloat
--------------------------------------------------------
--> V1.2 Initial release
mkinney88 said:
I have received the jelly bean update from t-mobile this morning. This is only the OTA.zip pulled from my phone. I know it is Android 4.1.1 I am currently working on this as a flash-able rooted room but i figured i would upload the OTA.zip for everyone else. I am currently uploading now so it might be a few minutes before you can download it. I am uploading as of 1:40pm EST.
Dropbox
Roughly 20 Minutes
Click to expand...
Click to collapse
Thanks for working on this! This is exactly what I was hoping someone would do. I really don't want the hassle of re-locking, flashing stock recovery, etc. just to get the OTA.
I'm currently running CM 10.1 but I've always had some weird GPS issues with CM on my One S and miss the Sense camera quality.
I'm backing up everything now and happen to be free most of the evening tonight so if you get it assembled as a flash-able rooted ROM let me know and I'd be happy to try it and/or help test it.
DigitalMonk said:
Thanks for working on this! This is exactly what I was hoping someone would do. I really don't want the hassle of re-locking, flashing stock recovery, etc. just to get the OTA.
I'm currently running CM 10.1 but I've always had some weird GPS issues with CM on my One S and miss the Sense camera quality.
I'm backing up everything now and happen to be free most of the evening tonight so if you get it assembled as a flash-able rooted ROM let me know and I'd be happy to try it and/or help test it.
Click to expand...
Click to collapse
I didn't have to re-lock my bootloader. I just changed my CID back to tmobile and ran a RUU. After the RUU and also the OTA update im still S-off and unlocked, it just flashed the stock android recovery back. FYI
mkinney88 said:
I didn't have to re-lock my bootloader. I just changed my CID back to tmobile and ran a RUU. After the RUU and also the OTA update im still S-off and unlocked, it just flashed the stock android recovery back. FYI
Click to expand...
Click to collapse
Good to know in case I get impatient. Haven't taken the time to get S-off but I've been unlocked, rooted and custom recovery since about day 5 of owning my One S.
I'm at work for a few more hours so I figured I can be patient and hold off and be available to test flashing a ROM if you end up doing one because if that's an option I'm guessing a lot of people will go that route rather then doing the CID change, RUU and wait for the OTA to download and install.
I've got a fresh titanium backup and nandroid done so I'll wait patiently to see where you go with this.
DigitalMonk said:
Good to know in case I get impatient. Haven't taken the time to get S-off but I've been unlocked, rooted and custom recovery since about day 5 of owning my One S.
I'm at work for a few more hours so I figured I can be patient and hold off and be available to test flashing a ROM if you end up doing one because if that's an option I'm guessing a lot of people will go that route rather then doing the CID change, RUU and wait for the OTA to download and install.
I've got a fresh titanium backup and nandroid done so I'll wait patiently to see where you go with this.
Click to expand...
Click to collapse
I will hopefully have a rooted deodexed and odexed version of this tonight unless i run into a problem. If I don't run into any problems expect a ROM around 10:30pm EST. It will only be rooted and stock I wont have anytime tonight to do modifications.
I am s-on, locked bootloader and on the ics version of the pacman rom....what steps do i need to take to flash the update?
lightninbug said:
I am s-on, locked bootloader and on the ics version of the pacman rom....what steps do i need to take to flash the update?
Click to expand...
Click to collapse
It's not flash-able yet. He was just posting the actual OTA.zip for other developers who may want to pull files from it.
DigitalMonk said:
It's not flash-able yet. He was just posting the actual OTA.zip for other developers who may want to pull files from it.
Click to expand...
Click to collapse
I know...let me rephrase.. How can I go about getting the official ota? With my setup listed above
Sent from my Nexus 4 using xda premium
mkinney88 said:
I will hopefully have a rooted deodexed and odexed version of this tonight unless i run into a problem. If I don't run into any problems expect a ROM around 10:30pm EST. It will only be rooted and stock I wont have anytime tonight to do modifications.
Click to expand...
Click to collapse
Perfect. Exactly what I'm looking for. I'd like to try the stock experience again with JB just to see what it's like if nothing else. My usage habits have changed recently and JB stock may well be good enough for me. I really want the really good camera back just with buttery goodnewss and Google Now.
lightninbug said:
I am s-on, locked bootloader and on the ics version of the pacman rom....what steps do i need to take to flash the update?
Click to expand...
Click to collapse
--> Download the T-Mobile RUU tmobile htc one s ics RUU
--> Run the RUU and it will return you to stock. Then go to setting->software->Update and get the first OTA then after you install that update go back and check for update again. ** You can also try running the ruu and then put the jellybean OTA on your internal storage and reboot into the stock recovery and apply update from internal storage. (i have not tried this yet) ** Should work though
mkinney88 said:
--> Download the T-Mobile RUU tmobile htc one s ics RUU
--> Run the RUU and it will return you to stock. Then go to setting->software->Update and get the first OTA then after you install that update go back and check for update again. you can also try running the ruu and then put the jellybean OTA on your internal storage and reboot into the stock recovery and apply update from internal storage.
Click to expand...
Click to collapse
No need to relock boot loader? Or flash stock recovery?
Sent from my Nexus 4 using xda premium
lightninbug said:
No need to relock boot loader? Or flash stock recovery?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am S-OFF and i didn't re-lock my boot-loader or flash recovery. I only use to re-locked my boot-loader when i was s-on but i don't know if it makes a difference. You should be S-OFF by now why are you not.
mkinney88 said:
I have received the jelly bean update from t-mobile this morning. This is only the OTA.zip pulled from my phone. I know it is Android 4.1.1 I am currently working on this as a flash-able rooted ROM but i figured i would upload the OTA.zip for everyone else.
//// I also uploaded the firmware.zip for this update. \\\\
Dropbox
--> If you download this please give me a thanks <--
**UPLOADED**
Edit: I can confirm if you are s-off this will not affect you at all. I did change my CID back to T-MOB010. I did NOT re-lock my bootloader, I ran the TMOUS_2.35.531.7 RUU to get back to stock and downloaded the OTA for JellyBean.
This does include GOOGLE NOW
HBOOT-2.15.0000
Radio-1.13.50.05.31
Click to expand...
Click to collapse
i didnt change my CID....and locked the bootloader...flashed stock recovery and ran the ota...
aegentirony said:
i didnt change my CID....and locked the bootloader...flashed stock recovery and ran the ota...
Click to expand...
Click to collapse
Thanks for the feed back
aegentirony said:
i didnt change my CID....and locked the bootloader...flashed stock recovery and ran the ota...
Click to expand...
Click to collapse
What ROM were you on? Curious as I would like to have stock jellybean (not rooted) on my One S.
I'm s-off and supercid. Just wondering what the steps would be if I wanted to try this.
Sent from my Galaxy Nexus using xda app-developers app
npiper05 said:
What ROM were you on? Curious as I would like to have stock jellybean (not rooted) on my One S.
I'm s-off and supercid. Just wondering what the steps would be if I wanted to try this.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This is a full update just flash stock recovery and then flash ota I think that should work. Please leave feedback and let us know.
So I'm guessing the are the steps.
1. Save update.zip to my sd
2. Flash stock recovery (I need to find this)
3. Boot into recovery (the stock recovery should
4. Stock recovery should flash the update
Do I need to change my CID back to T mobile? I've heard of bricks when flashing OTA with super cid.
Sent from my Galaxy Nexus using xda app-developers app
npiper05 said:
So I'm guessing the are the steps.
1. Save update.zip to my sd
2. Flash stock recovery (I need to find this)
3. Boot into recovery (the stock recovery should
4. Stock recovery should flash the update
Do I need to change my CID back to T mobile? I've heard of bricks when flashing OTA with super cid.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I changed back to the tmob010. I have uploaded the firmware to my dropbox on the link in the first post. You will find the stock recovery image there. Then just fastboot flash img and try from there.
npiper05 said:
What ROM were you on? Curious as I would like to have stock jellybean (not rooted) on my One S.
I'm s-off and supercid. Just wondering what the steps would be if I wanted to try this.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
i was on the latest T-Mobile US Rom , rooted, supercid, s-off
npiper05 said:
So I'm guessing the are the steps.
1. Save update.zip to my sd
2. Flash stock recovery (I need to find this)
3. Boot into recovery (the stock recovery should
4. Stock recovery should flash the update
Do I need to change my CID back to T mobile? I've heard of bricks when flashing OTA with super cid.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Are you rooted now ? ...You should just flash stock recovery in fastboot, relock your bootloader, flash the latest RUU...then let the phone OTA ...Stock JB not rooted will be the result.
aegentirony said:
i didnt change my CID....and locked the bootloader...flashed stock recovery and ran the ota...
Click to expand...
Click to collapse
aegentirony said:
i was on the latest T-Mobile US Rom , rooted, supercid, s-off
Are you rooted now ? ...You should just flash stock recovery in fastboot, relock your bootloader, flash the latest RUU...then let the phone OTA ...Stock JB not rooted will be the result.
Click to expand...
Click to collapse
Yes - rooted now. I have Trickdroid 9.0. Would love stock JB for work. Using stock Galaxy Nexus now, as I need stock setup, no root for work.
I tried going to the dropbox link, but had the "too much traffic" message.
If I want, could I flash stock recovery, flash RUU, then do a system update to try to get the JB update?
Only thing that makes me nervous is the SuperCID. I'll look for a link to change back to TMOB CID. I'm guessing it's not too difficult.
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
[RUU] [OTA] T-Mobile US Android 4.3 OTA (3.24.531.3) w/ Nandroid, Firmware & Radio
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DISCLAIMER
I am sharing this so everyone can have access to the official OTA. What you do with it from here is not my responsibility, nor do I care. Enjoy. I am not claiming ownership, nor am I claiming this will be much help by itself.
Update 10/23
The community has spoken, and this has brought a lot of stock options for the end user. As of 10/23 (today), we now have the OTA, a full Nandroid TWRP backup, two versions of the firmware, the radio only and now the RUU itself. The OP has been fully updated with links and credits to everything. Thank you to the Android community, this thread is a pretty great example of open source and people coming together with end products. Thanks for all the help here as well.
DOWNLOADS
RUU
3.24.531.3 T-Mobile RUU: http://forum.xda-developers.com/showthread.php?p=46756958
* thanks to Behold_this
OTA
*UPDATED 10/21 8PM*
My DropBox Link: https://db.tt/MWAGXkFc
Mirror Link: http://www.mediafire.com/?xjwbggpj5pw0l1l
* thanks to Mikey
NANDROIDS
TWRP Backup, No Root: http://forum.xda-developers.com/showpost.php?p=46695324&postcount=50
* thanks to Mikey
FIRMWARE
FIRMWARE (slim): http://forum.xda-developers.com/showpost.php?p=46691733&postcount=30
* does not include: boot.img, recovery.img or hboot.img
* thanks HTC_Phone
FIRMWARE + HBOOT: http://forum.xda-developers.com/showpost.php?p=46694631&postcount=43
* contains modded hboot without red warning text
* thanks to HTC_Phone
RADIO
RADIO: http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
* flashable radio only zip can be found here
* thanks to Mikey
Thanks for the link
Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
Mikey said:
Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
Click to expand...
Click to collapse
Any chance you can mirror the OTA? Dropbox terminated the OPs link
frettfreak said:
Any chance you can mirror the OTA? Dropbox terminated the OPs link
Click to expand...
Click to collapse
Uploading it now.......give me a couple minutes
TJD319 said:
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link. I am just sharing this with the community for developmental purposes. Hopefully, this may bring Wi-Fi Calling addons to ROMs like ViperOne and others I'm sure.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DropBox Link: https://db.tt/MWAGXkFc
Click to expand...
Click to collapse
So after hours of searching through the forums, I just wanted to clarify a couple of questions.
I have S-Off and unlocked bootloader but Stock Rom - NOT rooted and stock recovery. I also have the original MID/CID - 0713000 / T-MOB010.
I can still get the latest OTA - 3.24.531.3? The only requirement for the OTA is CID/ MID, stock recovery and stock ROM, correct?
Also, If I go ahead update it, My HBOOT will be updated to 1.54 and Bootloader will be locked but I still will retain s-OFF, correct?
And the only way in future to flash a custom ROM is via, htcdev bootloader unlock?
Thank You!!
Mikey said:
Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
Click to expand...
Click to collapse
f_v_man said:
So after hours of searching through the forums, I just wanted to clarify a couple of questions.
I have S-Off and unlocked bootloader but Stock Rom - NOT rooted and stock recovery. I also have the original MID/CID - 0713000 / T-MOB010.
I can still get the latest OTA - 3.24.531.3? The only requirement for the OTA is CID/ MID, stock recovery and stock ROM, correct?
Also, If I go ahead update it, My HBOOT will be updated to 1.54 and Bootloader will be locked but I still will retain s-OFF, correct?
And the only way in future to flash a custom ROM is via, htcdev bootloader unlock?
Thank You!!
Click to expand...
Click to collapse
I am pretty sure you need to relock the bootloader, and have stock recovery. AFAIK those are the requirements. HBOOT may be 1.55 as that is the latest but you SHOULD still keep s-off. But i make no promises. lol But yes, you will have to go to HTCDEV and get your unlock key again if you wantt o flash another rom (its a really easy process though)
TJD319 said:
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link. I am just sharing this with the community for developmental purposes. Hopefully, this may bring Wi-Fi Calling addons to ROMs like ViperOne and others I'm sure.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DropBox Link: https://db.tt/MWAGXkFc
Click to expand...
Click to collapse
Anyways to get a nandroid or to pull /system on an installed update.
I'm currently on a custom 4.2.2 ROM with Firmware 2.24.401.1, HBOOT 1.54, S-OFF, Super CID, and TWRP 2.6 bootloader on T-Mobile HTC One.
What is the process to upgrade to this OTA? Or is there a better to go to latest base, firmware, etc.?
Mikey said:
Uploading it now.......give me a couple minutes
Click to expand...
Click to collapse
Here you go
http://www.mediafire.com/download/xjwbggpj5pw0l1l/OTA_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3-1.27.531.11_release_337024c11bis4e2ha8yy5i.zip
I was on a rooted stock TMo ROM in order to get the update. However, i kept my Bootloader unlocked S-OFF, and I was rooted. Only thing really required is the stock odexed 4.1.2 ROM and the Stoxk boot and Recovery. SOFF doesnt matter, for me it didnt.
I was on Viper 4.2.2. I restored a nandroid of my stock 4.1.2 rooted, and all I then did was flash TMO stock recovery in fastboot.
Sent from my HTC One using XDA Premium 4 mobile app
TJD319 said:
I was on a rooted stock TMo ROM in order to get the update. However, i kept my Bootloader unlocked S-OFF, and I was rooted. Only thing really required is the stock odexed 4.1.2 ROM and the Stoxk boot and Recovery. SOFF doesnt matter, for me it didnt.
I was on Viper 4.2.2. I restored a nandroid of my stock 4.1.2 rooted, and all I then did was flash TMO stock recovery in fastboot.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The OTA doesn't help developers, they need the patched APK's after the OTA is installed.
SmiLey497 said:
The OTA doesn't help developers, they need the patched APK's after the OTA is installed.
Click to expand...
Click to collapse
I was answering someone's question about if they need the bootloader relocked or not.
As far as the devs go, now they've got the OTA and can do whatever they or anyone else wants with it. Its not really a crime to share.
Sent from my HTC One using XDA Premium 4 mobile app
Thanks for the upload. Question, to flash this, its just like flashing a firmware update, with the silver HTC on the screen? Pushed through ADB?
Rob
cvseuy said:
I'm currently on a custom 4.2.2 ROM with Firmware 2.24.401.1, HBOOT 1.54, S-OFF, Super CID, and TWRP 2.6 bootloader on T-Mobile HTC One.
What is the process to upgrade to this OTA? Or is there a better to go to latest base, firmware, etc.?
Click to expand...
Click to collapse
1. Restore nandroid backup for stock 4.1.2
2. Make sure boot.img and recovery.img are from stock T-Mobile.
3. Get OTA
OR
Download and install the stock T-Mobile ODEX ROM. Flash the ROM, doesnt matter if its rooted or not. Make sure it has stock recovery and boot images. And you can get OTA.
Sent from my HTC One using XDA Premium 4 mobile app
TJD319 said:
I was answering someone's question about if they need the bootloader relocked or not.
As far as the devs go, now they've got the OTA and can do whatever they or anyone else wants with it. Its not really a crime to share.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Said by a developer
"ota is just a patch, patches the existing files, with new code, there isn't a whole apk there. is useless unless you have a phone to apply patch on and then pull system"
that's why I was asking. No ROM can include stuff like Wi-Fi calling without the patched APK's.
i noticed this is a higher build number compared to the att 4.3 version
SmiLey497 said:
Said by a developer
"ota is just a patch, patches the existing files, with new code, there isn't a whole apk there. is useless unless you have a phone to apply patch on and then pull system"
that's why I was asking. No ROM can include stuff like Wi-Fi calling without the patched APK's.
Click to expand...
Click to collapse
Once again, i completely get this and for someone who wants to provide a full system dump would be great. But im not wiping yet, so i cant do that. Also, the OTA file contains an encrypted firmware.zip file which is completely independent of the patched apks. That's why Mikey posted the Radio. This is the whole reason I gave it to the community.
Anyway, im done. Im not trying to argue about some stupid OTA. If you don't want it, then don't download it.
Sent from my HTC One using XDA Premium 4 mobile app
So, I noticed a problem on 4.3 when trying to boot a recovery in fastboot. According to the following thread, Android 4.3 bootloader has changed the function of this fastboot command:
Code:
fastboot boot recovery_twrp.img
Reference URL of same solved issue on N4: http://forum.xda-developers.com/showthread.php?t=2380675
Now, we have to retrigger the command somehow inputting the right information in. When i ran the regular command, it says downloading ...OK and goes through the regular steps, but the phone hangs on the bootloader screen.
It never actually loads the custom recovery, just completely freezes the bootloader. I tried a couple different recoveries (CWM, TWRP) and they just don't do anything except lock up the phone.
I want to preserve my stock partitions and make a backup. I plan to go back to my 4.1.2 and perform the update, then load it and wipe so i can provide the stock nandroid backup for full throttle development. So if anyone knows the current command to boot a custom recovery in fastboot on 4.3, let me know.
Sent from my HTC One using XDA Premium 4 mobile app
TJD319 said:
So, I noticed a problem on 4.3 when trying to boot a recovery in fastboot. According to the following thread, Android 4.3 bootloader has changed the function of this fastboot command:
Code:
fastboot boot recovery_twrp.img
Reference URL of same solved issue on N4: http://forum.xda-developers.com/showthread.php?t=2380675
Now, we have to retrigger the command somehow inputting the right information in. When i ran the regular command, it says downloading ...OK and goes through the regular steps, but the phone hangs on the bootloader screen.
It never actually loads the custom recovery, just completely freezes the bootloader. I tried a couple different recoveries (CWM, TWRP) and they just don't do anything except lock up the phone.
I want to preserve my stock partitions and make a backup. I plan to go back to my 4.1.2 and perform the update, then load it and wipe so i can provide the stock nandroid backup for full throttle development. So if anyone knows the current command to boot a custom recovery in fastboot on 4.3, let me know.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You ran this one correct,
Code:
fastboot -c "lge.kcal=0|0|0|x" boot twrp.img
because that's the only solution I've seen so far, I'll try to look further.