Hello I hope someone could help me.
I have an lg g3 D855 international version, with kit kat 4.4.2 and its the 10e version.
I've root my device in order to install new custom rooms. At first I wanted to go to android marshmallow official and wanted to do the flashing with lg flash tool, but in every computer I have, it does not working, its either stuck in 2% and then it fails, or 4% and then it fails, and I tried to erase an install the new drivers and the old ones in the computer... But I couldn't get it to work. So I decided to root my device, and install twrp recovery, so I did. First I try to install the latest version of twrp, this I did it directly from the phone via TWRP manager. It was supose to work... But when I finish installing and went to recovery.. It went to a black screen saying "[700] fastboot mode started" or sometimes "[760] fastboot mode started" to my surprise the phone is not softbrick. I removed the battery and then reboot the phone and it works... But everytime I go to recovery or tried to install a new bump recovery... Because i thought that was the problem is still the same. I tried to install a new recovery with ADB but when I put the file path in order to install it... It said it couldn't find the recovery img in the path... But it was there... And I tried, but couldn't get it to work. I have some experience with custom roms on samsung galaxy s3, but change my phone, and this lg g3 is really making me crazy.
Thank you very much in advanced.
Any updates? Im having the same exact problem (d851)
In which computer you are trying the process. Which windows is installed on computer that you are using for installing stock rom.
Which guide you are following to install stock rom. Have you unlocked your device for bump, if not follow the guide.
http://forum.xda-developers.com/lg-g3/orig-development/bump-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
I am dead sure that your board is not d855.open your phone to confirm this.that is the reason your twrp is not compatible with your board.
droidrzr1610 said:
Any updates? Im having the same exact problem (d851)
Click to expand...
Click to collapse
Same problem for me.
I was using TWRP for weekly update of LineageOS 16.1 on D855 with no problem.
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App.
Then I tried to boot in Recovery mode and I got black screen with the message:
[700] fastboot mode started
I tried older version with no success installing them with ADB or TWRP App.
---------- Post added at 06:55 AM ---------- Previous post was at 06:32 AM ----------
Polex73 said:
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App..
Click to expand...
Click to collapse
I noticed the twrp-3.4.0-0-d855.img file was corrupted.
I downloaded from the https://eu.dl.twrp.me/d855/ directly to the phonr.
Problem solved
Related
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
uppon2 said:
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48205695&postcount=13
atifsh said:
http://forum.xda-developers.com/showpost.php?p=48205695&postcount=13
Click to expand...
Click to collapse
Thank you, I will use that if I ever get LG Tool to stop throwing me the low battery warning. What a stupid program to not give you the option to bypass it. Surely there is a way I can do this. My battery is at 99%. I just flashing madmack hacked and lockified recovery and now I can't even get in to recovery to do sideloads. I am running out of options, my only way is to get LG Tool or B2C to work
EDIT* I have recovery back. GRR why is this stupid message about low battery keep popping up
uppon2 said:
Thank you, I will use that if I ever get LG Tool to stop throwing me the low battery warning. What a stupid program to not give you the option to bypass it. Surely there is a way I can do this. My battery is at 99%. I just flashing madmack hacked and lockified recovery and now I can't even get in to recovery to do sideloads. I am running out of options, my only way is to get LG Tool or B2C to work
EDIT* I have recovery back. GRR why is this stupid message about low battery keep popping up
Click to expand...
Click to collapse
have not tested this from cm rom but works from any stock. bytheway i have optimus G not pro
from recovery adb push rom.zip (your rom)
adb push rom.zip /sdcard/0
(0 required for cwm and cm10.2)
flash that rom
enable debugging
run lgflash tool one that supports large files or the online one it will pass the battery and auto restart in download mode there it will give error just unplug replug and retry and it will be flashed this time.
atifsh said:
have not tested this from cm rom but works from any stock. bytheway i have optimus G not pro
from recovery adb push rom.zip (your rom)
adb push rom.zip /sdcard/0
(0 required for cwm and cm10.2)
flash that rom
enable debugging
run lgflash tool one that supports large files or the online one it will pass the battery and auto restart in download mode there it will give error just unplug replug and retry and it will be flashed this time.
Click to expand...
Click to collapse
I am unsure what this is but I am interested? Thanks, I ended up doing what I was trying to do in the first place and IT WORKED
To anybody that faces the same issue:
in recovery sideload install madmacks TWRP file attached below
after that is installed flash CM11 using the same sideload
The command in adb is adb sideload (your file name in here without the brackets.zip) You must include .zip
It is strange because it didn't work the first 3 times I flashed the ROM and on the fourth it worked, so keep trying
i can fix bootloop to cwm or recovery just 2 minutes. but u have to backup your stock recovery fírst before install cwm or twrp.
so thiss step to solve after u have boot loop. that u need to restore back your stock recovery on mmcblk0p28 then reboot. you will stuck at factory software repair. keep ur fone connected with the computer and type adb reboot. then u can boot into android os. and final step. u reinstall your custom recovery again and Enjoy. this fixing not for newbie and im typing it on my fone. someone can make automation script to help People solve it im lazy
Sent from my Optimus G Pro using Tapatalk
thaiminhan said:
i can fix bootloop to cwm or recovery just 2 minutes. but u have to backup your stock recovery fírst before install cwm or twrp.
so thiss step to solve after u have boot loop. that u need to restore back your stock recovery on mmcblk0p28 then reboot. you will stuck at factory software repair. keep ur fone connected with the computer and type adb reboot. then u can boot into android os. and final step. u reinstall your custom recovery again and Enjoy. this fixing not for newbie and im typing it on my fone. someone can make automation script to help People solve it im lazy
Sent from my Optimus G Pro using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help. I am not running stock and can not get a stock ROM to work (with locked bootloader obviously)
LG Tool is requesting for a TOT file which the E988 doesn't have, I have tried using E98810D_00.kdz file in the software field but it is not recognising the cab file. The DLL file is recognised but I don't know what else to do from there.
LG Mobile Support Tool keeps failing on me due to low battery error which as you can see, I have been trying my hardest to get it to work. Battery is at 99% but it still won't flash! - I am stuch with a custom ROM and a dodgy unlocked bootloader due to the latest release FreeGee.
I tried the old file you attached but it fails to download the image file to unlock my bootloaders, I guess because it is already unlocked.
What I need now is to find a way to relock my bootloader that doesn't involve LG Tool/LG Mobile Tool and then try the old FreeGee app again. Or I find a way to get passed this stupid battery warning
uppon2 said:
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
Click to expand...
Click to collapse
i have same problem with you, anyone have solution??
kuwir said:
i have same problem with you, anyone have solution??
Click to expand...
Click to collapse
Check this
http://forum.xda-developers.com/showthread.php?p=48225776
Sent from my LG-E980 using XDA Premium HD app
kuwir said:
i have same problem with you, anyone have solution??
Click to expand...
Click to collapse
First try to use LG Mobile Tool. All files and instructions found here CLICK ME
If that doesn't work the follow the instructions I posted earlier and it will get your phone booting again. As for getting back to stock and unlocking the bootloaders without causing kernel issues, I am still waiting for a response from Seth. He has been making a lot of changing as this is a known problem. The latest version is supposed to work like it used to now.
uppon2 said:
I am unsure what this is but I am interested? Thanks, I ended up doing what I was trying to do in the first place and IT WORKED
To anybody that faces the same issue:
in recovery sideload install madmacks TWRP file attached below
after that is installed flash CM11 using the same sideload
The command in adb is adb sideload (your file name in here without the brackets.zip) You must include .zip
It is strange because it didn't work the first 3 times I flashed the ROM and on the fourth it worked, so keep trying
Click to expand...
Click to collapse
Thanks! This worked 100%. Something's really up with the freegee CWM, totally useless. Had 3 days of a headache till I saw this post. I used to be a CWM guy, now TWRP all the way...! The interface is touch based and much easier to handle than CWM. Best of all it doesn't go into a bootloop! Cheers! :good::good:
I was running Lam Hoang 2.2 just fine on my D850 and then decided to update TWRP from 2.8.6.1 to 2.8.7.0 (released yesterday). I downloaded the right one. I couldn't get it to flash (using the TWRP app or Flashify) and it kept giving me the secure boot error message at the top left of the screen when trying to go back into recovery (it was booting fine, though).
From the TWRP thread, the app creator posted their app AutoRec (https://play.google.com/store/apps/details?id=b007.autorecd850) and I downloaded it, installed, and ran. It worked. I updated TWRP from within recovery and rebooted...and now I'm in trouble
I can't get into recovery (getting the secure boot error message again) and the phone won't boot normally anymore. I'm getting the LG logo with the words "Security Error" in bold beneath the logo: http://k36.kn3.net/ED11C35D9.png
Thoughts? Did I just brick my phone?
rczrider said:
I was running Lam Hoang 2.2 just fine on my D850 and then decided to update TWRP from 2.8.6.1 to 2.8.7.0 (released yesterday). I downloaded the right one. I couldn't get it to flash (using the TWRP app or Flashify) and it kept giving me the secure boot error message at the top left of the screen when trying to go back into recovery (it was booting fine, though).
From the TWRP thread, the app creator posted their app AutoRec (https://play.google.com/store/apps/details?id=b007.autorecd850) and I downloaded it, installed, and ran. It worked. I updated TWRP from within recovery and rebooted...and now I'm in trouble
I can't get into recovery (getting the secure boot error message again) and the phone won't boot normally anymore. I'm getting the LG logo with the words "Security Error" in bold beneath the logo: http://k36.kn3.net/ED11C35D9.png
Thoughts? Did I just brick my phone?
Click to expand...
Click to collapse
Maybe the recovery was not bump'd?
RapHaeL_4_4_4_ said:
Maybe the recovery was not bump'd?
Click to expand...
Click to collapse
That's possible. I got it directly from here: https://dl.twrp.me/d850/
rczrider said:
That's possible. I got it directly from here: https://dl.twrp.me/d850/
Click to expand...
Click to collapse
I ran into the same issue when i tried to flash the .img file through TWRP.
If you manage to boot your phone normally the you can use the imageprep method to bump the new TWRP version and flash it using the imagepregui. I managed to get 2.8.7 working using this method.
Same Problem "Secure Error"
So my friend I did the same thing as you did and I got stuck and now I cannot use my phone but I may need to go back to stock and then root and get back to AOSP.
I am thinking of maybe there is a recovery.img in the .TOT file and a Boot.img to flash and we may have our phones back in no time, Just maybe.
thefireofwar said:
So my friend I did the same thing as you did and I got stuck and now I cannot use my phone but I may need to go back to stock and then root and get back to AOSP.
I am thinking of maybe there is a recovery.img in the .TOT file and a Boot.img to flash and we may have our phones back in no time, Just maybe.
Click to expand...
Click to collapse
Very possible, but only if you have access to a method you can flash using (such as if you had removed laf and have fastboot)
I believe imageprep makes a backup of your previous files and stores them on your computer even.
But if you can't get into fastboot then you may have to do a factory kdz image
BoredKender said:
Very possible, but only if you have access to a method you can flash using (such as if you had removed laf and have fastboot)
I believe imageprep makes a backup of your previous files and stores them on your computer even.
But if you can't get into fastboot then you may have to do a factory kdz image
Click to expand...
Click to collapse
I am thinking of flashing the files with LG Flash Tool and maybe it will work as i will be extracting the Kitkat TOT file and restore to stock but only flashing the recovery and boot image.
It's possible, I can never get the dang flash tool to see my phone so I can't offer much guidance on that.
I'm thinking the TWRP folks uploaded a non-BUMP'd recovery image to their website...because now 2.8.7.0 is missing from their site and it was definitely there yesterday when I downloaded it: https://dl.twrp.me/d850/. Maybe they never BUMP their images?
I posted in the TWRP thread when it first happened and @bender_007 (maker of AutoRec) reminded me about restoring to stock via download mode and helped me get it back to stock. When I flashed TWRP last night after doing the stock KK > root > install recovery > upgrade to LP process, I used TWRP from @777jon's thread: https://www.androidfilehost.com/?w=files&flid=22377
So yeah, if you're like me and tried updating TWRP using the image from the TWRP site and borked your phone, I'm betting the only way to unbork it is to restore KK stock via the TOT.
Confirmed, it wasn't bumped(while the 2.8.6.0 was)
Poslano sa mog LG-D802 koristeći Tapatalk
Finally
I am back to AOSP after doing alot of "BACK TO STOCK" Now I am Rooted Bumped and AOSPed!!!!!!!!!!!!!!!!!!
Gotta to go back to KitKat to root and Bump " I have tried every Lollipop root method and didnt work for me
YAY!!!!!!!!!!!!
thefireofwar said:
I am back to AOSP after doing alot of "BACK TO STOCK" Now I am Rooted Bumped and AOSPed!!!!!!!!!!!!!!!!!!
Gotta to go back to KitKat to root and Bump " I have tried every Lollipop root method and didnt work for me
YAY!!!!!!!!!!!!
Click to expand...
Click to collapse
search for jac10000 thread in here he and 6ril1 for sure had the sollution for rooting
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
I think I've seen that in order to install TWRP on the V500 is similar to how on my VK810 variant, at least the part that requires downgrading your bootloader. If it's like the VK810, it has to be the bootloader from 4.2.2. I'm sure there's TWRP threads in these sections, specifically for the V500 that give the details and files.
I'd love to know a way too. I just rooted which went great, but I have the V50020f and don't want to do another thing until I see what happens in this thread. After years of flashing and rooting I finally hard bricked my Lenovo Yoga 10 and this is my replacement tablet, so I don't want to chance it at all. Until I read a concrete solution for this build I'm staying where I am.
That wall of text is really hard to read @[email protected]!c, when I first saw it I was too tired to try and decipher it so ignored it. Now I've had another look.
Have you tried downgrading to an older firmware which people have had success with?
I had trouble when I first got this tablet but kept reading the forum and found a method to downgrade, it isn't pretty but eventually it worked. As I'm new to this device I'm not overly familiar with the different official firmware versions so I'm not exactly sure what you've got.
My tablet was more complicated as the LG tool put the Chinese, no Google apps, version on for me as that is where it was bought. So I had to downgrade so I could get apps from the Play Store to flash my recovery!
So patience and research will reward you.
[email protected]!c said:
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
Click to expand...
Click to collapse
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
I know it didn't work for the OP, but coming from bone stock v50020f, I successfully rooted using ioroot25r1, updated Supersu through playstore, then using flashify i installed TWRP 2.8.7.1 (newest I think). Once booted into TWRP recovery, I wiped cache, data, and system, and then installed AOSP Marshmallow. All went smooth as silk, no problems at all. Now I can finally stop being jealous of my wifes Nexus 7!! Hope this helps some.
vettejock99 said:
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
Click to expand...
Click to collapse
Thanks.!
i have just used twrp manager apk from playstore (similar to flashify) to get TWRP 2.8.7.1 on stock v50020f, rooted using ioroot25r1 on a mac, with updated Supersu through playstore. just had to run the apk twice as it failed first time, and have booted into twrp recovery.
Had the same problem with the recovery but worked by rooting and flashing recovery with flashify.
Hi everyone, I'm in major trouble right now.
I just flashed a modem package from this link
https://www.androidfilehost.com/?fid=23578570567721897
and now I cant get to recovery or fastboot and of course cant boot up. Caan anyone help?
I flash using nameless latest twrp and my rom is Omni 6.0 test build.
Hey I have one problem here..
Im using oppo find7a Android 5.0 color os 2.1.5..
Already root using kingroot..
I want to flash to other os like cyanogen, gummybaer, miui etc
I follow all the step on many video on YouTube using TWRP ..
After I flash twrp recover img and reboot, it stuck on fastboot menu
It cannot enter the recovery menu
How do I solve this problem so I can do wipe cache and flash other os
Some people say I must unlock the bootloader so that I can enter TWRP recovery menu
Shouheng said:
Hi everyone, I'm in major trouble right now.
I just flashed a modem package from this link
https://www.androidfilehost.com/?fid=23578570567721897
and now I cant get to recovery or fastboot and of course cant boot up. Caan anyone help?
I flash using nameless latest twrp and my rom is Omni 6.0 test build.
Click to expand...
Click to collapse
Hello, almost the same happend to me.....flashed modem package on nameless ROM.
After reboot, the phone si completely dead.
No vibration, no fastboot, no recovery.....
Did you manage somehow to solve this????
EDIT: found this guide and it works http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
tw9 said:
Hello, almost the same happend to me.....flashed modem package on nameless ROM.
After reboot, the phone si completely dead.
No vibration, no fastboot, no recovery.....
Did you manage somehow to solve this????
EDIT: found this guide and it works http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
Click to expand...
Click to collapse
What's your device model name? After unbrick mobile data working fine?
My device is X9006 and on latest Nameless nightly everything is ok.
tw9 said:
My device is X9006 and on latest Nameless nightly everything is ok.
Click to expand...
Click to collapse
Can you give me like of drivers? I used one in unbrick tool but it is not getting installed
I have no other drivers than those in the unbrick thread.
There is also a process of installing them described, which is tricky, because the drivers are not digitally signed.
If you are on windows 7, you must put them in test mode....don't know how it is with other versions of windows, because I used my older machine with W7 for unbricking.
It is all there, in the unbrick thread.....If I remember correctly....
tw9 said:
I have no other drivers than those in the unbrick thread.
There is also a process of installing them described, which is tricky, because the drivers are not digitally signed.
If you are on windows 7, you must put them in test mode....don't know how it is with other versions of windows, because I used my older machine with W7 for unbricking.
It is all there, in the unbrick thread.....If I remember correctly....
Click to expand...
Click to collapse
Finally unbrciked the device using that guide and after some workarounds got 3g working. But the biggest problem I am facing now is. I am stuck in stock 1.2..5i with twrp 2.7.0 can't old backup are not showing in recovery also can't flash anything. No system update. Flashing nameless Rom latest results in updater script error. Tried flashing latest twrp but it will reboot to system every time I try to boot into recovery. Sorry for my bulky English.
Yes, this exact problem I had also to face.
And I don't remember it exactly, but If I'm not mistaken, I flashed the original ColorOS recovery, did some updates and finally then I ended up with ColorOS 2.1.5i, I think.....
From that point TWRP recoveries worked alright, even the newest versions.
If you managed to unbrick your device, this is piece of cake, just remember - you need original ColorOS recovery firstly.
tw9 said:
Yes, this exact problem I had also to face.
And I don't remember it exactly, but If I'm not mistaken, I flashed the original ColorOS recovery, did some updates and finally then I ended up with ColorOS 2.1.5i, I think.....
From that point TWRP recoveries worked alright, even the newest versions.
If you managed to unbrick your device, this is piece of cake, just remember - you need original ColorOS recovery firstly.
Click to expand...
Click to collapse
Thank you for your reply mate. Now flashed cm13 nightly using 2.8.4 I will be selling this phone ASAP. This fourm is almost inactive.
Guys I have serious problems with my LG G3 D855 - From Brazil
A long time ago I can't enter download mode because the phone can't pass the download mode logo (?), just like 'd.jpg'.
That wasn't a problem till the same occours in the recovery, just like 't.png'. No matter how much time, the phone keeps stuck in this screen.
My system is CM 13, I can't install any update or kdz or tot file. The system boots ok, the problem is that CM 13 is nightly and some apps doesn't work properly. I've tryed flash original recovery, the new twrp 3.0, the old twrp 2.8.5, and still get this. Tryed clear cache from adb but no sucess.
ADB through system still work fine, that can be a path to my solution.
Anyone can give a hand?
Anyway, Thanks!
Download mode might be about driver
Twrp did you install right version
Reccommend reinstall whole system kdz or tot flash
Sent from my LG-D855 using Tapatalk
Duckscreen said:
Download mode might be about driver
Twrp did you install right version
Reccommend reinstall whole system kdz or tot flash
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Can you show me the correct driver? I've already installed two drivers for this phone and the Google adb drivers