Related
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
Yes, it worths at least for myself. I have hboot 1.50 too and i rooted fast with no problems.
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
More than likely, yes. Most users who follow the guides don't seem to have issues.
The HTC unlock method changes the dynamics a bit from previous common and accepted methods. Many "new" users become between old and current guides.
As far as I've seen, there are only three limitations to hboot 1.5, compared with early "compromised" versions using the AlphaRevX revolutionary method.
1) Kernel is not able to be flashed from recovery mode. Work arounds include: flashing from normal Android mode, my app is great for that, Flash Image GUI. Loading the custom recovery from fastboot. Flashing the kernel from fastboot. Using the "dumlock" method with TWRP.
2) Unable to selectively flash radio images
3) Unable to selectively flash intial splash screens
If I'm missing anything, I'm sure somebody else can post up.
None of those seem like deal breakers to me. Thanks for the fast replies.
It's kind of a ***** just because you have to do a few extra steps but if you know what your doing you won't screw it up.
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Root is the way to go Get rid of bloat Also adb isn't hard I always fastboot boot recovery.img and wipe flash no issues
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
ls3mach said:
Should I start a new thread on this? I tried to root my HBoot1.5 with 2.17.651.5. When I have went through the HTC unlock process it stays locked. I tried to install the 2.08 version through the original RUU, but it keeps failing. Not sure where I should go from there.
Click to expand...
Click to collapse
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
That is what he needs to do to fix .
Sent from my PG86100 using xda premium
DjNawo said:
Yarr. I think I'm going to keep stock for probably just a bit longer. Maybe 1.5 S-Off wont be a problem then. Not bored of it yet, and coming from HTC Hero the thing is a dream.
Click to expand...
Click to collapse
You have Hboot 1.5 with S-off?
G.Newton said:
You have Hboot 1.5 with S-off?
Click to expand...
Click to collapse
No he doesn't from what he said he is stock and asking if he should root
xcpefrmreality said:
I used the 2.17 from http://www.filefactory.com/f/4ef0ef536face67a/ and mine unlocked. I ran the ruu while in hboot so it didnt check my current version. When i tried the same ruu from within android it failed every time.
What did it say when you flashed the unlock token? Did you get the message on the phone screen asking if you want to unlock?
Click to expand...
Click to collapse
Much obliged!
DjNawo said:
So I just got the EVO 3D and am running HBOOT 1.5 and the most recent update I believe. Nothing I could do about that, it was preloaded on there.
I'm wondering if it is even worth it for me to root my phone at this point. I've seen a few people hboot 1.5 **** up their phones and i'd rather not do that. I'm no stranger to custom roms at all (I installed countless ones on my Hero) so it's not that I'm not familiar. Were the people who messed up their phones just doing stuff they shouldn't have/being stupid in general?
Click to expand...
Click to collapse
I think some people just got ahead of themselves flashing wrong files. I got a bit worried too first go round after coming from a.Transform.
In my signature I've got a guide/flashing notes that are a bit more updated than some of the stickied threads that may help clear some things up.
Sent from my PG86100 using Tapatalk
What root did you use
Sent from my EVO 3D using XDA Premium
[/COLOR]
Yoyodude1124 said:
What root did you use
Click to expand...
Click to collapse
I used the HTC Unlock (zedomax's video), CWM Recovery, Su 3.07 zip, BusyBox (market), all layed out here:
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
Hey thanks again. Yeah I have the newest update, so i would need to get the 2.17 that xcp mentioned. Also, thanks for the guide above.
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hey man the phone isn't bricked if you have a pulsating dim red power light, alot of people came across the problem of actually killing batteries trying to brick their phones. If its pulsating just leave it charging on the wall socked for a while bit if it is a very very dim constant red light it is bricked and you would have to use a compatible computer that takes the drivers for your phone. Read through the thread you linked and search for your issue, it is a common one
****'ll Buff Out
gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Thanks, it's just dead as can be. I did eventually get it recognized by linux on the live cd and it successfully went through it's routine to get to hboot 1.40. The next step should be to install RUU 1.13. It's a KDDI phone. I used this
RUU_Shooter_K_S_KDDI_JP_1.11.970.2_Radio_1.02.00.0906_NV_1.39_01C_release_246058_signed.exe
for initially bricking it. I extracted the ROM first. That part went smoothly . I think I did everything right and i'm where i should be now but it just doesn't do anything... nothing. I did try to mess with emmc_recover but no luck yet. When I do the RUU I just keep getting "error 170 usb connection error." I've tried uninstalling/re-installing/different versions of HTC drivers. I keep messing with it for a bit and hopefully something gives! Oh and battery, no battery, I can't get anything. If I could get it recognized on the PC I think I'd have a shot! Thanks again,
gjash
runcool said:
The evo3d was designed for americans. We don't support the Japan people do to over population of your race. Also if you used your head you'd notice that the computer you're using likely is in the crappy Japan language no one uses. Therefore, you need to try another computer and it'll work. We can't support every computer out there. The Drivers won't work for every type of computer on the planet.
To make this racist reply short, it's your computer. you gotta try another computer. Try using an older system. I'll have to open it up to figure out which drivers they put in there, but I know for a fact it won't work on my computer. I'd have to use it on another as well.
They should put that in the instructions. hmmm But after trying another computer, get back with us.
ps again, you said you "tried it on other computers" model numbers of those and what language are they in? It does make a difference. But I'm glad you speak english or I'd just laugh. I'm really mean today. so sorry. hahaha. Let me know if I'm right.
ps again. remember drivers drivers and drivers. drivers only work with certain types of hardware.
edit, you said linux machine, BUT DID YOU EVEN INSTALL the drivers on it? lmao!?
Click to expand...
Click to collapse
Your a complete douche bag! Its people like you that drag society down! If I met you in person I would ***** SLAP you so hard it would not be funny!
The last I checked we all bleed red.
@op I am glad you got it worked out unfortunately I can not help because I have no idea who your carrier is. What I do know is if you update to ruu 2.17.651.5 you will be back on Hboot 1.5 but with S-off.
Sorry that is all the info I can give you.
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
gjash said:
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
Click to expand...
Click to collapse
After downgrading/flashing Hboot 1.40, the goal of the RUU is to install an earlier fully working Stock Rom (S-On still) that came with the same Hboot 1.40 that is pushed to the phone with the downgrade tool/process. Hopefully you can find an early KDDI ruu with Hboot 1.40 for this part. This allows you to run " http://Revolutionary.io 's rooting/S-Off tool to gain "S-Off" and install a custom Recovery like Revolutionary CWM Recovery 4.0.1.4 (or 4Ext Recovery).
From there (make a nandroid backup) you can update the firmware/radio if needed (make sure hboot 1.50 isn't included) and flash a current rooted rom (stock or custom) that matches your radio/baseband as appropriate. Maybe there is a current rooted stock KDDI RUU (PG86IMG.zip) without the hboot 1.50 or someone (like Mr.Esp, freeza, or xhausx) can help you pull the stock rom apart for this step.
You can also flash the SuperUser zip (app & binary) from custom recovery to gain root on a currently installed stock rom once you have S-Off.
That's my LIMITED understanding, but I'm not 100% sure about your situation overseas since I thought all foreign carriers outside the U.S. used GSM devices.
closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Can't really do anything at the moment. I can't flash RUU 1.13 and I can't get it to be recognized on USB so I could use ADB and try pushing something to it. I have no idea! This is a learning thing at this point. I did root my Asus transformer before though! Thanks for any help!
gjash
gjash said:
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Click to expand...
Click to collapse
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
closeone said:
But take the RUU .EXE that you upgraded your phone with already and grab the ROM out of there.
To get to your temp directory: press the Windows key and R on your keyboard at the same time. Type in this exactly: %temp%
Rename the rom.zip to PG86IMG.zip and put it on your SD card.
Click to expand...
Click to collapse
I haven't made any progress. I'm assuming I need to use emmc_recover to overwrite the boot partition and maybe the misc partition. So can someone help me figure out identifying the partition, how I can get linux to recognize the device so I have a chance to recover? Also, at this point I settle for anything working, any Hboot, whatever... It would be nice if I could post in the original thread, hmmmm. moderator, can you help there?
thanks,
gjash
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
mpgrimm2 said:
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
Click to expand...
Click to collapse
You are right... both KDDI 1.09 and 1.11 have Hboot 1.50. I guess the trying Sprint 1.13 wouldn't be an option? That's the question and I can't really find out as the KDDI ones and the Sprint ones don't work because I always get USB 170 connection errors. So kinda stuck, but greatly appreciate the help!
gjash
mpgrimm2 said:
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
Click to expand...
Click to collapse
I will start looking there... I was thinking that the KDDI Evo 3d is CDMA and it would have the same partition layout. I'd like to determine that and go from there. Can someone explain the sprint evo 3d partition layout? thanks!
gjash
I'm willing to mess with this phone so if any developers have something I can do, please let me know. Otherwise, I just try to get back to stock.
I extracted original hboot from latest KDDI RUU and renamed it hboot.img and then executed 'downgrade'
I got this error:
Waiting for device...
Found the Correct Device!
Writing image file!
dd: opening `/dev/sdf34': Permission denied
FAILED!!
Any ideas? Thanks!
gjash
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
mpgrimm2 said:
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
Click to expand...
Click to collapse
Getting closer I think... I just needed to do a sudo ./downgrade and it flashed fine. Now I have a red light on which is more than I had before. I will go to windows now and try to flash the KDDI RUU. thanks for the help.
gjash
Update:
I'm back up where I started. I used Unknownforce's hboot downgrade but renamed the original hboot from the KDDI RUU to hboot.img, according to Unknownforce's direction (thanks!). After I did that, the phone just booted up normally. I thought I would have to flash the RUU but wasn't necessary. I think with some changes this whole exploit could work with the japanese cdma version of the Evo 3D. If anyone can outline what I'd need to do, it might be fun. especially that I already ordered another phone, but I won't actually need it.
gjash
Does your device happen to be the KDDI ISW12HT?
(I assume it is from what you've said)
Do you know the exact model you have?
The current CDMA models that I'm aware of are the:
X515c: CDMA800, CDMA1900, ESMR800, WiMAX 2.5-2.7GHz (the sprint one)
X515d: CDMA800, CDMA1900 (I forget)
X515e: CDMA900, CDMA2100 (the HTC rider)
The ISW12HT is listed as having CDMA800, CDMA2100, which arnt any of those 3.
Do you happen to know what submodel you have? I have no idea how to check as I've never touched one.
I'm wondering if it's the X515b or a yet unknown one (by unknown I mean with regards to the model number)
I've already listed all the common and less-common models on the wiki: HTC Evo 3D - XDA wiki.
But I have no idea what the ISW12HT's model is, and a fair amount of googling turns up little.
If you could poke around your device/box/manual and find it I'd appreciate it
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.
Hey guys....
I feel really stupid about this entire thing but I've finally decided to post here because I'm getting desperate.
The guide in question (http://forum.xda-developers.com/showthread.php?t=1563342) is fairly striaghtforward. Except the links are really scattered, at least for me. I'm on HBOOT 1.58, and I've had numerous problems even getting to the point where my phone is relocked (it's currently HTC unlocked because I use an MIUI port ROM) successfully. I would bring my problems to that thread, but I don't have 10 posts, which is a questionable rule but w/e.
Anyway, here's my problem. First, I'll tell you what I've done so far, and the problem I've come across both times.
1. Place a "2.89 RUU" or whatever onto my SD card and call it PG86IMG. This is where most of my confusion is. OP of that thread hasn't yet covered what the difference between 2.17 and 2.89 is, but my understand is that 2.17 corresponds with HBOOT 1.5 and 2.89 to 1.58. Honestly, all these numbers piss me off when there's little to no documentation of what the hell they even mean. This file is about 448 MB and my understanding was that it was a stock RUU and would make it so I could access my phone while it was still locked, which you can't do with a 3rd party ROM like the one I usually use.
2. Lock my phone's bootloader. I just did fastboot oem lock in Windows and it rebooted to *** RELOCKED *** *** Security Warning ***. Apparently this is normal, and now I need to flash said RUU.
3. Flash the RUU. This took an EXTREMELY long time, and it went through Loading PG86IMG.zip.. then to some other stage that took much less time to complete. After that it just sits in the bootloader.
Here's my concern... I can't access my SD card. Why? Because I can't even get out of the bootloader or fastboot. All it does is sit here, and since I can't remove the update file PG86IMG.zip, if I try to enter recovery (which I'm sure won't work anyway) it will try to start loading that file again. I don't really know what step I missed here, but it's probably because I'm fairly clueless when it comes to this stuff, lol.
So, I did this once, and then I waited about 6 hours for HTCdev's site to stop crashing so I could unlock my phone again. Made it through a school day with my old ROM and stuff, deleted the update files so they wouldn't run again, etc. etc.
Now, I'm doing it again today with this new 2.89 RUU or whatever and the same exact problem is happening. So now I'm at a stage where my phone is entirely useless until HTCdev.com starts actually sending e-mails. I swear, these crashes on HTCdev's part could not be more untimely.
So basically, what am I doing wrong with relocking my phone? OP implies that I should be able to start my phone (not the bootloader, but actually start it) because they ask after you've supposedly re-locked the bootloader for you to move a new PG86IMG.zip file onto your SD card, which I'm unable to do because my phone can't get out of fastboot/bootloader screen. That's the next step, which is actually doing the downgrading.
And yes, I know that it's possible for HBOOT 1.58 because someone else already did it (last post in the thread).
At this point, I don't really care when I get it to work, man. This is proving to be such a gigantic pain in the ass just to install a new Jelly Bean ROM. I JUST WANT JELLY BEAN!
If anyone can send a noob in the right direction, that'd be great. I have all week and all weekend, but I've run out of time to waste on this for today. I guess most of what I need is to know what files I'm supposed to be downloading, because I have a feeling that's most of what I'm getting wrong.
I hope I've explained my problem well enough, and thanks a ton to anyone who just suffered through reading my essay and can offer help. I'll be sending this to OP of the guide as a PM so hopefully if none of you guys can help they can.
Thanks a ton everyone, I just want to get Jelly Bean on my phone and stop dealing with MIUI :laugh:
Update: Found this thread: http://forum.xda-developers.com/showthread.php?t=1495358. I believe this will probably help me out a lot! Wish I would've seen it sooner.
TL;DR: Need better explanation of how to relock 1.58 hboot bootloader with a stock rom, and where to find the rom.
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
coal686 said:
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
Click to expand...
Click to collapse
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Logic33 said:
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Click to expand...
Click to collapse
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
raptoro07 said:
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
Click to expand...
Click to collapse
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Logic33 said:
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Click to expand...
Click to collapse
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
coal686 said:
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
Click to expand...
Click to collapse
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Logic33 said:
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Click to expand...
Click to collapse
Good! :thumbup:
Keep posting questions, we'll do our best to help.
coal686 said:
Good! :thumbup:
Keep posting questions, we'll do our best to help.
Click to expand...
Click to collapse
LOLJK. I swear, at this point HTC must be trolling me. It's loaded up now. Thanks for trying to help everyone! I can't wait to get Jelly Bean on here soon!
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
coal686 said:
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
Click to expand...
Click to collapse
I have a feeling you didn't see my update It magically decided to work. Here comes double bricking action... this should be (un)fun D:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
chubaan said:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
Click to expand...
Click to collapse
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
fdavila17 said:
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
Click to expand...
Click to collapse
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
ruckstande said:
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
Click to expand...
Click to collapse
Just download the hboot you want, 1.50 or below to get PACMAN to.boot, rename it as PG86IMG.zip place it on the root of your sd card, go to.the bootloader and select yes to apply update , and your done
Sent from my PG86100 using xda premium
Thank you.. that's what I did. And after you're done make sure to wipe dalvik and cache from recovery, at least in my case I had to. And then flash the rom. And that's it..
Sent from my PG86100 using XDA Premium App
So I have the virgin mobile 3d and I am rooted with s-on. I've been trying to get it off tho. So I was following the quick and dirty thread. And so I relocked the boot loader and then I started up the RUU like the guide. And about halfway through the installation it gave me boot loader version error 140. So I looked it up and I think it means that I was trying to downgrade. And that's why it didn't work. I was supposedly going from 1.14 down to 1.13. These are the version The ruu gave. I'm not sure what the numbers were about but can someone help? That ruu was supposed to be the most updated one. And i have been searching like crazy. Any help would be appreciated. I understand these things, so don't be afraid to talk techy to me lmfao. Thanks
Sent from my SPH-L710 using xda app-developers app
monstaX said:
So I have the virgin mobile 3d and I am rooted with s-on. I've been trying to get it off tho. So I was following the quick and dirty thread. And so I relocked the boot loader and then I started up the RUU like the guide. And about halfway through the installation it gave me boot loader version error 140. So I looked it up and I think it means that I was trying to downgrade. And that's why it didn't work. I was supposedly going from 1.14 down to 1.13. These are the version The ruu gave. I'm not sure what the numbers were about but can someone help? That ruu was supposed to be the most updated one. And i have been searching like crazy. Any help would be appreciated. I understand these things, so don't be afraid to talk techy to me lmfao. Thanks
Click to expand...
Click to collapse
See the note for S-ON users in this post, which is also linked in the informational posts after Step3 of the guide. The reason you are having this problem is because you have already installed the OTA, which has a higher main version (mainver) than the VM RUU.
ramjet73
ramjet73 said:
See the note for S-ON users in this post, which is also linked in the informational posts after Step3 of the guide. The reason you are having this problem is because you have already installed the OTA, which has a higher main version (mainver) than the VM RUU.
ramjet73
Click to expand...
Click to collapse
ramjet youre the man. Im about to read it. I will try and then report back thanks
monstaX said:
ramjet youre the man. Im about to read it. I will try and then report back thanks
Click to expand...
Click to collapse
Good.
Don't forget to download and flash the OTA again after the RUU is flashed since it requires the stock recovery.
ramjet73
ramjet73 said:
Good.
Don't forget to download and flash the OTA again after the RUU is flashed since it requires the stock recovery.
ramjet73
Click to expand...
Click to collapse
So it worked!! I finally got s-off!!! Now one last thing, how do i go about downgrading the hboot. I plan on going SlimBean. I tried flashing the sprint 1.5 hboot but it failed. The error said that the custom ID failed. . Is there any way to downgrade?
monstaX said:
So it worked!! I finally got s-off!!! Now one last thing, how do i go about downgrading the hboot. I plan on going SlimBean. I tried flashing the sprint 1.5 hboot but it failed. The error said that the custom ID failed. . Is there any way to downgrade?
Click to expand...
Click to collapse
That's in this post, which is also linked after Step3 of the guide.
ramjet73
I have tried this. And a side note* when I boot into the boot loader it doesn't look for PG86IMG.zip it looks for PG86DIAG.zip. its really weird. Anyone know what this is? I tried renaming it to that but it doesn't do anything. It just reboots the boot loader. I have also tried flashing it through fastboot
Sent from my SPH-L710 using xda app-developers app
monstaX said:
I have tried this. And a side note* when I boot into the boot loader it doesn't look for PG86IMG.zip it looks for PG86DIAG.zip. its really weird. Anyone know what this is? I tried renaming it to that but it doesn't do anything. It just reboots the boot loader. I have also tried flashing it through fastboot
Click to expand...
Click to collapse
The PG86DIAG.zip file is an advanced diagnostic that is very tightly controlled by HTC, but the bootloader always looks for it anyway.
The filename for the zip doesn't matter when you use the fastboot flashing method. Can you paste the messages you are getting here starting with the "fastboot erase cache" command? Make sure you delete the PG86IMG.zip file from the root of the SD card before trying the fastboot method.
ramjet73
ramjet73 said:
The PG86DIAG.zip file is an advanced diagnostic that is very tightly controlled by HTC, but the bootloader always looks for it anyway.
The filename for the zip doesn't matter when you use the fastboot flashing method. Can you paste the messages you are getting here starting with the "fastboot erase cache" command? Make sure you delete the PG86IMG.zip file from the root of the SD card before trying the fastboot method.
ramjet73
Click to expand...
Click to collapse
OK sweet that it good to know. I tried both methods and it didn't work. But when I used the fast boot method I got a custom I'd check failed error. I'm not by the phone right now. But I remember the error. That's the only one I got. When I tried downgrading from 1.57jboot to 1.5
Sent from my SPH-L710 using xda app-developers app
monstaX said:
OK sweet that it good to know. I tried both methods and it didn't work. But when I used the fast boot method I got a custom I'd check failed error. I'm not by the phone right now. But I remember the error. That's the only one I got. When I tried downgrading from 1.57jboot to 1.5
Click to expand...
Click to collapse
If you are on hboot 1.57 then you probably have the Evo V 4G which means you need to use the Virgin Mobile version of the RUU.
ramjet73
ramjet73 said:
If you are on hboot 1.57 then you probably have the Evo V 4G which means you need to use the Virgin Mobile version of the RUU.
ramjet73
Click to expand...
Click to collapse
So you're saying I should extract the PG86IMG.zip from an older VM ruu? And then place in the root of my sdcard? That would give me the stock boot loader :-/. I already got s-off with jbear hboot 1.7
I'm trying to dual boot eventually so I want to be on hboot 1.5
Edit: one thing I haven't tried is leaving it named PG86IMG.zip and placing it on the SD card. But using 1.5 is that safe to try?. I'm thinking it will work because it is a sprint phone. It has sprint branding. It is just on VM. Let me know what you think
Sent from my SPH-L710 using xda app-developers app
monstaX said:
So you're saying I should extract the PG86IMG.zip from an older VM ruu? And then place in the root of my sdcard? That would give me the stock boot loader :-/. I already got s-off with jbear hboot 1.7
I'm trying to dual boot eventually so I want to be on hboot 1.5
Edit: one thing I haven't tried is leaving it named PG86IMG.zip and placing it on the SD card. But using 1.5 is that safe to try?. I'm thinking it will work because it is a sprint phone. It has sprint branding. It is just on VM. Let me know what you think
Click to expand...
Click to collapse
Follow the instructions in this post since you are S-OFF already. I recommend the JBear 1.50.5050 instead on the 1.50 hboot since that doesn't need to be unlocked to run extended fastboot commands.
ramjet73