Hi all, I'm probably not the first to have this problem and I'm sure the answer is out there I just can't find it. I can get TWRP to stick as a recovery but it's not my recovery of preference. Had to revert back to stock after my backup wouldn't load properly
now I obviously having problems with recovery. Tried using TWRP to backup after I re-rooted but when I restored it got stuck on boot screen. Anybody with any answers out there? Obviously I'm on stock T-Mobile Note 3, trying to get back to where I was, thanks in advance for any help!
Related
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.
So in attempting to flash touch TWRP on my phone running .244 I accidentally flashed recovery instead of boot like the thread states, as I had been using another thread to make sure I used the correct commands and used recovery. I then flashed it via boot like I'm supposed to when I realised. It now bootloops after getting to "Botting DoomKernel by DoomLord". I can enter recovery and bootloader just fine, but I can't boot into android. I recently had wiped my phone as I was having issues on a custom ROM and am back on pure stock, but am rooted. I don't have a backup just yet as I had been at my girlfriends house to got on to stock, and was actually flashing TWRP to do a NANDroid. What are my options?
What want happen if you flash only the kernel again? I dont know what it happens but I would try it if I had this problem xd
Thanks so much gripfly, I don't know why the thought never occurred to me. Phone is now fixed.
I need help with my sm-t217s. I made a backup because i was trying to install the candykat rom just to see if it works, but it didnt. Now i cant restore my SM-T217S. I need help. BTW im using CWM Recovery.
Is CWM recovery the problem? Please help. I need some responses as soon as possible.
I recently flashed CM12.1 on my S3. I was running rooted stockmod 4.3. Everthing went fine. I made a nandroid first. I was able to flash back to with my nandroid and then back to a nandroid of CM12. I tried to flash back again and booted into Touchwiz ROM with no Google services and most of many (too) many apps gone. I then tried to flash back to my CM12 Lollipop nandroid in recovery and got stuck in a bootloop. I could not get past the the Teamwin screen.
Even though my USB port is dicey I was able to use ODIN on my pc to flash back to stockmod_root 66. I then installed TWRP using TWRP manager on device. This went fine.
I then tried to flash back to CM12 in recovery using my nanback but the phone reboots after a few seconds with any task, even just wiping partitions. I am also now getting an error message after trying to load the same stockmod I used successfully earlier. The message is in Chinese so I have no idea what it says.
Any hope here?
Edit: I managed to load the stock image in ODIN and it is flashing now. Still do not understand what did wrong so as not to be able to restore my nan back of CM12. Was there a problem with my installation of TWRP with TWRP manager?
Thanks
I'm having a new issue with recovery. So for some reason I decided it would be a good idea to try to flash twrp via the twrp app to see if it would fix the inconsistency of twrp loading/not loading. Stupid decision. Twrp stopped working completely. It would load to the menu but was unresponsive. It also kept the phone from booting past the galaxy screen. I tried odining twrp 2.8.7.1, 2.8.7.0, 2.8.6.0. No change. So I odined the of7 tar, updated to ofe, odined the ofe rooted kernel. Phone booted and worked fine. So far so good. Then I tried odining the 2.8.7.1 recovery. Same issue occurred again. I have no idea why... So I had no choice but to repeat the whole tar/update/root process to get the phone back up and running. Now I am just rooted on the stock ofe and can't figure out how to get the recovery to work so I can get back to twisted rom. I even have a backup, but I can't restore it without booting into a working recovery. Any ideas on how to fix this would be greatly appreciated.
the recovery we need for 5.1.1 is twrp-2.8.7.1-zerofltespr.img.tar that spr is important and its around here somewhere. ill find a link when i get to work if someone else doesn't post