I have a bricked device. I think I accidentally flashed boot into abl_a using QFIL.
My device is stuck on the bootloader. I can only access the phone using fastboot command and with EDL mode controlled with QFIL. I tried going to recovery mode and it shows "Your device cannon be checked for corruption" with a yellow warning then reboots into bootloader again. Then I tried accessing download mode using "Power off-Hold vol up-Connect USB" technique and it shows "Your device has failed a routine safety check and will not boot" and reboots back to bootloader. I have my .kdz stock firmware but LGUP won't detect my device since I can't go to download mode.
I have tried these steps:
Booting TWRP using "fastboot boot twrp.img" Output: Failed to load/authenticate error.
Booting TWRP using "fastboot flash boot twrp.img" Output: OK but nothing happened.
Flashing TWRP using "fastboot flash recovery twrp.img" Output: recovery_a no such partitions error.
Flashing ABL V35 Bootloader using "fastboot flash abl abl_35.img" Output: OK but nothing happened.
Booting .kdz file using LGUP but LGUP doesn't detect any device in COM ports though it works using fastboot and adb before.
Downloading the full backup stock ROM and flashing the XML into the phone using QFIL. Output: Fail Firehose and Fail Sahara Error.
Any kind of help would be appreciated.
Many thanks.
Maple06 said:
I have a bricked device. I think I accidentally flashed boot into abl_a using QFIL.
My device is stuck on the bootloader. I can only access the phone using fastboot command and with EDL mode controlled with QFIL. I tried going to recovery mode and it shows "Your device cannon be checked for corruption" with a yellow warning then reboots into bootloader again. Then I tried accessing download mode using "Power off-Hold vol up-Connect USB" technique and it shows "Your device has failed a routine safety check and will not boot" and reboots back to bootloader. I have my .kdz stock firmware but LGUP won't detect my device since I can't go to download mode.
I have tried these steps:
Booting TWRP using "fastboot boot twrp.img" Output: Failed to load/authenticate error.
Booting TWRP using "fastboot flash boot twrp.img" Output: OK but nothing happened.
Flashing TWRP using "fastboot flash recovery twrp.img" Output: recovery_a no such partitions error.
Flashing ABL V35 Bootloader using "fastboot flash abl abl_35.img" Output: OK but nothing happened.
Booting .kdz file using LGUP but LGUP doesn't detect any device in COM ports though it works using fastboot and adb before.
Downloading the full backup stock ROM and flashing the XML into the phone using QFIL. Output: Fail Firehose and Fail Sahara Error.
Any kind of help would be appreciated.
Many thanks.
Click to expand...
Click to collapse
you need to get lgup working again with the device, for that I believe you need abl, laf, boot and dtbo. so get those from the kdz and flash using qfil, then you should be able to go directly to download (lgup) mode and flash kdz.
AsItLies said:
you need to get lgup working again with the device, for that I believe you need abl, laf, boot and dtbo. so get those from the kdz and flash using qfil, then you should be able to go directly to download (lgup) mode and flash kdz.
Click to expand...
Click to collapse
Hi, thanks for the reply,
I just extracted my .kdz file using LG Firmware Extract but I don't seem to find any abl, laf, boot, nor dtbo img files. I only got LGUPc.dll, LGUPc.dylib, and V409N30f00user-signed-ARB0OPE with no file extension. I tried extracting only the file with no file extension but I'm not sure what to do with the file.
Many thanks.
Maple06 said:
Hi, thanks for the reply,
I just extracted my .kdz file using LG Firmware Extract but I don't seem to find any abl, laf, boot, nor dtbo img files. I only got LGUPc.dll, LGUPc.dylib, and V409N30f00user-signed-ARB0OPE with no file extension. I tried extracting only the file with no file extension but I'm not sure what to do with the file.
Many thanks.
Click to expand...
Click to collapse
Follow this link. They are for kor 20n, so be sure once you flash with qfil, go directly to DL mode, don't try to boot the device. Follow directions in Notes.
Also, it would be wise to save off whats in those partitions first, even though it won't boot. At least that way, if you absolutely had to, you could get back to where you are now.
cheers
AsItLies said:
Follow this link. They are for kor 20n, so be sure once you flash with qfil, go directly to DL mode, don't try to boot the device. Follow directions in Notes.
Also, it would be wise to save off whats in those partitions first, even though it won't boot. At least that way, if you absolutely had to, you could get back to where you are now.
cheers
Click to expand...
Click to collapse
I just finished flashing those files, then I tried going to download mode, it gave me the yellow warning and boots back to the bootloader. I don't see many changes except when I start there is no yellow warning appearing, only when I try to go to recovery mode it still shows the yellow warning. Maybe there is something I did wrong?
Edit: I tried going to DL mode again and it actually goes to DL mode for 1 second and goes back to bootloader.
Thanks in advance.
Maple06 said:
I just finished flashing those files, then I tried going to download mode, it gave me the yellow warning and boots back to the bootloader. I don't see many changes except when I start there is no yellow warning appearing, only when I try to go to recovery mode it still shows the yellow warning. Maybe there is something I did wrong?
Edit: I tried going to DL mode again and it actually goes to DL mode for 1 second and goes back to bootloader.
Thanks in advance.
Click to expand...
Click to collapse
did you flash all four files to both slots? as notes indicate?
remember, after flashing in qfil, we need to hold both pwr and vol down to get out of edl mode. Once you hear the windows chime, indicating the device is disconnected, immediately let go of pwr and vol dwn and just hold vol up. Keep device connected with usb cable. Also be sure to use a usb 2 port, not usb 3. A usb 3 port can result in corrupted files as it's too fast for old qfil sftwre.
AsItLies said:
did you flash all four files to both slots? as notes indicate?
remember, after flashing in qfil, we need to hold both pwr and vol down to get out of edl mode. Once you hear the windows chime, indicating the device is disconnected, immediately let go of pwr and vol dwn and just hold vol up. Keep device connected with usb cable. Also be sure to use a usb 2 port, not usb 3. A usb 3 port can result in corrupted files as it's too fast for old qfil sftwre.
Click to expand...
Click to collapse
I just reflashed all of them and enter the download mode and it works! Now I can access LGUP and when I try to start flashing my .kdz file it failed but I'm now trying redownloading the .kdz file with KDZ downloader. Just in case that .kdz really need a special download. I'll update when my .kdz is finished downloaded and if the flash is successful or not. In the meantime, do you have any sources for the LG V40 LM-V409N .kdz file version? It'll be very useful in case this file failed.
Thank you very much
Hi, I am here with the update.
So I managed to download the .kdz file for the LM-V409N it rebooted and booted for a minute and it restarted then looped from "erasing" rainbow circle then goes to back stuck on LG with a light animation until I hold the power button and it rebooted back to the rainbow erasing circle. So I just put and redo everything and now I got it back on download mode.
I think that I just have a bad/corrupted .kdz file. Do you have a suggestion on where should I find the files? I tried from lg-roms but it's bad firmware. I'll try more firmware for KOR, LGT, and SKT.
Edit: Hmm, I seem to be stuck on either the LG or LGU+ symbol, I'm not sure what to do.
Edit: Apparently, my phone still got the issue that it restarts randomly. I have no idea how to fix it now since the issue still persists after several different phone stock ROM.
Many thanks.
Maple06 said:
Hi, I am here with the update.
So I managed to download the .kdz file for the LM-V409N it rebooted and booted for a minute and it restarted then looped from "erasing" rainbow circle then goes to back stuck on LG with a light animation until I hold the power button and it rebooted back to the rainbow erasing circle. So I just put and redo everything and now I got it back on download mode.
I think that I just have a bad/corrupted .kdz file. Do you have a suggestion on where should I find the files? I tried from lg-roms but it's bad firmware. I'll try more firmware for KOR, LGT, and SKT.
Edit: Hmm, I seem to be stuck on either the LG or LGU+ symbol, I'm not sure what to do,
Many thanks.
Click to expand...
Click to collapse
I'd suggest to get them here: https://lg-firmwares.com/lg-lmv409n-firmwares/
It's important to the md5 checksum to match against the hash they give you when you select a specific kdz. Then you know it's not corrupt.
after unbrick how to get IMEI? I have no backup. using V409N korean model.
AsItLies said:
I'd suggest to get them here: https://lg-firmwares.com/lg-lmv409n-firmwares/
It's important to the md5 checksum to match against the hash they give you when you select a specific kdz. Then you know it's not corrupt.
Click to expand...
Click to collapse
Thank you for your answer. It would've been working now if I didn't get unlucky on the device. You're really helpful to help from my hard-bricked phone into firmware booted.
Again, thank you very much
irfan64672 said:
after unbrick how to get IMEI? I have no backup. using V409N korean model.
Click to expand...
Click to collapse
If you unbricked your device with the stock firmware, just go to telephone and call *#06# and you got your imei. Best to backup your firmware with QFIL.
Related
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!
Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery
Code:
adb reboot recovery
. When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat
Which twrp you flashed? Check the correct twrp in my signature for honor 5C repository.
TassiloBalbo said:
Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery . When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat
Click to expand...
Click to collapse
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot
hassanjavaid8181 said:
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot
Click to expand...
Click to collapse
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Meaning you can boot to fastboot but your pc doesn't recognise it?
Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Did you try all method to going in fastboot.by adb fastboot command or by pressing vol- and power button?
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Glad that you fix your device.
If it is not bothering you let it be and enjoy using your phone.
Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.
TassiloBalbo said:
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.
Click to expand...
Click to collapse
Try removing the usb cable and then try to biot to fastboot. What about erecovery
shashank1320 said:
Try removing the usb cable and then try to biot to fastboot. What about erecovery
Click to expand...
Click to collapse
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.
TassiloBalbo said:
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.
Click to expand...
Click to collapse
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press
shashank1320 said:
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press
Click to expand...
Click to collapse
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]
TassiloBalbo said:
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]
Click to expand...
Click to collapse
Meaning the fastboot is accessible.
Now you have firmware zip, extract it amd you will get few files. Use dload method as given in my signature and you are good to go.
Else use Huawei extractor and browse to update.app you just got in above downloaded zip. You will get boot, recovery, system img you need.
I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery
TassiloBalbo said:
I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery
Click to expand...
Click to collapse
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you
shashank1320 said:
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you
Click to expand...
Click to collapse
NEM-L31 but I don't know the build number
TassiloBalbo said:
NEM-L31 but I don't know the build number
Click to expand...
Click to collapse
Build number is necessary to get right files..
hassanjavaid8181 said:
Build number is necessary to get right files..
Click to expand...
Click to collapse
I know. So do you think it's dead?
TassiloBalbo said:
I know. So do you think it's dead?
Click to expand...
Click to collapse
You should try huawei service center....
Ok so I was going about Trying to flash TWRP it wouldnt go. Tried a few times etc, nothing, so i gave up.
Now when i reboot or turn off and power up, i get a N/A in the top corner for a few seconds but then it boots up fine. But i cannot do a backup & reset, and i cant get into recovery now.
I get a start up failed your devices didnt start up successfully use the software repair assiant on your computer,
bottom says ap fastboot flashmode secure
error: failed to load kernel
fastboot reason: fall-through from recovery boot mode
but i can toggle to Start and it boots fine.
Computer now does not see the phone when i plug it in, it dont make a sound and is not in the device manager, also when i reboot to fastboot, it still isnt seen at all. flashing_unlocked so i can flash. but cant use adb since pc wont reconize phone now, and i cant reset.
So i can use the phone like normal atleast, but cant reset or access recovery. its like it just inst there
any ideas???
Thanks
Ok so the computer don't even ding when ya plug the phone I to it. On any computer I use. Is there a corrupted file that the phone uses when connecting to a computer... ?
Phone works fine.. just recovery is missing.. and with no way use to use adb... Is there any way to get the recovery back on?
Jtaxel said:
Ok so the computer don't even ding when ya plug the phone I to it. On any computer I use. Is there a corrupted file that the phone uses when connecting to a computer... ?
Phone works fine.. just recovery is missing.. and with no way use to use adb... Is there any way to get the recovery back on?
Click to expand...
Click to collapse
It would help to know what model your device is for one thing. Also, what command exactly did you use to flash the recovery? It almost sounds like you flashed the recovery to the wrong place or you did the erase command before trying to flash and borked the recovery partition.
ok,
Moto e4 plus, andrid 7.1.1
I did unlock the boot loader.
Security Patch - July 1 2018
Owens
xt1775
The TWRP on this site from git hub was only a zip file not in .img format, so i went TWRP official site and downloaded the one for the moto e4 plus
Put all files where they supposed to. did the adb,
first typed fastboot flash recovery.img that didnt work nothing at all, then did the right way,
fastboot flash recovery recovery.img, didnt work it was able to boot to recovery from adb, but not flash it.
tried a few times, no go, so after that, wheni reboot my phone, it goes straight to the bootloader screen and and says,
start up failed
your device didnt start up successfully use the software repair assisant on your omputer to repair your device.
ap fastboot mode ( secure)
error failed to load kernel!
fastbootReason: Fa;;-through from recovery boot mode
i can arrow down to start and it will start fine ( boot phone up normally )just goes to the n/a in top left for about 10 seconds then starts up normal. But i can NOW adb into my phone again and its reconized by the computer.
did i flash the wrong twrp?
Thanks
switch tools mode
ap fastboot mode (secure)
flashing_unlocked
gives cou emmc dram all that info also
Jtaxel said:
ok,
Moto e4 plus, andrid 7.1.1
I did unlock the boot loader.
Security Patch - July 1 2018
Owens
xt1775
The TWRP on this site from git hub was only a zip file not in .img format, so i went TWRP official site and downloaded the one for the moto e4 plus
Put all files where they supposed to. did the adb,
first typed fastboot flash recovery.img that didnt work nothing at all, then did the right way,
fastboot flash recovery recovery.img, didnt work it was able to boot to recovery from adb, but not flash it.
tried a few times, no go, so after that, wheni reboot my phone, it goes straight to the bootloader screen and and says,
start up failed
your device didnt start up successfully use the software repair assisant on your omputer to repair your device.
ap fastboot mode ( secure)
error failed to load kernel!
fastbootReason: Fa;;-through from recovery boot mode
i can arrow down to start and it will start fine ( boot phone up normally )just goes to the n/a in top left for about 10 seconds then starts up normal. But i can NOW adb into my phone again and its reconized by the computer.
did i flash the wrong twrp?
Thanks
switch tools mode
ap fastboot mode (secure)
flashing_unlocked
gives cou emmc dram all that info also
Click to expand...
Click to collapse
Try this twrp. It should work fine. Change the name to recovery.img and flash it
https://github.com/TwrpBuilder/andr...s/tag/TWRP-3.2.3-TwrpBuilder-2018-08-21_14-10
Jtaxel said:
The TWRP on this site from git hub was only a zip file not in .img format,
Click to expand...
Click to collapse
You unzip to extract the img file.
ST Dog said:
You unzip to extract the img file.
Click to expand...
Click to collapse
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Jtaxel said:
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Click to expand...
Click to collapse
That is the source not the image. Click on the link that ends with .img not .tar and you'll get an img
now if i try to fastboot boot recovery.img it boots to recovery but hangs on the recovery loading twrp screen.
and this error in adb now with any code i send
Jtaxel said:
now if i try to fastboot boot recovery.img it boots to recovery but hangs on the recovery loading twrp screen.
and this error in adb now with any code i send
Click to expand...
Click to collapse
You need to type in fastboot flash not fastboot boot. Boot will only "boot" the recovery but won't flash it onto your phone.
Jason M. said:
You need to type in fastboot flash not fastboot boot. Boot will only "boot" the recovery but won't flash it onto your phone.
Click to expand...
Click to collapse
yep i know, first time i tried this, it would boot when i type boot. BUT when i tried to FLASH it, it wouldnt flash and stay.
Now i cant even boot TWRP, just hangs on the TWRP logo screen. I let it sit for 5 mins, before it ould only take a few seconds.
BUT i am using the one from the offical site, not the one on github thats only a zip file.
unless someone has the img file from github.
BUT STILL like i said i get that error you see in CMD screenshot.
Jtaxel said:
yep i know, first time i tried this, it would boot when i type boot. BUT when i tried to FLASH it, it wouldnt flash and stay.
Now i cant even boot TWRP, just hangs on the TWRP logo screen. I let it sit for 5 mins, before it ould only take a few seconds.
BUT i am using the one from the offical site, not the one on github thats only a zip file.
unless someone has the img file from github.
BUT STILL like i said i get that error you see in CMD screenshot.
Click to expand...
Click to collapse
First of all that error is normal. Second, the img is right there on the page I posted the link to. I even posted a screenshot of me downloading it from there. I don't see any reason why I could download the img and you can't. I give up.
OK, sorry didnt see the link. I downloaded that, i flashed it. IT worked. But now when i reboot it goes straight to recovery. But i reboot to bootloader and start that way, no big deal.
Never seen those errors before, but yea it worked now, must have been the wrong TWRP. Works now. THank you
But whats the default password in TWRP
Jtaxel said:
OK, sorry didnt see the link. I downloaded that, i flashed it. IT worked. But now when i reboot it goes straight to recovery. But i reboot to bootloader and start that way, no big deal.
Never seen those errors before, but yea it worked now, must have been the wrong TWRP. Works now. THank you
But whats the default password in TWRP
Click to expand...
Click to collapse
Np. That's why we have a thanks button though. To fix your booting problem you can try connecting your phone to your PC and booting to the bootloader and run this command with fastboot:
fastboot oem fb_mode_clear
That should do it.
Jason M. said:
Np. That's why we have a thanks button though. To fix your booting problem you can try connecting your phone to your PC and booting to the bootloader and run this command with fastboot:
fastboot oem fb_mode_clear
That should do it.
Click to expand...
Click to collapse
tried a couple times, no go, thats ok tho.
But i cant flash nothing because its asking for a password to mount.
Jtaxel said:
tried a couple times, no go, thats ok tho.
But i cant flash nothing because its asking for a password to mount.
Click to expand...
Click to collapse
Ok, try:
fastboot erase DDR
That should solve your booting problem. I knew it was one or the other. Ignore the twrp asking for password and click on the mount settings and you'll see a little check box that says "mount system read only". Uncheck that box
password fixed, i flashed the no verify and super, and it wiped my phone, is that normal, just wondering ,
yes i made a backup
Jtaxel said:
password fixed, i flashed the no verify and super, and it wiped my phone, is that normal, just wondering ,
yes i made a backup
Click to expand...
Click to collapse
If you flashed the force encrypt noverity zip yes. If you don't want enryption or want it to be optional to encrypt use the one that says opt encrypt. This is all gone over possibly hundreds of times in numerous threads. You should do a little searching and reading.
Jtaxel said:
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Click to expand...
Click to collapse
My bad. Often a .img file is zipped because .img gets treated as a picture.
And you can also extract .img files from flashable zip releases.
Didn't think you might have grabbed a source code zip.
Hi,
Sequence of steps:
1. Extracted the boot.img from payload.bin and flashed it to the phone. At this point I was able to get into Fastboot
2. While in Fastboot I went into advanced and wiped the "System Settings", and that's when the trouble started - now the phone is stuck into a boot loop forever, I do however get the options to "Power Off" and "Restart"
3. But none of the options above in Step 2 is able to bring me back to Fastboot (and hence into fastbootd either)
Question: How can I get the phone into Fastboot Mode - have tried MSM Tool v4 as well, but that doesn't even recognize the phone
Edit - This seems to have been resolved now, think I had to press Vol Down + Power instead of Vol Up + Power
Was able to enter into Fastbootd as well, will try to proceed with unbricking the phone with a fresh mind tomorrow
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
VoltaGe86 said:
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
Click to expand...
Click to collapse
Thats right, "fastboot boot <file_name>" loads temporarily your custom recovery of choice. After rebooting your phone, the custome recovery is gone.
Otherwise, the command "fastboot flash <file_name> recovery" flashs permamently your custom recovery of choice to your device.
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Zekedw said:
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Click to expand...
Click to collapse
I have exactly the same issue, on a nord 2
How about vol+/vol-&power all together? When stuck that gives me some screen that allows start, recovery (the one where you can enter advanced settings I expect from your description) and bootloader booting.
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
protatocrisp said:
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
Click to expand...
Click to collapse
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
AsItLies said:
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
Click to expand...
Click to collapse
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
protatocrisp said:
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
Click to expand...
Click to collapse
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
AsItLies said:
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
Click to expand...
Click to collapse
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
protatocrisp said:
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
Click to expand...
Click to collapse
well if there's a lesson here it's that it's exceptionally important to pay attention to exactly what you're doing. Double check everything; that you're flashing the correct files, that you back up the correct files and name them appropriately, read directions over and over to be sure u understand.
it sounds like if you keep going back to fastboot when trying to start system, then you're probably re-flashing the engineering abl and not the original abl, which yer suppose to save off first.
yeah, maybe start over again by flashing a stock rom.