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.
ok, so i went through the s-off process and completed it successfully. It asked me if I wanted to flash the jb-hboot.zip which I said yes. Now, when I boot into hboot it has this ugly pink bar accross the top that says "juno..." (the name of the team). I am currently on the new firmware running BAMF Evita sense 4. Is there a stock ics hboot or something i can put back in its place that will leave s-off, be compatible with new firmware and not give custom labels accross the top?
Please help....
jbeitel said:
ok, so i went through the s-off process and completed it successfully. It asked me if I wanted to flash the jb-hboot.zip which I said yes. Now, when I boot into hboot it has this ugly pink bar accross the top that says "juno..." (the name of the team). I am currently on the new firmware running BAMF Evita sense 4. Is there a stock ics hboot or something i can put back in its place that will leave s-off, be compatible with new firmware and not give custom labels accross the top?
Please help....
Click to expand...
Click to collapse
Technically, you could just reflash the leaked RUU then and you will still have S-off. Changing Hboots , won't affect S-off, Numerous threads have popped up with just radio's and Hboots to flash. Just be careful and don't mix and match Radios and Hboots to avoid trouble.
mjh68 said:
Technically, you could just reflash the leaked RUU then and you will still have S-off. Changing Hboots , won't affect S-off, Numerous threads have popped up with just radio's and Hboots to flash. Just be careful and don't mix and match Radios and Hboots to avoid trouble.
Click to expand...
Click to collapse
do I have to relock anything like when I upgraded to the new ics firmware? I was hoping for a straight forware ph98img.zip flash. i know, thats lazy but easy.
IMO, leave it. Put up with eye sore. If the flash to the stock one goes belly up, you will brick the phone. Leave it til you need to go back to an S-On device.
Snuzzo said:
IMO, leave it. Put up with eye sore. If the flash to the stock one goes belly up, you will brick the phone. Leave it til you need to go back to an S-On device.
Click to expand...
Click to collapse
Technically true, but really as long as he doesn't pull the plug while its loading the Hboot its not a great danger.
---------- Post added at 12:03 PM ---------- Previous post was at 12:00 PM ----------
jbeitel said:
do I have to relock anything like when I upgraded to the new ics firmware? I was hoping for a straight forware ph98img.zip flash. i know, thats lazy but easy.
Click to expand...
Click to collapse
I am pretty sure , their hboot is already relocked . So shouldn't have to relock , I went all the way back to GB and used the full exe RUU and relocked since I didn't know that it was locked initially and it ran just fine.
I would try without relocking , it will either run or fail before it starts doing anything.
Thank you mjh. Yes it is relocked & again leave it as is. Trust me you will thank me later. No need for unlock codes anymore and just waiting for roms to be rebased and official OTA(not for the actual OTA but for kernel source if released).
you guys know how to frustrate a guy, geez. What a great world that everyone can have their own opinion. Now, who's do I want to have?
I know exactly how you feel. Cant make up my mind what I want to do either. Currently on ICS S-OFF displaying Tampered/Locked
Do I RUU back to GB and flash the ENG Hboot?
Do I go ahead and flash jb_hboot? And which one is it actually. There have been way to many threads and posts on S-OFF and a bunch of different answers.
Do I leave it alone and wait to see what happens with the next release?
In some ways it would be nice to be back on Hboot 2.11 and have ENG S-off but is it worth it? Wont really know until the next official release comes out.
jbeitel said:
you guys know how to frustrate a guy, geez. What a great world that everyone can have their own opinion. Now, who's do I want to have?
Click to expand...
Click to collapse
I am not telling not to flash, just telling you after S-off and using their Hboot it is already locked, but you can still flash the stock RUU. I did and haven't had any issues , but I didn't realize it was already locked so relocked and unlocked by HTC dev without knowing it . I am still tempted to flash the eng hboot , but not sure if I really have a need to.
mjh68 said:
I am not telling not to flash, just telling you after S-off and using their Hboot it is already locked, but you can still flash the stock RUU. I did and haven't had any issues , but I didn't realize it was already locked so relocked and unlocked by HTC dev without knowing it . I am still tempted to flash the eng hboot , but not sure if I really have a need to.
Click to expand...
Click to collapse
whats the big deal with the engineering hboot? is it different or is that the standard one in the ruu?
Snuzzo said:
No need for unlock codes anymore
Click to expand...
Click to collapse
There is more difference than this(allows more commands to be ran in prompts) but with an ENG hboot, you can keep it locked and s-off, along with still being able to flash anything your heart desires. ALTHOUGH if you wish to go back to s-on, flash an RUU of your choice first. As when you do write secureflag and a few reboots on an ENG hboot, you could brick.
Leave the hboot they give you. The tag might be annoying but it is better than having to re-unlock to use fastboot commands.
Why is un- re locking not ideal? It takes 2 minutes.
Sent from my v6 supercharged Rezound.
AJMetal87 said:
Why is un- re locking not ideal? It takes 2 minutes.
Sent from my v6 supercharged Rezound.
Click to expand...
Click to collapse
Scotty posted earlier if your S-OFF then unlock and relock again it will alway show relocked again unless you RUU then S-ON and then S-OFF again. If you S-OFF and don't unlock it and RUU it will say locked but its best to use the patched hboots supplied to be able to use certain fastboot commands that way you don't have to unlock and not have a problem with it saying relocked.
Sent from my ICS Rezound
LakerStar25 said:
Scotty posted earlier if your S-OFF then unlock and relock again it will alway show relocked again unless you RUU then S-ON and then S-OFF again. If you S-OFF and don't unlock it and RUU it will say locked but its best to use the patched hboots supplied to be able to use certain fastboot commands that way you don't have to unlock and not have a problem with it saying relocked.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Aside of the text difference on the bootloader and potential warranty comprimising, is there any other downfall?
No downfall. But again, nor needed to unlock if s-off.
Sent from my ADR6425LVW using XDA
I'm not trolling or trying to start a argument, but if that's a big deal to you to have the pink junabear banner across your hboot screen then you should have never s-off. I mean really. Who sits there and stares at the hboot screen and decides that it doesn't look good. Lmao.
Sent from my ADR6425LVW using XDA
Especially when the stock hboot uses the same color banner but says locked instead?
Via Rezound using XDA Premium
GB
Anyone who was on Gingerbread when the did S-Off does *NOT* have the Juououuoouououpnutbear logo; just standard Eng HBoot.
This would be me.
Bump. I need the stock Hboot to send back to Verizon. The GB hboot if anyone has it please.
So i was having the ghost touch issues on my phone for the past 2 weeks and thought maybe just to take it into sprint. So i had to unroot, RUU, etc and it was having the same issues. Took it into sprint and they said they ran diagnostics on it and nothing was wrong but when i got home it was doing the same thing. But now im updated on 2.89 and HBoot 1.58 and want to know how to root, s-on or s-off doesnt matter, and also downgrade so i can got back to aosp ROMs or Mazda's and also sense ROMs. So if anyone can help it wuld be greatly appreciated. P.S Yes i've searched this topic and it just came up with a lot of different pages and methods so telling me to search before asking isnt necessary.
NexusS4gFreak said:
So i was having the ghost touch issues on my phone for the past 2 weeks and thought maybe just to take it into sprint. So i had to unroot, RUU, etc and it was having the same issues. Took it into sprint and they said they ran diagnostics on it and nothing was wrong but when i got home it was doing the same thing. But now im updated on 2.89 and HBoot 1.58 and want to know how to root, s-on or s-off doesnt matter, and also downgrade so i can got back to aosp ROMs or Mazda's and also sense ROMs. So if anyone can help it wuld be greatly appreciated. P.S Yes i've searched this topic and it just came up with a lot of different pages and methods so telling me to search before asking isnt necessary.
Click to expand...
Click to collapse
You can try my guide which was designed to get you from any build with S-ON to a rooted, S-OFF Sprint ICS configuration as easily as possible. You can probably skip the first step, which is flashing the 2.89.651.2 RUU.exe, since it sounds like they did that already when they worked on your phone.
If they did the OTA instead you could have problems with the HTC unlock, so if that happens just go back and flash the RUU.exe.
Good luck!
ramjet73
ramjet73 said:
You can try my guide which was designed to get you from any build with S-ON to a rooted, S-OFF Sprint ICS configuration as easily as possible. You can probably skip the first step, which is flashing the 2.89.651.2 RUU.exe, since it sounds like they did that already when they worked on your phone.
If they did the OTA instead you could have problems with the HTC unlock, so if that happens just go back and flash the RUU.exe.
Good luck!
ramjet73
Click to expand...
Click to collapse
Thanks ramjet73, definitely wanna try but is the wire trick actually safe to do?
NexusS4gFreak said:
Thanks ramjet73, definitely wanna try but is the wire trick actually safe to do?
Click to expand...
Click to collapse
Yes. I've never heard of phone that was damaged by it. The SD card may get corrupted but that can always be reformatted.
ramjet73
ramjet73 said:
Yes. I've never heard of phone that was damaged by it. The SD card may get corrupted but that can always be reformatted.
ramjet73
Click to expand...
Click to collapse
Okay ill try, again thanks for your help and the guide ramjet73!
Unable to downgrade HBOOT 1.53.0007 to 1.49.0007
Hi, yesterday I decided to "upgrade" my sister's HTC EVO3D GSM to make unlock, root...also S-OFF if needed to flash any ROM, but it was the first time i was flashing EVO3D so it was whole day I sit at the computer watchin&reading tutorials and this forum before I could do anything...finally i partially succed, I made unlock by HTCdev method, flashed recovery via fastboot...flashed ROM from recovery, but I wanted to install CM9 ROM by agrabren and surely it wasnt working, because the phone is no HBOOT 1.53.0007...
So for the instance, the phone:
Is HTC EVO3D GSM
was on stock ICS 4.0.3 OTA rom
HBOOT 1.53.0007 S-ON
UNLOCKED S-ON by htcdev method
followed this thread to root http://forum.xda-developers.com/showthread.php?p=28106291 and flash ROM
Then it's working on ICS NonSense® 4.0
but i want to try CM9/10/AOKP ROMs so i realized i need to downgrade HBOOT to 1.49.0007 and get revolutionary S-OFF so i tried to follow this http://forum.xda-developers.com/showthread.php?t=1471246
The first method copying mmcblk0p31.img to sdcard and here im stuck....I dont understand why, but the command "adb shell dd....." copies mmcblk0p31 file of 16kB size and total empty content, so I cant change any version to 1.20.720.1 and cant downgrade....
So how to solve this problem? Is it cause that first I need to get hboot 1.53 S-OFF?
Thanks for the reply...
//Im sorry my post is also located here http://forum.xda-developers.com/showthread.php?t=1833367 where is I think better place for it and I didnt find how to delete it from here...
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
i have looked through the threads and i did not see anything about this question or anything close enough to it. I need to go back to sprint to get my phone fixed (the microphone doesn't always work. sometimes it does, sometimes it does not. i have found that it is not software related, but definitely a hardware issue.) but i do not want to get my account noted or anything. right now i am s-off (NOT htc dev unlocked), running TWRP recovery v 2.2.0, and running meanrom with a custom kernel that was installed with meanrom. i know i can run an RUU and return to stock, but i will still be s-off. i did install a custom bootloader (thanks to regaw_leinad) that makes it look like i am s-on and not tampered, but i do not know if sprint can still see if i am s-off. sorry if this is a noob question, but i have never dealt with s-off before.
http://forum.xda-developers.com/showthread.php?t=1744700
Look harder next time.... Just joking. This is what you want to read.
metalfan78 said:
http://forum.xda-developers.com/showthread.php?t=1744700
Look harder next time.... Just joking. This is what you want to read.
Click to expand...
Click to collapse
thank you! that was exactly what i was looking for! i guess i didn't look hard enough sorry.
but just to clarify, i cannot just leave my phone s-off? if i take it to sprint with s-off, but the custom bootloader that makes it look stock from regaw_leinad, will they still be able to find out that i am s-off?
I have never returned my phone to s-on in two years. I've never had a problem with the Sprint stores. It's your call though. If you do s-on it, tell them you don't want it updated. If it was me I would just have the stock rom on it and call it good
metalfan78 said:
I have never returned my phone to s-on in two years. I've never had a problem with the Sprint stores. It's your call though. If you do s-on it, tell them you don't want it updated. If it was me I would just have the stock rom on it and call it good
Click to expand...
Click to collapse
that is probably what i will do then. again, thank you!
You're welcome
ok, last question. if i run the latest ruu, will it update my hboot? i am still on 1.12 and i do not want a newer one. i downloaded the 1.13.651.1 ruu. is this fine? i am running meanrom v 4.0 if that info is needed.
I'm about to go 100% back to stock as well to try and resolve many of the problems i'm having, this thread has been particularly helpful, thanks
I think it does update your hboot, but I don't know for sure.
i have confirmed that it does indeed update your hboot.
if you have hboot 1.12, then use this ruu:
http://bit.ly/VPl2wn
it is the 1.13.651.1 ruu. it has hboot 1.12 in it.
tim.d said:
I'm about to go 100% back to stock as well to try and resolve many of the problems i'm having, this thread has been particularly helpful, thanks
Click to expand...
Click to collapse
i am glad to posted a helpful thread. but we can thank metalfan78 for supplying the information that helped us
sorry to post a third time, but i ran the ruu that i previously posted a link to and went to the sprint store (i also had to re-flash the custom bootloader from the regaw_leinad tool). they had no clue i was s-off or i had done anything to my phone. but there is one problem. if they had tried to update it and it updated the bootloader as well, it would have removed the custom one and put HTCs back on it. that wouldnt be a problem as you would still be s-off, but instead of looking stock(s-on, locked), it would now say s-off in the bootloader. so if you want to be sure that the sprint employees will not be able to tell you modded your phone, you do have to return to s-on. chances are that they wont try to update it, but its better to be safe than sorry!
Yea, true. I'm glad everything worked out.