[Q] G3 Corrupted Recovery - G3 Q&A, Help & Troubleshooting

N00b needing some help. It seems I have corrupted the recovery on my rooted G3 VS985. Used TWRP Manager to flash TWRP. Followed the app's instructions, installed BusyBox, applied the KitKat/Lollipop patch, went ahead and flashed. Booting into recovery just gives me a black screen and blinking blue and red LEDs. Since I'm not an expert, I'm a little paranoid to continue.
If I use bump to flash TWRP, will that wipe the corrupted file and flash a working version of TWRP (assuming I don't eff it up)? I've also seen root methods for the G3 that install TWRP as well. If I unroot and reroot with one of those methods with a bum recovery, will I brick my device? Sorry for the n00b questions, and I appreciate the help!

Look at here forum.xda-developers.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

I have d851, looking for another alternate solution for the corrupted recovery. please help.

Same issue
Same question here also. Updated twrp from twrp manager playstore app now when i enter recovery i get black screen and boot security error. Other than that i can go to download mode easily and can boot my device to android cloudy g3 without a hitch the only problem is that i can no longer use recovery

Related

[Q] 2 recoveries on 1 phone?

Hi everyone,
I just got my G Pro a couple days ago. I've been trying to read up as much as I can on the phone. I bought the phone used. It's on the V10k firmware (value pack or whatever they call it) and it was rooted, but I never did check to see if it had a custom recovery installed. Now, I installed FreeGee from the Play Store and had it flash TWRP 2.6.1. Installed successfully. But, when I reboot the phone, and I push a button to enter recovery mode, it takes me to CWM 6.0.2.8 by 985hPaKick v1. To top it off, if I "reboot recovery" from within CWM, or if I use "adb reboot recovery," it'll take me to TWRP. Anybody have a clue what's happening, or is this normal and I'm just not hip to it yet? I would've figured that if CWM was on here originally and I didn't know it, flashing TWRP would've just overwritten CWM. I'd like to be able to flash custom ROMs and such but I've never had this occur to me with an Android before, and I'm not trying to brick this thing. Any help and guidance would be greatly appreciated. Thank you!
Im new to the LG world also. I dont know how this happened but if you flash back to stock via LG flash tool then reroot. You can Freegee a recovery over the stock one just reflashed. When I flashed the TWRP recovery the touch screen was dead(when in recovery mode) so I reflahed CWM over it with Freegee and it worked. Hope this helps
Thanks bud, I'll give it a try.

[Q] Xposed, TWRP, Bootloop, Help!?!?!?!

Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.
sgtfrnz said:
Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.
Click to expand...
Click to collapse
Well something was messed up when you flashed xposed installer( i don't know what you mean by automatic method) but do a clean install,since you can get into download mode,grab the twrp img.tar and flash it using pc odin ,then you can access recovery, do all the wipes again by going under "advanced" and reflash your rom.Now to install xposed go to xda thread for it and grab the apk from there (i think it's available on play store as well).You should have no more issues
Twrp
Like the previous post said I'm not sure what you've done. When xposed framework is installed there is usually an unistall zip created on the internal so card. If you can get recovery find it and flash it
Sent from my GT-N7105 using Tapatalk
The device is now fixed.
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.
sgtfrnz said:
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.
Click to expand...
Click to collapse
Boot into Download mode and flash philsz touch recovery 6 and reboot device .. Everything will be ok>
Old thread may be old, but it's still relevant.
I just tried to install XPosed as well on my Note II and it did the same thing (mine's AT&T)
Info
Device: Note II
XPosed Version: 2.6.1
Install Method: "Recovery (flash zip automatically)"
Recovery Image: TWRP
Mine exhibited the same behavior as OP's, however after leaving it alone for a while to bootloop recovery as much as it wanted to, I came to my laptop, found this post, grabbed as USB cable, and I was just about to start the process of reflashing recovery when all of a sudden I saw my lock screen.
It took roughly five minutes of bootloop to get it there, but it successfully installed XPosed and my device is running fine.
So, for all the other Googler's out there that landed on this post, leave it alone for a while! See what happens. If it's still bootlooping, like, 30 minutes later, then try reflashing TWRP using ODIN. If that still doesn't work, reflash a new ROM using TWRP.

Samsung S4 Mini GT-I9192 Dual Sim Cannot Start Phone

Dear All,
Here's the problem:
The Goal: To Install CM-12.1 Custom ROM
What I have done:
1. Installed TWRP Recovery Manager and no matter how many times I tried, was unable to install TWRP Recovery
2. Installed Flashify, not possible to install TWRP, CWM or any other recovery!
3. Installed Rashr and finally was able to get PhilZ Touch 6 Recovery installed on the phone.
Rebooted to recovery and it's working! Great!
Now, I have the CM-12.1 zip file on the external SD card but can't flash the ROM no matter how many times I try. Yes, I did wipe factory reset and all the wipes possible, NOT ABLE TO INSTALL the Custom ROM.
The real problem now is that before I tried installing the custom ROM, I accidentally made a mistake, a really bad one too.
When my phone was starting normally, in Flashify (or Rashr, I don't remember now) I selected the downloaded TWRP recovery image for Kernel and rebooted the phone. Yes, a dumb move, I know, but for some stupid reason I did that! And now the phone won't start!!!
Getting this msg:
Set Warranty Bit: kernel
Plus, when I boot into Philz Touch 6 recovery, not able to install ROM or do anything else either.
I managed to install Aroma File Manager, and deleted some of the twrp recovery images, but still getting the kernel error.
Also, in Philz Touch recovery, I have done something wrong and I think I may have lost ROOT access. Tried several times to Re-Root Super SU but it says now install Super SU from the Market. How can I install Super SU from market if I cannot get the phone to start in the first place.
Anyway, if anyone knows how to fix these issues or has experienced similar problems, please share the steps you took to solve the problem.
All the help is appreciated!
Thanks vey much in advance!!!
P.S. Please write in comments if any screen capture is needed.
BOOTLOOP!
If anyone can, please help, I can't use my phone for over a week now!!!
the phone is stuck in bootloop!
the recovery I was using apparently wasn't the right version for my gt-i9192 and for some stupid reason it thought that my phone is gt-i9190!!! i was using twrp 3.0.0.0 serrano3gxx by the way. and i could not install the custom rom, the right rom for gt-i9192... because the recovery thinks my phone is gt-i9190... stupid right
so i installed openrecovery-twrp-2.8.7.0-serranodsxx-STABLE-signed zip file using the twrp recovery itself. and now i can't even go to recoery mode!!! WOW!! I think i ****ed up this phone big time!!!
i know there was a warning to not install the recovery using the recovery itself, but i didn't have a choice.
i did that because Odin is not working for my phone!! can't install anything with odin...
it just gets stuck and never finishes the flash. can't install anything with odin, nothing at all. just gets stuck!!
so now the problem is this stupid bootloop and on top of that i can't even get the phone to start the recovery, when I try, it goes back to this bootloop problem. by the way this is the bootloop msg:
Set Warranty Bit : kernel IN YELLOW COLOUR and the phone logo: Samsung Galaxy S4 mini GT-I9192

Lost root. How do I regain it?

Hi guys it's been a while since I've rooted any devices but decided to root my LG G PAD 8.3 (V500), since it is so outdated. I'm gonna go over exactly what I did on how I got here to better understand. Sorry in advance for the long winded post.
-Anyway, I had to downgrade to 4.2.2 by using the LG Flash Tool 2014.
-Then, I rooted my device by running root.bat Also, I had SuperSU when I rooted.
-After rooting, I installed TWRP via the play store, downloaded the most recent twrp.img and flashed it via the app. It took me forever to get to recovery by pressing power+volume down and then pressing power+volume down+volume up. But after what felt like 20+ tries, I got to TWRP recovery.
-I wiped my phone and flashed the most recent Lineage ROM. Unfortunately, after flashing the ROM, I could not flash GApps because it rebooted to the ROM after flashing. TWRP let me know that I had to update TWRP and since I did not have the play store and I was once again having trouble getting into recovery, I downloaded the most recent TWRP apk.
-When trying to open the apk, it gave me a "can't open file" message which I didn't understand why. After rebooting, for some reason, it then let me run the TWRP apk and installed the TWRP app. This is when I found out that I was no longer rooted because TWRP notified me. I double checked with root checker and indeed I was no longer rooted. I have no idea when or how that happened.
-Again, I couldn't get into TWRP recovery until I plugged in my phone to my PC and for whatever reason, it helped me get into recovery. I wiped the phone and proceeded to flash Lineage and GApps.
-I read that by flashing SuperSu I may regain root, so downloaded an updated SuperSu, went into recovery and flashed SuperSu. When rebooting, the LG screen came up with a message at the top left corner reading "secure booting error! Boot certification verify". At that point, I was in a bootloop and had to go into recovery, wipe and flash again minus supersu. So I am now on Lineage with GApps and no root.
How do I regain root? And anyone know how I was able to lose it? Back in the day when I was into flashing, I never had these problems and never lost root out of nowhere like this.
Also, if I wanted to get back to stock LG 4.2.2, how would I go about that? I know that currently, I can't use the LG Flash Tool 2014 because my current ROM does not have a USB Software option in order for the tool to recognize the tablet.
Any help would be greatly appreciated, thank you.

A70 Bootloop after Magisk flash *not enough posts for Dev*

Hey guys:
FIRST OFF: I don't have enough posts in order to stick this in Dev, SORRY!!!
I have read all related posts and stickies but still can't get this sorted out.
Let's get some background... I'm looking at rooting the phone with Magisk. This did not work directly and I was guided by another "how-to" to do it via TWRP instead.
Flashed the vbmeta and TWRP without issues. Booted into TWRP and tried to flash Magisk, which gave me an error at first. It was an old version so I tried a later version, which flashed "successfully," but after a reboot I'm stuck in a loop that reaches the SAMSUNG Galaxy A70 screen, then reboots to show that the bootloader is unlocked, and again and again and so forth...
What did I do wrong? And is there any way for me to fix the boot loop?
Holding in Volume Up does allow me to boot into TWRP so I don't feel as though the phone is bricked.
Any help will be appreciated, preferably that that gets my phone rooted, but even just getting it back to normal will work for me
Thanks in advance,
ShOrTyNoLeGs
Follow this guide
https://forum.xda-developers.com/ga...root-galaxy-a70-twrp-los-17-1-magisk-t4100655
After flashing magisk using twrp, you should reflash stock recovery, Reboot into it then select reboot system BEFORE 1ST BOOT to prevent bootloop.
Factory reset after flashing magisk in twrp will fix all bootloop.
Or follow the guide in my signature for successful root. But you wouldn't have twrp that way, just stock rooted rom

Categories

Resources