{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
General Information
Since we have S-Off, (and ONLY if you have S-Off!) we also can do a few more things than just flash hboots.
There are a few Firmware flashing threads and lots of zips and good and bad instructions. However, i noticed that many users asked about what they get when they flash what they download and also about how to flash it with S-OFF on various threads. This confusion has occasionally lead to people losing their custom kernels and custom recoveries and/or their SDcard partitions being unintentionally wiped.
I am writing this because i believe in "responsible" sharing. Since the full RUU's aren’t shared but only components (modified as well as unmodified) with often insufficient documentation, which in turn leads to a lot of confusion among the lesser informed users, i will try to catch some of that. I believe that sharing full RUU's would be a lot safer, as only those who actually know enough about it can disassemble them. RUU’s do always reassure users that there is a guaranteed and safe way to go back.
Now we are stuck with components only on a much larger scale than we were used to, due to a general change in sharing attitude and the original RUU source not being “as" active anymore. This is something that we ideally wish to not happen in XDA world. Now we don't live in an ideal world and someone has to ensure there are some proper and reliable info posts. I will try to share some of what i found during my XDA hunting.
*** Much appreciation to @Sneakyghost for creating this thread and maintaining it for a long time ***
This is Firmware for GSM PHONES ONLY - no cdma / sprint firmware here!
FUU HowToPrerequisites:
Current drivers available through HTC Sync Manager.
Please install, then remove again and leave only drivers!
Usage: Just run the ARUWIZARD.exe and profit!
ZIP Flash HowTo
Prerequisites:
You need ADB and Fastboot on your PC and instead of using the full ADB download (Huge!) you can either use the Android Tasks Batch script collection from @Sneakyghost, which sets up a “Mini ADB" on C:Android. Info in Post #1618. Or alternatively the HTC One Tool from @squabbi which also offers driver downloads and recovery downloads (handy shortcuts!).
To get ADB and Fastboot up and running please use search, many guides available..
Step-By-Step:1. If device is booted into Android, reboot into bootloader by running:
Code:
adb reboot bootloader
1.a Or else, if your device is in a different state or you just prefer the button method:
Press Power for 15 seconds and hold Vol Down at the same time, when the screen and charging LED go dark immediately release Power but keep holding Vol Down until you see the bootloader screen. Notice: If the device refuses to reboot, you might need to hold it to a bright light with its light sensor. This is a very specific bug on the HTC ONE.
2. Now place the Firmware_xx.zip into your adb/fastboot folder
3. Now run:
Code:
fastboot oem rebootRUU
4. Followed by:
Code:
fastboot flash zip Firmware_xx.zip
(replace "Firmware_xx.zip" with the name of your zip)
5. Now check the console output. It should approximately look like this:
C:Androidcom>fastboot flash zip 217_224_TWRP2601_combined_firmware.zip
sending 'zip' (35220 KB)...
OKAY [ 2.839s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.438s
Click to expand...
Click to collapse
“flush" certainly means “Flash" so press the arrow up key on your keyboard and enter to run the flash command again without reboot...
C:Androidcom>fastboot flash zip 217_224_TWRP2601_combined_firmware.zip
sending 'zip' (35220 KB)...
OKAY [ 2.835s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
(bootloader) [RUU]UZ,adsp,22
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,45
(bootloader) [RUU]UZ,adsp,56
(bootloader) [RUU]UZ,adsp,67
(bootloader) [RUU]UZ,adsp,79
(bootloader) [RUU]UZ,adsp,90
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[cir] unzipping & flushing...
(bootloader) [RUU]UZ,cir,0
(bootloader) [RUU]UZ,cir,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,13
(bootloader) [RUU]UZ,recovery,28
(bootloader) [RUU]UZ,recovery,39
(bootloader) [RUU]UZ,recovery,53
(bootloader) [RUU]UZ,recovery,64
(bootloader) [RUU]UZ,recovery,74
(bootloader) [RUU]UZ,recovery,85
(bootloader) [RUU]UZ,recovery,96
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,13
(bootloader) [RUU]UZ,radio,19
(bootloader) [RUU]UZ,radio,26
(bootloader) [RUU]UZ,radio,33
(bootloader) [RUU]UZ,radio,39
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,53
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,66
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,79
(bootloader) [RUU]UZ,radio,86
(bootloader) [RUU]UZ,radio,93
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,26
(bootloader) [RUU]WP,radio,53
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 49.443s]
finished. total time: 52.280s
C:Androidcom>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.039s
C:Androidcom>
Click to expand...
Click to collapse
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output to make sure it is safe to reboot! The bar will only fill up to 100% once you type:
6.
Code:
fastboot reboot-bootloader
Error handling strategies:IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always direct-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot...
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 seems to indicate different things, always relating to your phone not being eligible for a certain update. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match - there is no conclusive evidence yet, only hints. I can not monitor the commands being run by a RUU and determine which check exactly fails, so i am left guessing.
- 170 Check USB - FUU won’t run because of not working ADB.
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
fastboot oem writecid 11111111
You can change back to any desired CID after a successfull firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occured when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader and signed zip is required. These zips don’t work on locked, S-ON phones!
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers. One way to solve is to run the ARUWizard with the phone already in Fastboot mode. Else you will have to re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work well currently.
You flash at own risk. You're writing to critical parts of your phone.
If anything goes wrong along the way, you might be bricked.
___________________________________________________________________________________________________
Downloads
FUU Downloads (Windows only)
FUU Variants
Full Stock, WIPE FUU's:
Notice: Reflashes the /data partition with HTC’s DZDATA files (stock preload bloatware and reformats SDCard), meaning you *loose everything* on your SDCARD. Also replaces the Kernel, Ramdisk, recovery and Splash1 with latest stock images! Contains Stock Hboot (unmodified).
The /system partition will NOT be cleared. (Else this would be a RUU, not a FUU). So sometimes, a ROM might still boot after this, but more often it won’t. Be sure to know how to adb push or adb sideload a ROM to your SDcard after a FUU!
Combined, NoWipe FUU's:
Updates basic firmware partitions, does NOT touch the /data partition, leaves kernel, splash and ramdisk alone. Recovery will be replaced with TWRP.
Contains Stock Hboot (unmodified).
I won't provide new FUU's from now on. But the old ones will still be available.
If you want to use a FUU:
Download an old FUU from below and replace the rom.zip inside the folder with the new firmware zip of your choice. Then rename it to rom.zip and run the ARUWizard.exe.
FUU Downloads
Fastboot ZIP DownloadsZIP VariantsCombined, NoWipe ZIP's
Notice: This package is modified. Contents: TWRP recovery 2.6.3.3 (this is the most stable version, intended to give you the most stable firmwares i can do --> you can manually flash the newest recovery afterwards if you want to. Command "fastboot flash recovery xyz.img.) All other files are updated to latest version, removed Kernel, RAMdisk, Splash and SD wipe files so it should be good to update any firmware from 1.20 and up. Contains Stock Hboot (unmodified).
This package does NOT wipe SDcard.
Full Stock, WIPE ZIP's
Notice: Nothing removed - Everything stock! Needs ROM, (Custom) Kernel and (Custom) Recovery reflash after flashing this except when flashing stock 4.19 ROM afterwards. Phone won’t boot without ROM flash! Contains Stock Hboot (unmodified). *WIPES DATA /SDCARD*
Firmware ZIP Downloads
Credits
I have lost track of my firmware sources. I am so sorry i cannot name you guys all personally. The most common source would be @LlabTooFeR and HTCDev as well as @mike1986. and some others. If you find your stuff here and want to be included in the credits please contact me. I am very grateful for everyone busy providing dumps and direct leaks.
DisclaimerYou are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones at time of posting, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.
XDA:DevDB Information
[FIRMWARE] | [GUIDE] | [M7_UL] | Collection - Firmware, Tool/Utility for the HTC One (m7)
Contributors
Sneakyghost
Version Information
Status: Stable
Current Stable Version: 7.19.401.51
Stable Release Date: 2015-12-18
Created 2015-04-06
Last Updated 2015-12-18
Stock Hboot zips for RUUmode
General Information
The HBoots provided here are full stock hboots, completely unmodified.
Please don't post any modified Hboot files in this thread here, as i consider them to be insecure!
Downloads
I won't provide modified red warning gone Hboots.
If you want to use a modified red warning gone Hboot do it yourself and don't post it here:
Use the guide from Post#4
HBOOT Downloads
HowTo
For a detailed HowTo please follow the firmware flashing instructions in Post #1. Please just replace the zip names with the names of your respective hboot package. Everything else is 100% the same.
Now check the console output. It should approximately look like this:
Code:
C:\Android\com>fastboot flash zip orig_hboot_1.44.0000_M7_RUUmode.zip
sending 'zip' (486 KB)...
OKAY [ 0.245s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,52
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... [COLOR="Lime"][B]Successful[/B][/COLOR]
OKAY [ 2.176s]
finished. total time: 2.425s
Important: the flash process halts at 75% at phone screen! This is normal and a safety precaution! The last 25% is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot! The bar will only fill up to 100% once you type the following command:
Code:
fastboot reboot-bootloader
Error handling strategies:IF IT SAYS "FAILED" do NOT reboot the device but rather try the flash again or flash a stock hboot! If you reboot with a FAIL it could not boot up anymore! It could brick!
Please look up possible errors and strategies to deal with them in Post #1.
DisclaimerYou are aware that writing to the bootloader-partition increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on two phones at time of release, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i have only adapted it and you execute it. Go figure.
You understand that you should not do it if you are not willing to accept this risk.
Single Partition Images, RUUmode compatible
Separate touch driversNote: These drivers are not part of the common EMMC and get flashed to the touch controller chip. Thus, the flashing procedure looks a little different in the fasboot console output (the WP part is missing) and it takes quite long! Best is to leave it alone.Drivers for Synaptics S32028 Touch Controller
Working old touch driver for 4.1.2 ROM's: https://mega.co.nz/#!7YB1GCAJ!LaWJ8x5Vsjrw9YrLTIe262ZslZBNwRgp6i0qx2M_lIw
Working new touch driver for 4.2.2 ROM's: https://mega.co.nz/#!WMxxiLoI!AucvURiZhsuNJug59VKVDiOR8yw3o2mnqZ-ltczm9JcDrivers for new unknown “HMX852XD” Touch Panel:
http://goo.gl/yV873u
Separate stock splash screensNote: There are several splash screen threads out there. I will only add the normal HTC, TmoUS and Google Splash screens, just for easy reference.Splash1 files for the HTC ONE
HTC Sense ROM Splash OLD (with “Quietly Brilliant” Line from 1.27 and below): http://goo.gl/zptrTJ
HTC Sense ROM Splash NEW (from 1.27 Firmware up, no “Quietly Brilliant” line anymore): https://mega.co.nz/#!jAoDSBAY!KocCD06WGu-61TGB9FLO0XWpLvIu6xrFj2bIRtupNac
T-Mobile US Splash Screen: https://mega.co.nz/#!uJpUCbBI!DqNq4geGv3AupkMvIIEXlg7hbO1ihgr5frnAGUhjiLY
Google Edition Splash Screen: https://mega.co.nz/#!3NYzBJgB!IDDVWxddOf8z53ak_CagOE9wbn9POMa1Asx4JK4uFj8
Separate Stock RecoveriesNote:I was planning a stock Recovery collection since long as they do come in handy once in a while, although not too often. Now i remembered Guich had done that already a while ago, so i can spare that work. Thank you @GuichGuich’s thread in the Dev Section - deep down in the dark of the back pages
http://forum.xda-developers.com/showthread.php?t=2463387HowTo
For a detailed HowTo please follow the firmware flashing instructions in Post #1. Please just replace the zip names with the names of your respective hboot package. Everything else is 100% the same.
DisclaimerYou are aware that writing to the bootloader-partition increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on two phones at time of release, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i have only adapted it and you execute it. Go figure.
You understand that you should not do it if you are not willing to accept this risk.
Manual Hboot Hex Edit - "Crash Course" - On your own risk!
Manual Hboot Hex Edit - "Crash Course" - On your own risk!
! NO SUPPORT HERE IN THIS THREAD !
You want to edit your own hboot? Here is a crash-course how i do it: Notice: All at your own risk!
Get a !good! HEX Editor like this one http://mh-nexus.de/en/hxd/
Open your hboot-file with it (no matter if its a raw dd dumped piece or an .img or an .nb0 file - the edit takes place all the same).
Enter the search function of the Editor and type in: "this build is". That will find the right place for you.
You will then see this:
Code:
000ee1f0h: 6E 65 6C 2E 2E 2E 00 00 45 6E 74 65 72 69 6E 67 ; nel.....Entering
000ee200h: 20 4D 44 4D 20 52 61 6D 64 75 6D 70 20 6D 6F 64 ; MDM Ramdump mod
[COLOR="Red"]000ee210h: 65 2E 2E 2E 00 00 00 00 54 68 69 73 20 62 75 69 ; e.......This bui
000ee220h: 6C 64 20 69 73 20 66 6F 72 00 00 00 64 65 76 65 ; ld is for...deve
000ee230h: 6C 6F 70 6D 65 6E 74 20 70 75 72 70 6F 73 65 73 ; lopment purposes
000ee240h: 20 6F 6E 6C 79 00 00 00 44 6F 20 6E 6F 74 20 64 ; only...Do not d
000ee250h: 69 73 74 72 69 62 75 74 65 20 6F 75 74 73 69 64 ; istribute outsid
000ee260h: 65 20 6F 66 20 48 54 43 00 00 00 00 77 69 74 68 ; e of HTC....with
000ee270h: 6F 75 74 20 48 54 43 27 73 20 77 72 69 74 74 65 ; out HTC's writte
000ee280h: 6E 20 70 65 72 6D 69 73 73 69 6F 6E 2E 00 00 00 ; n permission....
000ee290h: 46 61 69 6C 75 72 65 20 74 6F 20 63 6F 6D 70 6C ; Failure to compl
000ee2a0h: 79 20 6D 61 79 00 00 00 6C 65 61 64 20 74 6F 20 ; y may...lead to
000ee2b0h: 6C 65 67 61 6C 20 61 63 74 69 6F 6E 2E 00 00 00 ; legal action....[/COLOR]
000ee2c0h: 68 62 6F 6F 74 3A 20 20 20 20 30 78 25 78 00 00 ; hboot: 0x%x..
000ee2d0h: 62 6F 6F 74 3A 20 20 20 20 20 30 78 25 78 00 00 ; boot: 0x%x..
In our example hboot 1.44.0000 the Text starts at Offset 000ee210h: right after a series of "65 2E 2E 2E 00 00 00 00 " The "T" of the text "This build is for.....blahblah" is the "54".
How erase it without changing the size of the file or damaging it? Well what i did was look at the spaces between the words displayed at the right hand side. If i place my Cursor on a space, it will show on the left HEX pane what numbers there are. Turns out, the spaces are just 20's. So i learned from that and then replaced the letters and dots with 20's.
For the Replace-Job place the Cursor into the left pane with the numbers! Don't replace in the right pane where you see the text!
Notice: @touch of jobo points out, that one should really only replace the non-zero digits with 0x20 (replace any two-digit number that is NOT zerozero with 20) and NOT replace with 00 so its spaces and not blanks. This way the hboot routine still "sees" text and not just empty space (a "Space" or 20 is regarded as text in this hex world. A "Blank" or 00 is not regarded as text but as a blank space). It is safer!
Now, make sure your HEX Editor is in overwrite mode and not doing anything else but replace existing bits (You'll be in deep sh.it if it kills bits or adds bits!). After finishing your edit, click "Save" and then compare the sizes of the original and the edited file. The Size must be exactly the same. Please do not only look at the dumb windows size but also check the full byte size.
our example hboot here has a size of 2.096.384 Bytes total before and after the edit.
This is how it looks in my edited hboots after the modification:
Code:
000ee200h: 20 4D 44 4D 20 52 61 6D 64 75 6D 70 20 6D 6F 64 ; MDM Ramdump mod
000ee210h: 65 2E 2E 2E 00 00 00 00 20 20 20 20 20 20 20 20 ; e.......
000ee220h: 20 20 20 20 20 20 20 20 20 00 00 00 20 20 20 20 ; ...
000ee230h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000ee240h: 20 20 20 20 20 00 00 00 20 20 20 20 20 20 20 20 ; ...
000ee250h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000ee260h: 20 20 20 20 20 20 20 20 00 00 00 00 20 20 20 20 ; ....
000ee270h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000ee280h: 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00 00 ; ...
000ee290h: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 ;
000ee2a0h: 20 20 20 20 20 00 00 00 20 20 20 20 20 20 20 20 ; ...
000ee2b0h: 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00 00 ; ...
000ee2c0h: 68 62 6F 6F 74 3A 20 20 20 20 30 78 25 78 00 00 ; hboot: 0x%x..
[2014.02.26] General Info on various Firmware related things
General Information
Flash Process Output:
There are a few steps in the flash process which are not really straightforward but i can maybe explain some of them here,so you can better understand what is happening:
sending 'zip' means: fastboot is sending zip over to client (here referred to as “remote”)
OKAY [ 2.839s] means status of sending was good. Transfer succeeded.
writing 'zip'... means the zip is being written to some location on the phone from the /temp location.
(bootloader) zip header checking... means the zip header is being checked for validity, see if it’s a real zip file.
(bootloader) zip info parsing... means most likely a check on the file hashes in the zip (integrity check - if the zip is borked, it will fail here)
(bootloader) checking model ID... The bootloader checks if the android-info.txt contains the right MID. If it fails here you gotta swap out your model ID in the android-info.txt file.
(bootloader) checking custom ID... The bootloader checks if the android-info.txt contains the right CID. If it fails here you gotta swap out your Customer ID in the android-info.txt file.
(bootloader) start image[hboot] unzipping for pre-update check... means the bootloader is now unzipping the [hboot] image. This line will be repeated before every image that is to be flashed.
(bootloader) start image[hboot] flushing... means the bootlaoder is now beginning to flash the [hboot] image.
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100 these three lines read [RUU] for what mode fastboot is in, WP for “Write Partition” for what is currently being done in RUUmode, “hboot” is the name of the currently flashed partition, number xx is a percent stage of the write process.
(bootloader) ...... Successful means the final status is successful.
Now, before the [RUU]WP,hboot,xx line we often see another line reading [RUU]UZ,radio,50 for example. That reads RUUmode is currently unzipping the Radio.img and at stage 50 percent. UZ means UNZIP.
If you see something like this:
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking... means it is checking the signature of the partition if it matches the expexted signature stored in the hboot.
(bootloader) verified fail means the signature in the image did not meet expectations.
(bootloader) ..... Bypassed means the image got skipped because its got the wrong signature.
This has to be interpreted like this: there are multiple “SBL” images, to be exact: type 1 has 3 variants and type 2 has only one variant. Of type 1 (“SBL1-x”), two get skipped, one gets flashed (see my log above), of type two (“SBLx”) both get flashed. I believe, SBL 2 and 3 are device independent, but SBL1 has three variants, of which only one fits the current device. So, depending on the device you have, you will see either SBL1-1, SBL1-2 or SBL1-3 being flashed and the other two subtypes being skipped (bypassed).
The same goes for the "dzdata" images in the firmware package. They come in three size flavors (16, 32 and 64 GB) and resemble the file structure of the /data partition. Depending on your model, only the one with the right size gets flashed, the others skipped.
Important to understand: nearly all FAILED messages that do NOT occur while [RUU]WP (write partition) should be considered harmless. Only a FAIL during a write operation will most likely result in a damaged partition. All other fails will probably leave the original partition intact and thus the device can be rebooted. So far my understanding.
General hints for RUUmode zips
- Opening a zip is best done with 7zip as WinRAR has lead to flash fails in the past.
- Choose low compression, higher compressions often fail. Pick "save" or "normal" to be safe, anything higher could cause the unzip in Bootloader to fail.
- Adding and Removing images is not a problem. The naming of the partition images seems flexible, yet if you encounter an “Error 23: parsing image fail” you need to rename the relevant image to something stock as not all names seem to be recognizable. The hboot determines the right partition from the header inside the image.
- Additional Dots in zip file names are known to have caused issues for a few people.
- Spaces in names are a no-go!
- Custom Recoveries can be added to those zips as well as custom kernels or hboots. In fact, if your phone is S-OFF, you can hex edit any partition and flash it. Be sure you know what you do though lol. I am just pointing out the possibilities. I am NOT saying it is safe!
- With S-ON, those zips only flash if everything is totally stock, from the android-info.txt being right up to all images being the correct versions for that update package and all having the right signatures. Reads: no custom messing with firmware zips for S-ON phones.
General hints for android-info.txt
- Use an Editor that doesn't mess up linebreaks like Windows Notepad does. Use Notepad++
- MID’s can be added one per line. Also supports wildcards i think e.g.: 71******, but i'm not sure.
- CID's can easily be added or removed- one per line, definetely supports wildcards (used by HTC in DevEd phone)
- Mainver line: should hold the version of the most current images, e.g if you combine older and newer files, add the MainVer from the newest. Format 2.24.401.1 (2= Base version always increases by 1 with each android base version rise, 24= Build version from HTC, 401= Regional/Customer identifier, 1= Revision of the HTC Build). This line is being written to the /misc Partition and is thouhgt to identify the whole phone firm/soft version - its not meant to only describe firmware or base alone. Those parts always belong together. My opinion: run Firm/Soft always from the same or very close revisions (eg. 4.06.1540.2 or .3 are no issue, whereas firmware from 1.20 with a ROM from 4.06 can already cause the one or other malfunction).
- hboot pre-update line: usually says "3" but i have seen different numbers. I think they determine if hboot-preflash is required (when you get “Error 90 - please flash imaga again immediately” this is when the hboot needs to be flashed separately first and then the rest... [Item subject to change]
- btype:1 not clear. [Item subject to change]
- aareport:1 Since HTC hboots come as "hboot_signedbyaa” i would read this as "aa" being htc ("hboot signed by aa") and aa report meaning report to htc if 1.
- Delcache means erase cache when rebooting. Simple. Some hboots seem to need it, some don't. Line is not present in every hboot. If you mess with a zip that contains the line, leave it active.
RUUmode:
is the mode used for RUU flashes by HTC. It allows a few more things than the normal fastboot. You recognize it by looking at the phone’s screen. It will be black, showing only a silver HTC logo and if a command is being active, a green progress bar.
Recovery flash risk:
In 2013 there had been a series of TWRP recoveries that have had issues flashing ROMs on a few HTC devices, mainly Aroma based issues. It's possible though that the one Brick i saw on the Ville from flashing a hboot in recovery was related to flashing it in recovery as i am not sure that the ROM flash fails are only Aroma based fails. I am rather sure that the method recovery zip’s most often uses to write an image file to NAND is not 100% bit correct and can cause trouble (This is the “DD” method). Due to the nature of this DD method, it can happen that single bits are flipped, which results in corruptions in the flashed hboot. That can manifest in a full brick or just in faulty operation, in blocked partitions (unwriteable partitions) and many more annoying things. While a full brick isn't really that likely to happen (we had one on the Ville Forums within a year which happened while flashing a hboot in recovery) a corruption of some sort is a little more likely. Since all types of corruptions can lead to severe problems it is desirable to have a safer method. There is a command for recovery “write_image” employed by HTC but i haven’t worked out how to use it and how it actually works and whether or not it is safer. So i decided to just stay away from recovery zips.
Apparently the zip flash executed in RUUmode utilizes a different write technique and is safer (It most likely is the same as “write_image” in updater-script ).
Please be aware though that this is an assumption. There is no real proof for this as we haven't gotten comprehensive documentations of HTC's stuff here. Anyway, this is the reason why i don't offer recovery zips. Even though it is perfectly possible to flash it in live android (using "dd if=/somedir/yourhboot of=/dev/block/mmcblk0p12") or recovery i prefer this method simply because i am sure it is safer.
JTAG with a RIFF Box
Every device of these days has so-called jtag test-points. Basically, these are points on the mainboards, where a direct connection to the main chip can be established and then that chip can be read and written to with an external device. Sometimes, these testpoints are hidden (like they are normal contacts of the chip) and no direct visible gold points on the board. It always takes a while after a device is released until the jtag layout is fully discovered but once that is done, companies like multi-com.pl start manufacturing small boards with pins that can be pressed onto the mainboard, so no soldering to the device is required. Once such a board exists, the mainboard can be hooked to the RIFF box which can rewrite a dead chip from the outside.
As long as there is no such small board (called a "JIG") the phone can still be revived but it is necessary to solder hair-thin wires to the test-points. That is perfectly possible, Tecardo can do such a thing, but its not very good for the board and cannot be done very often. At some point the solder points will degrade so much that the board is garbage then.
In case you really brick your device, you can contact Tecardo here: http://forum.xda-developers.com/showthread.php?t=2116062
S-OFF: Moonshine vs. Revone vs. Rumrunner
Revone does not install a custom hboot. So if you come here and flash my custom hboot and later go back with the backup i have here or with your own backup, you can then safely go back S-ON too.
Moonshine installs a custom hboot. So, if you come here and flash my custom hboot you will a.) loose moonshine special hboot and b.) you should also know that resetting moonshine S-OFF to S-ON is as dangerous as it is to do on my hboot, since its modded too! Moonshiners should also flash a stock hboot prior to set security back to ON.
Rumrunner is by now (End 2013) the most advanced and furthest developed S-OFF method as it now supports most versions and multiple devices, so the other two can be considered obsolete. Also, i am under the impression it doesnt install an engineering hboot, although there is one available for those who think they need it. So its leaving your hboot as is. Go support @beaups and @Fuses - they done a brilliant job, we’d have nothing without them.
Notes on the currently available hboots
Generally: Every hboot version number exists in different dev stages. So what i write here can be true for one type of e.g. “1.54” but not another. Each new base comes with an updated hboot - HTC has adapted a strategy though lately not to update the version numbers each time anymore. Which is very confusing for us.
- 1.44 can do Revone and Moonshine S-OFF, can also do command “fastboot boot xxx.img” but seems to destabilize bootloader when command getvar all is being run. A forced reboot is required then.
- 1.54 can be set S-OFF using Rumrunner. It crashes the bootloader if trying the fastboot boot command! It was noted by @uncommonaman a while ago, that this is NOT a bug but due to a change in the fastboot command syntax by Google. HTC has adopted it and one now needs to specify more parameters if the boot command is being used. The old command “hangs” the bootloader.
A (not working) solution attempt is here: http://forum.xda-developers.com/showpost.php?p=47600739&postcount=1977 and i am still looking for the correct parameters. You can help if you like.
- 1.55 Can be set S-OFF using Rumrunner. The same regarding boot command. New since either 1.54 or 1.55 (not clear) is the changed OFF state charging: the phone is now booting into a sort of recovery mode when charging from OFF state and displaying a charging animation. Later TWRP (2.6.3.3) supports these in the shape of a custom graphic.
1.56 seems to be much the same in terms of the aforementioned stuff, Rumrunner Universal 0.5.x does support it! (Proof by @bihslk thanks for that report! )
1.56 from base 4.18, 4.19 and related is NOT doing the Alarm Wakeup anymore! New bugs introduced. I was also notified that the HTCDev unlock doesn’t work for 1.54/1.55 in a certain scenario (GPE KitKat update, not able to unlock after that update).
MID and CID
MID = Model Identification. It serves the purpose of identifying the Model of the HTC ONE. There are at least 6 different ones if not more. PN0710000 (EU and North America, GSM/LTE) m7_ul and PN0711000 (Asia, GSM) m7_u and PN0712000 (US DEV, GSM/LTE) m7_ul and PN0720000 (US, Sprint) m7_wls. Then there is a PN0714000 (Australia, LTE) m7_ul and another variant for Japan PN0740000 (GSM, CDMA, LTE). Another few China variants are there too but they are dual sim and with SD Card and might not share the same hboot so i leave them out for now.
Source of this Data is here: http://forum.xda-developers.com/showthread.php?t=2223236
CID = Customer ID and describes, for which customer HTC made this phone. HTC has a few own CID's for its regional stores. Then certain carriers decide to have their own CID. T-Mobile US even has its own Model ID.
So, while the MID more like describes the hardware, the CID basically just describes the software set that comes delivered with it. Both get checked on when flashing in RUUmode. How to trick this system? Fairly easy. Just add your respective MID or CID to the android-info.txt file inside the ZIP.
Signature on the hboot and other partitions
In the Phones Firmware is a component that checks if certain partitions have a digital signature from HTC and deny read and write access if the signature is wrong or missing. The checking component is known to be the Security, which can be set to OFF. Then we say the phone is S-OFF.
For some partitions like the splash screen, it might not lead to a brick if you set security to ON while a custom splash is installed, as this partition is not vital for the boot process, it might just be skipped. System, recovery and boot do not have a signature at all. The HBOOT however does have it and i am sure Partition 3, which controls the Security flag, has it too and maybe some others like the secondary bootloader.
You guys have to understand that altering any of these partitions is deadly to your phone if you happen to leave them altered when switching security back on.
Determining your “Firmware Version”
I believe there is some wrong info circulating the HTC Fora. People keep saying when running fastboot getvar all it will report the Firmware Version in the line “Version-Main”. This is not always true though. Fastboot getvar all or alternatively getvar mainver pulls a version it finds in the MISC partition and relies on that to be correctly updated. Source
So how does that version string get updated? It is being taken from the android-info.txt file in any firmware zip that you flashed. The last zip you flashed determines what will be reported by the getvar function. So if you mess around with Firmware.zip’s and RUU’s a lot, chances are, that the version reported there is not equivalent to what you are already running. Often the android-info.txt has version entries not appropriate for the actual zip contents, for compatibility reasons, because it wasn’t done properly or whatever. My zips usually have the MainVer from the newest Firmware i took the components from, e.g my combined zips.
The "Firmware" as a concept like we use it on XDA does not exist in HTC's terms. HTC does NOT differentiate between the /System Partition (what we know as "the ROM") and the other 36 partitions. Hence, if you run getvar all or getvar mainver on a stock phone, it will report correctly. It does not go looking for a fictitious place where it would find a separate "Firmware" version. That place it is looking at is the Misc Partition and that’s correct as long as you haven’t messed with lots of different Firmware zips... So, if you happen to run a hybrid system with a ROM from one base and the other partition images from another base or multiple bases (like hboot from 1.27, radio from 4.06 and ROM from 3.62) the getvar function will report as "Version-Main" what it finds in /misc/, precisely the last zip you flashed determines the string put there.
Example: you flashed a radio with a RUUmode zip from Base 4.06 but the android-info.txt is maybe still an old one because the dude who made the zip, just dropped the new radio into an old existing zip, the getvar function will later report that old version as your mainver.
To check your firmware: boot to bootloader and look at the combination of hboot version and radio version - if you didn't flash those separate, the combination will let you know what base you are on (each OTA and RUU has the radioversion in its name).
Finding out your firmware is a game of guesses and knowing what you did to your device and where you are coming from.
If totally lost, best thing is to reflash some clean stock package to be sure you are on the same level with all partitions.
Long story short: you better know what you do because finding out your firmware is going to be difficult if you don't.
Further readingSome more useful threads with similar contents. Each has its own bits and pieces and re-wording that you don’t find here or understand here. So those threads might be helpful to you too.
- Mike1986’s Firmware thread
- Jolishj thread with Firmware packages including the red-warning-removed hboot already (for those who know the dangers of that hboot mod)
- Vomer’s ultimate guide thread
- Sir Crushalot’s genius stock reset packs
- Sir Crushalot’s nice Firmware packs with dark bootloader (GE 3.58 hboot)
- hes_theone64’s radio flash guide for recovery - method can be adapted for hboots etc.!
Related/ “Like” stuff
- HTC ONE Partition List
- Mike1986 Partition explanation
- Mike1986 Model Variants Thread
Thanks for that, it's great to have soff and now that on the one.
Nice work week do this after work
Sent from my HTC One using Tapatalk 4 Beta
Great job sneaky, I`m sure legions of ONE users will enjoy getting rid of the sh... red warning
Thanks for sharing Sneaky.
Ok now this is where the morons with brick comlaints come in.... happy killing your device!
Tecardo will revive your phones. He has an unbrick service going we originally set up for the HTC One S / Ville but he will be having the JIG for the ONE too and can then revive your devices.
So this is a conspiracy. I kill your phones so Tec can revive them and ask for Donations haha :laugh:
(just kidding just in case you didnt notice)
Nice people going to love this
Thanks for sharing from me too Sneaky, now I will not be scared of any red text, EVER
You have only just entered this section and BAM lol keep it up
would HTC_044 work with this? if not, can you get HTC_044 to work with this. I checked the android-info and there was no 044 in it.
Worked perfectly! Thanks.
Didn't I look in this topic earlier and a guy posted a Blue HTC spashscreen we could use ?
Sent from my HTC One using Tapatalk 2
I don't understand why we need this. If I flash a stock ROM the red tag goes away...
Hey,
i want to flash this hboot, but in android-info i can't found super cid.
can i flash this without adding super cid to this text file?
good job :good:
red warning is gone
thanks,work great
Great job Sneaky, I am free from red virus
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
crzykiller said:
I don't understand why we need this. If I flash a stock ROM the red tag goes away...
Click to expand...
Click to collapse
Nope you are wrong, ROMs do not change hboot
Related
Hi to everybody,my friend has a problem with his desire S.
his phone is turned off itself vibrating.now he can boot only in bootloader mode,and the recovery is gone.
here some spec.
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
( bootloader ) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) [email protected] baseband : 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__405
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
He also tried to flash the eng hboot to run a RUU,but seems he can't flash the hboot (hangs on "writing hboot").
thanks for any help.
Did your friend happen to pull his battery anytime before all this started?
Recovery doesn't just "disappear" - he must have done something prior to that...
Anyway, the first thing is to rule out (or in) a fried eMMC
So do this:
Set up adb/fastboot and connect your phone (link in my sig)
Then connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
adb shell
dmesg | grep mmc0
For further details, consult this excellent guide by amidabuddha:
http://forum.xda-developers.com/showthread.php?t=1284196
thanks for the quick reply.when I have the output of the dmesg | grep mmc0 ,I'll post here.I haven't the phone with me,so I have to wait for my friend.
the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?
NeTvAmPiRe70 said:
the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?
Click to expand...
Click to collapse
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery
enigmaamit said:
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery
Click to expand...
Click to collapse
...no luck hangs on "writing recovery".
NeTvAmPiRe70 said:
...no luck hangs on "writing recovery".
Click to expand...
Click to collapse
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE
enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
Click to expand...
Click to collapse
this is not the same thing but with a different recovery?
however,I'll give it a try.
NeTvAmPiRe70 said:
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
Click to expand...
Click to collapse
NeTvAmPiRe70 said:
this is not the same thing but with a different recovery?
however,I'll give it a try.
Click to expand...
Click to collapse
I don't know what was there in that file... so i sent you mine.
But if fastboot wasn't working, the possibility of an eMMC brick is looming larger...
Just try the commands i asked you to type in my first post... I mean boot into bootloader, then see if these commands cough up a report... if it doesn't work, boot into fastboot and try again. You must have some kind of recovery man...
Also, you didn't say what happens when you select Recovery option from the bootloader... what happens?
enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE
Click to expand...
Click to collapse
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.
NeTvAmPiRe70 said:
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.
Click to expand...
Click to collapse
Then i think your friend might have fried his eMMC.
Last resort is to call in the expert : Send a PM to amidabuddha, the guy whose guide i linked in my first post. I haven't found anyone more knowledgeable in these matters. If anyone can help you, its him.
I hope you can salvage the device...but its not looking very good....
thanks for your help,I'lll contact the expert
...and the expert has decreed:fried eMMC
NeTvAmPiRe70 said:
...and the expert has decreed:fried eMMC
Click to expand...
Click to collapse
That's what i thought too... just didn't want to mouth off such a grave judgement without being doubly sure.
Very sorry - unable to help any further. Hope your friend takes the news well, and wish him/her better luck for the next device!
Hello Everyone,
My Desire S was running Fallout 4.0 ROM. I had a couple sudden restarts in the last week and a half, but they seem to have been graphic related and because I didn't have the time to re-install, I just lived with it (not a big deal) for the time being.
However, yesterday when I picked up my phone I have noticed that it is stuck on the HTC boot screen. I thought that this is just another one of those restarts, but when the boot operation didn't progress I figured that something is wrong. I booted into recovery (CWM 5.0.2.0) and then got the infamous errors of can't mount Cache/System/Data.
This when my troubles have began because I cannot seem to be able to solve this issue.
1) From within the "mounts and storage" menu I cannot mount nor format the partitions (I get an error such as "Error mounting /cache!" and "Error formatting /cache! The latter takes also a long while in which the format is being attempted but in the end the error appears)
2) When I choose the wipe option (restore factory defaults) it takes a very long time (30-40 minutes) to wipe the data and cache partitions. Sometimes it gives an error message and some time it says complete, but with not effect whatsoever from what I can tell.
3) Attempt to restore my Nandroid backup fails (both of the original stick ROM that came with the phone and the more recent Fallout backup). An error message says that it cannot be completed.
4) I tried to flash several ROMs. The first two failed (including the original Fallout ROM that I have used). I think that I have managed to flash CM7 and RunnyDroid. I say think, because the process seem to be completed without an error, but nothing has changed otherwise, the system doesn't boot.
5) I checked my eMMC by booting into Fastboot and running the command
Code:
adb shell
dmesg | grep mmc0
from adb.
The output is
Code:
dmesg | grep mmc0
<3>[6.953796] mmc0: No card detect facilities available
<6>[6.954345] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,
<6>[6.954589] mmc0: Platform slot type: MMC
<6>[6.954711] mmc0: 4 bit data mode disabled
<6>[6.954925] mmc0: 8 bit data mode enabled
<6>[6.955078] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000
<6>[6.955291] mmc0: Slot eject status = 0
<6>[6.955413] mmc0: Power save feature enable = 1
<6>[6.955566] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c
<6>[6.955780] mmc0: DM cmd busaddr 0x0c36e000, cmdptr busaddr 0x0c3
<6>[7.109436] mmc0: new high speed MMC card at address 0001
<6>[7.111297] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
To my best understanding it means that the eMMC is not necessarily fried.
4) Because I cannot boot into the system I tried to re-flash recovery (actually 4EXT) via fastboot and adb, but it fails with the error
FAILED (remote: not allowed)
Click to expand...
Click to collapse
. The same happened when I tried to flash the boot.img from a ROM.
5. I read about installing a RUU. well, I think that I have found a version that fits my phone but all the download links are broken and a web search didn't find the version that I (think that I) need elsewhere. Also, those are EXE file, that to my best of understanding requires the Android system to be booted up in order the installation process to work, which I cannot accomplish at this point.
General details of my phone as appear in the HBOOT screen:
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011.14:58:38
Click to expand...
Click to collapse
Genreal details as received from running the commend
Code:
fastboot getvar all
in adb:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.15_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) serialno: HTXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG88*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.033s
Additional notes:
1) I took caution not to pull the battery, I know that it can have very negative effects. When I had to, before pulling the battery I have used the Volume up and down + Power combination to restart the phone and pulled the battery in that 2-3 seconds window before it restarts. I also didn't reconnect the battery immediately but waited about a minute.
3) I formatted my memory card (8GB) to FAT32, just in case the file system is corrupt (I have backed up everything first). This doesn't seem to have an effect.
4) I didn't root or S-OFF the phone myself. At the time of buying it I wasn't even aware of all of this and didn't plan to replace ROMs, etc., so I don't have much information about how the S-OFF and Root were achieved, this is how the phone was provided to me.
I would appreciate any input and advice. Is it a faulty eMMC? Is there anything else that I can do (I am far from being an expert in this field)?
Thank you very much.
Please try to be simple. I don't think that all these informations are necessary. This is a question Doesn't Have to be so long. The responders will ask you for additional info if needed.
Thank you for your reply, but I don't see the point in posting a vague and general question that will then require people to ask for information and suggest measures that one might already has taken.
From my experience in other forums (in which I'm more on the "helping" side) it is very frustrating to read vague and general questions and repeatedly ask for the same basic information over and over (and over) again just to get started. It is a waste of time and energy for all parties involved. In my opinion posting the relevant technical information, issue summary and steps already taken with their results is the way to go.
Update: I contacted the lab of the store from which I purchased the device. They tested it and told me that the board is (most probably) faulty, something to do with the electrical components. Because the device is still under warranty they will send it to be replaced.
Hopefully, the fact that I have flashed a custom ROM in the past won't be an obstacle in light of the nature of the fault.
Thank you.
You're right about the information. It does help to just provide it all and the information given is useful. Hope it all works out mate
Sent from my Desire S using Tapatalk 2
Hey guys, I have a problem with this phone HTC one mini, in fact I'm trying to unlock it with Sieempi method, but for this I need the device to be s-off. I unlocked the bootloader, the device be rooted, and when I try to use Rumrunner i got this error message.
Code:
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (19/120)
Waiting
Test 2: Booting device
Waiting for ADB (55/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (55/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Then i find this theard
http://forum.xda-developers.com/showthread.php?t=2573479
And download this two files, but then I stuck.
I'm not sure how to do the rest, but I tried it this way and I have failed.
I unpacked JmzM4_Kernel-09-4-13.zip file, and copied the boot.img file in the SDK folder from where I started CMD. In the CMD I typed "fastboot flash boot boot.img" and I got the message OK.
Then I went into recovery and found JmzM4_Kernel-09-4-13.zip file on the internal memory of a cell phone and I tried to install it (so I read) a zip file, and then I got the error MD5 file check, something like that.
I then reboot to recovery again and tried to install "JmzM4StockRootedOdex-WWE 1.22.401.1" also a zip file, and again the same error MD5 file check.
Then the phone in fastboot mode remained and could not boot the system. So I had to do a restore of backup I in which they made before I got into flash kernel, and roma.
Here is also my fastboot getvar all the info.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.22.0000
INFOversion-baseband: 1.28.40e.00.24
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.14.401.1
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid:
INFOproduct: m4_ul
INFOplatform: HBOOT-8930
INFOmodelid: PO5820000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4316mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-0e1af350
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.124s
C:\ADB>
Can someone tell me what is the solution for my problem, I just want my device S-off to try Sieempi method of unlocking, to see if it works. Thx!
Nothing? I try a couple thing more. I think its problem in the file I downloaded, and download a MD5 checker, and says thats ok. Then I save a md5 file from Md5 checker @ the same folder like zip file, and run again from recovery, and now got another error, you can see image.
IMG]http://tapatalk.imageshack.com/v2/14/10/08/624d91145625043f190be1d67997e6a2.jpg[/IMG]
Revone method doesnt work i got error -2. And boot intro the bootloader and stil s-on.
Please lock theard, phone was smashed. I lost nerves!
Hi Errornt
pardon if i only post today!
had your same situation and now i've solved! the solution? just flash a new kernel! i've used xXminiWHOOPERxX Kernel and now.... i'm s-off
so, unlock bootloader, install custom recovery and root, flash an insecure kernel with fastboot method and run rumrunner
that's all
i'm sorry for your smashed phone
br
ss
READ THIIS!
*this thread is for E8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
_____________________________________________________________________________________________________________________
this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
please note that s-off is required!
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
*i dont have E8. ian.anindya and a couple others have tested and provided dumps. please let me know and ill add you to the credits. also if someone wants to provide a copy of there cmd window doing the process,ill update that as well
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
secondary disclaimer: please use caution what mids you try and change. some devices may NOT be capable of being covertable to other devices due to available radio bands. in these cases,conversion may result in a bricked,or non-finctional device and may not be recoverable. i dont have the knowledge of E8 to say whats safe and whats not.
reference: http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210 make sure to hit the thanks button for @ian.anindya
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something(but not exactly) like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)change your MID
warning: *do not try and type the command. please copy and paste it
-0PAJ10000:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0PAJ10000 for modelid
fastboot reboot
________________________________________________________________________________________
your command window should look something(but not exactly) like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links:
remove tampered banner: http://forum.xda-developers.com/one-e8/general/how-to-remove-tampered-banner-t3019164
change lock status flag(lock/unlock bootloader):
other mids
0PAJ20000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
____________________________________________________________________________________________________________________________
0PAJ21000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ30000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ31000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ40000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x34\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ50000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x35\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
also mine!
Worked fine here.... Tnx
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.30306251.17_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: mec_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ21000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 87bcfea0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can we change:
product: mec_dugl
to
product: mec_dwgl
DutchDanny said:
Can we change:
product: mec_dugl
to
product: mec_dwgl
Click to expand...
Click to collapse
I haven't looked in to that,and for the most part it does not seem to be needed. I've converted m7_u to m7_ul variants without changing the product id and ruus, otas,etc work fine.
However... Just because you can,does not mean that you should. Folks have found that's its not a good idea to try and convert cdma world phones to gsm variants. For example m7_wlv to m7_ul.
So use caution in the conversions that you attempt
Sent from my HTC One max
I only changed MID and am on stock mec_dwgl.... Let's see what happens when ota arrives
Sent from my HTC One_E8 dual sim using Tapatalk
DutchDanny said:
I only changed MID and am on stock mec_dwgl.... Let's see what happens when ota arrives
Sent from my HTC One_E8 dual sim using Tapatalk
Click to expand...
Click to collapse
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.
parthasd said:
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.
Click to expand...
Click to collapse
converting to another variants firmware/software will NOT let you have different radio bands. this is mainly to run different stock software,and recieve stock OTA updates.
radio bands are at a much deeper level within the phone,and not accessible. youll pick up the same bands after a conversion as you do before.
as ive mentioned,be extremely careful what you do. trying to install gsm softare and firmware on a cdma,or cdma/gsm "world phone" or vice versa can cause irreversable damage and even hard bricks in some scenarios.
my advice would be if you cannot use your device as is,sell it and obtain a device intended for the region/carrier that you want to use it in.
parthasd said:
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.
Click to expand...
Click to collapse
I did change my M8sw China model successful to M8sw EU
You can read how I did this and try it at your own risk HERE
help to s-off
can anyone help me to s-off. I'm using M8sd OPAJ400 Indian dual sim
scotty1223 said:
0PAJ20000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
____________________________________________________________________________________________________________________________
0PAJ21000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ30000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ31000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ40000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x34\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ50000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x35\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
Click to expand...
Click to collapse
thanks for this great post, can you please share the command for m8sy taiwan mec dual opaj 22000. cant seem to find it any where since i bought this device but the meid was modified
sherazshery said:
thanks for this great post, can you please share the command for m8sy taiwan mec dual opaj 22000. cant seem to find it any where since i bought this device but the meid was modified
Click to expand...
Click to collapse
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)
scotty1223 said:
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)
Click to expand...
Click to collapse
Thanks for the quick reply
Complete model no. Is
HTC E8 Dual Sim(blue color) MEC_DUGL M8SY OPAJ22000
The command u shared is for this model?
scotty1223 said:
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)
Click to expand...
Click to collapse
thanks for your great post....is this for 0PAJ22000 ?????
when i input this text , adb dont give me any reaction ...are you know reason ???
my phone is s-off and supercid and unlock
HTC one E9 change MID
Hello friends !
I'm new one to xda.
please give me a code for this mid.
MID = 0PL312000
DutchDanny said:
Can we change:
product: mec_dugl
to
product: mec_dwgl
Click to expand...
Click to collapse
I got error "Permission Denied" plz help i need to change Chinese version to EU
Alizpk said:
I got error "Permission Denied" plz help i need to change Chinese version to EU
Click to expand...
Click to collapse
I don't have al the information anymore.
But are you s-off & supercid?
Yes I'm s off and super cid
DutchDanny said:
I don't have al the information anymore.
But are you s-off & supercid?
Click to expand...
Click to collapse
Yes S-off and supercid
FIRST AT ALL, BE SURE WHAT YOU DO, I AM NOT RESPONSIBLE FOR ANY DAMAGE, ETC... AT YOUR OWN RISK, THIS IS MY EXPERIENCE, IT CAN BUT IT MUST NOT WORK ON YOUR PHONE, YOU HAVE BEEN WARNED BERFORE DOING ANY ACTION
Guys, this is a story of a 3 year odyssey to get my IMEI on this phone back and at the end, YES!!! it works again. 100% full signal came back.
Now let's get into in....
First, tools you need to recovery your IMEI again.
- phone must be unlocked
- phone must be root
- phone should be on original stock 5.1
- TWRP Recovery ROM (use twrp-3.0.2-0-xt1032)
- from PlayStore download "Partitions Backup"
- from PlayStore download "Root Browser"
- XPOSED Framework and XPOSED Installer
- IMEI CHANGER (XPOSED MODULE)
- .IMG (use attached)
The story:
A friend of mine bought 2013 a Moto G (1st Gen) and wanted to root by himself. Root doesen't work, so he kept up. He decided to put an other rom on his phone, what he doesen't know, he erased all with command everything before (DICKHEAD): Fastboot erase all and Fastboot erase recovery <-- KILLER
From this moment.. after rebooting his phone the was no signal anymore. Serveral ROM and MODEMS tried out. Nothing just WIFI works. He gave the phone to me. 3 years later i wanted to re-awake this wonderful phone back to life.
Now, here comes the steps, you should do, to re-gain your phone...
01. choose and use a stock 5.1 rom of your country and flash it by fastboot command as always...
02. after rom installation and after reboot, install TWRP recovery rom with fastboot
03. reboot into recovery and install root in TWRP (use: UPDATE-SuperSU-v2.46)
04. reboot and download from PlayStore "Partitions Backup" and "Root Browser" and "IMEI Changer"
05. download XPOSED Framework (zip) and XPOSED Installer (apk)
06. reboot into TWRP install XPOSED Framework
07. reboot and install the XPOSED Installer APK with Root Browser and install IMEI Changer Module in XPOSED
08. reboot system, go into IMEI Changer and change your IMEI (under the back cover of your phone)
09. reboot and type in phone *#06#, you should see right now your IMEI, but the signal is already lost right? Okay, let's go ahead...
10. now return into Root Browser and see if there is a folder on your SDCARD "PartitionsBackups", if not, start the App and return
11. copy all three .img (attached) into it, start the App "Partitions Backup" again. Navigate to 3 dotted menu and and check "Restore a Partition"
12. navigate with "Root Browser" to the folder "PartitionsBackups" on SDCARD and use the first one, if successful, restore also the both other partitions. Forget the dd commands in terminal or cmd (doesent work), use the APP on top.
13. if it's done, reboot and pray... GOOD LUCK
14. Congrats, your signal should be back.
15. use Partitions Backup to backup all your partitions (as .img) and store them elsewhere.
16. set IMEI Changer as inactive and reboot, check with *#06#, otherwise let it active
17. !!! GIVE ME A THANKS, IF YOU ARE HAPPY WITH THIS !!!
NOTE!
YOUR IMEI WILL NOT SHOWN IN FASTBOOT!
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA8900FI4F
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 28F911020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 19 23:46:25 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3116.98.00y EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 19:06:25 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.104s
Reserved #2
Reserved #3
Can it work on Moto E dual sim 2014 indian version
Jerome-X said:
FIRST AT ALL, BE SURE WHAT YOU DO, I AM NOT RESPONSIBLE FOR ANY DAMAGE, ETC... AT YOUR OWN RISK, THIS IS MY EXPERIENCE, IT CAN BUT IT MUST NOT WORK ON YOUR PHONE, YOU HAVE BEEN WARNED BERFORE DOING ANY ACTION
Guys, this is a story of a 3 year odyssey to get my IMEI on this phone back and at the end, YES!!! it works again. 100% full signal came back.
Now let's get into in....
First, tools you need to recovery your IMEI again.
- phone must be unlocked
- phone must be root
- phone should be on original stock 5.1
- TWRP Recovery ROM (use twrp-3.0.2-0-xt1032)
- from PlayStore download "Partitions Backup"
- from PlayStore download "Root Browser"
- XPOSED Framework and XPOSED Installer
- IMEI CHANGER (XPOSED MODULE)
- .IMG (use attached)
The story:
A friend of mine bought 2013 a Moto G (1st Gen) and wanted to root by himself. Root doesen't work, so he kept up. He decided to put an other rom on his phone, what he doesen't know, he erased all with command everything before (DICKHEAD): Fastboot erase all and Fastboot erase recovery <-- KILLER
From this moment.. after rebooting his phone the was no signal anymore. Serveral ROM and MODEMS tried out. Nothing just WIFI works. He gave the phone to me. 3 years later i wanted to re-awake this wonderful phone back to life.
Now, here comes the steps, you should do, to re-gain your phone...
01. choose and use a stock 5.1 rom of your country and flash it by fastboot command as always...
02. after rom installation and after reboot, install TWRP recovery rom with fastboot
03. reboot into recovery and install root in TWRP (use: UPDATE-SuperSU-v2.46)
04. reboot and download from PlayStore "Partitions Backup" and "Root Browser" and "IMEI Changer"
05. download XPOSED Framework (zip) and XPOSED Installer (apk)
06. reboot into TWRP install XPOSED Framework
07. reboot and install the XPOSED Installer APK with Root Browser and install IMEI Changer Module in XPOSED
08. reboot system, go into IMEI Changer and change your IMEI (under the back cover of your phone)
09. reboot and type in phone *#06#, you should see right now your IMEI, but the signal is already lost right? Okay, let's go ahead...
10. now return into Root Browser and see if there is a folder on your SDCARD "PartitionsBackups", if not, start the App and return
11. copy all three .img (attached) into it, start the App "Partitions Backup" again. Navigate to 3 dotted menu and and check "Restore a Partition"
12. navigate with "Root Browser" to the folder "PartitionsBackups" on SDCARD and use the first one, if successful, restore also the both other partitions. Forget the dd commands in terminal or cmd (doesent work), use the APP on top.
13. if it's done, reboot and pray... GOOD LUCK
14. Congrats, your signal should be back.
15. use Partitions Backup to backup all your partitions (as .img) and store them elsewhere.
16. set IMEI Changer as inactive and reboot, check with *#06#, otherwise let it active
17. !!! GIVE ME A THANKS, IF YOU ARE HAPPY WITH THIS !!!
Click to expand...
Click to collapse
Bro, I also lost my imei number for moto e, it shows imei: 0, but in fastboot getvarall, it shows imei number.I think the img file you have attached will be different for moto e. I am ready to do anything, please guide. Thanks and regards
Im not an expert, but this method seems dangerous. The partitions you have attached are unique to your device, and flashing them on another device could cause serious permanent problems. I would suggest you remove these instructions until it is known what is contained within the hob, dhob and fsc partitions, unless someone can correct me.
Its up to the user to doing any action. This is my story, and my very own solution here, i wrote.
Gesendet von meinem SM-A310F mit Tapatalk
Professor Gibbins said:
Im not an expert, but this method seems dangerous. The partitions you have attached are unique to your device, and flashing them on another device could cause serious permanent problems. I would suggest you remove these instructions until it is known what is contained within the hob, dhob and fsc partitions, unless someone can correct me.
Click to expand...
Click to collapse
What problems? Even if they are the same IMEI still there is little chance that 2 users to be in the same country same network and same city. Anyway there are a lot of people who used the command and are screwed so it's great tutorial to revive the device
Sent from Samsung Galaxy S7
Jerome-X said:
Its up to the user to doing any action. This is my story, and my very own solution here, i wrote.
Click to expand...
Click to collapse
Exactly, this could mean that an inexperienced user might follow these instructions without understanding the implications. And when you say this is your very own solution, it's literal. This solution only applies to your specific device.
Eurofighter_ty said:
What problems? Even if they are the same IMEI still there is little chance that 2 users to be in the same country same network and same city. Anyway there are a lot of people who used the command and are screwed so it's great tutorial to revive the device
Click to expand...
Click to collapse
The IMEI duplication was only an example. There could be many other irreversible issues that the user doesn't even immediately realise.
Essentially, these partitions should never be overwritten without first taking a backup.
Yes of course, u re right
Gesendet von meinem SM-A310F mit Tapatalk
Haha, I'm not fussed with being right - just wanting to point out/give my opinion on the possible risks.
By all means keep your tutorial, but could I suggest adding a step where the 3 partitions are backed up before they are overwritten, just in case they need those partitions in the future.
Thank you so much for this really useful guide, I was hopeless and finally after 3 years was able to make my phone work.