Edit: PULLED
Some other stuff is WIP and this is just gonna add to the confusion having these zips in user's hands. There are a couple possibilities of future tools that are superior to this. This was also more of a POC more than anything.
Video Demo:
http://www.youtube.com/watch?v=XXcl_QgQEDU
THIS IS NOT S-OFF. IT NEVER WILL BE AND THIS DOESN'T CLAIM TO GIVE YOU S-OFF. IT JUST ALLOWS FOR ROMS TO BE INSTALLED AS IF WE HAD S-OFF WITH ONE EXTRA STEP.
IF YOU ARE ONLY A USER THERE REALLY ISN'T MUCH YOU CAN DO THIS THIS RIGHT NOW. GO AHEAD AND READ THE THREAD, ASK QUESTIONS, ETC, BUT DON'T FLASH ANYTHING UNLESS YOU UNDERSTAND WHAT IS GOING TO HAPPEN.
Background:
htcdev.com unlock allows us to modify /system from recovery. However, /recovery, /system, and /boot are writable when the system is booted into the OS. This is because htcdev.com unlock allows things booted from the boot partition to flash this stuff. So?
Why is this useful? We can flash recovery to /boot. This will cause the phone to boot into recovery, but since it is loaded from the boot partition, we have write access to /boot, /system, and /recovery. If recovery, such as amonra, is booted from /boot, we can flash boot images like we could in the past with other phones as if the device was S-OFF. When the new boot image is installed, it overwrites the recovery that was installed to /boot and the device will operate normally again.
How this works:
User flashes a PH98IMG.zip in hboot. This will flash amonra to /boot. When the user is asked to press power to reboot, the device will reboot into recovery with full permissions as if the device was S-OFF. Then, whatever rom they flash will be able to flash the boot image the rom needs within recovery.
Why is this better than just flashing the boot image with a PH98IMG.zip?
ROM Devs don't need to worry about mainver issues anymore. The only mainver issue will be the initial PH98IMG.zip that needs to be flashed. But, this PH98IMG.zip will be the same for every rom distributed no matter what, the user can just download the one they need for their mainver and use that one forever. No longer will you need to manually alter android-info.txt for every rom you flash. Plus, the PH98IMG.zip can just be left on the memory card forever because it will just take you to recovery if you flash it. So you can just leave it on your card and forget it. When you want to flash a rom, boot to hboot and the PH98IMG.zip will get loaded up, taking you to a full permission-ed recovery.
How to implement this:
Drop PH98IMG.zip on your SD card that is assigned to your mainver. This is the last time the mainver needs to be worried about until a new OTA comes out. When this is flashed, it will take you to the unprotected recovery so you can flash a new rom. Need to flash a new rom? Just run the PH98IMG.zip again and it will take you to unprotected recovery.
Devs, just add a boot image flashing line to your updater-scripts. No need to pack in PH98IMG.zips and the scripts that deal with them anymore.. The Rezound can now take "normal" roms despite S-ON.
Current Drawbacks
1. zImage Kernels still can't be flashed with this? Why? When they dump the boot image, they will actually be dumping the recovery image that the device is currently booted into. I am still thinking of a workaround for this. I have a few ideas, but I would like to do some testing to see what is the most simplistic for both kernel devs and the end user
2. If you use this to boot into recovery but don't flash a boot image your device will be stuck booting into recovery until a boot image is flashed. Still working on a workaround for this. It will likely be similar to the zImage workaround.
*Even with the drawbacks, this will work well for full roms.*
Attachments: PH98IMG.zips that will fire up recovery. Named [Mainver]PH98IMG.zip.
So the user just flashes the PH98IMG.zip, that will boot them into recovery, which then your rom+boot image can be flashed without worrying about Mainver. The dev can then make S-OFF like roms for the Rezound.
This thread: http://www.xda-developers.com/android/liberate-your-unlocked-sensation-or-evo-3d-with-dumlock/ got me thinking about this. Unfortunately we don't have TWRP, so we can't use their implementation. But this is almost as good
Great job on figuring this out Con.
Sent from my Xoom using xda premium
You saw the article on rootzwiki too? nice
con247 said:
Video Demo:
http://www.youtube.com/watch?v=XXcl_QgQEDU
*Currently adding annotations so the video makes sense lol*
Background:
htcdev.com unlock allows us to modify /system from recovery. However, /recovery, /system, and /boot are writable when the system is booted into the OS. This is because htcdev.com unlock allows things booted from the boot partition to flash this stuff. So?
Why is this useful? We can flash recovery to /boot. This will cause the phone to boot into recovery, but since it is loaded from the boot partition, we have write access to /boot, /system, and /recovery. If recovery, such as amonra, is booted from /boot, we can flash boot images like we could in the past with other phones as if the device was S-OFF. When the new boot image is installed, it overwrites the recovery that was installed to /boot and the device will operate normally again.
How this works:
User flashes a PH98IMG.zip in hboot. This will flash amonra to /boot. When the user is asked to press power to reboot, the device will reboot into recovery with full permissions as if the device was S-OFF. Then, whatever rom they flash will be able to flash the boot image the rom needs within recovery.
Why is this better than just flashing the boot image with a PH98IMG.zip?
ROM Devs don't need to worry about mainver issues anymore. The only mainver issue will be the initial PH98IMG.zip that needs to be flashed. But, this PH98IMG.zip will be the same for every rom distributed no matter what, the user can just download the one they need for their mainver and use that one forever. No longer will you need to manually alter android-info.txt for every rom you flash. Plus, the PH98IMG.zip can just be left on the memory card forever because it will just take you to recovery if you flash it. So you can just leave it on your card and forget it. When you want to flash a rom, boot to hboot and the PH98IMG.zip will get loaded up, taking you to a full permission-ed recovery.
How to implement this:
Drop PH98IMG.zip on your SD card that is assigned to your mainver. This is the last time the mainver needs to be worried about until a new OTA comes out. When this is flashed, it will take you to the unprotected recovery so you can flash a new rom. Need to flash a new rom? Just run the PH98IMG.zip again and it will take you to unprotected recovery.
Devs, just add a boot image flashing line to your updater-scripts. No need to pack in PH98IMG.zips and the scripts that deal with them anymore.. The Rezound can now take "normal" roms despite S-ON.
Current Drawbacks
1. zImage Kernels still can't be flashed with this? Why? When they dump the boot image, they will actually be dumping the recovery image that the device is currently booted into. I am still thinking of a workaround for this. I have a few ideas, but I would like to do some testing to see what is the most simplistic for both kernel devs and the end user
2. If you use this to boot into recovery but don't flash a boot image your device will be stuck booting into recovery until a boot image is flashed. Still working on a workaround for this. It will likely be similar to the zImage workaround.
*Even with the drawbacks, this will work well for full roms.*
Attachments: PH98IMG.zips that will fire up recovery. Named [Mainver]PH98IMG.zip.
So the user just flashes the PH98IMG.zip, that will boot them into recovery, which then your rom+boot image can be flashed without worrying about Mainver. The dev can then make S-OFF like roms for the Rezound.
Click to expand...
Click to collapse
Hmm, nice work Con ! so we just have to wait for Devs to adapt building the rom images to include the kernels again now correct ? I was thinking maybe this will help with flashing the new anthrax kernel that I am having a hard time getting to take.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
con247 said:
Video Demo:
http://www.youtube.com/watch?v=XXcl_QgQEDU
*Currently adding annotations so the video makes sense lol*
Background:
htcdev.com unlock allows us to modify /system from recovery. However, /recovery, /system, and /boot are writable when the system is booted into the OS. This is because htcdev.com unlock allows things booted from the boot partition to flash this stuff. So?
Why is this useful? We can flash recovery to /boot. This will cause the phone to boot into recovery, but since it is loaded from the boot partition, we have write access to /boot, /system, and /recovery. If recovery, such as amonra, is booted from /boot, we can flash boot images like we could in the past with other phones as if the device was S-OFF. When the new boot image is installed, it overwrites the recovery that was installed to /boot and the device will operate normally again.
How this works:
User flashes a PH98IMG.zip in hboot. This will flash amonra to /boot. When the user is asked to press power to reboot, the device will reboot into recovery with full permissions as if the device was S-OFF. Then, whatever rom they flash will be able to flash the boot image the rom needs within recovery.
Why is this better than just flashing the boot image with a PH98IMG.zip?
ROM Devs don't need to worry about mainver issues anymore. The only mainver issue will be the initial PH98IMG.zip that needs to be flashed. But, this PH98IMG.zip will be the same for every rom distributed no matter what, the user can just download the one they need for their mainver and use that one forever. No longer will you need to manually alter android-info.txt for every rom you flash. Plus, the PH98IMG.zip can just be left on the memory card forever because it will just take you to recovery if you flash it. So you can just leave it on your card and forget it. When you want to flash a rom, boot to hboot and the PH98IMG.zip will get loaded up, taking you to a full permission-ed recovery.
How to implement this:
Drop PH98IMG.zip on your SD card that is assigned to your mainver. This is the last time the mainver needs to be worried about until a new OTA comes out. When this is flashed, it will take you to the unprotected recovery so you can flash a new rom. Need to flash a new rom? Just run the PH98IMG.zip again and it will take you to unprotected recovery.
Devs, just add a boot image flashing line to your updater-scripts. No need to pack in PH98IMG.zips and the scripts that deal with them anymore.. The Rezound can now take "normal" roms despite S-ON.
Current Drawbacks
1. zImage Kernels still can't be flashed with this? Why? When they dump the boot image, they will actually be dumping the recovery image that the device is currently booted into. I am still thinking of a workaround for this. I have a few ideas, but I would like to do some testing to see what is the most simplistic for both kernel devs and the end user
2. If you use this to boot into recovery but don't flash a boot image your device will be stuck booting into recovery until a boot image is flashed. Still working on a workaround for this. It will likely be similar to the zImage workaround.
*Even with the drawbacks, this will work well for full roms.*
Attachments: PH98IMG.zips that will fire up recovery. Named [Mainver]PH98IMG.zip.
So the user just flashes the PH98IMG.zip, that will boot them into recovery, which then your rom+boot image can be flashed without worrying about Mainver. The dev can then make S-OFF like roms for the Rezound.
Click to expand...
Click to collapse
Hmm, nice work Con ! so we just have to wait for Devs to adapt building the rom images to include the kernels again now correct ? I was thinking maybe this will help with flashing the new anthrax kernel that I am having a hard time getting to take. When would you wipe then ? after running the Ph98img.zip or after it reboots you to unprotected recovery ?
Thanks Con. But we all know this is going to be asked so ill be the dummy to ask (here we go) So will this work with any recovery, even clockwork touch!!!!!
And this is why ALL devs dont get enough thanks!!!! That mainver issue can be a real pia if a person doesn't know how to fix, or how to do the work arounds.. Took me a few times, but now its become habit..lol Con, keep up the great work, we all appreciate it very much!
So this is really good, right? lol
Very excited to see how this develops!!!
i hope all the dev's adopt this to their roms
So would this effect the flashing of custom kernals as well?
Sent from my ADR6425LVW using XDA App
Njenson said:
So would this effect the flashing of custom kernals as well?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Read the thread
Sent from my ADR6425LVW using XDA App
Nice. Cant wait for a true complete rom. Hope you figure a way around the kernel issue. Complete roms will be a dream come true.
Sent from my ADR6425LVW using xda premium
con247 said:
Read the thread
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Sorry... I didn't really connect the dots on the whole zimage thing. I understand now
Sent from my ADR6425LVW using XDA App
evilstewie23 said:
Thanks Con. But we all know this is going to be asked so ill be the dummy to ask (here we go) So will this work with any recovery, even clockwork touch!!!!!
Click to expand...
Click to collapse
Yes. For example, if you have an image for CWM touch called recovery.img, rename it to boot.img and swap it out with the boot.img in the PH98IMG.zip files.
Noob proof now
Sent from my ADR6425LVW using XDA App
localceleb said:
Noob proof now
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Almost... ideally we would get DumLock support that would supplement this for kernel installations. Then it would be almost 100% noob proof for both roms and kernels, but I am sure someone would find a way to screw it up.
con247 said:
Almost... ideally we would get DumLock support that would supplement this for kernel installations.
Click to expand...
Click to collapse
Con, no homo or anything, but I kind of have a nerd-man-crush on you Well, your work, at least. lol I'm glad you have the Rez It's gonna be a tough choice to choose a phone next because I'm hoping you, Scott, Joel, Newt/Chingy, and everyone else will be on the phone I choose
WasabiWa83 said:
Con, no homo or anything, but I kind of have a nerd-man-crush on you Well, your work, at least. lol I'm glad you have the Rez It's gonna be a tough choice to choose a phone next because I'm hoping you, Scott, Joel, Newt/Chingy, and everyone else will be on the phone I choose
Click to expand...
Click to collapse
Lol. I just try to make things easier. If I can get the DumLock dev to support us partially, I can supplement our lack of TWRP recovery with a touchscreen Aroma installer zip
con247 said:
Lol. I just try to make things easier. If I can get the DumLock dev to support us partially, I can supplement our lack of TWRP recovery with a touchscreen Aroma installer zip
Click to expand...
Click to collapse
Siiiiiiick. Well, it's much appreciated. And you're still in college. I couldn't do what you do in college. Hell, I can't do it now lol. What are you studying?
WasabiWa83 said:
Siiiiiiick. Well, it's much appreciated. And you're still in college. I couldn't do what you do in college. Hell, I can't do it now lol. What are you studying?
Click to expand...
Click to collapse
Mechanical Engineering. This stuff is just a hobby.
con247 said:
Mechanical Engineering. This stuff is just a hobby.
Click to expand...
Click to collapse
Sweet. That should give you a nice paycheck when you get done. Well, for my sake and the sake of all of the other Rezound users, I'm glad you've chosen this as your hobby
Related
So we all know there's going to be people who won't go for s-off due to the nature of the exploit
So I was thinking, since developers are going to eventually migrate to flashing kernels in recovery that wouldn't it be possible for someone to make a script that tells if your s-off or s-on by a txt file placed on the root of your sdcard by the user and then either flashes the kernel in recovery if your s-off or pushes the hboot file to the root of your sdcard?
Sent from my ADR6425LVW using Tapatalk 2
That's a good question man.
My thinking is that since S-On people cannot flash a boot.img in recovery, why can't devs just package the rom/kernel together for everyone to flash? The S-Off people will be able to flash one package for the full rom and since the boot won;t be flashed for S-On users, just provide the boot.img or PH98IMG.zip to flash in bootloader.
The only thing is I don't much of the intricate details on if this would work properly and if S-On users would get an error/have issues if a rom attempted to flash the boot.img.
Marcismo55 said:
That's a good question man.
My thinking is that since S-On people cannot flash a boot.img in recovery, why can't devs just package the rom/kernel together for everyone to flash? The S-Off people will be able to flash one package for the full rom and since the boot won;t be flashed for S-On users, just provide the boot.img or PH98IMG.zip to flash in bootloader.
The only thing is I don't much of the intricate details on if this would work properly and if S-On users would get an error/have issues if a room attempted to flash the boot.img.
Click to expand...
Click to collapse
I don't know the syntax of the updater script but it shouldn't be to hard, maybe a file that says .soff
Then again a separate kernel would fix that as well
Sent from my ADR6425LVW using Tapatalk 2
Flashing the "old" way with s-off shouldn't make a difference though right? So really why change it.
loki993 said:
Flashing the "old" way with s-off shouldn't make a difference though right? So really why change it.
Click to expand...
Click to collapse
My thought was not to kick the s-on people to the curb and tell them either s-off or learn how to flash via a computer
I agree they should posses that knowledge but making it simpler for everyone benefits us in the fact that if it isn't simplified we are going to have a whole bunch of "I flashed this ics Rom and it won't boot" threads
Sent from my ADR6425LVW using Tapatalk 2
Right I understand. I just flashed my first ROM though. It flashed, loaded the PH98IMG on its own rebooted into fastboot and I just had to vol up to flash it. That will work if your s-off or s-on. So I say just write them all like that
Unless Im missing something.
loki993 said:
Right I understand. I just flashed my first ROM though. It flashed, loaded the PH98IMG on its own rebooted into fastboot and I just had to vol up to flash it. That will work if your s-off or s-on. So I say just write them all like that
Unless Im missing something.
Click to expand...
Click to collapse
Very many people including me don't want to bother with hboot zips for a kernel when it can be a one shot flash in recovery if your s-off
If someone has the knowledge could they shoot me a pm on if this is possible? I have an idea but I can't apply it
Sent from my ADR6425LVW using Tapatalk 2
loki993 said:
Right I understand. I just flashed my first ROM though. It flashed, loaded the PH98IMG on its own rebooted into fastboot and I just had to vol up to flash it. That will work if your s-off or s-on. So I say just write them all like that
Unless Im missing something.
Click to expand...
Click to collapse
What superchillpill is saying that if repackaged for s off, it wouldn't goto bootloader at all. Takes out that step altogether. If your point happened to go over my head, my apologies lol
Sent from my ADR6425LVW using Tapatalk 2
What I wil l try and do is provide PH98IMG flashable zips that can flash via HBoot. Let the ROM flash the kernel, its the way its been on other phones and I don't see any reason to change it. Consistency is key no need to learn something new. The kernel guys could just change their scripts and hopefully package boot.img's which are easy to replace in the ROM .zip (along with the WiFi module). It would be great to see init.d supported so we could add some speed tweaks using scripts.
Just have to provide a PH98IMG of the kernel for the ROM is all. Take an extra download for S-On. You can boot into the bootloader by using the recovery option reboot into bootloader in the developer menu.
It's also more convient when you don't have to remove the ph98img off the root of your sd everytime you flash a Rom!
HTC REZOUND
-DISCLAIMER: DO THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE THIS GUIDE CAUSES YOU TO DO. THIS WORKED FOR ME, BUT RESULTS MAY VARY.-
-PLEASE READ THE ENTIRE GUIDE BEFORE FOLLOWING ANY STEPS TO AVOID ANY CONFUSION-
-THIS GUIDE ONLY APPLIES IF YOU ARE ROOTED WITH S-OFF ON HBOOT 1.58-
-IF YOU HAVE INSTALLED THE ICS OTA UPDATE THEN YOU SHOULD HAVE HBOOT 1.58, UNLESS YOU HAVE DOWNGRADED.-
-IF YOU HAVE DOWNGRADED YOUR BOOTLOADER AND ARE NOT ON HBOOT 1.58, LEAVE THIS PAGE-
-I ALSO RECOMMEND THAT YOU HAVE TWO SEPARATE SD CARDS YOU CAN USE FOR THIS. NO DATA WILL BE DELETED OFF OF EITHER-
-KEEP IN MIND, THAT IF YOU DO THIS, YOU MAY NOT BE ABLE TO BOOT BACK INTO YOUR STOCK ICS ROM FROM THE OTA UPDATE-
-YOU WILL ALSO NEED A MICRO SD CARD READER TO PLUG YOUR SD CARD STRAIGHT INTO YOUR COMPUTER-
If you are not rooted, and do not have S-OFF, check out this guide by crimsy. It has all the instructions you need to root and obtain S-OFF. It worked for me.
Now for the fun part. You're positive you're on HBoot 1.58, and you're getting bootloops when you flash roms. The fix is actually quite simple.
First, go to this thread by mpgrimm2
Scroll down until you see a post on the thread by ramjet73. This post contains a list of HBoot downloads. These are all free.
First, find the one that says "PG86IMG_JBear_1.58.5858_hboot_Sprint_ICS.zip". Download that to use as a backup.
Now, we're gonna go by exactly what I did. But I recommend you do your own research on which Hboot is the best for whatever ROM you're trying to flash.
First off, all of these are already S-OFF, so you wont need to redo the wire trick.
Anyway, I downloaded the first one on the list, "PG86IMG_1.40-hboot.zip".
Now, to install this, you're pretty much gonna trick your phone into "updating" to it.
To do this, just download the HBoot you've chosen to be the best for you (in my case it was the first one on the list, 1.4).
Now just rename that file to "PG86IMG" without quotation marks.
Next, copy it to the root of your SD card.
The rest takes place on your phone. Power off your phone, and boot into the bootloader (Hold volume down + power button).
If you've done the previous steps correctly, your bootloader should detect the HBoot you downloaded, and ask if you want to update.
Volume up= Yes
Volume down = No
If you're positive about this, then choose "Yes".
It should update and tell you to reboot.
This is where I ran into a problem. I was still running stock ICS from the OTA update, and I got stuck in a bootloop. My phone would freeze at the the Sprint animation, turn off, and repeat. I thought I could just disregard it, boot into recovery, and flash my new ROM. But every time I booted into the bootloader all I could do was either update or reboot. This is where that micro SD card reader comes in. Just pop your SD card into your computer, and remove the HBoot you downloaded. Then put your SD card back in your phone and try rebooting into the bootloader again.
If it boots into your bootloader as normal, then that should be it. You should be on whatever HBoot version you chose to download (this worked for me with 1.4)
Now try flashing that ROM again and let me know how it goes.
Keep in mind, different ROMS may have different results. You may still need to flash certain kernals or wipe specific partitions as instructed by the developer of the ROM you want to flash.
Feedback is appreciated.
I prefer to put the PG86IMG file on my sd card while booted up normally. Then reboot straight into recovery bypassing the hboot screen. Wipe, flash rom then boot into bootloader and run the update. This prevents getting bootloops and keeps you from having to use the computer to rename or remove the file. Saves you some work!
Sent from my PG86100 using Tapatalk 2
If you are S-OFF you can also flash a different bootloader from fastboot on a PC avoiding the need to deal with the PG86IMG.zip file at all, then boot directly into recovery from the new bootloader. See my post here for alternative methods to flash a new bootloader when S-OFF, including multiple ways to delete the the PG86IMG.zip file when flashing one from the current bootloader.
ramjet73
Theres also
fastboot oem rebootRUU
fastboot flash zip PG86IMG.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
enter recovery & clear cache then reboot.
I believe this is the fastest way to flash a different hboot
iTzLOLtrain said:
I believe this is the fastest way to flash a different hboot
Click to expand...
Click to collapse
If you look at the guide I linked in my previous post which has similar instructions that I took from the unlimited.io website and tested, you can do this fastboot sequence to clear cache, flash a different bootloader, then reboot back to your current ROM:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip new_hboot.zip
fastboot reboot
Click to expand...
Click to collapse
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
If you need to flash another ROM before the reboot or do something else in recovery, you can issue the "fastboot boot recovery.img" command instead of "fastboot reboot" to go directly to your custom recovery since there is no "fastboot reboot-recovery" command.
ramjet73
ramjet73 said:
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
Click to expand...
Click to collapse
I know.. & because this thread is about bootloaders I thought that's how I would explain myself. Instead of going into more detail & say how you can flash .img files through that process....
iTzLOLtrain said:
I know.. & because this thread is about bootloaders I thought that's how I would explain myself. Instead of going into more detail & say how you can flash .img files through that process....
Click to expand...
Click to collapse
That's fine.
For clarification, the command I suggested to get back to recovery (fastboot boot recovery.img) is not flashing it, only booting it directly to avoid having to go to the bootloader first to get to recovery.
ramjet73
Guys, I made this guide because it seemed like the most basic and simple way to do it. I speak from experience when I say that the command prompt can be a little intimidating. It can be get pretty nerve wrecking when you dont have a back up phone and you feel like you have lots of room for error and you're terrified you might brick your device. This guide doesn't use any sort of external commands, making it seem a lot less manual. I wasn't trying to show people the fastest way. Just the easiest, less nerve wrecking way.
sawyerbenjamin said:
Guys, I made this guide because it seemed like the most basic and simple way to do it. I speak from experience when I say that the command prompt can be a little intimidating. It can be get pretty nerve wrecking when you dont have a back up phone and you feel like you have lots of room for error and you're terrified you might brick your device. This guide doesn't use any sort of external commands, making it seem a lot less manual. I wasn't trying to show people the fastest way. Just the easiest, less nerve wrecking way.
Click to expand...
Click to collapse
The guide I linked in post #3 of this thread provides alternatives for flashing a different bootloader and for deleting the PG86IMG.zip file if you choose that method. Some people are very comfortable with the fastboot commands and that method saves having to worry about deleting the PG86IMG.zip. It's always good to have alternatives because one size never fits all.
You asked for feedback in the OP and we're providing that.
ramjet73
ramjet73 said:
The guide I linked in post #3 of this thread provides alternatives for flashing a different bootloader and for deleting the PG86IMG.zip file if you choose that method. Some people are very comfortable with the fastboot commands and that method saves having to worry about deleting the PG86IMG.zip. It's always good to have alternatives because one size never fits all.
You asked for feedback in the OP and we're providing that.
ramjet73
Click to expand...
Click to collapse
Feedback - Information about reactions to a product, a person's performance of a task, etc., used as a basis for improvement.
You were promoting your own threads, not giving feedback. I have to thank you for the post that helped in making this guide, but your alternate methods aren't really necessary. I'm not sure how to say that without sounding rude or hostile, but Im sure you get my point.
sawyerbenjamin said:
You were promoting your own threads, not giving feedback. I have to thank you for the post that helped in making this guide, but your alternate methods aren't really necessary. I'm not sure how to say that without sounding rude or hostile, but Im sure you get my point.
Click to expand...
Click to collapse
OK, and if you want to be blunt my point was that your guide wasn't really necessary, and I think that's feedback on your "product", since the content was already covered in the guide I setup for people that want to change bootloaders when S-OFF, but if people prefer to use your version in the OP of this thread that's fine with me.
As I already stated, alternatives are good.
ramjet73
ramjet73 said:
OK, and if you want to be blunt my point was that your guide wasn't really necessary, and I think that's feedback on your "product", since the content was already covered in the guide I setup for people that want to change bootloaders when S-OFF, but if people prefer to use your version in the OP of this thread that's fine with me.
As I already stated, alternatives are good.
ramjet73
Click to expand...
Click to collapse
Ouch. That was uncalled for. To far bro. This is just a guide trying to help people. Not a place to get all ugly. Lol.
Dear sir
i have the same problem my phone get stuck on white htc screen
unrooted
s-on
relocked
hboot 1.5.0007
so can any one help me how to solve this problem
thanks
i also tried factory reset and to setup ICS ruu but it got stop when it try to reboot boat-loader and still the same problem
when trying to flash any thing recovery or boot failed and trying to put rom as pg86img also failed any one help me please this phone part of my daily life:crying::crying::crying:
The problem with s-on is that the kernel does not flash when you flash a rom. That is why it won't boot.
To fix the issue after flashing a rom, you need to pull the boot.img from the rom.zip and use fastboot to flash it.
fastboot flash boot boot.img
There are two options when you are s-on and flashing roms to flash the kernel with the rom and avoid bootloop.
The no pc method:
The easiest method is to use 4ext recovery with smart flash enabled. That will allow you to flash roms and kernel and avoid bootloop.
The PC method:
Keep a recovery.img in your fastboot directory. When you want to flash a rom, boot your recovery into the phones memory which allows you to flash the kernel with the rom.
You use: fastboot boot recovery.img
Then just install the rom once booted into recovery. While it seems the same, Booting into recovery using fastboot is different and will allow the kernel to flash.
Why does search turn up nothing for this?
I thought with S-Off and Root and 4ext, all my problems would be solved; sadly no! I can't flash kernels because the write_raw_image assert fails.
Why is this, and what can I do to get around it permanently, besides buying Flash Image Gui? Perhaps extract something from a kernel and flash that to fastboot boot boot.img?
For others that run into this problem, I have Virgin Mobile Evo V 4G.
Is this with every ROM you try to flash or just certain ones?
coal686 said:
Is this with every ROM you try to flash or just certain ones?
Click to expand...
Click to collapse
Hadn't gotten to ROMs yet was just trying to get a non-stock kernel.
Every kernel I tried, didn't work.
This was confusing.
https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui&hl=en
I bought Flash Image GUI, $1.* Only have to use it once, from then on you can flash kernels to your hearts content. Something was preventing 4ext recovery from writing to /boot. Thought S-Off removed all that. Whatever. Flash Image GUI opened up my current boot.img, ripped the wifi, Wimax modules from it and inserted them into MAC Sense-Kernel 3.1 that I had been trying to install, then used my SuperUser/Root in Android to flash the kernel + modules as a boot.img to my /boot.
Now that /boot is "unsecured", there is nothing (what was doing it in the first place?) blocking me from flashing in recovery going forward.
Phew. These phones getting more confusing and complicated by the day.
*I think you can just use TWRP2 or this: http://teamw.in/project/htcdumlock
rancur3p1c said:
Now that /boot is "unsecured", there is nothing (what was doing it in the first place?) blocking me from flashing in recovery going forward.
Phew. These phones getting more confusing and complicated by the day.
*I think you can just use TWRP2 or this: http://teamw.in/project/htcdumlock
Click to expand...
Click to collapse
You shouldn't need Flash Image GUI, 4EXT SmartFlash or TWRP dumlock if you are S-OFF. Those are all tools designed to help S-ON users that can't update the boot partition in recovery without starting it from fastboot.
Were you able to flash the RUU.exe and the OTA update successfully?
ramjet73
This is my case when flashing a MIUI ROM with a signed boot.img.
Check out this link: HTC EVO 3d Kernel flash issue
Greetings.
copecu said:
This is my case when flashing a MIUI ROM with a signed boot.img.
Check out this link: HTC EVO 3d Kernel flash issue
Greetings.
Click to expand...
Click to collapse
Yes, that's a specific configuration that causes a problem but the OP of this thread is having problems with kernels that everyone else is flashing with no problems. I'm sure the cause in this case is some sort of misunderstanding.
ramjet73
ramjet73 said:
You shouldn't need Flash Image GUI, 4EXT SmartFlash or TWRP dumlock if you are S-OFF. Those are all tools designed to help S-ON users that can't update the boot partition in recovery without starting it from fastboot.
Were you able to flash the RUU.exe and the OTA update successfully?
ramjet73
Click to expand...
Click to collapse
Yes tried a second time like you mentioned completed just fine. Oh well, works now.
ramjet73 said:
Yes, that's a specific configuration that causes a problem but the OP of this thread is having problems with kernels that everyone else is flashing with no problems. I'm sure the cause in this case is some sort of misunderstanding.
ramjet73
Click to expand...
Click to collapse
Beats me. I tried every configuration every kernel couldn't get anything to flash smart mode on or off.
Good Afternoon,
I am trying to get an idea of how the kernels/modules work in regards to S-ON, S-OFF, etc. Basically, Im just trying to understand the concept. I have noticed that a lot of the Kernels in the Custom Development thread say that you need to flash the kernel via fastboot, and then flash the modules via recovery, but others state that if you are S-OFF you can simply flash the .zip?
I suppose here are my questions:
What all does S-ON "protect" or impact?
Why can you simply flash the zip with S-OFF, but have a two-part process with S-ON?
What is the boot process for the DNA? Specifically, there is a boot.img, system image, etc. When someone says "bootloader" are they referring to the boot image, or is that a level lower than the boot image, that gets handed off to the boot image from the boot loader?
Thanks in advance for your answers!
DroidHaxxor said:
Good Afternoon,
I am trying to get an idea of how the kernels/modules work in regards to S-ON, S-OFF, etc. Basically, Im just trying to understand the concept. I have noticed that a lot of the Kernels in the Custom Development thread say that you need to flash the kernel via fastboot, and then flash the modules via recovery, but others state that if you are S-OFF you can simply flash the .zip?
I suppose here are my questions:
What all does S-ON "protect" or impact?
Why can you simply flash the zip with S-OFF, but have a two-part process with S-ON?
What is the boot process for the DNA? Specifically, there is a boot.img, system image, etc. When someone says "bootloader" are they referring to the boot image, or is that a level lower than the boot image, that gets handed off to the boot image from the boot loader?
Thanks in advance for your answers!
Click to expand...
Click to collapse
To the best of my ability... S-on/S-off is a security flag engrained into the system. This influences write protections and your ability to change them. When your S-off(securty flag off) then you have the ability to manipulate write protections as you please on the root directory(like c:\ on windows)... the boot partition exists on this directory... without s-off you only have write capabilities while in recovery or bootloader mode(cept for a few kernels that provide this ability). The bootloader is actually a sub OS level interface that allows for the flashing of firmwares and whatnot. Since you cant write to the boot partition without s-off then you have to acess the bootloader and push the system into fasstboot mode which is a manufacturer method of firmware flashing... with me??? ok so then the modules are the remainder of the kernel and reside in the system partition and therefor can be written in recovery and hence flashed with a .zip package. So when you have s-off this can all be accomplished in one go because you have write permissions on all directories and paritions greatly simplifying the process as well as providing system write capapbility natively (without kernel mod) during system up time. hope that all made sense at work and didnt have time to read back through
edit: heres a good read about android boot order and the meanings/descriptions of each item http://www.kpbird.com/2012/11/in-depth-android-boot-sequence-process.html
Thanks for the info. That makes sense. I appreciate it.
Nice writeup, and the link you provided is educational too :good:
Please help. I have unlocked this phone through HTC Dev. I have flashed a custom recovery. Somewhere through this process, the original installation of the factory rom from VM was deleted. That doesn't bother me because I was never going back to it anyway, but If I had it right now, I wouldn't be here. I have tried to use the RUU exe in fastboot and the RUU zip in recovery from here. Neither will install, exe throws errors and the zip returns [bad]. I have also tried the [ROM] NegaLite-BluRom-JCFunk | 2.95 | Sprint/VM | Sense/Apex/Nova | 03/25/2014. This eventually installed, but will not boot even with installing boot.img separately. I followed all directions to the best of my ability, but by no means am I saying I did correctly, but I am pretty sure I did. So to recap - I have whats in the title, but no rom whatsoever installed that can be accessed. Any takers?
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Click to expand...
Click to collapse
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
oD33z said:
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
D33z
Click to expand...
Click to collapse
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Click to expand...
Click to collapse
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
oD33z said:
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
Click to expand...
Click to collapse
here's the thread
http://forum.xda-developers.com/showthread.php?t=2831444
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I am great with linux, but was under the assumption it needed to be burned to cd and that USB was not an option, please advise if not the case. I have read a ton and I remember reading about Unknownforce, but cant remember if thats the case or not.
Off topic: I learned from you that it has to be locked to go stock, but does it need to be unlocked to flash your rom or locked as well?
Unlocked for custom, locked for stock.
Here is unknownforce ultimate tool,
there was a live cd version made for windows users scared of linux.
I use tiny core linux for this, Ubuntu tries to mount all the partitions and you only have a 5 second window when they are writeable. I have used Ubuntu, at first, but preferred tinycore.
But first you are going to need to get stock.zip to install.
http://forum.xda-developers.com/showthread.php?t=1653777
I would do fastboot boot recovery.img
Then install negalite, so atless you can boot the phone
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
here is 4ext recovery I would use this one first until you get used to things, best recovery for 3d.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
oD33z said:
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
Click to expand...
Click to collapse
did you fastboot boot?
There are several custom recoveries out there.
Here is thread for 4ext
http://forum.xda-developers.com/showthread.php?t=1408936
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
What I meant was, in your opinion, is the 4ext a better recovery than the unofficial TWRP?
During the install of Negalite at the point of -Setting Up Kernel Over-Clock Settings
under this it reads: assert failed: write_raw_image("/tmp/newboot.img","boot")
Is this a red flag of something not going right in any way?
After this I click Next>Recovery>Wipe Dalvik>Reboot and it boots into Fastboot. Whats happening at this point?
Since I am basically starting from scratch and the end goal is to have a kitkat rom and possibly S-OFF(if its a must to do so).
What all needs to be done as far as formatting, tweaks, or anything else to achieve the best performance, space, or anything you can think of?
Thats if you dont mind sharing. I appreciate your time and if I can be of service to you in any way, I will.
I am currently on the 4ext recovery with 1GB sd-ext 0 swap and formatted Ext4.
fastboot boot recovery.img
flashrom.zip from recovery
reboot, wipe dalvik, reboot
Negalite.zip installed with no errors whatsoever.
Thank You.
Beautiful smooth running rom btw.
Does all that above sound like I did the right things as for setting up and installing?
4ext is most stable, the unofficial has new features like f2fs and selinux, but 95% stable.
fastboot boot recovery.img is an old work around, also used to flash boot.img with fastboot. That is ok with roms that include a whole boot.img but roms like mine use a dynamic boot.img. Basically the installer makes the boot.img using your choices.
From what I know about Kitty kat I think you need to downgrade hboot or be s-off. Not sure I've stayed on ics for stability because I still use this phone. Also there is a new version of negalite on svn, just takes hours for me to upload a zip version.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Revision 7
Are you sure this is the latest?
oD33z said:
Revision 7
Are you sure this is the latest?
Click to expand...
Click to collapse
Lol, yes since I updated it a few weeks ago
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
I should have worded that different really, the revision numbers threw me, I honestly was just making sure I was in the right place. 48mb smaller, anything stripped?
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Click to expand...
Click to collapse
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
oD33z said:
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
Click to expand...
Click to collapse
Here. Try this
https://www.androidfilehost.com/?fid=23578570567720169
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer