Just signed up here first post to the threads but you guys been helping me out for years different devices programs huge thanks to everyone here.
New to this device I'm starting to really dig it ran couple stable 8.1 ROMs got magisk+systemless xposed running. I previously dualbooted lineage nougat with stock on my droid bionic using safestrap(wanted to add a gingerbread) before getting this phone. I flashed the Multirom Twrp but app said I was having kexec kernel issues then ended up bootlooping os or getting black screen few times ended up just full reflashing cm firmware putting regular twrp back up.
Seen video of multibooting many ROMs( but I assume older non Oreo ROMs) and Ubuntu touch from a flash drive. Is it possible for me to bootup with a safe stock, ubuntu, and a 8.1 ROM(read Aosp extended is compatible but couldnt flash a kernel on top of it)? Couldnt find stock cm 6.0.1 bacon zip was gunna try and flash think it was ap kernel again over that but I tried a couple kernels didn't know which one was the right one.
Is there any newer Multirom alternatives or proper current kernel patch link? Does EFI droid work better could I still get ubuntu? Any advice would be appreciated pointers in the right direction tried to do some digging trying to really superpower my device if I can before I log into my all apps and stuff again. Is this a wild goose chase? Or was I like one step away
Related
I have a new tf300t with Android 4.1.1 on it and I have followed an older guide to unlock the device and it said to put clockworkmod on it and the Cyanogenmod forums indicate a problem with that, so I went TWRP instead. The twrp site said to pick the right version (-jb) and I did that.
I put 2.6.latest of twrp on and did a backup. Everything is going great. I rooted the device with SuperSU, Copied over CM 10.2.nightly and the right gapps version and it flashed fine. I booted in and I let it go for awhile and it just bootlooped. I went back into twrp and reflashed to ensure that wasn't an issue (same problem) and restored and I'm back to the beginning. I decided to try the 10.1 version on Cyanogen's site and had the same issue. I'm thinking it's the bootloader version doesn't match -- needs to be 4.2, but I want to be careful not to brick the device since a lot of people have done that.
Any guidance or pointing me at a thread would be appreciated. I have a feeling that letting the OTA update take place on the device kind of ropes me into a corner I might not want to be in. I'd really like to be on the latest Android OS *assuming* most of the tf300t features work. I can handle some odd things not working quite right.
Thanks,
Rich
Step1
It appears that my semi-direct path is to get to the newest [MINUS 1] version of 4.2.1 from Asus.
TF300T-US_epad-10_6_1_27_1-UpdateLauncher.zip
Many newer ROMS require this boot loader, and many people say to stick with the twrp 2.5.0.0 because 2.6.x.x is buggy. I can confirm that 2.6.x.x (latest), the mount feature does appear to be broken.
My only concern now is timing. Upgrade to 2.5.0.0 first, or upgrade using fastboot to the new Asus rom. It might not matter and I might need to put TRWP back on after the flash anyhow.
Also, I did root my current OS before doing this update, so it will be interesting to see if that remains intact.
Rich
Step3
I used fastboot to update and I thought I could apply the TWRP 2.5.0.0 update right after it, but it wouldn't take it. I was a little worried that I borked it. It booted and went into the OS and updated a bunch of things. I noticed my SuperSU was no longer root even though it was going to try and survive the update.
Also: I switched to the 4.2 Launcher... not sure I want my tablet to run just like my phone. I might switch back.
I'm still going to try and get to a CM 10.2 rom, it might not be an official rom though.
Rich
Step 4
I decided to see where things were at with a fully tweaked 4.2.1 rom before the 4.3 rom and picked
[ROM]★●[TF300T/G/L/201/301][CROMi-X 5.0.2][ODEX/DEODEX 10.6.1.27.1][SEP 8]●★
This looks very well done/well polished and has lots of people testing it. Will update as I head to 4.3.
I have been flashing this afternoon trying to find a ROM that meets the following needs (without going into too much detail), but have not been able to find one that will will work without bootloops.
Basically, I am looking for a CM12 5.0 ROM that supports the AK kernel with working encryption. BlissPop has been badly buggy for me since late February, and I just tried with Temaseks 8.8 (last android 5.0.X version, still supports exposed) twice. First time tried to encrypt after flashing latest AK kernel and UKM zip, but my OPO would just reboot without encrypting. Then I tried flashing on a new clean install after encryrpting, and got a bootloop. I have also tried this on some other ROMs, even some F2FS ones but it didn't work (I don't think encryption works with F2FS).
Any help would be greatly appreciated. I can give more details as necessary. I never post on XDA, but I am by no means a novice to Android or flashing.
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.
I'm thinking of switching to a custom ROM for some time while I wait for the Samsung A12 One UI 4 update. Which is the most stable custom ROM for the A12 as of right now that one can use as a daily driver?
I followed everything as instructed and still couldn't install anything may I get some help plz? I tried countless times always going back to stock + magisk...
dreadmachine said:
I followed everything as instructed and still couldn't install anything may I get some help plz? I tried countless times always going back to stock + magisk...
Click to expand...
Click to collapse
What were you trying to do
Allehandro said:
What were you trying to do
Click to expand...
Click to collapse
I first rooted, then installed twrp, but couldn't boot to stock after flashing twrp, so tried flashing gsi arm64 ab, then gapps, and kernel, then it booted to welcome screen, but always random reboots all the time.. so I went back to stock..
From my experience with custom ROMs, I haven't found any good one with no bugs or crashes so I would only recommend one to use rooted stock. Just root your stock android and stick with it.
Allehandro said:
From my experience with custom ROMs, I haven't found any good one with no bugs or crashes so I would only recommend one to use rooted stock. Just root your stock android and stick with it.
Click to expand...
Click to collapse
hey...
how come there is there no rom for it.....
it seems like a snappy phone and 4 gigs of ram is fast af and suitable for any rom there is lol
did samsung do something to prevent flashing of roms or what....
cause i want to get this phone and i want it to last long
There are yet no custom ROMs for this device as of what I have seen so far. *Talking about a ROM that is fimware supported and not a generic one* You can install GSIs, which are love and hate. GSIs are a generic images which can be run on any andorid device with treble support and API LEVEL 29 or higher, aka starting with android 9(oreo). There is no support for VERIFIED_BOOT. It uses HIDL vendor interfaces. I can only tell you to wait if you want a fimware supported ROM, LinageOS is beeing build. I'm currently playing with my ARCH build, I will make a ROM too, but when I get everything setup as it should be. I talked plenty and still do both on these forums and on telegram, you can find some my interesting sayings in my Explaining Thread... Forgot to meniton I would recomend you to try LIR or Los19 if you are looking for a good GSI. I still haven't tried Los19 because doing stuff with ARCH...
Cheers,
Krypton
LAST_krypton said:
There are yet no custom ROMs for this device as of what I have seen so far. *Talking about a ROM that is fimware supported and not a generic one* You can install GSIs, which are love and hate. GSIs are a generic images which can be run on any andorid device with treble support and API LEVEL 29 or higher, aka starting with android 9(oreo). There is no support for VERIFIED_BOOT. It uses HIDL vendor interfaces. I can only tell you to wait if you want a fimware supported ROM, LinageOS is beeing build. I'm currently playing with my ARCH build, I will make a ROM too, but when I get everything setup as it should be. I talked plenty and still do both on these forums and on telegram, you can find some my interesting sayings in my Explaining Thread... Forgot to meniton I would recomend you to try LIR or Los19 if you are looking for a good GSI. I still haven't tried Los19 because doing stuff with ARCH...
Cheers,
Krypton
Click to expand...
Click to collapse
thanks for the info
I appreciate your hard work