Help!!!!! Urgent - Nexus 4 Q&A, Help & Troubleshooting

My friend has no operating system on his phone and he needs to put a software on his phone using team win recovery mount usb storage but his pc won't detect his device ? Would really appreciate some help any solutions
Also he has tried to flash stock and root option within the nexus root toolkit but this also gets stuck at bootloader stage as the computer does not know the device is connected.

Look for the drivers in one of the stickies and install them, then everything should work properly.

1. Mount usb wont work on the nexus 4, and it isnt meant to.
2. Dont use a toolkit
If you've got access to twrp this is what you need to do:
1. Setup adb: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
2. Install Koush's universal adb driver (google this for the download)
3. Put the phone into twrp
4. Download a rom on your pc and move it to your desktop. Rename it to "rom.zip".
5. Open a command prompt window and run the following commands:
Code:
adb devices
If your phones serial number shows up, continue. If not, reinstall drivers.
Code:
cd Desktop
adb push rom.zip /sdcard/
6. After its finished pushing, go to install within twrp and flash it.

Thank you it is working now
Sent from my HTC Desire X using xda app-developers app

waza97 said:
Thank you it is working now
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
Did you use my instructions, or did you just use a toolkit instead?

Your instructions thanks so much
Sent from my HTC Desire X using xda app-developers app

Related

[Q] ADB freezes when taping commands

I had to restore my Iconia, so i used the acer.Update.zip, then i flashed my system.img using connectbot directly from my tablet, then i did an hard-reset, now I need to push wifi modules.
I installed the android sdk and then i installed iconia drivers too on my Desktop PC running Windows Vista x32 (i know it sucks but right now i can't change os).
I run adb with the devices command and it recognizes my iconia, then i try to run any other command, as adb install C:\my.apk or adb shell and nothing happens...
If I try to close the shell it closes but the abd.exe process doesn't close even if I use the task manager, I have to reboot the PC.
Someone knows what to do, I yet googled but i haven't found anything...
excuse me for my bad english...
Well first off for your wifi modules you don't need adb any root file explorer will work. Put the modules on your SD card then copy them and go to system/lib/modules miunt the system as rw and paste them. Then reboot.
Sent from my PC36100 using XDA Premium App
The problem is that I haven't it and I can't install any apk without adb!
smaury said:
The problem is that I haven't it and I can't install any apk without adb!
Click to expand...
Click to collapse
Why can't you install apks without adb if your talking about gingerbreak just email it to yourself no adb required
Sent from my PC36100 using XDA Premium App
How can I download & install APKs if I haven't a filemanager and I can't connect to the internet?
Hmmmm. Well i would say restore with the Chinese update get a file.manager installed then flash your images that way your file.manager is installed I know.long work around but at work and don't have adb in front of me
Sent from my PC36100 using XDA Premium App
Is there a filemanager in the chinese update or at least wifi will work, i don't remember?
Yes Chinese has working wifi.
Sent from my PC36100 using XDA Premium App
Thank you i'll do that tonight!

[Solved) Need Help - I have formatted my Nex7 using TWRP

Hi,
I have been trying to educate myself by using TWRP (ver 2.3.2.1) and loading custom ROM's
I have used the format option in TWRP and now I can no long load or push any files to the SD card. I am able to use WegFresh Root Tool Kit (ver 1.6.1) and get to TWRP and to the bootloader (Android laying on it's back - chest open)
How do I re-create the proper file structure to be able to load ROM's once again. As an example..... "/system" is completely empty.
Thank you....
Update - The problem has been solved and it was due to the driver between my laptop and the Nex7. In Device Manager it was showing up as "Andriod Phone - Andriod Bootloader Interface" THIS WILL NOT WORK!
Your device manager has to say - "Android Phone - Android ADB Interface" for it to be able to push files to the Nex7
Thanks to all who helped me.
Have you reflashed your ROM of choice?
- Sent from my US Cellular SGS3
RMarkwald said:
Have you reflashed your ROM of choice?
- Sent from my US Cellular SGS3
Click to expand...
Click to collapse
Thank you for the reply. I am unable to push any ROM (zip file) using TWRP or adb push.....
When I use a DOS prompt and type - "adb push rom.zip /sdcard" I get a reply "error: device not found" It seems as thought I can't write any files to the sdcard since I formatted the sdcard. Is it a permission issue? How can I restore the proper file structure of the sdcard so that a rom can be pushed and loaded?
Thanks
Dekan54 said:
Thank you for the reply. I am unable to push any ROM (zip file) using TWRP or adb push.....
When I use a DOS prompt and type - "adb push rom.zip /sdcard" I get a reply "error: device not found" It seems as thought I can't write any files to the sdcard since I formatted the sdcard. Is it a permission issue? How can I restore the proper file structure of the sdcard so that a rom can be pushed and loaded?
Thanks
Click to expand...
Click to collapse
How does the device show up in Device Manager? I assume you're using Windows.
- Sent from my US Cellular SGS3
Yes - I am using Windows 8 (64bit)
In Device Manager it shows as "Andriod Phone - Andriod Bootloader Interface"
I have no OS on the NEX 7 so I can't turn "debug mode" on......
TWRP see the device id......
Thanks
Dekan54 said:
Yes - I am using Windows 8 (64bit)
In Device Manager it shows as "Andriod Phone - Andriod Bootloader Interface"
I have no OS on the NEX 7 so I can't turn "debug mode" on......
TWRP see the device id......
Thanks
Click to expand...
Click to collapse
I've heard that Win8 causes issues, specifically with fastboot flashing files. I've heard you can install the drivers and is recommended to turn off driver signing.
Debug mode only works when the device is booted in the OS, not recovery. Do you have access to another OS, like Linux or Win7? This may be easier to do.
- Sent from my US Cellular SGS3
I will fire up my old Win 7 laptop in the morning and give that go.....
Thank you for your help this evening.
Dekan54 said:
I will fire up my old Win 7 laptop in the morning and give that go.....
Thank you for your help this evening.
Click to expand...
Click to collapse
No problem! The reason I've suggested this is I've worked with someone for three hours and in the end it was Win8. Win7 worked in minutes.
Good luck! Post with an update!
- Sent from my US Cellular SGS3
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
And honestly, I'd flash to stock 4.2.1 from Google, re-root, flash recovery, then flash ROM of choice. With the latest version of Recovery of your choice you shouldn't run into this issue in the future.
- Sent from my US Cellular SGS3
if still not working reflash stock rom from google
Sent from my Nexus 7 using XDA Premium HD app
ngoralph said:
if still not working reflash stock rom from google
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I would love to reflash any rom.... (cwm 10, Google, etc....) but my NEX7 will not except (push) any files to it. If I could just get a rom.zip file over to it I could then load it via TWRP.
I am open to suggestions from anyone.
Thanks
RMarkwald said:
No problem! The reason I've suggested this is I've worked with someone for three hours and in the end it was Win8. Win7 worked in minutes.
Good luck! Post with an update!
- Sent from my US Cellular SGS3
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
And honestly, I'd flash to stock 4.2.1 from Google, re-root, flash recovery, then flash ROM of choice. With the latest version of Recovery of your choice you shouldn't run into this issue in the future.
- Sent from my US Cellular SGS3
Click to expand...
Click to collapse
Just an update....
I am getting the same results with Win7 OS that I was getting last night when you were helping me. My Nex7 is displayed in the device manager as - "Android Phone - Android Bootloader Interface" in Win7 just as it is in Win8.
I have been using Wegfresh's Nexus Root Toolkit (1.6.1). It will show me the device ID went I click the button - show device id. I am able to reboot into bootloader. I am able to boot into recovery and get to TWRP and navigate around.
If I could just get a stock or custom ROM file to the NEX7 I would be in good shape. But I am unable to "adb push" anything to the nex7.
I will be glad to go "step by step" to trouble shoot this with you.
Thanks
I've not mypc, so I can't help you step by step.
You can use the advanced options of the toolkit to flash a zip or use the sdk to use the adb sideload.
google will help you to found how use "adb sideload", as the option you can see in recovery.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Blackdragon77 said:
I've not mypc, so I can't help you step by step.
You can use the advanced options of the toolkit to flash a zip or use the sdk to use the adb sideload.
google will help you to found how use "adb sideload", as the option you can see in recovery.
Click to expand...
Click to collapse
Thank you for the reply. I have tried the "adb sideload" option in TWRP and it fails. I get the error - "error - device not found"
I welcome anyone who might have some idea's for me to try.
Thanks
Thy to see my edit upon how to run sideload.
You must not use the tookit, but you must install android sdk and use the true adb
Blackdragon77 said:
Thy to see my edit upon how to run sideload.
You must not use the tookit, but you must install android sdk and use the true adb
Click to expand...
Click to collapse
I will load the true adb sdk toolkit and give that a shot. Thank you for your help.
No problem! Tell me if that's the solution!
Inviato dal mio Nexus 7 con Tapatalk 2
I was having the same problem also. Correct me if I'm wrong, but I believe in Fastboot mode (Android laying on it's back - chest open), you cannot use adb. Here you can use Fastboot. Adb is use when in Recovery mode. Have you tried using fastboot.
Dekan54 said:
I would love to reflash any rom.... (cwm 10, Google, etc....) but my NEX7 will not except (push) any files to it. If I could just get a rom.zip file over to it I could then load it via TWRP.
I am open to suggestions from anyone.
Thanks
Click to expand...
Click to collapse
Do you connect your N7 with adb ? if yes, try the clockworkmod recovery v6.0.1.9 , it has a fuction very good to push rooms, it is the "instal zip from sideload"
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
Dekan54 said:
I will load the true adb sdk toolkit and give that a shot. Thank you for your help.
Click to expand...
Click to collapse
follow this videos :
1º How to Install ADB Drivers for Google Devices
http://www.youtube.com/watch?v=vUSRmtexmUo
2º How To Install ADB and Fastboot for Windows
http://www.youtube.com/watch?v=Yc4z-KYypgY
it worked for me
tabbiex said:
I was having the same problem also. Correct me if I'm wrong, but I believe in Fastboot mode (Android laying on it's back - chest open), you cannot use adb. Here you can use Fastboot. Adb is use when in Recovery mode. Have you tried using fastboot.
Click to expand...
Click to collapse
You are correct, the OP needs to go into recovery (TWRP recovery is fine) and use adb to push files to the device- you can't use adb from fastboot.
I have used exactly the same method myself as I was in exactly the same situation myself.
Of course the OP needs adb on his PC from the SDK as mentioned earlier in the thread.
Still having the same error after installing adb from the sdk on my Win7 computer. I also made sure I installed JAVA and downloader the updates for the adb sdk.
The error is still - "error - device not found"
When I use TWRP to look at the files on my Nex7 the following folders are present
cache
data
dev
proc
res
root
sbin
sdcard
sys
system
tmp
usb-otg
default.prop
fstab.grouper
fstab.qcom
init
init.rc
ueventd.goldfish.rc
ueventd.grouper.rc
uevent.rc
The folder "sdcard is empty except for a twrp folder....
Any other things I should try?
Thanks

[Q] How to push file using TWRP adb sideload and Nexus 4 Toolkits

Hi everybody
Today I've just messed up my phone by deleting all TWRP backups as well as ROM zip files on my N4 (haven't found out why i did it, hell!)
Now after wipe my current rom, I've totally in the middle of "NoRom"
I have TWRP, and Nexus 4 Toolkits installed on my PC. I think all drivers are installed correctly as well, since I used them to unlock bootloader and root my N4 before.
But i just cannot figure out how to "ADB sideload" zip file to my device in order to flash a new rom.
So please guild me to do this. Many thanks
Note: I read on TWRP page and they say that I have to enable adb sideload in TWRP on my N4 (of which i've done), then "From the command line, type adb sideload /path/to/rom.zip". From that point I cannot understand. How and where could I open the command line?
(sounds noobie but since downloading that Toolkits, I've got rid of pure ADB things, so now I don't have the sdk)
Thank you.
Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta
Spiralzz said:
Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK thank you, i'll try it
Back to the past when i got G1, i was familiar with sdk and adb thing. But as time passing by, i'm getting lazier and lazier lol, so i've almost forgotten those useful stuffs, just use some 1-click tools like the toolkits.
Help
Spiralzz said:
Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried sideload on my nexus 4 but it gives me this error...
"failed to write data 'protocol fault (no status)"
I have been trying to sideload cm 10.2 since my phone is stuck on the google boot logo...any ideas as to how to solve this problem?
Cheers beforehand!
close "adb.exe" in task manager
Help please. I've done the same thing as the OP. I do not know what to do next.
I am unable to mount the phone. I click on "Mount" from TWRP's main screen and nothing registers on my computer.
Under Advanced I am able to click on ADB Sideload but then the adb commands do not work to sideload a rom. I am able to use the command adb devices and that returns a response. I have also tried the adb push command to move the rom onto the phone with no response.
What should I do next?
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks that worked.
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hey bro it says device not found. what do i do?
---------- Post added at 09:46 PM ---------- Previous post was at 09:43 PM ----------
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.1.9 it didnt work for me it said device not found
---------- Post added at 10:37 PM ---------- Previous post was at 09:46 PM ----------
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hey Thank i got it working, but one thing i cant understand is i got in a boot loop cause install cm10.1.3 RC2 coming from cm 10.2 nightly version, i also flased gapp 4.2.2 assuming the rom was 4.2.2 that why. is this correct? i wanna go to cm10.1.3 RC2 current on 10.2 nightly how can i do this? which gapps should i install?
Do you have adb drivers installed?
What happens when you type
adb devices
In the command prompt
You should get the serial number of your phone, then next to it it should say recovery
If you have nothing listed then you have an issue with the drivers on your computer
Sent from my Nexus 4 using xda app-developers app
Hi,
I moved from slimbean build 8 (4.2.2) to Slimbean 5 (4.3)
After a couple of reboot the phone stucks an google screen, I tried to reflash the rom from twpr but nothing chaged.
If I try to sideload small files (like supersu) it works, with rom.zip files not..
I have "* failed to write data 'protocol fault (no status)' *" after some seconds.
If I try to use sideload from twpr home (2.6.0.0) adb doesn't work,
adb devices
List of devices attached
0076a0288a8c04be recovery
Cwm
Is it possible to do the same with Cwm instead of twrp? If so, how? Also, i have both twrp and cwm according to rom manager. How?
Thanks your a life saver!
Alex240188 said:
Do you have adb drivers installed?
What happens when you type
adb devices
In the command prompt
You should get the serial number of your phone, then next to it it should say recovery
If you have nothing listed then you have an issue with the drivers on your computer
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
HElp
Hi guys,
I had the same problem while trying to install a new rom and i got into a bootloop stuff.
I tried what its say before on this thread but my phone can't be found. what can i do ?
Excuse my english i'm French.
Thx for your help if somebody can help me.
i run adb push rom.zip /sdcard but it tells me: cannot stat 'rom.zip': No such file or directory
I know that my drivers are installed and i can see my device when i run adb devices. Thank you for any help i can get.
Jens_Karlsson said:
i run adb push rom.zip /sdcard but it tells me: cannot stat 'rom.zip': No such file or directory
I know that my drivers are installed and i can see my device when i run adb devices. Thank you for any help i can get.
Click to expand...
Click to collapse
being a noob at all of this, I am getting nowhere..... all I did so far was install android sdk. and put phone into sideload....
when I did adb push rom.zip /sdcard and it did some things?
then I do adb devices (in the cmd line of windows) and it gave me my serial number.... but what now?
I see nothing on the phone to load/install?
also: I type this: adb push rom.zip /sdcard
it says error closed.
Even i have been caught up with this same problem , and i found this thread which was pretty helpful
HTML:
http://forum.xda-developers.com/showthread.php?t=2318497
that saved my day !!
I have the same problem
I have the same issues. When i type adb devices in command prompt, I get
List of devices attached
(there are nothing under it) what should i to ? Help me please
Install http://koush.com/post/universal-adb-driver
Report back if still having issues.
help!!!!!
I get this but now what???
C:\adb> adb push rom.zip /sdcard
_
Nothing more and in my phones sd its the rom but failed when i tried to install it

Any way to sideload

I recently rooted my phone. I have not installed any ROMs because i love the stock rom so much but i decided to try one today. I didnt have my computer with me so i downloaded one today and rebooted into recovery. I saved my current rom and then wiped and accidently pressed Data, it asks if i want to wipe everything and i press back. I go to look at my downloads and they are all gone. I look for my backup i had JUST nandroid backed up and it was gone.
So there i am stuck. There is a thread for returning to Stock rom. Sure ok, but its a long process including the 2 gig download which is only uploading at 260mbit/s so another hour or 2.
I have tried sideloading a rom but it fails.
Any suggestions on how to get a rom onto the phone without booting it? I dont have a micro usb to sd card or i would have done that already =/
You need adb on the pc, connect, then in terminal or cmd
Code:
adb push ROM.zip /sdcard
Copying the zip to the folder with adb makes it easier and the above command correct, (of course replace ROM.zip with the actual name).
Sent from my Nexus 7 using Tapatalk
fr4nk1yn said:
You need adb on the pc, connect, then in terminal or cmd
Code:
adb push ROM.zip /sdcard
Copying the zip to the folder with adb makes it easier and the above command correct, (of course replace ROM.zip with the actual name).
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
via sideload or no?
No. Sideload could work, I don't remember the command off hand.
Adb push copies it to the internal memory then you flash through the menu normal.
Sent from my Nexus 7 using Tapatalk
fr4nk1yn said:
You need adb on the pc, connect, then in terminal or cmd
Code:
adb push ROM.zip /sdcard
Copying the zip to the folder with adb makes it easier and the above command correct, (of course replace ROM.zip with the actual name).
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I gave you thanks.
That seems to work. For anyone that gets into this situation where there are no roms in your phone and you have no way to transfer them. Boot into TWRP, do not use sideload. Just main screen. Device manager will show to be just "g2" and you need the driver. In the driver folder from http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869 driver section, update driver and browse to 64BitADB and choose androidandadb. It will then give you a list of options starting with Testing drivers, one that dates back to 2010 and another thats 2012. You want the one thats 2nd from the bottom called LG G2 verizon net adb or something like that. Works perfect and connects to adb.
If anyone truely needs this process i can break it down to specifics on how to get it to work. Thanks so much for your help fr4nk1yn!

stuck at circle

unlock bootloder,TWRP,super su, and I hane accidentally format it through TWRP now its not getting on just stuck on circle . in internal there is no data to flash and also not detecting adb or fastboot mode .
please help me
You'll need to get adb or fastboot working. Google 15 second adb drivers xda. Then adb push a rom on to your device while in recovery or side load a rom
Sent from my Nexus 5 using XDA Free mobile app
GS150R said:
unlock bootloder,TWRP,super su, and I hane accidentally format it through TWRP now its not getting on just stuck on circle . in internal there is no data to flash and also not detecting adb or fastboot mode .
please help me
Click to expand...
Click to collapse
Wipe your whole system via TWRP and restart into recovery. Connect your phone with your computer and check if your phone is recognized. Also check if you have install all necessary drivers.
jd1639 said:
You'll need to get adb or fastboot working. Google 15 second adb drivers xda. Then adb push a rom on to your device while in recovery or side load a rom
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
1) ADB is working .recovery mode is also working.
2) i have tried this adb sideload youtube video https://www.youtube.com/watch?v=CivvxcM1PCY.
3) when ever i was sliding abs sideload in TWRP
UPDATING PARTITION DETAILS...
E:STORAGE PARTATION "/TERP/BACKUP/004aef8c978b8659" not found
starting adb sideload feature...
4) by doing all above steps i am stuck at transferring ROM
GS150R said:
1) ADB is working .
2) i have tried this adb sideload youtube video https://www.youtube.com/watch?v=CivvxcM1PCY.
3) when ever i was sliding abs sideload in TWRP
UPDATING PARTITION DETAILS...
E:STORAGE PARTATION "/TERP/BACKUP/004aef8c978b8659" not found
starting adb sideload feature...
4) by doing all above steps i am stuck at transferring ROM
Click to expand...
Click to collapse
Rename the rom zip you're trying to flash to just rom.zip and put it on the root directory of your pc. Then open a command window in the folder your adb.exe is and run the command
adb push c:\rom.zip /sdcard/download
That'll put the rom on your device and you can then flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Rename the rom zip you're trying to flash to just rom.zip and put it on the root directory of your pc. Then open a command window in the folder your adb.exe is and run the command
adb push c:\rom.zip /sdcard/download
That'll put the rom on your device and you can then flash it in recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
thanks but not working . it behaves same as in screen shot
this might be help
using mskip tool kit
GS150R said:
thanks but not working . it behaves same as in screen shot
Click to expand...
Click to collapse
first use the command
adb devices
Does your device show up or do you get the same as you did before?
If it works use
adb push c:\rom.zip /sdcard/Download/rom.zip
jd1639 said:
first use the command
adb devices
Does your device show up or do you get the same as you did before?
If it works use
adb push c:\rom.zip /sdcard/Download/rom.zip
Click to expand...
Click to collapse
not working.
i am doing
1) open cmd from start run.
2) then type cd (copy address of platform tool in sdk)
3)adb devices it show device no.
4) adb push c:\rom.zip /sdcard/Download/rom.zip then some command run an stop .
GS150R said:
not working.
i am doing
1) open cmd from start run.
2) then type cd (copy address of platform tool in sdk)
3)adb devices it show device no.
4) adb push c:\rom.zip /sdcard/Download/rom.zip then some command run an stop .
Click to expand...
Click to collapse
If adb devices doesn't show a device then you don't have the usb drivers setup. Did you try the 15 second adb install I posted in one of my first posts? Just Google it
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If adb devices doesn't show a device then you don't have the usb drivers setup. Did you try the 15 second adb install I posted in one of my first posts? Just Google it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
15 sec adb works now he is showing my device.
but after push command it goes through long execution and stop same.
how i get into this situation
1) bootloder unlock,rooted,custom recovery ,
2) stock 4.4.4 running
3) then instead of flashing velocity rom I flash velocity gapp from TWRP.
4) reboot perform updating app and stuck.
5) then i have done "FORMAT DATA" in TWRP
6) AND STILL NOT BOOTING
GS150R said:
15 sec adb works now he is showing my device.
but after push command it goes through long execution and stop same.
Click to expand...
Click to collapse
Try a different usb port and cable. It will take a long time to push the rom, 5 to 10 minutes. It sounds like your usb connection is not good
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try a different usb port and cable. It will take a long time to push the rom, 5 to 10 minutes. It sounds like your usb connection is not good
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
not working :crying:
GS150R said:
not working :crying:
Click to expand...
Click to collapse
Boot into recovery and see if you can find the rom you pushed. If you do, flash it
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Boot into recovery and see if you can find the rom you pushed. If you do, flash it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
whenever i try to send a zip file it execute bunch of instruction and stop.
I have copied it in notepad take a look
GS150R said:
whenever i try to send a zip file it execute bunch of instruction and stop.
I have copied it in notepad take a look
Click to expand...
Click to collapse
This comes up if you try to execute a command adb doesn't know. Are you typing it in correctly?
Edit, I see the problem. You need a space after adb push c:\rom.zip. it should be adb push c:\rom.zip /sdcard....
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
This comes up if you try to execute a command adb doesn't know. Are you typing it in correctly?
Edit, I see the problem. You need a space after adb push c:\rom.zip. it should be adb push c:\rom.zip /sdcard....
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
By giving space it shows error:closed
GS150R said:
By giving space it shows error:closed
Click to expand...
Click to collapse
What error does it give? Everything must be typed correctly and the rom.zip must be on the root directory of your pc.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
What error does it give? Everything must be typed correctly and the rom.zip must be on the root directory of your pc.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
error is - error:closed and execution is terminated.
yes it is in the directory rom.zip

Categories

Resources