Related
Hi.
I bought my Sensation few days ago. Updated it to 1.45.401.2, got bored with stock Rom. So I decided to unlock bootloader to use CustomeRoms
I removed SIMCard from Sensation (I needed it in my old phone) and used official bootloader unlocker tool from this site http://www.htcdev.com/bootloader and everything went ok. After unlocking I rebooted my phone to bootloader and saw this:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
Good so far.
Installed Recovery 5.0.2.0 (official tool doesn't include this) - no problem.
Downloaded ROM SlimSense, made full wipe (cache, data system, dalvik etc) installed it per Recovery (succesfully), rebooted and.... the problems started.
After rebooting bootloop started. Full wipe, reinstalation (succesful again), reboot and the same - bootloop.I thought that instalation .zip file maybe was broken - let's try different. Downloaded virtuous_sensation-s-pyramid-v3.0.0-beta ROM, full wiped, installed (succesfully), reboot and... the same - bootloop.
I started suspecting something is wrong so decided to cure my phone by flashing stockROM. Downloaded RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed from XDA, full wiped with recovery, and tried to flash it -RUU founds my phone, reboot it to start instalation (black screen with white htc- missing percentage info) and try to send files to phone for 15-20 sec - then RUU show message that it cannot update my phone. When I unplug phone from usb, phone goes back to bootloader and show:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
RUU
Security fail!
Update fail!
After this "try" i still have fully working Recovery. I tried also 1.35 and 1.73 stock ROMs - the same fail
I tried to unlock super cid 11111111 but it didn'twork - some SMART_IO.CRD file is missing.
Then i tried to use revolutionary way of unlocking, but without system on the phone it doesn't recognize it. And i can't have system cause RUU doesn't work.
Then I remembered that my SIM card is out of phone.
So I put it back but it didn't change anything: full wipe, instalation of SlimSense, reboot and... bootloop again, the same with virtuos.
The same fail with RUU! , the same supercid and revolutionary failure.
So here comes my question:
Is there any other posibility to flash stock ROM? PG58img somehow?
Pls - DON'T TELL me that i should use revolutionary first - i know it now.
Tell me how to solve this problem.
Tachion81 said:
Hi.
I bought my Sensation few days ago. Updated it to 1.45.401.2, got bored with stock Rom. So I decided to unlock bootloader to use CustomeRoms
I removed SIMCard from Sensation (I needed it in my old phone) and used official bootloader unlocker tool from this site http://www.htcdev.com/bootloader and everything went ok. After unlocking I rebooted my phone to bootloader and saw this:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
Good so far.
Installed Recovery 5.0.2.0 (official tool doesn't include this) - no problem.
Downloaded ROM SlimSense, made full wipe (cache, data system, dalvik etc) installed it per Recovery (succesfully), rebooted and.... the problems started.
After rebooting bootloop started. Full wipe, reinstalation (succesful again), reboot and the same - bootloop.I thought that instalation .zip file maybe was broken - let's try different. Downloaded virtuous_sensation-s-pyramid-v3.0.0-beta ROM, full wiped, installed (succesfully), reboot and... the same - bootloop.
I started suspecting something is wrong so decided to cure my phone by flashing stockROM. Downloaded RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed from XDA, full wiped with recovery, and tried to flash it -RUU founds my phone, reboot it to start instalation (black screen with white htc- missing percentage info) and try to send files to phone for 15-20 sec - then RUU show message that it cannot update my phone. When I unplug phone from usb, phone goes back to bootloader and show:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
RUU
Security fail!
Update fail!
After this "try" i still have fully working Recovery. I tried also 1.35 and 1.73 stock ROMs - the same fail
I tried to unlock super cid 11111111 but it didn'twork - some SMART_IO.CRD file is missing.
Then i tried to use revolutionary way of unlocking, but without system on the phone it doesn't recognize it. And i can't have system cause RUU doesn't work.
Then I remembered that my SIM card is out of phone.
So I put it back but it didn't change anything: full wipe, instalation of SlimSense, reboot and... bootloop again, the same with virtuos.
The same fail with RUU! , the same supercid and revolutionary failure.
So here comes my question:
Is there any other posibility to flash stock ROM? PG58img somehow?
Pls - DON'T TELL me that i should use revolutionary first - i know it now.
Tell me how to solve this problem.
Click to expand...
Click to collapse
PG58img ??? yes, you can try this : http://goo-inside.me/ruu/pyramid/fu...00U_10.14.9035.01_M_release_208857_signed.zip
after download, rename to PG58IMG.zip and move to root of your sd-card, enter to bootloader -> flash this...
i could be wrong (not an expert) but maybe its failing because your phone still says its S-ON
vegi71 said:
i could be wrong (not an expert) but maybe its failing because your phone still says its S-ON
Click to expand...
Click to collapse
As far as I know Official bootloader unlocker gives only "UNLOCKED" and it's enough to flash custom ROMs.
@ ranggazay
I extracted rom.zip from StockROM 1.45 renamed it to PG58IMG.zip and tried to flash but still nothing. Also tried the same earliers StockRoms (1.35, 1.27 etc).
Unfortunately I can't use your file cause i gave my phone to service.
Any solution?
Hello,
did you find a solution to the problem? I experienced this today and thinking about a repair unless I find something here. Did you get any solution? Thank you.
Try flashing the RUU again whist the phone is on FASTBOOT-USB
Same problem here - I'm interested in any solution
Tachion81 said:
As far as I know Official bootloader unlocker gives only "UNLOCKED" and it's enough to flash custom ROMs.
@ ranggazay
I extracted rom.zip from StockROM 1.45 renamed it to PG58IMG.zip and tried to flash but still nothing. Also tried the same earliers StockRoms (1.35, 1.27 etc).
Unfortunately I can't use your file cause i gave my phone to service.
Click to expand...
Click to collapse
S on will not allow you to flash radios. Unlocked bootloader through HTC does not give you s off which is a requirement to flash custom ROMS.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Htc dev method unlock only few parts of the bootloader.
It doesn't unlock the radio area, it doesn't give you advanced fastboot write command access (that's why you can't change your cid) and I think that the boot.img partition (where there is the kernel) is not flashable from recovery.
You unlocked your bootloader on a 2.3.4 rom (with a 2.3.4 kernel, sense 3.0) and you tried to flash two 2.3.5 roms.
Without the possibility to flash a new kernel your phone was trying to boot with a 2.3.4 stock kernel + a rom that was meant for 2.3.5. This could be the cause of your bootloops.
I would try to install a 2.3.4 rom, like android revolution HD 3.x.x, you could have problems with wifi but it should boot at least.
First of all get S-off then supercid ur phone. You need to have s off to install any custom Rom properly. Ones you do that hopefully solve problem. Try not to messing around u might brick ur phone. You already void ur warranty by unlocking bootloader.
Sent from my HTC Sensation Z710e using xda premium
su27 said:
Same problem here - I'm interested in any solution
Click to expand...
Click to collapse
Grandelama said:
Htc dev method unlock only few parts of the bootloader.
It doesn't unlock the radio area, it doesn't give you advanced fastboot write command access (that's why you can't change your cid) and I think that the boot.img partition (where there is the kernel) is not flashable from recovery.
You unlocked your bootloader on a 2.3.4 rom (with a 2.3.4 kernel, sense 3.0) and you tried to flash two 2.3.5 roms.
Without the possibility to flash a new kernel your phone was trying to boot with a 2.3.4 stock kernel + a rom that was meant for 2.3.5. This could be the cause of your bootloops.
I would try to install a 2.3.4 rom, like android revolution HD 3.x.x, you could have problems with wifi but it should boot at least.
Click to expand...
Click to collapse
Same problem but with different unit--- I have a HTC ChaCha.
Any solutions please? I would love to get S-OFF on my ChaCha but I know that is only possible via an XTC Clip.
Why would he have problems with WiFi? I think my stock ROM got broken or one of the stock ROM's kernels got messed up when I installed BusyBox because for some odd reason when I restored to factory settings with stock ROM the WiFi had problems connecting. It couldn't connect to anything at all.
I had same problem and this is how I solved it
Ok here is answer to solve you
Flash any 2.3.5 Rom and open that zip in computer and extract the boot.IMF file and place it to the web folder in c drive and and flash it immediately after installing Rom
Go to bootloader and make sure fastboot USB connected and then flash the boot.IMG file from cmd prompt
Sent from my HTC Sensation Z710e using XDA
With s-on and **unlocked** via htc.dev, you can't flash radio.img or boot.img, nor can you write using fastboot (eg. superCID). RUU will not run with s-on.
You will need to revert and downgrade via this guide, you can then either continue with custom flashing or run the ruu correct for your original software/baseband/carrier/location.
http://forum.xda-developers.com/showthread.php?p=23222794
Sent from my Pyramid-T
solution
ok here is solution
just after u unlocked your bootloader u have to keep stock rom.....means official 2.3.4 and then u need to flash android revolution rom "3.6.x"
then after that rom boots...........just open the revolutionary.exe and try to root it and i am sure u will get s-off
this is what i did to get out of this problem.......after this super cid your phone and u will be able to flash any ruu.....
if u think this helped press thanks button
ptlsajan said:
ok here is solution
just after u unlocked your bootloader u have to keep stock rom.....means official 2.3.4 and then u need to flash android revolution rom "3.6.x"
then after that rom boots...........just open the revolutionary.exe and try to root it and i am sure u will get s-off
this is what i did to get out of this problem.......after this super cid your phone and u will be able to flash any ruu.....
if u think this helped press thanks button
Click to expand...
Click to collapse
Flashing a custom ROM does not give you s off. Which part of you can't flash radios and kernels with s on do you not get?. You cannot flash Android Revolution ROM with s on. Read the OP of the thread, requires s off.
from my HTC Sensation 4G with Beats Audio using xda premium
Rhiannon224 said:
Flashing a custom ROM does not give you s off. Which part of you can't flash radios and kernels with s on do you not get?. You cannot flash Android Revolution ROM with s on. Read the OP of the thread, requires s off.
from my HTC Sensation 4G with Beats Audio using xda premium
Click to expand...
Click to collapse
You're wrong. You can flash ARHD with s-on. The only requisite is to flash the kernel (boot.img) by "fastboot flash boot boot.img" and voila. You need to have the unlocked bootloader with htcdev too.
My Sensation came with HBOOT 1.21, so no revolutionary at all. I unlocked by htcdev, installed 4ext recovery and ARHD 4.1.3 this way.
nangu said:
You're wrong. You can flash ARHD with s-on. The only requisite is to flash the kernel (boot.img) by "fastboot flash boot boot.img" and voila. You need to have the unlocked bootloader with htcdev too.
My Sensation came with HBOOT 1.21, so no revolutionary at all. I unlocked by htcdev, installed 4ext recovery and ARHD 4.1.3 this way.
Click to expand...
Click to collapse
i read that HBOOT 1.21 can be S-OFFed " reported done by a member " in [S-OFF] Juopunutbear S-OFF or [Finally Here!] HTC Unbricking Project threads , i don't remember if the device on GB or ICS
i think it is Juopunutbear S-OFF search inside it [S-OFF] Juopunutbear S-OFF , it is done using the wire trick , link http://unlimited.io/
the only comment i have , is to verify the S-OFF type , is it like hardware S-OFF " i.e can't be S-ON again for warranty reasons ? " or it Software S-OFF
ruu security fail update fail
hi
i am using htc explorer. somedays before i unlocked my phone through htc developer site. After that i made a partition in my sd card to increase internal memory of phone via using link2sd apps.
i found that my old application like ndtv which were already installed in my phone are not working .i reset my mobile by going into its setting menu.
Now phone stucks htc word screen.
To get out of the problem i tried to installed ruu.
But at the last of its installation part
i get an error 155
and get an message
ruu
security fail
update fail
after rebooting my phone it stucks to htc
show me the way to get out of it.
nirajkpatle said:
hi
i am using htc explorer. somedays before i unlocked my phone through htc developer site. After that i made a partition in my sd card to increase internal memory of phone via using link2sd apps.
i found that my old application like ndtv which were already installed in my phone are not working .i reset my mobile by going into its setting menu.
Now phone stucks htc word screen.
To get out of the problem i tried to installed ruu.
But at the last of its installation part
i get an error 155
and get an message
ruu
security fail
update fail
after rebooting my phone it stucks to htc
show me the way to get out of it.
Click to expand...
Click to collapse
if i remember well error 155 means connection issues
but i can't tell you more because you came in a sensation/xe/4g forum
search for your device's forum and ask there
Hi all,
I'm having a strange issue with the hboot downgrade process. I S-OFFed my DS using revolutionary, but wanted to go back to a stock ROM using one of the shipped RUUs. I realised I cannot flash the RUU over the revolutionary hboot, so I looked around the forum for a recipe how to downgrade to a stock 0.98.0000 or anything that would not render my DS unusable after using RUU.
I tried most hboot.img files on this forum and none of them managed to overwrite the current file. I don't know what to do, when I use the zip file method I get "Bootloader bypassed" message and nothing changes. I tried android flasher as well, and even though it reports that phone has been flashed successfully it sill comes up with the revolutionary hboot version and running a RUU makes my phone stuck on the HTC logo.
There was one tutorial topic on how to go back to the original hboot, but it was pulled by the author due to people bricking their phones caused by not following the instructions properly etc.
I would appreciate any help, as I really want to go back to S-ON and stock ROM. At the moment I'm rocking CM7 as thankfully I made a nandroid backup before playing with the hboot stuff.
Kris
You first need to flash a hboot that can be over written by a RUU. The one you need is Eng 0.98.2000, once you've flashed that you can install the RUU.
I think u need to flash it using adb or fastboot whilst the phone is in bootloader or maybe recovery
Sent from my HTC Desire S using xda premium
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
edit: Issue solved, see page 2.
Also, in case this information helps - I do have a goldcard.img but it doesn't appear to work. My CID is T-Mob005
this guy seems to have been in the same boat as me but he did everything correctly - http://forum.xda-developers.com/showthread.php?t=1378921
if he still has his goldcard.img is there a chance it would work in my phone? I've PM'd him asking if he still has it
FrakEarth said:
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
Click to expand...
Click to collapse
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
tpbklake said:
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
Click to expand...
Click to collapse
Thanks, that's one problem down!
At present I have this RUU Europe Rom that won't load, and the T-MO UK ones still won't install either. I've installed ClockwordMod Recovery 5.0.2.0, so that's good, but I take it I still need a goldcard if I'm going to install a ROM that doesn't match my phone's carrier ID?
Is the reason these older T-Mobile ROMS won't install because of S-ON and the higher radio version number?
edit: by the way, cyanogenmod and similar ROMs appear to install with no errors in clockworkmod recovery but I don't think they are. If I load one of the RUU exes it shows the same 2.10.4 version number with no changes evident whatsoever.
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
gefilus said:
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
I realise that now... I'm less concerned about rooting / getting full S-Off again and more concerned with just getting any working ROM at all onto the phone... as it seems the only ones that are probably going to work are T-Mobile ones, and the only available ROMs I can find are older - I may have to send this off to someone
So you cab get into fastboot?? If you can then use downgrading without HTC Dec unlocked bootloader, there is a post about this, try it should work and use misc_version to let phone thinks he is on older hboot and then use latest T-Mobile ruu. I hope and it should work.
Sent from my HTC Desire S using xda premium
i would do this:
unlock with htcdev.com
downgrade hboot to 0.98.0000
use revolutionary for s-off
change cid to supercid
relock bootloader again
and flash the ruu of youre dreams.
think this should do it
This worked for me in the same situation
http://forum.xda-developers.com/showthread.php?t=1443636
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
FrakEarth said:
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
Click to expand...
Click to collapse
Only if you left on USB dedebuging if it's off then sorry can't. Bet if its o n you can easy make him to boot into fastboot. Take a try, and you need to be installed sdk and adb tools on, PC. Try switch on phone put into USB and open terminal, write adb devices if it works there will show a list and HTXXXXXXXXXX something. If it so then adb reboot - bootloader or if you have custom recovery boot there. If don't anderstand look commands in Wikipedia about adb. Good luck
Sent from my HTC Desire S using xda premium
Okay guys, managed to get this sorted.
Firstly, I read that if you mounted /system from Clockwork mod that ADB commands work... well I didn't get to try that out, because something else worked.
One of the reason RUU updates were failing was because the bootloader was unlocked, when I relocked (fastboot oem lock) they started working again, but I was getting Carrier ID errors on the European RUUs and the T-Mobile ones were too old.
I decided to visit a friend who also has a Desire S and from his phone I was able to get the CID (card identification register) code from a smaller microSD card I have -- this was one I hadn't tried as a goldcard before, and I was unable to try without being able to get at the GoldCard Helper app on my phone... so after using his phone and writing down BOTH CIDs, I tried both and it worked -- I now have the phone updated fully using the European RUU.
I think my mistake the first time may have been copying the wrong CID from Goldcard Helper: if you press Menu > Copy Code it seems to copy the code from MMC1, whereas my SD card was clearly MMC2 -- so my goldcard.img was completely incorrect the first time I tried it. I don't know why the phone let me partially install the European RUU without a goldcard and almost brick the phone, but I suspect it was because I had the Revolutionary bootloader with S-OFF.
So in summary if you have this problem I would suggest borrowing an Android phone (any should work) to get the right goldcard CID needed and then try installing an RUU.
Many thanks to everyone who replied and tried to help me, you guys helped me exhaust every other possibility - and I appreciate it a lot! Thanks!
Hey guys, so I bought a HTC Sensation XE yesterday (2nd hand), and it's my very first time owning this phone so I'm completely new here on this forum section.
Anyway, I want to get it to S-OFF and I tried following many different guides. In the end, I got really confused, and since I don't wanna risk bricking my phone, I thought I'd ask for some help. But first, here's some basic information about my phone:
1. Stock ICS v4.0.3
2. Software number - 3.33.709.152
3. Baseband version - 11.76A.3504.00U_11.24A.3504.31_M
4. HBoot - v1.29.0000
5. HTCdev Unlocked
6. CWM recovery installed and Rooted with SuperSu
Ok, so here's what I did. I followed this guide here, since the topic title says it's for any 1.2x HBoot:
http://forum.xda-developers.com/showthread.php?t=1661631
But since I'm already HTCdev Unlocked, then I have to go to this guide instead (as stated in the instructions):
http://forum.xda-developers.com/showthread.php?t=1614617
BUT, the topic clearly says it's for "HBOOT 1.27.0000 with 3.32 ICS Firmware".
So am I suppose to downgrade my HBoot and firmware then? But then, why would the guide (the first link) say it works for any 1.2x HBoot?
Well, I decided to attempt S-OFF anyway by skipping steps #1, #2 and #3 and jumping straight to step #4. I ran ControlBear, and I get the following error:
Connecting to device...
Searching device.....
Found device.....
Backing up......
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.....
Click to expand...
Click to collapse
I searched on the net and apparently the "Secondary Backup" shows up if you're using a custom rom (which I'm not). Other than that, I can't find any other info on this.
What should I do here?
anyone?
OK nvm I got it working. Apparently, I flashed the Superuser v3.07.zip file after getting my HTCdev unlock (because I needed to root it in order to attempt S-OFF), and somehow forgot I did that and then rooted it again by flashing SuperSu.
Somehow, having 2 superuser installed will cause Juopunutbear S-OFF to fail.
Anyway, I achieved S-OFF now, and at the end of the process it asked me if I want to install a modified (custom) HBoot, so I chose yes.
It said installed successfully, but it still shows I'm using HBoot v1.29.0000 in the boot menu (power off + volume down).
Is this suppose to be correct? I dunno what advantages there are for installing a custom HBoot, and apparently it's suppose to be v1.27, so I dunno if I did it correctly or not. It does say I have S-OFF in the menu so that went successfully, but not sure about my HBoot.......
get the hboot flashed. it gives you added benefit when you face any issues.
the best was to get a patched hboot flashed is by flashing revolutionary hboot (patch from hboot 1.29.0000 to 1.27.1100 i think -at the end of first post) ..from kohr-ah's firmware thread in sensation development section...flash that like a firmware (instructions in the same thread )
To delete one of the su apps go into system apps folder and delete the one you want.
Sent from my KFTT using xda premium
Hi, I have performed the procedure s-off and everything went well:
1) Changed the super and put us
2) procedure executed for s-off
3) In the bootloader unlocked and I have written cid 1111111
The problem is that in s-off rom no I do not work, start arriving at the unlock screen with the screen all black and you only see the top bar.
So if I install from s-on to s-off rom the same rom installed is not work more ... Someone can 'help me, I would put the maximushd but does not work if I have s-off
Thanks
waterseven said:
Hi, I have performed the procedure s-off and everything went well:
1) Changed the super and put us
2) procedure executed for s-off
3) In the bootloader unlocked and I have written cid 1111111
The problem is that in s-off rom no I do not work, start arriving at the unlock screen with the screen all black and you only see the top bar.
So if I install from s-on to s-off rom the same rom installed is not work more ... Someone can 'help me, I would put the maximushd but does not work if I have s-off
Thanks
Click to expand...
Click to collapse
I have found that in s-off I can not mount the sdcard.
Perhaps that is why any rom installed does not work, as it is not able to boot to access the internal memory. Is there any procedure I can 'to unlock the memory in s-off, or do I have to go back to s-on and stay there?:crying::crying::crying:
waterseven said:
I have found that in s-off I can not mount the sdcard.
Perhaps that is why any rom installed does not work, as it is not able to boot to access the internal memory. Is there any procedure I can 'to unlock the memory in s-off, or do I have to go back to s-on and stay there?:crying::crying::crying:
Click to expand...
Click to collapse
this is the exact same problem I faced and a few cases i saw.. the only solution was to go S-On (I used All in one toolkit) there's a simple 1 line command for S-on, and then did RUU to get the phone running.
till date cudnt find a way to do S-off. some have tried Both procedures Moonshine as well as Facepalm but the same kind of bootloop appeared.
If anyone could find a solution kindly do post it here.
Regards.
Sent from my HTC One S using xda app-developers app