I have been flashing for some time but excuse me if I sound stupid but the grey matter just don't work any more. I have RUU'd different RUU's from the 1.82 to 2.20 trying to get different customs to work and I can't figure out what base I am on. At the time I am using Clean Rom 6.1 R2 and things seem to work fine but just wondering. Some how I managed to go from HBOOT 2.14 I think down to HBOOT 1.09 without downgrading. I think I got it from some RUU. I have read that the HBOOT 1.09 is a golden thing on the phone but don't know why.
With this rom I have tried to flash the 3.18 radio and get a soft brick at the boot screen. I am pretty sure the last time I RUU'd I used the Cingular Us 1.82 and in the process it upgraded itself to the 1.83 . Now I have read that some roms with sense work better on the 3.18 RUU.. Will I loose the HBOOT 1.09 if I do this?
At the present
S-OFF
unlocked
CID 11111111
radio 0.24p..32.09.0501.......
I am just looking and trying different variations to find the best setup for my phone. Excuse me for sounding so stupid. The grey matter just is slush any more.
The 3.18 ruu will give you the 2.14 hboot but sense you are s-off which hboot you have is not that important people wanted the 1.09 hboot because you could flash radios and boot.img with it s-off allows you too do this no matter what hboot you have
Sent from my HTC One X using Tapatalk 2
Because you're s-off it doesn't matter what hboot you're on. Sense ROMs tend to run smoother/better with the latest update. So feel free to RUU up to 3.18. Don't relocked your bootloader, just ruu.
If you want to run AOSP ROMs after, though, you'll need to downgrade your touchscreen firmware.
Also for some people cm10 doesn't boot until they've upgraded for some odd reason.
Sent from my HTC One XL using xda app-developers app
exad said:
Because you're s-off it doesn't matter what hboot you're on. Sense ROMs tend to run smoother/better with the latest update. So feel free to RUU up to 3.18. Don't relocked your bootloader, just ruu.
If you want to run AOSP ROMs after, though, you'll need to downgrade your touchscreen firmware.
Also for some people cm10 doesn't boot until they've upgraded for some odd reason.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I understand that being S-OFF one could do most anything and be safe but I didn't really know if loosing the HBOOT 1.09 had any consequents or not. Plus, didn't know if upgradeing to the 3.18 firmware would be that beneficial or not. At one point I was on the 2.20 and took the OTA ATT udgrade to see what it was about but didn't like the rom ,but I did downgrade the touch screen . There are features with all the customs but don't like any one in particular, wish there some way to combine certain features from each one into one to make one that I liked for my phone. So far the best I can come up with is Clean Rom 6.1R2 with BlueIceSense CR6 and cityID apk. plus the radio from 3.18.
Thanks for understanding loss of grey matter stupidity
Related
Is there a way to revert back to pre-OTA/2.3.3? It seems like there are many more issues that fixes with this OTA. I hardly had any problems at all, and now my camera won't focus (can't use any barcode/qr readers), I'm getting the annoying screen capture/home button problem, etc, etc...
Quite annoying and I would have hoped that they would have come up with a fix by now.
RUU is the only way, which means losing all data (unless you root/back up first) - and you'd need to set your phone to Super CID to go backwards (I think) from a newer version to and older one
EddyOS said:
RUU is the only way, which means losing all data (unless you root/back up first) - and you'd need to set your phone to Super CID to go backwards (I think) from a newer version to and older one
Click to expand...
Click to collapse
As long as you're using the correct RUU for the phone, you don't need to change CID. I did it on my T-Mobile Sensation, from OTA 2.3.4 back to stock 2.3.3 through the RUU.
nxt said:
As long as you're using the correct RUU for the phone, you don't need to change CID. I did it on my T-Mobile Sensation, from OTA 2.3.4 back to stock 2.3.3 through the RUU.
Click to expand...
Click to collapse
Sent you a pm
Sent from my LG-P999 using XDA App
EddyOS said:
RUU is the only way, which means losing all data (unless you root/back up first) - and you'd need to set your phone to Super CID to go backwards (I think) from a newer version to and older one
Click to expand...
Click to collapse
He'll be okay flashing an RUU without SuperCID, it's only needed if flashing an RUU not authorized by the device.
Basically, if the update changed Hboot, he'll need to run revolutionary, then run RUU again as RUU doesn't accept downgrading hboot, which gives weird error codes.
The only way I figured out, was using Revolutionary as it updates the Hboot to an older one.
But as I understand OTA doesn't update Hboot. Right?
Sent from my HTC Sensation Z710e
Hello
can someone comment on the options with and progress for ROMS on base RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe base?
I see folks like me who have busted wifi or bricked outcomes and a lot fo snark thrown thier way. hard to keep it all straight.
Thanks in advance.
jimn235 said:
Hello
can someone comment on the options with and progress for ROMS on base RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe base?
I see folks like me who have busted wifi or bricked outcomes and a lot fo snark thrown thier way. hard to keep it all straight.
Thanks in advance.
Click to expand...
Click to collapse
Their Wifi breaks because they can't search for the fix. There are extra partitions that you have to flash in order to switch back and forth between all older bases and the newest Tmobile release.
T-Mobile Trickdroid and UnKnown_Retriution both work, and are both based on the latest T-Mobile release.
As for the partition, find them here http://forum.xda-developers.com/showpost.php?p=32170653&postcount=2668 I'm pretty sure you need a 1.09 hboot or lower to flash them.
Thanks. I don't think I had a choice of base I've had this 1 week. I'm hboot 1.14. I probably did the ota thoughtlessly in the first 5 minutes of owning this. Great phone but I like the nexus 7 base a little bettter for features. Looking forward to jellybean.
xxquicksh0txx said:
Their Wifi breaks because they can't search for the fix. There are extra partitions that you have to flash in order to switch back and forth between all older bases and the newest Tmobile release.
T-Mobile Trickdroid and UnKnown_Retriution both work, and are both based on the latest T-Mobile release.
As for the partition, find them here http://forum.xda-developers.com/showpost.php?p=32170653&postcount=2668 I'm pretty sure you need a 1.09 hboot or lower to flash them.
Click to expand...
Click to collapse
Im also on Hbot 14 and from what I keep reading there is no fix for our wifi issue since the patches ore for 9 and down. however, I'll try one of those roms. Thanks!
If you ran the T-Mobile update, which gives you HBOOT 1.14, your stuck with only running that same base roms for Wi-Fi to work. The only other option is to super cid and run RUU's 2.21 or 2.31 for it Wi-Fi to work on non 2.35 based roms.
HTC One™ S
fmedrano1977 said:
If you ran the T-Mobile update, which gives you HBOOT 1.14, your stuck with only running that same base roms for Wi-Fi to work. The only other option is to super cid and run RUU's 2.21 or 2.31 for it Wi-Fi to work on non 2.35 based roms.
HTC One™ S
Click to expand...
Click to collapse
So... To recap... 235 is current, the mod writers haven't caught up yet, and supercid involving 'dd' is an option for the impatient based on One X supercid.
dd is the quickest way to blow up a boot sector with a typo. I'm patient but at least this thread exists for the other unwary ota'rs
Might wanna try this if its true. I was reading the super cid thread but they didn't really touch bases on the subject. I wouldn't mind running strickly US sense roms but all the developement is on the Euro side and I need me some wifi so besides the eye candy its as good as it gets for us 1.14s. Hopefully you're right.
However, will super cid and new ruu save those files where the lower hboots have them? Also will I still have 1.14 ?
Seems weird to me that an OTA did that. I wonder if you could go into the TMo OTA edit some stuff and run the update and not get screwed. If only I knew more... I would dream less lol
Your stuck on HBOOT 1.14. Running RUU 2.21 or 2.31 will allow you to run any EU based rom with working Wi-Fi.
HTC One™ S
fmedrano1977 said:
Your stuck on HBOOT 1.14. Running RUU 2.21 or 2.31 will allow you to run any EU based rom with working Wi-Fi.
HTC One™ S
Click to expand...
Click to collapse
definitely want to try this
As per the title, does anyone have HBOOT 2.13? I have seen 1.06, 1.09, 1.14 and 2.15 but not 2.13. I have 2.13, and am afraid to flash any of the HBOOT flashables that remove the developer warning or tampered message, mainly because these zips were probably not designed to be flashed on my weird HBOOT version that I have never heard of myself.
It seems I am the only one who has this. Has anyone else got this HBOOT version and flashed one of those zips whilst S-OFF?
Edit: I definitely don't want to try when unsure, otherwise I am afraid I might brick my phone like my last One S.
usaff22 said:
As per the title, does anyone have HBOOT 2.13? I have seen 1.06, 1.09, 1.14 and 2.15 but not 2.13. I have 2.13, and am afraid to flash any of the HBOOT flashables that remove the developer warning or tampered message, mainly because these zips were probably not designed to be flashed on my weird HBOOT version that I have never heard of myself.
It seems I am the only one who has this. Has anyone else got this HBOOT version and flashed one of those zips whilst S-OFF?
Edit: I definitely don't want to try when unsure, otherwise I am afraid I might brick my phone like my last One S.
Click to expand...
Click to collapse
That actually is quite odd... I can't seem to find any mention of a 2.13 hboot anywhere. I'll keep looking though... Maybe someone like Behold or Torxx or even Tecardo might be able to shed some light on this...
Yep, if it does help I think it might be a custom T-Mobile UK HBOOT or something, but that's still very strange. After S-OFF, which is supposed to flash the 2.15 HBOOT after 1.14, I got 2.13 instead. Happened with my last One S too. The phone was rooted running the T-Mob UK JB firmware.
usaff22 said:
Yep, if it does help I think it might be a custom T-Mobile UK HBOOT or something, but that's still very strange. After S-OFF, which is supposed to flash the 2.15 HBOOT after 1.14, I got 2.13 instead. Happened with my last One S too. The phone was rooted running the T-Mob UK JB firmware.
Click to expand...
Click to collapse
can you make a dump of it so i can take a look at it?
Sent from my HTC One S using Tapatalk 2
blackwing182 said:
can you make a dump of it so i can take a look at it?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
I don't know what partition HBOOT is stored in, is it 0p4 or 0p12 or 0p3 or something else?
Sent from my One S using Tapatalk 2
usaff22 said:
As per the title, does anyone have HBOOT 2.13? I have seen 1.06, 1.09, 1.14 and 2.15 but not 2.13. I have 2.13, and am afraid to flash any of the HBOOT flashables that remove the developer warning or tampered message, mainly because these zips were probably not designed to be flashed on my weird HBOOT version that I have never heard of myself.
It seems I am the only one who has this. Has anyone else got this HBOOT version and flashed one of those zips whilst S-OFF?
Edit: I definitely don't want to try when unsure, otherwise I am afraid I might brick my phone like my last One S.
Click to expand...
Click to collapse
Could you help me find a branded run for my htc one s. S4 krait chip. locked to three Uk so it's branded Check my thread for details
http://forum.xda-developers.com/showthread.php?p=40645302&posted=1#post40645302
Please can you help me I soft bricked my phone and need this badly thanks
@Zaman-The-Man I replied in the other thread
Sent from my HTC One S using Tapatalk 2
I have got HBOOT 2.13 too, I sent my phone in for repair check bootloader and it was that... Previously I had 1.16 or something near that
I've just seen this thread, i'm also hboot 2.13, rooted with Pacman 4.4.4 RC1. Is there anywhere that explains these hboot differences?
After finally managing to work around Windows 8 and its BS, I rooted and unlocked the bootloader on my AT&T One X.
I'm now at the point of trying to update HBoot so that I can use the JB Roms. The phone is currently still running ICS. I followed the tutorial on YouTube from"onexroot" using JBWFlasher. My HBOOT versin is 1.14 currently, Originally my phone was S-ON with a CID of "11111111". I S-OFF'ed the phone and changed the CID to HTC__001 and all the way down the list because I keep getting the error "FAILED (remote: 41 model id check fail)". No matter which CID I give the phone or if I attempt to update for a device with S-ON or S-OFF.
Not really sure what else to try at this point as I've searched here and all over Google. I didn't want to bother you guys with it but I don't know where else to go.
Thanks for any help in advance.
Neorift said:
After finally managing to work around Windows 8 and its BS, I rooted and unlocked the bootloader on my AT&T One X.
I'm now at the point of trying to update HBoot so that I can use the JB Roms. The phone is currently still running ICS. I followed the tutorial on YouTube from"onexroot" using JBWFlasher. My HBOOT versin is 1.14 currently, Originally my phone was S-ON with a CID of "11111111". I S-OFF'ed the phone and changed the CID to HTC__001 and all the way down the list because I keep getting the error "FAILED (remote: 41 model id check fail)". No matter which CID I give the phone or if I attempt to update for a device with S-ON or S-OFF.
Not really sure what else to try at this point as I've searched here and all over Google. I didn't want to bother you guys with it but I don't know where else to go.
Thanks for any help in advance.
Click to expand...
Click to collapse
Unless I'm missing something, you don't need to update hboot to use JB ROMs. I never did and I've been using Sense and AOSP jellybean ROMs for the past 7 months or so.
RollTribe said:
Unless I'm missing something, you don't need to update hboot to use JB ROMs. I never did and I've been using Sense and AOSP jellybean ROMs for the past 7 months or so.
Click to expand...
Click to collapse
Really? Everything I read today mentioned the need to update hboot. My concern is being able to recover from it if it fails.
Yeah there's no need to update anything, just flash a jb rom from recovery. Once you have s-off hboot version kinda becomes moot
Sent from my HTC One X using xda premium
That model Id check fail is because your trying to flash a rom for the wrong phone.
Your lucky that's happening because usually it just bricks.
I should probably add that some people cannot boot newer JB Roms without updating hboot but that is not always the case and I still have no idea why it is so for some.
Yeah I should've asked... Do you have dual or quad core One X?
exad said:
That model Id check fail is because your trying to flash a rom for the wrong phone.
Your lucky that's happening because usually it just bricks.
I should probably add that some people cannot boot newer JB Roms without updating hboot but that is not always the case and I still have no idea why it is so for some.
Click to expand...
Click to collapse
I hadn't even gotten to the step to flash the ROM at that point. It was just for the hboot.
Anyway, got it sorted now. Thanks for the help everyone.
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
elias.acab said:
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
dr3amsINdigital said:
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
Click to expand...
Click to collapse
Oh I see, thanks!
Sent from my One S using xda app-developers app
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
rolo143 said:
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Moonshine S-OFF: http://forum.xda-developers.com/showthread.php?t=2325590
or
Facepalm S-OFF: http://forum.xda-developers.com/showthread.php?t=2155135
Absolutely right.
And how to remove the red warning text you can find here.
Keep in mind that once you're s-off and want to return to s-on (warranty, whatever...) you'll need to reflash any stock bootloader. Else you'll definitely brick your phone. Best thing is to run any RUU before you set s-on flag on your phone then. It'll automatically restore the stock bootloader that comes with it.
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
hongha_222 said:
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
Click to expand...
Click to collapse
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
rolo143 said:
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Your device must have s-off without s-off you WON'T BE ABLE TO RUN ROM.
Click to expand...
Click to collapse
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
hongha_222 said:
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
Click to expand...
Click to collapse
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
tsphan said:
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
Click to expand...
Click to collapse
you're right but I don't see any problem when I try the rcdata fix.
b) Type "mount" to see a list of mounts. I saw that the data block (p35) was being mounted again in /sdcard, which should be (p36). Checking /etc/fstab shows that the /sdcard was commented out!
I can do S-Off with hboot 2.16.
flashed with s-on
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
mattdbr said:
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
Click to expand...
Click to collapse
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
tivofool said:
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
Click to expand...
Click to collapse
Ok, will do. Sorry I didn't notice the S. Thanks