I find it hard to believe that there is no step-by-step out there, so I'm just going to assume that I'm really bad at internet searching and apologize for posting a question that surely must be answered somewhere out there...
I ultimately want to try out the newest ICS leak (depending on whether Flash works on it?), but it seems that the best first step is to get S-Off on my rooted, stock Gingerbread Rezound.
But I can't find a simple step-by-step instruction set anywhere... Can anyone point me in the right direction?
I downloaded a toolkit from hasoon2000 that's supposed to make things easy, but I don't know what to do with it.
hasoon2000 links to instructions that only show a video and assume I know how to use something called Juopunutbear(?).
It seems that every tidbit of information I can find is only partial...
Where can I find a step-by-step, beginning-to-end guide to get S-Off for a rooted Rezound? Am I missing something?
Prerequisites
- Must be on a stock Gingerbread ROM OR The 3.14.605.5 ICS Leak <---- NO OTHER ICS LEAKS BUT THIS ONE!
- Must be HTCDev unlocked
- Must be rooted
1. Install HTC Drivers
2. Go to www.HTCDev.com
2a. Follow instructions and unlock your bootloader/Device.
2b. flash a rooted rom/gain root access
3. Get a fresh microSD card or backup yours because s-off will delete everything on it.
4. After unlocking run the toolkit which will push you through s-off(Juno-w/e)
4a. Get a length of insulated wire about 8 or so inches, then when the Toolkit cmd prompt says to, ground it outThe pins you touch are in this picture.
5. If it worked, you'll be s-off'd, install a recovery & rom.
If still confused just ask, I'll try my best to walk you through it.
http://forum.xda-developers.com/showthread.php?t=1612035
The instructions are detailed on the unlimited.io site...
Sent from my ADR6425LVW using Tapatalk 2
When we speak of this "leak" for the rezound that means that we took ics 4.0 from another phone and ported it over.. so what is the leak vs porting it. When rezoind does finally get our 4.0 update , what perks will that bring us even though we have the "leak" or "port" ...we will be able to have aosp roms right
Sent from my ADR6425LVW using Tapatalk 2
SR3TLAW said:
When we speak of this "leak" for the rezound that means that we took ics 4.0 from another phone and ported it over.. so what is the leak vs porting it. When rezoind does finally get our 4.0 update , what perks will that bring us even though we have the "leak" or "port" ...we will be able to have aosp roms right
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but the leaks are not ported and they ARE for the Rezound. When the ota comes, I don't think it will be much different from what we have now (3.14.605.10).
I believe the source will have to be dropped for AOSP.
SR3TLAW said:
When we speak of this "leak" for the rezound that means that we took ics 4.0 from another phone and ported it over.. so what is the leak vs porting it. When rezoind does finally get our 4.0 update , what perks will that bring us even though we have the "leak" or "port" ...we will be able to have aosp roms right
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
The Rezound is getting Sense 3.6 with it's OTA update, the newer HTC ICS based phones are getting Sense 4.0.
The leaks are Sense 3.6 builds specific for the Rezound, the ports are Sense 4.0 based roms for other phones made to work on the Rezound.
So what exactly is the benefit to S-OFF? I tried to do it, but bricked my rezound. Luckily, Verizon exchanged it as DOA, and so I'm all good for now.
d.kozzer said:
So what exactly is the benefit to S-OFF? I tried to do it, but bricked my rezound. Luckily, Verizon exchanged it as DOA, and so I'm all good for now.
Click to expand...
Click to collapse
Easier flashing (don't have to create a ph98img.zip file any more) edit boot screen (my favorite reason) and be able to flash between different firmwares (this is a big deal).
Hmmm. Well, I've done all that with S-ON. I've got a custom ROM, custom recovery, custom boot animation (a JB one posted somewhere on this site), and the ICS leaked firmware. I don't remember using PH98IMG.ZIP (rather it was other zips), though I was pretty excited to play with a new phone, so I could be forgetting. Actually, now that I'm thinking more on it, I did flash the PH98IMG.ZIP when I put CleanROM on the phone, and so I suppose that also put the updated firmware on it.
d.kozzer said:
So what exactly is the benefit to S-OFF? I tried to do it, but bricked my rezound. Luckily, Verizon exchanged it as DOA, and so I'm all good for now.
Click to expand...
Click to collapse
The ability to do Nandroid restores and have it flash the boot.img without needing any help scripts or doing it manually via fastboot was my main reason for doing it..
d.kozzer said:
Hmmm. Well, I've done all that with S-ON. I've got a custom ROM, custom recovery, custom boot animation (a JB one posted somewhere on this site), and the ICS leaked firmware. I don't remember using PH98IMG.ZIP (rather it was other zips), though I was pretty excited to play with a new phone, so I could be forgetting. Actually, now that I'm thinking more on it, I did flash the PH98IMG.ZIP when I put CleanROM on the phone, and so I suppose that also put the updated firmware on it.
Click to expand...
Click to collapse
By "edit boot screen" he meant the splash screen before the boot animation (the blindingly bright white HTC screen). This can't be changed without having S-OFF.
The PH98IMG.zip you flashed with CleanROM was to update the kernel, not your firmware. Since you are S-ON, it won't install the boot.img in recovery during the ROM flash, so it uses a separate file to flash it in the bootloader. Otherwise, no boot.img = phone isn't booting (obviously).
Sent from my ADR6425LVW using XDA Premium.
To have call recording capabilities I would have to have s off becuae to record a call without an app depends on the kernel correct.
Sent from my ADR6425LVW using Tapatalk 2
I used the control bear s off tool tonight, after many, many...many times I finally got s-off. But now the only thing I have is the modified boot loader. I tried too use adb to push recovery and boot images and it would say success, but would actually never boot into them, it would just stay on the white and green HTC screen. Any help is appreciated of course, I just need to get booted up.
BOOT LOADER INFO:
JuopunutBear
Vigor Pvt ship s off rl
Hboot 2.21.21
Radio 0.95.00.1118r/0.95.00.1223r
OpenDSP v10.6.0.7611.00.0919
emmc boot
March 11 2012 22:16:16
Sent from my SPH-L710 using xda app-developers app
use laptop [for max safety so u wont get electric blackout]
flash scrosler Rooted ics rom
put empty sdcard
install htc drivers on stable windows 7 without virus or heavy apps running
make sure usb debugging is ON
remove sim
get a insulated wire with out strings
start the s-off by hansson [HTC Rezound S-Off All-In-One Toolkit v1.0]
use the wire when u told so
if u dont want to install the modded hboot so unlock it then flash recovery
Done
Proz00 said:
use laptop
use the wire when u told so
if u dont want to install the modded hboot so unlock it then flash recovery
Done
Click to expand...
Click to collapse
IMHO...no need to unlock it, so keep it locked.
tynan
Fortunately, I'm starting with a rooted Rezound already.
3. Blank microSD is no problem.
4. I don't know what "run the toolkit" means... or what "Juno" means. The top middle button of the toolkit I downloaded just refers me to webpages with confusing instructions and a broken video link (found the video elsewhere). I don't know which toolkit button I'm supposed to push, and nothing tells me which one helps me get S-Off. So... This is where I'm stuck.
killerb777
I'm sure the correct info is at that link, but there's so much information... And it seems like everyone refers to the same things by different names? ... JuopunutBear? ControlBear? But I'm not sure? It just isn't written for people who don't understand this stuff...
everyone
Thanks for taking a few moments to help me out with this, everyone.
bloodymurderlive said:
tynan
Fortunately, I'm starting with a rooted Rezound already.
3. Blank microSD is no problem.
4. I don't know what "run the toolkit" means... or what "Juno" means. The top middle button of the toolkit I downloaded just refers me to webpages with confusing instructions and a broken video link (found the video elsewhere). I don't know which toolkit button I'm supposed to push, and nothing tells me which one helps me get S-Off. So... This is where I'm stuck.
killerb777
I'm sure the correct info is at that link, but there's so much information... And it seems like everyone refers to the same things by different names? ... JuopunutBear? ControlBear? But I'm not sure? It just isn't written for people who don't understand this stuff...
everyone
Thanks for taking a few moments to help me out with this, everyone.
Click to expand...
Click to collapse
ON the toolkit...isn't there a "Run Juopunutbear V.6If....." in the left hand box? Run the one that corresponds to the firmware you have. You have GB so run the first one. Make sure you have read and know how to do the wire trick.
JuopunutBear is the name of the group that developed the s-off process...ControlBear is the name of the program file that is run to achieve it. Hansoons tool apparently downloads the programs you need to do everything. Follow the steps.
If you don't understand the terms bootloader, hboot, recovery..Read up on them here: http://forum.xda-developers.com/showthread.php?t=1641670
Don't worry about flashing a new hboot, just keep the one you have when you're done.
Also, I found it helpful to have a computer that could read the SD card. Just in case you need to download something to it for you phone.
Thanks for the update... So here are the simple instructions I'm following now:
1. - 2. Root device.
3. Backup microSD.
4. Select "Run Juopunutbear v.6 If You Are On Gingerbread" in Hasoon2000's S-Off toolkit, then click Run
5. Use insulated wire to connect Pin 1 and GND for two seconds when cmd prompt says "Do wire-trick now!! Look instructions at web"
... So what happens next? Does my device reboot as usual? Do I have to re-unlock? Re-root? Re-install amon recovery? In other words... Did it change anything other than giving me S-Off and wiping the microSD card?
bloodymurderlive said:
Thanks for the update... So here are the simple instructions I'm following now:
1. - 2. Root device.
3. Backup microSD.
4. Select "Run Juopunutbear v.6 If You Are On Gingerbread" in Hasoon2000's S-Off toolkit, then click Run
5. Use insulated wire to connect Pin 1 and GND for two seconds when cmd prompt says "Do wire-trick now!! Look instructions at web"
... So what happens next? Does my device reboot as usual? Do I have to re-unlock? Re-root? Re-install amon recovery? In other words... Did it change anything other than giving me S-Off and wiping the microSD card?
Click to expand...
Click to collapse
Getting there.
The wire trick..DON'T touch the contacts for 2 seconds. Touch them TWICE in 1.75 seconds. Example...touch..1.75s......touch.... Hold the wire firmly down in the hole to insure contact and just touch the gnd twice.
AFter, you do have to reinstall amon recovery...DON"T UNLOCK... no reason to. Again, it is a good backup to have a SD card reader available.
EDIT: If you want to be able to use fastboot commands after, then you do need to flash the Joupunut Hboot that is offered to you at the end of the process. I didn't. I just find flashable files for my needs.
Related
Well the title speaks for itself, this is my first thread on these forums, hope its in the rights section.
So, like the title asks...
How many people on hboot 1.5 have sucessfully done the Juopunutbear S-OFF mod? If you have is it worth it and do you think its really hard to do?
I only ask because the directions seem short, simple, and to the point.
Am I okay starting out with MeanROMICS 1.4?
How do I know what file download is appropriate for me (the thread in this section states .05 is good but the instructions on juopunutbears site say .01)?
And lastly on the unlimited.io page under the hboot downloads section, do i need any of these files and how do i distinguish the difference?
me
i did. heeeelllllaaaaaaa easy. even better is i recovered fully from VM firmware. now im rocking hboot eng 1.4.200. only thing with jupwhateverabear is the instructions dont prepare you for it asking if you want custom jphboot. i said no. ended up saying soff locked 1.5, then i used the jphboot and it said jupowhateverabear but didnt say whether it was locked or unlocked or relocked. now with hbooteng the line where all that crap would be isnt even there.
bdubble said:
i did. heeeelllllaaaaaaa easy. even better is i recovered fully from VM firmware. now im rocking hboot eng 1.4.200. only thing with jupwhateverabear is the instructions dont prepare you for it asking if you want custom jphboot. i said no. ended up saying soff locked 1.5, then i used the jphboot and it said jupowhateverabear but didnt say whether it was locked or unlocked or relocked. now with hbooteng the line where all that crap would be isnt even there.
Click to expand...
Click to collapse
great but why would i want the VM firmware? isnt the whole point of the juopunutbear thing to keep hboot 1.5 but with s-off?
I did it and it works. I extracted the files needed for the process, put it on my desktop, and followed the directions. I also watched a YouTube video on how they did the same steps on a HTC Amaze, so it was simple. I used a coaxial cable to do the process, shaped it as a "U" shape, then performed the steps. Did not brick my phone and only did it in one try.
right so what do i do with the extracted files besides the .exe?
theres the .img, .zip, and two .txt
typically you use the .img with fastboot and the .zip in recovery for a flash install but i dont see those steps in the instructions at all.
cowboyaryk said:
right so what do i do with the extracted files besides the .exe?
theres the .img, .zip, and two .txt
typically you use the .img with fastboot and the .zip in recovery for a flash install but i dont see those steps in the instructions at all.
Click to expand...
Click to collapse
The way I did was to create a folder on the desktop. Then put all of the files inside the folder. I opened the exe and made sure my phone was on fastboot usb. Then wait until it tells you to do the wire trick. The wire trick is all about timing. If it fails the first time, just run the program again. That's how I did it.
so you did nothing with the other four files? ran the exe and it took care of the rest?
cowboyaryk said:
so you did nothing with the other four files? ran the exe and it took care of the rest?
Click to expand...
Click to collapse
Yes. I also used a spare SD card I had laying around that got corrupted but I did not want to use my 16 GB card, so I swapped SD cards. You can later format it if you like. Just follow the instructions on the website and you should be fine.
i could just backup my SD card and use the one i have? or will it ruin it? or could i just use NO SD card?
cowboyaryk said:
i could just backup my SD card and use the one i have? or will it ruin it? or could i just use NO SD card?
Click to expand...
Click to collapse
You can also backup your SD card so you won't lose anything important. I was skeptic at first, but I was getting tired of flashing roms through fastboot. So I saw the opportunity and went for it. Honestly, I recommend using a spare SD card (does not matter the size) because it will create a backup in the SD card.
I did it with SOS Rom. Issues afterwards, can't download anything over 1g to my sd card through USB and can't load custom kernels or kernels found in roms though fastboot or other recoveries or flash image GUI. I am s off now. Could be because I used a non gb Rom or stock one. I take the blame, just learn from my stupidity. Going to try to unroot and try again tomorrow
Sent from my PG86100 using XDA
Nametaken said:
I did it with SOS Rom. Issues afterwards, can't download anything over 1g to my sd card through USB and can't load custom kernels or kernels found in roms though fastboot or other recoveries or flash image GUI. I am s off now. Could be because I used a non gb Rom or stock one. I take the blame, just learn from my stupidity. Going to try to unroot and try again tomorrow
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
That's weird. I was on SOS rom before I did the steps. Once I was done, I flashed the SOS rom again with no issues. The only difference I've made was to use fastboot to get to the revolutionary recovery to reflash the SOS rom again.
I did it, process was simple, I chose to install the optional hboot
Sent from my EVO One 3D using the XDA Premium App.
cowboyaryk said:
i could just backup my SD card and use the one i have? or will it ruin it? or could i just use NO SD card?
Click to expand...
Click to collapse
Super small chance it won't get cleaned out, but totally use another card. Pretty sure you need to have a card in there. I don't dare take chances anymore LOL
Sent from my PG86100 using XDA
Not the right section to put this.
I successfully got S-OFF from a stock rom after a couple tries i admit. And yes, the instructions are a bot short. I even searched for this "instructional video" that it mentions. The only video was for the Amaze, i believe. But, still the same method of execution. And first, you must make a backup of your SD Card if you want anything on it. Just backup the whole thing. I did notice that the Juopunutbear method did something to me SD card, it was salvageable after a format tho.
Gotta mention, the first time I tried this (unsuccessfully), when I booted up because I had given up, I noticed that I got caught in a boot loop. Every time ending up at the juopunutbear screen. Then I got scared, only to madly search how to get OUT of a boot loop, of which I thought I bricked it. And let me tell you it is possible to get out of it. I'll try and get the site I found up.
After I finally got back to stock I successfully tried the Juopunutbear method, along with the wire-trick and finally got it up. I tried to mimic the video to get the right number of taps and length of time that you need to make contact with the ground. It finally worked and it's freakin awesome. Been waiting a long time for someone to find out this hboot 1.5 problem.
This is not the proper place to put this better to put this in the already started thread for Juopunutbear or possibly even General or something. There is no development being made in this thread.
Overall I find the wire trick less invasive and less of a hassle then the whole downgrade, brick, update, process. No offence to the guys that designed the process. Because I'm sure it took more than their brains to do but personally, I like the combination of hardware / software hacking.
+1 for the wire trick S-OFF trick
Sent from my PG86100 using Tapatalk 2
Me! Easier than rooting. Except the wire trick. Took me 20 minutes
Sent from my PG86100 using xda premium
Can't quite get it....
Everyone else seems to do this with no problems, but this is my first root. Well im following this particular guide: http://forum.xda-developers.com/showthread.php?t=1813818 and have done everything up to completing the wire trick. When I run ControlBear.exe the phone boots up then the cmd window says "second backup failed immediately" and no options ever pop up on the screen on my phone. Can anyone propose a solution? Since this is my first time rooting, it could be a stupid noob mistake but for the life of me its killing me to be so close yet so far to soff.
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
Hi, everyone. I hope someone can answer my questions or point me to the thread with the answer to it. Below is the information for my Spint Evo 3D running stock ROM:
Shooter XC Ship S-off RL
HBoot 1.40.1100
Android 2.3.4
HTC Sense 3.0
Software: Shooter_S_Sprint_WWE_2.17.651.5_odex
The last time I did an update of my phone after rooting was early this year. Basically I installed a zipfile provided by a user on this forum (apologize to that user for not being able to credit him) that allows me to get the OTA update on my rooted phone. Now that Sprint released the Ice Cream Sandwich update for EVO 3D, I am looking to upgrade the software again. The main question is...was there a thread for this topic where someone has provided a zipfile to allow updates to ICS for a rooted phone (stock rom)? Would someone please point me to it if they found it (sorry, did not see it)? Second, is the update process the same as before? Do I wipe cache and/or dalvik cache and then just install from zipfile? Any help is appreciated. Just didn't want to brick my phone. Normally I let my sister test things out on her device before I do the same thing but last year she decided to go with Motorola Photon while I sticked with HTC. Help? Thanks.
Tommy
xionchen4628 said:
Hi, everyone. I hope someone can answer my questions or point me to the thread with the answer to it. Below is the information for my Spint Evo 3D running stock ROM:
Shooter XC Ship S-off RL
HBoot 1.40.1100
Android 2.3.4
HTC Sense 3.0
Software: Shooter_S_Sprint_WWE_2.17.651.5_odex
The last time I did an update of my phone after rooting was early this year. Basically I installed a zipfile provided by a user on this forum (apologize to that user for not being able to credit him) that allows me to get the OTA update on my rooted phone. Now that Sprint released the Ice Cream Sandwich update for EVO 3D, I am looking to upgrade the software again. The main question is...was there a thread for this topic where someone has provided a zipfile to allow updates to ICS for a rooted phone (stock rom)? Would someone please point me to it if they found it (sorry, did not see it)? Second, is the update process the same as before? Do I wipe cache and/or dalvik cache and then just install from zipfile? Any help is appreciated. Just didn't want to brick my phone. Normally I let my sister test things out on her device before I do the same thing but last year she decided to go with Motorola Photon while I sticked with HTC. Help? Thanks.
Tommy
Click to expand...
Click to collapse
That's simple mate, but you will lose, recovery and root, I can help get them back, but first you will need to flash this http://cmw.22aaf3.com/shooter/radio/1.09.00.0706/PG86IMG.zip by placing on your sd card root directory and booting into bootloader and then following on screen instructions
gav-collins1983 said:
That's simple mate, but you will lose, recovery and root, I can help get them back, but first you will need to flash this http://cmw.22aaf3.com/shooter/radio/1.09.00.0706/PG86IMG.zip by placing on your sd card root directory and booting into bootloader and then following on screen instructions
Click to expand...
Click to collapse
Hi. Thanks for replying. Please bear with me as I am more of a casual user who barely have any inkling of why he is doing something, only how to get to S-Off, rooted through developers who provided step-by-step guide for "Dummies who want to Root their Phone". I have been in contact with Ramjet73 who is really kind to answer my questions but I am trying not to bother him too much hence I am trying to pass on any further questions that I have to other users such as yourself. So...thank you in advance.
From what Ramjet73 told me, I can just run the RUU.exe for 2.89.651.2 (Sprint ICS build) since I am S-Off. However he then inform me that I need to download a custom bootloader and custom recovery. This supports your comments that I will lose recovery and root after update? Ramjet 73 suggested a custom bootloader from ENG or JBear. How is that different from the bootloader that you suggested in your reply?
I assume that after I update both the ICS RUU and the custom bootloader, I will remain S-Off and rooted with superuser status and apps such as titanium backup and wifi tethering operational?
As for custom recovery, Ramjet 73 suggested 4Ext Recovery which I assume is 4Ext Recovery Updater (if I want a free version) or 4Ext Recovery Control if I am willing to pay for more options. Now in the past, I haven't really install any custom recovery other than what was installed when I used Revolutionary's tool to turn my phone to S-Off. I believe that installed Clockworkmod which I access when I boot to it using Power+Vol Down. Is Rom Manager the newest equivalent to that? What is your opinion on 4Ext Recovery vs Rom Manager.
So to summarize, I run the RUU.exe for ICS upgrade. Then I flash a bootloader like you recommended in your reply or one of the custom bootloaders from ENG or JBear. Then flash a custom recovery and I am all set? Sorry for all these questions and I hope you can help. Thanks.
I'm looking for a cut and dry answer to this as well. I'll be monitoring this and if I see or figure out anything first ill post here.
Sent from my EVO using xda premium
sullivan7221 said:
I'm looking for a cut and dry answer to this as well. I'll be monitoring this and if I see or figure out anything first ill post here.
Click to expand...
Click to collapse
I thought I made it as "cut and dry" as possible:
1. Flash the 2.89.651.2 RUU (.exe from Windows or .zip from the bootloader if you prefer that)
2. Flash the JBear Sprint ICS (1.58.5858) bootloader so you can use fastboot commands
3. Flash 4EXT recovery using the "fastboot flash recovery recovery.img" command
4. Flash the superuser.zip of your choice or a custom rooted rom from 4EXT
I have more detailed instructions in my guide and a single download with the software you need for each of these steps.
Is there something that you don't understand about these steps, or are you just waiting for someone else to confirm that they work?
Edit: If you are looking for another way to do it you can follow the steps in this post, but you will wind up with the stock 1.58 bootloader and won't be able to run most fastboot commands unless you flash a custom bootloader. It takes about as long to flash the firmware, superwipe and ROM in that post and still flash a custom bootloader as it does to perform the above 4 steps, which I believe give you a cleaner ICS base, but it's up to you. That option will save you from having to reflash recovery.
ramjet73
Hi, sorry if I sound like I am doubting you. Your method are pretty simple. Being a relative newbie who rarely tinker with his phone, I am being extra careful to make sure I understand everything before doing something. In any case, I am going to just do it following your procedure. Just downloaded the QADERSO.zip from your guide. I will follow the 4 steps below. If I encounter any problems, then I hope you or other knowledgeable members of the forum can help out. If everything works out great, I will also post to this thread. Thanks.
ramjet73 said:
I thought I made it as "cut and dry" as possible:
1. Flash the 2.89.651.2 RUU (.exe from Windows or .zip from the bootloader if you prefer that)
2. Flash the JBear Sprint ICS (1.58.5858) bootloader so you can use fastboot commands
3. Flash 4EXT recovery using the "fastboot flash recovery recovery.img" command
4. Flash the superuser.zip of your choice or a custom rooted rom from 4EXT
I have more detailed instructions in my guide and a single download with the software you need for each of these steps.
Is there something that you don't understand about these steps, or are you just waiting for someone else to confirm that they work?
Edit: If you are looking for another way to do it you can follow the steps in this post, but you will wind up with the stock 1.58 bootloader and won't be able to run most fastboot commands unless you flash a custom bootloader. It takes about as long to flash the firmware, superwipe and ROM in that post and still flash a custom bootloader as it does to perform the above 4 steps, which I believe give you a cleaner ICS base, but it's up to you. That option will save you from having to reflash recovery.
ramjet73
Click to expand...
Click to collapse
xionchen4628 said:
Hi, sorry if I sound like I am doubting you. Your method are pretty simple. Being a relative newbie who rarely tinker with his phone, I am being extra careful to make sure I understand everything before doing something. In any case, I am going to just do it following your procedure. Just downloaded the QADERSO.zip from your guide. I will follow the 4 steps below. If I encounter any problems, then I hope you or other knowledgeable members of the forum can help out. If everything works out great, I will also post to this thread. Thanks.
Click to expand...
Click to collapse
No problem.
I was actually responding to sullivan7221 because I thought all his questions were answered in my guide thread and then I saw his post in this thread that seems to be asking the same things. It's no problem if he wants consensus from more people, but I did take exception to his reference to a "cut and dry answer". I know that Samsung and other brands have simpler "one click" processes for rooting because I've used them myself, but I've tried to refine and simplify the root and S-OFF process for the Evo 3D as much as possible, and I tested a "one click" root utility that popped up in this forum a few weeks ago and it didn't work.
I understand that you and sullivan7221 aren't looking for root and S-OFF since you both have that already, but it's still important to use a reliable and consistent method for upgrading to the offical Sprint ICS build, which may not be the easiest.
Good luck with your upgrade!
ramjet73
Well...HELP! I successfully update my phone to ICS (not so hard). Then I hit the wall called "Step 2" and promptly bounced right off on my ass. The first thing I try to do was flash the jb_boot.img through fastboot cmd. I put my phone (which is still S-Off like you said, H-Boot 1.58 with "Locked" all the way up top) into Fastboot then connected my phone to usb, resulting in Fastboot USB. Then I use the command "Fastboot flash boot jb_boot.img". Then the problem happened. It said:
writing 'boot'
failed (remote: not allowed)
From discussions online, I also checked to see if it sees my device using 'fastboot devices" and it seems to recognize it: "HT179..."
How do I unlock my bootloader? What did I do wrong? I have the jb_boot.img and jb_boot.zip from your file and the pg86img.zip that was recommended by the poster above containing a radio.img. Any other way to flash it?
Help?
ramjet73 said:
No problem.
I was actually responding to sullivan7221 because I thought all his questions were answered in my guide thread and then I saw his post in this thread that seems to be asking the same things. It's no problem if he wants consensus from more people, but I did take exception to his reference to a "cut and dry answer". I know that Samsung and other brands have simpler "one click" processes for rooting because I've used them myself, but I've tried to refine and simplify the root and S-OFF process for the Evo 3D as much as possible, and I tested a "one click" root utility that popped up in this forum a few weeks ago and it didn't work.
I understand that you and sullivan7221 aren't looking for root and S-OFF since you both have that already, but it's still important to use a reliable and consistent method for upgrading to the offical Sprint ICS build, which may not be the easiest.
Good luck with your upgrade!
ramjet73
Click to expand...
Click to collapse
Well...color me stupid (and an ass) for not reading in depth ramjet's guide. From ramjet's guide, I went to mpgrimm2's "Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 9-25-12" thread which eventually lead to ramjet's post with all the different bootloaders available. As suggested, I used JB's ICS bootloader and now in the bootloader page, it no longer say "locked" but "JuopunutBear" now. Onto flashing recovery.
xionchen4628 said:
Well...HELP! I successfully update my phone to ICS (not so hard). Then I hit the wall called "Step 2" and promptly bounced right off on my ass. The first thing I try to do was flash the jb_boot.img through fastboot cmd. I put my phone (which is still S-Off like you said, H-Boot 1.58 with "Locked" all the way up top) into Fastboot then connected my phone to usb, resulting in Fastboot USB. Then I use the command "Fastboot flash boot jb_boot.img". Then the problem happened. It said:
writing 'boot'
failed (remote: not allowed)
From discussions online, I also checked to see if it sees my device using 'fastboot devices" and it seems to recognize it: "HT179..."
How do I unlock my bootloader? What did I do wrong? I have the jb_boot.img and jb_boot.zip from your file and the pg86img.zip that was recommended by the poster above containing a radio.img. Any other way to flash it?
Help?
Click to expand...
Click to collapse
Okay, final update for those looking at this thread. I now have stock ICS, remained S-OFF and have superuser access. Basically I followed ramjet who was helping me out. The first thing that someone in my same position who wants to do the same thing, should navigate to ramjet's guide: (http://forum.xda-developers.com/showthread.php?t=1889438). Download his file (QADERSO.zip) and unzip it.
1) I turned on USB debugging on my phone and connected to my pc using "charge only" option.
2) I clicked on RUU.exe file in ramjet's QADERSO\RUU folder which then update my phone to ICS. When I access the bootloader, it now said "Locked", then "shooter xc ship s-off RL" and finally "Hboot1-58.5858". So now i have ICS, still S-off but with an upgraded locked bootloader.
3) Then I copied the custom bootloader "PG86IMG_jb_hboot_Sprint_ICS.zip into the root directory of my sd card (the zip file can be found in another of ramjet's post (http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7) and renamed it PG86IMG.zip. Once you go into the bootloader, the zip file will automatically update. Now instead of "Locked" on the top, you should have "JuopunutBear".
4) First remove the previous zip file from the directory. I put the "SuperSU-v0.96.zip" from the QADERSO\Root folder in the root director of my sd card again. then i access my bootloader once again.
5) I went into fastboot and then connect to my Pc with usb. It should now say "Fastboot USB".
6) you can now flash any recovery img that you want. This is where I differ from ramjet's suggestion of 4ext as I did a backup of my system before all of this with clockworkmod recovery.
7) once the recovery of your choice is installed, then just install the supersu.zip file from your sd card and you should have a rooted phone.
Thanks to ramjet for his guide and his help. Now onto my next problem. going back to the state I was before updating to ics. Posting another thread about it. Anyone who can help out, please do. Thanks.
xionchen4628 said:
Well...color me stupid (and an ass) for not reading in depth ramjet's guide. From ramjet's guide, I went to mpgrimm2's "Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 9-25-12" thread which eventually lead to ramjet's post with all the different bootloaders available. As suggested, I used JB's ICS bootloader and now in the bootloader page, it no longer say "locked" but "JuopunutBear" now. Onto flashing recovery.
Click to expand...
Click to collapse
I created a similar thread the other day but it got so overwhelming and it was just confusing me more so I deleted it. I'm starting a fresh one so I can maybe explain myself better, not confuse anyone else and get better answers.
I just got a replacement Rezound in the mail today. My phone is currently on 4.05.605.14 710RD, LOCKED, HBOOT is 2.28.0000 & radios are 2.23.10.0123r/2.23.10.0124r.
That last time I was able to S-OFF I used the wire method and ControlBear for Windows. I went to the website Unlimited.IO and they no longer support Windows so I have no idea on how to S-OFF since I did it months ago. However, I did find ControlBear v0.1 for Windows here on the forums: http://forum.xda-developers.com/showpost.php?p=27764982&postcount=2079 My first question is will this version work for me? If you download it and open it you can see the zips contents. I wasn't sure If had to RUU back down to an earlier version for it to work? And last time I ended up being on a Juopunutbear HBOOT somehow.
So basically I want to be able to get back onto CyanogenMod 10.1 properly this time. I haven't done anything to my phone yet, still unrooted, on stock, etc.. I know my first step is too unlock it using the htcdev website but from there I'm confused, I can't remember the steps its been too long.
I need someone to please explain how I can get back to CM 10.1 and remain on the latest firmware/drivers/hboot etc. So I need help with rooting, s-off, how to get TWRP recovery back on, which to do first, etc.
I appreciate the help and I'll make sure I save this in case it ever happens again. Also, my apologies again for the previous thread, it was just too much going on, I just need simple steps.
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
xanda143 said:
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
ControlBear 0.1 worked for me on Windows, took a few tries but it finally pulled through. These where my steps:
1. unlocked
2. flashed recovery
3. flashed [ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
4. flashed boot.img from the rom
5. did wired trick with CB 0.1
so i think im good now? just have a couple questions.
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
xXezmacXx said:
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
Click to expand...
Click to collapse
That's normal if you're still using an unpatched hboot. If you will still use some fastboot commands (I use fastboot boot zImage/fastboot flash zimage zImage alot) then look into vynlfreak's 2.27 patched hboot. DO NOT UNLOCK flash patched hboot instead.
xXezmacXx said:
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
Click to expand...
Click to collapse
Flash your rom and don't worry about mainver.
Just wanted to thank you two. I have always been hesitant about s-offing my phone. But seeing it here in a few simple steps gave me the courage to finally pull the trigger. I know I am super late to the S-Off party, but am thrilled to finally have arrived!
Hello. Never made a thread before and was really hoping I wouldn't have to or would find an answer elsewhere.
Since that didn't work out, here's my problem:
Background: Evo 3d, virgin mobile, unlocked bootloader, s-off, hboot was at 1.50, and I don't remember what the radio was at. I was running CM11 and was quite happy until two days ago when I stopped receiving texts! No clue why, just stopped. Hangouts, etc etc. Called VM and they had no idea why that was happening either. Tried switching roms, reinstalling backups, etc etc. Clean wipes and all. Then I saw someone said they had to [for some reason] reinstall everything stock and then they had messaging back. So that's what I set out to do.
In Between: Used the RUU that I'm fairly certain came with my phone. Everything was good, it erased everything, and "updated system" and signatures. It was almost finished when BAM, popped up with error 152 Image Update Error; right at the very end. Quite disappointing. Tried it multiple times again with the same result. Not sure what to do.
Current: Only screen I can see (looks like shortened bootloader screen) says "***locked***" at the top, hboot 1.57.0000, radio 1.06.00.126, then says openADSP-v02.6.0.2226.00.0217eMMc-boot
Also tried flashing the unlock_code.bin, and while it took it, it changed nothing. One screen I did see very briefly but cannot replicate said that everything was there except system. Not really sure how to take that or what to do. Any and all help would be helpful. As is it sits on the HTC screen with exclamation points in each corner. When unplugged from usb it gives me that above screen. Removing battering and restarting to bootloader still gives the same screen.
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Did you run ruu through windows or pg86img.zip?
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Through Windows; the RUU exe.
SammyMak said:
Through Windows; the RUU exe.
Click to expand...
Click to collapse
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
So I have my phone working now. I think it was the RUU.exe that I was using. I downloaded a different one from here http://androidruu.com/Shooter/ after much googling. That finally restored it to original VM stock rom etc. I couldn't use your method of placing the zip onto the root of my SD because despite it being there, it wouldn't go through the normal search for the file. I would remove the battery, put it back in, use the button key combo to try and open to bootloader, and it would go but it would be the page with the status and then it would instantly go back to the black screen with HTC logo.
Thank you for your help though!
Also I'm not sure how useful exactly this will be for anyone else, but if you find yourself ruu'd and needing better files...
The hboot ENG 1.04 I got from here: http://forum.xda-developers.com/showthread.php?t=1817513
ALL other downloads of that hboot did not work AT ALL.
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
The hboots on that site however are stock and most likely won't run the custom roms as well, if at all, as 1.04.
SammyMak said:
I got the updated radio from here: http://androidforums.com/cdma-evo-3d-all-things-root/648902-radios-hboot-firmware-all-downloads.html
But the hboots on the site aren't helpful fyi
Click to expand...
Click to collapse
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
hossman said:
You can try this
https://www.dropbox.com/s/d4baafpgchgg4ef/ruu-PG86IMG.zip
Put that on the root of your SD card and rename to pg86img.zip
Make sure its the only one there
Boot to boot loader and accept updates
It may reboot itself to bootloader, if it asks to accept again then accept
When its done reboot your phone
Rename or remove the file when done
Hope that helps
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
thank you!
Brian706 said:
Hey, that's my thread. Just curious what you mean by the hboots aren't helpful?
If there is a problem I'm unaware of, I'd be happy to know what it is so I can get it squared away.
Click to expand...
Click to collapse
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
SammyMak said:
I must apologize! I seem to have mis stated that; they are helpful with regards to them being the stock hboots. However in my particular case those stock hboots weren't for me. I'll edit that here in a sec, but if I was going back to full stock I'd definitely use your stock VM hboot and it would be helpful in that case. Hope that makes sense, no disrespect meant!
Click to expand...
Click to collapse
Thanks for clarifying that! I see what you meant now.
No worries, I didn't take offense or think you were disrespectful; I just wanted to make sure the downloads were working properly!
And for the record, the stock hboots will work just fine with custom roms. Hboot 1.50 for example will be compatible with the same selection of roms as JuopunutBear 1.50.5050. The difference is that JuopunutBear is patched and will allow for extra fastboot commands and allow them to be run on a locked bootloader.
The eng 1.04 hboot allows for extra fastboot commands that the stock hboot cannot. But you can boot any rom out there on the stock hboots. I've used stock 1.50 forever on this device.