Database Info

Help tf101g

hello peopleI need your help without any information someone deleted all my files tf101g
TF101G entering recovery mode with cwm
cwm 5.5.0.4 but this does not allow me to upgrade from external sd card. I tried to flash from w7 with some programs, wheelie, nvflash, tubuntu, oneclickrecovery among others.
adb shell
exec ' system bin sh' failed no such file or directory 2
pushing something. permission denied
NVFLASH
rcm version 0x4 command send failed (usb write failed)
can someone help me

Since you have a TF101G, NVFlash is not an option.
Does your device show up as an ADB device in windows when you boot to recovery?
Another thought- if you hold VOL DOWN and POWER for 12-15 seconds and release when you see the white text (and don't hit vol up to enter RCK), does it boot up?
If so, you just have a recovery bootloop and can boot using this method until we fix it.
If not, back to my first thought - if it shows in the device manager, update the drivers using the naked drivers 0.72.
Then try typing "adb devices" at a command prompt and see if it is recognized via USB.
If so, push your firmware using the following:
adb push firmware.zip /sdcard/
If that succeeds, you should be able to flash the firmware from recovery.

frederuco said:
Since you have a TF101G, NVFlash is not an option.
Does your device show up as an ADB device in windows when you boot to recovery?
Another thought- if you hold VOL DOWN and POWER for 12-15 seconds and release when you see the white text (and don't hit vol up to enter RCK), does it boot up?
If so, you just have a recovery bootloop and can boot using this method until we fix it.
If not, back to my first thought - if it shows in the device manager, update the drivers using the naked drivers 0.72.
Then try typing "adb devices" at a command prompt and see if it is recognized via USB.
If so, push your firmware using the following:
adb push firmware.zip /sdcard/
If that succeeds, you should be able to flash the firmware from recovery.
Click to expand...
Click to collapse
when i try
adb push firmware.zip /sdcard/
adb push firmware.zip /sdcard/ permission denied

Try fixing permissions in CWM. I think it is under advanced.

[Q] Recovering from soft brick

Hi all,
I was fiddling around with a rooted android 7 inch tablet (its a china-made tablet i believe - TWD_MID) with android 4.0.4 installed. In order to hide the status bar i tried to follow certain tricks (replaced the /system/app/settings.apk and /system/framework/android.policy.jar). This caused the tablet to go into a bootloop (the boot animation kept on playing)
The obvious solution offcourse was to install a new custom ROM (since i unfortunately did not hav a backup ROM) ; however doing it manually i came across these problems:
1. The tablet doesn't seem to have any sort of bootloader / custom recovery mode. I've tried power +volume up and power+ volume down; even did adb reboot-bootloader , adb reboot [recovery] but nothing - the tablet just kept booting normally and going into bootloop.
2. There seems to be some problem with fastboot as well - almost all the commands entered along with fastboot yield "<waiting for device>"
I even tried using uniflash to install a custom rom; the tablet reboots twice and uniflash gives a success message; but in reality there seems to be no change in the tablet
Till this point though, adb was working properly
Out of sheer desperation (I know i shouldn't have, but still ) I used adb push to push all the entire /system folder from the extracted folder of custom rom into the /system of the tablet.
Now i can't even use adb shell - any adb shell "[command]" gives the error :
- exec '/system/bin/sh' failed: Permission denied (13) -
Please if possible can someone give me some advice??
I'm hoping to find a way to:
1. Get adb shell working again
2. Install and enter into some sort of bootloader/custom recovery mode on the tablet; so i can install a rom from TF(ext sd) card
I want to get my tablet working again....
Please Help...
Thanx a lot in advance...

[Q] [HELP BRICK] power button broken bootloop

nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE

osos96 said:
nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE
Click to expand...
Click to collapse
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good

osos96 said:
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good
Click to expand...
Click to collapse
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"

!Lür said:
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"
Click to expand...
Click to collapse
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.

!Lür said:
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.
Click to expand...
Click to collapse
yup i just made it a step by step tut for noobs and your welcome

How do I use ADB to pull files from my Galaxy tab 2 while it's in Recovery Mode?

Hello, I'm trying to pull files from my Samsung Galaxy tab 2 10.1 while it's in Recovery Mode (I'm using Clockworkmod Recovery 6.0.1.0), with ADB. How do I do this?
I can't copy files when my tablet is booted normally because it restarts unpredictably if it sits in the lockscreen or homescreen long enough. The only time it can stay on for long periods of time is while it's in Recovery Mode, and only in Recovery Mode.
I'm running ADB via the Command Prompt and I need help pulling files off of my device while my device is in Recovery Mode. ADB recognizes my device when I type in 'adb devices', and labels it as 'xxxxxx... recovery'. I'm having trouble accessing the files within, and I'm a noob when it comes to using the right ADB commands.
I've tried typing in the command: 'adb pull /sdcard.../' and that command didn't work, telling me 'remote object not found'. Now I know for sure the path I'm using is the right one, because I was able to pull files using the path when the tablet's booted normally (but my tablet restarts halfway into the copying process when doing this, which I why I need to find a way to do this in Recovery Mode!). I figured that the device's internal sdcard storage probably isn't mounted, so I tried doing that in Recovery Mode via Mounts and Storage, and still, ADB couldn't access my device's internal storage, telling me once again 'remote object not found'.
Then I tried mounting my SD Card in ADB with the following command:
adb shell
~ # mount sdcard
It returns with:
mount: mounting /dev/null on /sdcard failed: no such device
I don't know what else to do ... the only way I can keep the device on long enough to copy ANYTHING is while it's in Recovery Mode, and the ADB commands I'm using aren't working. Someone halp!

I tried installing the latest CWM Recovery 6.0.4.5 (which should let me use ADB in recovery mode, yes?) for the Galaxy Tab 2, and it seems my device is in some kind of ... read only mode. I can't successfully install the .zip file in recovery, because when I reboot it still says, at the bottom of the screen, CWM Recovery 6.0.1.0.
I'm beginning to lose hope, here.

How to escape TWRP? Activate ADB w/ broken screen?

So my screen broke on my Note 10+, leaving only the top 15% with display and the bottom 60% with touch. I am trying to activate ADB on it so that I can backup my internal storage.
I booted into TWRP so that I could backup the rest of my system, which I did successfully, but because of the bad touch screen I am unable to hit the ADB side load button. I'd like to reboot into the system because I have ADB enabled there, however I also cannot click the reboot to system button, only reboot to download and shutdown. Since I can't see most of the screen, it is also not possible to access the terminal and work from there.
Anybody know how I can escape TWRP or otherwise activate ADB? Thanks for the help.

Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload

jwoegerbauer said:
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
Click to expand...
Click to collapse
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.

AllanRSS said:
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
Click to expand...
Click to collapse
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot

jwoegerbauer said:
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
Click to expand...
Click to collapse
I can not use ADB. It is for this very reason I am asking how to enable ADB. But thank you for these valuable ADB commands, I'll be sure to reboot my system once I enable ADB