I tried to root my me302kl by following the first post described in this thread, but it seems I've bricked my tablet
http://forum.xda-developers.com/showthread.php?t=2601837
I have the LTE version, unlocked the bootloader using the apk from Asus, and followed the fastboot method in the first post, and now I'm stuck at the Asus logo on startup. I'm trying to factory reset by using the update download from the Asus website, but when i try
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
it fails with this:
writing 'update'...
FAILED (remote: partition table doesn't exist)
Then I tried following perpe's advice but both methods did not work
Download the update zip for your device and sku from ASUS. Unpack it once, there should be a second zip, try to flash it with
fastboot update name-of-your.zip
if this doesn't wotk, then copy the update zip to an external sd card. Your sd card should be formated in far32. Place the card into the tablets sd card. Press Volume UP + Power to boot it into the bootloader, it should flash it automatically, if not look if yor bootloader has a menu entry "sd download..." select it with the volume keys and power.
Click to expand...
Click to collapse
When booting into recovery mode, I get the dead android robot icon, regardless of whether the .zip file is on the SD card or not. I've also tried making a system.img file out of the system folder from the extracted zip file and flashing that with fastboot flash system system.img and fastboot flash boot boot.img, but that didn't work either.
Any kind soul have advice on how to make use of the official Asus OTA .zip file, or perhaps be able to supply some .img backups for me to make use of?
EDIT
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Lenino83 said:
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Click to expand...
Click to collapse
download the OTA zip from the asus website
unzip once, you should have another zip
power on the tablet while holding volume up to boot into recovery mode
after the android robot shows up, hold volume up and press the power button to get the recovery menu to show
install the zip using adb sideload
using adb sideload will differ depending on what OS you're using. you can google to find out more specific instructions for that because it's a little more work to get it for windows. for OSX if you have homebrew, you can just 'brew install android' and it will install all the android tools for you.
once you have adb installed, in the terminal type 'adb sideload pathname_of_zip.zip' and it will restore your device to factory settings
I had the same problem and your trick saved me from sending it back. I am not sure if i would have send it back as I have yet to brick something since I am playing with android back in the days of Viewsonic gtablet. We are stuck with 4.2.
Sent from my T0LTE using Tapatalk
help
tkuichooseyou said:
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Click to expand...
Click to collapse
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
ionratiu2000 said:
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
Click to expand...
Click to collapse
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
back
rob_z11 said:
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
Click to expand...
Click to collapse
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
ionratiu2000 said:
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
Click to expand...
Click to collapse
You can download king's root or something which is a window app, and it does give your tablet root. I am not exactly sure about the name, but would let you know once I have access to my laptop.
Sent from my T0LTE using Tapatalk
ASUS MEMO PAD FHD10 ME302KL frozen logo screen
I have problem with my asus memo pad 10. It just shows asus logo startup screen and nothing more and it have no reaction with anything I do.
Please help!
I can't boot into recovery mode, but there is no problem to boot into fastboot mode!
Could anyone provide stock recovery file or link? Then I can flash recovery and do the adb sideload.
Thanks!!
Related
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Thx, Really wish someone had a one-click option, I guess i'll just have to jump in
I've been trying to boot into recovery for a while now, but with no luck. I installed the full SDK platform, and the Manager app downloaded and installed all the available packages (took forever). The 'push' command seemed to work fine, and when I do "adb reboot recovery" the tablet reboots, but just goes into the battery charging screen. Any idea why this might be happening, and what I can do to get into recovery?
kentoe said:
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Click to expand...
Click to collapse
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Itaintrite said:
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Click to expand...
Click to collapse
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Battery not recovery mode
I am in a similar situation, when I use adb to run recovery mode it sends me to teh battery charging screen. With the exception of that they only other things I can do are to hold power and vol to get option of using Fastboot or ODIN. I do not have any options ever to chose to go into recovery mode. Anyone know why this may be? I am running 3.1 IO version.
Thanks
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Installing the sdk works best, as drivers needed are acquired from the process! ELse there are extracted contents available on net including just the drivers, adb (and fastboot!)
Check my thread #9
http://forum.xda-developers.com/show....php?t=1136958
bakobitz said:
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Click to expand...
Click to collapse
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Berner said:
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Click to expand...
Click to collapse
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
engljeff said:
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
Click to expand...
Click to collapse
Use the quick boot app. Works well for me. Supports power off, recovery, and normal reboot for the free version. Oh yeah but that requires root.
Sent from my GT-P7510 using Tapatalk
mughalgxt said:
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
Click to expand...
Click to collapse
yes it did.. thats why I said try that ..
On 3.1 IO too .. though I broke it within 3 weeks
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
This worked for me on Rogers 4G version
After trying to install ICS on my folio 100 using Rom manager, the update to ICS failed. Now the Folio 100 starts normally, but it doesn’t react on the buttons (power + vol +, 3x power vol 1). It just starts normally and after that I can use everything the normal way. Except when I change language from English into Nederlands, it’s not saved and after a restart of the system it’s back in English again, including the time zone which will be back to GMT +00.00 which is very annoying. The only way to get rid of this is to reinstall Android 3. By the way, factory reset doesn’t reset anything. It just restarts the Folio.
Getting into recovery from the menu or from Rom manager won’t do the trick either. The only thing I can use is ABD. But the command “flash_image recovery recovery.img” gives an error: “Error scanning partitions: No such file or directory”. And the file is in the system-directory. So this is a dead end for me too. I searched the forum and the internet, tried several possibilities, but now I’m stuck. I’ve considered opening the Folio and to start it without NAND connected, but I haven’t tried this, because I still hope for a software solution. What will happen when I manually delete of format the internal SD? Is there anyone who can help me to get my folio into recovery one way or another? Data is lost already, so that’s no problem anymore in this case.
Fastboot command is: fastboot flash recovery recovery.x.y.z.img ... not flash_image recovery.img (name of the recovery ofc)
Ics ? CM9? If so just read the tutorial on the topic related its simple as hell...
Also best way to start an new: fast boot erase Linux/recovery/system/cache/userdata one after another then fastboot reboot (remove USB before it reboot) check the folio say magic mismatch error then reboot pressing long on power(6sec) then the recovery command.
Sent from my folio100 using XDA Premium HD app
Thanks but...
ReiverBlade said:
Fastboot command is: fastboot flash recovery recovery.x.y.z.img ... not flash_image recovery.img (name of the recovery ofc)
Ics ? CM9? If so just read the tutorial on the topic related its simple as hell...
Also best way to start an new: fast boot erase Linux/recovery/system/cache/userdata one after another then fastboot reboot (remove USB before it reboot) check the folio say magic mismatch error then reboot pressing long on power(6sec) then the recovery command.
Sent from my folio100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, but this isn't the solution. The main problem is that I can't get my Folio into fastboot/recovery mode anymore. After that updating is simple. Done it several times before. Do you have a suggestion how I can get it into fastboot/recovery mode. ADB wont work either.
Regards Erik
Weird... hum im not home but i will check that( full keyboard is easier to answer xD)
Sent from my GT-I9000 using XDA
ErikSnippe said:
Thanks, but this isn't the solution. The main problem is that I can't get my Folio into fastboot/recovery mode anymore. After that updating is simple. Done it several times before. Do you have a suggestion how I can get it into fastboot/recovery mode. ADB wont work either.
Regards Erik
Click to expand...
Click to collapse
Remove the sdcard!
Remove SD Card
stefannsv said:
Remove the sdcard!
Click to expand...
Click to collapse
I removed the external SD-card (to the right of the orange light). But that doesn't help. How can I remove the internal SD-card? I removed the back and the battery but I do not find a sd-card. Unmounting the internal SD-card doesn't do the trick either.
did You come in the recovery menu??
I think you flashed the ics withe the wrong recovery...
flash the old rom aigan (copy the update.zip in the sdcard and update the folio via recovery menu)
when that works, try aigan with fastboot to flash first boot, then recovery (but the right version!!)
stefannsv said:
did You come in the recovery menu??
I think you flashed the ics withe the wrong recovery...
flash the old rom aigan (copy the update.zip in the sdcard and update the folio via recovery menu)
when that works, try aigan with fastboot to flash first boot, then recovery (but the right version!!)
Click to expand...
Click to collapse
I think you're absolutely rigth about flashing the wrong recovery. Problem is that I can't come into a recovery menu (power + vol up). Fastboot won't work either (3xpower + vol up). I've used both before, so the configuration on my pc is right. Now al I have to do is boot into recovery or into fastboot. That's my problem, flashing with the working Honeycomb-version is no problem at al when I get into the recovery menu. Do you no what happens if I delete the complete /system/-directory on my folio? Is that an option to force the tab into recovery?
...and how want you delete the complete sys? do you mean with root explorer in rw-option?? thats very dangerous...can't you flash with rom manager?
Rom Manager
stefannsv said:
...and how want you delete the complete sys? do you mean with root explorer in rw-option?? thats very dangerous...can't you flash with rom manager?
Click to expand...
Click to collapse
I can access the internal sd-card using ADB. This way I should be able to delete/move/copy files. After puting the system-partionion in RW-state. In Adb shell the command "flash_image recover recover.img" gives an error "erros scanning partitions: No such file or directory". The image files exists! So I'm stuck there too.
I tried to use rommanager. It work once when i was installing ICS. After this it won't boot into recovery. When I use "Flash clockworkmod recovery" in Rommanager v5.0.0.6 i only get the following phone models: Advent Vega, Elocity A7, LG/T-mobile G2X, LGE Optimus 2x, Motorolo XOOM and Viewsonic Gtablet (smb_a1002) - bootloader 1.1. I tried all the phone models, but all they do is reboot the tablet. No choice will boot into recovery. Also tried clockworkmod recovery 2.5.1.4 but also no succes.
I do not know how to install clockworkmod 3.0.0.5 for Folio. I only can find an option to install it using recovery menu or fastboot. And both won't work on my tablet.
and you have put the recover.img file in the fastboot directory?
stefannsv said:
and you have put the recover.img file in the fastboot directory?
Click to expand...
Click to collapse
Where can i find the fastboot directory?
Here I've ad complain the Problem:
http://forum.xda-developers.com/showpost.php?p=23715985&postcount=467
the fastbootdirectory is in android-sdk-windows\platform-tools
There is the fastboot.exe too.
Put the two files in that directory, connect yout folio via usb in fastboot modus with your pc or laptop, make the described commands at windows shell.
stefannsv said:
Here I've ad complain the Problem:
http://forum.xda-developers.com/showpost.php?p=23715985&postcount=467
the fastbootdirectory is in android-sdk-windows\platform-tools
There is the fastboot.exe too.
Put the two files in that directory, connect yout folio via usb in fastboot modus with your pc or laptop, make the described commands at windows shell.
Click to expand...
Click to collapse
Still the main problem is that I can't put my folio into fastbootmode via usb.
so far only 2 things prevent my folio to go into fastboot: power cord and/or mini usb unplugged.
also you talk about removing internal SD but you know what they reffere as internal SD is : a chip soldered on the motherboard?Right?
one more thing lets make it clear: fasboot directory isnt fixed, for the sake of accessibility you can put it like me C:\tools_X
also renaming recovery5.0.0.4.img (the one from nopy) into recoveryA.img (i wonder if your error come because you write the wrong commande or if its because of recover.img instead of the right name for the file.)
last option before saying: you F***ed up your tablet if nothing mentioned above works
also side note: every answer from you after a recommendation from a user : contain a new error \\\ important your problem come from : not being able to go into fastboot mode or not being able to flash the recovery via fastboot (either due to : you putting the recovery img not in the right directory or input the wrong command) its important since 1st one is prolly f.u.b.a.r and the second one is recoverable by reading and doing step by step whats explain *exactely what is explain*
the only right command is : "fastboot flash recovery *name of the recovery*.img" and not Flash_recover recover.img as you write it 2 time now
Sent from my folio100 using XDA Premium HD app
ReiverBlade said:
so far only 2 things prevent my folio to go into fastboot: power cord and/or mini usb unplugged.
also you talk about removing internal SD but you know what they reffere as internal SD is : a chip soldered on the motherboard?Right?
one more thing lets make it clear: fasboot directory isnt fixed, for the sake of accessibility you can put it like me C:\tools_X
also renaming recovery5.0.0.4.img (the one from nopy) into recoveryA.img (i wonder if your error come because you write the wrong commande or if its because of recover.img instead of the right name for the file.)
last option before saying: you F***ed up your tablet if nothing mentioned above works
also side note: every answer from you after a recommendation from a user : contain a new error \\\ important your problem come from : not being able to go into fastboot mode or not being able to flash the recovery via fastboot (either due to : you putting the recovery img not in the right directory or input the wrong command) its important since 1st one is prolly f.u.b.a.r and the second one is recoverable by reading and doing step by step whats explain *exactely what is explain*
the only right command is : "fastboot flash recovery *name of the recovery*.img" and not Flash_recover recover.img as you write it 2 time now
Sent from my folio100 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for your help,
the fastboot command fastboot flash recovery......... doesn't work. My pc keeps waiting for the device. Which is to be expected while i can't boot my folio into fastboot-mode. The command i used before is in adb shell.
Can you tell me where to put recovery.img exactly on my folio? And what i should do after i,ve put it there. I can use a root-explorer on my folio and i can use adb push ...... to move or copy files. Also mounting system in rw-mode is no problem anymore. My folio is rooted and i can use it as root or su in adb-shell.
ErikSnippe said:
Thanks for your help,
the fastboot command fastboot flash recovery......... doesn't work. My pc keeps waiting for the device. Which is to be expected while i can't boot my folio into fastboot-mode. The command i used before is in adb shell.
Can you tell me where to put recovery.img exactly on my folio? And what i should do after i,ve put it there. I can use a root-explorer on my folio and i can use adb push ...... to move or copy files. Also mounting system in rw-mode is no problem anymore. My folio is rooted and i can use it as root or su in adb-shell.
Click to expand...
Click to collapse
Don't put the recovery.img into the folio! Copy it to your pc. In the folder where the fastboot.exe is. Then start your folio an go in the fastboot modus (power and three times volume up)
Connect your folio via mini-usb with your pc and open a windows shell(cmd).
Now type
fastboot erase recovery
Fastboot flash recovery nameoftherecoveryfile
stefannsv said:
Don't put the recovery.img into the folio! Copy it to your pc. In the folder where the fastboot.exe is. Then start your folio an go in the fastboot modus (power and three times volume up)
Connect your folio via mini-usb with your pc and open a windows shell(cmd).
Now type
fastboot erase recovery
Fastboot flash recovery nameoftherecoveryfile
Click to expand...
Click to collapse
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
ErikSnippe said:
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
Click to expand...
Click to collapse
install PDANet on your pc
ErikSnippe said:
I can't get into fastboot-mode with my folio!!!!!!! That's the whole problem. The pc stays waiting for the device!
Click to expand...
Click to collapse
Is the problem the fastboot modus at the folio or the connection to your pc?
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
perch_44 said:
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
Click to expand...
Click to collapse
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
flumpster said:
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
Click to expand...
Click to collapse
If that fails, I had the same issue with cwm, I installed twrp via fastboot and haven't had the problem of the file not showing up after adb push. Fustrating I know.... I tired everything I could think of in cwm multiple reboots different usb ports... on an on......
Please HELP CWM Roocovery Loop!!!
perch_44 said:
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
Click to expand...
Click to collapse
I am having the same exact problem. It started when I tried to restore my stock backup that I made using CWM 5.8.2.0 coming from the CM rom. I am stuck in the CWM recovery screen and cant get ADB to see the TF Prime. I just get error: device not found. How did you manage to push a zip if ADB wasn't seeing your device? I have been looking for a fix for the last week now.
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Danny80y said:
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Click to expand...
Click to collapse
How do I flash TWRP when Im stuck CWM?
hellshavoc said:
How do I flash TWRP when Im stuck CWM?
Click to expand...
Click to collapse
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Striatum_bdr said:
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Click to expand...
Click to collapse
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
hellshavoc said:
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
Click to expand...
Click to collapse
you hold the volume down until the screen starts, then you let go and wait
whycali said:
you hold the volume down until the screen starts, then you let go and wait
Click to expand...
Click to collapse
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
hellshavoc said:
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
Click to expand...
Click to collapse
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
It is confusing but just keep trying till you get it!! Once there go to the TWRP site they have the file and the fastboot commands all set in a guide.
I have exactly the same problem than you.
I had the fastboot/adb connection (I used to push the rom by adb), but i tried to install a wrong version on gapps. Since then, I'm stock in the recovery mode without adb/fastboot connection.
If you find a solution for that, pleaze post it !!
Striatum_bdr said:
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
Click to expand...
Click to collapse
Hello everyone, been a lurker for some time, but have never needed to post before until today. I'm accustomed to rooting and installing custom roms but I've never had anywhere close to as much difficulty as Im having with this tf201. Heres the situation:
Not sure if you'd call this bricked, as I have total access to fastboot, adb, and CWM Recovery (version 5.8.3.4 touch btw). However my most recent attempt ended with totally wiping from the volume down+power menu (whatever its called). I can not turn the tablet off, as it automatically boots to the asus splash screen (and goes no further, naturally). It is unlocked, and my drivers do work (both fastboot and adb recognize the device), but I can not flash or push anything to the sdcard (with adb its a protocol failure, with fastboot I get "sending zip....OKAY writing zip....FAILED [remote : [FileOperationFailed]]) Don't know if it needs to be said, but I also can't simply drop the file on the sd card as if it were a media storage device as "my computer" does not recognize that it is connected (Oh I am using the naked universal drivers from http://forum.xda-developers.com/showthread.php?t=1998650 )
So yeah, Im at a loss as it seems like no one has had this particular problem before (also my connector cable works fine, so its not that). Any help would, of course, be greatly appreciated.
EDIT: On the tablet after trying to flash with fastboot it returns "Failed to process command flash:zip error (0x30003)"
Really? Not a single person has any idea? Could really use some help here...
GrimAgent said:
Really? Not a single person has any idea? Could really use some help here...
Click to expand...
Click to collapse
You do not flash zips with fastboot.
First of all tell me where your "NVIDIA" logo is when you first power on, bottom center or bottom right?
The nvidia logo is in the bottom center of the "EEE PC Splash"
This is going to sound stupid, but did you verify the MD5 before you tried to flash it?
GrimAgent said:
The nvidia logo is in the bottom center of the "EEE PC Splash"
Click to expand...
Click to collapse
You are still on the ICS bootloader if NVIDIA is bottom center.
Go here http://www.teamw.in/project/twrp2/93 and follow the instructions for "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)"
You will need to get the ICS blob file. Never flash the wrong recovery for what bootloader you are on or you can brick your device.
If you get it working and you want to upgrade to Jellybean bootloader there is instructions in post 2 of the Hairybean Rom thread. "Upgrade instructions for ICS"
edit.. to make it a bit easier for you.
Get this file http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.4.4.0-tf201-ICS.blob
Rename it to twrp.blob
Place the twrp.blob in the same folder as your fastboot exe
Go into fastboot and type
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for it to finish and then type
fastboot -i 0x0B05 reboot
see if that works.
Damn, I had a feeling it was the bootloader issue that I messed up. I went searching all over for how to find out which one I had once I realized my potential mistake. Gonna give these steps a try
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
GrimAgent said:
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
Click to expand...
Click to collapse
If you now have twrp on there you dont need to push a file. Place the file on an external SD card on the root and plug it in before starting prime.
When going into TWRP go into install and select external SD. Pick your rom and then flash it.
Thanks a lot flumpster, everything's good now and Ive got cyanogen up and running smoothly. You've brought my tablet back to life and Ive learned a valuable lesson
Ok, so I attempted to root a Nabi 2 so I could use the SD card to hold apps since the onboard memory is terrible and I bricked the dang thing. I unlocked root supposedly using a one click app method, then I was able to attempt to update using the updater already on the Nabi. During the reboot, thats when it bricked. It is stuck in a constant boot loop mode that eventually ends up on a dead android screen.
My main problem is I know there has got to be a way to restore a stock rom/os on it, but every how to guide out there assumes that I already know what the hell they are talking about. SDK, ADB, HIV, STD, its irritating. Also, I tried TWRP, ADB, etc. but since the Nabi is in a constant boot loop and dead android screen, I can't get my PC to recognize it for more than 5 seconds. Is there a step by step guide to what I need to do for a novice? Like step 1. "since your PC can't recognize the device in the first place this is where you start". Step 2, use "this program, then this, and this is why".
Can anyone out there help me get pointed in the right direction? I am tech savvy but the existing guides assume too much, have broken links, and don't say anything about what to do when you can't even get your device to be recognized.
Thanks
Aaron
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Higher-Primate said:
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Click to expand...
Click to collapse
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
aicjofs said:
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
Click to expand...
Click to collapse
I want to say it was running 4.1 or 4.2 but I'm not positive. Stupid me should have written it down. Is it possible to load any of the versions now that I have wiped it? I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen. From there I did a - and + and got an option to side load recovery or boot to ADB I think it was. So since I can at least get there, is there anything I can do? Other than that, TWRP won't recognize it and says no drivers are loaded. I'm assuming because I can't get the Nabi to stay stable long enough to actually load anything on to it? The device recognizes for a few seconds then disappears.
Higher-Primate said:
I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen.
Click to expand...
Click to collapse
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
aicjofs said:
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
Click to expand...
Click to collapse
Ok, I tried fastboot, but it doesn't really do anything. Once I go into fastboot, I have more options. Bootloader, continue, reboot bootloader, reboot, and power off. None of the options allows the Nabi to show up as a device in device manager. Everything just takes me to the dead android unfortunately.
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Higher-Primate said:
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Click to expand...
Click to collapse
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
aicjofs said:
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
Click to expand...
Click to collapse
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Higher-Primate said:
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Click to expand...
Click to collapse
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
aicjofs said:
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
Click to expand...
Click to collapse
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Higher-Primate said:
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Click to expand...
Click to collapse
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
aicjofs said:
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
Click to expand...
Click to collapse
No problem at all. Ok, that seemed to have done something. I put in the exact one you just changed above, and I rebooted normally, now I have a TWRP screen on the Nabi display. Now, what instructions do I need to follow? Do I still use NabiLab2015, if so the Disney/Nick or NV7A - US? Both now say "TWRP +mount:mounting /system on ext4 failed: no such file or directory.
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Higher-Primate said:
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Click to expand...
Click to collapse
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
aicjofs said:
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
Click to expand...
Click to collapse
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Higher-Primate said:
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Click to expand...
Click to collapse
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
aicjofs said:
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
Click to expand...
Click to collapse
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Higher-Primate said:
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Click to expand...
Click to collapse
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
aicjofs said:
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
What happens if it won't let me create the backup folder? It errors out and says it can't create one.