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.
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
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.
Hello all,
I have a Mate 10 Pro that I was having trouble updating, I assumed due to having TWRP installed. So, I tried to restore the stock recovery via fastboot flash.
However, the flash would always fail with "remote: Command Not Allowed" error. Googling showed this to be result of locked bootloader, but my phone was indeed unlocked. Indicated on the screen when in Download mode.
Some threads suggested relocking and then unlocking the bootloader again. So I ran fastboot oem relock, which restarted and factory reset the phone. Then I ran fastboot oem unlock and I am now getting the "remote: Command Not Allowed" error, and my phone remains locked and now it will not boot at all but only to the eRecovery screen which wants to connect to wifi and download a package but getting package info always fails. Oh, and since I didn't think to remove my account, the phone is also FRP locked.
I had found a thread before this incident saying to change the DNS in order to get the eRecovery download to work, and at the time it did. Now the only thread I find with that suggestion (81.177.139.39, not sure it's the same one) it still fails to get package info.
So as it stands I have a FRP locked, bootloader locked Mate 10 Pro that will only boot to eRecovery.
Anyone have any suggestions?
Hi,
I tried to install twrp on my device and must have done something wrong. I then tried to use one of the fastboot roms to go back to stock. However, this didnt work and i was unable to boot past the fastboot bootloader. For some reason i then decided to run 'fastboot oem lock' and have locked the bootloader. I understand that was stupid and now i'm stuck at a screen that says 'Your device is corrupt. It can't be trusted and will not boot'. Is it possible to fix this or have i permanently bricked this. Thanks for any answers and i'll happily get any other information you need.
Also i have seen the thread that says to use the msm tool to reflash the stock firmware/unbrick but i can't get the device to go into EDL mode. Every time i hold the volume + and - buttons while booting the device shows up on my pc for about 5 seconds before disconnecting. Sorry if i've misunderstood these instructions but i've tried it so many times and it just doesn't seem to go to EDL mode.
Keep trying with MSM tool. It can be very finicky from what I've heard.
Try different usb ports, maybe different cable or computer.
Since you can start your device it's not really hard bricked and you should be able to restore it completely.
Sent from my OnePlus7TPro using XDA Labs
No need to worry.
Flashing the stock rom with fastboot did not work because you have relocked the bootloader. Unlock the bootloader again with fastboot oem unlock and then flash the fastboot stock rom. It would work just fine and you would be able to boot into stock rom.