Hi, everyone. I hope someone can answer my questions or point me to the thread with the answer to it. Below is the information for my Spint Evo 3D running stock ROM:
Shooter XC Ship S-off RL
HBoot 1.40.1100
Android 2.3.4
HTC Sense 3.0
Software: Shooter_S_Sprint_WWE_2.17.651.5_odex
The last time I did an update of my phone after rooting was early this year. Basically I installed a zipfile provided by a user on this forum (apologize to that user for not being able to credit him) that allows me to get the OTA update on my rooted phone. Now that Sprint released the Ice Cream Sandwich update for EVO 3D, I am looking to upgrade the software again. The main question is...was there a thread for this topic where someone has provided a zipfile to allow updates to ICS for a rooted phone (stock rom)? Would someone please point me to it if they found it (sorry, did not see it)? Second, is the update process the same as before? Do I wipe cache and/or dalvik cache and then just install from zipfile? Any help is appreciated. Just didn't want to brick my phone. Normally I let my sister test things out on her device before I do the same thing but last year she decided to go with Motorola Photon while I sticked with HTC. Help? Thanks.
Tommy
xionchen4628 said:
Hi, everyone. I hope someone can answer my questions or point me to the thread with the answer to it. Below is the information for my Spint Evo 3D running stock ROM:
Shooter XC Ship S-off RL
HBoot 1.40.1100
Android 2.3.4
HTC Sense 3.0
Software: Shooter_S_Sprint_WWE_2.17.651.5_odex
The last time I did an update of my phone after rooting was early this year. Basically I installed a zipfile provided by a user on this forum (apologize to that user for not being able to credit him) that allows me to get the OTA update on my rooted phone. Now that Sprint released the Ice Cream Sandwich update for EVO 3D, I am looking to upgrade the software again. The main question is...was there a thread for this topic where someone has provided a zipfile to allow updates to ICS for a rooted phone (stock rom)? Would someone please point me to it if they found it (sorry, did not see it)? Second, is the update process the same as before? Do I wipe cache and/or dalvik cache and then just install from zipfile? Any help is appreciated. Just didn't want to brick my phone. Normally I let my sister test things out on her device before I do the same thing but last year she decided to go with Motorola Photon while I sticked with HTC. Help? Thanks.
Tommy
Click to expand...
Click to collapse
That's simple mate, but you will lose, recovery and root, I can help get them back, but first you will need to flash this http://cmw.22aaf3.com/shooter/radio/1.09.00.0706/PG86IMG.zip by placing on your sd card root directory and booting into bootloader and then following on screen instructions
gav-collins1983 said:
That's simple mate, but you will lose, recovery and root, I can help get them back, but first you will need to flash this http://cmw.22aaf3.com/shooter/radio/1.09.00.0706/PG86IMG.zip by placing on your sd card root directory and booting into bootloader and then following on screen instructions
Click to expand...
Click to collapse
Hi. Thanks for replying. Please bear with me as I am more of a casual user who barely have any inkling of why he is doing something, only how to get to S-Off, rooted through developers who provided step-by-step guide for "Dummies who want to Root their Phone". I have been in contact with Ramjet73 who is really kind to answer my questions but I am trying not to bother him too much hence I am trying to pass on any further questions that I have to other users such as yourself. So...thank you in advance.
From what Ramjet73 told me, I can just run the RUU.exe for 2.89.651.2 (Sprint ICS build) since I am S-Off. However he then inform me that I need to download a custom bootloader and custom recovery. This supports your comments that I will lose recovery and root after update? Ramjet 73 suggested a custom bootloader from ENG or JBear. How is that different from the bootloader that you suggested in your reply?
I assume that after I update both the ICS RUU and the custom bootloader, I will remain S-Off and rooted with superuser status and apps such as titanium backup and wifi tethering operational?
As for custom recovery, Ramjet 73 suggested 4Ext Recovery which I assume is 4Ext Recovery Updater (if I want a free version) or 4Ext Recovery Control if I am willing to pay for more options. Now in the past, I haven't really install any custom recovery other than what was installed when I used Revolutionary's tool to turn my phone to S-Off. I believe that installed Clockworkmod which I access when I boot to it using Power+Vol Down. Is Rom Manager the newest equivalent to that? What is your opinion on 4Ext Recovery vs Rom Manager.
So to summarize, I run the RUU.exe for ICS upgrade. Then I flash a bootloader like you recommended in your reply or one of the custom bootloaders from ENG or JBear. Then flash a custom recovery and I am all set? Sorry for all these questions and I hope you can help. Thanks.
I'm looking for a cut and dry answer to this as well. I'll be monitoring this and if I see or figure out anything first ill post here.
Sent from my EVO using xda premium
sullivan7221 said:
I'm looking for a cut and dry answer to this as well. I'll be monitoring this and if I see or figure out anything first ill post here.
Click to expand...
Click to collapse
I thought I made it as "cut and dry" as possible:
1. Flash the 2.89.651.2 RUU (.exe from Windows or .zip from the bootloader if you prefer that)
2. Flash the JBear Sprint ICS (1.58.5858) bootloader so you can use fastboot commands
3. Flash 4EXT recovery using the "fastboot flash recovery recovery.img" command
4. Flash the superuser.zip of your choice or a custom rooted rom from 4EXT
I have more detailed instructions in my guide and a single download with the software you need for each of these steps.
Is there something that you don't understand about these steps, or are you just waiting for someone else to confirm that they work?
Edit: If you are looking for another way to do it you can follow the steps in this post, but you will wind up with the stock 1.58 bootloader and won't be able to run most fastboot commands unless you flash a custom bootloader. It takes about as long to flash the firmware, superwipe and ROM in that post and still flash a custom bootloader as it does to perform the above 4 steps, which I believe give you a cleaner ICS base, but it's up to you. That option will save you from having to reflash recovery.
ramjet73
Hi, sorry if I sound like I am doubting you. Your method are pretty simple. Being a relative newbie who rarely tinker with his phone, I am being extra careful to make sure I understand everything before doing something. In any case, I am going to just do it following your procedure. Just downloaded the QADERSO.zip from your guide. I will follow the 4 steps below. If I encounter any problems, then I hope you or other knowledgeable members of the forum can help out. If everything works out great, I will also post to this thread. Thanks.
ramjet73 said:
I thought I made it as "cut and dry" as possible:
1. Flash the 2.89.651.2 RUU (.exe from Windows or .zip from the bootloader if you prefer that)
2. Flash the JBear Sprint ICS (1.58.5858) bootloader so you can use fastboot commands
3. Flash 4EXT recovery using the "fastboot flash recovery recovery.img" command
4. Flash the superuser.zip of your choice or a custom rooted rom from 4EXT
I have more detailed instructions in my guide and a single download with the software you need for each of these steps.
Is there something that you don't understand about these steps, or are you just waiting for someone else to confirm that they work?
Edit: If you are looking for another way to do it you can follow the steps in this post, but you will wind up with the stock 1.58 bootloader and won't be able to run most fastboot commands unless you flash a custom bootloader. It takes about as long to flash the firmware, superwipe and ROM in that post and still flash a custom bootloader as it does to perform the above 4 steps, which I believe give you a cleaner ICS base, but it's up to you. That option will save you from having to reflash recovery.
ramjet73
Click to expand...
Click to collapse
xionchen4628 said:
Hi, sorry if I sound like I am doubting you. Your method are pretty simple. Being a relative newbie who rarely tinker with his phone, I am being extra careful to make sure I understand everything before doing something. In any case, I am going to just do it following your procedure. Just downloaded the QADERSO.zip from your guide. I will follow the 4 steps below. If I encounter any problems, then I hope you or other knowledgeable members of the forum can help out. If everything works out great, I will also post to this thread. Thanks.
Click to expand...
Click to collapse
No problem.
I was actually responding to sullivan7221 because I thought all his questions were answered in my guide thread and then I saw his post in this thread that seems to be asking the same things. It's no problem if he wants consensus from more people, but I did take exception to his reference to a "cut and dry answer". I know that Samsung and other brands have simpler "one click" processes for rooting because I've used them myself, but I've tried to refine and simplify the root and S-OFF process for the Evo 3D as much as possible, and I tested a "one click" root utility that popped up in this forum a few weeks ago and it didn't work.
I understand that you and sullivan7221 aren't looking for root and S-OFF since you both have that already, but it's still important to use a reliable and consistent method for upgrading to the offical Sprint ICS build, which may not be the easiest.
Good luck with your upgrade!
ramjet73
Well...HELP! I successfully update my phone to ICS (not so hard). Then I hit the wall called "Step 2" and promptly bounced right off on my ass. The first thing I try to do was flash the jb_boot.img through fastboot cmd. I put my phone (which is still S-Off like you said, H-Boot 1.58 with "Locked" all the way up top) into Fastboot then connected my phone to usb, resulting in Fastboot USB. Then I use the command "Fastboot flash boot jb_boot.img". Then the problem happened. It said:
writing 'boot'
failed (remote: not allowed)
From discussions online, I also checked to see if it sees my device using 'fastboot devices" and it seems to recognize it: "HT179..."
How do I unlock my bootloader? What did I do wrong? I have the jb_boot.img and jb_boot.zip from your file and the pg86img.zip that was recommended by the poster above containing a radio.img. Any other way to flash it?
Help?
ramjet73 said:
No problem.
I was actually responding to sullivan7221 because I thought all his questions were answered in my guide thread and then I saw his post in this thread that seems to be asking the same things. It's no problem if he wants consensus from more people, but I did take exception to his reference to a "cut and dry answer". I know that Samsung and other brands have simpler "one click" processes for rooting because I've used them myself, but I've tried to refine and simplify the root and S-OFF process for the Evo 3D as much as possible, and I tested a "one click" root utility that popped up in this forum a few weeks ago and it didn't work.
I understand that you and sullivan7221 aren't looking for root and S-OFF since you both have that already, but it's still important to use a reliable and consistent method for upgrading to the offical Sprint ICS build, which may not be the easiest.
Good luck with your upgrade!
ramjet73
Click to expand...
Click to collapse
Well...color me stupid (and an ass) for not reading in depth ramjet's guide. From ramjet's guide, I went to mpgrimm2's "Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 9-25-12" thread which eventually lead to ramjet's post with all the different bootloaders available. As suggested, I used JB's ICS bootloader and now in the bootloader page, it no longer say "locked" but "JuopunutBear" now. Onto flashing recovery.
xionchen4628 said:
Well...HELP! I successfully update my phone to ICS (not so hard). Then I hit the wall called "Step 2" and promptly bounced right off on my ass. The first thing I try to do was flash the jb_boot.img through fastboot cmd. I put my phone (which is still S-Off like you said, H-Boot 1.58 with "Locked" all the way up top) into Fastboot then connected my phone to usb, resulting in Fastboot USB. Then I use the command "Fastboot flash boot jb_boot.img". Then the problem happened. It said:
writing 'boot'
failed (remote: not allowed)
From discussions online, I also checked to see if it sees my device using 'fastboot devices" and it seems to recognize it: "HT179..."
How do I unlock my bootloader? What did I do wrong? I have the jb_boot.img and jb_boot.zip from your file and the pg86img.zip that was recommended by the poster above containing a radio.img. Any other way to flash it?
Help?
Click to expand...
Click to collapse
Okay, final update for those looking at this thread. I now have stock ICS, remained S-OFF and have superuser access. Basically I followed ramjet who was helping me out. The first thing that someone in my same position who wants to do the same thing, should navigate to ramjet's guide: (http://forum.xda-developers.com/showthread.php?t=1889438). Download his file (QADERSO.zip) and unzip it.
1) I turned on USB debugging on my phone and connected to my pc using "charge only" option.
2) I clicked on RUU.exe file in ramjet's QADERSO\RUU folder which then update my phone to ICS. When I access the bootloader, it now said "Locked", then "shooter xc ship s-off RL" and finally "Hboot1-58.5858". So now i have ICS, still S-off but with an upgraded locked bootloader.
3) Then I copied the custom bootloader "PG86IMG_jb_hboot_Sprint_ICS.zip into the root directory of my sd card (the zip file can be found in another of ramjet's post (http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7) and renamed it PG86IMG.zip. Once you go into the bootloader, the zip file will automatically update. Now instead of "Locked" on the top, you should have "JuopunutBear".
4) First remove the previous zip file from the directory. I put the "SuperSU-v0.96.zip" from the QADERSO\Root folder in the root director of my sd card again. then i access my bootloader once again.
5) I went into fastboot and then connect to my Pc with usb. It should now say "Fastboot USB".
6) you can now flash any recovery img that you want. This is where I differ from ramjet's suggestion of 4ext as I did a backup of my system before all of this with clockworkmod recovery.
7) once the recovery of your choice is installed, then just install the supersu.zip file from your sd card and you should have a rooted phone.
Thanks to ramjet for his guide and his help. Now onto my next problem. going back to the state I was before updating to ics. Posting another thread about it. Anyone who can help out, please do. Thanks.
xionchen4628 said:
Well...color me stupid (and an ass) for not reading in depth ramjet's guide. From ramjet's guide, I went to mpgrimm2's "Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 9-25-12" thread which eventually lead to ramjet's post with all the different bootloaders available. As suggested, I used JB's ICS bootloader and now in the bootloader page, it no longer say "locked" but "JuopunutBear" now. Onto flashing recovery.
Click to expand...
Click to collapse
Related
My phone has Android 2.2.2 but with HBoot 1.03, so whenever I try Revolutionary or uNRevoked, it tells me that my firmware is too new. I've been searching through the forums for a few days without much success, but if I've missed something somewhere, I apologize in advance for not spotting it sooner. Thank you for any help you can provide.
Scott
Since you upgraded to 1.03, you will have to unlock the bootloader using HTC's method: http://www.htcdev.com/bootloader/unlock-instructions (You will have to create an account on their site and log in to view the instructions.)
Where do we go from here?
I've unlocked the bootloader on my Aria, and it says that hboot is at version 1.03. How can I install a custom ROM from here (cyanogenmod)?
Adam_J_T said:
I've unlocked the bootloader on my Aria, and it says that hboot is at version 1.03. How can I install a custom ROM from here (cyanogenmod)?
Click to expand...
Click to collapse
Follow the instructions here: http://forum.xda-developers.com/showthread.php?p=14693680.
NB: Read all instructions before starting.
Getting a recovery on to an unlocked bootloader
Okay, I followed those instructions, but they posted the wrong recovery. It's for those who have just run revolutionary, and since my HBOOT was at 1.03.0000, it was impossible for me.
Here's what I did first:
1. I restored to default AT&T FroYo firmware, a download from HTC's Website.
2. I went to htcdev.com/bootloader to start the process. The Aria had to have an HBOOT upgrade from 1.02.0000 (what I was on because of the FroYo restore, although if I had known it then I would've just run revolutionary) to 1.03.0000.
*An aside: I've not had S-OFF before because for some reason I was running a totally different HBOOT. I got this phone used and that's probably why.
3. I unlocked the 1.03.0000 bootloader and realized I was screwed, because I had a) no root b) no recovery and c) no easy way to get back to the other HBOOT or load a recovery.
4. After unlocking the bootloader using HTC's methods (you have to register for a developer account, and they tell you to get three files that they provide: adb.exe, AdbWinApi.dll, and fastboot.exe) I was at stock FroYo.
5. I found a clockworkmod recovery image for the Aria on the internet. I've attached it for convenience.
6. I booted the Aria to HBOOT, plugged it in, and went to fastboot. It said "FASTBOOT USB" above my options. I already had the drivers installed, so no big deal.
7. Using the instructions in this thread, I was able to flash an alternate recovery. It's easy enough to get the .zip of the recovery off of clockworkmod's website, but I just decided not to do that for one reason or another. I didn't think about flashing a .zip, but it's easy enough. Same procedure.
8. I navigated to the directory I had all my files in from HTC's bootloader unlock process. I ran this:
fastboot flash recovery cwm-recovery.img
alternatively, you can run
fastboot flash zip <clockworkmod recovery for aria>.zip
9. I was successfully able to boot clockworkmod recovery and restore my backup of CM7.2.
I guess, if you wanted, you could flash CM7 or some other firmware with the same method through fastboot without going through recovery. I've not had much experience and I didn't want to brick my phone seeing as I don't have a backup device.
Adam_J_T said:
Okay, I followed those instructions, but they posted the wrong recovery. It's for those who have just run revolutionary, and since my HBOOT was at 1.03.0000, it was impossible for me.
Click to expand...
Click to collapse
I was referring to the instructions .
Adam_J_T said:
3. I unlocked the 1.03.0000 bootloader and realized I was screwed, because I had a) no root b) no recovery.
Click to expand...
Click to collapse
Unlocking a device's bootloader does not provide these things (it can allow you to get them though ).
Theonew said:
Unlocking a device's bootloader does not provide these things (it can allow you to get them though ).
Click to expand...
Click to collapse
I didn't expect it to, but I had no idea where to go from there; like I said previously, I'm kind of new. Thanks for all the help!
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.
-DISCLAIMER: DO THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE THIS GUIDE CAUSES YOU TO DO. THIS WORKED FOR ME, BUT RESULTS MAY VARY.-
-PLEASE READ THE ENTIRE GUIDE BEFORE FOLLOWING ANY STEPS TO AVOID ANY CONFUSION-
-THIS GUIDE ONLY APPLIES IF YOU ARE ROOTED WITH S-OFF ON HBOOT 1.58-
-IF YOU HAVE INSTALLED THE ICS OTA UPDATE THEN YOU SHOULD HAVE HBOOT 1.58, UNLESS YOU HAVE DOWNGRADED.-
-IF YOU HAVE DOWNGRADED YOUR BOOTLOADER AND ARE NOT ON HBOOT 1.58, LEAVE THIS PAGE-
-I ALSO RECOMMEND THAT YOU HAVE TWO SEPARATE SD CARDS YOU CAN USE FOR THIS. NO DATA WILL BE DELETED OFF OF EITHER-
-KEEP IN MIND, THAT IF YOU DO THIS, YOU MAY NOT BE ABLE TO BOOT BACK INTO YOUR STOCK ICS ROM FROM THE OTA UPDATE-
-YOU WILL ALSO NEED A MICRO SD CARD READER TO PLUG YOUR SD CARD STRAIGHT INTO YOUR COMPUTER-
If you are not rooted, and do not have S-OFF, check out this guide by crimsy. It has all the instructions you need to root and obtain S-OFF. It worked for me.
Now for the fun part. You're positive you're on HBoot 1.58, and you're getting bootloops when you flash roms. The fix is actually quite simple.
First, go to this thread by mpgrimm2
Scroll down until you see a post on the thread by ramjet73. This post contains a list of HBoot downloads. These are all free.
First, find the one that says "PG86IMG_JBear_1.58.5858_hboot_Sprint_ICS.zip". Download that to use as a backup.
Now, we're gonna go by exactly what I did. But I recommend you do your own research on which Hboot is the best for whatever ROM you're trying to flash.
First off, all of these are already S-OFF, so you wont need to redo the wire trick.
Anyway, I downloaded the first one on the list, "PG86IMG_1.40-hboot.zip".
Now, to install this, you're pretty much gonna trick your phone into "updating" to it.
To do this, just download the HBoot you've chosen to be the best for you (in my case it was the first one on the list, 1.4).
Now just rename that file to "PG86IMG" without quotation marks.
Next, copy it to the root of your SD card.
The rest takes place on your phone. Power off your phone, and boot into the bootloader (Hold volume down + power button).
If you've done the previous steps correctly, your bootloader should detect the HBoot you downloaded, and ask if you want to update.
Volume up= Yes
Volume down = No
If you're positive about this, then choose "Yes".
It should update and tell you to reboot.
This is where I ran into a problem. I was still running stock ICS from the OTA update, and I got stuck in a bootloop. My phone would freeze at the the Sprint animation, turn off, and repeat. I thought I could just disregard it, boot into recovery, and flash my new ROM. But every time I booted into the bootloader all I could do was either update or reboot. This is where that micro SD card reader comes in. Just pop your SD card into your computer, and remove the HBoot you downloaded. Then put your SD card back in your phone and try rebooting into the bootloader again.
If it boots into your bootloader as normal, then that should be it. You should be on whatever HBoot version you chose to download (this worked for me with 1.4)
Now try flashing that ROM again and let me know how it goes.
Keep in mind, different ROMS may have different results. You may still need to flash certain kernals or wipe specific partitions as instructed by the developer of the ROM you want to flash.
Feedback is appreciated.
I prefer to put the PG86IMG file on my sd card while booted up normally. Then reboot straight into recovery bypassing the hboot screen. Wipe, flash rom then boot into bootloader and run the update. This prevents getting bootloops and keeps you from having to use the computer to rename or remove the file. Saves you some work!
Sent from my PG86100 using Tapatalk 2
If you are S-OFF you can also flash a different bootloader from fastboot on a PC avoiding the need to deal with the PG86IMG.zip file at all, then boot directly into recovery from the new bootloader. See my post here for alternative methods to flash a new bootloader when S-OFF, including multiple ways to delete the the PG86IMG.zip file when flashing one from the current bootloader.
ramjet73
Theres also
fastboot oem rebootRUU
fastboot flash zip PG86IMG.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
enter recovery & clear cache then reboot.
I believe this is the fastest way to flash a different hboot
iTzLOLtrain said:
I believe this is the fastest way to flash a different hboot
Click to expand...
Click to collapse
If you look at the guide I linked in my previous post which has similar instructions that I took from the unlimited.io website and tested, you can do this fastboot sequence to clear cache, flash a different bootloader, then reboot back to your current ROM:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip new_hboot.zip
fastboot reboot
Click to expand...
Click to collapse
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
If you need to flash another ROM before the reboot or do something else in recovery, you can issue the "fastboot boot recovery.img" command instead of "fastboot reboot" to go directly to your custom recovery since there is no "fastboot reboot-recovery" command.
ramjet73
ramjet73 said:
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
Click to expand...
Click to collapse
I know.. & because this thread is about bootloaders I thought that's how I would explain myself. Instead of going into more detail & say how you can flash .img files through that process....
iTzLOLtrain said:
I know.. & because this thread is about bootloaders I thought that's how I would explain myself. Instead of going into more detail & say how you can flash .img files through that process....
Click to expand...
Click to collapse
That's fine.
For clarification, the command I suggested to get back to recovery (fastboot boot recovery.img) is not flashing it, only booting it directly to avoid having to go to the bootloader first to get to recovery.
ramjet73
Guys, I made this guide because it seemed like the most basic and simple way to do it. I speak from experience when I say that the command prompt can be a little intimidating. It can be get pretty nerve wrecking when you dont have a back up phone and you feel like you have lots of room for error and you're terrified you might brick your device. This guide doesn't use any sort of external commands, making it seem a lot less manual. I wasn't trying to show people the fastest way. Just the easiest, less nerve wrecking way.
sawyerbenjamin said:
Guys, I made this guide because it seemed like the most basic and simple way to do it. I speak from experience when I say that the command prompt can be a little intimidating. It can be get pretty nerve wrecking when you dont have a back up phone and you feel like you have lots of room for error and you're terrified you might brick your device. This guide doesn't use any sort of external commands, making it seem a lot less manual. I wasn't trying to show people the fastest way. Just the easiest, less nerve wrecking way.
Click to expand...
Click to collapse
The guide I linked in post #3 of this thread provides alternatives for flashing a different bootloader and for deleting the PG86IMG.zip file if you choose that method. Some people are very comfortable with the fastboot commands and that method saves having to worry about deleting the PG86IMG.zip. It's always good to have alternatives because one size never fits all.
You asked for feedback in the OP and we're providing that.
ramjet73
ramjet73 said:
The guide I linked in post #3 of this thread provides alternatives for flashing a different bootloader and for deleting the PG86IMG.zip file if you choose that method. Some people are very comfortable with the fastboot commands and that method saves having to worry about deleting the PG86IMG.zip. It's always good to have alternatives because one size never fits all.
You asked for feedback in the OP and we're providing that.
ramjet73
Click to expand...
Click to collapse
Feedback - Information about reactions to a product, a person's performance of a task, etc., used as a basis for improvement.
You were promoting your own threads, not giving feedback. I have to thank you for the post that helped in making this guide, but your alternate methods aren't really necessary. I'm not sure how to say that without sounding rude or hostile, but Im sure you get my point.
sawyerbenjamin said:
You were promoting your own threads, not giving feedback. I have to thank you for the post that helped in making this guide, but your alternate methods aren't really necessary. I'm not sure how to say that without sounding rude or hostile, but Im sure you get my point.
Click to expand...
Click to collapse
OK, and if you want to be blunt my point was that your guide wasn't really necessary, and I think that's feedback on your "product", since the content was already covered in the guide I setup for people that want to change bootloaders when S-OFF, but if people prefer to use your version in the OP of this thread that's fine with me.
As I already stated, alternatives are good.
ramjet73
ramjet73 said:
OK, and if you want to be blunt my point was that your guide wasn't really necessary, and I think that's feedback on your "product", since the content was already covered in the guide I setup for people that want to change bootloaders when S-OFF, but if people prefer to use your version in the OP of this thread that's fine with me.
As I already stated, alternatives are good.
ramjet73
Click to expand...
Click to collapse
Ouch. That was uncalled for. To far bro. This is just a guide trying to help people. Not a place to get all ugly. Lol.
Dear sir
i have the same problem my phone get stuck on white htc screen
unrooted
s-on
relocked
hboot 1.5.0007
so can any one help me how to solve this problem
thanks
i also tried factory reset and to setup ICS ruu but it got stop when it try to reboot boat-loader and still the same problem
when trying to flash any thing recovery or boot failed and trying to put rom as pg86img also failed any one help me please this phone part of my daily life:crying::crying::crying:
The problem with s-on is that the kernel does not flash when you flash a rom. That is why it won't boot.
To fix the issue after flashing a rom, you need to pull the boot.img from the rom.zip and use fastboot to flash it.
fastboot flash boot boot.img
There are two options when you are s-on and flashing roms to flash the kernel with the rom and avoid bootloop.
The no pc method:
The easiest method is to use 4ext recovery with smart flash enabled. That will allow you to flash roms and kernel and avoid bootloop.
The PC method:
Keep a recovery.img in your fastboot directory. When you want to flash a rom, boot your recovery into the phones memory which allows you to flash the kernel with the rom.
You use: fastboot boot recovery.img
Then just install the rom once booted into recovery. While it seems the same, Booting into recovery using fastboot is different and will allow the kernel to flash.
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.
Please help. I have unlocked this phone through HTC Dev. I have flashed a custom recovery. Somewhere through this process, the original installation of the factory rom from VM was deleted. That doesn't bother me because I was never going back to it anyway, but If I had it right now, I wouldn't be here. I have tried to use the RUU exe in fastboot and the RUU zip in recovery from here. Neither will install, exe throws errors and the zip returns [bad]. I have also tried the [ROM] NegaLite-BluRom-JCFunk | 2.95 | Sprint/VM | Sense/Apex/Nova | 03/25/2014. This eventually installed, but will not boot even with installing boot.img separately. I followed all directions to the best of my ability, but by no means am I saying I did correctly, but I am pretty sure I did. So to recap - I have whats in the title, but no rom whatsoever installed that can be accessed. Any takers?
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Click to expand...
Click to collapse
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
oD33z said:
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
D33z
Click to expand...
Click to collapse
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Click to expand...
Click to collapse
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
oD33z said:
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
Click to expand...
Click to collapse
here's the thread
http://forum.xda-developers.com/showthread.php?t=2831444
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I am great with linux, but was under the assumption it needed to be burned to cd and that USB was not an option, please advise if not the case. I have read a ton and I remember reading about Unknownforce, but cant remember if thats the case or not.
Off topic: I learned from you that it has to be locked to go stock, but does it need to be unlocked to flash your rom or locked as well?
Unlocked for custom, locked for stock.
Here is unknownforce ultimate tool,
there was a live cd version made for windows users scared of linux.
I use tiny core linux for this, Ubuntu tries to mount all the partitions and you only have a 5 second window when they are writeable. I have used Ubuntu, at first, but preferred tinycore.
But first you are going to need to get stock.zip to install.
http://forum.xda-developers.com/showthread.php?t=1653777
I would do fastboot boot recovery.img
Then install negalite, so atless you can boot the phone
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
here is 4ext recovery I would use this one first until you get used to things, best recovery for 3d.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
oD33z said:
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
Click to expand...
Click to collapse
did you fastboot boot?
There are several custom recoveries out there.
Here is thread for 4ext
http://forum.xda-developers.com/showthread.php?t=1408936
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
What I meant was, in your opinion, is the 4ext a better recovery than the unofficial TWRP?
During the install of Negalite at the point of -Setting Up Kernel Over-Clock Settings
under this it reads: assert failed: write_raw_image("/tmp/newboot.img","boot")
Is this a red flag of something not going right in any way?
After this I click Next>Recovery>Wipe Dalvik>Reboot and it boots into Fastboot. Whats happening at this point?
Since I am basically starting from scratch and the end goal is to have a kitkat rom and possibly S-OFF(if its a must to do so).
What all needs to be done as far as formatting, tweaks, or anything else to achieve the best performance, space, or anything you can think of?
Thats if you dont mind sharing. I appreciate your time and if I can be of service to you in any way, I will.
I am currently on the 4ext recovery with 1GB sd-ext 0 swap and formatted Ext4.
fastboot boot recovery.img
flashrom.zip from recovery
reboot, wipe dalvik, reboot
Negalite.zip installed with no errors whatsoever.
Thank You.
Beautiful smooth running rom btw.
Does all that above sound like I did the right things as for setting up and installing?
4ext is most stable, the unofficial has new features like f2fs and selinux, but 95% stable.
fastboot boot recovery.img is an old work around, also used to flash boot.img with fastboot. That is ok with roms that include a whole boot.img but roms like mine use a dynamic boot.img. Basically the installer makes the boot.img using your choices.
From what I know about Kitty kat I think you need to downgrade hboot or be s-off. Not sure I've stayed on ics for stability because I still use this phone. Also there is a new version of negalite on svn, just takes hours for me to upload a zip version.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Revision 7
Are you sure this is the latest?
oD33z said:
Revision 7
Are you sure this is the latest?
Click to expand...
Click to collapse
Lol, yes since I updated it a few weeks ago
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
I should have worded that different really, the revision numbers threw me, I honestly was just making sure I was in the right place. 48mb smaller, anything stripped?
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Click to expand...
Click to collapse
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
oD33z said:
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
Click to expand...
Click to collapse
Here. Try this
https://www.androidfilehost.com/?fid=23578570567720169
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer