Related
Hi to hall.
I bought an HTC Sensation with HBOOT 1.17. I've rooted it with the Official LEAK ROM, Sense 3.5 "2.08.401.1_stock_rooted_signed-v0.3.zip" ad S-OFF it.
Unfortunately I had to follow the procedure of S-ON to send back the phone in technical assistance.
Now I have my phone with display repaired, but the assistance have upgrated my HBOOT in new version 1.19.
These are bootloader informations:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.19.0000
eMMC-boot
Sep 6 2011,19:13:20
If i try the S-OFF with the revolutionary.io site it tell me tath the 1.19 is not supported.
How can i have the permanent root and the S-OFF?
Thank's and merry christmas to everybody.
can't you run RUU to reflash hboot to early version you use it to flash the revolutionary.io hboot back to stock
I'm a newbie, have you a guide or an how-to url?
Tanks
Sent from my HTC Sensation Z710e using XDA App
UP!
Nobody knows a solution to my problem?
You could try to flash back to hboot 1.17, check http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Just place the file (it must be called PG58IMG.zip) on the root folder of your sd-card, triple check md5 and then boot into bootloader to flash it.
If that works use should be able to S-Off.
Edit: Here are the same instructions (it's about firmware flashing but it's the same method, my reference is also mentioned there)
Edit2: I think Madenssblade is talking about flashing back to an earlier STOCK rom, see here, you can try that if the above does not work
Thank's a lot!
A question, if i launch the downgrade, it will destroy all my data?
If you flash the new ROM, yes (but not the data on your sdcard).
If you succeed in flashing the new hboot, no.
Good luck, I don't know if this all works given your device is S-ON, but it's worth a try (your HBOOT says unlocked).
A small update.
Yesterday i installed the app 4EXT Recovery Control and i noticed with surprise that i still root; perhaps it was sleeping in the state.
I cannot yet find a guide to give the S-OFF at HBOOT 1.19 .
ziopippo said:
I'm a newbie, have you a guide or an how-to url?
Tanks
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Hi, try to downgrade your firmware. I am not sure but it may work. Try the following.
A. Downgrading the firmware
Visit this thread. Download v1.17 firmware . Are u having superCID? If so then you can download any v1.17 firmware else choose that firmware file which includes your CID. If you are not sure about your CID follow that same thread to find it.
Flash the firmware by the following method.
1. place Firmware PG58IMG.zip (v1.17) on the root of your sdcard.
2. Remove the battery.
3. Wait a minute.
4. Put the battery.
5.Press power+ volume- key together.
6.Phone will boot into bootloader.
7.Follow the instruction on your phone screen.
If the firmware downgrade successfull then Perform Revolutionary method to make your device S-OFF. If this method does not work try flashing an RUU.
B. Flashing an older RUU (HBOOT 1.17 )
Find a suitable RUU from here.
If RUU Flashing fails, boot into bootloader. Then retry to flash the RUU.
Then try to follow Revolutionary method.
musarraf172 said:
Hi, try to downgrade your firmware. I am not sure but it may work. Try the following.
A. Downgrading the firmware
Visit this thread. Download v1.17 firmware . Are u having superCID? If so then you can download any v1.17 firmware else choose that firmware file which includes your CID. If you are not sure about your CID follow that same thread to find it.
Flash the firmware by the following method.
1. place Firmware PG58IMG.zip (v1.17) on the root of your sdcard.
2. Remove the battery.
3. Wait a minute.
4. Put the battery.
5.Press power+ volume- key together.
6.Phone will boot into bootloader.
7.Follow the instruction on your phone screen.
If the firmware downgrade successfull then Perform Revolutionary method to make your device S-OFF. If this method does not work try flashing an RUU.
B. Flashing an older RUU (HBOOT 1.17 )
Find a suitable RUU from here.
If RUU Flashing fails, boot into bootloader. Then retry to flash the RUU.
Then try to follow Revolutionary method.
Click to expand...
Click to collapse
I have tried this process several times but my HTC says "Parsing PG58IMG.zip"
could this be because i am S-ON? i am trying to downgrade from 1.23
slimldj said:
I have tried this process several times but my HTC says "Parsing PG58IMG.zip"
could this be because i am S-ON? i am trying to downgrade from 1.23
Click to expand...
Click to collapse
Did you try Flashing an RUU?
Sent from my HTC Sensation using Tapatalk
musarraf172 said:
Did you try Flashing an RUU?
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
yes. but when i try to, the phone enters the "black htc screen" and after a couple of minutes i get error 155 from the RUU saying i should get the corrent ROM Update utility.
i dont know whats wrong
Also i have tried to get the rom.zip from the temp folder of my computer sourced from the RUU. changed the name to P......zip so that bootloader can flash. it just ends up saying "parsing P........zip"
slimldj said:
yes. but when i try to, the phone enters the "black htc screen" and after a couple of minutes i get error 155 from the RUU saying i should get the corrent ROM Update utility.
i dont know whats wrong
Also i have tried to get the rom.zip from the temp folder of my computer sourced from the RUU. changed the name to P......zip so that bootloader can flash. it just ends up saying "parsing P........zip"
Click to expand...
Click to collapse
As I said earlier , be in bootloader mode first. Then flash RUU. Error 155 should go off.
musarraf172 said:
As I said earlier , be in bootloader mode first. Then flash RUU. Error 155 should go off.
Click to expand...
Click to collapse
tried that as well.. as soon as the RUU says sending, i see the error again... 155
slimldj said:
tried that as well.. as soon as the RUU says sending, i see the error again... 155
Click to expand...
Click to collapse
Hope surely the following posts will help you.
http://forum.xda-developers.com/showthread.php?t=1469296
http://forum.xda-developers.com/showthread.php?t=1478828
musarraf172 said:
Hope surely the following posts will help you.
http://forum.xda-developers.com/showthread.php?t=1469296
http://forum.xda-developers.com/showthread.php?t=1478828
Click to expand...
Click to collapse
hello excuse the disorder but having the same problem on and hboot 1.19 s-on can not flash a stock ruu wanted to ask if you found a way to put s-off.
Hi everyone! (sry for my bad english)
so I bought a new HTC sensation like a week ago.
it's comes with android 2.3.4 and sense 3.0.
I wanted to install ICS 4 a stock rom.
I tried everything: to get root, s-OFF, unlock bootloader (HTCdev and revolutionary), change CID and super cid.
none of them succed to me (I think only the HTCdev succed but i'm not sure).
I did so many guide and tried them like 50 times, I reached a dead end.
So I decided to ask for help, What's the first thing I should do, I wish you would help me step by step.
tnx.
What's your HBOOT version mate?
First of all you should S-OFF your device using the revolutionary utility..Other things can be done without much difficulty..Are you having trouble with S-OFF?
my h-boot is 1.18.0000
I tried to get S-OFF but i got this error: failed to get root!
roi258 said:
my h-boot is 1.18.0000
I tried to get S-OFF but i got this error: failed to get root!
Click to expand...
Click to collapse
Use this guide to soff... You will be successful if you follow this guide
http://forum.xda-developers.com/showthread.php?t=1541087
sent from my blazing fast pyramid through sonic waves
OMG is now restart loop
please help me guys, after doing what you told me its in restart loop.
my h-boot change to 1.17.1111 and its become s-off.
what can i do?
roi258 said:
please help me guys, after doing what you told me its in restart loop.
my h-boot change to 1.17.1111 and its become s-off.
what can i do?
Click to expand...
Click to collapse
NOW you are SOFF ...awesome the hard part is over
well what do you want to install now ICS stock rom or amazing custom ICS rom?
tell me asap...I'll guide you further
I want stock one, I download this rom and he is on my sd card:
http://forum.xda-developers.com/showthread.php?t=1529941
roi258 said:
I want stock one, I download this rom and he is on my sd card:
http://forum.xda-developers.com/showthread.php?t=1529941
Click to expand...
Click to collapse
good you just need 3.32 firware for that
first go to fastboot on you device and get cid of your device
"fastboot getvar cid"
better do super cid ...then you can install any RUU
to do supercid
"fastboot oem writecid 11111111" (eight ones)
if you are supercid get any 3.32 firmware from this thread
or get the 3.32 firmware corresponding to your cid
this is the thread
supercid ...get 3.32 from here
based on your cid ....get 3.32 from here
to install firmware follow step 4 and 5 from this thread
also for flashing the rom...you require custom recovery ....so did you got one ?
if you didn't then get this
4EXT touch recovery
keep this in your adb folder
and flash it via fastboot
"fastboot flash recovery recovery.img"
then the rom.zip you got need to be installed from the recovery
if you are still having doubts...click on the IRC HELP CHANNEL present in my signature...and join the IRC .. I'll be there to help you via real time chat
tnx you very much I now have android 4.0.3 with sense 3.6 because of you!!!!
roi258 said:
tnx you very much I now have android 4.0.3 with sense 3.6 because of you!!!!
Click to expand...
Click to collapse
Glad you got ics now .... But there is a way to say thnx in xda
Hello Everyone,
I need to send my Sensation in for dust removal. I was running CM9, changed my CID back to BM___01 or something for bell mobility, where the phone came from. I then did the
Code:
fastboot oem writesecureflag 3
and got a brick. I unbricked successfully with the unbricking project. Kudos to the devs of that.
I now have a problem. My CID is for bell, so can't flash anything else, error in the ruu.
My hboot is 1.27 and my radio 11.22.3504.07_M, so I can't flash any of the bell ruu because of error 140 wrong bootloader. The only RUUs for bell are gingerbread with really old hboot.
I think I need to s-off and change CID to get a newer ICS RUU on here.
3 questions:
1. can I s-off without any firmware (no recovery, no rom) on the device, so no adb
2. Is there any other way to get a booting rom on here?
3. can I revert back to the gingerbread RUU using some sort of hboot downgrade, once I have something installed? (rom)
Thanks for your help.
jcarrz1
jcarrz1 said:
Hello Everyone,
I need to send my Sensation in for dust removal. I was running CM9, changed my CID back to BM___01 or something for bell mobility, where the phone came from. I then did the
Code:
fastboot oem writesecureflag 3
and got a brick. I unbricked successfully with the unbricking project. Kudos to the devs of that.
I now have a problem. My CID is for bell, so can't flash anything else, error in the ruu.
My hboot is 1.27 and my radio 11.22.3504.07_M, so I can't flash any of the bell ruu because of error 140 wrong bootloader. The only RUUs for bell are gingerbread with really old hboot.
I think I need to s-off and change CID to get a newer ICS RUU on here.
3 questions:
1. can I s-off without any firmware (no recovery, no rom) on the device, so no adb
2. Is there any other way to get a booting rom on here?
3. can I revert back to the gingerbread RUU using some sort of hboot downgrade, once I have something installed? (rom)
Thanks for your help.
jcarrz1
Click to expand...
Click to collapse
Hmm that's a rough situation you are in.. If you can't find the ruu that would be a problem..
First try contacting football.. For ics ruu of bell.. (football provides most of the ruu's.. He is the OP of pyramid shipped rom collections thread present in sensation development section)
Try changing Cid to a well know one
Like this.. What you do is
First reboot to bootloader
fastboot oem writecid HTC__001 (supercid won't work.. So stick with this for now)
Then remove battery..
Then reinsert it. Power on to bootloader
And check Cid
fastboot getvar cid
If this worked.. Great. Find a Europe ruu and flash it
Last .. Try htc-dev unlock.. If luckily you..got unlocked bootloader..
Flash custom rom..Then SOFF..Then change back Cid..Then flash the old ruu of your Cid..Then SON
To get a working rom
Sent from my pyramid.. Through blazing fast sonic waves
For future reference; S-ON is the last thing you do when sending the phone back. RUU needs to happen before that.
The situation you're in, you're going to have to HTC Dev unlock your bootloader, and fastboot flash system and boot, possibly install a firmware PG58IMG as well... hopefully that will be enough to get the phone booting. Then you'll want to S-OFF and flash the RUU (this will also set you back to ***LOCKED***), then you can S-ON.
You guys are so helpful. I will try this.
My utmost thanks,
jcarrz1
Is HTC dev unlock reversible, and does it void my warranty even if I reverse it? does it leave any trace/can they tell?
Getting S-OFF removes all trace of it.
Rusty! said:
Getting S-OFF removes all trace of it.
Click to expand...
Click to collapse
And then getting S-ON again will be like stock configuration?
No, going S-OFF changes ***UNLOCKED*** back to ***LOCKED***
jcarrz1 said:
And then getting S-ON again will be like stock configuration?
Click to expand...
Click to collapse
yep...
if you use juopunutbear soff after HTC-dev unlock ..you will get locked/juopunutbear bootloader (instead of relocked )
then RUU (to make everything stock..and to prevent wrong SON brick) and SON again ..will be complete stock
Again, I am amazed by your helpfulness.
Thanks guys! you run the general section
jcarrz1
I can't flash firmware because it says "parsing package" and then does nothing
I can't push a system.img because it says "too large"
I've tried ARHD, CM9, and stock zippified roms, and none of them boot. Probably firmware issue, but see first problem...
any tips?
jcarrz1 said:
I can't flash firmware because it says "parsing package" and then does nothing
I can't push a system.img because it says "too large"
I've tried ARHD, CM9, and stock zippified roms, and none of them boot. Probably firmware issue, but see first problem...
any tips?
Click to expand...
Click to collapse
ohk for firmware flash you can use this
copy the firmware zip (PG58IMG.zip) to the adb/fastboot folder
open command prompt from adb/fastboot
then these commands one by one
fastboot erase cache
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed while flashing in the middle ..be careful)
fastboot reboot-bootloader
that would flash the firmware
Hi guys,
I've got some ****y problem. So I was on Jelly Bean rom with revolutionary S-Off but wanted to have feature full phone and thought ok go back to stock (bad idea...)
So I followed a tutorial flashed Eng Hboot and wanted to restore with an O2 Gingerbread RUU. Everything worked fine until I got Error 140 (Bootloader failure)...Now I'm S-On but I don't have any rom on my phone so I'm stuck in recovery.
S-On
Hboot 0.98.0000
Radio 38.03.02.14_M
In my opinion I have to get a goldcard to flash a ruu on top of all that **** ^^ Buuut I can't boot so no ADB, hence I can't get my CID. Tried some tools to get CID via card reader but It didn't work for me.
Any Help, Suggestions? Help me to fix my android and avoid to buy an Iphone ^^
Cheers
main version check fail...that stopped the RUU
Have a go at fastboot, if that doesn't work it will need to be sent off to the repair center to be reprogrammed by JTAG experts.
Sent from my Nexus One using xda app-developers app
I can enter fastboot and do commands that's not the problem. Sadly my hboot seems to be too low for htcdev unlock -.- ...And I don't know of any method to get ADB working in bootloader, fastboot, ...
Can you get into recovery from fastboot? If so, you can run ADB from there.
Sent from my Desire S
Why not trying to flash the ruu that suits your carrier,
Besides, it's best not to use eng-hboot in order to get back to s-on, imho,it's best to upgrade hboot to revolutionary 7.x after using revolutionary s-off, it's compatible with most 2.3.5ruus and custom roms.
I can get into recovery but it is stock recovery...and adb doesn't recognize my device while i'm in there ...
The ruu suits my carrier, as I said the signature check was true but the version check failed...i would need a newer o2 ruu but that doesn't exist
help me pls^^
Can you flash a custom recovery, such as 4EXT or CWM, using a PG88IMG zip file on your sdcard?
Sent from my Desire S
Hey Bill thx for your help! I used an old phone wich could get into CWM Got CID of SD Card and did the Gold Card method! Flashing Ruu PG88IMG right now
btw. This can be closed
Wody05 said:
btw. This can be closed
Click to expand...
Click to collapse
Just add [Solved] at the front of the title on the original post (OP).
Sent from my Desire S
WARNING*WARNING*WARNING
do this at your own risk! This is for s4 only!!
It has been brought to my attention that there might be a mid (model id) conflict
With flashing this and me along with others are trying to narrow down the issue. Thanks to @real187 for bring this to my attention.
I'm
S-off
Cid 11111111
MID PJ4011000
And had no problems flashing this firmware but others with same setup have reported soft brick.
OK I think @mkinney88 may have pin pointed where the soft brick may be coming from. If you s-off using facepalm, flash the firmware.zip and get soft bricked try this.
1. Get back to s-on (warning read directions several times before doing you CAN hard brick your phone) ~ http://forum.xda-developers.com/showthread.php?p=38267667
2. Get s-off with moonshine ~ http://forum.xda-developers.com/showthread.php?p=42613403
First off this is mostly ment for the T-Mobile branded phones but ill try and help all please let me know when asking questions if you have a T-Mobile or HTC branded phone (it has it right on the front of phone ).
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111 (I had no problem flashing firmware with s-off and Cid 11111111 but others have reported problems so if you don't want to chance it write your Cid to T-MOB010)
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Downloads
FIRMWARE ZIP DOWNLOAD
https://drive.google.com/folderview?id=0B-BYnLh2sosKamRwaUJJS05oU3M&usp=sharing or http://db.tt/Wua8mDS2
Credit go's to mkinney88 for the firmware
Bricks
First off if you can get into bootloader then you don't have a hard brick.
If your phone is in the black screen of death there may be hope but we're still trying to figure that one out.
If your phone doesn't respond to any input from you (power, power+volume down) then congratulations you have a hard brick but don't through it in the junk drawer just yet, you can have it jtag repaired (they open phone plug into main board and flash everything)
Here's the link (you do have to pay for this)
http://forum.xda-developers.com/showthread.php?p=37136553
One more just in case
rc420head said:
I'm starting this thread to have a place for noobs and long time users to ask and answer questions. This is going to be as noob friendly as possible but please keep questions firmware related only. So lets get started.
i really dont know how to make it any clearer then @mkinney88 did in his rom OP. all credit goes to him these institutions.
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/show....php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/show...1#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/show....php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/vil....3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery,
now youve followed that and now your stuck ether getting errors or phone is now acting all erratic? that's why you're here. go ahead ask any question you want about firmware noobish,dumb,anything as long as its firmware related. (sorry i cant tell you how to get the cute girl at the mall)
this is just a crude start ill add and refine as we get going.
please do don't ask firmware questions in development threads ask here.
If you want to see mkinney88's full guide go here paste bin
Click to expand...
Click to collapse
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
vatsaman said:
Don't flash the firmware on SuperCID which leads to brick, which can be recovered though
Click to expand...
Click to collapse
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
I put a note of this in op just now, thanks for the warning, I'm trying to figure out why some can do this Cid 11111111 and some can't.
-----------------------------------------
Friends don't let friends post without searching first!
rc420head said:
Bricks can't be recovered (unless you jtag) , you had a soft brick.
I had no problem doing this with s-off and Cid 11111111.
But I remember you from other threads and I have a few questions.
1. Is your phone t-mobile branded or htc? 2. When you first did the firmware update what was your hboot version?
-----------------------------------------
Friends don't let friends post without searching first!
Click to expand...
Click to collapse
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
Something else is going on. I used facepalm, and Cid 11111111 to flash firmware twice now with no issues and started same as you hboot 1.14
-----------------------------------------
Friends don't let friends post without searching first!
thank you!
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
khan.orak said:
I'm on Stock JB 4.1.1 and my CID is BM___001, rooted, unlocked BL.
There is no RUU for this CID and only a JB OTA, The radio version and software version match with those of the phone.
my question is: Without S-OFF and SuperCID, Can I use the OTA.zip to be flashed for getting stock ROM? e.g if I am on CM 10.1 and I want to revert back to stock, can I use the OTA.zip?
Click to expand...
Click to collapse
I'm not sure if I understand your question. So let me ask a few questions.
What hboot are you on?
What carrier are you using?
Are you wanting to try cm 10.1 and afraid for losing stock?
What is stock just HTC sense 4+ or is there carrier added stuff?
rc420head said:
I'm not sure if I understand your question. So let me ask a few questions.
Click to expand...
Click to collapse
ok I'll try to make it clearer.
What hboot are you on?
Click to expand...
Click to collapse
I'm on hboot 2.15.0000
What carrier are you using?
Click to expand...
Click to collapse
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Are you wanting to try cm 10.1 and afraid for losing stock?
Click to expand...
Click to collapse
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
What is stock just HTC sense 4+ or is there carrier added stuff?
Click to expand...
Click to collapse
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
khan.orak said:
ok I'll try to make it clearer.
I'm on hboot 2.15.0000
This phone is from Bell Mobility Canada, but I'm not using this carrier.
Exactly!! this is what I was asking. There isn't any RUU for stock JB 4.1.1, for the CID BM____001.
Stock sense is 4+ and is heavily bloated. It has got apps like DropBox, Let's Play Golf, Friend Stream, HTC Media Link HD, Polaris Office etc.
Click to expand...
Click to collapse
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
rc420head said:
OK since your on hboot 2.15 there's no need to upgrade firmware.
Since there is no RUU for stock the next best thing would to to make a back-up of stock using a custom recovery I would recommend twrp 2.3.3 (if you need help with this just ask that's what this thread is for)
Then I would copy the back up to your pc for safe keeping (you might even want to back it up on a cloud too I'd recommend goggle drive or Dropbox)
Click to expand...
Click to collapse
Thanks for the reply, really much appreciated.
I already have rooted the device and custom recovery TWRP 2.5. Though I am considering to downgrade it to 2.3.30. Now I made a backup of stock ROM. (System + Boot Partition)
So is this the only way I can get to stock?
I read somewhere that the following method could be used too(?)
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
khan.orak said:
S-OFF ---> Run an older RUU for Bell Mobility (probably ICS RUU) ---> Then update OTA.
Is this valid?
Click to expand...
Click to collapse
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Big thanks! :good:
vatsaman said:
Yeah mine was a softbrick. If you stroll over, u can find many people in my queue. May be it is happening only for people who got S-OFF with the Facepalm way. I was on Hboot 1.14 and so a T Mob branded one.
Also you will see a warning in Facepalm thread that flashing firmware on SuperCID phones likey causes a brick.
Click to expand...
Click to collapse
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
ardax said:
Yes, if an older RUU is available for your CID just get S-OFF first then use it. Then you'll be able to update via OTA.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes this will also work (I was under the impression no ruu's were available)
khan.orak said:
Big thanks! :good:
Click to expand...
Click to collapse
forgiven90 said:
This is very interesting to me because I have a unbranded one s from a small spinoff of T-mo in Iowa. I got s-off with facepalm and SuperCID at the same time, then on hboot 1.13. Now recently I upgraded hboot to 2.15 with a euro RUU, soft bricked but was able to recover with only a firmware flash. (details are a bit fuzzy right now) I didn't relock the bootloader, but did install stock recovery. Ever after this stunt I've had tons of problems with radio disconnects. I first thought my problem was hardware, but I just got it back from a very good repair shop and the same thing. Although better on a different carrier, I suspect only because the better carrier has stronger signal. I'm ready to try a older RUU or euro firmware or just about anything, this phone only has service 10% of the time where it used to be 100% right now I'm running the latest Trickdroid 10.3.2 Changing the fast.dormancy=2 helped a tiny bit but it's something more fundamental than that I'm thinking... Sugg anyone??
Prolly should add I'm using the euro 1.15 radio. Thanks
Edit, looks like maybe my problems may only be build prop related, if I change to.til.radio.svn=19 to 5 I get an instant connection, but only G...
ro.ril.hsdpa.category=28
ro.ril.hsupa.category=7
ro.ril.fast.dormancy.rule=0
ro.ril.radio.svn=5
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah disabling the fast dormancy solved all my problems. :good: