Okay I am on the EVO 3D running Viper Rom 1.0.0, (which has been giving me problems from the start and I am trying to remove it and revert to stock) running the 1.58 HBOOT, HTC dev unlocked, and S-On
Also i have windows 7 x64
The problem I am having is that ViperRom is not working at all. It's booting and running ok, but it gives me numerous problems, like apps not being able to run, apps not found in google play, and it randomly shuts down if I am doing something, like browsing the web or listening to music.
I have tried numerous times to flash different roms, revert to a stick rooted rom etc. But Viper doens't seem to want me to let it go. The only Rom that works for my Phone is Viper ROm ICS Sense 4.1, 1.0.0
Now my last resort is to revert to stock and unroot, then start all over. But now, adb does not want to recognize my device. I am using ADB from a different computer that I rooted my EVO on in the first place. But it should work. I try and type adb reboot bootloader and it gives me device not found. I manually reboot to my bootloader, I get fastboot usb, and then i type the command: fastboot oem lock to relock the device.
Still gives me waiting for device. I have htc sync, the usb drivers, java JDK, and android adk. But for some reason, the computer does not want to recognize my phone. Any suggestions?
If you really want to revert back to stock then your going to have to relock the bootloader then install the stock ruu. You can then reunlock the bootloader with teh same bin file they emailed you.
the relock you need to press and hold the vol dwn buttn and the power button. then go to fastboot (on phone) Then in the cmd line type
Code:
fastboot oem lock
Do you have all 3 files? adb.exe, AdbWinApi.dll, fastboot.exe
Also, I'm not sure if it matters but are you using a USB 3.0 port instead of 2.0? Perhaps run command prompt as administrator? Just throwing out things to try. Hope they work or spark better ideas.
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've had this phone for about a good 4 months now, was getting bored so i decide to unlock the bootloader, root, and install a new rom. Then i heard youwer able to activate the HTC logo button to wake and sleep your device with using a different kernel. tbaldens kernel v3.6. I have TWRP recovery installed with trickdroid as my rom.After i ran threw all the procedures to flash in Aroma installer. My phone won't turn on, when i connect it to my computer it shows up as a MTP device. When I do get it to power on its stuck at the "quietly brilliant" screen. cant get into recovery to restore from back up. PLEASE HELP! SOLDIER DEPLOYED!!!!!!!! dont have the means of sending it in. Any suggestion. Mac is my primary means of rooting. windows 8 drivers are kinda funky:crying::crying::crying::crying::crying::crying::crying:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
crashfocus said:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
Click to expand...
Click to collapse
can i do this from a mac? and i can't get into fastboot because it wont go past the htc logo screen. it is identified as a MTP device in windows
Ahhhh thankfully i was able to get into my bootloader and flash my recovery! but thanks for the reply bro
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
trp6senile said:
Okay, so basically I am a HUGE idiot. My phone has been running the latest version of ParanoidAndroid and I decided that I wanted to try MIUI. I booted into TWRP v2.6.3 and wiped everything a couple of times before installing it, and I forgot to install the boot.img afterwards (it was s-on). So now everytime I turn the phone on, it is just always on the boot animation for an eternity, and my computer won't recognize my phone so I can't use fastboot or use an RUU. I am also unable to flash PH98IMG from the phone itself. Is there anything I can do to fix this? Thank you very much in advance.
Click to expand...
Click to collapse
Take out the battery, put it back together, power on the phone while holding down the volume down key til you get the splash screen, that'll boot you to the bootloader...
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
trp6senile said:
No I understand that, but there's nothing I can do from the bootloader. Once I get there, I can either go to TWRP or choose Fastboot. When I choose fastboot, it will say Fastboot USB after connecting to my PC but it will still not show up or be recognized (and I have the drivers). My only other options are Recovery (TWRP), factory reset (also TWRP), clear storage, simlock, and image crc. All I need to do is load the boot.img file, but it appears to me I have no way of doing that now.
Click to expand...
Click to collapse
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
acejavelin said:
Being seen in fastboot has nothing to do with the ROM at all, you need to troubleshoot this from the PC end. When you start fastboot on the phone and connect to your PC you get nothing? Not even a connect sound?
Click to expand...
Click to collapse
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
trp6senile said:
I do get the connect and disconnect sounds. Whenever it makes the connect sound, it doesn't show up under "Devices with Removable Storage." When I heard the connect sound the first time I went to the cmd prompt and typed "fastboot devices" but it showed nothing.
Click to expand...
Click to collapse
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: http://www.htc.com/us/support/content.aspx?id=6196 once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
acejavelin said:
It won't show up as a drive at all in Fastboot mode, to see if it is connected properly go to Device Manager and look for ADB Interface -> My HTC, if it isn't there then your drivers are not installed properly. Drivers come from HTC Sync, which can be downloaded here: <link> once installed and the connections in Fastboot and ADB verified to be working, HTC Sync can be uninstalled (the drivers will stay).
When you run "fastboot devices" you get nothing? Or do you get something like "< waiting for device >" or literally nothing?
What version of Windows are you running, you need to be on Windows 7 or older? Running under Windows 8 is not recommended.
Click to expand...
Click to collapse
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
trp6senile said:
Ah, that may be my problem then, as I am on a Windows 8 computer. I will try all of this on a friends W7 computer in the next few hours and report back with the results. And when I did fastboot devices it literally said nothing and was ready for another command. Thanks for the help!
Click to expand...
Click to collapse
You can also use a live Linux CD like Ubuntu and boot that and install the Linux version of ADB, it works fine.
I'm in the middle of restoring an HTC One M7 Sprint phone to stock from CM11. Since I don't have S-Off, I tried using the minimal package from HTC1Guru, the Reset Download. I have TWRP Recovery, so I copied the Reset Download utility to the phone and ran it. That went ok, except the screen was unresponsive and I had to use a mouse. So, I tried to get an OTA (after relocking the bootloader) to get all current stock. A few minutes into the install of the OTA, it just locked up and there I sat, with the White HTC screen and nothing happening.
So I've tried several things. But a side effect of this condition is I could NOT run ADB. Now I do have a USB connection and it works; In Fastboot if I issue the FASTBOOT DEVICES command I get the device id back. But I could not get ADB to work at all, even though the cable is connected and all that (since Fastboot works). Oh, and ADB worked before this locked up. ADB Devices returns no devices. BUT (it gets weirder) I went back to Fastboot and flashed TWRP REcovery again, and if I enter RECOVERY, I can issue ADB Commands from recovery fine. But outside of recovery, I can't. And, more importantly, PROGRAMS CAN'T DETECT ADB. I tried Rumrunner's program to turn S-OFF, and I tried the ARUWizard RUU utility from Viperboy, and both said to check the USB cable, that ADB could not be found. But I went right to it, booted recovery, and there was ADB!
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen? since right now I can boot to REcovery but not to the ROM, I'm totally dead in the water.
Steve
Steve Thomas said:
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen?
Click to expand...
Click to collapse
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
_that said:
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
Click to expand...
Click to collapse
I thought I must be doing something wrong running ADB with the phone in Recovery since Rumrunner keeps failing with "No ADB Connection". But maybe it's something else.
Thanks!
So, in an attempt to return my device back to stock using the firmware1 and firmware2 method with Fastboot own rebootRUU instead of the simple executable (stupid me, right?)
I had to downgrade my HBOOT from 1.54 to 1.33 to run the RUU. However, upon downgrading it, it said that I had to immediately flush the firmware to the phone for preupdating or whatever, but by that time the Fastboot connection broke for some reason and I wasn't able to type in anymore commands. So I had to restart my phone, and now I am unable to establish a Fastboot connection in bootloader anymore. For some reason the drivers work absolutely fine when booted into android. But when I'm in the bootloader, the My HTC driver loads with a Code 10 this device could not be started error, and using the RUU exe just gets stuck on the black HTC screen because it can't run any Fastboot commands.
XDA, wat do?
Thanks!
Anyone? =/