Related
i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english
same problem here, help is needed!
A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM
Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?
I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device
Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...
Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.
@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers
Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!
Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.
Hi all,
I have a problem with my Sensation due to my own fault.
I want to flash ARHD ICS rom to my phone, and I started with rooting my Sensation. I followed all instruction til installing the Recovery (PG58IMG).
I downloaded two versions of PG58IMG (one for ICS and one for the other), but I copied the firmware for ICS version to my SD card and already installed it. Now, my phone already S-off but cannot reboot into homescreen. It keeps rebooting it self in white hTC screen (after I installed the ICS firmware).
I don't know how to fix. I tried to read the troubleshoot in the post but I still cannot fix it. Does anyone have a solution??
Thanks in advance
chuz said:
Hi all,
I have a problem with my Sensation due to my own fault.
I want to flash ARHD ICS rom to my phone, and I started with rooting my Sensation. I followed all instruction til installing the Recovery (PG58IMG).
I downloaded two versions of PG58IMG (one for ICS and one for the other), but I copied the firmware for ICS version to my SD card and already installed it. Now, my phone already S-off but cannot reboot into homescreen. It keeps rebooting it self in white hTC screen (after I installed the ICS firmware).
I don't know how to fix. I tried to read the troubleshoot in the post but I still cannot fix it. Does anyone have a solution??
Thanks in advance
Click to expand...
Click to collapse
If I understand you correctly you flashed the firmware upgrade BEFORE you flashed the new ICS rom? If so you'll need to get your sdcard card out (and get your computer to read it) so you can rename the PG85img on your sdcard so you can get back into recovery so you can flash the new ICS rom.
runderekrun said:
If I understand you correctly you flashed the firmware upgrade BEFORE you flashed the new ICS rom? If so you'll need to get your sdcard card out (and get your computer to read it) so you can rename the PG85img on your sdcard so you can get back into recovery so you can flash the new ICS rom.
Click to expand...
Click to collapse
Yes, I flashed the upgraded firmware before not only I flashed ICS rom, but also I get rooted. Now, I can't flash any rom as well as su-2.3.6.1-ef-signed.zip or su-2.3.6.3-efgh-signed.zip.
It still keep bootlooping. I tried to flash the other firmware, but it showed 'CID incorrect'. I don't know how to fix now
Did you check MD5 Sums before you flashed the ROM because it sounds like a bad download so re-download the ROM and reflash
Jonny said:
Did you check MD5 Sums before you flashed the ROM because it sounds like a bad download so re-download the ROM and reflash
Click to expand...
Click to collapse
I did check MD5 sums for all files I downloaded and it is corrected.
Now, I'm curious that whether it is possible to flash the upgraded firmware before being rooted.
And of course you need to be using the right version of the firmware for the rom you want to flash. Mike's latest uses 3.24 per here. http://forum.xda-developers.com/showthread.php?t=1459767
I don't know if you can get into fastboot or not, but you should be able to check the CID of your phone there, and download the right firmware for your phone. If your phone is carrier independent (i.e. didn't get on contract) then the HTC__xxx variety should be good.
airzone said:
And of course you need to be using the right version of the firmware for the rom you want to flash. Mike's latest uses 3.24 per here. http://forum.xda-developers.com/showthread.php?t=1459767
I don't know if you can get into fastboot or not, but you should be able to check the CID of your phone there, and download the right firmware for your phone. If your phone is carrier independent (i.e. didn't get on contract) then the HTC__xxx variety should be good.
Click to expand...
Click to collapse
Thank you so much for your link. I can boot my Sensation into the homescreen now. For my problem, I have to download and flash the older version (3.17) to fix it.
Thanks all of you for your reply again.
+1 for me, solve with a new download .
Just flash the Mod, the bootloop is normal.
I got the same problem, before i flashed Revolution Rom i used that radio package. After the radio package flash, my phone wass stuck in a bootloop.
I took the memory card out en removed the zip file en flashed the revolution rom. After that my phone started normal.
SOrry for the bad enlgish.
Good luck mate.
hey, guys i just had the same problem, kinda. lol
anyways my phone is rooted, s-off and superCID
when i went to install the new ics rom i did everything this thread http://forum.xda-developers.com/showthread.php?t=1459767
said to do and when the new root booted up for the first time, it would go up to the beats audio logo,( the ics rom with beats audio (xe)) then like restart back to the htc startup logo, then beats again then htc again, it just kept doing this..??
so i just deleated everything and restored back to origional backup rom.
so what did i do wrong?
a bad download link/file? can u give me a good one?
thanks, any help is greatly appreciated as iam totally lost right now...
edit:
also do i even need this file (PG58IMG.zip.) to flash the ics rom if my phone is superCID ??? iam confused on that part.
nevermind, figured it out and got it work! the new ics is pretty sweet!!
thanks for everything- towards all the developers and testers on here
Cool. The answer is yes of course. The firmware file contains a specific radio / hboot / etc version. The ROM you download and install is dependent on certain combinations of the firmware versions you have. The super cid just allows you to flash any of the firmwares available here... Otherwise you have to find the specific one for your region and/or carrier.
Also, don't forget you can use an adb logcat while your phone is booting to see if you can diagnose any boot-looping issues. Just run that command on your PC with your phone attached via USB cable
Kawirider594 said:
hey, guys i just had the same problem, kinda. lol
anyways my phone is rooted, s-off and superCID
when i went to install the new ics rom i did everything this thread http://forum.xda-developers.com/showthread.php?t=1459767
said to do and when the new root booted up for the first time, it would go up to the beats audio logo,( the ics rom with beats audio (xe)) then like restart back to the htc startup logo, then beats again then htc again, it just kept doing this..??
so i just deleated everything and restored back to origional backup rom.
so what did i do wrong?
a bad download link/file? can u give me a good one?
thanks, any help is greatly appreciated as iam totally lost right now...
edit:
also do i even need this file (PG58IMG.zip.) to flash the ics rom if my phone is superCID ??? iam confused on that part.
Click to expand...
Click to collapse
To do so,
1. Download the correct firmware version ( PG58IMG.zip V3.24 ) and copy it to the root of your SDCARD.
Be 200% sure that the downloaded zip file is not corrupted. ( Check the MD5 checksum after you download)
2. Pull Back the battery and wait for a minute.
3. Put the battery and press POWER+VOLUME Down Key together.
4. Your phone will detect the firmware.
5. Follow the screen and complete the flashing.
6. Download the ICS based ROM of your favor.
7. Boot into recovery and flash your rom.
Kawirider594 said:
hey, guys i just had the same problem, kinda. lol
anyways my phone is rooted, s-off and superCID
when i went to install the new ics rom i did everything this thread http://forum.xda-developers.com/showthread.php?t=1459767
said to do and when the new root booted up for the first time, it would go up to the beats audio logo,( the ics rom with beats audio (xe)) then like restart back to the htc startup logo, then beats again then htc again, it just kept doing this..??
so i just deleated everything and restored back to origional backup rom.
so what did i do wrong?
a bad download link/file? can u give me a good one?
thanks, any help is greatly appreciated as iam totally lost right now...
edit:
also do i even need this file (PG58IMG.zip.) to flash the ics rom if my phone is superCID ??? iam confused on that part.
Click to expand...
Click to collapse
No you didn't do everything the thread said to do because you're stuck in a bootloop. And yes, you must have correct firmware to run any ICS ROM.
1. SuperCID.
2. Load correct firmware for ROM version you wish to flash (there are 3 different firmwares, 3.06, 3.12 and 3.24. Make sure you've got the right one.
Put PG58IMG.zip on the root of your damn SD card.
Put the ROM you want on the root of your damn SD card.
Put a wipe or superwipe script on the root of your damn SD card.
So far it's easy, no?
Boot to bootloader, select FASTBOOT, select yes to update.
Watch the phone. You should see it flash some partitions, reboot itself, then flash the radio and some other crap.
When done you should be at correct HBOOT and radio.
Now, pull the battery. Pull the SD card.
Insert the battery. Start the phone with power + Volume down.
Move cursor to recovery.
Insert SD card and select recovery.
Flash the wipe script, flash the ROM.
Now if you did everything exactly like this, you will boot to normal phone in about 10 minutes or so.
This has been spelled out 50 times in 50 threads, including threads devoted to nothing but this procedure.
Your phone is a machine. It can only do what you tell it to do. If you screw up, it's screwed up. If you do everything exactly right, in the right order, carefully checking each step, your phone will behave.
Try again.
Do it right. Do it carefully.
P.
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
fashofasho said:
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
when you did S-OFF in order to install Cyanogen JB first you had to flash the latest fw version and then the rom
the rom you tried to install requires the latest fw version
now are you still s-off?
what is now your hboot version?
what is your fw version?
I am wondering if I made any major changes or done anything wrong.
1) Yesterday I attempted to "S-Off" my phone for the first time ever since purchase. When "revolutionary.io" asked me what Bootloader I was on, I connected the phone through USB and the revolutionary executable told me 1.18.0000. The first few tries failed because it just kept saying "Waiting for bootloader" but after messing with different HTC drivers and unplugging a bunch of times it finally took and went through S-off. Now when I boot into bootloader it says my verison is 1.17 S-off. Is it correct that I went backwards from 1.18 to 1.17?
2) I flashed a custom ROM but being a noob that I am I knew nothing about firmware so I was stuck in bootloop of Cyanogen JB. I flashed through RUU to stock ROM but it is not the same stock ROM that came with my phone out of the box, some of the settings are different it does have the same network though TMOUS; especially the personalize options some of them do not work (themes). Is it alright if I flashed to this ROM as opposed to the exact same one that my phone came with? If I update my firmware and flash Cyanogen again this ROM is basically gone anyways right? I am just concerned that by RUU flashing this stock ROM I changed the firmware or baseband or something important.
Thats all I'm wondering, hoping you can give me a Yes or a No and a brief explanation to each question, thanks so much
Click to expand...
Click to collapse
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
i got confused
.i think your answer is going for fashofasho
Skipjacks said:
1) Normal. You're good. And you'll have HBoot 1.27 or 1.29 when you're all done.
2) Not normal. You missed a step. You need to upgrade the firmware to 3.32 (HBoot 1.27) or 3.33 (HBoot 1.29). Either will run CM10, which gives you better performance is for you to decide. The difference is mainly the radio for cell reception. If you're a T Mobile user try the 3.32 for T Mobile for starters. (Available in the radio/firmware thread. Do a search and you'll find it.)
Basicly what you did was flash an Android 4.x ROM on Android 2.3 firmware. That doesn't work. They are incompatible.
If you RUU'ed back to stock, you might have reverted back to S-On and lost your custom recovery, so check. If you have S-On now, you have to start over.
If you still have s-off and can still get into your recovery (Clockwork or 4EXT, I receomend 4EXT but CM10 will load from either), find that Firmware thread, download 3.32 for T Mobile. Follow the instructions in that thread on how to install new firmware. It's painfully simple...you just put the firmware file on teh SD card, reboot, and let it do it's thing. The firmware thread will be more specific, but that's about it. It takes 2 minutes. The phone will suddenly go black and power off for a second during the process. Don't panic. It's normal. AND DON'T TOUCH IT UNTIL IT TELLS YOU TO!!!!
Once you've done that, the stock ROM you have now will not boot. You will need to boot to recovery (Clockwork or 4EXT), do a full wipe, and flash CM10 again.
It should not boot.
This entire process (if you are still s-off and have your recovery working still) should take no more than 15 minutes. It sounds complicated but it's really not. I promise!
I just gave you a general overview. If you get stuck at any point come back and ask more specific questions about where you are stuck.
Click to expand...
Click to collapse
Thanks for the reply. Okay so here is where I am currently at. I haven't done anything since I reflashed stock ROM throguh RUU after the fail cyanogen flash. On this stock ROM whenever I load into bootloader it still says s-off 1.17 but I did lose my clockworkmod. So according to your instructions I should either clockworkmod again or 4ext now, that's okay right? If so, going to flash firmware then cyanogen!! Or is there a problem that I have s-off but not recovery.
P.s. there is no point in running revolutionary and have it s-off again when I already have it right, just thought it might be necessary to make things fresh
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app
Skipjacks said:
If you have a bootable phone right now this is easy as you may not need adb or fast boot or anything.
First off you will need to install 4ext. Get the app from the Play Store. Then run it and let it install its recovery module. (You may need to be rooted to do thus, which your stock rom is not. Im not sure if you can flash the recovery without root or not because Ive never tried without root. If so, then you will have to install Superuser via fastboot I think. You any guide for rooting to get instructions on this. Its easy.)
You may also find a way to install 4ext recovery via flashing from bootloader, but you will have to search for that. You MAY even be able to install it with the firmware upgrade. You will have to see if that is an available option.
Get your firmware from this thread...
forum.xda-developers.com/showthread.php?t=1459767
Follow the instructions to update. Once you have 3.3x firmware and 4ext simply boot to recovery, do a full wipe, and flash cm10 (make sure cm10 is on your sd card. You can download it from your currently working gingerbread rom so you have it available)
You have like 15-20 minutes worth of work to do, so its not a monumental obstacle to overcome. It just seems like alot
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?
fashofasho said:
I am not rooted but am S-off. So my next step would be to root. I am suppose to have Clockworkmod to root AND 4EXT after right? Its not one or the other? I keep reading that people recommend 4ext is better than CWM but in order to root su-2.3.6.3-ef-signed.zip I need CWM first correct?
Click to expand...
Click to collapse
flash su-2.3.6.3-ef-signed.zip first and then install 4ext recovery
You're over engineering this. You don't need to root your current ROM first. That's an extra step since you're s-off.
If you are s-off it's really simple to get 4EXT recovery.
First, download this and put it on the root directory of your SD Card (meaning not in a folder, just on the SD Card. Do not rename it)
http://d-h.st/qnm
I got this download link from here...
http://forum.xda-developers.com/showthread.php?p=21989107
Click Thanks for Joaquinf in that thread. He made the 4EXT zip that's flashable through the bootloader.
That is 4EXT made into a zip file that's flashable via the bootloader, which you can do when you are S-off.
So put that file on the SD card, power the phone off, pull the battery out for a second and put it back in (this stops fastboot so you can get back to the bootloader). Then hold volume down and power at the same time. You have to hit both buttons at the same time. If it goes to the splash screen, pull the battery and try again.
When the bootloader loads up it will immediately find the PM58IMG.zip file. It will ask you if you want to install the update. Say yes by hitting volume up I think (it will tell you how to say yes)
Put the phone down and don't touch it until it tells you it's done. Should just take a second. But seriously don't touch it. Leave it alone.
If that works, you've just flashed 4EXT. You can check it by pulling the SD card out (so it doesn't try to flash the PM58IMG again) and rebooting to the bootloader and selecting 'recovery' from the menu. 4EXT should boot up.
This entire process so far shouldn't take more than 3 minutes total. It just sounds like a lot.
To see this detailed out by someone else in case you want to check what I'm saying, read steps 4 and 5 of the first post in this thread.
http://forum.xda-developers.com/showpost.php?p=21989063&postcount=1
Give the author 'thanks' again because he's awesome and deserves it.
Now you've got 4EXT installed. Great. You're 1/3rd of the way home.
Now you need to update your firmware. Delete the PM58IMG.zip file you used to flash 4EXT off the SD card (use a card reader or boot the phone up and delete it, whatever works. You can also use 4EXT as a card reader now too by choosing USB storage from inside 4EXT. It will give you access toteh SD card on your computer now)
Now get new Firmware from this thread.
http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
try the 3.33 firmware universal. First download link in post 2 of the thread above.
CHECK THE MD5 SUM!!!! I'M NOT PLAYING AROUND HERE!!! You are worried about bricking your phone, this is where you can do it if the firmware .zip is bad.
Put that PM58IMG file on your SD and flash it in the bootloader the same way you flashed 4EXT recovery a minute ago. (If you're still in 4EXT recovery you can use it's power menu to reboot into bootloader easily.)
This will take a minute. The phone will shut off and go black in the middle of this process. Your heart will skip a beat. Relax. It'll come back on. Again, put the phone down and walk away while it does it's thing and don't touch it until it says it's done.
Delete the PM58IMG file from your SD card.
You are now 2/3 of the way there. Your phone WILL NOT boot up right now because your ROM is not compatible with your firmware. Relax. That's supposed to happen.
Now you can flash CM10. Make sure you have the CM10.zip file on your SD card nad GApps. (Bruce has Gapps in his downloads page). Delete the PM58IMG firmware file from your SD card (that's important)
Pull the battery again so you can get back into bootloader. Get into bootloader (power + volume down)
Select Recovery
4EXT should boot up.
Go to the Wipe menu. Wipe all partitions except SD card. (Old ROM is now gone)
Go back to the main menu.
Install from SD
Find the CM10.zip file you should have downloaded and put onto the SD card. Flash it.
This will take about 3 minutes. 4EXT will flash it and ask if you want to reboot. You do not yet. Not you need to flash Gapps the same way you flashed the ROM.
When that's done, now you can reboot. You shoudl see the CyanogenMod boot animation after the splash screen. Give it a few minutes to boot up this first time. Once it boots, set it up the way you like it. If you enjoy it, donate a few bucks to the developer, Bruce.
You don't have to root CM10. It's already rooted when you boot it up the first time.
When trying to restore/unroot my One S something bad happened. I'm not sure, but I or the program I tried to use somehow erased the memory and completely removed the phone OS. What should I do to get my phone back to life?
EDIT:
My phone is back to life!
The solution that worked was a mixture of a few previously posted on xda.
I followed this tutorial: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing
Under ROM flashing I did steps 4-7 and then flashed the boot.img for my chosen Rom(Currently UTB: http://www.connect-utb.com/utb-rom-for-the-htc-one-s/) via CMD. Then I powered down, waited for a bit, and started the phone again. The phone finally worked as it was supposed, I got past boot image and entered the normal phone configuration.
The reason I chose UTB Rom was because someone else have had positive results with this Rom
(http://forum.xda-developers.com/showthread.php?p=25557817#post25850720 post #8),
which also proved correctly for me as I tried to install another Rom without success just a few mins later. (To get it to work again I followed my own instructions above, and it worked)
Thanks for your help! And I hope this solution will guide and help others with similar problem in the future!
-Heart
HeartOfFart said:
When trying to restore/unroot my One S something bad happened. I'm not sure, but I or the program I tried to use somehow erased the memory and completely removed the phone OS. What should I do to get my phone back to life?
Click to expand...
Click to collapse
Hello,
If you can get to the bootloader then you should relock it and flash the RUU for your phone. That will return it to stock and you can reroot or do whatever.
Rsotbiemrptson
You could also just reflash the ROM of your choice by going into TWRP custom recovery, mounting your sd card and copying the ROM over.
Then flash the ROM, and dont forget to also fastboot the relevant boot.img for that rom.
TWRP recovery is better than CW as it does allow you to mount your sd card. So download TWRP (google it) and fastboot flash recovery <filename>.img
then load the recovery then mount sd card. You should be good to go from there, unless your SD Card is corrupted. If that is the case, then check http://forum.xda-developers.com/showthread.php?t=2086156
Rsotbiemrptson said:
Hello,
If you can get to the bootloader then you should relock it and flash the RUU for your phone. That will return it to stock and you can reroot or do whatever.
Rsotbiemrptson
Click to expand...
Click to collapse
Yes, I can get into bootloader, but can't find the right RUU for my version.
Thanks guys, it's awesome that you help me!
Didn't find the correct RUU, so I get an error..
The other method posted will be tried out tomorrow!
AKToronto said:
You could also just reflash the ROM of your choice by going into TWRP custom recovery, mounting your sd card and copying the ROM over.
Then flash the ROM, and dont forget to also fastboot the relevant boot.img for that rom.
TWRP recovery is better than CW as it does allow you to mount your sd card. So download TWRP (google it) and fastboot flash recovery <filename>.img
then load the recovery then mount sd card. You should be good to go from there, unless your SD Card is corrupted. If that is the case, then check http://forum.xda-developers.com/showthread.php?t=2086156
Click to expand...
Click to collapse
I'm trying, but it doesn't work for me. Will give some more effort into this tomorrow. Does anyone have a good way to find the right RUU?
This rooting crap used to be easier man, I swear. I think I literally rooted my Evo through the web browser. Whatever...anyway, it just seemed a lot less riskier back then. I havent had an Android phone since then so I was happy to see my One S come in the mail. Right now though, I'm hoping I didn't waste my money. I'm gonna try to retrace my steps as explicitly as possible so someone can help me easier.
1. Unlocked the bootloader thru HTC Dev
2. Used this to root
3. Install recovery, TWRP.
4. Downloading CM10.2 ROM and Gapps to flash thru TWRP.
5. Cant mount sdCard. The mount screen in TWRP gives you 4 check box options, cant check 'mount sd'
5a. (Can boot phone as normal until now. Was on stock rooted rom with no problems but I hate sense and wanted to switch)
6. Wipe everything; data, cache, dalvik, sd.
7. Cant see SD Card at all now. No OS. Stuck on white HTC startup screen if I dont go to bootloader/recovery.
8. At this point I just tampered around with random solutions from threads I found on google, now I can see my SD card in TWRP file manager but its still not mountable (Even when I could check 'mount sd' windows doesnt see anything).
9. Tried relocking bootloader, running RUU, error code 155.
10. Right now, stuck with tampered unlocked bootloader, s-on, cant install rom because sd card wont mount and cant push ruu because it errors within 2 minutes. This was from last night, and I havent touched it today, and I wont touch it until someone who actually knows what they're doing can tell me whats up.
help
Hi,
I had a similar issue.. I followed a tutorial on YouTube and the guy forgot to mention that the ROM needs to be on the SD before rooting.
And my device was not reconised by my computer (win 7).
I messed around with a few recovery's.. turned out i was using a older version and after flashing about 3 recovery's my computer reconised my device when mounting SD card.
Hope this helps.
cfagan17 said:
This rooting crap used to be easier man, I swear. I think I literally rooted my Evo through the web browser. Whatever...anyway, it just seemed a lot less riskier back then. I havent had an Android phone since then so I was happy to see my One S come in the mail. Right now though, I'm hoping I didn't waste my money. I'm gonna try to retrace my steps as explicitly as possible so someone can help me easier.
1. Unlocked the bootloader thru HTC Dev
2. Used this to root
3. Install recovery, TWRP.
4. Downloading CM10.2 ROM and Gapps to flash thru TWRP.
5. Cant mount sdCard. The mount screen in TWRP gives you 4 check box options, cant check 'mount sd'
5a. (Can boot phone as normal until now. Was on stock rooted rom with no problems but I hate sense and wanted to switch)
6. Wipe everything; data, cache, dalvik, sd.
7. Cant see SD Card at all now. No OS. Stuck on white HTC startup screen if I dont go to bootloader/recovery.
8. At this point I just tampered around with random solutions from threads I found on google, now I can see my SD card in TWRP file manager but its still not mountable (Even when I could check 'mount sd' windows doesnt see anything).
9. Tried relocking bootloader, running RUU, error code 155.
10. Right now, stuck with tampered unlocked bootloader, s-on, cant install rom because sd card wont mount and cant push ruu because it errors within 2 minutes. This was from last night, and I havent touched it today, and I wont touch it until someone who actually knows what they're doing can tell me whats up.
Click to expand...
Click to collapse
Okay First I don't whether you have an S3 version (VilleC2) or an S4 version (Ville).
Understand this, when you format SD card using TWRP recovery, you can't mount it. It is because only the Stock HTC recovery is able to format the SD correctly.
What you ought to do now is:
1. Download stock HTC recovery for your phone version, S3 or S4.
2. flash the recovery through Fastboot using the command:
Code:
fastboot flash recovery recovery.img
3. Go to bootloader and select the option to erase Storage; if it's not there, then you will have to select Factory Reset, wiping your data and apps too.
Regards
Just use this - http://forum.xda-developers.com/showthread.php?t=2471151
It will almost do all things for you, Unlock Bootloader, Flash recovery, Root ...
And remember, if abd console says "error: device not found" or when downloading and fail install "HTC MTP drivers" don't worry, it happened to me too.
Remember, you need flashed Recovery, to be able to Gain Root. And Unlocked Bootloader to flash Recovery.
Now I am back to original stock ROM, rooted.
Windows still not recognizing SD card after mount. it gives option to mount internal_sd, but folder that sd is located is called 'sdcard'? I flashed stock recovery, clear storage, then factory reset, then root, then flash twrp.
Even when I put a custom ROM and gapps on the sd through stock ROM, it bootloops after flash. It's like HTC really doesnt want me to appreciate anything other than their crap stock firmware.
cfagan17 said:
Now I am back to original stock ROM, rooted.
Windows still not recognizing SD card after mount. it gives option to mount internal_sd, but folder that sd is located is called 'sdcard'? I flashed stock recovery, clear storage, then factory reset, then root, then flash twrp.
Even when I put a custom ROM and gapps on the sd through stock ROM, it bootloops after flash. It's like HTC really doesnt want me to appreciate anything other than their crap stock firmware.
Click to expand...
Click to collapse
Rooting the stock is not necessary flash a custom rom. Most roms that you flash are already rooted and root should be flashed in twrp if you just want a stock rooted rom
Flash the stock recovery, clear storage and factory reset. Then flash TWRP. If that doesn't boot for some reason you may need to flash the stock ruu.
If you chose to keep the stock firmware, you can download the superuser.apk from the playstore. When you run the app it will give you the option to reboot into TWRP to flash the root automatically.
mjsheldon4 said:
Rooting the stock is not necessary flash a custom rom. Most roms that you flash are already rooted and root should be flashed in twrp if you just want a stock rooted rom
Flash the stock recovery, clear storage and factory reset. Then flash TWRP. If that doesn't boot for some reason you may need to flash the stock ruu.
If you chose to keep the stock firmware, you can download the superuser.apk from the playstore. When you run the app it will give you the option to reboot into TWRP to flash the root automatically.
Click to expand...
Click to collapse
Even after clear storage, factory reset and TWRP flash I still cannot see the SD card in Windows or install a custom rom without white HTC bootloop. Only way I can mount the SD card is on the stock rom.
Also, Win says SD card is 10GB. Does everything else really use up 6GB?
cfagan17 said:
Even after clear storage, factory reset and TWRP flash I still cannot see the SD card in Windows or install a custom rom without white HTC bootloop. Only way I can mount the SD card is on the stock rom.
Also, Win says SD card is 10GB. Does everything else really use up 6GB?
Click to expand...
Click to collapse
What CID do you have. Have you matched the RUU with the your CID. If the CID's don't match it will give you and error and not flash. If you are SuperCID you can flash any RUU but with a stock CID you need the RUU that matches it.
mjsheldon4 said:
What CID do you have. Have you matched the RUU with the your CID. If the CID's don't match it will give you and error and not flash. If you are SuperCID you can flash any RUU but with a stock CID you need the RUU that matches it.
Click to expand...
Click to collapse
I already flashed RUU. I can't flash a custom ROM.
I don't see here. Are you s-off or on?
Sent from my CM 10.1 Motorola Xoom Wingray!
mjsheldon4 said:
I don't see here. Are you s-off or on?
Sent from my CM 10.1 Motorola Xoom Wingray!
Click to expand...
Click to collapse
On