Database Users

Looping reboot

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

Re-locking bootloader but is unlocked at each reboot

Hi everyone,
I went back to stock recovery and stock ROM (5.9.020S) in order to use Android Pay.
But I am facing one last issue for locking the device. Each time I go into fast boot mode, I lock the device, I check with device-info, it confirms it is locked. However after reboot I check again it has reverted back as unlocked.
How can I lock the persistently?
It is as if there is a script somewhere at boot that automatically unlock the device bootloader.

- flash the aboot from stock ROM
- flash the xbl from stock ROM
- do not reboot to keep the bootloader still unlocked
- boot in TWRP (do not flash)
- wipe, factory reset, format, reboot system

In order to do what you suggest, I flashed TWRP recovery first. Then I followed all the steps. Then I tried to flash the stock recovery back and tried to lock. Unfortunately, it did not help, still the same issue.
In fastboot, I do "fastboot flashing lock" or "fastboot oem lock". Then I check the status with "fastboot oem device-info". Right after, I always get "Device unlocked: false" which is good and confirm the lock has worked at first.
But if I reboot the bootloader and try again, then the status is back to "Device unlocked: true" and the device is unlocked again. It keeps unlocking after reboot if I attempt to lock.
I need to have the device NOT unlocked in order to use Android Pay. So now, I am not sure what to do to be able to lock the device...

You don't need to flash TWRP in fact sometimes you don't need it (if there is no encryption but do it to be sure) right after flashing
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn

These were indeed the files I flashed previously for aboot and xbl.
I tried again to flash the files in fastboot mode, then lock the device with "fastboot oem lock". After reboot, it is unlocked again.

Did you extract those files from 20s or any official OTA zip? Flashing those files are guaranteed to lock the bootloader again. I've tried it many times already so not sure what else could be missing.
What is being displayed when you do right after the flashing and TWRP steps?
Like this?
fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.097s]
finished. total time: 0.098s
---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------
See this thread if it will help...
https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513

I got the files from 20S. It really does not work for me.
I do:
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
After this when I check, it is like this (before and after reboot):
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.110s]
finished. total time: 0.111s
Click to expand...
Click to collapse
Anyway, thanks for trying to help me!

unsuccessful unlock attempt; bootloader status: "flashing_unlocked",

I have already unlocked a few Motos, including Moto G4 Play without any problem.
But this time is different.
After my unlock attempt, the phone is not actually unlocked and 'fastboot getvar all' reads out the following:
Code:
fastboot getvar all
(bootloader) version-bootloader: moto-msm8952-B1.03
(bootloader) product: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) sku: XT1625
athene:7.0/NPJ25.93-14/16
The phone boots and works ok, but the bootloader is NOT unlocked.
I guess I have to flash bootloader B1.03, 2016-10-21, (0xB103) from stock NPJ25.93-14?
Code:
fastboot flash bootloader bootloader.img

The getvar commands says that the bootloader is unlocked. What makes you think it isn't?

zeomal said:
The getvar commands says that the bootloader is unlocked. What makes you think it isn't?
Click to expand...
Click to collapse
Code:
(bootloader) securestate: flashing_unlocked
On bootloader screen:
Battery OK (Charging)
flashing_unlocked
On all other Motos I have unlocked it was:
Device is UNLOCK. Status Code:3

Regardless, did you try flashing a new recovery? If it works without a hitch, your device is unlocked.
Devices change.

del

zeomal said:
Regardless, did you try flashing a new recovery? If it works without a hitch, your device is unlocked
Click to expand...
Click to collapse
When I boot TWRP and run TWRP's file manager, I do not have access to files, even those on /external_sd.
which TWRP to use?
twrp-3.1.1-0-athene.img
twrp-3.1.1-athene_shreps.img

so you have twrp recovery installed correctly ???.
if yes then try to flash super su or custom rom ( resurrection remix best , i am using )
but take back up first with twrp
Sent from my Moto G4 Plus using Tapatalk

If you can flash and replace stock recovery with TWRP, your device is unlocked. You might want to enable TWRP to allow access to modify the system in the first screen, by flashing TWRP again and selecting that option in the first startup screen.

Stuck with Fastboot, DFU and locked bootloader

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

Bricked Xiaomi A1

Hello all,
I have my A1 with this problem after installing a custom rom, then tried to get back to stock rom and had no network. After that I made a lot of mistakes and now can't use mi flash tool, can't do a fastboot oem unlock(returns error) or fastboot oem edl(says ok but nothing happens.
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
Any ideas? I know I was dumb but i don't know what to do.
Thanks in advance

Had no answers but still manage to solve it.
1. fastboot oem set_active a
Then the phone booted.
2. Enable oem unlock at settings developer tools.
3. Get back to fastboot mode and boot into twrp.
4. Enjoy and flash whatever you want.