Develop Bugs

[Q]Help With Getting passed the adb loop step

Every since the root method came out, I've been trying to root my phone for hours and hours and I haven't been able to. Since this is a problem for quite a few other users, I figured we should have a thread just for this problem since the rooting thread is over 30 pages long at this point.
My problem is that I see the device in offline mode for a few seconds, and after that it displays an empty list again.
What I'd like to know from people who managed to root their phones, if they had to try something different from the instructions to get passed the adb loop step where you have to catch the device in offline mode? What OS are you running (Win, Mac, Linux and x86 or x64)? How many times did you try?

I got past the loop by hitting ctrl c as soon as it detected the device it worked for me. it seems if you let the loop continue and you get device not connected you have to try again. I was able to get this to work consistently twice.
Getting the adb portion of this is what took me the longest in the rooting process.

Had your same problem on Ubuntu
Had same problem on windows 7 64 bit
UNTIL:
installed pda net - then htc sync, then removed android device driver, then installed the (r3) driver from android sdk... the update you can download through their program.
After that it worked like a charm first time.
my best advice is to start running the loop just before you click recovery from the boot loader screen.
Once you got it, theres no need to be quick with control C - it stays there.
- Faylix / local

the PDANET program seems to mess with the offline loop thing.
Once I closed it, it goes through just fine..
The only problem im having is that im getting a E:Failid to verify whole-file signature when i push the update.zip
And also I've used both Windows 7 64bit and XP 32bit to no avail...

My guess is its all about the drivers. I must have mine all mixed up. I am stuck in loop with no device found either. I will try one more time with pdanet off but Ive tried on a pc without it too anyways.
Someone really needs to write an indepth guide like the G1 because drivers arent even meantioned in the guide and I know its a big part of it especially if you have had other android devices before with sdk plus adb. One thing I do notice is all of us with the loop issue have touble with the device showing in device manager. It displays android 1.0 instead of mts or adb whatever it supposed to be. If your device isnt recognized from hboot it wont make the proper jump into recovery. Hence the loop issue. Can anyone with root ellaborate this a bit more?

@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped

shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
You are a godsend. Spent the last two hours trying to time this just right by doing Step 2 and 3 over and over and over. 5 minutes after reading this post - Hello, Clockwork.

Lol
shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
I was having some trouble to, I found something else that I was gonna add but it was only on my end... I didn't have the same problem rooting my wifes. I will watch this thread and if I see any more posts I will drop my piece. Im glad someone else could post this before I could.

shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
Thanks Man, I guess I was pressing the Enter button to fast...
Got past eveything except the "SU" it says "Permission Denied"
NM about this post for some reason it started working after I installed "Setcpu". Went in to Terminal emulator and it gives me the # just fine..
For some reason its just ADB that gives Permission Denied..

"Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root."
Make sure you run this or you wont get SU rights, this programs needs to be installed to allow the SU rights.

AngelsShadow said:
"Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root."
Make sure you run this or you wont get SU rights, this programs needs to be installed to allow the SU rights.
Click to expand...
Click to collapse
Thank you thank you....
I've been repeating myself over and over regarding this...
It's the Number 1 issue why people can't Root & Flash to the ENGINEER Build!!

Still a no go
Marvin,
I am still getting the two device OFFLINE showing after going into recovery from hboot. I deleted ALL of the HTC SYNC software and drivers and ONLY installed PDAnet. I now can see the MY TOUCH SLIDE device when connected in hboot, unfortunately I still am having the same stupid problem. So since it's not showing android 1.0 anymore and still having the same problems, we might have to explore some other avenues. FOR THE LOVE OF ROOT SOMEONE PLEASE HELP US!!!

If you run loop and go to recovery and only see the device offline a couple times then it goes away, I do not think it is a driver issue at that point. As someone in the root thread explained, the loop is simply trying to catch the device in ADB mode as it's going into recovery. And then, randomly, it will "stick" in ADB mode. Now, I am not sure if there is a difference between our devices for those of us having trouble getting the ADB mode to stick.

Ok, I'm giving up. I have tried this hundreds and hundreds of times. I know I've followed the instructions the correct way (I've seen the video and read countless forum posts). This simply cannot be done on my phone. I am going to take it to the store and try to exchange it, perhaps for a black one.
Does anyone else have any suggestions?

as i posted in the other thread i was having problems trying to get adb "stick" open when i went from the bootloader into recovery so i went into the file explorer and right clicked on my computer then went to manage devices then went to the driver tab then clicked on update driver right before i went into recovery and this is what finally worked for me. the purpose wasnt to change the driver the purpose was to trick my computer into keeping adb open

Re: Getting passed the adb loop step
I had to hit power on phone and enter on pc at almost the same time to get it working. Then I realized that after you reboot, it boots back to your normal phone not recovery and then adb devices it shows up.
-------------------------------------
Sent via the XDA Tapatalk App

Re: Getting passed the adb loop step
Ugh none of these tricks have worked for me.. Still Stuck .. Maybe it's a computer issue.. Guess ill try a friends computer..
-------------------------------------
Sent via the XDA Tapatalk App

Maybe/hopefully someone will find a different/easier way to root these for those of us stuck here. I've also tried, exhausting many many things, everything from timing of hitting loop/recovery, all the way to almost completely breaking the ADB driver on my PC. This is thoroughly frustrating the hell out of me.

By the way, add "ECHO OFF" (without the quotes) to the top of the batch file. It makes it easier to see when it reads out the offline devices.

Re: Getting passed the adb loop step
If you go to settings then pc connection . What seeting should it be? Drive , sync, or charge?
-------------------------------------
Sent via the XDA Tapatalk App

Wiped Phone Now Can't See SD Card On Lappy, PLEASE HELP

I used Team win Recovery Project to wipe my phone Galaxy Nexus, and now when I plug the phone in to the lappy it doesn't show the sd card. Freaking out here cause I can't copy over a zip file to flash a ROM... please help...

The GNEX doesn't have an actual sdcard, so when you wiped the phone i'm guessing you wiped the virtual sd card.
You will have to adb push a rom to your phone.
One the top of the first Q&A page jubakuba has a guide that has a panic section in it.
The guide also shows how to install adb/fastboot and gives you the commands.

try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy

xskordeal said:
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
Click to expand...
Click to collapse
sorry, complete DOLT here. Where would I input the command?

If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.

How to get to a MS-DOS prompt or Windows command line
TheDodgey said:
sorry, complete DOLT here. Where would I input the command?
Click to expand...
Click to collapse
Click Start.
Click Run.
Type cmd or command and press enter.

gpfnzl said:
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
Click to expand...
Click to collapse
ok, following your instructions, and the instructions of the link, I have install ADB and can use cmd, however when I type adb shell, I get an error returning "device not found"
I see a lot of threads stating to make sure usb debugging is on, it was before I wiped the phone, but obviously I cant get to any settings at the moment.
on the verge of crying now, and noone likes to see a grown man cry

FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!

LOL
Normally if you can't see your device listed you haven't installed the drivers correctly.(or the correct drivers)
Also you have to open a command prompt window in the same folder as fastboot.exe and adb.exe
To do this in Windows 7:
Click the windows start button (bottom left hand corner)
In the search bar at the bottom type: cmd
At the top of the search list you will see the program cmd.exe right click and copy it.
Paste it into the same folder that has fastboot.exe and adb.exe
Now you can open the cmd window and type the command:
adb devices
Hit ENTER and if you have installed drivers correctly, the serial number of your phone will be listed.
If not, uninstall the drivers, download a new set of drivers from jubakuba or efrants guide and reinstall.
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
TheDodgey said:
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
Click to expand...
Click to collapse
didn't need to change the name of the rom zip. Just needed to type the full name of the .zip file.
Good to see it worked, and the tears have stopped

[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL

I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050

This involves unnecessarily deleting the contents of the internal sdcard.
The following method works 99% of the time, albeit in linux only:
1: reboot into recovery & do a mount usb storage (no mount sdcard)
this will just present your internal storage as a mass storage device to the system
2: do a
fsck.vfat /dev/sdX or /dev/ubX (whatever it gets detected as) - you can find out via (dmesg|tail)
Analogically, you can fix your data partition if it got corrupted.
You need to do it from recovery since not all roms have the fsck binaries available:
from recovery (copy - paste, unless you know what you're doing):
umount /cache
for x in {2,3,5}, do fsck.ext4 -fyD /dev/block/mmcblk0p1$x;sync;done;clear;echo done

XsMagical said:
I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.

movadoevo8 said:
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.
Click to expand...
Click to collapse
what is your base number and hboot ?normally the sdcard thing is fixed long time ago

One-X-master said:
what is your base number and hboot ?normally the sdcard thing is fixed long time ago
Click to expand...
Click to collapse
How do i locate the Hboot number is that the serial# if so here it is HT265W300361

movadoevo8 said:
How do i locate the Hboot number is that the serial# if so here it is HT265W300361
Click to expand...
Click to collapse
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there

One-X-master said:
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there
Click to expand...
Click to collapse
hboot = 1.14.0002

movadoevo8 said:
hboot = 1.14.0002
Click to expand...
Click to collapse
do you have the one xl? try to update it to latest base

One-X-master said:
do you have the one xl? try to update it to latest base
Click to expand...
Click to collapse
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.

movadoevo8 said:
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.
Click to expand...
Click to collapse
can you not mount adb sideload and flash through that ?

I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2

markb63 said:
can you not mount adb sideload and flash through that ?
Click to expand...
Click to collapse
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
One-X-master said:
I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.

movadoevo8 said:
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.
Click to expand...
Click to collapse
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!

markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?

movadoevo8 said:
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?
Click to expand...
Click to collapse
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?

markb63 said:
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?
Click to expand...
Click to collapse
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.

movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours

movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2

One-X-master said:
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I'm setting this up on my windows 7 machine, now I think i had an issue once on win 8. Updates to follow, thanks.

markb63 said:
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours
Click to expand...
Click to collapse

[q] SOLVED: ADB ROM PUSH ERROR: DEVICE NOT FOUND

EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1

lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways

lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app

when i tried to push error device not found lol

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app

lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.

If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.

Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks

lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.

sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.

tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.

lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*

xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.

UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi

lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1

Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again

Help please,, I screwed up my Nexus

So I got myself a S4, & planned to give my wife the Nexus,, But I screwed up and, wiped EVERYTHING. Now I can't get my computer to recognize my phone to side load or install a ROM through adb. I feel like its the drivers won't install correctly. I've tried 2 different computers and am at a loss. I need help.. it just keeps saying ( I think it says) "hardware not installed correctly" :crying: anybody?

ttocsm said:
So I got myself a S4, & planned to give my wife the Nexus,, But I screwed up and, wiped EVERYTHING. Now I can't get my computer to recognize my phone to side load or install a ROM through adb. I feel like its the drivers won't install correctly. I've tried 2 different computers and am at a loss. I need help.. it just keeps saying ( I think it says) "hardware not installed correctly" :crying: anybody?
Click to expand...
Click to collapse
I had a similar situation yesterday with a failed 4.4 install on my Gnex and this is what worked for me, YMMV.
I installed the Minimal ADB package from here on my PC.
"adb devices" from within the ADB window showed my Gnex.
I downloaded the CM 10.2 Rom and placed the zip on the root c: of my PC for the shortest path to remember.
"adb push c:\'rom name' space '/sdcard/download' " to push the zip file to my Gnex. This can take a few seconds depending on the size of the zip.
Boot in recovery and flash the ROM zip.
Here's a link to an ADB guide

TCStehle said:
I had a similar situation yesterday with a failed 4.4 install on my Gnex and this is what worked for me, YMMV.
I installed the Minimal ADB package from here on my PC.
"adb devices" from within the ADB window showed my Gnex.
I downloaded the CM 10.2 Rom and placed the zip on the root c: of my PC for the shortest path to remember.
"adb push c:\'rom name' space '/sdcard/download' " to push the zip file to my Gnex. This can take a few seconds depending on the size of the zip.
Boot in recovery and flash the ROM zip.
Here's a link to an ADB guide
Click to expand...
Click to collapse
Thanks for your reply,, but I think I have adb installed correctly, but not sure about the drivers??
**************************************** UPDATE !!!! *******************************************
HOT DAMN!!! I got it.. I used wugs toolkit and was finally able to get my computer to recognize my Nexus.. I was about ready to skip this thing across the lake. I better make a back up before I screw with it to much more..