So my Moto 4g has freeze and reboot during the last official lollipop update and now my phone is unable to boot
I try to reflash a stock rom using fastboot mode (and mflashtool) but I got errors
sending 'recovery' (10240 KB)...
OKAY [ 0.382s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.770s
After searching on xda forum it seems that the bootloader is locked so I'v try to use motorola's website to get the unlocked code (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) but I'v always get the error "Your device does not qualify for bootloader unlocking"
I've try to remove place and using the Unlock Data Scrub Tool but always the same issue.
As my phone is unable to boot is there anyway to unbrick it ? Maybe and official tool able to flash with locked bootloader or something ?
Related
Hi. I can't get passed the google splash screen on a Nexus 5 D821 and could use some help.
Here are the facts:
* The owner of the device told me it bricked after an update.
* The Bootloader is unlocked. When i tried to lock i got the following message:
Code:
fastboot oem lock
...
OKAY [ 0.041s]
finished. total time: 0.041s
But it wasnt persistent. When given reboot comand the phone switched OFF instead. I turned it on to bootloader again and it was still unlocked.
* I tried flashing stock rom LRX22c manually after a failed attempt with the flash-all script. I got the following error for bootloader, radio, boot and recovery:
Code:
FAILED (remote: flash write failure)
* I tried erasing cache and flashing userdata but the after over 60 minutes waiting i came to the conclusion that i wasnt going anywhere and just rebooted the phone.
*The only thing im actually able to flash without an error message is system.img:
Code:
fastboot flash system ~/Downloads/hammerhead-lrx22c/image-hammerhead-lrx22c/system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (981472 KB)...
OKAY [ 30.934s]
writing 'system'...
OKAY [ 62.705s]
finished. total time: 93.767s
* I tried booting TWRP, but i was unable to mount the file system (perhaps because i wasnt able to flash it. i used "fastboot boot twrp.img").
Are phones technically able to get to splash screen or bootloader with a damaged NAND or EEMC chip? Im starting to consider the possibility of a hardbrick. Why would i be able to write system.img if that was the case though? Any help is welcome
===============================================
alright so im pretty sure its a hard brick. The emmc is dead. its a shame :/ guess ill just try to sell it for parts. I would delete this thread because its pretty useless, but i have created my account a few days ago, and i ddont know how to.
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Ben36 said:
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of the imgs in their respective order. they all failed. i got the error
Code:
FAILED (remote: flash write failure)
. system.img was the only .img i was able to write, and i was wondering why. Also, when i try fastboot reboot the phone switches off. It doesnt reboot.
Hi,
after having TWRP, the factory reset function won't work since the data partition isn't recognized yet. Does anyone have the stock recovery version for this?
i already tried downloading from http://huaweidevices.ru/huaweiserviceworkarchivehuawei/eva-l19/recovery.img but it fails with the below message:
fastboot.exe flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35180 KB)...
OKAY [ 1.318s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.318s
edit: found out the issue was related to the allow OEM unlock as turned off
is your bootloader still unlocked?
4Fighting said:
is your bootloader still unlocked?
Click to expand...
Click to collapse
Yups, still unlocked bootloader and currently on twrp recovery, but will need stock recovery if any operations like upgrade or factory reset needs to be done.
I have a bricked moto g turbo which is locked so i cant flash firmware files i tried getting bootloader unlock code but a error shows up to tick allow bootloader unlock in developer options but i can't turn on my phone so I cant enable that option. please help
You don't need to be unlocked to flash factory firmware. Just go to http://forum.xda-developers.com/showthread.php?t=3169639 and get the correct firmware and follow the instructions in http://forum.xda-developers.com/showthread.php?t=3187750 and flash your device.
Bootloader unlock is only needed for downgrading, root, and flashing custom ROMs and recovery. It is not needed to flash a full factory image that is the same or newer.
And for the record, if OEM Unlocking is not enabled, the bootloader cannot be unlocked.
fastboot flash partition gpt.bin
sending 'partition' (32 KB)... OKAY
writing 'partition'... (bootloader) Preflash validation failed
FAIL
FAILED (remote failure)
Execution time is 1(s)
getting error
Hi i have the same error. But my problem is with the módem. I cant take signal. I try flash the original rom and don't work
Do you have the log file?
Hi. I got a Moto Maxx with Android Marshmallow (Telcel carrier).
After trying several roms, I decided to go back to stock, since I couldn't find a Marshmallow rom, I decided to update from 4.4. I installed "Mexico Retail Stock Kitkat /// RETLA_XT1225_4.4.4_KXG21.50-9_cid12_subsidy-DEFAULT_CFC.xml.zip" from this thread. Everything went fine, although I lost the custom recovery during the process.
Then, from the software updater option on the phone, I updated to Lollipop. Unfortunately, it didn't updated. Instead, I got a bricked phone. It didn't turned on.
In order to recover it. I followed this guide. The phone turned on again, and now I am stuck on an "empty" bootloader. The upper half of the screen only shows "Start", similar to the picture from the guide.
But I can't flash any stock rom. It seems by doing the steps of that guide, I re-locked my phone. I can't unlock it because, while I know my unlock bootloader code, mfastboot tells me I must enable "Enable OEM Unlock" in the developer settings (which I can't reach).
Trying to flash any stock rom gives me the following errors:
Code:
[B]>mfastboot flash partition gpt.bin[/B]
[I]target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.020s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.104s[/I]
>[B]mfastboot flash bootloader bootloader.img[/B]
[I]target max-sparse-size: 256MB
sending 'bootloader' (2159 KB)...
OKAY [ 0.112s]
writing 'bootloader'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.202s[/I]
>[B]mfastboot flash radio radio.img[/B]
[I]target max-sparse-size: 256MB
sending 'radio' (85457 KB)...
OKAY [ 2.753s]
writing 'radio'...
[B](bootloader) Motoboot: Unknown partition name[/B]
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.802s[/I]
>[B]mfastboot.exe flash system system.img_sparsechunk.0[/B]
[I]target max-sparse-size: 256MB
sending 'system' (253363 KB)...
OKAY [ 8.205s]
writing 'system'...
[B](bootloader) Permission denied[/B]
FAILED (remote failure)
finished. total time: 8.226s[/I]
I can't access to recovery. Please, help me :crying::crying::crying:
Why do people relock their bootloader?
With an unlocked bootloader you can flash other region images, if necessary, like Brazil. With locked bootloader your need Mexico. Your may even need your carrier firmware.
ChazzMatt said:
Why do people relock their bootloader?
Click to expand...
Click to collapse
It wasn't my intention. The phone bricked, and in order to return to bootloader I followed that guide. It worked but it seems that during the process it locked the phone.
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
---------- Post added at 03:23 PM ---------- Previous post was at 03:14 PM ----------
See this thread, but you'll need your region firmware.
https://forum.xda-developers.com/showthread.php?t=3662683
ChazzMatt said:
But you went from Marshmallow 6.0.1 back to Lollipop 5.0.2. You can't do that unless you omit gpt.bin in your flash commands. Otherwise you will get bootloop or brick your phone.
I assume at one time you had stock Marshmallow on the phone before trying custom ROMs? Or at the least, probably had flashed Marshmallow radio and bootloader?
With unlocked bootloader you can downgrade back to Lollipop or Kitkat, but you need to omit gpt.bin.
I would also omit recovery.img, to keep TWRP.
Click to expand...
Click to collapse
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
jairjy said:
Yes, as I said. The phone had Stock Marshmallow. I unlocked my bootloader, I tried custom roms, tried TWRP, I even could go back to stock KitKat (by omitting gpt.bin)
The problem came when I accepted to update to OTA Lollipop. The phone bricked; the screen didn't turned on. And while I found a guide that could unbrick the phone, I ended without recovery and with a relocked phone.
Click to expand...
Click to collapse
Because while you had downgraded to Kitkat, but you still had Marshmallow bootloader. You can't take OTA, because it will install bootloader and you cannot downgrade bootloader.
Have we discussed this before, because someone else did EXACTLY the same thing. Downgraded to Kitkat, then tried to take Lollipop OTA --which tries to install Lollipop bootloader!
So for the past week, my phone has been bricked. Bricked by flashing the wrong firmware, so now not able to access the whole phone, and making matters worse by flashing the wrong recovery for the phone. The phone being an Honor 8, FRD-L14, 64GB.
I'm not able to use dload to rollback anything, or use that option at all, since the recovery isn't eRecovery, and doesn't even have any recovery in itself.
The problem is that I'm able to boot into "download mode" my phones unlocked, and when I type in "fastboot oem get-bootinfo", the response is:
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.010s
But when trying to flash anything through fastboot in the cmd, like the command "fastboot flash recovery recovery.img" to flash a recovery on the phone, the response would then be:
target reported max download size of 471859200 bytes
sending 'recovery' (29378 KB)...
OKAY [ 0.803s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.814s
My phone is unlocked, and on the download mode screen, is shows:
PHONE Unlocked
FRP Unlock
My drivers are installed, as well as the device being shown in fastboot when typing in the command "fastboot devices"
I haven't been able to do a single thing to the phone, and have searched up a countless amount of hours to find the fix for the phone, if anyone can, please look into the problem and assist me, thanks .
Kc4k12 said:
So for the past week, my phone has been bricked. Bricked by flashing the wrong firmware, so now not able to access the whole phone, and making matters worse by flashing the wrong recovery for the phone. The phone being an Honor 8, FRD-L14, 64GB.
I'm not able to use dload to rollback anything, or use that option at all, since the recovery isn't eRecovery, and doesn't even have any recovery in itself.
The problem is that I'm able to boot into "download mode" my phones unlocked, and when I type in "fastboot oem get-bootinfo", the response is:
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.010s
But when trying to flash anything through fastboot in the cmd, like the command "fastboot flash recovery recovery.img" to flash a recovery on the phone, the response would then be:
target reported max download size of 471859200 bytes
sending 'recovery' (29378 KB)...
OKAY [ 0.803s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.814s
My phone is unlocked, and on the download mode screen, is shows:
PHONE Unlocked
FRP Unlock
My drivers are installed, as well as the device being shown in fastboot when typing in the command "fastboot devices"
I haven't been able to do a single thing to the phone, and have searched up a countless amount of hours to find the fix for the phone, if anyone can, please look into the problem and assist me, thanks .
Click to expand...
Click to collapse
You're in a tough situation my friend, what do you get when you try the dload method? In my opinion this is the only thing you can do. However i heard about a thing called "DC Unlocker" . It can flash a clean ROM and other good stuff for bricked Huawei phones, but you have to pay, and i don't know what the prices are. Hope you'll make it