Develop Bugs

[GUIDE][ROOT][Mac][Linux]Epic 4G Touch Root on Mac or Linux using Heimdall!

Video tutorial:
For those of you who want to root your Epic 4G Touch on a Mac or Linux, you can using this open-source tool called Heimdall.
Here's how to root your Epic 4G Touch on Mac or Linux.
Step 1. Put your Epic 4G Touch in Download Mode by holding down Volume Down button and Power button together for about 10 seconds then hit Volume Up button. Connect your phone to your computer via a USB cable.
Step 2. Go download the appropriate binaries for your Mac (OSX) or Linux 32-bit or 64bit at glassechidna.com.au
Get the file with "Binary" or "Binaries".
For Mac, you will get a .DMG file you can install and for Linux, you will get a .deb file you can install.
Install these files and open up a command prompt and type:
heimdall
You should get a bunch of syntax stuff, if so that's good, you have heimdall installed and working.
Step 3. Go download a rooted kernel, I recommend Zedomax Epic Touch Kernel v3:
Download Zedomax Epic Touch Kernel v3
*Note - You can also download any other kernel .tar file of your liking.
Step 4. Browse to the directory you've download the tar file by using command "cd":
cd /home/myusername/Downloads
Step 5. Untar the tar file:
tar xvf SPH-D710_Zedomax_EpicTouchKernel-v3.tar
Step 5. Double-check you have a zImage file in the directory by typing:
ls -l
Step 7. Type the following to flash:
heimdall flash --kernel zImage
Step 8. Reboot and you can check that you've rooted your phone by going to Settings->About phone and see "ZedomaxEpicTouchKernel" in Kernel version.
Also you will see a new app called "Superuser" in apps.
Congrats, you've been rooted with a Linux or Mac.
*****Want to thank me?*****
Subscribe to my email list at Epic 4g Touch Root, subscribe to my YouTube channel and sign up for membership at ACSyndicate.net.
*****Contact*****
Want to contact me?
Add me on GooglePlus:
https://plus.google.com/105122758270056069711
Add me on Facebook:
http://facebook.com/howtoblog
And me on twitter:
http://twitter.com/zedomax

reserved
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
reserved for funny cat LOL photos.

Reserved for sammichez
Sent from my SPH-D710 using xda premium

Did this yesterday on MacBook Pro, 64-bit. Works as advertised, pretty simple. One quick tip, don't need to unpack the tar in heimdall; a double-click will do the trick... just gotta remember where you put it (and make sure you're in the right directory).

silversx80 said:
Did this yesterday on MacBook Pro, 64-bit. Works as advertised, pretty simple. One quick tip, don't need to unpack the tar in heimdall; a double-click will do the trick... just gotta remember where you put it (and make sure you're in the right directory).
Click to expand...
Click to collapse
nice, thx for the cool tip bud.

just got my phone yesterday, and, was hoping that soon there would be a solution for us mac users..this looks great!
just a quick question; anyone who has used this, does it bork anything like wifi or bluetooth?
thanks again!

All I did was flash zedo's v3 kernel and everything still works. I'm actually getting better battery life, faster 3G and can now bench 450 lbs.
Nobody can make any guarantees, though... you know how it goes.

wow, benching 450 after flashing a rom is most impressive!
I'm having some issues with BT now, and its important for me for it to work; thats the only reason I asked..
This seems like the easiest root method I have seen for any Android phone, especially for a mac!
thanks

silversx80 said:
All I did was flash zedo's v3 kernel and everything still works. I'm actually getting better battery life, faster 3G and can now bench 450 lbs.
Nobody can make any guarantees, though... you know how it goes.
Click to expand...
Click to collapse
450 is really good, did rooting get you that energy?

LOL!
BTW, can you use any other recovery on this phone, or just Clockwork?
thanks!

So, heimdall is basically just an open-source implementation of tarball flashing with Odin? Very cool!
Also, would you mind listing MD5 or SHA1 checksum values for the kernels/etc that you post? Wouldn't want to flash anything corrupt...
EDIT: Nevermind, I went to actually download the file and the MD5 is right there! Thanks.
Thanks for all your work!

silversx80 said:
Did this yesterday on MacBook Pro, 64-bit. Works as advertised, pretty simple. One quick tip, don't need to unpack the tar in heimdall; a double-click will do the trick... just gotta remember where you put it (and make sure you're in the right directory).
Click to expand...
Click to collapse
Odd... Heimdall Frontend never liked Odin tars when I tried it. I admit I didn't put too much effort into it - I'm a commandline kind of guy.
On Linux boxes the frontend and commandline utility are installed separately - these instructions work if you only have the CL utility but not the frontend.
xak944 said:
So, heimdall is basically just an open-source implementation of tarball flashing with Odin? Very cool!
Also, would you mind listing MD5 or SHA1 checksum values for the kernels/etc that you post? Wouldn't want to flash anything corrupt...
EDIT: Nevermind, I went to actually download the file and the MD5 is right there! Thanks.
Thanks for all your work!
Click to expand...
Click to collapse
Yup. Heimdall is a lifesaver for kernel developers... Some people actually add the following to their kernel build scripts to autoflash.
Code:
adb reboot download
heimdall flash --kernel arch/arm/boot/zImage
Too bad you guys don't get SGS kernel flasher.
FYI a piece of advice from the Infuse community to the developers here - I strongly suggest having Odin-flashable dumps of a stock system and cache filesystem image made available. Having gtg465x's Ultimate Unbrick has been a lifesaver for the Infuse community - http://forum.xda-developers.com/showthread.php?t=1112555
You'll probably see less of me around here as time goes by - I originally stopped by because a rant on an Engadget thread made me curious, and it is really interesting to watch the first few weeks of development bringup for a device. I still remember the excitement when Rogers released the Infuse with Gingerbread... We had an army of AT&T users ready to walk the Rogers owners through anything needed to get good device dumps.

zedomax said:
450 is really good, did rooting get you that energy?
Click to expand...
Click to collapse
Oh yeah. Rooting makes me want to snap into a Slim Jim... in a good way.
Just flashed the stock kernel with Heimdall, still have root, no CWM (running some tests).

silversx80 said:
Oh yeah. Rooting makes me want to snap into a Slim Jim... in a good way.
Just flashed the stock kernel with Heimdall, still have root, no CWM (running some tests).
Click to expand...
Click to collapse
Nice, i feel the same way when i can get a new kernel working/compiling. But no, i cannot bench that much (yet), working on it.

Entropy512 said:
Odd... Heimdall Frontend never liked Odin tars when I tried it. I admit I didn't put too much effort into it - I'm a commandline kind of guy.
On Linux boxes the frontend and commandline utility are installed separately - these instructions work if you only have the CL utility but not the frontend.
Yup. Heimdall is a lifesaver for kernel developers... Some people actually add the following to their kernel build scripts to autoflash.
Code:
adb reboot download
heimdall flash --kernel arch/arm/boot/zImage
Too bad you guys don't get SGS kernel flasher.
FYI a piece of advice from the Infuse community to the developers here - I strongly suggest having Odin-flashable dumps of a stock system and cache filesystem image made available. Having gtg465x's Ultimate Unbrick has been a lifesaver for the Infuse community - http://forum.xda-developers.com/showthread.php?t=1112555
You'll probably see less of me around here as time goes by - I originally stopped by because a rant on an Engadget thread made me curious, and it is really interesting to watch the first few weeks of development bringup for a device. I still remember the excitement when Rogers released the Infuse with Gingerbread... We had an army of AT&T users ready to walk the Rogers owners through anything needed to get good device dumps.
Click to expand...
Click to collapse
odin is great but only works for windooows. good thing we have heimdall for linux and mac users.

having some trouble i installed heimdall on my mac and when i stype heimdall in terminal eliminator i get some errors thing
dyld: Library not loaded: /usr/local/lib/libusb-1.0.0.dylib
Referenced from: /usr/bin/heimdall
Reason: no suitable image found. Did find:
/usr/local/lib/libusb-1.0.0.dylib: stat() failed with errno=13
/usr/local/lib/libusb-1.0.0.dylib: stat() failed with errno=13
Trace/BPT trap: 5
is this right?

interhawk1 said:
having some trouble i installed heimdall on my mac and when i stype heimdall in terminal eliminator i get some errors thing
dyld: Library not loaded: /usr/local/lib/libusb-1.0.0.dylib
Referenced from: /usr/bin/heimdall
Reason: no suitable image found. Did find:
/usr/local/lib/libusb-1.0.0.dylib: stat() failed with errno=13
/usr/local/lib/libusb-1.0.0.dylib: stat() failed with errno=13
Trace/BPT trap: 5
is this right?
Click to expand...
Click to collapse
Install the Heimdall binaries not the front-end, binaries work great, i never got the front-end to work correctly.

zedomax said:
Install the Heimdall binaries not the front-end, binaries work great, i never got the front-end to work correctly.
Click to expand...
Click to collapse
I'm using a mac i don't see that option for 1.30 should i install 1.2.0?

interhawk1 said:
I'm using a mac i don't see that option for 1.30 should i install 1.2.0?
Click to expand...
Click to collapse
I installed 1.2.0 before 1.3.0, so I'm not sure if 1.3 installs the binaries.
Put your E4GT into download mode and plug it in. Run terminal and type "heimdall detect" (or it may be "heimdall --detect"). I don't think you need to be in any particular directory to detect a device. If it detects it, then the binaries are installed and you can flash a monkey to your device if you have the proper setup.

interhawk1 said:
I'm using a mac i don't see that option for 1.30 should i install 1.2.0?
Click to expand...
Click to collapse
Yes, 1.2.0 is fine.

Root your device EASILY! [CASUAL] [Linux] [Windows] [Mac]

Ok guys, I've been putting work into CASUAL for Windows and Linux. Mac is still experimental. Here's how this works: I'm comitted to providing an easy way to root your device and you provide me with feedback, positive or negative. All I'm asking for is if it worked or where it failed and what type of computer you're using.
Introduction
This root method should be about the easiest one ever created. You launch the java JAR file and click "Do It". CASUAL will take care of installing drivers, runtimes, providing clear and easy-to-understand instructions. I want this to be easy and if there's something that can be improved, let me know.
Instructions
Click here and make sure Java is up-to-date (not JavaScript that you hear about all the security vulnerabilities, Java).
Download and launch CASUAL
Plug in your device
click "Do It!"
note: if it asks you to install drivers, you want to do MSM8960.
Download
Download Root AT&T GS3 - CASUAL Revision 515b
http://goo.im/devs/AdamOutler/GS3-Root-ATT-Can
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Conclusion
Again, this is a test of CASUAL. I want to improve it. I would like your help in getting feedback to improve the Cross-platform ADB Scripting Unified Android Loader platform. I need to confirm that this works on all operating systems.
Test list:
Crossed off means it was tested.
High Priority OS's
Windows 7 -32 bit
Windows 7 - 64 bit
Windows 8
OSX Lion
OSX Mountain Lion
Debian based Linux 64
Debian based Linux 32
Raspberry Pi running Debian based distributions
Low Priority OS's
Windows XP 32
Windows XP 64
OSX Tiger
OSX Leopard
OSX Snow Leopard
Releases
CASUAL R302b - Initial release
CASUAL R306b - fixed freezing on Linux64, needs retesting on Windows and Mac.
CASUAL R308b - fixed freezing on Windows by reorganizing data collection. This may be an error on Windows Java where reading Error Stream too quickly causes a crash.
If you find a problem, or even find a solution, please let me know. I am subuscribed to this thread.

Very Nice my friend will have to try this if my wife lets me root her Galaxy AT&T:good:, Do have a question does this trip your counter like Odin one Does, Also i see you got Windows 7 64 bit cross off i only use 64 bit on Windows 7 will this work on 64 bit?

Venom0642 said:
Very Nice my friend will have to try this if my wife lets me root her Galaxy AT&T:good:, Do have a question does this trip your counter like Odin one Does, Also i see you got Windows 7 64 bit cross off i only use 64 bit on Windows 7 will this work on 64 bit?
Click to expand...
Click to collapse
Yes. It will trip the flash counter. This is part of the Loke daemon on the device and I cannot change that. You can use Triangle Away to remove the counter.
I'm crossing off operating systems which have been tested. As feedback comes in, they will be crossed off or have a note put by them until the next release.

AdamOutler said:
Yes. It will trip the flash counter. This is part of the Loke daemon on the device and I cannot change that. You can use Triangle Away to remove the counter.
I'm crossing off operating systems which have been tested. As feedback comes in, they will be crossed off or have a note put by them until the next release.
Click to expand...
Click to collapse
Ok well that's great News that it will work with Windows 7 64 bit Thanks!:good:

Re: Root your device EASILY! [CASUAL] [Experimental]
Thank you very much for all your work Adam. This is awesome.
Sent from my SAMSUNG-SGH-I747 using xda premium

Any plans to incorporate flashing a custom recovery at some point?
Sort of a one-click tool to take from stock to ready to flash a ROM?

I'll reflash stock, and give this a few run throughs on Win7 x64,
let you know if I have any issues.

Re: Root your device EASILY! [CASUAL] [Experimental]
Used this on win 7 32. Worked perfectly no problem. Thanks a lot. Helped me in a huge way.
Sent from my SGH-I747 using xda premium

Re: Root your device EASILY! [CASUAL] [Experimental]
Thanks Adam!
Sent from my SCH-I605 using xda app-developers app

shoupness said:
Used this on win 7 32. Worked perfectly no problem. Thanks a lot. Helped me in a huge way.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks! Crossed off the list!
I should also mention that you don't need to be stock. You can be rooted. The test is complete when you see Chainfire's CFAutoRoot.

new version available. Verified on Linux64. Should be working on Windows but needs testing. Mac needs testing.
Again, you need not be stock to verify everything works.

Windows 8 32bit is a no go. It hangs at checking device. I let it sit for about 10 minutes.
And as for windows 7 32bit also hangs on checking device but also tells me my device isn't paired right? It tells me to wait for onscreen instructions on my device that say to allow this computer and it doesn't ever pop up.

Tyler.Boston1 said:
Windows 8 32bit is a no go. It hangs at checking device. I let it sit for about 10 minutes.
And as for windows 7 32bit also hangs on checking device but also tells me my device isn't paired right? It tells me to wait for onscreen instructions on my device that say to allow this computer and it doesn't ever pop up.
Click to expand...
Click to collapse
Will you post your log (About -> Show Log) to pastebin and link it here

Ok, the freezing issue should be fixed.
I belive i have found an error in the Java language which I've isolated to Windows only. It appears to be an actual Java error. If you start a process, open a buffered reader to the process' STDERR and STDOUT, then immediately attempt to readLine from STDERR from a process which does not have a STDERR stream, it will halt the application and never finish the operation. I worked around this issue by reading STDERR after reading STDOUT. Line 131 addresses this issue https://code.google.com/p/android-c...ide&path=/trunk/GUI/src/CASUAL/Shell.java#131

@Mod's
IMO this thread should become a sticky so it doesn't get pushed back. Hope I'm not out of line.

This is a much needed tool for me......thanks! Quick question...whenever I install any utiluty/tool related to Heimdall, my computer stops recognizing my device, and I have to reinstall samsung drivers. Am I missing something? I using windows btw.

Chuckd610 said:
This is a much needed tool for me......thanks! Quick question...whenever I install any utiluty/tool related to Heimdall, my computer stops recognizing my device, and I have to reinstall samsung drivers. Am I missing something? I using windows btw.
Click to expand...
Click to collapse
Heimdall requires a generic driver, (WinUSB / libusb0 / libusbK), normally installed by Zadig.exe when your phone is in Download mode.
This shouldn't affect your device in normal (Android) mode, only in Download mode. If your having to reinstall drivers in normal mode you're doing it wrong, you installed the driver while your phone is in normal mode.
Because your phone has a different PID when its in Download from when its in normal mode (the driver from download mode can't be loaded in normal mode), thats the only reason I can think of why that would have happened.
Using USBDeview, (with your phone unplugged) remove all "Samsung" Drivers then next when you plug in your phone Windows will install the correct driver from the inf store.

Confirmed working on Windows 7 64bit....just used this to root my girlfriends GS3... thanks a bunch!

Hey man I can do some testing for OS X , specifically 10.8.2 . just send me a PM or something if you'd like some feedback or whatever
Sent from my SGH-I747 using Tapatalk 2

I have Mac and would like to participate and help in testing but I have a GS3 for T mobile will it work on my phone?

[GUIDE] Modifying 4.4.x based rom's updater-script to install in TWRP 2.5.0.0

MODIFY A 4.4.x BASED ROM'S UPDATER-SCRIPT TO FLASH WITH TWRP 2.5.0.0!
WARNING
This is a disclaimer: While this has been tested I am not responsible for ANY damage done to your device. I take no responsibility for bootloops, soft bricks, hard bricks, living brick monsters, your phone proving an omnipotent being fallible(thus negating all existence), your great aunt smoking bath salts, flying monkeys, hot pockets, obamacare, dingleberries, carnivorous dingleberries or Sundays. Use at your own risk!!
Secondary disclaimer: If you have carnivorous dingleberries then you have bigger problems to worry about - but for any phone related questions feel free to message me on here either privately or in the thread.
In honor of my 300th post here on xda I thought I should do my first guide. I decided to make this guide because some people have had issues with TWRP 2.6.x which is the version you need to flash kit kat roms. However TWRP 2.5.0.0 has been beyond stable for me and everyone I know who has used it on our wonderful ls970. So how do you flash 4.4 based roms from TWRP 2.5.0.0?! Edit the updater-script, ofcourse!!!!
Now keep in mind, the screenshots I supply will be on Linux because it is what I use - the steps should be the same for Windows, however the programs used will probably be different(Archive Manager vs 7zip/WinRar for instance). If anyone wants to do this on Windows and take screenshots I will gladly post them or give OP privileges so that you can add them yourself.
Are there any downsides to installing roms this way?
Yes - it will essentially break OTA updates for the roms. 4.4 roms built from source will always have an updater-script meant for the newer recovery versions and will not flash in 2.5.0.0. So if you want to dirty flash an update to the rom you are using, you will have to modify that updater-script as well.
Well, let's get down to business!
Things you will need:
A flashable zip file for your rom of choice(I use Vanir for this guide)
An archive manager(7zip/Winrar for Windows)
A text editor(I use gedit but Windows users will want to use Notepad++)
A working brain
Step 1: Open the flashable zip file with an archive manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2: Navigate to the updater-script found in META-INF/com/google/android/
Step 3: Open the updater-script from within the archive manager. Keep the archive manager open during this process. I'm using Linux Mint 15 so it opens in gedit. Once open, scroll down until you see a bunch of lines that say 'set_metadata' and 'set_metadata_recursive'. These are the lines we need to edit.
Step 4: Now everywhere you see 'metadata' in these lines, you want to replace 'metadata' with 'perm' like in the images below.
Step 5: After replacing metadata with perm, we need to re-organize things a bit to look more like a 4.3 updater-script. After the parentheses you will see directories/files in quotation marks like in the picture below.
We need to move all of these to the end of the parentheses like so.
Step 6: The next thing we need to do is delete everything else in the parentheses EXCEPT the numbers. The numbers and quotations we just moved will be the only things left in parentheses when we are done. Also keep in mind that '0x0' will also be removed.
So - everything highlighted below, needs to go!
When you are done, it will look like this:
And when you are done with ALL of it, here is what it will look like!
Step 7: Remove asserts. This isn't always needed but it also won't hurt. The asserts placed in flashable zips are to protect you from installing a rom that isn't compatible with your device. The problem we lgog users frequently have is that our phone is called many things(ls970, geehrc4g, geespr, etc). If you've ever gotten a "Flash failed this isn't a geespr" error in TWRP, it's because that particular version of TWRP doesn't recognize your device as a geespr(even though it is). So as long as you know the rom was built for your device, it is safe to delete these lines. They are found at the very top of the updater-script like shown below.
Step 8: Save and update! Once you are done editing, simply hit save in the text editor and your archive manager should give you a warning similar to this one below.
Hit the update button and the updater-script will save inside the flashable zip!
And that's it! Your 4.4 based rom will now flash on TWRP 2.5.0.0!!
Just be careful that you edit it exactly, pay attention to the punctuation. This is not difficult but can be time consuming. Using your text editor's "Replace" function properly will help speed up the process!
So why go through all of this?
Certain users here on the lgog forums have experienced a problem with TWRP 2.6.x that essentially bricks the device. Randomly and mysteriously, the phone won't boot into the system. When trying to boot into TWRP, it will ask for a password - even though the user never supplied one in the first place. If you cancel the password, TWRP loses all functionality.
Users in other threads(specifically the nexus4 and nexus5 users) have experienced the same problem but not to the extent our lgog users have. In most cases it is because the data partition became corrupt/encrypted. The solution is to format your data partition(So best case scenario, you lose EVERYTHING). Nexus users seem to still be able to do this after cancelling the password - some lgog users haven't been as fortunate. When they cancel the password, nothing mounts, so nothing works. Even using LGNPST to revert back to stock gives an error so the phone is essentially a paperweight.
What is the cause of this?
It still isn't certain however it may be a bad emmc chip. Can't an emmc chip go bad using TWRP 2.5.0.0? Ofcourse, so this may all be superstition. It may just be a coincidence that a person's emmc chip fried while using the updated versions of TWRP. But until someone has this issue on TWRP 2.5.0.0(None have been reported as far as I know, if it happens to you, please prove me wrong), I'm going to err on the side of caution and stick with what I know works.
For most users it will just be easier to flash a different recovery like Clockworkmod but I personally wanted to stick with one recovery. Using this method, TWRP 2.5.0.0 can flash everything from stock to 4.4.x! You can look here in the lgog forums for working recoveries and their uses/limitations. But at the very least I hope this guide helped you to understand updater-scripts a bit better and the role they play in flashing roms.​
QUESTIONS?
Feel free to ask me any questions you may have. If it doesn't flash, get a recovery log(from TWRP go to advanced->copy log to sd, then boot back into your system and it will be on your internal memory as recovery.log) and send it to me. Or open the recovery log yourself and look for E: (For error) around where the flash failed. Usually you will see a syntax error and it will tell you what line it was on - that means the edit wasn't done properly but you will atleast know where it went wrong.
Thanks
@xboxfanj - for showing me how to do this in the first place
@engine95 - for all of his guides here in the threads

For Windows, use 7zip and notepad++. They work good.
Nice guide for those of us that prefer TWRP. Thanks.
Edit. That info was in the spoiler. My bad.
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
For Windows, use 7zip and notepad++. They work good.
Nice guide for those of us that prefer TWRP. Thanks.
Edit. That info was in the spoiler. My bad.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man(out of daily thanks again) - I thought that's what Windows users should use but wasn't 100% sure.

Awesome work brother!
Sent from my Optimus G using xda app-developers app

PartimusPrime said:
Awesome work brother!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Ditto on that!

PartimusPrime said:
Awesome work brother!
Sent from my Optimus G using xda app-developers app
Click to expand...
Click to collapse
Code-Craft said:
Ditto on that!
Click to expand...
Click to collapse
Thanks guys! My laptop is so old I cant even attempt to build anything worthwhile(damn you 32 bit!) so I can only modify stuff but will pass on what I learn to you all. As soon as I get a new computer I will be learning how to build so stay tuned.

Good job man!! Hell yeah!
Sent from my LG-LS970 using XDA Premium 4 mobile app

[TOOL] HTC 10 (M10) All-In-One Toolkit V1.0.2 [3-5-2017]

Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
PLEASE READ THE PARAGRAPH BELOW THIS LINE​
It's been a few years since I made a toolkit. Since my last toolkit that I released, which was the M8, I had surgery done, graduated college and went through a ton in life. I haven't been in the Android scene in years. As much as I would have loved to, life has been hectic. I announced that I was going to release a toolkit for the HTC 10. It's been a few months since that announcement but here it is. I'm pretty sure there is quite a few kinks and bugs I'll need to fix, but I spent a lot of time on it and my eyes are tired at looking at all my code. Trying to remember how to code/script was hard enough as is, but it's definitely worth it for you guys. So to announce my software, I would like to present my toolkit for the HTC 10!
If this helped you out, Please press the thanks button and if you want, you can always donate!
FEATURES​
- Install HTC Drivers
- Enter Bootloader
- Get Token ID. Register at HTCDev, login to the site and submit the Token ID.
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Various useful commands
- Install Recoveries
User Provided Recoveries
TWRP
Kernels
User provided kernels
- Link to this thread
- Link to PM me if you need a phone unlocked
- Link to the One Development thread
- Boot Into Recovery/Bootloader/Phone
- Flash kernel/recovery/RUU zip
- Relock Bootloader (must be in fastboot)
- APK Batch Installer (Credits to hamsteyr)
- Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this!
Here is a screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Devs for making us ROMS!
- The community for being awesome!
- HTC for making us the phone so we can be a community!
- To everyone else I may have forgotten!
*DISCLAIMER*​
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
Donations​

Downloads
https://www.androidfilehost.com/?w=files&flid=158224
Changes
V1.0 Released! 1-14-2017
- Initial Release
v1.0.1 released! 3-1-2017
- Updated to unofficial TWRP 3.0.3.3 (thanks to 2WildFirE for providing the link and to Captain_Throwback for creating it!)
- Updated link to AndroidFileHost
v1.0.2 released! 3-5-2017
- Updated to unofficial TWRP 3.0.3.10

Bugs
- Directory has to have one word.
Ex:
Will Work. This will solve any issues if the buttons don't work when you press them.
C:\Users\John\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
C:\Users\John_Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
Will NOT work. Your directory will look something like this and buttons won't work when you press it.
C:\Users\John Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Click to expand...
Click to collapse
Looking to add in the future
- More recoveries
- Makes Requests!!!
FAQs
Q - Why Did you make this?
A - To make life easier
Q - You are limited on features. Why?
A- You can always make a request!
Q - Will this work on other devices?
A - Only the fastboot commands, HTC Dev unlock (device specific) and the HTC drivers. Toolkit is made for the specific device.
Q - My Anti-Virus says your program is a virus. Is it a really a virus?
A - No. It's a false-positive! My reputation on here shows otherwise. Here's some more info if you are skeptical.
https://www.autoitscript.com/wiki/AutoIt_and_Malware
Q - Will you support more devices in the future?
A - If people REALLY want, I can make it happen. I just don't want to make anything that nobody would use.
Q - Awesome! Can I make a donation?
A - Of course! Do not feel obligated though. If you would like to make a donation, you can click the button on my toolkit or under my username.

Any feedback is always nice!
Sent from my HTC 10 using Tapatalk

My phone has unlocked bootloader, still S-ON, used the tool kit to flash TWRP.
Everything run successfully but the phone can not enter Recovery to run backup. It just restart the phone normally.
I have tried many TWRP version, but still can not enter the Recovery.
HTC 10 - US Unlocked Version.
2.38.617.6

@clv2k @hasoon2000
Use unofficial version 3.0.3.0 twrp
Read post #2
https://forum.xda-developers.com/showthread.php?p=66347165
HTC_10 & Tapatalk

clv2k said:
My phone has unlocked bootloader, still S-ON, used the tool kit to flash TWRP.
Everything run successfully but the phone can not enter Recovery to run backup. It just restart the phone normally.
I have tried many TWRP version, but still can not enter the Recovery.
HTC 10 - US Unlocked Version.
2.38.617.6
Click to expand...
Click to collapse
Were you trying to reboot into recovery through the toolkit? If so, I'll test the command when I'm back home and look at the script. Have you tried doing so manually?
Sent from my HTC 10 using Tapatalk

awesome!

hasoon2000 said:
Were you trying to reboot into recovery through the toolkit? If so, I'll test the command when I'm back home and look at the script. Have you tried doing so manually?
Click to expand...
Click to collapse
I tried to flash TWRP manually by adb command and reboot to recovery but my phone still not enter it. What's wrong with the phone
Edit: Thanks Linar10, I replace TWRP 3.03.0 to the toolkit it run successful.
Thanks Hasoon2000 for the toolkit

I used the toolkit for my wife's 10. I did everything from zero to check if everything was OK and boy, it went smooth. Thanks a lot for the toolkit and for sharing it. It rocks.

https://forum.xda-developers.com/devdb/project/dl/?id=22854 latest twrp
Powered by the 10

I figured by now most people would realize how dangerous toolkits are, and would have stopped using them.
It's much safer to not use a toolkit, and you learn a lot more by learning, and performing the commands yourself.
Why would you have an S-ON command so close to a GETVAR command? Just something someone will accidentally click.
I've see many people come to IRC asking for help, saying "I didn't do anything to set my S-ON, all I did was use a toolkit."

The laptop is full of viruses and I have to take format
HTC 10 cihazımdan gönderildi

Zanzibar said:
I figured by now most people would realize how dangerous toolkits are, and would have stopped using them.
It's much safer to not use a toolkit, and you learn a lot more by learning, and performing the commands yourself.
Why would you have an S-ON command so close to a GETVAR command? Just something someone will accidentally click.
I've see many people come to IRC asking for help, saying "I didn't do anything to set my S-ON, all I did was use a toolkit."
Click to expand...
Click to collapse
I agree in part.
Yes, you learn a lot more by studying and asking how to type the commands yourself, but I see this toolkit (hasoon's is the only one I've used) as a way to begin with all this. I mean, you have to start somewhere and this is a valid way of doing it. You click some buttons, follow the instructions and if you are careful you can be sure you won't mess anything up.
That's how I started learning until I was able to do things myself. I don't have s-off because I don't know enough to be 100% sure I won't kill my phone, so I prefer doing some things (flashing kernels) from fastboot instead of recovery and not experimenting with different radios and such.
In short, you have some very valid points, but people has to start somewhere and this one is too a good way of doing so.

the file is a .exe not a .rar?????? One-10_All-In-One_Kit_v1.0.rar.exe

hasoon2000 said:
Downloads
http://d-h.st/users/hasoon2000/?fld_id=2808#files
Changes
V1.0 Released! 1-14-2017
- Initial Release
Click to expand...
Click to collapse
Hi, I cannot download the tool, is the link down?

seawind107 said:
Hi, I cannot download the tool, is the link down?
Click to expand...
Click to collapse
Works just fine for me, bud

File ok?
Can anybody tell me that the file is ok? thats the original file of the All-in-one Toolkit V1.0 downloaded today fom the original source...

Hello I can't download the toolkit. Every time it's taking me to download some chrome addons. Seems very fishy.
The file in the previous post also seems not legit. Toolkit is supposed to be 40 MB, this file is about 1MB...smells of viruses to me.

ulmcity said:
Can anybody tell me that the file is ok? thats the original file of the All-in-one Toolkit V1.0 downloaded today fom the original source...
Click to expand...
Click to collapse
madzur said:
Hello I can't download the toolkit. Every time it's taking me to download some chrome addons. Seems very fishy.
The file in the previous post also seems not legit. Toolkit is supposed to be 40 MB, this file is about 1MB...smells of viruses to me.
Click to expand...
Click to collapse
@ulmcity , looks legit @mazdur , as long as @hasoon2000 has been doing this i dont think he'd post a bogus link especially not on xda. Follow the link in the OP and itll take you straight to dev-host, if it doesnt then YOURE doing something wrong dude. Heres the link.
http://d-h.st/users/hasoon2000/?fld_id=2808#files
Sent from my 2PS64 using XDA-Developers Legacy app

[Tool] Frija - Samsung firmware downloader/checker

* * * PLEASE UNDERSTAND WHAT YOU ARE INSTALLING TO YOUR DEVICES AT ALL TIMES AND ME AND THE DEVELOPER ARE NOT RESPONSIBLE FOR ANY SORT OF DAMAGE TO YOUR DEVICE * * *
Hey Guys
Frija is a new tool (successor of now depreciated tool SamFirm) which allows users to download latest firmware for their device which can be flashed with Odin.
Frija can download Firmware for any Samsung Devices at High Speed.
Auto mode detects any Samsung Phone Model and CSC and finds all the required information directly from Samsung Server.
Frija downloads firmware directly from Samsung FUS (Firmware Update Server) without any third party websites being involved. It can pause/resume firmware downloads, even after network interruption, or app restart (if download was interrupted).
Frija comes with built in Support form, through which you can reach out to developer about any issues or bugs. Frija has built in App Updater, whenever new release of Frija is available users will be able to update to latest version of the app.
Frija does not have any Background or Startup services, which some users might be concerned about.
It also comes with Night theme, for those who prefer Night Mode on the app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fun fact about Frija: Frija is named after wife of Odin who can see future (In Norse Mythology) can download latest firmwares which can be flashed using Odin which uses Heimdall (A protocol that connects to a mobile device over USB) and Loke (low-level software running on the device). It kinda added a missing piece to the naming convention Samsung has.
This tool was created by wssyncmldm with contribution from CrazyApe and eragon5779. Devs receive all the support message directly and they are actively working on the app to fix any bugs or issue.
Updates:
NOTE: Auto Update has bug in version 1.1.1 and will need to manually update by using the new zip file posted today
Changelog:
1.1.2
• Improved firmware search.
• Fixed issue where firmware was not available for valid Device and CSC.
• Updated some message strings displayed to user
1.3.0
• Fixed decryption issue of enc2 type encrypted firmware
• Auto updater finally fixed, will not require downloading update manually after this update
1.4.1
• Added error message if Microsoft Redist packages are missing
• New Settings option
• Removed support message feature and added new Issue Tracker URL
• Overall UI improvement
• Added setting to disable CRC check
1.4.2
• Improved Firmware search method
• Added support for Dual Sim model
• Added Frija sage number in About Page
• Load Samsung dll libraries in efficient way
• Fixed sub text for on/off in Settings Page
1.4.3
•Fixed firmware lookup and download issue
1.4.4
• Fixed an issue where if firmware paused and resumed after downloading more than 1.9 GB failed to download complete firmware
• Added invite link to Frija Discord
You can find the download for Frija here.

Will there be a linux build or is it windows only?
Also it would be nice to have the sources available to audit the code and make sure it does no nasty stuff.

XenGi said:
Will there be a linux build or is it windows only?
Also it would be nice to have the sources available to audit the code and make sure it does no nasty stuff.
Click to expand...
Click to collapse
For now the software is for Windows only. As for now the developer doesn't have any plans to release the code to the public.

I have been a long time user of SamFirm, it was always the best way to get firmware as soon as it is avaialble. I really appreciate your work on this project. I tested it out for myself and it works Great! Thanks!!!

XenGi said:
Will there be a linux build or is it windows only?
Also it would be nice to have the sources available to audit the code and make sure it does no nasty stuff.
Click to expand...
Click to collapse
removed

invmini said:
For now the software is for Windows only. As for now the developer doesn't have any plans to release the code to the public.
Click to expand...
Click to collapse
That's sad to hear. I''m not willing to setup a windows installation somewhere just to run some closed source code. Opening the source would make it possible for others to port the code to linux or at least have a look at it and audit it. Not only for security concerns but also to hunt bugs and report them. I'm really uncomfortable running closed source software from a random guy on some random internet forum.

Looks cool! I would prefer it to run on my Chromebook... someday. Cheers

XenGi said:
That's sad to hear. I''m not willing to setup a windows installation somewhere just to run some closed source code. Opening the source would make it possible for others to port the code to linux or at least have a look at it and audit it. Not only for security concerns but also to hunt bugs and report them. I'm really uncomfortable running closed source software from a random guy on some random internet forum.
Click to expand...
Click to collapse
Making source open is not going to help someone port it, since it uses 3 libraries made by Samsung to get info about download link and download the firmware which are only available for windows

XenGi said:
That's sad to hear. I''m not willing to setup a windows installation somewhere just to run some closed source code. Opening the source would make it possible for others to port the code to linux or at least have a look at it and audit it. Not only for security concerns but also to hunt bugs and report them. I'm really uncomfortable running closed source software from a random guy on some random internet forum.
Click to expand...
Click to collapse
I'm also a Linux user. I do have Windows on one of my partitions, but I'll have to wait for more users to report on Frija before I trust it enough to run it. With that said, I appreciate the effort and the work put into developing a useful program like that, and I hope its developers don't take my distrust as an insult.

Virustotal report for the zip

I used it yesterday to download the Odin package for my s10 plus. Worked liked a champ. Thanks!
Sent from my SM-G975U using Tapatalk

OK when its finish the download i cannot find the zip file in the PC i choose other location and same problem

Will this trip nox or is it just a quicker way to get updates before the OTA release?

As it is downloading original, Stock Firmware, it will not trip KNOX.

Thanks for developing this tool, but sorry I got this error "frija has stopped working", I installed "c ++ 2008, c ++ 2010 and dotnet 4.5" is there anything I lack?

mytuhuyennninh said:
Thanks for developing this tool, but sorry I got this error "frija has stopped working", I installed "c ++ 2008, c ++ 2010 and dotnet 4.5" is there anything I lack?
Click to expand...
Click to collapse
It's a configuration issue on your end. I used the software and have had no issues.
Sent from my SM-G975U using Tapatalk

TechSilver13 said:
It's a configuration issue on your end. I used the software and have had no issues.
Sent from my SM-G975U using Tapatalk
Click to expand...
Click to collapse
I use windown 7 64b, configure the machine, intel core i3, 3320 3.3ghz, ram 8gb, and SSD for windown drive, and 4t for storage, I use the samfirm completely normal, is there any problem here ?

Its probably me not doing something right. But Frija does not recognize my phone. Does it need to be in recovery? Debug mode etc?

This tool is great I typed in my model number gm-975F then the CSC that I wanted ( I found an online list of them by googling it.) Then bam it downloaded the fw file really fast over 120mbit down. I love the tool thank you so much

acidburn76 said:
Its probably me not doing something right. But Frija does not recognize my phone. Does it need to be in recovery? Debug mode etc?
Click to expand...
Click to collapse
Recognize? You know what's the tool for right?