Database Users

[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] [CWM+ADB] Sideload stucks at 1%

Hey guys,
a mistake happend to me and i installed a wrong GAPPS,
now the ROM alerts "Android Keyboard (AOSP) crashed" every second.
I can't put a newer GAPPS on the phone using USB, because sending a file to the device doesn't run.
I don't know why, the drivers are installed and i can see the root of my phone, but can't copy files bigger than a few byte.
So i tried sideload.
I booted to recovery mode and selected adb sideload, and installed all windows drivers successfully.
But: When i try to copy the file like "adb sideload rom.zip", it stucks at 1%..
Anybody here who can help me? :/
Thanks!

matzen97 said:
Hey guys,
a mistake happend to me and i installed a wrong GAPPS,
now the ROM alerts "Android Keyboard (AOSP) crashed" every second.
I can't put a newer GAPPS on the phone using USB, because sending a file to the device doesn't run.
I don't know why, the drivers are installed and i can see the root of my phone, but can't copy files bigger than a few byte.
So i tried sideload.
I booted to recovery mode and selected adb sideload, and installed all windows drivers successfully.
But: When i try to copy the file like "adb sideload rom.zip", it stucks at 1%..
Anybody here who can help me? :/
Thanks!
Click to expand...
Click to collapse
Try using adb push.
adb push "Gapps path" data/media/0

abaaaabbbb63 said:
Try using adb push.
adb push "Gapps path" data/media/0
Click to expand...
Click to collapse
I get a "error:closed" error..

matzen97 said:
I get a "error:closed" error..
Click to expand...
Click to collapse
Don't know if you still need it or not...
Type in the following into the pc terminal when connected to the device via usb
adb kill-server
adb devices

Stuck on TWRP

Hi forum
I'm stock in TWRP after I flashed the SlimKat OS for the D802 on a too old recovery.
So I'm moving forward with ADB pushing a newer recovery.zip onto my phone but this is where I'm stuck. Although the command is very simple Windows 8 isnt recognizing the G2 even through I've installed root from this PC.
I guess my question is does anyone have a link for the very lg G2 driver when in TWRP mode? Apprently it's not the same as the one you use to root etc.
A million thanks for saving my day!

I found out I need to force Windows to recognize the driver as a LGE ADB device. Now I can push the file but I can't locate the file. What am I doing wrong?
adb push recovery.zip /sdcard/
The file is copied but I can't locate it on sdcard?

Haha I end up fixing my own issue. I just forgot to mount the DATA folder

Aaaannnd it worked. Thanks for looking either way

Wiped with no ROM on Internal storage

I have done this about 4 or 5 times before. I wipe the entire phone instead of just data and cache. Now I have nothing on the internal storage to install and the ROM is wiped. Heres what I have so far.
I downloaded ioroot10 to run adb. The driver seems to be the biggest issue. I can "adb reboot recovery" and I can also "adb sideload ROM.zip" but nothing happens.
Also, if I wipe the phone entirely, windows will pull up the internal storage. I can see twrp folder and such. I can even transfer small files, but when I try to transfer the ROM it says it is too large even though windows indicates it is 25g
Once before I had the correct driver installed that allowed me to sideload to TWRP and I could go into file explorer and see the file pop up, indicating it was transferring successfully. Waited about 20 minutes for it to finish and I was golden.
This time I am at a loss. Its been close to a year since I have recovered this phone and I cant seem to push the ROM to the phone.
Any help would be appreciated. The driver seems to be the biggest issue and running the LG_VZW_United_WHQL_v2.14.1 does not install the driver. I am forced to search for the driver. I have tried most and some will allow the phone to force reboot recovery and others will install and do nothing.
Some drivers:
adb sideload ROM.zip - error: cancel
Anyone have the exact driver I need for the phone that would be awesome.
Thanks for your time.

adb push romname.zip /sdcard/romname.zip

bender_007 said:
adb push romname.zip /sdcard/romname.zip
Click to expand...
Click to collapse
That looks familiar will try in a minute thanks alot

bender_007 said:
adb push romname.zip /sdcard/romname.zip
Click to expand...
Click to collapse
uswd the adb testing interface driver then it began transferring on first try
thanks again

If you have TWRP 2.8.4.0 installed, you can boot to recovery, then Mount -> Enable MTP and transfer files to the phone via USB connection to the computer.
Typos courtesy of my Blissful LG G2 (D803).

I deleted an important application on my rooted phone

Note: I'm new to XDA, so I've basically made no posts so far. I tried posting this under HTC Bolt/Evo 10, but since I have not made the 10 post threshold yet, I cannot post there, so I just made the post here. If this post needs to be relocated please let me know.
After rooting my phone (HTC Bolt), I foolishly deleted some bloatware applications without backing them up. One of them was TouchPal, a preinstalled keyboard app. I didn't think this would be much of a problem because I already had it disabled in settings and was using a separate keyboard app for other purposes.
However, when I restart my phone, it always asks me to type my pin and "decrypt" the phone. I'm not sure why it does this (previous cell phone didn't), but apparently (this is only a theory) it uses this keyboard application, so I can't actually type my PIN in to decrypt my phone.
I could be completely wrong, and I might have accidentally deleted some other important file from my phone, but either way, I don't know how to fix my phone right now.
I did a bit of research and found out I was supposed to flash a ROM onto my device. However, I don't think I can even connect my device to my computer because normally I would have to enable USB debugging and file transfers.
So basically: is there a way to connect my phone to my computer that would allow me to do whatever is necessary to let me access my phone again? (also should I be flashing a completely new ROM? I should still have everything on my phone except a couple bloatware applications, so is there an easier workaround?)
Update: I got my phone to connect to my PC by booting it in recovery mode. I'll delete this thread if I can successfully flash a ROM.

Hey!
You have already rooted your phone - perfekt!
Now you can start to your bootloader and from there you can flash a twrp recovery if you haven't yet.
If you didn't, there are many tutorials how to do: google: your phone flash custom recovery via fastboot mode
If you have done this - you can easily backup your data with twrp recovery (I think twrp is the best)
After you have done this you can make a full whipe of your system.
If you have done this maybe the failure isnt anymore, but now you have no code to unlock! If the app is still not there - go to apkmirror.com and download the app(there are even system apps). Or just google "xxx.apk download"
After this you can restore your data from twrp!
Summary:
1. Flash recovery. Via fastboot mode
2. Restore your data via recovery
3. Full Wipe
4. Restart
5. If app is still not there - search for APK and install
6. Reboot to recovery (e.g. volume up and home at starting phone, google...)
7. Restore data
8. Restart to system.
I don't know if this Is work, but it's worth to try.
If this don't work: you can transfer data from phone to PC via fastboot mode and then you can flash custom ROM or stock rom,...
I hope this works!
Greets
Ksa

Ksawerion said:
Hey!
You have already rooted your phone - perfekt!
Now you can start to your bootloader and from there you can flash a twrp recovery if you haven't yet.
If you didn't, there are many tutorials how to do: google: your phone flash custom recovery via fastboot mode
If you have done this - you can easily backup your data with twrp recovery (I think twrp is the best)
After you have done this you can make a full whipe of your system.
If you have done this maybe the failure isnt anymore, but now you have no code to unlock! If the app is still not there - go to apkmirror.com and download the app(there are even system apps). Or just google "xxx.apk download"
After this you can restore your data from twrp!
Summary:
1. Flash recovery. Via fastboot mode
2. Restore your data via recovery
3. Full Wipe
4. Restart
5. If app is still not there - search for APK and install
6. Reboot to recovery (e.g. volume up and home at starting phone, google...)
7. Restore data
8. Restart to system.
I don't know if this Is work, but it's worth to try.
If this don't work: you can transfer data from phone to PC via fastboot mode and then you can flash custom ROM or stock rom,...
I hope this works!
Greets
Ksa
Click to expand...
Click to collapse
Thanks for the reply. How would I install the apk onto my device?

ztcfrank123 said:
Thanks for the reply. How would I install the apk onto my device?
Click to expand...
Click to collapse
I remember an easier way.
Maybe you can install app via ADB in recovery mode.
Therefore you need:
custom recovery
ADB tools installed on your PC
USB Driver installed
The APK downloaded from here: https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=TouchPal
If you have done this - reboot to recovery.
Navigate on your PC to the adb tools folder where adb.exe is in it. Open CMD with right click on address line.
Then write in CMD:
adb devices
If your phone is found, adb commands are working.
Then copy the APK in the folder where adb.exe is in it.
Type in CMD:
adb push xxx.apk /system/app(the address where you delete apk)
So maybe this works
So first check:
- custom recovery flashed?
- adb tools installed?
- USB driver installed?
If you have further questions, let me know.
KSA

Ksawerion said:
Type in CMD:
adb push xxx.apk /system/app(the address where you delete apk)
Click to expand...
Click to collapse
How would I find out the address where I deleted the apk? I already had adb, USB drivers, and custom recovery installed.

ztcfrank123 said:
How would I find out the address where I deleted the apk? I already had adb, USB drivers, and custom recovery installed.
Click to expand...
Click to collapse
How did you delete the files?
Nice, then boot into recovery start CMD where you adb is installed and write" adb devices"
Do you see your device?

Ksawerion said:
How did you delete the files?
Nice, then boot into recovery start CMD where you adb is installed and write" adb devices"
Do you see your device?
Click to expand...
Click to collapse
The files were deleted within the phone itself through Titanium Backup, so I have no idea where the file location is. As of now, I can adb push the apk, but I don't know where to push it to.

ztcfrank123 said:
The files were deleted within the phone itself through Titanium Backup, so I have no idea where the file location is. As of now, I can adb push the apk, but I don't know where to push it to.
Click to expand...
Click to collapse
The now try:
adb remount
adb push Xxx.apk /system/app
adb shell chmod 644 /system/app/xxx.apk
adb reboot

Ksawerion said:
The now try:
adb remount
adb push Xxx.apk /system/app
adb shell chmod 644 /system/app/xxx.apk
adb reboot
Click to expand...
Click to collapse
Sorry for the late reply.
The command "adb shell chmod 644 /system/app/xxx.apk" doesn't work for some reason. It says it is not a directory. (I changed the name from xxx to the actual apk name by the way)

ztcfrank123 said:
Sorry for the late reply.
The command "adb shell chmod 644 /system/app/xxx.apk" doesn't work for some reason. It says it is not a directory. (I changed the name from xxx to the actual apk name by the way)
Click to expand...
Click to collapse
Okay then forget this command and only try 'adb push' command, and restart phone maybe it works. Merry Christmas bre

Ksawerion said:
Okay then forget this command and only try 'adb push' command, and restart phone maybe it works. Merry Christmas bre
Click to expand...
Click to collapse
Yeah... I already tried that. Also I tried a bunch of other adb commands like deleting the file and it couldn't find the directory either .
Merry Christmas to you too!

ztcfrank123 said:
Yeah... I already tried that. Also I tried a bunch of other adb commands like deleting the file and it couldn't find the directory either .
Merry Christmas to you too!
Click to expand...
Click to collapse
Was pushing successful? What says CMD after 'adb push'?