Hello everyone,
After having unlocked the boot loader I flashed via fast boot TWRP. The only problem is that I flashed "fastboot flash BOOT recovery.img" instead of RECOVERY... I wasn't paying enough attention...
The phone still boots but it goes straight to recovery. What can I do? Fast boot still recognizes it. I was thinking of extracting the boot.img file from a sense based rom like android revolution HD for the m8 or putting the whole rom android revolution HD on an sd card and flashing via recovery. In other threads users had already flashed a custom rom so they could flash the boot.img extracting it from that but I don't know since I still had the stock unlocked rom.
Would one of these solutions solve the problem?
u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU
djkinetic said:
u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU
Click to expand...
Click to collapse
I'll try flashing a boot.img, the other solution is beyond my current skills...
Just extract the boot.img from the ROM you were using. If stock, download one of the stock Roms and then extract the boot.IMG from it and then
fastboot flash boot boot.img
Obviously the boot.img will need to be in your fastboot/adb folder.
Sent from my HTC One_M8 using xda app-developers app
thank you both, I flashed the correct boot.img and everything is fine now
djkinetic said:
u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU
Click to expand...
Click to collapse
What... He just needs to flash a kernel, why potentially cause someone to brick their device by flashing a hboot which wouldn't even solve the issue?
where did you get the boot.img file ? care to share it I am stuck too. My phones is from Rogers
tawer said:
where did you get the boot.img file ? care to share it I am stuck too. My phones is from Rogers
Click to expand...
Click to collapse
Go to my backup thread and get a nandroid ....the kernel is inside the backup.
Thank you so much.
Related
Man, Ive really screwed up now... I didn't back up the stock ROM, tried to root her phone using the HTC Sync method described here.
I successfully unlocked the bootloader and rooted, but still have S-ON. I have HBOOT ver 0.98, by the way.
Then after installing a Cyanogenmod 7.2 ROM through ClockworkMod Recovery (no errors there), the phone freezes on boot at the white screen with green HTC letters.
I tried flashing another ROM (several actually), but they all do the same thing. Freeze on the white boot screen, doesn't matter how long I wait.
So in an effort to get it back to stock, I tried flashing a stock RUU through the bootloader, and I get an error "Main version is older!". Checked my version through "fastboot getvar all" and the main version on phone is 6.01.605.05, so apparently I can't flash anything less than that. The latest version RUU that I've been able to find for download is 5.10.605.9.
Im fairly new to this, but I don't think I can use ADB commands without booting into the OS, is that right?
So in short:
-unable to boot to OS
-can't find a custom ROM that will boot
-can't use ADB commands to downgrade HBOOT or get S-OFF (or can I somehow?)
-can't flash an RUU because my phones version registering higher than anything I can find on the net
So does anyone have any ideas?
Calm down, did you flash the boot.img through fast boot?
To me it looks like you didn't, flash your rom open the rom on computer take out the boot.img and but phone in fast boot then enter the following command
Fastboot boot boot.img
Sent from my SCH-I535 using xda app-developers app
Yes, I tried but it keeps failing. Do you know if my phone has to be unlocked before I flash the boot.img? Also, I am still s-on and don't know how to get s-off from a 6.01.605.05. I am stuck in bootloop and can't get into recovery only hboot/fastboot. Will the Roms you mentioned work with s-on? Should I try flashing the boot.img, system.img, and recovery.img from one of those roms?
GoonAssJuan said:
Calm down, did you flash the boot.img through fast boot?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
mrkmzo said:
Yes, I tried but it keeps failing. Do you know if my phone has to be unlocked before I flash the boot.img? Also, I am still s-on and don't know how to get s-off from a 6.01.605.05. I am stuck in bootloop and can't get into recovery only hboot/fastboot. Will the Roms you mentioned work with s-on? Should I try flashing the boot.img, system.img, and recovery.img from one of those roms?
Click to expand...
Click to collapse
Any rom will work as long as you flash the boot.img from that specific rom
Sent from my SCH-I535 using xda app-developers app
Had the same problem
I had the same problem and flashing the boot.img does work. Make sure your fastboot and boot.img are in the same folder and and you hold shift and open command prompt from there. Also make sure your drivers are working properly. After you flash your boot image to you phone the clear all data/cache/davsik and then instal cyanogenmod!
Hey
I was following this tutorial:
http://forum.xda-developers.com/showthread.php?t=1525100
And everything worked well untill the part I had to boot into recovery mode.
I couldn't get into it and decided to skip that part and just flash the boot.img from the ROM
http://forum.xda-developers.com/showthread.php?t=1778202
I flashed everything succesful without any errors but now my phone won't boot, it just gives me a black screen and can't get into recovery.
My bootloader is unlocked and I can still get into it.
I was thinking about flashing the stock RUU or another ROM, but is this possible?
Now I can't use my desire hd .. need some help with it.
EDIT:
I'm S-ON and unlocked bootloader.
I just tried to flash CWM and it flashed succesfully but still couldn't boot into recovery..
That tutorial is for the Desire S. What RUU did you use?
bananagranola said:
That tutorial is for the Desire S. What RUU did you use?
Click to expand...
Click to collapse
I didn't use RUU yet, I was thinking about it..
...OK, I'm confused. Exactly what have you done?
bananagranola said:
...OK, I'm confused. Exactly what have you done?
Click to expand...
Click to collapse
First I unlocked the bootloader.
Then I moved the ROM's zip file to the SD card.
I flashed the 4EXT Recovery after that.
I couldn't boot into recovery so I flashed the ROM's boot.img
Then I couldn't boot my phone in normal mode
After that I flashed CWM but it also didn't work..
Then I used fastboot erase cache and after that I tried fastboot oem rebootRUU
that's all I did untill now
What did you have on your phone to begin with, stock? What ROM zip did you get the boot.img from? How did you flash recovery? Which image?
bananagranola said:
What did you have on your phone to begin with, stock? What ROM zip did you get the boot.img from? How did you flash recovery? Which image?
Click to expand...
Click to collapse
I had stock rom on my phone, didn't make a backup.
http://forum.xda-developers.com/showthread.php?t=2335496 is the rom I tried to put on my phone, that is where the boot.img is from.
And I flashed recovery with
fastboot flash recovery recovery.img
btw, i dont have a file PD98IMG
EDIT:
I tried booting into recovery with the command fastboot boot recovery.img
but it is stuck on the HTC screen
OK, you've flashed a JB AOSP boot.img on a Froyo/GB Sense ROM. No wonder it's not booting. Again, where did you get the recovery image from? You need to flash a working recovery from fastboot (fastboot flash recovery recovery.img), flash the ROM from recovery, and flash the matching boot.img from fastboot (fastboot flash boot boot.img).
bananagranola said:
OK, you've flashed a JB AOSP boot.img on a Froyo/GB Sense ROM. No wonder it's not booting. Again, where did you get the recovery image from? You need to flash a working recovery from fastboot (fastboot flash recovery recovery.img), flash the ROM from recovery, and flash the matching boot.img from fastboot (fastboot flash boot boot.img).
Click to expand...
Click to collapse
I just googled the CWM Recover img...
Can you link me to a working recovery img? and to a ROM that is running android 4.0 or higher and is easier to flash?
thanks man!
SmikkelMikkel said:
I just googled the CWM Recover img...
Can you link me to a working recovery img? and to a ROM that is running android 4.0 or higher and is easier to flash?
thanks man!
Click to expand...
Click to collapse
Recoveries are device specific. http://www.clockworkmod.com/rommanager. ROMs are all flashed the same way if you are S-On with an unlocked bootloader.
bananagranola said:
Recoveries are device specific. http://www.clockworkmod.com/rommanager. ROMs are all flashed the same way if you are S-On with an unlocked bootloader.
Click to expand...
Click to collapse
Well thanks, I fixed it myself but still thank you for your help.
You sent me in the right direction !
Hi,
Today i tried to install the MIUI rom for my HTC one X, but it kept freezing after 20 seconds.
So i flashed the backup i made before i flashed the MIUI rom, but it froze.
After that i tried to flash a backup i made about a month ago, but didnt work either.
Please help, many thanks
Did you flash the boot image from the miui ROM zip? And when flashed your backups did you reflash the boot img from the backups ?. Last but not least , did you fastboot erase cache after flashing each rom ?
Sent from my thumbs
nogotaclue said:
Did you flash the boot image from the miui ROM zip? And when flashed your backups did you reflash the boot img from the backups ?. Last but not least , did you fastboot erase cache after flashing each rom ?
Sent from my thumbs
Click to expand...
Click to collapse
Thanks to reply so fast,
i did flash the boot.img from the zip of the MIUI. but did not fastboot erase cache.
After i installed the MIUI rom, i booted my device several times and could get passed the bootlogo, but it just freezes after 30 seconds or so.
So i decided to flash those backups, without reflashing the boot.img (thought the backup restores those) niether did i fastboot erase cache.
so now he freezes on the bootlogo after 3 second or so.
Seems to me that you didn't wiped properly, or your hboot is to low maybe ?
Mr Hofs said:
Seems to me that you didn't wiped properly, or your hboot is to low maybe ?
Click to expand...
Click to collapse
my hboot is 1.12.0000
So i need to update my hboot?
i did data/factory reset and wiped dalvic cache in my recovery
Yep thats why JB roms won't boot
Mr Hofs said:
Yep thats why JB roms won't boot
Click to expand...
Click to collapse
thank you very much for your help,
found a threat were you give step by step instructions how to upgrade your hboot, but my question is, can i do all this whitout a rom installed because none will boot.
Depends on wich thread
And yes it should be possible, just flash the standalone firmware, or return to your original stock ICS 2.17 rom and update via official HTC ota.
Mr Hofs said:
Depends on wich thread
And yes it should be possible, just flash the standalone firmware, or return to your original stock ICS 2.17 rom and update via official HTC ota.
Click to expand...
Click to collapse
ok i'll flash the firmware, this is the thread i found: http://forum.xda-developers.com/showthread.php?t=2221171
Give me your main version number
Fastboot getvar version-main
Mr Hofs said:
Give me your main version number
Fastboot getvar version-main
Click to expand...
Click to collapse
2.17.401.2
Well then you need this one for sure !
http://www.androidrevolution.nl/downloader/download.php?file=3.14.401.31.zip
Mr Hofs said:
Well then you need this one for sure !
http://www.androidrevolution.nl/downloader/download.php?file=3.14.401.31.zip
Click to expand...
Click to collapse
So this is the firmware i need to flash using fastboot right?
thanks again for helping me out
First rename the zip to firmware.zip
Fastboot oem lock
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (may be needed twice)
Then unlock the bootloader, flash a custom recovery and then the desired new rom
Mr Hofs said:
First rename the zip to firmware.zip
Fastboot oem lock
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip (may be needed twice)
Then unlock the bootloader, flash a custom recovery and then the desired new rom
Click to expand...
Click to collapse
and the recovery i need to flash is that the one in the zip you send me or do i need to download one myself, and unlocking bootloader is on the site of htc right?
Uhm no the new custom recovery is here.....this one works fine for me
http://db.tt/SPXdFfPw
And if you still have the unlock file, then you can flah it right away
Fastboot flash unlocktoken unlock_code.bin
If you haven't got one you must make one indeed via the HTC devsite
Mr Hofs said:
Uhm no the new custom recovery is here.....this one works fine for me
http://db.tt/SPXdFfPw
And if you still have the unlock file, then you can flah it right away
Fastboot flash unlocktoken unlock_code.bin
If you haven't got one you must make one indeed via the HTC devsite
Click to expand...
Click to collapse
Thank you so much for your time.
No problem :thumbup:
Mr Hofs said:
No problem :thumbup:
Click to expand...
Click to collapse
now i got a other problem, my fastboot doesnt seem to recognize my phone.
it did a few days ago when i tried to flash the rom :s
Try to update the HTC drivers ......
I've been using the HTC Desire HD for a long time, and I was wondering if things I've learnt with that phone are still relevant.
With the DHD, if the phone was S-ON (but with an unlocked bootloader and a custom recovery), whenever flashing a new ROM it was necessary to extract the boot.img file from the zip and flash it manually by using: fastboot flash boot boot.img.
That was because a custom recovery couldn't flash a custom kernel while the device was S-ON.
Is that also the case with an M8 device that stays S-ON?
Or is a custom recovery now able to write any custom kernel regardless of being S-ON/S-OFF?
Thanks!
Indeed
s-on = Flash kernel via fastboot
s-off = kernel is flashed via rom/recovery
Thank you for the quick reply!
quick question..if what you say is true..if s on flash kernal in fastboot..if s off just flash normally threw recovery...why in captins thread with his GPE rom..says s off users must flash boot.img in fastboot?...i was about to try his rom ,before i got to that part..i am s off and ive never had to flash a boot.img threw fastboot before flashing the rom....next question..do i need to unpack the rom zip ,extract the boot.img flash it in fastboot..then repack the zip and flash again in recovery?ive never had to do this..i thought i would see a boot.img zip as a seperate download wouldve been lot easier...ive never unpacked a zip to extract a boot.img before...so i had to back out for now..can someone plz give me step by step directions how to flash captins GPE rom..really appreciate it..and i know im in the correct section to ask such a newbie question..thanks in advance
is this still true with modern Marshmallow/Nougat ROMs (and their associated firmware updates)? the device is unlocked and S-ON?
example: I just flashed ViperROM v6.1 on Tmobile M8 with v6.2 firmware and separate flash of boot.img NOT required.
In fact, I validated theory by doing the traditional procedure and result as phone that did not boot.
traditional procedure: flash ROM via TWRP and reboot direct into bootloader and fastboot. then finalize by manual flash of boot.img via fastboot. boot.img pulled from root directory of ROM zip.
any insight would be appreciated. -GA
Mr Hofs said:
Indeed
s-on = Flash kernel via fastboot
s-off = kernel is flashed via rom/recovery
Click to expand...
Click to collapse
gads1 said:
is this still true with modern Marshmallow/Nougat ROMs (and their associated firmware updates)? the device is unlocked and S-ON?
example: I just flashed ViperROM v6.1 on Tmobile M8 with v6.2 firmware and separate flash of boot.img NOT required.
In fact, I validated theory by doing the traditional procedure and result as phone that did not boot.
traditional procedure: flash ROM via TWRP and reboot direct into bootloader and fastboot. then finalize by manual flash of boot.img via fastboot. boot.img pulled from root directory of ROM zip.
Click to expand...
Click to collapse
No need to flash boot.img separately using fastboot (with s-on).
But it shouldn't hurt anything, either. It's just a redundant step, as you are just flashing the same boot.img that TWRP is already installing.
Try it again, without flashing boot.img separately. But I have a feeling something else is causing no boot. Make sure you are using current TWRP (version 3.1) with default TWRP wipe (cache, dalvik and data), or try another ROM.
I tried installing cm rom ...stable version...and by mistake wiped everything...the rom gave me get prop error....after that the mobile is stuck on hboot
i can unlock the bootloader and lock it and its on HBOOT. Plus i installed the TWRP. Tried side loading rom to it but error.
This is my getvar msg....attached....please help
tried everything...even htc all in one tool kit...locked the phone ..flashed the recovery and boot img and stock through all in one...but error
unlocked and through TWRP tried diff roms...pacman ...cm... but nothing... error
please give links to files (recovery, boot, stock rom, ...etc...etc) when you recommend as stuck and have no phone
ishaqz said:
I tried installing cm rom ...stable version...and by mistake wiped everything...the rom gave me get prop error....after that the mobile is stuck on hboot
i can unlock the bootloader and lock it and its on HBOOT. Plus i installed the TWRP. Tried side loading rom to it but error.
This is my getvar msg....attached....please help
tried everything...even htc all in one tool kit...locked the phone ..flashed the recovery and boot img and stock through all in one...but error
unlocked and through TWRP tried diff roms...pacman ...cm... but nothing... error
please give links to files (recovery, boot, stock rom, ...etc...etc) when you recommend as stuck and have no phone
Click to expand...
Click to collapse
Your hboot is too low. Now download this RUU run as administrator then apply all system updates and the flash the CM11
Thant said:
Your hboot is too low. Now download this RUU run as administrator then apply all system updates and the flash the CM11
Click to expand...
Click to collapse
Just connect through Hboot...?.... leave the device as locked? and run this on fastboot usb? Thats it?
ishaqz said:
Just connect through Hboot...?.... leave the device as locked? and run this on fastboot usb? Thats it?
Click to expand...
Click to collapse
Lock the device start the RUU on the PC after this fallow the instruction on the screen
Thant said:
Lock the device start the RUU on the PC after this fallow the instruction on the screen
Click to expand...
Click to collapse
Thanks buddy...that worked.... :good:
should i now unlock in hboot ...flash recovery TWRP or CWM.... and then install CM11?
any other steps?
Can you give link of stable CM11 please....
or best rom recommended?
ishaqz said:
Thanks buddy...that worked.... :good:
should i now unlock in hboot ...flash recovery TWRP or CWM.... and then install CM11?
any other steps?
Can you give link of stable CM11 please....
or best rom recommended?
Click to expand...
Click to collapse
Check for update and update the phone to latest JB 4.2.2 then unlock bootloader copy CM11 to a folder on your cd card flash twrp 2.7.1 then flash CM11 and flash boot.img from CM11.zip archive
Thant said:
Check for update and update the phone to latest JB 4.2.2 then unlock bootloader copy CM11 to a folder on your cd card flash twrp 2.7.1 then flash CM11 and flash boot.img from CM11.zip archive
Click to expand...
Click to collapse
Yup..still updating... thanks and hats off man....
hope not too much but can you post links to the three...stable cm11 or best rom according to you ...TWRP lastest and i guess boot img will be in the file... just few step by step if possible and links...as dont want to get stuck again :silly:
THANKS again...loads:angel:
ishaqz said:
Yup..still updating... thanks and hats off man....
hope not too much but can you post links to the three...stable cm11 or best rom according to you ...TWRP lastest and i guess boot img will be in the file... just few step by step if possible and links...as dont want to get stuck again :silly:
THANKS again...loads:angel:
Click to expand...
Click to collapse
1. I don't use AOSP download CM11 from Original android thread and gapps. Then copy the CM11.zip and gapps to a folder on your sd card
2. take the boot.img from CM11.zip and paste it in your fastboot folder
3. Download TWRP 2.7.1 and paste it in your fastboot foldert and flash it fastboot flash recovery recovery.img and then fastboot flash boot boot.img and last fastboot erase cache
4. Go in recovery flash First CM11.zip then Gapps and reboot and voala