[Q] JB and ADB/Fastboot/APX modes - Transformer TF300T Q&A, Help & Troubleshooting

I have a locked, rooted (before JB/OTA ROM) restored
with Root Keeper, TF300T on JB 4.1.1.
I have ADB working properly when on Stock OTA ROM.
I am able to adb shell & su for a root shell.
I installed the APX mode driver, booted the tablet
ibn APX mode, and windows device manager
reports an APX Transformer.
I'm hoping that means the APX driver is correctly
installed?
When I unlock the bootloader, I should be
able to boot the tablet into fastboot mode
to run 'fastboot flash recovery recovery.img'
(which ever it is, and for the JB boot loader),
right?
Once I reboot into recovery, adb devices
should see the tablet as a recovery mode
device?
I'm interested in CROMI 3 3+ ROM.
I did an adb backup of the tablet,
and a TiBu of the apps & data
and system data. I also backed up
my calender to an iCal file and
my contacts to a vCard file.
I also did a TiBu to an update.zip
of my user apps and their data.
Did I forget anything? I'm hoping
to figure out how to copy the
contents of /sdcard to a directory
on the docks sdcard, (would
ES FE or Root Explorer do that?).
Thanks

Related

[ADB] Trying to backup - Birck? Hope not

Hi! I was trying to backup my Orange Monte Carlo following a Portuguese tutorial but I'm stuck in the middle and I've got no help! Hope you can provide some! These are the steps I followed (translated)
1 - Install ADB Made Easy;
2 - Open cmd;
3 - Activate cellphone debug mode;
4 - Connect via usb (without mass storage) and install drivers if request [it was requested and i installed];
5 - Run adb devices, it should show your device [it did];
6 - Run adb reboot bootloader, your cellphone will boot in Fastboot, wich is an Android image without menus [correct until here];
7 - Run fastboot devices, your device yor a question mark(?) should show up (advance to next step), else you miss drivers [step not completed];
cmd says 'fastboot' is not recognized as a command. Now my phone is stuck connected to the computer with an adriod pick and I have no clue on what to do next!
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
shanman-2 said:
Don't know where you were going with this but to reboot your phone just pull the battery ..
Not bricked
Click to expand...
Click to collapse
Thank you! Do you have any idea why the last command doesn't work? I believe it has something to do with file location... I'm trying to backup my Monte Carlo. Next steps were to "fastboot boot recovery.img" and then backup.
It should be in the platform-tools directory of the android-sdk. Verify that it's there...if so cd to that directory and it should work
I already fixed it for myself, thanks! Now I can't seem to be able to install clockwork!
Doing <<fastboot boot "C:\Users\R&J\Downloads\recovery.img">> reboots the device but doesn't enter recovery.
Doing <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> , <<fastboot reboot>> and <<adb wait-for-device reboot recovery>> results the phone entering android's default recovery (no acess to backup feature).
Any way to help? Thank you!
The first command <<fastboot flash recovery "C:\Users\R&J\Downloads\recovery.img">> is trying to write the recovery.img you downloaded to a recovery partition on your device. It may not be overwriting the original recovery.
try changing permissions by doing
adb shell
su
chmod 777 /recovery
then try to flash again
Lol it seems like I have been luck enough to solve my own problems, I have sucessfully installed ClockworkMod Recovery 4.0.1.4 unofficial MoDaCo Edition using a bat file . Now I can't seem to find a way to flash recovery back to stock. I though this was an option inside the modded recovery. Any tips? Thanks again!
EDIT: I have the stock recovery file . God... this tutorials I'm folowing aren't that noob friendly...

Back to stock

I rooted, and loaded cm9 rom. I prefer stock rom but when I restored my backup there was no wifi (apparently a common issue). Anyway, I am looking for a way to get back to stock rom. I downloaded firmware from Asus but dont know if that is what I need or what to do with it. I am using the twrp recovery
Thanks for any help
All you have to do is download the full Asus ZIP from my thread and flash in CMW and it will restore your fully stock ROM without recovery
http://forum.xda-developers.com/showthread.php?t=1680570
ok thanks now to figure out how to get cwm into my tablet-- right now trying to install sdk
i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here
this worked
Terminal Emulator Method
Install Android Terminal Emulator on your tablet.
Download the ClockworkMod Recovery image file directly to your tablet, preferably in the root of the /sdcard directory. Take note of where the file is saved. Rename the file to cwm-touch.blob.
Launch Android Terminal Emulator on your tablet.
Enter the commands below. If you did not save/move/copy the image file to the /sdcard directory, you need to replace /sdcardin the second command below with the correct directory where you saved the recovery image file to.
su
dd if=/sdcard/cwm-touch.blob of=/dev/block/mmcblk0p4
Reboot your tablet. The blob file will be automatically installed as your tablet reboots.
voodoo_dr said:
i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here
Click to expand...
Click to collapse
You can uninstall Eclipse. It has nothing to do with Android or flashing anything. It's an Integrated Development Environment, which is kind of like a word processor for programmers. The only relation it has to Android is that it supports the Java programming language, so a lot of Android developers use it. If you're not going to be writing apps or messing with Android source code, it's probably best if you uninstall Eclipse, just because you won't use it, and it's taking up storage space.
Also, what were you expecting to happen when you put the tablet in fastboot mode? It just opens up a serial connection with a host (in this case, your computer) and allows the host to access the tablet via fastboot (sounds confusing, I know; it's not particularly fast, and doesn't have much to do with booting anything; it's like ADB but for low-level [hardware] flashing) and run commands. The tablet itself does nothing except display the message that it's in fastboot mode. Once the tablet says that, you run fastboot on the computer.
thanks for the reply. Now I have a brick---tried to install stock rom and hangs on asus with the wheel going round and round. It deleted my cwm so now no recovery on tablet. When I go into fastboot, it doesnt seem to recognize my tablet adb devices--nothing comes up
In my device manager I see no adp drivers- the only driver which keeps installing when I plug in the tablet and go to fastmode is the asus bootloader interface so I cant do anything with the tablet--- no recognition of device with adb devices command Help please
If you're in fastboot, ADB won't recognize the tablet. You need to use the fastboot commands with fastboot.
What to do:
-download the CWM blob on your computer
-put the CWM blob in the directory on your computer with the fastboot program
-boot the tablet into fastboot, and flash CWM
-boot into CWM, and restore the nandroid backup you should have made.
Alternately, if you didn't make a nandroid backup, you can boot into recovery, push the Asus stock ROM to /sdcard on your tablet via ADB (I'm assuming ADB works in the stock recovery), then reboot into recovery, and it should flash the update automatically. This will erase ALL your data, including /sdcard.
is cwm blob recovery.img?
I'm not sure if flashing .img files works with this tablet, but you could try. If it doesn't work, go to the place you got the recovery (as long as it's not from ROM Manager, and you're positive it's not the TF201's recovery), and there should be a file that ends in .blob. That's the one you need.
then I just place it in the same directory and click on fastboot? or is there more to it? seems to be having trouble with drivers mtp driver not installing???
I don't use Windows, so I don't know about the drivers. There's a thread in the development section with all the Windows drivers you need, though.
You put the blob in the directory where fastboot is. You open the command line (open Run, and type "cmd" [no quotes]) and run the fastboot command from there.
got it thanks cwm is back

[Guide] Flash SuperSu and get root without installing custom recovery

Hi!
This guide is for the people who want to try a custom kernel and have root acces and still want to be able to get OTA's with the stock recovery. I haven't tested this on the M4 but on the HTC One V it works!
Try this at your own risk, I am NOT responsible for any damage!
Requierments:
- HTC drivers
- ADB
- fastboot
Step 1: backup your data using ADB
ADB can be used to backup your app data this is how:
1) Create a folder on your desktop called ie. M4.
2) Open terminal (linux/mac) or cmd and browse to the folder you just created.
Code:
for example:
cd Desktop/M4
3) Now backup your SMS messages and contacts using the message and phone app on your phone and copy and paste the file using usb to your desktop, or sync them with google
4) In the terminal you type
Code:
adb backup -apk -all -f backup.ab
to start the backup and follow the instructions on your phone. (Note that you are still in the M4 folder.)
5) After the backup is finished there should be an file called backup.ab in the M4 folder, you now have a backup
6) Just to be sure also copy your whole storage partition to your desktop
Unlocking the bootloader
Follow this guide to unlock the bootloader: http://www.htcdev.com/bootloader/
Unlocking the bootloader will factory reset your phone, you can restore using the backup we made.
Getting root acces
1) Go to http://http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip and download the flashable supersu.zip file
2) Put the .zip file on the root of your phones sdcard
3) Download this recovery: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m4 and put it in your M4 folder on your desktop.
4) Open your terminal and browse to your M4 folder:
Code:
for example:
cd Desktop/M4
5) Reboot your phone into the bootloader using the screen on/off and volume down buttons
6) Select fastboot and make sure you see fastboot usb
7) Type:
Code:
fastboot boot philz_touch_6.41.6-m4.img
this will load a custom recovery but it will not install it, the stock recovery will be kept.
8) Flash supersu.zip in this "live" recovery and after it's finished reboot your phone to system. You should now be rooted and have SuperSu.apk installed.
Restore your backup
Restore your backup using the terminal and type:
Code:
adb restore backup.ab
You are now rooted and can try custom kernels and recieve OTA's because you still have the stock recovery. Don't mess to much with the files in /system or an OTA might fail.
can anyone confirm if this works for rooting a HTC One Mini (M4)?
I did that on my HTC D816w dual sim China Unicom Version. But i used CWM rather than philztouch thingy. It works perfectly fine so far. Root checker say device is rooted properly.
Anyone can get me a guide of how to use the functions of SuperSU. Like a link or something
Aktharcod said:
I did that on my HTC D816w dual sim China Unicom Version. But i used CWM rather than philztouch thingy. It works perfectly fine so far. Root checker say device is rooted properly.
Anyone can get me a guide of how to use the functions of SuperSU. Like a link or something
Click to expand...
Click to collapse
can you explain to me how you did it i have the exact phone have already unlocked the bootloader but after running fastboot boot philz touch img nothing happens when i choose recovery. May be am doing the wrong thing am not able to access the super su file on SD. How can i run it live as he has said ??
I'm already rooted
LQi said:
Hi!
This guide is for the people who want to try a custom kernel and have root acces and still want to be able to get OTA's with the stock recovery. I haven't tested this on the M4 but on the HTC One V it works!
Try this at your own risk, I am NOT responsible for any damage!
Requierments:
- HTC drivers
- ADB
- fastboot
Step 1: backup your data using ADB
ADB can be used to backup your app data this is how:
1) Create a folder on your desktop called ie. M4.
2) Open terminal (linux/mac) or cmd and browse to the folder you just created.
Code:
for example:
cd Desktop/M4
3) Now backup your SMS messages and contacts using the message and phone app on your phone and copy and paste the file using usb to your desktop, or sync them with google
4) In the terminal you type
Code:
adb backup -apk -all -f backup.ab
to start the backup and follow the instructions on your phone. (Note that you are still in the M4 folder.)
5) After the backup is finished there should be an file called backup.ab in the M4 folder, you now have a backup
6) Just to be sure also copy your whole storage partition to your desktop
Unlocking the bootloader
Follow this guide to unlock the bootloader
Unlocking the bootloader will factory reset your phone, you can restore using the backup we made.
Getting root acces
1) Go to and download the flashable supersu.zip file
2) Put the .zip file on the root of your phones sdcard
3) Download this recovery: and put it in your M4 folder on your desktop.
4) Open your terminal and browse to your M4 folder:
Code:
for example:
cd Desktop/M4
5) Reboot your phone into the bootloader using the screen on/off and volume down buttons
6) Select fastboot and make sure you see fastboot usb
7) Type:
Code:
fastboot boot philz_touch_6.41.6-m4.img
this will load a custom recovery but it will not install it, the stock recovery will be kept.
8) Flash supersu.zip in this "live" recovery and after it's finished reboot your phone to system. You should now be rooted and have SuperSu.apk installed.
Restore your backup
Restore your backup using the terminal and type:
Code:
adb restore backup.ab
You are now rooted and can try custom kernels and recieve OTA's because you still have the stock recovery. Don't mess to much with the files in /system or an OTA might fail.
Click to expand...
Click to collapse
What if I'm already rooted and Ijust want to load the recovery? Oh, and, I already have TWRP loaded (no custom kernel, no custom ROM, just Rooted and Unlocked), will there be any problem if I just connect my phone (HTC One V) to computer and then I just type the command "fastboot boot philz_touch_6.41.6-m4.img"? Shall I uninstall TWRP?And how do i do this?...
Yes, I know that there will not be any other updates for HTC One V, but I want to install a custom kernel, and then I will be able to S-OFF my phone, and then I will be able to install a Custom ROM I know it's possible to install Custom ROMs without S-OFF, but i saw some guys that bricked their phones (HTC One V) trying to install Custom ROMs without S-OFF, so I just want to ensure
Victor271 said:
What if I'm already rooted and Ijust want to load the recovery? Oh, and, I already have TWRP loaded (no custom kernel, no custom ROM, just Rooted and Unlocked), will there be any problem if I just connect my phone (HTC One V) to computer and then I just type the command "fastboot boot philz_touch_6.41.6-m4.img"? Shall I uninstall TWRP?And how do i do this?...
Yes, I know that there will not be any other updates for HTC One V, but I want to install a custom kernel, and then I will be able to S-OFF my phone, and then I will be able to install a Custom ROM I know it's possible to install Custom ROMs without S-OFF, but i saw some guys that bricked their phones (HTC One V) trying to install Custom ROMs without S-OFF, so I just want to ensure
Click to expand...
Click to collapse
I dont think a recovery that isnt made for your device will work. The HOV has its own version of Philz recovery so try that one.
On another note, HTC disabled recovery sideloading on the m4 since the kitkat OTA. Maybe it is still useful for people with other devices...
Ok
LQi said:
I dont think a recovery that isnt made for your device will work. The HOV has its own version of Philz recovery so try that one.
On another note, HTC disabled recovery sideloading on the m4 since the kitkat OTA. Maybe it is still useful for people with other devices...
Click to expand...
Click to collapse
Well, anyway, I don't really need Philz... thanks anyway for reply
Brilliant. Thanks so much for posting this. I re-rooted my Nexus 10 after reflashing with the latest stock binary, using TWRP loaded from my desktop. I didn't have to touch the stock recovery.

No OS installed! OnePlus one

Hello all.
I know there are many threads of this kind but nothing worked for me. So Please help!
I unlocked my bootloader, installed TWRP and flashed SuperSU binaries. Everything was working fine.
Then I wanted to flash cm12 nightly. So i downloaded the zip file and also the Gaaps.zip file. I transfered them to the phone and booted to recovery.
1. Then instead of wiping cache i wiped the whole system i.e factory data reset. So then i tried reboot it says NO OS INSTALLED! do you want to continue? After that "Your phone is not rooted. Install SuperSU? As i don't have the SuperSU files so it just reboots to the bootscreen and stays there. I can go to the recovery and fastboot mode.
2. then i booted to recovery and went to adb sideload. I have the ADB files on my desktop and pasted the ROM.zip file to the folder.
3. Then i tried the command adb sideload ROM.zip with my phone connected. But then a lot of coding appears in the cmd window and phone stays at adb sideload.
4. When i connect my phone to my pc in recovery It comes up as "One" in the disk drives. I open it and it has a folder named TWRP and inside thata file. Nothing else. The good thing is I have a nandroid backup of my device when it had SuperSU binaries.
*the "One disappears when I go to ADB sideload in my phone*
So can I transfer the backup to my phone in a separate folder named "Backups" and install it via restore in TWRP? Or do have to do something else?
Please help! Please! :crying:
You're already getting help for this here:
http://forum.xda-developers.com/showthread.php?t=3044924
Transmitted via Bacon

Error in ADB: Can't push apps/files due to system is read only.

Hello guys! Hope I can find my salvation here. Hehe
I've been coding my Windows App that functions much like a custom recovery but I came into a problem which is bugging me
since last week. I can't seem to push files to my phone through adb. I have no idea why it wont work because pull is working fine, and shell as well. I tried remounting the file system as rw but still no luck. Hope you can help me out guys
My phone's Specification:
-Spreadtrum SC7731
-Running Android 5.1
My environment:
-Windows 10
-adb installed
-device drivers installed.
PS: If you are wondering why make a recovery that runs in PC while you can just have it in your phone?
-Unfortunately, I got a problem with that. I ported TWRP for my phone, but touch wont work which makes it useless.
Please help me sensei's!
Unlock the bootloader, flash a custom recovery (CMW for exmpl), put the root package at the root dir of the sdcard, now boot the phone into recovery mode and select install zip from sdcard then reboot
On pc, write the following command : "adb remount"
Gratzz you're now rooted and able to push files into system partition ��
Root at your own risk. Unlocking the bootloader makes you lose the warranty and will wipe your data .. So take a backup.
FinnTheHuman. said:
Unlock the bootloader, flash a custom recovery (CMW for exmpl), put the root package at the root dir of the sdcard, now boot the phone into recovery mode and select install zip from sdcard then reboot
On pc, write the following command : "adb remount"
Gratzz you're now rooted and able to push files into system partition ��
Root at your own risk. Unlocking the bootloader makes you lose the warranty and will wipe your data .. So take a backup.
Click to expand...
Click to collapse
Reread the OP. :fingers-crossed::fingers-crossed: I'm on Spreadtrum phone which means no source(yet.. or forever). I don't really know if you just misinterpreted the post or just trying to acquire post count. :3

Categories

Resources