So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
I think it's getting a model information check fail in lg flashtool, ugh this sucks.
bova80 said:
So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
Click to expand...
Click to collapse
LOL, i just went through the same thing. I'll be posting a fix tonight I worked out with Scott.
"There is a "back door" method. This is why they updated TWRP by the way...
Download this: https://dl.dropboxusercontent.com/u/...with cmd.zip
Extract it to desktop. open the command.bat file.
Type "adb reboot recovery" then press enter. You need to keep doing this during the factory reset.
This assumes you have drivers installed. If you have no drivers installed for recovery mode then just select generic Google Nexus ADB drivers.
You kinda have to hammer the reboot recovery command. Its all timing... To hammer it... press the up arrow in the dos prompt and that will repeat the line. then press enter.
Keep doing it until you see it reboot to twrp and you should be able to sideload or load from storage.
It may take 10 or 15 minutes to get the exact right timing so dont give up.
And of course, this is all dependent upon you having the drivers already installed."
- Scott
For timing, you'll need to wait right when TWRP starts writing the script and start hammering it out. Timing is everything so when you see the TWRP screen starting hitting the up cursor and enter. It should load recovery. Don't bother using the tool, it won't work as it thinks your device is a D802 and won't be compatible with the dll. This will get you back to normal and from here you can just wipe and reinstall the rom again fresh with out losing media/data on the your drive.
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
MkV05 said:
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
Click to expand...
Click to collapse
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
SamsungGalaxyStig said:
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
Click to expand...
Click to collapse
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
ccmbr002 said:
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
Click to expand...
Click to collapse
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
so I got it right when it said teamwin to reboot but everytime it reboot it tried to run the script and would never actually go into twrp. att is sending me a new phone but I'm worried when I send this one back they'll get me for being rooted.
SamsungGalaxyStig said:
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
Click to expand...
Click to collapse
I just messaged him to double check - I don't have access to my phone for a few days (out of town) but if he hasn't responded by the time I get home I'll just go ahead and try it and post here if it works or not. Thanks again for sharing this file!
Got the file... and MANY THANKS!!! It allowed me to un-softbrick my G2 finally
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
updating partition details
Running boot script....
Finished running bootscript,
Processing AOSP recovery commands....
----Wiping Data Partition----
Wiping data without data/media...
Done.
Removing all files under '/cache'
---- data partition wipe complete!
Done processing script file
Click to expand...
Click to collapse
bova80 said:
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
Click to expand...
Click to collapse
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
SamsungGalaxyStig said:
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
Click to expand...
Click to collapse
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
bova80 said:
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
Click to expand...
Click to collapse
Are you constantly doing the adb recovery reboot? or once or twice?
SamsungGalaxyStig said:
Are you constantly doing the adb recovery reboot? or once or twice?
Click to expand...
Click to collapse
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
bova80 said:
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
Click to expand...
Click to collapse
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
SamsungGalaxyStig said:
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
Click to expand...
Click to collapse
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
bova80 said:
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
Click to expand...
Click to collapse
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
SamsungGalaxyStig said:
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
Click to expand...
Click to collapse
on a pc. when i go under device manager I think it says something like lg modem, I'll know for sure when I get home.
omg it finally worked! thanks, I eventually just gave up with the command prompt and it went in.
Related
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
First of all, there's no such thing as semi brick, there's brick or not. Try installing your Rom again..
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
dude, he cant back up if he cant access the homescreen. neither can he use rom manager..
cant use the hardware buttons to get into dl or recovery either... read op guys...
2010ngojo said:
[Q] Need help with semi/soft brick!
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
Click to expand...
Click to collapse
Do this bro... just tested it myself, works fine...
get adb installed on your computer, should already have it if your rooting but if not get it, youll find it in the stickied thread for informative links in the development section.
get a cmd prompt open on your computer and type in
>adb devices
let it start up deamon and it will tell you device not found, its ok.
now type and have ready...
>adb reboot recovery (do NOT press enter yet)
start your phone like normal. before its even finished with the boot up tmobile animation and the galaxy s (but after the plain vibrant text/picture) logo press enter. if it says error: device not found then wait all the way till galaxy s only you did it too early...
screen will go black and reboot into standard recovery... hope to goodness you had a working clockwork recovery installed and nandroid ready for this next part...
go down using your volume keys and select reinstall packages using the power key
now in clockwork recovery go down to nandroid
now go to restore
go to your earliest back up and restore it.
there you go.
I would start fresh get odin set up and reinstall the original rom at this point as something may still be corrupted, reroot, install latest clockworkmod, latest vibrant 9 rom (im using and see no bugs and runs better then the vibrant 6 rom i had) and DONT install the lag fix until the newest "TRUE" lag fix comes out with the new file system and kernel that JAC is working on and has almost ready.
good luck and pm me if any of these steps need further explanation.
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
iwillkillyou said:
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
hes just stated man that he cant even get into recovery, my guess is hes locked out using the volume up/down keys like many new phones are (which btw is a known defect, spend 10min on the phone with tmobile doing thier trouble shooting to show them it doesnt work and they send you a replacement..) sooooo I gave him a way to get into recovery without the buttons and not having to wait till he gets to a black screen where possibly its frozen and he cant use adb commands.
I was just making mention to you also that he cant even back stuff up NOW (hopefully he already archived all his apps and data) and hes better off starting fresh since hes getting problems using his current rom/lagfix....
Thanks for the quick reply p()()pypants, but i will have to try your method later. It's late and I have class (college) tomorrow, but i will post my results soon. Thank you again.
Edit 1:
Btw, is there a way to back up my current rom? Like the way rom manager back up roms? I know my current rom works before so that's why I want to back it up.
Edit 2:
Actually i did not use adb to root my phone, just used the one click method. So can you please give me more detailed instructions on how to install/use adb?
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
2010ngojo said:
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
Click to expand...
Click to collapse
Do you have the right drivers installed? You can check here: http://forum.xda-developers.com/showthread.php?t=728929
Another very stupid question, just to cover all bases - your phone is plugged into the computer, correct? When you install the new drivers, try plugging the phone into a different USB port on the computer than you've been using, so it will hopefully pick up the new drivers without much extra effort.
If that doesn't help, just keep trying the command while the phone boots up. Maybe you'll get lucky and it will work. Sorry I don't have any real solution for you :\
I'm fairly sure I have the right drivers, otherwise I wouldn't be able to root in the first place. Yes, the phone is plugged in also. I'll try a different USB port and see what happens...
Update: Trying different USB ports does not help.
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.
gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:
Didn't work Will try other method
Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Two options:
1. Flash a custom recovery using "fastboot flash recovery recovery.img", then boot into it and flash a ROM
2. Download the stock android images from the Google dev site and flash them using fastboot
nikonjunkie said:
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Click to expand...
Click to collapse
Download the 4.3 image HERE
Then, plug in your phone into your computer, boot into fastboot mode, extract the zip and run the flash-all.bat file (Or the .sh if your on a *nix/OSX computer). This will flash 4.3. If you don't want to loose your data, delete the userdata.img in the zip file before running the .bat/.sh file. Wipe cache in recovery, and it should boot.
Go into fastboot and download the stock image from Google.
Run the batch file it comes with and bam, you should be good to go
Sent from my Nexus 4 using xda app-developers app
nikonjunkie said:
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Click to expand...
Click to collapse
Once you see the Android laying on its back with a red triangle, press and hold power button and then press volume up once. That'll take you to the recovery options. At this point you must decide if you want to wipe data/factory reset (which will let you go past the X logo) because that'll wipe your device, all your data will be gone.
lopezk38 said:
Download the 4.3 image HERE
Then, plug in your phone into your computer, boot into fastboot mode, extract the zip and run the flash-all.bat file (Or the .sh if your on a *nix/OSX computer). This will flash 4.3. If you don't want to loose your data, delete the userdata.img in the zip file before running the .bat/.sh file. Wipe cache in recovery, and it should boot.
Click to expand...
Click to collapse
Do I need ADB installed? Have never needed it for any reason on this computer
The flash-all.bat file is giving me the error "fastboot is not recognized as an internal or external command" (am on Win 8)
Not sure if it's relevant, but I don't believe I have USB debugging enabled right now. It is 99% of the time, but of course right now I'm almost sure it's not. Am I screwed? My phone isn't showing up as a drive on my computer like it normally would. Thanks in advance!
nikonjunkie said:
Do I need ADB installed? Have never needed it for any reason on this computer
The flash-all.bat file is giving me the error "fastboot is not recognized as an internal or external command" (am on Win 8)
Not sure if it's relevant, but I don't believe I have USB debugging enabled right now. It is 99% of the time, but of course right now I'm almost sure it's not. Am I screwed? My phone isn't showing up as a drive on my computer like it normally would.
Click to expand...
Click to collapse
Yeah, you need fastboot.exe. I attached a copy from my Windows partition. Download it, extract it, and put the fastboot.exe in the same folder that you have the flash-all.bat
lopezk38 said:
Yeah, you need fastboot.exe. I attached a copy from my Windows partition. Download it, extract it, and put the fastboot.exe in the same folder that you have the flash-all.bat
Click to expand...
Click to collapse
Thanks. I downloaded the file from your link, extracted it, moved to the same folder I have the BAT file. Ran the BAT file, got this error:
The program can't start becayse AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
nikonjunkie said:
Thanks. I downloaded the file from your link, extracted it, moved to the same folder I have the BAT file. Ran the BAT file, got this error:
The program can't start becayse AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
Click to expand...
Click to collapse
Same thing that you did with the fastboot.zip with the attached ADB.zip
lopezk38 said:
Same thing that you did with the fastboot.zip with the attached ADB.zip
Click to expand...
Click to collapse
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
nikonjunkie said:
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
Click to expand...
Click to collapse
Your welcome
nikonjunkie said:
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
Click to expand...
Click to collapse
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
nikonjunkie said:
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
Click to expand...
Click to collapse
I have the similar problem here - OTA 4.3 finished ok, but I've lost my root. When I try to boot into recovery, I got "No command" (probably in english, it's in fact translated) and Android laying with open belly.
After rebooting, system itself works as normal.
Thanks for any help.
nikonjunkie said:
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
Click to expand...
Click to collapse
That's the stock recovery, press and hold power and then press volume up to get the stock menu
EddyOS said:
That's the stock recovery, press and hold power and then press volume up to get the stock menu
Click to expand...
Click to collapse
The open Android belly is *supposed* to show up? Wow, then I guess I've had a custom recovery so long I can't recall ever seeing this.
If I do that sequence, then I get the options:
- reboot system now
- apply update from ADB
- wipe data/factory reset
- wipe cash partition
If this is the stock recovery, then how do I go about getting a custom recovery on here? So far have been unsuccessful with sideloading anything via the toolkits. I'm now on 4.3, unrooted, but unlocked bootloader. I guess I was expecting the menu that permits you to flash a zip on the phone FROM the phone.
Thanks!
nikonjunkie said:
The open Android belly is *supposed* to show up? Wow, then I guess I've had a custom recovery so long I can't recall ever seeing this.
If I do that sequence, then I get the options:
- reboot system now
- apply update from ADB
- wipe data/factory reset
- wipe cash partition
If this is the stock recovery, then how do I go about getting a custom recovery on here? So far have been unsuccessful with sideloading anything via the toolkits. I'm now on 4.3, unrooted, but unlocked bootloader. I guess I was expecting the menu that permits you to flash a zip on the phone FROM the phone.
Thanks!
Click to expand...
Click to collapse
Download the latest TWRP version for Mako. Boot to bootloader. Open a CMD window and type:
fastboot flash recovery yourrecoveryname.img
Mercado_Negro said:
Download the latest TWRP version for Mako. Boot to bootloader. Open a CMD window and type:
fastboot flash recovery yourrecoveryname.img
Click to expand...
Click to collapse
J*sus C******. Now I can't even get the phone to be recognized as an ADB device. What happened since last night, I have no idea. The toolkits don't help, by any method. Have rebooted computer, phone, unchecked and rechecked USB debugging about a zillion times, uninstalled and reinstalled drivers. It's like the phone is invisible. Four more hours, and I am throwing this Nexus off the 23rd floor balcony.
Thanks, though!
nikonjunkie said:
J*sus C******. Now I can't even get the phone to be recognized as an ADB device. What happened since last night, I have no idea. The toolkits don't help, by any method. Have rebooted computer, phone, unchecked and rechecked USB debugging about a zillion times, uninstalled and reinstalled drivers. It's like the phone is invisible. Four more hours, and I am throwing this Nexus off the 23rd floor balcony.
Thanks, though!
Click to expand...
Click to collapse
When you connect your device via USB, does the computer recognize it and open up a window where you can see your files/folders?
Mercado_Negro said:
When you connect your device via USB, does the computer recognize it and open up a window where you can see your files/folders?
Click to expand...
Click to collapse
Sometimes it does, sometimes it doesn't. I can't figure out the inconsistency. Same things are checked. I've changed USB ports (tried all three), tried a new cable, quadruple-checked the settings. Rebooted the phone and the computer, and still it's inconsistent. I can hear the little chime on the computer indicating it's recognizing the device, but only half the time does it open the folder to view files. The other half of the time, the phone doesn't show up as a drive under My Computer at all--even after a refresh.
In a strange new dvelopment, in Wug's Nexus Root Toolkit, the phone is recognized in bootloader mode, but nothing on this green earth can make it show up as an ADB device when powered up and booted into Android. I've tried going at it from every angle. Didn't have this problem last night. Other than setting up email and moving icons around, I didn't do much to it, so I'm mystified and annoyed.
Thanks for any ideas.
Yeah, that's happened here as well. Sometimes I have to unplug and plug it back in to make it show folders and files. It's inconsistent as you say (though to be honest, I can't remember if it's happened again since I flashed 4.3 a week ago). Anyways, you say that adb can't see it when you type "adb devices", right? If you turn off your device (unplugged), then press and hold power and volume down buttons for a few seconds to go to Bootloader and then plug it back in, can you run any adb command? Like push, pull, etc.? That would rule out any faulty file in your platform-tools folder (where fastboot.exe is).
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
toopty said:
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
Click to expand...
Click to collapse
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
cgillie92 said:
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
Click to expand...
Click to collapse
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
toopty said:
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
Click to expand...
Click to collapse
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
cgillie92 said:
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
Click to expand...
Click to collapse
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
toopty said:
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
Click to expand...
Click to collapse
I hope someone helps us out. I really cant afford a new one because the warranty is void. I was going back to stock because of all of the little bugs that need to be ironed out in roms. cause kit kat is around the corner hopefully and my problem virtually is the same i might have had my brightness on auto or something prior to that.
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
After following the instructions on the above link i was able to get fastboot status on my phone. It did not fully restore my phone however. I was able to flash twrp via fastboot. I was then able to boot into twrp and run the command at this link via twrp terminal http://forum.xda-developers.com/showthread.php?t=2451696
Thanks to everyone for all your help.
toopty said:
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Click to expand...
Click to collapse
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
cgillie92 said:
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
Click to expand...
Click to collapse
Ignore all the message, unplug you phone get ready to type the command, plug it in and immediately press enter to run the command. it took some trial and error, and i had to use this other post to help me out. I actually got fastboot working first, then used this post to http://forum.xda-developers.com/showthread.php?t=2477595 to get download mode working, and to flash twrp recovery. After that i used this post to run the command line from with twrp. http://forum.xda-developers.com/showthread.php?t=2451696 . I didn't have to flash the factory tot to my phone, but i have that option now because download mode is working. This process will work, there is hope for you getting your phone back. I'm fully recovered. I decided 12B is not worth it in the mean time, but if you want 12B you need to flash the factory tot and then upgrade. There is a way to root 12B, but as of this time you are unable to get Custom Recovery on it.
As title states. I recently traded for this phone with a friend so I could use viper4android. He had already updated it. Is there anything I can do? Thanks internet.
You can still root on 12a. Download the .Kdz file
my_handle said:
You can still root on 12a. Download the .Kdz file
Click to expand...
Click to collapse
Thanks so much. I will try that again. I was just having issue with lg up.
If it's an issue with lgup not seeing the device try using the uppercut program like I did. https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Tzimmerman15243 said:
Thanks so much. I will try that again. I was just having issue with lg up.
Click to expand...
Click to collapse
my_handle said:
If it's an issue with lgup not seeing the device try using the uppercut program like I did. https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Click to expand...
Click to collapse
That worked great! Thanks so much! However, i am now having issues with Root/Twrp/Bootloader. I can make it through to installing twrp, but the device does not continue boot up past the Verizon logo and loading animation. I let it stay there vibrating for about 30 minutes. Haha
Tzimmerman15243 said:
That worked great! Thanks so much! However, i am now having issues with Root/Twrp/Bootloader. I can make it through to installing twrp, but the device does not continue boot up past the Verizon logo and loading animation. I let it stay there vibrating for about 30 minutes. Haha
Click to expand...
Click to collapse
What exactly have you done?
my_handle said:
What exactly have you done?
Click to expand...
Click to collapse
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.
Tzimmerman15243 said:
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.
Click to expand...
Click to collapse
If you're stuck where I think
*VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
my_handle said:
If you're stuck where I think
*VERIZON USERS******
It has come to my attention that some users have encountered abnormally long first boot time(over 20 minutes before first time setup)
To resolve this issue:
Boot into bootloader by pulling the battery and reinserting it and holding VOL- and phugging in the phone. then typing:
Code:
fastboot flash boot boot2.img
fastboot reboot
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
Click to expand...
Click to collapse
So i did try the first part. I flashed boot2 and it got me to the Password screen. The second part says to fix that by booting recovery (Twrp) and erasing the things correctly. I cant get into twrp or any sort of recovery. Not by adb (cant boot phone past password screen or verizon screen) or by button holding on power up. (just continues with boot up. I can get into fastboot mode and download mode.
I would try step 2..bat again if you still can't get it try reaching out to @me2151. He's the mad genius that got this and he's pretty good with helping those who are stuck
my_handle said:
I would try step 2..bat again if you still can't get it try reaching out to @me2151. He's the mad genius that got this and he's pretty good with helping those who are stuck
Click to expand...
Click to collapse
Thanks so much! I'm very new to posting. Is there some way I thank you? Like officially? haha
Tzimmerman15243 said:
Lets see..
I have followed the steps here multiple times.
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
If you are familiar, i get through step3 and it requires you to reboot to recovery via adb after start up, but it never starts up. I have tried flashing boot2.img as well to try it, but that gets me too a secure start up password thing I cant get past.
Also, in some directions i t says to enable OEM unlocking in developer settings. I am on Verizon and I do not have that option. Not sure if this is related? Just throwing that out there.
Click to expand...
Click to collapse
If you get to the secure start up password and you cannot get any further, you did not decrypt the phone by formatting the data and such.
nahepler90 said:
If you get to the secure start up password and you cannot get any further, you did not decrypt the phone by formatting the data and such.
Click to expand...
Click to collapse
Is decrypting something I need to do before getting into Twrp? I can't get into recovery.
Also, and this might be nothing, but it seemed to work in my case, but when you're in that rebooting step, make sure you're unplugged. Mine did the same, sat there for 20+ minutes vibrating away. I redid the steps but without it plugged in, and it went through. I've also noticed that on rebooting my phone (different ROM now but still), if I'm plugged into my computer, it'll go into vibrating and act quirky during the reboot, whereas if I'm not plugged into the USB, then it restarts normally.
Totally might be all coincidental, but if you haven't tried it that way, worth a shot.
Tzimmerman15243 said:
Is decrypting something I need to do before getting into Twrp? I can't get into recovery.
Click to expand...
Click to collapse
No the decrypting is done in twrp. Did you successfully install twrp through adb/fastboot?
CharlzO_2000 said:
Also, and this might be nothing, but it seemed to work in my case, but when you're in that rebooting step, make sure you're unplugged. Mine did the same, sat there for 20+ minutes vibrating away. I redid the steps but without it plugged in, and it went through. I've also noticed that on rebooting my phone (different ROM now but still), if I'm plugged into my computer, it'll go into vibrating and act quirky during the reboot, whereas if I'm not plugged into the USB, then it restarts normally.
Totally might be all coincidental, but if you haven't tried it that way, worth a shot.
Click to expand...
Click to collapse
Thanks for the reply! I have tried all sorts of booting with both Boot1 and boot2 img. Both unplugged and plugged in to no avail.
nahepler90 said:
No the decrypting is done in twrp. Did you successfully install twrp through adb/fastboot?
Click to expand...
Click to collapse
I think its installed? Haha. It goes through in fastboot as in fastboot flash recovery twrp.....blah blah.img
But, i have not been able to boot to it in any form.
Solved! I messaged @me2151 himself and he straightened me out. It is always the simplest things. I was trying to boot into recovery the incorrect way by way of not only releasing the power button. Thanks for all the friendly internet help. When I posted here, I had no idea there were so many great people out here behind the text. Thanks again!
Tzimmerman15243 said:
Solved! I messaged @me2151 himself and he straightened me out. It is always the simplest things. I was trying to boot into recovery the incorrect way by way of not only releasing the power button. Thanks for all the friendly internet help. When I posted here, I had no idea there were so many great people out here behind the text. Thanks again!
Click to expand...
Click to collapse
Sorry o didnt get back to you sooner. Glad you got it worked out! @me2151 helped me out getting root on my phone as well. Hes a good help
Glad you got it figured out. And I told you he was good about helping