So I recently unlocked ky bootloader and rioted and flash cwm,and flash a cm10 Rom and it boots up but just stays at the bootlogo AMD doesn't do anything else anyone know what's wrong?
Sent from my HTC VLE_U using xda premium
brandontamas said:
So I recently unlocked ky bootloader and rioted and flash cwm,and flash a cm10 Rom and it boots up but just stays at the bootlogo AMD doesn't do anything else anyone know what's wrong?
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
You need to fastboot boot.img.
u did not flash the kernel that is the boot.img. from fastboot flash the boot.img by using this command---
fastboot flash boot boot.img
Sent from my One V
Related
I bought it yesterday and when I tried to go with the rooting process, when I rebooted into the bootloader, it said ***UNLOCKED*** and above that it said ***TAMPERED***. I figured that it was already unlocked so I resumed with the process. I installed the CWM recovery and the SuperSU.
However, it still say "Ship S-On" in the bootloader. Am I free to flash ROMs or am I supposed to get it to S-Off somehow?
S-Off rooting has not been achieved yet. Unlocking bootloader and rooting with the current methods will allow for custom ROM installation.
hTc One S
One s doesnt have S-off yet,but you can flash rom s anyway .you will just have to fastboot the boot or use twrp recovery ,
I would stick to fastboot tho as twrp doesn't always flash the boot for me.
Enjoy
Sent from my HTC One S using xda premium
pushtostop said:
One s doesnt have S-off yet,but you can flash rom s anyway .you will just have to fastboot the boot or use twrp recovery ,
I would stick to fastboot tho as twrp doesn't always flash the boot for me.
Enjoy
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
So I flash the ROM first. Then If i want to install a kernel, I install through fastboot? In that order?
For example: I flash This ROM first and then I reboot into fastboot in the bootloader to flash This Kernel?
Ya you can flash kernel first or last doesn't matter , just fastboot boot.IMG reboot to recovery and flash Rom
Sent from my HTC One S using xda premium
i was craving some aosp so I wiped then flashed aokp. Want to switch back now, so I rebooted to recovery but twrp splashscreen shows for 2 seconds, then screen goes black. then the phone reboots into normal os. i tried reinstalling twrp via goomanager to no avail. will flashing the img make any difference? any one else have this issue?
ok i tried flashing the twrp img and still no go. gonna try ruu'ing now unless someone jumps in with a solution.
Are you rooted and bootloader unlocked?
Sent from my HTC One X using xda premium
yes... i've been around here for ages. just this problem is very weird. tried erasing recovery via fastboot and says fastboot remote not allowed FAILED. gonna ruu now.
if ruu dosent work try relocking bootloader by using the "fastboot oem lock" command i believe and then ruu
Sent from my HTC One X using xda premium
DJ-midnite said:
if ruu dosent work try relocking bootloader by using the "fastboot oem lock" command i believe and then ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
lol thats what I just said but thanks anyway
k ruu'ed and all is back to normal. interestingly, no data was wiped when i relocked bootloader and flashed ruu.
and remember try wiping/factory reset when flashing aokp on twrp, and youre welcome
Sent from my HTC One X using xda premium
i need help i cant get the wifi to work on the viper rom 1.2.0 i wiped everything and once i flashed i wiped again and still nothing
Anyone?
Sent from my HTC One S using xda app-developers app
If your on the latest tmob ota you're out of luck
Sent from my HTC VLE_U using xda app-developers app
Can't he just change his cid to 001 and flash 2.31 ruu?
Sent from a man, using a mobile phone
Have you tried flashing the boot.img (the correct one, extracted from the ROM zip) with fastboot? Well, try it again! "adb fastboot flash boot boot.img" and make sure that you have the boot.img in the folder where you run the command. This way you will reflash the kernel and at least the WiFi problem should go away.
VERY IMPORTANT after you run the flash boot command in fastboot, it is recommended to do a "fastboot erase cache" before booting.
Cheers!
Do i need to flash the boot.img from the kernel from fastboot before installing the kernel from recovery? Or if this is completely wrong and im crazy, could someone correct me
Many thanks!
Depends on your Hboot. I'd downgrade it if yours is 1.14 or higher
Sent from my One X using xda premium
Is there an easier way of rooting after running ruu 3.18 update if I was already s-off?
Sent from my HTC One X using xda premium
If your bootloader is unlocked just flash twrp 2.3.3.1 or under. Then you can flash su or wipe everything and flash a ROM.
Sent from my One X using xda app-developers app
exad said:
If your bootloader is unlocked just flash twrp 2.3.3.1 or under. Then you can flash su or wipe everything and flash a ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I've unlocked bootloader and installed twrp also flashed su and tried to flash CM10. I wiped cashe and and then installed CM10.1 and now it freezes on "HTC quitly briliant" screen and some warning notes under it.. what to do?
Is it necessary tu S-off?
Wipe everything not just cache. Then fastboot flash boot boot.IMG right before or after flashing the ROM. The boot.img should be extracted from the ROM you're flashing.
Sent from my One X using xda app-developers app
exad said:
Wipe everything not just cache. Then fastboot flash boot boot.IMG right before or after flashing the ROM. The boot.img should be extracted from the ROM you're flashing.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Is it necessary to S-off?
Only if you wish to ruu without bricking after supercid
Sent from my Sony Tablet S using xda app-developers app
Wouldn't the ruu lock the bootloader tho?
Nevermind it worked!
Sent from my HTC One X using xda app-developers app
mircony said:
Wouldn't the ruu lock the bootloader tho?
Click to expand...
Click to collapse
No. RUU doesn't "lock" anything. If S-on, you typically need to relock the bootloader to run an RUU (but as mentioned, running the 3.18 RUU with S-on and SuperCID will brick the device).
But with S-off, it doesn't matter if bootloader is locked or not.