So I was on my way to unlocking my boot loader and rooting the phone when i ran into this issue. (i am on AT&T)
The phone is stuck on a Red Exclamation Point and then it reboots to a white HTC screen every minute or two.
Where I was at in the process my bootloader was "unlocked", "tampered" displayed. I had even backed up with TWRP. The thing was I couldnt get the USB Debugging turned on. I turned it on before I started the process and was having trouble finishing with superuser and rooting the device. I had been trying forever to setup the S-OFF Feature to NO AVAIL.
Once I unlocked on HTCdev and then setup TWRP I just could never get the phone back to normal.
Once again this is the INT'L Version of the HTC ONE MAX and I just don't know where to turn next.
Please help. I am without phone and just purchased yesterday.
TIA - Mark
Well what you need is an ruu (rom utility updater) which is an updater program officially from htc. but I can't seem to find it for you, perhaps because it's not even made yet..
I'm affraid it's gonna have to go back to the store, are you able to acces to bootloader? if not, then don't worry about it being unlocked, they'll never notice. They're going to reset it for you or give you a replacement.
shaggydiamond said:
Well what you need is an ruu (rom utility updater) which is an updater program officially from htc. but I can't seem to find it for you, perhaps because it's not even made yet..
I'm affraid it's gonna have to go back to the store, are you able to acces to bootloader? if not, then don't worry about it being unlocked, they'll never notice. They're going to reset it for you or give you a replacement.
Click to expand...
Click to collapse
heres my question how do i know what RUU to search for? how do i figure out which version i need based on my phone?
Thanks in advance.
Mark
Well you say you have the international version? but you got it from at&t so it's carrier branded right?
but first things first, you have to be able to access the bootloader to start the ruu. So can you access it?
when in fastboot: find out the CID by this command: fastboot getvar cid
If it answers with : None. Don't worry, try this command: fastboot oem readcid
Then it will tell you the CID. this code is needed when receiving updates from your carrier.
You will need to find the ruu for your CID, any other ruu won't work.
If you find an international ruu for your phone, you can use that one, but you have to have SuperCID.
You can get superCID after you s-off..
If you have SuperCID you can flash any ruu for your device, be careful though, I bricked my htc one s with a wrong ruu.
Goodluck!
the phone is not sold by ATT but is GSM
i cannot access boot loader.
I cant get past the RED EXCLAMATION (so am I bricked?)
this is the phone...
http://www.amazon.com/HTC-One-Max-F...92559809&sr=8-3&keywords=htc+one+max+unlocked
when in fastboot: find out the CID by this command: fastboot getvar cid
If it answers with : None. Don't worry, try this command: fastboot oem readcid
also i did find the TRWP backup if that matters or helps....
i tried both commands and it says fastboot is notrecognized as an internal or external command
operable program or batch file.
Well if you cannot access the bootloader, then you can't use fastboot commands..
Can you tell me what button pressing combinations you have used to enter bootloader?
Can you try to power the phone off completely and then just hold volume down?
The twrp backup can come in handy when your phone gets a working recovery, don't delete that
when i hold down the vol down...it just stays on RED EXCLAMATION....and when I try and enter bootloader mode with vol it just gives me the reset to the White HTC screen and back to the RED EXCL
i have not been able to power down completely
dankduke said:
when i hold down the vol down...it just stays on RED EXCLAMATION....and when I try and enter bootloader mode with vol it just gives me the reset to the White HTC screen and back to the RED EXCL
Click to expand...
Click to collapse
I'm pretty clueless here, If i were you i would keep trying to get in the bootloader. I have had a similar soft brick on my htc one and after half an hour of pressing every key combination it ended up in the bootloader. If that doesn't work I would let it get replaced on warranty
Okay so now I need some HELP.
I took out the SD Card and the SIM Card and the Bootloader screen comes up.
My choices are FASTBOOT, RECOVERY FACTORY RESET, SIM LOCK etc.
What do I do. I feel like I got one chance at this!
And here is my boot loader
my last question....how do i enable the USB Debugging. It shows as being OFF.
Can i do through boot loader or through the CMD Prompt..?
dankduke said:
my last question....how do i enable the USB Debugging. It shows as being OFF.
Can i do through boot loader or through the CMD Prompt..?
Click to expand...
Click to collapse
okey here's what you do, you don't have to have usb debugging enabled. that's only for adb purposes. You need to try and access the twrp recovery from the bootloader. If it doesn't work. try and look for the boot.img file of a twrp recovery for your device and flash that through fastboot
Related
Hi,
I hope someone here can help me! I was trying to upgrade the recovery image and radio on my UK Orange HTC Hero but something has gone horribly wrong.
The phone no longer boots any further than the "HERO" logo splash screen. I've tried leaving it for 10mins+ but no change.
I can't get to the recovery menu
If I have the USB cable plugged in and hold down HOME while putting in the battery in, it shows "FASTBOOT USB" in red at the top left
I've tried using fastboot to flash/update/updateall/boot various signed images but all return "Remote: not allow"
I've tried various RUU recoveries which all seem to work up until the phone tries to reboot into bootloader mode and then just hang with "Waiting for bootloader"
Is it bricked? :-(
Thanks,
Paul
Some more info...
Using fastboot getvar I've got the following version numbers:
Bootloader: 1.76.0007
Baseband: 6.35.09.26
Main: 2.73.61.5
cid: ORANG00§♠Å
Try this
Try booting without the SD card in. Worked for me once.
Nope, still no joy
A logcat would be good.
Sorry, should have been a bit clearer.
The phone doesn't boot, it hangs at the HERO splash screen and won't even enter recovery mode - therefore no ADB access.
All I have access to is fastboot, but anything I try and flash from fastboot fails with "Remote: not allow", presumably because my SPL won't allow fastboot stuff.
Unless there is another way of doing a logcat?
If you are able to get to the fastboot screen then can you still get to the stock recovery and reset your factory then see what happens.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
How would I do that?
Holding down Home while powering on just hangs on the Hero splash screen too.
Thanks!
Edit:
I've also tried VOL-DOWN + Trackball + Power to enter the bootloader, nothing - again it just hangs on the HERO splash screen
A shameless bump...
Anyone have any ideas?
I've tried making a goldcard but I'm not sure how it's going to help.
pejaym said:
A shameless bump...
Anyone have any ideas?
I've tried making a goldcard but I'm not sure how it's going to help.
Click to expand...
Click to collapse
If you have a gold card you should be able to flash any of the HTC hero rru exe files.
That's what I thought.
Same as before though, the RUU detects the phone/versions but when it goes to flash it, the phone reboots but instead of going to the bootloader it goes straight back to the HERO logo splash with "FASTBOOT USB" in red in the top left corner (ie: What it was like when starting the RUU procedure, and all I ever see).
That's when the RUU says "Waiting for bootloader..." and eventually times out.
I've also tried extracting the RUU rom.zip and flashing that manually with fastboot (with and withhout the goldcard in place) but that doesn't work either. If I just do the rom.zip it says invalid signature (like it doesn't detect it as a valid ZIP).
If I extract the various .img files from the ZIP and try and fastboot flash them individually then I get the "remote: not allow" with or without the goldcard.
Any luck... I'm in the same situation... trapped in the fastboot..
I found the solution!
Downloaded the RUU (ftp://xda:[email protected]_2.73.405.5_WWE_release_signed_NoDriver.exe) and while in fastboot usb run the wizard!
And the hero is working again!
Sorry but you'd bricked your phone I think.
Hello,
I have an EVO 3D that was having screen issues.
When I took it to the Sprint store they said my warranty was void for having ViperRom on the device.
The device was HTC unlocked and had ViperRom redline.
I asked them to not note that down and that I would come back tomorrow with the device back to stock settings.
I made a mistake though when I manually flashed a boot.img using adb.
Now I just get a blank screen when the phone starts. I am not able to enable USB debugging or disable fastboot.
Now I can get into the bootloader by using power and the down key.
Since the phone is in Unlocked Mode and S-ON I can't update through ADB without USB debugging or fastboot disabled.
Also any PG86IMG.zip on the SD card doesn't ask for an update when the phone is HTC unlocked
There is no bootloader option to relock the phone either.
If anyone can please help I would greatly appreciate it. I'm supposed to go back there today 9/18/2012 at 4PM PST
Are you able to get into fastboot on your phone? If so what you have to do is relock your bootloader first. Fastboot oem lock is the command. Your phone should pick up the pg86img file and update.
Jsparta26 said:
Are you able to get into fastboot on your phone? If so what you have to do is relock your bootloader first. Fastboot oem lock is the command. Your phone should pick up the pg86img file and update.
Click to expand...
Click to collapse
I can't relock the bootloader using any PC tools. I can get into the bootloader menu by pressing Vol- but since the phone give a black screen when I try to booth I cannot enable USB debugging nor disable fastboot. I think this is what is preventing me from being able to connect to the phone via USB... I'm working on that assumption however I could be wrong.
mateo650 said:
I can't relock the bootloader using any PC tools. I can get into the bootloader menu by pressing Vol- but since the phone give a black screen when I try to booth I cannot enable USB debugging nor disable fastboot. I think this is what is preventing me from being able to connect to the phone via USB... I'm working on that assumption however I could be wrong.
Click to expand...
Click to collapse
I can see when I turn the phone on it's actually functioning, just with a black screen. It still makes noises for receiving text and so on I just can't enable usb debugging and disable fastboot blind. I wonder if I found my HDMI adapter if an external display would work. That would be weird.
mateo650 said:
I can see when I turn the phone on it's actually functioning, just with a black screen. It still makes noises for receiving text and so on I just can't enable usb debugging and disable fastboot blind. I wonder if I found my HDMI adapter if an external display would work. That would be weird.
Click to expand...
Click to collapse
UPDATE: I figured it out that just by selecting fastboot and THEN connecting the USB I could get USB connectivity!
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 I tried Unlocking Bootloader with a made up unlock.bin.
Word of warning be careful if you try it.
This is my experience: OEM UNLOCK with a made up bin phone gives a warning about wiping.
Out of curiosity I wanted to see if it would just fail out it didn't, but instead wiped the phone like it was unlocking the BL, I went into bootloader to check it was still locked (as expected).
But doing the procedure did something to my bootloader. If the phone is off (shutdown) and I plug it into the charger it will immediately boot into bootloader on it's own without me touching the power button.
Also from a powered off state if I power like normal it will boot to bootloader screen instead of system, from which I can boot into the system without issues and the phone works fine.
From a powered up state If I hold the power button for safe mode it will reboot into bootloader mode and then I have to start the phone to get to safe mode.
Has anyone else experienced this? Would reflashing the Nougat firmware correct it?
If not I am fine with the phone the way it is.
Get in bootloader and type: fastboot oem fb_mode_clear
It's a command to close the "startup directly into bootloader". Device should start normal again.
Bender1987 said:
Get in bootloader and type: fastboot oem fb_mode_clear
It's a command to close the "startup directly into bootloader". Device should start normal again.
Click to expand...
Click to collapse
Thank you I will try that when I get home this evening.
Edit: that solved the issue I think I'll leave the boot loader alone for awhile lol.