Dear XDA Community,
Today as I was using my PC I picked up my phone and found it to be turned off. I tried turning it on but it would just get stuck on the "M" logo and turn off after some seconds, and it wouldn't go further than that screen. I tried going into the recovery and tried factory resetting but it fails... Please I need help as I fear that my phone is dead forever :crying::crying:
The bootloader is locked and there is no way to unlock it as At&t does not allow.. The phone does not go after the M screen.. Please help since I cannot afford a new phone..
EDIT: I also tried to factory reset via fastboot that didn't work and returned this
"D:\Minimal ADB and Fastboot>fastboot devices
TA9890A198 fastboot
D:\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.943s
D:\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) has-slot:cache: not found
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.002s"
Related
Hi ,
I have a really big problem, yesterday, my Moto G was good, without any problem, and in a few minutes, the cellphone shutdown and i tried to turn on, the screen was stuck in the Motorola Logo, i found a solution for that in the internet, Flash and put the original Firmware, i tried to do that, i deleted all(With Minimal ADB and Fastboot), and when i going to flash the firmware, the cellphone shutdown, the battery died.
I tried to charge it all the night, with the original charger, i don't have recovery mode, i tried to charge it in Unlock and Lock mode in the fastboot, anything happen, in this moment, i put a batch with:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
but this is what the console show me:
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
I Really need somebody can help me with this problem.
Thanks for all.
(Sorry if my english is too bad)-
imDavid said:
Hi ,
I have a really big problem, yesterday, my Moto G was good, without any problem, and in a few minutes, the cellphone shutdown and i tried to turn on, the screen was stuck in the Motorola Logo, i found a solution for that in the internet, Flash and put the original Firmware, i tried to do that, i deleted all(With Minimal ADB and Fastboot), and when i going to flash the firmware, the cellphone shutdown, the battery died.
I tried to charge it all the night, with the original charger, i don't have recovery mode, i tried to charge it in Unlock and Lock mode in the fastboot, anything happen, in this moment, i put a batch with:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
but this is what the console show me:
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
I Really need somebody can help me with this problem.
Thanks for all.
(Sorry if my english is too bad)-
Click to expand...
Click to collapse
Moto bootloader doesn't support 'battery-voltage' command.
c:\Android>fastboot devices
DXU0218424003291 fastboot
c:\Android>fastboot oem get-product-model
(bootloader)
OKAY [ 0.000s]
Finished. Total time: 0.000s
c:\Android>fastboot oem get-psid
FAILED (remote: 'Command not allowed')
Finished. Total time: 0.047s
c:\Android>fastboot oem get-build-number
(bootloader) :
OKAY [ 0.000s]
Finished. Total time: 0.016s
c:\Android>fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.000s]
Finished. Total time: 0.000s
phone is now stuck in fastboot mode. screen will not turn on, no vibration or lights at all. i used flash and downgrade tool.
jerimiepalmer81 said:
c:\Android>fastboot devices
DXU0218424003291 fastboot
c:\Android>fastboot oem get-product-model
(bootloader)
OKAY [ 0.000s]
Finished. Total time: 0.000s
c:\Android>fastboot oem get-psid
FAILED (remote: 'Command not allowed')
Finished. Total time: 0.047s
c:\Android>fastboot oem get-build-number
(bootloader) :
OKAY [ 0.000s]
Finished. Total time: 0.016s
c:\Android>fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.000s]
Finished. Total time: 0.000s
phone is now stuck in fastboot mode. screen will not turn on, no vibration or lights at all. i used flash and downgrade tool.
Click to expand...
Click to collapse
huawei not allowed downgrading... flash back latest emui9 with erecovery
spityu85hun said:
huawei not allowed downgrading... flash back latest emui9 with erecovery
Click to expand...
Click to collapse
He's not even able to enter erecovery or any mode. Most likely he cannot even turn it off. His device is on with black screen.
@jerimiepalmer81
How did you brick it? I mean which firmware were you on and to which fw you wanted to rollback? Which method did you use.
I am afraid I don't have good news for You. I hard bricked my clt-l29 when I tried to rollback to oreo 161 from pie 195 (when it wasn't allowed). Eventually I had my motherboard replaced by hw service center.
jerimiepalmer81 said:
c:\Android>fastboot devices
DXU0218424003291 fastboot
c:\Android>fastboot oem get-product-model
(bootloader)
OKAY [ 0.000s]
Finished. Total time: 0.000s
c:\Android>fastboot oem get-psid
FAILED (remote: 'Command not allowed')
Finished. Total time: 0.047s
c:\Android>fastboot oem get-build-number
(bootloader) :
OKAY [ 0.000s]
Finished. Total time: 0.016s
c:\Android>fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.000s]
Finished. Total time: 0.000s
phone is now stuck in fastboot mode. screen will not turn on, no vibration or lights at all. i used flash and downgrade tool.
Click to expand...
Click to collapse
Exact same thing happened to me. Had canadian rebranded to l29 was working great for a long time then I was upgrading to pie and phone bricked. Tried everything from the OTG method ull find in various thread to the flash files from extracting firmware and then flashing using fastboot (basically the method call of flashing enough files to get the phone in working order) I flashed canadian and l29 files both 8.1 and 9.0 nothing did anything.
Finally took it to huawei third party repair store first one told be it was water damage second one wanted me to send to huawei cuz "software issue" third one told me they will replace mother board but ill take about 3 week because first they have to replace lcd just in case. I didnt tell anyone of them that i ****ed it up just told them ota update and when i came back to the phone it was like this. Getting my phone back today after work.
Gluck.
I am thinking about trying sigmakey Huawei edition. Its the only tool I can find that can flash the chip. Last ditch effort. Says can fix hard brick. And if phone responds to fastboot commands the motherboard has to be working in some fashion.
I was able to flash phone with DC phoenix after accessing test point and triggering Huawei usb com 1.0. screen now turns on and will boot recovery but phone shows no IMEI, no ESN, and will not boot system. I have tried everything. Flashed every OTA that has ever been issued for this device, as well as trying the open Kirin ROM and nothing, obviously I have tried recovery, booting to a patched twrp, firmware finder DNS method. Can not for the life of me figure out the "ANDROID_INFO.txt" problem to flash OTA zip from fastboot. So I think I have corrupted the partitions that Huawei won't let me see/flash. Any ideas???
Hello,
My Huawei P10 will not start up. Can boot into fastboot no problems, this is what comes out.
Android reboot reason:
coldboot
NA
volumnkey_down_press_process_func
Tried to flash a recovery into phone to boot upin recovery, however it comes with this error.
fastboot flash recovery twrp_p10_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.532s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.539s
When charging the Electric symbol appears with a circle around it and it is in red. Randomly when charging it will turn on by itself and get frozen on the Huawei logo. But it will not turn on at all when not plugged into mains. Trying to turn on when it is plugged in mains only displays charging logo.
Not entirely sure if that is the correct recovery that I should be using, quick google search has given me that result. Would it be possible to flash a stock ROM?
suenoromis said:
Hello,
My Huawei P10 will not start up. Can boot into fastboot no problems, this is what comes out.
Android reboot reason:
coldboot
NA
volumnkey_down_press_process_func
Tried to flash a recovery into phone to boot upin recovery, however it comes with this error.
fastboot flash recovery twrp_p10_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.532s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.539s
When charging the Electric symbol appears with a circle around it and it is in red. Randomly when charging it will turn on by itself and get frozen on the Huawei logo. But it will not turn on at all when not plugged into mains. Trying to turn on when it is plugged in mains only displays charging logo.
Not entirely sure if that is the correct recovery that I should be using, quick google search has given me that result. Would it be possible to flash a stock ROM?
Click to expand...
Click to collapse
Bootloader and FRP unlocked (both red on Fastboot screen)?
Test in Fastboot (first command below):
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
Try booting to eRecovery (connect to charger, keep pressing Vol+, then Pow) and Install latest firmware and recovery
zgfg said:
Bootloader and FRP unlocked (both red on Fastboot screen)?
Test in Fastboot (first command below):
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
Try booting to eRecovery (connect to charger, keep pressing Vol+, then Pow) and Install latest firmware and recovery
Click to expand...
Click to collapse
PHONE Locked
FRP Lock
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastboot oem get-product-model
...
(bootloader) VTR-L09
OKAY [ 0.005s]
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
vendorcountry: ee/gb
finished. total time: 0.006s
C:\adb>fastboot oem get-build-number
...
(bootloader) :NRD90M test-keys
OKAY [ 0.005s]
finished. total time: 0.005s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :VTR-L09C652B101
OKAY [ 0.007s]
finished. total time: 0.007s
That is what I get when running your code
Edit: Doing VolUp + Power key with charger does nothing. restarts the charging logo.
charging logo loops when charger is plugged in and doing nothing. Shows charging logo, led notification flashes red 3 times and turns off, turns on again with charging logo, red led flashes 3 times, turns off...
suenoromis said:
PHONE Locked
FRP Lock
Code:
C:\adb>fastboot oem get-bootinfo
(bootloader) locked
OKAY [ 0.001s]
finished. total time: 0.001s
...
Click to expand...
Click to collapse
So Bootloader (and FRP=OEM) locked, you are not allowed to flash anything ;(
zgfg said:
So Bootloader (and FRP=OEM) locked, you are not allowed to flash anything ;(
Click to expand...
Click to collapse
Phone = Dead
?
suenoromis said:
Phone = Dead
?
Click to expand...
Click to collapse
You can try flashing by Testpoints - need to open cover and short-wire the pins.
Never played with, here is some guide for P10
https://forum.xda-developers.com/mate-9/help/solution-19-00-fix-hardbricked-huawei-t3750315
You can also ask for paid help from (discuss before you buy credits):
https://ministryofsolutions.com/paid-services/amp
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://chimeratool.com/
https://funkyhuawei.club/
Hi!
Sorry for my English at the beggining!
After a successful downgrade (camera problem) and an attempt to return to the new android version through dload, the phone did not start.
Stops on the huawei logo, does not go to bootloader at all, and what is worse, the phone does not go off because it is constantly trying to start itself and because of this the battery is discharged and I can not do anything. Anyone have any ideas?
Only fastboot is working but nothings works there and photo is in ink below how it looks.
Plz help!
imgur.com/xeAsELp
wysoczanin said:
Hi!
Sorry for my English at the beggining!
After a successful downgrade (camera problem) and an attempt to return to the new android version through dload, the phone did not start.
Stops on the huawei logo, does not go to bootloader at all, and what is worse, the phone does not go off because it is constantly trying to start itself and because of this the battery is discharged and I can not do anything. Anyone have any ideas?
Only fastboot is working but nothings works there and photo is in ink below how it looks.
Plz help!
imgur.com/xeAsELp
Click to expand...
Click to collapse
You rolled back to MM - actually, what was your stock firmware and to which (c900, by DLOAD ?) did you roll-back?
As per Fastboot screen, rolling-back (as usual) locked FRP and Bootloader, but still try to execute commands (what they return for status?) :
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Your Fastboot photo says to connect to HiSuite - I don't know could you (without booting to system), did you try if it maybe offers you restoring the firmware
Hi! Thx for answering!
Below are the commands answear!
It was the newest 7.0 but my bro had problem with camera and tried to rollback to MM. He usesd DLOAD method.
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot devices
MWS7N17118004613 fastboot
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.007s]
finished. total time: 0.007s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot oem get-product-model
...
(bootloader) EVA-L09
OKAY [ 0.005s]
finished. total time: 0.006s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot oem get-build-number
...
(bootloader) :EVA-L09C900B182
OKAY [ 0.004s]
finished. total time: 0.005s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Command not allowed)
finished. total time: 0.011s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools> fastboot getvar vendorcountry
vendorcountry: dt/pl
finished. total time: 0.005s
PS C:\Users\Lukasz\Desktop\Marcinek\adb\platform-tools>
Im downloading hisuite right now
Issue fixed!
DC Phoenix was needed to do this, and HCU!
So if someone have similar issue, u r gonna need to spend 20 euros to fix it
Hi, I'm pretty sure I know the answer is I'm out of luck but hoping for some tips if anyone has them. My Moto X4 XT1900-1 AndroidOne phone bricked itself. It was complaining about not having a SIM card, so I shutdown the phone to clean the SIM card, and when it rebooted I got the "your device is corrupted and can not be trusted" screen of death. This phone is not unlocked and I've tried to unlock it with no luck. I also tried using the Motorola Rescue and Smart Assistant tool, which fails while flashing the bootloader. These are the commands I've tried from fastboot:
fastboot oem unlock:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.001s]
Finished. Total time: 0.001s
fastboot oem get_unlock_data:
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
Finished. Total time: 0.002s
fastboot flashing unlock:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.001s]
Finished. Total time: 0.001s
fastboot flashing unlock_critical:
(bootloader) Not supported command
OKAY [ 0.000s]
Finished. Total time: 0.000s
Any suggestions would be awesome.