Related
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Uberjim said:
Hello being the noob i am i cannot restore any roms to my prime i accedntally wiped the whole internal partition and currently only have twrp installed it is version 2.2.0 i cant seem to get it to show in windows nor do i know the command in twrp for the sd card as i have a rom on there but it wont let me access it. im pulling my hair out and at the moment my prime wont swich off as it just keeps turning itself on and going to the ee pad logo and stopping there
can someone please help me to get it working again its probably simple but ive about had enough !! also cant get adb to work as the drivers keep faling to install on my pc error 10
HELP !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Slight update used wsg unbricker and now running clockwork mod instead of twrp dont know if thats good or bad at lest it proves pushing stuff to it works to a degree
Click to expand...
Click to collapse
Still trying to fix this I now have no recovery and just get the two icons wipe data and fast boot or it just keeps trying to load a Rom that isn't there so it sticks on the main logo screen if I could get it to show in windows that would be great but now I have no recovery I'm not sure how to even get it to install anything once I do !
deleted
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
kokopuphz said:
As long as you have the fastboot logo, there should be hope. First, you will need to do whatever you can to get your computer to recognize fastboot mode. In order to do this, click on the fastboot icon on your prime and then plug your usb into your pc. What does windows say? Is the device showing in the windows device manager?
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
It shows up but then says failed to install driver will try it on different pc,s see if it works thanks for the replies seems fairly easy
Ive found on my device that it sometimes requests two different drivers. One for adb/fastboot, and one for mtp. I just cancel the one for mtp as they are not in the naked driver set, and windows then detects another different device.
Sent from my SO-01C using xda app-developers app
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Uberjim said:
okay fast boot is working and the android bootloader device shows in installed drivers but when i type in adb devices nothing shows up ?
Click to expand...
Click to collapse
Okay, you're half way home! The reason why nothing shows in adb is because fastboot and adb are two completely different interfaces. When in fastboot, your device will be expecting the fastboot command only.
Now what you will have to do is find a recovery that is in the blob format. Cwm would probably be okay. Twrp would be good, however the new version requires the nvflash version of the bootloader.
Once you find the blob of the recovery you want, place this in the same folder as the file fastboot.exe
It should be in the same place as adb. If not, place the blob somewhere easy to remember.
Then in a command prompt, type
fastboot -i 0x0b05 flash recovery blobfilename
If you placed the blob in the same place as fastboot, then the above will be the blob filename, or better would be to include the path as well.
Sent from my SO-01C using xda app-developers app
Looks like this could help
http://forum.xda-developers.com/showthread.php?t=1662158
Sent from my PadFone using Tapatalk 2
hi guys and girls happy to report that thanks to the community my prime is aliiiive !!! used a utility off here called knives and forks to install adb and then downloaded fast boot and extracted to my users directory then used the fast boot command to push the blob to the prime into recovery then used adb push adb push virtuous_prime_s_9.4.2.21_v1.zip /sdcard/ and installed virtuous to get it running then it all shows up thankyou to everyone so happy took all of five minutes lol. my trip to london for 3 hours will be less boring now !!!:laugh::highfive:
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.
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
ICruentusI said:
I've read around on the forums trying many different things, but my problem is still here. ADB finds my phone when I am in normal phone mode, but once I go into fastboot mode it shows an empty list of attached devices. I've tried multiple different drivers and I've yet to have it show up. I tried on three different computers so far to no avail.
My friend got it working on his laptop once and flashed a kenel onto the phone that broke my wifi.. and we can't get ADB to load again to flash back the original. Sigh.
Can someone please help me?
So far I've tried HTC's drivers and the Universal drivers found on the Nexus forums. My Device Manager says Android USB Devices -> HTC, Corporation when my phone is in fastboot mode. the adb command shows List of devices attached and a black line after that. I'd show images if XDA didn't block me.
Click to expand...
Click to collapse
Adb doesnt work in fastboot. Use fastboot flash boot boot.img then flash the kernel modules in recovery.
Sent from my HTC6435LVW using xda app-developers app
Wow
Thank you very much. Complete noob at playing with Android devices .
When you flash a kernel, you have to make sure to also flash the kernel modules in recovery. That's what caused the wifi to stop working. Same thing happened to me haha.
Sent from my (Viped out)³ DROID DNA
Hi anyone willing to help. I have had a friend's TF201 for about a month and have come to the point where I can't get any further. We believe heis device has been bricked during the OTA JB update. nvFlash was never added to device.
I can get it into fastboot, however the device does not show up in device manager or shows in ADB. I have confirmed ADB working by using another device that shows up. I know that it is currently on an ICS bootloader, since the NVIDIA logo is in the center bottom. We have tried a different cable and same results.
MOST IMPORTANTLY: which I have not been able to find any literature on is that when it is booted into fastboot only 2 icons appear: 'Wipe Data" and "Fast Boot" USB Icon. There is no Android icon...THIS confuses and scares me.
Is there any hope for this device? I have done so much research and time on this, but can not come up with anything else. Anyone??
Tried connecting in ADB in Win, Mac and Ubuntu. Not showing up? Totally stumped now.r
Bump.
ZeroLozen said:
Bump.
Click to expand...
Click to collapse
You do not have access to adb in fastboot. Only in a custom recovery or in the OS.
You do have access to fastboot commands tho if you have the drivers installed.
Having bricked a tf300t with the 4.2 Ota, I feel ya. Make sure you've got the correct drivers. Look at connected devices on your PC, it should say fast boot device, if it does, then your drivers are fine, going into fast boot, fastboot devices in cmd / however you have your fast boot set up. Look for your devices serial number.. It should show serial , if your drivers are correct..
Sent from my ASUS Transformer Pad TF300T using xda premium
I have tried all necessary things for drivers including the naked driver set for Win. Device wont show up in Linux or Mac environment either. it appears that the fastboot is ICS but it received the OTA JB update. Is there a way to recover from this? The other thing that concerned me is that in fastboot there is no Android Logo (just wipe data, and USB). Is this device recoverable from this state?
You have the upgraded bootloader. They removed a few things but it goes instantly to download mode..... when plugged in to pc. What does it say under control panel / hardware and printers. . When you plug it in. Does it make the tell tale sound?
Sent from my SPH-D710 using Tapatalk 2
Actually I think the incorrect fastboot had been loaded before I got it. To my understanding the OTA JB update was applied and then fastboot was added (but if the nVidia logo is in the center, that is the ICS fastboot correct?) So is my problem here that the incorrect fastboot had been flashed?
After upgrading to CM 12.1 everything was just fine. Got my tablet to charger and left it there for a while. And then i saw that i was looping.
It's trying to enter recovery (TWRM) "or something like" and restarting.
I' sitting on forum for 3 days already. trying to get some information and did lot's of things. Nothing helps.
Can anyone help me with this somehow? I'm almost crying and losing it (not really, but that what i feel inside)
Please. Any help. I think I've read all forum about this thing.
Thank you.
Do you have the real TWRP (i.e. not Safestrap!) & an unlocked bootloader?
don't think so. or better say i'm not sure about it. how can i check?
Edit:
i can run adb and after command "adb devices" it shows serial number and status: recovery.
i can use the command adb reboot-bootloader which puts me in fastboot mode. but then i try adb devices and have nothing there.
also, any command like "fastboot...." gets me to "waiting for device" and nothing more.
I tried two different computers. all ports. all cables that i've found.
Edit 2:
also after command "adb shell" i ca see "~ # ←[6n" and i can put there only reboot command
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Cl4ncy said:
Well, first of all CM12.1 requires TWRP & an unlocked bootloader, if you don't have those, flashing CM12.1 was a bad idea.
So what happens during boot? Do you see the Safestrap logo and had to either wait 10 seconds or press continue to boot? Can you enter Safestrap there by pressing Recovery? Which Safestrap version is it (if any)?
The real TWRP can be accessed by pressing and holding Volume up, then pressing and holding Power, release both when the grey Kindle Fire logo appears on screen.
As having TWRP is a key requirement here, it's important to figure out what you really have (either Safestrap or TWRP).
And do NOT do a factory reset in amazon's stock recovery with Safestrap installed! Will brick the HDX!
As @Davey126 mentioned here you can check whether the bootloader ist unlocked by opening a fastboot prompt (i.e. DOS box, then change dir to your adb directory), then enter:
fastboot -i 0x1949 oem idme
You will only get a response if unlocked.
If you use Windows and get the waiting for device fastboot issue, try these drivers, could be a pain in the ass to install them in Win8(.1)/Win10 x64 though. And note that you probably need to (re-)install the original Amazon Drivers again to get the HDX noticed in Explorer in order to get files copied it.
Click to expand...
Click to collapse
Also verify you have a Kindle HDX ... not HD or generic Fire.
the fastboot command got me still only 1 message "waiting for device"
Tried to install drivers. While looping, in device manager, i can see "Fire devices: Android composite ADB Interface"
and "Portable devices: MTP USB Device"
If i enter fastboot mode, gets me to "Other devices: Unknown device" and i just cant figure out how to install the drivers. Tried to download some stuff. plugged, unplugged.
Edit:
After some work done with drivers, i input adb kill-server and adb devices and get "Serial Number Unauthorized"
So maybe i should change word "work" to "messing" with driver
what do i do from here... is there any live chat for it maybe? or i can call someone?
Well, do you have the real TWRP or Safestrap? Can you enter recovery?
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Still haven't answered Safestrap or native TWRP query (you should know). Do this:
- long press power until device shuts off
- restart device with power button (only)
- detail the 1st, 2nd and 3rd screens you see
If you do not have native TWRP (with unlocked bootloader) you likely borked your device with the installation of CM 12.1. Generally not repairable.
oreal crast said:
well, only thing i get it's blue screen and "Teamwin" and after like 3-4 second restarts and go on looping same "Teamwin"
Click to expand...
Click to collapse
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Cl4ncy said:
Ok, that should be the real TWRP, the Safestrap screen looks different.
This could mean you've TWRP installed, but the bootloader is locked. So I'd suggest to unlock the bootloader, you can't screw up anything, and can try this nice tool.
Click to expand...
Click to collapse
To check if your bootloader is unlocked (assumes you previously unlocked and still have the prerequisite software installed on host):
- power down device
- press vol-down + power; release both keys when "[fastboot]" prompt appears
- tether your device
- open a command prompt (assuming Windows)
- issue command: fastboot -i 0x1949 oem idme ?
- you will only get a response if bootloader is unlocked
If the (Windows) host displays "<waiting for device>":
- press <ctrl>-c to break wait
- start device manager (different window)
- located device with explanation mark (likely under "portable devices")
- right click -> update driver software -> browse my computer... -> Let me pick...
- select driver from list (ideally one that contains the words 'fastboot'); might have to try a few
- reissue above command
Bit of a PiTA ... might be easier to simply try the one click unlock tool as there is no additional risk to your device. It will either work or not.
I guess i'll check it only next week. Leaving all this things for the weekend.
I'll keep you updated guys.
Anyway, i really appreciate your help! Thank you so much for helping
same problem
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
stephio said:
Good evening, I am very interested by the article, in fact, I currently have the same problem and I began to be very sad. all stages cited by oreal Crast are similar to the ones I tested. when I enter the command prompt 'adb devices' I get the number of my tablet and status RECOVERY.
'adb shell' gives me "~ # ← [6n"
I even re installs the uboot, boot.img and TWRP freedom by following the steps in one tech site
but at reboot, by entering the command "fastboot oem recovery 0x1949 -i 'my tablet again has a boot loop on teamwin.
i want to resolve very fast this problem because i need my tablet urgently:crying:
ps: I don't think that I can meet these problems because after having bought my tablet to a friend (the tablet possessed CyanogenMod 11 android 5.0.1 I think) I did a factory reset . it is from this manipulation on my tablet reboot teamwin.
thank you for your helping
Click to expand...
Click to collapse
I assume you have an unlocked bootloader and were running 'native' twrp (not Safestrap) when the problem occured. Unfortunately, there is no known 'quick fix' recovery from this failure scenario (boot looping on teamwin spash screen) as you have tried to reinstall twrp without success. Someone very talented with android might be able to unravel the problem. Best guess (and it is only a guess) is the recovery partition became damaged to such an extent it the contents can not be replaced without performing a low level format/reset of your device.
Some curiosities:
- Android 5.0.1 and CM11? (impossible combination)
- TWRP freedom? (not supported on HDX)
Are your certain your device is a HDX and not some other model?
same problem
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
stephio said:
for android version I listed above, I do not know exactly because I have used my tablet a day without really paying attention to it but I think I saw the android 5.0.1 but regarding cyanogen, I just imagined it based on readings on the web.
for this is my tablet AMAZON KINDLE FIRE with a HD 8.9 and the TWRP I recently flashed, I got through the website wikicyanogenmod in the "on how to install cyanogen hd amazon kindle 8.9.
I can not post a link because I am new to the forum so I can only quote the sites where I could download my data.
* I really count on your help to all.
Click to expand...
Click to collapse
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
same problem
EncryptedCurse said:
You still haven't made it clear whether you have an HD or HDX model.
You're on the HDX forum, but you're talking about documentation on the CyanogenMod wiki for the HD 8.9.
The problem likely stems from the fact that you flashed a recovery for the wrong device.
Click to expand...
Click to collapse
I searched the web and I have definitely amazon kindle fire HD 8.9 because even his appearance differs from the HDX 8.9.
no I do not really think the problem comes from the data flash HD 8.9 (wikicyanogenmod) because I flashed the data after doing a factory reset without actually knowing that this would pose a problem with amazon tablets.
the tablet was working well but I was unable to connect to the wifi. I thought it would be nice to change rom and install a suitable and stable rom for my tablet, but my operation I was surprised because I had never heard of this kind of problems caused by an factory reset