bootloader flash error - Moto G4 Plus Questions & Answers

Hi guys...
I has flash stock rom in my xt1626 and now I have a erro while I flash bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(bootloader) committing: bootloader.default.xml ...
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.411s]
finished. total time: 0.536s
And now, when my phone turn on. I has lost my network activity and my digital tv.
I'm lost with I have to do.
Someone knows how I solve this?

Which rom did you flash? Sounds you've flashed not a rom for xt1626!

this one: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I always flash this. And never had a single problem.
There's not specific rom stock for xt1626. I never found.
My cel phone recognize like xt1626, sim 1 is working, but shows only "no service". sim 2 disappeared and digital tv app too.
{
"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"
}

What is status of both IMEI ? Are those correct with sticker (on backside / box) ?
Have you flashed anything else with or before this ROM ?

IMEI 1 is ok. IMEI 2 not exist cause sim 2 is not working.
I don't know what's happened. But mobile radio doesn't turning on.

Related

[RUU]M9+ RUU file

“ht”tp:/“/pan.baidu.c”o“m/s/1o6zHTpC 密码(psw): y571
Now , just has 3 file NAME :
ZhongZhuangbao_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_431201.ZIP
ZhongZhuangbao_HTCCN_CHS_2_1.08.1405.6_Radio_1.1506V24P14.1605.0421__431815_DownLoadModen.zip
ZhongZhuangbao_HTCCN_CHS_2_1.08.1405.6_Radio_1.1506V24P14.1605.0421__431815.zip
I upload speed is only 10-45KB, all the M9+ruu add up to have 50GB.
Now I only upload 3 most people need.
If other people need more, I will upload more.
2GB file takes a week
I've got a question
Publish all the NEWEST RUU What damage to HTC?I don't want to hurt the interests of the HTC company.
Good job, guy!!
TW(709),please!
Thanks!
Sent from my HTC_M9pw using XDA Free mobile app
UAE RUU
Do you have the update ruu for the UAE version .? thnx in advance
Thanks for share it
But,it's only china?
thank you
it is only in chines . can you try to upload it in another website please ?
Thank you so much!!! Could you share HK(708)? =)
I'll upload some too to mega.nz when I'll get back from vacation
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this on S-On, you must have your device Relocked (on S-Off you don't need to relock) and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800
tbalden said:
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this you must have your device Relocked and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800
Click to expand...
Click to collapse
Hi tbalden,
Even the MD5checksum is verified, still can't find the system.img in the rom.zip
the size in the zip file also seems not right.
May you check it?
{
"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"
}
you need to use a linux, there latest ruuveal, 'ruuveal -D xy.zip' to properly unzip all with system image parts as these are large zips (special format). Then you will have to unify the system img parts with Hima_ImgTool from m9 forum threads. Then you can mount and/or browse them as EXT4 filesystems.
Also, if you are thinking about restoring to stock, it might be better to just flash the whole zip as it's intended by HTC with fastboot.
tbalden said:
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this you must have your device Relocked and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800
Click to expand...
Click to collapse
thanks for the signed RUUs. I'm downloading now I will try them later. I have a question. how can I install different region RUUs? Do I have to change MID like in htc one m8 or m9? If yes, where can I find mid for specific regions/?
---------- Post added at 02:01 AM ---------- Previous post was at 01:22 AM ----------
load_file: could not allocate -2053247557 bytes
error: cannot load '0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip'
I'm getting this error. anyone explain plz/
jura.m said:
thanks for the signed RUUs. I'm downloading now I will try them later. I have a question. how can I install different region RUUs? Do I have to change MID like in htc one m8 or m9? If yes, where can I find mid for specific regions/?
---------- Post added at 02:01 AM ---------- Previous post was at 01:22 AM ----------
load_file: could not allocate -2053247557 bytes
error: cannot load '0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip'
I'm getting this error. anyone explain plz/
Click to expand...
Click to collapse
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.
tbalden said:
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.
Click to expand...
Click to collapse
Code:
D:\M9pw>htc_fastboot oem rebootRUU
...
OKAY [ 0.000s]
finished. total time: 0.000s
htc_fastboot finished. total time: 0.173s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.696s]
writing 'zip'...
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.244s
htc_fastboot finished. total time: 25.291s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.575s]
writing 'zip'...
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
[COLOR="Red"](bootloader) ERR ZIP signature checking failed...[/COLOR]
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.481s
htc_fastboot finished. total time: 30.171s
D:\M9pw>fastboot reboot
rebooting...
finished. total time: -0.000s
Now,try to copy the file to SD card.
yvtc75 said:
Code:
D:\M9pw>htc_fastboot oem rebootRUU
...
OKAY [ 0.000s]
finished. total time: 0.000s
htc_fastboot finished. total time: 0.173s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.696s]
writing 'zip'...
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.244s
htc_fastboot finished. total time: 25.291s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.575s]
writing 'zip'...
(bootloader) HOSD CL#549681
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
[COLOR="Red"](bootloader) ERR ZIP signature checking failed...[/COLOR]
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.481s
htc_fastboot finished. total time: 30.171s
D:\M9pw>fastboot reboot
rebooting...
finished. total time: -0.000s
Now,try to copy the file to SD card.
Click to expand...
Click to collapse
Do you have the bootloader on higher version than the zip? I think you can't do that. You need the same main version or lower on the phone boot loader (1.08) to flash it. I used the Chinese zip a few times and it went well but I haven't updated the bootloader over 1.08
http://www.xda-developers.com/misctool-gives-htc-users-power-to-readwrite-main-version/
tbalden said:
Do you have the bootloader on higher version than the zip? I think you can't do that. You need the same main version or lower of phone boot loader (1.08) to flash it. I used the Chinese zip a few times and it went well but I haven't updated the bootloader over 1.08
http://www.xda-developers.com/misctool-gives-htc-users-power-to-readwrite-main-version/
Click to expand...
Click to collapse
I misunderstood the post.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
OK,thanks tbalden.
I know the issue. I forgot this main version I ever used in the era of One X.
I must defraud the RUU of main version in the android-info.
Thanks again!! :good:
About modifying main version: I think that will only work with s-off, or maybe even there not either. You need to modify the main version of your phone, not the zip, because modifying the zip will make the signature invalid on it and it won't flash.
tbalden said:
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.
Click to expand...
Click to collapse
thanks man. I figured that out after I googled that issue I was getting. I downloaded htc fastboot and done that. I got cid error when I tried to install 707 and 709 RUUs. My device was already s-offed and I changed cid to supercid 11111111. after that I managed to install 707 version. thanks for your help.
yvtc75 said:
I misunderstood the post.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?................SuSam
Click to expand...
Click to collapse
Wait for RUU 1.81 release, and now my phone device is 1.61, so 1.08 version is too low, can not be used unless the s-off ~ :crying:
玻璃施工 said:
Wait for RUU 1.81 release, and now my phone device is 1.61, so 1.08 version is too low, can not be used unless the s-off ~ :crying:
Click to expand...
Click to collapse
Wow.......... cool name!! :good:
Yep, wait for the newest RUU.
Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software.
yvtc75 said:
Wow.......... cool name!! :good:
Yep, wait for the newest RUU.........Susan
Click to expand...
Click to collapse
mm... Their ROM is the only antidote to save M9+ (take the Low stool

failed to unlock bootloader moto x play 6 (with fastboot)

Hi everybody,
I have a moto x play updated to 6.0 official that i am trying to unlock to root but so far failed.
I have installed ALL drivers then uninstalled then reinstalled more than five times but still failed to get unlock string.
The device is seen in adb/fastboot and the bootloader logs on the device show the commands i am sending but it still says failed try again.
I have followed all advice given on the other posts but same message, so i typed in the getvar all cmd hopeing it could help someone find a solution thanks in advance.
C:\Users\Sandwiches>fastboot devices
ZY22247TWN fastboot
C:\Users\Sandwiches>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.281s
C:\Users\Sandwiches>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8939-80.EC
(bootloader) product: lux
(bootloader) board: lux
(bootloader) secure: yes
(bootloader) hwrev: 0x82C0
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Toshiba REV=07 PRV=00 TYPE=57
(bootloader) ram: 2048MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8939
(bootloader) serialno: ZY22247TWN
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 54FE1D0400000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358967060920707
(bootloader) meid:
(bootloader) date: 08-14-2015
(bootloader) sku: XT1562
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Feb 22 16:31:24 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0/MPD24.6
(bootloader) ro.build.fingerprint[1]: 5-18.1/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.14.1.lux_reteu.re
(bootloader) ro.build.version.full[1]: teu.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband: M8936_2020628.40.03.21.50R LUX_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-g6dd1a6d (hudsoncm
(bootloader) kernel.version[1]: @ilclbld73) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Dec 3 16:18:03 CST 2015
(bootloader) sbl1.git: git=MBM-NG-V80.EC-0-g7abea31
(bootloader) rpm.git: git=MBM-NG-V80.EC-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.EC-0-ga1c5ae6
(bootloader) hyp.git: git=MBM-NG-V80.EC-0-ga1c5ae6
(bootloader) aboot.git: git=MBM-NG-V80.EC-0-gcfa8344
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:customize: raw
(bootloader) partition-typeem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-sizeadA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-sizeadB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000180000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000600000
(bootloader) partition-size:clogo: 0x0000000000600000
(bootloader) partition-sizeersist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-size:recovery: 0x0000000001ffc000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-sizeadC: 0x000000000061e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-sizeem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:cache: 0x0000000030000000
(bootloader) partition-size:system: 0x00000000aa000000
(bootloader) partition-size:userdata: 0x00000002c03e0000
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.452s
Make sure that OEM Unlocking is enabled in Developer Options. I had the same problem when I did mine.
{
"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"
}
Sent from my Moto X Play
I used this tool "WinDroid" to unlock the bootloader. Its fully automated and very easy to use.
You can unlock your bootloader only with a few mouse clicks. Very handy tool :good:
http://forum.xda-developers.com/showthread.php?t=2499926
moto
brian10161 said:
Make sure that OEM Unlocking is enabled in Developer Options. I had the same problem when I did mine.
Sent from my Moto X Play
Click to expand...
Click to collapse
They are all enabled.
Developer Options are enabled
Usb debug enabled
oem unlocking enabled
Thats what i can't understand.
Sickaxis79 said:
I used this tool "WinDroid" to unlock the bootloader. Its fully automated and very easy to use.
You can unlock your bootloader only with a few mouse clicks. Very handy tool :good:
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
i have tried the tool suggested gives me an error contact xda devs message.
That is very weird. Just wondering, can you try using mfasboot instead of fastboot? It's the Motorola branded version of the software. Maybe it will help?
Sent from my Moto X Play
brian10161 said:
That is very weird. Just wondering, can you try using mfasboot instead of fastboot? It's the Motorola branded version of the software. Maybe it will help?
Sent from my Moto X Play
Click to expand...
Click to collapse
Same message
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.268s
I did have it sent for repair a couple of weeks ago because i forget my gmail account details, do you think that has somethink to do with it.
I do not think it will help but maybe worth a try to just factory reset it and see if has an effect.
That might be your best net, you will be erased anyway when you unlock so nothing to lose attempting it.
Sent from my XT1563 using Tapatalk
No luck, i will try a full windows reinstall tomorrow maybe that will help if not i am stuck with a unrooted phone :crying:
I don't think reinstalling Windows will be necessary. I have a feeling something has changed as far as Moto goes. Does your phone have any subsidy on it? Was it purchased out right? Maybe a network unlock is needed? What carrier, if it applies, was it purchased through?
Sent from my Moto G 2014 using Tapatalk
brian10161 said:
I don't think reinstalling Windows will be necessary. I have a feeling something has changed as far as Moto goes. Does your phone have any subsidy on it? Was it purchased out right? Maybe a network unlock is needed? What carrier, if it applies, was it purchased through?
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
What do you mean by subsidy?.
It was purchased on ebay a couple of days before official launch day. It was unlocked out of the box to any carrier and i haven't had a sim in it at all as i have another phone for that.
Oh okay. A subsidy, in what I'm referring to, is when a phone is purchased with a contract or a tab and has a debt owed against the phone.
Just was curious. But if the phone was purchased before launch I'm wondering if maybe it has a special board with older software in it that won't allow a bootloader unlock.
Very strange, I have never seen anything like it.
Sent from my Moto X Play
No subsidy no contacts.
I brought it off the top of my head between 3-7 days before launch day.
I won't know about old software stuff i'm a novice at the stuff its my second phone in 11 years! and both i've had in the last year so i'm new to this stuff.
brian10161 said:
Oh okay. A subsidy, in what I'm referring to, is when a phone is purchased with a contract or a tab and has a debt owed against the phone.
Just was curious. But if the phone was purchased before launch I'm wondering if maybe it has a special board with older software in it that won't allow a bootloader unlock.
Very strange, I have never seen anything like it.
Sent from my Moto X Play
Click to expand...
Click to collapse
A part from unique id strings and region code from this guys getvar all info it looks the same as mine. But i did notice his bootloader date is older (bootloader) date: 08-05-2015 vs mine (bootloader) date: 08-14-2015 if that counts at all, like i said i am new to this.
http://forum.xda-developers.com/mot...nlock-data-t3225594/post63320372#post63320372
Try this fastboot and unlock bootloader
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
if nothing works ask the service center guys to unlock it.
Have you also installed the Motorola device drivers?
drmuruga said:
Try this fastboot and unlock bootloader
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Click to expand...
Click to collapse
Thats what i am using when receiving the failed message and its been tried as admin and without still the same.
Sickaxis79 said:
Have you also installed the Motorola device drivers?
Click to expand...
Click to collapse
I have installed and reinstalled the moto device manager/drivers and the ADB Installer v1.4.3 exactly as instructed + i have used fastboot, mfastboot and tried out the windroid toolkit.
I have usb debug, oem unlocking and dev options enabled.
hello everybody said:
I have installed and reinstalled the moto device manager/drivers and the ADB Installer v1.4.3 exactly as instructed + i have used fastboot, mfastboot and tried out the windroid toolkit.
I have usb debug, oem unlocking and dev options enabled.
Click to expand...
Click to collapse
Maybe you could try using another pc from someone else and see if it works. Its a very strange situation.

[GUIDE][MM][6.12.1540.4] HTC One M8 to Developer Edition with Original RUU EXE File

Device MUST be S-OFF!
Requirements
HTC Fastboot and ADB : Google Drive
Firmware : Google Drive
RUU EXE : http://www.htc.com/us/support/htc-one-m8/news/
First Step
Change your MID and CID from yours to Developer Edition.
{
"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"
}
Open your Command Prompt on your installation folder with "Left Shift + Right Mouse Click"
MID Change
adb.exe shell
su (if needed to get a # prompt)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit (if you have #, 2 times)
adb.exe reboot-bootloader
CID Change
htc_fastboot.exe oem writecid BS_US002
htc_fastboot.exe reboot-bootloader
htc_fastboot.exe oem rebootRUU (you have to see black screen with green HTC logo)
Flash firmware-6.12.1540.4
htc_fastboot.exe flash zip firmware-6.12.1540.4.zip (you have to get error, try again this time it will do)
htc_fastboot.exe reboot-bootloader ( do this when firmware process done, you have to see a green bar at 100%)
htc_fastboot.exe erase cache
Flash 6.12.1540.4 RUU
You have to open RUU EXE which downloaded from htc news website.
Wait until UNCOMPRESSING done.
You have to see "License Agreement", DO NOT close this window.
Open your file explorer or run command and type %TEMP% , and click ENTER
You have to be in there "C:\Users\*your pc name*\AppData\Local\Temp"
Find last edited Folder, it must have "corecomp.ini" , "dotnetinstaller.exe" , "ISBEW64.exe" and another Folder.
Open this folder and copy "rom.zip" into your installation folder where htc_fastboot.exe exist.
htc_fastboot.exe oem rebootRUU (you have to see black screen with green HTC logo)
htc_fastboot.exe flash zip rom.zip (first you have to get error, but the process restart automatically)
You have to wait about 5-10 minutes until all processes done.
htc_fastboot.exe reboot-bootloader
htc_fastboot.exe erase cache
PRESS volume down button to do Factory Reset and PRESS power button to select.
Phone restart automatically, when the factory reset done
All done, be happy
Boss pls help me
HTC M8 Sprint
CID : BS_US002
MODEL : OP6B70000
Pls help Me .... when i am try to flash firmware-6.12.1540.4 then error massage
C:\Users\MONOAR\Desktop\One_M8_All-In-One_Kit_v\data>fastboot.exe flash zip firm
ware-6.12.1540.4.zip
< waiting for device >
target reported max download size of 1826414592 bytes
error: cannot load 'firmware-6.12.1540.4.zip': No error
[email protected]
monoar30 said:
HTC M8 Sprint
CID : BS_US002
MODEL : OP6B70000
Pls help Me .... when i am try to flash firmware-6.12.1540.4 then error massage
C:\Users\MONOAR\Desktop\One_M8_All-In-One_Kit_v\data>fastboot.exe flash zip firm
ware-6.12.1540.4.zip
< waiting for device >
target reported max download size of 1826414592 bytes
error: cannot load 'firmware-6.12.1540.4.zip': No error
[email protected]
Click to expand...
Click to collapse
dunno if i m reading that paths wrong but it looks you did something wrong related to the filepaths of the firmware and adb itself. - go into your folder were adb is located. might be inside your One-M8-All-In-One_Kit folder ....then paste the firmware zip in just the same folder. ( location of adb ) ....after that, navigate to that adb location/folder, (you should actually be there because you have just copied the firmware zip into that folder ..so skip that .... press shift + right mousebutton on empty space inside of the folder ( so dont start any program or click on a file, just hold shift and press the right mousekey to open die normal windows dialog window where you can change the view of the folder or add new files etc. )
by using the shift+right mouse key combi, u will see another option inside of that dialog apart from the common stuff you normally have listed. -> "open command prompt right here" ( or something similar, dunno the exact wording in english )
so click that order, it will open up the windows console (cmd) -> make your phone reboot to the bootloader by writing "adb reboot-bootloader" ( i guess it should be obvious that your phone needs to be connected via usb allready )
- ( you can also just hold the power button on your phone and pick bootloader at the boot-menu, just as you like.
- arrived at bootloader, make sure you phone shows "fastboot-usb"
- write "fastboot oem rebootRUU" inside the cmd window -> phone should boot into the RUU modus.
- write "fastboot flash zip firmware-6.12.1540.4.zip" (not fastboot".exe" - just fastboot ... ) -> make sure you use the correct name of the zip. - you need use the filename of the firmware that you ve copied into the adb folder at the beginning. - to prevent issues, you should rename the firmware zip to something simple. - like just firmware.zip or firm.zip, without that versionsnumber. - its just easier for you to write that into the cmd window and you will be sure that issues might be not related to some wrong written filename.
done.
edit: @sceryavuz is htc_fastboot anything special or just the normal adb? if it is different, may you explain to me what it is?
What is the advantage of the Developer edition?
Can I do this with a vzw m8? I want to see if this helps me run GPE and AOSP roms without the cellular issues I've been having. Also, can I change back as well?
Sent from my HTC6525LVW using XDA-Developers mobile app
edit: @sceryavuz is htc_fastboot anything special or just the normal adb? if it is different, may you explain to me what it is?[/QUOTE]
htc_fastboot you need this for flashing firmware. Security reasons. You can't flash recovery, for example with this.
fastboot it's for everithing else, other than firmware.
For me it was like that, at least..
vladaxx said:
What is the advantage of the Developer edition?
Click to expand...
Click to collapse
It is the full unlocked rom, you can do anything with Developer Edition without any errors. This is the most stable version.
Dan Tekle said:
Can I do this with a vzw m8? I want to see if this helps me run GPE and AOSP roms without the cellular issues I've been having. Also, can I change back as well?
Sent from my HTC6525LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't know if it is work or not? I have AT&T device and it works. Sprint and verizon device may have specific modem.
_moelle said:
dunno if i m reading that paths wrong but it looks you did something wrong related to the filepaths of the firmware and adb itself. - go into your folder were adb is located. might be inside your One-M8-All-In-One_Kit folder ....then paste the firmware zip in just the same folder. ( location of adb ) ....after that, navigate to that adb location/folder, (you should actually be there because you have just copied the firmware zip into that folder ..so skip that .... press shift + right mousebutton on empty space inside of the folder ( so dont start any program or click on a file, just hold shift and press the right mousekey to open die normal windows dialog window where you can change the view of the folder or add new files etc. )
by using the shift+right mouse key combi, u will see another option inside of that dialog apart from the common stuff you normally have listed. -> "open command prompt right here" ( or something similar, dunno the exact wording in english )
so click that order, it will open up the windows console (cmd) -> make your phone reboot to the bootloader by writing "adb reboot-bootloader" ( i guess it should be obvious that your phone needs to be connected via usb allready )
- ( you can also just hold the power button on your phone and pick bootloader at the boot-menu, just as you like.
- arrived at bootloader, make sure you phone shows "fastboot-usb"
- write "fastboot oem rebootRUU" inside the cmd window -> phone should boot into the RUU modus.
- write "fastboot flash zip firmware-6.12.1540.4.zip" (not fastboot".exe" - just fastboot ... ) -> make sure you use the correct name of the zip. - you need use the filename of the firmware that you ve copied into the adb folder at the beginning. - to prevent issues, you should rename the firmware zip to something simple. - like just firmware.zip or firm.zip, without that versionsnumber. - its just easier for you to write that into the cmd window and you will be sure that issues might be not related to some wrong written filename.
done.
edit: @sceryavuz is htc_fastboot anything special or just the normal adb? if it is different, may you explain to me what it is?
Click to expand...
Click to collapse
htc_fastboot is stock fastboot that released by htc. You can use your fastboot already have. htc_fastboot check all zip or img file for compatibility.
null0seven said:
edit: @sceryavuz is htc_fastboot anything special or just the normal adb? if it is different, may you explain to me what it is?
htc_fastboot you need this for flashing firmware. Security reasons. You can't flash recovery, for example with this.
fastboot it's for everithing else, other than firmware.
For me it was like that, at least..
Click to expand...
Click to collapse
Yes, mostly agreed (security and compatibility reasons). You can flash TWRP with htc_fastboot
@monoar30 @_moelle @Dan Tekle @null0seven @sceryavuz
hey guys just to make it sense
you can't convert CDMA ( device) firmware to GSM firmware
sprint and Verizon can't be converted to any other GSM firmware
HTC_fastboot used to flash big .zip as you can flash any thing by regular fastboot but RUU.zip needs to be flashed by HTC_fastboot
Did anyone with Verizon M8 manage to install it?
I managed to change CID, MID and install firmware without any errors, but when I try to flash rom.zip it says file is too large. Also the device doesn't recognize SIM card when on Developer Edition firmware. I guess this is because of the hardware difference, we won't be able to get this ROM working.
M.Ned said:
Did anyone with Verizon M8 manage to install it?
I managed to change CID, MID and install firmware without any errors, but when I try to flash rom.zip it says file is too large. Also the device doesn't recognize SIM card when on Developer Edition firmware. I guess this is because of the hardware difference, we won't be able to get this ROM working.
Click to expand...
Click to collapse
you are lucky if your device still working
read the post above yours
you can't flash GSM firmware on CDMA device because the hardware is different
i have a verizon htc one M8, unlocked, S-OFF, SuperCID, rooted, boot loader unlocked working with GSM carrier in India, I unlocked couple more LTE bands etc. Can I flash this as I don't have the CDMA only device?
Chandresh204 said:
i have a verizon htc one M8, unlocked, S-OFF, SuperCID, rooted, boot loader unlocked working with GSM carrier in India, I unlocked couple more LTE bands etc. Can I flash this as I don't have the CDMA only device?
Click to expand...
Click to collapse
if your device hardware match the GSM variant then you can
if didn't then you can't
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**************
(bootloader) imei: 99**************
(bootloader) imei2: Not Support
(bootloader) meid: 99**************
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
--------------------------------------------------------------------------------
Successfully able to change my cid as well as mid as previous its was 0P6B70000
So now i am still not able to install developer version rom
And Successfully flashed firmware-6.12.1540.4.zip
{F:\Utility\Softwares\Mobile Flushing\HTC one m8>fastboot flash zip firmware-6.12.1540.4.zip
sending 'zip' (31625 KB)...
OKAY [ 1.994s]
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) total_image_number=8
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
(bootloader) current_image_number=7
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.177s
F:\Utility\Softwares\Mobile Flushing\HTC one m8>fastboot flash zip firmware-6.12.1540.4.zip
sending 'zip' (31625 KB)...
OKAY [ 2.004s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=16
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,43
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,65
(bootloader) [RUU]UZ,adsp,75
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,45
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(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) current_image_number=2
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=3
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=4
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1,0
(bootloader) [RUU]WP,sbl1,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) current_image_number=6
(bootloader) start image[sdi] unzipping & flushing...
(bootloader) [RUU]UZ,sdi,0
(bootloader) [RUU]UZ,sdi,100
(bootloader) [RUU]WP,sdi,0
(bootloader) [RUU]WP,sdi,100
(bootloader) ...... Successful
(bootloader) current_image_number=7
(bootloader) start image[sensor_hub] unzipping & flushing...
(bootloader) [RUU]UZ,sensor_hub,0
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) [RUU]WP,sensor_hub,0
(bootloader) [RUU]WP,sensor_hub,4
(bootloader) [RUU]WP,sensor_hub,8
(bootloader) [RUU]WP,sensor_hub,12
(bootloader) [RUU]WP,sensor_hub,16
(bootloader) [RUU]WP,sensor_hub,20
(bootloader) [RUU]WP,sensor_hub,24
(bootloader) [RUU]WP,sensor_hub,28
(bootloader) [RUU]WP,sensor_hub,32
(bootloader) [RUU]WP,sensor_hub,36
(bootloader) [RUU]WP,sensor_hub,40
(bootloader) [RUU]WP,sensor_hub,44
(bootloader) [RUU]WP,sensor_hub,48
(bootloader) [RUU]WP,sensor_hub,52
(bootloader) [RUU]WP,sensor_hub,56
(bootloader) [RUU]WP,sensor_hub,60
(bootloader) [RUU]WP,sensor_hub,64
(bootloader) [RUU]WP,sensor_hub,68
(bootloader) [RUU]WP,sensor_hub,72
(bootloader) [RUU]WP,sensor_hub,76
(bootloader) [RUU]WP,sensor_hub,80
(bootloader) [RUU]WP,sensor_hub,84
(bootloader) [RUU]WP,sensor_hub,88
(bootloader) [RUU]WP,sensor_hub,92
(bootloader) [RUU]WP,sensor_hub,96
(bootloader) [RUU]WP,sensor_hub,100
(bootloader) ...... Successful
(bootloader) current_image_number=8
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=9
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ..... Bypassed
(bootloader) current_image_number=10
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ..... Bypassed
(bootloader) current_image_number=11
(bootloader) start image[tz] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=12
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=13
(bootloader) start image[radio] unzipping & flushing...
(bootloader) trying to rename MBA
(bootloader) ...... Successful
(bootloader) current_image_number=14
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) current_image_number=15
OKAY [ 59.617s]
finished. total time: 61.621s }
---------------------------------------------------
and when i am flashing rom.zip then its saying
F:\Utility\Softwares\Mobile Flushing\HTC one m8>fastboot flash zip rom.zip
load_file: could not allocate 1574717756 bytes
error: cannot load 'rom.zip'
so what should i do
Shakil Murm said:
(bootloader) product: m8_whl
Click to expand...
Click to collapse
Your device is m8_whl and this RUU is meant for m8_ul or m8_ul_ca only.
Return to stock .. if you're lucky you still can use your device but lose the ability to connect to 3G/4G/LTE.
(because you most probably already bricked the radio after your flash the firmware which is not meant for your device variant)
ckpv5 said:
Your device is m8_whl and this RUU is meant for m8_ul or m8_ul_ca only.
Return to stock .. if you're lucky you still can use your device but lose the ability to connect to 3G/4G/LTE.
(because you most probably already bricked the radio after your flash the firmware which is not meant for your device variant)
Click to expand...
Click to collapse
i'm trying to tell them that this method works on GSM devices only but no one read
please @sceryavuz ADD IT TO OP THIS METHOD WORKS ON GSM DEVICES ONLY NO VERIZON OR SPRINT
please ckpv5 am i right or not ??
RUU Not Working?
Hi,
I followed your instructions and the Developer Edition rom flashed and appears to be working fine, thanks very much.
After setting the phone up I wanted to try and test flashing again with RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe . The process fails after "Verifying information on your Android phone. Please wait..." with ERROR 170 USB CONNECTION ERROR. I've checked and the USB connection seems to be fine. Is this to be expected?
Thanks again.
0graham0 said:
Hi,
I followed your instructions and the Developer Edition rom flashed and appears to be working fine, thanks very much.
After setting the phone up I wanted to try and test flashing again with RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe . The process fails after "Verifying information on your Android phone. Please wait..." with ERROR 170 USB CONNECTION ERROR. I've checked and the USB connection seems to be fine. Is this to be expected?
Thanks again.
Click to expand...
Click to collapse
run the RUU while the device boot into fastboot and use USB 2 not USB 3
Sent from my HTC One M8 using XDA Labs
ahmed.ismael said:
run the RUU while the device boot into fastboot and use USB 2 not USB 3
Click to expand...
Click to collapse
ah, that did the trick. thanks very much.
I was unable to flash the rom.zip with google's fastboot.exe (recogniced wrong size, header error, etc.....)!
Use htc_fastboot.exe found in the same temporary folder as rom.zip!
Worked for me. Why flash firmware first??
OP instructions worked for me . Was coming from US AT&T / Cingular (Cricket?)
Why did we flash firmware zip firmware and THEN flash the RUU pulled from the temp folder?

Motorola XT1644 No Service

i got 3 phones with the same problem. phone is brand new never used... BUT one this written on top is MOTOROLA CONFIDENTIAL PROPERTY: NOT FOR SALE... so i wonder is this possible to get signal on this device?
i flashed with XT1644_ATHENE_RETUS_MPJ24.139-48_cid50_subsidy-DEFAULT_regulatory-XT1644_CFC.xml but problem is the same... when search for network it shows "error while searching network".
here is fastboot info
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: Athene_16MP
(bootloader) board: Athene_16MP
(bootloader) secure: no
(bootloader) hwrev: P1A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB TOSHIBA 032G32 RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: NADI110010
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 7C0B3E0000000000000000000000
(bootloader) securestate: engineering
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 3541150xxxxxxxx
(bootloader) meid:
(bootloader) date: 12-24-2015
(bootloader) sku: XTBLAH
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jul 29 4:38:35 UTC 1971"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-48/48:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.31.48.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband: M8952_70009.08.03.45R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.10.84-g06a4fb5 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld35) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Sun Jun 5 11:16:49 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.129s
nomi_42us said:
i got 3 phones with the same problem. phone is brand new never used... BUT one this written on top is MOTOROLA CONFIDENTIAL PROPERTY: NOT FOR SALE... so i wonder is this possible to get signal on this device?
i flashed with XT1644_ATHENE_RETUS_MPJ24.139-48_cid50_subsidy-DEFAULT_regulatory-XT1644_CFC.xml but problem is the same... when search for network it shows "error while searching network".
Click to expand...
Click to collapse
Try different SIM card
HueyT said:
Try different SIM card
Click to expand...
Click to collapse
Already did but same problem
nomi_42us said:
Already did but same problem
Click to expand...
Click to collapse
Try to cut a piece of 3"X5" index card to same size as sim card and put it under sim as you're inserting into slot. Maybe this will improve contact to phone? Otherwise, I have no clue if you still have this problem after reflashing N stock rom using FASTBOOT.
HueyT said:
Try to cut a piece of 3"X5" index card to same size as sim card and put it under sim as you're inserting into slot. Maybe this will improve contact to phone? Otherwise, I have no clue if you still have this problem after reflashing N stock rom using FASTBOOT.
Click to expand...
Click to collapse
there is no sim tray/slot in this model. sim is directly inserted in phone... anyone else have any clue?
nomi_42us said:
there is no sim tray/slot in this model. sim is directly inserted in phone... anyone else have any clue?
Click to expand...
Click to collapse
How are you inserting your SIM card into your device?
Hmm, that device does not look healthy regardless:
1) If this was a genuine engineering sample, then it may have certain functions disabled depending on what stage of development it came from. The IMEI may also not be registered. Alternatively, it might have been misflashed before you got it.
2)CID of 0xDEAD and a baseband of DFLT_FSG suggest a bad flash too. I don't know if flashing a correct HW partition to the device would allow it to recognise the SIM (or at least assign the correct radio settings).
3)Attempting to flash further on engineering state devices might cause boot looping as pointed out by acejavelin https://forums.lenovo.com/t5/MOTORO...g-and-Unlocked-bootloader-status/td-p/3420219
I'd suggest, if you can, to return the phone and get a refund, this device might be more trouble than it's worth.
there is inside info from phone. and i do repair phones and customer gave me even dead warranty so i can do all tries without worry, so if there is any possible solution i am willing to try...
{
"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"
}
nomi_42us said:
there is inside info from phone. and i do repair phones and customer gave me even dead warranty so i can do all tries without worry, so if there is any possible solution i am willing to try...
Click to expand...
Click to collapse
Stick an active SIM card from your cell provider in SIM1 slot. The far left is MicroSD. The middle one is SIM1. The far right is SIM2.
HueyT said:
Stick an active SIM card from your cell provider in SIM1 slot. The far left is MicroSD. The middle one is SIM1. The far right is SIM2.
Click to expand...
Click to collapse
already tried that one also as per my knowledge network is locked because of test unit. i want to gain access by any way. because radio is always off. want to know is it possible to turn it on?
nomi_42us said:
already tried that one also as per my knowledge network is locked because of test unit. i want to gain access by any way. because radio is always off. want to know is it possible to turn it on?
Click to expand...
Click to collapse
Try the Secret menu in phone dialer to enable radio :
*#*#4636#*#*
then chose "enable radio" mode or change to "USA band" on upper right corner of menu.
Its easy too fix if you are in Pk,
karachi.
nomi_42us said:
there is inside info from phone. and i do repair phones and customer gave me even dead warranty so i can do all tries without worry, so if there is any possible solution i am willing to try...
Click to expand...
Click to collapse
Salik Iqbal said:
Its easy too fix if you are in Pk,
karachi.
Click to expand...
Click to collapse
i am not in karachi but if you give me working solution i can pay you for that
nomi_42us said:
i am not in karachi but if you give me working solution i can pay you for that
Click to expand...
Click to collapse
check your imei, it could be zero (0).
if it is, you need to change your modem to dsds.
read this guide its for z play, but you can apply it to g4 plus also
https://forum.xda-developers.com/moto-z-play/how-to/guide-to-enable-dualsim-singlesim-t3570601

fastboot flash boot FAILED

Edit 2: Ok I think I'm good now. For some reason, I had to keep unplugging/replugging the USB cable, running "fastboot oem fb_mode_set" again, and continue from the last command that failed
I'm in the middle of flashing the 137-93-10 update via fastboot and when I got to the flash boot step, I got a FAILED message
{
"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"
}
I tried doing it twice and got slightly different errors
I'm currently still sitting in the bootloader, and I'm incredibly afraid of continuing with a potentially messed up boot partition. How should I proceed at this point?
Edit: Here's my command history if it helps:
Code:
D:\Box Sync\Default Sync Folder\android-sdk-windows\platform-tools>fastboot devices
ZY224LGXGS fastboot
D:\Box Sync\Default Sync Folder\android-sdk-windows\platform-tools>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.004s]
finished. total time: 0.005s
D:\Box Sync\Default Sync Folder\android-sdk-windows\platform-tools>fastboot flash partition 137-93-10\gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.164s]
finished. total time: 0.171s
D:\Box Sync\Default Sync Folder\android-sdk-windows\platform-tools>fastboot flash bootloader 137-93-10\bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.138s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.659s]
finished. total time: 0.799s
D:\Box Sync\Default Sync Folder\android-sdk-windows\platform-tools>fastboot flash logo 137-93-10\logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.060s]
writing 'logo'...
OKAY [ 0.109s]
finished. total time: 0.171s
D:\Box Sync\Default Sync Folder\android-sdk-windows\platform-tools>fastboot flash boot 137-93-10\boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target didn't report max-download-size
sending 'boot' (16384 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.005s
D:\Box Sync\Default Sync Folder\android-sdk-windows\platform-tools>fastboot flash boot 137-93-10\boot.img
target didn't report max-download-size
sending 'boot' (16384 KB)...
FAILED (command write failed (No error))
finished. total time: 0.006s

Categories

Resources