So i got my brand new verizon Lg G2 Yesterday, straight from verizon. It came stock Running VS98012B, Build number JDQ39B, Android 4.2.2.
I ran it completely stock for a little bit, and loved it. But ima crack flasher, and cant run stock for long. So i decided to root. I Used ioroot24 With a few hiccups(ADB drivers wouldnt install with windows 7, So i had to boot into windows xp and do the process).
So im now running the same software with a completely functioning and full root. Next step was to install TWRP or Cwm(philz). I followed WACOmalts Guide.... with no success.
(http://forum.xda-developers.com/showthread.php?t=2449670) This one.
Option 1 Goes good until this step
"./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img"
It always says something failed (Not sure about the message Because i cant repeat it now) Or it gives me a list of commands, as if i typed "adb"
Option 2 I can follow completely through with no errors, But rebooting into recovery always brings me to a black screen.
Ive tried the 2.6.3.1 and the 2.6.3.2 .img files with so success. So i downloaded both 2.6.3.3 and 2.7.0.0 zips and extracted the recovery img and tried using those files. Still a black screen.
Option 3 Just dont work for me.
Has anyone Had his trouble before? Im not a huge noob, Ive had a optimus l9, galaxy nexus, and htc incredible 4g, All with working recoverys So im sure i have enough knowledge. Please Help!
s-chassis said:
So i got my brand new verizon Lg G2 Yesterday, straight from verizon. It came stock Running VS98012B, Build number JDQ39B, Android 4.2.2.
I ran it completely stock for a little bit, and loved it. But ima crack flasher, and cant run stock for long. So i decided to root. I Used ioroot24 With a few hiccups(ADB drivers wouldnt install with windows 7, So i had to boot into windows xp and do the process).
So im now running the same software with a completely functioning and full root. Next step was to install TWRP or Cwm(philz). I followed WACOmalts Guide.... with no success.
(http://forum.xda-developers.com/showthread.php?t=2449670) This one.
Option 1 Goes good until this step
"./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img"
It always says something failed (Not sure about the message Because i cant repeat it now) Or it gives me a list of commands, as if i typed "adb"
Option 2 I can follow completely through with no errors, But rebooting into recovery always brings me to a black screen.
Ive tried the 2.6.3.1 and the 2.6.3.2 .img files with so success. So i downloaded both 2.6.3.3 and 2.7.0.0 zips and extracted the recovery img and tried using those files. Still a black screen.
Option 3 Just dont work for me.
Has anyone Had his trouble before? Im not a huge noob, Ive had a optimus l9, galaxy nexus, and htc incredible 4g, All with working recoverys So im sure i have enough knowledge. Please Help!
Click to expand...
Click to collapse
Just ran into the same issue it doesn't seem like anyone has an answer for this yet, some from this thread http://forum.xda-developers.com/showthread.php?t=2584052
said they were able to just flash back to stock and do everything over and it worked but I was looking into to that but the KDZ method is apparently broken at the time and for the TOT method to restore I can't find a VS98012B (latest VZ firmware so far) TOT file to use for the restore so I don't break anything else.
I'll see what I can find and let me know if you find anything :good:
try Flashify app from the store :good:
Ok so "s-chassis" so being as persistent as I am:laugh:, I was able to find the stock recovery for VS98012B in another thread you can download it here:
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=193184686
Look at post #10
Then I used the dd method to flash the recovery, here it is if you forgot
adb push recovery_vs98012b.img /data/local/tmp/recovery_vs98012b.img
adb shell
(IF YOU DONT SEE A # prompt, type su to get it.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery_vs98012b.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
I got back to the stock recovery but the android has a red exclamation mark on it not sure why but if you have any ideas let me know
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!
I have the VZW LG G2 was running a stock rooted rom with CWM recovery. Accidentally accepted the OTA this morning and now my phone constantly boots into CWM. I have wiped everything, done fresh installs of stock rom, CM11, Gummy 4.4.1, and done a restore of the stock rooted rom but still boots straight into recovery. Any help would be awesome.
CoryFNM said:
I have the VZW LG G2 was running a stock rooted rom with CWM recovery. Accidentally accepted the OTA this morning and now my phone constantly boots into CWM. I have wiped everything, done fresh installs of stock rom, CM11, Gummy 4.4.1, and done a restore of the stock rooted rom but still boots straight into recovery. Any help would be awesome.
Click to expand...
Click to collapse
I think you have to go back to stock....use the thread in general forum ...back to stock....
CoryFNM said:
I have the VZW LG G2 was running a stock rooted rom with CWM recovery. Accidentally accepted the OTA this morning and now my phone constantly boots into CWM. I have wiped everything, done fresh installs of stock rom, CM11, Gummy 4.4.1, and done a restore of the stock rooted rom but still boots straight into recovery. Any help would be awesome.
Click to expand...
Click to collapse
So there's a Verizon OTA now as well? I thought I read it was for the AT&T variant and maybe T-Mobile.
Anyway, good luck solving your problem. I'll be keeping an eye on this thread as I've also got a Verizon G2.
Rodeojones said:
So there's a Verizon OTA now as well? I thought I read it was for the AT&T variant and maybe T-Mobile.
Anyway, good luck solving your problem. I'll be keeping an eye on this thread as I've also got a Verizon G2.
Click to expand...
Click to collapse
Yeah it showed up last night and I hit install later, which I guess it did automatically during the night. Should've just frozen Update in Rom Toolbox and not had to worry about it.
Anybody know if this thread http://forum.xda-developers.com/showthread.php?t=2451696 will work for CWM 6.0.4.4??
I really can't afford to mess this phone up with a hard brick. Just switched to VZW and she told me not to root cuz I would mess it up - can't let her be right lol.
Well it looks like I cannot get into download mode either. When I press the Vol + and plug it into a computer it still boots to CWM. I also assume that debugging is turned off because I cannot send commands via terminal. Cant find any threads on here that address this issue with CWM only TWRP. I had been using TWRP for so long too I want to kick my self for switching back to CWM! Would be an easy fix if CWM had terminal
Well I finally got it to work by using a linux computer. No Windows computer would recognize the phone and I tried four different computers.
I just installed the jdk the sdk then followed the directions on this page
http://forum.xda-developers.com/showthread.php?t=2451696
I hope that this might help someone else. If all else fails just run ubuntu from cd and do it that way no drivers no problems.
thanks for all the help.
CoryFNM said:
Well I finally got it to work by using a linux computer. No Windows computer would recognize the phone and I tried four different computers.
I just installed the jdk the sdk then followed the directions on this page
http://forum.xda-developers.com/showthread.php?t=2451696
I hope that this might help someone else. If all else fails just run ubuntu from cd and do it that way no drivers no problems.
thanks for all the help.
Click to expand...
Click to collapse
Ah man koush universal drivers prob would of worked
RubbleTea said:
Ah man koush universal drivers prob would of worked
Click to expand...
Click to collapse
I tried the koush drivers and it would show up as an android device but it still wouldnt let me push the commands via terminal. I've seen a lot of people with simular problems. I'm hoping that this thread will help someone.
I have a better idea to repair this problem.
1- You have to install LG Phone drivers and Android.sdk
2- Download TWRP for LG G2 and paste it to platform-tools folder in android.sdk direction on your PC
3- Go to recovery and plug the phone to PC
4- Next, in your phone recovery CWM you have to choose install zip and install.zip from sideload. Then wait for install the drivers of phone on your PC.
5- Open console in folder platform-tools (shift + PPM) and type adb sideload nameofTWRPfile.zip
6- Then reboot phone
7- Next enter to another time to recovery (now will be TWRP recovery)
8- Enter advanced and terminal console
9- Choose select and type the second option from this site: http://forum.xda-developers.com/showthread.php?t=2451696
10- Reboot phone
In my case is everything ok, but you have to remember that you can't install any OTA on custom ROM !
Sorry, but my english is not so good
thank you so much! This worked
tomajo2 said:
I have a better idea to repair this problem.
1- You have to install LG Phone drivers and Android.sdk
2- Download TWRP for LG G2 and paste it to platform-tools folder in android.sdk direction on your PC
3- Go to recovery and plug the phone to PC
4- Next, in your phone recovery CWM you have to choose install zip and install.zip from sideload. Then wait for install the drivers of phone on your PC.
5- Open console in folder platform-tools (shift + PPM) and type adb sideload nameofTWRPfile.zip
6- Then reboot phone
7- Next enter to another time to recovery (now will be TWRP recovery)
8- Enter advanced and terminal console
9- Choose select and type the second option from this site: http://forum.xda-developers.com/showthread.php?t=2451696
10- Reboot phone
In my case is everything ok, but you have to remember that you can't install any OTA on custom ROM !
Sorry, but my english is not so good
Click to expand...
Click to collapse
When I got my ATT G2 I rooted it, and installed TWRP custom Recovery. A week ago I got a system update notification, without thinking I updated the phone. It rebooted into TWRP recovery, and all I can do is navigate around the Recovery. I factory restored my phone, so I don't have SU, and I can't enter download mode. Any ideas on how I can fix my phone, or go about getting it replace?
SpectralFlames said:
When I got my ATT G2 I rooted it, and installed TWRP custom Recovery. A week ago I got a system update notification, without thinking I updated the phone. It rebooted into TWRP recovery, and all I can do is navigate around the Recovery. I factory restored my phone, so I don't have SU, and I can't enter download mode. Any ideas on how I can fix my phone, or go about getting it replace?
Click to expand...
Click to collapse
You could try pushing a rom to twrp from adb if your PC doesn't recognize try Koush universal drivers to make it recognize
RubbleTea said:
You could try pushing a rom to twrp from adb if your PC doesn't recognize try Koush universal drivers to make it recognize
Click to expand...
Click to collapse
Could you give me instructinos on how I would do that?
I was having the same issue after accidentally installing an update on my VZW G2. I tried evey solution for 9 hours with no luck including the Koush universal drivers. The only way I could get the phone to be recognized by any computer was to use ubuntu. Once I had the JDK and SDK installed I ran the commands from this tutorial - http://forum.xda-developers.com/showthread.php?t=2451696
I hope this helps someone out
if you dont have ubuntu installed on a computer you could always make a live cd and run it from that
CoryFNM said:
I was having the same issue after accidentally installing an update on my VZW G2. I tried evey solution for 9 hours with no luck including the Koush universal drivers. The only way I could get the phone to be recognized by any computer was to use ubuntu. Once I had the JDK and SDK installed I ran the commands from this tutorial - http://forum.xda-developers.com/showthread.php?t=2451696
I hope this helps someone out
if you dont have ubuntu installed on a computer you could always make a live cd and run it from that
Click to expand...
Click to collapse
MATE you saved my day...thanks so much....got the stock image back working again with the help of the command in the thread you where mentioning.
thanks once more.
best.
upage
So I am not sure what I did, but I was just trying to flash the Grievous ROM earlier and it would not work, just kept going to a black screen on start up even though I didn't get any errors when installing. I retardedly forgot to make a backup so I have nothing to go back to. I tried to go into download mode to restore through the LG tool, and amazingly somehow it now says my phone is a D802.
I can still get into recovery and download mode and haven't seen fastboot yet, but I can't get my computer to recognize my phone in adb or sideload while in the recovery menu... Not sure what to do. It sucks that this phone doesn't have removable SD.
Anyone got any ideas? I've looked through other threads of people who have had this problem and luckily(I think) I still haven't got to fastboot. I was thinking if I can just get the stock files on there I can flash it in TWRP without having to even use the LG Flashtool, but I am at a loss for how to get the stock ROM on my phone.
WHAT DO I DO?
Install the kernel for the d800. To hey your phone to be recognized in recovery you will need the proper drivers, try pdanet. Drivers
Sent from my LG-D800 using Tapatalk
Okay I successfully got adb to work in the TWRP menu with the pdanet drivers, and I pushed the stock rom .zip to my phone but it won't let me flash it. Where do I get just the stock kernel?
Nevermind, got the ATT stock rooted rom from scotts site to push and install, which still gave me a black screen but afterwards but made download mode work, so got it back to stock! YAY!
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.