Related
Hi all!
Yesterday I want to change my old ROM for a newer one. I downloaded the new ROM and I copied it to my micro SD. From CWM recovery I wiped the table and also I did the formats (System,data,etc) and when I tried to flash the ROM i saw that there was no "Install from external SD card" option only "from internal"....but there's no zip in there. Now my tablet don't pass ASUS logo and I' dont have (or I don't know how I can do it) option to acces to the internal memory to copy there the new ROM.
CAn please some one hel me?
Thanks a lot!
joanmv said:
Hi all!
Yesterday I want to change my old ROM for a newer one. I downloaded the new ROM and I copied it to my micro SD. From CWM recovery I wiped the table and also I did the formats (System,data,etc) and when I tried to flash the ROM i saw that there was no "Install from external SD card" option only "from internal"....but there's no zip in there. Now my tablet don't pass ASUS logo and I' dont have (or I don't know how I can do it) option to acces to the internal memory to copy there the new ROM.
CAn please some one hel me?
Thanks a lot!
Click to expand...
Click to collapse
wrong thread, this thread is NOT for posting questions. post a question you want to ask in the Q&A thread
Anyway, use EasyFlasher-0.8.3b tool to flash the stock ROM and use the latest CWM recovery for tf101. i found that the latest version (v6.0.2.1) has an option to choose whether to install it from SD card and also internal memory
TheMrcool212 said:
wrong thread, this thread is NOT for posting questions. post a question you want to ask in the Q&A thread
Anyway, use EasyFlasher-0.8.3b tool to flash the stock ROM and use the latest CWM recovery for tf101. i found that the latest version (v6.0.2.1) has an option to choose whether to install it from SD card and also internal memory
Click to expand...
Click to collapse
I'm sorry for posting in the wrong thread. Could you please move it to the correct forum?
Thank you for the answer. I've read that easyflasher was not compatible with TF101 G but may be I was a older version. I'll try it and I'll post if it works.
Thank you again!
Sent from my GT-N7100 using Tapatalk 2
Thread moved,
Remember the development section is for development threads only, if you have a question this belongs in the Q&A section
joanmv said:
I'm sorry for posting in the wrong thread. Could you please move it to the correct forum?
Thank you for the answer. I've read that easyflasher was not compatible with TF101 G but may be I was a older version. I'll try it and I'll post if it works.
Thank you again!
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Correct, the TF101G has a different SBK so you are out of luck with EasyFlasher or anything that uses APX mode.
You have 2 options:
1 - Push the ROM you want to flash to the internal storage.
2 - Install a new recovery that supports external storage like TWRP or the Rayman's 6.X version in the development section.
Both of these involve using ADB to push/install the files when the tablet is in recovery. You will need a computer, your tablet and the USB charging cord.
On your PC, download and unzip the Naked Drivers.
Plug your tablet into the PC. It should find new hardware. Go to the Device Manager (through Control Panel - System) and look for your device. It may show up as an Android or Asus ADB device, or unknown hardware. Right click on it and update driver. Pick the driver (browse to it, do not let it scan) where you put the naked drivers. This should install a good working ADB driver.
Once that is complete, you will need to get a copy of ADB. It is in the Android SDK, but if you only need ADB, you can get it from this thread: http://forum.xda-developers.com/showthread.php?t=1955627 It also has some help on getting ADB working.
Once you get ADB downloaded, put the exe in a folder named c:\adb\.
Next, open a command prompt and type cd c:\adb followed by adb devices
At this point, it should restart adb (it may error out and say the daemon failed to start, just execute the adb devices command again) and show a recovery device connected.
Method 1
Now, you need the ROM you want to flash. Download this and put it in the c:\adb folder. I am going to call it ROM.zip.
From the command prompt type adb push ROM.zip /sdcard/
It will then push the file ROM.zip to your tablet.
From this point, you should be able to go to your recovery on your tablet and Install ZIP from SDCard and then it should show the file you just pushed to your /sdcard/.
Method 2
Figure out what recovery you want to flash and you will need the blob file. If the recovery has a zip version that flashes via recovery, you can use method 1 to push it to your tablet. If the recovery only has a blob version (like TWRP) you will need to install it using dd.
First, download the recovery. I am going to save it as c:\adb\RECOVERY.blob
In a command prompt, type adb push RECOVERY.blob /sdcard/
Once complete, type adb shell and you will get a [email protected]# prompt.
Type dd if=/sdcard/RECOVERY.blob of=/dev/block/mmcblk0p4
Once that completes type adb reboot
The tablet will now reboot. Do not try to enter recovery immediately, be sure to let the progress indicator complete on the Eee Pad screen. This is where it actually flashes the new recovery.
Once that completes, hold VOL DOWN and POWER for 12-15 seconds, then release and tap VOL UP when you see the white text. This will boot you into (hopefully) your new recovery.
This is TWRP recovery and Stock rooted roms for the ICS firmware on the tablet.
These will only work if you currently have ICS running on your tablet. If you still have honeycomb then do the upgrade first.
Nothing was added or removed from the stock roms besides root and busybox.
Only bug with TWRP is that you can't mount sdcard in recovery. Just use adb push.
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Thanks:
attn1 - gave me some help since I am new to pantech devices
Dees_troy - for TWRP code obviously
Tassadar - for his rotation code for twrp. Without this it wouldn't have been possible
Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support and so forth. No apps were added or removed. Both Odexed and Deodexed versions below.
Downloads
just in case i need another
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
mavblues said:
Once I reboot into fastboot, I am getting 'cannot load twrprecovery.img': no error
Any ideas? I even created a directory named tools in the adb directory on my computer and moved twrprecovery.img into it.
(Thought that might help).
Where is the twrprecovery.img file supposed to reside? (On the computer, or on the phone?)
Click to expand...
Click to collapse
On the computer. your command prompt should be at wherever you put twrprecovery.img file is. So for example you put twrprecovery.img at the root of c:, your command prompt should read c:/ .....
Sent from my M7 using xda premium
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
mavblues said:
Tada!!!
Thanks, you rock!
---------- Post added at 01:39 PM ---------- Previous post was at 01:10 PM ----------
OK, stupid question:
How do you reboot to TWRP? It loaded the first time, and I did a backup.
After reboot, I can only seem to get into the standard recovery.
What is the button combination to get to TWRP?
Also, will we be able to use goo manager to update TWRP as new versions come out, or is this a custom version?
TIA
Click to expand...
Click to collapse
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
jmztaylor said:
Read the instructions. You HAVE to flash the zip I provided for recovery to be installed permanently.
This recovery required some special code for screen rotation. Dees_troy is working on getting it added to mainline. So right now you can't get it through goo manager. But I work closely with Dees to make sure all my builds are officially supported. I will post here when it becomes available through there
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Got it - working great!
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
dagadu said:
I'm stuck on fastboot mode. <waiting on device>
I tried unplug/replug USB to different connector, and it's still on <waiting for device>
I even tried to install driver manually from each files pantech folder and still no response
TWRP is on same folder and also set on environment variable
I have done adb devices and it detects as PORORO03111xxxxxxxxxxx
Any suggestion guys?
Click to expand...
Click to collapse
Did you check "USB debugging" on the tablet?
Also, I had to set USB connection on the tablet to the last choice "PC Data Mode".
Hope it helps.
jmztaylor said:
Waiting on device in fastboot means drivers aren't installed or the wrong ones are. Download the software upgrade app from pantech site then install. Browse to the install directory and run the installer for the drivers. But before that uninstall whatever drivers you have installed currently. I'm mobile or else I would link you directly
Sent from my M7 using xda premium
Click to expand...
Click to collapse
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
dagadu said:
Is this what you're referring to? I download it from Pantech website.
htt p://c7240 62.r62 .cf2.rackcdn. com/PantechPCSuite_1.1.1.3437. exe
When do I need to install the driver? During fastboot mode, or normal mode?
I also notice that when I change the usb mode to MTP, it detects missing driver as well.
During normal mode it detects 2 pantech drivers in order to connect to pc suite.
Oya, when you guys do adb devices, does your device detect POROROxxxxxxx as well or only numbers?
I wonder this has anything to do with it, because I was trying to root with honeycomb version earlier and my pantech is ICS 4.0.4
Click to expand...
Click to collapse
Anytime when the tablet is not plugged in. This will make the computer automatically install anything needed for the tablet and you won't have issues with fastboot or adb anymore
Sent from my M7 using xda premium
jmztaylor said:
Instructions for installing TWRP Recovery:
1. Ensure you have Android SDK installed with adb and fastboot working
2. Download both the twrprecovery.img and twrprecovery.zip from here
3. Copy twrprecovery.zip to external sdcard
4. Reboot tablet to bootloader by issuing the command "adb reboot bootloader"
5. Then "fastboot boot twrprecovery.img"
6. When in recovery choose install then browse to /sdcard and choose twrprecovery.zip and flash that zip
7. Now TWRP is installed permanently.
Click to expand...
Click to collapse
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
1806 said:
I did not understand anything of this manual...
I took the CWM file for Pantech A810S and replaced it recovery to ours, flashed(connect working Element to PC and start cwm.but), everything works.
Click to expand...
Click to collapse
Actually it's similar steps; however, yours is more like 1-click root
Anyway, I tried everything all above, but it didn't solve my problem, then I found the solution from other website
I just want to share in case others are stuck in fastboot mode like me:
1. When your tablet screen is on fastboot mode (white), go to device manager on your pc
2. Right click on Android > Update driver
3. Click on Browse driver
4. Choose Let me pick manually from my pc list
5. Choose Android phone and pick the first list there. It should be "Android ADB..."
6. Install and fastboot continued
if you can't find Android ADB from your pc list, then you should unplug device then install PC Suite.
here's the old tuts: youtube com/watch?v=UHRonVzBMsI
Hopefully it helps others and thank you very much for all your help!
Delete!
Finally! and a question
Finally a recovery for the element! Rhanks to the OP. Now I am less afraid to tinker with my tablet.
Question: The most important thing right now that I'd like to do is move the folder /data/data from the internal storage, to the internal SD card. This is stopping me from using Google Magazines and Google music, since their data is being stored there, and it shares space with actual applications. 1GB is not that much space for APPS, Dalvik Cache and APPs' data when you add magazines, and when google starts caching Music and Chrome data there. I currently only have 300MB left before I install Music and magazines. And that is AFTER I've used app2sd on all apps that can be moved. How do I do this?
I have tried simply creating a Link using "ln - s /mnt/sdcard/data /data/data" once I copied/moved the contents of the directory, which sort of works initially, but it will not work after a reboot. It actually stops my tablet from booting. (again, thanks to the OP for the recovery).
right now, I am just doing an "ln" on the specific folder inside the /data/data folder, but it acts weird when I use Titanium Backup to restore data
-> Android noob <-
Installing TWRP went smooth as silk. With twrprecovery.zip on you micro sdcard and Element connected with usb cable and USB debuuging checked 1.Just copy twrprecovery.img into your sdk folder/ platform-tools and also have a copy of cmd.exe from windows in the platform-tools folder. 2. Start cmd.exe and type or copy & paste command reboot bootloader 3. Then on white screen(fastboot) type or paste command fastboot boot twrprecovery.img 4. When you boot into TWRP install twrprecovery.zip.....As you rebbot system TWRP should ask if you want Supersu installed and swipe to install. Once rebooted install supersu from the Play store and open Supersu to update SU file all should be good
Thanks for the info and files. I know I'm a little late on this Tablet but picked it up cheap and with ATT 4G it goes along with my devices. The orginial owner hadn't even installed ICS and she wasn't even aware of an update. She now owns an Apple :laugh::laugh:device LOL
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
marcustaz said:
I just picked one up for $90 bucks off ebay. It was on slickdeals .net
Figured i'd use it around the pool and save my phone!
No one has deved a JB rom though Could KK even be possible?
Click to expand...
Click to collapse
Yes good deal, got mine last month on Craigslist for $70.00 and works really well. The owner hadn't even updated to 4.0 or even knew how. It is a good tablet and have rooted it. I think its development is pretty well dead as not many sold. Only thing bad about it is the Element reads 2nd partition instead of 1st as most android devices do, so harder to use link2sd or folder mount as they both use 2nd partition.
Sent from my PantechP4100 using XDA Premium 4 mobile app
I flashed eos-tf101-20130704-121, and it does not boot. I've tried several times, and I made sure to wipe the system, cache, etc. why is it not working?
also, how do I get into download mode?
That's an ancient build of a dead ROM project
KatKiss is the new EOS
http://forum.xda-developers.com/showthread.php?t=2362764
Unfortunately, I don't have a spare sd card, and I can't seem to get download mode to work, so I was hoping I could install the ROM update, and install KatKiss. I am working on getting KatKiss though!
If yo boot to recovery you can use ADB to push files to your tablets internal memory to flash.
frederuco said:
If yo boot to recovery you can use ADB to push files to your tablets internal memory to flash.
Click to expand...
Click to collapse
sorry - how do I do this? never used adb before.
sniper8752 said:
I flashed eos-tf101-20130704-121, and it does not boot. I've tried several times, and I made sure to wipe the system, cache, etc. why is it not working?
also, how do I get into download mode?
Click to expand...
Click to collapse
you have to wipe cache and dalvik after flashing the rom
KronicSkillz said:
you have to wipe cache and dalvik after flashing the rom
Click to expand...
Click to collapse
no luck.
Im going to guess that you have CWM Recovery installed ?
If yes, that is likely the reason for it not booting
You'll need to put the TF into APX Mode (Volume up & Power while connected to the PC > USB)
Nothing will appear on the TF screen, but the PC should recognise it
Follow the instructions here to get TWRP Recovery installed instead
http://forum.xda-developers.com/showthread.php?t=1688012
sniper8752 said:
sorry - how do I do this? never used adb before.
Click to expand...
Click to collapse
You need adb from the Android SDK. I have a zip of the files you need here: http://db.tt/b9dQ6xzp
Unzip these to c:\adb\
Plug your tablet in using the USB cable. Your computer should detect a new device. Update the driver with the Naked Drivers 0.72 ADB driver found in the Dev forum (I think it is on page 2 of threads). If you are running Win 8, there are some extra steps to allow you to use this driver.
Once your devices shows in the device manager as an ADB device, open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
At this point, it will probably restart the daemon and then it should show a recovery device. If it does, you can proceed. If not, check that your cable is good, and that an ADB device is showing in the device manager.
Grab the ROM of choice and any GAPPS and kernel that you want to move over to your device. Put them in the c:\adb folder. They will be referred to a ROM.zip, GAPPS.zip and kernel.zip going forward.
Execute the following:
Code:
adb push ROM.zip /sdcard/
adb push GAPPS.zip /sdcard/
adb push kernel.zip /sdcard/
Note there is a space between the zip and the /sdcard/. If you omit this space it will not work.
After each time the "adb push" is executed, it may take up to 10 minutes to push the file depending on how big it is. Just be patient until it says it was pushed successfully.
Once this is done, you should see these files in the internal memory of your device when in recovery.
thanks! got it to work.
Ok, So basically I accidentally formatted my entire phone while trying to flash SlimKat... Noobish, I know, lol. My question is: If I'm still able to enter recovery (TWRP) would I be able to flash a rom still or should I revert to stock 4.4.2?
vI Ragnarok Iv said:
Ok, So basically I accidentally formatted my entire phone while trying to flash SlimKat... Noobish, I know, lol. My question is: If I'm still able to enter recovery (TWRP) would I be able to flash a rom still or should I revert to stock 4.4.2?
Click to expand...
Click to collapse
if you can still enter recovery, you can adb push a rom/gapps to your phone and flash tbem.
simms22 said:
if you can still enter recovery, you can adb push a rom/gapps to your phone and flash tbem.
Click to expand...
Click to collapse
Ok, cool. Would you mind elaborating a bit, I'm not too familiar with using console commands to flash. Also, thanks for the help!!
vI Ragnarok Iv said:
Ok, cool. Would you mind elaborating a bit, I'm not too familiar with using console commands to flash. Also, thanks for the help!!
Click to expand...
Click to collapse
Please look at this thread, and read it thoroughly.
-Download ROM and Gapps, transfer it to your ADB folder and rename it to something easy (Eg : Rom.zip and Gapps.zip).
-Open CMD/Terminal, navigate to your ADB folder.
-Boot into recovery on your phone and plug in your phone, find something called ADB Sideload. It's under Advance in TWRP if I'm not mistaken.
-Type in "adb sideload *.zip" . Replace * with your zip name you have renamed earlier.
-Your phone should be flashing the zip. Simply reboot and you should be perfectly fine.
exb0 said:
Please look at this thread, and read it thoroughly.
-Download ROM and Gapps, transfer it to your ADB folder and rename it to something easy (Eg : Rom.zip and Gapps.zip).
-Open CMD/Terminal, navigate to your ADB folder.
-Boot into recovery on your phone and plug in your phone, find something called ADB Sideload. It's under Advance in TWRP if I'm not mistaken.
-Type in "adb sideload *.zip" . Replace * with your zip name you have renamed earlier.
-Your phone should be flashing the zip. Simply reboot and you should be perfectly fine.
Click to expand...
Click to collapse
Thank you, sir. Couldn't get adb sideload to work so I just flashed the factory image of 4.4.2. No big deal, I'll just have to Re-root. :/
vI Ragnarok Iv said:
Thank you, sir. Couldn't get adb sideload to work so I just flashed the factory image of 4.4.2. No big deal, I'll just have to Re-root. :/
Click to expand...
Click to collapse
Oh, that was probably a driver issue. No worries, you can always get into android, transfer the custom rom into your SD card, boot into recovery, wipe and flash if you want to try out a custom rom.
hey guys,
I was on stock 8.1 oxygen 5.1.8 rooted magisk with exposed installed, everything worked fine !
Untill I flashed https://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/8-0-8-1-t3822594 I flashed the first zip file (8.0-8.1 black theme), after restart the phone is stuck in the oxygen bootscreen. Just to be safe before flashing I also put the uninstall zip file, so I flashed the uninstall zip file, but the phone is still stuck in the oxygen boot screen.
The big problem is, I have some data on my phone which i which to retrieve, I can enter into twrp but when connecting to the pc, the pc does not find my op6 drive. How can I fix this, the data is really important on the op6 which i would like to retrieve to my pc.
I hope someone can help me out here.
TWRP doesn't support MTP for now. So use:
adb pull /sdcard
It will download all files from Your internal storage to Your PC.
Just make sure that You have minimal adb installed on Your PC, and then run that command in PowerShell/CMD or Terminal.
ProtoDeVNan0 said:
TWRP doesn't support MTP for now. So use:
adb pull /sdcard
It will download all files from Your internal storage to Your PC.
Just make sure that You have minimal adb installed on Your PC, and then run that command in PowerShell/CMD or Terminal.
Click to expand...
Click to collapse
thnx for response, but could you just tell me in steps what I should do to retrieve my internal data without moving all the files from the phone to pc, the most important files are only the pictures and videos I shot. Is there a way to select specific folders that I would like to transport to my pc ?
There's an mtp enabled unofficial twrp version that you could boot from fastboot:
https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
comicbookguy72 said:
There's an mtp enabled unofficial twrp version that you could boot from fastboot:
https://forum.xda-developers.com/oneplus-6/development/recovery-twrp-3-2-2-0-touch-recovery-t3813317
Click to expand...
Click to collapse
thnx but i am already transfering all the files from my 128gb through the adb pull, I already extracted around 55gb, I think in one hour it should be done.
Anyways, I am really gratefull for the help I received, I hope to see a stable twrp with mtp ^^,