Hard to say. They have been known to take their sweet @ss time with those boot loader token requests lately.
Sent from my HOX w/CM10.1
Quick question,
Will my phone be inoperable while I attempt to unlock the bootloader?
HTCdev still hasn't registered my account even after I've replied to them so I'm skeptical about the reply time for a token from them.
Thanks in advance guys!
Yes. I'd read up on adb, Hboot,and if this is your first android exploit? Read up on recovery IMG.... There is a lot more.
Sent from my HOX w/CM10.1
I put android on my touchpad, i dont know know if that counts.
But right now, this looks like it might be over my head...
I thought I just need to root it, unlock the bootloader, and then install the custom ROM.
Now I'm reading about changing the radio, hboot, etc.
Its not all that bad... Lol. Most custom ROMs have there own kernel's and radio built in so no worries there. You on the right track. We have s-off now also bonus! But starting with unlocking and if you have Hboot 1.14 you'll want to downgrade you Hboot with jet. Ah ya.... know I'm down to chat on gtalk if you pm me I'll set you up.
Sent from my HOX w/CM10.1
IMost custom ROMs have there own kernel's and radio built in so no worries there.
But right now, this looks like it might be over my head...
I thought I just need to root it, unlock the bootloader, and then install the custom ROM.
Now I'm reading about changing the radio, hboot, etc.
Its not all that bad... Lol. Most custom ROMs have there own kernel's and radio built in so no worries there. You on the right track. We have s-off now also bonus! But starting with unlocking and if you have Hboot 1.14 you'll want to downgrade you Hboot with jet. Ah ya.... know I'm down to chat on gtalk if you pm me I'll set you up.
Sent from my HOX w/CM10.1
No need to downgrade hboot now that we have s-off. Numerous people have confirmed that s-off removes the kernel flashing issue with 2.2x and later.
Stuck on HTC logo with red letters after trying to restore the original at&t rom from a backup I made earlier.
A user mentioned a similar problem around page six of the thread. He was told to hold down the power button and the volume down button to get to fastboot. That doesn't work. That has never worked for me. When I hold the buttons down the arrow, home, and recent apps buttons start flashing, but nothing happens.
Hold power and volume down for a few seconds (about 5 sec) until the capacitive buttons flash, and keep holding. The phone will power off. Once the screen is black, release the power button (keep holding volume down) then press power button for 3 seconds and release. Keep holding volume down (shouldn't have release it at any point in the sequence so far) until the white hboot screen comes up.
Sounds like your original problem, is you just forgot to flash boot.img when you flashed the ROM.
What hboot version?
I thought I had flashed the boot.img. I used the fastboot flash boot boot.img command with the boot.img extracted from the AOKP ROM.
C:\X_Factor_Windows>fastboot flash boot boot.img
sending 'boot' (5300 KB)... OKAY
writing 'boot'... OKAY
I put the ROM.zip file and the gapps.zip file on the phone's storage. I wiped dalvik cache, system, and factory reset.
I gotta say, I'm proud of our little community. I really haven't seen any harsh words or flaming of the recent wave of noobs, even though a lot of problems could have been easily avoidable on their part. Great job for those who have helped someone recently. I'm sure those in need appreciated it, even if they haven't hit the thanks button. They'll soon see how great the HOXLers are!
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium