After unlock, root install recovery, by following
http://www.htconeforum.com/forum/htc-one-s-hacks/385-how-unlock-root-htc-one-s.html
then I put miui.2.8.24 from official website:
http://www.miui.com/extra.php?mod=download/rom&fid=160
after reboot, install miui, then reboot, the screen stays on the boot picture of miui, never changes, I guess that failed, and too bad, I didn't notice there is back up function in recovery, so I didn't notice,
what I have is: fast boot still talks to the phone, but seems can't mount the phone as a drive, so I can't load other ROMs to try it out.
then I try to follow this one:
http://www.htconeforum.com/forum/ht...c-one-s-back-100-stock-relocked.html#post2817
to restore the stock rom, there was any luck, after long time trying, RUU just failed. what should I do now?
I already relock it, can I still unlock it? if so, is there anywhere I can find stock img, and use fast boot to flash the stock img? is that possible?
Thanks.
Did you fastboot the boot.img of say ROM you're flashing?
If using CWM you need to fastboot the boot.img, just extract the boot.img from the ROM
Using fastboot
Code:
fastboot flash boot boot.img
baseballfanz said:
Did you fastboot the boot.img of say ROM you're flashing?
If using CWM you need to fastboot the boot.img, just extract the boot.img from the ROM
Using fastboot
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
first of all, thanks for reply,
no, but i did try to flash another boot.img, and wasn't any luck, so each rom has its own boot.img?
Ummm.......Yeah. It should be in the zip of rom you flashed.
T-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Ummm.......Yeah. It should be in the zip of rom you flashed.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
thanks, I will try it tonight. by the way, after you rooted, you get better battery performance while running stock rom?
Related
hi guys
when i was flashing roms before i had to manually flash boot.img in fastboot since i didnt have twrp
but i noticed the kernel is the same date as the rom i just flashed today (cm10)
do the new CWMs flash the boot.img ?
You need to fastboot because there is no s off
Sent from my HTC One S using xda premium
qwerty warrior said:
hi guys
when i was flashing roms before i had to manually flash boot.img in fastboot since i didnt have twrp
but i noticed the kernel is the same date as the rom i just flashed today (cm10)
do the new CWMs flash the boot.img ?
Click to expand...
Click to collapse
CWM has always been able to flash boot.img with the ROM if you fastboot booted into CWM, like so: (provided the clockwork-recovery-version-blabla.img file is in your current dir ofc)
Code:
fastboot boot clockwork-recovery-version-blabla.img
Maybe CWM can flash the boot.img on certain Hboot versions, what is yours?
Ooh is there a new CWM version for ville?
frdd said:
CWM has always been able to flash boot.img with the ROM if you fastboot booted into CWM, like so: (provided the clockwork-recovery-version-blabla.img file is in your current dir ofc)
Code:
fastboot boot clockwork-recovery-version-blabla.img
Maybe CWM can flash the boot.img on certain Hboot versions, what is yours?
Ooh is there a new CWM version for ville?
Click to expand...
Click to collapse
from what i read only TWRP had the ability to flash boot.img without going into fastboot and using ADB
but when i went into rom manager it said new clockworkmod 5.8.3.1 so i updated
and noticed the new kernel after a normal rom update in recover (CWM)
qwerty warrior said:
from what i read only TWRP had the ability to flash boot.img without going into fastboot and using ADB
but when i went into rom manager it said new clockworkmod 5.8.3.1 so i updated
and noticed the new kernel after a normal rom update in recover (CWM)
Click to expand...
Click to collapse
Na CWM can do it if booted the way i described. Kind of defeats the purpose though as you still need to have a computer hooked up, might as well fastboot flash the boot image. 5.8.3.1 is a couple of months old. But check which Hboot version you have, that might explain why it works for you. You can also check your kernel version with ADB by the way, like so:
HTML:
adb shell uname -a
Hello all. Im new to this particular forum. I own a Galaxy Nexus, but I am unlocking/rooting my buddies One S for him. I have gone through the loops already; unlocked the bootloader, rooted, and installed custom recovery (CWM) with no issues. I was pleasantly surprised to find out that it was a snap compared to his previous HTC Legend. Nightmare.
Anyway, forgive me if this has in fact been answered as I have been searching. After a custom ROM is flashed you still have to flash a boot img via fastboot? I attempted to install CM10 yesterday and get stuck at the HTC boot screen?? Luckily I made a nandroid of the stock ROM and easily reverted. Where do I find the appropriate boot img? Is it just the img that is found in the unpacked ROM? Couldn't find anything pertaining to this in the ROM write up. I know with my Nexus you flash the ROM via recovery and that is it. Strange that you need to also flash the boot img following the ROM flash.
Any help is appreciated.
brunswick000 said:
Hello all. Im new to this particular forum. I own a Galaxy Nexus, but I am unlocking/rooting my buddies One S for him. I have gone through the loops already; unlocked the bootloader, rooted, and installed custom recovery (CWM) with no issues. I was pleasantly surprised to find out that it was a snap compared to his previous HTC Legend. Nightmare.
Anyway, forgive me if this has in fact been answered as I have been searching. After a custom ROM is flashed you still have to flash a boot img via fastboot? I attempted to install CM10 yesterday and get stuck at the HTC boot screen?? Luckily I made a nandroid of the stock ROM and easily reverted. Where do I find the appropriate boot img? Is it just the img that is found in the unpacked ROM? Couldn't find anything pertaining to this in the ROM write up. I know with my Nexus you flash the ROM via recovery and that is it. Strange that you need to also flash the boot img following the ROM flash.
Any help is appreciated.
Click to expand...
Click to collapse
Hello there, since you installed cwm recovery, you have to flash the boot.img via fastboot, if you have the twrp recovery you may not need to flash it via fastboot, it does it for you if you have an hboot under 1.14 but if its over that hboot your going to have to flash the boot.img for any Rom via fastboot. It still wouldn't hurt to flash the boot.img via fastboot but that's just me, well I hope I helped you and if I did then good, and if you wanna know more just ask...
If I helped then just press the thanks button
Sent from my One S
leohdz148 said:
Hello there, since you installed cwm recovery, you have to flash the boot.img via fastboot, if you have the twrp recovery you may not need to flash it via fastboot, it does it for you if you have an hboot under 1.14 but if its over that hboot your going to have to flash the boot.img for any Rom via fastboot. It still wouldn't hurt to flash the boot.img via fastboot but that's just me, well I hope I helped you and if I did then good, and if you wanna know more just ask...
If I helped then just press the thanks button
Sent from my One S
Click to expand...
Click to collapse
Got it to work. Thank you. :good:
brunswick000 said:
Got it to work. Thank you. :good:
Click to expand...
Click to collapse
Hi,
I was using CM10 and now I want to revert back to my previously used stock ROM. However after restoring I'm still unable to boot (I'm using ClockworkMod Touch). Do I need to flash the stock boot.img too? Where I can find it?
Thanks in advance!
TnTonly said:
Hi,
I was using CM10 and now I want to revert back to my previously used stock ROM. However after restoring I'm still unable to boot (I'm using ClockworkMod Touch). Do I need to flash the stock boot.img too? Where I can find it?
Thanks in advance!
Click to expand...
Click to collapse
Its in the rom.zip just extract it. Also look for Flash Image Gui in apps section as enables you too flash a boot.img direct from your phone whilst booted in a rom and will even extract the files for you from the new rom.zip!
Edit: Link to Flash Image Gui - http://forum.xda-developers.com/showthread.php?t=1954121
shadowch31 said:
Its in the rom.zip just extract it. Also look for Flash Image Gui in apps section as enables you too flash a boot.img direct from your phone whilst booted in a rom and will even extract the files for you from the new rom.zip!
Edit: Link to Flash Image Gui - http://forum.xda-developers.com/showthread.php?t=1954121
Click to expand...
Click to collapse
I can't find the zip file for stock HTC ROM
Anyway, I found the boot.img in the nandroid backup folder and it's all good now.
Thank you for the link! ^_^
I would also switch to TWRP. Seems to have less issues, if any, for most folks
Get it thru Goo Manager from PlayStore--
Hi i'm new to the att htc one x, just rooted, and installed twrp... then flash cleanrom5. I also noticed clean has a kernel, i did not see an install guide, but i've installed kernels before on my captivate. So what i'm wondering if it's as easy as....
1. place kernel on phone storage
2. reboot into recovery
3. install kernel from recovery
4. reboot
If there anything i am missing or if i am completely off could someone please help me out with this?
Thank you :good:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
redpoint73 said:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
Click to expand...
Click to collapse
Would you mind walking me through that process?
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
cannon19932006 said:
Would you mind walking me through that process?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
absolutelygrim said:
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
Click to expand...
Click to collapse
I don't see anything about flashing kernels in that thread.
cannon19932006 said:
I don't see anything about flashing kernels in that thread.
Click to expand...
Click to collapse
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery. fastboot flash method http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
edit: btw, what exploit did you use to achieve root? Was it the x-factor exploit?
cannon19932006 said:
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
Click to expand...
Click to collapse
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
redpoint73 said:
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
Click to expand...
Click to collapse
i used x-factor yes, and yes it's 1.14, thank you both for the help.
cannon19932006 said:
i used x-factor yes, and yes it's 1.14, thank you both for the help.
Click to expand...
Click to collapse
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
absolutelygrim said:
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
Click to expand...
Click to collapse
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
cannon19932006 said:
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
Click to expand...
Click to collapse
Well, If cleanROM is using the same Kernel as stock, then you got lucky. If they use the same kernel, no need to flash boot.img.
If they are different kernels and you dont flash boot.img, you are now in a bootloop
lol Universal City
not bad
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
cannon19932006 said:
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
Click to expand...
Click to collapse
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
absolutelygrim said:
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
Click to expand...
Click to collapse
Success, THANKS!
absolutelygrim said:
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery.
Click to expand...
Click to collapse
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
cimenta said:
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
Click to expand...
Click to collapse
Because the new hboot makes it to where you cant flash kernels through recovery. only fasboot
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
cimenta said:
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
Click to expand...
Click to collapse
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
absolutelygrim said:
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
Click to expand...
Click to collapse
So although ROM zip file contains boot.img when flashing boot.img won't be flashed? That's why we need to flash is separately? Is it important to flash it before flashing ROM?
Thank you.R
I'm also, learning as I go. From reading and multiple failed attempts at flashing ROMs and kernels, I have found the correct way with 1.14 Hboot.
-dl the rom/kernel
-extract only the boot.img file
- save both .zip and boot to your desired folder.
-go into recovery and mount sd card to pc
-transfer .zip file to your phones sd card
-get back into fastboot on your phone
-transfer boot.img to fastboot folder
-from fastboot cmd prompt(if you have win7, open your folder with fastboot in it hold shift+right click and open cmd)
-type "fastboot boot boot.img" without quotes
-go back into recovery and clean cache/delvik
-then install .zip that you copied to the sd card
You should be good to go from there.
If I have left anything out, please feel free to correct.
Sent from my HTC One X using xda app-developers app
It is often stated that it is necessary to manually flash boot.img via fastboot AFTER installing a xxrom.zip in recovery.
Is this really necessary?
If you take a look in the file updater-script, which belongs to every xxrom.zip, you find that boot.img is flashed as last action in the update procedure (seen e.g. in the latest CM10-nightly). So I guess that it is not necessary to additionally flash it afterwards using fastboot.
Am I right?
1aladdin1 said:
It is often stated that it is necessary to manually flash boot.img via fastboot AFTER installing a xxrom.zip in recovery.
Is this really necessary?
If you take a look in the file updater-script, which belongs to every xxrom.zip, you find that boot.img is flashed as last action in the update procedure (seen e.g. in the latest CM10-nightly). So I guess that it is not necessary to additionally flash it afterwards using fastboot.
Am I right?
Click to expand...
Click to collapse
You are wrong and right lol. If your Hboot is 1.09 or lower TWRP can flash the boot.img but if you higher you have to fastboot or use Flash Image GUI app. And always a good idea to flash boot.img just in case it has changed but thats more for AOSP roms.
Darknites said:
You are wrong and right lol. If your Hboot is 1.09 or lower TWRP can flash the boot.img but if you higher you have to fastboot or use Flash Image GUI app. And always a good idea to flash boot.img just in case it has changed but thats more for AOSP roms.
Click to expand...
Click to collapse
I have Hboot 1.13 - so I need to "fastboot flash boot boot.img"
Unfortunately there is no error message showing that flashing the boot-partition during xxrom.zip-Installation in TWRP-recovery has failed.
I suppose that there is no particular order between installing the xxrom.zip and flashing boot-partition. Am I right?
1aladdin1 said:
I have Hboot 1.13 - so I need to "fastboot flash boot boot.img"
Unfortunately there is no error message showing that flashing the boot-partition during xxrom.zip-Installation in TWRP-recovery has failed.
I suppose that there is no particular order between installing the xxrom.zip and flashing boot-partition. Am I right?
Click to expand...
Click to collapse
I use to fastboot first then rom but now I just use Flash Image GUI. TWRP wont say its failed for some reason but it can if you remove the boot.img but thats nothing to worry about.
there is a method how to downgrade hboot:
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade+unbrick
it's a little bit tricky and requires some linux knowledge, but it takes you down to hboot 1.06
Flashed the latest RUU from HERE, and it boots into the OS perfectly.
Then, flashed Stock GPE from HERE and also tried LolliGPE from HERE. Both will not get past the boot screen, after waiting over 30min's.
In attempts to fix, the latest full firmware, TWRP, full wipe/dirty wipe, and DH's 5.1 firmware have been flashed, then the custom ROM's flashed again followed. Same issue is persists. Each time, trying to flash the RUU back, boots without issue.
Prior to flashing the latest RUU (hboot method, 0P6BIMG.zip), I have ran all the ROM's mentioned and others without issue.
I'm at a loss of what to try next, or why it's hanging. Right now, i'm leaving it for hours at the boot screen, but I doubt this is going to cure anything and only provide a hot phone during the whole time.
The phone is unlocked, S-OFF, and SuperCID.
Any suggestions i'm willing to try.
Update:
Woke up 6+ hours later, and it was still stuck on the boot screen.
Flashed the latest Fluent ROM found HERE, and it boots fine. Then did a full wipe (Cache, Dalvik Cache, Data, System), then the standalone data wipe, and factory reset. Installed GPE from HERE, and it stuck on the boot screen again after waiting 20min's...
Next step i'm going to try is 4.4.4 RUU, then full latest OEM firmware. If GPE doesn't boot still, i'll try DH's 5.1 firmware.
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
kcasner said:
Still has the same problem.
I have no idea what else to try. Wish I never flashed that damn RUU file!
Click to expand...
Click to collapse
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
santod040 said:
The stock secure boot.img is probably what's causing you issues.
Choose a Rom, take it's boot.img and fastboot flash it.
fastboot flash boot boot.img
Then flash the Rom.
Profit...!?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
That was exactly it, what a relief. Thank you!
kcasner said:
That was exactly it, what a relief. Thank you!
Click to expand...
Click to collapse
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
dottat said:
Run files are not to blame or the problem. In fact, if you simply flash a full ruu file your phone would boot up fine.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
kcasner said:
That's what I said in the first post/sentence. The boot.img in the RUU was the root cause for other ROM's not booting. This was verified 3x with identical results.
santod040 was spot on :good:
Click to expand...
Click to collapse
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
dottat said:
I don't think you follow me.
The ruu is the same as stock.
Do you recall having to manually flash an insecure boot img before you flashed your first custom rom?
It's no different.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Honestly can't recall. I follow; we're on the same page, different lingo.
kcasner said:
Honestly can't recall. I follow; we're on the same page, different lingo.
Click to expand...
Click to collapse
kcasner, I had exactly same issue as you. Could you explain a bit detail on how you get it fixed?
I want to flash DH5.1. Are these correct steps I should following:
1) open DH5.1 zip file, find the boot.img (I found there're two boot.img, stock/boot.img and elite/boot.img, I guess I should use later one)
2) fastboot flash the boot.img
3) boot into recovery to flash DH5.1
4) reboot
Thanks for help!