I am currently running hboot1.5 and HTC unlocked with Root running TWRP recovery. I know there are limitations to what Roms I can flash with S-On rooting. How can I tell which Roms will work? I have been running stock 2.3.4 since I bought the phone used about 3 weeks ago. It seems to run okay, but my Quadrant scores are consistently less than 2k (usually ~1900-1950) when my wife's bone stock MoPho benchmarks at ~2300-2500. I'm pissed that the guy I bought it from took the OTA for hboot1.5 which severely limits me at the moment, but I just want to get the most out of my phone. Can anyone point me in the direction of some good custom roms that will work with my configuration? I don't need to run 3500's but it would be nice to be over 2k. (Even my rooted epic with SRF1.1.1 scored 2300's all day long)
_-Jay-_ said:
I am currently running hboot1.5 and HTC unlocked with Root running TWRP recovery. I know there are limitations to what Roms I can flash with S-On rooting. How can I tell which Roms will work? I have been running stock 2.3.4 since I bought the phone used about 3 weeks ago. It seems to run okay, but my Quadrant scores are consistently less than 2k (usually ~1900-1950) when my wife's bone stock MoPho benchmarks at ~2300-2500. I'm pissed that the guy I bought it from took the OTA for hboot1.5 which severely limits me at the moment, but I just want to get the most out of my phone. Can anyone point me in the direction of some good custom roms that will work with my configuration? I don't need to run 3500's but it would be nice to be over 2k. (Even my rooted epic with SRF1.1.1 scored 2300's all day long)
Click to expand...
Click to collapse
Im running viperROM & LOVE IT! Tried a few others & while some are faster, viperMOD is stable as stable can get. As far as limitations with custom kerenels, you can flash them as long as you access recovery from fastboot.
adb reboot bootloader
fastboot boot recovery.img
Then flash away!!!
If you want something nasty fast, try Synergy nightly. Be warned, not so stable at times depending how you set it up.
_-Jay-_ said:
I am currently running hboot1.5 and HTC unlocked with Root running TWRP recovery. I know there are limitations to what Roms I can flash with S-On rooting. How can I tell which Roms will work? I have been running stock 2.3.4 since I bought the phone used about 3 weeks ago. It seems to run okay, but my Quadrant scores are consistently less than 2k (usually ~1900-1950) when my wife's bone stock MoPho benchmarks at ~2300-2500. I'm pissed that the guy I bought it from took the OTA for hboot1.5 which severely limits me at the moment, but I just want to get the most out of my phone. Can anyone point me in the direction of some good custom roms that will work with my configuration? I don't need to run 3500's but it would be nice to be over 2k. (Even my rooted epic with SRF1.1.1 scored 2300's all day long)
Click to expand...
Click to collapse
You can flash any ROM you want and any kernel you want.
The only limitations are the steps/procedures you have to following when flashing the files due to HTC's unlock method. The key limitation is HTC does not unlock write access for the kernel while in traditional recovery.
Taken from a lil guide I've put together after answering this question over and over on the Q&A board.
The ways around HTC's limitations are as follows:
HTC Unlock - Hboot version 1.50
Methods to Properly Flash a Kernel with HTC Unlock
1) Using Flash Image GUI (FIG):
For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put/download the kernel .zip file onto your sdcard, select the file from inside the application. FIG will verify the .zip file and its contents. Once it passes verification, select Flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Using Custom Recovery:
Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Using fastboot:
Boot into the custom recovery using the traditional methods, reboot recovery, vol down + power -> bootloader -> recovery, etc, and flash the ROM. Due to the HTC lock on the boot partition (where kernel is stored), the custom recovery will report everything was successful, but the kernel will NOT have been loaded.
Reboot into fastboot mode and then flash the kernel (extracted from the ROM .zip file) using the computer and this command: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included in the ROM .zip instead of the boot.img for the kernel. The zImage will not work properly using the fastboot method.
Post back any questions or concerns you might have. Good luck!
Ok, I will try it out and see if I can do it correctly. Thanks you guys.
Related
Ok like many I upgraded my phone and used HTC's S-Off Tool. That means no AOSP for me
The purpose of this thread is to discuss methods of downgrading the hboot to one that allows kernel flashing, as well as keep up to date regarding development in this area.
I attempted to flash the Eng Hboot through bootloader and no dice. I also tried
Code:
C:\Android>fastboot flash hboot hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.363s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.365s
I also tried RUU and it didn't work either
Now its up to you real devs to try and figure this out
EDIT:Thanks to JTNiggle we have a workaround for kernel flash
Edit:
Alright, it works. You can flash an older ROM, in my case Ava's V1, and then got to fastboot and flash the kernel for that rom. It will take, and so far everything works. Wifi, 4g, 3g, voice, bluetooth, all good.
This is pretty sweet news to me, seems like there wont be as many limitations with this as we thought.
So to do this for yourself, first, download your rom of choice.
Then use 7zip or another utility to open the archive and copy out the boot.img, put that boot.img on the root of your sdcard before you flash ur rom.
Boot into recovery and wipe as necessary, then flash ur rom. When finished, while still in recovery, go back to main menu and pick advanced menu, then reboot menu, then pick bootloader.
Once it boots to fastboot usb, you can do this from a command prompt from ur sdk tools folder,
Code:
fastboot flash boot boot.img
it will give you an output sbout being okay, and once finished, you can do,
Code:
fastboot reboot
And ur good to go, you should boot into your rom just as you would expect, happy as a clam. Hopefully this is something that will be able to be fixed along the way so that you don't have to do these steps. Heck, there may be an easier way now, but I'm no dev, so I'll leave it to someone who is.
For now, i've got an htc unlocked phone here running Ava's v1 with a 2.6.35.10 kernel and it's buttery smooth.
Click to expand...
Click to collapse
Reserved.....
reserved as well....
and just in case also reserved.....
Just so you know you can flash kernels with hboot 1.5.
Just saying...
Here is the link on how to: http://forum.xda-developers.com/showpost.php?p=17107369&postcount=32
I used alpharev and theres no AOSP for me either!
Really..?
Sent from my PG86100 using XDA App
Yea, u can flash everything but radios
Sent from my PG86100 using Tapatalk
Thats fine and all but I think its kinda ridiculous that HTC's s-off isn't really fully unlocked... The one time I decide to go the official methods I get screwed
Won't be making that mistake again..
This method also works and the flashes take:
Have your recovery image (I have cwm in the same directory as fastboot.exe to make things easier).
Boot into bootloader, choose fasboot, connect the phone via usb (turns into fastboot usb)
Command prompt, "fastboot boot whatever your recovery image name is.img" (obviously exclude the "")
So for me I.E. it will be "fastboot boot cwm-4.0.1.4.img"
The phone will boot into recovery, now, since you called recovery from fastboot, it will flash any rom or kernel like in the OP's method (i have tried it and sticks, it appears the sole fact of launching or using fastboot removes any lock HTC has left there). The advantage is, if you have a ROM that includes a modified kernel already (like overclocking and such), you don't have to extract the kernel and flash it separately.
Thanks Brandas!.
You can flash kernels via fastboot with hboot 1.5. I can confirm this I did it a few times on ny old 3d
sent from a double barreled shooter
i have discussed how to flash kernels on hboot 1.50 on here a few weeks ago...
it can be done - did it the other day as a matter of fact
fastboot flash boot boot.img
we had to do this on synergy, cause the installer script could not flash the ramdisk from the rom. after fastbooting the ramdisk..all the issues went away.
so you with hboot 1.5 we just dont have root yet?
armonwilson888 said:
so you with hboot 1.5 we just dont have root yet?
Click to expand...
Click to collapse
if you have 1.5 - what i walked someone thru on synergy's chat - (that someone else copied/pasted it on here and took credit for, spelling errors and all) is this:
they unlocked via HTCDEV.COM from a 1.40 bootloader - she did this under the advise of another forum (not xda). this process involved to updating to the latest RUU/firmware/hboot/radio package, then using htcdev.com to unlock the bootloader. after she did this, she was stuck.
we fastbooted clockwork recovery's IMG file to her phone, and flashed synergy
we noticed it wasnt working correcly, so i had her superwipe, and format w/ the ext4 optimization tool - it still wasnt working correctly.
*after the 1st flash of synergy, clockwork recovery broke and refused to work, even after being re-flashed via fastboot. we have since flashed TeamWin's recovery from a IMG file using fastboot, and have had no issues w/ the recovery tool.
after i looked in to it, i found the stock HTC kernel and ramdisk was still installed.
we fastbooted the ramdisk - and now she is 100% up and running.
i personally would wait for 1.50 to be cracked to get full S-OFF, but if u cant wait, you can still unlock, flash roms, root, and fastboot the ramdisk.
chad.goodman said:
if you have 1.5 - what i walked someone thru on synergy's chat - (that someone else copied/pasted it on here and took credit for, spelling errors and all) is this:
they unlocked via HTCDEV.COM from a 1.40 bootloader - she did this under the advise of another forum (not xda). this process involved to updating to the latest RUU/firmware/hboot/radio package, then using htcdev.com to unlock the bootloader. after she did this, she was stuck.
we fastbooted clockwork recovery's IMG file to her phone, and flashed synergy
we noticed it wasnt working correcly, so i had her superwipe, and format w/ the ext4 optimization tool - it still wasnt working correctly.
*after the 1st flash of synergy, clockwork recovery broke and refused to work, even after being re-flashed via fastboot. we have since flashed TeamWin's recovery from a IMG file using fastboot, and have had no issues w/ the recovery tool.
after i looked in to it, i found the stock HTC kernel and ramdisk was still installed.
we fastbooted the ramdisk - and now she is 100% up and running.
i personally would wait for 1.50 to be cracked to get full S-OFF, but if u cant wait, you can still unlock, flash roms, root, and fastboot the ramdisk.
Click to expand...
Click to collapse
Who is the op? Ill update the post with this information and give him/her credit.
chad.goodman said:
if you have 1.5 - what i walked someone thru on synergy's chat - (that someone else copied/pasted it on here and took credit for, spelling errors and all) is this:
they unlocked via HTCDEV.COM from a 1.40 bootloader - she did this under the advise of another forum (not xda). this process involved to updating to the latest RUU/firmware/hboot/radio package, then using htcdev.com to unlock the bootloader. after she did this, she was stuck.
we fastbooted clockwork recovery's IMG file to her phone, and flashed synergy
we noticed it wasnt working correcly, so i had her superwipe, and format w/ the ext4 optimization tool - it still wasnt working correctly.
*after the 1st flash of synergy, clockwork recovery broke and refused to work, even after being re-flashed via fastboot. we have since flashed TeamWin's recovery from a IMG file using fastboot, and have had no issues w/ the recovery tool.
after i looked in to it, i found the stock HTC kernel and ramdisk was still installed.
we fastbooted the ramdisk - and now she is 100% up and running.
i personally would wait for 1.50 to be cracked to get full S-OFF, but if u cant wait, you can still unlock, flash roms, root, and fastboot the ramdisk.
Click to expand...
Click to collapse
Thanks, I just switched to the 3vo from the atrix and ota'ed at first boot. should have researched first. I guess I will just have to wait...
You might see if you can get some help from the devs that hang out in #Thunderbolt on the andirc.com chat to help with downgrading hboot. We had to do it for the original Thunderbolt s-off method. It involved flashing the misc partition with an "unsecure boot image" I believe is what they called it. I don't really know how it works or if the same could be done with the Evo3D but it might be worth a shot.
Sent from my HTC Thunderbolt
JBO1018 said:
You might see if you can get some help from the devs that hang out in #Thunderbolt on the andirc.com chat to help with downgrading hboot. We had to do it for the original Thunderbolt s-off method. It involved flashing the misc partition with an "unsecure boot image" I believe is what they called it. I don't really know how it works or if the same could be done with the Evo3D but it might be worth a shot.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
I tried with the misc partition hack but it still doesnt work. IEF from revolutionary also tried on my friend's phone with the misc partition. Even after you flashed the edited one, hboot still reads the new version(IEF thought maybe the misc partition was being rewritten somehow at boot). We really tried everything everything he could think of. We couldnt get the hboot to downgrade no matter what trick we used
OK I understand that a kernel can be flashed after using HTC unlock method on HBOOT 1.50. That is good news. Even though I don't have the latest HBOOT and I used the REvolutionary tool to s-off my phone, I am very interested in the development of being able to downgrade the latest HBOOT. The reason? Well, if something were to happen and I have to get a replacement phone and it came with the latest update out of the box. Or, if I have to take it to a Sprint repair center and I have to unroot and go back to stock and they update to the latest firmware. I would use HTC's method to unlock, but would prefer to downgrade and use Revolutionary. I understand that they are working on supporting the latest HBOOT in Revolutionary, but from what I understand the updates patches the fr3vo exploit and other holes. I hope that just because kernels can be flashed that no one works on finding a way to downgrade the HBOOT after using HTC's unlock method.
In advance menu, there is no REBOOT MENU to boot to bootloader. is this for CWM Recovery ?
I have been an avid Android user for a few years now. I had an ATT Captivate which had a huge dev following. It was so easy to flash and switch ROMs on a whim.
This is my first HTC phone and over the weekend I went through the steps to unlock the bootloader then root it. To get it to root I had to load the Amon RA recovery and then install su and superuser. It worked and it appears I have root now. But I am confused what H-Boot, fastboot, etc are?? I'm used to the phone being able to boot right into recovery and then go through the clockworkmod options while in recovery, making it so easy to load a new ROM in a zip.
Is there anywhere I can read to learn more about the HTC bootloader, H-BOOT, fastboot, etc? It seems to be a lot more complicated than the OG Droid and my Galaxy S.
Thanks.
derek4484 said:
I have been an avid Android user for a few years now. I had an ATT Captivate which had a huge dev following. It was so easy to flash and switch ROMs on a whim.
This is my first HTC phone and over the weekend I went through the steps to unlock the bootloader then root it. To get it to root I had to load the Amon RA recovery and then install su and superuser. It worked and it appears I have root now. But I am confused what H-Boot, fastboot, etc are?? I'm used to the phone being able to boot right into recovery and then go through the clockworkmod options while in recovery, making it so easy to load a new ROM in a zip.
Is there anywhere I can read to learn more about the HTC bootloader, H-BOOT, fastboot, etc? It seems to be a lot more complicated than the OG Droid and my Galaxy S.
Thanks.
Click to expand...
Click to collapse
It's actually not all that bad. The HTC bootloader(H-BOOT) is a locked up tighter than fort knox beast that doesn't want to let us do what we want to.. But for good reason. The HTC bootloader as you already know can be unlocked via HTCDev. This allows us to use custom ROMs, recovery, and kernels but keeps us from the radio. It also forces us to manually update the kernel with each ROM. Some developers have bundled a method of flashing the kernel within the ROM but it's from dev to dev/ROM to ROM.
Fastboot is a method to allow flashing of filesystems over USB. For instance when you flashed Amon-Ra you used a command "fastboot flash recovery xxxx.img" This tells the command to flash the recovery partition with xxxx.img.
Flashing via ClockWorkMod carries the same issue as described above. You either have to manually flash the kernel or the dev has to package the ROM to include automatic flashing. One of the caveats to automatic flashing is that it will update a version in your firmware(mainver) and potentially create issues. For this reason only, I suggest getting very comfortable with manually flashing a kernel vs the automated method.
If you have other questions feel free to ask. Or check out some of the wiki's out there like this one: http://android-dls.com/wiki/index.php?title=Main_Page
I've been trying to root my HTC Evo 4G LTE phone and I've run into some problems. I was able to root the phone with no problem, however I wasn't able to get S-OFF due to my HBOOT version. I flashed CWM 10 rom so that I could get Jelly Bean on my phone but every time I booted my phone up, it would just hang on the boot logo.
I researched a little more and I found out that I didn't have the right kernel to run that Rom. I read that I was suppose to Flash the boot.img from the Rom I wanted to install using the Flash Image GUI app. I did so, and when my phone rebooted, it goes straight to the Bootloader / Fastboot screen automatically. I can not get it to load the Rom I flashed.
Can anyone help me or lead me in the direction to get the rom to load correctly?
Thanks
juaxoo said:
I've been trying to root my HTC Evo 4G LTE phone and I've run into some problems. I was able to root the phone with no problem, however I wasn't able to get S-OFF due to my HBOOT version. I flashed CWM 10 rom so that I could get Jelly Bean on my phone but every time I booted my phone up, it would just hang on the boot logo.
I researched a little more and I found out that I didn't have the right kernel to run that Rom. I read that I was suppose to Flash the boot.img from the Rom I wanted to install using the Flash Image GUI app. I did so, and when my phone rebooted, it goes straight to the Bootloader / Fastboot screen automatically. I can not get it to load the Rom I flashed.
Can anyone help me or lead me in the direction to get the rom to load correctly?
Thanks
Click to expand...
Click to collapse
I had the same problem when I first Jumped ship from Sense. Since you have S-ON you need to also flash the kernel of any aosp rom. So first things first do you have the android development tools installed on your computer?
T3CHW0LF said:
I had the same problem when I first Jumped ship from Sense. Since you have S-ON you need to also flash the kernel of any aosp rom. So first things first do you have the android development tools installed on your computer?
Click to expand...
Click to collapse
Yes I do. I am using a Mac if that helps in any way
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
simonsgray said:
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
Click to expand...
Click to collapse
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Thanks man. sig is a little out of date, i havent' needed xda as much since jumping to nexus. TWRP and i didn't do the s-off stuff. it says it needs a stock rom and i just havea spinning cyanogen mod. i will try install the 4ext and see if that changes the results.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
simonsgray said:
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
Click to expand...
Click to collapse
If you want to flash back to the stock ICS image you need to first relock your bootloader. When you relock it will say relocked when in hboot. The procedure is to place the image in the root of your external SD card and select from hboot. It should recognize and flash back to stock, however everything other than your external SD gets wiped in the process. So you need to make sure you have a good recent backup. Also, you remember when you first HTC dev unlocked they sent you an image to push to unlock? Well, I hope you saved it, because you'll need it again to re-unlock the bootloader after flashing the firmware image, but before attaining s-off.
However, if you were already on your carrier's latest ICS firmware before you started flashing different ROMs, you probably already have their latest radio. If you install the latest 4ext and enable smart flash, you'll probably succeed in installing any of the source built ROMs (ASOP, CM, PACman, evervolv) without s-off, because ROMs built from the source don't have the CID flag in their binaries.
If you still decide to go back and attain s-off the procedure is as follows: 1) relock your bootloader 2) flash the latest stock firmware for the carrier that sold your device. 3) Unlock your bootloader again using the image and commands you previously did to HTC dev unlock the first time, 4) get s-off using the wire-trick 5) flash the hacked hboot (and another radio if you desire, but not required for most ROMs) 6) super CID to remove all carrier locked file / partition limitations and protections 7) Flash your preferred recovery. Because you're now s-off you can use TWRP, CWM, or 4ext since the protected partitions are no longer an issue. 8) Flash any ROM you want provided it's based on ICS or later (below won't work because the radio is incompatible).
Edit: One other thing to note before starting any of this make sure your battery is fully charged. Also, the first time you boot after installing CM or any ASOP based ROM it can take quite some time to go through the process before you get to the login screen. For me it usually takes a little under 10 mins. It may at first appear to be a little sluggish until the rom settles, usually about 10-15 mins.
I hope this helps
Q&A for [ROM][4.4.4_r2][OFFICIAL][GPL] LiquidSmooth v3.2 - vigor - 10|12|14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
bunchies said:
Final KitKat build coming soon, Lollipop was released this morning :thumbup:
Let's see if the Rezound can run android 5.0
Click to expand...
Click to collapse
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
catcher8587 said:
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
Click to expand...
Click to collapse
Yeah, you will be fine
s-on users flash boot.img in fastboot
Last Build
I set the last build and at once found an error. If to come Settings - the Mobile network - Settings of the operator you give out an error: "In application of "com.android.phone" there was an error..." At all so? I quickly discharge the battery for some reason!
Crash video playing
added small problem... When I want to view video sometimes issues the error message. Video doesn't play...
re:chrome floating windows
Just uninstall and download an older version of chrome. Then, don't accept the update. You can't turn off the floating windows. Very annoying
HTC Rezound Liquidsmooth 3.2 ROM install failure
I used this link (theunlockr.com/2013/10/22/how-to-root-the-htc-rezound/) on my stock HTC Verizon Rezound to unlock the bootloader, installed TWRP, and SuperSU to gain access to root.
Then I downloaded LiquidSmooth 3.2 11/5/14 R2 -- Android 4.4.4 and Gapps 4.4.4 Build 8.1 (not Build 7 on this site) I used TWRP to flash both files in the same flash event to the phone. I had placed the files on the INTERNAL SD in the DOWNLOAD directory. Wiped before and after the flash. Phone came up to HTC screen, Blinked, and returned to HTC screen. Waited 10 minutes or so and had to pull battery . Tried another boot with same results. Restored. Repeated same results.
Downloaded the LS v3.2 file again. Downloaded an md5 checker program to my computer. Both files passed. Repeated using second v3.2 file with same results. Downloaded the 8/21/2014 version of the file, md5 checked it, and repeated with same results.
Then downloaded the final LS v2.9 JB4.2.2 file and the appropriate GAPPS file and md5ed it. Repeated with same results.
I am now back to my rooted but stock ROM. I would like to get this LS v3.2 KitKat ROM installed, but am at my wits end.
I also used this link (android.wonderhowto.com/how-to/ultimate-guide-using-twrp-only-custom-recovery-youll-ever-need-0156006/) to troubleshoot. That is why I did a wipe in advance of the first install attempt and I think most of the others as well, although I couldn't tell it helped. I tried the Fix Permissions hint several times but it failed each time.
The only think I have ever read about on HTC phones is S-On or S-Off, but I don't think this applies as neither link source I referred to mentioned S-ON.
Any help would be appreciated. Thanks in advance.
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Thanks a Million or perhaps 10 million!!!
acejavelin said:
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Click to expand...
Click to collapse
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
xdatsellers said:
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
Click to expand...
Click to collapse
Most general tutorials on flashing ROMs on HTC devices includes this information, although most devs will say their ROMs are for S-OFF devices only, it is assumed with a little fastboot trickery most ROMs will work fine, but devs usually make the assumption you know what you are doing.
I would HIGHLY recommend you go S-OFF... if something catastrophic happens and you are S-ON there is often no method of recovery, since all current RUU (HTC's proprietary ROM restoration image) files are prior to current, so do downgrade and restore to stock you must be S-OFF. Rumrunner makes the S-OFF process pretty painless if you are on a custom ROM already.
The boot image, or more accurately the /boot partition, cannot be written to under normal recovery well S-ON, so that affects a nandroid restore as well, you would have to extract the boot image and flash it manually as well to restore a nandroid. BUT, if you boot the recovery image via fastboot it gets around the /boot write restriction even when S-ON... this is a key difference, essentially you are taking the recovery image and telling the phone "this is your new kernel, start it like a ROM" which gets around some of the S-ON restrictions.
Grey network bars
Hello bunchies
I really enjoyed using this rom except this problem my network bars are grey but i can make and receive calls and use the 3g on slow speed (the problem when i call the customer service centre i can't press numbers)
I've checked hboot radio and recovery they are updated
Sorry for my bad English and thanks in advance
Need help to install liquidsmooth
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Thank you
Sent from my SM-N900 using XDA Free mobile app
edwardnizz said:
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Click to expand...
Click to collapse
Assuming you are on current Hboot & radios, upgrade to latest TWRP, flash ROM ZIP and Gapps, fastboot flash boot.img, then reboot and enjoy.
Hello i'm just asking if there wont be any problems with rom update such as recovery boot loop or Freeze or crashes .....etc kthnxbai
can't send SMS or ssd with liquidsmooth 3.2
Hi. As the title says , i cant sens SMS nor use ussd codes. Another issue is that i can't play music. Any help would be appreciated.