Related
Sorry for the noob question. Ive read many forums and not found astraight answer. I know the answer is out there, just want to get this thing rooted though. My evo 3d is running software version 2.08.651.2. Everything is entirely sock right now. I want root for wireless tether and overclock.
This software meqns i am running hboot 1.5 doesnt it? If so which methods work for root? Ive found several methods and watched several videos. If i try and choose the wrong method what are the consequences? If i couod post links id link the stuff ive found. Thanks guys is it true that the htc method does not achieve s-off?
The software version and hboot version isn't entirely connected 100%.
To check which hboot version you have, you'll have to remove the battery, put it back in, and then hold "Volume Down" button and then power on the phone (Most phones don't require having to remove the battery, but the EVO apparently does, as i found out the hard way after 20 times trying to get into recovery..)
It'll say something along the lines of:
*** LOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-x.xx.xxxx
Reply with the HBOOT version and i can tell you more. (or someone else can)
If you try and root and S-OFF with the wrong methods, wrong tools, wrong phone etc, you could potentially brick the phone (which, as it sounds, means it'll be just as useful as a brick, since you can't do anything on it.. at all), but that is an absolute worst case scenario, and it will not happen if you do it correctly (which might sound hard, with all the technical mumbo jumbo, but it is actully quite easy).
The officla HTC Method does indeed not achieve S-OFF, so it's not an optimal solution.
Moonbloom said:
The software version and hboot version isn't entirely connected 100%.
To check which hboot version you have, you'll have to remove the battery, put it back in, and then hold "Volume Down" button and then power on the phone (Most phones don't require having to remove the battery, but the EVO apparently does, as i found out the hard way after 20 times trying to get into recovery..)
It'll say something along the lines of:
*** LOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-x.xx.xxxx
Reply with the HBOOT version and i can tell you more. (or someone else can)
If you try and root and S-OFF with the wrong methods, wrong tools, wrong phone etc, you could potentially brick the phone (which, as it sounds, means it'll be just as useful as a brick, since you can't do anything on it.. at all), but that is an absolute worst case scenario, and it will not happen if you do it correctly (which might sound hard, with all the technical mumbo jumbo, but it is actully quite easy).
The officla HTC Method does indeed not achieve S-OFF, so it's not an optimal solution.
Click to expand...
Click to collapse
So, do i need s-off? Im kind of a noob, so really advanced functiojs arent really useful yet. Ive read a few threads trying to figure what s-off is exactly, and it sounds like all it does is open a few extra commands over root. Kind of what i understand busybox does in others. I may misunderstand though. If i go ahead with the htc method of root and revolutionary figures out the s-off next week will i still be able to acheive s-off?
This is somewhat unrelated, but if, when i need to repoace an existing file with a new onein say astro, can i simply rename the old one with like a .bbb on the end and not move it? At several poihts in theroot process you are required to replace an existing file with a new one of the same name. Then replace the old one, or delete the added one. Can I just rename the old one, then put the name back and delete the new one to revert?
Indeed my phone is Hboot version 1.5. It reads
Locked
shooter xc ship s-on rL
Hboot-1.50.0000
Emmc-boot
Aug 7 2011, 10:21:40
So with 1.5 my only option is HTC method? With my tab I am able to completely uninstall and unroot as I please. Is the same true here? can someone link me a video of someone dependable doing it the HTC way? if I post my plan for rooting here will someone let me know if I'm off base so I don't brick my phone?
Can someone tell me the deal with cwm? Does it work or not? If its both ways, then what are the conditions under which it fails? Do I need to install cwm and twrp? What should I plan to do if cwm fails to install?
Another noob question. What is pushing a file exactly, and how and why is it done? I really don't want to get half way through this and discover I dont know what in gods name I'm doing.
I think I read on xda somewhere that if you turn of fastboot in the settings you dont have to remove the battery.
That's a lot of questions, a lot of this info can be found in the wikis and guides in the development section, but I can probably answer a few.
S-on is the encrypted bootloader, you need a special signature to he able to flash any ROMs or anything else to the system. Only HTC has the keys. So s-off allows you to install a custom recovery or anything else that can rewrite to the system.
From what I read so far HTC so called unlocked is not s-off like we are used to. People are having trouble flashing recoveries and kernels to their phones. I haven't payed much attention to the HTC method cause I used the unrevoked method.
You don't need s-off to flash ROMs but I guess if you want complete control over your phone (like the ability to flash bootloaders and various recoveries) you need to be s-off.
If you want to replace a file in the system name the old file extention .bak and then drop the new file in. Reboot to complete the changes. To revert, delete the modified file and just rename and take off the .bak extension.
As of now yes your only method of unlocking is using the HTC method with the 1.50 bootloader. CWM works fine and I think its the only compatible recovery with the 1.50 BL, TWRP is more polished and has a few added functions. I don't know when unrevoked will crack 1.5. Eventually they will.
If you don't know what in gods name your doing, don't mess with it until you do or understand the directions. Go though the general and q&a because I know there are already threads discussing setbacks and situations that your asking about.
Hope this helps.
One other thing to note is you need a different than stock kernal to overclock
Drewmungus said:
One other thing to note is you need a different than stock kernal to overclock
Click to expand...
Click to collapse
The problem is HTC's unlock method DOES NOT allow you to flash a kernel! I repeat, it DOES NOT allow you to flash a kernel. I would highly suggest waiting for AlphaRevX and Unrevoked to implement the latest HBOOT to be supported in their tool. It is being worked on and when it is done it will give 100% s-off and unlock nand write protection(or eMMC in our case). It will allow you to flash kernels, radios and whatever else your heart desires. I suggest holding off until Revolutionary is updated. They will then tell you if you need to do HTC's method before theirs or not. If you use HTC's method and then Revolutionary is updated and you want full unlock, there is no way to know if you are screwed or not. We really need a sticky thread describing the difference between the 2 unlock methods and the benefits of each one. There are tons of posts in Q&A and General about 'I have HBOOT 1.50, can I overclock my phone?'...The answer is NO, because you have to be able to flash custom kernels to overclock and HTC is not going to allow that to happen. If they did they would have tons of returned devices from people screwing up their phones from overclocking and flashing radios and what not. It really makes sense to me why HTC didn't fully unlock the phone, but if you wait for the Revolutionary tool to be updated, it will. By then we may even have the latest source code for HTC's 2.3.4 kernel and will have custom kernels to play with. Right now there is no overclockable kernels for the latest update from HTC because they haven't released the kernel source yet.
thats confirmed, no kernel. and dont try. screws things up a little. reflashed. no change. you think if i flash the stock kernel it would let me? i think probably not. rom was doing fine till i attempted kernel though. synergy. its nice. lot nicer with s-off im sure.
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Have you tried flashing a cwm recovery? I think I read someone had the same problem.seens your s-off you should still be able to flash a recovery, and after that's done then you can be able to wipe and flash anything you want, and you well even be able to downgrade your hboot.
Nope, it wont let me flash a recovery through fastboot...access denied (phone shows locked). I cant install it with "flash image gui" because i dont have root.
I know it should be an easy fix because I have the all important s-off...I just cant find how to do it.
taminrob said:
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Click to expand...
Click to collapse
S-Off just means that the security is off, and you're able to write onto the boot partition of the phone when flashing a ROM, in one shot. If your Hboot = 1.50, you may have to unlock your bootloader via HTCDEV method, your phone gets wiped. Try HTC SuperTool, maybe it will work, since you're S-Off.
http://forum.xda-developers.com/showthread.php?p=21538250
Follow my post and the links in there should get you back to 1.4
Sent from my HTC Evo 3D using Tapatalk
Thank you, that got me back in where I needed to be! Was able to load CWM again and restored from my back up...now all I need to do is make since of all the conflicting instructions to do this update so the icon goes away...found some that are fairly clear, but the links are broken now that the upload sites are blacklisted.
Either way, just glad to have my hboot back where it belongs.
I am beyond feeling like a ReeeTard right now. As someone who beta tests for a lot of ROM builders and knows a great deal about Android, software development etc... please don't reply to this with a smart a** remark. It helps no one and makes you look like just a jerk.
We all have our days where we simply cannot think straight, I am dealing with a great deal of stress, in my life, so forgive me for somehow not finding the answer to this question.
I updated my phone, using an RUU...My phone WAS hboot 1.40, now however it's hboot 1.50, and it's UNLOCKED (the bootloader) as well as S-Off, Am I forgetting to do something to have ROOT access?
So I am hboot 1.50 UNLOCKED and S-off
With all of those things I thought, because I cant seem to think clearly right now, that I was rooted. I however ran root checker and I am not.
Please throw me a bone and fill me in on what I am missing here. It's been a rough couple weeks for me.
Much appreciated.
quickfixguru said:
I am beyond feeling like a ReeeTard right now. As someone who beta tests for a lot of ROM builders and knows a great deal about Android, software development etc... please don't reply to this with a smart a** remark. It helps no one and makes you look like just a jerk.
We all have our days where we simply cannot think straight, I am dealing with a great deal of stress, in my life, so forgive me for somehow not finding the answer to this question.
I updated my phone, using an RUU...My phone WAS hboot 1.40, now however it's hboot 1.50, and it's UNLOCKED (the bootloader) as well as S-Off, Am I forgetting to do something to have ROOT access?
So I am hboot 1.50 UNLOCKED and S-off
With all of those things I thought, because I cant seem to think clearly right now, that I was rooted. I however ran root checker and I am not.
Please throw me a bone and fill me in on what I am missing here. It's been a rough couple weeks for me.
Much appreciated.
Click to expand...
Click to collapse
Hey! No worries man. You're almost there. All you need to do is flash a recovery now. Choose a recovery, and flash it, either a pg86img.zip or a recovery.img, and flash it. Once you have recovery flashed, either just flash a rooted ROM, or flash a su.zip. Then you should be good to go.
Sent from my PG86100 using Tapatalk
Thanks a lot man, I appreciate it. I knew I needed to flash superuser I just wanted to be sure it was just flash a recovery then su.zip
quickfixguru said:
Thanks a lot man, I appreciate it. I knew I needed to flash superuser I just wanted to be sure it was just flash a recovery then su.zip
Click to expand...
Click to collapse
You're welcome. Glad to help. Let me know if you have further questions. if you just decide to flash a su.zip, as opposed to an entire custom rom, you'd probably have the best luck looking in the old original TWRP thread for one. I know that had a su.zip posted in it. I'll see if i can find it for you real quick.
EDIT: Here's a super user zip http://techerrata.com/toastcfh/Shooter/su-2.3.6.3-efgh-fixed-unsigned.zip that I found in the 3rd post of this old thread http://forum.xda-developers.com/showthread.php?t=1192077&highlight=twrp+recovery. That's not the newest super user app, but it should work just fine, and you should be able to update it from there once you get it installed.
buckley nailed it!
i was actually unaware that updating your bootloader would still leave you s-off if you were on 1.4. that is interesting... although i would still never update.
did you know that it would still leave you with your NAND unlocked when you updated?
cobraboy85 said:
buckley nailed it!
i was actually unaware that updating your bootloader would still leave you s-off if you were on 1.4. that is interesting... although i would still never update.
did you know that it would still leave you with your NAND unlocked when you updated?
Click to expand...
Click to collapse
Yea, updating will still leave you S-off. You won't have a custom recovery anymore, and you'll be on hboot 1.5, but you still have S-off. There is pretty much no way that I know of to turn it back to S-on without going into fastboot and doing that 'fastboot setsecureflag3' command or whatever it is. The revolutionary team gave us some pretty damn permanent S-off, lol. I've seen lots of people take OTA updates, and still have S-off. You can even downgrade the hboot back to 1.4 if you wanted to, even though there really isn't a reason to. Having hboot 1.5 with S-off is just the same as having 1.4 with s-off, you don't need to do any extra stuff to flash.
ok so ill be honest. ive been out of the loop for a long time and have very little idea whats going on with android development and whatnot. im hoping someone can help me get to where i need to get. attached are screenshots of what firmware im on and and rom. i want to get onto cm9 and i have tried flashing it but it wouldnt boot. i think i have s-off and i dont know how to unlock it. (noob i know) any info helps and id really appreciate it. thanks
LWell, we know you are bootloader unlocked because you have a custom ROM installed. If you want CM9, and you are s-on, make sure you follow the instructions in the OP of that thread.
You can check your s-off status by shutting your phone off, pull battery, put battery back in, and press volume down and power until you see the white screen. Up in the top right it will say either s-on or s-off.
edward650 said:
ok so ill be honest. ive been out of the loop for a long time and have very little idea whats going on with android development and whatnot. im hoping someone can help me get to where i need to get. attached are screenshots of what firmware im on and and rom. i want to get onto cm9 and i have tried flashing it but it wouldnt boot. i think i have s-off and i dont know how to unlock it. (noob i know) any info helps and id really appreciate it. thanks
Click to expand...
Click to collapse
If you're s-off, there is no reason to unlock (aside from fastboot commands, but that seems trivial once you've achieved s-off). Also, looks like you're on GB firmware. If I was you, I'd RUU with the latest leak from AndroidPolice. If you're s-off, it's easy. Just re-flash amonra 3.15 after you run the ruu. You'll have the latest radios, as well as ICS. That's where to start; then it's very easy to flash a CM9 ROM.
iamwalterwhite said:
If you're s-off, there is no reason to unlock (aside from fastboot commands, but that seems trivial once you've achieved s-off). Also, looks like you're on GB firmware. If I was you, I'd RUU with the latest leak from AndroidPolice. If you're s-off, it's easy. Just re-flash amonra 3.15 after you run the ruu. You'll have the latest radios, as well as ICS. That's where to start; then it's very easy to flash a CM9 ROM.
Click to expand...
Click to collapse
i thought it had s-off but it is on and the top says unlocked. how can i changed it back to off? when trying to get on the RUU leak it wont work, ill try again tomorrow but maybe you know whats up
So you're S-On and locked, but you want to be S-Off? You need to run Jupunout-Bear if you just want to be unlocked go to HTC Dev. If you're unlocked your boot and radio partitions are still locked, but can be flashed via the fastboot command. If you're S-Off you can do it directly from the phone.
The wire trick for S-Off can be tricky to do perfectly, since you need to time it correctly which is 1.5 seconds. Someone made a metronome sound file but its a pain to start the process, play the sound file and then do the wire trick. I found out that the easiest way to do is it to just skip the file and use a rigid piece of wire and start with the ground pin depressed and then tap pin 1 twice since it's a lot harder to miss than by doing it vice versa, which I did multiple times. Also the words mississippi mississippi when said at a normal speed equal just about 1.5 seconds.
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