I was trying to do this:
STEP 5 - CHANGING BACK TO S-ON - PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A RISK OF BRICKING READ BEFORE GOING TO STEP 1.
YOU MUST Follow this correctly otherwise you could semi-brick your device (Semi bricks recovery by re-flashing RUU). If you follow it correctly YOU WILL GET S-ON SUCCESSFULLY -confirmed by other users
I cannot be held responsible if anything goes wrong but i will help in every situation. 2 unrecoverable bricks so far. 1 due to not flashing RUU
First time i did this with a custom ROM installed - semi-bricked my device (couldn't boot due to security warning as S-on doesn't work with custom roms), restored it using RUU.exe
Second time after S-off i took the following steps and successfully went back to S-ON without any problems and booted up into stock rom.
Confirmed to work by several others as well as myself
1. Follow Step 4 above to get SuperCID - Skip if you already have it
2. Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
So if you are already on a stock ROM or you just went back to stock ROM, i don't care, restore the stock ROM again using the RUU.exe if you don't want to be bricked!
Connect to your phone in charging mode. click the "RUU_pyramid_*****.exe" file you downloaded and follow on screen instructions.
3. Make sure when you download the RUU. download the same or similiar RUU version as your phone came with (e.g. Tmous or EU or Asian etc). As long as you install a stock rom similiar to what you had you should be ok. FAILURE TO DO THIS MAY BRICK YOUR PHONE.
4. Switch your phone on now and let it boot for the first time and just skip through the welcome screen.
5. Go back to Step 4 - SUPERCID and go through 1 to 7 to get to the fastboot bootloader. (so just do what you did before, put adb files in local disk, adb reboot bootloader etc)
6. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja)
7. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
8. Bootloader should now read Pyramid PVT Ship S-ON RL.
9. Remove and reinsert the battery. Press power on as normal
I think I read it at least 5 times before I went ahead. And SOMEHOW I did managed to overlook step 2 (I even downloaded the RUU - just didn't run it).
And now the phone is dead as a doornail
Is there ANYTHING I can try/do?
I'm on stock ROM.
EDIT: I sent it back to the shop.
EDIT:
Just got the phone back today
They have replaced the "main board". So the phone got a new IMEI...
So my phone is up and kicking again
Asmund said:
I was trying to do this:
STEP 5 - CHANGING BACK TO S-ON - PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A RISK OF BRICKING READ BEFORE GOING TO STEP 1.
YOU MUST Follow this correctly otherwise you could semi-brick your device (Semi bricks recovery by re-flashing RUU). If you follow it correctly YOU WILL GET S-ON SUCCESSFULLY -confirmed by other users
I cannot be held responsible if anything goes wrong but i will help in every situation. 2 unrecoverable bricks so far. 1 due to not flashing RUU
First time i did this with a custom ROM installed - semi-bricked my device (couldn't boot due to security warning as S-on doesn't work with custom roms), restored it using RUU.exe
Second time after S-off i took the following steps and successfully went back to S-ON without any problems and booted up into stock rom.
Confirmed to work by several others as well as myself
1. Follow Step 4 above to get SuperCID - Skip if you already have it
2. Restore your official stock Rom: Just click here to download an Official Rom RESTORE STOCK EVEN IF YOU JUST RESTORED IT RECENTLY OR ARE ALREADY ON STOCK ROM. This is to ensure nothing gets changed in stock for S-on to be successful
So if you are already on a stock ROM or you just went back to stock ROM, i don't care, restore the stock ROM again using the RUU.exe if you don't want to be bricked!
Connect to your phone in charging mode. click the "RUU_pyramid_*****.exe" file you downloaded and follow on screen instructions.
3. Make sure when you download the RUU. download the same or similiar RUU version as your phone came with (e.g. Tmous or EU or Asian etc). As long as you install a stock rom similiar to what you had you should be ok. FAILURE TO DO THIS MAY BRICK YOUR PHONE.
4. Switch your phone on now and let it boot for the first time and just skip through the welcome screen.
5. Go back to Step 4 - SUPERCID and go through 1 to 7 to get to the fastboot bootloader. (so just do what you did before, put adb files in local disk, adb reboot bootloader etc)
6. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja)
7. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
8. Bootloader should now read Pyramid PVT Ship S-ON RL.
9. Remove and reinsert the battery. Press power on as normal
I think I read it at least 5 times before I went ahead. And SOMEHOW I did managed to overlook step 2 (I even downloaded the RUU - just didn't run it).
And now the phone is dead as a doornail
Is there ANYTHING I can try/do?
I'm on stock ROM.
Click to expand...
Click to collapse
So you went s off, stayed stock, then tried to s on? No other changes? how far did you get , the write secure flag? And how dead, like no power at all, or boot loop, frozen splash screen?
bobbymokie said:
So you went s off, stayed stock, then tried to s on? No other changes? how far did you get , the write secure flag? And how dead, like no power at all, or boot loop, frozen splash screen?
Click to expand...
Click to collapse
Yes, I only rooted it (successfully).
And now I had some problems with the battery cover and wanted to sent it back for a replacement or at least fix it.
So I would unroot it before I brought back to the store.....
I think its dead as can be. There is like no power. Nothing happens when I press the power button - even if I take the battery out and put it back in.
I did everything from 1 to 9 (except step 2)
Asmund said:
Yes, I only rooted it (successfully).
And now I had some problems with the battery cover and wanted to sent it back for a replacement or at least fix it.
So I would unroot it before I brought back to the store.....
I think its dead as can be. There is like no power. Nothing happens when I press the power button - even if I take the battery out and put it back in.
I did everything from 1 to 9 (except step 2)
Click to expand...
Click to collapse
does the led light up when plugged in to the charger? Also, who is the carrier?
bobbymokie said:
does the led light up when plugged in to the charger? Also, who is the carrier?
Click to expand...
Click to collapse
No, unfortunately nothing from the led. The phone is unbranded and unlocked (I'm from Europe, its quite normal to buy a "carrier-free phone here).
Asmund said:
No, unfortunately nothing from the led. The phone is unbranded and unlocked (I'm from Europe, its quite normal to buy a "carrier-free phone here).
Click to expand...
Click to collapse
Bummer. not aware of a way to help. Had hoped it was carrier purchased, as they'd probably exchange it for you. Sorry : (
bobbymokie said:
Bummer. not aware of a way to help. Had hoped it was carrier purchased, as they'd probably exchange it for you. Sorry : (
Click to expand...
Click to collapse
Yes, indeed. I can only blame myself
Thanks for trying to help me out.
Maybe some other guys know something. Or maybe I'm just screwed
How likely is it they I will get a replacement if I take it back to the store?
I mean can they read the phone status somehow, and that way see that I
I messed it up?
Asmund said:
Yes, indeed. I can only blame myself
Thanks for trying to help me out.
Maybe some other guys know something. Or maybe I'm just screwed
How likely is it they I will get a replacement if I take it back to the store?
I mean can they read the phone status somehow, and that way see that I
I messed it up?
Click to expand...
Click to collapse
well if its completely dead they can't read anything from it. Adb won't even find it. But that's not exactly honest (not saying I wouldn't try) to return it as defective
As bobbymokie said, chances are, if you go to a local carrier store, they will exchange it for you once they realize there is no physical or water damage to the phone but it still won't turn on.
While this isn't the most honest way to handle it, I can't say I have not done this successfully in the past.
I'll take a shot at it.....
let us know how it goes
dinhhviet said:
let us know how it goes
Click to expand...
Click to collapse
Just got the phone back today
They have replaced the "main board". So the phone got a new IMEI...
So my phone is up and kicking again
just send it and say it just died on its own
shut my mouth please, hehehe
Nice to know you got a new device
jigners said:
just send it and say it just died on its own
Click to expand...
Click to collapse
Did you real my last post? Just got it back today
Its quite likely you get a replacement, just told them that it suddenly stopped working, if its dead as you say they should get you a new one
Related
i downgraded but could not get root. how do i and what method do i use to make it completely stock.
TO RETURN TO STOCK:
Make sure you S-ON (if able) BEFORE you Unroot. The S-On tool needs root permissions to function.
Step 1 (S-On):
Run Bubby323's S-On tool: S-On Tool
Step 2 (Unroot/Return Stock ROM):
Flash the stock AT&T ROM: RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed.exe
That's the original factory shipped rom, not rooted. =]
That will return everything back to the way it was when you bought it.
And just to be clear, you actually run the EXE file on your windows computer, with your phone connected via USB. Don't do anything crazy like try to put it on the SD card or something, because that won't work.
Edit: If you are still S-Off after running the tool, and need to S-On, read post 27 of this thread BEFORE you unroot with the stock ROM.
Ive been thinking of doing the same thing. I have s-off. Is there anyway to have root on the stock rom?
Not as of yet. The only way it's accomplished so far is with the downgrade. There are developers working on a way for that to be accomplished soon though, I'm sure.
Would there be any way to tell there is s-off for warranty purposes? Can that be turned off?
ClearD said:
From what I understand, flash this:
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
That's the original factory shipped rom, not rooted. =]
That will return everything back to the way it was when you bought it. The only thing it will not fix is S-Off, which it doesn't look like you've done yet anyways.
And just to be clear, you actually run the EXE file on your windows computer, with your phone connected via USB. Don't do anything crazy like try to put it on the SD card or something, because that won't work.
Click to expand...
Click to collapse
It's just the equivalent to an odin for captivated.
Sent from my Desire HD using XDA App
Apparently there is a way to root the stock rom. See this thread: http://forum.xda-developers.com/showthread.php?t=957901
budco2000 said:
i downgraded but could not get root. how do i and what method do i use to make it completely stock.
Click to expand...
Click to collapse
Budco, if you downgraded, you can get root - the hard part is done. Come back to the IRC channel and be patient. When you were there there was a ton of activity.
I'm trying to return to stock after the "stock with root" rom, due to my wifi not working. I despite having a fully charged batter, the ruu errors saying that my batter is less than 30%.
any suggestions?
rdgoeson4ever said:
I'm trying to return to stock after the "stock with root" rom, due to my wifi not working. I despite having a fully charged batter, the ruu errors saying that my batter is less than 30%.
any suggestions?
Click to expand...
Click to collapse
Use CWM to wipe battery stats. That may help.
don't you have to reverse S-OFF to S-ON in order to flash a stock ROM?
harlenm said:
Would there be any way to tell there is s-off for warranty purposes? Can that be turned off?
Click to expand...
Click to collapse
You can tell by reading your HBOOT (bootloader) screen. It will say "S-Off".
You're supposed to be able to get into this menu by holding volume down while pressing the power button to boot, however I haven't gotten it to work yet.
The hack tool uses "gfree", the T-Mobile G2 program for turning S-Off, which should have a method for turning S-On as well. I'll try to dig it up later, but check the Desire HD forum area for turning S-On. I believe they have made a program to do it.
Edit: To get to that menu, hold volume down while using the "Reset" option in the shut down menu.
ClearD said:
You're supposed to be able to get into this menu by holding volume down while pressing the power button to boot, however I haven't gotten it to work yet.
Click to expand...
Click to collapse
Same here. I can only get in from restart. The phone vibrates a couple of times then boots right into recovery.
I keep getting error 170. Has anyone else seen this and what is the solution? I rebooted the phone and PC (W7 x64) but am still getting the same error.
What are you doing when you receive this error? What exactly is throwing the error?
lrs421 said:
Same here. I can only get in from restart. The phone vibrates a couple of times then boots right into recovery.
Click to expand...
Click to collapse
And thank you!! I've been trying to figure that one out! ;]
I kept getting error 130 battery to low but my battery was at 65%. Says you need minimum 30%
sgaar said:
I keep getting error 170. Has anyone else seen this and what is the solution? I rebooted the phone and PC (W7 x64) but am still getting the same error.
Click to expand...
Click to collapse
Error 170 means that the RUU program cannot find the phone. Make sure you have installed HTC Sync on your PC. It installs some drivers that the RUU needs to find the phone via the USB cable.
returning to stock?
Can someone instruct me on how to return my Inspire back to stock? I tried rooting using attn1 instructions and also the youtube videos. It got to the downgrade part but once it rebooted, I can't get the device recognized like when I type in hackerize-ace clean in the command prompt. It won't work so I'd like to fix it. Any and all help will be greatly appreciated. I feel like I've bricked my phone and I'm sick about it. Thank you.
if you want to finish rooting, make sure USB debugging is on. I'm pretty sure when i rebooted from downgrading, since it was a fresh install, it was set to off, and that sounds like the culprit with the device not being recognized.
**VIDEO AT THE BOTTOM!!**
Requirements
ADB: Click here for windows or Linux or download from) Sensation S-off guide
You Will Need HTC Drivers http://forum.xda-developers.com/atta...7&d=1312092669
*DO NOT ADD "" TO COMMANDS!!!
1. On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
2. Create a new folder called "adb" and extract the files from adb.zip (link above) into it. Make sure it doesn't create another folder in the adb folder when extracting
3. Install HTC USB Driver 3.0.0.007.
4. Press Windows + R, it will open Run. (linux users ignore this)
5. Type "cmd". (or open terminal on linux)
6. Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode
7. On your phone, Go to Settings > Applications > Development > Enable USB Debugging
8. enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
9. If it is recognized, then download your official RUU, please get the same/similar version that came with your phone. If you fail then you might Brick your Device!
10. Start RUU.exe and follow on screen commands.
11. After reboot, turn phone off without fastboot on, or, take out battery and then Hold Volume down button and power on.
12. Bootloader should now read Pyramid PVT Ship S-OFF RL.
13. Remove and reinsert the battery. Press power on as normal
Optional To change to stock S-ON
PROCEED WITH CAUTION. ONLY DO THIS IF YOU ABSOLUTELY HAVE TO. BEWARE THERE IS A SMALL RISK OF BRICKING
15. Boot up into the new ROM and On your phone, Follow steps 4-8 above then continue here
16. enter the command "fastboot oem writesecureflag 3" (Thanks Dazweeja who came up with this)
17. Reboot into bootloader using "fastboot reboot-bootloader" or remove & reinsert the battery and press power on while keeping hold of volume down.
18. Bootloader should now read Pyramid PVT Ship S-ON RL.
19. Remove and reinsert the battery. Press power on as normal
USE IF SEMI BRICKED
20. IF IT DOESN'T REBOOT and bootloader says ***Security Warning**
Remove and re-insert the battery and go back into bootloader and holding Volume Down +power button select fastboot
21. Run RUU.exe to reflash stock rom. (the one u just downloaded in step 1) and then reboot. It should work now
*NOTE*
This removes ROOT and custom recovery!!
I take No Credit for the Idea!
I am in no way responsible if YOU brick your phone!
If you want to add stock SuperCID AFTER you installed RUU.exe, Then Go Here For CID's, They Must Be Your Mobile Carriers... Ex: T-Mobile USA = (Carrier"TMUS") (CID"T-MOB010")
CID CANNOT BE CHANGED AFTER S-ON, it must be done while S-off
I added a video to download! you may need to re-record
http://www.mediafire.com/?ibn7168nd2ywr5d
Good Day to You and Good Luck!
Feel free to Comment for Help
If you need any help feel free to post comments
well thanks for this guide, but we're all hoping to never send our beloved Sensation in warranty return
Yeah, I would hate to send it in.
Read Me!
Everyone should do this and then reinstall custom recovery and root. Only because if sent to warranty and they see Revolution, you are screwed.
plocri said:
well thanks for this guide, but we're all hoping to never send our beloved Sensation in warranty return
Click to expand...
Click to collapse
Nice write up and VERY Noob friendly! I was reading through and in my head, half the time, going well duh. Then it clicked, you said Noob friendly. I think it will help almost all Noobs but there will be at least ONE that F's it up!
Again, nice write up!
setzer715 said:
Nice write up and VERY Noob friendly! I was reading through and in my head, half the time, going well duh. Then it clicked, you said Noob friendly. I think it will help almost all Noobs but there will be at least ONE that F's it up!
Again, nice write up!
Click to expand...
Click to collapse
Thanks, Its funny cause im a junior member and im writing NOOB friendly threads
Well was a junior member when i wrote this lol
Just to let you know if you stay with S-OFF HTC will now...
Hboot is a different version from HTC, it ends in 10xx rather than 00xx
So even if it doesnt say revolution, they still can tell
Best to restore to S-ON which is a bit risky if you dont follow instructions to the t..
Cheers
P.S. Also why are you giving SuperCid since everyone will need to flash their Stock RUU anyway?
broncogr said:
Just to let you know if you stay with S-OFF HTC will now...
Hboot is a different version from HTC, it ends in 10xx rather than 00xx
So even if it doesnt say revolution, they still can tell
Best to restore to S-ON which is a bit risky if you dont follow instructions to the t..
Cheers
P.S. Also why are you giving SuperCid since everyone will need to flash their Stock RUU anyway?
Click to expand...
Click to collapse
nope my hboot is 1.17.0008, which is stock T-Mobile HBoot. And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
alphadog32 said:
nope my hboot is 1.17.0008, which is stock T-Mobile HBoot. And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
Click to expand...
Click to collapse
If it is stock hboot then you have missed all fastboot flash functionality that alpharev has put in their hboot.
Can you flash radio, splash and so on with this hboot you have now?
broncogr said:
If it is stock hboot then you have missed all fastboot flash functionality that alpharev has put in their hboot.
Can you flash radio, splash and so on with this hboot you have now?
Click to expand...
Click to collapse
Yes I can flash.
alphadog32 said:
And the SuperCID is because people are going to mess up and pick the wrong RUU.exe,
Click to expand...
Click to collapse
By encouraging people to install SuperCID, all you are doing is making their phone more traceable for tampering if it goes back for warranty, and allowing them to install the wrong RUU. If they don't have SuperCID, they'll get 'ERROR[131]: CUSTOMER ID ERROR' if they try to flash the wrong RUU and it will stop without flashing anything to the phone.
I know you're just trying to help, but all they have to do is run the latest released RUU for their region. Nothing more.
alphadog32 said:
Yes I can flash.
Click to expand...
Click to collapse
He means use 'fastboot flash' commands which you can't with the stock hboot.
Oh. I thought he meant ROM installing and installing root. Thank You.
Sent from my HTC Sensation 4G using XDA App
How do i know if CWM is removed?
Hi,
i did all the steps and get s-on back with stock rom.
my question is how do i know whether i have removed CWM as well? when i vol down + power, it went into bootloader. it's the same screen as when i have CWM installed. the only difference is the S-on, at least the ones i can recognize is different.
thx
here is what i need to know... i am actually getting and exchange and have to send this back in because the vibration stopped working. It as TMOUSA Sensation. So far here is what i have gathered about my phone:
Baseband/radio version: 10.42.9007.00u_10.11.9007.15_m
Build number: 1.35.401.1 cl84734
hboot: 1.17.1011
CID: T-MOB010
I looked at the http://forum.xda-developers.com/showthread.php?t=1074559 page and they listed two RUU for TMOUSA:
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
and
RUU_Pyramid_TMOUS_1.27.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_192098_signed
which one of these am i suppose to use? Will my baseband/radio be updated to a different band/radio?
radiikal said:
Hi,
i did all the steps and get s-on back with stock rom.
my question is how do i know whether i have removed CWM as well? when i vol down + power
thx
Click to expand...
Click to collapse
i will try to answer ur question.. after u went thru all the process to get s-off with the idea of installing custom roms using CWM, u will get into recovery with the steps power+vol down them u scroll down and pick recovery taking u to CWM..try now and it should take u to stock recovey, after u finally figure it this out by ur self..im pretty sure u will feel like u can conquer the android world..
Pick 1.29.xxx.x for TMOBILEUSA
HTC Sensation
RESTORED TO S-ON
STOCK HBOOT
STOCK ROM
ROOTED
Is this safe?? im planning to remove my superuser,root,CWM but keep S-OFF because im tired of worrying that my phone will die when i'm out and i won't be able to charge it
If you mess up, you may brick your device!
AFTER i DL the RUU, where do i paste it at?
Hi everyone,
yesterday I wanted to load a custom ICS rom on my HTC Sensation XE. I did S-off the phone, got root access. I downloaded the firmware, rom, and a super wipe zip file for the new rom. Put them all on my sd card and flashed them.
After I flashed the wipe file and the rom the phone was booting up and couldn't go further than boot screen, so I tried several times, wiped the phone and etc.
After few times trying when i went to the recovery, it gave me a message to update and I said yes! I think I shouldn't cause after that it tried to update something in recovery and it failed, system reboot and phone shut down.
since then i can't even turn on the phone!!!! I've got battery charged nearly 80% so the problem is not the battery. Can any of you guys please help me?
So to clarify, it wont start when you press Vol down and Power on at the same time?
No nothing happens!!! like i can't do anything with it or even make it work to a point that I can restore my backed up firmware etc...
device manager detects it though, but cant install the driver....
nbdelmore said:
No nothing happens!!! like i can't do anything with it or even make it work to a point that I can restore my backed up firmware etc...
device manager detects it though, but cant install the driver....
Click to expand...
Click to collapse
Yeah it soundslikeyou have Becker it some how. You may want to check out this thread, that is if you want to Teutonic do it yourself. But be warned I annotated 100% sure this will work on your Sensation. The other option is to try for warranty exchange or find someone to JTAG your Sensation. I can put you in touch with someone that can JTAG it if all else fails and you don't mind sending your phone off for a two or three days.
did u flash a non xe rom, did u do the supercid
T-Macgnolia said:
Yeah it soundslikeyou have Becker it some how. You may want to check out this thread, that is if you want to Teutonic do it yourself. But be warned I annotated 100% sure this will work on your Sensation. The other option is to try for warranty exchange or find someone to JTAG your Sensation. I can put you in touch with someone that can JTAG it if all else fails and you don't mind sending your phone off for a two or three days.
Click to expand...
Click to collapse
thanks for your answer macgnolia, I will give it a try this arvo and I let u know later with my result. I might need you to hook me up with someone who can fix it for me later on if i couldn't fix it on my own in few hours though.
cazper210 said:
did u flash a non xe rom, did u do the supercid
Click to expand...
Click to collapse
well I think i did. Im really not sure as of now cause i did so many things to fix the issue and finally i got it broken completely! but right now the problem is i cant even trun on the phone to go to recovery and check if it is spercid or not!
Most probably you didn't delete the PG58IMG (firmware) from sd card after flashing firmware. So each time you reboot into bootloader it asks to update in a never ending loop.
Delete any PG58IMG from sd card and reboot bootloader then go to recovery and flash the rom.
Also, what rom you were trying to flash and what firmware? what is the version of your Hboot? 1.27?
Hope it helps
kualmente said:
Most probably you didn't delete the PG58IMG (firmware) from sd card after flashing firmware. So each time you reboot into bootloader it asks to update in a never ending loop.
Delete any PG58IMG from sd card and reboot bootloader then go to recovery and flash the rom.
Also, what rom you were trying to flash and what firmware? what is the version of your Hboot? 1.27?
Hope it helps
Click to expand...
Click to collapse
yes true, i had the zip file on the sdcard and when it booted up the last time, it asked me to update and I selected yes (and I think I shouldn't) since then I cant turn on the device at all. I just took the sdcard out and deleted the PG58IMG.zip file but still nothing happened!
I was trying to flash revolution HD rom 6.6.1 if i'm not mistaken. is there any way that I can check the version of my HBOOT now? cause I'm not sure if it was 1.27 or not (as far as I remember, it was)
Pull out and reinsert the battery?
Power on while keeping pressed volume down + power button doesn't work? It should bring you to the bootloader.
It doesnt matter if you updated twice or three times the same PG58IMG. It is important that it was the right one.
All bootloader flashable zips are named PG58IMG but the content might be different (firmware, recoveries, spashscreen and even full roms etc etc).
Also, did you install a custom recovery or not? it is necessary to have a custom recovery to flash any custom rom
nbdelmore said:
No nothing happens!!! like i can't do anything with it or even make it work to a point that I can restore my backed up firmware etc...
device manager detects it though, but cant install the driver....
Click to expand...
Click to collapse
what is it detected as?
http://forum.xda-developers.com/showthread.php?p=21989107
follow this step by step, make sure u dont skip anything and when your phone is up and running dont forget to press the thanks button. if u need help along the way you can ask.
flashing file with bootloader is different from the custom rom.
flash 3.32 pg.. file approx 11-13 mb then without rebooting pull battery out and back in then reboot into recovery and flash the rom file and you are good to go.
panjaby said:
http://forum.xda-developers.com/showthread.php?p=21989107
follow this step by step, make sure u dont skip anything and when your phone is up and running dont forget to press the thanks button. if u need help along the way you can ask.
flashing file with bootloader is different from the custom rom.
flash 3.32 pg.. file approx 11-13 mb then without rebooting pull battery out and back in then reboot into recovery and flash the rom file and you are good to go.
Click to expand...
Click to collapse
How can the OP do this, the device will not even turn on to boot into fastboot or the bootloader therefore the instructions in the thread you linked are pretty much useless to the OP. It seems that the OP has hard bricked the device somehow,maybe fried the processor Blythe back to back flashes or fried the NAND memory with the back to back flashes, who really knows at this point. But right now my money is on JTAG or replacing the mainboard willbe the only fix.
T-Macgnolia said:
How can the OP do this, the device will not even turn on to boot into fastboot or the bootloader therefore the instructions in the thread you linked are pretty much useless to the OP. It seems that the OP has hard bricked the device somehow,maybe fried the processor Blythe back to back flashes or fried the NAND memory with the back to back flashes, who really knows at this point. But right now my money is on JTAG or replacing the mainboard willbe the only fix.
Click to expand...
Click to collapse
he mentioned nothing about trying it with adb/sdk fastboot using command prompt,
i was in similar situation with my friends phone last week, after 3 days of searching and reading i finally followed that thread and now the sensation is running ordroid 2.1 rom. the buttons on the phone got disabled somehow. had to manually install drivers in device manager, like he mentioned that comp detects the phone. so before giving up adb/sdk is worth a try atleast in my case it was.
Well, i'm sorry for you, man
A little foreshadow. I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install. I was silly and decided to clear the system... Which erased my OS completely.
For a while I was able to get to the TWRT(?) screen where I could mount my sd card, etc. While researching the problem I came across this:
a solution of fastbooting a recovery.img
I ran the fastboot recovery.img. The only problem is the only screen I can now access is the bootloader. I have bootloader 1.14.0002 loaded onto my phone if that helps.
Is there anyway to try to get a operating system or flash a rom onto this phone still or is it bricked for good? Also if I was able to put a rom onto it, what do you sugggest?
When I try to go to Recovery or Factory Reset, I get the HTC screen with the red text underneath it and it never goes any further.
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
That is the information listed in my bootloader as of now. I am not showing it listed as a drive in my computer when connected to USB. Also when I 'power off' I am in a reset cycle that doesn't stop.
I really appreciate any help in advance. This was a big wake up call to myself about how I should be a lot more careful when messing with these things.
Thank you to everyone that answers!
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
You might be hosed. Can you get into bootloader?
Sent from my One X using xda premium
Read before doing anything. Such a simple task. It's easy to read, it's hard to come back from a brick.
Sent from my One XL using XDA Premium
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer. http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.0-evita.img
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Not only does fastboot erase cache not take long it avoids many stupid little issues. I would say it's a must when flashing a new recovery.
Sent from my One X using xda app-developers app
sinkthehalffoot said:
I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install.
Click to expand...
Click to collapse
The reason it went to recovery is very simple. The OTA needs to have stock recovery in order to install. You don't have stock recovery on your phone anymore, you have custom recovery (TWRP). So the OTA stalled there, when it didn't find stock recovery.
sinkthehalffoot said:
I was silly and decided to clear the system... Which erased my OS completely.
Click to expand...
Click to collapse
Of course it did, what were you expecting to happen? Wiping the OS is the very definition of what happens when you wipe system. If you didn't know what wiping system would do, you shouldn't have done it. For that matter, you shouldn't be doing anything on your phone if you don't know what its for.
A lot of this points to a fundamental lack of reading and understanding:
- Don't know the name of the custom recovery installed on the system
- Wiping things without knowing what they are
- Basic rule (that many folks here seem to ignore, for reasons unknown): Don't install any OTA on a rooted device without first researching what will happen
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
You aren't bricked. With very few exceptions (and this isn't one of those) if the screen turns on, and you can get into hboot, the phone is recoverable. And probably fairly easily so, with the right steps. But you need to do some homework before proceeding.
redpoint73 said:
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
Click to expand...
Click to collapse
+1000
This is exactly the kind of situation that occurs when people get in over their heads and start blundering around.
http://forum.xda-developers.com/showthread.php?t=2232141
InflatedTitan said:
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer.
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In case anyone ends up stumbling here with a similar issue, this solution worked to a 'T'. Thank you again InflatedTitan.
To everyone else, yes I know, I should of read more than I had. I saw the jellybean update and have been wanting it for a while and acted with haste. I learned a valuable lesson from it all.
Lol this "solution" was around before you posted. You just didn't read or search enough.
Sent from my One X using xda app-developers app
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol :beer:
Sent from my HTC One X using xda app-developers app
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I thought I was the only one. In fact I just rooted a nook tablet and installed twrp. Slides to flash... And I could swear I was on cloud 9.
But bravo on the explanation sir. Love a good write up. Even though i already know it, feels good to read it.
Sent from my Carbon-ize Evita using xda-developers app
[HELP] Not sure if bricked or hardware issue?
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
pharrjw said:
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
exad said:
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
Click to expand...
Click to collapse
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Sent from my HTC One X using xda app-developers app
pharrjw said:
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
Click to expand...
Click to collapse
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Thanks again for the replies guys.
31ken31 said:
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Click to expand...
Click to collapse
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
exad said:
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Click to expand...
Click to collapse
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
pharrjw said:
Thanks again for the replies guys.
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
Click to expand...
Click to collapse
factory reset in bootloader corrupts the SD card. We wont worry about that just yet as there's nothing we can do about it until we can get recovery on there.
You're going to have to be very careful because it sounds like your EMMC partitions might have some issues. if you can get it to bootlaoder KEEP IT AT THAT SCREEN. don't power it off or anything, leave it there. Because one wrong move could be a perma brick. If we can get a rom on there to S-OFF with, we can RUU to restore your emmc partitions.
Sorry for flooding this Forum with something basic as this but as a mere mortal I don't possess the mental capacity nor stamina to crash course my way in to this whole developers battleground.
I got a HTC ONE S that had been unlocked( I think) and when stupid me tried to do a system update (uncustomed to the way of the android as a convert apple-noob:silly I updated the phone with some kind of CID package which immediately sent the HTC in to the dreadded:
"This build is for development purposes only 20second loop of doom"
so after hours of studying this ancient language of boots, CID, builds, and alien laungage mumbo I havn't even been able to get the USB fastboot to work.
thusly I admit defeat and beg and plead to ye ascent beings only know as developers to make a complete noob-proof course of action how to tackle this peculiar problem.
so can anyone please make a step by step guid of what to download, how to install, where to get it and what to do That'd beeee swell.:highfive:
also I'll be going away so may not answer until sunday
any takers on helping me solve this riddle?
Welcome to the world of bricking and screwing up. This is not like Apple jailbreaking where you press one button on a website and it works.
This is pain and suffering. I would try and run an RUU to get the phone to stock. There are tons of threads on how to run an RUU. If the phone is not S-OFF, you will have to relock boot loader to run the RUU.
808phone said:
Welcome to the world of bricking and screwing up. This is not like Apple jailbreaking where you press one button on a website and it works.
This is pain and suffering. I would try and run an RUU to get the phone to stock. There are tons of threads on how to run an RUU. If the phone is not S-OFF, you will have to relock boot loader to run the RUU.
Click to expand...
Click to collapse
alright cheers, pretty sure it's S-ON and despite not knowing anything you just said at least it's something.
I also assume I'll need USB fastboot for this so I guess I'll start by trying to get that working
Anyone else care to explain the steps to take in greater detail? This was not a failed attempt at jailbreaking it was purely accidental so I have no experience doing this
Edit: I might add I suck at searching through forums aswell (especially when I don't know what I'm looking for) so maybe just a link to the proper threads would help me loads
LuckyXII said:
Anyone else care to explain the steps to take in greater detail? This was not a failed attempt at jailbreaking it was purely accidental so I have no experience doing this
Edit: I might add I suck at searching through forums aswell (especially when I don't know what I'm looking for) so maybe just a link to the proper threads would help me loads
Click to expand...
Click to collapse
To get back to stock, you run an RUU (ROM update utility). Here is a thread:
http://forum.xda-developers.com/showthread.php?t=2678700
I guess it's similar to running iTunes and pressing the restore button - but more involved.
not sure if I have a custom recovery but either way I couldn't flash the recovery.img and the RUU I ran didn't work (it was the same RUU that was installed on the phone)
Phone is S-ON
hboot 2.15.0000
open dps v31.1.0.45.0815
eMMc-boot
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
LuckyXII said:
not sure if I have a custom recovery but either way I couldn't flash the recovery.img and the RUU I ran didn't work (it was the same RUU that was installed on the phone)
Phone is S-ON
hboot 2.15.0000
open dps v31.1.0.45.0815
eMMc-boot
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
Click to expand...
Click to collapse
Did you relock the boot loader before running RUU?
808phone said:
Did you relock the boot loader before running RUU?
Click to expand...
Click to collapse
I followed the steps but can't say I remember seeing "relocking boot loader" I will have to check this out further in the morning
LuckyXII said:
I followed the steps but can't say I remember seeing "relocking boot loader" I will have to check this out further in the morning
Click to expand...
Click to collapse
OK, then check this link out:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
808phone said:
OK, then check this link out:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Click to expand...
Click to collapse
cannot open "Unlock_code.bin" :/
tried everything... changing the directive in cmd to match the location of the bin file but nothing works
adb can't find my device but fastboot can which could be why the RUU nor unlocking bootloader won't work and to get adb to work I need to enable USB debugging which can't be done while the phone is looping (unless some1 knows the right command line)
I am retarded
since I got this phone second hand I didn't know what had been done with it other than what I installed to cause my problems...
one of the things that had been done previously was unlocking bootloader.. hence the very obvious "Unlocked" in the boot menu.... sooo unlocking an unlocked bootloader was kinda redundant
tried oem locking the boot b4 but missed to specify where the files where (C:adb), lock worked and RUU installed without a hing!
thanks for your help if I knew what I was doing your instructions would have worked perfectly!
Alright!!!!!! Well, you are set!
So..... now that's it's back to stock. Are you going to use it as-is? Or are you planning to try a custom ROM again?
Try booting into the boot loader by shutting off the phone, then pressing volume down while pressing power. If it doesn't go to boot loader, then press and hold power for something like 10 seconds until the phone shuts off, then press volume down, and power again. Keep holding volume down until you get the boot loader menu.
Write down what it says about your HBOOT and whether you are S-OFF or S-ON.
DO NOT CHOOSE ANY COMMANDS FOR NOW
Press and hold power until the phone turns off again when you are done. Then press power again to turn the phone on again after a few seconds to use your phone regularly.
808phone said:
Alright!!!!!! Well, you are set!
So..... now that's it's back to stock. Are you going to use it as-is? Or are you planning to try a custom ROM again?
Try booting into the boot loader by shutting off the phone, then pressing volume down while pressing power. If it doesn't go to boot loader, then press and hold power for something like 10 seconds until the phone shuts off, then press volume down, and power again. Keep holding volume down until you get the boot loader menu.
Write down what it says about your HBOOT and whether you are S-OFF or S-ON.
DO NOT CHOOSE ANY COMMANDS FOR NOW
Press and hold power until the phone turns off again when you are done. Then press power again to turn the phone on again after a few seconds to use your phone regularly.
Click to expand...
Click to collapse
well if I were to try something now that I've already started walking down the path it'd probably be kitkat...
http://forum.xda-developers.com/showthread.php?t=2183023
note sure if I'm ready though
LuckyXII said:
well if I were to try something now that I've already started walking down the path it'd probably be kitkat...
http://forum.xda-developers.com/showthread.php?t=2183023
note sure if I'm ready though
Click to expand...
Click to collapse
OK take your time and when you are ready, PM me. I really do suggest CandyKat if you go for a custom ROM. It is the best ROM I have used on the ONE S. CM11 was ok for me, but for some reason CandyKat is just running so much better.
808phone said:
OK take your time and when you are ready, PM me. I really do suggest CandyKat if you go for a custom ROM. It is the best ROM I have used on the ONE S. CM11 was ok for me, but for some reason CandyKat is just running so much better.
Click to expand...
Click to collapse
Alright I will look in to it! Thank you for all the help wouldn't have done it without you