Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release was Android 10-based). I have attempted to make this install as painless as possible. Please read the notes below carefully. WARNING: you are responsible for your own actions, so please be careful. If you brick something, that's on you.
Update to latest stock ROM as of 3/24/2022 (T500XXU3BVB3).
Unlock bootloader using steps described in this thread. Make sure that after your device wipes and reboots after the bootloader is unlocked that you go through the setup wizard again and back into Developer Settings and enable OEM Unlocking. I think you need to connect to wifi for this option to appear, so if you don't see it try that.
Boot to download mode, then install VBMeta Disabler via Odin.
Reboot to download mode, then install TWRP via Odin.
Reboot to download mode again, then install LineageOS via Odin.
Boot to TWRP, push "fix_brightness.sh" to the device and run it, then format data.
That should be all that is necessary. If you get stuck in a loop with TWRP where you can't boot to system (seems to happen regularly to me) I included a script in TWRP that should get you out. From the TWRP cli run the command "exit_twrp". It will say "out of space" when finished (instantly). Then reboot to system. If for some reason that still doesn't work and you boot back to TWRP, repeat.
Known Issues:
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
TWRP touchscreen seems to be unresponsive for several seconds upon first booting into TWRP. Just patiently wait a few seconds and try again.
You'll see errors in TWRP about /keyrefuge, etc. Ignore that. I believe it's related to the inability to decrypt internal storage using FBE.
Installing Gapps (Nik and Flame) doesn't work, but no worry because the ROM includes Gapps
Security: by default this ROM has root access and USB debugging (adb) is enabled unsecured. Anyone can plug into it and have full root access. So disable USB debugging if you don't want that! TWRP is the same way, though data is encrypted. Someone could install malware into your system partition though. In short, this is for hobbyists, not someone with security concerns.
Sources:
Device tree for TWRP from my Github; branch TWRP-11 specifically: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Kernel sources from Samsung: https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
Files:
LineageOS 19.1 Beta2
TWRP 3.6.1 Beta 5
VB Meta Disabler
Brightness Fix
Updates:
You can update this ROM yourself by installing a new GSI to the system partition.
Download new GSI from here onto Micro SD card: https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Boot into TWRP
Run command: blockdev --setrw /dev/block/mapper/system
Run command: dd if=/external_sd/<your_downloaded_gsi.img> of=/dev/block/mapper/system bs=1M
Wait for dd command to finish, then reboot into system. Don't forget to use "exit_twrp" command if you keep booting into TWRP.
Thanx! I must flash gsi via Odin over AP?
torekiki said:
Thanx! I must flash gsi via Odin over AP?
Click to expand...
Click to collapse
If by GSI you mean the Lineage .tar file I linked to, then yes. That particular file is more than a GSI, it is a super partition including the GSI, vendor, product, and odm partitions. Flash this via Odin to AP and in the future you can install standalone GSIs of Lineage using TWRP with the instructions at the bottom of the post.
After formatting data, tablet just keeps booting to TWRP. Won't boot to system.
lewmur said:
After formatting data, tablet just keeps booting to TWRP. Won't boot to system.
Click to expand...
Click to collapse
Read the op. I specifically address this.
Hi thanks for all your work. Question , I do step 3 successfully and it boots to OS, but step 4 when I try to install TWRP it fails and when trying to boot I get error "Only official released binaries are allowed to be flashed(vbmeta)" and I need to reinstall stock OS for it to boot again. Any Suggestions what I may be missing or doing wrong?
hakkers420 said:
Hi thanks for all your work. Question , I do step 3 successfully and it boots to OS, but step 4 when I try to install TWRP it fails and when trying to boot I get error "Only official released binaries are allowed to be flashed(vbmeta)" and I need to reinstall stock OS for it to boot again. Any Suggestions what I may be missing or doing wrong?
Click to expand...
Click to collapse
When you do step 3 and boot to the os make sure you verify that bootloader unlock is still enabled in Developer Options. If it is, I suggest reinstalling stock and then starting over.
agreenbhm said:
When you do step 3 and boot to the os make sure you verify that bootloader unlock is still enabled in Developer Options. If it is, I suggest reinstalling stock and then starting over.
Click to expand...
Click to collapse
When I check OEM Unlock it's selected to ON its 'greyed out' bootloader is already unlocked.
hakkers420 said:
When I check OEM Unlock it's selected to ON its 'greyed out' bootloader is already unlocked.
Click to expand...
Click to collapse
Good, that's what it should be. Try reflashing the vbmeta disabler again and then flashing TWRP.
agreenbhm said:
Good, that's what it should be. Try reflashing the vbmeta disabler again and then flashing TWRP.
Click to expand...
Click to collapse
So I tried that but it fails in Odin.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 0 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> vbmeta.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hakkers420 said:
So I tried that but it fails in Odin.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 0 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> vbmeta.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I know I ran into this once the past few days but am having difficulty remembering exactly how I resolved it. I think your best bet is to start from scratch, reinstalling stock and doing a factory reset.
agreenbhm said:
I know I ran into this once the past few days but am having difficulty remembering exactly how I resolved it. I think your best bet is to start from scratch, reinstalling stock and doing a factory reset.
Click to expand...
Click to collapse
Thanks will give it another shot see what happens.
On the page for unlocking bootloader that you provided are you supposed to do all 7 steps or can I just do up to step 3 and not worry about 4-7?
hakkers420 said:
On the page for unlocking bootloader that you provided are you supposed to do all 7 steps or can I just do up to step 3 and not worry about 4-7?
Click to expand...
Click to collapse
Correct, you can stop after 3.
Figured it out, before step 4 boot to OS and reenable developer options and USB Debugging.
agreenbhm said:
Correct, you can stop after 3.
Click to expand...
Click to collapse
Now step 6 when trying to boot to TWRP it boots to the stock recovery for some reason. I think I may have to take a break for a bit.
edit: after a break and a reinstall of twrp all seems to be good now
agreenbhm said:
If by GSI you mean the Lineage .tar file I linked to, then yes. That particular file is more than a GSI, it is a super partition including the GSI, vendor, product, and odm partitions. Flash this via Odin to AP and in the future you can install standalone GSIs of Lineage using TWRP with the instructions at the bottom of the post.
Click to expand...
Click to collapse
I am a huge fan of GSI but doesnt realy understand what it is and how to use it ( this isnt my first account just forget my pw XD) so it would be a pleasure for me if you would write a few words about it thanks in advantage :_)
agreenbhm said:
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release was Android 10-based). I have attempted to make this install as painless as possible. Please read the notes below carefully. WARNING: you are responsible for your own actions, so please be careful. If you brick something, that's on you.
Update to latest stock ROM as of 3/24/2022 (T500XXU3BVB3).
Unlock bootloader using steps described in this thread. Make sure that after your device wipes and reboots after the bootloader is unlocked that you go through the setup wizard again and back into Developer Settings and enable OEM Unlocking. I think you need to connect to wifi for this option to appear, so if you don't see it try that.
Boot to download mode, then install VBMeta Disabler via Odin.
Reboot to download mode, then install TWRP via Odin.
Reboot to download mode again, then install LineageOS via Odin.
Boot to TWRP, push "fix_brightness.sh" to the device and run it, then format data.
That should be all that is necessary. If you get stuck in a loop with TWRP where you can't boot to system (seems to happen regularly to me) I included a script in TWRP that should get you out. From the TWRP cli run the command "exit_twrp". It will say "out of space" when finished (instantly). Then reboot to system. If for some reason that still doesn't work and you boot back to TWRP, repeat.
Known Issues:
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
TWRP touchscreen seems to be unresponsive for several seconds upon first booting into TWRP. Just patiently wait a few seconds and try again.
You'll see errors in TWRP about /keyrefuge, etc. Ignore that. I believe it's related to the inability to decrypt internal storage using FBE.
Installing Gapps (Nik and Flame) doesn't work, but no worry because the ROM includes Gapps
Security: by default this ROM has root access and USB debugging (adb) is enabled unsecured. Anyone can plug into it and have full root access. So disable USB debugging if you don't want that! TWRP is the same way, though data is encrypted. Someone could install malware into your system partition though. In short, this is for hobbyists, not someone with security concerns.
Sources:
Device tree for TWRP from my Github; branch TWRP-11 specifically: https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Kernel sources from Samsung: https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
Files:
LineageOS 19.1 Beta2
TWRP 3.6.1 Beta 5
VB Meta Disabler
Brightness Fix
Updates:
You can update this ROM yourself by installing a new GSI to the system partition.
Download new GSI from here onto Micro SD card: https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Boot into TWRP
Run command: blockdev --setrw /dev/block/mapper/system
Run command: dd if=/external_sd/<your_downloaded_gsi.img> of=/dev/block/mapper/system bs=1M
Wait for dd command to finish, then reboot into system. Don't forget to use "exit_twrp" command if you keep booting into TWRP.
Click to expand...
Click to collapse
thank you you did a amazing work
Noskilldode said:
I am a huge fan of GSI but doesnt realy understand what it is and how to use it ( this isnt my first account just forget my pw XD) so it would be a pleasure for me if you would write a few words about it thanks in advantage :_)
Click to expand...
Click to collapse
In short, a GSI is a special type of system image that is made to work across multiple devices. It stands for generic system image. The ROM that I included in the op is a super image which contains not only the system partition but also the vendor partition, which includes device specific drivers and things like that, plus a couple other partitions.
What is the syntax to push the fix_brightness file? I have it on the extternal SD card. Can I just copy to a directory on the internal SD?
Related
I have a German S6 Galaxy Edge G925F. I rooted it early on with Kingroot, which (I gather) blocked me from receiving OTA updates from my provider. So I was stuck at 5.0.2. I've flashed custom ROMs on all my previous android devices, so this morning I thought I'd try flashing XtreStoLite as a way of getting to 5.1.1, and a nicer 5.1.1 at that! I used the directions at http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467 . I made a stupid mistake though, and started the update before reading ALL the instructions ALL the way through.
Now I can get into Download mode, but otherwise I'm stuck at the initial "samsung galaxy s6 edge powered by android" boot screen, with red text at the top:
Code:
KERNEL IS NOT SEANDROID ENFORCING
SYSTEM REV. CHECK FAIL. DEVICE: 2, BINARY: 1
I'm on a Mac, and since JOdin can't seem to read PIT files anymore I'm using pure heimdall command line. So here's what I did:
1) Downloaded G925F-XXU2BOGG-BOOTLOADER.tar from the above thread, and flashed the contained 5.1.1 cm.bin and sboot.bin. (
Code:
heimdall flash --no-reboot --80 sboot.bin --90 cm.bin
)
2) Immediately found myself unable to boot. Worried I had already ****ed up, I did not flash the modem (since that's the part that REALLY can't go back AFAIK)
3) Flashed TWRP linked from http://zidroid.com/how-to-install-twrp-root-galaxy-s6-edge-on-android-5-1-1/ . (
Code:
heimdall flash --no-reboot --6 recovery.img
).
Still couldn't boot into recovery.
4) Flashed a 5.1.1 kernel to see if that would help me boot: S6_UniKernel_v8-0002-ODIN from http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395 .
Now I'm stuck. I can't get into recovery mode to flash the actual rom, and my 5.0.2 OS doesn't match my 5.1.1 bootloader or kernel. If I could flash a 5.1.1 OS from heimdall that would be my next step, but I can't find one to use, and I'm not sure which partition(s) it would go to anyway.
On the download mode screen I see
Code:
ODIN MODE
PRODUCT NAME: SM-G925F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0304)
AP SWREV: B: 2 K:2 S:2
Please help! How I can get to recovery mode from here?
I dusted off an old Windows machine and fired it up, just to use ODIN. Found a vanilla 5.1.1 ROM for ODIN, and installed it from there... and it worked perfectly!
I don't understand why so many ROMs exist for odin, but no one packages for Heimdall. Heimdall seems much more reliable, and it's cross platform! Plus, we actually know what it's doing... /rant
Anyway, for whatever unlucky soul finds this... Flashing 5.1.1 via ODIN involved overwriting boot.img, cache.img, recovery.img, system.img, and modem.bin . Of course that's just one step for ODIN, you get a single .tar.md5 file, press the "AP" button to load it in, and it flashes those files to the right partitions in sequence.
So unless you have all of those files, I guess you can't do an update with Heimdall. You actually NEED a windows device.
ohthehugemanatee said:
I dusted off an old Windows machine and fired it up, just to use ODIN. Found a vanilla 5.1.1 ROM for ODIN, and installed it from there... and it worked perfectly!
I don't understand why so many ROMs exist for odin, but no one packages for Heimdall. Heimdall seems much more reliable, and it's cross platform! Plus, we actually know what it's doing... /rant
Anyway, for whatever unlucky soul finds this... Flashing 5.1.1 via ODIN involved overwriting boot.img, cache.img, recovery.img, system.img, and modem.bin . Of course that's just one step for ODIN, you get a single .tar.md5 file, press the "AP" button to load it in, and it flashes those files to the right partitions in sequence.
So unless you have all of those files, I guess you can't do an update with Heimdall. You actually NEED a windows device.
Click to expand...
Click to collapse
hi there i did the same thing as the op and my situation is identical but i am using windows so could you please help me because i am stuck now.
Just flash a custom recovery, boot into recovery, wipe everything then flash the custom rom. Pretty simple stuff no rocket science involved
Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 05/01/2019
TWRP 3.2.3-1 OO build released.
Current status: Beta
Update 02/02/2017
TWRP 3.2.1-1 NN build released.
Current status: Stable
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN
As soon as the screen goes blank change to POWER + HOME + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
Do NOT boot the OS, move on to the root instructions below.
NOTE: ON ANDROID 5.1.1+ DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
Oreo/Pie:
TWRP_3.2.3-1_sm-t380_4119
TWRP_3.2.3-1_sm-t385_5119
Nougat:
TWRP_3.2.1-1_sm-t380_15118
To Root:
Download the latest Magisk release:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
1. Boot to Twrp
2. Format the Data partition (NOT WIPE) using the FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check /DATA is mountable.
4. Install Magisk
OREO/PIE ONLY:
5. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
6. Reboot
Kernel source T380DXU2BRK3: : https://opensource.samsung.com/uploadSearch?searchValue=sm-t380
TWRP recovery source: https://github.com/omnirom/android_bootable_recovery
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Here is a question
Should I do it in TWRP?
https://forum.xda-developers.com/showpost.php?p=75542737&postcount=35
mingkee said:
Here is a question
Should I do it in TWRP?
https://forum.xda-developers.com/showpost.php?p=75542737&postcount=35
Click to expand...
Click to collapse
Please do not quote the entire OP.
Please remove the quote.
I take it you are referring to the modifications?
It doesn't matter how you do it as long as you do it before reboot.
ashyx said:
Please do not quote the entire OP.
Please remove the quote.
I take it you are referring to the modifications?
It doesn't matter how you do it as long as you do it before reboot.
Click to expand...
Click to collapse
Sorry for that.
It's browser problem which doesn't let me post without quoting
Firefox for Android.
Thanks for your recovery.
Mine finally rooted.
help me
help please, I can not install the twrp, odin tells me that everything is ok, and when I run the recovery it appears no command, my tablet is sm t380
aquamoon1 said:
help please, I can not install the twrp, odin tells me that everything is ok, and when I run the recovery it appears no command, my tablet is sm t380
Click to expand...
Click to collapse
Did you see any error on the unit?
If it is a new machine, you have to wait 7 days for OEM Unlock in Developers Option shows up.
mingkee said:
Did you see any error on the unit?
If it is a new machine, you have to wait 7 days for OEM Unlock in Developers Option shows up.
Click to expand...
Click to collapse
No error and have 1 month with OEM unlocked
aquamoon1 said:
help please, I can not install the twrp, odin tells me that everything is ok, and when I run the recovery it appears no command, my tablet is sm t380
Click to expand...
Click to collapse
You didn't follow the instructions in the OP. You have booted to stock recovery.
There's a minor mistake to enter TWRP.
After flashing TWRP in Download mode, press and hold Volume Down and Power buttons, and as soon as the screen goes blank, press Volume Up + Power + Home buttons until you see "entering recovery"
TWRP intstalled OK and Data partition formatted as instructed. SuperSU and boot image patch zips installed, rebooted and after two auto reboots the tablet powers down and is unresponsive. Can still manually boot to TWRP. ?? Any hints??
Thanks for the guide, seems to have worked fine. Have TWRP, Root, Magisk on my Tab A T385 after following all the guides on this forum.
Impossible. ALL THE GUIDES? There are so many errors and omissions in THIS guide, it's impossible that you could have successfully completed root by following it. I, too, researched other posts on other guides. Perhaps I missed something. It would be good to clean up THIS guide so others don't have to do it.
NavyDave49 said:
Impossible. ALL THE GUIDES? There are so many errors and omissions in THIS guide, it's impossible that you could have successfully completed root by following it. I, too, researched other posts on other guides. Perhaps I missed something. It would be good to clean up THIS guide so others don't have to do it.
Click to expand...
Click to collapse
Maybe you shouldn't be attempting to root your device if you are incapable of following instructions that every one else seems to manage with just fine.
I suggest you try www.spoonfeeders.com.
Didn't work for me. Tab SM-T380. Using Odin3 v3.11. OEM unlock is checked and running Build RB3. USB debugging is check too if that matters in download mode.
Do I need to flash back to stock firmware first? I don't think I read that I need to flash stock first, just that you said I should download it in case of a soft brick. Or do you think it might be my Odin ver. Honestly I don't know, every time I've done this on previous devises it worked, so not sure where to go from here.
My Tab says "Only official released binaries are allowed to be flashed"
Odin says...
Code:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Chrisrobbins30 said:
Didn't work for me. Tab SM-T380. Using Odin3 v3.11. OEM unlock is checked and running Build RB3. USB debugging is check too if that matters in download mode.
Do I need to flash back to stock firmware first? I don't think I read that I need to flash stock first, just that you said I should download it in case of a soft brick. Or do you think it might be my Odin ver. Honestly I don't know, every time I've done this on previous devises it worked, so not sure where to go from here.
My Tab says "Only official released binaries are allowed to be flashed"
Odin says...
Click to expand...
Click to collapse
Check for RMM state in Odin mode.
ashyx said:
Check for RMM state in Odin mode.
Click to expand...
Click to collapse
As I was trying to find out what you where talking about. I discovered you where referring to a line of txt in download mode. So I went back to download mode to check. I didn't see the RMM line though. But I thought maybe I have to try to flash again to get that line. But oddly this time it passed. Crazy right? thx for the help tho...
It's amazing that even Samsung's tablets are getting TWRP, even if they might not be as glorious as their phones.
Speaking of which, will TWRP 3.2.0 ever be able to support the older (and weaker) model of this device called an SM-T350? I'm out to build Android Oreo for those old tablets from three years ago and 3.1.1 does not seem to know what an Oreo is.
Sent from my OnePlus 3T using XDA Labs
I'm in TWRP but when I try to boot to system I get suck in a boot loop. I think maybe I f**ked up. I forgot to put SU on my SD card and I wanted to do a backup before I booted to system. It wouldn't let me. So I tried wiping and it wouldn't let me do that. So I skipped a step and used the format option. That worked and then I made a backup, but it said something about reloading the data. Then I tried rebooting to system and got the boot loop. I can still get in TWRP but can't get boot system. Do I need to start over? Reflash stock and stuff or am I missing something?
Edit: False alarm again, damn what the hell eveything wants to take 2 tries first. I'm good to go now.
Newbs, if you're having trouble flashing TWRP to your Smasung Galaxy A T380 (2017) and you're having no luck following several different ROOT or TWRP tutorials on here, try a different button combination. I tried over 15 times with existing tutorial combinations (including this one) and they were not right for my device - which is a week old.
Note: after unlocking developer options in Settings, you will have to wait 7 days for OEM unlock to show up in your settings... so turn that and USB Debugging on. But if you boot to download mode in the meantime you may be able to do it anyway on the T380 (thanks to ashyx for pointing this out) - OEM lock was showing as "OFF" the day I got it - I just couldn't get the flash button combos right! If not, then wait the 7 days for the option to show up.
I used ODIN 3.12.5. Uncheck auto-boot (you will find it in the "Options" tab of Odin)
Load up the TWRP file provided in this tutorial in the AP slot.
To put your device into download mode, turn it of, then hold: Power + Volume Down + Home (not what is said in this tutorial)
Flash, then once you get your success message/"PASS" message - here's the important bit that's different from this tutorial and others I've seen. To get out of DL mode, hold Power + Volume Down + HOME (HOME is the additional step that has been missing)
As soon as the screen goes blank, switch to Power + Volume Up + HOME. You should boot straight to TWRP then... and follow the rest of ashyx tutorial for root & installing the encrypt patch.
I don't know why this was different from this tutorial, or others I've seen.... but it was. And I was killing myself using the other button combos with no success (either straight back to ordinary boot following this tutorial steps, or hitting error following suggested Power + Volume Down to ext DL, then Power + Volume Up + Home to boot to recovery in a root tutorial or two).
TL;DR version if hitting problems - use the HOME BUTTON AS WELL on BOTH the suggested steps in the OP's tutorial after flashing.
Hi! I found a way, to install J730FM official stock Oreo ROM, on J730F.
Everything working fine. Sorry for my little bit bad english.
Code:
I am not responsible for bricked devices and other things, created after using this flahing method.
a) Flash Oreo 8.1.0 (SER) stock ROM using Odin, without bootloader file, but use PIT file from attached files.
- https://www.sammobile.com/firmwares/galaxy-j7/SM-J730FM/SER/download/J730FMXXU4BRI3/234618/
- View attachment J7Y17LTE_EUR_OPEN.zip
b) In the end of flashing, you get a error with radio (or something similar). Just unplug USB cable, and turn off the phone using combination buttons (VOL- + POW) - press both for many seconds. Now turn the device into download mode once time more.
b) Flash custom recovery using odin. Recommended a Mohi's1117 TWRP from link below.
https://forum.xda-developers.com/galaxy-j7-2017/development/recovery-t-r-p-3-2-1-0-t3751717
c) Okay. After flashing, just restart phone, and let boot to system. Everything should working. If not, just flash ROM from link below, and try everything from this tutorial again.
https://forum.xda-developers.com/galaxy-j7-2017/development/rom-j5-pro-rom-j730xx-t3838073
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
?
EyuphanKundakci said:
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
?
Click to expand...
Click to collapse
You miss PIT file. Just make every steps from tutorial.
Steku1997 said:
You miss PIT file. Just make every steps from tutorial.
Click to expand...
Click to collapse
I placed odin pit file but same error.
EyuphanKundakci said:
I placed odin pit file but same error.
Click to expand...
Click to collapse
What showing your J7 screen?
Steku1997 said:
What showing your J7 screen?
Click to expand...
Click to collapse
Red text: SECURE CHECK FAIL : (PIT)
This pit file for nougat?
EyuphanKundakci said:
Red text: SECURE CHECK FAIL : (PIT)
This pit file for nougat?
Click to expand...
Click to collapse
For all. Nougat and Oreo. Try to use other version of Odin.
Steku1997 said:
For all. Nougat and Oreo. Try to use other version of Odin.
Click to expand...
Click to collapse
I try odin3 v3.13 now: SECURE CHECK FAIL : (BOOTLOADER)
EyuphanKundakci said:
I try odin3 v3.13 now: SECURE CHECK FAIL : (BOOTLOADER)
Click to expand...
Click to collapse
Uncheck BL option in location with bootloader. Or don't select a BL software file.
I am installed but my screen is fake amoled screen touch screen is not working ((((((((((((((((((
EyuphanKundakci said:
I am installed but my screen is fake amoled screen touch screen is not working ((((((((((((((((((
Click to expand...
Click to collapse
So, then try last step. And remember, this tutorial is only for J730F/DS.
Are you sure it's ok to flash FM on F?
ion1s said:
Are you sure it's ok to flash FM on F?
Click to expand...
Click to collapse
Yes, i'm trying. Actually i'm using this ROM on my phone. Working pretty good.
does someone have the oreo firmware somewhere else than sammobile ? it's terribly slow !
imaGine00 said:
does someone have the oreo firmware somewhere else than sammobile ? it's terribly slow !
Click to expand...
Click to collapse
https://drive.google.com/file/d/172lo5GTJ5oHf9V9HieoxEvM9nryTsyYR/view
Thanks, ezer90!
Steku1997 said:
So, then try last step. And remember, this tutorial is only for J730F/DS.
Click to expand...
Click to collapse
I tried other 8.1 rom but same problem My touch screen is not answering. Because amoled screen is fake. WTF SAMSUNG????
Ok, I confirm this guide is good. I already flashed it, without radio error or something *I flashed only AP and CSC.
need a root for this?
Easy way to get pit file for J7 pro
Steku1997 said:
For all. Nougat and Oreo. Try to use other version of Odin.
Click to expand...
Click to collapse
here is the simple way to get pit file ( i have also got) from firmware package
1) extract firmware package
2) find package with name " CSC_ODD_J730GMODD3ARF3_CL13775238_QB18498802_REV00_user_low_ship.tar.md5"
3) rename it CSC.tar
4) extract it and you will get pit fine inside the package
WAVESKLR said:
need a root for this?
Click to expand...
Click to collapse
Nope.
Hello,
First time posting so please let me know if you need more info.
SM-G935A
AT&T
8.0.0 Oreo
Samsung Experience 9.0
I am currently trying to root my AT&T Samsung Galaxy S7 Edge SM-G935A
I've tried multiple tutorials:
https://forum.xda-developers.com/verizon-s7-edge/development/easyroot-unroot-t3859762
https://www.smartphoneclinics.com/easy-root-samsung-att-galaxy-s7-edge-sm-g935a-sm-g930a/
i have followed many tutorials about using the Princes modified Odin to transfer an Engineer image to achieve root but anytime I attempt to flash any of the files i've found in tutuorials i receive an error.
Odin tells me :
<ID:1/010> Added!!
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:1/010> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:1/010> File analysis..
<ID:0/009> SetupConnection..
<ID:1/010> SetupConnection..
<ID:1/010> Initialzation..
<ID:1/010> Get PIT for mapping..
<ID:1/010> Firmware update start..
<ID:1/010> SingleDownload.
<ID:1/010> boot.img
<ID:1/010> RQT_CLOSE !!
<ID:1/010>
<ID:1/010> Complete(Write) operation failed.
And on my odin screen on my s7 it displays
ODIN MODE (HIGH SPEED)
PRODUCT NAME : SM-G935A
CURRENT BINARY : SAMSUNG OFFICIAL
SYSTEM STATUS : OFFICIAL
FRP LOCK : OFF
WARRANTY VOID : 0x0
QUALCOMM SECUREBOOT : ENABLE
RP SWREV B9(2, 1.1.1.1) K9 S9
SECURE DOWNLOAD : ENABLE
SW REV CHECK FAIL : [boot]Fused 9 > Binary 1
What i've been lead to believe is that this means I am attempting to flash a version that is currently lower than my current FW. Yet all I am attempting to do is gain root access and this is supposed to be universal on any SM-G935A device. What is the cause of this? How can I gain root access?
I was considering flashing the SM-G935U to see if I am able to flash a root easier.
What should I do??
Right along with you...
Did you ever find out how to get this to work?
I was trying flash a root version. The tutorial I was using had me flashing G935U firmware but same as you I got a "Complete(WRITE) operation failed" error.
Soo I went to samsungs website and asked their Support chat for a link to the OFFICIAL RECOVERY.
But here my deal... (And im sorry in advance for bothering you with this) Since I tried flashing the "U" firmware it erased what existed on the phone..... So Im more than positive that the "Allow OEM Unlock" is no longer enabled. Whats more is even before I tried flashing the "U" firmware I recall seeing that "NO RECOVERY WAS FOUND" in the Recovery mode
So its looking for a file that couldnt be found before hand and now im unable to boot into the phone at all since Im stuck in a loop....
Anyways... Were you able to figure it out and get your phone working again properly? There's so much information out there and so many files and versions ... I just get lost....
Bottom line... Ya get it fixed? If so how? THANKS
I have rooted the Samsung Galaxy S7 Edge G935P on binary 5 using our Team's root (Team UAT) however it is only a repair root and not a full on user root. Meant for obtaining root to work on the S7 with repairs that require root.
Hi folks,
I had opened the bootloader for this device, the TRWP is starting fine. The partitions: product, boot and vendor is not modified, only the vbmeta has been changed, and also the recovery and the system.
I'm used the system file: lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img
The file I'll has flash with the command: heimdall flash --SYSTEM lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img, the flashing was successfully.
The SMA105 is booting, but after 10 minutes, the phone is stucking in the same boot logo. Nothing is happend, no steps for terminating the system installation. It seams, the SMA105 waiting for an command. But, I can not read an log file for the booting or switching of temporally the bootlogo.
Any solutions for me?
Greetings tiptel170
P.S.
Flashing other roms for example Viper etc ... This is the same effect. Wateing and wateing ...
renaming the file "bootaniamation.zip" in the folder /system/media was not successful. Because, it turns the animation on with the word "ANDROID". And the adb logcat, the same it will not working.
I'll has changed the file default.prop
Code:
ro.adb.secure=0
persist.sys.usb.config=mtp,adb
ro.secure=0
Thanks...
Edit:
On the SM-T813 I'll had the same problem, but I could resolved with the "heimdall print-pit". And the tablett reboot normaly. But I use the same command on the A10, nothing has been changed, the same result with the booting.
I did the same haha. It shows android but it booted
tiptel170 said:
Hi folks,
I had opened the bootloader for this device, the TRWP is starting fine. The partitions: product, boot and vendor is not modified, only the vbmeta has been changed, and also the recovery and the system.
I'm used the system file: lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img
The file I'll has flash with the command: heimdall flash --SYSTEM lineage-17.1-20200402-UNOFFICIAL-treble_a64_bvN.img, the flashing was successfully.
The SMA105 is booting, but after 10 minutes, the phone is stucking in the same boot logo. Nothing is happend, no steps for terminating the system installation. It seams, the SMA105 waiting for an command. But, I can not read an log file for the booting or switching of temporally the bootlogo.
Any solutions for me?
Greetings tiptel170
P.S.
Flashing other roms for example Viper etc ... This is the same effect. Wateing and wateing ...
Click to expand...
Click to collapse
Samsung Galaxy A10 has Lineage 17.1 custom rom (arm and arm64 versions)
You can download them here:
arm version
arm64 version
Note:
-> They will boot only with permissive selinux kernels (here)
-> It's a rom, not a gsi. It has it's own vendor.
-> You just need to flash the rom in recovery (twrp) , and then flash the permissive kernel.
Hello Chatur27,
I 'll had installed the system and the kernel. This is the same effect, stucks on booting. Then I 'll changed form arm to arm64 with the same kernel, it's the same result. And I used the twrp. And waiting more then 10min for the finish up the booting.
tiptel170 said:
Hello Chatur27,
I 'll had installed the system and the kernel. This is the same effect, stucks on booting. Then I 'll changed form arm to arm64 with the same kernel, it's the same result. And I used the twrp. And waiting more then 10min for the finish up the booting.
Click to expand...
Click to collapse
I will suggest you to stick to stock rom if you are not able to install a rom
Cheers!
I'm able to install roms on the Samsung phones / tablets. Something is missing, but it will not continua. And on this phone is not an stock rom installed, it's empty. I think I will be back to the stock rom and then reinstall the LOS 17. May be I' ll erased an part for booting. ;-)
Cheers.
Update:
I 'll had downloaded the firmware for this phone, then I extracted the packages in to the /tmp directory:
Code:
BL_A105FNXXU6BUC3_CL20057335_QB39107009_REV00_user_low_ship.tar
cm.bin.lz4
param.lz4
sboot.bin.lz4
And
Code:
CP_A105FNXXU6BUC3_CP18543320_CL20057335_QB39107009_REV00_user_low_ship.tar
modem.bin.lz4
Decompress the lz4 files:
Code:
cd /tmp
for lz4 in `ls *.lz4`; do unlz4 $lz4; done
Boot in to the download-modus and than I had flashed with heimdall
Code:
heimdall flash --CM cm.bin --PARAM param.bin --SBOOT sboot.bin --RADIO modem.bin
The RADIO partition is very important, if is not installed your SIM-Card wil not be detected and the mobil network will not work!
Reboot to the download-modus
And finally I had installed the twrp-3.5.2_9-0-a10.img.tar and vbmeta_disabled.tar:
Code:
heimdall flash --RECOVERY recovery.img --VBMETA vbmeta.img
Reboot again in this case in to the recovery mode:
Wipe
Code:
data
cache
And install this:
Code:
lineage-17.1-20200921-UNOFFICIAL-a10.zip
open-gapps
magisk-amager 20.4
And the phone will be start up normaly.
This system with this version works well, but:
- The battery runs out very fast - in an day is the battery at 9%
- Open files with WhatsApp, K9-Mail or simelar dose not work: The dialog open with an APP will be open very sohrt and cloed quickly, by WhatsApp crashed the window and restart the Whatsapp.
And this version of the lineage OS lineage-17.1-20210221-UNOFFICIAL-a10.zip
- Crashed the grafics, the screen goes withe, and then I need make an hard reset.
Need help for resolver the problem.
Thanks, tiptel170