Database Users

(Q) Help needed, unable to flash a recovery mode, and phone not booting any more.

Hello, I would really appreciate some advice.
I had a Magic 32b which i rooted, flashed CM and passed on to my brother about an year ago. He now tried to flash another ROM and maybe bricked the phone.
He followed steps in [custom Radio/SPL for dummies][32B] http://forum.xda-developers.com/showthread.php?t=523680
He couldn't flash recovery mode because of an error ( signature verify fail) but he could load it via fastboot boot img and followed steps- 1-9 doing so. after superwipe and flashing radio he flashed Hboot and then couldn't get into recovery any more.
Now the phone has default recovery mode, and every time i try to flash an "update.zip" it gives me "signature verification failed".
Does not boot normally.
In fastboot cannot flash any recovery "signature verification failed" and when i try to load a recovery by fastboot boot recovery, it downloads it and then gets stuck at booting.
HBOOT-1.33.0013d
RADIO- 2.22.27.08
Any advice would be great.
Thanks in advance

hope this helps, seen it on other threads:
fastboot getvar version-main 1.75.162.3_R
fastboot getvar cid VODAP102
I know that i should make a goldcard to solve the problem, but if the phone only boots in recovery and fastboot, ADB commands do not work. Only fastboot commands work, so how can I make a goldcard?

The fix:
Download this file: https://rapidshare.com/files/1368708004/1.89.162.1.nbh
Download my fastboot commander tool found in my signature (not the magic version)
Using the tool, flash the file using the "Full zip" tab and do so inside fastboot mode.
It can take some time to finish....
Once done you should be back to stock 1.89.162.1 Vodafone Germany CRC24
From there, follow my root guide which is found in my signature...
Good luck

Thanks a lot for your response, I tried flashing the ZIP but failed
The weird thing is that it appears at S-ON, but i'm pretty sure that i had S-OFF an year ago when I flashed CM ROM, a new kernel and recovery on it ( otherwise it wouldn't have worked).
Is it possible to change the SPL from a good one to a perfected one with security? (at least that's what I think my brother did)
###Calling fastboot with: getvar version-baseband###
version-baseband: 2.22.27.08
finished. total time: 0.008s
********************************
###Calling fastboot with: getvar version-bootloader###
version-bootloader: 1.33.0013d
finished. total time: 0.002s
********************************
###Calling fastboot with: getvar product###
product: sapphire
finished. total time: 0.006s
********************************
###Calling fastboot with: getvar mid###
mid: SAPP10000
finished. total time: 0.001s
********************************
###Calling fastboot with: getvar security###
security: on
finished. total time: 0.002s
********************************
###Calling fastboot with: getvar build-mode###
build-mode: SHIP
finished. total time: 0.003s
********************************
###Calling fastboot with: flash zip
sending 'zip' (97795 KB)... OKAY [ 20.744s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
I have a nandroid Backup made, but i can't restore it
I'm open to any other suggestions.
and thanks again for at least giving mea little hope .

Try to put the nbh file in same directory as fastboot.exe then issue this command
Code:
fastboot flash nbh 1.89.162.1.nbh

Succeeded
I followed the last instructions and managed to setup the ROM.
after rooting and installing new radio , SPL and new ROM i'm now running Ginger Yoshi 1.2 and gave the phone back to my brother. Hope that i won't have to deal with it again and just stick to my SGS.
Thanks a lot for your support and applications.
I tried to donate, but I got some errors( I tried three times) and couldn't finish the transaction. I think that my bank does not see pay-pal as a trusted site and rejects the transaction.

No problem... glad it worked out for you.
You actually just helped me find a bug in the tool (the first one).
"Full rom" tab should automatically change the fastboot command depending on the rom type. In your case, it was nbh and not zip... this is gona be fixed :0)

VNS-L21 bricked. Black screen. Only fastboot available

hello
i had a beautiful and full working P9 Lite, VNS-L21 Dual Sim with stock Android 7.0.
wanted to downgrade to MM, but i got it bricked
boot unlocked, flashed TWRP, then OEM file and then Official (all from here : http://www.htcmania.com/showthread.php?t=1261335)
after starting official MM flashing by VOL+, VOL- and POWER, got error "Software install failed!" and dead from that moment.
flashed different TWRP and tried to boot into recovery by VOL+ and POWER, but nothing
also flashed different versions of 6.0 and 7 by fastboot, nothing. at some point boot got locked back, but unlocked it again.
disassembled, disconnected battery, nothing.
ready to try any ideea you think may be lucky.
thanks

If you're getting fastboot try and unlock your bootloader, install twrp for mm. Try and download your firmware eg L21C532B160, leave it in the zip format, place on your SD card, then boot into TWRP and flash the zip file. That should do the trick.
Sent from my HUAWEI VNS-L21 using Tapatalk

Install revolution recovery flash oem and dload c432

@slaughta8868, @Dimitardt - thanks, but in that situation only DC Phoenix or Furious Resurrector could get me out. These 2 progs are able to write absolutely anything into phone, and all needed partitions. Also able to revive by testpoint. i had access to Furious Resurrector and now phone is alive again.
but got this error, no matter what firmware is written.
any idea ?
photo fastboot http://imgur.com/a/vqoJM
C:\AndroidADB>fastboot oem get-build-number
...
(bootloader) :VNS-L21C432B130
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidADB>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1470987496
OKAY [ 0.000s]
finished. total time: 0.000s
thanks

https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 try this

I have the same problem with my VNS-L31. Tried to rollback and it just turned off at 99% or 100% and now it does not turn back on. I can only access fastboot through the PC. No dload or recovery. Tried flashing separate system.img, boot.img etc. files but it does not work. Is there really no way other than Furious Resurrector or DC Phoenix to flash the full UPDATE.APP through fastboot? Is there no package, custom ROM, whatever, which has an android-info.txt inside?

i got same problem. after flash no vibration, no display, only fastboot accessible:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :EVA-L09C432B136
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: RISK
(bootloader) change_time: 1463672304
OKAY [ 0.008s]
finished. total time: 0.010s

nbkappa said:
@slaughta8868, @Dimitardt - thanks, but in that situation only DC Phoenix or Furious Resurrector could get me out. These 2 progs are able to write absolutely anything into phone, and all needed partitions. Also able to revive by testpoint. i had access to Furious Resurrector and now phone is alive again.
but got this error, no matter what firmware is written.
any idea ?
photo fastboot http://imgur.com/a/vqoJM
C:\AndroidADB>fastboot oem get-build-number
...
(bootloader) :VNS-L21C432B130
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidADB>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1470987496
OKAY [ 0.000s]
finished. total time: 0.000s
thanks
Click to expand...
Click to collapse
Can you show me test point image VNS-L31 please?

Test point
Here test point image

XT1563 - boot loop

I have Moto X play XT1563. It was stuck in a boot loop - moto logo->circle and "erasing"->reboot
Fastboot and ADB works
I tried to flash new firmware (stock image) - failed:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
based on that and research I decided to unlock bootloader, which ended up with:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
since phone is unalbe to boot I cannot go to dev options. Is there any way to have it done using adb or fastboot? even low level linux way to change something in the config?
or (easier way) - anyone aware where can I find new Bell firmware? now I have M8936_2020632.44.03.21.57R LUX_BELLCA_CUST
Appreciate any suggestions

Check here
https://github.com/motoxplay/stock
there is a bell firmware but is tagged with a BELL? so, don´t know if will it work
Cheers.

Thanks - checked that before - this one is 6.0.1 and I need 7.1.1
Version NPD26.48-21-1 to be exact

I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s

stingu said:
I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
Do you have an unlocked bootloader?

Did you try to install TWRP ? It's not bootloader unlocked, is it ?

Bootloader is locked, while trying to unlock it I get:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Flashing and booting fails, for stock and TWRP

Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?

Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?

Need help to unbrick my Mate 8

My Mate originally is L29C636 running on Nougat beta (I forgot the exact version)
Because I wanted to get Oreo, I downgrading to MM using rollback package, debrand to DL00 (Which I think unsuccessful) and then flash DL00 ROM. Along the way I think I mess up pretty badly. In MM TWRP I tried to flash Oreo ROM and it stuck halfway. I think the fastboot and EMUI dload got replaced during this process.
Now what is working are I can boot fastboot and it show my device is unlocked. eRecovery also can be accessed. EMUI dload can also be accessed. Don't have TWRP and no System/OS so can't boot up.
In fastboot I can't flash anything at all it seems. Oreo/Nougat/MM TWRP recovery, Nougat and MM system.img/userdata.img/cust.img/cache.img, all failed. I manage to get some info on my current brand:
Code:
C:\SDK\android-sdk-windows\platform-tools>fastboot oem get-product-model
...
(bootloader) NEXT
OKAY [ 0.003s]
finished. total time: 0.004s
C:\SDK\android-sdk-windows\platform-tools>fastboot oem get-build-number
...
(bootloader) :NXT-C00B103
OKAY [ 0.004s]
finished. total time: 0.005s
C:\SDK\android-sdk-windows\platform-tools>fastboot getvar vendorcountry
vendorcountry: dualcu/cn
finished. total time: 0.003s
C:\SDK\android-sdk-windows\platform-tools>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.020s
C:\SDK\android-sdk-windows\platform-tools>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.014s
With eRecovery, it always "Getting package info failed" message. I've tried changing my wifi DNS to 81.177.139.39 and also 188.225.84.142 but both same result. Maybe because my oeminfo all screw up?
In EMUI dload I tried using UPDATE.APP from L29C636's Nougat and MM, both fail. Oreo "DL00C17B828 (8.0.0.828) " and "DL00C17B839 (8.0.0.839)" also fail, but using HuaweiUpdateExtractor_0.9.9.5 when I tried to open UPDATE.APP content, it give
Code:
RECOVERY_RAMDIS.img: Invalid header crc - Expected: 65161 Got: 27292
So I don't know is it Oreo ROM not compatible with HuaweiUpdateExtractor? But the file that come together in the zip "update_NXT-DL00_dualcu_cn.app" content can be viewed by HuaweiUpdateExtractor, thought when I try to fastboot flash CUST.img and USERDATA.img that I extracted from "update_NXT-DL00_dualcu_cn.app", it still getting FAILED message.
I'm really out of idea now whats more can I do. I already spend tens of hours trying different ways or combination and reading as many info to see if I missed out something. If anyone can give some suggestion what else should I try, I really appreciate it. :crying: :fingers-crossed:

I can't make TWRP on my Asus X00QD (ZE620KL)

Hello,
I can unlock my phone :
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) ABL Info: Q-ZE620KLXXXX
OKAY [ 0.008s]
finished. total time: 0.008s
but I don't make TWRP...
For flash it was "good" but it's recovery original with command line
and for boot in TWRP I have :
fastboot boot 'recovery.img'
downloading 'boot.img'...
OKAY [ 0.637s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.638s
I tested 3 TWRP different ones with the same result
Can you help me please ?

Please help me, I have no solution, and I want to put custom rom in my phone.
I have to put TWRP in my phone for custom rom

Ciao!
this error is common on my Asus x00QD when i use stock Android 10, you need to downgrade to 9 !
Please check on the Net for Q-P-UL-ASUS_X00QD-ASUS-16.0615.2002.120-1.1.33-user.zip and push it via SDcard or ADB, then retry with FastBoot

I can't make, when reboot, it was Android 10...
And Asus flash tool does not work, he can't find m'y phone in fastboot and recovery