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 ?
My friend made the mistake of following a youtube video and really messed up his phone. He has TWRP installed but he's S-On and deleted his restore image. The only thing that functions on this phone is HBOOT. The bootloader was relocked, and now I can't even access recovery. I need some help here. He was trying to get a custom rom installed, but he never went S-Off. Running the RUU provided in DirtyRacun wouldn't work even though it was for the correct HBOOT version. I have no idea where to start on fixing this thing. It is running HBOOT-2.09. I am very comfortable using adb and fastboot - I use it frequently with my HTC One. This almost seems beyond repair - but I'm pretty sure it is fixable. Please help. I have access to both a Linux and a Windows machine, so a solution involving either isn't out of the question. Since recovery isn't accessable, it has to be a fix involving fastboot and adb almost exclusively.
Have you tried to unlock the bootloader again? Once you unlock you can push a recovery to the phone and then flash a ROM. Remember, since he's S-on you'll have to install the kernel separately from the ROM (or use a ROM that has a S-on kernel installer). Hit the top link in my sig for more info.
Sent from my HTC device
I unlocked the bootloader again and got back in to TWRP. Because I am S-On I pushed MeanBean v284 onto the phone but the installation fails every time. I've tried wiping everything, formatting the partitions again, and I can't get past this point.
EDIT: My error says:
"E-Mount: Unable to find partition for path '/MeanBean-v284-jewel-ltevo.zip'
Error flashing zip '/MeanBean-v284-jewel-ltevo.zip'
Updating partition details..."
What version of TWRP and where did you get it?
Sent from my HTC device
Magnum_Enforcer said:
What version of TWRP and where did you get it?
Sent from my HTC device
Click to expand...
Click to collapse
2.7.0.0. He said it was linked from the xda forums. Also, I am going to try the rumrunner s off that was recommended on your guide right now. I can't enable USB debugging because there is no OS on the device right now.
You'll need to install a ROM before you can S-off.
Also, once you get recovery working again you may find the guide in the link below useful.
http://forum.xda-developers.com/showthread.php?t=2443108
Sent from my HTC device
Magnum_Enforcer said:
You'll need to install a ROM before you can S-off.
Sent from my HTC device
Click to expand...
Click to collapse
According to the MeanBean guide, it will work S-On. I'm not sure if you have to flash the kernel seperately, and on top of that I'm not sure how to do that. I haven't been able to find specific instructions other than using fastboot with a boot.img file. I haven't tried this yet with MeanBean, but it didn't work with the Viper Rom.
EDIT: I made it to the step where you flash the ROM (further than I've gotten so far today...). It says the kernel was not installed when installing MeanBean.
Just follow the directions in the ROM thread and you'll be fine. You essentially have to flash the zip file twice. If you want further info, click the top link in my sig.
Sent from my HTC device
Magnum_Enforcer said:
Just follow the directions in the ROM thread and you'll be fine. You essentially have to flash the zip file twice. If you want further info, click the top link in my sig.
Sent from my HTC device
Click to expand...
Click to collapse
After installing the second time, I am still getting the same: "ERROR: Kernel Not Installed!
Copying flashable ZIPs. to /sdcard/Meanbean
Please reboot now!
Updating partition details..."
I am gradually looking through all 949 pages to try to find a solution
EDIT 2: I tried flashing the boot.img file using fastboot as it said in your post to install the kernel. I am still getting that installation error.
Got an old phone from a friend which I'm using since wife broke her phone and I'm trying to decide what to replace it with.
Anyhow, I have an Aria with hboot 1.03, I have unlocked it via the HTC site and managed to get Cyano 10 on it. It is still s-on and I've tried multiple times to redownload Cyano 11 and always get an error of "Error in <name>.zip (Status 0) Installation Aborted". I'm making an assumption based on research that it is due to a combination of s-on and hboot 1.03 so I need to kick it down to 1.02 and s-off it. However, I have been unable to find a valid link for the Official HTC Froyo link to downgrade so I can run Revolutionary to s-off and move ahead.
Thanks in advance.
Hmm, can't find a link either... I can reupload it for you
But before you do that, try updating your recovery to this: http://forum.xda-developers.com/showthread.php?t=2474662
HTCdev unlock shouldn't have any problems with CM11, so it's probably your recovery...
Anyway, here's the RUU
http://goo.gl/OBVJL7
md5sum: 66d703b8a92fc382c38ceec4992a379c
And the rom.zip extracted from it if you just want to run it directly from the phone:
http://goo.gl/WF3RhW
md5sum: 49e737569d1d99e11e652ddcfc15bf84
Edit: Here's a list of them instead of just the AT&T one: http://www.androidruu.com/?developer=Liberty
Thank you Win, that did it. I had to fastboot the CMW as it wouldn't upgrade through recovery, after that I just flashed CM11.
CollinsJ said:
Thank you Win, that did it. I had to fastboot the CMW as it wouldn't upgrade through recovery, after that I just flashed CM11.
Click to expand...
Click to collapse
Problem is that due to S-On it is not possible to write to recovery partition from recovery. You also can't write to boot partition, but you can install ROMs without problems if you flash boot image separately through fastboot.
dansou901 said:
Problem is that due to S-On it is not possible to write to recovery partition from recovery. You also can't write to boot partition, but you can install ROMs without problems if you flash boot image separately through fastboot.
Click to expand...
Click to collapse
Boot images can be flashed from recovery just fine with S-ON... maybe you're thinking of newer (but not newest) HTC devices? I've heard they did that
WinSuk said:
Boot images can be flashed from recovery just fine with S-ON... maybe you're thinking of newer (but not newest) HTC devices? I've heard they did that
Click to expand...
Click to collapse
Possible. I own one of them (points at signature) and it's been that way for me then. When I rooted my Gratia way back, I also directly did the S-OFF so I never checked the procedure with S-ON. Have been a newbie at that time.
So I'm in a similar boat. I have an old aria, and seeing a cm11, id like to try it (though a nexus is my dd). Anyway, i had cm7 on it, went through some old nandroids, and finally got back to 2.1 just after i used unrevoked on it. I've tried to flash the posted rom.zip (2.2.2, so i can then s-off and /or upgrade hboot [which i also tried to do via htcdev with no success]), it fails a sig check on my cwm 2.5.0.1, telling me bad, even though i verified the md5. Figured it could be the recovery, but i cannot flash the newer version on here via ./fastboot flash recovery recovery.img. i also tried ./fastboot boot recovery.img to no avail. I also couldnt flash the recovery through the old cwm. Im baffled a bit here... Any suggestions are welcomed.
Im thinking of trying to put my sim in it and see if the old att update would go through, any thoughts on that?
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.
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.