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
Related
I have bricked or atleast semi bricked my Folio and i dont know if it can be fixed. It began with damaged internal sd, so i try the format zip but no luck. May device have been like this 3 days now. I NEED HELP, AND YES I HAVE ASKED IN GENERAL SECTION. but i didnt get an answer for days. I need help by someone who can tell me how to set up fastboot. My folio boots i can get to clockwork recovery and i can get in to fastboot mode. I have working ADB on my computer. The install fails when recovery is writing boot.img iget this message: assert failed
write_raw_image("/cache/boot.img", "linux")
E:Error in /sdcard/FolioMod.zip
(Status 7)
It installs system.img fine. So i was thinking i could fastboot boot.img to the device and maybe it boots. So i put Folio in Fastboot mode,insert usb, and update driver, go to command prompt and write fastboot devices all i get is:
? fastboot
Is there anything special i have to keep in mind to setup fastboot for Folio. I used the fastboot that came with SDK. Do i have to add something more to .inf file for fastboot? Do have to use any special fastboot just for Tegra2 devices? Is my fastboot mode damaged? Please i need help i have waited for days in general section not one answer. Hoping on better luck here in the dev section
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
mblaster said:
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
Click to expand...
Click to collapse
I had entered the part to .inf file but havent done the echo part in command prompt, will try now. Its weird as hell all i get when writing fastboot devices is a ? fastboot. Its a windows Vista 32 im using and SDK 08. And when i enter this echo 0x955 i just get that its the wrong path.
I got fastboot working didnt know it could be ? fastboot when it was connected. I kept getting it so i tryed to send some commands and it got thru. **** so i have had it working for days. I have flashed the boot.img via fastboot and am now trying to do an advanced restore of a nandroid. Will see how it goes. If its not working can i flash system.img and boot.img? Will that work? Well atleast now i can flash standard recovery and send it to toshiba
Probleem Solved Thank you mblaster, you wrote it could look like this when writing fastboot devices: ?????? or atleast something like it so i thought maybe i am connected as my said: ? fastboot . So i tryed some commands and they got thru. So to anyone who tryes to install fastboot try commands. I was waiting for days(dumb, i know). So now im back and kickin, watch out
Moved to proper forum
I'm trying to root my Evo 3D with hboot 1.5 and have been following the instructions in the development thread. However, I get stuck at the command "fastboot getvar mainver" in step 1. At this step, windows detects a new device 'Android 1.0' and unsuccessfully tries to install drivers for it. As a result, the only thing I see in my command window is "< waiting for device >."
I don't want to permanently brick my phone so I'd like to ensure that I have properly changed the version to 1.10.651.2 before proceeding.
Does anyone have any ideas on how to resolve this or provide me with a link to the proper drivers?
Thanks!
EDIT: Problem solved. I installed some HTC drivers I found!
When I got my m7 I tried to s-off but nothing worked. I eventually figured out that ADB won't work. I am rooted, running IC 3.06 (KK 4.42, Sense 6) and would love to upgrade to insertcoin 6.05 but I'm afraid to do it without ADB to fall back on. Anyone know how to fix this?
I have tried to run many s-off programs from three different PCs running Windows 7 and updated Linux Mint DE, Ubuntu 14.04 with original cable and other good quality ones. I can communicate with the phone with fastboot and can copy and paste to the phone perfectly in every OS. But when I try to ADB reboot or any other command, I get "device not found" .
pete2bec2 said:
When I got my m7 I tried to s-off but nothing worked. I eventually figured out that ADB won't work. I am rooted, running IC 3.06 (KK 4.42, Sense 6) and would love to upgrade to insertcoin 6.05 but I'm afraid to do it without ADB to fall back on. Anyone know how to fix this?
I have tried to run many s-off programs from three different PCs running Windows 7 and updated Linux Mint DE, Ubuntu 14.04 with original cable and other good quality ones. I can communicate with the phone with fastboot and can copy and paste to the phone perfectly in every OS. But when I try to ADB reboot or any other command, I get "device not found" .
Click to expand...
Click to collapse
ADB only works in Android OS with USB debugging enabled or in a custom recovery. If the phone is showing FASTBOOT USB then ADB will not work!
I was in Android with USB debugging enabled, on a PC with drivers. I could copy and paste files between phone and PC. But if I typed ADB devices in a terminal window, I got devices not found. I didn't get unknown command, so it saw the correct path. No matter what command I typed, I got device not found.
pete2bec2 said:
I was in Android with USB debugging enabled, on a PC with drivers. I could copy and paste files between phone and PC. But if I typed ADB devices in a terminal window, I got devices not found. I didn't get unknown command, so it saw the correct path. No matter what command I typed, I got device not found.
Click to expand...
Click to collapse
Have you updated your ADB/Fastboot files or update the drivers?
Edit 2: [SOLVED] Just needed to run it as sudo (duh). Discovered solution @ Stack Overflow article titled: "Android fastboot waiting for device".
Probably an easy fix. Haven't flashed a ROM in a while and forgot some stuff.
Problem: Accidentally deleted Google Now launcher. OS wouldn't load properly.
Action: Was able to get into settings, so I DL'ed the latest nightly build for CM13. Got it on the device successfully. Wiped the delvik, cache, system and all that, but when I tried to flash the build, I get an error:
Checking for MD5 file...
Skipping MD5 check: No MD5 file found
Sprint CDMA variant detected!
Reboot into Bootloader Mode, connect your device to PC and from PC terminal type:
fastboot oem config fsg-id boost
and then flash the CM mod again
Click to expand...
Click to collapse
Next Action: I recently re-installed Linux Mint, so I had to re-install the ADB and Fastboot. I did so per the instructions on LifeHacker for Linux (can't link to it BC I'm a new user still on XDA).
Current Issue: I can't figure out how to open a terminal for my device. If I installed ADB and Fastboot correctly I should just be able to right-click and select 'Open Terminal here' like I did before, but for some reason (probably some terminal command I'm forgetting) my PC isn't allowing me terminal access to the device still/yet.
Other Information:
My PC does recognize my device as a USB storage device.
My old ROM did have ADB Debugging.
I still have access to Fastboot and TWRP (not bricked, thankfully).
CM13 ROM file is still in the device. So, I'm very close, but still a step away from fixing this.
I think I'm missing something simple, but I haven't done this in a while.
Thank you for your help in advance! :good::good::good:
Edit
Forgot to mention: When I connect the device and put it into Fastboot and then type in the command "fastboot oem config fsg-id boost" in my terminal, I get: <Waiting for device>. So, something is missing.
EDIT: nvm, didn't see your edit. I use linux and didn't have to install anything besides Minimal ADB & Fastboot.
Solved. :victory::good:
Just needed to run command ("fastboot oem config fsg-id boost") as sudo. Duh. :silly:
Found solution @ Stack Overflow articled titled "Android fastboot waiting for device".
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!