Related
I followed the instructions from here ( http://forum.xda-developers.com/showthread.php?t=743769 ) up until flashing the actual zip and forgot I put the zip on my external sdcard rather than "internal" sdcard. Now my phone won't get past the initial white Samsung Vibrant screen. Also, I can only get into stock recovery. After clicking "reinstall packages" it just reboots and brings me back to stock recovery. Please help. Thank you.
You will need to flash back to stock then you will have access to your phone again.. you will have to start over to flash that rom. after you flash back to stock using odin
use this thread
http://forum.xda-developers.com/showthread.php?t=734475
You will need the right windows drivers so Odin will see your phone pick them up here.
Windows 64bit
Windows 32bit
Directions posted by setzer715
1. Put your phone in download mode by plugging it in and then holding Vol Up+Down and Power. As SOON as the screen goes black release power but NOT Vol Up+Down.
2. Launch Odin
3. Unplug your phone.
4. Load the pit and pda files into odin.
5. Plug your phone back in. You should now see one of the small blocks turn yellow and show you the com port. If not, something is wrong with your drivers.
6. Click start. If it flashes, great. If it hangs at File analasys then repeat 1-5.
6a. If Odin hangs at cache.rfs then move on to 6b.
6b. Unplug your phone (Odin will say it was removed) and remove the battery. DO NOT SHUT DOWN ODIN!!!!!!
6c. Put the battery back in and plug it back into your computer and put it back into download mode using step 1.
6d. Press start on Odin and it should now flash.
Also if you continue to hang at cache.rfs I found that if you delete s1_odin_20100512.pit then copy a new copy of the file over to your odin directory it seems to work fine after that.
Damn it.Thanks....
vol dn+up should get you to the stock recovery util right? the yellow and blue one?
edit: nvm, scare is over lol
On step 6d, where it says to press start again on odin, odin does not let me do this. The start, reset, pit, pda, etc... buttons are grey and will not let me press them. Help!
EDIT: also gives me a message in the upper left corner that says "CACHE" if that helps (in the far upper left box above where the yellow COM3 thing was.
bumpbumpbump
$iMoney said:
On step 6d, where it says to press start again on odin, odin does not let me do this. The start, reset, pit, pda, etc... buttons are grey and will not let me press them. Help!
EDIT: also gives me a message in the upper left corner that says "CACHE" if that helps (in the far upper left box above where the yellow COM3 thing was.
Click to expand...
Click to collapse
You need to delete your s1_odin_20100512.pit file and then extract a new copy to the odin folder then flash again. happened to me and that is all I did to fix it. step 6d did not work for me has well.
Hmmmm it's still not working. Would it help if i made a video showing what i'm doing then you can look it over and tell me if I'm doing something incorrectly? Also maybe I should be more clear. There is no way for me to start the flash again after removing my device as per step 6 without having to completely restart odin, thus restarting the process.
Update: Still not working. Really need a fix for this. Is there another way to un-brick my phone?
EDIT: To clarify, my problem was getting stuck as Cache.rfs and never going past that. I did try the previous steps listed in this article, as well as trying to reinstall all drivers and even using different Odin copies from other threads (even though they were all the same Odin 3). No .pit file seemed to work for me. Also, I'd like to point out that I have this issue with my netbook, but my work computer where I've done all my Odin flashing before did not have this issue, and I could use the .pit files perfectly fine.
First off, I'm not anyone special (I guess depends on the meaning of special), I don't dev... I play around. That's all. So take this all with a grain of salt.
I had the same issue, and have spent all night trying to fix it. Just now I didn't use the .pit file at all. Just the .tar in the PDA slot. Immediately went through and reflashed everything and I am fully up and running.
I can't guarantee that I don't have some kind of issues now but I am now back at my home screen and the phone seems to be operating fine.
The files I used are as follows:
Stock 2.1 firmware for the Vibrant: http://forum.xda-developers.com/showthread.php?t=739091
Samsung studio 7 (seemed to get Odin to recognize the phone without having to disconnect and reconnect, thought it might have something to do with the issue, though not sure): http://www.4shared.com/file/117435710/3d286573/Samsung_PC_Studio_72249.html
And the Samsung USB Drivers: http://forum.xda-developers.com/showthread.php?t=728929
Now, if a real dev can tell us what happens when you don't use the .pit file, we can know if there is any longterm repercussion from this. Short term though, working like a dream. I hope this helps, because being stuck without a working Vibrant sucks!
ODIN is a pain but I've found a way to get it work pretty consistently for me. Whenever you flash a ROM or back to stock, always make sure you enable USB debugging, and have adb working on your computer.
Open up your command console, plug in your device, open up ODIN, and type "adb reboot download". ODIN should recognize your phone when it restarts and a COM will light up.
From my experience, ODIN recognizes the devices better this way and hasn't hung for me so far (granted it's only 3 times). When I was booting into download manually and then plugging in the USB, it would hang at cache.rfs. If you don't have USB debugging enabled, then only thing you can do is keep retrying over and over. Took me like 15 tries once before it finally ran.
Can't thank you guys enough. Phone is back to normal! As soon as I didn't use the pit file it worked like a charm.
hey...i'm in the same situation as you...i can't get it to work...i'm trying to do just the tar file right now but it still hangs on cache.rfs how long did you have to wait?
$iMoney said:
Can't thank you guys enough. Phone is back to normal! As soon as I didn't use the pit file it worked like a charm.
Click to expand...
Click to collapse
which firmware did you use? did you use the true stck 2.1 firmware?
tq745 said:
hey...i'm in the same situation as you...i can't get it to work...i'm trying to do just the tar file right now but it still hangs on cache.rfs how long did you have to wait?
Click to expand...
Click to collapse
It should go right away. If it's hanging at cache.rfs, then it's not working. I really think its a drivers issue with ODIN. Just keep restarting your phone and ODIN and retrying.
I used the tar file that is linked to from the second post on this thread. I didn't even download what you linked me to, I just didn't use the pit file, like you told me and it worked with the files I already had.
My phone will absolutely not go into download mode. Is this a sign of some other problem or am i just out of luck?
ahhduy said:
My phone will absolutely not go into download mode. Is this a sign of some other problem or am i just out of luck?
Click to expand...
Click to collapse
how are you trying to get into download mode?
skater4690 said:
how are you trying to get into download mode?
Click to expand...
Click to collapse
Holding down + power when turning on, tried other varients like volume up instead of down, usb connected or usb not connected etc.
ahhduy said:
Holding down + power when turning on, tried other varients like volume up instead of down, usb connected or usb not connected etc.
Click to expand...
Click to collapse
ok try this...
1)plug into a usb with power
2)wait for the battery to show up
3)hold power and both volume buttons
4)wait for the vibrant screen to flash twice it will go once then seem like it turns off but then pops up agian
5)after it turns off the second time release the power button but still hold the volume buttons and you should be in download mode now
REMEMBER TO HAVE THE USB PLUGGED INTO THE COMPUTER AND YOUR PHONE!!!
Ok, before I get flamed, I did search (and search and search and search)...
Here's the back story. I have a VZW Galaxy Tab, and I was running OldMacNut's Honeycomb alpha on my tab... I wanted to be able to use 3G, so I wanted to use another ROM, so I attempted to flash one through recovery. It failed everytime I tried, so I went back to Heimdall and did a clean original stock download, and everything went wonderful...
Me, not being able to leave the damn thing alone figured I would root it, and then throw CWM back onto it, then install the GB rooted ROM on... Well, when I ran CWM it converted the the file extention, and when it went to reboot, it just boot looped.
So I held the power button down, and shut it down. I had it plugged into the charger and walked away from it for a few minutes to take care of something else, and when I came back to it, the sceen showed the battery icon like it was charging, but a multi-lined circle in the middle of the battery, and the green moving part of the battery wasn't working like I have seen on the Galaxy S devices...
I went to try to turn it back on, and nothing happened, so I researched some, and left well enough alone and let it charge.
Now, the battery icon isn't even on the screen, and the screen stays black all the time.... No matter any combination of buttons or screen holds I do, it isn't turning back on now, even while it is plugged directly into the wall.
I'm at a lost.
Any help would be AWESOME!!!!
THANKS IN ADVANCE!!!!!
EDIT: I let the Tab sit for a LONG time, and I got the battery icon thing back... Still afraid to try anything else atm.
PLEASE PLEASE HALP!!!!!
Can you get to download mode?
Tabulous said:
Can you get to download mode?
Click to expand...
Click to collapse
That's the issue... I can't. I've tried and tried. I left the tab plugged in overnight, so I'm hoping that it at least is fully charged now, so I can try to mess with it today some.
here's what you should do. let's start from the very beginning.
1. download heimdall. get it here: http://forum.xda-developers.com/showthread.php?t=755265
2. download the stock verizon files. get them here: http://www.blackmugmedia.com/Android...n/VZW Stock/
you need all four files.
3. download the drivers for the samsung sch-i800. find those here: http://downloadcenter.samsung.com/co...v1.3.350.0.exe
4. unzip heimdall. go into the drivers folder, and run zadig.exe. at the top, select 'list all devices'. go to the dropdown menu, and select Samsung Composite USB (i'm pretty sure that's what it was called.) click start, and let it run.
5. open the heimdall front end.
6. put system in system (if you're flashing to ec02, then put factory in system) put cache into cache put param into param put the zimage into both the kernel and recovery slots.
7. turn your tab off, and plug it into the computer using USB. hold down the power and the volume down buttons until you see the little droid dude with a shovel.
8. click the start button on heimdall.
9. wait for the flash to complete (don't unplug your device, obviously, during the flashing.) once your phone reboots, it's okay to unplug it.
10. now, boot into the stock recovery, and wipe data and cache. update to ec02
11. enable usb debugging.
12. plug your phone back in to the computer.
13. now run superoneclick for root. get that here: http://forum.xda-developers.com/showthread.php?t=803682
14. either play with it in stock, or go find oldmacnut's excellent Better Than Life Rom, and follow the instructions to flash that.
15. enjoy your tab!
Hit me on the thanks button if you find it useful ; )
Sent from my Galaxy Tab using xda premium
That's good advice for some people infinity, but as detailed in the immediately prior post, the OP cannot access Download Mode, rendering your instructions unworkable. Without either Recovery or Download modes, there's not much you can do unless you're willing to try the UnBrickable Mod (search for it).
Hope that helps.
THIS WILL BE USING THE CM 7.1 ROM. IT WORKS WITH OTHER ROMS TOO. JUST FOLLOW SAME PROCEDURE WITH YOUR ROM.
INTRODUCTION AND WARNINGS:
If you have an Evo 4g updated to android 2.3.5 with hboot 2.18.0001 and your wifi always randomly disconnects this guide is for you! The reason the server disconnects is because your router could be incompatible with your HTC phone. If it's just because of some wifi problems and some easy fixes could be made, I would go with that. But for those who have the same problem, not only will you get a cool Cyanogenmod 7.1 look... you'll be able to play PL with wifi.
I'll try to make it as easy to understand as possible... as I'm not good with this stuff either and it took time to understand the guides. Actually I used several guides but I'll kind of combine them.
This guide is for flashing Cyanogenmod 7.1 and what to do before. I am not responsible if there are any problems with your device. Use this guide at your own risk, although there's 99.99999% chance everything will go right if you follow the guide.
PART ONE:
First you'll want to install this file, you need winrar. Just unzip onto desktop so it's easier. You won't actually be using the tool but the root folder. Read the xda first post first though... http://forum.xda-developers.com/show...75&postcount=1
Here's link to download if you've read the post:
http://goo-inside.me/apps/frigid/
Then you'll want to go to www.htcdev.com.
You'll have to register there and use a real email address.
After you register login and click unlock boot loader. Where there's a scroll-down, choose "all other supported models"
Then click get started, the site will guide you through the next steps. Remember, this could void your warranty, I'm pretty sure there is a way to undo this all but remember do this at your own risk.
Tips: If you can't navigate to the right place remember to type "cd [insert name of root folder]"
To get the address, just go to root folder and click copy address at the top. (Right click on where it shows what folder you're in)
After you have successfully unlocked your boot loader you are ready for part 2.
PART TWO:
Enter fast boot on your phone again.
If you closed your command prompt, (which is fine) open it again.
Download this file and save it:
http://files.androidspin.com/downlo...ECOVERY/&file=recovery-RA-supersonic-v2.3.img
The file should appear in downloads.
Move the file into your folder titled root.
If the file is not named recovery rename it to that.
In your command prompt go the the root folder address like you did in part one.
Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)
Once the prompt finishes the command, go back to main boot loader screen. Then use the volume keys to go down to select recovery.
Press the power button to select recovery.
Once the recovery boots on your phone, select use the volume keys to select/highlight USB MS then press the power button.
Take this zip (don't unzip it) and place it into your sd card (just the root, not in any folders).
Zip: http://download.cyanogenmod.com/get/...nic-signed.zip
Press the power button to exit USB MS.
Now go back to main screen of recovery.
Highlight/select the choice flash zip from sd card and press the power button.
Select/highlight the zip you put in your sd card and press the power button to flash.
Press the power button again to confirm.
Once it's done flashing reboot your phone.
If your phone goes into boot loop (keeps rebooting at cyanogen logo thing) then go to your recovery again and select wipe and select wipe all data/factory reset.
OPTIONAL PART 2.5:
If you're looking for Google apps you might want to flash this too, same thing with the Cyanogen ROM, flash it same way.
http://cmw.22aaf3.com/gapps/gapps-gb...828-signed.zip
This working for everyone?
Do people actually read this? Did I post in wrong section?
Guide updated v1.1
Fixed link to Amon Ra Recovery. Last link worked but file was deleted.
Hey man, I have no need for the guide , but much thanks, sincerely. Thanks
sent from AOKP heaven
Ok... I guess...
so does using that htc super tool folder instead of android sdx not wipe everything while unlocking? Or does it still do a factory reset when you unlock?
Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.
BigPimpin said:
Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.
Click to expand...
Click to collapse
have to take it out of disk drive mode i believe and put it in charge only
evo4gnoob said:
have to take it out of disk drive mode i believe and put it in charge only
Click to expand...
Click to collapse
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"
BigPimpin said:
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"
Click to expand...
Click to collapse
when i did it to my phone i had it in charge only
This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.
Tried disk drive on and off a couple times and still getting stuck on the red exclamation.
BigPimpin said:
This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.
Click to expand...
Click to collapse
Recovery just puts a base place where you can flash roms and stuff.
And if you get a bootloop on CM7.1 yes you will have to wipe all.
As for the recovery flash problem, try putting it on charge only and usb debugging. Then power off phone or just take out battery and reboot into bootloader. Go into fastboot again and try to flash recovery on again. Then try it.
Did you rename the recovery img to recovery? Or if it's not saved as recovery.img rename it to that.
I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.
BigPimpin said:
I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.
Click to expand...
Click to collapse
When you go to the bootloader it scans for a PC36IMG.zip file. Normally if you were s-off that's how you would flash a recovery. Since your s-on unlocked the only thing that can be flashed in PC36IMG.zip format is a file signed by HTC like a RUU
Sent from my swiper using XDA App
I got a chance to see some of the names of the missing files it lists when going into boot load. The PC36IMG.zip is one of them that says no image. So guessing that file isn't even there at all. I searched for a PC36IMG.zip file and put it in there and got more then I have seeme before on that screen. I had a blue progress meter on the right side. When it got done it said something about being too old and unsuccessful.
Also, I tried starting all over, even going into the htcdev site again. When I did that all the step worked, but when it's supposed to get to the screen where it tells you it will wipe your phone, that screen never comes up. Now I'm wondering if I can just start all the way over. Can I go into my phone and of I select factory reset, will it make the phone a totally stock phone again and change anything I might have changed? Not that I'm sure I have even changed anything at all to this point.
Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?
BigPimpin said:
Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?
Click to expand...
Click to collapse
it shouldnt find a PC36IMG.zip file or the other. Only files in that can be flashed in that format is radios hboots splash screen RUUs recoveries. You shouldnt go around just flashing random things in the bootloader you can end up bricking your phone
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).
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.