Database Info

[Q] Getting back to stock from unlocked bootloader

I unlocked my MT4GS's bootloader a few months ago using HTC's tool, but I now find myself in a place where I need to reflash a stock ROM due to miscellaneous malfunctions. It's not for warranty/damage, I tried to restore my ROM to factory settings and couldn't due to removing the Sense UI for ADWLauncher. I tried to reflash my ClockWorkMod stock ROM backup, but it had a MD5 mismatch (and, sadly, was deleted accidently last night in organizing my SD card).
I am on an unlocked bootloader with S-ON RL showing on the boot screen. I have tried downloading one of the SG59IMG.zip files (both the latest 1.63 release, and the 1.55 release), but those do not work. I place them on my SD Card's root and allow HBOOT to find them, but it reports "Wrong ZIP!". I've read that re-locking my bootloader will fix this; any confirmation?
At this point, what I really want to do is get my phone back on a stock ROM, with or without ClockWorkMod, and start over again with the rooting process. As I said, this isn't for warranty service; I want to make sure I have a good stock recovery image available and that I have a solidly working phone while I wait for an ICS ROM that's stable for everyday use to come around.
Thanks in advance for any help.

WinterHalliwell said:
I unlocked my MT4GS's bootloader a few months ago using HTC's tool, but I now find myself in a place where I need to reflash a stock ROM due to miscellaneous malfunctions. It's not for warranty/damage, I tried to restore my ROM to factory settings and couldn't due to removing the Sense UI for ADWLauncher. I tried to reflash my ClockWorkMod stock ROM backup, but it had a MD5 mismatch (and, sadly, was deleted accidently last night in organizing my SD card).
I am on an unlocked bootloader with S-ON RL showing on the boot screen. I have tried downloading one of the SG59IMG.zip files (both the latest 1.63 release, and the 1.55 release), but those do not work. I place them on my SD Card's root and allow HBOOT to find them, but it reports "Wrong ZIP!". I've read that re-locking my bootloader will fix this; any confirmation?
At this point, what I really want to do is get my phone back on a stock ROM, with or without ClockWorkMod, and start over again with the rooting process. As I said, this isn't for warranty service; I want to make sure I have a good stock recovery image available and that I have a solidly working phone while I wait for an ICS ROM that's stable for everyday use to come around.
Thanks in advance for any help.
Click to expand...
Click to collapse
Get the stock recovery from the devs section, Change " SG59IMG.zip" to " PG59IMG.zip", relock the bootloader so that hboot will see the zip. I think the lock command is "fastboot oem lock". To unlock it again you would have to flash the unlock token again
Sent from my DoubleShot Lite using Tapatalk

ac3theone said:
Get the stock recovery from the devs section, Change " SG59IMG.zip" to " PG59IMG.zip", relock the bootloader so that hboot will see the zip. I think the lock command is "fastboot oem lock". To unlock it again you would have to flash the unlock token again
Sent from my DoubleShot Lite using Tapatalk
Click to expand...
Click to collapse
Whoops, it is PG59IMG already, just at work and wasn't in front of my phone at the time to confirm the file name. Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.

WinterHalliwell said:
Whoops, it is PG59IMG already, just at work and wasn't in front of my phone at the time to confirm the file name. Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.
Click to expand...
Click to collapse
Theres no other way that i know of sry
Sent from my DoubleShot Lite using Tapatalk

http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
That covers everything.

WinterHalliwell said:
... Is there a way to relock my bootloader without using the fastboot program from my computer? I've already uninstalled all of the HTC/ADB stuff to save processing power on my netbook and I'd like to avoid reinstalling it all if at all possible.
Click to expand...
Click to collapse
Ask and ye shall receive - I put together a package with the bare minimum you need to use ADB or fastboot. At about 736kb I think it's exactly what you were looking for.
(windows machine)
You don't need to install the entire SDK just to get the ADB or fastboot tools - all you need is what's here.
doubleshot_adb-fastboot.zip
Download Link
MD5: 47e72c0a2e2c1caaabd95b5df83e8913
Size: 736.03 KB
I also included a command prompt .bat file (Command.bat) so that when you unzip the archive to a folder, open that folder and double-click the Command.bat file and it will open you up to a command prompt already in the folder with the tools, wherever it is.
No more typing in some annoying CD command to get to the directory with the tools - simply open the folder (wherever it is at the time) and run Command.bat.
You will be ready to just dive right into ADB or fastboot commands (which is all you want, anyway, right?)
You will need the fastboot drivers for the doubleshot installed if they are not - get them here:
HTCDriver.exe
Download Link
MD5: 7fe1a01a816722718c6d369a3dc49166
Size: 13.08 MB
...and these are the same drivers that originally came on the SDcard of the doubleshot when you first got it. If you lost them, you can grab them again.
Enjoy!

OTA_Ville_U_TMOUS_1.84.531.2-1.53.531.16_release_2651973pm4j0bopq68v1g1.zip

Here is a link to the OTA. I didn't want to apply it till some smarter fellas could dig into it and see what kind of damage it does, so hopefully this will speed that process up a little.
Do not flash this .zip, it's for developmental purposes. I just made it available because I received the OTA on my phone this morning and did not see it posted yet.
https://docs.google.com/open?id=0B3QFSwNX3WR4VXpZcVR2M2NlQUU

Here's an alternative link if the above one fails or is too busy
http://db.tt/lLyptM9n
Sent from my HTC VLE_U using XDA

ozzie1p said:
Here is a link to the OTA. I didn't want to apply it till some smarter fellas could dig into it and see what kind of damage it does, so hopefully this will speed that process up a little.
https://docs.google.com/open?id=0B3QFSwNX3WR4VXpZcVR2M2NlQUU
Click to expand...
Click to collapse
Epic thank you sir

You guys rock!!!

EDIT: Sorry that sounded really NEWBish... I am unrooted and am currently having an issue re-unlocking my bootloader to root.
Is there an RUU available that I might be able to flash?

I wouldn't flash it until it gets sorted out what's in it. It looks like the firmware.zip has a new h-boot (hboot_8960_1.09.0000_20120402_signedbyaa.img) so if they've patched some holes that were in the old one then flashing this might screw you if they get s-off on the previous h-boot.......I think

Cayniarb said:
** this assumes that you have adb and fastboot in your PATH and that you know how to use them.
** this also assumes that you have some recovery.img file (named as such) saved in whatever directory you are running terminal commands from.
** this also assumes you are running linux. If all of the above conditions are met, the process should also be the same on Windows and OS X, but I have not tested that and cannot confirm that.
** this assumes that if you do not fully comprehend all of the above, that you will stop reading now. I am not responsible for any damage caused to your device by following these instructions.
Step 1: Find and download the following images from the 1.78.41.2 RUU: radio.img, wcnss.img, and adsp.img. Save them on your device's storage partition (/sdcard) named as listed here (** this assumes that if you use other names you also know how to adjust future commands).
Step 2: Boot your device into fastboot mode. Your choice of 'adb reboot bootloader' or manually powering down, booting to hboot, and selecting fastboot. (Future commands assume your device is plugged in to the computer at this point)
Step 3: On the computer, run: fastboot boot recovery.img
Step 4: Wait for your device to boot in to what looks like a normal recovery session. While it looks this way, it is not normal. In this recovery, you have the ability to do pretty much everything you can on an s-OFF device (flashing boot or other partitions, etc).
Step 5: This will depend on your recovery. Whatever the process is, make sure that your /sdcard partition is mounted (not mounting USB, but making the /sdcard partition readable to things like adb).
Step 6: On the computer, run:
adb shell
dd if=/sdcard/radio.img of=/dev/block/mmcblk0p17
dd if=/sdcard/wcnss.img of=/dev/block/mmcblk0p19
dd if=/sdcard/adsp.img of=/dev/block/mmcblk0p18
Step 7: In the same recovery session, on the device, flash whatever 1.78-based ROM you like (Note: I have not seen ill effects using this on a 1.53-based ROM, but YMMV).
Step 8: Reboot. Enjoy.
Click to expand...
Click to collapse
This is from the radio thread i would assume, that it will work the same way. All those files are included in the OTA zip file. Thoughts?

ozzie1p said:
I wouldn't flash it until it gets sorted out what's in it. It looks like the firmware.zip has a new h-boot (hboot_8960_1.09.0000_20120402_signedbyaa.img) so if they've patched some holes that were in the old one then flashing this might screw you if they get s-off on the previous h-boot.......I think
Click to expand...
Click to collapse
Right now I just want to get my damn bootloader unlocked and I cant seem to figure out what is going on with it. I've done this a million times so its not that I dont know what im doing like all the others have accused me of, its simply an issue that the unlock token flashes fine but upon rebooting the bootloader is still relocked. Its driving me mad right now... I just want to flash an T-Mo RUU to get back to stock at this point.

go to the official ruu thread by football and download the tmous ruu from there... put your phone into fastboot usb mode and start the ruu.

Will that RUU overwrite a newer H-Boot?

Radio 0.16.31501S.16_2_10.22.31501S.10L flashable zip here
Edit: Yes. This is from the update.

http://db.tt/W3l8QdGU
Another link just in case
Sent from my HTC One S

strker45 said:
go to the official ruu thread by football and download the tmous ruu from there... put your phone into fastboot usb mode and start the ruu.
Click to expand...
Click to collapse
I appreciate you trying to provide assistance. An RUU with a lower HBOOT will not overwrite a newer one so that option is not possible.
Thanks

how can this manually be applied? or is it even possible i know things have changed . but for w/e reason my phone still isnt seeing the ota and i've restored completely to stock with the offical ruu

Thanks guys, will try to update TrickDroid TMOUS ASAP

infinityhombre said:
Radio 0.16.31501S.16_2_10.22.31501S.10L flashable zip here
Click to expand...
Click to collapse
This is one version number short of the EU Radio.
Code:
EU Baseband Version: 0.16.31501S.17_2_10.23.31501S.10L
US Baseband Version: 0.16.31501S.16_2_10.22.31501S.10L

infinityhombre said:
Radio 0.16.31501S.16_2_10.22.31501S.10L flashable zip here
Click to expand...
Click to collapse
Did you pull this from the OTA?

Im kind of a noob here, how do i manually flash the OTA?

doktortaru said:
This is one version number short of the EU Radio.
Code:
EU Baseband Version: 0.16.31501S.17_2_10.23.31501S.10L
US Baseband Version: 0.16.31501S.16_2_10.22.31501S.10L
Click to expand...
Click to collapse
Makes me wonder if it's even worth updating to the US one. Seems like it'd be better to just use the EU radio.
There's one way to find out....

infinityhombre said:
Radio 0.16.31501S.16_2_10.22.31501S.10L flashable zip here
Click to expand...
Click to collapse
Thanks! Quick and easy

Radio Downgrade failure???

hey guys, i am trying to root my inspire. When i ran the Ace Hack kit, it gave me the error saying ...
********* Radio Downgrade failed ***********
** Either:
** Goldcard failed
** USB connections are not working 100
********* Radio Downgrade failed ***********
Press any key to continue . . .
i made sure the antivirus was disabled, removed apple software, 2 pcs, 2 sync cable and will be trying another SD card, but im stuck. Also i tried to boot in HBOOT but no luck either. The HBOOT screen came up but no luch on trying to load the img file. Please assist me if you can, Thanx

Probably an SD card that can't be used as a gold card. Get another SD and try again.
Sent from my Inspire 4G using xda premium

Gizmoe said:
Probably an SD card that can't be used as a gold card. Get another SD and try again.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I'm having the same problem. I've tried swapping the SD card. Any other ideas?

Same problem...
I already try to change the SD using another and format to FAT32, but result still same.
Is there any solution or any other method to continue rooting my phones with this state?
Appreciate for any comments

victasa said:
Same problem...
I already try to change the SD using another and format to FAT32, but result still same.
Is there any solution or any other method to continue rooting my phones with this state?
Appreciate for any comments
Click to expand...
Click to collapse
That is due to corrupted sdcard. Anyway, you can unlock the bootloader, flash a custom recovery and root without the Hack Kit (take into consideration that is has been discontinued as so has the files and support) Check my signature for doubts

glevitan said:
That is due to corrupted sdcard. Anyway, you can unlock the bootloader, flash a custom recovery and root without the Hack Kit (take into consideration that is has been discontinued as so has the files and support) Check my signature for doubts
Click to expand...
Click to collapse
OK, I try to unlock bootloader now. But I got stuck to this (same problem with other guy in this forum, but no lead):
My ROM Software Numbre is 3.13.707.4, and the RUU tool (PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe) displayed the same number. The option I was given was "Update the current ROM version." So I clicked update and it says "From Image Version 3.13.707.4 To Image Version 3.13.0.0". I clicked next to proceed. Then I get:
ERROR [190]: ROM IS NOT UPDATED
Your ROM version is not the latest version.
Please upgrade to 3.13.707.3 to apply this RUU to be able to unlock your bootloader. On your phone, go to Menu > Settings > About phone > Software updates > Check now. After you have updated, please run the RUU again to upgrade your HBOOT to unlock your phone. Click Exit to quit.
At this point I went back to the phone and performed the "check now", but there are no other updates.
I have google for this (ROM 3.34.707.3) but leads to nothing... no problem solving at all...
Stuck again now....

Updated :
Finally I can root my phone...
Problem described above, can be solved by update the Hboot version manually check this :http://forum.xda-developers.com/showthread.php?t=2252161
I can download update Hboot files from the link in there...
Then I continue with unlocking bootloader as describe in your signature (using easy unlock tools) then continue to flash CWM and SU using easy ace hack tools... Wow your tools is very easy to understand for a noob like me
Now, since i already have root access, it should be enough for me...
But just curious, how to gain S-Off access from here... I still not clear enough about S-off and S-On difference, what exactly advantages to have S-Off?

Please help me!
Hi Victasa:
Can you tell me how you solved this problem step by step?
I followed the link into your post, but I have a problem, I speak Spanish, and do not understand English well :crying:. Please can you tell me exactly how you did it?
Thank You

Decasys said:
Hi Victasa:
Can you tell me how you solved this problem step by step?
I followed the link into your post, but I have a problem, I speak Spanish, and do not understand English well :crying:. Please can you tell me exactly how you did it?
Thank You
Click to expand...
Click to collapse
Hi Decasys, follow this step :
*Unlock boot loader with htcdev/bootloader
see your HBOOT version : you face problem describe on this thread if your hboot ver is 2.00.0027 you have to download file as below to achieve version 2.00.0029 because it support token key for unlock.
1. download this rom copy to your c:\ drive : http://www.mobfirmware.com/dl/behtash/imei dhd/rom.zip
2. then download : http://www.mobfirmware.com/dl/behtash/imei dhd/dhd update hboot by behtash.rar
3. run hboot update by behtash.bat in normal mode ,waiting until flash hboot complete
at this point your HBOOT will be upgrade to 2.00.0029 (check it)
*Then continue to use :
Easy unlock tools, follow insctrution in this therad : http://forum.xda-developers.com/showthread.php?t=2133336
at this point, on your bootloader, it will have "unlocked" notification on the top
*Then continue to use :
Easy Ace root tools, on this thread : http://forum.xda-developers.com/showthread.php?t=2169515
When you run it, just choose to flash CWM (as I remember it was option #2)
And then continue to flash SU (as I remember it was option #3)
That's all, you gain root access.
:good::good::good::good::good:
---------- Post added at 10:44 AM ---------- Previous post was at 09:47 AM ----------
Update again...
Seems the way I get the root access can't use to install custom ROM.
I try to install cyanogenmod as in this thread : http://forum.xda-developers.com/showthread.php?t=2073992
But seems after do all the steps to install a custom rom there, my phone was stuck on HTC logo...
Fortunately, I have do nandroid backup, so I can restore to stock roms...
What i want to ask is, why my phone can't install custom ROM now? I know that I still has S-ON, but is that the cause? If yes, is there any possible way for me to get S-Off and install a custom ROM?
glevitan, i need your help again I think :angel:
Update again :
After checking on some place, apprantly i still left some steps
this one :
Flashing roms with an unlocked bootloader
Unlock your bootloader and flash a custom recovery (CWM or 4ext)
Download the rom zip file you are willing to flash to your PC.
Extract the the boot.img from inside the zip file (do not extract the whole rom)
Put the zip file in your sdcard.
Boot into recovery and do a full wipe (wipe data/factory reset, wipe cache partition, format system)
Flash rom (install zip from sdcard)
Reboot into bootloader again and plug the phone to the PC.
You need to be in fastboot usb (if you see HBOOT USB PLUG in the phone, just press power to toggle)
Open a cmd/terminal and navigate to where the boot.img file is located.
Type: fastboot flash boot boot.img
Reboot and now you should be enjoying your custom rom
Finally I can enjoy my custom rom

Finally.
Finally.
I did it. I followed your instructions and I have root my phone.
I'm using the Custom ROM JellyTime and works perfectly.
Many Thanks for your help.
:good:

[Tutorial][S4/S3] How to use OTA zip to get back to Stock OS

Lately, many people, including myself, have been at a disadvantage of not having an official RUU for JellyBean so that stock environment can be achieved. Although sometimes, OTA's are available which can do the job. Hence this Tutorial. Also this saves the effort to do S-OFF/SuperCID which often brings along more problems.
This Tutorial, in principle, can be applied to both S4 and S3 variants.
All thanks to @xander1993 at the VilleC2 Development Section who created the original thread Here. Though somewhat unclear and related to VilleC2, I thought of making a thorough guide for Ville with some minor changes.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For T-MOBILE UK Users: (UK people with other operators e.g Three, Vodafone etc can also try the Jellybean Nandroid backup IF their firmware is upgraded to that of Jellybean)
ICS Users: Those stuck on ICS custom ROMs and can't get stock, Use This RUU to get to stock ICS and then update to Jellybean via System Updates Check. Thanks to @ppm48
Jellybean Users:Those stuck on Jellybean custom ROMs wanting to get stock, I have a Stock Jellybean 4.1.1 Nandroid backup for you guys Here Since there isn't any OTA.zip for T-Mobile UK for Jellybean. You can just flash this Nandroid right away without using this tutorial. Again, Thanks to @ppm48 for this. Also, if you have bootloops after restoring this backup, flash a Jellybean Sense boot.img.
Additionally refer to this post by @mkoev , should prove a lot helpful. Then you can follow the tutorial.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For OPTUS Users with CID OPTUS001: (All thanks to @salac)
Get the modified OTA.zip Here. by @salac
salac said:
Follow the instructions from step 12.
Step 14. Flashing the firmware.zip worked the second try for me
Step 22. I did flash the boot.img to make sure it will work since I don't think I had the original one.
Good Luck
Click to expand...
Click to collapse
Optus users please follow @salac 's post above to flash the OTA.zip
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Pre-requisites:
1. Notepad++
2. 7-Zip (Recommended)
3. ADB+Fastboot (Get it Here)
4. HTC drivers (Standalone OR HTC Sync Manager Drivers)
5. Unlock_code.bin from HTCDev to unlock bootloader.
6. Any OS (Custom/Stock) present on the phone. (I have not tested it for phones without any OS, you may try it at your own risk and post results here) Not Needed anymore.
Common Steps:
In this guide, I will ask you to go to fastboot/adb so you should know how you would do that. (All fastboot/adb commands are to be given via Command Prompt from PC)
To execute Fastboot Commands:
- Go to fastboot folder on your PC
- Go to fastboot via bootloader on your phone
- Connect the Phone to PC and on the Phone it should say Fastboot - USB Mode
- Now in the fastboot folder on your PC, Hold Shift + Right-Click and click Open Command Window Here
- Now you can enter commands given in the guide for fastboot.
To execute ADB Commands:
- Same procedure except that you don't need to go to fasboot on your phone. You can execute adb commands while in Android OS/desktop.
To boot into Bootloader:
- While the phone is turned off, Press Volume Down + Power Button simultaneously.
OR
- If you are in Android OS, use the following adb command to boot into bootloader:
Code:
adb reboot bootloader
OR
- If you want to reboot into bootloader from fastboot:
Code:
fastboot reboot-bootloader
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Caution for SuperCID users: Please click the CROSS button on your Browser Tab, as flashing this is not intended for you. Either don't flash the OTA.zip, which will brick your phone if you do, OR change your CID to original one. e.g. H3G__001, BM___001, ORANG001
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Procedure:
- ** - ** - ** - Make Nandroid Backups before you do anything, remember you are doing this at your own risk - ** - ** - ** -
1. Download a OTA.zip – Most likely from Here. (You can rename the OTA file which usually has a long name to simply OTA.zip for ease)
2. Extract firmware.zip from OTA.zip. Then extract boot.img from firmware.zip. For now, copy Boot.img to ADB+Fastboot Folder..
3. Now to match the CID of your phone. You can get the CID of your phone via CID Getter from Play Store. Once opened, at the top will be your CID in Red color.
Alternatively, You can also get CID of your phone via Fastboot. Command for that is:
Code:
fastboot getvar cid
and it should display your CID.
4. Inside firmware.zip, look for android-info.txt. Supported CIDs should be mentioned inside this file. If it matches with that of your phone, Proceed otherwise stop and don't put yourself into more problems. (CID Match Exception: This 4th step may not be applicable to you if & only if you are to skip steps 11 to 16, if this is the case, you may flash OTA.zip skipping steps 11 to 16; Read step 10 for more info and then come back here)
5. We need to remove some code lines from inside the OTA.zip. For this, Open the OTA.zip with 7-zip (Right-click ---> 7-zip ---> Open Archive).
6. Head over to META-INF\com\google\android and find a file named updater-script. Drag it out of the archive to the folder/desktop where you can edit it. You should make an extra copy of this file.
7. Once you drag it out, delete the original updater-script inside the archive. It will recompress OTA.zip.
8. Edit with Notepad++ the extracted updater-script file. Find these lines (in the beginning of the file) and delete them altogether:
Code:
[COLOR="Purple"]assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"BM___001") == "t");[/COLOR]
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PJ4011000") == "t");,
assert(check_mid("simple", "PJ4011000") == "t");
);
You should delete these lines up to exact semi-colon ; at the end. (the purple lines with different CIDs can be different from those mentioned here, so no need to panic, just delete them)
9. Once edited, Copy this edited updater-script into the OTA.zip archive at the same location from which it was removed. It will recompress OTA.zip. You may now transfer OTA.zip to your SD-Card on your phone.
10. If you previously updated to JellyBean via OTA (Or if you have the exact or newer firmware on your phone than that present inside OTA.zip), skip steps 11 to 16. For example, if you have HBOOT Version 2.15.0000/2.13.0000 or above, it means you have already upgraded to Jellybean firmware so no need for Steps 11 to 16.
In case, if you are to proceed to step 11, that is if you are to flash firmware.zip, make sure to match CID as mentioned in step 4 to avoid any bricks. This is especially useful for those who have ICS and want to get stock JB or those on JB but want complete stock HBOOT, recovery etc.
11. Place firmware.zip extracted from OTA.zip inside ADB + Fastboot Folder.
12. Lock the bootloader, if unlocked. For this, go to fastboot on your phone and give the command:
Code:
fastboot oem lock
The phone reboots after this.
13. While in Android OS/Desktop, fire up Command window on PC to give the following ADB command to boot into OEM Update Mode.
Code:
adb reboot oem-78
OR (if you can't access OS to execute adb)
From Fastboot:
Code:
fastboot oem rebootRUU
You should be seeing HTC logo.
14. While in OEM Update Mode, give the following fastboot command to flash firmware:
Code:
fastboot flash zip firmware.zip
If it fails with error and doesn't show any Green Progressbar, keep trying the above command. Usually works after a few tries.
********** DO NOT REBOOT MANUALLY UNTIL IT FINISHES FLASHING FIRMWARE OR YOU'LL BRICK YOUR PHONE *************
15. Once firmware is updated, reboot into bootloader. Go into fastboot.
16. Place Unlock_code.bin inside ADB + Fastboot Folder. Use the following fastboot command to unlock your bootloader again. (This will wipe your phone except for SD, so you must make a backup before doing this)
Code:
[COLOR="Blue"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
17. Download a recovery. Preferred Recovery is TWRP 2.3.3.0 and I have not tested this guide with any other version. Put the recovery in the ADB + Fastboot folder.
18. Now go into bootloader again. This time to flash the recovery anew.
Code:
fastboot flash recovery recovery.img
19. Now go to the recovery via bootloader. Wipe data/factory reset, cache, dalvik.
20. Restore the Nandroid backup you had made earlier.
21. Now Flash the OTA.zip which is on your SD-Card. It should flash fine.
22. Go to fastboot via bootloader. We are now going to flash kernel with the following command, boot.img you had earlier copied to ADB+Fastboot folder.
Code:
fastboot flash boot boot.img
23. Reboot to the OS and you should see complete stock JB OS.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Please Rate the thread and Hit the Thanks button if this tutorial helped you!

I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Well, When I edited OTA.zip, it was the same size before/after. But maybe OS X uses different compression values.
I think you should go ahead with it and try it.

I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
.......................
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Can you use Winzip/Winrar? Might want to check with those two..

mortek said:
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
Click to expand...
Click to collapse
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.

khan.orak said:
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
Click to expand...
Click to collapse
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.

mortek said:
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
Click to expand...
Click to collapse
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.

khan.orak said:
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
Click to expand...
Click to collapse
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.

mortek said:
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
Click to expand...
Click to collapse
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.

khan.orak said:
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
Click to expand...
Click to collapse
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.

mortek said:
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
Click to expand...
Click to collapse
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!

khan.orak said:
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
Click to expand...
Click to collapse
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
sending 'zip' (400 KB)...
OKAY [ 0.226s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.735s
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s

mortek said:
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
...........
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
Click to expand...
Click to collapse
I suspect hardware failure.
Sent from my HTC One S using Tapatalk 4 Beta

Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.

booenson said:
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
Click to expand...
Click to collapse
What recovery did you use? And did you edit updater script using notepad++?
Edit: Yup, after searching, Error Status 6 appears when you edit the UPDATER-SCRIPT using wordpad/windows editor which messes all that is inside it. Use Notepad++

khan.orak said:
What recovery did you use? And did you edit updater script using notepad++?
Click to expand...
Click to collapse
TWRP 2.4.1.0. No, I used notepad, but after googling and reading the differences between notepad++ and notepad, I will have to re edit with notepad++. Will try again tomorrow when I have more time, I still need to use this phone for work and can't have it bricked lol

Tried this again, flash went through and then flashed the boot.img included with the OTA zip, and my phones stuck at the "htc one" loading screen
Edit: relocked, flashed the stock recovery, thought it was still stuck at the loading screen so I unlocked it then went to install TWRP again to restore my nandroid, and it decided to finally boot. I guess I just needed to give it more time, currently back on 4.1.1, time to send this thing in under warranty so I can get my 3G/HSPA+ fixed. Thanks!

Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app

asdfasdfvful said:
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I think yes. You can check if you CID is supported. It is inside the OTA.zip\firmware.zip, a file named android-info.txt and the supported CIDs will be there.
Edit: You should first check your CID. Download CID GETTER from Play Store. Shows CID in red on top.

[Q] I Soft Bricked my HTC One M8

Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.

Edit
Sorry I completely forgot to add that I put my nandroid backup on my flash drive but when I went to use it it did not work. I believe this is because I did not have a big enough flash drive so it did not completely back up. LOL! Tonight was not my night.

radiowavedev said:
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Click to expand...
Click to collapse
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.

When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.

andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
+1

andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
That is why this was so strange to me. The hboot firmware sounds promising though.

bigblueshock said:
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
Click to expand...
Click to collapse
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?

radiowavedev said:
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
Click to expand...
Click to collapse
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "

andybones said:
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
Click to expand...
Click to collapse
Thank you for all of the useful information I will give this a shot tonight.

radiowavedev said:
Thank you for all of the useful information I will give this a shot tonight.
Click to expand...
Click to collapse
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.

andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Yeah I'm quite used to the ways of XDA but honestly had no idea about hboot. And I definitely will be thanking them. I'm now home and will test it out. I'll post my results afterwards.

andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?

radiowavedev said:
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
Click to expand...
Click to collapse
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader

Im sorry this might be stupid but what do you mean by not running fastboot command? And you say reboot-bootloader shouldn't I do reboot-recovery and flash my custom rom after factory resetting of course. Sorry im just trying to make sure im thorough. I would think messing up hboot would permanently brick my phone.

andybones said:
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Click to expand...
Click to collapse
Would it just be easier to use a nandroid backup?

I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.

radiowavedev said:
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
Click to expand...
Click to collapse
Separate the terminology "ROM" and "Firmware" for a moment. Firmware should/will never change regardless of what ROM's you flash. Think of firmware as a computers BIOS, And ROM as your computers operating system.
First, turn your phone off. Second, hold volume down + power button and do NOT let go of volume down until you're in the boot loader screen. Step 3) switch the boot loader into fast boot within that screen(Fast boot or fast boot USB may come up by default it will be highlighted in red). If you're plugged up to your computer via USB, it should automatically say "Fastboot USB". Then you can execute the commands in the command prompt andybones was talking about.
Did i loose you anywhere?
You could just nandroid back to your previous ROM... but that defeats the purpose. You'll never be able to go to a newer Sense ROM without the firmware upgrade anyway. You might as well get it done because it may improve your network signal, boot times, etc. Usually only benefits you,
After you upgrade firmware, it will say hboot 3.18.0000, Radio: 1.09.20.0702,

radiowavedev said:
Would it just be easier to use a nandroid backup?
Click to expand...
Click to collapse
I didn't just waste my time to write you up a STEP BY STEP FOOL proof guide.
I am not doing this for my benefit...
You made a thread.
You asked for help.
I gave detailed, if you mess up you didn't follow them exactly..
Why would you have me give you exact directions to fix your phone, then ask about a nandroid?
NO. If it were that simple my friend, don't you think I would have let you known this?
I'm sorry if this comes off rude, but I went out of my way to give you exact detailed instructions and you blow them off.
Why make a thread and then not take the advice from a Recognized Contributor to this site!?
I hope you can understand how frustrating this is.
I don't do this because it's fun for me to help get your phone fixed, I do it because you asked for help, and I like to help, but when my help goes un-heard and blown off - I walk away. - Best of luck my friend.
I am still going to help because that's the kind of guy I am..
Run the RUU since you are S-OFF if nothing else works.
You are a SOFT-brick. Very easy to fix.

Andybones, I totally understand. I wasnt trying to be rude im just confused and trying to come up with ideas. I understand it was dumb to mention the nandroid now. I hope you can accept my sincerest apology. I appreciate everything you have done for me and understand if you dont want to help me any longer. Like I said it was not my intention to be rude but I see how it can look like that. I just dont know what im doing.

Hi there, I believe I may have been in the same position as you at some point. What actually is happening is that you are trying to flash a new ROM (4.4.3 I believe) with the old hboot. The ROM should still boot but it will take up to 20min.
How to fix this:
1. Boot into boot loader, (manually or adb)
2. Choose fastboot
3. Connect to USB
4. Open command prompt
5. Fastboot devices
6. fastboot oem rebootRUU
7. You should see a black screen with a dark HTC logo.
8. fastboot flash zip (nameofzip).zip
9. When it finishes type fastboot reboot-bootloader (hyphen required)
10. You just flashed the new firmware but it has no os. You now need to flash a ROM or restore a nandroid backup.
Sent from my HTC One M8 GPE converted using XDA Premium mobile app