Database Info

RUU Updates HTC: BE CAREFUL

--- Updated and simplified
Updates from HTC are randomly released for countries and regions. These Update may lock your phone. As of today, phones can be unlocked again by using the GOLDCARD approach. However, there is a much simpler way to prevent bad things from happening:
If you like flashing HTC roms and have no intention to lock your phone, follow these steps:
On the PC
1. Double Click the .exe from the update. Wait for the first window to appear (DO NOT CONNECT YOUR PHONE). Don't close the application but do not continue
2. Open explorer and navigate to the hidden directory:
Windows 7: \users\$username$\AppData\Local\Temp\... followed by something like ...\{2A3DF7FC-1693-4C53-8883-6CF09DED700D}\...
Vista: documents and settings\.....
3. You should find the install application files along with a file "Rom.zip" (40 to 90 Megs)
4. Extract the ROM.zip to your SDK Tools directory, where fastboot.exe resides
5. open command shell and navigate to your Tools directory (supposing SDK, adb and fastboot are installed)
On the Phone
6. Enter recovery console on phone (press "home" + then "on")
7. Do a nandroid backup
8. Select Wipe your phone
9. Hold "back" and select "reboot system" in recovery to enter Fastboot mode
On the PC
10. Type: "fastboot flash boot boot.img" .... wait to complete
11. Type: "fastboot flash system system.img" .... wait to complete
12. Type: "fastboot flash userdata userdata.img" .... wait to complete
13. [Optional] Type: "fastboot flash radio radio.img" .... wait to complete (note: some HTC radios locked windows mobile phones. I am not sure whether this applies for Android)
14. Reboot your phone
15. Keep the update if you like it, revert to backup via recovery and nandroid in case you don't
And sorry for any confusion caused...
Regards,
fde

Thanks a lot mate... I will try the official sense for my magic then using this method first =D...

Are you sure....
That this will work? I have made the RUU Flash: RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_Nordic_release_signed_NoDriver
And that resulted in:
HBOOT-1-33-0014
CPLD-12
RADIO-3-22-23-18
I don't understand what you are meaning about the Radio.img file.
And what about the HBOOT file?

Yes it works. Just verfied it aigain. What the RUU package does is:
1. Extract the application to a temp file
2. Use ADB to flash the ROM to your phone
By the approach described in the first post, the application unpacks itself into a temp directory. This allows you to access the ROM-File which is stored as ROM.zip or something similar. By moving only the vital Boot, System and Userdata, you avoid flashing your Recovery console or Bootloader (Hboot).
It implies of course, that you DO NOT continue with the RUU application as soon as the first window becomes visible. (I will adjust the above Tutorial and make it simpler).

Problem
But the problem is that I allready have flashed my phone, is this the way to revert is så I can root it again and put custom roms on it again?

same here
ZeaDK said:
But the problem is that I allready have flashed my phone, is this the way to revert is så I can root it again and put custom roms on it again?
Click to expand...
Click to collapse
I also want to know how I can flash new ROM since people said that my spl is perfected after upgrading
I was learned that we need to use goldcard method to root again.
In our case, any idea which ROM to use as we gotta use higher ROM?
Or are we able to gain root access without touching the existing ROM?
Now even cannot boot to recovery mode.
So stupid to upgrade it although the ROM is stable and fast but no root access sucks.
any help would be appreciated.
thanks,
thihaz

Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde

feicher said:
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
Click to expand...
Click to collapse
The problem with the goldcard method is that you lose the roms as well...

Sir, would you please let me know how to flashing engineering SPL, right now i have HBoot-1.76.007 which shipped with the Singapore HTC sense rom.
BTW: i don't care i will lose the rom or not.
Many thanks!
I flashed using RUU_Sapphire_HTC_Asia_WWE_2.16.707.3_SG_release_signed_NoDriver.exe with golden card, but got "check main rom verion" error msg.
then flashed using RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe with golden card, same error msg again.
I really have no idea how to flash back to engineering SPL, i'm stuck in Singapore HTC sense rom.
feicher said:
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
Click to expand...
Click to collapse

i got 1 rom.zip(11mb) & another one rom1.zip(89mb).
But both I also can't unzip. Any idea? Thanks.

radonsg said:
i got 1 rom.zip(11mb) & another one rom1.zip(89mb).
But both I also can't unzip. Any idea? Thanks.
Click to expand...
Click to collapse
I did this twice on a Swiss Update, which btw wasn't worth applying. Just by the Size it's rom1.zip.
Let me download the Singapore and see what I can do.... But then looking at the guys post it seems the second file in the post is what you need. Download this package and only flash boot, system and data in fastboot mode. (From Step 4. onward in the guide). Anyway I will have a look.

phygee said:
Sir, would you please let me know how to flashing engineering SPL, right now i have HBoot-1.76.007 which shipped with the Singapore HTC sense rom.
BTW: i don't care i will lose the rom or not.
Many thanks!
I flashed using RUU_Sapphire_HTC_Asia_WWE_2.16.707.3_SG_release_signed_NoDriver.exe with golden card, but got "check main rom verion" error msg.
then flashed using RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe with golden card, same error msg again.
I really have no idea how to flash back to engineering SPL, i'm stuck in Singapore HTC sense rom.
Click to expand...
Click to collapse
Please follow the GOLDCARD method. I am not a recovery expert. I try to be cautious and was lucky until now (so I never tried it myself, but it is reported to work). Sorry for that. If :No-Frost: knows of a better guide with regard to GOLDCARD, please post!
Regards,
fde

feicher said:
Please follow the GOLDCARD method. I am not a recovery expert. I try to be cautious and was lucky until now (so I never tried it myself, but it is reported to work). Sorry for that. If :No-Frost: knows of a better guide with regard to GOLDCARD, please post!
Regards,
fde
Click to expand...
Click to collapse
For now the only method I know is the goldcard one... But in my country, using the goldcard method, makes the magics lose the 3g, edge or any internet mobile connection... =(...

Be careful, by using this method you can not upgrade to Snese UI (example TW). The reason being system image in Sense UI is larger than the previous 1.5 ROM system image, so system partition needs to be re-sized, which the RUU update does it for you. Otherwise you are struck with failed system image flashing.

signiture verifiaction fail
I get a signiture verifiaction fail when trying to write the .img files using fastboot. Any suggestions?

[Q] Nexus S stuck on Google logo and unlock bootloader screen

I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T

I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!

May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk

RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock

Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk

Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk

RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!

RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot

Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)

surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it

Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!

I'll try today, but my problem is that adb cannot find the device, fastboot can

I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip

I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>

Is the problem solved？

szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped

Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...

If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.

any other suggestion? I'm out of ideas

I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.

[SOLVED] Soft Brick... Can't install ROMS and pushing does not work.

First of all I decided to install CM10 without making a backup on TWRP 2 (clever Kyle). Then when it was stuck on the bootanimation for about an hour, I got annoyed and looked through the forums for help. "Factory reset, clear caches before installing etc" So I deleted the ROM, factory reset via TWRP, deleted both cache and then tried to install CM10. Failed.
Then I tried to mount the SD card to my computer to try to find other ROMS to install. Viper and Energy both failed. I then tried CM10, Viper and Energy with CWM 5.8, and the installation of all gets aborted almost instantly, which I am guessing means that it failed on there as well. I then tried ADB, and pushing keeps failing. Does anybody have any ideas at all on how to get just any ROM onto the phone so that I can get the official 4.1 update again (my phone was on 4.1 before trying CM10, so the HBOOT is most likely 4.1 as well). Any advice would be greatly appreciated, because having a £350 paperweight is not what I particularly want, especially considering I have another 9 months contract to run and no spare phone on the same network as my current contract.

kylepont said:
Any advice would be greatly appreciated
Click to expand...
Click to collapse
When you say that installing ROMs fails and adb pushing fails, you should tell us what error messages you get.
If you can still get into bootloader, you're probably going to be fine.
First, check that you can mount your sdcard in recovery. I don't mean mount onto your PC over USB, but just mount the sdcard partition onto the root filesystem.
If you can not get into recovery, re-flash one.
If recovery can not mount the sdcard, then you have to go to the sticky on how to fix unmountable sdcard. It involves flashing a stock recovery and then clearing storage from bootloader.
If your recovery is good and your sdcard is mountable, adb pushing should work. If it doesn't, post error messages. Make sure your sdcard is mounted before you try to push fils to it.
In recovery, format system, data, cache, but not sdcard. Then flash a zip. Then boot back into bootloader/fastboot and fastboot flash the boot image that comes with the rom. (Did you do this last step when flashing other roms?)
If this does not work not for you, describe in detail what you do and what you see. If it does work out, I suggest you make a nandroid backup so you can get back to this state, and S-off the device.
-Jobo

touch of jobo said:
If this does not work not for you, describe in detail what you do and what you see.
Click to expand...
Click to collapse
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update

Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Click to expand...
Click to collapse
Have you flashed the boot.img?
fastboot flash boot boot.img
Sent from my One S using Tapatalk 2

usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img
Click to expand...
Click to collapse
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?

kylepont said:
Sometimes a print screen can speak louder than words.
Click to expand...
Click to collapse
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Edit:
kylepont said:
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
The flashing instructions for your ROM will likely state that you have to 'flash the boot image (or boot.img or kernel) in fastboot before booting into the rom.
You can find a file named 'boot.img' inside your rom zip. You have to flash that in fastboot. You can do it before or after flashing the rom, but you must do it before booting into the rom.

kylepont said:
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img/QUOTE]
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
Extract the boot.img file from the ROM. Place it in your adb folder. Boot into bootloader, select fastboot and connect to PC. Type command fastboot flash boot boot img
Click to expand...
Click to collapse

touch of jobo said:
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Click to expand...
Click to collapse
All the boxes are ticked on the TWRP Mount screen, including System and SD card. And yes, I did make sure that it is:
1) in the same folder as the adb
2) called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
And usaff22, does that involve unzipping the ROM that I am using?

Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...

kylepont said:
I did make sure that it is [...] called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
Click to expand...
Click to collapse
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
kylepont said:
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
Click to expand...
Click to collapse
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Also, does it say anything interesting when it fails?
Before flashing the zip, did you format your system, data, cache partitions?

EDIT: After repeatedly trying to adb push, I finally got CM10.zip.zip onto the phone. Flashing took a bit longer than last time, but booting took no time at all. Thank you touch of jobo and usaff22, your advice was a lot of help.
touch of jobo said:
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
Click to expand...
Click to collapse
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
touch of jobo said:
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Click to expand...
Click to collapse
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
touch of jobo said:
Before flashing the zip, did you format your system, data, cache partitions?
Click to expand...
Click to collapse
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder

kylepont said:
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
Click to expand...
Click to collapse
I can't help with that adb error. Never seen it. Try searching the forums for it. Sorry. Also, I don't use Windows, so I don't know about driver versions and things.
kylepont said:
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
Click to expand...
Click to collapse
TWRP and CWM are both fine for flashing ROMs, just not this specific version of TWRP. Since I dont use it myself, I dont know the exact version numbers, but read around a bit and you'll find what worked for others.
Maybe flashing a different recovery will even get rid of your protocol error.
If you've made nandroid backups (I guess you havent or we wouldnt be here.. sorry) you should stay with the same recovery (same 'brand', not same version) or you can't restore them.
kylepont said:
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
Click to expand...
Click to collapse
The CM10.zip should be on your sdcard, not your system partition. You dont need the boot img at all on your device. You need it on your PC in order to fastboot flash it.
Before flashing a ROM you should wipe your 'system', 'data', and 'cache' partitions, but not your 'sdcard' partition. Only if you flash (a newer version of) the same ROM you have operational, then you can sometimes flash without wiping. This is called 'dirty flashing'. But this does not apply in your case.

Successful flash of CyanogenMod, thanks for the help.
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.

Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Click to expand...
Click to collapse
I would rename the zip to something else like sense.zip, place it on the desktop and do adb push C:\Users\username\Desktop\sense.zip /sdcard/
Make sure you use backward slashes for the PC file location, and forward slashes for the phone paste location.
This way we are also providing the full path on the PC.
Also make sure you use the latest adb from the SDK website. You don't need the whole thing, just the platform-tools bit, and replace the files in the new folder with the old one.
Sent from my One S using Tapatalk 2

Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.

kylepont said:
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
Click to expand...
Click to collapse
You might be able to find an RUU lying around on one of the websites which give RUUs such as androidfiles.org/ruu
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.

kylepont said:
the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required)
Click to expand...
Click to collapse
You can extract the recovery image from any RUU or OTA. Recoveries do not depend on carrier.
But .. if you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.

touch of jobo said:
If you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
Click to expand...
Click to collapse
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
usaff22 said:
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
Click to expand...
Click to collapse
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.

kylepont said:
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
Click to expand...
Click to collapse
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
kylepont said:
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
Click to expand...
Click to collapse
This is the thread: http://forum.xda-developers.com/showthread.php?t=1671643
It involves extracting, hex-editing, and flashing a critical part of your device. If you make the slightest mistake you have a brick. However, if you read carefully and double check every step, it's not difficult. Many have done it. Read the thread.
Once you have supercid, you may as well get s-off as well. (This is the thread: http://forum.xda-developers.com/showthread.php?t=2155135 ) That way you can always flash anything.
Whatever you decide to do, before you start on anything, read all the instructions to the end, so that you're sure you can complete the process before you start. Also, before you start any process, try to understand what each step does and why it is necessary. That may involve a lot of reading and searching, but that is a Good Thing in the end.

touch of jobo said:
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
Click to expand...
Click to collapse
It is unmountable. I tried CWM and TWRP to no avail. Also, I have HBOOT version 2.15 which I heard is a bugger to work with. Also, I got the ZIP file for the stock 4.1, and I read that the stock recovery is in the firmware folder, but I cannot access it. (https://www.dropbox.com/s/kyn9sb5x7gpd7fr/Picture2.png) Then, I tried to get to the CID, following the instructions that you gave me, and I didn't get very far (https://www.dropbox.com/s/g6ik0i3los7unde/Picture3.png)

[Q] reverting from custom kernel to stock?

sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!

Download the relevant kernel to your device from here.
Reboot to recovery
Install the zip you just downloaded
This stuff tends to be a lot simpler than you'd expect, tbh.

dallas220 said:
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Click to expand...
Click to collapse
Download the factory images from Google : https://developers.google.com/android/nexus/images#hammerheadkot49h
Extract the boot.img and flash it via fastboot.. (fastboot flash boot boot.img)
Make sure your on stock rom before you flash it..
Sent from my Nexus 5 using Tapatalk

dallas220 said:
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Click to expand...
Click to collapse
Fastboot, you flash with fastboot and yes the kernel image is boot.img. You should probably also reflash your ROM (system.img if you're on the stock ROM) as many custom kernels also modify the system partition.

BirchBarlow said:
Fastboot, you flash with fastboot and yes the kernel image is boot.img. You should probably also reflash your ROM (system.img if you're on the stock ROM) as many custom kernels also modify the system partition.
Click to expand...
Click to collapse
Thanks for all the replies guys!
I am indeed on stock rom. To flash the system.img is pretty much the same as the boot.img yes?

dallas220 said:
Thanks for all the replies guys!
I am indeed on stock rom. To flash the system.img is pretty much the same as the boot.img yes?
Click to expand...
Click to collapse
Hi,
Same way: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.

Hammer_Of_The_Gods said:
Hi,
Same way: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Click to expand...
Click to collapse
Thank you brother
And just to add to my noobness.. Returning to stock kernel and or rom doesn't wipe any files on the phone correct? Ie picture data etc....?

dallas220 said:
Thank you brother
And just to add to my noobness.. Returning to stock kernel and or rom doesn't wipe any files on the phone correct? Ie picture data etc....?
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, you are fine!
If you are using the flashall script then remove the -w flag and you're good to go!
Sent from my Nexus 5 using Tapatalk

vin4yak said:
As long as you don't flash the userdata.img, you are fine!
If you are using the flashall script then remove the -w flag and you're good to go!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I plan on flashing sys and boot!
And so sorry but what do you mean the flashall srcipt?
Would that be basically flashing everything to stock?
Sorry for such dumb questions

dallas220 said:
I plan on flashing sys and boot!
And so sorry but what do you mean the flashall srcipt?
Would that be basically flashing everything to stock?
Click to expand...
Click to collapse
So no worries since you don't flash all (you use the "Method2" from the link I posted above), about the "flash-all.sh" file, when you open the factory image file, you have this script, more info here about the "-w" to delete: http://forum.xda-developers.com/showpost.php?p=51949577&postcount=4.

Hammer_Of_The_Gods said:
So no worries since you don't flash all (you use the "Method2" from the link I posted above), about the "flash-all.sh" file, when you open the factory image file, you have this script, more info here about the "-w" to delete: http://forum.xda-developers.com/showpost.php?p=51949577&postcount=4.
Click to expand...
Click to collapse
thanks for you help my brother. Just another question.. If I have a nandroidbackup on the computer that I made before I installed my custom kernel, could you somehow use that to get back to the stock kernel? Is that something...or I am just asking the most ridiculous questions?
It seems the more I read, the less I am confident with adb, flashing, backups etc.... :S

dallas220 said:
thanks for you help my brother. Just another question.. If I have a nandroidbackup on the computer that I made before I installed my custom kernel, could you somehow use that to get back to the stock kernel? Is that something...or I am just asking the most ridiculous questions?
It seems the more I read, the less I am confident with adb, flashing, backups etc.... :S
Click to expand...
Click to collapse
If want the stock kernel download the factory images from google and flash the boot.img via fastboot. That's the easiest way.
If you still want to use nandroid backup then copy the nandroid backup to the correct location... Head over to Philz Touch recovery and use the custom restore option by which you can select only the "boot" and "system" partition. But I haven't tried doing it so can't say whether it will work or not. However, technically it should work. I have no idea how to do this using TWRP though as I haven't used it much.

Please help: How to return htc u11 to stock

Hi guys,
My phone now is on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
What are the steps to return the htc u11 to stock please?
The original software number of my phone is: 1.11.400.4
EDIT: I went to: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
& downloaded stock recovery & nandroid TWRP backup (for 1.11.400.4).
However, I couldnt flash that nandroid TWRP from TWRP recovery.
Long story short, I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!

dsymbol said:
Hi guys,
What's the process of returning the htc u11 to stock please?
Googling doesn't give me much result.
Long story short but I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!
Click to expand...
Click to collapse
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.

purple patch said:
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.
Click to expand...
Click to collapse
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks

dsymbol said:
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik. I'm more of a trial and error guy lol. Read guide pages to know for certain, check HTC 10 guides, same steps.

purple patch said:
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik.
Click to expand...
Click to collapse
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch

dsymbol said:
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch
Click to expand...
Click to collapse
Get the one from here and follow instructions. That's what the thread is for. https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048. Sorry i don't have time to do the leg work for you (i'm out atm), but it's all there.

download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814

Use the ruu, you might need the HTC drivers but in the future never not make a backup, 15 mins could save u a major headache

AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
I'm downloading it now & will report back very soon.
Thanks for the tip AllGamer!!!

AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you

dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
If you don't have an external SD.
1. Lock your bootloader.
2. Boot to download mode.
3. Open a cmd window and run the below commands.
fastboot orm rebootRUU (hit enter)
fastboot flash zip (drag the zip into the cmd window then hit enter)

dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.

AllGamer said:
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.
Click to expand...
Click to collapse
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4

LeeDroid said:
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
Click to expand...
Click to collapse
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now

dsymbol said:
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now
Click to expand...
Click to collapse
Added an extra step incase you don't have an external sd

dsymbol said:
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4
Click to expand...
Click to collapse
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227

michaelbsheldon said:
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227
Click to expand...
Click to collapse
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4

LeeDroid said:
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4
Click to expand...
Click to collapse
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice

dsymbol said:
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice
Click to expand...
Click to collapse
adb reboot download
fastboot oem lock

LeeDroid said:
adb reboot download
fastboot oem lock
Click to expand...
Click to collapse
Confirmation number: 5G354245BV234401U