I got the Rezound phone from a relative and want to turn it into a wireless keyboard for my HTPC. First, I want do decrapify the phone and remove all the Verizon crap from it. I have unlocked the boot loader already, but I haven't tried the wire trick yet. This is the version of the software on the phone:
Android Version 4.0.3
HTC Sense Version 3.6
I am struggling to find relevant threads that are Linux relevant and still contain live links to ROMS/utilities/etc. Any pointers would be appreciated.
drroc said:
I got the Rezound phone from a relative and want to turn it into a wireless keyboard for my HTPC. First, I want do decrapify the phone and remove all the Verizon crap from it. I have unlocked the boot loader already, but I haven't tried the wire trick yet. This is the version of the software on the phone:
Android Version 4.0.3
HTC Sense Version 3.6
I am struggling to find relevant threads that are Linux relevant and still contain live links to ROMS/utilities/etc. Any pointers would be appreciated.
Click to expand...
Click to collapse
to root all you gotta do is download and install amon ra 3.16 via fastboot method and install su & superuser from developer options in that recovery...if you need further help pm me....the rez works very differently than most devices...even other htc's
drroc said:
I got the Rezound phone from a relative and want to turn it into a wireless keyboard for my HTPC. First, I want do decrapify the phone and remove all the Verizon crap from it. I have unlocked the boot loader already, but I haven't tried the wire trick yet. This is the version of the software on the phone:
Android Version 4.0.3
HTC Sense Version 3.6
I am struggling to find relevant threads that are Linux relevant and still contain live links to ROMS/utilities/etc. Any pointers would be appreciated.
Click to expand...
Click to collapse
You need fastboot for linux, everything else is handled on the phone itself. What ROM are you trying to use that it would even let you use it as a keyboard for an HTPC?
mjones73 said:
You need fastboot for linux, everything else is handled on the phone itself. What ROM are you trying to use that it would even let you use it as a keyboard for an HTPC?
Click to expand...
Click to collapse
I have fastboot/adb toolset for Linux. I am just trying to collect all the files I need to root this particular phone. I was thinking of using an unofficial CyanogenMod. I am not a fan of the HTC Sense ROM, plus there is a lot of Verizon crap on the phone.
As far as the keyboard goes, there are plenty of apps on the Google play market that turn a phone into a "keyboard." The phone just sends the key/mouse events via WiFi to a server app on the HTPC, which in turn emulates keyboard/mouse events.
drroc said:
I have fastboot/adb toolset for Linux. I am just trying to collect all the files I need to root this particular phone. I was thinking of using an unofficial CyanogenMod. I am not a fan of the HTC Sense ROM, plus there is a lot of Verizon crap on the phone.
As far as the keyboard goes, there are plenty of apps on the Google play market that turn a phone into a "keyboard." The phone just sends the key/mouse events via WiFi to a server app on the HTPC, which in turn emulates keyboard/mouse events.
Click to expand...
Click to collapse
If you've unlocked the bootloader, you need to install a custom recovery and you're good to go. If your intention is just to install another rom, no point in rooting the current one.
I recommend TWRP - http://forum.xda-developers.com/showthread.php?t=1902381
Grab the latest file there, rename it PH98IMG.zip, put it on your SD card root, shut down, pull the battery, put it back in, power on while holding the volume down key, hit power once in the bootloader, it should scan the SD card, find the file and ask you to press volume up to upgrade, doing that will change your recovery.
I'd reboot back to your rom afterwards and get that file off your SD card. Once done you can follow the same steps to get to the bootloader and select recovery from the menu to get into TWRP.
I'd suggest CM10.2, CM11 is stable, has a few issues to be worked out still, though if you're only using the phone as a remote, it should be fine for you.
Follow the s-on install instructions on the CM10.2 or CM11 threads, that's what you'll need fastboot for.
CM10.2 - http://forum.xda-developers.com/showthread.php?t=2406421
CM11 - http://forum.xda-developers.com/showthread.php?t=2535777
mjones73 said:
If you've unlocked the bootloader, you need to install a custom recovery and you're good to go. If your intention is just to install another rom, no point in rooting the current one.
I recommend TWRP - http://forum.xda-developers.com/showthread.php?t=1902381
Grab the latest file there, rename it PH98IMG.zip, put it on your SD card root, shut down, pull the battery, put it back in, power on while holding the volume down key, hit power once in the bootloader, it should scan the SD card, find the file and ask you to press volume up to upgrade, doing that will change your recovery.
Click to expand...
Click to collapse
I got an error "Main Version is older!"
If it helps: HBOOT 2.28.0
drroc said:
I got an error "Main Version is older!"
If it helps: HBOOT 2.28.0
Click to expand...
Click to collapse
Yeah the android-info.txt needs to be updated since the phone is on the latest build. If you have something you can extract the contents of the zip and re-package them, change the string in that file to .
modelid: PH9810000 cidnum: VZW__001 mainver: 4.05.605.14 btype:1 aareport:1 hbootpreupdate:12
If that doesn't work, you can use fastboot to flash it instead.
mjones73 said:
Yeah the android-info.txt needs to be updated since the phone is on the latest build. If you have something you can extract the contents of the zip and re-package them, change the string in that file to .
modelid: PH9810000 cidnum: VZW__001 mainver: 4.05.605.14 btype:1 aareport:1 hbootpreupdate:12
If that doesn't work, you can use fastboot to flash it instead.
Click to expand...
Click to collapse
Thanks. Updating the android-info.txt did the trick. I can now enter TWRP. Although CM11 doesn't appear to be booting. I am just stuck at the HTC screen. I followed the wipe instructions before I installed the ROM.
drroc said:
Thanks. Updating the android-info.txt did the trick. I can now enter TWRP. Although CM11 doesn't appear to be booting. I am just stuck at the HTC screen. I followed the wipe instructions before I installed the ROM.
Click to expand...
Click to collapse
You need to fastboot flash the kernel, it's in the s-on install instructions.
From the bootloader on the phone, select fastboot and hit power.
Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
Watch the output of the terminal, it should say something like "sent successfully".
Finally send this command:
Code:
fastboot reboot
This command reboots your device into Android. Wait for it to boot up and enjoy your new freshly installed CM11
mjones73 said:
You need to fastboot flash the kernel, it's in the s-on install instructions.
Click to expand...
Click to collapse
Ah. I missed that part. Now it works Thanks again!
drroc said:
Ah. I missed that part. Now it works Thanks again!
Click to expand...
Click to collapse
No problem, that's an extra step you'll need to do anytime you flash a rom since you're s-on.
If you decide to s-off the phone sometime, the kernel would get installed as part of the rom install, being s-off lets you revert firmware if needed also. If you're not gonna do a lot of flashing, I'd leave it as is.
Related
When I first got my Rezound months and months ago, I found and installed one of the stock, rooted ROMS on this site, and installed it.
Much to my annoyance, Verizon has been trying to push the latest update to my phone, so I came back to get the latest relevant ROM. I found http://forum.xda-developers.com/showthread.php?t=1835422 ("stock rooted deodexed 4.03.605.02") and flashed it from Recovery.
The problem is, whenever I try to boot the phone, it gets to the white screen with the green HTC logo, and just sits there. Did I miss a step or something? It's been a long while since I last flashed a ROM, and I'm sure I forgot something...
Thanks.
beleynn said:
When I first got my Rezound months and months ago, I found and installed one of the stock, rooted ROMS on this site, and installed it.
Much to my annoyance, Verizon has been trying to push the latest update to my phone, so I came back to get the latest relevant ROM. I found http://forum.xda-developers.com/showthread.php?t=1835422 ("stock rooted deodexed 4.03.605.02") and flashed it from Recovery.
The problem is, whenever I try to boot the phone, it gets to the white screen with the green HTC logo, and just sits there. Did I miss a step or something? It's been a long while since I last flashed a ROM, and I'm sure I forgot something...
Thanks.
Click to expand...
Click to collapse
looks like you tried to update to a ICS rom from a stock rom.
are you s-off or dev unlocked?
synisterwolf said:
looks like you tried to update to a ICS rom from a stock rom.
are you s-off or dev unlocked?
Click to expand...
Click to collapse
Dev unlocked.
beleynn said:
Dev unlocked.
Click to expand...
Click to collapse
you are going to need to re lock the bootloader and run the ruu.
this will wipe your internal sd card so please back it up
here are the steps:
1. back up rom
2. back up internal sd card
3. fastboot oem lock command
4. download the latest ruu
5. pull the zip out of it and name it PH98IMG.zip
6. place on root of external sd card
7. make sure you have 70% or more on the battery
8. boot into hboot and let it run.
8.1 first pass will be quick and it will ask you to reboot, say yes and grab a beer because the next part will take some time.
9. boot into stock rom
10. dev unlock and all that fun stuff again
synisterwolf said:
you are going to need to re lock the bootloader and run the ruu.
this will wipe your internal sd card so please back it up
here are the steps:
1. back up rom
2. back up internal sd card
3. fastboot oem lock command
4. download the latest ruu
5. pull the zip out of it and name it PH98IMG.zip
6. place on root of external sd card
7. make sure you have 70% or more on the battery
8. boot into hboot and let it run.
8.1 first pass will be quick and it will ask you to reboot, say yes and grab a beer because the next part will take some time.
9. boot into stock rom
10. dev unlock and all that fun stuff again
Click to expand...
Click to collapse
Thanks, but a few questions:
first, when I first got the phone and rooted it, S-Off wasn't available at the time (which is why I didn't do it then). Would it be better (and/or easier) to do that instead of dev unlock?
second, how do I "fastboot oem lock"? It's been months since I last flashed a ROM, and, as always, I forgot how to do these things.
Thanks again.
beleynn said:
Thanks, but a few questions:
first, when I first got the phone and rooted it, S-Off wasn't available at the time (which is why I didn't do it then). Would it be better (and/or easier) to do that instead of dev unlock?
second, how do I "fastboot oem lock"? It's been months since I last flashed a ROM, and, as always, I forgot how to do these things.
Thanks again.
Click to expand...
Click to collapse
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
synisterwolf said:
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
Click to expand...
Click to collapse
I *had* ADB, then I built a new PC, so thanks for the link.
Once I do S-Off, do I still follow the other steps except for 3?
synisterwolf said:
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
Click to expand...
Click to collapse
Ok, so I got to step 9 no problem (your ADB/Fastbook download was 1000x easier than downloading the whole damn package from Google).
Can I now just load up the rooted stock ROM I found earlier, or do I have to do the Dev unlock first?
beleynn said:
I *had* ADB, then I built a new PC, so thanks for the link.
Once I do S-Off, do I still follow the other steps except for 3?
Click to expand...
Click to collapse
If you are s-off you dont need to OEM lock the phone because s-off > dev unlock
so once you are s-off all you need to do is this:
1. download RUU of your choice
2. place on the root of the sd card
3. back up your internal sd because it will be wiped
4. make sure you have 70% battery or better
5. boot into hboot and let hboot take care of the rest.
5.1 first pass of the install will go quickly and ask for a reboot. it will boot back into hboot and continue the install.
6. boot into the stock rom once.
or if you want s-on
1. do the htc dev unlock fun
2. need to load up an engineering hboot to do fastboot commands.
once you have dev unlock then you can do recovery, then load any ICS rom that is meant for our phone. if you wanted to go back to GB you would need s-off so you can downgrade with a GB RUU. (but why would we want to go backwards. )
optional
if you want to install a recovery and you want to do it the fastboot way, you will need an engineering hboot which you can get from the s-off site
or
if you find a recovery that is in zip form just let hboot install it for you.
I AM PLAYING WITH MY REZOUND FROM LAST 1 MONTH YESTERDAY I THOUGHT I HAVE TO UPDATE IT TO ICS(RUU FROM ANDROIDPOLICE) AND FLASHED RUU FROM HEREhttp://www.androidpolice.com/2012/08/02/exclusive-download-htc-rezound-ice-cream-sandwich-ruu-for-final-ota-3-14-605-12/
AFTER FLASHING RUU PHONE STARTS REBOOTING ,NO APPS DOWNLOAD FROM PLAY STORE ,
NOW I WANTS TO GO BACK TO GINGERBREAD OFFICIAL ROM
PLZ SOMEONE HELP ME SO I CAN FLASH GB OFFICIAL RUU ON MY REZOUND
DETAILS OF MY REZOUND-
TAMPERED
****RELOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT -2.25.0000
RADIO-1.22.10.0421R/1.22.10.0424R
OPENDSP-V13.6.0.7611.00.0104
EMMC-BOOT
APR 12 2012,16:47:46
PLZ SUGGEST ME TO GO BACK TO GB OR ANY FIX TO STOP ALL RANDOM REBOOTS.
In order to downgrade you need to S-OFF, then flash one of the old RUU's.
Did you factory reset after installing the ICS?
I would also try installing the new 4.3.605.2 RUU from Android Police... factory default, flash twice (if you flash an RUU, ALWAYS do it twice), then factory default again.
acejavelin said:
In order to downgrade you need to S-OFF, then flash one of the old RUU's.
Did you factory reset after installing the ICS?
I would also try installing the new 4.3.605.2 RUU from Android Police... factory default, flash twice (if you flash an RUU, ALWAYS do it twice), then factory default again.
Click to expand...
Click to collapse
+1 I would try the factory reset before anything. then follow the steps above.
if you are 100% sure you want to go back to GB then you would need s-off
you need s-off to go back to gingerbread. try flashing the new 4.3.605.2
Thnx for all replies can someone confirm Ruu 4.3.605.2 is stable and working fine ?
Sent from my SGH-T999 using xda app-developers app
I have searched google but not able to found any valid link for latest ruu can someone plz post latest ruu link for download ?
Sent from my SGH-T999 using xda app-developers app
sanchitgrover said:
I have searched google but not able to found any valid link for latest ruu can someone plz post latest ruu link for download ?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It is completely stable, and fixes way more issues than the changelog mentions...
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
And select AP Mirror #1 which is hosted on beta.androidfilehost.com, a very reliable and (usually) speedy server, it takes about 3 minutes for me to download it ( I have done it lots of times, people keep saying doesn't work), just click the link, then the green circle with a down arrow to download it (to the left of the filename), MD5 matches every time. If that one give you trouble, go to the same link and on the right hand side there are mirrors of that server, they work equally well.
And like every ROM, VERIFY the MD5 before flashing... if it don't match, don't flash!
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
scy1192 said:
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
Click to expand...
Click to collapse
So this will work with out S-off? I am on Venom Rom on ICS. Great Rom but when I plug my headphones in the phone reboots. I want to get back to Stock ICS.
Thanks
duvious said:
So this will work with out S-off? I am on Venom Rom on ICS. Great Rom but when I plug my headphones in the phone reboots. I want to get back to Stock ICS.
Thanks
Click to expand...
Click to collapse
Without S-OFF you can only go same version or newer, not backwards, but you will have to relock your bootloader... You should then be able to flash the 4.3.605.2 RUU with no problem.
scy1192 said:
It looks like your RUU didn't install completely. Flash it *several* times, until you get the screen where all items are listen as "OK" and it says to reboot.
If that still doesn't work, try flashing it through fastboot:
install HTC Sync (this will install drivers for adb and bootloader debug). Somehow obtain fastboot.exe (pretty sure it comes with HTC Sync. If not, download the Rezound All In One Toolkit. Open a command prompt and change the directory to the same one that fastboot.exe is in (use the command "cd" then the full folder location, ex "cd c:\users\yourname\desktop\fastboot folder").
Next, you'll want to take out your phone's SD card. Power on the phone, holding power and volume down to boot into the bootloader. Then, choose fastboot. Connect your phone to your PC at this time. Now use the command "fastboot oem rebootRUU". Your phone will reboot to a black screen with a silver HTC logo. Next, drag the RUU file you downloaded (doesn't matter what it's named) to the same folder as fastboot.exe. Use the command "fastboot flash zip <ruu name>", replacing "<ruu name>" with the name of the file, obviously. Once the command prompt says it's done, you can safely turn off your phone, or do a battery pull if necessary.
I highly recommend you do not revert to Gingerbread, because it requires a firmware downgrade and the S-Off procedure is necessary. Things can go horribly wrong with S-off especially if you don't know what you're doing.
Click to expand...
Click to collapse
acejavelin said:
Without S-OFF you can only go same version or newer, not backwards, but you will have to relock your bootloader... You should then be able to flash the 4.3.605.2 RUU with no problem.
Click to expand...
Click to collapse
That is great news. I will relock and flash!
htc rezound hboot 2.25.0000 can flash global verizon rom?
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
u can flash gb rom with patch to fix sdcard mounting problem
unlock ur device
install recovery
flash the rom & patch
flash the kernel via fastboot or hboot
then power it on normally
or
flash stock gb only the rom.zip and boot.img via hboot
root
patch ur device manually
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
just download it from android police and flash, flash twice followed with a factory reset. should b in good shape after.
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
For the global RUU - http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Feel free to open a new thread vs using an 8 month old one that isn't related to your problem if you can't find what you're looking for also.
basheerbr said:
want to flash global verizon rom , hboot version 2.25, s-on , locked, please help, want to use on gsm services
Click to expand...
Click to collapse
mike7728 said:
just download it from android police and flash, flash twice followed with a factory reset. should b in good shape after.
Click to expand...
Click to collapse
Also, make sure you allow it to fully do its thing, don't pull battery or anything in the middle of it. The screen will go black for a second or two, just wait it out. It will leave you in bootloader when it's done iirc.
So I'm very new to this and so far I have my bootloader unlocked and my device is rooted. However when I tried to load any roms I get stuck with and HTC white screen once I restart after installing the room. I'm always able to restore my backup using CWM but now I'm stuck and not sure what I'm doing incorrectly. I read somewhere that my HBoot probably needs to be updated but I can't find anything that explains how to do that.
When I go into my bootloader what is see is below. I'm so stuck, I'm not sure what I'm missing or what I should be doing. I'm very new to this and have tried reading a lot of stuff, but I just can't seem to get it. So the more step by step info you can give to me the better. Thanks in advance for you help.
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:56
HBOOT
<VOL UP> to previous item
<VOL DOWN. to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
You're probably not flashing the boot.img since you are S-ON. To flash a ROM, you need adb set up.
Download the ROM you want, and open it with an unzip program like WinRAR. In your adb setup, navigate to the platform-tools folder and drag and drop the boot.img there. Once that's done, delete it from the ROM's .zip. Drop the modified .zip onto your internal storage or SD card and flash it through recovery. Make sure you factory reset and wipe cache first. Once it's flashed, reboot to the bootloader.
Now, right-click while holding the Shift key in the platform-tools folder and open a command window. Select BOOTLOADER on the phone so it says "FASTBOOT USB". Type in the command window "fastboot flash boot boot.img" and wait for it to say OKAY. Now type "fastboot reboot" and you should be headed into the ROM from there for initial setup!
If you're using Plain-Andy or another recent KitKat ROM, I recommend you use PhilZTouch Recovery instead which is like an advanced ClockworkMod.
Your on old radios..... After you get a ROM running by as stated before, open the zip, place the boot.img on the root of your platform-tools folder on your computer, and initiating the command while in fastboot on your phone:
fastboot flash boot boot.img
I would suggest going s-off, very easy now via rum-runner, after running rum-rummer then run a RUU.... Refer to rav3nt3ch guide on downgrading going up to newest radios, it will take you completely back to stock locked and stock recovery. But after running the RUU unlock, flash recovery, and flash ROM again. The newest hboot is 2.28.000 and newest radio is 2.23.10.0123/2.23.10.0124r
But only use a RUU after going s-off. I would HIGHLY HIGHLY HIGHLY suggest it.... Or wait I think you can update radios via a ph98IMG.zip but I'm not sure.... I think you can... But that also requires s-off.... So..... pm me if that made no sense and I will provide any help you need.... Or just explain going s-off and RUU and such with help in finding things....
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
thanks
Thank you so much this worked. I am using Liquid-JB-v2.37-OFFICIAL-vigor. Phone is up and running, just gotta get used to it...it feels like a new phone already. Anything else you think I should do now?
kcipopnevets said:
You're probably not flashing the boot.img since you are S-ON. To flash a ROM, you need adb set up.
Download the ROM you want, and open it with an unzip program like WinRAR. In your adb setup, navigate to the platform-tools folder and drag and drop the boot.img there. Once that's done, delete it from the ROM's .zip. Drop the modified .zip onto your internal storage or SD card and flash it through recovery. Make sure you factory reset and wipe cache first. Once it's flashed, reboot to the bootloader.
Now, right-click while holding the Shift key in the platform-tools folder and open a command window. Select BOOTLOADER on the phone so it says "FASTBOOT USB". Type in the command window "fastboot flash boot boot.img" and wait for it to say OKAY. Now type "fastboot reboot" and you should be headed into the ROM from there for initial setup!
If you're using Plain-Andy or another recent KitKat ROM, I recommend you use PhilZTouch Recovery instead which is like an advanced ClockworkMod.
Click to expand...
Click to collapse
Terrryble said:
Thank you so much this worked. I am using Liquid-JB-v2.37-OFFICIAL-vigor. Phone is up and running, just gotta get used to it...it feels like a new phone already. Anything else you think I should do now?
Click to expand...
Click to collapse
That's up to you. Why not try apps like Xposed Framework or get a great music experience with ViPER4Android?
Next steps?
I got the the liquid smooth rom installed as per the directions given by kcipopnevets above...Should I go ahead and do what you suggested to update radios and the going s-off? I really appreciate everyone's help.
pball52998 said:
Your on old radios..... After you get a ROM running by as stated before, open the zip, place the boot.img on the root of your platform-tools folder on your computer, and initiating the command while in fastboot on your phone:
fastboot flash boot boot.img
I would suggest going s-off, very easy now via rum-runner, after running rum-rummer then run a RUU.... Refer to rav3nt3ch guide on downgrading going up to newest radios, it will take you completely back to stock locked and stock recovery. But after running the RUU unlock, flash recovery, and flash ROM again. The newest hboot is 2.28.000 and newest radio is 2.23.10.0123/2.23.10.0124r
But only use a RUU after going s-off. I would HIGHLY HIGHLY HIGHLY suggest it.... Or wait I think you can update radios via a ph98IMG.zip but I'm not sure.... I think you can... But that also requires s-off.... So..... pm me if that made no sense and I will provide any help you need.... Or just explain going s-off and RUU and such with help in finding things....
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
Click to expand...
Click to collapse
Terrryble said:
I got the the liquid smooth rom installed as per the directions given by kcipopnevets above...Should I go ahead and do what you suggested to update radios and the going s-off? I really appreciate everyone's help.
Click to expand...
Click to collapse
I would strongly suggest going S-OFF, just use rumrunner but make sure you backup first... I can't stress this enough, make a complete nandroid backup with TWRP or CWM before you start, it is common in the S-OFF process with rumrunner to wipe the device (at least partially so it won't boot). Restoring the nandroid is the easiest fix, from there updating radios or anything else is simple.
acejavelin said:
I would strongly suggest going S-OFF, just use rumrunner but make sure you backup first... I can't stress this enough, make a complete nandroid backup with TWRP or CWM before you start, it is common in the S-OFF process with rumrunner to wipe the device (at least partially so it won't boot). Restoring the nandroid is the easiest fix, from there updating radios or anything else is simple.
Click to expand...
Click to collapse
Am I the only person who couldn't restore my backups after rumrunner because all four failed!?!!?!?!?!??!?!?!?!?!? WTF!?!?!?!?
pball52998 said:
Am I the only person who couldn't restore my backups after rumrunner because all four failed!?!!?!?!?!??!?!?!?!?!? WTF!?!?!?!?
Click to expand...
Click to collapse
Lol... Probably not the only one, just the only one I am aware of.
Sent from my LG-G2 using Tapatalk
acejavelin said:
Lol... Probably not the only one, just the only one I am aware of.
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
._. greatttttttt, more great luck of what happens to me XD, but lol darn
I'm now s-off...trying to get help to update radios...also would like to get tampered label removed...
acejavelin said:
I would strongly suggest going S-OFF, just use rumrunner but make sure you backup first... I can't stress this enough, make a complete nandroid backup with TWRP or CWM before you start, it is common in the S-OFF process with rumrunner to wipe the device (at least partially so it won't boot). Restoring the nandroid is the easiest fix, from there updating radios or anything else is simple.
Click to expand...
Click to collapse
Terrryble said:
I'm now s-off...trying to get help to update radios...also would like to get tampered label removed...
Click to expand...
Click to collapse
Your S-OFF, it is easy... just flash the radios and firmware (bootloader) like any ROM, put the ZIP on SD card, start TWRP/CWM, flash the the firmware.zip file and reboot. Done.
Get the files you need from this post: http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
I helped him through pm he's on newest radios.... And o damn forgot about that method too. *facenuke* ughh
Sent from my Rezound using tapatalk. CyanogenMod 11. S-off.
Anyone here have Liquid-JB-v2.37-OFFICIAL-vigor.zip?
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
chilort said:
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
Click to expand...
Click to collapse
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
es0tericcha0s said:
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
Click to expand...
Click to collapse
I'm going to bring some of this to you in pieces so I may edit this post for more info to answer your questions (I have a toddler running around and it is dinner time).
I do not know my firmware version. Under relocked my phone says:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.29.40g.00.19
OpenDSP-v19.2.0268.0927
OS-4.13.502.3
eMMC-boot 1024MB
Jul 11 2014,20:49:19.0
I cannot hotlink but the one in this thread (http://forum.xda-developers.com/showthread.php?t=2777778) is one of the RUUs I tried. I tried others but in my haste to try to get this thing running again I didn't exactly take good records.
After running getvar all
version: 0.5
version-bootloader: 2.22.0000
version-baseband: 1.29.40g.00.19
version-cpld: None
version-microp: None
version-main: 4.13.502.3
version-misc: PVT SHIP S-ON
serialno: HT385WA00294
imei: 356482050078674
meid:
product: m4_ul
platform: HBOOT-8930
modelid: PO5822000
cidnum: CWS__001
battery-status: good
battery-voltage: 4314mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e1af350
hbootpreupdate: 11
gencheckpt: 0
Edit:
Okay, when trying the RUUs I get Error 155: Unknown error.
My PC is a an old Core 2 Duo and crashed a few times just trying to load the RUU. The RUU then asks to go through a recovery mode. It shows a picture with four exclamation points in the corners of the screen on the phone. My phone does not have the exclamation points. I've tried the recovery process a few times and it doesn't do anything.
The error about something being too long was when I was trying to load a .zip using fastboot from my Mac.
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
es0tericcha0s said:
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
Click to expand...
Click to collapse
Thank you for the help! I am not at all opposed to a custom rom (I thought going backward might be easier than forward). But that goes beyond what I've read so far. I know I could Google it, but would appreciate any links, pointers, or other primers.
Stock + root is what I was trying to achieve.
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
es0tericcha0s said:
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
Click to expand...
Click to collapse
The version of TWRP on my phone is 2.6.0.0. This is not version listed in the link you posted. They list 2.7.0.5. Will this be problematic?
I went ahead and gave it a try. I loaded TWRP and went into the adb sideload feature. The screen for sideload listed the following:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Running boot script ...
Finished running boot script.
E: TWFunc::Copy_Log -- Can't open destination log
E: Unable to mount '/cache'
Starting ADB sideload feature ...
I saved the rom as rom.zip to make things easier as suggested. In my terminal window I typed the command as listed (ADP and the rom are in the same folder). In the terminal window I received:
error: closed
error: closed
You will definitely need the newer TWRP before it will work. But you don't use adb sideload. As long as the PC recognizes the phone correctly, then you just need to open the Command Prompt, change directories to the folder where adb and rom.zip are store and then copy and paste the command into it and hit enter. It should start to send. It will take awhile and there is no timer so just go grab a sandwich or drink or something and be patient.
You can use this video for reference:
https://www.youtube.com/watch?v=Hn4E3fKX7WM
It's a different device, but the same exact steps. He does state that he puts the name of the rom after /sdcard/ in the command, but it's not necessary. Won't make a difference for this.
Okay. That was somewhat helpful. I couldn't find TWRP 2.7.0.5, but I did get 2.7.1.1 and I got it loaded.
I've tried the adb command. It sits there for a long time, then the phone reboots into TWRP. I get no messages back in the terminal window and nothing is loaded into the /sdcard directory (or anywhere else as far as I can tell).
Edit: wait. Formatted it and am going to try again.
Edit 2: loading rom!!!
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
es0tericcha0s said:
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
Click to expand...
Click to collapse
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
chilort said:
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
Click to expand...
Click to collapse
:good::highfive::victory:
es0tericcha0s said:
:good::highfive::victory:
Click to expand...
Click to collapse
Thank you again for walking me through this. It is nice to have my HTC back. My slow, piece of junk work phone can now go back to running BOINC.
No problem. It's how I give back to the community.
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.