Hi,
I have a Vodafone (UK) branded Desire Z which today froze whilst I was using it. This left me no option to remove the battery and re-insert it to clear the phone.
Unfortunately the phone will not fully boot now - all I get is the standard HTC screen, followed by the Vodafone logo screen. It then goes black and restarts.
I have tried removing the battery and leaving it for a while before reinserting. I have also removed and replaced the sim and the SD card, but still no joy.
Is there a 'safe mode' way of booting the Desire Z that I could try or has my phone just died?
Any help gratefully received.
http://forum.xda-developers.com/showthread.php?t=842495
Hi again,
Thanks for that link - I have read and re-read as suggested and attempted to follow the instructions but the second link (cwm recovery) is dead - it takes you to a 'removed by mod' post, so I didn't get far!
Just to give a bit further info, I took my device into a local 'fone doctor' shop, where they managed to fix it (or so I thought! - cost me £22 as well! ). The phone was back with the stock HTC Sense on it.
Anyway, within about three hours of the phone working, it froze again - and is now back to being stuck on the White HTC boot screen (rather than the looping it was doing previously). I have a feeling that my phone may just be knackered!
If I do the hold volume and switch on thing, I get the following:-
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
Apr 11 2011,23:36:27
....plus the usual HBOOT, FASTBOOT, RECOVERY options etc.
To confirm, I have NEVER rooted my phone. Up to the point it originally froze it had only had the official over the air updates.
I do have HTC Sync installed on my PC, so all of the required USB drivers should be available.
I also have the Android SDK installed (I have dabbled in development) so have adb.
I have read many posts over the last couple of days, but the majority seem to say that if you have "S-ON" you could well be screwed.
Also, adb does not seem to recognise my phone - I have no idea if I had "enable USB debugging" checked or not - again, if this was not the case then I fear I could be screwed!
If anyone has any further idea's of how I could possibly bring my phone back to life it would be hugely appreciated.............or should I just give up and look to get my old G1 unlocked?!
Many thanks.
ok ...you can´t reach your phone with adb if your are not booted into a rom.
do you have fastboot installed on your pc?
if yes then enter fastboot menu (power & tp) and then type fastboot devices on your pc...
your device should be listed.
then type fastboot oem boot and if you are lucky your phone boots again
EDIT: or push power & volume+ to enter recovery and wipe cache or do a factory reset... and do some researching about emmc chip
Many thanks hoffmas. I managed to run the fastboot commands you mentioned which did indeed force a reboot, but unfortunately only back to the white HTC splash screen.
The output from the commands was:-
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot devices
XXXXXXXXXXX fastboot
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is VODAP001
(bootloader) setting->cid::VODAP001
(bootloader) serial number: XXXXXXXXXXX
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =497
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.04.03_M androidboot
(bootloader) .cid=VODAP001 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=VODA-UK androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0BERT06529 androidboot.bootloader=0.85.0013 zygote_oneshot=o
(bootloader) ff kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:66802 msec
FAILED (status read failed (Too many links))
finished. total time: 8.078s
I am guessing that the "FAILED" line at the bottom is another way of saying "Sorry Mate, your phone is knackered!".
I also tried selecting "Recovery" from the menu - that brought up a black screen with the two green arrows around the device picture. This lasted for about 10 seconds, then the phone vibrated about 6 times and went totally blank again - no reboot, no splash screen nothing.
When I try and select the "Factory Reset" option, nothing happens at all. I can move up and down to it using the vol keys, but when I click the power button to select it, nothing happens.
Thanks for all the suggestions anyway - I guess I'll have to get the trusty old G1 unlocked.
I don't think I'll ever tie myself into a two year contract again - bit annoying to be paying for two years when you only get 13months out of the phone!
sry to hear that it didn´t work... but delete the serial number of your phone in your posting.
maybe there is a way to use fastboot for factory reset... but i don´t know how :S
ok... this should be the commands:
fastboot erase userdata
fastboot erase data
fastboot erase cache
Thanks again hoffmas - unfortunately when I run those commands I get this:-
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.016s
Not looking good.
I'm guessing the "FAILED (remote: not allowed)" means pretty much nothing will work.
Thanks again for your help - it is much appreciated.
yes you are right... looks like you need eng hboot to do this
sry, but i have no idea what else you could try... maybe someone else knows better
Related
Hi guys,
I've searched all over the internet and offcourse XDA but I don't know what to do anymore.
Somehow my HTC Desire Z frooze a few weeks back, and after pulling the battery the phone was stuck at the HTC screen. I tried factory reset,recovery etc but that all didn't work. The phone just freezes.
The phone is NOT rooted, unlocked etc. No apps where installed before the phone froze.
Some information:
Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
"fastboot getvar all" output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.4
(bootloader) serialno: SH0B9RT0****
(bootloader) imei: ****************
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
1. Downloaded this RUU which i'm sure it's correct.
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed
2. Drivers are installed and recognized (fastboot and bootloader) on Windows 7 x64 and Windows XP Home Edition. (have 2 PC's just in case)
3. I have installed the latest Android SDK.
4. I have installed HTC Sync. (messed around with drivers from Google and HTC)(believe me I know what i'm doing so it can't be because of the drivers)
5. I don't have or need a goldcard.
6. ADB is recognized by Windows but shows
Code:
error: device not found
7. Fastboot lists my device as "fastboot devices"
Code:
SH0B9RT0**** fastboot
8. When in HBOOT I can manually switch back and forth between fastboot and bootloader, but when selecting "reboot bootloader" from the fastboot menu the phone immediatly freezes again.
9. When the RUU reboots the bootloader the phone freezes.
10. When the RUU says "waiting for bootloader", and I manually power on the phone to HBOOT (seen as "Android Bootloader Interface" by Windows) the phone still isn't recognized.
11. Also tried updating the device list for ADB from the command line "androind update adb" - no result
12. Manually add the device ID "0BB4" to "adb_usb.ini" - still not seen by ADB.
I really believe I tried everything google threw at me. Can my bootloader be corrupted somehow? Any suggestions?
--------------------
UPDATE:
I extracted the ROM.zip from the RUU, renamed it to PC10IMG.zip and placed it in the root of my SD card. Booted up the phone in HBOOT and it automaticly started the update process. At this point it is once again stuck at the bootloader.
At this point I think the eMMC chip is dead.
Code:
[COLOR="Blue"]HBOOT[/COLOR]
[COLOR="Green"]Parsing PC10IMG.zip [SD ZIP]
[1] BOOTLOADER [COLOR="Magenta"]- Updating[/COLOR]
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] SPLASH2
[7] USERDATA
[8] TP
[9] TP
[10] RADIO_V2
[11] RADIO_CUST[/COLOR]
[COLOR="Blue"]Do you want to start update?[/COLOR]
[COLOR="Red"]<VOL UP> Yes
<VOL DOWN> No[/COLOR]
[COLOR="Blue"]Update is in progress...[/COLOR]
[COLOR="Red"]Do not power off the device![/COLOR]
I have the same issue with a TMOUS G2
tried all the steps like you
also tried flashing just the hboot first and also the whole rom through ADB in fastboot but i get a weird error that the command was incorrect by 1byte or something like that
did you ever get anywhere with your phone?
You've probably got a fried emmc, which is a hardware issue.
if it is that, there is nothing you can do about it, except get a warranty replacement (if its still under warranty)
Being unrooted and S-ON limits anything you can do even if the emmc isn't fried.
-Nipqer
Nipqer said:
You've probably got a fried emmc, which is a hardware issue.
if it is that, there is nothing you can do about it, except get a warranty replacement (if its still under warranty)
Being unrooted and S-ON limits anything you can do even if the emmc isn't fried.
-Nipqer
Click to expand...
Click to collapse
yup :/
it was even a pain in the ass to try to do the PC10 method because all zips I found from the gude to restore to stock were too old.. fortunately I was able to extract the rom from the update from a few weeks ago and that would have worked, but as you say, I think my emmc is hosed
wish there was a tool like on the evo where you purposely 'hardbrick' the phone but can flash/repartition the bootloader in ubuntu
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,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Sam to me. Any help?
ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.
typo - fastboot, not fasboot
fastboot oem fb_mode_clear
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.
With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...
Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?
XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
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 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