Installed TWRP twrp-3.1.0-1-lt02ltetmo.img on Samsung Galaxy Tab 3 SM-T217S using Heimdall 1.4.0. Eventually will install LineageOS but as a first step wanted to successfully install TWRP. Have zero experience with all this besides occasional casual usage on an old tablet with the stock KitKat install.
First thing to note to anyone else trying to install a ROM on a Samsung Glaxy Tab 3 SM-T217S. twrp-3.1.0-1-lt02ltetmo.img works. twrp-3.1.1-0-lt02ltetmo.img causes an endless reboot. If accidentally install twrp-3.1.1-0-lt02ltetmo.img use Heimdall to install twrp-3.1.0-1-lt02ltetmo.img.
So TWRP installed okay. Now the device boots into TWRP. How can TWRP be set to boot back "into" the KitKat Android that is currently installed? LUKS encryption (or whatever LUKS/dm-crypt derivative Android uses) is used but assume this shouldn't be an issue since /boot ins't encrypted with LUKS/dm-crypt.
Decided to forget trying to boot old rom and install LineageOS. Assumed (wrongly, maybe?) that TWRP was a bootloader like grub that could easily load standard rom with LUKS/dm-crypt.
Couldn't use TWRP to wipe /data or other partitions due to encryption. TWRP can however just reformat which worked. Than used "adb sideload" to install LineageOS and OpenGApps. About OpenGApps. Used the "aroma" variant which allows choice of which apps to install. The touch screen and home/ back buttons do not work for proceeding with the OpenGApps install. Have to kinda use the volume and power buttons to make and select options during the install. Never really figured out how to make choices so just installed the "pico" (minimal) variant of OpenGApps which installed fine.
Installing LineageOS was absolutely worth it to anyone else thinking about doing so.
Related
I have a Sprint Galaxy Note 3.
As of yesterday it was functioning perfectly with a rooted stock Android 5.0 I tried to put a custom rom on it so I could use xposed and it has been borked ever since, I will list the steps I took and everything I've tried and their results below:
(I did full wipes in between each different flash)
1. Flashed TWRP with Odin (worked)
2. Flashed CyanogenMod with TWRP (worked)
3. Booted into CM to discover I could not get any data connection (could still make calls)
3. Booted to TWRP and flashed DarkLord rom (said there were errors [writing symlinks], caused boot loop)
4. Tried step 3 with Norma rom, CivZ rom, and a Stock Rooted rom (all same results of boot loop)
5. Booted to download mode and tried to flash samsung stock kitkat (just said failed)
6. Booted to download mode and tried to flash samsung stock lolipop (failed)
7. Booted back to TWRP and flashed CM again (this time not only no data, but no calls either)
Seems like maybe one of the issues may be the abundance of region codes and whatnot for all of these roms (including samsung official) and none of them seem to be for USA.
Does anyone have any suggestions or help to offer that I haven't already tried? I don't care what the rom is at this point, I just need a working phone that makes calls and has data as I'm out of town away from family and need to be in touch.
That said, obviously my preference would be to have a rooted KitKat rom so I can install xposed, or a rooted lolipop that isn't a samsung ART (for the same reason), but I'll genuinely be happy with anything that works.
I could be wrong, but is it maybe best to stick with CM simply because it's the only thing that will boot right now? If so how would I go about solving the non existence of a network connection.
I am also using Ting as a provider and they hop off Sprint networks. I had full bars of signal in this location the entire time when I was stock. Thanks in advance!
HunterNIU said:
I have a Sprint Galaxy Note 3.
As of yesterday it was functioning perfectly with a rooted stock Android 5.0 I tried to put a custom rom on it so I could use xposed and it has been borked ever since, I will list the steps I took and everything I've tried and their results below:
(I did full wipes in between each different flash)
1. Flashed TWRP with Odin (worked)
2. Flashed CyanogenMod with TWRP (worked)
3. Booted into CM to discover I could not get any data connection (could still make calls)
3. Booted to TWRP and flashed DarkLord rom (said there were errors, caused boot loop)
4. Tried step 3 with Norma rom, CivZ rom, and a Stock Rooted rom (all same results of boot loop)
5. Booted to download mode and tried to flash samsung stock kitkat (just said failed)
6. Booted to download mode and tried to flash samsung stock lolipop (failed)
7. Booted back to TWRP and flashed CM again (this time not only no data, but no calls either)
Seems like maybe one of the issues may be the abundance of region codes and whatnot for all of these roms (including samsung official) and none of them seem to be for USA.
Does anyone have any suggestions or help to offer that I haven't already tried? I don't care what the rom is at this point, I just need a working phone that makes calls and has data as I'm out of town away from family and need to be in touch.
That said, obviously my preference would be to have a rooted KitKat rom so I can install xposed, or a rooted lolipop that isn't a samsung ART (for the same reason), but I'll genuinely be happy with anything that works.
I could be wrong, but is it maybe best to stick with CM simply because it's the only thing that will boot right now? If so how would I go about solving the non existence of a network connection.
I am also using Ting as a provider and they hop off Sprint networks. I had full bars of signal in this location the entire time when I was stock. Thanks in advance!
Click to expand...
Click to collapse
1. Power off your phone completely
2. Boot into download mode (power + volume down button - then press volume up button to get into download)
3. Use Odin to flash this, which is the tar for OC5 - http://forum.xda-developers.com/note-3-sprint/development/romodin-t3095540
4. Reboot into STOCK recovery and factory default reset. If you skip this step, you will have issues
5. Once booted into OS, power off again and re-do step # 2 to get into download mode
6. Use Odin to flash TWRP
7. Once complete, immediately reboot into TWRP, or you will be dumped into stock recovery next time you try to get into recovery. I've done it this way since MJ4 and never had an issue.
8. Wipe everything including internal storage - NOT your external SD
9. Install ROM of your choice; I would recommend this one which is deodex and will allow you to install Xposed - http://forum.xda-developers.com/note-3-sprint/development/rom-t3132662
10. Profit
Good luck!
rpenrod23 said:
1. Power off your phone completely
2. Boot into download mode (power + volume down button - then press volume up button to get into download)
3. Use Odin to flash this, which is the tar for OC5 - http://forum.xda-developers.com/note-3-sprint/development/romodin-t3095540
4. Reboot into STOCK recovery and factory default reset. If you skip this step, you will have issues
5. Once booted into OS, power off again and re-do step # 2 to get into download mode
6. Use Odin to flash TWRP
7. Once complete, immediately reboot into TWRP, or you will be dumped into stock recovery next time you try to get into recovery. I've done it this way since MJ4 and never had an issue.
8. Wipe everything including internal storage - NOT your external SD
9. Install ROM of your choice; I would recommend this one which is deodex and will allow you to install Xposed - http://forum.xda-developers.com/note-3-sprint/development/rom-t3132662
10. Profit
Good luck!
Click to expand...
Click to collapse
Thank you so much for such a quick response! I'm downloading the file now and will be trying this as soon as it's completed. Also the rom you recommended was one I tried that failed, but hopefully with your extra steps it will work because it looks exactly like what I'm looking for.
UPDATE:
That worked fantastic @rpenrod23 thank you so much! Where is your donate button?
Hi everyone,
I have a problem with my phone. Android 7.1.2 (Lineage OS 14.1) is installed in the GS4, and it worked perfectly. The recovery is TWRP. Yesterday, the Lineage OS developers released a system update, so I downloaded it from the phone settings and then tapped on the icon to install it. Then it booted into recovery and I installed the file downloaded (the auto-installation does not work for me). So, when it finished installing the new version, I rebooted the phone and... it was stuck at the Galaxy S4 boot logo. Hence, I rebooted it to see if ti worked but nothing, so I decided to go again into recovery ad perform a full wipe and a clean installation. Rebooted the phone but it continues to stuck at the logo. I also tried to install a previous version of android, which I am sure it works (because it was the first I installed), but the situation doesn't change. I also tried to get into downloading mode, and it goes, so I used a tool called FonePaw Data Recovery to try to fix the problem but it doesn't change. I also installed a different version of TWRP via Odin, but the system won't boot.
So, in conclusion, the phone is able to boot properly into recovery mode and downloading mode but not able to boot system. What can I do now?
davide3569 said:
Hi everyone,
I have a problem with my phone. Android 7.1.2 (Lineage OS 14.1) is installed in the GS4, and it worked perfectly. The recovery is TWRP. Yesterday, the Lineage OS developers released a system update, so I downloaded it from the phone settings and then tapped on the icon to install it. Then it booted into recovery and I installed the file downloaded (the auto-installation does not work for me). So, when it finished installing the new version, I rebooted the phone and... it was stuck at the Galaxy S4 boot logo. Hence, I rebooted it to see if ti worked but nothing, so I decided to go again into recovery ad perform a full wipe and a clean installation. Rebooted the phone but it continues to stuck at the logo. I also tried to install a previous version of android, which I am sure it works (because it was the first I installed), but the situation doesn't change. I also tried to get into downloading mode, and it goes, so I used a tool called FonePaw Data Recovery to try to fix the problem but it doesn't change. I also installed a different version of TWRP via Odin, but the system won't boot.
So, in conclusion, the phone is able to boot properly into recovery mode and downloading mode but not able to boot system. What can I do now?
Click to expand...
Click to collapse
Restore Back to Stock an then use stable twrp
Teddy Lo said:
Restore Back to Stock an then use stable twrp
Click to expand...
Click to collapse
Man, you saved me!!!
I followed this guide and now it works perfectly. Wow! Thank you very very much.
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
bskov said:
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
Click to expand...
Click to collapse
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
Yeah, im going to back it all up once I get home and wipe it clean to flash DFE and flash the ROM on top.
Also, I flash Magisk Uninstaller, it told me it couldn't find a stock boot image (and then proceeded to generate one), and then once I restarted the phone I went to CPU-Z to check root access and it changed to "No", so something was taking effect.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
So, I tried decrypting, but I can't, because of something with Android Pie. Doesn't matter now, I wiped every storage partition clean and flashed the firmware twice, then flashed Magisk on top, now it's working. Thanks anyway!
That prompt not showing up and magisk manager not showing in app drawer is a common issue for me even though I've never installed MultiROM on my device. You can ignore both.
Here's what I do to resolve the issue:
1) Install Magisk Manager apk.
2) Go to settings, scroll down to "automatic response", click that, click either grant or deny, then click it again and this time set it as prompt.
That should show the superuser prompt.
Hi guys,
i have an old ASUS MeMOPad FHD10 LTE, which i am trying to use LineageOS with.
TLDR: suddenly no Touch input in TWRP Recovery AND LineageOS 15.1/16 after it worked at first, OTG cable with mouse/keyboard input as workaround, in stock ROM the touch input IS working without problems
I unlocked the bootloader, did a backup of stock recovery img, flashed TWRP v3.2.3-0 for [Asus_ME302KL][DUMA] (from here). I rebooted to TWRP and made a NANDROID backup and flashed LineageOS ROM 15.1 (from here)
Everything worked perfectly fine until here, i booted up LineageOS 15.1 successfully, then i tried to flash mindthegapps (from here), i noticed too late this was the 64bit Version and ofc it bugged out to hell.
I then wiped data/cache and flashed 15.1 ROM and this time i used opengapps full package for 8.1 and flashed it directly after, but on reboot LineageOS 15.1 got stuck (just rebooted after 20min loading screen).
Then after a few more steps and tinkering, including trying out Lineage 16 for ME302KL, at one point the touch input in TWRP stopped responding on entering recovery. Multiple restarts didn't help. I didn't do anything other then flashing ROMs and wiping data/cache (at some point /system too).
I plugged in an USB Mouse with OTG and was able to navigate and flash back the stock ROM from nandroid backup, the touch input worked just fine!
Then i rebooted into TWRP, still no touch. I flashed LineageOS 15.1 ROM, and to my shocking, also no touch input after booting up. Flashing back stock ROM did get it back to working again. I even flashed back the stock recovery IMG and re-flashed TWRP again, still no luck.
What else is there, that i can try?
I was thinking of fastboot erase/format in bootloader, which partitions do i have to delete for a FULL reset, since flashing back stock recovery/rom didn't help?
Got touch input working with twrp-3.1.1-0-duma (older version), proceeded to flash Lineage 14.1 for MeMOPAD10 FHD... still no touch input there.. im so confused, any help?
Got touch working now with AOSP Extended ROM: https://forum.xda-developers.com/android/general/rom-aosp-extended-v4-4-t3637692
For now i'll stick to that.. but why does it break on LineageOS?
Hi, May i know how you unlocked the boot loader? for me the .apk downloaded from ASUS is not working. it always says "An unkown error occurs, which may be a network connection issue. please wait and try again later".
is there any other way to unlock the bootloader? appreciate your response.
Hello, may I ask how you unlocked the boot loader?
Hello!
Yesterday, after succesfuly installing the modified VBmeta image and flashing TWRP, i ended up wiping my OS accidentaly.
Trying to take advantage of the situtation, i searched some custom roms to install, and found the Lineage OS 18.0 Thread on the Galaxy a10 custom roms. I wiped the required caches, and flashed the OS, Magisk and Gapps (NikGapps) in this order.
However, my phone won't boot anymore. It shows the first samsung screen (warning me that i'm not using a official firmware), then the screen warning that the bootloader is unlocked, and then the phone just goes black screen indefinitely. I can force restart with power + volume down, but can't access recovery or download mode by any means, as it just goes black when i try. PC won't recognize the phone as well, giving me no way to install scatter firmware of any sorts.
Is there anyway to save my phone?
Hello! If you still have issues, I have the same phone. The problem was the custom rom I was trying to install (LineageOS). Crdroid booted up just fine.