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
Please don't flame me for asking, but i couldn't find instructions anywhere. I know if your s-on and want to flash aosp roms you need to flash the boot img via fast boot. I just cant seem to do it right and end up in the splash screen indefinitely. Any help is appreciated. Thanks in advance.
This thread helped me resolve the same issue.
http://forum.xda-developers.com/showthread.php?t=1937949
Do you flash the rom first and then the fastboot boot.img, or the other way around?
mito8485 said:
Do you flash the rom first and then the fastboot boot.img, or the other way around?
Click to expand...
Click to collapse
I flashed the boot.img after I installed the rom. I'm not sure if that was the correct way, but it worked for me.
A very simple solution is to download Flash Image GUI, and use it to flash the kernel of the Rom while your phone is still booted and functional. You can do this by opening the app and locating the Rom file, then hit yes to install it to the partition. After extracted, boot into recovery, do your wipes, and flash the AOSP rom. This saves the need for a computer.
Another thing to try is to boot into recovery, flash the rom, let it boot to the boot animation, hard reboot into recovery, and reflash. (This works with Sense roms, but I haven't tried it with AOSP roms yet)
P.S.: I am S-On also
When I was s-on I would flash the rom then boot straight to bootloader, fastboot. USB and flash the boot img. This method always worked for me
Sent from my EVO using xda premium
Thanks for the help. I found that flashing the boot.IMG first then the ROM works good for me. But I will try the GUI app
Sent from my EVO using xda premium
The GUI application works as advertised but it's handy to be used to using fastboot also. Never know when your gonna need it
Sent from my EVO using xda premium
corcgaigh said:
The GUI application works as advertised but it's handy to be used to using fastboot also. Never know when your gonna need it
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I'll keep that in mind. I will educate myself about that method.
______________________________
HTC Evo 4G LTE
One question so when flashing a boot.img I pull it from Rom and fastboot flash. My question is when I do recover flash after do I leave boot image in original zipped Rom folder and recovery flash, or is it not supposed to be in it at all, being I already flashed boot.img via fastboot?
jander54111 said:
One question so when flashing a boot.img I pull it from Rom and fastboot flash. My question is when I do recover flash after do I leave boot image in original zipped Rom folder and recovery flash, or is it not supposed to be in it at all, being I already flashed boot.img via fastboot?
Click to expand...
Click to collapse
Just keep it in the zip
So everyone I have done goes through but lockscreen has no touch functions. I can't get past it any suggestions?
Sent from my EVO using xda app-developers app
Are you s-off?
What rom are you using?
Are you doing a clean install?
jander54111 said:
So everyone I have done goes through but lockscreen has no touch functions. I can't get past it any suggestions?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You are probably on the latest firmware and flashed a 3.15 rom, my guess, you need then to flash a 3.16 sense rom, aosp and 3. 15 roms touch screen doesn't work with the newest firmware, if you are s-off you can downgrade it, if you are s-on I suggest you to go to the original development thread and get s-off using baby racoon if your hboot is 2.09... Good luck
Sent from my EVO using xda app-developers app
I am selling one of my Rezounds I need to return it to mostly stock.
Before installing the latest Infection rom I was on the current OTA rom. Basically I think all I need to do is reflash the stock recovery image and the current OTA rom and if needed go back to locked. Problem is, I don't have a copy of the recovery.img from the current OTA rom. Can anybody link me to it. Thanks
Sent from my Infected Rezound
Here is a post with the full OTApkg.zip for 4.05.605.14:
http://forum.xda-developers.com/showpost.php?p=40757466&postcount=19
If you extract the firmware.zip, there is the recovery.img which you can either put into a custom ph98img.zip and run in hboot or flash it from your computer using adb stuff. I recently had to restore my Rez back to stock as it is getting returned to Verizon for a replacement. I used the ph98img route to reinstall recovery after unrooting. I also then had to S-on the phone so I had to make sure it was bone stock so the S-on didn't brick it.
ETA: I'm not sure if that full OTApkg.zip will be enough to get you back to stock but what I had done in the past was to flash this stock rooted rom with Amonra 3.16 http://forum.xda-developers.com/showpost.php?p=40941755&postcount=1 ( I was already on 4.05.605.14), do the full unroot option using the supersu app that was already there, and then flash the stock recovery and I was back to fully stock.
---------- Post added at 12:32 PM ---------- Previous post was at 12:09 PM ----------
Any chance your phone was S-off?
mikeyk101 said:
Here is a post with the full OTApkg.zip for 4.05.605.14:
http://forum.xda-developers.com/showpost.php?p=40757466&postcount=19
If you extract the firmware.zip, there is the recovery.img which you can either put into a custom ph98img.zip and run in hboot or flash it from your computer using adb stuff. I recently had to restore my Rez back to stock as it is getting returned to Verizon for a replacement. I used the ph98img route to reinstall recovery after unrooting. I also then had to S-on the phone so I had to make sure it was bone stock so the S-on didn't brick it.
ETA: I'm not sure if that full OTApkg.zip will be enough to get you back to stock but what I had done in the past was to flash this stock rooted rom with Amonra 3.16 http://forum.xda-developers.com/showpost.php?p=40941755&postcount=1 ( I was already on 4.05.605.14), do the full unroot option using the supersu app that was already there, and then flash the stock recovery and I was back to fully stock.
---------- Post added at 12:32 PM ---------- Previous post was at 12:09 PM ----------
Any chance your phone was S-off?
Click to expand...
Click to collapse
Thanks... I am S-ON but that should really be all I need... I don't really need to go 100% pure stock, but if I can get it close that will work. Replacing the recovery image and leaving it S-ON, then flash the Stock OTA Rooted ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2260154 and I think I will be close enough to sell it. If someone wants it with a custom ROM I can just leave TWRP and Infection, or whatever ROM they want, but I just need a quick option to return to "stock" if the buyer wants.
acejavelin said:
Thanks... I am S-ON but that should really be all I need... I don't really need to go 100% pure stock, but if I can get it close that will work. Replacing the recovery image and leaving it S-ON, then flash the Stock OTA Rooted ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2260154 and I think I will be close enough to sell it. If someone wants it with a custom ROM I can just leave TWRP and Infection, or whatever ROM they want, but I just need a quick option to return to "stock" if the buyer wants.
Click to expand...
Click to collapse
You may want to flash the rooted stock before replacing the recovery back to stock. I don't know if the stock recovery will allow it...
mikeyk101 said:
You may want to flash the rooted stock before replacing the recovery back to stock. I don't know if the stock recovery will allow it...
Click to expand...
Click to collapse
The beauty of being unlocked is it doesn't matter... All I need to do is go into fastboot and use "fastboot boot recovery.img" for TWRP and I can flash anything, irregardless of what the installed recovery allows. But thanks for the warning, this is probably what I would do anyway.
Doh!, I completely forgot about that way... Yup, that would work as well
I'm trying to give this phone to my buddy. Haven't used it since I got the S4, and he is still using a Dinc. I tried what was listed here, but it's only made things worse. I was on Stock 4.03.605 (leaked Global RUU) unlocked, rooted, s-on. I tried updating the firmware with the OTAzip. I made the PH98IMG.zip, and ran it through the bootloader. It only updated Hboot from 2.7 to 2.8. It did NOT give me 4.05.605 like I was looking for. I tried to run the Global Stock rom but got stuck in a white HTC screen. The only thing I can make work right now is a viperrom, but wifi will not turn on. I was hoping to give this to him as close to stock, but without wifi, it's not going to be very useful.
Currently I have it locked s-on with stock recovery, but I can unlock and put amon ra back on it. I use a mac so commands are a bit different for me, but I know the basics and what to on the mac (mostly). Any help would be appreciated. I tried to run the leaked global RUU again to reset it, but because the Hboot updated, it won't run it. I can't find an RUU for 4.05.605
318sugarhill said:
I'm trying to give this phone to my buddy. Haven't used it since I got the S4, and he is still using a Dinc. I tried what was listed here, but it's only made things worse. I was on Stock 4.03.605 (leaked Global RUU) unlocked, rooted, s-on. I tried updating the firmware with the OTAzip. I made the PH98IMG.zip, and ran it through the bootloader. It only updated Hboot from 2.7 to 2.8. It did NOT give me 4.05.605 like I was looking for. I tried to run the Global Stock rom but got stuck in a white HTC screen. The only thing I can make work right now is a viperrom, but wifi will not turn on. I was hoping to give this to him as close to stock, but without wifi, it's not going to be very useful.
Currently I have it locked s-on with stock recovery, but I can unlock and put amon ra back on it. I use a mac so commands are a bit different for me, but I know the basics and what to on the mac (mostly). Any help would be appreciated. I tried to run the leaked global RUU again to reset it, but because the Hboot updated, it won't run it. I can't find an RUU for 4.05.605
Click to expand...
Click to collapse
My circumstance was very specific, this thread was not really intended to be a guide to take any version of software to another, I already had the firmware (HBoot & radios) for 4.5.605.14, just needed a few pieces to get back to "stockish"... There are other ways to return to stock for different software versions and this thread doesn't address any of those.
The OTApkg.zip is only for going from 3.14.605.13 to 4.5.605.14, no other combinations of versions will work properly. I am surprised that HBoot updated... what radios are you on now? If the radios updated then you might be OK, you can just unlock, then fastboot boot recovery.img of TWRP and flash in the stock/rooted 4.5.605.14 ROM (NOT an RUU, but just the ROM), otherwise you could be in a situation where you need to S-OFF and flash radios and tweak from there. If your HBoot updated then the leaked RUU won't work either, you could be in a tight spot.
BTW, the reason Viper won't work is you likely have a kernel mismatch, to install a ROM on an S-ON Rezound you need to flash the boot.img separately, that is where the kernel is, but that also requires you to be unlocked by HTCdev.
acejavelin said:
My circumstance was very specific, this thread was not really intended to be a guide to take any version of software to another, I already had the firmware (HBoot & radios) for 4.5.605.14, just needed a few pieces to get back to "stockish"... There are other ways to return to stock for different software versions and this thread doesn't address any of those.
The OTApkg.zip is only for going from 3.14.605.13 to 4.5.605.14, no other combinations of versions will work properly. I am surprised that HBoot updated... what radios are you on now? If the radios updated then you might be OK, you can just unlock, then fastboot boot recovery.img of TWRP and flash in the stock/rooted 4.5.605.14 ROM (NOT an RUU, but just the ROM), otherwise you could be in a situation where you need to S-OFF and flash radios and tweak from there. If your HBoot updated then the leaked RUU won't work either, you could be in a tight spot.
BTW, the reason Viper won't work is you likely have a kernel mismatch, to install a ROM on an S-ON Rezound you need to flash the boot.img separately, that is where the kernel is, but that also requires you to be unlocked by HTCdev.
Click to expand...
Click to collapse
Damn....I have tried to flash the kernel (boot.img) through the fastboot command, but it never works right and leaves me stuck with a white HTC screen. Again, if it's bricked, it's not the end of the world for me as I upgraded to the S4, but my buddy was looking forward to 4g.
Basebands are 2.23.10.0123r, and 2.23.10.0124r
Well I think you're in luck, you have the firmware for the latest software installed... hboot and radios match for 4.5.605.14, all you need now is to unlock and flash a correct ROM! Working so I can't grab link right now, just get unlocked via HTCdev and post when that's done... all isn't list yet!
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
Well I think you're in luck, you have the firmware for the latest software installed... hboot and radios match for 4.5.605.14, all you need now is to unlock and flash a correct ROM! Working so I can't grab link right now, just get unlocked via HTCdev and post when that's done... all isn't list yet!
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I just unlocked again..I don't need the HTCdev site anymore. The token and all that jazz is all saved to an android folder on the my macHD. I downloaded TRWP. Should I flash that next?
318sugarhill said:
I just unlocked again..I don't need the HTCdev site anymore. The token and all that jazz is all saved to an android folder on the my macHD. I downloaded TRWP. Should I flash that next?
Click to expand...
Click to collapse
If you wish..
Actually installing a custom recovery is not required as long as you can fastboot boot the recovery image.
Did you want to return to mostly stock, or did you want to run a custom ROM like Infection Or something else?
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
If you wish..
Actually installing a custom recovery is not required as long as you can fastboot boot the recovery image.
Did you want to return to mostly stock, or did you want to run a custom ROM like Infection Or something else?
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I was looking for stock. 4.05.605 is ideal so he can play with it if he wishes. I don't want to have to field questions once its his. I don't mind helping him, but I don't want to cause him issues he's not looking for.
I have the image downloaded. How do I fastboot boot the recovery? Just ./fastboot boot recovery.img (as i have renamed the img as recovery.img)
Use this one
http://forum.xda-developers.com/showthread.php?t=2260154
[ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
Flash ROM, extract boot.img and flash then should be goof to go.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
Use this one
http://forum.xda-developers.com/showthread.php?t=2260154
[ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
Flash ROM, extract boot.img and flash then should be goof to go.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I tried this earlier, but I get the white HTC screen lockup. When you say extract boot.img, you mean unzip the download, pull out the boot.img and put it in my android folder to fastboot flash correct? The command I use is ./fastboot flash boot boot.img. It appears everything works, but it never boots. Just gets stuck in the white screen.
I'm downloading it now, should be about 14 more minutes. I will try it all again, and see what happens. Fingers crossed. let me know if my commands are wrong or I'm missing anything. the ./ is needed for mac.
If you load TWRP via Fastboot boot it will flash boot.img for you, if you load if from hboot you have to flash manually.
Before flashing ROM, download and flash the CleanWipe x5 script found in a thread on the development forum.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
If you load TWRP via Fastboot boot it will flash boot.img for you.
Before flashing ROM, download and flash the CleanWipe x5 script found in a thread on the development forum.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I flashed twrp via fastboot flash recovery. I'm missing something. what is fastboot boot for TWRP?
318sugarhill said:
I flashed twrp via fastboot flash recovery. I'm missing something. what is fastboot boot for TWRP?
Click to expand...
Click to collapse
That works, just requires extra steps. I don't flash recovery anymore, you can go into fastboot on the phone, then execute fastboot boot recovery.img from PC, this gives an unlocked HTC phone temporary S-OFF saving steps of flashing boot.img seperately and avoiding the dreaded Tampered flag (if it hasn't been set).
Lots of ways to skin a cat I guess.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
acejavelin said:
That works, just requires extra steps. I don't flash recovery anymore, you can go into fastboot on the phone, then execute fastboot boot recovery.img from PC, this gives an unlocked HTC phone temporary S-OFF saving steps of flashing boot.img seperately and avoiding the dreaded Tampered flag (if it hasn't been set).
Lots of ways to skin a cat I guess.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
I have the tampered flag. But I don't care about that. I'm long past warranty anyway. But when I use the command ./fastboot boot recovery.img it says cannot load "recovery.img"
318sugarhill said:
I have the tampered flag. But I don't care about that. I'm long past warranty anyway. But when I use the command ./fastboot boot recovery.img it says cannot load "recovery.img"
Click to expand...
Click to collapse
You need to extract the recovery.img file from the TWRP zip and put it in the fastboot directory.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app