Hey,
I hard bricked my phone (no download mode, no recovery and no fastboot) and then managed to fix it (VIA SRK Tool) and got download mode back.
Now I need to install a recovery, and I cant go and manually check if the TWRP recovery is already installed or not, because if I do go to check and the recovery is not there then the phone will factory reset (and I'll lose all my data).
KDZ Method isn't working, it keeps saying I need to restart my device at 23% (same on two different PCs).
So is there any way of flashing the TWRP recovery through the download mode?
Thanks a lot
(I have a D801, I can get to download mode, factory reset screen and LG logo which then leads to the "Security error" coz there is no firmware in the phone.)
Related
Hi, I just bought an LG G2 D802 20B Model a couple days ago, yesterday I wanted to downgrade to 4.2.2 and I ended up bricking the phone.
The phone is non rooted, doesn't have any custom recovery, and not recognized by adb even though i installed all the drivers ( koush drivers, PdaNet, Lg drivers ...)
At first I flashed with .kdz file and it ended in bootloop, I tried to factory reset but it doesnt have any effects with the stock recovery it only shows the green android bot and blue progress bar and then restart in 3 seconds and reboots to lg logo and start looping.. After a restart the download mode didn't work anymore it showed me fastboot error, I searched for the tutorial that actually worked and I flashed with .tot method but there is still bootloop and the download mode is stuck at the image attached. The phone is not recognized by neither windows or ubuntu therefore I can't use adb to fix the partitions.
Can any body provide me with a solution? The phone is still new and it will be a shame if its transformed to a brick in 3 days :crying:
Hey..hmm i think thats how download mode it is...so did you tried to flash again a firmware?
raulx222 said:
Hey..hmm i think thats how download mode it is...so did you tried to flash again a firmware?
Click to expand...
Click to collapse
Actually the picture attached is stuck and it doesnt change , and the pc can't recognize the phone so I cant flash it with another firmware
BUMP! please help!!
This isn't download mode.
here
only aboot, boot, laf..
bender_007 said:
This isn't download mode.
here
only aboot, boot, laf..
Click to expand...
Click to collapse
Thanks for your reply, however the phone is not recognized on windows neither on ubuntu therefore this tutorial can't help ...
I am in the exact same situation.
Mine is a D802 32GB Hong Kong model. I stupidly ran AutoRec which soft-bricked my phone. Managed to get Download Mode working, then flashed 20C and 20B which bootlooped. Then I attempted to flash 10B, which got me into this exact state:
Download Mode not working (only shows "Download Mode", does not go to firmware recovery screen, not detected in Win/Linux)
Factory reset (Power + Vol Down) can go to factory reset screen, after factory reset, still bootloop.
Once in a while, I also get the Android icon which then disappears after a few seconds and goes to LG logo again.
If I plug the phone in and do a factory reset, Windows detects the LGE AndroidNet modem, and Linux will detect cdc_acm USB Abstract Control Model driver. Flash Tool and LG Mobile Support seems to detect the phone and attempt to flash, but the phone restarts after a short while.
I have no idea what else to do
I installed autorec recovery.as soon as i booted I realized the presence of white lines which have never gone.I cant flash any zip file such as the JDI kernal.It cannot enter into download mode even after erasing recovery, laf, aboot, boot and flashing back stock aboot, boot and laf.I cannot see the LGE port so I cannot tot it back neither does kdz flashing work since it cannot go into download mode.Adb doesn't show up.
What I got is only fastboot + white lines (they only cleared up once by luck so I could see fastboot mode on the phone) .
Please help me Un-Brick it ASAP.look at the questions below.
Thanks
-Should I re-flash all 12 partitions via fastboot (use twrp as recovery).
-It is written d802 on the cover but could the motherboard be different inside?
-Supposing I was to flash 16 GB to a 32 GB phone or vise versa would it affect anything.
-What are my options at this stage and what is the best method to approach this
http://forum.xda-developers.com/lg-g2/general/mega-tut-how-to-fix-bricked-lg-g2-t3055033
Would This Guide Work? I have seen in other guides where they warn about replacing the original recovery but rather suggest you use twrp.
-I think this is a refurbished device.
UPDATE
ok So I managed to fix the white lines and they have completely disappeared which is a plus point.I can finally see download mode for a second before it disappears.I can also go to factory reset mode after holding vol down and power but I have not reset it yet.
Any fix for 1 second download mode?Once I get to download mode i can tot back.
if you have custom recovery try different kernels, wipe, flash bootloader you must be on download mode to revert to stock.
at this point if you cant use the download mode at all, you must try riffbox(search on google)
zhjackss said:
if you have custom recovery try different kernels, wipe, flash bootloader you must be on download mode to revert to stock.
at this point if you cant use the download mode at all, you must try riffbox(search on google)
Click to expand...
Click to collapse
Holy Mother Of.......The RIFFBOX is crazy....i do XBOX 360 modding and i know the difficulty..hehe.....Actually I see download mode for a second and it disappears........which custom recovery can i flash via fastboot, philz or twrp and which ones are the right ones to download.....i am already pissed off at autorec.i feel I am getting close after I cleared up white lines now only fastboot stands in the way.I know many people who mess up and enter bulk mode at this stage and I wanna avoid.I also cant find the right kdz file for my LG cause the imei is a spoofed one that is invalid in the first place so i am hoping for a miracle at this stage.Thanks for the help.......what do you think I can do apart from riffbox?
sohailsameja said:
Holy Mother Of.......The RIFFBOX is crazy....i do XBOX 360 modding and i know the difficulty..hehe.....Actually I see download mode for a second and it disappears........which custom recovery can i flash via fastboot, philz or twrp and which ones are the right ones to download.....i am already pissed off at autorec.i feel I am getting close after I cleared up white lines now only fastboot stands in the way.I know many people who mess up and enter bulk mode at this stage and I wanna avoid.I also cant find the right kdz file for my LG cause the imei is a spoofed one that is invalid in the first place so i am hoping for a miracle at this stage.Thanks for the help.......what do you think I can do apart from riffbox?
Click to expand...
Click to collapse
Just try everything you see on xda. I never faced a 1 sec download mode before and believe me i bricked(hard/soft and beyond) many times and came back, it aint die. Once download mode is broke there must something really not working. In other saying you need to revert to stock. Also, if you dont have custom recovery i also dont believe you can flash a custom recovery, you could try adb push laf.img recovery.img aboot.img etc. But its going be hard bricked.
Man i was thinking i faced every difficulty with d802 but you proved me wrong :laugh:
I pushed the three files that's when the white lines cleared up and download mode came for a second....there is a similar case on Android forums where they download mode comes for a second. The worst part is the IMEI was patched to a very u usual IMEI on the back cover, it's not even an LG imei so i can't find the write kdz file to extract partitions from....I have to rely on trial and error......at this stage I don't wanna enter qhsusb mode aka hard brick...... I just have to revive download mode.......actually when I attempt to boot laf. IMG I get a dtb error ?any thing I can try
So I just wanna confirm this. if i flash any custom recovery say cwm (of course for lg g2 d802) via fastboot mode using the command fastboot flash recovery recovery.img will it actually install the recovery or what.and then to enter recovery i have to essentially hard reset (vol down + power ) so as to enter recovery.now if there is no recovery it will hard reset and i will enter qhsusb mode which i dont want.So does flashing a recovery image via fastboot install the recovery or what.Please assist.
sohailsameja said:
ok So I managed to fix the white lines and they have completely disappeared which is a plus point.I can finally see download mode for a second before it disappears.I can also go to factory reset mode after holding vol down and power but I have not reset it yet.
Any fix for 1 second download mode?Once I get to download mode i can tot back.
Click to expand...
Click to collapse
How were you able to fix the white lines issue @sohailsameja?
Hey,
I hard bricked my phone, the one where you connect to the PC 15 or so drives open up (no download mode, no recovery and no fastboot) and then managed to fix it (VIA SRK Tool which flashed a stock recovery instead of a custom one) and got download mode back.
KDZ Method isn't working, it keeps saying I need to restart my device 2%.
So is there any way of flashing the TWRP recovery through the download mode or at the very least any way to extract my data (only a few folders) through the download mode?
I don't know why but no one seems to notice this thread
Thanks a lot, any help will be much appreciated.
PS: Please ask if any further information is required
(I have a D801, I can get to download mode, factory reset screen and LG logo which then leads to the "Security error" coz there is no firmware in the phone.)
So, I did brick my D802 in some way.
After a long history from cloudy g2-g3, rr, cm12, cm13, lineage 14.1, I clicked by mistake on the OTA of the lineage.
I thought I could stop the update once in the recovery, but I got stucked in the recovery bootloop. I got rid of it via recovery terminal, but system didn't boot. I tried reflashing lineage, nothing happened, I tried restoring a cm13 full backup, nothing happened, so I got back in download mode to restock with lollipop kdz (the one I used every time I restocked to change rom). It did not work, and I had to download a different KDZ to get to stock again.
Now, all the methods always used to root + recovery didn't work, so I manually rooted, installed the proper AUTOREC, but it didn't work (as I understand after hours of searching because supersu had updated himself in the meantime).
So I tried to install the TWRP image using flashify, it didn't work and corrupted something in my recovery. So i tried to unroot everything and reinstall the original root + supersu without letting him autoupdate. Not working.
Well, now I can boot and I can get in original lollipop rom, but I have no recovery and download mode appears but doesn't work anymore (once I had 3 COM ports when connected in download mode, now I can see only one; kdz flash does not sense the phone connected). When I try to open recovery I got the error "boot certification verify, secureboot error" in the top left corner of the screen, then a white page opens with the message "critical error" "demigod crash handler", volume up to download mode (that opens but does not work), volume down to reboot.
Now, I am stucked, I cannot find any suggestion of what to do to get the recovery working or to get the download mode working again.
Any help will be highly appreciated.
Thank you very much guys.
Not sure will it help but you may give it a try:
https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Drunkenmazter said:
Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Click to expand...
Click to collapse
Use one of the less archaic methods:
Download "EDL Tool" from the ROMs, kernels, development section, along with an EDL package that goes with your phone model. Put your phone in EDL and just flash it with that tool. after that, if it still doesn't boot you have to format data, because you might have conflicting data. If you can't do it from EDL Tool (i think you can, don't remember) just enter the recovery with Vol+ and Power and make a factory reset
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
From some other threads, I believe you could try to EDL flash Nougat instead of Oreo, it would work better.
https://forum.xda-developers.com/axon-7/help/help-edl-factory-restore-stuck-device-t4031619
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
xperiaatic said:
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
Click to expand...
Click to collapse
According to other threads, the problem could be due to "sparse" structure while flashing.
I suggest the following:
- Use Axon 7 EDL toolkit to flash latest official TWRP recovery (for Oreo a specific TWRP would be requied).
- Inside TWRP then wipe data/factory reset and at the utmost Format data. Then retry to boot.
- If not OK, reflash with EDL full ROM and try again.
Already done that for several times with O ja N EDL rom's but no luck. Can't get to recovery nor make system to boot.
Did you successful unlocked bootloader?
If not, I would recommended Axon 7 EDL Tool by djkuz, flashing nougat edl package and unlock it through the options.
Can you get into stock recovery after flashing EDL package? It supposed to have a format option for userdata and cache.
Did you try to get into fastboot mode? Power + Vol up buttons if i'm not wrong.
If so, you could try to format these partitions.
fastboot erase /cache
fastboot erase /data
I have experienced the same problem but I have resolved flashing, with Xiaomi MiFlash (sometimes I use this program because occasionally flashing EDL packages with AxonEDLTool, it gives me problems like this) this package Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL.
With this EDL, if the flash is successful, you will find NFound recovery 3.2.1-7 installed with which you can make a complete wipe and / or format them with the file system you prefer.
Afterwards, using MiFlash or EDLTool at your discretion, you can flash the EDL of the original system if you prefer.
I'm not an expert but this has solved my problem.
To unlock the bootloader, if the unlocking with EDLTool does not go well (it happened to me just yesterday while I was installing a Rom on another Axon 7), you can use Axon7ToolKit 1.2.1, it always worked well for me.
I hope it can help :fingers-crossed:.
xperiaatic said:
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
Click to expand...
Click to collapse
Hi, just want to let here my solution for the same problem, it may help others.
I tried to flash A2017G_B10_NOUGAT_FULL_EDL and A2017G_B02_OREO_FULL_EDL but always getting the Can't mount /cache/recovery/last_locale error, phone completely bricked.
So I flashed A2017_B13_FULL_EDL_UNBRICK_DFU using MiFlash through EDL, you can find this here: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 (if your EDL mode works fine there is no need to disassemble the phone as shown in that tutorial)
Now the phone is completely working, recovery and system, but everything in chinese.
Then I flashed A2017G_B02_OREO_FULL_EDL using MiFlash through EDL, and now everything is working and in english
Thanks a lot for the tip! A2017_B13_FULL_EDL_UNBRICK_DFU did the trick and unbrick the phone.
What i did:
1. used MiFlash to flash A2017_B13_FULL_EDL_UNBRICK_DFU
2. after that A2017G_B03_OREO_FULL_EDL
3. reboot to recovery and performed factory reset
First time I did not perform the factory reset and got stuck on the boot picture without the reset function (power button did not work). Drained the battery and performed factory reset and got the phone working again.
update:
Phone is not stable on B03, some apps crashing from time to time for no apparent reason and also soft reboots happening randomly.
Now I got stuck on the Axon boot screen again after rebooting the phone manually and waiting for the battery to drain ...
i did not install or perform any custom action to the system, just regular use and apps, but it is still acting up badly.
I was planning to use this phone as a secondary handset because it is actually a very nice piece of hardware but now i am starting to have second thoughts about that.