i just picked up a wifi only best buy flyer. downloaded the 2 brightstar RUUs in preperation for future exploring
im familiar with htc devices(had several htc phones),and familiar with revolutionary. since the honeycomb installs require an incompatible hboot,and the fastboot flashing of seperate partitions,i was wondering if there is ANY procedure that could work to achieve a true radio s-off for the flyer?
i understand the need for the HC install procedures,and radio s-off would let us just flash whole ruus without needing to worry about the main version tag.
downgrade and adb dont scare me
since were on the subject of ruus,will all the ruus listed run on the best buy flyer(understanding that some phone and carrier specific parts wont work) if one uses the permanent revolutionary hboot and a gold card? having some experience with a multicarrier htc merge,seems like they should. pretty comfortable with hboot flashes and running .exe files on my phones,just making sure im still on familiar ground
No, only the Brightstar RUUs run on the BB Flyers.
Thanks for the reply. What will happen if you flashed a different ruu? FCs and non-functionality,or won't boot?
Do the different variants not share an hboot and kernel?
Sent from my ADR6400L using XDA Premium App
If you try to flash a different model like a 3g on a wifi only , it will detect the wrong model number and refuse to install. If you flash a different region RUU on the same model, it may work, but you will not have your locals to match, i.e you might be missing English US. The software is all the same, so there is no reason to do that.
DigitalMD said:
If you try to flash a different model like a 3g on a wifi only , it will detect the wrong model number and refuse to install. If you flash a different region RUU on the same model, it may work, but you will not have your locals to match, i.e you might be missing English US. The software is all the same, so there is no reason to do that.
Click to expand...
Click to collapse
Not really true, but I don't want to elaborate on that becasue I don't want to be responsible for people doing stupid things.
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
DigitalMD said:
No, only the Brightstar RUUs run on the BB Flyers.
Click to expand...
Click to collapse
That is not entirely correct. This only applies in a scenario where an upgrade to HC has been done. If you stay within honeycomb RUUs goldcards will work.
---------- Post added at 03:14 PM ---------- Previous post was at 03:13 PM ----------
scotty1223 said:
... was wondering if there is ANY procedure that could work to achieve a true radio s-off for the flyer?
Click to expand...
Click to collapse
Not right now...working on it.
Thanks for clarifying.
globatron said:
Not right now...working on it.
Click to expand...
Click to collapse
awsome! guess ill just use revolutionary for now. please give me a shout if theres anything i can do to help,or if you need testers
scotty1223 said:
awsome! guess ill just use revolutionary for now. please give me a shout if theres anything i can do to help,or if you need testers
Click to expand...
Click to collapse
Noted, but I do have the necessary equipment to test myself and anything I do find will be released through Revolutionary.
any progress with radio s-off?
Related
So I want to unroot my phone. But the unrooting guide (found here: http://forum.xda-developers.com/showthread.php?t=1671577) is several months old I believe. Also, in the guide he says that you can flash the RUU to a newer version but not to an older version. well the RUU's that are linked for download are 1.12 and 1.13. I am currently running MeanRom which is 1.22. Is this a problem?
The correct RUU to run is going to depend on your H-boot and firmware, not on the ROM.
Why in gods name would you want to unroot?
Rxpert said:
The correct RUU to run is going to depend on your H-boot and firmware, not on the ROM.
Why in gods name would you want to unroot?
Click to expand...
Click to collapse
I understand that it is not related to the ROM. but the ROM I am running is based off of the 1.22.651.36 RUU. So I could't run a different RUU. And I am unrooting to see if I can possibly get 3g data back. I have absolutely no data even when my wife has full 3g right next to me. If that doesn't resolve it, then I need it unrooted so that I can exchange it. I personally wouldn't un root if I didn't think it 100% necessary.
revaew said:
I understand that it is not related to the ROM. but the ROM I am running is based off of the 1.22.651.36 RUU. So I could't run a different RUU. And I am unrooting to see if I can possibly get 3g data back. I have absolutely no data even when my wife has full 3g right next to me. If that doesn't resolve it, then I need it unrooted so that I can exchange it. I personally wouldn't un root if I didn't think it 100% necessary.
Click to expand...
Click to collapse
Try updating to the latest radio version. It might fix your 3g problem. I believe flashing radios requires S-OFF or version 1.12 of hboot:
http://forum.xda-developers.com/showthread.php?t=1704612
This won't affect your root or bootloader status.
Sent from my EVO LTE
---------- Post added at 10:49 PM ---------- Previous post was at 10:34 PM ----------
Also, maybe try updating your Profile and PRL?
Sent from my EVO LTE
premo15 said:
Try updating to the latest radio version. It might fix your 3g problem. I believe flashing radios requires S-OFF or version 1.12 of hboot:
http://forum.xda-developers.com/showthread.php?t=1704612
This won't affect your root or bootloader status.
Sent from my EVO LTE
---------- Post added at 10:49 PM ---------- Previous post was at 10:34 PM ----------
Also, maybe try updating your Profile and PRL?
Sent from my EVO LTE
Click to expand...
Click to collapse
I unrooted and got my 3g back. I am going to see about rerooting it and seeing if my problem persists. I will also look into updating Profile and PRL.
Thanks for the suggestions.
REDACTED
You are experiencing an issue that occurred in May when users went flash happy when an leaked ics vm ruu came. This was a problem for those who were s-on because it meant you couldn't go back. Idk all the details but tjeres some guides that can help you out. There's a guide that can help you get back on sprint banner. You might have to run a gb firmware ruu exe first then use this link to get back on to sprint banner http://forum.xda-developers.com/showthread.php?t=1654061. After that you could take the ota to update to ics and use ramjet73's guide to gain root and s-off. Let me know if I helped you in anyway. Please hit the thanks button.
---------- Post added at 09:48 AM ---------- Previous post was at 09:19 AM ----------
I found another link you can look at to help you out http://forum.xda-developers.com/showthread.php?t=1653777. Good luck.
Jsparta26 said:
I found another link you can look at to help you out http://forum.xda-developers.com/showthread.php?t=1653777. Good luck.
Click to expand...
Click to collapse
That's the link you want to use and expect to put some time and effort into backing out the Virgin Mobile changes. It's not a good idea to flash RUU's and firmware not intended for the model of the Evo 3D that you own as I indicated in my guide:
WARNING: When you are S-OFF, PG86IMG.zip files can be flashed from the bootloader without being signed, which means you can flash any bootloader or firmware you want. But be careful and always make sure the stuff you are flashing is designed for your phone, or you may have serious problems if you force something to flash that was designed for another carrier or phone.
Click to expand...
Click to collapse
The reason that you are having problems is that there is firmware being flashed for one carrier that is not being overriden by flashing the RUU for another carrier. The RUU (.exe or .zip) can only replace/refresh the software and firmware it was designed to include.
Good luck returning it to the Sprint version.
ramjet73
REDACTED
Hello!
I think I'm close to bricking my HTC Flyer Wifi 16GB and could use som help from the bright minds of XDA.
What I'm trying to do is to revert back from DexterJB to stock GB/HC and going S-On again since the tablet is beeing sent in for service (bad screen). However, when downgrading something went wrong and now i only have access to the bootloader (volume - and Power).
How did I get here?
As I said, I was trying to downgrade from DexterJB, following this guide: http://forum.xda-developers.com/showthread.php?t=1346200
I got to step 11 where an error told me the device ID was wrong and the update process was aborted. Now the tablet only reaches the HTC white bootscreen and stops.
My cidnum is: HTC__Y13 so the RUU i was using should have worked: RUU_Flyer_HC_S_HTC_WWE_3.55.405.1_Radio_20.4801.30.0822U_3822.10.08.07_M_release_226690_signed
I also tried these RUUs:
RUU_Flyer_HTC_WWE_1.36.405.5_R_Radio_20.35.30.089BU_3809.05.0401.04_M_release_189803_signed
RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed
All of them just hits me with the error: 130 wrong model ID.
What can i do to fix this? Willing to donate a beer to the one who can help me out with this since i need it fixed ASAP.
Well, what version of the Flyer do you have (region, etc.)?
redpoint73 said:
Well, what version of the Flyer do you have (region, etc.)?
Click to expand...
Click to collapse
Bought in Sweden (so region should be Europe/North?), Wifi edition so not branded - HTC_Y13, thats about all information I have.
Ah, got it working again! Followed the steps here: http://forum.xda-developers.com/showthread.php?t=1358758
Now i just have to figure out how to remove REVOLUTIONARY and go back to S-ON. Guess I'll have to buy myself that beer now.
RobertRoos_ said:
Bought in Sweden (so region should be Europe/North?), Wifi edition so not branded - HTC_Y13, thats about all information I have.
Click to expand...
Click to collapse
I think Europe is all WWE version, so that you were right about. But for WiFi only, the RUU says "WiFi" in the file name. So I think that is why the RUUs your tried resulted in version error. At least that seems to be the case for RUUs listed here: http://forum.xda-developers.com/showthread.php?t=1062184
---------- Post added at 04:30 PM ---------- Previous post was at 03:59 PM ----------
RobertRoos_ said:
Now i just have to figure out how to remove REVOLUTIONARY and go back to S-ON. Guess I'll have to buy myself that beer now.
Click to expand...
Click to collapse
The method in your OP seems to be the way to go. Downgrading the hboot should get you S-On. Running the stock RUU will get you back to stock recovery. I think its just a matter of finding the right RUU for your version.
Edited for accuracy:
For those happy folks finally moving to 4.4.2 (Verizon and Sprint most recently) please keep in mind that we do NOT yet have an ruu for 4.4.2. If you are S-ON you will NOT be able to save yourself using any 4.3 ruu if you have updated your hboot. Keep in mind an hboot can be flashed without any other part of an update so make sure you know what you are doing and what you have done to your device.
Just a public service announcement to hopefully bring people back to reality before they go modding their new 4.4.2 goodness.
Can't 4.4's hboot replace itself with the RUU's hboot,
(like usual 2 pass RUU install)?
Or did you mean for S-ON devices?
Im sure some magic can be worked for those that are s-off and can flash non encrypted. S-on folks definitely have to watch out. Overall its just best that people think before they play.
Jiggity Janx said:
Im sure some magic can be worked for those that are s-off and can flash non encrypted. S-on folks definitely have to watch out. Overall its just best that people think before they play.
Click to expand...
Click to collapse
S-off should download. Might have to test lol
Sent from my HTC6600LVW using Tapatalk
Aren't the s-off'ed and unlocked devices able to use their respective RUU's to downgrade? Example like myself I wen't from 1.11.605.4 official to the new 2.16.605.2 that if I ran in to a problem I could do the 0P3PIMG.zip from SD method or do the fastboot oem rebootRUU with the vzw.t6.0P3PIMG_1.11.605.4.zip and I was under the impression we could downgrade or upgrade as we see fit so long as we are s-off??? Isn't that how it's always been? I thought s-on users only really had to be careful since they could only upgrade due to main version issue and also not having a KitKat RUU now available if they took the update while s-on.... Some clarity would be great! Honestly though I thought the way I just worded it is how it's always been with HTC devices...
Jiggity Janx said:
Im sure some magic can be worked for those that are s-off and can flash non encrypted. S-on folks definitely have to watch out. Overall its just best that people think before they play.
Click to expand...
Click to collapse
ALL of this discussion is why I started this thread!
It is important we get to the complete truth. IMO my OP stands valid until we have confirmation otherwise.
Jiggity Janx said:
ALL of this discussion is why I started this thread!
It is important we get to the complete truth. IMO my OP stands valid until we have confirmation otherwise.
Click to expand...
Click to collapse
Last night, @waco2hot33 ran the RUU and went s-on to take the OTA...and was able to regain s-off, root, and unlocked via WeakSauce/firewater s-off...Here's how he did it
But, once you're back to s-off, and have root, no matter what hboot you have, you can run the commands from @scotty1223's thread found HERE to unlock the new hboot
End of discussion?
Yeah that's incorrect hehe... For s-on users that stands true... They need to be extremely careful until something becomes available, but speaking for the Verizon users that took the OTA and are s-off... Unlocked is NOT necessary, just as long as they are s-off they can actually downgrade back to stock 4.3 for whatever the reason may be.. i.e.: warranty, bad flash, etc etc... It's 100% always been this way for all HTC devices that are s-off... It's by far the greatest feature or perk of having an HTC device... If you don't believe me then grab the encrypted vzw.t6_1.11.605.4 RUU and run it, you will see you will have no issues downgrading. While s-on users if they attempted they would get the main version to low error, s-off bypasses that...
Jiggity Janx said:
ALL of this discussion is why I started this thread!
It is important we get to the complete truth. IMO my OP stands valid until we have confirmation otherwise.
Click to expand...
Click to collapse
Murrda said:
Yeah that's incorrect hehe... For s-on users that stands true... They need to be extremely careful until something becomes available, but speaking for the Verizon users that took the OTA and are s-off... Unlocked is NOT necessary, just as long as they are s-off they can actually downgrade back to stock 4.3 for whatever the reason may be.. i.e.: warranty, bad flash, etc etc... It's 100% always been this way for all HTC devices that are s-off... It's by far the greatest feature or perk of having an HTC device... If you don't believe me then grab the encrypted vzw.t6_1.11.605.4 RUU and run it, you will see you will have no issues downgrading. While s-on users if they attempted they would get the main version to low error, s-off bypasses that...
Click to expand...
Click to collapse
Please read my post above yours. Waco went s-on, took the update and installed it, and was able to regain s-off via the link i posted above. Therefore, one COULD root the newest update whether they are s-on or s-off.
I did something similar but why did he s-on?? Def didn't have to do that... I got the OTA and it failed 2 times so I said F it and ran the encrypted RUU just to get back to a complete stock state in case it was a boot.img or something missing issue and I remained "s-off" and "unlocked", redownloaded the OTA after booting back up and the OTA then flashed perfectly fine with booting in to KitKat and still s-off and unlocked. Only thing I had to do was fastboot TWRP back and flashed the SuperSU v1.94 and I was straight!
Did he think he needed to be s-on to take the OTA?
Vinchenzop said:
Last night, @waco2hot33 ran the RUU and went s-on to take the OTA...and was able to regain s-off, root, and unlocked via WeakSauce/firewater s-off...Here's how he did it
But, once you're back to s-off, and have root, no matter what hboot you have, you can run the commands from @scotty1223's thread found HERE to unlock the new hboot
End of discussion?
Click to expand...
Click to collapse
Murrda said:
I did something similar but why did he s-on?? Def didn't have to do that... I got the OTA and it failed 2 times so I said F it and ran the encrypted RUU just to get back to a complete stock state in case it was a boot.img or something missing issue and I remained "s-off" and "unlocked", redownloaded the OTA after booting back up and the OTA then flashed perfectly fine with booting in to KitKat and still s-off and unlocked. Only thing I had to do was fastboot TWRP back and flashed the SuperSU v1.94 and I was straight!
Did he think he needed to be s-on to take the OTA?
Click to expand...
Click to collapse
Noob moment? Tired? Acid flashback? Your guess is as good as mine, but he went s-on and was able to regain s-off via WeakSauce temp-root and firewater s-off with newest OTA/firmware. So...success? lol
I got what you are saying.. You are stating it is possible to root unlock and s-off official KitKat but what Jiggity Janx created the OP for was saying to everyone to be careful in case they soft bricked hard bricked boot looped or what have you that when on official KitKat there phone may be rendered unusable because there is no KitKat RUU.... What good is a rooted phone if you can't boot it? I was stating that if you are s-off and can at least boot to hboot that you are 100% safe and can run the Jelly Bean RUU....
Vinchenzop said:
Please read my post above yours. Waco went s-on, took the update and installed it, and was able to regain s-off via the link i posted above. Therefore, one COULD root the newest update whether they are s-on or s-off.
Click to expand...
Click to collapse
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
But yes that is indeed good to know though, thanks for the info! Good to know s-on or off we can work with KitKat!
Verdict.....s-off allows full downgrade of everything via ruu. Firmware and hboot. Just tested myself.
Sent from my Nexus 7 using Tapatalk
Murrda said:
I got what you are saying.. You are stating it is possible to root unlock and s-off official KitKat but what Jiggity Janx created the OP for was saying to everyone to be careful in case they soft bricked hard bricked boot looped or what have you that when on official KitKat there phone may be rendered unusable because there is no KitKat RUU.... What good is a rooted phone if you can't boot it? I was stating that if you are s-off and can at least boot to hboot that you are 100% safe and can run the Jelly Bean RUU....
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
But yes that is indeed good to know though, thanks for the info! Good to know s-on or off we can work with KitKat!
Click to expand...
Click to collapse
I understand and agree, but if you're s-on, the likelyhood of you bricking your device is nearly null. If you're s-off, you could likely use the 4.3 RUU and downgrade your hboot (i did this yesterday during a brain lapse after taking/applying the update).
So if you're looking if being s-off allows you to downgrade your hboot, then the answer is yes.
dottat said:
Verdict.....s-off allows full downgrade of everything via ruu. Firmware and hboot. Just tested myself.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
And that's a second confirmations
LOL..... Thank you!!
dottat said:
Verdict.....s-off allows full downgrade of everything via ruu. Firmware and hboot. Just tested myself.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------
OP and or title should be corrected so it is not misleading to some looking for answers... Maybe I'll make a thread for users as reference for all the variants
I think the intent of the op was really meant for the users who are currently s-on and running KitKat. If they run into issues they likely won't be able to root and s-off and will be screwed as there currently isn't public KitKat ruu available.
Good discussion. Please don't discuss the intent of the thread anymore.
Sent from my Nexus 7 using Tapatalk
What did that mean ~~~> Don't discuss the intent of the thread anymore
dottat said:
I think the intent of the op was really meant for the users who are currently s-on and running KitKat. If they run into issues they likely won't be able to root and s-off and will be screwed as there currently isn't public KitKat ruu available.
Good discussion. Please don't discuss the intent of the thread anymore.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Vinchenzop said:
Therefore, one COULD root the newest update whether they are s-on or s-off.
Click to expand...
Click to collapse
Vinchenzop said:
I understand and agree, but if you're s-on, the likelyhood of you bricking your device is nearly null.
Click to expand...
Click to collapse
IMO if you can root it you can f it up. So s-on users do have some risk and currently there is no fix for them on 4.4.2 where there was a fix for them on 4.3 (encrypted ruu).
Good to see that soff users should be good to use a lower version ruu to downgrade if needed.
I have updated and downgraded to the stock version OS and hboot. But I'm also S Off. I had to use the decrypted RUU file though....
TappEd from my HTC One Max
Check out my website for encouragement....
www.projectintercession.blogspot.com
Murrda said:
What did that mean ~~~> Don't discuss the intent of the thread anymore
Click to expand...
Click to collapse
Lol...I meant let's not lose sight of the warning here. Noobs will be confused.
Sent from my Nexus 7 using Tapatalk
Hello people,
I've been using Nexus devices for a while on which rooting/flashing/updating was far simpler than my new phone - HTC One M8. I have been researching for around 2 months now and still have not been able to come to a clear-cut solution to my problem.
I am currently on 4.4.2 and my CID is CWS_001, I am S-On and firewater did not work - before going for sunshine, I want to know if it is possible for me to update my firmware in order to flash 4.4.4 and above ROMs. I tried flashing a newer ROM but its boot up time was huge and performance was lagging as well, after research I found out that I need to update firmware for it.
Now, I do not even know which firmware I currently am on since there is too much going on in HTC One M8's forums for a new person to get a grip of things. If any one from the XDA community could clarify and simplify things for me, I would be highly grateful.
Thank you.
Cannot flash firmware without being s-off, more than likely you are on either 1.58.502 or 2.23.502 if you took the ota before it was pulled.
Untamed Fantasy said:
Now, I do not even know which firmware I currently am on since there is too much going on in HTC One M8's forums for a new person to get a grip of things. If any one from the XDA community could clarify and simplify things for me, I would be highly grateful.
Click to expand...
Click to collapse
Hboot 3.16 = 1.12, 1.54, or 1.58 firmware
Hboot 3.18 = 2.23 firmware
With 1.x firmware, you can only run ROMs based on 1.x software (otherwise experience long boot times and/or broken WiFi).
Similarly, on 2.23 firmware, you can only run ROMs based on 2.x software
EDIT: Corrected the hboot numbers. Sorry for the typos!
Thank you for the response guys. I just booted into fastboot to check my HBOOT and it says "HBOOT-3.16.0.0000".
That does not match with any of the two options posted in the previous post. I am trying to identify my current HBOOT and firmware in order to flash a ROM which matches these IDs. Do you have any suggestions as to what I should do to determine the two?
Untamed Fantasy said:
Hello people,
I've been using Nexus devices for a while on which rooting/flashing/updating was far simpler than my new phone - HTC One M8. I have been researching for around 2 months now and still have not been able to come to a clear-cut solution to my problem.
I am currently on 4.4.2 and my CID is CWS_001, I am S-On and firewater did not work - before going for sunshine, I want to know if it is possible for me to update my firmware in order to flash 4.4.4 and above ROMs. I tried flashing a newer ROM but its boot up time was huge and performance was lagging as well, after research I found out that I need to update firmware for it.
Now, I do not even know which firmware I currently am on since there is too much going on in HTC One M8's forums for a new person to get a grip of things. If any one from the XDA community could clarify and simplify things for me, I would be highly grateful.
Thank you.
Click to expand...
Click to collapse
Did you try firewater before it was discontinued or is it still available for you?
I tried it around two months back and got message that it is not possible to attain S-OFF. Tried a couple of times again later too but same outcome.
I am in the same situation as the OP, only difference is that I have S-OFF from Sunshine.. Just got my phone. I hope to follow along as you guys help him out.
Untamed Fantasy said:
Thank you for the response guys. I just booted into fastboot to check my HBOOT and it says "HBOOT-3.16.0.0000".
That does not match with any of the two options posted in the previous post. I am trying to identify my current HBOOT and firmware in order to flash a ROM which matches these IDs. Do you have any suggestions as to what I should do to determine the two?
Click to expand...
Click to collapse
Sorry bud, my bad. Typo on my previous post. It should be:
Hboot 3.16 = 1.12, 1.54, or 1.58 firmware
Hboot 3.18 = 2.23 firmware
---------- Post added at 11:28 AM ---------- Previous post was at 11:20 AM ----------
Untamed Fantasy said:
I am currently on 4.4.2 and my CID is CWS_001, I am S-On and firewater did not work - before going for sunshine, I want to know if it is possible for me to update my firmware in order to flash 4.4.4 and above ROMs.
Click to expand...
Click to collapse
Back to the core question: NO you cannot update your firmware by any "official" means at this time, with your current configuration (s-on). There is no AT&T update that contains 3.x firmware. To update the firmware by "unofficial" means you need s-off.
S-off by sunshine, then update the firmware as outlined in the thread below:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
badbwoydes said:
I am in the same situation as the OP, only difference is that I have S-OFF from Sunshine.. Just got my phone. I hope to follow along as you guys help him out.
Click to expand...
Click to collapse
Since you are already s-off, just follow the instructions in the thread I linked above to update firmware.