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.
I bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
Click to expand...
Click to collapse
Index:
1st post: Root the HTC EVO 3D
2nd post: S-OFF and completely unlock the EVO 3D
Rooting the HTC EVO 3D
When it comes to only rooting the device, it works somewhat as easy as a nexus.
To the users who are already familiar with rooting, the (very) quick instructions are as follows:
► Unlock bootloader from htcdev.com
► Flash custom recovery
► Flash root
►► Easy huh? though so.
Click to expand...
Click to collapse
For the completely unfamiliar users, here's the real deal:
Prerequisites:
► You need ADB and fastboot: get the SDK from HERE that has it all.
► Alternatively: get the portable ADB and fastboot from HERE, but i don't offer support for those. (Thanks for the mysterious user who uploaded them to box).
► You need either 4EXT or CWM recoveries... your choice (thanks @monx®)
► You need the root binary, get SuperSU zip file.
Click to expand...
Click to collapse
Unlock the Bootloader:
► After setting it all up, pick up your EVO 3D, go to settings, development options, and turn on USB Debugging.
► Open up a cmd on PC, and type this:
Code:
adb reboot bootloader
►► This will make the phone reboot to bootloader.
► After it has booted, hit the power button to go to fastboot (don't press and hold, just press a small click)
► If you see FASTBOOT at the top, and not FASTBOOT USB, click the volume buttons to go up and down so that the screen refreshes into FASTBOOT USB at the top... if that makes any sense
► Type this into the cmd:
Code:
fastboot oem get_identifier_token
►► This will give you a bunch of numbers, i can't explain this better than HTCDevs themselves, so go exactly HERE and follow their guide (you need to be signed in to their website to be able to view the instructions)
► So after you hit submit and get the unlock_code.bin do this:
Code:
fastboot flash unlocktoken Unlock_code.bin
►► Again.. HERE is the HTC guide, but in short: after executing this command, use the volume buttons to select yes, and press the power button to select it.
►► I cannot stress this enough... THE ABOVE STEP WILL WIPE ALL OF YOUR DATA!!!... Should i make this a size 7? you won't like it.
Click to expand...
Click to collapse
Flash a custom recovery:
►► You have two options for recoveries here: 4EXT, and CWM (or ClockWorkMod). Personally, i prefer 4EXT.
► Execute this command:
Code:
fastboot flash recovery NAME.img
►► NAME is the actual name of your recovery .img file.
Click to expand...
Click to collapse
R00T!
► You're now in fastboot, highlight bootloader and press the power button
►► You should wait a bit for the unlocked bootloader to make its scans
► Select recovery from there and press the power button to boot to it
► Remember the SuperSU zip file we downloaded earlier? We need to put that on the phone's sdcard. Two ways:
1) Take out the sdcard from the phone, plug it in the PC, and put the zip there
2) Toggle USB storage (for 4EXT) or mount USB storage (for CWM) while plugged in to the PC to access the sdcard from there and put the zip there
► Now hit back till you get to the first menu
► Select install zip from sdcard
► Choose zip from sdcard
► Look for the SuperSu zip file and select it, then hit yes
►► After flashing, comes the REALLY hard part:
► Hit back to the first menu
► Select reboot system now (VERY hard! )
Click to expand...
Click to collapse
You're rooted!
Why another guide? Well... I didn't find any guide that really helped me understand what i should do to update from ICS to JB or KK or whatever... So i started doing things by myself, i did it with 2 3 HTC Evo 3Ds and both worked fine at the end, so i started writing this guide... have fun! Thread also available at rirozizo.blogspot.com (WITH PICTURES!)
Scenario: You're on ICS, latest update, latest bootloader. You're either on stock ROM, or custom ROM. Your bootloader is locked or unlocked. You're S-ON.
Solution: S-OFF your bootloader, downgrade it, get ICS+ ROMs (like JB or KK)
Time to do the process: I did it in 1 Hour 15 Minutes
Requirements: Linux OS (either native, dual booted (ME!), or LiveCD... You pick), HTC Evo 3D, USB Cable (with data transfer support), an internet connection for the downloads, an microSD, and wire.
WARNING: It is important to backup all the contents that are on your microSD before doing anything. I did the wire trick on two Evo 3Ds, and one of them corrupted the microSD, so we had to format it.
Now let's start.
►In Linux, download adb and fastboot using "sudo apt-get install android-tools-adb" and "sudo apt-get install android-tools-fastboot".
►Download THIS flashable root .zip file (don't extract that... please)
►Download juopunutbear's (Call that "juo" ) wire trick script HERE and extract it. (pick the appropriate .tgz file for your device)
►Download a ROM to your liking (ICS, JB, KK, Froyo... you can do anything after this guide )
►Transfer both the ROM and the root to your phone... keep juo on PC
►Go to unlimited.io and learn how to do the wire trick there.
►Download THIS PG86IMG.zip file, DON'T DO ANYTHING TO IT!
Click to expand...
Click to collapse
Note: To flash on Rogers, you can just mod the model ID from PG8630000 to PG8631000 in the zip file, so sometimes you should DO something
Backup if you need to
►►You can backup your apps using any app-backup app, we won't go through it
►►Go to recovery
►Type "adb reboot recovery"
►►Make a NANDROID Backup
►Go to "backup and restore", and backup.
►►It took 733 seconds to finish the huge backup i was doing... so yeah... take a bath or something in the mean time.
►PLEASE, transfer the backups you made to your PC, don't leave them on the microSD just to be on the safe side
Click to expand...
Click to collapse
Get to stock rooted (Skip if you're already on stock)
If you're on a custom ROM, you'll need to flash stock... not just any stock... but RUU stock.
►Get the RUU that is for your phone (you may google that)
►►Here's a tip: type "fastboot getvar all" and look for "(bootloader) version-main:"... check the number next to it, and download the RUU that has that number.
Now flash RUU... flash? yes... FLASH!! How? via fastboot... What? Yes!
►Get to fastboot (turn the phone off, hold power and volume down), plug it in the PC
►Type this in a terminal "fastboot oem lock"
►►Now your bootloader is locked, we can flash RUU
►Open up the RUU.exe from windows
►Hit next two times (you're gonna have to check some checkboxes too), and leave it open
►►Don't start any process from it, just keep it there
►Open a file explorer (Like My Computer, or whatever...)
►Type in the path textbox "%TEMP%"
►Sort the files by "date modified" and open the first folder you see there
►►You'll see a bunch of files there, and probably a folder too
►Look for "rom.zip" (you might even go to that folder too to check inside it)
►Copy "rom.zip" to somewhere easily accessible
►►Now back to linux
►Type "fastboot erase cache"
►Once that's done type "fastboot oem rebootRUU"
►►You'll see a black screen with a silver HTC in the middle
►Type "fastboot flash zip X" where X is the path to the rom.zip file we got earlier.
►Now leave it there
►►It took me 426.617 seconds for the process to finish... you may go eat something... maybe relax in the bathroom if you want
►►Now once the terminal says it's done, you might see the HTC green progress bar stuck at 95%... don't worry, it's nothing... it's a bug in RUU mode, so just type "fastboot reboot" and you'll reboot to stock ROM.
Click to expand...
Click to collapse
I'm on stock ROM... now what?
ROOT DAT STOCK! (Optional, but i did it just in case)
►►So now we need to root the stock ROM we have.
►►To root, we need to unlock bootloader first.
►Go to htcdev.com and follow the guide there to unlock your bootloader
►Once that's done, download THIS recovery and flash in fastboot it using "fastboot flash recovery cwm.img"
►Once that's done, hit "BOOTLOADER" in the list (using the power button), wait for about 5 seconds, then hit "RECOVERY"
►►You're now in CWM recovery.
►►Now that you're inside the recovery, volume up is up, volume down is down, power is enter
►Go to install zip from sdcard
►Choose zip from sdcard
►Locate the root .zip file we transfered earlier
►Hit the "yes" button hidden between these "no no no" buttons
►►You might want to repeat the flashing process if it gives an error... Second time is guaranteed to work
►►You're now rooted.
►"***Go back***" to the first menu, and "reboot system now".
Click to expand...
Click to collapse
S-OFF
►Once booted, go to settings, developer options, and enable USB debugging there
►Then in linux, navigate to where we extracted juo's zip, and open a terminal there
►Type these commands "chmod 755 ControlBear" and hit enter
►The type "./ControlBear" and hit enter
►►Now it'll guide you through... it keeps saying "beer beer"... yeah... the dev likes to have fun, like me
►When it says "Do the wire trick now" do it (using unlimited.io's guide).
Click to expand...
Click to collapse
IMPORTANT: If the script errors out with a "Still sober" error... just redo the script, it'll succeed then...
FINALLY, YOU ARE S-OFFed... too much caps huh? oh well... It was a long process... you can start feel the sense of accomplishment there.
Downgrade to BL 1.49
►►Now to downgrade bootloader to 1.49....
►►Remember that PG86IMG.zip file?
►Put it on the root of your sdcard (so don't put it inside any folder)
►Boot to bootloader
►Press BOOTLOADER button...
►Now we wait until the installation is finished... of course, press YES when it says so.
►►You're now on bootloader 1.49, S-OFFed, and with a custom recovery...
Click to expand...
Click to collapse
Well? What are you waiting for? Go flash a Kitkat ROM! GO!!
NOTE: You might wanna get 4EXT recovery to be able to flash kitkat ROMs, good luck!
If you're already on ics you don't need to flash ruu.
For the wire trick it's not necessary to root the device.
All you have to do before is to unlock via htcdev.
For downgrading I'd recommend juopunutbear gb hboot from their site.
tom0769 said:
If you're already on ics you don't need to flash ruu.
For the wire trick it's not necessary to root the device.
All you have to do before is to unlock via htcdev.
For downgrading I'd recommend juopunutbear gb hboot from their site.
Click to expand...
Click to collapse
you need to be on full stock for juopunutbear to work, otherwise it'll say be on stock...
you need to be rooted for juopunutbear to work, otherwise it'll say be rooted...
and i think the script os different between ICS and GB... not just hboot... meh
Sent from my Nexus 4
Good but if you want KK ROM, you must use the latest 4EXT recovery touch, otherwise it will fail
Also this recovery is much easier for use then CWM
Benik3 said:
Good but if you want KK ROM, you must use the latest 4EXT recovery touch, otherwise it will fail
Also this recovery is much easier for use then CWM
Click to expand...
Click to collapse
oh? didn't know that thanks!
I'll update the guide as soon as i can (fix links and add 4EXT)
Sent from my Nexus 4
rirozizo said:
you need to be on full stock for juopunutbear to work, otherwise it'll say be on stock...
you need to be rooted for juopunutbear to work, otherwise it'll say be rooted...
and i think the script os different between ICS and GB... not just hboot... meh
Sent from my Nexus 4
Click to expand...
Click to collapse
In the OP you stated "Scenario: You're on ICS, latest update, latest bootloader", so I'd assume it's already stock ICS.
I did the wire trick on 2 EVOs, just unlocked, not rooted (as stated on juopunut site).
The gb hboot I mentioned is the 1.49.9999 hboot (look here) for downgrading afterwards.
tom0769 said:
In the OP you stated "Scenario: You're on ICS, latest update, latest bootloader", so I'd assume it's already stock ICS.
I did the wire trick on 2 EVOs, just unlocked, not rooted (as stated on juopunut site).
The gb hboot I mentioned is the 1.49.9999 hboot (look here) for downgrading afterwards.
Click to expand...
Click to collapse
i S-OFFed two EVOs, both were on KingCobra ICS ROM... so don't assume stock...
Sent from my Nexus 4
rirozizo said:
i S-OFFed two EVOs, both were on KingCobra ICS ROM... so don't assume stock...
Sent from my Nexus 4
Click to expand...
Click to collapse
Yep, but if someone is already on stock, he could skip the ruu step.
Also it's not necessary to root the stock rom when you want to flash a custom rom that is already rooted.
I did the steps as follows (in short):
- unlock bootloader (the htcdev method)
- do the wire trick (controlbear)
- flash the juopunutbear hboot in fastboot (1.49.9999)
- flash the recovery image in fastboot (latest 4ext)
- flsh any custom rom
Starting point on both phones was stock ics locked, s-on, hboot 1.53.0007
Don't get me wrong, I only wanted to help to get your guide a little leaner.
tom0769 said:
Yep, but if someone is already on stock, he could skip the ruu step.
Also it's not necessary to root the stock rom when you want to flash a custom rom that is already rooted.
I did the steps as follows (in short):
- unlock bootloader (the htcdev method)
- do the wire trick (controlbear)
- flash the juopunutbear hboot in fastboot (1.49.9999)
- flash the recovery image in fastboot (latest 4ext)
- flsh any custom rom
Starting point on both phones was stock ics locked, s-on, hboot 1.53.0007
Don't get me wrong, I only wanted to help to get your guide a little leaner.
Click to expand...
Click to collapse
yeah yeah sure, I'm not getting you wrong...
I'll update the guide soon, I'll add "optional" after the stock title... and add "optional" after rooting (that's what i did so i think I'll just keep it)
thanks for the help
Sent from my Nexus 4
rirozizo said:
i S-OFFed two EVOs, both were on KingCobra ICS ROM... so don't assume stock...
Sent from my Nexus 4
Click to expand...
Click to collapse
Yup i even S-Off from mwakious3Drom® ROM! I tried and thank god it worked as getting back to stock was too much of a trouble lol.
Oh and about 4EXT recovery yes you do need the latest as i couldn't instal the Cyanogenmod 4.4 without the latest update.
If i downgrade to 1.49 with this - HTC EVO 3D GSM (shooteru) GB HBOOT - 1.49.9999 , what version do i need to choose on revolutionary website 1,49,0007 or 1,49,0008
g3ar said:
If i downgrade to 1.49 with this - HTC EVO 3D GSM (shooteru) GB HBOOT - 1.49.9999 , what version do i need to choose on revolutionary website 1,49,0007 or 1,49,0008
Click to expand...
Click to collapse
there was no mention of revolutionary in this guide
ye.. my fault i read it few times and then i understand what i need to do and how
tom0769 said:
Yep, but if someone is already on stock, he could skip the ruu step.
Also it's not necessary to root the stock rom when you want to flash a custom rom that is already rooted.
I did the steps as follows (in short):
- unlock bootloader (the htcdev method)
- do the wire trick (controlbear)
- flash the juopunutbear hboot in fastboot (1.49.9999)
- flash the recovery image in fastboot (latest 4ext)
- flsh any custom rom
Starting point on both phones was stock ics locked, s-on, hboot 1.53.0007
Don't get me wrong, I only wanted to help to get your guide a little leaner.
Click to expand...
Click to collapse
I followed these steps, everything was a success, but i m having problem flashing recovery image in fastboot? 4ext? I cannot seem to find this file i need? Other i have tried just hangs. It says my device is not rooted. So do i need to flash recovery before it' rooted?
Thanks.
rethan2 said:
I followed these steps, everything was a success, but i m having problem flashing recovery image in fastboot? 4ext? I cannot seem to find this file i need? Other i have tried just hangs. It says my device is not rooted. So do i need to flash recovery before it' rooted?
Thanks.
Click to expand...
Click to collapse
Here you can find the latest 4ext. Flash it and you can install every rom. Root is not required because all custom roms are pre-rooted.
Code:
fastboot flash recovery 4EXT_Recovery_Touch_v1.0.0.6_RC1.img
Sent from my Evo 3D
mhnx said:
Here you can find the latest 4ext. Flash it and you can install every rom. Root is not required because all custom roms are pre-rooted.
Code:
fastboot flash recovery 4EXT_Recovery_Touch_v1.0.0.6_RC1.img
Sent from my Evo 3D
Click to expand...
Click to collapse
OK thanks a mil, sorted now!
Can i do this in windows? i don't have other pc with linux or something like that...
XeNNz said:
Can i do this in windows? i don't have other pc with linux or something like that...
Click to expand...
Click to collapse
you're gonna have a bad time:
-juo dropped support for windows
-windows needs drivers... they act weird on fastboot
-a VM won't do too as the drivers of windows will be needed... which act weird
Sent from my Nexus 4
So..i have to give up. Thank you for fast reply !
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.