[HBOOT][11/14/12] JET - The Jewel/Evita Toolkit (Linux) - Sprint HTC EVO 4G LTE

Disclaimer: This is BETA. It works well, but may still set fire to your house if you anger it.
UPDATE 11/14/12 - Updated OP with SLS's fix for device detection.
JET - The Jewel/Evita Tool "kit."
JET performs several useful functions, including:
Downgrading your HBOOT to 1.12, allowing the use of LazyPanda instead of DirtyRacun (S-OFF without having to wipe the phone if you already have root) Note that this is unsupported by Team Unlimited, however it works just fine.
SuperCID (For downgrading firmware via RUU)
Partition/IMEI backup.
Detection of eMMC partitions on a phone stuck in Qualcomm download mode
Possible unbricking of your device (depending on circumstances)
JET is and always will be 100% open source and with full support given here on XDA.
Changelog
11/9/12 - Name change to better reflect the direction of this project. Ported to Evita. Rewrote device detection code.
11/1/2012 - Added SuperCID capability
10/24/2012 - Modified emmc_recover to catch stalls at "Wait device /dev/sdXXX......" and try to recover.
10/21/2012 - Added --recover and --unbrick command line options
10/19/2012 - Beta posted
Click to expand...
Click to collapse
Credits:
Credit for the original downgrading idea belongs to Mac_Gyver as seen in this post:
http://forum.xda-developers.com/showthread.php?t=1932914
This post refined that process and can still be referenced for manual downgrading:
http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Closeone for code submissions and a steady flow of awesome ideas.
SouL Shadow for some slick logging code
Initial Testers (AKA People willing to let a total stranger intentionally brick their phone for SCIENCE!)
AZ Fadeout
benny3
kjcmusic17
michael.stollaire
My lovely wife (distract with shiny object, snatch phone, cackle wildly, proceed to brick)
Some local folks not on XDA
absolutelygrimm and 18th.abn for consulting on the Evita side of things.
The XDA community for rallying behind this project and offering support to your fellow members
Click to expand...
Click to collapse
Requirements
Unlocked bootloader and a recent TWRP already flashed. (RegawMOD Rooter works well for this)
A NATIVE Linux installation, or a LiveCD/Wubi install. Virtual Machines are NOT SUPPORTED.
[*]A 32 bit Linux installation/CD, or install ia32-libs or ia32-libs-multiarch
Linux Kernel v3.0 or higher (Ubuntu 12.04 LiveCDs meet this requirement)
USB Debugging turned on
Click to expand...
Click to collapse
FAQ
Q: Help! The tool keeps saying "Failed to flash HBoot" repeatedly. What do I do?
A: This is a timing issue. If the tool can't get a good lock on your phone, it will give and error and then try again. It will keep trying until it locks onto the phone and can flash. In addition, it is safe to unplug and replug the USB cable during this step, even to another USB port.
Q: This thing is taking forever!! Is it supposed to?
A: The process usually takes about 10 minutes but can take 15 or longer depending. Unfortunately the process for flashing the bootloader is rather painful, and has to be done in very small pieces. Thank HTC for that one. Ubuntu is also partially to blame.
Q: Is this a bootable CD? Can I use this from Windows?
A: This is NOT a bootable LiveCD. A LiveCD version (with further enhancements) is in the works.
Q: Is there/Will there be a Windows version?
A: No. Nor are there plans to make a Windows native version. There are some inherent issues with the way Windows deals with USB devices that prohibits us from accessing QDL. If you're not comfortable trying/using Linux, I suggest you wait for the LiveCD to be finished.
Click to expand...
Click to collapse
Instructions:
Boot Linux.
Download attached package.
Unzip to somewhere you have write access (/home/ubuntu for Ubuntu LiveCD users)
Open terminal.
cd to working directory.
$ chmod +x jet
$ sudo ./jet
Follow the onscreen instructions.
/happydance
Click to expand...
Click to collapse
Command Line Options
Code:
-b or --backup : Backup mode only (make bakp4 and fsp4, don't force QDL)
-c or --cidpreserve : Don't SuperCID the backup P4 file
-d or --detect : Find device (/dev/sd?)
-r or --recover : Load HBOOT 1.12 and existing backup P4 (for people who stalled after QDL force)
-s or --supercid : SuperCID mod for nonbricked phones
-u or --unbrick : Load existing backup P4 file ONLY. (Quit QDL without downgrade)
Click to expand...
Click to collapse
To do:
P4 file generation from user entered MEID.
Merge both HW versions of JET and detect device at load.
LiveCD
Click to expand...
Click to collapse
Source:
You can follow code revisions for the shell script here:
https://github.com/yarrimapirate/JET
LiveCD Development is underway. You can follow the code here:
https://github.com/closeone/JET
I use a modified version of Fuses emmc_recover. I have forked his source here:
https://github.com/yarrimapirate/emmc_recover
Click to expand...
Click to collapse
A big Thank You to all who've sent donations! Caffeine and beer help generate code, and a few extra bucks convinces the wife it's worth the time I spend glued to my PC/phone. Your donation money is also being used to buy devices to further test/develop with. :good:

o yut!!!! ill take 1#

i'll take #2!
I already have s-off but this is sweet!

Fixin' to unlock mine. I might give this a shot.

nice to have this around

Never done anything like this, but I understand all the terminology and I'm pretty sure I understand what happens every step along the way. Never used Linux, but I can follow directions, so I think I might try this...

kjcmusic17 said:
Never done anything like this, but I understand all the terminology and I'm pretty sure I understand what happens every step along the way. Never used Linux, but I can follow directions, so I think I might try this...
Click to expand...
Click to collapse
PM me.... I'm about to start round 2 of testing and I need a couple more testers.

yarrimapirate said:
PM me.... I'm about to start round 2 of testing and I need a couple more testers.
Click to expand...
Click to collapse
Done and Done

I'd volunteer but my partitions are borked somehow and now I have to try and back up my data so I can reinstall everything. Somehow this has to be the gf's fault, I caught her running as root the other day just so she could change the font color on the time. *sigh*

om4 said:
I'd volunteer but my partitions are borked somehow and now I have to try and back up my data so I can reinstall everything. Somehow this has to be the gf's fault, I caught her running as root the other day just so she could change the font color on the time. *sigh*
Click to expand...
Click to collapse
Take it out of that $200 you owe her.

PC not phone lol

I need one.

Nice Work! I am now on hboot 1.12 Thanks

om4 said:
PC not phone lol
Click to expand...
Click to collapse
Why should that matter?
hurled from my AOKP'd Evo LTE. Enjoy.

She screwed up my pc not my phone lol

Now I feel comfortable with the idea of swapping my phone. I have 3 dead pixels, but feared getting a 1.5/1.9 hboot device! Thanks guys!
Sent From My HTC Evo 4G LTE, On The Now Network From Sprint!

Well im s-off again ....w00t!!

Thinking real hard about trying this. I'm no linux expert but I've used it full time for 5 years. Might give it a go if I have some free time this weekend.
Edit: Also, Yarr, do you have a PayPal account?
Edit2: LOL, on the web interface Yarr's PayPal is stupidly obvious. Not so much on Tapatalk.

cfbauer said:
Thinking real hard about trying this. I'm no linux expert but I've used it full time for 5 years. Might give it a go if I have some free time this weekend.
Edit: Also, Yarr, do you have a PayPal account?
Click to expand...
Click to collapse
Once complete, if you can execute some shell commands you'll have no trouble with this.
Paypal link is in my profile.

Wicked genius and balls in this thread, here.
hurled from my AOKP'd Evo LTE. Enjoy.

Related

[GUIDE]Complete Guide to Obtain S-OFF, Flash Recovery, and Install ROOT for the EVO3D

Hello everyone,
I wanted to take some time today to make a very clear and concise guide on how to complete the root process for the EVO3D. I understand that there is at least one other floating around at this point. If you don't have a firm grasp of how all of this works though, you may run into problems or have questions. I commissioned my guide to try and add clarity to the process and to also teach our communities newest members some of the ins and outs of modding our phones. The guide is far too large to post in a thread, therefore I've created a PDF of it and am offering it for download.
Feel free to mirror my guide and provide me with the link so that I can add it below.
Below is a Preface and Contents of the Guide. Feel free to ask questions or address any concerns you may have as I will be revising the guide.
The Complete Guide to Obtain S-OFF, Flash Recovery, and Install ROOT for the EVO3D
Authored by: sidepart of the
XDA-Developers Forum
Revision 1.1 - Published July 30, 2011​
Preface
Prior to reading this document, please be aware that as a disclaimer, I am not responsible for anything that goes wrong in this guide. Some people will run into issues that others do not. This is especially true with the differing versions of the Android-SDK. Some advanced users are using an older version which uses different commands than are offered by the latest Android-SDK. I encourage you to ask questions and keep an open mind. Try to understand the commands that are given here, and how you might have to be flexible in changing them to work for your situation. If at any time you are not comfortable with this process I highly recommend seeking out assistance from a more knowledgeable friend.
What this Guide Assumes
I assume that you will be downloading the latest version of the Android SDK which at the time of this document’s creation is R12. I also assume that you are using Windows 7, but this translates very easily into Windows Vista or XP.
Disclaimer
I am not responsible for any problems or fatal errors that may or may not occur through the process of performing the instructions of this guide. If at any time you are not comfortable with this process I highly recommend seeking out assistance from a more knowledgeable friend.
Contents of this Guide
What is S-OFF, Recovery and Root?
It’s not Just “ROOT”. Getting Past Outdated Nomenclature.
When I Say, “Do this”, Perform the Following Steps
Going to HBOOT
Booting into Recovery
Enabling USB Debugging
Install the Android-SDK
Obtaining S-OFF Status
Obtaining “unrevoked & AlphaRev’s: Revolutionary S-OFF & Recovery Tool”
Common Questions
Running “unrevoked & AlphaRev’s: Revolutionary S-OFF & Recovery Tool”
Common Questions
Flashing a Recovery Program
Flashing the TeamWin Recovery Project Recovery Program
Flashing or Installing the Superuser Management Program (Root)
Conclusion
Acknowledgements
Click Here to Download
Changelog
Revision 1.1 - July 30, 2011
Fixed some glaring grammatical and spelling errors.
Added a Common Questions section under item 4b.
Added a common question to 4b,i. It instructs users on how to paste their Beta key-code into the Revolutionary EXE program.
Fixed some formatting.
Used your guide and had no problems thank you!
Have not used it yet but this is very helpful... will be rooting my wifes e3d tonight... wasn't going to do it off of the other thread... I had no idea what it was talking about. Thanks for taking the time to put this together
Sent from my SPH-D700 using XDA App
Kind of hilarious to see my access.log right now. Lots of people looking at the guide interspersed with a few people discovering my site's index.html.
Used your guide and almost worked flawlessly The only problem I had was flashing the TeamWin recovery with the following command: ..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
The img that I downloaded through the site was like 1.0.1, but the error was on my end. Otherwise awesome guide!
So much info!!! love it.. nice
Sent from my PG86100 using www.psvitahacks.co app
bryangene said:
Used your guide and almost worked flawlessly The only problem I had was flashing the TeamWin recovery with the following command: ..\tools\fastboot.exe flash recovery recovery-twrp-shooter-1.0.0.img
The img that I downloaded through the site was like 1.0.1, but the error was on my end. Otherwise awesome guide!
Click to expand...
Click to collapse
I think they may have updated since I first published. I might see if I can emphasize that you're supposed to use the downloaded filename in the command.
Excellent guide!
Sent from my PG86100 using XDA Premium App
Lovely guide! for those who get
E:Error in /tmp/sideload/package.zip
(status 0)
just reflash su >_>
zander145 said:
Lovely guide! for those who get
E:Error in /tmp/sideload/package.zip
(status 0)
just reflash su >_>
Click to expand...
Click to collapse
I actually tried to load the zip from http://goo-inside.me/superuser and it wouldn't work. Retried it quite a few times and got the same error. I found an unsigned version of it in clark44's guide and that one worked just fine. Not sure what the problem was, hence my recommendation to grab superuser from the market and follow it's instructions instead. Seems to be working out well.
I think I might add something about this to the guide if too many people are running into the problem.
Any problems with not being able to send/recieve calls/texts with this? Haven't really messed around too much with the girlfriend's phone b/c she's terrified of not being able to get calls and what not..
I know this is a beta setup for now, so i'm assuming it'll turn into a simple one click type of thing when it gets to that point..?
Edit: I went through all this on my phone and had no problems really except having to call Sprint ..
Followed the guide as instructed...revolution wont recognize my device...it just hangs on waiting for device. I double checked to ensure usb debugging was enabled but it just hangs there.. Again i did follow the guide from step 1 and this is where im at...any suggestions?
SBERG117 said:
Followed the guide as instructed...revolution wont recognize my device...it just hangs on waiting for device. I double checked to ensure usb debugging was enabled but it just hangs there.. Again i did follow the guide from step 1 and this is where im at...any suggestions?
Click to expand...
Click to collapse
I would take a look at the documentation for the Revolution EXE, it could shed some more light on the situation that you're experiencing. Off hand though, I do have some recommendations.
Do you have HTC sync installed? I was reading around and found that this was causing an issue with the revolution program. Try removing that first.
If that's not the case and this still isn't working, there could be a driver conflict with some previously installed android drivers on your system. To clear that up, I would recommend grabbing the latest HTC drivers mentioned in the Revolution documentation. This is the most recent link that I've found: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
The process may require you to manually remove the old drivers and manually install the new ones. If you're not certain of how to do this, it's beyond the help of my guide. I would encourage you to look up the process online or ask a friend to show you.
Hope this helps!
Neogenx said:
Any problems with not being able to send/recieve calls/texts with this? Haven't really messed around too much with the girlfriend's phone b/c she's terrified of not being able to get calls and what not..
I know this is a beta setup for now, so i'm assuming it'll turn into a simple one click type of thing when it gets to that point..?
Edit: I went through all this on my phone and had no problems really except having to call Sprint ..
Click to expand...
Click to collapse
The only related issue that I've come across is the "Error 16" when provisioning the phone after s-off. As you found, this usually fixed with a call to Sprint. I'll never say, "never" though. Be aware that making modifications to the phone always carries with it an inherent risk, however small or unlikely. The risk of course is part of what makes it fun, but girlfriends (mine) seem to seldom understand this.
If the root method is ever released, there is potential for it to become more of a one-click procedure, but I don't think there's a guarantee of course.
Thanks for the guide!
I'm stuck though!
The Revolutionary Command Window says:
"Waiting for fastboot..."
And my phone rebooted into the HBOOT screen but it shows: S-ON
What should I do?
Is this in your guide?
1. Install drivers: http://www.multiupload.com/2OFYWZFCCR
2. Put phone in full boot, usb debugging on , charge only.
3. Uninstall HTC Sync if installed.
4. Profit.
sidepart said:
I would take a look at the documentation for the Revolution EXE, it could shed some more light on the situation that you're experiencing. Off hand though, I do have some recommendations.
Do you have HTC sync installed? I was reading around and found that this was causing an issue with the revolution program. Try removing that first.
If that's not the case and this still isn't working, there could be a driver conflict with some previously installed android drivers on your system. To clear that up, I would recommend grabbing the latest HTC drivers mentioned in the Revolution documentation. This is the most recent link that I've found: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
The process may require you to manually remove the old drivers and manually install the new ones. If you're not certain of how to do this, it's beyond the help of my guide. I would encourage you to look up the process online or ask a friend to show you.
Hope this helps!
Click to expand...
Click to collapse
Updating the driver worked..im good to go now.. thnx..

[Q] DINC Owner Coming To The Dark Side....Kind Of....

Hey everyone I was the proud owner of a DINC and the wife has a DINC2 and now I just purchased a Rezound and well...it's time to yank the guts out of this thing and get it right. It's been a long time since I've gone through the rooting process and on the DINC it was incredibly (see what I did there) straight forward. I'm currently running through a ton of treads trying to make sense of everything and just had a couple quick high level questions.
After rooting do roms keep the beats audio feature?
Will this phone also use the clockworkmod interface?
I'm seeing different responses, some are saying hboot and some saying bootloader, which will give me the closest setup to my DINC?
Thanks so much everyone, looking forward to see what all you guru's are cooking up around here for this phone!
1. I think the sense ROMS keep the beats audio, but there is a flashable mod found here that will add beats to any Rom and make it work with all apps within that rom
2. Clockworkmod is very buggy on the Rezound so you will want to use Amon RA (link is in my signature) which is similar to Clockworkmod but not exactly the same.
3. HBoot and bootloader are the same thing. Battery pull and hold volume down and power to access. Or reboot to bootloader if your rom supports that in the power down menu.
Check out Nil's ICS topic, Lots of good info there, Im sure if you had the Dinc/rooted then you must have tried Nil's Business Sense Rom, His Rezound ICS Rom is even better.
Link to Nil's Rom: http://forum.xda-developers.com/showthread.php?t=1508118
Hitch
1. Keep the phone stock for a week and make sure it is how you like it physically, ie not overheating, and all that jazz
2. Unlock the bootloader or hboot by going to htcdev.com
3. Install amon ra with fastboot commands
4. In amon ra go to developer menu and install the super user thing (not the eng one)
5. S-off by going to unlimited.io
oops i forgot this 5.5 install a modified hboot after you ruu to the latest firmware
6. If you even need help someone has probably had that problem already and had it solved so find that thread!
7. You now can do well pretty much whatever.. flash roms in amon ra, etc do whatever
8. Give me a thanks if i helped
thanks everyone, I'm starting the process now (this is a lot more steps than my DINC was, and seems super complex) and I'm already having issues installing the SDK as it won't see java and setting the environment variable isn't doing crap, I'm gonna stay stock for a bit until I feel like diving deep. I was really hoping it was going to be like the Unrevoked setup where I plug it in and click a button lol
AlmostTactful said:
thanks everyone, I'm starting the process now (this is a lot more steps than my DINC was, and seems super complex) and I'm already having issues installing the SDK as it won't see java and setting the environment variable isn't doing crap, I'm gonna stay stock for a bit until I feel like diving deep. I was really hoping it was going to be like the Unrevoked setup where I plug it in and click a button lol
Click to expand...
Click to collapse
It's honestly not that hard once you get adb up and running... Most of the the root process are laid out step by step and extremely simple... Just follow the steps closely and you'll get it.
Sent from my ADR6425LVW using xda premium
with the issues I'm having in windows would it be easier to do it on my wifes mac?
I have a Mac and it was super easy. All you have to do is install java, install the Mac sdk, and ur good to go. U don't need anything complicated like drivers or any of that crap on the Mac.
You can do it on a Mac, but contrary to modern belief, it is just much simpler on windows.
GrayTheWolf said:
You can do it on a Mac, it is just much simpler on windows.
Click to expand...
Click to collapse
That's far from true. It's much much easier on a mac. I've done it on both trust me.
PROTIP
AlmostTactful said:
thanks everyone, I'm starting the process now (this is a lot more steps than my DINC was, and seems super complex) and I'm already having issues installing the SDK as it won't see java and setting the environment variable isn't doing crap, I'm gonna stay stock for a bit until I feel like diving deep. I was really hoping it was going to be like the Unrevoked setup where I plug it in and click a button lol
Click to expand...
Click to collapse
PROTIP: For you and whoever else is new at this, you don't need to install the whole SDK environment as outlined on the HTC Dev website. If you're not developing code, that is a whole lotta unnecessary downloading and headache.
Get latest drivers as a part of HTC Sync if you don't have them installed.
Hasoon2000's toolkit has all the files you need from the HTC Dev process, no need to install the SDK and Java.
Really all that is needed from the SDK process are drivers and adb and fastboot commands plus their supporting files. Whenever you need adb or fastboot commands you can just open a command prompt directed at the toolkit's Data folder. Bam.
Now get that thing unlocked and get to the fun part, shorting it out with some cabling or a paper clip!
PhantasmRezound said:
PROTIP: For you and whoever else is new at this, you don't need to install the whole SDK environment as outlined on the HTC Dev website. If you're not developing code, that is a whole lotta unnecessary downloading and headache.
Get latest drivers as a part of HTC Sync if you don't have them installed.
Hasoon2000's toolkit has all the files you need from the HTC Dev process, no need to install the SDK and Java.
Really all that is needed from the SDK process are drivers and adb and fastboot commands plus their supporting files. Whenever you need adb or fastboot commands you can just open a command prompt directed at the toolkit's Data folder. Bam.
Now get that thing unlocked and get to the fun part, shorting it out with some cabling or a paper clip!
Click to expand...
Click to collapse
I'm considering making multiple accounts so I can thank you more than once, that is a pot of gold. 5 mins later I'm doing backups in recovery and trying to pick a new rom while that completes.
AshtonTS said:
That's far from true. It's much much easier on a mac. I've done it on both trust me.
Click to expand...
Click to collapse
Oh really?
I thought it was more complicated because there is a whole separate thread on it.
Hey guys let's curb the windows vs mac thing at the end of the day we all know Android is better XD and that's something we can all agree on haha
AlmostTactful said:
Hey guys let's curb the windows vs mac thing at the end of the day we all know Android is better XD and that's something we can all agree on haha
Click to expand...
Click to collapse
We aren't arguing. I just thought it was more complicated on a Mac.
AlmostTactful said:
with the issues I'm having in windows would it be easier to do it on my wifes mac?
Click to expand...
Click to collapse
I was under the impression that this was easier on a PC but regardless you can only run the S-OFF program in PC or Linux. My girlfriend and I only have Macs so I waited until I could use my parent's PC to S-OFF. That was for the best anyway because It gave my a month of other people's trial and error to learn from.
Anyway I would say this is far more complex than my DInc, especially when it feels like half of the community is holding its breath on AOSP. good luck.
GrayTheWolf said:
We aren't arguing. I just thought it was more complicated on a Mac.
Click to expand...
Click to collapse
It's the same just minus the drivers and crap. When I had to set up adb and fastboot on a Pc it took me FOREVER to find the damn drivers. The mac I just had to install java and then the sdk.
The whole separate thread is for people who can't think for themselves

[TOOL]TF201 NVFLash [Updated 21. July]

After much hard work and scary semi-bricks, we are proud to finally provide nvflash to the masses!
This release allows unlocked devices to create a set of device-specific files that lets you access nvflash.
Once the procedure is done, you will always be able to recover any software brick (even bootloader!) as long as you keep your files safe!
NOTE: THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES
More details at http://androidroot.mobi/?p=452
Important note: We kind of forgot to clarify what the license for wheelie was so here goes. Due to the nature of wheelie and the importance of people always using the latest version, Wheelie is NOT redistributable! You are allowed to download it and use it, but you are not allowed to redistribute it in any way - this means no GUI's including it, no reposting zips/tar.gz's and similar! At a later date, we will be releasing our source code and relicense it as GPL.
Update log:
18. July: Added windows version!
21. July: Clarify License
Enjoy
- AndroidRoot.Mobi Team
NOTE: If anyone wishes to donate, http://androidroot.mobi/donations/ is place to do it! DO NOT DONATE DIRECTLY TO ME.
Dude... exactly what I need. You are awesome.
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.
williemeiser said:
I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.
Click to expand...
Click to collapse
Nobody else can provide their blobs to other users, Each device has a different SBK making them incompatible with other devices.
however, you are not "bricked" if you can access fastboot, you have enough access to perform what is required
lilstevie said:
Nobody else can provide their blobs to other users, Each device has a different SBK making them incompatible with other devices.
however, you are not "bricked" if you can access fastboot, you have enough access to perform what is required
Click to expand...
Click to collapse
Is it? Maybe Im just too nervous. but I cant access recovery. Even when i flashed it in fastboot,still i cannot access it. N im running out of ideas,
williemeiser said:
Is it? Maybe Im just too nervous. but I cant access recovery. Even when i flashed it in fastboot,still i cannot access it. N im running out of ideas,
Click to expand...
Click to collapse
you could try fastboot boot recovery.img (where you have a cwm image named recovery.img) and see if that boots, if that doesn't work it is probably a hardware issue.
are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?
demandarin said:
are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?
Click to expand...
Click to collapse
Tbh... If you don't have the ability to follow the simple instructions then you have no business attempting this process at all...
kmdm said:
Tbh... If you don't have the ability to follow the simple instructions then you have no business attempting this process at all...
Click to expand...
Click to collapse
good one.
I knew someone was going to say that..lol. just like rooting methods and other tweaks, a more simpler automated way usually arrives. I have no problem with this but I'm sure alot of others might.
time will tell. I'm sure this will be cooked up into an app/exe.
its all good though
demandarin said:
good one.
I knew someone was going to say that..lol. just like rooting methods and other tweaks, a more simpler automated way usually arrives. I have no problem with this but I'm sure alot of others might.
time will tell. I'm sure this will be cooked up into an app/exe.
its all good though
Click to expand...
Click to collapse
I cannot speak for the others but I personally would not be impressed with this outcome. It is not like other rooting methods and other tweaks, this carries a high brick risk. One-clicks and all those types of installers trivialize the risk that we are trying to make users aware of. Making someone read the instructions gives us the opportunity to really reinforce the risk that you are undertaking.
Is this for real???? iiiiiaaaaaahhhh!!!
Edit: can anyone mirror nvflash t3/ics binary?
lilstevie said:
I cannot speak for the others but I personally would not be impressed with this outcome. It is not like other rooting methods and other tweaks, this carries a high brick risk. One-clicks and all those types of installers trivialize the risk that we are trying to make users aware of. Making someone read the instructions gives us the opportunity to really reinforce the risk that you are undertaking.
Click to expand...
Click to collapse
very well put. you right.
So if we have twrp and a custom rom installed this will still work correct?
Sent from my Transformer Prime TF201 using Tapatalk 2
Great stuff!
I went to download nvflash from Nvidia and was greeted with the message:
"Posted July 12, 2012
NVIDIA suspended operations today of the NVIDIA Developer Zone (developer.nvidia.com). We did this in response to attacks on the site by unauthorized third parties who may have gained access to hashed passwords."
Can anyone send me the nvflash util?
joeyddr said:
So if we have twrp and a custom rom installed this will still work correct?
Sent from my Transformer Prime TF201 using Tapatalk 2
Click to expand...
Click to collapse
yeah, it should still work fine, as long as /data has not been messed up.
lilstevie said:
yeah, it should still work fine, as long as /data has not been messed up.
Click to expand...
Click to collapse
Could you kindly post a mirror link for NVflash? The Nvidia development forums are down due to an investigation of a hacking attack... Or, may be I am searching the wrong place so could you link an active download link from Nvidia site?
litetaker said:
Could you kindly post a mirror link for NVflash? The Nvidia development forums are down due to an investigation of a hacking attack... Or, may be I am searching the wrong place so could you link an active download link from Nvidia site?
Click to expand...
Click to collapse
Anyone with the tegra 3 ICS nvflash? I can't find it anywhere either.
I tried following the instructions on Androidroot.mobi but when I run the following command in windows
fastboot -i 0x0b05 flash bootloader ebtblob.bin
I get bootloader error 0x30003 and I am told that flash was unsuccessful in Command prompt, I am a little confused as to what this means. Additionally is there special setup required for Fastboot? (ive done a quick look around and havent found anything). If anyone can point me to a detailed explanation I would appreciate it, I clearly don't know enough yet to press forward this set up and I'd rather not risk bricking my prime cuz of my ignorance
Thank you in advance
shreddintyres said:
fastboot -i 0x0b05 flash bootloader ebtblob.bin
I get bootloader error 0x30003 and I am told that flash was unsuccessful in Command prompt,
Click to expand...
Click to collapse
What bootloader version do you have at the moment?
kmdm said:
What bootloader version do you have at the moment?
Click to expand...
Click to collapse
I'm not sure, i should have the stock asus bootloader, I am unlocked and have TWRP as recovery.
Presently i am running AOKP milestone 6.1

A journey into the bowels of S-OFF - A guide for the professional semi-noob

I went through the S-OFF, etc process from scratch last weekend (soup to nuts from stock GB), and decided to share my notes.
There is no original information posted here, just a re-organized walkthrough to reference & accommodate what's already out there.
Hopefully a few find it helpful (I know I woulda )
Disclaimer:
this is a Windows-centric walkthrough, that assumes (in parts) that this isn't your first day at the rodeo. Never be scared to use Google or the IRC chat (sorry dsb9938 for the newb flood :laugh
This walkthrough is just an end to a means. You'll find people mention different ways they've accomplish the full process - this post is just a historical document on how I accomplished the same goal.
My methods were definitely successful, though my technique was admittedly ghetto at times. If any uber-pro's notice areas where this is the case, feel free to chime in & i'll update that chunk with credit to you.
I take no responsibility for anything you were inspired to do as a result of reading this post... unless it made you happy, I will take credit for that
The full process in a chronological nutshell:
HTC Unlock
Flash recovery
Root
Juopunutbear S-OFF
Flash latest firmware
Re-flash recovery
Flash ROM
Things to do beforehand:
disable fast boot // settings > power > uncheck
-- this is a universal truth throughout this process, if you have problems booting into the bootloader, check into this.
enable USB debugging - settings > applications > development > check USB debugging
-- this is another universal truth, if something isn't able to communicate with your device, check into this
verify your bootloader / system status
-- power down
-- hold down power & vol- at the same time while booting up
-- it should say Locked & S-ON at the top
backup SD card
backup anything on the internal storage that you care about
*Optional - wipe SD card
*Optional - install an MD5 checker (if you don't already have one)
-- Windows: http://download.cnet.com/MD5-Checker/3000-2092_4-10410639.html?tag=mncol;1
-- Android (for later): https://play.google.com/store/apps/details?id=com.fab.md5
BE PATIENT. seriously. I know you want to get back to MW3, but this can take a while. Your device will go through several lengthy processes. If something looks unresponsive and it starts to scare you, just wait it out for a few minutes before going willy nilly with the power button. At times, you will end up having to manually power on again, but give it time before getting antsy. If your ADD is driving you crazy, just bite your lip and power through it.
Steps 1, 2, & 3)
Unlock, Recovery, & Root:​
go to htc dev
sign up / confirm from email / log in
install the stuff they tell you to, listed on the right of the page
Install / use the Rezound All-In-One Toolkit on your PC to accomplish the rest
for recovery, I chose Amon RA
The more you know ✩....
-- a dude doing recovery the manual way - http://youtu.be/AvSeLmXSjVI
-- the recovery is accessed through the bootloader menu
Step 4)
S-OFF:​
Charge battery full
Make sure fast boot is still off
Make sure USB debugging is enabled
Download the latest juopunutbear for rezound here (Windows, Latest ICS)
*Optional - Verify the MD5
Follow juopunutbear instructions - here, then here
*Optional - Do a backup via recovery
The more you know ✩....
-- controlbear was randomly having a hard time seeing my device, I solved this by:
---- closing controlbear command prompt
---- toggling on HTC Sync as the USB connection type (on the rezound)
---- this caused the device to be recognized differently in windows & installed a driver
---- I started controlbear again, but it hung at "Searching for device"
---- I closed it & ran it again
---- then it worked
-- for the rooting part of this, when it boots you into recovery, check both SD card locations for SuperSU.zip
-- this process froze on me many times, closing and restarting controlbear seemed to fix it
---- seriously did this at least 10 times - it happened randomly at seemingly scary places. (each time getting me further than the last)
-- juopunutbear hboot? - I said yes
-- SD card issues? do a factory reset.
-- Still have SD card issues? you just need to update the firmware, move along.
-- USB debugging path has changed in ICS, you can enable it here: settings > developer options > check USB debugging
-- ATTENTION: Not getting any reception/ signal? put the case back on, broseph
more info:
-- S-off is Official!!! With Instructions...
-- S-OFF FAQ
Step 5)
Latest firmware:​
Download the latest RUU (3.14.605.10 as of July 16) to update the firmware to ICS - http://bit.ly/KlRfKZ
-- *Optional - Verify MD5
Rename the RUU to "PH98IMG.zip"
Copy the renamed update to the root of your external SD Card.
Power down / reboot into bootloader / wait 5-10 minutes for it to finish
Step 6)
Fastboot flash recovery:​
After s-off and firmware update, you need to re-flash recovery via fastboot, this process is described here -- # < anybody have a link? #
-- *Optional - Do a backup via recovery
The more you know ✩....
-- flashing recovery via fastboot is only necessary if you want to keep the top of the bootloader reading as "Locked" (even though it's already S-OFF'd).
-- I did not want this, (mine reads "Unlocked") so if you don't want that, then just re-unlock using the same method as you did the first time, and then re-flash recovery the same way again.
REPEAT: Not getting a reception/ signal? put the case back on.
Step 7)
ROM​
Download ROM of your choice (I used Nils' Business ICS, Sense 4.0, v1.2)
-- *Optional - Verify MD5
Copy the zip to the root of your external SD Card.
Follow the ROM installation instructions (Wipe, etc) & install via recovery
-- *Optional - Do a backup via recovery
Hooray!
-- credit where it's due & thanks to all who came before me.
i came here because the title said BOWELS! 0.o
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Wrote up a similar guide last week at TeamBAMF's site:
http://www.teambamf.net/topic/4122-generic-guide-to-root-and-install-roms-on-the-rezound/
AshtonTS said:
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Click to expand...
Click to collapse
ha, might have been the reason controlbear failed so many times (still ended up working though).
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
dustintheweb said:
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
Click to expand...
Click to collapse
Yeah makes sense.
dustintheweb said:
ha, might have been the reason controlbear failed so many times (still ended up working though).
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
Click to expand...
Click to collapse
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Divine_Madcat said:
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Click to expand...
Click to collapse
Just to add on to that, a noob who can't use adb and fastboot fully probably has no need for s-off
So no fast boot Ehhh?
I just checked, mine is on, so is that why my 8 hours of s-off attempts failed?
Sent from my ADR6425LVW using Tapatalk 2
Divine_Madcat said:
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Click to expand...
Click to collapse
meh, maybe i've just had good luck, but I've personally found over the years (and reiterated from others) that HTC phones are fairly hard to brick. I mean, yeah, people should read up on stuff and not be idiots when going down this road, but there's no reason to treat it as delicate of a process as some do.
I like to think of it more as training a dog, rather than walking on egg shells. Take your time, be patient, but don't forget to make it fun.
-- and if at any point you're unsure on how to do something, don't panic - just post your question in the forums or in the chat and be prepared to wait. Someone will help you eventually.
AshtonTS said:
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Click to expand...
Click to collapse
First, this is exactly what I was looking for so thank you. I've read just about every post for unlocking and s-off, but I'm glad you put it all together!
Second, so step #5 should really be #4?
Third, flame me if you want, but I don't have the developer tools menu to enable USB debugging. Does that show after using unlocking via HTC dev?
Thanks again!
dustintheweb said:
meh, maybe i've just had good luck, but I've personally found over the years (and reiterated from others) that HTC phones are fairly hard to brick. I mean, yeah, people should read up on stuff and not be idiots when going down this road, but there's no reason to treat it as delicate of a process as some do.
I like to think of it more as training a dog, rather than walking on egg shells. Take your time, be patient, but don't forget to make it fun.
-- and if at any point you're unsure on how to do something, don't panic - just post your question in the forums or in the chat and be prepared to wait. Someone will help you eventually.
Click to expand...
Click to collapse
This is how it should be but not all people think like that most just wanna put people on blast
Sent from my ADR6400L using xda app-developers app
BSquaredB2 said:
Second, so step #5 should really be #4?
Click to expand...
Click to collapse
It worked for me, but AshtonTS says there is a better way. Search through the S-OFF FAQ thread (or similar) and see if you can get a consensus of what other people did.
BSquaredB2 said:
Third, flame me if you want, but I don't have the developer tools menu to enable USB debugging. Does that show after using unlocking via HTC dev?
Click to expand...
Click to collapse
If you're on GB, go to settings > applications > development > check USB debugging
Sorry about that, I had the ICS path in the guide (now fixed).

Help Needed

guys, i'm new to the amaze, last night i managed to unlock the bootloader, rooted and even installed 4ext recovery, the issue is that i am on an unbranded amaze with that old GB stock (hate it), i can't find the control bear to get it s-off'ed, anyone has the link for the windows file? i saw the tutorial on youtube, couldn't find the exe to it...
is it safe to do that wire trick? can someone send me the exe file or pm me? i would be very greatful, thanks
jafferkhan said:
guys, i'm new to the amaze, last night i managed to unlock the bootloader, rooted and even installed 4ext recovery, the issue is that i am on an unbranded amaze with that old GB stock (hate it), i can't find the control bear to get it s-off'ed, anyone has the link for the windows file? i saw the tutorial on youtube, couldn't find the exe to it...
is it safe to do that wire trick? can someone send me the exe file or pm me? i would be very greatful, thanks
Click to expand...
Click to collapse
Unlimited.io no longer supports the Windows version.
I wonder however if any info here will help you:
http://forum.xda-developers.com/showthread.php?t=2437057
http://www.youtube.com/watch?v=PELMvlA-lWw
A reminder to be very careful. I make no warranties express or implied, but will admit total success after completing all the pre-requisites and then following the proper procedure through linux. Granted, my timing was off, and it took a great many more than several tries, however on the plus side, I get points for perseverence, and it was truly exciting thinking I could have destroyed my phone at any moment, and somehow, did not. FWIW, I used an older than recommended version of linux (don't remember which) than that specified, but can't recommend anyone else do that.
Good luck.
pbergonzi said:
Unlimited.io no longer supports the Windows version.
I wonder however if any info here will help you:
http://forum.xda-developers.com/showthread.php?t=2437057
http://www.youtube.com/watch?v=PELMvlA-lWw
A reminder to be very careful. I make no warranties express or implied, but will admit total success after completing all the pre-requisites and then following the proper procedure through linux. Granted, my timing was off, and it took a great many more than several tries, however on the plus side, I get points for perseverence, and it was truly exciting thinking I could have destroyed my phone at any moment, and somehow, did not. FWIW, I used an older than recommended version of linux (don't remember which) than that specified, but can't recommend anyone else do that.
Good luck.
Click to expand...
Click to collapse
it doesn't help, it redirects towards the unlimited.io website,still without the windows installer
I see links below the video that download files from 4shared. One for GB, one for ICS.
jafferkhan said:
it doesn't help, it redirects towards the unlimited.io website,still without the windows installer
Click to expand...
Click to collapse
Why you guys take risks of doing those risky things with windows...
So many guys bricked their phones...
And few have working also but who knows..
And Linux is not that hard according to me..
Just get started then... Even you don't Know.then we are here to help you out..
Read the precautions and all...and you will be fine with wire trick also
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
shubham211995 said:
Why you guys take risks of doing those risky things with windows...
Click to expand...
Click to collapse
Good point, shubham211995.
There is a clear notice in the pre-requsites on the unlimited.io website to use Ubuntu 12.04 and newer 32-bit, and that even if one has Windows installed, one can use the LiveCD:
"1. Supported Operating Systems:
We only support Ubuntu 12.04 (and newer) 32bit, you may use a LiveCD if you have the wrong OS installed natively. LiveUSB will NOT work!
Ubuntu 64bit, Ubuntu versions lower than 12.04, other Linux distros, Virtual Machines and Mac's will NOT work - we will not help you if you break your device!"
live cd
you can download a live cd and run it on vm ware if do not want linux on your computer.
If you're still stuck @ravike14 can help you out!
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app

Categories

Resources