[Q] Noob error flashing. Need help recovering. - HTC Desire S

Hi,
Sorry - attack of the noobie. I've messed up putting a custom ROM on my ICS Desire S and need help recovering to a state where I can restart the process.
I'll detail the process but I've basically wiped the standard ROM but failed to get S-OFF for hboot2.02.0002 so the device freezes after the HTC splash-screen. I'd like to try to get it back to stock so I can try again. But no backup.
Details:
I tried to follow a set of instructions from the MIUI blog: http://en.miui.com/a-107.html
I downloaded the MIUI 3.12.27 ROM and copied to sdcard
Got the g12 flashing tools and android sdk (windows 7)
Went to recovery mode and discovered HBOOT version 2.02.0002
Went to revolutionary to get s-off but realised there was no tool for my version of hboot.
MISTAKE1: went to htcdev to use unlocking tool, assuming this was S-OFF too.
Followed htcunlock instructions to unlock bootloader and continue process.
Flashed clockworkmod recovery
Nandroid backup
Wipe-data/factory reset & wipe cache
Installed from sd card
Rebooted and screen went black (though backlit) after the HTC splash-screen.
had a dig about forums and tried different custom ROMS but with no improvement.
MISTAKE2: in order to make room for extra ROMS on the sd card, I deleted the Nandoid backup from the card - thinking I had copied it to the PC but hadn't.
Realised it was still S-ON, I found instructions to downgrade hboot (http://forum.xda-developers.com/showthread.php?t=1318919) but I need to get my devices back to running stock ICS first.
I've got the official HTC RUU for ICS - but the installation procedure assumes I have a working OS to run HTCsync against. I only have recovery.
So I'm after some help before making matters worse.
As I understand it, I need to relock the bootloader and get the official ICS RUU reinstalled (AND BACKED UP) but I'm not sure how to do that from the state the phone is in. Can I push the standard ROM back on there from recovery and get it working again?
Thanks

Your other option is to flash the boot.img from the rom you installed through fastboot. (and repeat any time you install a new Rom or updated rom version, while your phone is still s-on)

teadrinker said:
Your other option is to flash the boot.img from the rom you installed through fastboot. (and repeat any time you install a new Rom or updated rom version, while your phone is still s-on)
Click to expand...
Click to collapse
Wonderful - thanks - saved me hours.

Related

Desire s stuck after 2.3.5 update

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.

Virtuous ROM: SuperCID and Firmware upgrade NOT needed?

The thread [GUIDE] A must read for those noobs who want to enjoy ICS states that ALL ICS roms need a firmware upgrade.
However, the installation instructions for the Virtuous ROM doesn't say anything at all about upgrading the firmware: http://www.virtuousrom.com/p/documentation.html
Which one is right?
Also, just to be on the safe side, is SuperCID needed?
The documentation page you linked is installation instructions for all Virtuous ROMs, so it's pretty generic. If you look at the description page for Virtuous Inquisition, which is ICS-based, the page does mention firmware. That ROM is based on the most recent 3.32 firmware, which is probably what you want to use. AFAIK, all ICS ROMs require firmware version of 3.12 or greater.
As for SuperCID, I think there are firmware downloads on the forums now that don't require it but it's also pretty easy to do.
pyrilium said:
The documentation page you linked is installation instructions for all Virtuous ROMs
Click to expand...
Click to collapse
Ahhh. Ok. That was the missing link. Thanks.
I have a rooted S-OFF Sensation 4G with the stock ROM and ClockWork. So all I need to do is:
Flash the Firmware that doesn't require SuperCID
Nandroid Backup / Wipe
And then I can flash Virtuous.
Is that correct?
Also, does flashing Firmware alone cause a wipe?
That is correct, although I would do your nandroid backup before you flash the firmware. I'm not sure that it will wipe the system partitions, but it might.
The only other thing is that it can be a pain to get back into recovery after you flash the firmware if you're not using adb, since whenever you boot into the boot loader it will detect the firmware (PG58IMG.zip) on your SD card and ask if you want to flash it. One solution is to remove PG58IMG.zip from the SD card using an SD reader after you do the firmware update, but if you have adb installed & working you can also simply issue the command "adb reboot recovery" when the phone is off. This won't work when you're in the bootloader, although there's probably an equivalent fastboot command.
pyrilium said:
That is correct, although I would do your nandroid backup before you flash the firmware. I'm not sure that it will wipe the system partitions, but it might.
The only other thing is that it can be a pain to get back into recovery after you flash the firmware if you're not using adb, since whenever you boot into the boot loader it will detect the firmware (PG58IMG.zip) on your SD card and ask if you want to flash it. One solution is to remove PG58IMG.zip from the SD card using an SD reader after you do the firmware update, but if you have adb installed & working you can also simply issue the command "adb reboot recovery" when the phone is off. This won't work when you're in the bootloader, although there's probably an equivalent fastboot command.
Click to expand...
Click to collapse
Wow, this is extremely helpful, thank you. One other thing: does it matter what version of ClockWork I'm using? (I rooted/did S-Off a loooooong time ago.)
Glad I can help!
I don't know whether the version of CWM matters. I doubt it would, other than maybe making a nandroid backup in a format other than current, but it's not that hard to update the recovery either.
I actually started using 4ext recovery recently, and I like it a fair bit better than CWM. It's something like $2.00 on the market, but includes a userspace application that lets you do things like set up a series of recovery operations (i.e. make backup, wipe, flash a set of zips) and then reboot into recovery to run them.
Perfect, thanks. I'll give this a shot.
Every few weeks I look up how to move to ICS but then lose my enthusiasm once I see all the things I'd have to do to switch haha. But today I noticed that Virtuous doesn't need some of those steps
One more question: SuperWIPE is unnecessary for Virtuous Inquisition correct? I see that it is necessary for Android Revolution, but I just wanted to make sure.
I've always seen superwipe recommended as part of the upgrade process from GB to ICS. It might not be required for Virtuous, but I don't see why you'd want to avoid it. The flashing process *will* wipe your phone - you want to use something like Titanium Backup to backup/restore app states if that's a problem - and performing the superwipe takes almost no time.
Woohoo! Successfully upgraded from stock Gingerbread (rooted & S-Off) to Virtuous Inquisition ICS! I wrote down what I did, so if anyone is interested, below is how I did it. It took about 15 minutes in total (not including the backups). Hopefully it helps someone else out there!
Titanium Backup all apps
Nandroid Backup via ClockWork Recovery (1434 MB)
Get CID Version:
Download ADB/Fastboot files from attachment from Post #1 of the [Firmware][Mar 12] thread
Connect phone to PC -> adb reboot bootloader -> Then in bootloader:
fastboot getvar cid: T-MOB010
fastboot getvar mid: PG5810000
fastboot reboot
Download the appropriate Firmware from above thread (CTRL+F for T-MOB010/PG5810000) and the Virtuous ROM from Virtous Website
Copy both files to sdcard, check md5 on both
Flash Firmware:
Turn phone off -> Hold Volume-Down + Power to enter bootloader
Wait for the firmware package to be found and confirm to update as prompted
Once completed successfully and asks you to reboot, pull the battery out. (Gingerbread & firmware are incompatible, causes bootloops)
With phone off and plugged into PC, do adb reboot recovery (Thanks pyrilium!)
Mount USB storage
Use PC to delete firmware file from sdcard
Wipe all data and cache -> Flash Virtuous -> Reboot
(Note that YES, flashing firmware causes bootloops -- as I found out! So firmware and ROM must both be flashed together.)
And thanks pyrilium for the note about using "adb reboot recovery" while the phone is off! I would have never figured that you could issue adb commands with your phone off. That tip isn't even in any of the guides, so thanks for that! Extremely helpful.
Anyway, hope that helps others out there. And thanks for helping me!

[Q] Paranoid noob question regarding S-off and previous Bootloader

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.

[Q] SD card appears as only 48MB. how come?

Hi, seems like my One S's sdcard partition has corrupted. been using TWRP 2.500 and recently upadted to 2.6.30 to use the new Maximus Rom. During the rom installation, I wiped the sdcard sectrion by mistake so I couldn't get to flash the zip file, then, I've tried multiple times of recovery.img flashings via RUU mode or on the bootloader screen. Finally when I got the TWRP recovery mode again, it says the sdcard folder only accepts 48 MB so I cannot push any custom roms since they are bigger than 500MB... Any ideas? Should I send it to the repair shops? Please Help!! Thank you!
FYI, my phone was
Tampered, Unlocked, S-off
also, when I press mount button on TWRP, this list appears
Cache
Data
Internal SDcard
System
USB-OTG
but I select Internal SD, the computer says the removable disk has only 48MB of available space.(I wiped it multiple times!)
puwa said:
Hi, seems like my One S's sdcard partition has corrupted. been using TWRP 2.500 and recently upadted to 2.6.30 to use the new Maximus Rom. During the rom installation, I wiped the sdcard sectrion by mistake so I couldn't get to flash the zip file, then, I've tried multiple times of recovery.img flashings via RUU mode or on the bootloader screen. Finally when I got the TWRP recovery mode again, it says the sdcard folder only accepts 48 MB so I cannot push any custom roms since they are bigger than 500MB... Any ideas? Should I send it to the repair shops? Please Help!! Thank you!
FYI, my phone was
Tampered, Unlocked, S-off
also, when I press mount button on TWRP, this list appears
Cache
Data
Internal SDcard
System
USB-OTG
but I select Internal SD, the computer says the removable disk has only 48MB of available space.(I wiped it multiple times!)
Click to expand...
Click to collapse
Omg. Why the people dont read op before they are going to flash new Rom. Just follow the instructions.
Sent from my HTC One S
tominozh said:
Omg. Why the people dont read op before they are going to flash new Rom. Just follow the instructions.
Sent from my HTC One S
Click to expand...
Click to collapse
Could you please tell me at least it's repairable or not? I want your help..
Also, I wonder what part I missed so it happened...hmm
puwa said:
Could you please tell me at least it's repairable or not? I want your help..
Also, I wonder what part I missed so it happened...hmm
Click to expand...
Click to collapse
Yes, don't sweat it. It is repairable.
It's hard for my to tell what you missed, because you didn't write what you did. So just follow installation instructions in the first post of maximus Rom. (flash new firmware, modified recovery, then Rom).
Sent from my HTC One S
tominozh said:
Yes, don't sweat it. It is repairable.
It's hard for my to tell what you missed, because you didn't write what you did. So just follow installation instructions in the first post of maximus Rom. (flash new firmware, modified recovery, then Rom).
Sent from my HTC One S
Click to expand...
Click to collapse
thank you! so, for flashing a new firmware, what would be a good firmware to start? any recommendations? i tried the firmware.zip in the install kit but not worked. same 48MB limit on the /sdcard/. any ideas?
:laugh:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
gelo01 said:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
Click to expand...
Click to collapse
GRT!! Thanks so much for saving my LIFE!!
gelo01 said:
Just follow this. It worked for almost all of us..
http://forum.xda-developers.com/showthread.php?p=45621060
Click to expand...
Click to collapse
All of these steps work for me except flashing the recovery as a ZIP. I get the wrong CID error (code 42 if i remember correctly). Thing is, I flash the .img directly usign fastboot flash recovery and that works but then the install process says, in android, transfer ROM. At this point, I don't have access to the SD card and the ROM is not in my sd card (it was wiped anyway?)
*EDIT*
Ok I changed my CID to 1111111 and now it works to flash the firmware. I still get partitions errors it seems though.
What I did is flash the stock recovery, clear storage, factory reset, reflashed the firmware given in Maximus thread, then the TWRP given and still, I get problems with my sdcard not mounting?
GabeyC said:
All of these steps work for me except flashing the recovery as a ZIP. I get the wrong CID error (code 42 if i remember correctly). Thing is, I flash the .img directly usign fastboot flash recovery and that works but then the install process says, in android, transfer ROM. At this point, I don't have access to the SD card and the ROM is not in my sd card (it was wiped anyway?)
*EDIT*
Ok I changed my CID to 1111111 and now it works to flash the firmware. I still get partitions errors it seems though.
What I did is flash the stock recovery, clear storage, factory reset, reflashed the firmware given in Maximus thread, then the TWRP given and still, I get problems with my sdcard not mounting?
Click to expand...
Click to collapse
if you are talking about mounting usb storage in recovery, then no, you cannot do that on Maximus HD rom. (it's a modified TWRP to work on the new firmware)
You can sideload in TWRP or ADB push the rom to your sdcard.
I would give you a link to a page describing it, but search is unavailable right now, have to try later.
But just search that thread with keyword sideload. There you will find the exact commands to load the rom onto your sdcard.
tivofool said:
if you are talking about mounting usb storage in recovery, then no, you cannot do that on Maximus HD rom. (it's a modified TWRP to work on the new firmware)
You can sideload in TWRP or ADB push the rom to your sdcard.
I would give you a link to a page describing it, but search is unavailable right now, have to try later.
But just search that thread with keyword sideload. There you will find the exact commands to load the rom onto your sdcard.
Click to expand...
Click to collapse
Yea, that's exactly what I ended up doing... it's not clear on any thread though...
Thanks
I went back to CM, didn't like maximus so much and it didn't fix my EDGE only problem so
It went back to 48mb
Hi i had the same problem with my htc one s.So i paniced and for some reason i put s-on(I deleted the os from the pc using mount storage) I managed to fix it by installing the recovery as zip. Then i tried to adb sideload a rom but it didn't work. So i went to boot loader then to fast boot and did fastboot flash zip Energyrom.zip. That gave me an error so i went back to recovery to try to side load the rom again, but my sdcard went back to 48mb.I reflashed the recovery (the one from install package) same thing . What do i do????? I need help asap i want my phone back (IM ONLY 12) Please reply asap.
cyberusman said:
Hi i had the same problem with my htc one s.So i paniced and for some reason i put s-on(I deleted the os from the pc using mount storage) I managed to fix it by installing the recovery as zip. Then i tried to adb sideload a rom but it didn't work. So i went to boot loader then to fast boot and did fastboot flash zip Energyrom.zip. That gave me an error so i went back to recovery to try to side load the rom again, but my sdcard went back to 48mb.I reflashed the recovery (the one from install package) same thing . What do i do????? I need help asap i want my phone back (IM ONLY 12) Please reply asap.
Click to expand...
Click to collapse
I think the easiest way is to flash the stock recovery and then do a sdcard wipe then a factory reset.
After that, you go through the process as described in the maximus rom thread, you will have to flash with sideload. That should work afterward
I am doomed
Hi guys,
Yesterday I decided to try MaximusROM 10.0.0 HD on my HTC One S, which is s-OFF and with superCID. The problem is: I didn't flashed first the rom as it was said, and I just used the Installation Package, installing directly the firmware.zip and the modified recovery. I tried to follow the steps written before, but now my phone works with the stock rom but it says that there are only 48mb in sd card, and that means that I can't even take photos, because I have no memory left. I found out that my phone, when is booted up, in settings says that I have 15,96GB of space for applications. What can I do?
GabeyC said:
I think the easiest way is to flash the stock recovery and then do a sdcard wipe then a factory reset.
After that, you go through the process as described in the maximus rom thread, you will have to flash with sideload. That should work afterward
Click to expand...
Click to collapse
I think I need to to that process my sdcard appears to be 10 gig only. Do you have a link for stock recovery? mine is S4.
48 mb storage = new 3.16 firmware
fix = flash custom 2.6.1 twrp
Sent from my HTC One S using XDA Premium 4 mobile app
lost sd card 48mb
Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48
help
dcvc said:
Hi I have big problem with my HTC one s I decided to install maximus hd but I need super cid and s-off facepalm metod everything I do original cid cange to 1111111... Get s-off acses and and install Rom then firmware and when Rom but Rom loads very slowly and sometimes
Black screen and not won't load Rom. And I decided to back s-on and back to original CID HTC_111 and install tricdroid beta 10.0 and then my sdcard 48mb. I try everything flash stock recovery delete all data and wipe but still 48mb try changing a few recovery cmrecovery all types and Twrp recovery but work one prefect Twrp 2.6.1.0 this recovery show me 12gb but I installed Rom on pc 48 I try again flash firmware from maximus hd but failed bicose I change my cid and back to s-on then. I try to go to s-off and change my cid to 11111111.
Noting happen my cid still htc_111 I can't do s-off my hboot is 2.16.0000 I read this forums I find many solutions but no-one don't help my. Try install three roms trickdroid magiobeta and source v14 still 48 I just want get my sd card please somebody. I try many thing relock boot loader try with ruu but still 48
Click to expand...
Click to collapse
Someone may be help me with this trouble :crying::crying::crying::crying::crying::crying::crying::crying::crying:
:crying::crying::crying::crying::crying::crying: Thanks for the help :crying::crying::crying::crying::crying:
same here what should we do i have managed to install magiorom but windows shows only 48mb all i want is to get back to stock but i messed up my cid i am on roger001 but i cannot find a correct rom as i have mi mid pj4010000 please help me get back to stock

Useless HTC Sensation

HI! Today I got an HTC Sensation from a friend and it was laggy due to it's stock rom with preinstalled apps and stuff, so I decided to move to a custom ROM, the first one which caught my eye was 5.0 CM12 from the development section, so I copied it to sdcard.
I have managed to unlock the bootloader through the htcdev site and then flashed the lasted CWM Recovery available, 5.8.0 and then formatted cache, data, system, dalvik, because that's what I've always been doing on my Galaxy S2, it was very straight forward.
But now, I can't install a custom rom, tried that one and the slim pyramid one, even a cyanogenmod rom but still no luck. It would abort the installation and output an error about filesystems which can't be found or it woudn't say nothing but will restart the phone straight to recovery mode.
Also, tried 4ext recovery and still no luck. At this point I started panicking and tried to resolve this by installing the stock rom, RUU.
Downloaded RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed , which is the perfect match for my phone but also fails to finish installation, telling me something about failed/unknown mounts/filesystem... If it will help, I will tell you exactly what the error is.
At this moment I have S-On in bootloader, and can't see any radio serial metioned at the top. Tried some instructions flashing PG58IMG.zip , but it doesn't seem to do anything.
Please, help me out because at this point my phone won't go anywhere but bootloader and recovery.
AKAndrew41 said:
HI! Today I got an HTC Sensation from a friend and it was laggy due to it's stock rom with preinstalled apps and stuff, so I decided to move to a custom ROM, the first one which caught my eye was 5.0 CM12 from the development section, so I copied it to sdcard.
I have managed to unlock the bootloader through the htcdev site and then flashed the lasted CWM Recovery available, 5.8.0 and then formatted cache, data, system, dalvik, because that's what I've always been doing on my Galaxy S2, it was very straight forward.
But now, I can't install a custom rom, tried that one and the slim pyramid one, even a cyanogenmod rom but still no luck. It would abort the installation and output an error about filesystems which can't be found or it woudn't say nothing but will restart the phone straight to recovery mode.
Also, tried 4ext recovery and still no luck. At this point I started panicking and tried to resolve this by installing the stock rom, RUU.
Downloaded RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed , which is the perfect match for my phone but also fails to finish installation, telling me something about failed/unknown mounts/filesystem... If it will help, I will tell you exactly what the error is.
At this moment I have S-On in bootloader, and can't see any radio serial metioned at the top. Tried some instructions flashing PG58IMG.zip , but it doesn't seem to do anything.
Please, help me out because at this point my phone won't go anywhere but bootloader and recovery.
Click to expand...
Click to collapse
install latest 4ext from here
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
the command is fastboot flash recovery recovery.img
then from 4ext format all partitions except sdcard
enable smartflash( because you are on S-ON)
flash the custom rom
note: enable smartflash exactly before flashing the rom
Thank you very much! I've managed to install SKimKAT now. But how can I get S-Off permanent? Also, I can't install the stock RUU firmware.
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed
It freezes on the "sending" stage for hours.
AKAndrew41 said:
Thank you very much! I've managed to install SKimKAT now. But how can I get S-Off permanent? Also, I can't install the stock RUU firmware.
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed
It freezes on the "sending" stage for hours.
Click to expand...
Click to collapse
see this guide
http://forum.xda-developers.com/showthread.php?t=2751187

Categories

Resources