Related
The solution is very simple and ive tested it on more then 5 different senarios when i get the bug.
1. install TWRP recovery (you can even sideload it with fastboot if you dont wanna install it on phone(if you got stock recovery etc.), with this command "fastboot boot openrecovery-twrp-2.7.1.0-m8.img"
2. make a full wipe, check all boxes except external SD :highfive:, that will erase /data/media and also /data where the encryption bug lies.
3. install your ROM or restore your ROM from backup.
4. then reboot recovery and flash the recovery you want (or sideload it with the command above).
5. done, now the encryption bug is gone :good:
if this still dont work, try the solution given by maxrdlf95 in his thread here http://forum.xda-developers.com/showthread.php?t=2773203
smaberg said:
The solution is very simple and ive tested it on more then 5 different senarios when i get the bug.
1. install TWRP recovery (you can even sideload it with fastboot if you dont wanna install it on phone(if you got stock recovery etc.), with this command "fastboot boot openrecovery-twrp-2.7.1.0-m8.img"
2. make a full wipe, check all boxes except external SD :highfive:, that will erase /data/media and also /data where the encryption bug lies.
3. install your ROM or restore your ROM from backup.
4. then reboot recovery and flash the recovery you want (or sideload it with the command above).
5. done, now the encryption bug is gone :good:
if this still dont work, try the solution given by maxrdlf95 in his thread here http://forum.xda-developers.com/showthread.php?t=2773203
Click to expand...
Click to collapse
So, what youre basically saying is wipe data? I think the point is most people dont wanna do that, and doesnt the other fix allow you to fix the issue without wiping? Just trying to understand...
mikeyinid said:
So, what youre basically saying is wipe data? I think the point is most people dont wanna do that, and doesnt the other fix allow you to fix the issue without wiping? Just trying to understand...
Click to expand...
Click to collapse
Make a full backup of your ROM first, then my steps (cwm, philz won't work).
Then Restore backup...
Philz and cwm won't wipe the important parts, so with them the bug will still be there. So twrp with all options check will do the trick.
This method worked for me. I selected all options except external sd card when wiping. Wiping failed. Then I went to format data, typed in "yes" and formatted my internal storage. I then went back to select all option to wipe everything and surprisingly "It Worked", I was able to wipe everything and restore my rom successfully.
Thanks for this!!! (AT&T User!)
Sorry...wrong thread
My phone Isn't Rooted nor has the bootloader is Unlocked
smaberg said:
The solution is very simple and ive tested it on more then 5 different senarios when i get the bug.
1. install TWRP recovery (you can even sideload it with fastboot if you dont wanna install it on phone(if you got stock recovery etc.), with this command "fastboot boot openrecovery-twrp-2.7.1.0-m8.img"
2. make a full wipe, check all boxes except external SD :highfive:, that will erase /data/media and also /data where the encryption bug lies.
3. install your ROM or restore your ROM from backup.
4. then reboot recovery and flash the recovery you want (or sideload it with the command above).
5. done, now the encryption bug is gone :good:
if this still dont work, try the solution given by maxrdlf95 in his thread here http://forum.xda-developers.com/showthread.php?t=2773203
Click to expand...
Click to collapse
Hello, I have the same Issue, just that my bootloader is locked, the phone has never been rooted, here's an image of the phone, also here's a getvar from the phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.24.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: F********500
(bootloader) imei: 3*************5
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 59ee16dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.027s
I also tried to manually format userdata, flash recovery, flash boot and this is what I get:
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.005s
target reported max download size of 1826410496 bytes
sending 'recovery' (16050 KB)...
OKAY [ 1.475s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
erickobain said:
Hello, I have the same Issue, just that my bootloader is locked, the phone has never been rooted, here's an image of the phone, also here's a getvar from the phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.24.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: F********500
(bootloader) imei: 3*************5
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 59ee16dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.027s
I also tried to manually format userdata, flash recovery, flash boot and this is what I get:
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.005s
target reported max download size of 1826410496 bytes
sending 'recovery' (16050 KB)...
OKAY [ 1.475s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
Click to expand...
Click to collapse
Unlock the bootloader.
It wont let me...
erickobain said:
It wont let me...
Click to expand...
Click to collapse
Nobody is going to know what that means. You need to provide details and specifics on what you tried, what exact step you got stuck, including details on error messages or other results on the phone's screen, computer screen, etc.
Responding with one sentence like you did, and expecting anyone to be able to help, is not the proper way to post or ask for help.
You can't install TWRP with a locked bootloader. You need to unlock the bootloader via HTCDev.com. If you had problems with the bootloader unlock process, you need to be specific on what step, and what errors you encountered; of you expect us to advise you.
Hi all,
I've created a simple guide to restore your HTC One M8 back to stock firmware while still being on S-ON.
This guide will provide you with all the files required to restore your EUROPEAN device back to stock.
If you have an device from another region, you'll need to find the RUU & recovery image yourself. (see below)
Prerequisites:
- HTC Drivers (just install HTC Sync and the included drivers, then remove HTC Sync)
- Fastboot package
- Stock recovery.img (you'll need the recovery.img with the same fw version as the RUU you're going to flash) (Link to 4.16.401.10 recovery.img for European non-carier devices)
- The RUU for your region/carrier. (Link to 4.16.401.10 for European non-carier devices)
If you have an USA /USA carrier device, go here for the RUU files
If you have an device from another region than Europe or USA, good luck finding the correct RUU
Look here to find recovery.img files for all regions (thanks to @exocetdj)
Because this guide is intended for S-ON, only the RUU for your region/carrier will work.
If you don't have an RUU or cannot find one for your region/carrier, S-OFF your device and follow this guide to restore your HTC One M8 back to stock. (thanks to @EddyOS)
After you've gone trough all steps;
- The red text during boot will be gone
- You'll have the stock firmware, system, recovery and boot.img
- Your bootloader will say "Relocked"
- Your bootloader will say "Software status: Official"
Let's start:
Step 1:
Start the RUU exe by double clicking on it, it will take a few seconds before it starts. After it has started, do not continue but go to your temp folder (type %TEMP% in your address bar)
Find the folder with the temporary files from the RUU (mine was called: {C48DBAA3-1CC0-4DF6-B069-B9CCB27F93C9})
Inside this folder there should be a few files and another folder with a long code as name (mine was called: {50F2F878-636A-496F-A7CB-544C067E0C4B})
Inside this folder, scroll down until you find rom.zip, open this file
Extract boot_signed.img and place it in a folder with the downloaded stock recovery and the fastboot.exe file
Now close the RUU installation wizard
Step 2:
Turn off your device
Hold VOL-Down + Power, after a few seconds you'll be in the bootloader. Now release the buttons
Navigate with the volume buttons to fastboot and confirm with the power button.
Step 3:
You should now have a folder with the following files:
- fastboot.exe
- AdbWinApi.dll
- AdbWinUsbApi.dll
- boot.img (extracted from the rom.zip)
- recovery.img (see prerequisites)
Inside the folder while holding shift, click right mouse and choose Open command window here
Before starting, it's recommended to rename the recovery file to recovery.img and the kernel to boot.img
Type the following commands in order (make sure to check the output and see if every command is successful before executing the next command)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot oem lock
This will push the stock kernel & recovery and relock your device.
Step 4:
Open the RUU installation wizard again and follow the instructions.
It will start flashing the RUU on your device.
After 8-12 minutes, the installation will be complete and your device will boot into system.
Step 5: (optional)
Power off your device
Hold VOL-Down + Power, after a few seconds you'll be in the bootloader. Now release the buttons
Verify that your bootloader says "Relocked" & "Software status: Official"
Congratulations, your device is back to stock again. After it's finished booting and optimizing 261(!) pre installed apps, you'll be greeted by the setup wizard on your phone.
If you have any questions, let me know.
Common problems:
Fastboot cannot find my device?
- try reinstalling the HTC drivers included with HTC Sync, and make sure to remove HTC Sync afterwards but leaving the drivers installed
I've got error 155 when trying to flash the RUU
- make sure your bootloader is locked. This tool only works when you have stock kernel, recovery and your bootloader is locked or relocked.
Reserved
TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks
This is a great guide for those that just want to return to stock for their own purposes. However, this will not be enough for sending the phone into warranty, for that you'll need to take a few more steps with S-Off to get that RELOCKED flag to say LOCKED.
dima470 said:
This is a great guide for those that just want to return to stock for their own purposes. However, this will not be enough for sending the phone into warranty, for that you'll need to take a few more steps with S-Off to get that RELOCKED flag to say LOCKED.
Click to expand...
Click to collapse
From my experience with HTC warranty repairs, they don't really care about the bootloader being 'relocked', S-Off is a more common cause for them to not repair the device.
But, above differs per repair center / per country
al_wizard said:
TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks
Click to expand...
Click to collapse
Where did you bought your device?
al_wizard said:
TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks
Click to expand...
Click to collapse
You are S-ON so you need to relock the bootloader and run the ruu.
If you want to give all info to work with you need to post the outcome of :
Fastboot getvar all
Delete the serial and imei and post the list here.
Or check the firmware & nand backup thread here in the general section. Restore the stock rom and recovery and perform ota updates which also will upgrade the firmware
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
Joery360 said:
From my experience with HTC warranty repairs, they don't really care about the bootloader being 'relocked', S-Off is a more common cause for them to not repair the device.
But, above differs per repair center / per country
Where did you bought your device?
Click to expand...
Click to collapse
Has nothing to do with where he bought it from, it is depending on the phones hardware & software, for all we know its imported.
The specs are important not where he got it from. And you can't tie it down on how repair centers handle the phones....that's a matter of good luck !
Joery360 said:
Where did you bought your device?
Click to expand...
Click to collapse
I bought it second-hand from Qatar if you mean country.
Hi. I tried to use this guide but it I couldn't follow it through. I have relocked, tempered, S-ON, CID : TMOB102 phone. It is stuck in the HTC logo after a full wipe from twrp. I don't have OS, and the main version is empty. So far I have tried all the European RUU which gave CID error and 2 T-Mobile RUU's with MID error both. Can anyone give me a suggestion?
Problem extracting boot_signed.img
When I try to extract the boot_signed.img akk I get from Winzip is "cant find central directory"
Any ideas??
This is a great guide for those that just want to return to stock for their own purposes.
Hi,
I just needs to get OTA on my phone and i dont mind it being tampered or unlocked.
Will this method work on my phone ?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH495WM01309
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
:/
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.895s
I have no OS now if I try to reboot I get stuck on boot logo. What can I do to get back to stock with OTA and everything?
C:\Users\Ali\Desktop\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.61.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
thanks this helped me revive my m8
Pc can't identify my device. phone gets htc logo then it turns black and disconnects from pc. RUU wiz error (170) usb connection error.
royalkalana said:
Hi,
I just needs to get OTA on my phone and i dont mind it being tampered or unlocked.
Will this method work on my phone ?.....
Click to expand...
Click to collapse
Yes
gorner92 said:
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting..
Click to expand...
Click to collapse
Please check if your device is unlocked. You can't flash boot.img's while on a locked bootloader.
Cpre said:
Pc can't identify my device. phone gets htc logo then it turns black and disconnects from pc. RUU wiz error (170) usb connection error.
Click to expand...
Click to collapse
Reinstall the HTC drivers.
gorner92 said:
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.895s
I have no OS now if I try to reboot I get stuck on boot logo. What can I do to get back to stock with OTA and everything?
C:\Users\Ali\Desktop\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.61.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
Click to expand...
Click to collapse
You are using the wrong command ! It's :
Fastboot flash boot boot.img
NOT
Fastboot boot boot.img ! That's why you got stuck. And indeed make sure the bootloader is UNLOCKED before you flash !
While i don't even know flashing the boot.img and recovery seperatly first is actually needed because all that's needed is to relock the bootloader and run the ruu.exe or the temp rom.zip via sd card.
afaik the ruu method takes care of the boot.img and recovery on its own.
Got a problem with 3rd command (locking oem) in step 3. It goes like this:
C:\adb>fastboot flash boot boot.img
target reported max download size of 1826021376 bytes
sending 'boot' (8780 KB)...
OKAY [ 1.001s]
writing 'boot'...
OKAY [ 0.464s]
finished. total time: 1.465s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1826021376 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.710s]
writing 'recovery'...
OKAY [ 0.646s]
finished. total time: 2.357s
C:\adb>fastboot oem lock
...
(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) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.194s
My getvar all before flashing:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 0000000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cindum: HTC__032
Now my phone is stuck on my ROM's boot logo and now I can't access bootloader.
EDIT:
I've managed to access bootloader by holding power + volup and then holding vol down. After that installing via RUU went smooth.
Hi, I followed your instructions, but before I could start with 4th device booted up and i accidentaly accepted upgrade. It rebooted and upgraded the device, and then stuck on boot screen. Now I try to update it through RUU but it says image version 4.16.401.13, and I can't find RUU for that version. Any ideas? Can I somehow reinstall twrp and restore nandroid backup?
P.S. in bootloader it still says software status: modified :/
P.P.S. I still managed to make RUU go through all the steps, from a billionth time. It would usually stuck on steps 0, step 1, or step 3. Now it seems like it's booting fine... Time to shower away all the cold sweat from my body.
Hi Guys,
I have windows 8.1 and can't open rom.zip file. I have an error : The compressed Folder is invalid. Installed winzip, 7-zip - can't go ahead.
If you are having trouble sending the ruu and you are stuck at sending 0/7 or 1/8 and only htc logo. then just delete htc sync manager from your pc!!!
Hello, I am totally lost... I've been trying to solve this problem but no luck... I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (stuck on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
###########
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
##############
any one can help me plz.
anyone can help
t.zennad said:
anyone can help
Click to expand...
Click to collapse
I'm also in the same condition...
fastboot not accessible...
Help!!!
Axon 7 mini 7.1.1 build B2017gV1.2.0B14
Still waiting too.
Get a stock recovery (not TWRP), flash it with fasboot flash recovery recovery.img
I think tdm has a thread with all stock images, flash the one for your country
https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538
If this doesn't work, maybe the verity check fails, making the device unable to boot, then go ahead and flash system and boot via fastboot.
fastboot flash system system.img
fastboot flash boot boot.img
Good luck
just a hailmairy here but...
"(bootloader) Charger screen enabled: 'false'"
in Advanced Settings ->Developer Options->Stay Awake (while charging) [ ]
should possible be switched on as it does mentions that charging screen set to off?
Probably would only sort one item though but you never know and if it does your one more step forward.
sonnettie
HEEEEELP! From Liquid tried to flash Lineage16.....flashed bootloader...I'm stuck on fastboot. The down volume key is broken. Only up volume works but not in fastboot. Tried to adb/flash a sock recovery....only can reboot in fastboot dialogue. Any solution? Thank you.
Hello
any one can help please, i am still in same problem
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3447000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:bc13c89a
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.022s
------
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
-------
I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (loop on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
Thanks
I tried to unlock my b2017g with fastboot commands but not luck, i tried use Hydra too... i hope will find a solution soon :/
Hi Everybody, I think I have a similar issue. After many years with regular stock system I decided to change to a custom ROM, hoping I can use my phone with my native language, which was not in the stock rom.
But now I stucked in the fastboot, and I can not get out of it. I can access my phone via fastboot, I have already flashed the TWRP, but the phone can not boot into the recovery and the system. How can I fix this? Please help me, I like this phone, I would like to get it back to life.
I bricked my Axon mini n2015 by flashing No verity boot.img and a custom recovery. Now phone is stuck in fastboot mode. Help guys, what do i do?
Looks like no solution
Hello, and thank you in advance for your assistance.
I bought a "new" Verizon HTC 10 off Ebay. It seemed to be a stock phone, with version 2.4xxxx; I am not exactly sure which version. I have bought my 2 daughters HTC 10's as well. There's are fine. They both have version 3.xxxx. I thought to upgrade my phone to somewhere around their version, because my phone seemed to have connectivity issues when both Wi-Fi and Data were enabled at the same time. However, the OS said they were no new updates for the phone. I checked the HTC site and they had the 2.51.617.32 RUU available. It said it would wipe all data, but that was no consequence to me because I didn't want to save anything. I didn't make a recovery backup (Stupid)! I downloaded the RUU, started it, and it errored out at about 90%; Erro 155: Unknown Error - The ROM update utility cannot update your Android phone. Please get the correct ROM update utility and try again. After that, on reboot the phone constantly reboots. I stop it by booting into download mode. Then choosing "power off". Since then, I have tried the RUU several more times, I have downloaded it again just to make sure I had an uncorrupted exe, I put in on my SD card and tried to update it that way: E: Signature Verification failed - error 21. I have tried the 3.6xxxx update from one of the people on this site. I get all the same messages. Also, I have used htc_fastboot to see if that would work. It errors out at 90% as well at tp_syn3708.img error. I have taken it to a repair shop, but they weren't able to fix it. I have chatted back and forth with HTC support. They had me change the CID to BS_US001. That did nothing. I read more on this forum and changed the CID to VZ_001. That didn't change anything. At this point, what are my options? I'm using an older backup phone, but I hope I can "reboot" this one. Thanks again.
Byrdman2b said:
Hello, and thank you in advance for your assistance.
I bought a "new" Verizon HTC 10 off Ebay. It seemed to be a stock phone, with version 2.4xxxx; I am not exactly sure which version. I have bought my 2 daughters HTC 10's as well. There's are fine. They both have version 3.xxxx. I thought to upgrade my phone to somewhere around their version, because my phone seemed to have connectivity issues when both Wi-Fi and Data were enabled at the same time. However, the OS said they were no new updates for the phone. I checked the HTC site and they had the 2.51.617.32 RUU available. It said it would wipe all data, but that was no consequence to me because I didn't want to save anything. I didn't make a recovery backup (Stupid)! I downloaded the RUU, started it, and it errored out at about 90%; Erro 155: Unknown Error - The ROM update utility cannot update your Android phone. Please get the correct ROM update utility and try again. After that, on reboot the phone constantly reboots. I stop it by booting into download mode. Then choosing "power off". Since then, I have tried the RUU several more times, I have downloaded it again just to make sure I had an uncorrupted exe, I put in on my SD card and tried to update it that way: E: Signature Verification failed - error 21. I have tried the 3.6xxxx update from one of the people on this site. I get all the same messages. Also, I have used htc_fastboot to see if that would work. It errors out at 90% as well at tp_syn3708.img error. I have taken it to a repair shop, but they weren't able to fix it. I have chatted back and forth with HTC support. They had me change the CID to BS_US001. That did nothing. I read more on this forum and changed the CID to VZ_001. That didn't change anything. At this point, what are my options? I'm using an older backup phone, but I hope I can "reboot" this one. Thanks again.
Click to expand...
Click to collapse
VZ__001
That's two underscores, not one.
That should work using the Verizon Oreo RUU, if it's indeed a Verizon model and the MID matches.
Although I feel you've already done too many changes for this information to be accurate, paste the output of:
fastboot getvar all
Remove the serial and imei for security purposes.
Sent from my Pixel 3 XL using Tapatalk
santod040 said:
VZ__001
That's two underscores, not one.
That should work using the Verizon Oreo RUU, if it's indeed a Verizon model and the MID matches.
Although I feel you've already done too many changes for this information to be accurate, paste the output of:
fastboot getvar all
Remove the serial and imei for security purposes.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
(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.18.605.13
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: VZW__001
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.244s
Byrdman2b said:
(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.18.605.13
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS650000
(bootloader) cid: VZW__001
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.244s
Click to expand...
Click to collapse
You need the VZW Oreo RUU.
https://forum.xda-developers.com/showthread.php?p=70340077
Sent from my Pixel 3 XL using Tapatalk
santod040 said:
You need the VZW Oreo RUU.
https://forum.xda-developers.com/showthread.php?p=70340077
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yes - I have already tried this one. Using htc_fastboot, this is the one that errors out on tp_syn3708. Should I download the file again and repeat the procedure?
Byrdman2b said:
Yes - I have already tried this one. Using htc_fastboot, this is the one that errors out on tp_syn3708. Should I download the file again and repeat the procedure?
Click to expand...
Click to collapse
Try using SD card method and verify the md5 sum of the download and/or redownload if need be.
Sent from my Pixel 3 XL using Tapatalk
santod040 said:
Try using SD card method and verify the md5 sum of the download and/or redownload if need be.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
What is the command to verify the md5 sum of the download?
Byrdman2b said:
What is the command to verify the md5 sum of the download?
Click to expand...
Click to collapse
On Linux:
md5sum filename.zip
Replace filename with actual name of file.
On Windows:
CertUtil -hashfile <path to file> MD5
Sent from my Pixel 3 XL using Tapatalk
santod040 said:
On Linux:
md5sum filename.zip
Replace filename with actual name of file.
On Windows:
CertUtil -hashfile <path to file> MD5
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Here is what I get after downloading (again), MD5sum checking, and sending the file through fastboot:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.18.605.13
found large-zip header, file count: 29
processing file 1/29...
sending 'zip' (113449 KB)...
OKAY [ 5.377s]
writing 'zip'...
(bootloader) HOSD CL#1016573
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) WARN Skip partition_info due to unmatched partition name
(bootloader) WARN Skip lockbooter.img due to unmatched partition name
(bootloader) WARN Skip backup_android-info.txt due to unmatched partitio
(bootloader) n name
(bootloader) get 32 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) boot_sign[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: 7.979s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (113449 KB)...
OKAY [ 5.427s]
writing 'zip'...
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_s
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP ERROR CODE, 22
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 7.544s
htc_fastboot finished. total time: 32.112s
I'll get in on the SD card and try it as well.
Byrdman2b said:
Here is what I get after downloading (again), MD5sum checking, and sending the file through fastboot:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.18.605.13
found large-zip header, file count: 29
processing file 1/29...
sending 'zip' (113449 KB)...
OKAY [ 5.377s]
writing 'zip'...
(bootloader) HOSD CL#1016573
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) WARN Skip partition_info due to unmatched partition name
(bootloader) WARN Skip lockbooter.img due to unmatched partition name
(bootloader) WARN Skip backup_android-info.txt due to unmatched partitio
(bootloader) n name
(bootloader) get 32 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) [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: 7.979s
preupdate done, rebooting...
resending command...
< waiting for device >
sending 'zip' (113449 KB)...
OKAY [ 5.427s]
writing 'zip'...
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_s
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP ERROR CODE, 22
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 7.544s
htc_fastboot finished. total time: 32.112s
I'll get in on the SD card and try it as well.
Click to expand...
Click to collapse
Update-
When trying to update from SD card, I get the message:
E: footer is wrong
Update Package verification took 0.2 s (result 1)
E: Signature verification failed
E: Error 21
Installation aborted
Byrdman2b said:
Update-
When trying to update from SD card, I get the message:
E: footer is wrong
Update Package verification took 0.2 s (result 1)
E: Signature verification failed
E: Error 21
Installation aborted
Click to expand...
Click to collapse
You're using Download mode to install via SD card method, as stated in my stock thread, where firmware is posted, right?
Sounds like you're trying to flash via stock recovery, which is not the correct procedure...
Sent from my Pixel 3 XL using Tapatalk
I used Recovery mode (not download mode) to apply the update from SD card. Is this the correct procedure?
Byrdman2b said:
I used Recovery mode (not download mode) to apply the update from SD card. Is this the correct procedure?
Click to expand...
Click to collapse
No, check my post for flashing firmware via SD card method in the same thread, second post.
Same process applies to flashing an RUU.
Sent from my Pixel 3 XL using Tapatalk
santod040 said:
No, check my post for flashing firmware via SD card method in the same thread, second post.
Same process applies to flashing an RUU.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Success!!!!!!! Success!!!!! I flashed it from SD, from bootloaded mode, and it worked properly. My phone is up and running now. Wow, I thought I would have to purchase another one. I am very grateful to you Sir. You are the 3rd person that I have worked with in order to get this phone working. I even took it to a shop where they repair phones, but they still couldn't get it working. Thank you for your help.
Byrdman2b said:
Success!!!!!!! Success!!!!! I flashed it from SD, from bootloaded mode, and it worked properly. My phone is up and running now. Wow, I thought I would have to purchase another one. I am very grateful to you Sir. You are the 3rd person that I have worked with in order to get this phone working. I even took it to a shop where they repair phones, but they still couldn't get it working. Thank you for your help.
Click to expand...
Click to collapse
No problem.
I'm glad to hear it worked out for you. [emoji106]
Sent from my Pixel 3 XL using Tapatalk
I know that it might be wrong to post here but, also i got one from eBay too. Phone was on Nougat and working fine, updated to Oreo when i turned on the Wifi on home. Oreo update begins and was working fine, except that on the lockscreen it was showing two cities instead of one... I tried everything to set it one one city but i couldn't figure what was wrong. So i decided to wipe it to factory reset. And then the problems begins... I notice that the battery drains so fast that i don't know why or what is causing that stuff... I charge it by quick charge and low charge and it's the same battery life just go around 11 or less hours. And it is always warn doing nothing, just lying around there. I had wiped and even installed the RUU from an external SD and the issue continues...
Also i had to rename the zip because i had the same error 21 and i changed the name and worked
Hello guys,
I need help. Definitely
My phone stopped booting into system after some service.
First a little brief:
Phone never showed any problems before.
LCD+Touch were replaced.
Phone stopped booting into system.
Stills boots/ works perfectly in fastboot, recovery and userdebug.
Tried:
factory reset
unlocking and relocking bootloader
flashing several factory and stock RAWs
stock recovery and TWRP
stock raw alone
update stock system from stock raw
twrp + stock rom + magisk
twrp + lineageos + magisk
several guides on this forum
Nothing works. Problem remains the same, doesn’t matter the alternative I try.
Now the whole story:
I’ve had this phone for a while. Always did the OTA updates. Never had problems… at all.
Some days ago, I dropped it and was finally able to break the screen. The lcd became black in some spots and had different brightness in others. Touch kind of worked, kind of got crazy after some seconds (and I had to turn the screen off and on again).
I’ve got some experience in repairing electronics and phones. So, I watched/read a dozen guides about this particular service, bought an original LCD+Touch kit, and replaced myself.
No apparent problems with that. The process is quite simple and straight forward. (I knew what I was doing. But if you tell me something might be wrong with that, I will look into it. I will take any help. Just tell me what to do.)
And so it begins.
I set my phone up again - without gluing anything, as it was the first test – and turn it on. It seems to boot normally… boot logo shows normally… boot animation seems to take longer than usual… the screen suddenly goes black.
I open the whole thing again, check every connector, everything is ok.
I try to turn it on again, now the phone turns off after just one or two seconds of boot animation.
I did then a factory reset, problem persisted just the same.
I thought to myself: “ok, then. System must be somehow corrupted.”
I updated the system to the lasted version in ASUS website trough adb sideload. Problem persisted.
“ok, maybe I must clear the system partition then… let’s go a little further”.
I read some guides, and proceeded to unlock the bootloader (flash factory raw, fastboot commands, flash oreo raw), flash TWRP and LineageOS.
When I turn it on again, a bit of hope. Boot animation takes, again, a long time. An “encrypting device” screen comes up and I believe it’s finally over. But no. The phone goes off after about 10 seconds of supposed encrypting and, when I turn it on again, same as before… two seconds of boot animation and then darkness.
After that I Just went deeper into the habbit hole.
Tried several brick fixes in sent by the XDA community.
Tried flashing RAWs using Asus Flash Tool (v1.0.0.86 (20201124)) and flashall_AFT.cmd (that comes inside de RAWs.
Tried all combination and orders I could imagine of the following RAWs:
CSC_ZE552KL_13.1301.1603.53_WW_Lock_20171128
CSC_ZE552KL_13_13_1_36_M2_6_7_P7_userdebug
WW_ZE552KL_13.20.10.137_M3.10.35_Phone-user.raw
WW_ZE552KL_14.2020.1703.28_M3.10.47.3_Phone-user.raw
WW_ZE552KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw
WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
It doesn’t matter. Whenever I flash a RAW, the phone goes to this encrypting process and then goes black. From there on, I can flash anything through adb sideload, fastboot or twrp…. It shows the boot logo, (possibly shows the dm-verity screen, depending on the set up), and goes off after about 2 seconds of boot animation.
Tested everything I could with TWRP: LCD, Touch, mounting partitions and storage seem to be working fine.
Tested everything I could with the factory RAW userdebug (using command fastboot oem enable-userdebug boots a very simple system (there’s an image below)): Again, LCD and touch work fine. Also, hard keys, wifi, Bluetooth, calling, messaging, 4G and both speakers are working.
And there we get to present time. I just don’t know what else I can do.
My next steps would be going into QFIL flashing. That would actually be new to me. But since I can use all these functions properly, it doesn’t seem to me that that’s the way to go.
Please help. I will take anything. Tell what I may have passed by. Send me the guides you think may help me, even if I’ve already tried.
I can give you any information you guys believe is pertinent.
I will start leaving here some info I think may help:
ZE552KL Z012DC ASUS_Z012DC Brazilian model BRAZIL
4GB RAM. 64GB storage.
Code:
C:\Users\Vanisi\Desktop\ZE552KL>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4236000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:O-CS4 - 4 - user
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x1fe00000
(bootloader) partition-type:asdf:ext4
(bootloader) partition-size:asdf: 0x4000000
(bootloader) partition-type:APD:ext4
(bootloader) partition-size:APD: 0xd000000
(bootloader) partition-type:ADF:ext4
(bootloader) partition-size:ADF: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x8000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd683f7000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xf0000000
(bootloader) cpuid:046
(bootloader) project:ZE552KL
(bootloader) serialno:H2AZB601E85****
(bootloader) kernel:lk
(bootloader) product:MSM8953
all:
Finished. Total time: 0.281s
C:\Users\Vanisi\Desktop\ZE552KL>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) Device is_authorized: false
(bootloader) ssn_num: H2AZB601E85****
(bootloader) isn_num: MB352KL0AB****
(bootloader) check_fused: 0
(bootloader) Device resize: false
(bootloader) BOOT_COUNT : 175
(bootloader) SB=Y
(bootloader) Re-partition: false
(bootloader) Device had been rooted: >>> YES <<< (Warranty void)
(bootloader) Device has copy fsg to fsgCA: false
(bootloader) Device last copy fsg status: fail
(bootloader) verity_mode: 1
(bootloader) is_ffu: false
(bootloader) verity_counter: 0
(bootloader) total verity_counter: 0
OKAY [ 0.203s]
Finished. Total time: 0.203s
C:\Users\Vanisi\Desktop\ZE552KL>fastboot oem system-info
(bootloader) board_info: msm8953
(bootloader) mem_info: 4GB
(bootloader) mmc_info:
(bootloader) product_name: ASUS_Z012D
(bootloader) product_locale: en-US
(bootloader) product_carrier: US-ASUS_Z012D-WW_Phone
(bootloader) csc_build_version: WW_ZE552KL-13.20.10.152-20161222
(bootloader) bt_mac: 2C4D5****B18
(bootloader) wifi_mac: 2C4D5****E38
(bootloader) imei: 35905207393****
(bootloader) imei2: 35905207393****
(bootloader) ssn: H2AZB601E85****
(bootloader) isn: MB352KL0A****
(bootloader) color: 1B
(bootloader) country: BR
(bootloader) customer: CKD
(bootloader) revenuecountry: BR
OKAY [ 0.188s]
Finished. Total time: 0.188s
(the **** don't actually come up... it's just to hide the information I believe may be sensitive)
Help. Please