Related
Hi, I have already unlocked my HTC and tested a few ROMs on it, GPE was the last one I had installed and during that install I also set S-ON somehow. Don't ask me how. Maybe I never had S-OFF, but I did install a GPE ROM from this forum on it somehow.
I honestly don't remember the details from then but now I need to restore it back to stock so I can give the phone away to someone who shouldn't have to worry about OTA upgrades not working.
I have TWRP 3.0.0-1 installed, Unlocked bootloader, S-On and no idea of how to proceed. I found links online talking about connecting wires to set S-OFF, is this really necessary? Can it not be done using fastboot and adb?
I tried the correct HTC__Y13 Nandroid backup from this thread here (http://forum.xda-developers.com/showthread.php?t=2701376) but I don't know how to restore it. fastboot flash zip file.zip does not work, in TWRP Install it says the file is corrupt even though md5sum is correct. TWRP Restore doesn't find the zip so I assume it's not for that system.
All these english terms, and guides from 5 years ago are confusing to me, can someone please help me restore my HTC One M8 to factory defaults?
4e03845aeab375746b4553e610047680 /run/media/stemid/EC06-256C/RUU-4.16.401.10-0P6BIMG.zip
https://paste.fedoraproject.org/367177/14634149/ fastboot getvars all output
You need to relock bootloader to install RUU - command fastboot oem lock
What you need : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
and here is the latest Marshmallow stock ROM if you want it, or you can use that 4.16.401.10 RUU you already have ... same procedure :
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
swehack said:
I found links online talking about connecting wires to set S-OFF, is this really necessary? Can it not be done using fastboot and adb?
Click to expand...
Click to collapse
S-off isn't needed to return to stock, if that is what you are getting at.
But for the record, NO, s-off can not be done by fastboot/adb. You need a working OS to use the sunshine app ($25) which is the only way to s-off.
swehack said:
I tried the correct HTC__Y13 Nandroid backup from this thread here (http://forum.xda-developers.com/showthread.php?t=2701376) but I don't know how to restore it. fastboot flash zip file.zip does not work, in TWRP Install it says the file is corrupt even though md5sum is correct. TWRP Restore doesn't find the zip so I assume it's not for that system.
Click to expand...
Click to collapse
Its not a flashable zip, you have to unzip the contents, then place the extracted folder in the proper location.
It describes in Post #2 of the collection thread (in the Q&A, second Question), how to restore a backup. Although its a bit brief, and ckpv5's thread gives better step-by-step instructions: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
But the RUU method given by ckpv5 in the last reply, is probably the easier path in your case.
ckpv5 said:
You need to relock bootloader to install RUU - command fastboot oem lock
What you need : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
and here is the latest Marshmallow stock ROM if you want it, or you can use that 4.16.401.10 RUU you already have ... same procedure :
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Ok so now I start with an HTC that is RELOCKED, with TWRP installed. I use TWRP to wipe dalvik, cache, data just in case. Software status is modified.
This is the output of fastboot oem lock.
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
Disable hiding known file extensions in Explorer.exe.
Verify checksum of RUU.zip (469c3b8504ce2a2c8aae0fde17bfe028) and htc_fastboot.exe (7343c5bcec64373f83d69bd074954759) with fciv -md5.
Boot into fastboot.
Check fastboot devices.
Run fastboot oem rebootRUU so it reboots into the silver HTC logo screen
Run htc_fastboot.exe flash zip RUU.zip
Output from htc_fastboot.exe is at first.
Code:
sending 'zip'... (53965 KB) OKAY
sending time = 2.627 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,99
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) current_image_number=5
(bootloader) current_image_number=7
FAILED (status malformed (0 bytes))
Execution time is 14(s)
I try again and get a longer run.
Code:
sending 'zip'... (53965 KB) OKAY
sending time = 2.625 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) [RUU]UZ,rpm,0
(bootloader) signature checking...
(bootloader) current_image_number=2
(bootloader) [RUU]UZ,adsp,10
(bootloader) [RUU]UZ,adsp,33
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,76
(bootloader) [RUU]UZ,adsp,98
(bootloader) [RUU]WP,adsp,0
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,38
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) current_image_number=4
(bootloader) [RUU]UZ,wcnss,22
(bootloader) [RUU]UZ,wcnss,68
(bootloader) [RUU]UZ,wcnss,100
(bootloader) [RUU]WP,wcnss,100
(bootloader) current_image_number=5
(bootloader) [RUU]UZ,tp,100
(bootloader) current_image_number=6
(bootloader) [RUU]UZ,tp,100
(bootloader) current_image_number=7
(bootloader) [RUU]UZ,sensor_hub,100
(bootloader) [RUU]WP,sensor_hub,12
(bootloader) [RUU]WP,sensor_hub,68
(bootloader) [RUU]WP,sensor_hub,92
(bootloader) verified fail
(bootloader) current_image_number=10
(bootloader) ...... Successful
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) verified fail
(bootloader) current_image_number=12
(bootloader) current_image_number=13
(bootloader) current_image_number=14
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) current_image_number=16
OKAY
sending 'zip'... (549729 KB) OKAY
sending time = 17.657 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=1
(bootloader) start image[system] unzipping & flushing...
(bootloader) [RUU]UZ,system,0
(bootloader) [RUU]UZ,system,8
(bootloader) [RUU]UZ,system,16
(bootloader) [RUU]UZ,system,24
(bootloader) [RUU]UZ,system,32
(bootloader) [RUU]UZ,system,40
(bootloader) [RUU]UZ,system,48
(bootloader) [RUU]UZ,system,56
(bootloader) [RUU]UZ,system,64
(bootloader) [RUU]UZ,system,72
(bootloader) [RUU]UZ,system,80
(bootloader) [RUU]UZ,system,88
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,100
(bootloader) [RUU]WP,system,0
(bootloader) [RUU]WP,system,8
(bootloader) [RUU]WP,system,16
(bootloader) [RUU]WP,system,24
(bootloader) [RUU]WP,system,32
(bootloader) [RUU]WP,system,40
(bootloader) [RUU]WP,system,48
(bootloader) [RUU]WP,system,56
(bootloader) [RUU]WP,system,64
(bootloader) [RUU]WP,system,72
(bootloader) [RUU]WP,system,80
(bootloader) [RUU]WP,system,88
(bootloader) [RUU]WP,system,96
(bootloader) [RUU]WP,system,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
After that it just hangs and nothing happens, on the HTC screen I see the silver logo with a full green progress bar under it.
The first time I came here I tried to issue fastboot reboot in another terminal but that gave me the following text from htc_fastboot.
Code:
FAILED (status malformed (0 bytes))
Execution time is 261(s)
So this time I'm just waiting to see if anything else happens, only a few minutes so far.
It looks weird the size of RUU you flashed is 53965 KB
Are you sure you tried to install the correct one in your folder ?
Make sure you have one zip only. I've seen people trying to flash RUU but instead flashing unsigned firmware.
You also can try flashing with microSD method.
ckpv5 said:
It looks weird the size of RUU you flashed is 53965 KB
Are you sure you tried to install the correct one in your folder ?
Make sure you have one zip only. I've seen people trying to flash RUU but instead flashing unsigned firmware.
You also can try flashing with microSD method.
Click to expand...
Click to collapse
It eventually worked, the sizes were correct but htc_flashboot.exe went through several iterations of "sending 'zip'... (some size KB) OKAY" before it finally exited with this.
Code:
Flash Zip Complete
Execution time is 358(s)
I had a Fedora laptop with Windows in a VM before but I tried it at home with my desktop Windows system, natively, and then it worked much better. I think the USB connection between the VM and the host is unreliable.
Yeah.. I notice that too because today I did fastboot flash rom.zip
Great that you solved your problem
So, I have a feeling I have an M9 that has suffered the dreaded dead NAND, but I want to be sure.
Phone has been working fine for long time now, no random reboots. Last night all of a sudden it just self reboots, and just stuck in a vibrate/boot screen with white background loop. I tried to get into recovery directly with Vol Down/Power but it boot loops at the silver HTC logo/black screen. The only way I can get into recovery is via fastboot while it's boot looping on the silver logo splash screen, I hold vol Up/Down and I get into fastboot. I can either choose to go to download or TWRP recovery.
Download mode screen shows
Code:
*** UNLOCKED***
htc_himauhl PVT S-OFF
CID-11111111
LK-1.0.0.0000
RADIO-01.01_U11440801_96.01.51207G_F
OpenDSP-15.6.1.00522.8994_1026.
OS-3.50.710.1
May 27 2016, 15:22:38(761596)
If I go into "System" info I can see the eMMC type and everything else.
Code:
SN: FAxxxxxxx
IMEI: xxxxxx
MEID:
eMMC: Hynix 29824MB 61079552? sectors
eMMC cid: 90014a48.42473465.xxxxxxxx.xxxxxxxxx
eMMC firmware version: : 0x7?
eMMC life[267-269]: 03 01 0b?
sbl1-1.2.50.1.3
tz-3.01.193.02
TP: Maxim-1.31.55_p8_chipID-0x78_twID-0C?
CIR: Peel - version 20
SHUB: 001.065.028.037.001.001
LCD: HIMA FHD Tianma/Renesas video mode dsi panel?
CPU: Unknown
CPU rev: 2.1
DDR: 000000001, 3GB
HOWEVER fastboot getvar all doesn't show the eMMC type - that being said my OTHER HTC M9 that works doesn't show that info - it the same as the dead M9 - even though other posts I've read suggest that because there is no eMMC info it must be dead NAND - but I can see the eMMC info in "download mode" screen.
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) serialno: FAxxxxxxxxxx
(bootloader) current-slot:
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) version-main: 4.23.710.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
finished. total time: 0.010s
So what I have done, went into recovery and tried to reflash custom ROM. Did not work. Had a copy of HTC RUU zip on external SD card, went into download mode and tried to flash, it begins does the pre-update flash but then when it tried to reboot into download mode to continue flashing the rest of the partitions - it gets stuck into the silver logo boot loop. So cannot flash HTC RUU. Have also tried to flash RUU using fastboot method but still same problems.
Have tried adb shell and manually mount the partitions but get "invalid argument" - which is odd, maybe because it's adb shell when in TWRP recovery.
"mount -t /dev/block/mmcblk0p067 /data"
Have reformatted the partition as ext4 with correct variables, but still cannot mount.
Have also tried a TWRP backup restore and no luck there.... it says it formats the various partitions but fails when TWRP tries to mount and fails to do the restore.
Any suggestions or ideas would be much appreciated.
Here is the output from the fastboot flash zip -it doesn't get past the preupdate stage - repeats over and over
Code:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.50.710.1
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (172319 KB)...
OKAY [ 10.833s]
writing 'zip'...
(bootloader) HOSD CL#761596
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 12.809s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (172319 KB)...
OKAY [ 11.119s]
writing 'zip'...
(bootloader) HOSD CL#761596
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) radio.i[email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 13.093s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (172319 KB)...
OKAY [ 11.106s]
writing 'zip'...
(bootloader) HOSD CL#761596
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 13.091s
preupdate done, rebooting...
Have superCID, unlocked bootloader and S-OFF.
I suffer exactly the same probelems, did you resolve it? Thanks!
Is it possible that there was some update that ran yesterday an f*&ked devices up ?
I also have severe problems and i see a few more here... coincidence ?
mishumashu said:
Is it possible that there was some update that ran yesterday an f*&ked devices up ?
I also have severe problems and i see a few more here... coincidence ?
Click to expand...
Click to collapse
It's a hardware issue not a software issue. All phones by all OEMs that use the infamous SD810 are suffering from similar problems. The dead nand was quite common at the beginning of 2017. Then there were much less threads about the issue and it seems like it's getting more common, again.
@Qube-au
You didn't mention which RUU you used. In addition, it's a bit odd that you fastboot getvar shows a different firmware than your download mode. If you're actually running the 3.x firmware and used a 3.x RUU I'd suggest you to try an older RUU (e.g. a 2.x one). If it's actually running the 4.x firmware and you used the 4.x RUU you might want to contact Llabtoofer's RUU service (linked in the ReadMe thread). Unfortunately, there's no free solution in the latter case since there's no alternative 4.x RUU you could flash than the one you already tried. (I'm assuming that you checked the integrity of the RUU by looking at its MD5 checksum and that the calculated value matched the desired one.)
Nonetheless, these are only solutions in the case that you suffer from a software and not a hardware issue. Chances are high that the suggestions won't work since you might actually suffer from a bad nand.
exactly the same problem here on about the exact same day
one more to the count. Mine died two days avo. It can't be coincidence.
I'm about to buy a Nand reader to try at least to save my data.
did anybody try it?
Please i am in urgent need of moto g5 cedric blankflash to revive my hardbricked device. Thank you
Can you tell me what happened at first so that me and others avoid what you did?
ap4ss3rby said:
Can you tell me what happened at first so that me and others avoid what you did?
Click to expand...
Click to collapse
I flashed a wrong rom
Which rom? How did u make this ?
Hi! I'm in a similar situation here! I wanted to flash a retail firmware of the XT1676 for my little brother's phone, he just forgot to tell me he had just updated it and so the firmware/rom I flashed was an old update (dating back to February if I'm correct) and it bricked, I managed to access TWRP (I have unlocked the bootloader yesterday and I booted the file) and to push a custom rom (ViperOS) but it cannot access any network outside of Wifi.
I can access the bootloader, but since pushing the custom rom to the phone, I cannot flash or boot TWRP.
When I try to flash via flashboot the lastest firmware I have found, it just says "
fastboot flash partition gpt.bin
target max-sparse-size: 256MB
error: cannot load 'gpt.bin': No error
fastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
error: cannot load 'bootloader.img': No error" and on and on with every file.
I also messed up by trying in a last resort to repair the partition data, system and cache in TWRP and it changed data & cache from f2fs to ext4 and I don't know if that's a part of the same issue here.
My brother is currently freaking out since he has had the phone for only 2 months but all the apps that bloated the phone made him ask me to do this.
If anyone can create or find the blankflash or just help me or OP, that would be neat.
Sincerely and desperately, Thibziboy
slowflamez said:
I flashed a wrong rom
Click to expand...
Click to collapse
How did you flash it? (Zip through recovery or using fastboot)
If you did it using the recovery you should still be able to acces recovery (or flash one with fastboot) ...
Someone should help urgently! its very important cos virtually all users who tried to update or downgrade their devices got a hard bricked device as the end result. Please don't let this devices useless in our hands. Thanks
tyty48 said:
Hi! I'm in a similar situation here! I wanted to flash a retail firmware of the XT1676 for my little brother's phone, he just forgot to tell me he had just updated it and so the firmware/rom I flashed was an old update (dating back to February if I'm correct) and it bricked, I managed to access TWRP (I have unlocked the bootloader yesterday and I booted the file) and to push a custom rom (ViperOS) but it cannot access any network outside of Wifi.
I can access the bootloader, but since pushing the custom rom to the phone, I cannot flash or boot TWRP.
When I try to flash via flashboot the lastest firmware I have found, it just says "
fastboot flash partition gpt.bin
target max-sparse-size: 256MB
error: cannot load 'gpt.bin': No error
fastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
error: cannot load 'bootloader.img': No error" and on and on with every file.
I also messed up by trying in a last resort to repair the partition data, system and cache in TWRP and it changed data & cache from f2fs to ext4 and I don't know if that's a part of the same issue here.
My brother is currently freaking out since he has had the phone for only 2 months but all the apps that bloated the phone made him ask me to do this.
If anyone can create or find the blankflash or just help me or OP, that would be neat.
Sincerely and desperately, Thibziboy
Click to expand...
Click to collapse
Just flash without GPT and Bootloader. Tried it.
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
slowflamez said:
Someone should help urgently! its very important cos virtually all users who tried to update or downgrade their devices got a hard bricked device as the end result. Please don't let this devices useless in our hands. Thanks
Click to expand...
Click to collapse
Contact Moto using the livechat. Just tell the truth
Hey! I just tried it, it failed... here's the log it gave me:
C:\WINDOWS\system32>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
error: cannot load 'logo.bin': No error
C:\WINDOWS\system32>mfastboot flash boot boot.img
target max-sparse-size: 256MB
error: cannot load 'boot.img': No error
C:\WINDOWS\system32>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
error: cannot load 'recovery.img': No error
C:\WINDOWS\system32>mfastboot flash dsp adspso.bin
target max-sparse-size: 256MB
error: cannot load 'adspso.bin': No error
C:\WINDOWS\system32>mfastboot flash oem oem.img
target max-sparse-size: 256MB
error: cannot load 'oem.img': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.1': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.2': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.3': No error
C:\WINDOWS\system32>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.4': No error
C:\WINDOWS\system32>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
error: cannot load 'NON-HLOS.bin': No error
C:\WINDOWS\system32>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.037s]
finished. total time: 0.039s
C:\WINDOWS\system32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.037s]
finished. total time: 0.039s
C:\WINDOWS\system32>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
error: cannot load 'fsg.mbn': No error
C:\WINDOWS\system32>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.021s
C:\WINDOWS\system32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.070s]
finished. total time: 0.074s
C:\WINDOWS\system32>mfastboot erase customize
erasing 'customize'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
C:\WINDOWS\system32>mfastboot erase clogo
erasing 'clogo'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
Click to expand...
Click to collapse
I don't know if it can help, but I sent a getvar all to the phone and this came out:
C:\WINDOWS\system32>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.23
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3224V2KT
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: E7437CF900000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: eio
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351865087161254
(bootloader) meid:
(bootloader) date: 06-08-2017
(bootloader) sku: XT1676
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0:17:20 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPP25.1
(bootloader) ro.build.fingerprint[1]: 37-33/31:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.31.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g7d1eb92 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Mon Feb 6 19:00:09 CST
(bootloader) kernel.version[3]: 2017
(bootloader) sbl1.git: git=MBM-NG-VB8.23-0-g2cafa24
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) devcfg.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) keymaster.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) cmnlib.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VB8.21-0-g6c4172f-dirty
(bootloader) prov.git: git=MBM-NG-VB8.09-0-g1a41aff
(bootloader) aboot.git: git=MBM-NG-VB8.23-0-g8fcce1f
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
Click to expand...
Click to collapse
tyty48 said:
Hey! I just tried it, it failed... here's the log it gave me:
I don't know if it can help, but I sent a getvar all to the phone and this came out:
Click to expand...
Click to collapse
What is a getvar please and how can I get it?
slowflamez said:
What is a getvar please and how can I get it?
Click to expand...
Click to collapse
It's a fastboot command
Look at how he typed it in on the command prompt with the resulting output in his post
Requires you to have fastboot setup - in his case he was using mfastboot from Motorola although the standard fastboot will probably have the same result
TheFixItMan said:
It's a fastboot command
Look at how he typed it in on the command prompt with the resulting output in his post
Requires you to have fastboot setup - in his case he was using mfastboot from Motorola although the standard fastboot will probably have the same result
Click to expand...
Click to collapse
Kindly send the commands..Please
slowflamez said:
Kindly send the commands..Please
Click to expand...
Click to collapse
Like I said - the commands are in the post that he wrote! Have you read that post and looked at what commands were typed to generate that output?
It was
mfastboot getvar all
Still no solution?
Hi there people!
I have got my HTC10 running on software version 2.42.651.66 (which seems to be Sprint US edition). However I am running this device in UAE without any network issues.
Is there any way to update to Anroid 8.0 Oreo?
Would appreciate some help.
hi!
did you actually get the update?
i'm in the same scenario
cigarpill said:
hi!
did you actually get the update?
i'm in the same scenario
Click to expand...
Click to collapse
no idea how you guys use google but i just typed in "2.42.651 HTC10 RUU" and all of a sudden out of the blue i see download links
https://androidfilehost.com/?fid=457095661767153377
First link i got was this one....all sorts of ruu files
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
Now that's weird right !
Mr Hofs said:
no idea how you guys use google but i just typed in "2.42.651 HTC10 RUU" and all of a sudden out of the blue i see download links
https://androidfilehost.com/?fid=457095661767153377
First link i got was this one....all sorts of ruu files
https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
Now that's weird right !
Click to expand...
Click to collapse
haha
i've seen that page, but i don't get that RUU to work
i downloaded it and it's a zip... isn't a RUU an exe?
even if i flash it like a zip throught fastboot i can't find any stock RUU for my actual firmware, in case of any error
i'm s-off but my bootloader is locked (wtf did the last user did?!), and i can't relock it...
so, i'm really lost... would you help me?
cigarpill said:
haha
i've seen that page, but i don't get that RUU to work
i downloaded it and it's a zip... isn't a RUU an exe?
even if i flash it like a zip throught fastboot i can't find any stock RUU for my actual firmware, in case of any error
i'm s-off but my bootloader is locked (wtf did the last user did?!), and i can't relock it...
so, i'm really lost... would you help me?
Click to expand...
Click to collapse
A ruu.zip is easiest flashed through download mode. Rename the ruu.zip to 2PS6IMG.zip and copy it to the SDCARD then enter download mode, the file will be automatically detected and you will be asked to flash it.
If the 2.42 ruu doesn't work pick the 2.5x ruu and do the above again.
"wtf did the user do" the user did nothing, he used sunshine and they offer the option to s-off the device and keep the status of the bootloader locked.
What is locked can't be relocked obviously, if you want unlocked status just rerun the sunshine app and change your values.
Edit : it even says there EXACTLY what to do with the ruu.zip, please pay some attention and read a bit more carefully.
Keep me posted. Cheers
This is literally written in that thread
Mr Hofs said:
A ruu.zip is easiest flashed through download mode. Rename the ruu.zip to 2PS6IMG.zip and copy it to the SDCARD then enter download mode, the file will be automatically detected and you will be asked to flash it.
If the 2.42 ruu doesn't work pick the 2.5x ruu and do the above again.
"wtf did the user do" the user did nothing, he used sunshine and they offer the option to s-off the device and keep the status of the bootloader locked.
What is locked can't be relocked obviously, if you want unlocked status just rerun the sunshine app and change your values.
Edit : it even says there EXACTLY what to do with the ruu.zip, please pay some attention and read a bit more carefully.
Keep me posted. Cheers
Click to expand...
Click to collapse
you are amazing!
look, i just have a 2gb sd card, so i just will stick to the fastboot process
right now check this:
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno:
(bootloader) current-slot:
(bootloader) imei: :silly:
(bootloader) version-main: 2.42.651.6
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: 11111111
all:
finished. total time: 0.007s
my main goal is to have OREO on this beautiful cdma gsm htc 10 Sprint variant, let me tell you what i have done until now.
1. i went to this post and checked all my options: https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257.
2. i downloaded the very first exe showed there, which is Sprint_HTC10_3.18.651.3_RUU. i executed it but failed with an infamous 132 signature error. i read about but didn't find a solution.
3. i decided to leave any exe for the noobs, so i downloaded my exact ruu.zip, which is 2PS6IMG_2.42.651.6_RUU.zip. actually my firmware is 2.42.651.66, with and extra 6; anyway, it failed too but this time with this message on PowerShell:
PS C:\zzzTuco153\HTC path\HTC10> fastboot flash zip firmware.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
4. i moved on and downloaded this 105.1mb firmware: 2PS6IMG_Sprint_2.42.651.6_signed_firmware.zp. i flashed it twice:
PS C:\zzzTuco153\HTC path\HTC10> fastboot flash zip firmware.zip
target reported max download size of 1579200000 bytes
sending 'zip' (107623 KB)...
OKAY [ 5.777s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) Perform pre-update
(bootloader) get 21 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 8.070s
PS C:\zzzTuco153\HTC path\HTC10> fastboot flash zip firmware.zip
target reported max download size of 1579200000 bytes
sending 'zip' (107623 KB)...
OKAY [ 6.082s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) get 21 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY [ 8.712s]
finished. total time: 14.794s
5. i was happy, now something flashed correctly so i flashed the 2PS6IMG_2.42.651.6_RUU.zip ruu again and guess what...
PS C:\zzzTuco153\HTC path\HTC10> fastboot flash zip ruu.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
6. i didn't give up, so i downloaded the 100mb firmware 2PS6IMG_Sprint_3.18.651.3_signed_firmware.zip for oreo and did all the same with the ruu for oreo, same result....
7. i noticed this https://forum.xda-developers.com/showpost.php?p=67056758&postcount=4, so i proved Sneaky's fastboot. this time the previous steps became into this
C:\Android>fastboot flash zip 2PS6IMG.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (8492 KB)...
OKAY [ 1.416s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_O
(bootloader) V1mhK
(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 RU_HEADER_ERROR )
finished. total time: 3.505s
SOOOOOO, now i'm stuck on this puzzle
i'm certainly wrong at something, and my phone isn't turning on, it's bootlooping.
what would be my next step... help me :crying:
cigarpill said:
you are amazing!
look, i just have a 2gb sd card, so i just will stick to the fastboot process
right now check this:
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno:
(bootloader) current-slot:
(bootloader) imei: :silly:
(bootloader) version-main: 2.42.651.6
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: 11111111
all:
finished. total time: 0.007s
my main goal is to have OREO on this beautiful cdma gsm htc 10 Sprint variant, let me tell you what i have done until now.
1. i went to this post and checked all my options: https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257.
2. i downloaded the very first exe showed there, which is Sprint_HTC10_3.18.651.3_RUU. i executed it but failed with an infamous 132 signature error. i read about but didn't find a solution.
3. i decided to leave any exe for the noobs, so i downloaded my exact ruu.zip, which is 2PS6IMG_2.42.651.6_RUU.zip. actually my firmware is 2.42.651.66, with and extra 6; anyway, it failed too but this time with this message on PowerShell:
PS C:\zzzTuco153\HTC path\HTC10> fastboot flash zip firmware.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
4. i moved on and downloaded this 105.1mb firmware: 2PS6IMG_Sprint_2.42.651.6_signed_firmware.zp. i flashed it twice:
PS C:\zzzTuco153\HTC path\HTC10> fastboot flash zip firmware.zip
target reported max download size of 1579200000 bytes
sending 'zip' (107623 KB)...
OKAY [ 5.777s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) Perform pre-update
(bootloader) get 21 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
finished. total time: 8.070s
PS C:\zzzTuco153\HTC path\HTC10> fastboot flash zip firmware.zip
target reported max download size of 1579200000 bytes
sending 'zip' (107623 KB)...
OKAY [ 6.082s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) get 21 images from zip(zip_type=3)
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY [ 8.712s]
finished. total time: 14.794s
5. i was happy, now something flashed correctly so i flashed the 2PS6IMG_2.42.651.6_RUU.zip ruu again and guess what...
PS C:\zzzTuco153\HTC path\HTC10> fastboot flash zip ruu.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
6. i didn't give up, so i downloaded the 100mb firmware 2PS6IMG_Sprint_3.18.651.3_signed_firmware.zip for oreo and did all the same with the ruu for oreo, same result....
7. i noticed this https://forum.xda-developers.com/showpost.php?p=67056758&postcount=4, so i proved Sneaky's fastboot. this time the previous steps became into this
C:\Android>fastboot flash zip 2PS6IMG.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (8492 KB)...
OKAY [ 1.416s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_O
(bootloader) V1mhK
(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 RU_HEADER_ERROR )
finished. total time: 3.505s
SOOOOOO, now i'm stuck on this puzzle
i'm certainly wrong at something, and my phone isn't turning on, it's bootlooping.
what would be my next step... help me :crying:
Click to expand...
Click to collapse
Stubborn to stay with fastboot commands......well done
But what next......
First it's needed to get into the bootloader or download mode. If you are still on the 2.42 firmware than also use that ruu (that your OS is .66 and the ruu .6 is not relevant, that's just software related and not firmware and it won't interfere the flash). Read up in one of the guides about the the topic "RUU mode" it's done via a command "fastboot oem rebootRUU" but i am not 100% sure at this time if you enter this menu via the bootloader or download menu, check that out please. At the moment i don't have the time to do searches.
If you can't get that to work i can suggest to enter download mode, flash TWRP, flash a stock based nougat rom, rerun sunshine and set all flags to s-off and unlocked bootloader instead of a locked one. In the very beginning that flag caused issues flashing kernels which they addressed later on with further development, maybe your device is has a hiccup at that level somehow.
Cheers
Mr Hofs said:
Stubborn to stay with fastboot commands......well done
But what next......
First it's needed to get into the bootloader or download mode. If you are still on the 2.42 firmware than also use that ruu (that your OS is .66 and the ruu .6 is not relevant, that's just software related and not firmware and it won't interfere the flash). Read up in one of the guides about the the topic "RUU mode" it's done via a command "fastboot oem rebootRUU" but i am not 100% sure at this time if you enter this menu via the bootloader or download menu, check that out please. At the moment i don't have the time to do searches.
If you can't get that to work i can suggest to enter download mode, flash TWRP, flash a stock based nougat rom, rerun sunshine and set all flags to s-off and unlocked bootloader instead of a locked one. In the very beginning that flag caused issues flashing kernels which they addressed later on with further development, maybe your device is has a hiccup at that level somehow.
Cheers
Click to expand...
Click to collapse
guess what????
i did it!
i flashed the 100mb oreo FIRMWARE listed on that page... then i RUUed with the first exe
i have SPRINT oreo.... but
i hate the bloatware and that hands free activation... stuff i cant use in my country even if i want
wonder, is there a way to flash the developer ruu without damaging the CDMA options? i mean, i recently found out there are 2 variants... gsm and CDMA... didnt know CDMA existed because i live in LatinAmerica. im afraid to flash another zip and lost my signal or something
thank you for your help-1
PD... i m still wondering how to unlock my bootloader, i installed sunshine apk but theres only option to reboot.
the reason why i want to unlock my bl its because in developer options i cant UNLOCK OEM as the option isnt selectable... why?
cigarpill said:
guess what????
i did it!
i flashed the 100mb oreo FIRMWARE listed on that page... then i RUUed with the first exe
i have SPRINT oreo.... but
i hate the bloatware and that hands free activation... stuff i cant use in my country even if i want
wonder, is there a way to flash the developer ruu without damaging the CDMA options? i mean, i recently found out there are 2 variants... gsm and CDMA... didnt know CDMA existed because i live in LatinAmerica. im afraid to flash another zip and lost my signal or something
thank you for your help-1
PD... i m still wondering how to unlock my bootloader, i installed sunshine apk but theres only option to reboot.
the reason why i want to unlock my bl its because in developer options i cant UNLOCK OEM as the option isnt selectable... why?
Click to expand...
Click to collapse
Sprint / GSM / CDMA conversion, don't know anything about that and i really can't help with that.
Bloatware, root the OS and delete the bloatware manually
Why do you want to change the unlock oem status in settings ?
Mr Hofs said:
Sprint / GSM / CDMA conversion, don't know anything about that and i really can't help with that.
Bloatware, root the OS and delete the bloatware manually
Why do you want to change the unlock oem status in settings ?
Click to expand...
Click to collapse
as far as i can understand
to change mid cid and flash other ruus
cigarpill said:
as far as i can understand
to change mid cid and flash other ruus
Click to expand...
Click to collapse
Nope. Oem unlock allows you to unlock the bootloader which is needed to flash TWRP and with that custom roms.
To get s-off you need to run sunshine and that requires root so the first time the device needs oem unlock enabled, unlock the bootloader, root the OS and perform sunshine to acquire s-off.
To change cid and mid you need s-off which you already have. So in a way you do not need that option enabled.
Why don't you start with the basics and read more in the sprint section to gain more knowledge and learn if sprint can even be converted in a safe way ?
UPDATE: I was able to run 3.16.617.2 RUU.exe while phone was in RUU mode. The program successfully detected the phone and restored it back to stock.
Hi,
I was trying to roll back from LOS (Android 9) to stock 8.0 Oreo.
I downloaded the RUU zip, renamed it to 2PS6IMG.zip, and flashed it but got a model ID mismatch error, and flash failed. Tried fastboot getvar all and got the following:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:<Removed on purpose>
version-baseband and version-bootloader are returned blank by this command.
i tried to fastboot flash the ruu zip and got the following error:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 960139745 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 960139745 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 960139745 is not a multiple of the block size 4096
OKAY [ 37.228s]
Writing sparse 'zip' 1/2 (bootloader) HOSD CL#1012001
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_c
(bootloader) FoslP
(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 ')
Finished. Total time: 58.930s
Any suggestions?
Yeah you flashed "a" ruu, which one exactly ? Second the fastboot getvar all command should be done with the phone in download mode. Not bootloader.
Try again and give the proper info.
Cheers
Mr Hofs said:
Yeah you flashed "a" ruu, which one exactly ? Second the fastboot getvar all command should be done with the phone in download mode. Not bootloader.
Try again and give the proper info.
Cheers
Click to expand...
Click to collapse
Oh sorry, my bad. The fastboot getvar all from download mode gives:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: HT6ARBN00041
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: <Removed>
(bootloader) version-main: 3.16.401.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: BS_US001
I have tried the 3.16.401.2 RUU zip, but it failed. I then realized that the correct zip for BS_US001 would be 3.16.617.2. So i flashed that, but same result.
Currently I am:
S-on
relocked
stuck in download mode
If i try to flash RUU zip from sd card, i get "12 RU zip error", and if i try flashing via fastboot, i get
Code:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 933555519 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 933555519 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 933555519 is not a multiple of the block size 4096
OKAY [ 50.183s]
Writing sparse 'zip' 1/2 (bootloader) HOSD CL#1012001
FAILED (remote: '9 RU_SECURITY_FAIL zip from usb command in download mode')
Finished. Total time: 56.306s
Tip 1 : keep your issue in 1 thread ONLY ! it's confusing
Now, your CID is actually from another model and your OS version is wwe Europe.....that can't be done with s-on.
Q1: are you sure your device isn't s-off but with s-on status ? This can be possible because sunshine provides that option.
Try the sunshine app to see if your device has been registered there, if so it will make things easier.
Please confirm the questions i have for you.
Mr Hofs said:
Tip 1 : keep your issue in 1 thread ONLY ! it's confusing
Now, your CID is actually from another model and your OS version is wwe Europe.....that can't be done with s-on.
Q1: are you sure your device isn't s-off but with s-on status ? This can be possible because sunshine provides that option.
Try the sunshine app to see if your device has been registered there, if so it will make things easier.
Please confirm the questions i have for you.
Click to expand...
Click to collapse
I am not S-OFF, my download mode says S-ON. I have never tried setting it to s-off
fastboot getvar all in download mode shows: (bootloader) version-main: 3.16.401.2
while on the phone screen it says OS-3.16.617.2
cid: BS_US001
mid: 2PS650000
can not use the sunshine app since i can only boot into download and bootloader mode.
Also apologies about the multiple thread confusion, will only post in this one now.
Khizar Amin said:
Hi,
I was trying to roll back from LOS (Android 9) to stock 8.0 Oreo.
I downloaded the RUU zip, renamed it to 2PS6IMG.zip, and flashed it but got a model ID mismatch error, and flash failed. Tried fastboot getvar all and got the following:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) boot-mode:FASTBOOT
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:<Removed on purpose>
version-baseband and version-bootloader are returned blank by this command.
i tried to fastboot flash the ruu zip and got the following error:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 960139745 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 960139745 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 960139745 is not a multiple of the block size 4096
OKAY [ 37.228s]
Writing sparse 'zip' 1/2 (bootloader) HOSD CL#1012001
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_c
(bootloader) FoslP
(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 ')
Finished. Total time: 58.930s
Any suggestions?
Click to expand...
Click to collapse
Was able to get an RUU exe to work with phone in RUU mode
Thanks a bunch though @Mr Hofs
Khizar Amin said:
Was able to get an RUU exe to work with phone in RUU mode
Thanks a bunch though @Mr Hofs
Click to expand...
Click to collapse
Would you mind explaining how you did it exactly with what ruu. Because still your OS did not match your CID.
Thanks in advance
Edit :
You didn't read well. When your download mode says 3.16.401 and your CID BS 001 it's been modded because they mismatch.
So either your device has been set to s-off but with the s-on flag by sunshine.
So again : try this
Download the sunshine app (has nothing to do with your bootloader) and run it. When the application continues all the way without payment and you can reset your options it's been registered and thus modded.
Please read carefully what i write......
Mr Hofs said:
Would you mind explaining how you did it exactly with what ruu. Because still your OS did not match your CID.
Thanks in advance
Edit :
You didn't read well. When your download mode says 3.16.401 and your CID BS 001 it's been modded because they mismatch.
So either your device has been set to s-off but with the s-on flag by sunshine.
So again : try this
Download the sunshine app (has nothing to do with your bootloader) and run it. When the application continues all the way without payment and you can reset your options it's been registered and thus modded.
Please read carefully what i write......
Click to expand...
Click to collapse
When i was trying to fix the phone, i first tried with the .401 zip several times, but it would always fail during the process. Then, while searching on xda, i realized that i was using the wrong RUU, so i downloaded the .617 ruu exe to match my CID
I booted the phone to RUU mode, since it was only booting to bootloader, RUU or download modes, and ran the ruu exe. RUU detected my phone and i started the flash, and to my surprise, it actually worked without error. This was surprising because RUU.zip failed to flash, but somehow, exe did not. After the phone booted up, i was able to unlock bootloader again.
I have tried the sunshine thing, but the phone currently isnt rooted. I`ll root phone and get back in a bit.
Edit:
This is the current fastboot getvar all result
(bootloader) kernel: lk
(bootloader) product: htc_pmewl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno:
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei:
(bootloader) version-main: 3.16.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: BS_US001
Mr Hofs said:
Would you mind explaining how you did it exactly with what ruu. Because still your OS did not match your CID.
Thanks in advance
Edit :
You didn't read well. When your download mode says 3.16.401 and your CID BS 001 it's been modded because they mismatch.
So either your device has been set to s-off but with the s-on flag by sunshine.
So again : try this
Download the sunshine app (has nothing to do with your bootloader) and run it. When the application continues all the way without payment and you can reset your options it's been registered and thus modded.
Please read carefully what i write......
Click to expand...
Click to collapse
Rooted, checked sunshine. It takes me to payment. Sunshine has not been purchased for this device.
Khizar Amin said:
Rooted, checked sunshine. It takes me to payment. Sunshine has not been purchased for this device.
Click to expand...
Click to collapse
Then i have no idea what happened to your device but a IS unlocked CID and European firmware isn't really possible. At least your issue is fixed but it still baffles me.
Cheers