Related
Hello,
i have a T-Mobile flyer 3G 32gb with original HC
Build-number 3.55.111.1
baseband 20.4803.30.0822U_3822.11.08.07M2
HBoot 1.11.0011
Radio 3822.11.08.07M2
CID T-MOB101
I want to S-off and flash a custom rom but i don't know the best, the right, way to do this. So it's possible to have S-Off with this device?
I downloaded the T-Mobile RUU but with this RUU i can't downgrade to GB.
The RUU updater say Error 140 and stopped.
So what can i do for S-Off?
devil-77 said:
Hello,
i have a T-Mobile flyer 3G 32gb with original HC
Build-number 3.55.111.1
baseband 20.4803.30.0822U_3822.11.08.07M2
HBoot 1.11.0011
Radio 3822.11.08.07M2
CID T-MOB101
I want to S-off and flash a custom rom but i don't know the best, the right, way to do this. So it's possible to have S-Off with this device?
I downloaded the T-Mobile RUU but with this RUU i can't downgrade to GB.
The RUU updater say Error 140 and stopped.
So what can i do for S-Off?
Click to expand...
Click to collapse
Hey man...
I have the EXACT same flyer, everything the same... Did you manage to get it s-off and rooted back to Honeycomb?? I have read all the forums, but I actually can't find a clear solution! Lemme know please or if anybody can put it simple! Thanks!
custom rom for flyer with stock hc
These steps would help :
- unlock boot loader over htcdev
- flash cwm with fastboot
- with cwm you're able to flash any custom rom (zip files)
It worked at least on my htc evo 3D.
Hey,
I have somewhat of the same question - but remain puzzled... I unlocked the Flyer's bootloader yesterday through HTCdev, flashed a Revolutionary recovery (based on CWM) through fastboot and could then install SuperUser through an update.zip in the stock ROM.
I have mode some development on other devices, so I'm familiar with bootloaders and stuff. The forums are mostly talking about S-OFF and I don't really understand how that concerns me, because now that my stock ROM is rooted, I can do whatever I like (remove bloat etc.). I may not understand all implications of S-ON, but I know that my bootloader tells me my Flyer is S-ON.
Now, is there any problem to flash another ROM through CW Recovery? Will, for example, LeeDroid's ROM replace anything connected to 3G (I have the model running on AWS frequencies, which are quite unusual). Could I simply flash LeeDroid's ROM, then get back to my stock backup without any problem?
I guess the question is; since my bootloader is unlocked, does S-ON or OFF concern me in any way? Or is S-OFF only important for those who can't unlock their bootloaders through HTCdev?
Thanks!
(I do promise to write something up for the wiki if ever I understand
S-On means you can't flash a custom ROM through recovery or ROM Manager. You can only flash using fastboot.
Thanks!
So considering that I just tried to downgrade to Gingerbread in Windows and that I got Error 155 (which seems to be undocumented - the message was à la 'something went wrong - I don't know what'), can I restore CW recoveries through fastboot as well?
I wouldn't mind to plug the cable, and S-OFF seems like an unnecessary hassle to me... (I just want OpenVPN and from here I took as much time trying to figure that out than I would need to compile the module myself).
I guess what puzzles me is this (from the LeeDroid thread): "If you have acheived S-Off via HTCDev, you will need to extract the boot.img from the Kernel.zip and flash it via fastboot"
I don't have S-OFF. I have an unlocked bootloader.
Does that mean that if I want to switch to LeeDroid I first have to fastboot flash boot.img and then install the rest through CW recovery?
Similarly, if I want to get back to stock, I fastboot flash the boot.img from my backup and apply the rest through CW recovery?
Thus: S-ON actually only prevents the boot partition to be changed outside from fastboot?
Thanks again!
redpoint73 said:
S-On means you can't flash a custom ROM through recovery or ROM Manager. You can only flash using fastboot.
Click to expand...
Click to collapse
Hm. I just did full restore with CW recovery.
And I had already applied update.zip's with the recovery.
ADD: SOLVED. What I wrote in the post above was right. I can apply any zip file, but CW can't write boot.img. Solution: fastboot flash boot boot.img.
All the rest works. In order to get back to a backup I guess it's the same way - flash boot.img, apply the restore.
cid: TMOB010 and HBoot 1.11.0011 Please Help Soff this thing.
I have the exact same problem and I assume I need s-off to make this work like a phone. Yes? Has anybody figured this out yet?
bud.
First time flashing. Unlocked using HTC method, thought I backed up my rom using rom manager, went and flashed to Cyanogenmod 9. Didn't like it, wanted to go back to stock, but can't find the back up. Now my radio doesn't work, can't figure out which version of stock rom I need to flash either. Any help appreciated.
with htc unlock root, you need to flash roms by booting to recovery through fastboot, there are other options, but this one works 100% of the time.
Well yeah, I did that, but how to I get a stock rom back on so my phone will work? I can't connect to the mobile network now. How do I know which stock rom to download? I guess I don't understand how to tell I'm getting the right rom.
U want the latest ruu it will update everything.. dunno how u flash cause I'm s off
Ps in the future please post questions in q&a and not* development thread
did it help? hit the button!
sent from a viper bitten alien
Thanks, and sorry for not posting in correct location. Guess I don't know how to flash the RUU without being in S-OFF.
Check the stickies, there's a link to stock rooted ROMs in there somewhere. I'd link it, but I'm in a crappy area and it takes ages to load a thread.
On the other hand, why not just pick a ROM that's not in alpha and actually has most features working?
Sent from my HTC EVO 3D using Tapatalk
mushroom_cult said:
Check the stickies, there's a link to stock rooted
On the other hand, why not just pick a ROM that's not in alpha and actually has most features working?
Sent from my HTC EVO 3D using Tapatalk
Click to expand...
Click to collapse
True, I'll have to take a look at the other roms
Use team wins HTC unlock flashing tool its on rootzwiki
Sent from my MB855 using xda premium
You would want to boot into the bootloader, relock it and DL the RUU found in this LINK. Once downloaded, run the RUU.exe file on your pc while your phone is in the bootloader. It will flash your phone with the stock 2.17 update. When you are completed, boot back into bootloader and unlock your phone again using the HTC Unlock method. From there, you can flash any ROM with a 2.17 base and should be fine, but remember do a backup and to wipe first.
Thanks doeboy711!
I'm not too impressed with TWRP2 as it wasn't completely wiping things when it should have been so I recommend the older TWRP 1.1 (recovery). Also since you have hboot 1.5 you'll probably find Flash Image GUI a little easier to use for flashing kernels. If you didn't flash the right kernel that might be why your radio is not working. You can find flash image gui Here. It's pretty self explanatory. Before you flash a new rom, open Flash image gui, select kernel, browse to the rom. Let it do it's thing and when it prompts you to reboot to recovery, flash your rom like normal.
Actually, do I want to flash the RUU since it's still S-ON?
Do you have a HBoot 1.5? If so, that is the only way to upgrade to the new 2.17 base, which is the base of all the new ROM's. Just ensure that you lock the bootloader before you run the RUU or it will fail. It won't brick your device, but you will have to run it twice, learned the hard way here lol. Just pull your battery and boot into bootloader, lock it and then run the RUU if you did run it while it was unlocked still.
If you have a lower Hboot and can gain S-off, then no, don't run the RUU. You should be able to get S-off and flash anything you want at anytime.
Not sure how I'm supposed to get the RUU without a premium account at filefactory
Which hboot are you on? 1.4 or 1.5?
Sorry, hboot 1.50
DrkNvmbr81 said:
Not sure how I'm supposed to get the RUU without a premium account at filefactory
Click to expand...
Click to collapse
Post 55 had another DL for it but I saved you the time to try and find it and here it IS.
doeboy711, you are awesome. Thanks for the help, I'm gonna try it right now.
Do I backup and wipe before I flash this RUU?
DrkNvmbr81 said:
doeboy711, you are awesome. Thanks for the help, I'm gonna try it right now.
Do I backup and wipe before I flash this RUU?
Click to expand...
Click to collapse
Well you will loose everything once you run the RUU, so if you want to back up apps it's up to you. The RUU will wipe everything for you though, so don't worry about that.
I've got it back to normal. Thanks for your help.
Hi I need to take my phone in for repair and want to revert to Sprint's stock ICS, however I am on the engineering hboot 1.04 and don't want to lose that. I have flashed the OTA ROM from here (http://forum.xda-developers.com/showthread.php?t=1808150) but I am boot looping due to the kernel. Can anyone point me to a compatible flashable kernel?
And as a follow up, if I were to flash directly to Sprints current OTA, is it possible to downgrade all the way back to HBOOT 1.04?
daviderickson said:
Hi I need to take my phone in for repair and want to revert to Sprint's stock ICS, however I am on the engineering hboot 1.04 and don't want to lose that. I have flashed the OTA ROM from here (http://forum.xda-developers.com/showthread.php?t=1808150) but I am boot looping due to the kernel. Can anyone point me to a compatible flashable kernel?
Click to expand...
Click to collapse
The reason you are boot looping is because that ROM requires bootloader (hboot) 1.58, which is part of the updated 2.89.651.2 firmware. You can either flash the firmware from the OP of that thread, or reset everything to 100% stock by downloading the Sprint ICS RUU from here and flashing it from Windows.
Your radio status will stay S-OFF, and you can easily flash any bootloader you want from the stock bootloader once you get your phone back.
ramjet73
ramjet73 said:
The reason you are boot looping is because that ROM requires bootloader (hboot) 1.58, which is part of the updated 2.89.651.2 firmware. You can either flash the firmware from the OP of that thread, or reset everything to 100% stock by downloading the Sprint ICS RUU from here and flashing it from Windows.
Your radio status will stay S-OFF, and you can easily flash any bootloader you want from the stock bootloader once you get your phone back.
ramjet73
Click to expand...
Click to collapse
Thanks ramjet- And this won't require me having to go through HTC's unlock procedure right?
daviderickson said:
Thanks ramjet- And this won't require me having to go through HTC's unlock procedure right?
Click to expand...
Click to collapse
That's correct.
As long as you are S-OFF now and don't set S-ON before bringing the phone in for service, you can flash whatever bootloader you want after you get your phone back and then flash any ROM/kernel combination that works with that hboot.
Of course, S-ON could be set by whoever works on your phone, but I've never heard of that happening and the wire trick is pretty easy if you should need to get S-OFF again.
ramjet73
Hey ramjet-
I just got my phone back from repair, it is still listed as S-OFF, but is listed as locked. Since this seems to be a somewhat unique starting point compared to other threads, what is the procedure to go from S-OFF/locked to another hboot? Do I just pick an arbitrary RUU and flash with it?
daviderickson said:
Hey ramjet-
I just got my phone back from repair, it is still listed as S-OFF, but is listed as locked. Since this seems to be a somewhat unique starting point compared to other threads, what is the procedure to go from S-OFF/locked to another hboot? Do I just pick an arbitrary RUU and flash with it?
Click to expand...
Click to collapse
It's good that it has the bootloader locked because that's the stock status and you don't need it unlocked if you have S-OFF. However, if you want to run fastboot commands like "flash", "erase" and "boot" from a PC you need to flash a custom bootloader, then you can flash a custom recovery after that using the "fastboot flash recovery recovery.img" command. Your bootloader status will still be "locked" but the custom hboots ignore that status and run the fastboot commands anyway.
This post explains how to select and flash a different hboot when you are S-OFF.
ramjet73
Thanks for the pointer, I was able to flash back to 1.04 ENG, and get 4ext back installed. Is there any particular reason to run a newer hboot like Jbear's 1.58 other than if needed for kernel/ROM compatibility?
daviderickson said:
Thanks for the pointer, I was able to flash back to 1.04 ENG, and get 4ext back installed. Is there any particular reason to run a newer hboot like Jbear's 1.58 other than if needed for kernel/ROM compatibility?
Click to expand...
Click to collapse
No. Only if you want to run the ROM's that require it like coolexe's Cool ICS and Virus's Viper3D. The thread I linked on bootloaders gives a lot more detail on compatibility with different types of ROM's.
ramjet73
So I have s-off, tampered, and am able to get to TWRP recovery. ..but no SU and rooted apps say im not rooted.
Any suggestions? I went throught the Regaraw method but got stuck in the rooting phone process....it wouldnt go forward... is there something I cam flash or something? Any help will be highly appreciated!
How did you get soff if all you did is run regawmod, soff requires hboot 1.12 and lazy panda, if you have anything higher then 1.12 then it requires a whole other set of tools to downgrade the hboot. If you have recovery already just flash any custom rom
om4 said:
How did you get soff if all you did is run regawmod, soff requires hboot 1.12 and lazy panda, if you have anything higher then 1.12 then it requires a whole other set of tools to downgrade the hboot. If you have recovery already just flash any custom rom
Click to expand...
Click to collapse
Yeah I have recovery and this... am I rooted?
Try this, flash it in recovery and then wipe cache and dalvik. It would be easier to just flash a custom rom though
om4 said:
Try this, flash it in recovery and then wipe cache and dalvik. It would be easier to just flash a custom rom though[/QUOTE)
I just noticed that I has S On in that screen shot....dang it!
Sent from the third Galaxy
Click to expand...
Click to collapse
Just flash the superuser.zip I linked for you
om4 said:
Just flash the superuser.zip I linked for you
Click to expand...
Click to collapse
Even with S-ON?
Sent from the third Galaxy
The bootloader is unlocked so it doesn't matter. In the past we had to resort to exploiting the hboot for soff but now the security on the bootloader can be turned off, partially at least. It allows us to write to the partitions except for boot. There are plenty of workarounds for flashing the kernel. Basically fastboot, flash image gui, boot image flasher, HTC dumlock and the kernel installer script. There is an automated script being worked on to allow people to downgrade their hboot but honestly most users should stay away from it until it's stable.
om4 said:
The bootloader is unlocked so it doesn't matter. In the past we had to resort to exploiting the hboot for soff but now the security on the bootloader can be turned off, partially at least. It allows us to write to the partitions except for boot. There are plenty of workarounds for flashing the kernel. Basically fastboot, flash image gui, boot image flasher, HTC dumlock and the kernel installer script. There is an automated script being worked on to allow people to downgrade their hboot but honestly most users should stay away from it until it's stable.
Click to expand...
Click to collapse
Thanks for taking the time to explain this.
Sent from the third Galaxy
So I have the my EVO is unlocked, but S-ON. I'm Ruu 3.16 and HBOOT 2.09
I'm running a buggy Cyanogenmod 10.3 alpha or something.
I've tried to Moonshine, I've tried flashing roms S-ON way with CMD prompt but touchscreen only works on the Cyanogenmod 10.3.
My next attempt was to try the Dirty Racun, but I don't want to go through the whole not having a phone situation. So I might try over the weekend.
I seen this post http://forum.xda-developers.com/showthread.php?t=2089509
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily.
I wanted to try it, but I'm not sure if it will work. I'm pretty computer savvy but custom roms and stuff is so new to me. So my question is how can I either go back to stock Android which I would prefer or go S-Off to dl stable ROMS. Can anyone help?
Thanks to all that reply.
mixtkid said:
So I have the my EVO is unlocked, but S-ON. I'm Ruu 3.16 and HBOOT 2.09
I'm running a buggy Cyanogenmod 10.3 alpha or something.
I've tried to Moonshine, I've tried flashing roms S-ON way with CMD prompt but touchscreen only works on the Cyanogenmod 10.3.
My next attempt was to try the Dirty Racun, but I don't want to go through the whole not having a phone situation. So I might try over the weekend.
I seen this post http://forum.xda-developers.com/showthread.php?t=2089509
Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.
After this flash stock RUU again.
Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily.
I wanted to try it, but I'm not sure if it will work. I'm pretty computer savvy but custom roms and stuff is so new to me. So my question is how can I either go back to stock Android which I would prefer or go S-Off to dl stable ROMS. Can anyone help?
Thanks to all that reply.
Click to expand...
Click to collapse
You have a few choices: Stay rooted, S-on & understand the limitations of being S-on means that you have to flash the kernel separately from the ROM. Click on the top link in my sig to understand more. Or you can go for S-off, as many of us already have.
Your touchscreen issue is due to an updated touch panel driver that was included in the 3.16 update. You can only use Sense ROM's based on software version 3.16 & 3.17, or AOSP ROM's with the 3.4 kernel. You can downgrade the driver if you're S-off, which will allow you to run older ROM's.
You ultimately have to decide what you want to do with your phone. If you want to flash ROM's while S-on, that's not a problem, just understand that there is a little more work involved to get the ROM up & running. S-off makes life much easier. Remember, there is an entire community here to help you, too:thumbup:
Sent from my HTC EVO 4G LTE
FinZ28 said:
You have a few choices: Stay rooted, S-on & understand the limitations of being S-on means that you have to flash the kernel separately from the ROM. Click on the top link in my sig to understand more. Or you can go for S-off, as many of us already have.
Your touchscreen issue is due to an updated touch panel driver that was included in the 3.16 update. You can only use Sense ROM's based on software version 3.16 & 3.17, or AOSP ROM's with the 3.4 kernel. You can downgrade the driver if you're S-off, which will allow you to run older ROM's.
You ultimately have to decide what you want to do with your phone. If you want to flash ROM's while S-on, that's not a problem, just understand that there is a little more work involved to get the ROM up & running. S-off makes life much easier. Remember, there is an entire community here to help you, too:thumbup:
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
So I think I'd probably just Flash a ROM S-ON version like I already have done. I've tried the S-Off stuff before and failed with Moonshine, and Facepalm i think its called. Could you tell me a good ROM that will confirmed work with 3.16 S-ON. Also I have TWRP recovery if that makes a difference. Thanks for the fast reply by the way.
MeanBean is S-on friendly. Flash the ROM zip once and reboot. The phone will boot to the HTC splash screen and then reboot to recovery. Flash the ROM zip again and reboot. Don't forget to wipe properly in TWRP prior to flashing.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You have a few choices: Stay rooted, S-on & understand the limitations of being S-on means that you have to flash the kernel separately from the ROM. Click on the top link in my sig to understand more. Or you can go for S-off, as many of us already have.
Your touchscreen issue is due to an updated touch panel driver that was included in the 3.16 update. You can only use Sense ROM's based on software version 3.16 & 3.17, or AOSP ROM's with the 3.4 kernel. You can downgrade the driver if you're S-off, which will allow you to run older ROM's.
You ultimately have to decide what you want to do with your phone. If you want to flash ROM's while S-on, that's not a problem, just understand that there is a little more work involved to get the ROM up & running. S-off makes life much easier. Remember, there is an entire community here to help you, too:thumbup:
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
FinZ28 said:
MeanBean is S-on friendly. Flash the ROM zip once and reboot. The phone will boot to the HTC splash screen and then reboot to recovery. Flash the ROM zip again and reboot. Don't forget to wipe properly in TWRP prior to flashing.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thank you for the help. I'm going to give it a try after work. I'll let you know how it goes.