I have the evo the shift down to 2.2 and I've tried running the one click root, and manual script to obtain s-off but for some reason the phone won't take the eng hboot. I even have the bootloader unlocked. Also try perma-rooting through visionary and its still a no go.
Any suggestions?
Sent from my PC36100 using xda premium
What bootloader version are you on? You say the bootloader is unlocked, did you use the unlock tool then downgrade using the ruu? If so, what is happening when you try and flash the eng bootloader?
Sent from my PG06100 using Tapatalk 2
crump84 said:
What bootloader version are you on? You say the bootloader is unlocked, did you use the unlock tool then downgrade using the ruu? If so, what is happening when you try and flash the eng bootloader?
Sent from my PG06100 using Tapatalk 2
Click to expand...
Click to collapse
I'll have to check what version the bootloader is later when I get off work. I did use the unlock tool then I ran into an issue where all the phone did was stay on the htc screen. I ended up fixing it using this guide: http://forum.xda-developers.com/showthread.php?t=1513386
It flashed 2.2 so now when I go to root I put in all the commands in cmd and it looks like it flashed the hboot, but when I got to check the md5sum it doesn't match the hboot I'm attempting to flash. It only matches the one on the phone.
MTsol said:
I'll have to check what version the bootloader is later when I get off work. I did use the unlock tool then I ran into an issue where all the phone did was stay on the htc screen. I ended up fixing it using this guide: http://forum.xda-developers.com/showthread.php?t=1513386
It flashed 2.2 so now when I go to root I put in all the commands in cmd and it looks like it flashed the hboot, but when I got to check the md5sum it doesn't match the hboot I'm attempting to flash. It only matches the one on the phone.
Click to expand...
Click to collapse
Did you go through the downgrade process after using the unlock tool? Just unlocking the bootloader and flashing a 2.2 ROM won't allow you to achieve s-off. You need to actually downgrade your Hboot by using the RUU. Sorry if I'm misunderstanding but you never mentioned downgraded the actual bootloader.
Sent from my PG06100 using Tapatalk 2
crump84 said:
Did you go through the downgrade process after using the unlock tool? Just unlocking the bootloader and flashing a 2.2 ROM won't allow you to achieve s-off. You need to actually downgrade your Hboot by using the RUU. Sorry if I'm misunderstanding but you never mentioned downgraded the actual bootloader.
Sent from my PG06100 using Tapatalk 2
Click to expand...
Click to collapse
Downgrading the Hboot is where I'm having issues. I thought the ruu didn't downgrade the hboot?
Sent from my PC36100 using xda premium
MTsol said:
Downgrading the Hboot is where I'm having issues. I thought the ruu didn't downgrade the hboot?
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
You need to run the Froyo RUU in order to achieve s-off. I'm not sure what all you've done but since you unlocked the bootloader you may want to check this thread http://forum.xda-developers.com/showthread.php?t=1357157
Or this one (HTC unlock isn't needed for this method) http://forum.xda-developers.com/showthread.php?t=1558532 not sure how this will work since you used the unlock tool.
Sent from my PG06100 using Tapatalk 2
crump84 said:
You need to run the Froyo RUU in order to achieve s-off. I'm not sure what all you've done but since you unlocked the bootloader you may want to check this thread http://forum.xda-developers.com/showthread.php?t=1357157
Or this one (HTC unlock isn't needed for this method) http://forum.xda-developers.com/showthread.php?t=1558532 not sure how this will work since you used the unlock tool.
Sent from my PG06100 using Tapatalk 2
Click to expand...
Click to collapse
Also if the 2.2 RUU .exe isn't running from HBOOT, you can Boot into Fastboot, and run it. You might be able to use the indirect's method after the HTC Unlock Tool, IDK. But I would personally just Update back to 2.3.4 . Then start the process all over again using indirect's method. I used the idiect's Manual Method, it worked perfectly.
my Hboot version is 0.99.0001. Each time I run the ruu it gets stuck at 13% and says checking header.
MTsol said:
my Hboot version is 0.99.0001. Each time I run the ruu it gets stuck at 13% and says checking header.
Click to expand...
Click to collapse
Crump asked you a very important question. What steps have you done already before the RUU ? Also make sure your not using some knock off cable.
The phone started off with being on 2.3.4 and I followed the steps from the first link crump posted. Then after I flashed the clockwork recovery the phone wouldn't boot into anything. After I got that fixed by pushing the 2.2 update to the phone I followed the steps to flash the eng hboot. But when I go to verify the hboot it doesn't match the one its supposed to be.
Sent from my PC36100 using xda premium
MTsol said:
The phone started off with being on 2.3.4 and I followed the steps from the first link crump posted. Then after I flashed the clockwork recovery the phone wouldn't boot into anything. After I got that fixed by pushing the 2.2 update to the phone I followed the steps to flash the eng hboot. But when I go to verify the hboot it doesn't match the one its supposed to be.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Well you should have RUU'd back to 2.2 first. Then rooted, and then Recovery. Are you S-OFF at this point? If not, what I would suggest you do is Update to 2.3.4 . Then start the whole process over with the second link crump posted for indirect's method. Use the Manual Method, and follow the steps carefully. It works, I've used it several times.
Woo I got it! It was weird though I did the ota update back to 2.3.4 and after it was done I got the same result as before (shift stuck on htc screen) So I grestored it back to 2.2 then ran indirect's method then it let me run the ruu. After all that the shift took the hboot without a problem. So I am now S-OFF again.
Thanks to you both prboy1969 & crump84
Your very welcome. Glad you got it all sorted out . Now go enjoy your phone
TEAM MiK
MikROMs Since 3/13/11
Related
Hi
I have a sensation xe. I rooted it before upgrading it to ICS (before is GB).
I upgraded it by flashing official ics rom due to I previously installed clockworkmod recovery which stop me from normal way of upgrade.
After upgrade everything's fine, but superuser and clockworkmod gone.
When I install superuser it says binary not found. but I checked my bootloader it says S-OFF.
What should I do?
Android - 4.0.3
Software number - 3.32.401.105
Hboot - 1.27.0000
Radio - 11.22.3504.07_M
Nevermind.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
I don't know what is that, I think not.
I flashed it using RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R_Radio_11.69.3504.00U_11.22.3504.07_M_release_251961_signed.exe
If you find it locked you have to unlock first with htcdev.com but many user won't recommend it but at this time I think it the only way to unlock the bootloader, install the custom recovery(CWM) and install the superuser(root the phone).
You can get the details on this post.
But I already have it rooted before upgrade. I thought it will remain rooted? coz my bootloader shown S-OFF
OK, you have S-off. I guess you should be able to flash Revolutionary firmware from Boot loader, then use fast boot to flash the recovery, then flash root from the recovery you installed earlier and voila.
Sent from my Sensation using Tapatalk 2 Beta-6
Or, flash a firmware that contains recovery and then flash super user (just make sure its the correct firmware.) (I don't remember exactly where I seen this firmware, but I'm sure I have. Maybe here or somewhere else)
Sent from my Sensation using Tapatalk 2 Beta-6
xegneto said:
But I already have it rooted before upgrade. I thought it will remain rooted? coz my bootloader shown S-OFF
Click to expand...
Click to collapse
If you are S-Off you can root it again (because you flashed a RUU you lost root)
1) need to have a custom recovery (CWN or 4EXT). There is a nice tool to instal 4ext recovery HERE or download this PG58IMG. Just put it in your sd card and flash it from bootloader.
2) Then Download and install from custom recovery the Superuser-3.0.7-efghi-signed.zip
Done!
kualmente said:
If you are S-Off you can root it again (because you flashed a RUU you lost root)
1) need to have a custom recovery (CWN or 4EXT). There is a nice tool to instal 4ext recovery HERE
2) Download and install from recovery Superuser-3.0.7-efghi-signed.zip
Done!
Click to expand...
Click to collapse
By flashing the RUU he lost recovery.
Sent from my Sensation using Tapatalk 2 Beta-6
BurnRubber90 said:
By flashing the RUU he lost recovery.
Sent from my Sensation using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
In fact I wrote point 1) he needs a custom recovery first
XaQi 101 said:
If you find it locked you have to unlock first with htcdev.com but many user won't recommend it but at this time I think it the only way to unlock the bootloader, install the custom recovery(CWM) and install the superuser(root the phone).
You can get the details on this post.
Click to expand...
Click to collapse
They don't recommend it because it doesn't unlock the bootloader completely. Read more and please don't recommend it, it's incorrect. His bootloader is already unlocked, hence he is s off. As already mentioned he needs to root and install Recovery.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
kualmente said:
In fact I wrote point 1) he needs a custom recovery first
Click to expand...
Click to collapse
And the app needs root
Sent from my Sensation using Tapatalk 2 Beta-6
BurnRubber90 said:
And the app needs root
Sent from my Sensation using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Not if you flash a PG58IMG from bootloader. Done hundreds of times
If you download from Market then yes, you need root.
kualmente said:
Not if you flash a PG58IMG from bootloader. Done hundreds of times
Click to expand...
Click to collapse
You got me lol. I'm used to either flashing recovery through fast boot or running revolutionary to get it installed, then switch to 4EXT through the app
Sent from my Sensation using Tapatalk 2 Beta-6
BurnRubber90 said:
You got me lol. I'm used to either flashing recovery through fast boot or running revolutionary to get it installed, then switch to 4EXT through the app
Sent from my Sensation using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Correct. By revolutionary you install CWM and then you can switch to 4ext. same as I did but in his case he doesn't need to use Revolutionary because already unlocked and s-Offed (and also because Revolutionary doesn't support Hboot 1.27). He needs just to install a custom recovery by a PG58IMG and superuser to get root again.
If the. Hboot is the issue why not just get an older one, put it in a zip called pjwhatever.zip (not sure I own a wildfire) and then just put into bootloader and flash it. He has s-off like.??
sent from my android powered beast!
heavy_metal_man said:
If the. Hboot is the issue why not just get an older one, put it in a zip called pjwhatever.zip (not sure I own a wildfire) and then just put into bootloader and flash it. He has s-off like.??
sent from my android powered beast!
Click to expand...
Click to collapse
Hboot has nothing to do. The OP wants just root the phone again after upgrade to ICS.
Also, I think we are hitchhiking the thread with OT postings.
That said, this is my last post here.
For the OP: Follow instructions few posts above and good luck
kualmente said:
Hboot has nothing to do. The OP wants just root the phone again after upgrade to ICS.
Also, I think we are hitchhiking the thread with OT postings.
That said, this is my last post here.
For the OP: Follow instructions few posts above and good luck
Click to expand...
Click to collapse
ahh, sorry i misread. i thought the ruu had upgraded the hboot to the htcdev hboot that has the locked unlocked thing. my bad.
Thank you so much for teaching me. I have custom recovery and superuser now in my phone.
but I have 1 more question, what is the ***LOCKED*** means in my bootloader? Is that simlock?
xegneto said:
Thank you so much for teaching me. I have custom recovery and superuser now in my phone.
but I have 1 more question, what is the ***LOCKED*** means in my bootloader? Is that simlock?
Click to expand...
Click to collapse
It means you cannot use advanced fastboot commands. You're still s off, don't worry about locked.
Sent from my HTC Sensation 4G with Beats Audio using xda premium
I have looked but not found any specifics on my question. I installed 3.20.502.52 RUU when my phone was already S-off and rooted prior due some issues I was having (big mistake, I know). I re-installed a recovery no problem (still s-off) and have been using custom ROMs since. I am actually thinking about flashing RUU 2.47.502.7 which was the original update to Gingerbread from Froyo because I am looking into playing around some with UOT. My concern is whether I will actually be able to flash the ruu safely or not. Since my bootloader was updated to 2.0, will it be downgraded back to 0.85? If so will I be able to utilize AAHK again?
aybarrap1 said:
I have looked but not found any specifics on my question. I installed 3.20.502.52 RUU when my phone was already S-off and rooted prior due some issues I was having (big mistake, I know). I re-installed a recovery no problem (still s-off) and have been using custom ROMs since. I am actually thinking about flashing RUU 2.47.502.7 which was the original update to Gingerbread from Froyo because I am looking into playing around some with UOT. My concern is whether I will actually be able to flash the ruu safely or not. Since my bootloader was updated to 2.0, will it be downgraded back to 0.85? If so will I be able to utilize AAHK again?
Click to expand...
Click to collapse
The ruu can't run on an older hboot than the one included in ruu. You can use a PD98IMG though to flash the older gingerbread hboot and then run ruu.
Sent from my Inspire 4G using xda premium
---------- Post added at 09:46 PM ---------- Previous post was at 09:41 PM ----------
Here is that IMG if you need it.
HBOOT 0.85.0024 PD98IMG
Sent from my Inspire 4G using xda premium
Gizmoe said:
The ruu can't run on an older hboot than the one included in ruu. You can use a PD98IMG though to flash the older gingerbread hboot and then run ruu.
Click to expand...
Click to collapse
Sounds simple enough. So once I flash the older hboot and run the ruu, I should be able to use AAHK to obtain root? Flashing the hboot should leave my s-off intact.
aybarrap1 said:
Sounds simple enough. So once I flash the older hboot and run the ruu, I should be able to use AAHK to obtain root? Flashing the hboot should leave my s-off intact.
Click to expand...
Click to collapse
You will remain s off. If you want to remain on that ruu with root by using the hack kit you would have to revert back to s on before running option 1 again. Hack kit option 1 won't run successfully if you are s off already. I would just re flash recovery and then find a rooted version of the stock ruu and flash via recovery or use a PD98IMG.
Sent from my Inspire 4G using xda premium
After going back to the old hboot and flashing a recovery, I recommend flashing ClearDroid 1.3.0, booting and then flashing 1.3.1 without wiping. It is a very stable, customized version of the Gingerbread Sense 2.1 rom.
Sent using the power of the dark side.
Reverting to S-off
Gizmoe said:
You will remain s off. If you want to remain on that ruu with root by using the hack kit you would have to revert back to s on before running option 1 again. Hack kit option 1 won't run successfully if you are s off already. I would just re flash recovery and then find a rooted version of the stock ruu and flash via recovery or use a PD98IMG.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I know that AAHK has the option to revert back to stock unrooted and S-on. I tried it back when I first rooted just for the sake of doing so (was out of warranty anyway). If I flash the older bootloader, will AAHK revert everything to unrooted and s-on regardless of what ROM I am using? I am currently on CM7. If leaving CM7 in place and flashing the PD98IMG.zip then AAHK immediately after will work it will actually save time.
I am wanting to do some UOT from scratch on this so I can learn. I have upgraded my contract and got the AT&T Galaxy S3. Now I am taking the Inspire to use as a test phone and personal ROM development learning just because. I want to have fun with it since I am no longer relying on it as my daily phone.
aybarrap1 said:
I know that AAHK has the option to revert back to stock unrooted and S-on. I tried it back when I first rooted just for the sake of doing so (was out of warranty anyway). If I flash the older bootloader, will AAHK revert everything to unrooted and s-on regardless of what ROM I am using? I am currently on CM7. If leaving CM7 in place and flashing the PD98IMG.zip then AAHK immediately after will work it will actually save time.
I am wanting to do some UOT from scratch on this so I can learn. I have upgraded my contract and got the AT&T Galaxy S3. Now I am taking the Inspire to use as a test phone and personal ROM development learning just because. I want to have fun with it since I am no longer relying on it as my daily phone.
Click to expand...
Click to collapse
I don't see why that wouldn't work. As long as you have the older hboot it should do the stock s on process. Then just run option 1. You should dabble in using dsixda kitchen if you want to start learning Rom cooking. You can take the rom.zip from the ruu and just root it and install busy box and create your own Rom.zip.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I don't see why that wouldn't work. As long as you have the older hboot it should do the stock s on process. Then just run option 1. You should dabble in using dsixda kitchen if you want to start learning Rom cooking. You can take the rom.zip from the ruu and just root it and install busy box and create your own Rom.zip.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I will take a look at dsixda. Thank you for your feedback.
Ok here it goes I will try to explain my situation. Sorry for my lack of information, and other nonsense.
I have unlocked bootloaded using HTC dev my bootloader shows a pink ***UNLOCKED*** at the top. I have loaded cwm recovery using aahk. All my attempts at trying to gain s-off have failed. I dont care about setting CID to 111111 (however many 1's it is) Is there a way to gain S-OFF with out using the aahk. I can't seem to flash any ROMS using cwm because of s-on?
When trying to attempt the downgrade via aahk in linux I am getting invalid image or some error in HBOOT, I just need to figure out how to gain s-off and all my problem I think will be solved. My problem, I have root, s-on, cwm recovery. but when flashing zips in CWM I get stuck on HTC screen. It's like its failing to write to some partitions because of s-on? I can make and restore backups just fine, except that one time when I flashed a boot.img with fastboot. (was getting desperate) so I restored and flashed the boot.img from my nandroid. All is well again.
Running Software:
Android v 2.3.3
HTC Sense 2.1
Baseband 12.56.60.25U_26.10.04.03_M
Kernal 2.6.35.10-gd2564fb
Build 2.47.502.7
HBOOT info:
*** UNLOCKED *** (Via HTC DEV )
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
Please any help or other information will be very helpful, in the mean time I will search and read up on everything. But all I seem to find is outdated information, and aahk. I would prefer to do everything manually, not matter how hard or how long it takes. I feel better doing everything myself, and I will know what went wrong and where when doing it this way. Please if there is a way to manually S-OFF, HELPS! :angel:
P.S. I have root if that helps, gained root using another tool I think it was htcsupertoolv3, but I have tried another tool as well, HTC_QuickRoot_1.1.13_Release.
Another question, Is it the radio flashing that gains S-OFF? is there a way to radio flash using fastboot with S-ON? I can flash stuff with fastboot. I Imagine I can flash with Hboot as well using a gold card, but for some reason I'm getting invalid image errors in Hboot when using aahk.
I just need some help in general lol. Don't be shy ppl I hit the thanks button alot. Thanks in advance!
You need to flash the insecure boot img and relock the bootloader before trying to run aahk... Do you have good instructions for that process?
Sent from my HTC Desire HD using xda app-developers app
RuggedHunter said:
You need to flash the insecure boot img and relock the bootloader before trying to run aahk... Do you have good instructions for that process?
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Wow, so all I need is the boot.img ( I can flash with fastboot correct?) Then relock bootloader, I don't exactly have good instructions, but I'm sure I can find! Thank you My head was hurting, now to start my search!
p.s. If you already got a link by all means post away!
I pm'd you step by step instructions for unlocking inspire, build 3.02.502.52...assuming that's what you are dealing with... If you're part way through the process already, or have already rooted via another method though, I have know idea if it'll work or what potential consequences there could be....so use it at your own risk.
Sent from my HTC Desire HD using xda app-developers app
RuggedHunter said:
I pm'd you step by step instructions for unlocking inspire, build 3.02.502.52...assuming that's what you are dealing with... If you're part way through the process already, or have already rooted via another method though, I have know idea if it'll work or what potential consequences there could be....so use it at your own risk.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Worked Like A Champ! Thank You, That boot.img is actually the one I flashed before when I thought I had screwed everything up. I just didnt relock then rerun aahk. I feel so dumb now. Thank goodness you saved my day! Much LOVE AND THANKS!
Glad I could actually help...
Now go flash Viper 1.2.3 in the Desire HD Dev threads and enjoy your *new* phone!
Sent from my HTC Desire HD using xda app-developers app
Totally went with Jellytime R30 xD, Perhaps I'll try Viper
This was my first HTC phone, and I must say after getting through all the confusion in reading old outdated stuff. It's one of my favs!
Again Thanks for the info about flashing the insecure boot.img and relocking bootloader in prep for aahk, Hopefully ppl like me who tend to overlook stuff will see this, and help them too.
Until my next phone adventure! Peace OUT XDA!
I'll just put this link here for anyone else who stumbles across this thread. It's a detailed list of instructions for new att Rom
http://forum.xda-developers.com/showthread.php?p=30828287
Sent from my Inspire 4G using xda premium
I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.
You need to S-off first.
Sent from my HTC One X using xda premium
tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.
knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Bump
Sent from my One S using XDA Premium 4 mobile app
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
bump
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.
Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.
pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!
So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks
pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755
[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.