I've been trying to root with viperboy's Primetime but when I connect my TF201 to my computer it shows up in device manager only as the TF201 and not as any sort of ADB interface. I've tried all the drivers I can find including those included with viperMOD and Asus Sync. I've followed all the other instructions to the letter. Video tutorials aren't helping because they all seem to effortlessly get ADB going. My firmware is 2.13 and yes, I do have USB debugging ticked on (when I toggle it back and forth device manager does refresh but doesn't seem to connect or disconnect any devices). I've also tried adding legacy hardware and under the Android Phone category there are drivers listed from both Asus and Google for ADB interfaces among other things, but when I try any of them the device ends up with a code 10 (cannot start). I've already spent hours trying just to get ADB going, please help me if you can.
Please help!
fezir said:
I've been trying to root with viperboy's Primetime but when I connect my TF201 to my computer it shows up in device manager only as the TF201 and not as any sort of ADB interface. I've tried all the drivers I can find including those included with viperMOD and Asus Sync. I've followed all the other instructions to the letter. Video tutorials aren't helping because they all seem to effortlessly get ADB going. My firmware is 2.13 and yes, I do have USB debugging ticked on (when I toggle it back and forth device manager does refresh but doesn't seem to connect or disconnect any devices). I've also tried adding legacy hardware and under the Android Phone category there are drivers listed from both Asus and Google for ADB interfaces among other things, but when I try any of them the device ends up with a code 10 (cannot start). I've already spent hours trying just to get ADB going, please help me if you can.
Click to expand...
Click to collapse
I hate to sound like a noob, but I am having the same problem!!!!
I went through the developer forum and found a response from "Ciddy", on the matter, this is the link { http://forum.xda-developers.com/showpost.php?p=21049320&postcount=89 } , this seemed to work for several other people, but not me.
This is what happens:
1. Uninstall Asus Sync (BTW Asus Sync does not detect the TP for me either).
2. Hit Win+R, enter "devmgmt.msc" (no quotes), brings up device manager.
3. Connect the prime, when it shows up in device manager, select it and hit Del.
Then search for new hardware and install the supplied drivers.
4. After the first reboot of the prime, check the device manager, it should show Asus MTP device [ THIS IS WHERE THE DEVICE MANAGER DISPLAYS Transformer Prime TF201, NOT Asus MTP device] with a notification; update its driver from the Viper pack.
ADB does not detect the TP in command promt. Windows 7 64x. Everything is updated, I have ADB from rooting HTC's and several other android device's. I have reset the TP to factory default's twice. and I have read and read, and have not found anything, PLEASE HELP!
** PS. I am only able to transfer files with Windows Explorer.
*** Calling Asus Support was pointless, they aren't even familial with ADB.
I have the Android SDK/Eclipse loaded on my machine so ADB is fine for me, of course. So, cannot help in your situation.
I wonder if you have considered downloading the Android Terminal Emulator from the market and just entering your commands directly on the Prime? The first time I rooted a phone, that's the way I did it, since I had no clue what ADB was. Not a permanent solution to your problem, but perhaps it can get you by for now.
Of course, I may be missing something as to why this won't work...
Edit: I read up on the TPSparky root and Viperboy's tool ... pretty sure at this point that what I am saying above will not work.
Resolved
I resolved the issue. There is still something blocking me from ADBing into the tablet with my Windows PC but I tried on an Ubuntu box and it worked perfectly. I am now successfully rooted.
How did you solve it?
yoinjo said:
How did you solve it?
Click to expand...
Click to collapse
I used a computer running Ubuntu. Never got it working with my Windows laptop.
I installed http://forum.xda-developers.com/showthread.php?t=1426502 drivers and now my TF201 shows under Android Devices (Asus Transformer Prime ADB Interfaces). ADB however still returns error: device not found
So I've solved the problem too.
I've used an old 32bit XP computer with 2.0 USB
I had that problem....i sovled it.......it was me...i forgot to go into settings on the TP and under dev options make sure USB debugging is checked.....after i did that everything went smooth
Sent from my Transformer Prime TF201 using Tapatalk
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Any update on this?
When having started the tab normally it gets recognised with device id.
When in fastboot mode - nothing
I installed several driver but the tab does not get recognised (2PCs win7)
YodaDaCoda said:
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Click to expand...
Click to collapse
i got here same problem, any progress on this one? did you already found a way to fix this issue? thanks.
YodaDaCoda said:
I'm having a similar problem. I've spent the last three days on-and-off trying to get this thing to show up in ADB.
So far, I've tried using both Ubuntu and Windows 7 (both x64), both detect the device and Windows shows it in Device Manager as "Asus Transformer Prime ADB Interface" - using the Univeral Naked Driver Beta 0.6.
Unfortunately, when I do adb devices, all I get is
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
It's probably worth noting that I previously rooted using mempodroid but (like an idiot) didn't install RootKeeper and when I got the OTA from 9.4.2.11 to 9.4.2.14, I lost root, and haven't been able to make it show in adb ever since.
Can anyone shed some light on this issue? I'm rather missing root.
Click to expand...
Click to collapse
Sorry for asking an obvious question but are you in recovery when you are trying to do adb? If you are then download the nvflash file from dev thread, unzip it, open the folder until you see the adb.exe file.
Press and hold shift on the keyboard, right click in the window and select command prompt here.
Now do adb devices it should show up.
I am having the same problem. I have tried all available drivers on internet from number of forums. Still no luck . I have also tried from Windows 8 64 Bit and Windows 32 Bit laptops. From the same laptop, I was able to connect my Xperia U and it showed under "adb devices". What am I missing? I need to install custom ROM. Please help.
Did anyone solved this problem? I have Win 7 64-bit and have been following a thread on installing Crombi-KK
After adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard, Hairybean TWRP was installed and now i need to boot into fastboot
but adb is no longer working.
I tried reinstalling drivers for TF201 but no adb access.
update1:
Ok. I managed to solve the first problem with no ADB access. In recovery I clicked to Reboot, and clicked System. While system was rebooting I was holding Power Down and got into fastboot mode. I lost ADB access but apparently still have fastboot access so I have proceeded with the instructions to flash blob
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob, then
fastboot -i 0x0b05 reboot-bootloader
In recovery the instructions say format next, so now I am currently formatting, so I will update everyone who need this.
I still don't know why I lost ADB access which I had. Some people here suggested ubuntu but I don't have it.
After formatting I will need ADB to push crombi to device, but I twrp recognizes SD card so if I don't get ADB access after formating I will
try to copy crombi-kk to SD card and then flash it from recovery. I will write what happened when formatting is done.
update2:
After format which took 30 minutes I suddenly have ADB access. Wtf??? Anyway I pushed crombi-kk zip on the tablet and flash it. After 5 minutes of flashing everything working great. Will send a donation. Tablet with stock 4.1.1 was slow 4.4 is great. Thanks everyone who made it possible.
Related
Hi comrades!
Ihave unlocked prime 32dock.
Yesterday I tried to flash the firmware KJY2010 Primalicious 9.4.2.21.
1) First, I installed the CWM 5.8.2.0 - successfully
2) rebooted several times - everything was OK. The factory firmware loaded.
3) Then I found the instructions KJY2010 Primalicious 9.4.2.21 - is successfully established.
4) The new firmware is loaded. I set up wifi, google account and decided to reboot.
5) After rebooting, I was constantly load in the CWM.
I go to instruction Brick 1a
adb give me this result:
Code:
c:\Tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
c:\Tools>
I try 2 other Prime usb driver - result the same. (In device manager Asus transformer Prime set OK, whithout any warnings)
I try do this under Linux - result the same.
What else can i do in this situation?
I have backup image and i try do restore - result the same.
I try wipe data - result the same.
Please HELP.
See this thread to get your Prime recognized by adb:
http://forum.xda-developers.com/showthread.php?t=1426502
thanks
tedr108 said:
See this thread to get your Prime recognized by adb:
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
big thanks.
I already tried this driver yesterday, but was inattentive. did not remove the old drivers first.
Who made everything clear to the user manual (deleted the driver and rebooted the computer).
It worked! Thank you and the author of the driver! My tablet is restored.
I had this problem with my prime with it 1a bricked. so i tried it on my laptop instead of my desktop and was able to adb. Think my desktop needs a reimage but i was not in the mood to do it.
yurmala22 said:
big thanks.
I already tried this driver yesterday, but was inattentive. did not remove the old drivers first.
Who made everything clear to the user manual (deleted the driver and rebooted the computer).
It worked! Thank you and the author of the driver! My tablet is restored.
Click to expand...
Click to collapse
FIXED!
Hiya mate, any chane you can write down your procedure if thats cool, ive got the exact same issue as you,
- ive deleted anything that looks like a driver pack from asus in my add remove program (im on xp)
- ive uninstalled the driver from the listing in the device manager (Android Phone > Asus Transformer Prime ADB Interface) which comes up when i hook up the tab while its in CWM
-restarted comp, connect my tab, point xp's driver install program to the universal naked driver folder
- all set, yet still getting the device not found
I have adb folder in C:\ directory
CMD into the run menu
CD change C:\
cd adb
adb shell
daemon not running. starting it now on port5037
daemon started successfully
error: device not found
Been looking around for a while now, pulling my hair out, a few snippets here and there, some have been successfull, but no detail on how they got it fixed
Out of all of them, your situation best describes the one im in at the moment, am i missing something?
Hoping you or anyone really, have a solution, and perhaps help anyone else who might get into a similar situation
By the way, for the record, my brick occured because i stupidly Factory/Reset using the ROMS ( Virtuous Prime/Stock kernel) menu, rather then CMW's Factory/Reset
Any help would be mucho appreciated
Edit: Sorry ive just realised how old the thread is, hope no one minds, if not
-Tried asus sync
-Tried pdanet?(is that right?) drivers
- Hoping for a solution that doesnt involve deleting internal sd card content as ive got 1 or two nand backups im in the process of streamlining, if thats possible that is
Edit 2
Ok, managed to get past the device not found part,
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Installed another version of adb(link above, follow instructions), i guess the adb i was using was a dud
Edit 3
Fiiinaly fixed it, problem was adb, for anyone who might have similar symptoms try installing and following the instructions in the link just up there ^^^^
And to be thorough, follow the instructions written by Diamondback (option 1a)
http://forum.xda-developers.com/showthread.php?t=1514088
Heres the snippet, if Diamondback dont mind?
Once adb's installed correctly
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.
There you go folks, if a noob like me can do it.......well, you get the idea
Hi everyone,
Well I'm in that freak out stage.... where I am sure some of you have been.
Heres my issue...
I have a transformer prime that;
I just unrooted using Vipermod
Then did a factory reset
Now I am stuck in CWM recovery
I attempted to do a restore but after it gets done it brings me back into the recovery
I attempted to ADB but the command prompt opens and closes right away ( I assume from not being in USB debugging, which I cant get into without a rom)
I have no rom's currently downloaded into the prime as I just wiped everything in there as well.
Please i'll gladly pay $5 to anyone who can fix this without it breaking more (hard bricking if I havent already done so)
AHHH please guys help, I'm afraid it will run out of battery soon then I'll be royally screwedddd
anyone?
are you on windows 7?
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
birchnick10 said:
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
Click to expand...
Click to collapse
Turn on your tablet, let it boot into CWM.
Open cmd, cd to the directory with adb (for example cd C:\android), then copy this line of text below and right click > paste in the command prompt window.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
That should get you out of CWM into Android, assuming your restore works fine.
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
can i fastboot push a rom to the internal sd card or better yet can i install a rom from the external SD card via Clockwork mod recovery?
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
Navigate to %android sdk folder%\extras\google\usb_driver, open android_winusb.inf and copy the following in the sections
"Google.NTx86" and "Google.NTamd64"
; TF201
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
;
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
Click to expand...
Click to collapse
Save the file and then try running the adb command I gave again.
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
birchnick10 said:
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
Click to expand...
Click to collapse
Try the instructions here. Try using this only as a last-ditch resort.
it wont shut off either... i tried both of the above mentions and cant get adb to recognize the prime
Attempted both and stuck at recovery loop without root. any more ideas? is it possible to flash rom from external sd? or is there a recovery I could fastboot rhat has this feature?
Attempted both and neither work. I need to somehow get usb debugging enabled while in clockwork mod. Or figure out a way to install a rom via external SD card while in CWM. Any more help is appreciated!
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
No adb debugging is needed in cwm. Even without any ROM installed. Recovery is different from Android.
Try to long press power (at least ten seconds) to hard reboot, and see if it changes something in device detection.
Did a hard reset and it boots me back into Recovery.
I was able to get a new rom into the internal SD via the emergency/backup.zip method but after it completes and I do a reboot it just boots right back into recovery again.
Any help please is apprecaited.
$5 bounty for a fix via paypal
Oh joy. This one is a spaghetti western in the making.
Okay. Question first : Does Windows 7 RECOGNISE the device in any way shape or form. To find out if this can be done, you need to power up the device and hold the power and volume down buttons, DO NOT press volume up when it suggests a kernel image. If you get three icons, hit vol down once and up once, then plug the USB cable into the PC and the tablet.
If it sees "Something", you've a chance. Download the naked universal USB driver from the dev forum, install it and have your device pick it up on the windows computer. I'm assuming from your comments that you've GOT a working fastboot and adb so I'm going to skip the instructions on that.
If you do have a something, and it's recognised, hit fastboot -i 0x0b05 reboot, if it reboots of it's own accord at this point, you can confirm you have working ADB and Fastboot access. From there you've a few choices. My personal preference would be to ADB push a rom down -after- doing a rebuild of the recovery image via fastboot (I really recommend TWRP for this bit).
http://forum.xda-developers.com/showthread.php?p=26093546#post26093546 - This post here which I wrote will explain how to flash TWRP from fastboot access, presuming you can get it. Once that step is done, wipe EVERYTHING from TWRP, and I mean the whole nine yards, including /system. Raze the memory down to only things it can't actually nuke. Once that's done, reboot to fastboot protocol, get a ROM pushed via ADB and install from inside TWRP.
That -should- get you back in business. Though judging by the tangle you're in, I make no promises.
ADB wont recognize the device. I have installed and uninstalled the drivers about 5 times.
It wont boot into fastboot - just goes directly into Clockwork Mod recovery. Even while holding power and volume down text comes up that says looking for asus recovery. then says clockwork recovery and boots directly into that.
The only way I can get anything into the internal SD card is with MasterZen88's Emergency script tool that puts any 1 file into the internal SD card as backup.zip
It was unrooted prior to all of this as well.
*cringe*
If ADB isn't working -at all- and it's not using the naked USB drivers to get you any kind of workable access. You're starting to smell very much like a hard brick scenario. I'm honestly not sure if there's a way out of that. A lot of the solutions for unbricking absolutely require that the device is able to talk to the outside world, if it's not and the ADB shell is essentially telling you it's talking to dead air, you're in a world of pain.
It's a long shot but it may be worth speaking to ASUS to see if they are willing to, for a fee, restore your tablet to factory settings. Though I can't imagine that will be cheap or simple. If you are able to get an RMA or a means of getting ASUS to poke it, make sure to take photos. Their techies appear to have the worst case of butterfingers in the world.
Go over Pandaball's suggestion, because that's really the last step I can think of before contacting ASUS
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Have you reviewed the jmztaylor method?
Have you reviewed this method?
http://forum.xda-developers.com/showthread.php?t=1905674
Worked for me after I grabbed the drivers from PDAnet.
I have one issue of Android is Updating stuck in loop that some others in that thread have sorted out but I can't quite get working yet!
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
same problem.
I am having the same exact problem. I have reviewed the jmz method and keep getting stuck in cmd saying path not specified. Any solutions. All steps have been followed to the letter.
watchdog153 said:
Never even heard of rooting before last week. I decided to buy the Nabi 2 for my sons Christmas gift
Trying to get the thing rooted, Im a total No0b at this
Ill try to explain at what point in the process im at... When i type "adb devices" in the command promt the nabi is listed (some serial number)
but when I type "fastboot devices" i get nothing listed
I tried running the root process and got a andriod guy laying down with a red exclamation point over his corpse, also alot of "cant recognize device" error messages in the command menu
I dont think fastboot is working... can anyone tell me how to enable fastboot?
Thanks so much
Update*
Ok I just tried to run the root installer a different way (last time i was in the bootloader menu)
This time the tablet was fully loaded and screen unlocked. I ran option number "1".
The command promt returned this:
# waiting for device . . .
# If stuck here drivers are not installed
The system cannot find the path specified
# Rebooting device
The system cannot find the path specified
# press enter when you see text on the screen after Nabi logo
# If stuck here drivers are not installed
press any key to continue . . .
What drivers? I used PdaNetZ350 to install drivers... I dont know what im doing wrong
Click to expand...
Click to collapse
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
cruise350 said:
Make sure you are only selecting option #2 in the script, option #1 doesn't work. Follow the on screen instructions exactly. If it isn't recognizing the nabi in the script than the drivers aren't installed or try a different usb port. I couldn't get it to work on my win 8 laptop but was successful on my windows 64bit desktop. Using the pdanet drivers is the key. Just because you can plug the nabi into your computer and see the drive contents doesn't mean the drivers are loaded. Windows sees the nabi as a media device and uses generic mtp drivers that won't work with adb. Once you have successfully rooted your nabi, go back into recovery and install the gapps.zip separately. Enjoy!
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
This thread goes through doing it manually, it is written for Ubuntu(linux) but it can be used in windows as well, you just don't use sudo for the commands. Also the package in the following thread already has the updated gapps package that does away with the "android upgrading" on every boot.
http://forum.xda-developers.com/showthread.php?t=2016463
fast boot won't install
Had ''path not specified'' it gets to the if stuck here drivers aren't installed. A window pops up saying ''installing fast boot'' but then says it failed. Thats where im stuck.
4.1.1 OS
2.4 product version
Thinking the 2.4 update is a problem.
Any suggestions?
I know i'm years late here but I really HATE adb and esp. BAT files that are just suppose to do their thing........I'm hitting a wall with this Nabi 2 Bat file for TWRP / ROOT. I've used PDAnet plenty in the past for internet but never for the purpose of just getting drivers so I have no idea I hate that program too. ANYWHO , I'm getting "cannot find specified path" which I probably could fix if I ****ing knew which ****ing path it was looking for. SO if anyone could please enlighten me here , I've installed and uninstalled PDA net some 10 times now , with Samsung selected , with LG selected with OTHER selected , I cannot get this to work. I can do FASTBOOT devices , and poof it shows up , adb works fine all that , show the device but I cannot get this ****ing BAT all in one installion to work. I'm really just about to flash it all manually through ADB but I'd rather use the installer to make sure I get the random WINGS files removed or whatever. Any help would be great , thanks.
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
I have a HTC Google Nexus 9 tablet. I recently received the update to Android 6.0.1 via the normal push notification. The update got stuck on ‘optimizing your apps 1 of 74’. It normally moves up in the numbers within minutes but it remained on ‘1 of 74’ for an entire night. So, the next morning I switched off by holding the power button.
The system still booted but soon enough I received error messages like ‘there is an internal error, contact the manufacturer’ and during the boot it says that my system was corrupted.
I decided on a factory reset. It went through with it. But when setting up the cleaned system, there is another problem: I can pick my language and connect to my WIFi without problem. But then it goes to a screen where it says ‘checking connection. This may take a while.’ It gets stuck there for several hours - so it is clearly faulty as I don’t think ‘a while’ means 12 hours and more. I also don’t think that the factory reset solved the problem anyway as I still receive error messages, hinting at a corrupted system, during and after the boot.
So, I decided to try to flash a system image.
I got the Minimal Android Debugging Bridge ADB and Fastboot on Windows 7 and Ubuntu,
Then I followed the Google developers instructions and downloaded Volantis MOB30D from there.
I also got Android drivers for Windows, but I’m not entirely certain if they are right.
When I connect the Nexus 9 to the Windows computer, I now see in Device manager: ASUS Android Devices -> Android ADB Interface
It’s not an ASUS tablet though and I can’t see the Nexus 9 in ‘Computer’ (it used to show up there as ‘Portable Media player’
Is it possible that I got the wronger drivers and if so, how would I install the correct ones?
Then I start the Nexus 9 and hold power and volume up down to get to the bootloader.
It says ‘Fastboot USB’
I also says ‘device state - locked’ . I can’t get to the system settings to do the OEM unlock as I’m stuck on ‘checking connection’ when I boot normally.
Then I opened ‘Minimal ADB and Fastboot’ on Windows and tried the following commands:
Fastboot flashing unlock
… and it says:
FAILED (remote not allowed)
Then …
Fastboot oem unlock
… and it says:
(bootloader) ability is 0
(bootloader) permission denied for this command
Then I tried the same on Ubuntu. The device doesn’t show in the left hand side panel. When I try the above commands it just says
waiting for device
So, I guess Ubuntu doesn’t even recognize the Nexus 9
I then opened ‘Additional Drivers’ but it just says searching for available drivers and then no proprietary drivers are in use on this system
Any advice for Nexus 9 drivers on Ubuntu?
I also tried from the bootloader: Hboot → Recovery → Apply update from ADB
In Ubuntu I went to the directory where the ZIp file of the system image is located
Then I typed in the terminal:
adb sideload image-volantis-mob30d.zip
And it says …
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
1. You don't have correct drivers for Nexus 9. The Nexus Root Toolkit has a driver instillation guide.
2. You can not sideload factory images.
Try sideloading the failed ota available here
Code:
April 2016 Nexus OTA Updates - Security Level 2016-04-02
Nexus 9 (LTE) [URL="https://android.googleapis.com/packages/ota/google_flounderlte_volantisg/9ae7d85d6433d055a9e4f3049ac86eb0e562bbf1.signed-signed-volantisg-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
Nexus 9 (Wi-Fi) [URL="https://android.googleapis.com/packages/ota/google_flounder_volantis/6a2119f2077022c1ba852f2c613b8ce942c33836.signed-signed-volantis-MOB30D-from-MMB29V.zip"]MOB30D from MMB29V[/URL]
If that doesn't work try sideloading Android N OTA
aeglyss said:
Any advice for Nexus 9 drivers on Ubuntu?
Error: insufficient permission for device
I’m running out of ideas. Can anyone help?
Click to expand...
Click to collapse
I don't know specifically about Ubuntu, but I've done several updates to usb-connected android devices using Debian linux, and I've never needed to add a device-specific driver.
Some additional ideas on the permissions:
(1) Did you enable "USB Debugging" in Settings->Developer Options?
(2) From your Linux machine, did you try to run adb as the root user or use sudo? I have to do this for both adb and fastboot. (Example command line: '$sudo adb devices', without the quotes.)
(3) Finally on the Linux side, did you try to connect first via adb? And, if so, did you look on your Nexus for an "Enable..." approval notification?
Good luck!
cheers,
john
Thanks everyone. I managed to fix it
aeglyss said:
Thanks everyone. I managed to fix it
Click to expand...
Click to collapse
Hi, I am at a similar point, my Google Nexus 9 failed doing the update, I then tried to factory re-set it and now it is trying to check connections...
I have downloaded the bootloader and my Windws 10 pc can see the tablet via explorer. I believe I have also switched the tablet to Fastboot but bootloader doesn't sem to be able to make the connection.
I was wondering if you are able to provide me with instruction as to how to rescue this tablet. I am not an expert, so I would appreciate any instructions to be as simple as possible.
Thank you for your help,
Mike