Database Info

[ROOT] [i8160] [Ace2] Advanced rooting procedure WITHOUT increasing the Flash counter

SAMSUNG GALAXY ACE 2 i8160/i8160P
This could be complicated if you never used any Linux os, however with this method you can root your phone without increasing the flash counter.
Kernel, recovery, etc. will be the same as in original samsung roms, we will flash a modified (pre-rooted) system.img.
For prerooted system images and csc files see 2nd post!
Requirements:
Linux - Ubuntu 12 recommended (a virtual one will also do the job)
Windows with Odin for flashing
Patience
References:
Ext4Utils
Insipred by: Expert root method which does not increase the flash counter
First of all download your original rom from: http://www.sammobile.com/firmware/?page=3
1, Create a "samsung" directory on your linux filesystem -> "home/username" folder where username is your linux username.
2, Extract the downloaded firmware, then move system.img.md5 and cache.img.md5 to home/username/samsung dir.
(root_package.zip and ext4utils.zip also extract here)
3, Open a terminal window, and enter:
Code:
sudo mkdir /mnt/system
Type the root password and enter.
4, Now set current dir to samsung directory and mount the system image:
Code:
cd /home/username/samsung
mv system.img.md5 system.img.ext4
make
./simg2img system.img.ext4 system.img
sudo mount system.img /mnt/system
if you get error when executiong "make" type:
Code:
sudo apt-get install zlib1g-dev
5, The original system image has been mounted, now extract su binary and superuser.apk to samsung dir then, enter:
I suggest only su binary to include in /system, SuperUser can be installed later!
Code:
sudo cp su /mnt/system/bin/su
6, Now we have to adjust the permissions:
For SU binary:
Code:
sudo chown root:root /mnt/system/bin/su
sudo chmod 06755 /mnt/system/bin/su
For SuperUser app:
Code:
sudo chmod 644 /mnt/system/app/superuser.apk
7, Unmount the image:
Code:
sudo umount /mnt/system
or if it's not working:
Code:
sudo umount system.img
8, Now create md5 hashes:
Code:
md5sum -t system.img>>system.img
mv system.img system.img.md5
if you get "permission denied" first:
Code:
sudo chown username:username system.img
9, Create falshable tar and md5 hashes for odin package:
Code:
tar cf system_rooted.tar system.img.md5
md5sum -t system_rooted.tar>>system_rooted.tar
mv system_rooted.tar system_rooted.tar.md5
As you remember we copied the cache.img.md5 also, that's because we need to flash this as a separated CSC package.
10, Creating CSC package.
Code:
tar cf csc.tar cache.img.md5
md5sum -t csc.tar>>csc.tar
mv csc.tar csc.tar.md5
11, Now open Odin and select system_rooted.tar.md5 as PDA, and csc.tar as csc.
Check: Auto reboot and F. Reset Time.
Enjoy your rooted phone.
NOTES:
After flashing phone will boot in recovery mode to apply csc, then reboots automatically to normal mode.
If you download different rom than already have on the device first flash the unmodified samsung tar as PDA.

PRE-ROOTED ROMs
(Only modified system and csc - if Superuser not included download manually from Play store or install from sdcard)
PDA: XXLD8 | CSC: I8160DBTLD2 -> -> DOWNLOAD <-
Thanks to: powermetza
PDA: XXLD8 | CSC: XXLD3 | Product code: XEO -> Mirror 1 | Mirror 2
Thanks to: mastermid | szczepan2
For i8160P - Galaxy Ace 2 NFC model
PDA: I8160PXXLE6 | CSC: I8160PDBTLE5 -> Mirrors
Thanks to: soraxx
SuperUser FIX for pre-rooted rom (only if you have problems): View
FLASHING INSTRUCTIONS
0, Download odin from 1st post, extract the downloaded (pre-rooted) rom.
1, Open odin and select csc.tar.md5 (or something like that it's a smaller file max. 20 MB) as CSC.
2, Select the other file (possibly system.tar.md5 or pda.tar.md5, it's 500+ MB) as PDA.
3, Check, Auto reboot and F. Reset Time then start.
(of course first switch to download mode and connect the phone )

mount: must specify filesystem (this is error)
My OS - Linux Mint 13 with MATE, run natively.

I don't know what's the problem, the filesystem should be ext4, but in Ubuntu mounted without any errors.

any chance to reset counter? mine just rooted yesterday. damn

Thank you! It would be a good solution can be used under Windows ...
GT-I8160-ról küldve

@Szaby59
Three simple questions:
1. Can I use this method to cook pre-rooted ROM (that doesn't increase flash counter), but without samsungs bloatware? In other words: Can I somehow remove any APK that comes from samsung and still have valid warranty?
2. Did you tried this method with flash_counter=0 or did you already voided warranty and then NOT increased flash_counter?
3. Are both values "Custom Binary Download=NO" and "Current Binary: Samsung Official" still intact after this root method?
Anyway... Thank you for this... I was waiting for something like this since I bought I8160.

1, I think you can remove apps and modify some other things if you want I didn't test it but 99% it's possible (or you can remove aps later with root explorer from /system/app)
But for warranty purposes (removing root, restoring original apps) reflash the original unmodified samsung tar.
2-3, No, I didn't tried any other methods, the custom binary downloads is 0 (NO) and I have "Samsung Official".
I think the counter only observing kernel flashes, with this method the flash counter will be the same as before the flash.
Also I noticed when you reboot from adb or terminal to download mode it doesn't shows the odin mode... stuffs, only when you use the hardware keys (vol down+home+power). !Maybe! in this way we can flash a modified kernel but it's not 100% and first you need to root the phone somehow to enable "su reboot download" command.

By the way... There is no way to download the ROM from THIS site... Loading, loading, and... loading...

szczepan2 said:
By the way... There is no way to download the ROM from THIS site... Loading, loading, and... loading...
Click to expand...
Click to collapse
Login first -> blank screen -> go back and refresh > download firmware.

Do I need to create CSC file again if I want to flash back to stock-non rooted firmware? Or should I use stock PDA file only, without CSC?
Can you write down a simple "Going back to stock ROM procedure without touching Flash Counter". Many noobs (including me) would be grateful for complete solution.

Maybe the editing ROM is not working because it's Polish? I can't open it too with any archive manager...

arroyo said:
Do I need to create CSC file again if I want to flash back to stock-non rooted firmware? Or should I use stock PDA file only, without CSC?
Can you write down a simple "Going back to stock ROM procedure without touching Flash Counter". Many noobs (including me) would be grateful for complete solution.
Click to expand...
Click to collapse
Just flash back the original tar with all files as pda no csc or phone needed it's included in the tar.
@szczepan2: you can't use any know archiver to open img.md5 files.
For extracting the tar use winrar or 7zip.

Szaby59 said:
@szczepan2: you can't use any know archiver to open img.md5 files.
For extracting the tar use winrar or 7zip.
Click to expand...
Click to collapse
Ahh, got it. So if it impossible to open it, so how it's possible to mount it?
Ehh, i'm really angry because I can't root my phone... You use Ubuntu in VM or native? Or maybe LiveCD?

szczepan2 said:
Ahh, got it. So if it impossible to open it, so how it's possible to mount it?
Ehh, i'm really angry because I can't root my phone... You use Ubuntu in VM or native? Or maybe LiveCD?
Click to expand...
Click to collapse
I installed on a virtualbox virtual machine, (with 8 GB vhd) for mounting and rooting follow the steps from 1st post.

@Szaby59
I have also the problem that I need to specify type of mounting filesystem, but I have an idea.
If you are able to mount succesfuly system.img, then could you in console just type:
Code:
mount
It will give you the list with all mounted devices/images and their types - I would be grateful if you could check what type is /mnt/system.
Thanks in advance.

mastermid said:
@Szaby59
I have also the problem that I need to specify type of mounting filesystem, but I have an idea.
If you are able to mount succesfuly system.img, then could you in console just type:
Code:
mount
It will give you the list with all mounted devices/images and their types - I would be grateful if you could check what type is /mnt/system.
Thanks in advance.
Click to expand...
Click to collapse
It shows ext4 filesystem.

mastermid said:
@Szaby59
I have also the problem that I need to specify type of mounting filesystem, but I have an idea.
If you are able to mount succesfuly system.img, then could you in console just type:
Code:
mount
It will give you the list with all mounted devices/images and their types - I would be grateful if you could check what type is /mnt/system.
Thanks in advance.
Click to expand...
Click to collapse
cloudm33 samsung # mount -t ext4 system.img /mnt/system/
mount: Filesystem error, wrong superblock at /dev/loop0 etc.

Tutorial updated with additional tools and instructions.

Szaby59 said:
Tutorial updated with additional tools and instructions.
Click to expand...
Click to collapse
Can you upload also a pre-rooted rom?
For example the polish or the germany stock rom?
Thanks in advance!

[REF][I9500-I9505] How to repack galaxy S4 img files (system/cache)

Hi xda
for some reson the ext4_utils is not working well on the galaxy s4, but there is another way to do that.
so thanks to hua_wuxin explained to me how to do it, and big thank to Chenglu for this.
What do you need to do:
first flash the firmware you wnat to modify, and root the phone. (it's can't be done without root first)
Do your changes in the device, by root explorer, zip files and etc.
Then via CMD (or terminal emulator) you type the following commands to dump the partition to samsung img file. (odin img, not ext4)
The commands according to the device and partition.
I9500
System:
Code:
su
make_ext4fs -s -l 2764M -a system /sdcard/system.img /system
Cache:
Code:
su
make_ext4fs -s -l 2072M -a cache /sdcard/cache.img /cache
I9505
System:
Code:
su
make_ext4fs -s -l 2760M -a system /sdcard/system.img.ext4 /system
Cache:
Code:
su
make_ext4fs -s -l 2070M -a cache /sdcard/cache.img.ext4 /cache
Now you can flash in odin by making tar from this modified img and the rest of the firmware.
The commands to create tar file, for example to I9500. (Cygwin or Linux)
Code:
tar -c boot.img cache.img hidden.img modem.bin recovery.img system.img >> file_name.tar
md5sum -t file_name.tar >> file_name.tar
mv file_name.tar file_name.tar.md5
Good Luck!
Sorry for my bad english.

Unfortunately, this still doesn't work for the I9500. Works fine for I9505 (which for me never had any issue at all, and worked with existing make_ext4fs tools just fine), but can't get *anything* to work with I9500.

To me it worked for both I9500 and I9505.
I created successfully for the I9500/I9505 scripts to add hebrew language to the languages list, by flashing custem recovery and cache img. (extended command and zip like your old root method to I9300)
also, i created full firmwares to both models with system and cache modified.
i flashed this files on over 1000 devices (I9500), and it's works gerat.

avicohh said:
To me it worked for both I9500 and I9505.
I created successfully for the I9500/I9505 scripts to add hebrew language to the languages list, by flashing custem recovery and cache img. (extended command and zip like your old root method to I9300)
also, i created full firmwares to both models with system and cache modified.
i flashed this files on over 1000 devices (I9500), and it's works gerat.
Click to expand...
Click to collapse
Have you tried making the I9500 image on the I9505 ? Or only on the I9500 ?
Could you make and attach an empty (or containing one small file: echo 1 > file ) custom cache.img for the I9500, so I can test some more ?
Really need to get this working I wish I actually had the device, heh ...
EDIT: Also maybe attach the make_ext4fs from your device ?

Chainfire said:
Unfortunately, this still doesn't work for the I9500. Works fine for I9505 (which for me never had any issue at all, and worked with existing make_ext4fs tools just fine), but can't get *anything* to work with I9500.
Click to expand...
Click to collapse
+1 :good:

You have to make the img on the same model exactly, because they have some differences in the img building.
For example the cache.img from the I9500 cannot be convert to ext4 by sgs2ext4.jar on windows. The cache.img.ext4 from the i9505 converted fine with this jar, so there is some differences. (Maybe it is the CPU differences)
any way I made the imgs for the i9500 on the i9500, and for i9505 on i9505.
I dont have the i9500 next to me, I have it in the work. (I will be there tomorrow)
For now i'm attaching a small cache.img from the firmware I made, containing only a command file for wipe data. (after flashing)
I hope it's will help.
Any way if you want, you can send me the cfroot folder with the root files and i will build it tomorrow for you to a cache.img. (with 32M size or 2072M)
btw. how exactly i can copy the the make_ext4fs from my device? (ftom where)

Thanks, just trying to figure out what the damned difference is
If you're on Windows, can you run this ? https://dl.dropboxusercontent.com/u/25695577/i9500_makefs_test.zip
Should make a cache.img file from your i9500, identical to ones I have here from a different device. This may help me figure the difference. Please attach both cache.img and commands.out files

file attached

Thanks! My my, Samsung is adding bytes to the image, make it non-standard and outside of spec. Not sure what those bytes mean yet, I've made an image with them zeroed out. Can you see if this flashes no your i9500, or ODIN produces an error ?

check it now.
edit:
works!!
how did you made this img? (on the I9505/computer)

Awesome!
Can you try this test version of CF-Auto-Root ? https://dl.dropboxusercontent.com/u/25695577/cfar_i9500_test.zip
Please:
- unroot your device before trying (just do full unroot from SuperSU's settings tab)
- flash this test CF-Auto-Root
- pay attention - is the Android you see during rooting red, blue, or green ?
- boot and see if you are re-rooted
As for what I did: I put a lot of files together, figured out what the difference was, and wrote a tool to convert between normal images and the ones used for the i9500. If all this works, I'll upload the tool (and the code, and the docs) later.
These images are made on the computer, by the way. As I said before, for the I9505 I didn't need to do this on the phone anyway, just make_ext4fs from latest Android source. And add to that my new tool, and you can make images for i9500 ... no phone needed.

works great!
i flashed it on new device and i checked it with root explorer.
the android was red like all cf-auto root.
waitng to your tool..
thanks.

https://github.com/Chainfire/sgs4ext4fs

Chainfire said:
https://github.com/Chainfire/sgs4ext4fs
Click to expand...
Click to collapse
Hi Cainfire, tnx for your tools, may be this can help you repack image I9505...
checkout android-4.2.2_r1.2

as i9000 said:
Hi Cainfire, tnx for your tools, may be this can help you repack image I9505...
checkout android-4.2.2_r1.2
Click to expand...
Click to collapse
I don't get it... I don't need help repacking i9505, as I've stated, latest ext4 utils will just work ?

i need to repack firmware for i9505 with hidden.img.ext4
i see in your commands hidden.img without ext4 extension

This should be work (create hidden img from the device)
Code:
make_ext4fs -s -l 500M -a hidden /sdcard/hidden.img.ext4 /preload
if you like to make a tar file, use those commands
Code:
tar -c boot.img cache.img.ext4 hidden.img.ext4 modem.bin NON-HLOS.bin persdata.img.ext4 recovery.img system.img.ext4 >> file_name.tar
md5sum -t file_name.tar >> file_name.tar
mv file_name.tar file_name.tar.md5

Works like a charm
Thanks Chainfire
I've tried it on the cache partition and system partition on i9500 and everything is more than fine/
Thank you very much.

do we need to make cache.img.ext4 off of our phone in Terminal EMUlator for all to work well or is that optional. thanks
also why such a large cache size and what is the difference between the larger and smaller cache recommended sizes ? ie 30M vs the 2000+ size and should we stick with those numbers.
iask because one time odin failed me on the cach.img.ext4 so I am wondering thanks again

hebrew
Hello cainfire,thanks for your work,it's amazing, i'm useing it alot.
Is there a chance to get a hebrew script or a tar for the samsung galaxy 9505,9500
You will make me happy and i would be happy to buy u a beer
Thanks

[RAMDISK] [RECOVERY] Samsung SM-R760

Hello all,
Please find attached the recovery and the ramdisk from the firmware.
I have no language knowledge ( C+, Java ) and hence cant help with getting a root.
Could someone please look at the files and help us achieve a root.
Thanks.
Ramdisk : http://www21.zippyshare.com/v/YI1WNBKI/file.html
Recovery: http://www21.zippyshare.com/v/VffwNEbb/file.html

Anyone here with rooting skills ?

tids2k said:
Anyone here with rooting skills ?
Click to expand...
Click to collapse
not too sure why sdb sdk command "sdb root on" exist if it's always permission denied haha, but i might have something little tricky to get root acces, still on it tought

Root would be awesome. Maybe @cipherswitch can give us some pointers as his Gear S root thread is well put together.

Jhfreeze said:
Root would be awesome. Maybe @cipherswitch can give us some pointers as his Gear S root thread is well put together.
Click to expand...
Click to collapse
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.

cipherswitch said:
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.
Click to expand...
Click to collapse
We need to do a insert exploit with a method like Magisk as rooting will trigger will Knox fuse and then Samsung pay will become unusable. Also there is actually an app that checks whether the device has been rooted or not in the watch itself. My suggestion would be to pack a binary with su.apk and then making an Odin flashable package, but then I'm not sure if it will proceed as the signature validation will fail.

tids2k said:
We need to do a insert exploit with a method like Magisk as rooting will trigger will Knox fuse and then Samsung pay will become unusable. Also there is actually an app that checks whether the device has been rooted or not in the watch itself. My suggestion would be to pack a binary with su.apk and then making an Odin flashable package, but then I'm not sure if it will proceed as the signature validation will fail.
Click to expand...
Click to collapse
Im fairly sure it will beacuse its not digitally signed by Sammy.

cipherswitch said:
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.
Click to expand...
Click to collapse
i got access via sdb sheel to few sbin command like "pivot_root" and "switch_root" if this could help..
and i was able to use initrd scripts

Stupid question.
No idea if allready Gear S3 is rooted...
I was able to successfully root Tizen handsets with same method and same 1 file:
SM-Z130H
SM-Z300H
SM-Z300F
SM-Z200F
Procedure...
Copy file su into bin folder...
Easiest way... modify rootfs.img... then flash result with Odin.
Ehm... not tested with any Gear... but...
Maybe check this special Factory Firmware... aka Combination.
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
Extract rootfs.img ...
You will see su in bin folder:
/bin/su
In theory you could try now to use this su file... and inject in other rootfs.img... then flash.
Own risk!
Only as info.
I am to lazy to buy Gear S3 to check my theory...
Best Regards

adfree said:
Stupid question.
No idea if allready Gear S3 is rooted...
I was able to successfully root Tizen handsets with same method and same 1 file:
SM-Z130H
SM-Z300H
SM-Z300F
SM-Z200F
Procedure...
Copy file su into bin folder...
Easiest way... modify rootfs.img... then flash result with Odin.
Ehm... not tested with any Gear... but...
Maybe check this special Factory Firmware... aka Combination.
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
Extract rootfs.img ...
You will see su in bin folder:
/bin/su
In theory you could try now to use this su file... and inject in other rootfs.img... then flash.
Own risk!
Only as info.
I am to lazy to buy Gear S3 to check my theory...
Best Regards
Click to expand...
Click to collapse
Too bad root checker will spot that su binary and blow warranty void fuse than farewell spay

Too bad root checker will spot that su binary and...
Click to expand...
Click to collapse
Root Checker on Z-Mobiles only disable access to FOTA Server...
Not really deep investigation... but an app could check Root... maybe not Bootlaoder...
Something like this...
com.samsung.rootdetection-syspopup ...
Maybe to remove the "App" which checks if su is present or not...
No idea how much Security inside Gear S3... but maybe if you compare difference between Combination "FTMA" Firmware... and normal...
Otherwise you would also loose warranty blabla with this file?
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
No idea yet. Only theory...
Best Regards

adfree said:
Root Checker on Z-Mobiles only disable access to FOTA Server...
Not really deep investigation... but an app could check Root... maybe not Bootlaoder...
Something like this...
com.samsung.rootdetection-syspopup ...
Maybe to remove the "App" which checks if su is present or not...
No idea how much Security inside Gear S3... but maybe if you compare difference between Combination "FTMA" Firmware... and normal...
Otherwise you would also loose warranty blabla with this file?
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
No idea yet. Only theory...
Best Regards
Click to expand...
Click to collapse
With official firmwares you can't loose warranty. As you mentioned this was an internal build with most of the apps scrapped.

I treid to mount the storage but getting write protection error. Trying to compile TWRP and test but unable to do so. @cipherswitch @DevALT. Some screenshots

I could create rootfs.img with su inside...
su file I would take from combination file...
Code:
COMBINATION-FTMA_R760XXU1APK3.tar.md5
rootfs.img I have at the moment only from this Firmware:
Code:
R760XXU1APK7_R760OXA1APK7.zip
And I have NO Gear Watch to test self.
So I "need" tester with balls and SM-R760 who is able to flash with Odin...
OWN risk!
I could do it and upload...
But to prevent waste my time...
I will try to "explain" first...
Before I was able to root my SM-Z130H...
I have used rooted GT-I9300 to create my modified rootfs.img...
Extracting files from rootfs.img under Windows was easy with Windows Tools...
But creation of valid rootfs.img is better to do with Linux...
Need few minutes to upload extracted su file... and to post few Commands for SDB... or ADB ...
Best Regards
Edit 1.
su added...
Taken from Combination Firmware...
MD5
Code:
B784CC4DBBC86EFCC308D239D1235CE0
Now this file "must" inject into folder bin in rootfs.img
Edit 2.
Here is example how I would do it with my rooted Tizen SM-Z130H... with Batch file... few Commands for SDB:
Code:
sdb root on
sdb push su /opt/usr/media/Others
sdb shell mount -t ext4 -o loop,rw /opt/usr/media/Others/rootfs.img /opt/usr/media/Others/2
sdb shell cp /opt/usr/media/Others/su /opt/usr/media/Others/2/bin
sdb shell cd /opt/usr/media/Others/2
sdb shell sync
pause
sdb shell cd /
sdb shell umount /opt/usr/media/Others/2
rootfs.img I would copy manually to folder Others...
For rooted Android device... replace sdb with adb... and few path changes...

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-R760
For Kernel related study... Source Code is available...
I was only to lazy to download...
But in theory also here in repos...
1 RPM is inside with su...
Will check after Download... "soon"...
Best Regards

Downloaded...
SM-R765_Opensource.zip
Extracted:
SM-R765_repos.tar.gz
Unpack:
coreutils-6.9.rpm
Bingo... su Binary is inside.
But still problem...
I don't know how to install RPM without ROOT access.
I can only install RPM if allready device is rooted...
So I only know this way to inject su into rootfs.img and create then valid TAR file to use with Odin...
Simple Copy and Paste solution.
Best Regards

adfree said:
I could create rootfs.img with su inside...
su file I would take from combination file...
Code:
COMBINATION-FTMA_R760XXU1APK3.tar.md5
rootfs.img I have at the moment only from this Firmware:
Code:
R760XXU1APK7_R760OXA1APK7.zip
And I have NO Gear Watch to test self.
So I "need" tester with balls and SM-R760 who is able to flash with Odin...
OWN risk!
I could do it and upload...
But to prevent waste my time...
I will try to "explain" first...
Before I was able to root my SM-Z130H...
I have used rooted GT-I9300 to create my modified rootfs.img...
Extracting files from rootfs.img under Windows was easy with Windows Tools...
But creation of valid rootfs.img is better to do with Linux...
Need few minutes to upload extracted su file... and to post few Commands for SDB... or ADB ...
Best Regards
Edit 1.
su added...
Taken from Combination Firmware...
MD5
Code:
B784CC4DBBC86EFCC308D239D1235CE0
Now this file "must" inject into folder bin in rootfs.img
Edit 2.
Here is example how I would do it with my rooted Tizen SM-Z130H... with Batch file... few Commands for SDB:
Code:
sdb root on
sdb push su /opt/usr/media/Others
sdb shell mount -t ext4 -o loop,rw /opt/usr/media/Others/rootfs.img /opt/usr/media/Others/2
sdb shell cp /opt/usr/media/Others/su /opt/usr/media/Others/2/bin
sdb shell cd /opt/usr/media/Others/2
sdb shell sync
pause
sdb shell cd /
sdb shell umount /opt/usr/media/Others/2
rootfs.img I would copy manually to folder Others...
For rooted Android device... replace sdb with adb... and few path changes...
Click to expand...
Click to collapse
gonna try that but i'll compile myself, not that I don't trust you but if it breaks my gear s3 i want to be the one who brick it
and also for weird reason sdb root on dosen't want to work on windows (will try on Linux tomorrow, work till very late :'( )
simple curiosity did you use RPM based distro to create your rootfs.img, if not witch distro are you using?
adfree said:
Downloaded...
SM-R765_Opensource.zip
Extracted:
SM-R765_repos.tar.gz
Unpack:
coreutils-6.9.rpm
Bingo... su Binary is inside.
But still problem...
I don't know how to install RPM without ROOT access.
I can only install RPM if allready device is rooted...
So I only know this way to inject su into rootfs.img and create then valid TAR file to use with Odin...
Simple Copy and Paste solution.
Best Regards
Click to expand...
Click to collapse
as i said upthere sdb root on command won't work on my windows and your solution seems to be the one will try everything tomorrow on my Linux pc will give an update right after

Code:
sdb root on
This is only possible, if you have allready su in bin folder:
Code:
/bin/su
For better understanding you could install Tizen Studio for instance...
https://developer.tizen.org/development/tizen-studio/download
It is possible to use SDB with Emulator...
Also Wearable Image available...
So you don't need to buy Tizen Mobile or other real device to test...
Simple study Image in Emulator...
You can delete su from Image and then play again with command:
Code:
sdb root on
simple curiosity did you use RPM based distro to create your rootfs.img, if not witch distro are you using?
Click to expand...
Click to collapse
I am Windows Fan Boy...
So first time... before my SM-Z130H was rooted. I've created rootfs.img with GT-I9300 (Android handset)...
Since my SM-Z130H is rooted... I am using this device.
I've never tried to create rootfs.img with Computer... with handset it was easier for me.
Maybe I find my old post with GT-I9300... to check my ADB Commands... because path could be different...
Best Regards
Edit 1.
2 years ago... I found "inspiration" by Gear Watch Thread...
https://forum.xda-developers.com/showpost.php?p=59457357&postcount=95
Then I did something like this:
https://forum.xda-developers.com/showpost.php?p=59478150&postcount=97
Important is for Odin... TAR file...
I can remember not all Windows TAR Packer were valid...
So I am using since over 2 years only IZArc Tool.
Also important... use only rootfs.img from Firmware which is on your device...
Not mix Firmware parts from different versions... to prevent funny sideeffects.
Best Regards

sorry for late update i couldn't test anything today no free time for me until wednesday but sure will I test everything there :l

DevALT said:
sorry for late update i couldn't test anything today no free time for me until wednesday but sure will I test everything there :l
Click to expand...
Click to collapse
No panic.
For few things I have spend many months... years.
And I understand Gear S3 is at the moment very expensive "test" device...
I can wait. :angel:
Maybe someone have halfdead Gear S3... with brroken display or Water Damage or something similar...
Best Regards

Odin4 v1.0 for Linux

Hi Folks - The Info below is "obsolete" as @TheAirBlow found a New Version in the LAP$US Samsung leak ( something I didn't know was a thing ... show's how much attention I've been paying lately lol )
The newer version appears to support newer samsung firmwares which using lz4 files inside the tar's ( according to the license at least )
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux
Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in...
forum.xda-developers.com
[OLD POST BELOW]
Hi Folks
It's been a while since I posted here but I think it might be time for me to get involved again
Anyway I was reading the "Odin Downloader Release Notes.xls" and decided to translate the Korean to English. I was quite surprised to see that there was an Entry noting the release of "Odin V1.0 for Linux" ... WTF a Linux version of Odin. I figured I'd try to track this B**tard down and I've finally found one.
In some random Odin3 v3.12.7 Download I've discovered a binary called odin4 which looks legit. It's a command line tool.
The help looks like this
Code:
Usage : odin4 [args...]
Odin4 downloader. odin4 version 1.0.
-v SHOW VERSION
-w Show License
-b Add Bootloader file
-a Add AP image file
-c Add CP image file
-s Add CSC file
-u Add UMS file
-V Home binary validation check with pit file
-d Set a device path (detect automatically without this option)
-l Show downloadable devices path
IMPORTANT : You must set up your system to detect your device.
create this file: /etc/udev/rules.d/51-android.rules
to add a line to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
(http://developer.android.com/tools/device.html)
And you maybe need to unload a module cdc_acm before downloading.
$sudo rmmod cdc_acm
OR
echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf
Example :
$sudo rmmod cdc_acm
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
Example (Select One Device):
$odin4 -l
PATH_OF_DEVICE_A
PATH_OF_DEVICE_B
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A
and the beginning of the show license has
Code:
odin4 -w
Copyright(C) 2016 Samsung Electronics.Co, Ltd. All rights reserved.
the file output is as follows
Code:
odin4: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=bdec684a47ab0b2109cb60b1bea18e3878750f30, with debug_info, not stripped
Not stripped with debug info.. sounds interesting!
I've attached the Odin rar file I found it in if anyone is interesting in playing with it. I haven't managed to flash anything with it. although I was only attempting to flash a J320FN combination firmware.
Obviously use at your own risk etc etc.. and have fun!
trevd

Additional: I can confirm this works a treat on the Galaxy S6 at least ( SM-G920P ) :good:

[/QUOTE] I was only attempting to flash a J320FN [/QUOTE]
Well isn't that interesting. Is that the J3 series Samsung, that I have the J320, the J327 and the J337-V?

I decided to make an unexpected change to linux, currently on Ubuntu 14. So I have had to find new tools to work with. I'm not even sure this was really ever intended to work, but it does. Perfectly. restored a Galaxy S4 SM-S975L to stock using your linux based binary. Truly impressive.
---------- Post added at 05:09 PM ---------- Previous post was at 04:56 PM ----------
P.S. So far this has done everything the Windows based ODIN does. Just re-rooted with it too

It also works with newest of Samsung phones, flashed Galaxy G975U earlier, must decompress lz4 files and repack tar

kalexander7 said:
It also works with newest of Samsung phones, flashed Galaxy G975U earlier, must decompress lz4 files and repack tar
Click to expand...
Click to collapse
Yeah that's what I was doing with those newer firmwares. I did contemplate writing a bash wrapper to handle the lz4b stuff but never got round to it lol. I'm always hunting for a newer version which might slip out of Samsung by accident at some point.

Hi
Sorry for joining to this thread a few years later. I cannot find the odin4 .rar file that trevd is supposed to have uploaded. Could you pleae help?
Thanks

Would be nice if somebody has a download link for this, thanks.

feddozz said:
Hi
Sorry for joining to this thread a few years later. I cannot find the odin4 .rar file that trevd is supposed to have uploaded. Could you pleae help?
Thanks
Click to expand...
Click to collapse
Synt4x.93 said:
Would be nice if somebody has a download link for this, thanks.
Click to expand...
Click to collapse
Found one! There you go...
https://androidfilehost.com/?fid=674106145207484582
Another: https://androidfilehost.com/?fid=6006931924117939794

trevd said:
Hi Folks
It's been a while since I posted here but I think it might be time for me to get involved again
Anyway I was reading the "Odin Downloader Release Notes.xls" and decided to translate the Korean to English. I was quite surprised to see that there was an Entry noting the release of "Odin V1.0 for Linux" ... WTF a Linux version of Odin. I figured I'd try to track this B**tard down and I've finally found one.
In some random Odin3 v3.12.7 Download I've discovered a binary called odin4 which looks legit. It's a command line tool.
The help looks like this
Code:
Usage : odin4 [args...]
Odin4 downloader. odin4 version 1.0.
-v SHOW VERSION
-w Show License
-b Add Bootloader file
-a Add AP image file
-c Add CP image file
-s Add CSC file
-u Add UMS file
-V Home binary validation check with pit file
-d Set a device path (detect automatically without this option)
-l Show downloadable devices path
IMPORTANT : You must set up your system to detect your device.
create this file: /etc/udev/rules.d/51-android.rules
to add a line to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
(http://developer.android.com/tools/device.html)
And you maybe need to unload a module cdc_acm before downloading.
$sudo rmmod cdc_acm
OR
echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf
Example :
$sudo rmmod cdc_acm
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
Example (Select One Device):
$odin4 -l
PATH_OF_DEVICE_A
PATH_OF_DEVICE_B
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A
and the beginning of the show license has
Code:
odin4 -w
Copyright(C) 2016 Samsung Electronics.Co, Ltd. All rights reserved.
the file output is as follows
Code:
odin4: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=bdec684a47ab0b2109cb60b1bea18e3878750f30, with debug_info, not stripped
Not stripped with debug info.. sounds interesting!
I've attached the Odin rar file I found it in if anyone is interesting in playing with it. I haven't managed to flash anything with it. although I was only attempting to flash a J320FN combination firmware.
Obviously use at your own risk etc etc.. and have fun!
trevd
Click to expand...
Click to collapse
Hi, I realize that the binary you found is non exist in any other Odin download, even from it's official Odin Forum. I've been using Odin version that you've uploaded several times with big success. However, in my phone I can only flash Android 7.0 with this Odin version.
Now that I have a stock ROM for 9.0, this Odin version doesn't work. Even after I decompress lz4 and re-tar it again. After long digging on the internet, many told me that it was because I was using older version of Odin. Yours is 3.12, the latest now is 3.14. They suggested me to use newer version, little did they know I don't have Windows machine. Heimdall is a mess and never work on my Samsung, Jodin doesn't work as well.
I was wondering if you have newer version of Odin ? With binary as well ?
-------------------------------------------------------------------------------------------------------------------------
UPDATE
--------------------------------------------------------------------------------------------------------------------------
After changing ports and cable around 126722 times, I can confirm this Odin STILL WORKS !
I was able to flash a fresh ROM of Android 9 on my Samsung Galaxy S8.
TIPS : Use USB 3.0 cable, but not a fast charging cable. Fast charging cable didn't work on me at all. As for ports, port 3.0 works just fine
Only for flashing a fresh ROM. Rooting doesn't seem to work at all.

sheinbo said:
After changing ports and cables around 126721 times, I failed completely to get JODIN working - now I discover this thread- but I have to admit: I have not idea what exactly to do with odin4 (blame on me). So 2 questions: could anybody tell step by step what do do with that ODIN4 - and: did anybody flash A10 or A11?
Click to expand...
Click to collapse
1. I'm assuming you have a Linux machine ? This will run only in Linux terminal environment (or Mac -- perhaps). You can read the first post from the OP, he explains in detailed of how to use this tool (in example section), I don't think I could explain any better than the OP.
Download Odin4 from this thread, then extract it in a folder along with your extracted ROM. Inside your folder, right click and choose "Open in Terminal". Put your phone in Download mode, try to connect it 126721 times with a cable to your machine and start flashing from terminal with this code :
sudo chmod a+x odin4
./odin4 -b [your BL file] -a [your AP file] -c [your CP file] -s [your CSC file]
Click to expand...
Click to collapse
For better example, take a look at OP's original post. If flashing is succeed, your phone will restart automatically. If not, change the cable 126721 more times.
2. No. Haven't tried with A10 or A11

Question root Samsung Galaxy Watch 4?

Is there any custom roms or root guide for the Samsung Galaxy Watch 4???

No full firmware leaked nor any "hacks"...
Maybe look here:
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
Best Regards

For your info...
Samsung released Open Source for Kernel...
Firmware and Combination Firmware and FOTA Delta and CSC change and...
Looks like it could be harder since Tizen... A Stock Firmware for netOdin/Odin not available yet... B Combination Firmware not available yet C FOTA Delta File for study I have...
forum.xda-developers.com
In theory this is 1 step for Custom and/or Root...
Please remember f$%ing Knox crap...
You can faster kill Watch and/or drip Knox...
Best Regards

Maybe somebody is able to compile Kernel... IMHO this is safe... to do this... at your Computer...
I can not remember posts... easy thing just click...
Best Regards

I have compiled the Kernel, I Can't confirm if it works or not or what to do with it, but here it is https://mega.nz/folder/B00EEaQT#tctZiPD5-on3NA8KPBuRDA

Oh...
I am surpriced...
This was really fast. Thank you.
My tiny brain works really slow... and Linux related much slower... because I am Windows Fanboy...
Need some time to check...
Best Regards

A
I can not find script inside Source to create boot.img...
B
No idea if this Kernel is compatible with latest DUJA or something like this firmware...
Kernel Version for BUH9 seems...
adb shell cat /proc/version
Code:
Linux version 4.19.151-22353390-abR870XXU1BUH9 ([email protected]) (Android (6443078 based on r383902) clang version 11.0.1 (https://android.googlesource.com/toolchain/llvm-project b397f81060ce6d701042b782172ed13bee898b79), GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315) #1 SMP PREEMPT Wed Aug 11 20:22:14 KST 2021
C
...

Please.
Your Kernel is AUGE or updated BUH9 Source?
I can only see this with my old eyes...
Linux version 4.19.151 (roo...
Thanx in advance.
Best Regards

I compiled the kernel for SM-R860 (based on SM-R870_NA_RR_Opensource.zip + SM-R860_NA_RR_Opensource_R860XXU1AUGE_diff.zip sources).
I'm not sure if I created the dtbo.img correctly, I did:
python mkdtboimg.py create ./dtbo.img ./out/arch/arm64/boot/dts/*/*.dtbo
I uploaded the whole output directory (out/arch/arm64/boot/), so that anyone could create a dtbo.img if I did it wrong.
This kernel is not tested!
File on MEGA
mega.nz

In Android Studio is Wear Image rooted...
su Binary is inside:
Code:
/system/xbin/su
Somebody have an idea where we find su in Source...
In Tizen I have taken su Binary and other stuff also from RPM files...
Best Regards
Edit 1.
Need some time with Google and other search to educate myself...
What special privileges "/system/xbin/su" does have w.r.t. root access?
This answer says: Because of the way directory/file permissions are configured on Android, you need to have the su binary on your /system partition in order for it to work. Putting elsewhere...
android.stackexchange.com

From Wear AVD...
Code:
generic_x86_arm:/ # cd /system/xbin/
generic_x86_arm:/system/xbin # ls -a1l su
-rwsr-x--- 1 root shell 6500 2021-12-16 17:23 su
generic_x86_arm:/system/xbin # su --help
usage: su [WHO [COMMAND...]]
Switch to WHO (default 'root') and run the given COMMAND (default sh).
WHO is a comma-separated list of user, group, and supplementary groups
in that order.
generic_x86_arm:/system/xbin # su -h
usage: su [WHO [COMMAND...]]
Switch to WHO (default 'root') and run the given COMMAND (default sh).
WHO is a comma-separated list of user, group, and supplementary groups
in that order.
Attached is this su Binary from Wear AVD Revision 8...
Only as info...
Maybe somebody is able to build from GW4 Source Platform and/or su...
Best Regards

thei1575 said:
I have compiled the Kernel, I Can't confirm if it works or not or what to do with it, but here it is https://mega.nz/folder/B00EEaQT#tctZiPD5-on3NA8KPBuRDA
Click to expand...
Click to collapse
Hello, how to compile kernel firmware, can you provide some tutorials, thank you