Yeah...I know S-off makes everything easier...but I'm stuck with S-on. I dropped my phone (while plugged in) on the charging port, jarring it to the point of no longer being able to connect it to my computer for ADB communication. I'm assuming s-off isn't possibly without a working usb connection.
So...I'm wondering how to go about flashing a custom kernel from the bootloader while being s-on and unlocked. I've attempted to pull boot.img from within a custom ROM package, rename to PH98IMG.zip, and put it on the root of my SD...but this apparently doesn't work. What do I have to do to avoid being stuck forever with my current setup (aside from abandoning the phone)?? Any advice would be appreciated!
KaceMN said:
Yeah...I know S-off makes everything easier...but I'm stuck with S-on. I dropped my phone (while plugged in) on the charging port, jarring it to the point of no longer being able to connect it to my computer for ADB communication. I'm assuming s-off isn't possibly without a working usb connection.
So...I'm wondering how to go about flashing a custom kernel from the bootloader while being s-on and unlocked. I've attempted to pull boot.img from within a custom ROM package, rename to PH98IMG.zip, and put it on the root of my SD...but this apparently doesn't work. What do I have to do to avoid being stuck forever with my current setup (aside from abandoning the phone)?? Any advice would be appreciated!
Click to expand...
Click to collapse
some roms use wireless adb i.e. viperrez im not sure as to how youd go about doing this for the particular rom your running but thas is the best knowledge i have of using fastboot commands without your usb.. i think its time for a new phone bud:/
It seems to me like my solution lies in the creation of an appropriate PH98IMG.zip file to place in the root of my SD card and flash within the bootloader. I know that early Rezound ROMS would supply this file along with the main download, catering to s-on ...so it is something that can be done. I'm just wondering about the specifics of creating such a file from a boot.img file.
I'm not going to give up on the phone. I'll be able to charge via an inductive pad, its just a matter of being able to keep up-to-date kernels without ADB via USB.
i am also S-ON, and I would like to be able to just flash the kernel in the bootloader using a PH98IMG placed on the sd card. I am used to just flashing a rom in recovery, then booting to the bootloader and flashing the PH98IMG.
My newest rom, ElipticRez has a boot.img posted for S-ON users. So, i have placed the boot.img in a PH98IMG zip that i have used before, but something always seem to go wrong. Either it wont update in the bootloader, or it does update but my wifi wont work.
Any suggestions on how to get a kernel to work using a PH98IMG for S-ON users?
Flyhalf's latest TWRP build has the HTC Dumlock in it, which should allow you to flash boot.img's with S-On. Don't know the real details on it, but it's covered in the thread.
zourn said:
Flyhalf's latest TWRP build has the HTC Dumlock in it, which should allow you to flash boot.img's with S-On. Don't know the real details on it, but it's covered in the thread.
Click to expand...
Click to collapse
or if you dont want to risk re flashing recovery and bricking because you have no charging port, you could flash countershrike 2.2. it has built in s-on flashing. no pc required
What if the charging port works, then is there any way to apply custom kernels to ROMs?
Dogbone737 said:
What if the charging port works, then is there any way to apply custom kernels to ROMs?
Click to expand...
Click to collapse
Yes. Then you can use fastboot to flash using the following command:
fastboot flash boot boot.img
feralicious said:
Yes. Then you can use fastboot to flash using the following command:
fastboot flash boot boot.img
Click to expand...
Click to collapse
What if no boot.img is provided with the kernel. Right now I want to apply snuzzo's funky kernel 1.7 to cm 10. 1.7 does not have a boot.img with it. Do I have to wait until he makes a s-on varient of 1.7 before I can apply it. Or can I take the boot.IMG from another ROM that uses 1.7?
Dogbone737 said:
What if no boot.img is provided with the kernel. Right now I want to apply snuzzo's funky kernel 1.7 to cm 10. 1.7 does not have a boot.img with it. Do I have to wait until he makes a s-on varient of 1.7 before I can apply it. Or can I take the boot.IMG from another ROM that uses 1.7?
Click to expand...
Click to collapse
"fastboot flash zimage zImage(extracted from kernel folder)"
Snuzzo said:
"fastboot flash zimage zImage(extracted from kernel folder)"
Click to expand...
Click to collapse
Thanks for the response. but when I enter the commands this is the error I receive:
http://forum.xda-developers.com/attachment.php?attachmentid=1511055&stc=1&d=1353880347
Damn. So I guess I will have to play with s on installer for it. Grrr
Sent from my ADR6425LVW using Xparent Green Tapatalk 2
Related
I ported an unofficial build of CM7 over to the Rezound from the Sensation. I’m not sure why, but the ROM will not boot past the splash screen, so I am going to turn this into a community WIP.
ROM Progress Synopsis :
- Rom was ported over from the HTC Sensation
- A custom kernel was compiled from CM7 source
Working:
Unknown
Not Working
Unknown
Here is what I have done so far.
Since our device isn’t officially supported by CM7, this ROM was ported from a CM7.a3 rom from the Evo3D. Porting from the Evo shouldn’t be a problem since the devices are very similar, both having the msm8660 chipset.
The base ROM that was used was a stock vigor OTA.
Files that were injected in to the base ROM from the CM7 ROM:
- /system/app folder minus phone and Bluetooth
- /system/framework
- /system/fonts and /system/media
- necessary /system/lib files including libandroid_runtime.so
- init.d
- necessary permissions
- altered build.prop
- custom update script
How to install:
NOTE: THIS ROM CURRENTLY DOESN'T BOOT. This is currently a WORK IN PROGRESS and no promises are made that a fully functional ROM will be produced from these efforts. The purpose of this thread is to collaborate all of our CM7 efforts into one thread. DON'T GET YOUR HOPES UP.
As of now, this ROM is GB only. Here is an excellent thread explaining GB/ICS firmware combos: clicky Thanks superchilpil
Disclaimer: I am not responsible for any harm that comes to you or your device by flashing my stuff. Do this at your own risk.
Download link: quada_CM7_20120716
This is a COMMUNITY PROJECT. I want help working on this so we can get this stable as fast as possible. If you are able to help with this project, don’t be afraid to contact me on this thread, PM me, or tweet me Quada03.
Changelog
20120716 - Rebased of off HTC Pyramid (Sensation) which is slightly closer to our device (no 3D screen)
20120715– initial port from Evo 3D
To do list
Replace libaudio.so in system files
Try to find someone who still has the CM7 tree/repo from GB Pyramid. This way we can build straight from source.
ROM Progress:
As of right now, the ROM will not boot past the splash screen. I did a logcat and there are no fatal errors but an audio driver seems to be in a constant loop. I’ll see if I can post a pastebin later today.
Nice work bro. Can't wait to see where this heads
Sent from my Rezound
This would be awesome but again, there is no working RIL for any aosp variation. That will be your biggest hurdle.....
+ 10000000
...
siulmagic said:
...
Click to expand...
Click to collapse
??
he just saving place for future
Erm, why does this require a different HBOOT?
Exciting. Can't wait to see this get worked on more.
Chyrux said:
Erm, why does this require a different HBOOT?
Click to expand...
Click to collapse
You can't flash boot.img files with the stock hboot. If you want to work on the ROM and don't want to switch hboots, a PH98IMG zip could be made in 10 seconds, but I am constantly switching kernels to see if that is part of the problem. I hate always having a PH98IMG on the SD card. It makes it a pain to go back into recovery.
Quada said:
You can't flash boot.img files with the stock hboot. If you want to work on the ROM and don't want to switch hboots, a PH98IMG zip could be made in 10 seconds, but I am constantly switching kernels to see if that is part of the problem. I hate always having a PH98IMG on the SD card. It makes it a pain to go back into recovery.
Click to expand...
Click to collapse
Most people here understand this, they are more than likely s-off and if they are s-off then they already have a custome hboot
The ones who choose to stay s-on have to deal with the consequences
Sent from my ADR6425LVW using Tapatalk 2
Quada said:
You can't flash boot.img files with the stock hboot. If you want to work on the ROM and don't want to switch hboots, a PH98IMG zip could be made in 10 seconds, but I am constantly switching kernels to see if that is part of the problem. I hate always having a PH98IMG on the SD card. It makes it a pain to go back into recovery.
Click to expand...
Click to collapse
Yeah, you can. I'm s–on and I don't bother with ph98 zips. I just flash the boot.img and have never had a problem lol
Sent from my ADR6425LVW using Tapatalk 2
Chyrux said:
Yeah, you can. I'm s–on and I don't bother with ph98 zips. I just flash the boot.img and have never had a problem lol
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You are S-ON with the stock HBOOT and you can flash boot.img? I'm not saying you are for sure wrong, but my stock hboot would not let me flash another boot.img.
Maybe he's referring to flashing from hboot and not recovery
Sent from my ADR6425LVW using Tapatalk
Quada said:
You can't flash boot.img files with the stock hboot. If you want to work on the ROM and don't want to switch hboots, a PH98IMG zip could be made in 10 seconds, but I am constantly switching kernels to see if that is part of the problem. I hate always having a PH98IMG on the SD card. It makes it a pain to go back into recovery.
Click to expand...
Click to collapse
You're talking about the difference of being S-On vs S-Off, not stock hboot vs modified hboot. The main thing a stock hboot won't allow is using fastboot commands. If you install a recovery via PH98IMG.zip, then most people won't miss fastboot commands. I've always been on stock hboot since being S-Off.
Yes I've been waiting for this
Sent from my iPad using Tapatalk HD
nolimit78 said:
Maybe he's referring to flashing from hboot and not recovery
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
This.
destro158 said:
You're talking about the difference of being S-On vs S-Off, not stock hboot vs modified hboot. The main thing a stock hboot won't allow is using fastboot commands. If you install a recovery via PH98IMG.zip, then most people won't miss fastboot commands. I've always been on stock hboot since being S-Off.
Click to expand...
Click to collapse
I use JBs hboot to modify the kernel with fastboot commands in HBOOT. A stock hboot will not allow for this, I believe the only way would be to use a PH98IMG or flash a kernel in recovery using a script. I just feel that flashing in fastboot is much easier.
fastboot flash boot boot.img
or
fastboot boot zimage zImage
Quada said:
I use JBs hboot to modify the kernel with fastboot commands in HBOOT. A stock hboot will not allow for this, I believe the only way would be to use a PH98IMG or flash a kernel in recovery using a script. I just feel that flashing in fastboot is much easier.
fastboot flash boot boot.img
or
fastboot boot zimage zImage
Click to expand...
Click to collapse
I do that in stock hboot even when I was s-off...
I unlocked my rezound with htcdev site. Installed twrp recovery then I try to install any custom rom and the phone starts to boot up and stops. I tried clockwork mod and amon ra recovery and I get the same results. For example the xp sense rom gets to the beats audio logo and stops loading. I let it sit for a half hour and would not go further. I'm sure I'm doing something wrong. Any help would be appreciated, thanks.
You're still S-ON, righr? You need to boot to bootloader and flash the kernel. It's probably already on your card as a PH98IMG.ZIP file.
My name's Harold and I'm a flashaholic.....
hgoldner said:
You're still S-ON, righr? You need to boot to bootloader and flash the kernel. It's probably already on your card as a PH98IMG.ZIP file.
My name's Harold and I'm a flashaholic.....
Click to expand...
Click to collapse
It's not on there, where can i find it? Thanks.
Anyone please?
Assuming you are S-ON, and assuming (further) that you flashed a ROM that has an alternative kernel flash for S-ON versus S-OFF (check the OP, it usually says whether you have to be S-OFF or not), look inside the zip file for the ROM. Sometimes the kernel is already inside as a PH98IMG.ZIP, sometimes it's "generated" during ROM flash (after which you have to reboot to hboot to flash it).
Reread the OP for your ROM and see what it recommends. If it's S-OFF only, you'll need to flash a different ROM that lets you flash if you're S-ON.
That did the trick.
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
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
Looking for the RUU for the 2.28 hboot. Every RUU I run ends up with the phone telling me that the firmware on the device is too new for the RUU i just ran. Now, from what I recall about the last time i tried messing with a Rezound, the RUU was an .exe you run from your computer, but all the stuff ive been finding are all .zips that you run in recovery. I dont care about s-off and/or root, all i want is a full restore like the pone has never been used. This is for one of my kiddos phones that has the 2.28 hboot that he has somehow (not necessarily) bricked, but has jacked it up pretty good and its laggy and just operating like crap. Some linky type help would be greatly appreciated, and in the meanwhile, im firing up some old computers that i used when previously messing with another rezound i owned years ago. Thanks in advance for any help!!
youdoofus said:
Looking for the RUU for the 2.28 hboot. Every RUU I run ends up with the phone telling me that the firmware on the device is too new for the RUU i just ran. Now, from what I recall about the last time i tried messing with a Rezound, the RUU was an .exe you run from your computer, but all the stuff ive been finding are all .zips that you run in recovery. I dont care about s-off and/or root, all i want is a full restore like the pone has never been used. This is for one of my kiddos phones that has the 2.28 hboot that he has somehow (not necessarily) bricked, but has jacked it up pretty good and its laggy and just operating like crap. Some linky type help would be greatly appreciated, and in the meanwhile, im firing up some old computers that i used when previously messing with another rezound i owned years ago. Thanks in advance for any help!!
Click to expand...
Click to collapse
Unfortunately, there is no RUU for Hboot 2.28 (actually, firmware version 4.5.605.14)... The last full RUU was either 3.14.605.12 (Official) or 4.3.605.2 (unofficial leak). The problem is neither will install on your device because it is S-On, which is a safety measure that prevents older versions of firmware from being installed as well as other things. If the phone is not bootable after a factory reset in the bootloader, your options are:
1) Install a custom or a stock-ish aftermarket ROM
2) S-OFF the device so that you can run an older RUU and allow it to update OTA (option 1 would have to be done prior to attempting this)
3) Send it off for JTAG programming
Honestly, the first option is the most economical... there are tons of really good ROMs out there for the Rezound, from a stock/rooted image to full blown custom ROMs based on CyanogenMod or any number of other projects.
Let us know what you think, and we can advise you from there.
That makes sense actually LoL couldn't find the RUU and no explanation as to why. I think I'll do either 1 or 2, not sure yet. Thanks for the response!!
Sent from my SM-G900P using XDA Free mobile app
ok, so i got the cwm, amon-ra and twrp recovery PH98IMG files and attempted to flash them in hboot and it checks the package but never asks me to install them. Im s-on still, and from what i understand about the rezound, thats ok to still be able to flash ROMS (at least sense ROMS). Please forgive my ignorance, but im a galaxy rooter mainly nowadays and this confounded(and old) thing is just bugging me now LoL Im betting that im skipping a step, any gifts of knowledge from the the Rezound Android Yodas out there?
youdoofus said:
ok, so i got the cwm, amon-ra and twrp recovery PH98IMG files and attempted to flash them in hboot and it checks the package but never asks me to install them. Im s-on still, and from what i understand about the rezound, thats ok to still be able to flash ROMS (at least sense ROMS). Please forgive my ignorance, but im a galaxy rooter mainly nowadays and this confounded(and old) thing is just bugging me now LoL Im betting that im skipping a step, any gifts of knowledge from the the Rezound Android Yodas out there?
Click to expand...
Click to collapse
If you are S-ON you cannot flash via an unsigned PH98IMG (you must be S-Off to do this), you have do it with fastboot... and remember that if you flash a ROM image with recovery booted from the device, you must manually fastboot flash the boot.img of the ROM with the command:
fastboot flash boot boot.img
You can avoid this by booting recovery via fastboot... put the recovery.img file in your fastboot folder, start the phone in Hboot and select Fastboot, then use the command:
fastboot boot recovery.img
Then the device can flash the boot.img with the ROM.
acejavelin said:
If you are S-ON you cannot flash via an unsigned PH98IMG (you must be S-Off to do this), you have do it with fastboot... and remember that if you flash a ROM image with recovery booted from the device, you must manually fastboot flash the boot.img of the ROM with the command:
fastboot flash boot boot.img
You can avoid this by booting recovery via fastboot... put the recovery.img file in your fastboot folder, start the phone in Hboot and select Fastboot, then use the command:
fastboot boot recovery.img
Then the device can flash the boot.img with the ROM.
Click to expand...
Click to collapse
Thanks!! Call me an idiot, but that last bit confused me. What fastboot folder? On the card or phone? And the "with the ROM part" is that assuming that I have a ROM file that im also installing at the same time?
youdoofus said:
Thanks!! Call me an idiot, but that last bit confused me. What fastboot folder? On the card or phone? And the "with the ROM part" is that assuming that I have a ROM file that im also installing at the same time?
Click to expand...
Click to collapse
I mean in a folder on your PC... fastboot and adb should be in the platform_tools directory of your Android Studio SDK installation in Windows.
Fastboot and adb are tools to manipulate your phone from your computer, and are a requirement when modding the Rezound... Or use Linux and install android-tools-fastboot and android-tools-adb from the Ubuntu software repository.
The boot.img file is inside the ROM zip file, the boot partition can't be written to by recovery if it's booted from your phone well S-On, you have to push it manually with fastboot.