Heimdall for Linux and mac - this is a program that is used on Linux that's similar to Odin for windows. It is capable of flashing extracted tar firmware AP,CP,CSC,and BL using download mode for Samsung devices.
This is not my program.
Also I am limited to Linux for heimdall so testing Mac I can not do but Instructions to install will also be posted using a link
I am testing how to flash the s7 for others limited to Linux or mac.
Linux install of Heimdall on Linux:
Go to the official website here: http://goo.gl/PQC1RN
Scroll down and click on Download(for Linux)
Click to download the Heimdall version for your Linux version (EX. ubuntu13.04-heimdall_1.4.0-0_amd64.deb will work with 14.04 & 13.04 64bit)
Click and download the frontend if you don't like to work inside the terminal
Open your Downloads folder and click to install the files you downloaded
Remember to open Heimdall as Admin(sudo) so it works correctly
Mac install:
http://rootmygalaxy.net/install-odin...3-for-mac-osx/
Steps to flashing frimware on linux:
1. open terminal and type sudo heimdall-frontend
2. look for flash tab
3. extract firmware zip to a folder then create 4 more folders named AP,BL,CP,and CSC
4. Rename AP,BL,CP,CSC by removing the .md5 part of the file name leaving only the .tar at the end
5. Extract each tar to its specific folder
6. Under the flash tab look for pit file and click browse, goto CSC folder and click the pit file
7. Now look for add and from the list under partition details choose which file to add then click browse under it should have the file name you are looking for under partition details if unsure what to put, go through each folder you made and keep adding each file
8. then click start
This is capable of flashing the firmware , as in the pictures it shows it works and fails, i am thinking because i am flashing all at once instead of each folder separate, or in the wrong order
there are forums on xda on how to use heimdall more extensivly but im just doing this for the s7 so productive comments are welcomed
Also this is being tested on a sprint version of the s7 g930p that has been flashed to g930u firmware, in the pictures im flashing a firmware i already have installed just incase i mess up
Worked like a charm for me, this post needs more attention.
XCnathan32 said:
Worked like a charm for me, this post needs more attention.
Click to expand...
Click to collapse
U were able to get all firmware files flashed and able to use phone
Related
Hi,
I downloaded a ROM from sammobile.com for my galaxy tab 10.1, and all I want is system.img which is located in a tar.md5 file .
if I extract is with 7zip I get a message "there is no correct record at the end of archive"
and dsixda kitchen don't seem to recognize it .
any ideas please .
thanks.
Well its simple just rename it to .tar and use winrar to extract it. the md5 extension makes odin calculate a hash to check if the firmware you're flashing is not corrupted.
hi,
I did that and I got a message "there is no correct record at the end of archive"
the files are extracted but I think it is corrupted because dsixda kitchen can't read it.
just extract it by 7-Zip and don't care about message
I have this problem too, my 7-zpi say that can´t open file format unknowed or damage.
your download maybe interupted, try download it again and do md5 checksum
Ace Duos Kernel
how to get s6802 custom kernel??
jeckyvanz said:
how to get s6802 custom kernel??
Click to expand...
Click to collapse
You can find a beta release custom kernel for the Samsung Galaxy Ace Duos from here.
kernel
thanks. but the download link doesnt work again.
MD5
I've problem with restoring through CWM.
it said "md5 sums mismatch. how to troble it?
logic5 said:
Hi,
I downloaded a ROM from sammobile.com for my galaxy tab 10.1, and all I want is system.img which is located in a tar.md5 file .
if I extract is with 7zip I get a message "there is no correct record at the end of archive"
and dsixda kitchen don't seem to recognize it .
any ideas please .
thanks.
Click to expand...
Click to collapse
You might be opening the wrong file.
You have to download 2 files:
xxxx.tar
xxxx.tar.md5
the first one is the one you have to open.
the second one is the one that only have the MD5 result of the first.
( http://en.wikipedia.org/wiki/MD5 )
jeckyvanz said:
I've problem with restoring through CWM.
it said "md5 sums mismatch. how to troble it?
Click to expand...
Click to collapse
Redownlaod and try to unzip again. Kitchen should open it, make sure u have kitchen scripts for your phone or edit from flashable zip. Afaik
best idea
dont use 7zip but use unoversal extractor. it will extract everything.
I have the same issue for 5301. I have to get either the recovery or system img for creating a custom rom. Usually samsung firmware files can be extracted using izarc, 7zip or universal extract tool. some can be opened with ultraISO or similar tool. I tried dsixdas kitchen as well. That does not even acknowledge this ROM. These firmwares come as a single tar file with md5 sum attached. There is something different about this ROM file that wont even let let the regular tools see what is inside the file. I tried to open it with a hex editor and it looks similar what a regular tar.md5 file would look. Looking at the log file from universal extractor:
TrID/32 - File Identifier v2.02 - (C) 2003-06 By M.Pontello
Definitions found: 2641
Analyzing...
Collecting data from file: C:\Technical\S5301XXALJ7_S5301OXXALJ8_S5301XXLJ7_HOME.tar.md5
99.3% (.TAR) TAR archive (149/5)
0.6% (.LZMA) LZMA compressed file (1/1)
7-Zip Tar archive extractions cannot be logged.
If Odin can flash these files using the same boot, recovery and system... images then there must be a way to extract these img files. wonder if odin extracts to a temp location?
Here is a link to the file http://hotfile.com/dl/198648982/cfb...5301_EUR_1_20130214151121_61bveu8l1b.zip.html
logic5 said:
Hi,
I downloaded a ROM from sammobile.com for my galaxy tab 10.1, and all I want is system.img which is located in a tar.md5 file .
if I extract is with 7zip I get a message "there is no correct record at the end of archive"
and dsixda kitchen don't seem to recognize it .
any ideas please .
thanks.
Click to expand...
Click to collapse
Use odinatrix to extrat system.img n modem files..
Its the easiest tool do so...
U may also use splitfus2 bt its way trickier to use than odinatrix.
masum73 said:
I have the same issue for 5301. I have to get either the recovery or system img for creating a custom rom. Usually samsung firmware files can be extracted using izarc, 7zip or universal extract tool. some can be opened with ultraISO or similar tool. I tried dsixdas kitchen as well. That does not even acknowledge this ROM. These firmwares come as a single tar file with md5 sum attached. There is something different about this ROM file that wont even let let the regular tools see what is inside the file. I tried to open it with a hex editor and it looks similar what a regular tar.md5 file would look. Looking at the log file from universal extractor:
TrID/32 - File Identifier v2.02 - (C) 2003-06 By M.Pontello
Definitions found: 2641
Analyzing...
Collecting data from file: C:\Technical\S5301XXALJ7_S5301OXXALJ8_S5301XXLJ7_HOME.tar.md5
99.3% (.TAR) TAR archive (149/5)
0.6% (.LZMA) LZMA compressed file (1/1)
7-Zip Tar archive extractions cannot be logged.
If Odin can flash these files using the same boot, recovery and system... images then there must be a way to extract these img files. wonder if odin extracts to a temp location?
Here is a link to the file http://hotfile.com/dl/198648982/cfb...5301_EUR_1_20130214151121_61bveu8l1b.zip.html
Click to expand...
Click to collapse
Don't be lazy.
Lift your hand n press the Thanxxx Button.=)
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
frankito777 said:
You might be opening the wrong file.
You have to download 2 files:
xxxx.tar
xxxx.tar.md5
the first one is the one you have to open.
the second one is the one that only have the MD5 result of the first.
( http://en.wikipedia.org/wiki/MD5 )
Click to expand...
Click to collapse
Now there is only one xxx_home.tar.md5 file..
That was old days.
Be a part of new world.
N now u cnt extract through an archve manager.
U need espicial tools like splitfus2 n odinatrix to extract files.
Don't be lazy.
Lift your hand n press the Thanxxx Button.=)
Thanks SArnab! so finally I am able to split the files using odinatrix. Now for this type of turbo ROMs how do I create odin flashable file???
I created a regular odin tar file with md5 sum but that does not go past 'NAND Write Start'. Please advise.
masum73 said:
Thanks SArnab! so finally I am able to split the files using odinatrix. Now for this type of turbo ROMs how do I create odin flashable file???
I created a regular odin tar file with md5 sum but that does not go past 'NAND Write Start'. Please advise.
Click to expand...
Click to collapse
Your pc shud b superfast so that odintrix can work witout lag.
My HP G6 lapi took around 10 mins to extrqct the one .tar.md5 file..
The tool will automatically extract diffrnt .tar files such as modem_xxx.tar pda_xxx.tar n csc_xxx.tar
Now u can use these to flash through odin witout any prb.
U can use pda.tar in kitchen to get boot.img n system.img.
Kitchen will also help u extract sysmtem foldr from system.img.
U can also flash through odin the single .tar.md5....
Choose that in pda field...
Odin is smart enough to do rest of the part.
Don't be lazy.
Lift your hand n press the Thanxxx Button.=)
Appreciate the quick response. I guess my question was not clear enough. I extracted the recovery and created a clockwork recovery named recovery.img. Now I want to flash this recovery back on the device. I created the tar file using:
tar -H ustar -c recovery.img > CWMrecovery.tar
md5sum -t CWMrecovery.tar >> CWMrecovery.tar
mv CWMrecovery.tar CWMrecovery.tar.md5
When I flash this using odin3_v3.07 md5 is verified but he flash does not go through and stops at NAND write start. Is there a special way to create a odin flashable tar.md5 file foe these turbo firmwares?
masum73 said:
Appreciate the quick response. I guess my question was not clear enough. I extracted the recovery and created a clockwork recovery named recovery.img. Now I want to flash this recovery back on the device. I created the tar file using:
tar -H ustar -c recovery.img > CWMrecovery.tar
md5sum -t CWMrecovery.tar >> CWMrecovery.tar
mv CWMrecovery.tar CWMrecovery.tar.md5
When I flash this using odin3_v3.07 md5 is verified but he flash does not go through and stops at NAND write start. Is there a special way to create a odin flashable tar.md5 file foe these turbo firmwares?
Click to expand...
Click to collapse
Sorry, I have no idea bout wat u r talkin.
I never did this so cant help u in tis part.
Oh ya where did u put the tar file in odin??
In pda fieled or csc or modem??
I think its need to be in pda field.
I cnt help more on this.
But ya I wnt leave it here.
A user named Deadly can help u.
He is great in converting odin to cwm n cwm to odin.
Hope u understan wat I mean.
Don't be lazy.
Lift your hand n press the Thanxxx Button.=)
System App
how to install custom system ui/android status bar on system. my device gt-s6802. what's compatible with mine??
I'm trying to change the stock firmware on my unlocked unrooted international S3: I9300 to an official Samsung ROM downloaded from sammobile. The file I downloaded is called I9300XXDLJ4_I9300OXADLJ4_BTU. It's the UK unbranded firmware. The current firmware is on the phone is:
AP: I9300XXBLH3
CP: I9300XXLH1
CSC: I9300OPSBLH3
I have unzipped the file downloaded from Sammobile, which then gave me a tar.md5 file. So I change the file to just .tar, then unzipped that file. Inside that file I have:
boot.img
cache.img
hidden.img
modem.img
recovery.img
system.img
I then tried to use this tutorial on youtube called: How to Use Heimdall on Mac OSX to Install Kernels and ROMs!
When I open Heimdall on my MacBook, I plug my phone in (in download mode) and go to utilities, detect device, which it does. Then I save the PIT file on my desktop. I then go to the flash tab and browse for the PIT file, load that. Then when I go to add the files I don't have any files listed above called zimage or factoryfs etc, but also the Heimdell options doesn't have anything called kernal or the other ones anyway. My options in the partition name drop down box are:
Bootloader
Userdata
OTA
Hidden
System
Cache
Radio
Recovery
Boot
Param
EFS
BOTA1
BOTA0
MD5HDR
TZSW
The video says to match the files, but mine seems to have different names for things.
I have searched and read many forum posts on here and other sites. Can anyone tell me what I am doing wrong with either the unzipping or with Heimdall?
Thanks
Samsung hate apple....thats probably your problem
Sent from my GT-I9300 using xda premium
Thanks, but I only have access to a Mac. I did try my work computer, but it won't let me install any programs like Odin and drivers without Admin privileges.
Hey guys.. Odin3 version3 and higher has gz support. I've been working with this for a bit and tonight I found that Odin will accept tar.md5.gz files. This is important for GNote2 users as the stock ROM is 1.2Gigs! You can get an extra 10-40% compression and 100% gaurantee that the files arrive to your users computer in the condition that you packaged them using this method. I have not found a guide on using the gz format so I thought I would write one up.
You will need:
A Linux computer
Your rom (we will call it MyROM)
How to package for Odin on Windows
I will cover packing into a single file, adding an MD5, and compressing the file down. For the purposes of this, we are working with "MyROM". You will want to call your ROM whatever you like. Just make sure to add version information to the file name so users don't get confused. Also note, the name MUST be consistent throughout the process. If you change the name, Odin can fail.
Another good tip is to put a model number in the name so there is no confusion as to what device your Odin package goes to. Several users, myself included, have 20+ Odin packages on their computer.
So first you want to turn the ROM into a single tar file and then make sure changes are written to the disk.
Code:
tar -H ustar -c boot.img hidden.img modem.bin param.bin recovery.img system.img tz.img sboot.bin>./MyROM.tar;sync;
Next we want to add an MD5 to the file so Odin can check its consistancy.
Code:
md5sum MyROM.tar >> MyROM.tar;
Now we will change it into a tar.md5 file so Odin knows it has an MD5 attached to it.
Code:
mv MyROM.tar MyROM.tar.md5; sync;
Finally we will compress it with GZip. GZip is the only compression method supported by Odin.
Code:
gzip MyROM.tar.md5 -c -v > MyROM.tar.md5.gz;
You will now have a file called MyROM.tar.md5.gz.
Conclusion
The first time the file is flashed, Odin will uncompress it into MyROM.tar.md5, then check its consistancy, then flash the file. Using this method you will be transferring the smallest file possible and adding integrity checks.
notes
Note to Verizon GNote2 users: Stay away from using Odin after IROM unlock as flashing a package intended for another device will perma-lock your device into another carrier's bootloaders. Especially stay away from GS3 as the displays are not compatible.
good ****! this is def useful
Awesome news! Any test results with the older versions? If not one click solutions may not benefit.. but servers and users will by cutting the downloads even more!
Sent from my SPH-L900 using Tapatalk 2
Windows OS
How can I do it on a Windows computer?
MAQ7 said:
How can I do it on a Windows computer?
Click to expand...
Click to collapse
Install Virtual Box and a Linux distribution. I haven't seen any tools for Windows that work properly to make tar archives that work with Odin.
cygwin.
Mine all work
imnuts said:
Install Virtual Box and a Linux distribution. I haven't seen any tools for Windows that work properly to make tar archives that work with Odin.
Click to expand...
Click to collapse
adrynalyne said:
cygwin.
Mine all work
Click to expand...
Click to collapse
I managed to make tar on Windows using cygwin :good:.
Thank you
Interesting adam, I always compressed the whole odin package into a rar file (same effect but one step extra). Also I made an article about odin a while ago:
http://broodplank.net/?p=496
Btw, did you know that you can put cwm backups (ext4.tar) inside an odin package? It's the first odin image I ever saw, filled with a CWM backup, and yes it works XD
But it's not an 1:1 copy of course, Also I wonder how nandroid backups actually store their permissions, I mean dd is a 1:1 dump, which is logical, cwm has the updater-script. but the nandroid backups which are actually just tar files packed with the contents, how do they store it?
Last thing, Odin packages can be a last resort fix, believe me, many users reported that flashing my rom broodROM_RC5.tar.md5 (which contains about 13 files, you can imagine how many partitions it includes) fixed their phone when nothing else worked.
So thank you Samsung for leaking your tool, A world with Samsung Kies only would be a very sad "softbricky" world
broodplank1337 said:
But it's not an 1:1 copy of course, Also I wonder how nandroid backups actually store their permissions, I mean dd is a 1:1 dump, which is logical, cwm has the updater-script. but the nandroid backups which are actually just tar files packed with the contents, how do they store it?
Click to expand...
Click to collapse
TAR files preserve file permissions.
I still like making a 7z out of the final .tar.md5 file.
The info in OP is great to know as it does save a step for the end user but I'd rather them take a couple steps to vet out the incompetent ones. Could prevent a brick
mrRobinson said:
I still like making a 7z out of the final .tar.md5 file.
The info in OP is great to know as it does save a step for the end user but I'd rather them take a couple steps to vet out the incompetent ones. Could prevent a brick
Click to expand...
Click to collapse
Only on the Verizon Galaxy Note. All others are IROM locked. The IROM lock prevents flashing of an improper SBOOT. An unlocked VZWGNote 2 can flash any SBOOT.
Other than this specific case, adding third party tools other than ZIP compression means your user must download special tools.
Extra files?
If I were to pack an extra README.txt file into the tar before prepping it for Odin, would Odin then ignore it during the flash? Obviously there's no entry for what to do with an extraneous text file in the pit, so hopefully Odin would just disregard it.
I happened to find out today that heimdall has support for "Heimdall Firmware Packages." You can read and write them from the heimdall frontend (the 1.3 FE binary is forward compatible with my source built 1.4 heimdall). What's interesting, is that the format is almost identical to odin's format. It is still packaged in a tar file, and it contains the same system.img, boot.bin, recovery.bin etc. files you'd find in the Odin tar. By default it's format is Package.tar.gz. The only significant difference is the addition of a firmware.xml file that identifies the proper partition for each image file, as well as the target platform, the author, and other details like that.
So I got curious. I took a Package.tar.gz file generated by heimdall, and repackaged it as a Package.tar.MD5.gz file. Heimdall has no problem reading this! So the upshot is, Odin now handles the .gz, so as long as Odin isn't bothered by an extra firmware.xml file inside the tar, the same format would be compatible with either tool.
PS> Don't flame me about flash counters or bricked phones. I do understand that Odin/Heimdall are only particularly relevant for returning a phone to stock, but that's still a very important functionality and it would be great to have a unified format.
Hello how do i flash a recovery.img file using heimdall? all i get to choose from is .pit file, and of what i cna't find anywhere for gt-i9205. Since im a linux user this is a big issue. I have read about heimdall and forund out that i should put the recovery.img in the "heimdall" folder but where is it located? i have seen the executable file while browsing through all files in different directories but no heimdall folder anywhere.
Windows is one of the bigest problems for me since my computer seams to not like it, after install on this PC it just gets bluescreen, have tried everything from XP to W10B.
EDIT:
I just found out how to do it xD
i had to create the pit file for my device in heimdall, then select the recovery partition and select my recovery.img file, uncheck repartition, check No Reboot and check Resume (use after "No Reboot")
It all worked great, now running PhilZ Touch 6.48.4. Thanks anyway xD
Hello,
This would be a short & sweet guide on how to install a custom ROM on your Samsung using ODIN. I'm going to tailored this guide for the S10e G9700 HK version (is the phone I own) I'm a linux user but Odin only runs on Windows so this works 100% on a Windows 10 VM an of course native on Windows.
1. Who is this for?
For people that can't or don't want to install TWRP on their devices. For example TWRP doesn't work with the S10E Snapdragon G9700 the HK/CHG version.
2. Will this method work on my bootloader locked phone?
NO!
Bootloader locked phones are locked in hardware there's no way to flash anything but carriers ROMs to them. If you can unlock the bootloader this guide will work for you.
https://www.getdroidtips.com/how-to-unlock-bootloader-on-samsung-galaxy-phones/
3. Can I use this only with the G9700 phone?
No you can use any device, but this guide is tailored to the s10e g9700; because the TWRP version for this phone doesnt work with Android10.
4. Why not use Heimdall and do the guide entirely on Linux?
I use Manjaro [Arch] linux and tried to get Heimdall to work but couldn't, so choose the path of least resistance, so ODIN and windows is what we got .
5. Recommended ROMs?
I'm not a fan of Google Apps so my recommendations are these (2) ROMs:
1. https://github.com/phhusson/treble_...ad/v219/system-quack-arm64-aonly-floss.img.xz (No bloat, Stock Android 10 with FOSS Apps replacements of Gapps, you can install your own on top, Like I use Google Maps (the only Gapp I use)
2. https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_bvN.img.xz/download (Lineage OS 17.1 - this is vanilla, you will have to install an App store like F-Droid or Aurora from the .apk files using ADB [FYI] - This is what I use as my daily driver!
note* the proximity sensor doesn't work with the S10E and PHH based ROMs - https://github.com/phhusson/treble_experimentations/issues/592#issuecomment-519853332
6. If using a PHH based ROM from phhusoon set this to get Bluetooth Audio working?
Under Developer Options - toggle ON "Disable Bluetooth A2DP hardware offload"
Credit goes to (for their work) @phhusson @AndyYan (Project Treble PHH & LineageOS PHH) & @mkh.mourad (CMD Script)
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Requirements
7zip - https://www.7-zip.org/
Odin - https://samsungodin.com/
CMD or PowerShell (Windows) - View attachment tar-md5-script-tool.zip
Step-by-Step Process
Get your phone Official Stock ROM - https://samfw.com/firmware/SM-G9700/TGY (this is the one for my phone)
Extract the downloaded file (you'll have the BL, AP, CP, CSC) .TAR.MD5 files
Using 7zip extract just the AP .tar.md5 (it'll have img.lz4 files: boot.img.lz4, vbmeta.img.lz4 & system.img.ext4.lz4)
Download a clean vbmeta.img file from Google - https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Now we need to compress the vbmeta.img file (just downloaded from google) using LZ4.
Go into the /bin folder inside the script zip file provided (or download LZ4 from https://github.com/lz4/lz4/releases)
Run this command
Code:
lz4.exe -B6 --content-size vbmeta.img vbmeta.img.lz4
Done with vbmeta.img (keep the vbmeta.img.lz4 file)
Now download your favorite Custom ROM (https://github.com/phhusson/treble_...ad/v219/system-quack-arm64-aonly-floss.img.xz)
Using 7zip extract the .img.xz file & Rename the file inside to system.img.ext4 (this is the system OS without lz4 compression)
Now we need to compress the system.img.ext4 file (just renamed) using LZ4.
Run this command
Code:
lz4.exe -B6 --content-size system.img.ext4 system.img.ext4.lz4
Done with system.img.ext4 (keep the system.img.ext4.lz4 file)
Want to Root the device? if yes continue on; if not skip to step 24
Take the boot.img.lz4 extracted from the stock ROM (the AP.tar.md5 file)
We need to decompress this file using LZ4.
Run this command
Code:
lz4.exe -d boot.img.lz4 boot.img
Transfer this boot.img file to a phone and run Magisk Manager (doesnt need to be a rooted phone) and patch the boot.img file
Take the patched file on your phone and transfer to your computer
Rename the patched Magisk file to boot.img
Now we need to compress the boot.img file (just renamed) using LZ4.
Run this command
Code:
lz4.exe -B6 --content-size boot.img boot.img.lz4
Done with the renamed Magisk patched (keep the boot.img.lz4 file)
Replace the stock boot.img.lz4, vbmeta.img.lz4 & system.img.ext4.lz4 with the new customize files
Extract the files from tar-md5-script-tool.zip
Copy or Move all files below to the tar-md5-script-tool folder
Files are: (we don't need the meta-data folder with fota.zip)
boot.img.lz4
dqmdbg.img.ext4.lz4
dtbo.img.lz4
persist.img.ext4.lz4
recovery.img.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vbmeta.img.lz4
vendor.img.ext4.lz4
Now we are going to build the AP file to use with Odin
Run the batch.bat file from the tar-md5-script-tool folder
Once it finishes go to the /tar-md5-script-tool/temp-folder/
Inside you will find the AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5
Flash the BL, CP, CSC (use HOME_CSC) from your Stock ROM & AP (using AP_TAR_MD5_CUSTOM_FILE_ODIN.tar.md5)
Done
Thanks to @Alberbeast for reaching out and encouragement to help the community and S10e G9700 owners :good:
note* the proximity sensor doesn't work with the S10E and PHH based ROMs - https://github.com/phhusson/treble_e...ment-519853332
Click to expand...
Click to collapse
This issue has actually been fixed a long time ago, you need to select "Enable extra sensors" in Treble settings though.
If someone knows or provides a place where to upload a complete ROM I can upload the Complete AP.tar.md5 ROM for LOS 17.1 OS Rooted with Magisk and the Android Stock FOSS image just to use with Odin. Let me know! Thanks
phhusson said:
This issue has actually been fixed a long time ago, you need to select "Enable extra sensors" in Treble settings though.
Click to expand...
Click to collapse
Oh thanks! I did had it enable and it didnt pair with my car radio; but I will try it and edit the post accordingly and let you know if theres a bug with the G9700 if it doesnt work
wow this is awesome:laugh: thank you so much @kkoo for the effort to create this guide, it's a life saver for those of us who can't use twrp and want to try aosp.
Thanks again bro!
I am new to Samsung
Following OP doesnt trip knox and other Samsung stuff , correct ? Which means, I can reflash with Samsung stock rom with losing samsung functionality like samsung pay.
Does it work with us or canadian version of the snapdragon?
pchetan2 said:
Following OP doesnt trip knox and other Samsung stuff , correct ? Which means, I can reflash with Samsung stock rom with losing samsung functionality like samsung pay.
Click to expand...
Click to collapse
You can always reflash back to Samsung Stock ROM. I don't use any Samsung App so never cared about knox, but I assume it does trip knox.
bilrage said:
Does it work with us or canadian version of the snapdragon?
Click to expand...
Click to collapse
No it doesn't work with any North America Galaxy S10 as those have the bootloader locked!
Do the Roms have gaps?
Diaze said:
Do the Roms have gaps?
Click to expand...
Click to collapse
Here
https://github.com/phhusson/treble_experimentations/releases
Get the one for your phone Arm64 probably with Gapps.
kkoo said:
If someone knows or provides a place where to upload a complete ROM I can upload the Complete AP.tar.md5 ROM for LOS 17.1 OS Rooted with Magisk and the Android Stock FOSS image just to use with Odin. Let me know! Thanks
Click to expand...
Click to collapse
You can upload your complete rom here https://androidfilehost.com/
Can you please explain why you use Aonly and ABonly both rom in this tutorial..? as I know only ABonly rom is for galaxy 10 series. maybe I am wrong but can you please explain it..
Thanks for your hard work Brother..
Nobin118960 said:
You can upload your complete rom here https://androidfilehost.com/
Can you please explain why you use Aonly and ABonly both rom in this tutorial..? as I know only ABonly rom is for galaxy 10 series. maybe I am wrong but can you please explain it..
Thanks for your hard work Brother..
Click to expand...
Click to collapse
Hey, sorry I already deleted the Windows VM with the complete ROM images.
Yes for my S10E Galaxy phone I use the Aonly ROM as this is what worked for me. Also I don't plan to use the functionality of an A/B ROM so to meet the extra things A/B gives are unnecessary. But like you probably assume, you can use any ROM or Phone you like. I based the tutorial on the Galaxy S10e because thats what I own.
Excited with this. I own a G9700 HK version, and I didn't even root it - been rooted since like 2012.
Miss custom roms and this thread completely encourages me to give it a shot for this device. Thank you.
Did you manage to get microg installed on LineageOs?
Will this work for the Snapdragon S9+ (SM-G965U1)?
Does it work with Exynos Devices?
Samsung Galaxy m11 ships with 32 bit os android 10 Snapdragon 450. So, which gsi should be used?
Litleck said:
Will this work for the Snapdragon S9+ (SM-G965U1)?
Click to expand...
Click to collapse
Similar quotations here... I have a N950U (ATT)
I really miss my GS2 and how easy it was too flash that device!
Nice, thanks for sharing.
I wonder if it trips Knox, if someone can check.
is it possible to flash an older firmware through this process?