i was flashing a rom via ruu then when the error that says flush immediately popped up i typed fastboot oem rebootRUU but it said waiting for device so i disconnected the phone and rebooted into fastboot but i might have rebooted into android i can't remember, now fastboot doesnt work. anyone help ? thanks.
also on the bootloader it says OS-3.62.1700.1 (3.10.502.2) in red letters. its relocked bootloader s-off cid1111111 i wanted to go to stock cause its on gpe 4.4.2 and its still there.
Related
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
further
by the way, i think i went wrong by failing to flash boot.img as i have s-on. after install of rom via cwm, flyer got in a bootloop (ended up having to bootstrap battery as it drained). since this, flyer would not boot. Entering recovery just caused a quick glimpse of recovery screen before bootlooping. Since this i now can only get to my hboot screens, attempting to boot or recovery just gives me the wgite htc screen indefinitely.
adb driver?
ok, i think my issue is with adb.
with flyer in hboot so options are
fastboot
recovery
factory reset
clear storage
simlock
image crc
when i check device manager, it is listed as ADB interface, expand that and you get 'bootloader interface'
put flyer in fastboot mode, i see
bootloader
reboot reboot bootloader
power down
and the device is gone from device manager completely.
in either mode, when in adb running command 'adb devices' i get nothing, although running commands such as 'fastboot flash boot boot.img/recovery.img i get a success message after writing. 'fastboot reboot' will successfully reboot the device but it still does not boot up or enter recovery when attempted.
am i missing an adb driver or something?
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
Hey guys I need help. My HTC One is stuck in bootloader mode. I was trying to upgrade to the latest T-Mobile update. I tried downgrading with an RUU and I tired to flash stock recovery. I'm not all too sure what exactly happened, but I have no OS or recovery mode. All I have is bootloader mode. When I try to reboot to OS there is a bootloop. When I try to go into recovery a picture of a phone shows up with a red triangle and exclamation point. When I enter Fastboot in the bootloader it shows up on the phone as Fastboot USB. Although it says Fastboot USB, the phone is not recognized on the computer. When I try to enter fastboot commands, the prompt says "waiting for device" no matter what command I type.
If I could get the computer to recognize the phone, I could flash a recovery and a ROM or run an RUU. But that is only if I could get it to recognize the phone and I can't. I have searched for days and I can't find anything that works.
I have no OS, no recovery mode, and the bootloader isn't recognized on the computer. Please help! any help/advice will be greatly appriciated!
Please and thank you! :good:
amkivb said:
Hey guys I need help. My HTC One is stuck in bootloader mode. I was trying to upgrade to the latest T-Mobile update. I tried downgrading with an RUU and I tired to flash stock recovery. I'm not all too sure what exactly happened, but I have no OS or recovery mode. All I have is bootloader mode. When I try to reboot to OS there is a bootloop. When I try to go into recovery a picture of a phone shows up with a red triangle and exclamation point. When I enter Fastboot in the bootloader it shows up on the phone as Fastboot USB. Although it says Fastboot USB, the phone is not recognized on the computer. When I try to enter fastboot commands, the prompt says "waiting for device" no matter what command I type.
If I could get the computer to recognize the phone, I could flash a recovery and a ROM or run an RUU. But that is only if I could get it to recognize the phone and I can't. I have searched for days and I can't find anything that works.
I have no OS, no recovery mode, and the bootloader isn't recognized on the computer. Please help! any help/advice will be greatly appriciated!
Please and thank you! :good:
Click to expand...
Click to collapse
keep on rebooting until it's seen in the PC. Make sure the driver is installed (or forcible install it if it's an unknown device).
After that, once you're able to see it... re-flash the unlock token (fastboot flase unlocktoken unlock_code.bin). That will get you back into the ROM. At least, that's what did for me:
http://forum.xda-developers.com/showthread.php?t=2665481
But I can't reflash an older RUU at all, so I can't downgrade.
Drashna said:
keep on rebooting until it's seen in the PC. Make sure the driver is installed (or forcible install it if it's an unknown device).
After that, once you're able to see it... re-flash the unlock token (fastboot flase unlocktoken unlock_code.bin). That will get you back into the ROM. At least, that's what did for me:
http://forum.xda-developers.com/showthread.php?t=2665481
But I can't reflash an older RUU at all, so I can't downgrade.
Click to expand...
Click to collapse
I figured it out. All I needed was windows 7 instead of 8 for some reason. After I installed 7 I just ran the 4.3 RUU. Now I have a different problem. Originally this all happened because I was going to upgrade to the new 4.4.2. Now I can't flash stock recovery. I have cwm but I need stock recovery to upgrade to 4.4.2. Since there is no 4.4.2 RUU I don't know what to do now.
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? =/
Hello there!
I was on Sultanxds Custom rom + kernel and decided to flash another Rom. Therefore i wanted to update my TWRP to Version 3.0.2.0.
So i went into fastboot, connected my phone to the pc as always an ran the comand: "fastboot flash recovery twrp-3.0.2-0-onyx-20161116-113742.img". I got the message: "FAILED (remote: Device not unlocked cannot flash or erase)"
So i checked for oem unlock and this was the message i got.
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false"
I just dont understand why the bootloader is locked... how is this even possible but anyways so i tried to just normaly reboot the device. But now i see the 1+ logo for 1 sec and it vibrates. And then it turns black again and I see the logo again and again...
But i'm still able to enter fastboot mode and i can send command from my PC. Can anyone tell what steps i have to do to make it bootable again? (is this a hardbrick?).
Thx in advice!
I just followed the hardbrick guide and i'm now on stock OS. For some reason the bootloader was locked again... problem solved and this thread can be closed...