Ok so before I start I did try to put this on the developers page but I haven't made enough posts yet so it didn't let me .... I am having lots of problems with my Canadian Samsung galaxy s4 sgh 1337m .... I don't even know where to start .. first off im rooted so I have that covered I know that for a fact I also have team win recovery project ... now I want to rom buy my phone will NOT allow me to do it ... I will go online I will download the rom and the Gapps directly to my internal storage ... il go into it il do the whole wipe cache and Delvik and then factory reset .. then ill flash the rom and the Gapps and it says failed to flash the rom but the Gapps are successful .. I then flash my backup and proceed with my day .... YES I am downloading them for the correct device .... why is this happening ?? in my last post someone replied my Twrp may be out dated so I went onto my new computer and tried to install Odin again so I could flash the new Twrp to my device and my computer wont let me open Odin its a new windows 8 and it WILL NOT open it it gives me some Chinese letters and closes ... Why is this happening to me ?? why cant I open Odin or download Roms to my phone ... I've watched numerous instruction videos and it works perfectly for everyone accept for me .. someone please help me .... if my issue is resolved I will be donating to XDA .... this issue has been ongoing for weeks .
have you verified the md5 sum of your downloads?
also what backup method did you use?
muskratt said:
have you verified the md5 sum of your downloads?
also what backup method did you use?[/QUOTE
What is the whole verify thing your telling me about ive never had to do it before on other devices its just been simple .... also I use team win recovery project to create my backups
Click to expand...
Click to collapse
Lets start with what rom are you trying to flash? I noticed you are trying to flash gapps.....so I take it you are trying to flash a aosp rom.
Timtim1234321 said:
muskratt said:
have you verified the md5 sum of your downloads?
also what backup method did you use?[/QUOTE
What is the whole verify thing your telling me about ive never had to do it before on other devices its just been simple .... also I use team win recovery project to create my backups
Click to expand...
Click to collapse
Most roms provide an md5 number to verify a good download. It is a checksum that tells you the download is good. Get a file explorer like FX Explorer. Long press on rom you downloaded and then open details. It will have selection to do a checksum. The number should match the one from the rom site where you downloaded it from. Very common to get a bad download from time to time. You can also use terminal on pc, if you familiar with that and have adb on your pc. I prefer that method. I do it as soon as download to rom to pc.
Also, what version twrp are you on. Most prefer 2.5.0.2. This is a flashable zip for it.
https://www.dropbox.com/sh/yhrq0tia8512rj9/FCjN8C9RMT/TWRP_Flashable-2.5.0.2.zip
Flash thru your current twrp recovery. Unless you already have 2.5.0.2 or the very latest twrp seems ok. On 2.5.0.2 don't ever do a format where you have to type "yes" to comfirm format.
I always wipe thru the Advanced menu manually. I wipe System/Data/Caches 3x. Always do that flashing new roms on new versions to a rom, unless dev says otherwise. Or, on CM Nightlies. Even then it doesn't hurt to do a full wipe on occasion. Crap can build up over time dirty flashing and cause issues.
As Ax said, unless you are flashing a CM roms, no need for gapps. Also, depending on rom you are flashing you may need to flash your carriers kernel after rom.
So, more info may be needed to help you--:good:
Click to expand...
Click to collapse
Related
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
droidzen10 said:
I apologize for the Noob question(s), but does anyone know if the **.zip.md5sum** file as listed below needs to be flashed in conjunction with the actual Rom? If so, do they need to be flashed in a particular order? I haven't been doing so since it appears to be a blank file based on the size. I only ask because ever since switching to OmniRom from GummyRom, my phone seems to get stuck at the Samsung logo screen. About half the time it requires a battery pull because my phone seems to just be stuck at boot. I'm using the latest version of CWM and have read in the Omni thread that switching to the latest version of TWRP resolved the problem. I am just curious if others are or have experienced this problem and what they did to resolve it?
Lastly, I know this is more like a three part question and if I have to post it in another thread I will. But I did try to install TWRP from the Goo Manager app and when the download page loads it doesn't install anything. The page just says it's preparing my download, but doesn't download anything. Any thoughts or suggestions would be greatly appreciated...
I am using a Verizon Galaxy S4
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip 2013-12-08 18:40 193587 KB
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum 2013-12-08 18:40 0 KB
Click to expand...
Click to collapse
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
OmniRom flashing question
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
It should not be flashed.
Its been a while since I used the twrp check-sum someone correct me if wrong.....I verify the MD5 before i put the rom on phone to ensure its a good download.
GooManager has always been flaky on my Skyrocket and on my buddies S3, but that is just me talking, nothing against goomanager. That being said I have always preferred to flash recoveries from the recovery, or odin this ensures (me) that the flash went well.
You can almost always find a zip of the latest recovery for your phone in one of the development threads or you can ask on the S4 Q&A thread if someone has one or if they can get you one. I haven't been to your forum but i'm sure there is a TWRP thread to follow.
Click to expand...
Click to collapse
Thanks for your answer and suggestion regarding flashing a recovery. I've been doing a lot of reading here on XDA and quite a few have suggested using Flashify to flash recoveries....
Tweakecho said:
First things first, the MD5sum is the checksum of the ROM at buildtime, all you need to do is have this in the same folder as the ROM when flashing and TWRP will verify the checksum of the ROM before installing, so if it is a mismatch it stops you right there.
Click to expand...
Click to collapse
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Riiquiem said:
It doesn't work that way for me. I always put the files in the same folder but TWRP 2.6.3.3 always says that there is no md5 file to be found.
Click to expand...
Click to collapse
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
AngryHapposai said:
It's because the file extension is wrong.
Zip md5 Verification (looks for file with zipname.zip.md5)
So, if you downloaded these files :
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip
omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum
You need to rename "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5sum" to "omni-4.4.1-20131208-jfltevzw-NIGHTLY.zip.md5".
Click to expand...
Click to collapse
That explains why mine always reports an error as well. *fixes all future build md5's
Having the same problem MD5 not found while flashing ROM. lemme try renaming. Will say again, if its work
What I have:
I have a Samsung J5 (2015) SM-500FN which ran out of storage and basically hung itself up. There is no data I want to recover, but I want to install either a stock ROM or (preferably) something else like Lineage - I just want to get a usable phone again.
My problem:
I have tried to download *many* stock ROM
s from reputable sources like SamMobile (for this specific phone, but trying different release dates and country codes) but every single one of those ZIPs is corrupt, even when downloading from a different computer.
Flashing with ODIN anyway gives a FAIL result and a device that cannot boot, not even into recovery: It gives a green screen with the text: `An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.`
Ironically, the Smart Switch software just says this device is not supported. The older Kies3 software lets me enter the exact model# followed by the serial# - but then it says this device is not supported. So neither Samsung software is usable, but I can still use ODIN.
Even with the phone in this broken state, I can install TWRP again. So it is not completely bricked. I boot into TWRP and copy a LineageOS ZIP file to /sdcard, but when I try to install that, the TRWP console says: `E3004: This package is for device j5nlte,j5nltexx; this device is .` Note how it doesn't appear to recognize that this device is indeed the model j5nlte!
Android.SE says that "E3004" means my TWRP is too old, but I use `twrp-3.1.1-1-j5nlte` which is currently the newest version for this phone.
I would also like to try a factory reset, but that requires the stock recovery which won't boot (see step 2 above).
My question: How do I get out of this catch-22?
It seems that if I could just get around that E3004 then I would be fine. But I have found no ways to trick the installer into ignoring that error.
Flash an updated twrp .IMG file which you can extract from the file here j5nlte (TWRP)
Just flash the img in twrp and reboot to recovery
Then with the updated twrp try flashing the rom again
garylawwd said:
Flash an updated twrp .IMG file which you can extract from the file here
Click to expand...
Click to collapse
THANK YOU! This did the trick. May I ask: what is the origin of that TRWP image? How could I have found that on my own?
torbengb said:
THANK YOU! This did the trick. May I ask: what is the origin of that TRWP image? How could I have found that on my own?
Click to expand...
Click to collapse
No problem at all, glad all is working for you now. Happens all the time with people having the wrong recovery its no big deal but a lesson learned is always make a backup in twrp before going tinckering around with things or keep a copy of a rom, that you know works, on your SD card.
From the bootleggers pie rom thread.
The Dev of that also builds his own twrp for all j5 2015 models.
he's a really great guy to have supporting our j5 community
From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !
Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number
I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!
Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse
Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.
finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed
Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
You don’t unzip the .tar files. Keep them as is.
secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.
is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse
fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.
framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY
framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.
I can boot into Samsung recovery and can boot into Download mode. I have tried factory resetting the tablet. I have tried reflashing the stock image with Odin 3.09 in Download but everything I try just fails. It comes up with a message in stock Samsung Recovery that says:
#REboot Recovery Cause is [[check_boot_mode]RebootRecoveryWith Key]
#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
dm-verity verification failed. . .
E: Failed to clear BCB message: failed to open /dev/block/bootdevic
e/by-name/misc: No such file or directory
Could someone please help me figure out what I need to do. I am familiar with Odin for the most part. I would be FOREVER GRATEFUL! Thank you! :victory:
TWRP to save the day!
obtain stock rom and after flashing with Odin 3b patched also flash twrp and then and using either an external storage sd card or USB otg cable and a flash drive restore them twrp backup available elsewhere on the site , try use samfirm or whatever and go to android file host and search t380 and sort thru it but everything you need is there
mrstuffandthings said:
TWRP to save the day!
obtain stock rom and after flashing with Odin 3b patched also flash twrp and then and using either an external storage sd card or USB otg cable and a flash drive restore them twrp backup available elsewhere on the site , try use samfirm or whatever and go to android file host and search t380 and sort thru it but everything you need is there
Click to expand...
Click to collapse
mine also has the same problem, another problem is my OEM is locked. So I cannot install twrp.
Hello there, I`ve bought a vietnamese Samsung Galaxy Tab A 8.0 2019.
Can I flash the european Rom on it?
Is there maybe twrp to flash and perhaps Custom Rom's?
I wanna use it as a german model.
I am not an informed authority whatsoever but I did have quite a few close calls with my same device and I repeatedly managed to get it going. That must hurt to hear without a clear step by step specific with links instructions I know but let me not mislead you either. What good is that?! Well I can refer you to some of the resources I had luck with , it’s been a few years since too so I will go look and see if I have anything concrete , off the top of my head I want to say thanks to magisk the bootloader never did get unlocked , and I only ran the boot.img thru the app and then had my tarp ready to flash right after, be persistent I must have mangled and recovered over two dozen times here and there and again ambiguous encouragement empty as it is I can say from my experience that more than a few things that worked ended up being very simple but minor factors such as unchecking the auto reboot and flashing the twrp right after , another saving grace came in the form of a few die hard twrp flushable zips that enabled simple functions while in twrp bc I remember I would get as far as twrp and then loose the bootable os until I had reflashed the correct boot from inside twrp and I recall dmverity can be mitigated with a zip flashed inside twrp , now that sounds great but only just the right twrp would allow for this flashing feature at all so again hit and miss , I’ll go look at some of those files and review before I make any specific suggestions which would drive me nuts but if your lucky I was actually just noticing I still had an old custom rom that I had cooked up with one of those command line rom kitchens, so standby for real info but for now off hand …
Androidfilehost.com was a killer source of roms and where I found the working twrp
Back then samfirm was already depreciated but still worked and it was the fastest around but
Samsung firmware download - find All Official Android & Samsung Updates | updato.com
Are you looking for the official Samsung software to download? At updato.com, you'll find the latest Android device updates. Check on your own!
updato.com
Jonny boy , again knowing I don’t really know I want to say your good to go as I flashed all manner of rom from all over but I do remember something about I think the us version that seemed XAR less appealing I think bc it was a little more locked down but you would do well of course to refer to that list of the country codes for the roms obv, and as far as twrp I found mine on that android file host but on that same site was an identical looking version that once inside couldn’t flash or mount things properly , see what the trick was , was once armed with a twrp flashable zip i would wipe everything and include the dmverity disabled and whatever else , the patched boot.img And so if your careful even if you flash the wrong twrp first you can inside still flash that other one and reboot to it , my custom rom is nothing to get interested in all it were was a trimmed down stock , tho I did manage later to get some neat custom boot animations , I’ll check out my old files and return sooner this time
WARNING : I JUST COPY PASTED THIS FROM A SEARCH FOR sm-t380 on androidfilehose but it seems someone has been busy since i...
god mode?
Search Results for "sm-t380" | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
please lmk how things gel, or not
hope i was not all nonsense