im on hboot 1.15 and i understand i need to flash the cm10 Boot.img but how do i get it I cant seem to extract the cm10 zip file for some reason
Its in the rom. Just pull it out and put it in your adb folder
cortes742 said:
im on hboot 1.15 and i understand i need to flash the cm10 Boot.img but how do i get it I cant seem to extract the cm10 zip file for some reason
Click to expand...
Click to collapse
my free application, Flash Image GUI, will automatically extract the boot.img file and flash it. Then the next step is to reboot into the custom recovery and install the exact same rom.zip file.
essentially with htc's unlock method, the kernel portion of a ROM .zip can't be loaded from the standard recovery boot mode. my application, Flash Image GUI, loads the kernel portion of the ROM .zip from Android mode, easily allowing you to reboot into the custom recovery and apply the system portion of the ROM .zip.
if you're interesting in the more manual/command line route, which requires access to a desktop, the command you'll need is fastboot flash boot boot.img. in addition, the ROM .zip file should be the same as any other .zip file. if it doesn't open properly, might be a corrupt download. the boot.img is generally located in the root of the rom.zip file, or sometimes in a sub folder called kernel or boot. Flash Image GUI is very good at searching/locating the boot.img file in valid ROM .zip files.
hope the suggestions and some of those technical details help!
joeykrim said:
my free application, Flash Image GUI, will automatically extract the boot.img file and flash it. Then the next step is to reboot into the custom recovery and install the exact same rom.zip file.
essentially with htc's unlock method, the kernel portion of a ROM .zip can't be loaded from the standard recovery boot mode. my application, Flash Image GUI, loads the kernel portion of the ROM .zip from Android mode, easily allowing you to reboot into the custom recovery and apply the system portion of the ROM .zip.
if you're interesting in the more manual/command line route, which requires access to a desktop, the command you'll need is fastboot flash boot boot.img. in addition, the ROM .zip file should be the same as any other .zip file. if it doesn't open properly, might be a corrupt download. the boot.img is generally located in the root of the rom.zip file, or sometimes in a sub folder called kernel or boot. Flash Image GUI is very good at searching/locating the boot.img file in valid ROM .zip files.
hope the suggestions and some of those technical details help!
Click to expand...
Click to collapse
I tried using that method but your app says it could not locate the right zimage from the CM10Zip that i downloaded of Xda i was really confused as to why i couldnt even open the cm10 zip without getting and error on my desktop let alone the app. any thoughts?
cortes742 said:
I tried using that method but your app says it could not locate the right zimage from the CM10Zip that i downloaded of Xda i was really confused as to why i couldnt even open the cm10 zip without getting and error on my desktop let alone the app. any thoughts?
Click to expand...
Click to collapse
Try downloading the ROM again and use a program like 7zip to unzip the ROM. I'm pretty sure you can go into the ROM with esfile explorer from your phone. Then use flash image GUI and select the boot.IMG exactly.
Sent from my EVO using xda premium
Never mind....
cortes742 said:
I tried using that method but your app says it could not locate the right zimage from the CM10Zip that i downloaded of Xda i was really confused as to why i couldnt even open the cm10 zip without getting and error on my desktop let alone the app. any thoughts?
Click to expand...
Click to collapse
Sounds like a bad download of the ROM .zip file. Downloading a 2nd time should resolve the issue. Many times you can check the md5sum of the downloaded file to ensure the download is correct.
If you still get the error from my app, after downloading the file again and ensure the md5sums match, link me to the exact file? I'd like to take a look.
Hope that helps!
joeykrim said:
Sounds like a bad download of the ROM .zip file. Downloading a 2nd time should resolve the issue. Many times you can check the md5sum of the downloaded file to ensure the download is correct.
If you still get the error from my app, after downloading the file again and ensure the md5sums match, link me to the exact file? I'd like to take a look.
Hope that helps!
Click to expand...
Click to collapse
thanks bro after downloading it a couple times it still wasnt working for me but after the 8/29/2012 update i downloaded it unzipped like a charm. =0 thanks for the amazing support!
So i was able to get the cm10 boot.img and flash it through the flash Gui app. once i did that flashed the cm10 rom in recovery. i triedd to boot into it and i keep getting sent back to the bootloader. I wiped cache davlik factory reset and wiped the system. was i not supposed to wipe the system? now i cant even restore to a sense rom is it because i flashed the cm10 boot.img? i am assuming i need to FASTBOOT a sense boot.img since i cant get into a sense rom.
So finally after flash gui not working for me i Fastbooted the Boot.img through adb and was able to flash cm10 zip again and it BOOTED! i tried this method after downloading the 8/31/2012 cm10 zip. I think i wiped system last time which messed up the whole thing!
cortes742 said:
So finally after flash gui not working for me i Fastbooted the Boot.img through adb and was able to flash cm10 zip again and it BOOTED! i tried this method after downloading the 8/31/2012 cm10 zip. I think i wiped system last time which messed up the whole thing!
Click to expand...
Click to collapse
Wiping the system and then trying to boot will definitely cause issues. Glad everything worked out!
For future reference, if you do experience any issues you think are related to how Flash Image GUI functions, feel free to post up in that thread. I do my best to respond as soon as possible!
Related
I just rooted using a guide for the revolutionary method. It says the .exe is supposed to ask if you want to install clockwork after it obtains s-off & it never asked me. I do have s-off but no recovery and no superuser as well. I searched this problem and found answers. I found a zip & renamed it to PG86IMG.zip on the root of my sd or whatever & tried to install it but i don't think it worked. I've tried to go into recovery & all I get is an image of a phone & a red triangle. I have a clockwork img now but I have no idea how to install it & i tried to go to my sdk but all my laptop says it has is sdk manager & it won't let me enter any commands. I've been reading for hours & I'm stuck. Any help would be appreciated if anyone knows & thanks
Download this file and rename it PG86IMG.zip and place on the root of your sdcard. Its twrp recovery, which I prefer to cwm
http://db.tt/aShyeKO9
Now turn off phone and boot into the hboot and wait for it to check for update files and follow instructions to install. I think its up for yes and down for no, and wait for it to install. Then reboot and delete the file from your SD card. You should be able to boot into recovery now. Then flash this fixed su found in the twrp recovery thread.
http://db.tt/bZeTixgR
Sent from my Premium XDA app
lexusmike said:
Download this file and rename it PG86IMG.zip and place on the root of your sdcard. Its twrp recovery, which I prefer to cwm
http://db.tt/aShyeKO9
Now turn off phone and boot into the hboot and wait for it to check for update files and follow instructions to install. I think its up for yes and down for no, and wait for it to install. Then reboot and delete the file from your SD card. You should be able to boot into recovery now. Then flash this fixed su found in the twrp recovery thread.
http://db.tt/bZeTixgR
Sent from my Premium XDA app
Click to expand...
Click to collapse
I renamed it and everything & put it on the root of my sd but when I get into hboot & it loads it says no image
Make sure you don't have the file named as PG86IMG.zip.zip
If you have file extensions turned off in Windows you may have done that by accident. If you have file extensions hidden just name is PG86IMG without the .zip part.
You're also probably trying to flash a recovery on an HBOOT v1.5 phone; I've had no luck flashing it with the aformentioned .zip method try using fastboot to flash the recovery:
(On windows)
fastboot flash recovery [whatever the name of the file is].img
Click to expand...
Click to collapse
If you're not familiar w/ fastboot and such see the following thread:
http://forum.xda-developers.com/showthread.php?t=1239821
respectagain said:
Make sure you don't have the file named as PG86IMG.zip.zip
If you have file extensions turned off in Windows you may have done that by accident. If you have file extensions hidden just name is PG86IMG without the .zip part.
Click to expand...
Click to collapse
This was actually the issue. I put the .zip in there when I really just should've put PG86IMG so it wouldn't have .zip twice. Thanks for the help guys
Sent from my PG86100 using xda premium
from
http://forum.xda-developers.com/showthread.php?p=26199933
I already dl the gsmfix.zip file but I don't know how to flash it.
thx
gabox99 said:
from
http://forum.xda-developers.com/showthread.php?p=26199933
I already dl the gsmfix.zip file but I don't know how to flash it.
thx
Click to expand...
Click to collapse
Flash in recovery. You need Amon Ra installed or any other recovery like TWRP or CWM. Boot into recovery and choose zip from SD.
zac41189 said:
Flash in recovery. You need Amon Ra installed or any other recovery like TWRP or CWM. Boot into recovery and choose zip from SD.
Click to expand...
Click to collapse
thx
now the phone gets stuck in the
white screen
with the words
htc one
p.d.
my ROM is BAMF-33112-RELEASE-KEYS.zip
don't flash gsmfix.zip there. that is only for sense 4 ROM developed by Joel.
On the same page of download link you can find stockgsmfix.zip, try to flash that as bamf-33112-release-keys.zip is based on sense 3.6. hope this helps you!
kancherlapraneeth said:
don't flash gsmfix.zip there. that is only for sense 4 ROM developed by Joel.
On the same page of download link you can find stockgsmfix.zip, try to flash that as bamf-33112-release-keys.zip is based on sense 3.6. hope this helps you!
Click to expand...
Click to collapse
I flash stockgsmfix.zip and the phone still gets stuck in the white screen
with the words htc one
It should work. anyway you are running BAMF sense 3.6 ROM right?
IF that is the case , do clean wipe, flash ROM again, change below values in /system/build.prop file using any editor and reboot once( better do factory reset )
ro.config.lte=false
ro.telephony.default_network=3
kancherlapraneeth said:
It should work. anyway you are running BAMF sense 3.6 ROM right?
IF that is the case , do clean wipe, flash ROM again, change below values in /system/build.prop file using any editor and reboot once( better do factory reset )
ro.config.lte=false
ro.telephony.default_network=3
Click to expand...
Click to collapse
ro.config.lte=false
ro.telephony.default_network=3
I made those changes inside the BAMF-33112-RELEASE-KEYS.zip file and save it
I did the steps and the same, gets stuck after reboot
in the white htc screen.
were you able to boot atleast once? if you are s-on you need extract boot.img (kernel) and need to flash it via fastboot usb ( fastboot flash boot boot.img)
below are steps
- extract boot.img from your downloaded zip file
- place it in android-sdk/platform tools folder- you will have fastboot executable there ( need to have android sdk and HTC driver installed on your pc)
- open command prompt ( right click on cmd -> run ad admin) and navigate to platform-tools folder
- reboot your phone to booltloader and select fastboot
- run command "fastboot flash boot boot.img"
- reboot the phone
If a flashable boot,img is provided in BAMF thread you can just flash it via bootloader
kancherlapraneeth said:
were you able to boot atleast once? if you are s-on you need extract boot.img (kernel) and need to flash it via fastboot usb ( fastboot flash boot boot.img)
below are steps
- extract boot.img from your downloaded zip file
- place it in android-sdk/platform tools folder- you will have fastboot executable there ( need to have android sdk and HTC driver installed on your pc)
- open command prompt ( right click on cmd -> run ad admin) and navigate to platform-tools folder
- reboot your phone to booltloader and select fastboot
- run command "fastboot flash boot boot.img"
- reboot the phone
If a flashable boot,img is provided in BAMF thread you can just flash it via bootloader
Click to expand...
Click to collapse
I extract boot.img from PH98IMGnewfirmwarepeople.zip
I did it and the same, it gets stuck in white HTC screen.
Extract boot.img from your downloaded rom zip file and flash
Sent from my PI86100 using Board Express
gabox99 said:
I extract boot.img from PH98IMGnewfirmwarepeople.zip
I did it and the same, it gets stuck in white HTC screen.
Click to expand...
Click to collapse
the issue is with the STOCKGSMFIX.zip, it seems doesn't work with
BAMF-33112-RELEASE-KEYS ROM
dont flash that. just change the build.prop values and flash ROM and boot.img. that should be good enough!
kancherlapraneeth said:
dont flash that. just change the build.prop values and flash ROM and boot.img. that should be good enough!
Click to expand...
Click to collapse
Finally!
It works!
I can send SMS!
thank you!
I rooted my htc evo 4g lte and have twrp installed, and tried to flash a rom, when i rebooted it always takes me back to hboot screen and is stuck there, won't actually boot up. I am able to go to recovery and use twrp including usb mount (maybe a zip i could flash to help). I have searched for awhile but haven't found any real solution for my phone yet.
I have S-on, no external sd card.
If you need any more info just ask.
Thanks in advance for the help!
Extract the boot.img from the rom, place it in adb folder and put phone in fastboot
Type fastboot flash boot boot.img and restart the phone
solved!!!!!!!
om4 said:
Extract the boot.img from the rom, place it in adb folder and put phone in fastboot
Type fastboot flash boot boot.img and restart the phone
Click to expand...
Click to collapse
Thankyou so much for the fast reply, and fix!! I did what you said and it worked! The funny thing is that it was my first flash, is there something i did or should avoid to have this happen to me again? Any way I am so grateful and now am going to try out team venoms viper4g 2.0.2 new rom!
If others have the same problem and want more detailed info about what I did:
1. downloaded sdk manager developer.android.com/sdk/index. html opened the program and installed platform tools
2. Since I have twrp I put into recovery and mounted usb found the zip of the rom i wanted to flash opened it found the boot.img and copied it to the folder where platform tools where installed (C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools)
3. got back to hboot screen
4. opened cmd to the folder by typing: cd then file path like mine above
5. then in cmd typed fastboot flash boot boot.img it will do its thing
6. restart phone and hopefully work for you too!
vipomorge said:
Thankyou so much for the fast reply, and fix!! I did what you said and it worked! The funny thing is that it was my first flash, is there something i did or should avoid to have this happen to me again? Any way I am so grateful and now am going to try out team venoms viper4g 2.0.2 new rom!
If others have the same problem and want more detailed info about what I did:
1. downloaded sdk manager developer.android.com/sdk/index. html opened the program and installed platform tools
2. Since I have twrp I put into recovery and mounted usb found the zip of the rom i wanted to flash opened it found the boot.img and copied it to the folder where platform tools where installed (C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools)
3. got back to hboot screen
4. opened cmd to the folder by typing: cd then file path like mine above
5. then in cmd typed fastboot flash boot boot.img it will do its thing
6. restart phone and hopefully work for you too!
Click to expand...
Click to collapse
If you are s-on, the kernel won't flash with the rom so you have to flash it separately like om4 showed you. Some roms, like MeanRom have modified their install script to automatically load the kernel to avoid this extra step.
The latest Mean installer failed for me, as did the latest Viper, something to keep in mind if you try those and they don't boot
I would like to download CM9 for my HTC Rezound S-ON. I have read through the Mega thread dedicated to it ( [ROMs][10/1/2012] CyanogenMod 9 [MEGATHREAD][CDMA] ) and have downloaded the CM9 zip and GAPPS zip but when I go to download the S-ON boot.img it says that it has either been removed or moved. I read through the entire thread and there was one update done but that download also has been removed. Without this download I cannot get CM9.
Could someone please let me know if I am misunderstanding this thread or provide me with the proper place to download it from. I am new to XDA however, my phone is rooted and flashed recovery Arom RA and I previously had an HTC Incredible rooted, flashed and had CM7.2.
Any help would be greatly appreciated.I can tell by the threads and posts the time and work that the developers take when creating these different ROMS.
Thank you
owensmomie said:
I would like to download CM9 for my HTC Rezound S-ON. I have read through the Mega thread dedicated to it ( [ROMs][10/1/2012] CyanogenMod 9 [MEGATHREAD][CDMA] ) and have downloaded the CM9 zip and GAPPS zip but when I go to download the S-ON boot.img it says that it has either been removed or moved. I read through the entire thread and there was one update done but that download also has been removed. Without this download I cannot get CM9.
Could someone please let me know if I am misunderstanding this thread or provide me with the proper place to download it from. I am new to XDA however, my phone is rooted and flashed recovery Arom RA and I previously had an HTC Incredible rooted, flashed and had CM7.2.
Any help would be greatly appreciated.I can tell by the threads and posts the time and work that the developers take when creating these different ROMS.
Thank you
Click to expand...
Click to collapse
Take the boot.img that is inside the cm9 .zip you downloaded and flash it in HBOOT with fastboot
Like Fly wrote, extract the boot.img from the cm9.zip, then zip the boot.img and name it PH98IMG. Place the PH98IMG.zip file on your SD card. Flash the ROM, then go into the bootloader and run fastboot.
Or, download CounterShrike, that's the only ROM that worked for me and S-on. You still have to go into the bootloader, but this ROM's installer places the file for you.
platinumthomas said:
Like Fly wrote, extract the boot.img from the cm9.zip, then zip the boot.img and name it PH98IMG. Place the PH98IMG.zip file on your SD card. Flash the ROM, then go into the bootloader and run fastboot.
Or, download CounterShrike, that's the only ROM that worked for me and S-on. You still have to go into the bootloader, but this ROM's installer places the file for you.
Click to expand...
Click to collapse
Thank you both very much for your quick responses. I thought that the file may be in the CM9 zip, but my husband said no and since he is the resident "tech genius" I listened to him. I cannot wait to flash this to my phone CM is my favorite ROM and I have missed it on my new rezound.
Again thank you for your help.
platinumthomas said:
Like Fly wrote, extract the boot.img from the cm9.zip, then zip the boot.img and name it PH98IMG. Place the PH98IMG.zip file on your SD card. Flash the ROM, then go into the bootloader and run fastboot
Click to expand...
Click to collapse
This will not work. You'll also need a proper Android.info file in the PH98IMG.
Could I take the .img file and flash it using adb on the computer?
jcd173339 said:
Could I take the .img file and flash it using adb on the computer?
Click to expand...
Click to collapse
No, but close. Boot into bootloader, go to fastboot, and run "fastboot flash boot boot.img"
Sent from my ADR6425LVW using Tapatalk 2
edit.... so I somehow miraculously now have it working again.... installed amon-ra recovery, then unsuccessfully flashed Neo, but was able to get Ecliptic Rez to work... can't seem to delete this thread though...
Hi,
So I was running the most recent RUU re-locked, S-on.
I went through the unlock process successfully, then got TWRP on my phone (not even sure how this worked... was using the Rezound all-in-one tool, it didn't seem to work properly the first time, but was able to pull up TWRP through Recover later on) then used TWRP to flash SuperSU and was rooted. Then feeling cocky I went ahead and did a clean wipe (note: I was very dumb and never setup a Restore... I thought, oh everything is going great, I'll just flash real quick, no reason to create a backup.... lesson learned haha) and tried to flash Ecliptic Rez. The first time it didn't work... it almost instantly said it was "installed" but didn't work. I tried to Flash it again, this time it looked good, took a while to install, everything looked great. I rebooted and the EclipticRez splash screen came up.... but then it stayed up, and it's still up. I can go back to recovery/hboot/whatever.
If it matters I pretty much flashed Ecliptic with all the options as default (except I chose S-on)...
I also tried just now to flash NeoMax2.0 but this is stuck at the splash screen as well. I tried to flash this rom first by having it as PM98IMG.zip on my root, but it didn't seem to install properly (it went through an initial phase on hboot for about a minute then went back to the hboot screen. So I then flashed it using TWRP, it said it was "injected successfully" (or something like that) but then when I rebooted it went to the splash screen and is stuck there...
If it matters too, my phone is "unlocked" and "tampered" on hboot.
My questions are...
Where should I go from here?
I really don't wanna mess with S-OFF..
I'm trying to learn more about amon-ra recovery but it's gonna take a while for me to digest all that info.
Could it be a TWRP issue in some way?
Any help/ideas would be greatly appreciated, thanks!
For future reference, since you are s-on (as am I) you need to flash the kernel after the ROM.
Some ROMs you have to pull the kernel out and do it in fastboot, or some, like Ecliptic, will put a PH98IMG on your sd card and put you in hboot after the ROM flashes. Then you accept the update if it doesn't start automatically and it will flash the kernel and then you should be able to boot.
You shouldn't need to rename the ROM to PH98IMG, just select flash zip in recovery and navigate to it.
feralicious said:
For future reference, since you are s-on (as am I) you need to flash the kernel after the ROM.
Some ROMs you have to pull the kernel out and do it in fastboot, or some, like Ecliptic, will put a PH98IMG on your sd card and put you in hboot after the ROM flashes. Then you accept the update if it doesn't start automatically and it will flash the kernel and then you should be able to boot.
You shouldn't need to rename the ROM to PH98IMG, just select flash zip in recovery and navigate to it.
Click to expand...
Click to collapse
That's dead on! Thank you. That was the difference I noticed. I'm not sure why, but amon-ra after flashing EclipticRez sent me back to hboot and there I realized that I was supposed to do another step, and at that point I thought, hey this might work this time lol
Out of curiosity.... so you say some ROMs have you "pull the kernel out" - what exactly does that mean? Would I have to download (or perhaps just located the kernel in the SD card) and change that to PH98IMG and put it on SD Root so it loads that update in hboot? Thanks
Since I download everything to my pc then transfer to my phone, what I do is just look in the ROM zip file in explorer and then copy the boot.img out of it into my fastboot folder. Then I just flash it from there using:
fastboot flash boot boot.img
There's probably a way to get it out using Root Explorer or ES File Explorer, but I don't know how you would put it into a PH98IMG file on the phone.
I avoid PH98IMG files whenever possible. Those could be anything packaged up into a file named PH98IMG and I feel safer flashing something using the real name. Would hate to use the wrong PH98IMG file by accident and do something I regret later.
feralicious said:
Since I download everything to my pc then transfer to my phone, what I do is just look in the ROM zip file in explorer and then copy the boot.img out of it into my fastboot folder. Then I just flash it from there using:
fastboot flash boot boot.img
There's probably a way to get it out using Root Explorer or ES File Explorer, but I don't know how you would put it into a PH98IMG file on the phone.
I avoid PH98IMG files whenever possible. Those could be anything packaged up into a file named PH98IMG and I feel safer flashing something using the real name. Would hate to use the wrong PH98IMG file by accident and do something I regret later.
Click to expand...
Click to collapse
Ok cool, so you'd flash your ROM first using the command prompt, then after the ROM has finished installing and you're back in hboot you would then flash the boot.img (aka Kernel right?)?
Flash the ROM in recovery - on the phone, not fastboot. I just download to my pc and store everything there then copy what I need to my phone when I want. So when I flash a ROM I copy it to my sd card to use in my phone.
Then you may or may not have to flash the kernel in fastboot. Only need to use fastboot if the ROM doesn't make a PH98IMG file for you and put it on your sd card. If it does make one I believe it will put you in bootloader and ask you if you want to update and you just select yes with no need to use pc.