Related
I been trying for days to get my HTC Flyer with Honeycomb rooted via the GUIDE but I am stuck at step 1.
"If you are not on an appropriate gingerbread version, eg. if you have upgraded to honeycomb then downgrade by using an appropriate RUU; to identify your RUU see: here"
(downgrade to Gingerbread) but I get stuck at the "Fastboot getvar cid" stage to find out which RUU I have. When I have the Flyer in Fastboot mode and connect the cable, I get an error when it trys to install the "Android 1.0" driver.
I have uninstalled, rebooted, reinstalled, repeatedly. I just tried another link that suggested to try installing PDANet for Android to get around this problem. Now when I run Fastboot, rather than just "waiting for connection", I get an error that says "getvar:cid FAILED (status malformed (1 bytes)) finished.
*** Update***
I just tried a different HP Laptop with Windows 7 installed & I had the exact same error regarding the Android 1.0 driver as soon as I plugged in the Flyer when it was in Fastboot mode. Is there some other setting other than Fastboot off I need to do on the Flyer itself? Any other suggestions would be GREATLY appreciated.
Please help!! I am at my wits end here.
thanks,
sPk
still need help
I am still struggling here.
By pointing the Android 1.0 driver installer to the PDANet directory, it found a ADB driver and installed it. But I still get the "malformed error" when I try to use "Fastboot getvar cid" command to find RUU version. Is there another way to get the RUU version??
I think the driver is communicating with the Flyer as I was able to get Flyer to respond to the serialno command.
I have OTA update and want to root/Rom with HBoot 1.11.00011.
If I can't get the RUU version, is there a most likely suspected RUU for a WiFi only Flyer that I just got from Buy.com for US market.
thanks in advance for your help.
sPk
You have the android sdk installed right?
Andriod SDK
Gumby63 said:
You have the android sdk installed right?
Click to expand...
Click to collapse
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
windsurfsail said:
What will the Android SDK provide? I downloaded "Andriod SDK r16" for windows but it doesn't run. I unzipped it, tried running the "SDK Manager.exe" but it fails indicating that it failed to find android.bat. I also tried the SDK installer but it said that it required JDK (Java SE Development kit). Which was a huge install & I still didn't get the SDK to execute.
Is the ADB USB driver the correct driver when in Fastboot mode?
thanks,
sPk
Click to expand...
Click to collapse
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
SDK
Gumby63 said:
Ok so what you need to do is open up cmd prompt and type 'cd (your tools folder of the sdk)
You can do that by dragging and dropping the tools folder into the cmd window.
Now that you have done that, try doing the fastboot command again and see if it works.
Click to expand...
Click to collapse
I was able to get the Android SDK & Java installed properly. I uninstalled the driver in the Device Manager and then pointed the driver install to Android SDK/Tools and it indicated that the driver was already installed. I tried Fastboot command for the zilllionth time and still got the same malformed error. So I uninstalled driver & deleted it this time and tried to re-install but now it doesn't find the driver files (because I deleted them). I can re-install SDK or just point it to the PDANet directory again.
Is the correct driver for Fastboot the the Android ADB? It is the only one I have been able to get to load when I plug in the Flyer in Fastboot mode.
thanks,
sPk
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
hboot & fastboot confusion
globatron said:
Yeah, you're getting the error because you're doing it completely wrong.
Install the drivers that you're told to install in the thread not any other drivers, then put your device in fastboot mode, not hboot mode(which is the mode you have it in) when trying to run fastboot commands.
Click to expand...
Click to collapse
DOH!
Globatron, thanks for the clarification. In all my reading of threads, I never saw any definition of hboot & fastboot. Since it wasn't working, I installed the other drivers in an effort to fix what was apparently a driver issue.
Is "fastboot mode" just having the "Fast boot" box checked under the Power settings?
thanks again!
sPk
Fastboot mode
After searching in the forums for a while, I found a description on how to get into "fastboot mode". I have added below in case someone else is new enough not to know.
I ran the command & it finally worked. Being in the right mode was key.
sooo, I now have the cidnum= BS_US001 but looking through the list of the RUU's files, I still don't see any reference to this CID. Another stupid question: How do I find which of the list of 25 RUU files is correct for my WiFi Flyer?
UPDATE: Found out how to find RUU file from link.
http://forum.xda-developers.com/showpost.php?p=18508220&postcount=2
modelid: PG4140000 (Wifi Flyer)
RUU_Flyer_BrightstarUS_WWE_X.XX.1540.XX
cidnum: BS_US001
cidnum: HTC__055
sPk
----------------------------------------------------------
You need to be in fastboot mode. Two ways to get there.
Get into boot then select fastboot
Or
While booted in android connect to PC then enter "adb reboot bootloader" (assuming you know adb a little)
Once in fastboot you need to enter the commands in a cmd terminal on your PC just like adb
What I learned, that may help you...
I had a surprisingly difficult time getting my OTA Honeycomb US WiFi Flyer S-Off'ed, Rooted & uploading a new ROM. I did get it done but there were some basic things I should have known or done. Thanks to Globatron & all who post on this board.
1: Before you start, make sure your PC's drivers are 100% working. I had Windows driver problems that caused other problems. Make sure that your tablet is properly recognized by the PC when the tablet is in Fastboot/Hboot modes, and in regular Android mode.
2: I didn't understand the difference between Hboot & Fastboot. This small thing made all the difference and was one of my major issues. Because I had the tablet in Hboot not Fastboot, the Fastboot commands didn't work and I couldn't get my RUU version
3: Pay attention to the phone's settings. Especially USB Debug mode, Fastboot mode.
4: After I had finally downgraded to Gingerbread. I couldn't figure out why Revolutionary wouldn't recognize my tablet. The simple answer was when I had downgraded to Gingerbread, all my phone settings were back to stock also so I had go in and change the USB Debug and Fastboot modes. It would be helpful to add a reminder in the GUIDE to make sure that these settings are changed before running Revolutionary.
5: Not really related but I had a problem when I wanted to backup my newly Rooted/ROM'ed phone. I had previously purchased the Titanium Backup Pro and I installed it on the Flyer but it wasn't listed in the Apps menu but was listed in the Manage Apps. Because Google-Play/Android Marketplace only copied over the paid apps to my newly upgraded Flyer, it didn't copy the free version of Titanium Backup. You must load both the free version & the paid Pro version for it to work.
I hope this helps someone who runs into any of the same issues I had.
thanks,
sPk
I neglected to flash vendor.img when installing the M preview and did "fastboot reboot" after flashing everything else manually. Now whenever my N9 boots, it only shows the Google logo. I've tried going into Recovery and wiping/factory reset with no success.
Is there any way I can a) flash the remaining vendor.img; or b) return my N9 back to 5.1.1?
shaiwon said:
I neglected to flash vendor.img when installing the M preview and did "fastboot reboot" after flashing everything else manually. Now whenever my N9 boots, it only shows the Google logo. I've tried going into Recovery and wiping/factory reset with no success.
Is there any way I can a) flash the remaining vendor.img; or b) return my N9 back to 5.1.1?
Click to expand...
Click to collapse
Boot back into your bootloader, and "fastboot flash vendor vendor.img"
That's what I'm trying to do but I don't know how to connect the tablet with my Mac to run the command in fastboot. When I type "adb devices", it no longer lists my device as attached. Would appreciate instructions in how to connect again through USB to flash the vendor image.
shaiwon said:
That's what I'm trying to do but I don't know how to connect the tablet with my Mac to run the command in fastboot. When I type "adb devices", it no longer lists my device as attached. Would appreciate instructions in how to connect again through USB to flash the vendor image.
Click to expand...
Click to collapse
There's not enough information here to help you.
So if I understand well, you previously were able use ADB and fastboot on this computer?
Does your computer recognize your N9? Can you see the N9's SDcard from your Mac?
If yes, then is "USB debugging" enabled in Developer Options?
When you try ADB devices, did you click the "always allow/trust connection with this computer" popup on your N9's screen?
cam30era said:
There's not enough information here to help you.
So if I understand well, you previously were able use ADB and fastboot on this computer?
Does your computer recognize your N9? Can you see the N9's SDcard from your Mac?
If yes, then is "USB debugging" enabled in Developer Options?
When you try ADB devices, did you click the "always allow/trust connection with this computer" popup on your N9's screen?
Click to expand...
Click to collapse
Before flashing the preview image using fastboot, I had USB debugging enabled. When rebooting after flashing all the files (except vendor.img), the tablet would power on and show only the "Google" logo and go no further. So I tried booting into fastboot and recovery, but when I plug in the tablet to my Mac and try "adb devices", it doesn't recognize it being connected.
Since I cannot turn the N9 on fully to go into Developer Options and enable USB debugging again, how do I connect it to my Mac again so I can flash the remaining file and complete the setup?
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
sogrady said:
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
Click to expand...
Click to collapse
Hi, sogrady...
You don't need ADB to flash anything... All you need is FASTBOOT and a working connection to your PC/Mac.
----
ADB debugging is irrelevant when it comes to running fastboot flash commands. ADB is only meaningful when running a fully booted version of Android OR when running a Recovery... Stock or Custom.
Providing your Nexus 9 bootloader is unlocked, you should be able to run fastboot flash commands without problem.
To confirm you have a working fastboot connection, and with the device booted into it's bootloader, type...
Code:
fastboot devices
This should return your N9s unique device id... If it doesn't, you likely have a driver/connectivity issue... but it has nothing to do with ADB debugging - On or Off.
Rgrds,
Ged.
sogrady said:
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
Click to expand...
Click to collapse
I thought so too, but I found a solution.
Check out my post here: http://forum.xda-developers.com/nexus-9/help/help-boot-loop-os-n-t3122167#post61051773
Hopefully, it helps.
Unfortunately, fastboot can't see the device either:
Code:
ferro$ fastboot devices
ferro$
This is with the Nexus 9 connected and in fastboot mode. As for it being a driver issue, everything that I've seen suggests that specific to Windows, and I'm on Mac. Is that accurate, or are there drivers I need to install on a Mac?
GedBlake said:
Hi, sogrady...
To confirm you have a working fastboot connection, and with the device booted into it's bootloader, type...
Code:
fastboot devices
This should return your N9s unique device id... If it doesn't, you likely have a driver/connectivity issue... but it has nothing to do with ADB debugging - On or Off.
Rgrds,
Ged.
Click to expand...
Click to collapse
sogrady said:
Unfortunately, fastboot can't see the device either:
Code:
ferro$ fastboot devices
ferro$
This is with the Nexus 9 connected and in fastboot mode. As for it being a driver issue, everything that I've seen suggests that specific to Windows, and I'm on Mac. Is that accurate, or are there drivers I need to install on a Mac?
Click to expand...
Click to collapse
No drivers on a Mac. And the command should be "./fastboot devices". You need the "period" and "backslash" before the command.
cam30era said:
No drivers on a Mac.
Click to expand...
Click to collapse
So assuming fastboot doesn't see the device, then, I'm out of options and looking at an RMA?
cam30era said:
And the command should be "./fastboot devices". You need the "period" and "backslash" before the command.
Click to expand...
Click to collapse
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them with the ./ prefix is unnecessary. Certainly worked just fine the first time around without them.
sogrady said:
So assuming fastboot doesn't see the device, then, I'm out of options and looking at an RMA?
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them without the ./ preference is unnecessary. Certainly worked just fine the first time around without them.
Click to expand...
Click to collapse
Hi, again sogrady....
Don't give up so easily...
When you say "I'm out of options", what options have you tried exactly?
Another computer? Another USB cable? A different USB port on a computer?? There could be several variables causing problems for you.
One other point, are you certain your Nexus 9 is fully booted into fastboot mode, and not just the HBOOT bootloader...
You should see something like my attached screenshot...
If you see this, then all things being equal, fastboot commands should work without problems.
Hope this helps...
Rgrds,
Ged.
sogrady said:
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them with the ./ prefix is unnecessary. Certainly worked just fine the first time around without them.
Click to expand...
Click to collapse
Update the binaries, they may be outdated.
You can use my script for this: http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
Happy to report success - well, partial success anyway. Per @GedBlake, I swapped in a new machine and cable, and per @simmac I made sure my binaries were updated. As it turns out, this was unnecessary: my mistake, after looking at @GedBlake's screenshot was that I was not down in fastboot, I was in hboot. As soon as dropped down into fastboot, voila:
Code:
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot devices
HT4CRJT01274 fastboot
So, problem solved I figured. I re-downloaded the M image to my new machine, checked the MD5 and attempted to flash all. As with the previous iteration, it failed due to a new (to me) set of errors:
Code:
error: cannot load 'system.img'
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
sending 'vendor' (147127 KB)...
ERROR: usb_write failed with status e000404f
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
ERROR: could not get pipe properties
ERROR: could not get pipe properties
rebooting...
ERROR: usb_write failed with status e0004061
finished. total time: 0.000s
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
ERROR: usb_write failed with status e00002ed
At which point I figured that I would simply load the *.img's manually, one by one. But fastboot had by this point become squirrelly about even seeing the machine.
Code:
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot devices
ERROR: could not get pipe properties
ERROR: could not get pipe properties
???????????? fastboot
At which point I decided to simply see if I could go back and load 5.1.1 and deal with M later. While that flash-all.sh script failed as well, I was able to put 5.1.1 back on via the following manually:
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
unzip image-volantis-lmy47x.zip
cd image-volantis-lmy47x
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot reboot
At which point the device booted back up into 5.1.1. So big thanks folks for helping me restore an otherwise bricked machine! Much appreciated. Hope the steps help anyone else caught in a bricking cycle.
And if anyone has any idea why my M load failed, I'd be all ears because I would like to load that up at some point. For now, though, I'm just happy to have a working machine again.
Update: Ok, strike the above. Re-ran that process for the Android M build and it went off without a hitch this time, although the setup wizard failed so the build itself looks to be buggy. That at least is not related to the flashing process, however, so proceed to flash M onto the device if you're willing to try and get past those issues.
Symptoms
This is for a Nvidia Dreamtab NV08B. Due to a system change you made, or an official Nabi OTA update the tablet now no longer boots.This could be the tablet hanging/frozen/stuck from any point from when turning the tablet on up to the Dreamworks characters screen and never boots any further. You have attempted at least 2 factory reset through the stock recovery and it still does not boot.
NOTE: If your Dreamtab was recently working and you made no system changes, or system updates but is now hanging at the Dreamworks characters try this first: https://forum.xda-developers.com/nabi-2/general/guide-dreamtab-hangs-characters-t3528698
Solution
Restore the tablet to software version 1.3.12 stock condition: Unlock the bootloader to allow tablet modification. This will wipe ALL the data from the tablet. Format all ext4 partitions and check filesystem integrity. Reinstall recovery, boot, system and addon partitions. Optionally install the fsck binary that is missing on the tablet. Reinstall bootloader
Procedure
Only for Nvidia Dreamtab NV08B. Use this at your own risk, your warranty is void. You will lose all personal data on the device
To get an understand of how the device works with fastboot, ADB, and recovery read through this :http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
You will need to install ADB and fastboot drivers yourself. I have included a copy of Nabilab drivers for 32bit and 64bit computers in the download in the driver folder. Refer to the link above to understand driver installation and booting the tablet to fastboot. This is a script driven restore of the tablet, most of these task are automated.
General flow:
-- Download the Dreamtab_NV08B_restore.zip
-- Extract the zip file to a location of your choosing on your computer.
-- Connect the Dreamtab powered off to your computer via USB cable.
-- If you want to install the driver provided in the zip do it now.
-- Open the file recover_dreamtab file
-- A command prompt opens and the script runs as below. The script has the instructions in it, the below is just a summary.
(automated = script will do it for you. User = you need to take action)
(automated) Extract the files you will need for recovery.
(user) Boot the tablet to fastboot pressing vol+ and power button. Use vol- to select fastboot protocol.
(automated) Check fastboot operational
(user) If script hangs here, user will need to check drivers)
(automated) Initiate bootloader unlocl
(user) Use vol- button to select yes, and vol+ to acknowledge
(automated) Wipes userdata and cache and unlocks bootloader
(automated) Formats data partition
(automated) Boot TWRP 3.0.0 recovery temporarily
(automated) Check data partition integrity
(automated) Format and check cache partition
(automated) Check CPU serial number for TWRP backup
(automated) Push the restore files, bootloader, and fsck patch to Nabi internal storage
(automated) Restore recovery, boot, system, and addon partition files.
(user) Prompt user to install fsck binary that the stock Nabi is missing. I recommend this. but there is a no option.
(automated) Install fsck patch if selected by user
(automated) Install 1.3.7 bootloader
(automated) Remove restore files from tablet
(automated) Reboot
Note: The boot loader is left unlocked. Sometimes you will get a google play service error during first boot.
Download
AHF Download Link: Dreamtab_NV08B_restore
___________________________________________
I'm having an issue when the script switches from fastboot to recovery. First, the TWRP 3.0 recovery.img isn't anywhere in the restore zip. So I put that in the install folder (I already had it installed on the DT but nothing was working so I tried this anyways). The ADB driver verifies and the script echos "ADB is functional. On tablet Swipe to Allow Modification." The script boots the device into TWRP just fine and I swipe past the Allow Modification screen. I press any key on the script to continue but every single task is followed by "error: device not found." I've triple checked that both the DT shows up as an ADB Interface in the Device Manager and I can use "adb devices" to see it, yet the script still returns the error. Any thoughts?
Also, how feasible would it be to simply do this by hand? I'm pretty well versed in fastboot/adb but dealing with partitions is something that I tend to shy away from for fear of bricking a device. Since I can get adb to see the device could I simply copy the commands from the script?
Alternatively, could I simply add the .win and .md5 files into the RESTORE folder myself via drag and drop and do a wipe and restore straight from TWRP?
CriticalComposer said:
I'm having an issue when the script switches from fastboot to recovery. First, the TWRP 3.0 recovery.img isn't anywhere in the restore zip. So I put that in the install folder (I already had it installed on the DT but nothing was working so I tried this anyways). The ADB driver verifies and the script echos "ADB is functional. On tablet Swipe to Allow Modification." The script boots the device into TWRP just fine and I swipe past the Allow Modification screen. I press any key on the script to continue but every single task is followed by "error: device not found." I've triple checked that both the DT shows up as an ADB Interface in the Device Manager and I can use "adb devices" to see it, yet the script still returns the error. Any thoughts?
Also, how feasible would it be to simply do this by hand? I'm pretty well versed in fastboot/adb but dealing with partitions is something that I tend to shy away from for fear of bricking a device. Since I can get adb to see the device could I simply copy the commands from the script?
Alternatively, could I simply add the .win and .md5 files into the RESTORE folder myself via drag and drop and do a wipe and restore straight from TWRP?
Click to expand...
Click to collapse
Sorry about that, I re-uploaded.
Yes you could copy the files over, or do the script by hand. Drop and drag is by far the easiest especially if you use external SD card. Part of me wants to know why the script isn't working for you though.
I just found something and I don't know if this is the issue. When TWRP is idle the device is showing up as "Google Nexus ADB Interface" and "adb devices" cannot see it. However, if I go to TWRP to initiate ADB Sideload then it shows up as "Android ADB Interface" and "adb devices" sees it no problem. I've tried changing the Google Nexus driver to the Android one but I can't seem to find it. Both the .inf from NabiLabs and the Universal Naked Drivers show up as Google Nexus ADB Interfaces.
Also, I grabbed your re-uped version and ran into a problem that I forgot I had to fix last time as well. ADB always hangs after starting the daemon. I had to use my personal adb (v32) to get it to stop hanging (your package uses adb v36). Alternatively, I found that when it hangs, I can start the v32 daemon and then go back to your script which will restart the v36 daemon and it seems to run fine...though it still doesn't see my tablet.
CriticalComposer said:
I just found something and I don't know if this is the issue. When TWRP is idle the device is showing up as "Google Nexus ADB Interface" and "adb devices" cannot see it. However, if I go to TWRP to initiate ADB Sideload then it shows up as "Android ADB Interface" and "adb devices" sees it no problem. I've tried changing the Google Nexus driver to the Android one but I can't seem to find it. Both the .inf from NabiLabs and the Universal Naked Drivers show up as Google Nexus ADB Interfaces.
Also, I grabbed your re-uped version and ran into a problem that I forgot I had to fix last time as well. ADB always hangs after starting the daemon. I had to use my personal adb (v32) to get it to stop hanging (your package uses adb v36). Alternatively, I found that when it hangs, I can start the v32 daemon and then go back to your script which will restart the v36 daemon and it seems to run fine...though it still doesn't see my tablet.
Click to expand...
Click to collapse
Go to the mount page in TWRP and disable MTP. When MTP is enabled it's really an ADB "composite device", when it's disabled it's a "single" interface.
To fix the ADB issue try adding
tools/adb kill-server
to the beginning of script.
Disabling the MTP worked like a charm. I would highly recommend adding that to the script as an echo so that others don't run into the same confusion. My tablet is up and working again. Thanks a ton for putting this script together. I would rather have had Nabi release factory images but this works just as well!
Thank you very much for the procedure.
is there any solution for Intel Version? (IN08A)
Thank You Thank You Thank You. This worked when everything else failed. Couple notes: Yes I had to Disable the MTP. No biggie. Then when I got to the Yes/No prompt to install fsck binary, I typed yes hit enter and the command prompt closed! I started over and and tried typing "No", same results. I actually tried the entire process a couple more times before I just used the TWRP to Reboot... all went well... I did see the Google Error but hit Ok and everything continued till it got to the setup page.. All in All an excellent script Thanks for your time and effort to do this.
Old thread, I know-
Thanks for this, but my nabi dreamtab 08B1 bootloader unlock doesn't work.
I installed your drivers, and the fastboot oem unlock reports:
Code:
C:\Users\me\Downloads\DTTWRPinstaller300>cd files
C:\Users\me\Downloads\DTTWRPinstaller300\files>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 4.916s
C:\Users\me\Downloads\DTTWRPinstaller300\files>
any ideas? I've tried this several times- this is after a factory reset, and the tablet bootloops from teh characters screen.
thanks again!
phil_socal said:
Old thread, I know-
Thanks for this, but my nabi dreamtab 08B1 bootloader unlock doesn't work.
I installed your drivers, and the fastboot oem unlock reports:
Code:
C:\Users\me\Downloads\DTTWRPinstaller300>cd files
C:\Users\me\Downloads\DTTWRPinstaller300\files>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 4.916s
C:\Users\me\Downloads\DTTWRPinstaller300\files>
any ideas? I've tried this several times- this is after a factory reset, and the tablet bootloops from teh characters screen.
thanks again!
Click to expand...
Click to collapse
Nothing comes to mind. The only time I have seen that failed message was on a tablet where the flash had gone bad, but the tablet wouldn't erase data and cache like it looks like yours did. Anything else plugged in, cables good? You could try the -i switch although I don't recall seeing a Dreamtab that needed it, I am mobile and cant remember. It's like fastboot -i 0x0489 oem unlock or something.
Downloaded and installed ADB. Following tutorial here:
https://www.xda-developers.com/nexus-6p-bootloop-fix/
Specifically:
- Connect your smartphone or tablet to your computer with a USB cable. Change the USB mode to “file transfer (MTP)” mode. Some OEMs may or may not require this, but it’s best to just leave it in this mode for general compatibility.
- In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices
- On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).install adb
- Finally, re-enter the command from step #6. If everything was successful, you should now see your device’s serial number in the command prompt. Yay! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
https://www.xda-developers.com/install-adb-windows-macos-linux/
I did all the above. But don't see anything from:
C:\ADB>fastboot devices
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
Nexus 6P was plugged into the USB cable on Win10 machine. Am in MTP mode. Most recent Google USB drivers installed.
I have done OEM Unlock in setup|Developer options. I have also turned on USB debugging in same options.
I am [obviously] lost. Anyone know what else I might try?
OK, I have made a little progress messing around on my own. It seems that running from the CMD line in Win 10, ADB command works but Fastboot does not. WHY? Bith are in the same directory.
If I type Fastboot by itself, then I get a list of the associated parameters, which means that the CMD system DOES recognize the Fastboot command.
Now, if I run CMD====> "ADB devices", it looks like my device is recognized and attached (that is my serial# below).
But if I try CMD=====> "Fastboot devices", as the instructions require, I get nothing. And if I try to run the flash job via Fastboot, that does not work either.
==================
C:\ADB>adb devices
List of devices attached
8XV5Txxxxxxxxxxx device
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
===================
Wondering if I need to install the Android SDK on Windows for this process to work?
I Think You need to Redo The process from Step One.
I Heard about This and Never Did An OTA.
If it Persists Try Using A Different PC and If After That It doesn't work Then Yes Android SDK is The last Option.
Sent from my Nexus 6P using Tapatalk
Solved. I needed to add the ADB install directory to the environmental path. Don't quite understand why, but doing so allowed me to get the problem fixed.
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!