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.
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:
can't flash a CWM recovery on my wife's E980 using Freegee....Mine is the white one and I had no loki issues with it...everytime you flsays:
"checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image. "
yes I did use Freegee already and install CWM. When I booted it gave me this...I can't install any ROMS. yet my other G Pro (white) is fine and hasn't given me any issues. RIght now I'm stuck with it booting into clockwork by itself. And I would like to use TWRP but the version that comes with Freegee doesn't work right on the damn screen. If it's not bootlooping into Clockwork then it gets frozen at the LG screen with something about security crap. and the funny part is...I used Freegee both times.
EDIT: used LGFlashTool to bring it back..but she wants a custom ROM and every recovery I flash to it either
1. used this recovery. tried flashing using a CWM recovery that I used from Freegee http://forum.xda-developers.com/showthread.php?t=2552611
freezes at the LG screen with a SECURITY ERROR on the left corner of the screen (flashtools will fix)
2. When I do successfully flash a recovery using Freegee and I get it to boot into CWM it won't come back out of CWM it will boot automatically into it (LGflashtools will fix)
3. the freegee TWRP in won't work right with the touch screen.
Yes I saw that there are 2 topics similar to this, but they are G2's. Mine is an AT&T E980 that i'm having issues with.
I had exactly this same problem. I'm also on AT&T E980 and could not find a fix anywhere for this phone. I flashed back to stock so many times that I was ready to just get rid of it. What I finally noticed was that, if I flashed back to stock and took the update to E98010P, I could flash TWRP through FreeGee and the touch would work. I also used VooDoo OTA to preserve root through the update. I don't know if it was necessary, but it didn't cause me any problems and everything worked.
I have no idea why CWM stopped working and I could not use Phil's recovery either, but the whole experience has been maddening and I have never had so many problems with a phone before. Hope this helps.
i have the same annoying problem!
can someone help?
after the rom flash was done i've got the error so i immediately restored my backup
EdgarSnyder said:
I had exactly this same problem. I'm also on AT&T E980 and could not find a fix anywhere for this phone. I flashed back to stock so many times that I was ready to just get rid of it. What I finally noticed was that, if I flashed back to stock and took the update to E98010P, I could flash TWRP through FreeGee and the touch would work. I also used VooDoo OTA to preserve root through the update. I don't know if it was necessary, but it didn't cause me any problems and everything worked.
I have no idea why CWM stopped working and I could not use Phil's recovery either, but the whole experience has been maddening and I have never had so many problems with a phone before. Hope this helps.
Click to expand...
Click to collapse
so...Root using the old firmware...voodoo OTA then update?...and then restore root and then Freegee should work fine with TWRP?
ive installed the twrp recovery and the flash completed , but the idiot checked the MD5 than skipped it than finished and on the bottom line just did NOTHING!
what the hell!
what is going on with this phone! so frustrating ...
Yeah, I went back to stock, rooted and installed FreeGee and Voodoo, then took the update and flashed TWRP thru FreeGee.
Sent from my LG-E980 using xda app-developers app
and?
no you can install whatever rom you want?
amirnew said:
and?
no you can install whatever rom you want?
Click to expand...
Click to collapse
No, i'm pretty sure on the firmware i'm running (not sure what you're running) can only flash touchwiz based ROMS. No Cyanogenmod, AOSP or anything not based on samsung's stock UI
stanleyopar2000 said:
No, i'm pretty sure on the firmware i'm running (not sure what you're running) can only flash touchwiz based ROMS. No Cyanogenmod, AOSP or anything not based on samsung's stock UI
Click to expand...
Click to collapse
i've tryied flashing custom 4.1.2 rom... and my phone is e980 from att
amirnew said:
i've tryied flashing custom 4.1.2 rom... and my phone is e980 from att
Click to expand...
Click to collapse
wrong thread. it was meant for this one
http://forum.xda-developers.com/showthread.php?p=51529974
stanleyopar2000 said:
can't flash a CWM recovery on my wife's E980 using Freegee....Mine is the white one and I had no loki issues with it...everytime you flsays:
"checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image. "
yes I did use Freegee already and install CWM. When I booted it gave me this...I can't install any ROMS. yet my other G Pro (white) is fine and hasn't given me any issues. RIght now I'm stuck with it booting into clockwork by itself. And I would like to use TWRP but the version that comes with Freegee doesn't work right on the damn screen. If it's not bootlooping into Clockwork then it gets frozen at the LG screen with something about security crap. and the funny part is...I used Freegee both times.
EDIT: used LGFlashTool to bring it back..but she wants a custom ROM and every recovery I flash to it either
1. used this recovery. tried flashing using a CWM recovery that I used from Freegee http://forum.xda-developers.com/showthread.php?t=2552611
freezes at the LG screen with a SECURITY ERROR on the left corner of the screen (flashtools will fix)
2. When I do successfully flash a recovery using Freegee and I get it to boot into CWM it won't come back out of CWM it will boot automatically into it (LGflashtools will fix)
3. the freegee TWRP in won't work right with the touch screen.
Yes I saw that there are 2 topics similar to this, but they are G2's. Mine is an AT&T E980 that i'm having issues with.
Click to expand...
Click to collapse
Ok I have used CWM from FreeGee and used the Carbon (http://forum.xda-developers.com/showthread.php?t=2439911) ROM and it does not need lokifying for my AT&T E980. It loads fine. I'm looking for a way to fix the lokifying thing though as I can't flash too many ROMs, a lot need lokifying.
I've personally had no issues on my E980 using TWRP flashed by FreeGee, but you can always try the "hacked" TWRP provided by @madmack
http://forum.xda-developers.com/showpost.php?p=45497511&postcount=235
chp said:
I've personally had no issues on my E980 using TWRP flashed by FreeGee, but you can always try the "hacked" TWRP provided by @madmack
http://forum.xda-developers.com/showpost.php?p=45497511&postcount=235
Click to expand...
Click to collapse
+1
Always used Madmack's hacked TWRP for anything that requires loki and it works flawlessly.
Sent from my 4.4 Sphinx REMOD LG-E980
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
So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life
I recently flashed v30b on my D855. I did a clean (CSE) flash with the LG flash tool 2014 and rooted the device with KingRoot. But every time I reboot I lose root acces.
I installed the bump'd version of TWRP with flashify, but when I try to boot into TWRP I get a MISMATCH_SIG_LEN error before the screen goes black and the led starts blinking. I then pull out the battery to start over with a fresh unrooted phone. I think I loose root acces before entering recovery or something. I did some searching, but the only solution I found was to do a clean install, which I already did.
My goal is to install TWRP to flash custom ROMs. How do I fix this?
I think that after installing root with kingroot you will need to perm root it. Kingroot is only temporaty and even if you uninstall it you get unrooted.
Nikolatas said:
I think that after installing root with kingroot you will need to perm root it. Kingroot is only temporaty and even if you uninstall it you get unrooted.
Click to expand...
Click to collapse
I'm having a sort of similar problem on my D85130d. I downgraded fine from 30g to 30d with LGUP. downloaded kingroot and rooted. That was all good. Installed TWRP and flashed the recovery rom and was able to make a backup of my current stock rom (which has saved my life because I think I've soft bricked my phone about 4 times trying to permanent root hahah). Since I AM new to rooting I think I'm missing a certain step, (or maybe the zips im trying to flash are corrupt?) Basically, tried https://forum.xda-developers.com/tm...wngrading-rooting-t3608851/page3#post74961164 and I've also tried https://forum.xda-developers.com/tm...ock-d851-30d-kdz-flashable-zips-imgs-t3367371. The problem with the first one is its not completely specific and like I mentioned before, I'm a white belt at rooting lol. The second thread gave me hope and i do have TWRP installed so I downloaded the 2 main zips I would need (a. LG-D85130D-Flashable.Boot-AUTOREPACK.zip
and b. SuperSU zip) reboot to recovery and flashed both zips separately then reboot. But I end up with a TMO screen and it stays like that. This last time I even left it loading on that screen for about 2 hours and no such luck. I'm wondering is there something I'm missing? Any help would be greatly appreciated from the XDA gods
HingleMcCringleberry said:
I'm having a sort of similar problem on my D85130d. I downgraded fine from 30g to 30d with LGUP. downloaded kingroot and rooted. That was all good. Installed TWRP and flashed the recovery rom and was able to make a backup of my current stock rom (which has saved my life because I think I've soft bricked my phone about 4 times trying to permanent root hahah). Since I AM new to rooting I think I'm missing a certain step, (or maybe the zips im trying to flash are corrupt?) Basically, tried https://forum.xda-developers.com/tm...wngrading-rooting-t3608851/page3#post74961164 and I've also tried https://forum.xda-developers.com/tm...ock-d851-30d-kdz-flashable-zips-imgs-t3367371. The problem with the first one is its not completely specific and like I mentioned before, I'm a white belt at rooting lol. The second thread gave me hope and i do have TWRP installed so I downloaded the 2 main zips I would need (a. LG-D85130D-Flashable.Boot-AUTOREPACK.zip
and b. SuperSU zip) reboot to recovery and flashed both zips separately then reboot. But I end up with a TMO screen and it stays like that. This last time I even left it loading on that screen for about 2 hours and no such luck. I'm wondering is there something I'm missing? Any help would be greatly appreciated from the XDA gods
Click to expand...
Click to collapse
To be fair, i perma rooted the v30B variant. Im not sure bout the D. I rooted it with kingroot, installed TWRP via autorec, i went in recovery and flashed the file thats in the post, rebooted and then installed supersu from the playstore and im perma rooted. After that kingroot is gone and you are left with supersu. This is the guide i followed https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268