I've had a tmo g2 since november, i'm still on 4.2.2, I just rooted the phone and I'm trying to install a recovery. I tried TWRP by the app in the playstore, then voldown + power to get into recovery, just reloaded the phone. For a split second, i get a recovery android guy with text saying something is updating, but then it just loads the tmo logo and goes back into the phone. I d/led the AIO at
http://forum.xda-developers.com/showthread.php?t=2633941&page=4
I uninstalled twrp and tried all three offered but the same thing happens with each, so am I screwed? Plz plz plz, I'm hoping someone can point out what I'm missing here, innumerable thanks if you can.
Bump maybe?
hope someone who can helps sees this before it fades away...
go onto the play store and get freegee it should detect your phone and come up with compatable recoveries if so click the recovery you want and it will download and install
If NOT then google twrp revovery for lg g2 d801 and download a version of twrp for your model and get twrp manager from play store on the twrp manager go to install then locate the downloaded recovery then flash it after a while you will have a custom recovery instaed hope this worked for you
Thanks Reecegibbs. That's what I did while I was waiting for someone to respond to this. Same thing essentially, but now i can't get the little android guy to pop up. I got freegee, tried cwm but it stalled and never finished, but I installed twrp that way, tried to reboot to recovery, and the same thing happened minus the momentary glimpse of droid.
Phoenity said:
Thanks Reecegibbs. That's what I did while I was waiting for someone to respond to this. Same thing essentially, but now i can't get the little android guy to pop up. I got freegee, tried cwm but it stalled and never finished, but I installed twrp that way, tried to reboot to recovery, and the same thing happened minus the momentary glimpse of droid.
Click to expand...
Click to collapse
the only thing i can think of right now is to backup all your data on your phone reflash the kdz file and then do a hard resetwhen booted use the ioroot it the freegee will do the rest this will work but it will require you to lose your apps and rember to back up personal data as this will wipe that too
Reecegibbs said:
the only thing i can think of right now is to backup all your data on your phone reflash the kdz file and then do a hard resetwhen booted use the ioroot it the freegee will do the rest this will work but it will require you to lose your apps and rember to back up personal data as this will wipe that too
Click to expand...
Click to collapse
Pretty sure I'm not missing something major, but wth is a kdz file? I used ioroot24 to root, and like i said, twrp thru the play store and then the AIO i linked to to try flashing a recovery. I know I have all the drivers installed properly, otherwise I wouldn't have been able to root, so where does this kdz file come into play?
Phoenity said:
Pretty sure I'm not missing something major, but wth is a kdz file? I used ioroot24 to root, and like i said, twrp thru the play store and then the AIO i linked to to try flashing a recovery. I know I have all the drivers installed properly, otherwise I wouldn't have been able to root, so where does this kdz file come into play?
Click to expand...
Click to collapse
a kdz file is basically the whole operating system with extracrap thrown in for the lg g2 they are normally about 1.5gb to 2.1gb in size for you phone i will link the right kdz file if you can tell me the infomation about your phone and also give you the tools to flash it if your interested
Thanks for the offer, but I got it myself last night. I had to use freegee to install TWRP, then I downloaded the twrp app, gave it SU access and used it to boot into recovery, which worked this time, so I could flash the rom. Apparently it takes two.
Related
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
paryguy said:
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
Click to expand...
Click to collapse
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
TWRP
Follow the install instructions for TWRP 2.6.3.2. Then after you've confirmed you can boot the OS from the recovery, place the 2.6.3.3 on the root of your SD. Reboot into recovery and flash 2.6.3.3. Reboot into recovery again and you'll be good to go.
Version 2.6.3.2 won't flash 4.4 ROMs but 2.6.3.3 will flash 4.2 (I'm assuming), 4.3, and 4.4.
Download FreeGee app from the play store and install TWRP recovery from it. It was the only way I could install it on my LG G2.
So many
simon_lefisch said:
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
paryguy said:
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
Click to expand...
Click to collapse
What build number are you on?
Sent from chdhsheh fhhdud
vnrse Theologisch
simon_lefisch said:
What build number are you on?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I used RussGJohnson solution and it worked in a matter of seconds. Now I'm stuck though. I wiped everything and can boot into TWRP but I have no ability to sideload anything. I have all the latest LG drivers, even the lastest android sdk drivers, nothing is working. If I boot up normally the LG logo comes up and just sits there.
I can boot into recovery using the whole volume down + power button combo but then when I go to sideload my computer isn't seeing the device. I'm on a Win 8 machine using the stock cable. I've tried both USB 2 and 3 ports
It's done
Using RussGJohnson's suggestion worked great.
The issue I had with being unable to sideload a ROM wasn't resolved but I just used my Mac to do it instead. That worked just fine. Win8 couldn't recognize the device while in recovery. Go figure.
free gee very fast
Use Flashify u n00b.
I posted yesterday on this topic but wanted to give an update.
I downloaded the cyanogenmod for my LG G2. The you tube video I watched as watch?v=tyBc45ScZzw. When I try to reboot into revovery mode all I get a black screen and little Android guy with a red triangle over the top and a exclamation point in it.
\\\
Any help as to what I am doing wrong to get into recovery mode? I actually factory defaulted yestersday and tried again and the same thing is happening.
Thanks for the help
TheBull50 said:
I posted yesterday on this topic but wanted to give an update.
I downloaded the cyanogenmod for my LG G2. The you tube video I watched as watch?v=tyBc45ScZzw. When I try to reboot into revovery mode all I get a black screen and little Android guy with a red triangle over the top and a exclamation point in it.
\\\
Any help as to what I am doing wrong to get into recovery mode? I actually factory defaulted yestersday and tried again and the same thing is happening.
Thanks for the help
Click to expand...
Click to collapse
Seems you haven't installed a custom recovery yet buddy, if you tried, you've failed.
First root your phone, then install a custom recovery, then try again booting into your recovery.
If your already on stock kk, I don't believe you can install a custom recovery yet, only root it. So you would first have to downgrade back to JB.
Check the
Merfy said:
Seems you haven't installed a custom recovery yet buddy, if you tried, you've failed.
First root your phone, then install a custom recovery, then try again booting into your recovery.
If your already on stock kk, I don't believe you can install a custom recovery yet, only root it. So you would first have to downgrade back to JB.
Check the
Click to expand...
Click to collapse
What would be the best custom recovery to install? I def know my phone is rooted. That I already check. I have yet to go up to KK . My phone says Android Version 4.2.2
TheBull50 said:
What would be the best custom recovery to install? I def know my phone is rooted. That I already check. I have yet to go up to KK . My phone says Android Version 4.2.2
Click to expand...
Click to collapse
Well there only 2 options really, I'd say TWRP is more user friendly, so i would recommend that to you, before installing a rom first read the instructions and make sure they haven't first recommend a recovery for that specific rom installation.
Once you have a custom recovery its very simple to switch between them.
Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2469995
It's an old method but is very easy. This will install twrp but an old version.
So before using the method above first download the latest twrp onto your phone, i don't know what version of the g2 you have so if you reply i can try point you to the latest, but if you search for twrp 2.7 for your phone you should find it. You want it in .zip format.
So after saving the file to your phone, go ahead and follow the instructions above, if it says it successful, try booting into recovery again, the same way you managed to format your phone but this time it should boot your recovery, then press install .zip and flash the latest twrp.
Then your ready to go! just follow the instructions for the roms you'd like and flash them.
Best of Luck!
Merfy said:
Well there only 2 options really, I'd say TWRP is more user friendly, so i would recommend that to you, before installing a rom first read the instructions and make sure they haven't first recommend a recovery for that specific rom installation.
Once you have a custom recovery its very simple to switch between them.
Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2469995
It's an old method but is very easy. This will install twrp but an old version.
So before using the method above first download the latest twrp onto your phone, i don't know what version of the g2 you have so if you reply i can try point you to the latest, but if you search for twrp 2.7 for your phone you should find it. You want it in .zip format.
So after saving the file to your phone, go ahead and follow the instructions above, if it says it successful, try booting into recovery again, the same way you managed to format your phone but this time it should boot your recovery, then press install .zip and flash the latest twrp.
Then your ready to go! just follow the instructions for the roms you'd like and flash them.
Best of Luck!
Click to expand...
Click to collapse
I'm using a Verizon LG G2 VS980 . I just downloaded TWRP 2.7 though so I am going to give that a go !!
I got my spare G2 today and have run into a bit of a problem with rooting it. The root process seems to have gone fine. It says I am rooted and I can use Root Explorer to remove bloat and such, but something seems to have gone wrong with the recovery. If I try to boot into recovery, I get an error message that says something about Secure booting error. It has some other info, but the screen goes black so quickly that I can't make out what it is saying. If I hold the power button down, I can reboot the phone as normal so it's not bricked, but without a recovery I can't do any custom Roms. I've tried various methods to flash a new recovery and they all said they were successful, but I still can't get into recovery mode.
Does anyone know what I did wrong or how to get around this? The phone came with firmware 4.4.2 26a if that means anything to your advice.
Thanks a million for any help.
Looks like your recovery gone. Flash stock Lollipop Kdz then root and install TWRP with Autorec from Google Play.
Thank you. Just did the TOT method to flash back to stock 26a so thankfully all is back to normal. Now i'm afraid to try it again because I don't know what went wrong. The ioroot version I have is an older version for 24a or backwards. That's the one I used for my original G2. So I tried using a different method (one click) for this phone and it was a mistake. Could I use the flash tool to kdz back to 24a and then root using the method I know or do I have to stick to 26a for hardware reasons?
Heyy guys, this is my first time posting a new thread
Unfortunately, my phone is stuck in TWRP recovery. When it was still working I downloaded Flashify. I don't remember what but when it restarted the phone, it stayed in TWRP recovery and never went back to normal. I tried wiping my phone several times and still won't go back. Then I pressed the option Change or Repair System File or something like that. But I put the wrong option on that menu and now it is completely stuck on the TWRP startup screen , I can't enter TWRP at all.
I tried everything that I possibly could. I even tried flashing a different version of TWRP and Philz Touch but still didn't budge. If y'all have any possible solutions, please speak up. My phone has been like this for about 6 days :crying:
I'm downloading the stock firmware of my model SM-G928F (G928FXXSBPIB). That's the only thing that I think that could possibly make it work. Do y'all think the same or is there something else I could do?
Go in download mode and flash that stock firmware that you downloaded.
Tahseen I said:
Go in download mode and flash that stock firmware that you downloaded.
Click to expand...
Click to collapse
Flashing the stock rom worked:victory:
Garxth said:
Flashing the stock rom worked:victory:
Click to expand...
Click to collapse
Ok so now if you want to root your phone. first install twrp and make sure oem is unlocked. Then when you boot into twrp make sure you dont select that option at the start otherwise you will keep booting into twrp continuously. Next flash cf auto root and then go back into twrp and enable that option that was disabled before you rooted your phone. You should be fully rooted with no errors.