I have a problem with my LG G2 802, I installed TWRP 2.6.3.3 also installed with root, the problem is that LG sent me an update to install Android 4.4.2 and accept the update, restart automatically when opened TWRP 2.6.3.3, and now every time I open TWRP reboot.
I tried connecting to PC, but I do not recognize the drivers. I uninstalled the drivers and I reinstalled and I jump the same error.
If anyone can help me.
My problem now is that does not let me to Android, automatically load the TWRP and no way to get into Android, well I do not recognize the device into the computer and the drivers are installed correctly.
Greetings and Thanks
cristian.vcastillo said:
I have a problem with my LG G2 802, I installed TWRP 2.6.3.3 also installed with root, the problem is that LG sent me an update to install Android 4.4.2 and accept the update, restart automatically when opened TWRP 2.6.3.3, and now every time I open TWRP reboot.
I tried connecting to PC, but I do not recognize the drivers. I uninstalled the drivers and I reinstalled and I jump the same error.
If anyone can help me.
My problem now is that does not let me to Android, automatically load the TWRP and no way to get into Android, well I do not recognize the device into the computer and the drivers are installed correctly.
Greetings and Thanks
Click to expand...
Click to collapse
you should applied update on stock recovery not on custom recovery
try to flash stock recovery via twrp recovery(if any way available)
Related
Hey, can anyone help me. I just wanna install current twrp version cause its necessary for an Android 4.4.4 custom rom. When i rooted my phone today and installed twrp 2.5.0.1 and Android 4.2.2 CynaogenMod 10.1 all worked fine. Found out this version is to old to run Android 4.4.4 installation so I tried to update to newest trwp version and getting an error now. When i go to pink screen on phone and execute fastboot flash recovery i get the report "waiting for device". googled this and google says "driver is not installed" when having this issue. Wanted to reinstall the "Huawei_usb_driver_2.0.6.601" driver on Windows 8.1 but there is no uninstall.exe. How to reinstall this driver or what i need to do to fix this issue? Unfortunately flashing worked before....
Also tried to run GooManager but it didnt find any new version of twrp.
mindhunter123 said:
Hey, can anyone help me. I just wanna install current twrp version cause its necessary for an Android 4.4.4 custom rom. When i rooted my phone today and installed twrp 2.5.0.1 and Android 4.2.2 CynaogenMod 10.1 all worked fine. Found out this version is to old to run Android 4.4.4 installation so I tried to update to newest trwp version and getting an error now. When i go to pink screen on phone and execute fastboot flash recovery i get the report "waiting for device". googled this and google says "driver is not installed" when having this issue. Wanted to reinstall the "Huawei_usb_driver_2.0.6.601" driver on Windows 8.1 but there is no uninstall.exe. How to reinstall this driver or what i need to do to fix this issue? Unfortunately flashing worked before....
Also tried to run GooManager but it didnt find any new version of twrp.
Click to expand...
Click to collapse
Should be able to use Flashify.
Hey guys
I would be more than thankful if someone could help me with this problem.
So, I had installed Cyanogenmod 13 and cyanogen recovery. Worked perfectly. Then I tried to install TWRP, BUT I accidently installed TWRP version for OnePlus One (bacon)
I installed TWRP via fastboot. Now my device doesnt boot to Os. After that loading screen it goes straight to recovery mod (cm).
Installed cm rom via recovery, but that did not help. I found help quide for bricked devices at OP forum, but my Pc doesnt reconize the phone. I can get the device to bootloader/fastboot mode, but cannot send any commands ( doesnt find any devices )
Your home boyy jalmari
You need to install the drivers for adb and fastboot. There's a small packet with all you need, instead of using Google's.
Sent from my ONE E1003 using Tapatalk
Hello guys,
I rootet my Phone with the Kingroot.apk, after that i wantet to Flash with Flashify the TWRP Recovery.
It worked so far but then my Phone reboots only into the TWRP Recovery. Because of that i decidet to install the Stock PPOS Rom but after i flashed it, my phone doesnt boot into the OS or even in the Recovery. I tryied to Repair it with ADB but the Phone connect and disconnect every second from my PC.
I installed all Drivers.
sry for my bad English im from Germany and im new here
Maybe you didn't installed correct drivers. try finding another
You can also go in fastboot, from there you can flash supported twrp and install supported custom rom :laugh:
So, I kind of rooted my device using Kingo Root and it wasn't successful (I guess). So, in fastboot mode, I tried OEM unlock and it didn't work too; but anyway, I flashed TWRP recovery into my phone and through that I tried to install CM 13,14 custom ROMs which was completely unsuccessful. It doesn't allow me to install any ROM. And says that root privilege is lost. And now, all that I have access to is a phone stuck in bootloop and TWRP which doesn't allow me anything to do because apparently root access is lost. :crying:
I tried every method of flashing via YGDP tool and it is stuck at 'entering download mode'. I have installed different drivers over and again to fix as suggested by different threads but still, it's the same. [Windows 8.1] . And is there any other tool to flash this same stock ROM or better, can I get root access again in a bricked device and install a custom ROM any way?:fingers-crossed:
I also have access to ADB sideload via TWRP, so can I get stock ROM in .zip format. So far, I can only find it in .CPB format; maybe I can use .zip stock ROM via ADB sideload to flash it. Please help if any of this is possible.
*Apology for such a long question but I think you guys must know everything in order to provide me with a fix*
It's fixed.
dhananjaydhiman said:
So, I kind of rooted my device using Kingo Root and it wasn't successful (I guess). So, in fastboot mode, I tried OEM unlock and it didn't work too; but anyway, I flashed TWRP recovery into my phone and through that I tried to install CM 13,14 custom ROMs which was completely unsuccessful. It doesn't allow me to install any ROM. And says that root privilege is lost. And now, all that I have access to is a phone stuck in bootloop and TWRP which doesn't allow me anything to do because apparently root access is lost. :crying:
I tried every method of flashing via YGDP tool and it is stuck at 'entering download mode'. I have installed different drivers over and again to fix as suggested by different threads but still, it's the same. [Windows 8.1] . And is there any other tool to flash this same stock ROM or better, can I get root access again in a bricked device and install a custom ROM any way?:fingers-crossed:
I also have access to ADB sideload via TWRP, so can I get stock ROM in .zip format. So far, I can only find it in .CPB format; maybe I can use .zip stock ROM via ADB sideload to flash it. Please help if any of this is possible.
*Apology for such a long question but I think you guys must know everything in order to provide me with a fix*
Click to expand...
Click to collapse
Its fixed now, I assume it was because of the ROM file being downloaded through chrome in phone, I downloaded ROM and GApps in PC and flashed through TWRP and bam! Its back on:laugh:
TWRP - 2.4.4
ROM - Resurrection Remix 5.7.2
Thanks anyways!
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!