Allright , my computer gave its last breath this morning im s on is there a way to flash the boot without the pc
Yes, if you have a PH98IMG of the kernel. A lot of ROMs now will make the PH98IMG of the boot.img for you during install though, so all you need to do is accept the "update" after you flash the ROM. Or, some ROMs come with the kernel in a PH98IMG file posted in the OP that you can download. You just put that on your sd card and flash it in hboot.
If the ROM you want to use doesn't have one you can make one by swapping out the boot.img inside a PH98IMG file that is already made. Just make sure the android-info.txt file has the correct mainver listed in it.
I've attached a PH98IMG of an OLD stock boot.img you can use as a template (do not flash this kernel). Delete the boot.img in it and replace it with the one you want to use and edit the android-info.txt file to your mainver since this one is from GB days. If you don't know it and can use the pc to get it put the phone in fastboot and type
fastboot getvar all
(hm... can you do all that on your phone? I'm not sure...)
In case you can't use your pc at all and it helps, I'm currently on the global leak and my mainver is... huh... mine is blank when I use "fastboot getvar all". Hmph.
Or, is there a particular kernel you need to flash now? If you post your mainver I or someone else can make a PH98IMG file of it for you.
Related
I am S-ON. Flashed everything fine through amon ra. flashed gapps. went to hboot. found ph98img file no problem, but did not ask for the volume up acknowledgement. not sure what I'm missing. I only need the boot image correct? any help would be greatly appreciated.
I'm pretty sure Rage doesn't come with a PH98IMG, so that was probably an old file from a previous ROM. You need to extract the boot.img from the ROM zip file and flash it in fastboot from a PC. "fastboot flash boot boot.img"
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.
Hi all! Just done unlocking bootloader, flash Amon Ra recovery and root. Now I want to flash custom rom but i am lost about flashing the boot.img in hboot, i really don't know how to flash it. I am at S-ON.. Any help would be appreciated. Tnx in advace!
you know what I don't know how to do it too. but there are some roms that will do it for you even if you are s-on
There's two possible ways you might have to do it.
1. If the ROM makes a PH98IMG file and puts it on your sd card then it will take you to hboot after it's done flashing and all you have to do is say "yes" to accept the "update". It will flash the kernel and then you can boot up the phone. After it's booted up make sure you delete that PH98IMG file so you can boot up again.
I think that if it's going to do this it will give you the option to select s-off or s-on when flashing the ROM.
2. If it doesn't do the above you will have to pull the kernel from the ROM. Just look in the ROM zip file in explorer on your pc 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
Some ROMs, like EclipticRez, give you the option of a few kernels. You can just pull the one you want and when you flash it change "boot.img" to whatever the name of that kernel is.
feralicious said:
There's two possible ways you might have to do it.
1. If the ROM makes a PH98IMG file and puts it on your sd card then it will take you to hboot after it's done flashing and all you have to do is say "yes" to accept the "update". It will flash the kernel and then you can boot up the phone. After it's booted up make sure you delete that PH98IMG file so you can boot up again.
I think that if it's going to do this it will give you the option to select s-off or s-on when flashing the ROM.
2. If it doesn't do the above you will have to pull the kernel from the ROM. Just look in the ROM zip file in explorer on your pc 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
Some ROMs, like EclipticRez, give you the option of a few kernels. You can just pull the one you want and when you flash it change "boot.img" to whatever the name of that kernel is.
Click to expand...
Click to collapse
Thank you so much for your help! I'm now running custom rom. I even flashed to the latest firmware.
I used to have one but I lost it and I don't know if you have tried but its really hard to find one.
what are you looking to do
most people refer to the RUU. but PH98IMG.zip can be alot of different things
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
if your not looking to get back to stock than don't flash the zip from the link above
bunchies said:
what are you looking to do
most people refer to the RUU. but PH98IMG.zip can be alot of different things
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
if your not looking to get back to stock than don't flash the zip from the link above
Click to expand...
Click to collapse
Well basically I need the txt file in the boot img. my phone is s-on and I always have to flash the ph
are you sure your not getting that confused?
if flashing a rom.
1.Flash ROM zip in recovery
2.Take the boot.img out of the ROM zip you just flashed
3.Reboot to Fastboot and flash the boot.img through ADB with the command: Fastboot flash boot boot.img
i don't see why anyone would need to flash the boot.img from an RUU. and if you did flash a boot.img from an RUU after you installed a ROM than i dont think the ROM would work at all
just clearing that up if you don't know or new to ROMing :good:
Or just "fastboot boot recovery.zip" and flash normally, if you are S-ON and BOOT recovery via fastboot, you can flash the ROM normally and not have to manually flash the boot.img in Fastboot like you do if you flash the ROM from an installed recovery.
bunchies said:
are you sure your not getting that confused?
if flashing a rom.
1.Flash ROM zip in recovery
2.Take the boot.img out of the ROM zip you just flashed
3.Reboot to Fastboot and flash the boot.img through ADB with the command: Fastboot flash boot boot.img
i don't see why anyone would need to flash the boot.img from an RUU. and if you did flash a boot.img from an RUU after you installed a ROM than i dont think the ROM would work at all
just clearing that up if you don't know or new to ROMing :good:
Click to expand...
Click to collapse
As a mac user I tried this. With adb all set up on the mac to use terminal (the whole folder and everything was set up long ago when unlocking). I have to use the command ./fastboot instead of just fastboot with terminal. Anyway, when ./fastboot flash boot boot.img it never works. It seems like it works, but then the phone just goes into the white HTC screen and is stuck there. It never boots.
earlier today I flashed the V5.14.531.9 firmware and went from TWRP running on my 4.4.2 V5.14.531.9, to stock.
This was so I could be stock and flash the OTA.zip and get to 6.10.531.9 that I'm at now.
I've since flashed TWRP again so that I could make a Nandroid of the "stock" ROM, jic.
Where or how can I extract the firmware/stock recovery of 6.10.531.9 so I have it for the next time?
Or would re-flashing the OTA.zip do just that?
Dumb question prolly. But you'll get over it.
metropical said:
earlier today I flashed the V5.14.531.9 firmware and went from TWRP running on my 4.4.2 V5.14.531.9, to stock.
This was so I could be stock and flash the OTA.zip and get to 6.10.531.9 that I'm at now.
I've since flashed TWRP again so that I could make a Nandroid of the "stock" ROM, jic.
Where or how can I extract the firmware/stock recovery of 6.10.531.9 so I have it for the next time?
Or would re-flashing the OTA.zip do just that?
Dumb question prolly. But you'll get over it.
Click to expand...
Click to collapse
You can get the stock recovery from the OTA, just unzip it then unzip firmware.zip the recovery.img can be extracted from the zip. You can also extract the firmware, but just check it closely to see if all of the files are there sometimes OTA firmwares are short some files. I would compare it against an older firmware that has worked for you in the past.
Also, if you are S-OFF to make a completely stock nandroid you would need to downgrade to hboot 1.44 then you can use the fastboot boot recovery.img command. You would rename your custom recovery to recovery.img for this to work. Then you would go into the custom recovery and backup the system, cache, recovery etc. After the successful backup then you would boot in bootloader, change your hboot back to original and flash the custom recovery.
majmoz said:
You can get the stock recovery from the OTA, just unzip it then unzip firmware.zip the recovery.img can be extracted from the zip. You can also extract the firmware, but just check it closely to see if all of the files are there sometimes OTA firmwares are short some files. I would compare it against an older firmware that has worked for you in the past.
Also, if you are S-OFF to make a completely stock nandroid you would need to downgrade to hboot 1.44 then you can use the fastboot boot recovery.img command. You would rename your custom recovery to recovery.img for this to work. Then you would go into the custom recovery and backup the system, cache, recovery etc. After the successful backup then you would boot in bootloader, change your hboot back to original and flash the custom recovery.
Click to expand...
Click to collapse
first off. thanks. I think this may be the most concise and direct answer I've ever received in the 4 or 5 years I've been on XDA, sad to say.
I did as you suggested and unzipped the OTA and the Firmware after. Unzipping the firmware got me a slightly smaller copy of it with a .cpgz extension.
How would one one downgrade to HBOOT 1.44? I'm at 1.57 with this OTA'd ROM.
metropical said:
first off. thanks. I think this may be the most concise and direct answer I've ever received in the 4 or 5 years I've been on XDA, sad to say.
I did as you suggested and unzipped the OTA and the Firmware after. Unzipping the firmware got me a slightly smaller copy of it with a .cpgz extension.
How would one one downgrade to HBOOT 1.44? I'm at 1.57 with this OTA'd ROM.
Click to expand...
Click to collapse
Go to nkk71's SuperGuide in my signature he explains how to do it. Once you download the hboot_1.44.zip I would make a copy of it and name it hboot_1.57.zip. Then I would extract the hboot from the OTA firmware and put it in the hboot_1.57.zip. This way you have an file that you can flash in fastboot. When you download the hboot_1.44.zip check the android_info.txt file to ensure your MID & CID are present. I believe they are but I would double check to be sure.
hboot
majmoz said:
Go to nkk71's SuperGuide in my signature he explains how to do it. Once you download the hboot_1.44.zip I would make a copy of it and name it hboot_1.57.zip. Then I would extract the hboot from the OTA firmware and put it in the hboot_1.57.zip. This way you have an file that you can flash in fastboot. When you download the hboot_1.44.zip check the android_info.txt file to ensure your MID & CID are present. I believe they are but I would double check to be sure.
Click to expand...
Click to collapse
dl'd hboot 1.44. my mid and cid are both there, with * in the last few places.
do you know where in the OTA unzipped the hboot resides and is it named something else?
and about unzipping the firmware.zip in the OTA, any idea on why the .cpgz extension?
another question.
this: RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.9_Radio_4T.28.3218.04_10.33E.1718.01L_release_387953_signed_2.exe
and this :
OTA_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.9-5.14.531.1_R_release_387954jjhcxbzgi6808nml.zip
in theory are the same thing except one is .exe and the other .zip. Since I'm on a Mac, the .exe is useless to me unless I install W7 again.
If the same I'd toss the .exe.
also is stock recovery still available after flashing TWRP by doing it manually from the phone (rather than Terminal) or does the flash of TWRP blow stock out?
Thanks again,
metropical said:
dl'd hboot 1.44. my mid and cid are both there, with * in the last few places.
do you know where in the OTA unzipped the hboot resides and is it named something else?
and about unzipping the firmware.zip in the OTA, any idea on why the .cpgz extension?
another question.
this: RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.9_Radio_4T.28.3218.04_10.33E.1718.01L_release_387953_signed_2.exe
and this :
OTA_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.9-5.14.531.1_R_release_387954jjhcxbzgi6808nml.zip
in theory are the same thing except one is .exe and the other .zip. Since I'm on a Mac, the .exe is useless to me unless I install W7 again.
If the same I'd toss the .exe.
Thanks again,
Click to expand...
Click to collapse
Inside of the OTA is firmware.zip; inside firmware.zip is hboot_signedbyaa.img this is your hboot. I don't know about the .cpgz extension and on the OTA I got when I downloaded it from the phone doesn't have it in firmware.zip. The difference between the RUU and the OTA is the OTA is just an update and may or may not have all of the files necessary to completely rebuild the phone. The RUU has all of the files. Oftentimes, the update will only have those files that the service provider/manufacturer made a change to the original files, while the RUU has all of the files regardless where or not it was updated. Keep the RUU file and if you happen to have a Windows machine around you can make a RUU rom.zip. Here is how:
Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone. Here's the android-info.txt extracted from my RUU exe:
Code:
[B]modelid: PN0713000
cidnum: T-MOB010
mainver: 6.10.531.9
btype:1
aareport:1
hbootpreupdate:3[/B]
You can then verify that you have the correct RUU if the MID matches that of your phone and if you can see your CID in that list. If either (or both) of the MID or CID does not match that of your phone, the RUU process will fail. The mainver is the firmware that is going to be flashed onto your phone. For easy reference, create a new folder and name it exactly like the RUU exe file and put the rom.zip and android-info.txt in there so you won't have trouble identifying that rom.zip file later if you need to flash it again. Now, you can close the RUU installation window and all the files in that temp folder containing rom.zip will be instantly erased. Note that if you open the rom.zip with WinZip/WinRAR, you will see a list of all the files but if you try to extract or double-click to open any of these files, you will get an error saying that the file is corrupt. This warning is only due to the files being encrypted by HTC, since the RUU is an official release and is digitally signed. To access those encrypted files, you will need to decrypt them on Linux.
Click to expand...
Click to collapse
majmoz said:
Inside of the OTA is firmware.zip; inside firmware.zip is hboot_signedbyaa.img this is your hboot. I don't know about the .cpgz extension and on the OTA I got when I downloaded it from the phone doesn't have it in firmware.zip. The difference between the RUU and the OTA is the OTA is just an update and may or may not have all of the files necessary to completely rebuild the phone. The RUU has all of the files. Oftentimes, the update will only have those files that the service provider/manufacturer made a change to the original files, while the RUU has all of the files regardless where or not it was updated. Keep the RUU file and if you happen to have a Windows machine around you can make a RUU rom.zip. Here is how:
Click to expand...
Click to collapse
for some reason unzipping on a Mac seems to give different results than on windows.
I'll keep both and perhaps reinstall the W7 partition on BootCamp again.
Thanks for the clear info , again.