Prime still Bootloop and to CWM and wont Mount - Asus Eee Pad Transformer Prime

so its been already 2 months no way i can fix this still doing the same thing turn on boots and then loops to CWM same thing over n over and no connection to my computer so basicly now i feel i waisted 500 billz and used it from feb till now and no way i can fix it no ideas and asking around how can i putit back to live no answers yet nada so my guessin is not way a big amount and send it to asus or is there still a way to save it? i really missed my prime u use it alot but since still stuck on loop from EEE Pad to CWM and no mount :crying:

klutch said:
so its been already 2 months no way i can fix this still doing the same thing turn on boots and then loops to CWM same thing over n over and no connection to my computer so basicly now i feel i waisted 500 billz and used it from feb till now and no way i can fix it no ideas and asking around how can i putit back to live no answers yet nada so my guessin is not way a big amount and send it to asus or is there still a way to save it? i really missed my prime u use it alot but since still stuck on loop from EEE Pad to CWM and no mount :crying:
Click to expand...
Click to collapse
I am having the same problem man......I can't get the PC to detect my prime so I can't push any .zip
if you get adb to work, this is a solution http://forum.xda-developers.com/showthread.php?t=1661128&highlight=boot+loop

@klutch
what have you done before your prime stuck in the boot loop?
tried to flash anything or something like that

if i remember correctly you can't mount the prime as a removeable disk in CWM unless they fixed it
your best bet is to go into CWM and use adb to push the flashable zip files in there
you can do that by the following commands
Code:
adb push [directory/file name.zip] [/mnt/sdcard/]

if your device is not recognized by windows, then ADB does not work. that's the OP's problem.... and mine as well. ~$230 to fix my prime.

have you already tried to enter fastboot mode and flash a fresh rom from there?

I was able to get the PC detect my TFP by installing the driver from this link
[ADB/FB/APX Driver] Universal Naked Driver 0.7
You should be able to adb afterwards....Then follow 'OPTION 1a" from this link
[HOW-TO] Unbrick your Transformer Prime (or not)
I installed nvflash to make sure this won't happen again
hope this helps!

naked drivers
urboy4mbx said:
I was able to get the PC detect my TFP by installing the driver from this link
[ADB/FB/APX Driver] Universal Naked Driver 0.7
You should be able to adb afterwards....Then follow 'OPTION 1a" from this link
[HOW-TO] Unbrick your Transformer Prime (or not)
I installed nvflash to make sure this won't happen again
hope this helps!
Click to expand...
Click to collapse
i dont get how to install naked drivers when everytime i plug in my prime it just says unknown device in device manager and when i try to update the driver it says i have the best or latest driver. plz someone help me!!!!

InkD_up_G33k said:
i dont get how to install naked drivers when everytime i plug in my prime it just says unknown device in device manager and when i try to update the driver it says i have the best or latest driver. plz someone help me!!!!
Click to expand...
Click to collapse
in CWM while the TFP is plugged to your PC, click "update driver" and make sure you point to the location where "android_winusb.inf" file is located.
if you are in CWM the TFP will pick up "android_winusb.inf" driver
if you are in fastboot mode the TFP will pick up "android_apxusb.inf" driver
Also, I had to try on 3 different computers to make this work.

i just found out wat happen the original usb asus was messed up and i brought one on ebay and it worked so all this for a USB cable i was going crazy

urboy4mbx said:
in CWM while the TFP is plugged to your PC, click "update driver" and make sure you point to the location where "android_winusb.inf" file is located.
if you are in CWM the TFP will pick up "android_winusb.inf" driver
if you are in fastboot mode the TFP will pick up "android_apxusb.inf" driver
Also, I had to try on 3 different computers to make this work.
Click to expand...
Click to collapse
Ok so wen i plug in my tfp while in cwm the only thing that pops up in device manager is unown device in the usb controllers section thats it and wen i try to update driver it says i i have the best driver already and im pointing it to a folder on my desktop with the naked drivers and nothing evn with have disk it says its not 64 bit or sumtn. im about ready to give up and just sell it to someone who prolly can fix it cuz i cant seem to get naked drivers to install to let the computer recognize my tfp so i can adb

InkD_up_G33k said:
Ok so wen i plug in my tfp while in cwm the only thing that pops up in device manager is unown device in the usb controllers section thats it and wen i try to update driver it says i i have the best driver already and im pointing it to a folder on my desktop with the naked drivers and nothing evn with have disk it says its not 64 bit or sumtn. im about ready to give up and just sell it to someone who prolly can fix it cuz i cant seem to get naked drivers to install to let the computer recognize my tfp so i can adb
Click to expand...
Click to collapse
as I asked earlier, did you try to set your prime into fastboot mode and flash a fresh rom from there?
if it does not work with windows, you could try linux, e.g. an ubuntu live cd. download the linux fastboot from here
you can flash a new rom with
fastboot -i 0x0b05 flash boot "path to rom blob"
or new recovery using
fastboot -i 0x0b05 flash recovery "path to recovery image blob"
unfortunately i'm not able to supply links to download fastboot, sorry for that.

klutch said:
i just found out wat happen the original usb asus was messed up and i brought one on ebay and it worked so all this for a USB cable i was going crazy
Click to expand...
Click to collapse
wow, I thought you tried a diff cable already?? well, glad it was just the cable for you! I tried 3 diff cables on mine and it still didn't work

apfel.kuchen said:
as I asked earlier, did you try to set your prime into fastboot mode and flash a fresh rom from there?
if it does not work with windows, you could try linux, e.g. an ubuntu live cd. download the linux fastboot from here
you can flash a new rom with
fastboot -i 0x0b05 flash boot "path to rom blob"
or new recovery using
fastboot -i 0x0b05 flash recovery "path to recovery image blob"
unfortunately i'm not able to supply links to download fastboot, sorry for that.
Click to expand...
Click to collapse
yea when i hold power and volume down it doesnt work as usual when it tells you to press up in the next five seconds. and ive tried restoring back up and flashing a new rom but it just boots up into cwm and my sdcard slot is ****ed up becuz of my lil cousins sticking **** inside the slot so it doesnt read anymore so i cant push files or put files on like that either.

pressing vol- + power and vol+ after 5 seconds should lead you into recovery (CWM) but fastboot is somewhat different. if you do not press vol+ after 5 seconds but either wait longer, you will see a screen where to select how to proceed (USB mode, android, and something else). if you select usb and then connect the tablet to your pc you are in fastboot mode and should be able to flash rom and recovery using the fastboot tool on your PC. using this you wouldn't need a working sd card, only a rom and/or recovery in blob format.

apfel.kuchen said:
pressing vol- + power and vol+ after 5 seconds should lead you into recovery (CWM) but fastboot is somewhat different. if you do not press vol+ after 5 seconds but either wait longer, you will see a screen where to select how to proceed (USB mode, android, and something else). if you select usb and then connect the tablet to your pc you are in fastboot mode and should be able to flash rom and recovery using the fastboot tool on your PC. using this you wouldn't need a working sd card, only a rom and/or recovery in blob format.
Click to expand...
Click to collapse
yes i know that but thats the problem im not able to go into fastboot i tried it, it reboots into recovery on its own and i know the only way im going to unbrick this is by adb but my device isnt showing up on my computer just unknown device under usb contollers which i tried to install the naked drivers but is unable to

hmm.. ok thats bad.
do you have a linux machine to check if it is a windows problem?
because it doesn't really make sense to me that CWM is working but adbd not.

i may have found a solution
this is just my experience but it seems like the different adb's that people are posting of the forums are outdated and dont work properly with some primes. I have tried several the windows task manager said "asus transformer prime adb interface" with the naked drivers as soon as i used the adb included in the sdk from <developer.android.com/sdk/index.html> it worked. so install the sdk then in the command prompt navigate to the platform tools inside where it was installed us the adb.exe found there.
as far as using the wrong drivers when you remove the device there might be the option to delete the device driver check that then scan for new devices......point it to where ever you unziped
this may not work for you but this is what finally resurrected my prime after 24 hours

Okay I just had the same problem ... after some research and some trial and error I was able to fix my prime.
First to make your life simple open a command prompt. You will have a flashing cursor next to the directory that you command prompt defaults to.
In my case it was c:/users/peter
You can put the sdk files anywhere on your computer but if you put them in the default command prompt folder you don't have to change the directory with dos commands.
Next with your prime not connected go into the device manager and delete any instances of the prime. Reboot your PC.
Next download the universal naked drivers
Connect your prime, if you go back into device manager you'll find it under USB devices. Click on upgrade drivers and navigate to the universal naked drivers. It should install if not your universal naked drivers might be outdated but uninstalling / deleting the previous instance of your prime should take care of any issues.
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
After this I recommend installing the androidroot.mobi custom boot loader and nvflash to make your prime unbrickable I also changed my recovery from cwm to twrp2 to help eliminate this from happening again.

Same here
What if you only have TWRP Recovery and not CMW? I have the exact same problem, but none of my machines will even detect a new device to find drivers for. I have a laptop with Ubuntu 12.04, another laptop with Windows XP, and an iMac with Snow Leopard. All have Android SDK and ADB but I can not get either to detect the device in Recovery mode. I tried fast boot, but every time I click the USB symbol, the TFP just locks up and freezes and still no detection. Can anyone help? I know if I can get it detected, I will be able to handle the rest.
pcdonovan said:
Okay I just had the same problem ... after some research and some trial and error I was able to fix my prime.
First to make your life simple open a command prompt. You will have a flashing cursor next to the directory that you command prompt defaults to.
In my case it was c:/users/peter
You can put the sdk files anywhere on your computer but if you put them in the default command prompt folder you don't have to change the directory with dos commands.
Next with your prime not connected go into the device manager and delete any instances of the prime. Reboot your PC.
Next download the universal naked drivers
Connect your prime, if you go back into device manager you'll find it under USB devices. Click on upgrade drivers and navigate to the universal naked drivers. It should install if not your universal naked drivers might be outdated but uninstalling / deleting the previous instance of your prime should take care of any issues.
Now do the following:
Make sure your Prime is in Recovery mode (CWM)
Open a cmd line on your pc
Type: "adb shell"
You should see a "#" now
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
After this I recommend installing the androidroot.mobi custom boot loader and nvflash to make your prime unbrickable I also changed my recovery from cwm to twrp2 to help eliminate this from happening again.
Click to expand...
Click to collapse

Related

help am I an idiot part 2

I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
robboy said:
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
Click to expand...
Click to collapse
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
It does change to fastboot usb on red. The only thing I can think of is do you have to install the sdk as I couldn't see a setup app. I just have all the files on the c dive. Will try skipping the first step when I get home
you dont install the sdk, just unzip it
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
jackdaniels_lee said:
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
Click to expand...
Click to collapse
Grrrr still no joy. Just device not found. Im deleting all files that I have downloaded for drivers sdk etc and try and start again from scratch.
Do I need to partion my SD card before I do this as i have been having probs with that as well.
jackdaniels_lee said:
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
Click to expand...
Click to collapse
Done that as well. If My device runs fastboot this should mean the drivers are correct.
robboy said:
Done that as well. If My device runs fastboot this should mean the drivers are correct.
Click to expand...
Click to collapse
yes if u succeed to enter fastboot, it means it had recognised the phone? are u using windows 7 by the way? cause u have to download the precise drivers for the OS u r using whether x64, win 7 ....
I seem to remember having problems with this until I enabled the USB debugging mode in the options somewhere.
As for drivers, I'm running Windows 7 x64 and the x64 Vista drivers did the job fine.

[Q] Adb commands to install TWRP

So I unlocked my Prime on .21 and I've been trying to get a recovery on it with no luck. Obviously, I can't use Rom or Goo Manager as it's not rooted. I can't flash a zip file because I don't have a recovery. I've tried installing it in fastboot with no luck. From what I've read fastboot is not an operable command on the Prime so I tried installing the universal naked driver and using the provided commands with it. According to the directions I have to unistall previous drivers....I have a LOT. If that's the case I might as well try on a fresh PC as I have Moto, HP, HTC, Samsung, etc drivers installed.
Back on topic - TWRP's page ( http://teamw.in/project/twrp2/93) provides commands for "ADB / Terminal" to install their recovery but the commands provided are clearly for terminal emulator which I'd have to be rooted to use. So how do these commands convert to ADB?
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Any help is much appreciated! I really don't want to downgrade to root and install recovery. If I can't get fastboot or adb to work, I'll keep that as plan C.
Sent from my DROID RAZR using Tapatalk
Use fastboot it's easier. http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/ and obviesly replace cwm with twrp.
Sent from my Transformer Prime TF201 using XDA Premium App
Makrilli said:
Use fastboot it's easier. http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/ and obviesly replace cwm with twrp.
Sent from my Transformer Prime TF201 using XDA Premium App
Click to expand...
Click to collapse
I cannot get fastboot commands to work on my Prime. Do you have the Universal Naked Drivers installed and have you used this method?
Sent from my DROID RAZR using Tapatalk
I used this one and I didn't have to install any drivers, worked out of the box. What do you mean about you couldn't get fastboot to work. Did you also write -i 0x0B05 between fastboot and flash
?
Sent from my sgs2 running cm9
I probably should post this as a seperate guide, here :
-----
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
----
Hope this helps.
Hobbesian said:
I probably should post this as a seperate guide, here :
-----
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
----
Hope this helps.
Click to expand...
Click to collapse
Thanks for the tutorial. I'm fairly familiar with adb and fastboot. My problem lies in the fastboot drivers. I was not able to install the Universal Naked Drivers. If I tried to install them over the existing drivers it failed. If I deleted the existing drivers, I was not able locate the device to install the new drivers. I would either reboot the computer OR unplug and plug the device in but each time the old drivers would auto install. Again, thanks for your input and I'll give this a go when I have some more time.
Sent from my DROID RAZR using Tapatalk
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Hobbesian said:
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Click to expand...
Click to collapse
I didn't have an issues with the adb drivers. I don't why fastboot is being such a pain.
Sent from my DROID RAZR using Tapatalk
joshw0000 said:
I didn't have an issues with the adb drivers. I don't why fastboot is being such a pain.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
All the problems you see is with people that is using Windows.
Sent from my i9250
Hobbesian said:
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Click to expand...
Click to collapse
Just wanted to shoot a quick thanks. I finally found time to tinker with my Prime and turns out I had the drivers properly installed but was booting to recovery not fastboot, hence fastboot device wasn't found. When booted properly, it flashed the first try. I'm now TWRP recovered and Gummy rom'ed. Its amazing how one can overlook a simple step and until someone plainly states it, they never even question it.
Sent from my Transformer Prime using Tapatalk

Nothing but fastboot!!!

I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
Sent from my Transformer Prime TF201 using Tapatalk 2
Second option, tell your cousin he owes you 500 bucks, go buy a new prime or infinity and give him the one he broke.
Skitsofrantik said:
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Click to expand...
Click to collapse
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
I've tried that but thanks for the input
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
lilstevie said:
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
Click to expand...
Click to collapse
I'm gonna try this. Thanks for the tip.
Skitsofrantik said:
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Tried NVFlash
I tried NVFlash but I can't get past the first step. When I do this command fastboot -i 0x0b05 flash staging ebtblob.bin I get this result:
sending 'staging' (998 KB)...
OKAY [0.962s]
writing 'staging'...
FAILED (unknown status code)
finished. total time: 10970.597s
Anyone know what's going wrong?
SOTK said:
Skitsofrantik said:
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
Skitsofrantik said:
SOTK said:
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
If you go into device manager and rightclick the asus android device then update drivers. Now do not let windows choose, do it manually and point windows to the naked driver... Also there are 2 drivers.. one for intel 86 and the other for amd... 64 the numbers are at the end of the file name if I remember correctly... be sure to choose the correct one for your pc chip otherwise yeah you can do it all day and get no where... When you try adb, I will assume you are in recovery mode and not fastboot because they are 2 different horses... If you only have fastboot then you should consider installing an older version of twrp like 2.1... I posted it somewhere in here.... that should get you into recovery where you can adb a rom to the prime.... check for posts by me, I have explained this a few times here.....
From a previous post.....
go here ....http://forum.xda-developers.com/show....php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/show....php?t=1774352
start again from ******now boot to recovery....
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/show....php?t=1782413
Download and install http://forum.xda-developers.com/show....php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Click to expand...
Click to collapse

[Q] Sprint optik can't switch to USB Debugging mode after flashing kernel

Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
mdky said:
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
Click to expand...
Click to collapse
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
For more info, you should check Android's page on ADB if you would like. http://developer.android.com/tools/help/adb.html
I'm not sure if any of this is actually directly related to your issue, but it is nice to start with the basics.
wildstang83 said:
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
Click to expand...
Click to collapse
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
mdky said:
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
wildstang83 said:
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
Click to expand...
Click to collapse
I will try these command when I get home, thank u!:good:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
mdky said:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
Click to expand...
Click to collapse
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
wildstang83 said:
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
Click to expand...
Click to collapse
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
mdky said:
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
Click to expand...
Click to collapse
Oh wow, that is quite the ordeal, but atleast its something huh, lol
I wonder if you could run adb and fastboot commands in xp mode on your win7 pc?
I know there is a way to run programs in XP mode, its just been awhile since I've done it.
And its no problem to keep trying to help, even if I don't know the device and all that. Maybe I can learn to while we are at it, and maybe make a new friend along the way

[Q] bricked prime ?

hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
jojo665 said:
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
Click to expand...
Click to collapse
First of all try adb push Name_of_Rom.zip /sdcard/
If that does not work try adb push Name_of_Rom.zip /system/media/
If that still does not work then download the correct TWRP blob file from the following link for your bootloader. http://www.teamw.in/project/twrp2/93
The fact that you are on CWM and was using CM 10 makes me believe that you are still on the ICS bootloader but to make 100 percent sure when you first power on the device look at where the "NVIDIA" logo is. If it is bottom center it is ICS, if it is bottom right it is Jellybean. (MAKE SURE YOU GET THE CORRECT TWRP VERSION FOR YOUR BOOTLOADER)
Now rename the blob file you downloaded to twrp.blob. Go into fastboot and type the following.
fastboot -i 0x0b05 flash recovery twrp.blob
This should install TWRP which will allow you to install a rom off an external micro sd.
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
jojo665 said:
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
Click to expand...
Click to collapse
What exactly did you do? I'm trying to extinguish all avenues before I have to RMA my tablet. Thanks for the help!

Categories

Resources