Moto E4 Bricked - Moto E4 Questions & Answers

Hello, First of all, excuse my bad English.
I have a Moto E4, which I had with Magisk, the following happened ...
I downloaded a module and the cell phone I keep working on the logo.
I tried to flash a stock rom, but there were no positive results, directly the cell phone at that time did not come out of "Recovery"
Search thousands of sites, download thousands of Stock's Roms, but no luck, no Rom works for me.
I tried to put Lineage Os on it and it tells me that it is only for Moviles Perry and it told me that I had a Cedric.
Look for a Rom that contains "Cedric" but there was no result, try to install different Roms but the same error as always.
"Zip file is invalid, etc" This happens with "TWRP"
and so with everything.
My device says the following when turning on.
-------------------------------------------------- ----------------------------------------
"AP Fastboot Flash Mode (Secure)
BL: BA. 34 (sha-c2e3dec, 2018-12-18 14:33:15)
Baseband <not found>
Product / Variant: Perry XT1768 16GB P3B
Serial Number: ZY2246DMSQ
CPU: MSM8917
eMMC: 16GB SAMSUNG QE13MB RV = 08 PV = 0D FV = 000000000000000D
DRAM = 2GB SAMSUNG LP3 DIE = 8Gb M5 = 01 M6 = 05 M7 = 00 M8 = 1F
Console [NULL] null
Tools Mode Config: DISABLED
Battery OK
Flashing_unlocked
Software status: Modified
Connect USB Data Cable
-------------------------------------------------- ----------------------------------------------
Then try to install the roms with Fastboot
And it returns this error in all steps.
-------------------------------------------------- --------------------------------------------
C: \ Program Files \ Minimal ADB and Fastboot> fastboot flash partition "C: \ Users \ Esmoli Denisse A \ Desktop \ mfastboot_adb_tools_HardReset_info_mEUsaYg \ mfastboot \ 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.067s]
writing 'partition' ...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Canceling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.199s
C: \ Program Files \ Minimal ADB and Fastboot>
-------------------------------------------------- -------------------------------------------------- ----
I read in many places that it is because of the "Rom Stock" that it is outdated or is not compatible with my phone, but I don't know what else to try. I tried mostly all the "Rom"
To finish "RSD Lite" the cell phone does not recognize me, I already downloaded all the drivers and nothing.
Any solution? What else can I try? Is there a "Rom" for my device?
Thank you.

A quick Google search shows that "Cedric" is a Moto G5. You need to go to the Moto G5 forums and search for what you need there.

Related

[How to] flash Lollipop on Desire 820 dual sim Non-Indian variant. Fix Wrong Variant

Hi guys, so a friend of mine got a Desire 820 dual sim few days back. Device came in a very messy condition in terms for software. It was already Super CID'd & S-OFFed, no option to update software & around 200 languages. So i tried different threads to fix the issue & upgrade the phone to Lollipop.
I was able to get it back to stock Indian KK RUU 1.22.720.1 assuming that it was an Indian variant based on its id A51_DTUL but it was not the case.. After downloading the 1.22.720.10 update, it was giving me error like Modified System or Wrong Variant
Cut short i managed to identify / fix the problem & successfully upgraded the phone to Android L
Story line is that most of the guides available for 820 dual sim Lollipop upgrade are for the Indian variant with MID 0PFJ10000. Problem occurring is with its Chinesse sibbling with MID 0PFJ11000 & this is where the phone wont allow you to do software updates.
RUU is just checking the CID while in the OTA updater-script they have plenty of checks before flashing it.
So in the below KK updater-script, you can see that first it is checking for the current firmware, then CID & then MID
PHP:
mount("ext4", "EMMC", "system", "/system");
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/htc_asia_india/htc_a51dtul:4.4.4/KTU84P/429556.1:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/htc_asia_india/htc_a51dtul:4.4.4/KTU84P/429556.10:user/release-keys");
assert(file_getprop("/system/build.prop", "ro.aa.taskid") == "402794" ||
file_getprop("/system/build.prop", "ro.aa.taskid") == "447333");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__038") == "t");
);
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "0PFJ10000") == "t");,
assert(check_mid("simple", "0PFJ10000") == "t");
This is point where we get Wrong Variant or Modified System error on device other than 0PFJ10000 MID.
So inorder to get rid of this error & getting all the updates automatically while keeping your ROM in stock status. These are the requirements / guidelines.
Required:
S-OFF
Root
Super CID
I assume you already know about fastboot commands stuff
So before proceeding, verify that you phone is A51_DTUL & the processor type is hTCBmsm8939 with 2GB of RAM. You can do this by booting into bootloader & run command fastboot getvar all
1st step, change MID of your device -> from 0PFJ11000 to 0PFJ10000. Run the following ADB commands:
PHP:
adb shell
su
echo -ne '\x30\x00\x50\x00\x46\x00\x4a\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
exit
adb reboot bootloader
Now once the commands are successful, to verify the MID in fastboot again verify it with command fastboot getvar MID. It should now be 0PFJ10000
So we killed the BUG :laugh:
2nd step:
2a. download Indian KK RUU from this thread -> Thanks to sshivampp & robinsahlot
2b. Rename the downloaded ZIP to “0PFJIMG.zip” or to 0PFJIMG.txt incase you are unable to copy it
2c. Copy the 0PFJIMG.txt / zip file to the External SD card & do change the extension back to .zip incase you had to change it to .txt
2d. Reboot into bootloader & dont forget to disable Fastboot option under power settings
2e. Press Vol up for update once prompted
You will lot of checks & update prompts on the screen
Once successful, reboot the phone & check for software updates. You should now be able to install all the OTAs without any errors
Special thanks to h1dd3n_sn1p3r for his initial guide on upgrading to Android L.
And our dexter, Mr. scotty1223 for his amazing guides & work. Through which i was able to figure out MID change part
Lovely! Thanks for credit towards me!
Excellent find bro ?
Any one knows MID of HK variant?
help
Hey, thanks for this post, i have tried every solution posted in this site, but anyone of them worked, this one seems the most effective one, but i cant change the MID! I copy the code, hit enter, the window closes, but when i reboot the phone and check de getvar mid, it doesnt change! what can i do? i have the phone in S-OFF, rooted and super CID... the phone was unlocked, tried this way, but now is relocked, tried this one also but its the same MID ..thaks for the help u can give me
ok i try some of the code, just to avoid the window from closing and it says this :
adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found...
gpcga said:
Hey, thanks for this post, i have tried every solution posted in this site, but anyone of them worked, this one seems the most effective one, but i cant change the MID! I copy the code, hit enter, the window closes, but when i reboot the phone and check de getvar mid, it doesnt change! what can i do? i have the phone in S-OFF, rooted and super CID... the phone was unlocked, tried this way, but now is relocked, tried this one also but its the same MID ..thaks for the help u can give me
ok i try some of the code, just to avoid the window from closing and it says this :
adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found...
Click to expand...
Click to collapse
What is the current MID of your device? also is it Qualcomm processor? If you boot the phone nornally with ADB debugging. is it detected? as from the last line it seems device is not connected or not detected
I changed the recovery
Hello, the phone didn't connect because of the recovery, I flashed another one, and that was it. Thanks, I have the stock lollipop 5.0.2 now. This is the only solution that worked fast and effective.
fshami said:
What is the current MID of your device? also is it Qualcomm processor? If you boot the phone nornally with ADB debugging. is it detected? as from the last line it seems device is not connected or not detected
Click to expand...
Click to collapse
Would this method work on my Chinese Desire 820t?
sponmagnet said:
Would this method work on my Chinese Desire 820t?
Click to expand...
Click to collapse
This thread is for the non-indian variants with Qualcomm chipset.. all details in first post. So if u have the same mid OPFJ11xxx then go a head & try.. be sure ur hardware specs match as i mentioned in the guide
Can anybody post instructions of how to change MID to TW variant? (-> from 0PFJ10000 to 0PFJ12000)
Prowler_gr said:
Can anybody post instructions of how to change MID to TW variant? (-> from 0PFJ10000 to 0PFJ12000)
Click to expand...
Click to collapse
PHP:
adb shell
su
echo -ne '\x30\x00\x50\x00\x46\x00\x4a\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
exit
adb reboot bootloader
I am getting error
"adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found..."
Device is connected !!!
I tried everything but nothing works...
I want my phone to run on lollipop
please help me
shubhamkanwaria said:
I am getting error
"adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found..."
Device is connected !!!
I tried everything but nothing works...
I want my phone to run on lollipop
please help me
Click to expand...
Click to collapse
Check if USB debugging is enabled.. and after connecting the phone, all drivers are installed properly
fshami said:
Check if USB debugging is enabled.. and after connecting the phone, all drivers are installed properly
Click to expand...
Click to collapse
USB debugging is enabled and all drivers are properly installed but still same error.
shubhamkanwaria said:
USB debugging is enabled and all drivers are properly installed but still same error.
Click to expand...
Click to collapse
If your phone is booted, still adb devices command is not showing your device?
Sent from my HTC One E9PLUS dual sim using XDA-Developers mobile app
fshami said:
If your phone is booted, still adb devices command is not showing your device?
Sent from my HTC One E9PLUS dual sim using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you so much... i got it... Now my phone running on lollipop.....
shubhamkanwaria said:
Thank you so much... i got it... Now my phone running on lollipop.....
Click to expand...
Click to collapse
glad to help
fshami said:
Hi guys, so a friend of mine got a Desire 820 dual sim few days back. Device came in a very messy condition in terms for software. It was already Super CID'd & S-OFFed, no option to update software & around 200 languages. So i tried different threads to fix the issue & upgrade the phone to Lollipop.
I was able to get it back to stock Indian KK RUU 1.22.720.1 assuming that it was an Indian variant based on its id A51_DTUL but it was not the case.. After downloading the 1.22.720.10 update, it was giving me error like Modified System or Wrong Variant
Cut short i managed to identify / fix the problem & successfully upgraded the phone to Android L
Story line is that most of the guides available for 820 dual sim Lollipop upgrade are for the Indian variant with MID 0PFJ10000. Problem occurring is with its Chinesse sibbling with MID 0PFJ11000 & this is where the phone wont allow you to do software updates.
RUU is just checking the CID while in the OTA updater-script they have plenty of checks before flashing it.
So in the below KK updater-script, you can see that first it is checking for the current firmware, then CID & then MID
PHP:
mount("ext4", "EMMC", "system", "/system");
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/htc_asia_india/htc_a51dtul:4.4.4/KTU84P/429556.1:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/htc_asia_india/htc_a51dtul:4.4.4/KTU84P/429556.10:user/release-keys");
assert(file_getprop("/system/build.prop", "ro.aa.taskid") == "402794" ||
file_getprop("/system/build.prop", "ro.aa.taskid") == "447333");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__038") == "t");
);
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "0PFJ10000") == "t");,
assert(check_mid("simple", "0PFJ10000") == "t");
This is point where we get Wrong Variant or Modified System error on device other than 0PFJ10000 MID.
So inorder to get rid of this error & getting all the updates automatically while keeping your ROM in stock status. These are the requirements / guidelines.
Required:
S-OFF
Root
Super CID
I assume you already know about fastboot commands stuff
So before proceeding, verify that you phone is A51_DTUL & the processor type is hTCBmsm8939 with 2GB of RAM. You can do this by booting into bootloader & run command fastboot getvar all
1st step, change MID of your device -> from 0PFJ11000 to 0PFJ10000. Run the following ADB commands:
PHP:
adb shell
su
echo -ne '\x30\x00\x50\x00\x46\x00\x4a\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
exit
adb reboot bootloader
Now once the commands are successful, to verify the MID in fastboot again verify it with command fastboot getvar MID. It should now be 0PFJ10000
So we killed the BUG :laugh:
2nd step:
2a. download Indian KK RUU from this thread -> Thanks to sshivampp & robinsahlot
2b. Rename the downloaded ZIP to “0PFJIMG.zip” or to 0PFJIMG.txt incase you are unable to copy it
2c. Copy the 0PFJIMG.txt / zip file to the External SD card & do change the extension back to .zip incase you had to change it to .txt
2d. Reboot into bootloader & dont forget to disable Fastboot option under power settings
2e. Press Vol up for update once prompted
You will lot of checks & update prompts on the screen
Once successful, reboot the phone & check for software updates. You should now be able to install all the OTAs without any errors
Special thanks to h1dd3n_sn1p3r for his initial guide on upgrading to Android L.
And our dexter, Mr. scotty1223 for his amazing guides & work. Through which i was able to figure out MID change part
Click to expand...
Click to collapse
sorry .. this is no more available .. please check the next replay #18
fshami said:
Hi guys, so a friend of mine got a Desire 820 dual sim few days back. Device came in a very messy condition in terms for software. It was already Super CID'd & S-OFFed, no option to update software & around 200 languages. So i tried different threads to fix the issue & upgrade the phone to Lollipop.
I was able to get it back to stock Indian KK RUU 1.22.720.1 assuming that it was an Indian variant based on its id A51_DTUL but it was not the case.. After downloading the 1.22.720.10 update, it was giving me error like Modified System or Wrong Variant
Cut short i managed to identify / fix the problem & successfully upgraded the phone to Android L
Story line is that most of the guides available for 820 dual sim Lollipop upgrade are for the Indian variant with MID 0PFJ10000. Problem occurring is with its Chinesse sibbling with MID 0PFJ11000 & this is where the phone wont allow you to do software updates.
RUU is just checking the CID while in the OTA updater-script they have plenty of checks before flashing it.
So in the below KK updater-script, you can see that first it is checking for the current firmware, then CID & then MID
PHP:
mount("ext4", "EMMC", "system", "/system");
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/htc_asia_india/htc_a51dtul:4.4.4/KTU84P/429556.1:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc/htc_asia_india/htc_a51dtul:4.4.4/KTU84P/429556.10:user/release-keys");
assert(file_getprop("/system/build.prop", "ro.aa.taskid") == "402794" ||
file_getprop("/system/build.prop", "ro.aa.taskid") == "447333");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__038") == "t");
);
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "0PFJ10000") == "t");,
assert(check_mid("simple", "0PFJ10000") == "t");
This is point where we get Wrong Variant or Modified System error on device other than 0PFJ10000 MID.
So inorder to get rid of this error & getting all the updates automatically while keeping your ROM in stock status. These are the requirements / guidelines.
Required:
S-OFF
Root
Super CID
I assume you already know about fastboot commands stuff
So before proceeding, verify that you phone is A51_DTUL & the processor type is hTCBmsm8939 with 2GB of RAM. You can do this by booting into bootloader & run command fastboot getvar all
1st step, change MID of your device -> from 0PFJ11000 to 0PFJ10000. Run the following ADB commands:
PHP:
adb shell
su
echo -ne '\x30\x00\x50\x00\x46\x00\x4a\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
exit
adb reboot bootloader
Now once the commands are successful, to verify the MID in fastboot again verify it with command fastboot getvar MID. It should now be 0PFJ10000
So we killed the BUG :laugh:
2nd step:
2a. download Indian KK RUU from this thread -> Thanks to sshivampp & robinsahlot
2b. Rename the downloaded ZIP to “0PFJIMG.zip” or to 0PFJIMG.txt incase you are unable to copy it
2c. Copy the 0PFJIMG.txt / zip file to the External SD card & do change the extension back to .zip incase you had to change it to .txt
2d. Reboot into bootloader & dont forget to disable Fastboot option under power settings
2e. Press Vol up for update once prompted
You will lot of checks & update prompts on the screen
Once successful, reboot the phone & check for software updates. You should now be able to install all the OTAs without any errors
Special thanks to h1dd3n_sn1p3r for his initial guide on upgrading to Android L.
And our dexter, Mr. scotty1223 for his amazing guides & work. Through which i was able to figure out MID change part
Click to expand...
Click to collapse
my data before :
D:\HTC\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.01.010_U1030481_08.01.41119
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.22.720.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4ANYC01045
(bootloader) imei: 355386060878133
(bootloader) imei2: 355386060878141
(bootloader) meid: 00000000000000
(bootloader) product: a51_dtul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ11000
(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: ed7d3c37
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name:
all: Done!
finished. total time: 0.022s
D:\HTC\fastboot>
and do :
D:\HTC\fastboot>adb shell
[email protected]_a51dtul:/ $ su
[email protected]_a51dtul:/ # echo -ne '\x30\x00\x50\x00\x46\x00\x4a\x00\x31\x00\x30\x0>
17+0 records in
17+0 records out
17 bytes transferred in 0.005 secs (3400 bytes/sec)
[email protected]_a51dtul:/ # exit
[email protected]_a51dtul:/ $ exit
so the data after :
D:\HTC\fastboot>fastboot getvar mid
mid: 0PFJ10000
finished. total time: 0.002s
D:\HTC\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.01.010_U1030481_08.01.41119
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.22.720.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4ANYC01045
(bootloader) imei: 355386060878133
(bootloader) imei2: 355386060878141
(bootloader) meid: 00000000000000
(bootloader) product: a51_dtul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ10000
(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: ed7d3c37
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name:
all: Done!
finished. total time: 0.034s
D:\HTC\fastboot>
checked update .. 70.01MB .. downloaded .. but still got the msg (your system modified contact htc)
#Note : i was downloaded the ruu that you mention .. just changed mid then checked update
any help ??
nabilovetch said:
my data before :
D:\HTC\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.01.010_U1030481_08.01.41119
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.22.720.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4ANYC01045
(bootloader) imei: 355386060878133
(bootloader) imei2: 355386060878141
(bootloader) meid: 00000000000000
(bootloader) product: a51_dtul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ11000
(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: ed7d3c37
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name:
all: Done!
finished. total time: 0.022s
D:\HTC\fastboot>
and do :
D:\HTC\fastboot>adb shell
[email protected]_a51dtul:/ $ su
[email protected]_a51dtul:/ # echo -ne '\x30\x00\x50\x00\x46\x00\x4a\x00\x31\x00\x30\x0>
17+0 records in
17+0 records out
17 bytes transferred in 0.005 secs (3400 bytes/sec)
[email protected]_a51dtul:/ # exit
[email protected]_a51dtul:/ $ exit
so the data after :
D:\HTC\fastboot>fastboot getvar mid
mid: 0PFJ10000
finished. total time: 0.002s
D:\HTC\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 01.01.010_U1030481_08.01.41119
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.22.720.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4ANYC01045
(bootloader) imei: 355386060878133
(bootloader) imei2: 355386060878141
(bootloader) meid: 00000000000000
(bootloader) product: a51_dtul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ10000
(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: ed7d3c37
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name:
all: Done!
finished. total time: 0.034s
D:\HTC\fastboot>
checked update .. 70.01MB .. downloaded .. but still got the msg (your system modified contact htc)
#Note : i was downloaded the ruu that you mention .. just changed mid then checked update
any help ??
Click to expand...
Click to collapse
Good you've changed CID & MID. Now download & flash the RUU i mentioned. Once flashed then your device will do updates
Sent from my HTC One E9PLUS dual sim using XDA-Developers mobile app
fshami said:
Good you've changed CID & MID. Now download & flash the RUU i mentioned. Once flashed then your device will do updates
Sent from my HTC One E9PLUS dual sim using XDA- mobile app
Click to expand...
Click to collapse
i do factory reset and reflash ruu using sd card ..
still got the msg (your software is modified, contact htc)

[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?

Update my M9+

Hello,
I would like to update my HTC M9+.
The current version is :
Android : 5.0.2
HTC Sense : 7.0
base band : 1.1506V24P59.2508.1008_HTW
build : 1.03.708.12 CL608897 release-keys
cid: HTC--622
I live in France, but I've bought my phone on internet, and I think it come from Hong-Kong...
I don't know wich update I have to use...
Can you help me ?
(sorry for my English, it's not my native language...).
I asked the customer service about this problem
The answer was the package on the internet not working and you have to give us your phone to update it
Sent from my HTC One M9PLUS using XDA-Developers Legacy app
So... the best way is to buy a new phone...
fanfanus said:
So... the best way is to buy a new phone...
Click to expand...
Click to collapse
Hi, can you please share all the details about your phone with "fastboot getvar all" ? Do you know about this ?
After this you need to S-OFF with sunshine apk and come back to me here will give you instructons more....
Cheers!
P
Peacemaker69 said:
Hi, can you please share all the details about your phone with "fastboot getvar all" ? Do you know about this ?
Click to expand...
Click to collapse
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaur_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.03.708.12
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711001
(bootloader) cid: HTC__622
all:
finished. total time: 0.003s
Peacemaker69 said:
After this you need to S-OFF with sunshine apk and come back to me here will give you instructons more....P
Click to expand...
Click to collapse
It's done.
fanfanus said:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaur_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: 358812064*****xxx
(bootloader) version-main: 1.03.708.12
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711001
(bootloader) cid: HTC__622
all:
finished. total time: 0.003s
It's done.
Click to expand...
Click to collapse
Ok... Did take S-OFF with sunshine apk ?
P.S. Remove your IMEI from here...
Yes i use sunshine apk to the S-OFF
fanfanus said:
Yes i use sunshine apk to the S-OFF
Click to expand...
Click to collapse
Ok, do you want to flash EU version to your phone? Because you are in EU as I can see... So am I...
Let me know....
Peacemaker69 said:
Ok, do you want to flash EU version to your phone? Because you are in EU as I can see... So am I...
Let me know....
Click to expand...
Click to collapse
Sure ! If it's work.
I read some componentes of the phone could change with the asian versions ? Is il not a prob ?
fanfanus said:
Sure ! If it's work.
I read some componentes of the phone could change with the asian versions ? Is il not a prob ?
Click to expand...
Click to collapse
Yup, it is but I'm not 100% sure.. Your version is from Hong Kong and it is "Supreme camera".... Correct ?
Alright, let's start...
First you need to change your CID...
---Before start flashing you need to download my ABD files... Check attached files down below
---Create some backup of your system before doing this !
Down this:
https://androidfilehost.com/?fid=745425885120699799
1. Go into Download mode and type command:
fastboot oem writecid HTC__621
2. Then command: fastboot reboot ... After that for and check if you CID has changed.. After go again to Download mode.
3. Rename zip file to 0PK7IMG.zip --must be putted in the same folder with fastboot ADB !!!!
4. fastboot oem rebootRUU
5. fastboot flash zip 0PK7IMG.zip
6. fastboot reboot
If you got some error message just let me know...
Cheers!
P
Peacemaker69 said:
5. fastboot flash zip 0PK7IMG.zip
Click to expand...
Click to collapse
ahah my SD card is too little...
Code:
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (8512 KB)...
OKAY [ 1.299s]
writing 'zip'...
(bootloader) HOSD CL#608897
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 2.376s
htc_fastboot finished. total time: 5.293s
fanfanus said:
ahah my SD card is too little...
Code:
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (8512 KB)...
OKAY [ 1.299s]
writing 'zip'...
(bootloader) HOSD CL#608897
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 2.376s
htc_fastboot finished. total time: 5.293s
Click to expand...
Click to collapse
You can try to install this with TWRP recovery If you have installed... Try that
Hello,
I try with a new SD card.
For the asian ROM you give me :
Code:
C:\Users\fanfa\Desktop\tempo\fastboot_adb>fastboot flash zip 0PK7IMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (8376 KB)...
OKAY [ 1.338s]
writing 'zip'...
(bootloader) HOSD CL#608897
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 2.412s
htc_fastboot finished. total time: 22.947s
And I try with the UE version (1.90) :
Code:
C:\Users\fanfa\Desktop\tempo\fastboot_adb>fastboot flash zip 0PK7IMG_EU.zip
htc_fastboot v3.0.9.2 (2015-05-29)
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (78987 KB)...
OKAY [ 3.854s]
writing 'zip'...
(bootloader) HOSD CL#608897
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7: fail to flash via downloadzip)
finished. total time: 4.988s
htc_fastboot finished. total time: 12.511s
Any suggestion ?
Thanks
fanfanus said:
Hello,
I try with a new SD card.
For the asian ROM you give me :
Code:
C:\Users\fanfa\Desktop\tempo\fastboot_adb>fastboot flash zip 0PK7IMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (8376 KB)...
OKAY [ 1.338s]
writing 'zip'...
(bootloader) HOSD CL#608897
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22: fail to flash via downloadzip)
finished. total time: 2.412s
htc_fastboot finished. total time: 22.947s
And I try with the UE version (1.90) :
Code:
C:\Users\fanfa\Desktop\tempo\fastboot_adb>fastboot flash zip 0PK7IMG_EU.zip
htc_fastboot v3.0.9.2 (2015-05-29)
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (78987 KB)...
OKAY [ 3.854s]
writing 'zip'...
(bootloader) HOSD CL#608897
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7: fail to flash via downloadzip)
finished. total time: 4.988s
htc_fastboot finished. total time: 12.511s
Any suggestion ?
Thanks
Click to expand...
Click to collapse
Hi again,
Did you try to change your CID ? Install TWRP and then flash the file that I give you and let me know... Do you know how to change your CID and install TWRP ?
Peacemaker69 said:
Did you try to change your CID ?
Click to expand...
Click to collapse
I succeed to install the europe version. I change the CID with a super CID :
Code:
fastboot oem writecid 11111111
It's working but.... only self-portrait is aviable in camera !
fanfanus said:
I succeed to install the europe version. I change the CID with a super CID :
Code:
fastboot oem writecid 11111111
It's working but.... only self-portrait is aviable in camera !
Click to expand...
Click to collapse
How did you install with fastboot or SD card or via TWRP? and which version of ?
I use fastbook.
now :
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.90.401.3
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711001
(bootloader) cid: 11111111
Android is always 5.0.2
The phone ask me to install android 6.0 with this version. But It refuse to intall it because my phone was modified...
fanfanus said:
I use fastbook.
now :
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: 358812064194422
(bootloader) version-main: 1.90.401.3
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711001
(bootloader) cid: 11111111
Android is always 5.0.2
The phone ask me to install android 6.0 with this version. But It refuse to intall it because my phone was modified...
Click to expand...
Click to collapse
You can change your CID If you find Asia RUUs with 6.0 version... Other way is to flash "CleanSlate 2.0 rom" via TWRP,,, and see if that would helps..
Here you can download CleanSlate 2.0 rom :
https://forum.xda-developers.com/on...nslate-1-0-world-wide-edition-t3120017/page36
I foud this version :
0PK7IMG_HIAUR_ML_TUHL_M60_SENSE70_MR_hTC_Asia_TW_2.15.709.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_486004_signed_HBoot.zip
(http://en.pars-hamrah.com/download-...-_release_487210_combined_signed_2_4-zip.html)
But I don't find a free link....
Peacemaker69 said:
You can change your CID If you find Asia RUUs with 6.0 version... Other way is to flash "CleanSlate 2.0 rom" via TWRP,,, and see if that would helps..
Here you can download CleanSlate 2.0 rom :
https://forum.xda-developers.com/on...nslate-1-0-world-wide-edition-t3120017/page36
Click to expand...
Click to collapse
hai peacemaker..
i want to clean flash my htc one m9+ ..can u teach me step by step please..
my baseband version is 1.1550v70.2501.0304_HTW..
i want to change to asia WW stock rom but have no idea at all what to do..
currently my phone dont have a network and cant register any sim since i moved from taiwan to malaysia..
i will be so grateful if u can help me with this thanks

Need to go back to stock, bootloop

Hello,
So my U Ultra was rooted, then unrooted.
Months later, the phone has some sort of software issue causing it to restart (probably a corrupt file)
Now i want to take it back to being a fully unrooted stock.
Please see details below
Fastboot getvar all:
kernel: lk
(bootloader) product: htc_ocedugl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: FA72F1700260
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 355167081167528
(bootloader) version-main: 2.19.400.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF20000
(bootloader) cid: HTC__060
The bootloader shows following info:
*** RELOCKED ***
*** FUSED (PRODUCTION)***
htc_ocedugl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v24.0.8996.00007_1206_OCE
OS-2.19.400.1
Feb 13 2018,16:29:19(1026541)
It's an Indian region phone i think, since the ota files i find online with the matching radio reads HTC INDIA
So i've tried the sdcard method as well as fastboot flash zip method, trying with 2 different files:
OTA_OCEAN_N[email protected]80211.2_63.34_release_522885kzkqxuugr4zk0yr5.zip
link: https://androidfilehost.com/?fid=746010030569965797
&
2PZFIMG_OCEAN_NOTE[email protected]70502_53.34_release_503372_signed_2_4.[email protected]
link: https://androidfilehost.com/?fid=3700668719832236174
Yes, i renamed it to "2PZFIMG.zip" and placed it on root of the sdcard,
for the OTA file mentioned above, i end up with the following error:
"99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0
99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0
99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0"​
For the 2nd zip, I receive the following error:
"19 RU_MAIN_VER_FAIL os-version in android-info missing or i
19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i"​
fastboot flash zip concludes with the following error:
"zeeraks-mbp-2:~ zeerakata$ /Users/zeerakata/Documents/android/platform-tools/fastboot flash zip /Users/zeerakata/Documents/android/platform-tools/rom.zip
ERROR: Couldn't create a device interface iterator: (e00002bd)
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 904116903 is not a multiple of the block size 4096
Sending sparse 'zip' 1/2 (1048572 KB) error: write_sparse_skip_chunk: don't care size 904116903 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 904116903 is not a multiple of the block size 4096
OKAY [ 52.655s]
Writing 'zip' (bootloader) HOSD CL#1026541
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_b
(bootloader) xkQ1e
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(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, 22
(bootloader) [email protected]
FAILED (remote: '22 RU_HEADER_ERROR ')
fastboot: error: Command failed"​
I'm not a pro at this, but i've been playing around with android rooting and stuff for a while now.
Please help me with this.
Need to go back to stock
UPDATE:
So i downloaded a file with the following title,
2PZFIMG_OCEAN_NOTE_DU[email protected]80211.2_63.34_release_524957_combined_s
and it is successfully flashed via SDcard method:
I still am stuck on a bootloop, i cant make it past the htc logo, onto the loading screen
PLEASE HELP
Found the right RUU
The OTA file mentioned wouldnt flash, so i found an RUU of the same variant.
https://androidfilehost.com/?fid=11410963190603866517
It did the job, but seems like this wasn't it for my phone. Seems like a hardware issue to me since it would randomly freeze, even followed by a long-timed vibration till it turned off. So i'll be taking it for repair to a shop.

[Partially solved]FS Half-borked... help.

I need help. I flashed the wrong .img to userdata and now it refuses to be formated:
Code:
[email protected]:~$ fastboot -w
Erasing 'userdata' OKAY [ 55.085s]
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I also tried:
Code:
[email protected]:~$ fastboot --force --disable-verification format:ext4:0x1987357000 userdata
Warning: userdata size is 0x1987357000, but 0x1987357000 was requested for formatting.
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
When I get all vars from each slot I get the following differences:
Code:
Slot a+b diff
Produced: 09/15/2022 03:39:14 PM
Mode: Differences, Ignoring Unimportant
Left file: /home/moe/a.txt Right file: /home/moe/b:txt
6 (bootloader) battery-voltage:4115 <> 6 (bootloader) battery-voltage:4087
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
11 (bootloader) partition-size:userdata: 0x1987 <> 11 (bootloader) partition-size:userdata: 0x1987357000
12 (bootloader) partition-type:system_a:ext4 12 (bootloader) partition-type:system_b:ext4
13 (bootloader) partition-size:system_a: 0x1000 13 (bootloader) partition-size:system_b: 0x100000000
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
33 (bootloader) current-slot:_a <> 33 (bootloader) current-slot:_b
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------
37 (bootloader) slot-retry-count:_a:6 <> 37 (bootloader) slot-retry-count:_a:0
38 (bootloader) slot-unbootable:_a:no 38 (bootloader) slot-unbootable:_a:yes
--------------------------------------------------------------------------------------------------------
Any tips are welcomed. Thanks.
[Update]After flashing stock (*.032) ROM the phone will boot from slot a but I still get an error when attempting to format userdata:
Code:
[email protected]:~/Downloads/ph-1/032$ fastboot -w
Erasing 'userdata' OKAY [ 52.228s]
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
So far I have not seen any adverse effect on the phone operation, and Storage reports the right sizes. Still, what's going on here? How to fix it?

Categories

Resources