Hey guys,
im a bit of a moron and decided to update my desire s to 2.3.5 from 2.3.3 using the file RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
i have a deisre s from three (UK) which i s-off'ed myself.
the updated completed fine, but crashed when it reboted, now my desire freezes at the htc logo screen, if i press the volume down button and try to go to recovery i get a red triangle and exclamtion mark.
any ideas please?
thank you
chairmanmeow1 said:
Hey guys,
im a bit of a moron and decided to update my desire s to 2.3.5 from 2.3.3 using the file RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
i have a deisre s from three (UK) which i s-off'ed myself.
the updated completed fine, but crashed when it reboted, now my desire freezes at the htc logo screen, if i press the volume down button and try to go to recovery i get a red triangle and exclamtion mark.
any ideas please?
thank you
Click to expand...
Click to collapse
Which method did you use to gain s-off, revolutionary? What is your current hboot?
I'm suggesting it's still 6.XXXX, downgrade your hboot and run the ruu again.
Recovery isn't present cause a ruu puts you back to stock, there is only a fault at the revolutionary hboot, it can't be overwritten with standard methods, look at the index thread, there is a downgrade tutorial.
Swyped from my Desire S
Tectas said:
Recovery isn't present cause a ruu puts you back to stock
Click to expand...
Click to collapse
could he try and install fastboot drivers and flash a new hboot/rom/custom recovery or would what the RUU has done render my solution useless..
correct me if i'm wrong...
Zachary
anonymous_1997 said:
could he try and flash a custom recovery through fastboot and flash a new hboot/rom or would what the RUU has done render my solution useless
Click to expand...
Click to collapse
He can do that if his hboot hasn't changed, but as i understand it, he wants the ruu.
But another option would be to run the ruu without attached device. Don't close the first window. Search for the rom.zip. Copy it into any other folder. Open it and remove everything except the system.img & boot.img. Rename the rom.zip to PG88IMG.zip and flash it from bootloader or flash the system.img and boot.img itself with fastboot. But I don't know if this is what he wants, cause only the system is changed, but not recovery or bootloader.
Hi, i did use revolutionary to s-off, wanted to get rid off the ****ty three branded rom, my
hboot is 6.98.1002
radio 3822.10.08.04_M
can i downgrade the hboot without being able to boot into the phone?
i just want to get it working again, dont mind not having 2.3.5
The easiest way would be to flash a custom recovery image with fastboot (such as clockworkmod), after that download another hboot from here or here.
Extract the hboot.img.
Reboot to recovery. Open a terminal and type
Code:
adb devices
adb push hboot.img /sdcard/hboot.img (be sure you're in the folder where hboot.img is on your harddrive)
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your alpharev hboot )
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flash new hboot )
exit
Reboot to bootloader, there should be 0.98.2000 or 2.00.2002 instead of 6.98.1002, after that you can run every ruu you want, but don't forget, after running a ruu your bootloader is back to s-on.
---------- Post added at 02:25 PM ---------- Previous post was at 02:20 PM ----------
Oh btw, why you want to use the ruu and not a custom 2.3.5 rom with sense 3 or 3.5, there are as many out there.
Tectas said:
He can do that if his hboot hasn't changed, but as i understand it, he wants the ruu.
But another option would be to run the ruu without attached device. Don't close the first window. Search for the rom.zip. Copy it into any other folder. Open it and remove everything except the system.img & boot.img. Rename the rom.zip to PG88IMG.zip and flash it from bootloader or flash the system.img and boot.img itself with fastboot. But I don't know if this is what he wants, cause only the system is changed, but not recovery or bootloader.
Click to expand...
Click to collapse
ok gotcha..thanks for clearing that up
---------- Post added at 12:34 PM ---------- Previous post was at 12:28 PM ----------
Tectas said:
Reboot to recovery. Open a terminal and type
Code:
adb devices
adb push hboot.img /sdcard/hboot.img (be sure you're in the folder where hboot.img is on your harddrive)
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your alpharev hboot )
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flash new hboot )
exit
Click to expand...
Click to collapse
didnt know you could backup your hboot good info probably should do that next time i flash a hboot... last one i did was a eng s-off from revolutionary's pvt ship s-off
Since you're revolutionary s-off, you could flash 4ext or clockworkmod recovery, and then flash a custom rom. The official Ruu tries to install latest hboot with new partitioning table (/system and /system/lib are now separated). As revolutionary hboot can't be replaced by ruu, it can't work. Just either flash a custom rom, or flash eng hboot over revolutionary, search for "engHBOOToverARX" in desire s forums. I used that method to get rid of revolutionary hboot.
Sent from my HTC Desire S with Virtuous Affinity
download ANDROID FLASHER and 4EXT recovery.zip from the 4EXT thread. Open the ZIP and extract the recovery.img, and flash using ANDROID FLASHER. Then, open recovery and format cache. DONE
thanks for the help guys
i downloaded the fastboot drivers and the android flasher program also cynogen 7.1 stable build
i run the program with my phone in fstboot and then tick recovery or bootloader?
Recovery, and select the recovery.img from the 4ext recovery.zip. You can find it in the thread.
Sent from my iPod touch using Tapatalk
thanks
all is well again, i have cynogenmod 7.1 running
Related
Hello guys! I do know that I should ask this question in "GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5" thread but you know I can't do it because I do not have enough posts.
To admins: if you find my question useful then please replace this post to the appropriate forum thread.
Finally my question:
I have Desire S, it was S-Off'ed by Revo, then Rooted and now I have 6.98.1002 Hboot (and I'm using Proxuser's Desire S Gingerbread 2.3.5 with Sense 3.0 {v0.5} ROM).
All I want now is to upgrade my bootloader to 2.00.2002 and then to flash a new stock kernel.
Although we have a detailed manual by Biglsd and Mihaibuda, I can't perform it.
As manual says, I should
b1)In cmd run the following commands (after each command press enter):
adb devices
adb shell
su
Click to expand...
Click to collapse
but after "su" I have this issue:
and I think smth is going wrong because if i try then to flash new hboot using
"dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18"
adb tells me that it can not find file or directory.
May be someone knows what's the problem?
PS. I have read all "GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5" thread and found there a jorgen2009's way to update hboot http://forum.xda-developers.com/showpost.php?p=17059447&postcount=63. But this way is only for those guys who have old HBOOT ENG S-OFF. Or I'm mistaken?
Did you copy the hboot.img to your sdcard? It's not necessary to write the su command. Write directly the two dd commands. I did the whole process last night successfully...
Alex_whatever, thank you man for your answer. I have just performed flashing new Hboot. Of course I copy hboot.img to the root directory of my sdcard before I start the whole procedure. And as people in "GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5" thread told, once I see a "#" symbol in cmd, I'm a superuser. So it is not necessary to write "su" as u tell me. But the problem was in incorrect sdcard mounting. After I mounted /sdcard via appropriate menu in recovery I am able to access it via "dd" comands.
Messengerskiller said:
But the problem was in incorrect sdcard mounting.
Click to expand...
Click to collapse
Oh, ok i got it! I hadn't any sdcard mount issue. That's why i asked if you copy the hboot.img to the sdcard..
Ok, Alex_whatever, may be you tell me how did you flash kernel after flashing new hboot (if you did it)?
If I put htc-kernel-2.6.35.10-g71.blablabla.zip into the root directory of sdcard, then boot in recovery then choose "install zip from sdcard" and choose copied zip, it does flash it, but after this htc does not boot. It only boots in recovery again and again if I try to "reboot system now" from recovery.
So what's the problem now?
Did you make a backup of your rom before hboot flash? Because after the hboot flash you have to wipe all the partitions and restore the rom. Then you flash the kernel and in the end you have to flash PG88IMG.zip via bootloader. You must copy PG88IMG.zip to your sdcard.
If you didn't a backup, wipe the partitions and flash the rom again. Then flash the kernel and finally flash PG88IMG.zip.
Seems like I'm an amazing noob. F##k yeah.
My mother used to ask me "baby, don't you forget to make a backup before?" and I always answered "of course yes!". So I have a nandroid backup and it's quite nice, isn't it? (=
Although everything seems to be clear I forget about PG88IMG.zip. Brickwall wants to meet my head, I know. So I boot in recovery, wipe everything, do nandroid backup, then flash kernel, than try to flash PG88IMG.zip via recovery and of course it tells me that process aborted.
Ok. Let's sum up.
All the things one should know to update his/her hboot seems to be clear.
Then to flash new kernel one should flash kernel's zip from recovery and then flash lib.img (PG88IMG.zip) via bootloader.
If it were written in "GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5" thread, it would be manу times easier for noobs like me to upgrade their htc.
Thank you, Alex_whatever , anyway.
Messengerskiller said:
My mother used to ask me "baby, don't you forget to make a backup before?" and I always answered "of course yes!". So I have a nandroid backup and it's quite nice, isn't it?
Click to expand...
Click to collapse
Hahahah... Don't worry man! You can always reflash your rom. After the kernel flash remember to reboot to bootloader and follow the on-screen instructions to flash the PG88IMG.zip.
Cheers.
Hi,
After running with revolutionary and my rooted stock rom 1.47.401.4, I got yesterday a new OTA with 2.10.401.4 (2.3.5 and sense 3).
When trying to install it, it failed (blue android with big "!" on my screen)
First I downgraded my hboot back to 0.98.0000, but than I did something stupid .
I flash my hboot to the one provided with the OTA 2.00.0002, incl radio and all other stuff from the firmware.zip.
Now I ended up with a *** LOCKED *** HBOOT 2.00.0002, but also a 1.47.401.4 rom with android.
I tried to use the RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe from windows, but that fails as the hboot has the incorrect version.
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
I also searched for an RUU_Sage_HTC_Europe_*2.10.401.4*.exe as that might work because the HBOOT has the right version, but I could not find anything like that
Does anyone have an idea how I can go forward or how to go back ??
My phone is alive again as used the recovery.img procedure below and installed Saga3D 3.0. After that, I tried also the RUU installation to fully go back to stock, but that doesn't work. It complains about a security failure in hboot screen. I locked it back with 'fastboot oem lock', but that doesn't make the RUU work either.
lessimp said:
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
Click to expand...
Click to collapse
did u try that or u think that wont work?
Before I updated to 2.00.0002, I created a dd-backup on the sdcard for the 0.98.000
when I however use adb to connect, I don't see how I can restore that back without root. I also didn't see the sdcard mounted
I was also thinking ....
Would it maybe also be possible to create a PG88IMG.zip with all the right software for 1.47.401.4 ? and restore that via recovery ? would the current hboot allow a downgrade ?
Today I was able to get the **LOCKED*** off to UNLOCKED via htcdev.com
In the thread http://forum.xda-developers.com/showthread.php?t=1299438
I found this (identical to my problem)
If anyone has the same problem and has hboot-2.00.0002 & S-ON you have to unlock the bootloader via htcdev.com site following all the steps and flash the EXT4 Recovery via FASTBOOT and NOT ADB.!!
Then go to recovery and flash any custom rom.
I don't unserstand what I have to do next. ADB does not work anymore, and only fastboot is available. I downloaded an EXT4 recovery (4EXTRecovery_v2.1.0_saga.zip) which have me an recovery.img and a META-INF folder.
When I name the zip image update.zip, and run
C:\android>fastboot.exe update update.zip
it fails with ...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
How to I proceed to get it working ?
BTW, HBOOT is UNLOCKED but still S-ON
Please help
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
budingyun said:
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
Click to expand...
Click to collapse
You can RUU with that correct version or follow my instructions to achieve custom recovery/rom since you are already "unlocked":
Skanob said:
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
fastboot flash recovery D:\recovery.img (<- should be directory of 4ext recovery image)
fastboot reboot-bootloader
Now you should have 4ext recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
From here on you can now flash custom ROMs that you would like that is compatible to Desire S.
Right after playing around with my dev desire-s, i'm stuck:
I have hboot 2.00.0002 with S-ON and unlocked using htcdev
4ext on recovery
I want to either run stock 2.10 rom or downgrade to 1.47
Running 2.10 RUU gives error 155 same with RUU 1.47
using 4ext to flash PB99IMG of 2.10 doesn't work (ie does boot)
funny thing: looking at the partition table in 4ext its missing the /devlog and /system/lib partitions.
I did try http://forum.xda-developers.com/showthread.php?t=1318919 but no success
anybody have a clue what i'm doing wrong ??
Thanks
Jesterz said:
Right after playing around with my dev desire-s, i'm stuck:
I have hboot 2.00.0002 with S-ON and unlocked using htcdev
4ext on recovery
I want to either run stock 2.10 rom or downgrade to 1.47
Running 2.10 RUU gives error 155 same with RUU 1.47
using 4ext to flash PB99IMG of 2.10 doesn't work (ie does boot)
funny thing: looking at the partition table in 4ext its missing the /devlog and /system/lib partitions.
I did try http://forum.xda-developers.com/showthread.php?t=1318919 but no success
anybody have a clue what i'm doing wrong ??
Thanks
Click to expand...
Click to collapse
.... Follow this guide buddy and hope it will solve your issue.............
Guys i followed these guides... only to find i had s-on still after unlocking bootloader from HTCDEV but could not root install a recovery fornthis very reason of s-0n
here is how i manged to work round it and all good for me.
1 i downloaded the new android fash tool in android development section.
2 i downloaded a clockmod recovery .img for my desire s phone.
3 i installed the android flash tool which i found to be user friendly and then i loaded the recovery .img in in which the android tool have drop down boxes (so easy)
4 i pressed the flash button after loading .img in the android flash tool...........and thats it i have a recovery image installed on my desire s with s-on.
NEXT STEP.....
i then rooted my phone this way
1 i downloaded from the su zipfile from the alpharevx/revu help page looks like this.......Does Revolutionary give me root?
No. You will need to flash this zipfile from recovery.
2 i installed this file to my root of sdcard
3 as i have a recovery in fast boot now i select install zip from sd
4 install the file you loaded on your sd.... something like this...su-2.3.6.3efgh-singed
ALL DONE YOU HAVE CLOCKMOD RECOVERY AND ROOTED WITH S-ON WITH A UNLOCKED BOOTLOADER FROM HTCDEV.
hope this all helps if not been coverd before but of course at your own risk.
Jesterz said:
Right after playing around with my dev desire-s, i'm stuck:
I have hboot 2.00.0002 with S-ON and unlocked using htcdev
4ext on recovery
I want to either run stock 2.10 rom or downgrade to 1.47
Running 2.10 RUU gives error 155 same with RUU 1.47
using 4ext to flash PB99IMG of 2.10 doesn't work (ie does boot)
funny thing: looking at the partition table in 4ext its missing the /devlog and /system/lib partitions.
I did try http://forum.xda-developers.com/showthread.php?t=1318919 but no success
anybody have a clue what i'm doing wrong ??
Thanks
Click to expand...
Click to collapse
You do not use recovery to flash a PB99img.zip file. You copy it to the root directory of your SD card and the boot into HBOOT and it will then ask you to apply the update.
partly solved by doing this:
http://forum.xda-developers.com/showthread.php?t=1330400&page=5
ie, i can now boot custom rom, still need to check if stock rom will work
Jesterz said:
partly solved by doing this:
http://forum.xda-developers.com/showthread.php?t=1330400&page=5
ie, i can now boot custom rom, still need to check if stock rom will work
Click to expand...
Click to collapse
should be able too by making a gold card first because of the s-on
---------- Post added at 10:02 PM ---------- Previous post was at 09:52 PM ----------
tpbklake said:
You do not use recovery to flash a PB99img.zip file. You copy it to the root directory of your SD card and the boot into HBOOT and it will then ask you to apply the update.
Click to expand...
Click to collapse
correct me if i am wrong PB99IMG IS FOR THE DESIRE AND PG88IMG IS FOR THE DESIRE S........ in this post its stated you have desire s but using PB99IMG INSTEAD OF PG88IMG
hotpointdave said:
should be able too by making a gold card first because of the s-on
---------- Post added at 10:02 PM ---------- Previous post was at 09:52 PM ----------
correct me if i am wrong PB99IMG IS FOR THE DESIRE AND PG88IMG IS FOR THE DESIRE S........ in this post its stated you have desire s but using PB99IMG INSTEAD OF PG88IMG
Click to expand...
Click to collapse
Good catch. I completely missed that in his previous post. He should be renaming the file to PG88IMG.zip.
As the title says my phone is stuck on the "initiating swagger" bootscreen from my last ROM. So initially I was trying to try out a new 4.3 based rom, but eventually figured out it wasn't working because my HBOOT is too old (1.14.002). From what I gather in order to upgrade my HBOOT safely, I need S-OFF. I had unlocked bootloader and SUPERCID but never got S-OFF. So I tried to restore to the backup I mad in TWRP, but that wouldn't make it past the bootloader, so I downloaded another 4.1.2 ROM instead, which got me to the previously mentioned bootscreen and thats as far as I go. What can I do from here? I gone through countless times, wiping cache,data, factory reset then installing rom, the loading boot.img, but I'm stuck. Any help would be appreciated.
At&T htc one x
hboot 1.14.002
If you're s-on you need to flash the boot.img from the ROM zip via fastboot.
And yes you must have s-off to safely run the 3.18 RUU to meet the requirements for the 4.2.2 ROMs.
Sent from my Evita
timmaaa said:
If you're s-on you need to flash the boot.img from the ROM zip via fastboot.
And yes you must have s-off to safely run the 3.18 RUU to meet the requirements for the 4.2.2 ROMs.
Sent from my Evita
Click to expand...
Click to collapse
I have been flashing the boot.img through the bootloader via fastboot. No luck.
Which version of TWRP are you using?
Sent from my Evita
timmaaa said:
Which version of TWRP are you using?
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.5
That's good problem, 2.5 is full of bugs. You need to upgrade to at least the 2.6 version. Here's how:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and try again.
Sent from my Evita
Awesome, that worked. Now in order to flash a 4.3 mod I need to get S-off and then upgrade the hboot, right? How to I upgrade the hboot?
Thanks a lot.
Actually nevermind, I put hboot 2.14 on there and am now running PACman rom. Thanks again.
Recently I tried out a custom rom on my T-mobile branded One S, but I want to revert back to stock in order to do a S-OFF.
Before flashing the custom rom I ran the latest official t-mobile firmware, non rooted, original recovery, h-boot 2.16 and radio 1.15, S-ON. I unlocked the phone with an HTC-dev unlock token, flashed TWRP recovery and flashed a custom rom but left the phone S-ON.
Now I want to revert back to stock so I can do a S-OFF (which is needed for certain roms). I picked a RUU corresponding my CID t-mob101, in this case the only one I could find was:
Code:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
I wanted to try this one, but the download link is dead:
Code:
RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_si gned.exe
I flashed back the original recovery, relocked the phone and tried to run the RUU. However when running the RUU I get an 155 error, which means the RUU isn't corresponding to my CID?
Does this mean i'm out of any options reverting to stock? I don't have a nandroid backup..
Thanks in advance!
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
First: S-off using facepalm follow this:
1) update your android sdk by clicking android sdk manager and then update from there.
2) after the update finished, shut down your computer and then turn it on again.
3) turn off your phone, just leave it off for like 5 minutes then go to recovery, wipe cache and dalvik cache, then fix permissions then reboot to system.
4) using ONLY the oem htc usb cable, plug in your phone to a usb 2.0 port.
5) just before doing anything else, first check if your phone is recognized by typing "adb devices", there you should see your devices' serial number if it's recognized correctly.
6) then proceed to the steps of facepalm.
Just remember to NOT do the fastboot flash firmware again after error 92. Then after finishing "fastboot oem boot", your computer should then recognize again your phone, then you could proceed to the last three commands.
This is how i managed to have s-off using facepalm. At first i was really frustrated of that error 99, but a little reading and searching won't hurt you.
Take note that the steps i just said may or may not be required to do so, and i don't know if all these steps are really necessary but i just want to share to you guys that have had the same problem as mine. Good luck guys. Hope this helps.
Click to expand...
Click to collapse
hongha_222 said:
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
Click to expand...
Click to collapse
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
mk13139 said:
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
Click to expand...
Click to collapse
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
hongha_222 said:
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
Click to expand...
Click to collapse
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
mk13139 said:
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
Click to expand...
Click to collapse
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
hongha_222 said:
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
Click to expand...
Click to collapse
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
cyberusman said:
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
Click to expand...
Click to collapse
I was on HBOOT 2.15 (from JB OTA). With that hboot, you can not get SuperCID only by altering it in mmcblk0p4, so I had to do s-off first. If you have SuperCID, why dont you try facepalm s-off method? http://forum.xda-developers.com/showthread.php?t=2155135
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
rolo143 said:
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Have you tried my instructions that are on this page? http://forum.xda-developers.com/showpost.php?p=46939498&postcount=7
I haven't. Can I use that method and install the backup doesn't matter which firmware version I have?
Sent from my One S using xda app-developers app
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
When you had this problem were you on hboot 2.16? I have super cid but when i try to flash the zip file for face palm s-off it gives me error 99 unkown fail