Hi,
i bricked my phone (by flashing lineageos16, now in QDL mode). Tried both blankflash files (oreo and NDX) but the logs usually look like:
EDIT: Somehow I managed to blank flash the device (literally tried it a zillion times) and since being genius I flashed the wrong file...
It was the Verizon file and now I'm stuck at the bootscreen saying the device is locked. I can unlock it but the next reboot it's locked again.
I guess, because of it, I'm unable to flash a recovery or a different bootloader (fastboot command always fails). When booting a recovery via fastboot the device shows the 'powered by' logo and nothing happens.
Selecting Qcom from the menu takes me back to the 'Fastboot Flash mode' screen. Tried the restart-edl command, same happens (fb_mode_clear doesn't help).
EDIT2: Talking to myself...
Battery does not load. I was able to flash a different bootloader (from the offical EU image) by changing the partition names inside the XML file (bootloader.image) to <something>_a. After that I flashed the whole image to the phone (again with
changed partition names "<something>_a" in flashall.bat).
Result: The device bootloops (powered by logo) and after some attempts it restores the verizon bootloader.
EDIT3: Still talking to myself...
No chance to flash a firmware without flashing the correct singleboot.img first. Putting the device into edl mode doesn't work (command restricted. edl cable or hotkeys neither work. SBL partitions protected. TP for edl unknown).
Related
As noted Here, and following on, I managed to get updated through to the OTA ICS, and attempted an upgrade to the 3.1 FlexRom.
After some attempts at fixing things, I'm at the point right now, where the issue seems to be in the boot-up sequence.
I have the following variables in play:
* I have fastboot access, but no ADB.
* The tab is now stuck in a continuous loop of the ANDROID boot loader screen.
(previously, it was the FlexRom bootloader)
* The USB at first was trying to install the A500 drivers, and now fails on "MTP USB Device" installation. It fails, but because it's unlocked, I have the first point available.
* CWM no longer loads, nor can I access any recovery functions.
(When CWM was loading, I used it to flash back to the stock OTA rom, rather than attempt another upgrade)
Attempted:
*using fastboot to update the rom via the update command. FAIL.
*using fastboot to run the OEM unlocker. The computer side says "OKAY" but nothing changed on the screen.
*fastboot WILL reboot the tab if given the command, so I know something is getting through, even with the failure of the USB cord to "work"
Have not attempted:
* Hard reset via the little hole. (I honestly don't think it will work)
* Methods I'm not aware of.
So to sum up, I'm stuck in a boot loop and can't get out.
Ideas?
Did you remove bootloader.blob and the recovery folder,from that stock OTA that you flash trough CWM?
I think you are not.That's why you're in this situation.Your bootloader is locked again, and you have the stock recovery (or may be broken recovery).
Try to do hard reset (the real hard reset) with the lock screen button+volume and power (search this forum or google it).It may help you .
Did you try other fastboot commands like: 'fastboot flash recovery recovey.img' or 'fastboot flash boot boot.img' (boot.img and recovery.img must be in the same folder with fastboot to do it this way) what they return?
If above doesn't help you still has a chance with nvflash but you must read this thread after post #48
Hope this is helpful enough!
sending 'recovery' (6144 KB)... FAILED (remote: (00000002))
(for 'fastboot flash recovery recovery.img')
Now it did reboot, and it seems I may be locked again.
This error popped up:
Fastboot: Not support the command in Lock mode
Failed to process command download: hexidecimal error code
No errors on a proper 'hard' reboot, it erased userdata and cache, and is letting me into the setup, so that's probably a good thing.
and indeed it is. I'm back into the OS, and it booted up normally.
I thought I had tried it before, but apparently, it didn't take.
Thanks!
Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance
I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that
Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload
Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.
I have an Asus Zenfone 2 Z00AD (ZE551ML). I tried to unlock the bootloader, which turned out to be a disaster as when the bat file said "All done", I wasn't able to get any input or display from the device. However, my computer was able to "Recognize" it by playing "Device plugged in" sound and then "Device plugged off" sound (I guess the device was still functional?). I tried to un-brick it using the xFSTK download tool and the ASUS Flash Tool, which again yielded the same result being the phone's not responding but still being recognized. I managed to get it into OS (with the boot animation thing) but I noticed that whenever i went to the bootloader and restart into recovery mode, the device shows the "ASUS" logo, then flashes and then it continues to boot into OS, not the recovery. I've tried flashing the recovery through fastboot but that didn't work as well. I don't even know what to do right now. Does anyone here know how to fix it? I need to get the device functional as soon as possible.
Try to flash custom recovery in fastboot mode
(If your bootloader is unlocked)
You have not lost your recovery partition, you only haven’t a recovery image properly installed. You have to flash a recovery (fastboot flash recovery.img) suitable for your os configuration (which is compatible with the boot loader version, divided in Lollipop and Marshmallow).
You can find here the latest TWRP.
Stuck on splash screen "Your device has been unlocked and can't be trusted."
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
gabrce said:
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
Click to expand...
Click to collapse
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
mrmazak said:
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
Click to expand...
Click to collapse
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
gabrce said:
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
Click to expand...
Click to collapse
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
mrmazak said:
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
Click to expand...
Click to collapse
Thank you but "fastboot get prop" is not the right command. If anybody has a solution it will be awesome.
Download the latest full ota package for your device (around 2gb)
Extract the contents of the update. App using huawei firmware extractor and
Flash
kernel
Ramdisk
Recover ramdisk
System and cust images using fastboot
After that flash the correct version of twrp for your device and then install images of version and vendor(found in update. App file) partitions using twrp.
.
This method worked for me
It didn't worked for me... Do you know any other method?
I tried many TWRP versions but the phone doesn't boot into TWRP...
I will explain in detail my final title saying: partition error lol
i was unlocking my bootloader quiet, at the time of reading the partitions (abl_a and abl_b) it said the following error: read data fail:firehose fail:FHloader failrocess fail qfil
I ended up not backing up the partitions (stupidity I know) and proceeded, after carrying out the process of loading the v35.img file into the partitions, I went to do the fasatboot commands, until then everything was normal, I saw that it was unlocked, when I went in in download mode to put the Stock Rom, it was about 3 seconds on the "download mode" icon and the following message appeared: your device has failed a routine safety check and will not boot
stayed a few seconds in this message and restarted to fastboot mode, I tried to start in recovery mode and went to fastboot mode, I turned off and on normally as if to enter android, it gives the warning that the bootloader is unlocked and goes back to fastboot mode...
I went back to EDL mode and, in Qfil, I went to the laf_a and laf_b partitions, after loading, I clicked on the "erase" command on both partitions, I went to download mode and, before the download mode logo appeared, it went straight to fastboot mode
I'm lost, I'm a little layman, I went on the adrenaline rush of installing a custom rom, I already unlocked the bootloader on my friend's phone and it was so much easier and quieter...
I don't want to lose this device, can someone with a good heart help me solve it??
maybe someone would send the abl_a and abl_b files for me to replace and solve, I don't know if it would work, it's just an idea...
model: LG710EMW
Last stock rom installed: G710EMW20a_00_OPEN_SCA_DS_OP_1108.kdz (Android 9)
Sou brasileiro, talvez essas informações ajudem em algo
Try Android 10
zMarkTM said:
I will explain in detail my final title saying: partition error lol
i was unlocking my bootloader quiet, at the time of reading the partitions (abl_a and abl_b) it said the following error: read data fail:firehose fail:FHloader failrocess fail qfil
I ended up not backing up the partitions (stupidity I know) and proceeded, after carrying out the process of loading the v35.img file into the partitions, I went to do the fasatboot commands, until then everything was normal, I saw that it was unlocked, when I went in in download mode to put the Stock Rom, it was about 3 seconds on the "download mode" icon and the following message appeared: your device has failed a routine safety check and will not boot
stayed a few seconds in this message and restarted to fastboot mode, I tried to start in recovery mode and went to fastboot mode, I turned off and on normally as if to enter android, it gives the warning that the bootloader is unlocked and goes back to fastboot mode...
I went back to EDL mode and, in Qfil, I went to the laf_a and laf_b partitions, after loading, I clicked on the "erase" command on both partitions, I went to download mode and, before the download mode logo appeared, it went straight to fastboot mode
I'm lost, I'm a little layman, I went on the adrenaline rush of installing a custom rom, I already unlocked the bootloader on my friend's phone and it was so much easier and quieter...
I don't want to lose this device, can someone with a good heart help me solve it??
maybe someone would send the abl_a and abl_b files for me to replace and solve, I don't know if it would work, it's just an idea...
model: LG710EMW
Last stock rom installed: G710EMW20a_00_OPEN_SCA_DS_OP_1108.kdz (Android 9)
Sou brasileiro, talvez essas informações ajudem em algo
Click to expand...
Click to collapse
I only can get to EDL mode on my phone now. Im working on this process but cant get the right files to extract from the DZ to proceed. Maybe you'll have luck. https://forum.xda-developers.com/t/...ewer-lg-phones-from-edl-or-9008-mode.4213851/