Related
So I stumbled upon the files for the nougat beta program for samsung on another forum that I follow. I just wanted to share this and know if this could mean anything as in a modified stock nougat for our phone or possible even a bootloader exploint found in this beta. Read the original link first for more details.
CAUTION
User Maherk from the forum said this on the flashing matter:
"One issue that I faced while flashing the device, is that Odin kept crashing when the process gets to system.img, which meant that I soft bricked my phone.
If that happened to you, don't panic, press volume down+power button for 10 seconds, the phone will show an emergency message, stay there, and plug the phone and flash the file again. Don't go back to the download mode, just stay on the emergency screen and flash it.
Another thing to consider, the zip file you get might have 4 files, AP, BL, CS, and CSC. If it does, then make sure to rename the AP to .tar instead of the .tar.md5
Good luck"
All credits below:
http://www.phonearena.com/news/No-place-left-at-the-Android-7.0-Nougat-beta-table-for-your-Galaxy-S7-Heres-how-to-sideload-it_id87665
Download to the Zip (2.06 GB):
http://downloadmirror.co/1KtH/G930FXXU1ZPK4-thanks-samfirm.net.zip
This is for the UK Exynos model. I'm fairly certain it won't work on Snapdragon devices, but would love for someone to tell me I'm wrong.
Have you flashed this on G930T?
atrix_noob said:
Have you flashed this on G930T?
Click to expand...
Click to collapse
I would've like to but I cannot as I need my phone for work. If someone would like to try this I would appreciate it very much but do be wary of risks that are posed with flashing Roms.
It will not work. It's like trying to put diesel in a gasoline engine.
I thought the same, this will not work.
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint. It would appear that Boost and Virgin Mobile variants can be flashed as they are used on Sprint's network, but no promises will be made.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing.
In the "CSC" box, use the file beginning with "home_CSC" to retain your user data, or use the "CSC" file to completely wipe user data. If you bricked your device, you may need to resort to using the "CSC" file. If you flash with "home" and it still fails to work, use "CSC." (that's my understanding of the two files anyways)
If you are down-grading, you may have to select the "NAND erase all" check box. This will completely wipe the device and should allow a fresh install. Be careful, if the phone dies, I would worry about a hard brick, but I'm not positive about that though.
Google Drive link:
https://drive.google.com/file/d/0B2iEgzRTFjrQWlpEbURIWUlXLWc/view?usp=drivesdk
There have been several reports that these Odin ROMs fail to flash. If that happens to you, you may be able to try an alternate procedure here. Keep in mind this procedure will trip Knox and probably void warranty if you haven't done that already:
https://forum.xda-developers.com/general/general/rom-stock-pl1-samsung-galaxy-j3-emerge-t3689346
The newer QI1 version is posted here, and has been confirmed:
https://forum.xda-developers.com/showpost.php?p=74171277&postcount=39
and if you're more enterprising with your computer and image file skills:
https://forum.xda-developers.com/showpost.php?p=74137125&postcount=29
Greaper88 said:
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing. I'm not sure what the difference between the "CSC" and the "HOME _CSC" files is (or that it really matters), but I'd imagine that if one is resorting to this, then someone could tell us... Based on my previous devices, I'd recommend the "CSC" file.
https://drive.google.com/file/d/0B2iEgzRTFjrQWlpEbURIWUlXLWc/view?usp=drivesdk
Click to expand...
Click to collapse
good stuff broseph,might (MIGHT) have a go ,idk re cinfiging my type of peivacy and workarounds aint time cheap so ill leave it at that, good ish tho, I wanna create a deodexed verasion myself but had a setback pc wise regarding a unbootable Hdd , I believe a deodexed rom to be a pre-requisite to having the xposed framework workout ....am i correct in believing this guys and gals? Let me know because I really love my ubuntu pc and would most likely buy a hdd just for these type of tasks since compipation would require over 100gb from what I have heard ,. 4 gb file then decompile and rexompile eaxh of the apps and framework resources.
Doctur said:
good stuff broseph,might (MIGHT) have a go ,idk re cinfiging my type of peivacy and workarounds aint time cheap so ill leave it at that, good ish tho, I wanna create a deodexed verasion myself but had a setback pc wise regarding a unbootable Hdd , I believe a deodexed rom to be a pre-requisite to having the xposed framework workout ....am i correct in believing this guys and gals? Let me know because I really love my ubuntu pc and would most likely buy a hdd just for these type of tasks since compipation would require over 100gb from what I have heard ,. 4 gb file then decompile and rexompile eaxh of the apps and framework resources.
Click to expand...
Click to collapse
The system ROM is actually about five and a half gigabytes based on the storage info in the device settings (on my device anyways). So here's what I'm thinking makes sense for space required. I'm just gonna round the decompiled ROM up to 6GB to allow room to play with. Here's the space you'll need at a minimum:
1. 6GB for the compiled ROM.
2. 6GB for the decompiled ROM.
3. 6GB minimum for working with the ROM, so that your source is unmodified.
4. 6GB for the recompiled ROM.
So you'd need a minimum of 24 GB to work with, but the more you have, the more breathing room you have. This is just my 2¢... As for the rest of it, I have no real clue.
I just bought the j327p last week and I am returning it today if I can't get the tethering to work.
I tried editing a lot of the easily searchable fixes which there aren't many.
Do you know if installing this might work?
Just obtained this phone from Boost Mobile. Am I correct in thinking that this ROM should work on a Boost Mobile phone seeing as Boost is an MVNO of Sprint?
SammaelAkuma said:
Just obtained this phone from Boost Mobile. Am I correct in thinking that this ROM should work on a Boost Mobile phone seeing as Boost is an MVNO of Sprint?
Click to expand...
Click to collapse
It works and it's been updated from APL1 to AQB6 .. at least mine has .. and I don't know what was updated or what's new but it's still on Android 6.0 .. I just used this to fix my Boost J3 Emerge after it got stuck installing an app from the Galaxy S8
Doctur said:
...I believe a deodexed rom to be a pre-requisite to having the xposed
This link will get xposed to work...
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
TD378
Divided we stall,
United We Install!
Click to expand...
Click to collapse
Actually Wanam got xposed working on our device. Nice tut but its really almost standard issue when dealing with samsung. Im guessing this is your first galaxy phone? Personally done myself on the galaxy s4 sch r970 (ya the one from 2013.. ), j7 j700t and this galaxy emerge 327p, there are also many tutorials on how to do so, thanks for trying to help, but you could have just linked wanams thread wich has all cautions and tuts in like 12 words a HUGE thanks to Wanam for spending countless hours making a modded version of xposed that is compatible with ours as well as many other galaxy devices!!!
Project89Odin said:
...Im guessing this is your first galaxy phone? Personally done myself on the galaxy s4 sch r970 (ya the one from 2013.. ), j7 j700t and this galaxy emerge 327p...
Click to expand...
Click to collapse
Choose to stay away from "main stream" phones for a number of reasons.
But at the request of your post, link has been updated!
TD378
DIVIDED WE STALL
UNITED WE INSTALL
Thank you, the Galaxy J3 is not a very followed device by samsung of the fact that it is not high-end
________________________________________________________________________________
http://iphon8.fr/ galaxy note 9
Greaper88 said:
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing. I'm not sure what the difference between the "CSC" and the "HOME _CSC" files is (or that it really matters), but I'd imagine that if one is resorting to this, then someone could tell us... Based on my previous devices, I'd recommend the "CSC" file.
Click to expand...
Click to collapse
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
vivianajeanty said:
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
Click to expand...
Click to collapse
Download the default firmware here...
http://updato.com/firmware-archive-select-model?record=F2F2C99C28B211E7963AFA163EE8F90B
In Odin, put each file in the correct section "ex. APxxx goes in AP section."
Use CSCxxx file NOT Home_CSCxxx in CSC section. All data will be lost.
Brick problem will be solved. Let me know if you need a tut created.
TD378
Divided we stall
United we install
If refering to me as this being my first Samsung that would be a negative....mainly all ive dealt with or care to deal with besides a few exceptions ( IOS Not EVER being one of those) After all thesr years of either referring quickly to this site or the last 2 1/2 pouring countless hours learning random device or specific ...usefull or not (* Few times have i bee let downyet its been an occurance.. worth noting) I belived it was time to throw my hat inthe ring.
So mainly besides wanting to recontribute the resources I have.....mostly my hours of studying and stuff i picked up retentetion being put work and the test and the Love of Working in A Linux Terminal
(*Flavor preference is not important.)
And the Fact that I have a Laptop that can process at about 3.7ghz with 8 threads if you include hyperthreading...along with my growing older and not wanting to Let small contributions like that and Development left saught after by the few.....and honestly which matters in some places I am only scraping by so Financially I have nothing to offer the community along with Tha Mad Love I have for everything XDA ....put that together and you got me doing what I can..Lately it hasnt been to much but wait around and other issues that have eaten away at time leaving me unable to do simple things such as deodex......tho I was looking to do it the hard way and by hand..
My apologizies if the post after mine answered or the second one did but I have yet to read link .....so besides me knowing Wanam got a way around it for most the Install and Stuff
My true and Last Attempt at my first Question
FINGERS CROSSED
LONG
Would there be any necessity in the terms of Modular Functionality either individual or a compilation of your choosing and or combination that would specifically require you to deodex the firmware of any 5.0 or Higher Samsung Based Firmware so that one might have a higher sucess rate or all around better experince?
SHORT
Should i spend my time deodexing this rom for the few who have it in attempts to better the end user experience , spend my time else ?
Id like a little bit of step i the right direction but might just do it and then move to more time , intelectually and pc resource consuming work....
---------- Post added at 01:14 PM ---------- Previous post was at 01:04 PM ----------
vivianajeanty said:
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
Click to expand...
Click to collapse
Umm I know if you downloaded off a disrepputable and FREE source that it might be the CSC partiton. I ll pm you with a copy of my firmware that was Adb Pulled by my old Firmware subcription site and did in Fact come from my device.....or the file was set to reupload for seeding purposes....idk either way we will handle this as a community united.
NOTE
I have since given device up....
Havent given up on it ...
So yeah to modding out a new more flagship type model...
Building ,Porting , Deodexing this J3 ....
And just seeing a lil development o a mid to low end device * price =low specs=mid....ish
Growing as a person in both knowledge and contributionally as well. Thanks 4 time.... **Sorry if I ramble.**
this did get my boost samsung j3 emerge working again but the problem is no matter what i do i can not get it to pass the safety net test :/ the software version is also different from the stock version
this version:j327pvpu1apl1
stock version:J327PVPU0APJ2
am i correct in assuming that this could be my safety net issue? and if so can anyone help point me in the right direction to the stock boost firmware? ill be searching for it regardless but if i can get help before i find it then that'd be super thanks for asking
tac0xenon said:
this did get my boost samsung j3 emerge working again but the problem is no matter what i do i can not get it to pass the safety net test :/ the software version is also different from the stock version
this version:j327pvpu1apl1
stock version:J327PVPU0APJ2
am i correct in assuming that this could be my safety net issue? and if so can anyone help point me in the right direction to the stock boost firmware? ill be searching for it regardless but if i can get help before i find it then that'd be super thanks for asking
Click to expand...
Click to collapse
Are you rooted? Or running a custom kernel? Both of those things and a few others will cause you to fail. Another option would be to select NAND erase in ODIN when you flash. That will completely wipe your device before flashing, but as with any flashing procedures, it could lead to an unusable device.
Greaper88 said:
Are you rooted? Or running a custom kernel? Both of those things and a few others will cause you to fail. Another option would be to select NAND erase in ODIN when you flash. That will completely wipe your device before flashing, but as with any flashing procedures, it could lead to an unusable device.
Click to expand...
Click to collapse
I was rooted with super su but after failing safety net I began searching for a a way around it and i successfully unrooted my phone then re rooted with magisk and passed the safety net test yay! And life was good for a while until I to install xposed framework. I made a super noob mistake and flashed it with a low battery percentage and of course it died in the middle of it. I turned my phone on and no OS... Crap baskets... noob mistake number 2 my nandroid backup I must not have been paying attention and tried to save it to internal storage instead of the SD card which if you own this phone you probably know that it doesn't work that way so double crap baskets.
Fast forward to finding this post I loaded it up everything works as it should but it won't pass safety net rooted or not and no custom kernel
This is not a life or death problem as everything works flawlessly except for the safety net test But my woman likes to go on walks and play Pokémon go together and now I can't and it is slightly annoying that we are no longer able to. It's a cheap way to get outside and have a little fun towards the end of the week as opposed to Netflix and other boring stuff
tac0xenon said:
I was rooted with super su but after failing safety net I began searching for a a way around it and i successfully unrooted my phone then re rooted with magisk and passed the safety net test yay! And life was good for a while until I to install xposed framework. I made a super noob mistake and flashed it with a low battery percentage and of course it died in the middle of it. I turned my phone on and no OS... Crap baskets... noob mistake number 2 my nandroid backup I must not have been paying attention and tried to save it to internal storage instead of the SD card which if you own this phone you probably know that it doesn't work that way so double crap baskets.
Fast forward to finding this post I loaded it up everything works as it should but it won't pass safety net rooted or not and no custom kernel
This is not a life or death problem as everything works flawlessly except for the safety net test But my woman likes to go on walks and play Pokémon go together and now I can't and it is slightly annoying that we are no longer able to. It's a cheap way to get outside and have a little fun towards the end of the week as opposed to Netflix and other boring stuff
Click to expand...
Click to collapse
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Greaper88 said:
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Click to expand...
Click to collapse
Thanks for the tips I'll try it when I get home and let you know how it goes much appreciated
Greaper88 said:
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Click to expand...
Click to collapse
Had to flash three times but your advice worked thank you very much
Frp
Hello I have a question I'm a newbie and I would like to know if when I do install the stock rom does that mean I have to put in the google account information of the person providing the stock rom
Nougat has been terrible for me since the OTA upgrade. VERY laggy...quite often, like almost constantly, lags of 5 to 15 seconds to do anything (scrolling, swtiching apps, clicking a button, etc). It is pretty much unusable. So I want to go back!
However, though I've done ROM flashing on earlier phones, it is not something I do often, so need a bit of help. I know the basic process, but trying to understand which stock firmware to flash. I see them here for the 920i (sammobile com/firmwares/galaxy-s6/SM-G920I/)...but no US region. I suspect because I bought this as an unlocked phone...it was from another region. I am in the US and have ATT as my provider. So which firmware version specifically would I flash...thinking Australia...just because it would be in English...but can only one point me in the right direction?
Thanks a bunch,
Chad
PS: Ive tried to troubleshoot the issues in nougat a bit, but without much luck...I've seen to turn off animation, no help. Run in safe mode...seems to run ok, but then its running none of my apps....I suppose I could install all my apps, then reinstall one at a time...but that would take more time than I have. Any other suggestions...I am open!
Anyone? This phone is driving me nuts!
Don't do OTA updates, they only Layer actual system installed, always perform a clean update from an original firmware file.
chadwixk said:
Nougat has been terrible for me since the OTA upgrade. VERY laggy...quite often, like almost constantly, lags of 5 to 15 seconds to do anything (scrolling, swtiching apps, clicking a button, etc). It is pretty much unusable. So I want to go back!
However, though I've done ROM flashing on earlier phones, it is not something I do often, so need a bit of help. I know the basic process, but trying to understand which stock firmware to flash. I see them here for the 920i (sammobile com/firmwares/galaxy-s6/SM-G920I/)...but no US region. I suspect because I bought this as an unlocked phone...it was from another region. I am in the US and have ATT as my provider. So which firmware version specifically would I flash...thinking Australia...just because it would be in English...but can only one point me in the right direction?
Thanks a bunch,
Chad
PS: Ive tried to troubleshoot the issues in nougat a bit, but without much luck...I've seen to turn off animation, no help. Run in safe mode...seems to run ok, but then its running none of my apps....I suppose I could install all my apps, then reinstall one at a time...but that would take more time than I have. Any other suggestions...I am open!
Click to expand...
Click to collapse
First Download an app called: PHONE INFO SAMSUNG. Open it and check your original CSC code. Once you find this, go to updato.com enter your model number and select your CSC in filters. Find the FW you want to download and download it.
Once the firmware had downloaded extract it. Download Samsung Odin and open it up. Make sure you have Samsung USB Drivers installed. Select AP in Odin and select the previously extracted file. Wait for it to check the md5. Wipe your entire phone including Internal Storage. Put your phone into Download and hit Start in Odin.
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
** PLEASE DO YOUR PART AND READ / SEARCH / RESEARCH BEFORE POSTING AND/OR ATTEMPTING ANY MODIFICATIONS TO YOUR DEVICE. THIS GUIDE ASSUMES YOU ALREADY KNOW HOW TO OR HAVE ALREADY UNLOCKED YOUR BOOTLOADER, ALREADY ROOTED YOUR DEVICE, HOW TO FIX KG STATE ISSUES, HOW TO USE ODIN, 7-ZIP, LZ4 TOOL, ETC. THIS POST IS SIMPLY MY OBSERVATIONS AND STEPS TO UPDATE THE FIRMWARE WHILE ROOTED WITH MAGISK, WITHOUT LOSING DATA / REQUIRING A WIPE. MODIFYING YOUR DEVICE COMES WITH INHERENT RISKS, AND IT'S NOT MY RESPONSIBILITY IF YOU LOSE YOUR DATA. THE STEPS I SHARE HAVE WORKED WITHOUT FAIL FOR ME, BUT THAT DOESN'T MEAN YOU MAY NOT RUN INTO PROBLEMS. BACKUP YOUR DATA.**
The reason I decided to write up this guide is because of the extremely large amount of misinformation, as well as general noob-ness (no offense to anyone, just my observations to be completely honest), that I seem to come across when it comes to the Samsung sub-forums around here. I've seen many people state that updating the firmware on this particular device (Galaxy Tab S6 LITE) will REQUIRE a data wipe, which is simply not true in my experience. However, I will admit that the procedure is extremely bass ackwards when it comes to this particular device, so maybe that's why people have been claiming this.
This guide only applies to stock Samsung firmware users.
Spoiler: Boring Backstory (click to read):
I ditched Samsung a long time ago, after the Galaxy S5 (not TAB, but the phone) days, when they really started locking up the bootloaders on the USA variants. Only T-Mobile was excluded on that particular model, but from what I understand, pretty much all Snapdragons since then have been completely locked down, across all carriers. So first of all, F*CK Samsung for being dickholes. Other than that, I recently decided I wanted to start using an Android tablet again, so at first I bought a Galaxy Tab S6 Lite several months ago. Eventually I got the Galaxy Tab S7 Plus, after hearing (and it's true) that the S7 series tablets actually kept Widevine L1 status after unlocking bootloader / rooting. Heck yeah.
Anyway, my Tab S6 Lite just gathered dust over the last few months, but now that I'm donating it to a friend of mine who's in school, I reloaded it with stock firmware, but rooted and heavily modified (he's an art student, so having all the stock Samsung / S-Pen integrations will be very useful for him). I finally decided to take some rough notes (written and mental, lol) about the process of updating the firmware WITHOUT losing data. As in updating your device as if like taking a standard OTA, but needing to do it manually because we're rooted and modified.
Unfortunately, like I said this device is freaking weird. Not sure if it's because it's Exynos (it's my first Exy device) or what, but it doesn't follow the same procedure as I've been used to back in the Galaxy phone days, other Tabs I've come across, nor with the Galaxy Tab S7 Plus I now own... Which is to literally follow the instructions as the creator of Magisk himself, @topjohnwu, published on his Github (see the Samsung section): https://topjohnwu.github.io/Magisk/install.html
But following those official Magisk instructions will result in this particular device not being able to boot, and you will need to wipe and start over. tl;dr - normally for sammy devices, you need to patch the full AP file in Magisk Manager and flash that in the AP slot in Odin because it also patches vbmeta to work around AVB. But for this device, this doesn't seem to be the case. At least in my experience.
Spoiler: Technical Rantings; Still Worth A Read IMO (click to read):
For some reason, on this particular device, you can't just patch the entire AP file. That will result in your device not booting, and eventually requiring a clean (wipe it all) Odin flash. Instead you need to flash the full, unmodified AP file (which normally would screw you over and is completely advised against), and then some extra steps... Anyway, I've outlined those steps below, as well as some preparation you'll need to do beforehand, which really just involves patching the boot image itself and placing in a .tar archive, which I would hope you already know how to do to be perfectly honest.
Not sure WTF is going on, as on other Samsung devices, you want to patch the entire AP file because Magisk will also automatically patch the vbmeta image thus working around AVB restrictions. It's really freaking weird to me because normally failing to patch vbmeta should normally result in inability to boot and subsequent SOL situation where you need to wipe... but with this device, it's ass backwards. And Magisk does indeed patch the vbmeta image when patching the full AP for this device... Why instead you need to skip patching the full AP file and flash just the patched boot image separately (thus skipping patching vbmeta) makes little sense to me. Not sure why this tablet is different, but again I'm not usually a huge fan of Samsung anyway so I really don't give AF. But they make the best Android tablets, so now that I've recently bought them (though I won't have this model S6 Lite for much longer), well I wanted to share with you guys; here are my working update instructions for the Galaxy Tab S6 Lite, without losing data. At least it works for me.
FOLLOW THIS GUIDE AT YOUR OWN RISK! AND BACKUP YOUR CRAP BEFORE ATTEMPTING, JUST IN CASE.
I'm not responsible for any problems you incur, etc. etc. blah blah.
(BTW, this is for the SM-P610 - WiFi USA version. Not tested on LTE, and if you try on LTE, you'll also have a CP file to flash, fyi. I have no experience with the LTE model either). This guide assumes you already have your bootloader unlocked, know how to use Odin, aren't a complete noob, and can at least restore back to stock if crap goes sideways.
Below are some bonus resources anyway, to hopefully clear up some silly questions before they come up.
* Please thank the devs and OP's of these posts if you find them helpful and/or use their tools. It's the least you can do! *
[FRIJA] USE THIS TO DOWNLOAD THE LATEST FIRMWARE: https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910584/
[ODIN *PATCHED*] I RECOMMEND VERSION "Odin3 v3.14.1_3B_PatcheD": https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
[LZ4 TOOL] DECRYPTS LZ4 EXTENSION'D FILES: https://github.com/lz4/lz4/releases
[BL WARNING TEXT REMOVAL] TO REMOVE UGLY WARNING TEXT AT BOOT: https://forum.xda-developers.com/t/...tock-firmwares-modded-bl-warningtext.4195829/
* Please thank the devs and OP's of these posts if you find them helpful and/or use their tools. It's the least you can do! *
***************************** STEPS TO UPDATE FIRMWARE: *****************************
Use Frija (download thread provided above), or download firmware from somewhere like samfw.com
Open / unzip the firmware, and then open the AP archive and pull boot.img.lz4.
Using LZ4 tool (download thread provided above), decrypt boot.img.lz4 to boot.img
* you can just simply drag and drop the boot.img.lz4 file over the lz4.exe binary in Windows explorer
Copy boot.img to your tablet. Open Magisk (Manager) and patch the file.
Copy the Magisk Patched boot file back to your PC. Rename it as boot.img
Create .tar file (tar file name doesn't matter) containing ONLY boot.img - do not use compression (if using 7-Zip, add the boot.img to archive, select archive format as "tar", and use compression level as "Store"). While the .tar file name doesn't matter, IT SHOULD ONLY CONTAIN A SINGLE FILE - boot.img
Reboot to download mode. Hook up your tablet to your PC.
**IT MAY GET SCARY HERE ON SOME STEPS, BUT CONTINUE FOLLOWING THIS EXACTLY**
(Use Odin3 v3.14.1_3B_PatcheD, link provided above)
Flash new stock firmware, using BL / AP / HOME_CSC (must use HOME_CSC to not wipe data, DO NOT USE THE REGULAR CSC FILE OR IT WILL AUTOMATICALLY WIPE). If you have LTE version, also flash the CP file in CP slot. WiFi version does not have CP file.
Using default Odin options is fine (F. Reset Time, Auto Reboot). In fact, I would recommend it for the sake of following this guide.
It'll be scary, but it will reboot a few times and eventually boot into recovery mode. Don't interrupt the process and let it eventually settle on its own into recovery mode (after a few seemingly failed boot attempts).
It'll make you think you're screwed and must factory wipe the device. DON'T FREAK OUT. Options will be:
Try again
Factory data reset
View recovery logs
While USB cable is still plugged into the tablet and computer, select Try again (tap power button, but don't hold the button down) and then immediately hold down volume up and down at the same time so that and until it goes back to download mode. As prompted, press volume up to continue.
Using Odin, flash ONLY the magisk patched boot image tar file (uncheck BL / CSC boxes if Odin is still open from before). Also you can flash the modified bootloader splash tar as well at this time, might as well kill 2 birds with 1 stone. Again, you can just leave default options enabled (F. Reset Time, Auto Reboot).
Again, this will be very scary. It won't boot to system, but rather bootloader again. Probably an error at the bottom, something like "failed to load locales from the resource files" / "failed to compare" / whatever. However, the normal recovery options should now be available.
YOU WILL ONLY WIPE CACHE PARTITION (scroll down to "Wipe cache partition", and then confirm yes. Then select "Reboot system now".
It will take a while to boot, but this time you should eventually get to the lone "SAMSUNG" boot logo (this is a great sign), and then eventually get the "Tablet is updating..." box which shows the progress as it re-optimizes all of your apps.
That's it, and once it finishes optimizing your apps, should continue to load to your lockscreen! If so, congratulations, you've now updated to the latest firmware while retaining root without losing your data!
**********************************************************
Even with a heavily modified tablet, this has worked over several months, including the jump from A10 to A11. SafetyNet still passes (using kdrag0n's module), YouTube Vanced (my module), LSposed with Firefds kit and GravityBox R, and a bunch of other Magisk modules.
I'm very much aware you can save time by tweaking the above process, but this was the very safest exact procedure I could think of, so I recommend following it exactly as I wrote above.
Good luck, I hope it works for you, and enjoy your tablets!
just in case
and another
Damn, thanks dude. I'd just about given up clean flashing and thought I'll give your suggestion a go and it worked like a Boss! Im using the LTE version and not a single hiccup. Thank you for saving me a huge hassle. Only things i didn't follow was use frija, paid$2.99 and got the firmware. Everything else was exactly what you did. Worked man! Thank you so much again.
If anyone wants the latest. ACR firmware for SM-P615, lemme know and I'll share my drive link with you.
Cheers! Kudos. On latest may update now.
Didn't do the 2 birds one stone thing, was scared. I'm gonna do that later. Again, just to clarify, i run Magisk only for and root level file brousing, does it really matter if i don't pass the test? Everything runs as it should, just curious if there was a benefit to it.
Thanks a lot for this detailed guide!
It worked perfectly on my Galaxy tab S7, I updated it successfully with magisk already installed.
didnt work for me on the CUH2 update
sunmybun said:
didnt work for me on the CUH2 update
Click to expand...
Click to collapse
I actually just tried it and it does still work for CUH2. I am happy for this firmware as I was having a weird system reboot every time I unlock with PIN.
shattacrew said:
I actually just tried it and it does still work for CUH2. I am happy for this firmware as I was having a weird system reboot every time I unlock with PIN.
Click to expand...
Click to collapse
it mightve not worked for me because i decrypted my data partition by factory reset and disabling the system to encrypt and check the partition before booting.
one of the tablets is encrypted and is using the KOO firmware, and the updating steps doesnt work either.
Ive flashed the tablets that were originally XAR firmware to KOO firmware.
im giving my inputs with my situation.
if anyone can find a way for my situtation, let me know =)
So I haven't updated my rooted tablet since the September 2020 update. Can I still jump to the latest version and still root or do I need to do some additional steps first?
still hasnt worked for me. I even went back to the tablet being encrypted.
for people who updated to DUL9 and rooted. please tell me the steps because it doesnt work for me
Can you specify the process of creating the TAR file? I patched the boot file from AP in Magisk already.
I used WinRar to make a .zip containing boot.img, then renamed it from AP-SLOT.zip to AP-SLOT.tar. Don't know if that's acceptable. I also used the "Store" compression method.
Afterwards what slot in Odin do you upload the .tar file to? I tried the AP slot but it hangs at "File analysis.....". It seems like it want a .tar.md5 file
TheCoryGuy said:
Can you specify the process of creating the TAR file? I patched the boot file from AP in Magisk already.
I used WinRar to make a .zip containing boot.img, then renamed it from AP-SLOT.zip to AP-SLOT.tar. Don't know if that's acceptable. I also used the "Store" compression method.
Afterwards what slot in Odin do you upload the .tar file to? I tried the AP slot but it hangs at "File analysis.....". It seems like it want a .tar.md5 file
Click to expand...
Click to collapse
you cant just rename from zip to tar. you have to use a diff program like 7zip to make into .tar
Great instruction. Everything is up and running and that stupid splash screen is gone. Great job, @i5lee8bit.
Late for the party...
I've found a python utility to download Samsung firmware at full speed.
It's quite easy to use:
SamLoader
[Tool] Samloader (SamFirm / Frija replacement)
Hello, I recently wanted to download some firmware for my Samsung device, but I realized that there is no 100% open source program to do so. In fact, all the tools that claim to do so require a library that is packed by Themida (so it is...
forum.xda-developers.com
Thank you @i5lee8bit this worked like a charm.
One question though, using a patched Odin is a not a requirement, is it?
Thank you @eddiefive for samloader link.
I just completed this to upgrade to Android 13 on my Tab S6 Lite. It worked perfectly. Thanks so much. I'm always amazed at the community support here.
awtompson said:
I just completed this to upgrade to Android 13 on my Tab S6 Lite. It worked perfectly. Thanks so much. I'm always amazed at the community support here.
Click to expand...
Click to collapse
I had successfully used this method to update to Android 12 (SM-P610_2_20221024120141_tk8omuwosv_fac)
I just tried updating to Android 13 (SM-P610_3_20230118120131_f9h5nltlpa_fac) and after wiping the cache step and rebooting to system, it goes into bootloop.
I tried twice, and in fact I re-downloaded everything and did all the steps just in case there was any corruption in any step or I missed something. Same thing. bootloop.
Had to re-apply Android 12 to recover the tablet.
I used Odin3 v3.14.1_3B_PatcheD
Any ideas?
badabing2003 said:
I had successfully used this method to update to Android 12 (SM-P610_2_20221024120141_tk8omuwosv_fac)
I just tried updating to Android 13 (SM-P610_3_20230118120131_f9h5nltlpa_fac) and after wiping the cache step and rebooting to system, it goes into bootloop.
I tried twice, and in fact I re-downloaded everything and did all the steps just in case there was any corruption in any step or I missed something. Same thing. bootloop.
Had to re-apply Android 12 to recover the tablet.
I used Odin3 v3.14.1_3B_PatcheD
Any ideas?
Click to expand...
Click to collapse
Not really. I did not use the patched Odin but I don't think that'st the problem. The boot after wiping cache did take long time, but no boot loops. The trickiest part is getting it to reboot into download mode after the "Try again" step. Wish I could be more help.
awtompson said:
Not really. I did not use the patched Odin but I don't think that'st the problem. The boot after wiping cache did take long time, but no boot loops. The trickiest part is getting it to reboot into download mode after the "Try again" step. Wish I could be more help.
Click to expand...
Click to collapse
Thanks, rebooting to download was easy for me, but the damn thing almost immediately would go into bootloop after the wipe, no long wait.