Elephone B Version 2016 CyanogenMod 13 ? - Elephone P8000

it was funny how I realized mine was the new version now
I made this thread here so you guys can discuss, this is for information to others who have gotten the new elephone
1) How do we get root ?
No, there isnt any proper recovery last @Emileh ported it did not work very well you are able to flash it the recovery but you are unable to boot back into the system it just stuck at the elephone logo.
2) as of now we only have one rom that has been up here and running K06TE-A.A.vR14.E1.160707 (2016 Version)
K05TS-A.A.vR1E.E2.160217 (2015 Version)
3) cosmetic mixed up (happens alot on chinese phone)
my front is the old 2015 version cover but my back is the new fingerprint cover (possible you can confirm with that is the new elephone you have if you are not sure.
4) so no root and no cyanogenmod and no recovery ?
as of now Im not sure about root, cause I did tried to flash recovery from @Emileh but I could not boot back to android os, so we cant flash supersu,
kingroot and others dont work !
also there some memory layout changed, so it will render the android 5.1 roms useless, please dont try unless you know what you are doing and know how to recover from mediatek usb port
5) will CyanogenMod 13 work ?
to be honest we need a fully working recovery.
maybe there can explain and clear anything more that I left out, I have just gotten the phone
@skeleton1911 @BlueFlame4 @Emileh @Deepflex
somehelp would be nice. thanks would be nice to get cm13 for both the 2015 and 2016 working

Hey,
well the 2015 and 2016 versions are basically two different devices - despite having the same name they share very little. A unified CM 13 build is thus not only difficult to establish but I would even say that it makes things more complex than developing two single versions. That said, CM 13 for the 2016 should be rather easy to bring up because it ships with 6.0. Basically you could take Deepflex's P9000 tree, change it according to the 2016_P8000 and boom - should work. With that you can then of course also compile a working recovery to achieve root That's the theory at least

Is that so but we have yet to achive root and figure out what is the internal changes between those two? Maybe @Deepflux can lend a helping hand in this wish you could help out @BlueFlame4, cause I finally had the money to get this phone possible if you could look into the recovery issue on why it does not boot after flashing it aka bootloop at elephone logo

** Attempted to Port and it does not work. did repack twice.

Hey. Just saw this topic.
I made a better version of the recovery (but forgot to post it), which is actually able to flash roms. It now also mounts everything properly. Flashing root on stock rom works 100%. (only thing not working in ADB, I think).
I will upload it later.
Problem is, there are no roms (expect stock, which you flash using SP Flash Tools). You can't flash the roms that other have made for the old version of the phone. Doesn't work like that.

Emileh said:
Hey. Just saw this topic.
I made a better version of the recovery (but forgot to post it), which is actually able to flash roms. It now also mounts everything properly. Flashing root on stock rom works 100%. (only thing not working in ADB, I think).
I will upload it later.
Problem is, there are no roms (expect stock, which you flash using SP Flash Tools). You can't flash the roms that other have made for the old version of the phone. Doesn't work like that.
Click to expand...
Click to collapse
yeah @BlueFlame4
mention something about cyanogenmod from @Deepflex, could it be this ?
https://github.com/Deepflex/android_device_elephone_p8000/commits/master
hopefully we can get cyanogenmod working, possible if you release the recovery ? is it TWRP ?

Zenns said:
yeah @BlueFlame4
mention something about cyanogenmod from @Deepflex, could it be this ?
https://github.com/Deepflex/android_device_elephone_p8000/commits/master
hopefully we can get cyanogenmod working, possible if you release the recovery ? is it TWRP ?
Click to expand...
Click to collapse
I was talking about this. You have to adapt it to the P8000 and have to use a 3.18 kernel (+ M blobs) though.

there isnt any 3.18 kernel that was released right ? m blobs can be extracted question is why won't your cm13.1 work on the new elephone ? memory changes ? it is still same soc right or there is something different quite confused.

Bump

Related

[WIP][ROM][Verizon] CM10.1 for LG G2 (Verizon) looking for help!!

Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: kernel, device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_kernel_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
10/17/13:
http://forum.xda-developers.com/showpost.php?p=46554268&postcount=271
10/12/13: alpha
http://forum.xda-developers.com/showpost.php?p=46407049&postcount=138
10/3/13: Super alpha
http://forum.xda-developers.com/showpost.php?p=46147336&postcount=74
I would love to help, but I admit I don't know much about Android development. I've got an AT&T G2 and I know C# and a bit of C++, so I'm sure I can figure out C. I think it's awesome that you're working on CM, if I can help out somehow I'd love to!
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
bose301s said:
Not trying to be a **** because I can't wait for CM on this device, but why 10.1? Why not just go ahead to CM 10.2 and Android 4.3?
Click to expand...
Click to collapse
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
fonix232 said:
Because our kernel, etc., are all set up for Android 4.2.2. Meaning, it is easier to get 4.2.2 running, and then move forward to get 10.2.
JackpotClavin: We already have a "few" devs prepping a device tree, though it still misses the proprietary blob references. You should take a look at them, all the device trees are on Github, under TeamLGOG.
Click to expand...
Click to collapse
Ok, that is what I was thinking but I have never done any dev work or anything so I figured I would ask.
I cant help but I sure want to thank you folks for trying to get this up and running. This phone is an absolute BEAST! Coming from the gnex I'm excited about the G2's potential.
Sent from my VS980 4G using Tapatalk 4
Thanks!
I just wanted to thank you very very much for working on this! I knew this was going to be a well developed phone and I bet before 4 months we will have a good amount of choice as far as roms go. Thanks again!
I've been trying to port beanstalk to the G2 but I need the same information you are trying for. I need device trees to sync with. I can PM you with what info I've came up with So far if you are interested.?
Edit: tress are up! Great work
Sent from my LG-D800 using xda app-developers app
If you lived in my town I'd probably help by cleaning the gutters for you hehe. Thanks for your work!
Sent from my EVO using xda app-developers app
I am definitely willing to help in any way I can.
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
grandmasterlarry said:
I am willing to beta test and report bugs, dont know much about development but I want CM i have been using it forever...
Click to expand...
Click to collapse
same goes for me, I have the Korean version.
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
mrbig012 said:
Does CyanogenMod get rid of features like KnockON? I have grown accustomed to it and don't know if I could do without it (my device sits in a vehicle dock a lot of the time where the buttons on the back are 100% inaccessible unless I disconnect the charger, remove phone from dock/holder and find the buttons on the back.)
Is KnockON a Snapdragon 800 feature, or an LG UI feature (I think so, as it doesn't seem to work except in the notif bar, the stock browser, and the stock lock screen)? Can it be added to the AOSP/CM code perhaps?
Click to expand...
Click to collapse
LG UI feature. I'm fairly sure it will be ported to an AOSP/CM10/LGUI hybrid ROM at some point. I believe part of the issue that devs are running into is that a lot of the custom LG software appears to be tied together.
Can you guys keep us updated on your progress, this is a make or break thing for me with this phone, CM is just so much better than any stock ROM that I don't know if I can deal with a phone that has no prospect of official support.
JackpotClavin said:
Howdy folks
I'd like to thank:
Dan Rosenberg (djrbliss) for Loki (the exploit that allows for custom boot images)
Dees_Troy (for TWRP)
Everybody who has contributed to the CyanogenMod Project
xiaolu for github tools used for unpacking and repacking boot images
I picked up my brand new LG G2 on Friday and I've been hard at work to get CM10.1 booting on it ever since yesterday; but a few hours ago I got my first boot -> http://imgur.com/a/1sZz2
I'm using a few proprietary files that I'd like to not use in the future (more than just the Adreno blobs)
But I'm looking to get a team together to get this working 100%
I will post device and vendor source as soon as I get back from cleaning gutters at my dad's house
What works:
Literally nothing, Android won't boot unless you have the necessary EGL libraries, so I just threw those in because I knew it would boot, and nothing else just to get a bare-bones (but booting) ROM. You can navigate throughout UI fine though (it's very smooth believe it or not).
I'll also upload a proof-of-concept build for those willing to see what CM10.1 will look like on our G2s. I'm currently unable to flash a zip in TWRP recovery, so I have to boot into recovery, wipe data, boot into fastboot, flash a system.img and a boot.img and reboot
If I were any person who likes to ROM but will like to remain stock until there's a stable ROM, I'd add a random "#" to any empty line in the file /system/build.prop which will throw off the sha1sum checker when the recovery goes to install an OTA update (this will block all OTAs from ever installing, thus keeping the current boot image exploit viable and it won't be patched up as the OTA won't be able to install. (root is required)
Edit: device and vendor sources are up!
https://github.com/JackpotClavin/android_device_lge_g2
https://github.com/JackpotClavin/android_vendor_lge_g2
Click to expand...
Click to collapse
Are we going to try getting mobile network and wifi working first? Is adb working?
droid_<3er said:
Are we going to try getting mobile network and wifi working first? Is adb working?
Click to expand...
Click to collapse
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
JackpotClavin said:
First is audio. It's proving to be a big problem. I can't get anything working using either prebuilt binaries from stock, or building from source
Click to expand...
Click to collapse
I am NOT a developer, but this could help perhaps?
http://opensource.wolfsonmicro.com/content/wm5110-linux-driver-released
Not sure if it really is open source or only available as binaries, but the WM5110 is the audio SoC in this phone... I am probably not helping.
Additionally, I think the S4 uses this SoC as well. It's a pretty new part but is gaining a lot of momentum.
Edit: My god that WM5110 is a hell of a part... quad-core, 600 MIPS... dayum!
Glad to hear an update, even if it's about issues. Seeing that there are people actively working on this to make it happen makes me much happier and less worried about keeping this phone vs. returning it tomorrow or Friday to see how the Nexus 5 plays out etc.
Have any of you tried talking to Ricardo Cerqueira? He is in fact the primary maintainer for all LG Devices with regards to Cyanogenmod. I am sure he is planning on supporting this device in the near future, I just don't know when. It will probably be when the device is more readily available since it was pretty much just released.

x9076 with R63419 LCD working recoveries

TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?
GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).
So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.
Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!
Does the offical TWRP and CM support this find7 with new LCD????
Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.
Double the question. Lack of working TWRP is just fatal to any tinkering.
GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit
Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....
Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1

BLN-L24 links have bad key in the Honor 6x Repository thread

Need to rollback, or be advised of any custom ROMS that work..
Try Elite ROM from ROM section. it should work fine.
I personally would not recommend installing Elite ROM as it is more hassle than it is worth when you try to switch ROMs. It re/debrands your device and even after restoring a nandroid your audio will not work nor will your camera function properly. What files have bad keys? I put a lot of those up and the keys should work fine....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
@ghostair is your device bricked? IMO none of the ROMs for this phone are worth installing on a main phone because there is too much functionality lost, no disrespect to the devs. Elite ROM does have the least amount of bugs but it is a hassle as I mentioned earlier. My main gripe about it is when installing and uninstalling apps you must restart the device in order for the apps to be added or removed from the app drawer....its a major annoyance.
BLN-L24C567B110 Thanks to @Dazed No More
boot - https://mega.nz/#!ceRkHQoA!L8MECn8Ul...8JwO7ZuVEEr8mk
recovery - https://mega.nz/#!sOZAUJTZ!QKKROoWkI...UPNDwL79ZI1yQI
BLN-L24C567B360 Thanks to @Dazed No More
boot - https://mega.nz/#!hDQB3RCT!YTH2j1IhJ...y_prJHEgHdSrxg
recovery - https://mega.nz/#!Fa4DBbxS!XDIczpXcr...TApUtNvcOMEDnc
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
ghostair said:
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
Click to expand...
Click to collapse
Is your device bricked? You say you want to rollback, but have you started the process....what firmware are you on?
Dazed No More said:
....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
.
Click to expand...
Click to collapse
Let me check mate. Thanks for pointing that out.
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
ghostair said:
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
Click to expand...
Click to collapse
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Im assuming you did not make a full backup in TWRP before flashing any ROMs, in which case you have learned a valuable lesson....always have a backup. But since you dont we will get you back to EMUI which I assume is what you mean when you say roll back.
Dazed No More said:
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Click to expand...
Click to collapse
I understand, I probably should have just used, "go back," to EMUI. Since LOS 13 isn't usable in the least, as I can't make calls, and it drops LTE.
If they work then how? I followed everything, flashing vendor.img with fastboot, then flashing the respective zip?
I'd rather not go back to EMUI, it's why I haven't been able to actually "use it as a phone," since purchase.
Why would you not want to go back to EMUI? Its smooth and everything works. EMUI is the reason you havent been able to use it as a phone?? There is not one single ROM for this device that works entirely and has full functionality. You're always going to be missing something whether its the camera, LTE, calls, etc.
You're going to have to go back to EMUI so you can update to Anrdoid 7.0 (be sure to make a full backup) and then flash away all the ROMS you like and you will see they are all broken in some way. This is most definitely not the phone to use if you are looking for polished ROMs.
My last tip before departing......download the flashable vendor zip if you still want to mess around with the ROMs, it makes life much easier. Its in one of the threads in that forum I think AOKP

Is there more ROMs?

I recently purchased an tab S4 just an update from my previous Samsung tablet. I was wondering is there more ROMs for this tablet or ROMs currently in development? I noticed theres like 2 ROMs for this tablet. I have a note 8 and I'm currently running deluxerom on and it, and I really enjoy the tweaks and customization I'm able to do. I was looking for a same kind of feature for my tablet. Would greatly appreciate the answers I'm looking for. Thanks!
Mkami said:
I recently purchased an tab S4 just an update from my previous Samsung tablet. I was wondering is there more ROMs for this tablet or ROMs currently in development? I noticed theres like 2 ROMs for this tablet. I have a note 8 and I'm currently running deluxerom on and it, and I really enjoy the tweaks and customization I'm able to do. I was looking for a same kind of feature for my tablet. Would greatly appreciate the answers I'm looking for. Thanks!
Click to expand...
Click to collapse
Pretty much zero support. You can get a few 9.0 GSI ROMs to boot, but they all have issues. Mine has been sitting around since it was purchased while still using my old 2014 model.
veekay said:
Pretty much zero support. You can get a few 9.0 GSI ROMs to boot, but they all have issues. Mine has been sitting around since it was purchased while still using my old 2014 model.
Click to expand...
Click to collapse
Aww no way!? Really? I excitingly got this tablet cause of the features and thought perhaps there would be amazing ROMs for this particular tablet, but I guess not xD What are GSI ROMs? Also as a desperate attempt would other tablet ROMs work on this s4? Thanks mate!
Mkami said:
Aww no way!? Really? I excitingly got this tablet cause of the features and thought perhaps there would be amazing ROMs for this particular tablet, but I guess not xD What are GSI ROMs? Also as a desperate attempt would other tablet ROMs work on this s4? Thanks mate!
Click to expand...
Click to collapse
I had thought the same thing, but it seems the S3 is the last tablet to get real support.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Some of the ones for 9 will work, but most features won't work too well, if at all.
You might be able to get another rom to work, I know I had no luck. Even trying ones with similar hardware, they all failed to even flash since the booting numbers are different.
Kind of have to be satisfied with Samsung, half baked custom roms or sell the thing.
Mkami said:
Aww no way!? Really? I excitingly got this tablet cause of the features and thought perhaps there would be amazing ROMs for this particular tablet, but I guess not xD What are GSI ROMs? Also as a desperate attempt would other tablet ROMs work on this s4? Thanks mate!
Click to expand...
Click to collapse
First,download "Treble Check" app from playstore & read for your device...
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
(Some GSIs roms are not compatible with some devices!)
veekay said:
I had thought the same thing, but it seems the S3 is the last tablet to get real support.
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Some of the ones for 9 will work, but most features won't work too well, if at all.
You might be able to get another rom to work, I know I had no luck. Even trying ones with similar hardware, they all failed to even flash since the booting numbers are different.
Kind of have to be satisfied with Samsung, half baked custom roms or sell the thing.
Click to expand...
Click to collapse
Hey Veekay I tried it and you're right unfortunately I came across the same issue as you brother
Now I'm stuck and I need help sorting my device out, was wondering if you knew this issue or could help?
When I got the stock firmware back and then when I flash TWRP with odin after going into TWRP I get 0mb as internal
so when I format and then go back into my load up the screen after SAMSUNG says "verification failed" and then reset
on the bottom. I tried other options as well. Without even wiping on TWRP the devices boots up into the setup wizard for the firmware fine
but after I wipe TWRP so I can get access to my internal drive my samsung boots into that verification reset screen. Got any clue as to how I can
resolve this issue? Thanks a bunch!
daitalos said:
First,download "Treble Check" app from playstore & read for your device...
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
(Some GSIs roms are not compatible with some devices!)
Click to expand...
Click to collapse
Hey! Thanks for your reply, will this work for PIE? I can't downgrade from PIE to OREO
and I don't know if GSI even works properly on my device
Mkami said:
Hey Veekay I tried it and you're right unfortunately I came across the same issue as you brother
Now I'm stuck and I need help sorting my device out, was wondering if you knew this issue or could help?
When I got the stock firmware back and then when I flash TWRP with odin after going into TWRP I get 0mb as internal
so when I format and then go back into my load up the screen after SAMSUNG says "verification failed" and then reset
on the bottom. I tried other options as well. Without even wiping on TWRP the devices boots up into the setup wizard for the firmware fine
but after I wipe TWRP so I can get access to my internal drive my samsung boots into that verification reset screen. Got any clue as to how I can
resolve this issue? Thanks a bunch!
Click to expand...
Click to collapse
Have you tried just reloading the latest stock firmware from scratch?
Yup, its unfortunate that there isn't much community support for this device. The Tab S4 is Project Treble supported and a few GSI ROMS do work. But as others have said they are unstable and not for use as a daily driver. We have a few discussion threads here talking about them.
veekay said:
Have you tried just reloading the latest stock firmware from scratch?
Click to expand...
Click to collapse
Would that work? If I did that I would still be able to download and install TWRP and have a root? Because of it being PIE
UndeadAnarchy said:
Yup, its unfortunate that there isn't much community support for this device. The Tab S4 is Project Treble supported and a few GSI ROMS do work. But as others have said they are unstable and not for use as a daily driver. We have a few discussion threads here talking about them.
Click to expand...
Click to collapse
I am going to do more research on these projects because I really wish there was more ROMs its quite an amazing tablet but the potential with the stock ROM lacks a lot
Mkami said:
Hey! Thanks for your reply, will this work for PIE? I can't downgrade from PIE to OREO
and I don't know if GSI even works properly on my device
Click to expand...
Click to collapse
Generic System Image (GSI) list :
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
you can try only "Android 9 Pie" official or unofficial gsi roms..
and remember ! Some GSIs roms maybe are not compatible with some devices! you can ask for your device on each thread
(for example look here): https://github.com/phhusson/treble_experimentations/issues/777
(usually this Gsi aosp 9 phh, generally works on most devices...BUT! ask first,and discuss it in the thread)
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
daitalos said:
Generic System Image (GSI) list :
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
you can try only "Android 9 Pie" official or unofficial gsi roms..
and remember ! Some GSIs roms maybe are not compatible with some devices! you can ask for your device on each thread
(for example look here): https://github.com/phhusson/treble_experimentations/issues/777
(usually this Gsi aosp 9 phh, generally works on most devices...BUT! ask first,and discuss it in the thread)
https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
Click to expand...
Click to collapse
Can I do this without stock ROM and only TWRP? Because having the stock ROM is disabling my twrp to function without wiping and if I wipe than my stock ROM doesn't work
Thanks!
Mkami said:
Can I do this without stock ROM and only TWRP? Because having the stock ROM is disabling my twrp to function without wiping and if I wipe than my stock ROM doesn't work
Thanks!
Click to expand...
Click to collapse
Sorry,but I don't understand what do you mean " without stock rom and only twrp"...
you can install a Gsi rom, with two ways
Via TWRP, or Via Fastboot : https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ (Tab S4 is a-only arm64)
for any other question, it is better to ask in the thread : https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
(read carefully in OP & you can post,every single question there for your device,and you will get certainly help from the developer or from any other user..)
Mkami said:
Can I do this without stock ROM and only TWRP? Because having the stock ROM is disabling my twrp to function without wiping and if I wipe than my stock ROM doesn't work
Thanks!
Click to expand...
Click to collapse
You are going to have to just wipe it and start over from square one, unless you made a TWRP backup before starting all of this.
Download and flash the latest stock rom from recovery and then you can load twrp again.
I was looking at the possibility of using GSI's on some devices, and while they can offer new life to older devices, they're not entirely stable all the time unless you're willing to make your own changes. I know Lineage has made some excellent progress, but it's not fullproof yet and I wouldn't try it unless you're willing to not use your device as a daily use device.
I had an extra T-Mobile Revvlry which is basically a rebranded Moto g7 Play that I installed the Lineage GSI image and it works fairly well. However, this is more the exception to the rule and Moto devices, I feel, are far simpler in design vs certain Samsung devices. It also had a ton of trial and error involved for me to get it up and running properly.
Is it possible as the s4 becomes older, more people buy it and Samsung stops releasing official updates that someone will come along and create a ROM for it? Or is it more like Samsung locked the bootloaders and its close to impossible to write a ROM for it? Is it still possible to root the s4?
slipnslider said:
Is it possible as the s4 becomes older, more people buy it and Samsung stops releasing official updates that someone will come along and create a ROM for it? Or is it more like Samsung locked the bootloaders and its close to impossible to write a ROM for it? Is it still possible to root the s4?
Click to expand...
Click to collapse
Read very carefully without rush ! for " WETA Kernel + Encryption disabler " etc
especially, read the user comments carefully, and ask on the thread for any questions you have..
https://forum.xda-developers.com/galaxy-tab-s4/development/recovery-twrp-3-3-0-sm-t83x-t3928278 (Pie version)
https://forum.xda-developers.com/showpost.php?p=79483624&postcount=2
https://forum.xda-developers.com/galaxy-tab-s4/how-to/guide-sm-t83x-twrp-magisk-t4059227
( Newest Odin v3.14.4 is there : https://dl2018.sammobile.com/Odin3-v3.14.4.zip )
Thanks. I took a quick peak at the roms and kernels in the roms and kernels forum and they are pretty much all abandoned.
Someone did mention that the LOS 16.0 and ArrowOS GSI's work alright but are a bit buggy.
slipnslider said:
Thanks. I took a quick peak at the roms and kernels in the roms and kernels forum and they are pretty much all abandoned.
Someone did mention that the LOS 16.0 and ArrowOS GSI's work alright but are a bit buggy.
Click to expand...
Click to collapse
samsung,maybe at the end of july to give the upgrade to android 10....it is very likely to happen I think
yes,all Gsi Roms still have various problems unfortunately...
my opinion is: stay to stock rom for now....you can "uninstall" many applications if you want & without root, via "samsung package disabler"(paid) from playstore, or with this way:
https://beebom.com/how-remove-bloatware-android-without-root/
also,you can Install "NiceLock Downloader Companion App" ,to add some features on your device : https://forum.xda-developers.com/galaxy-note-9/themes/nicelock-module-download-links-module-t3923844
with this way I operate my device until now..

Question what about twrp guys? :(

hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Evon88 said:
hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Click to expand...
Click to collapse
What device and firmware?
TheGhost1951 said:
What device and firmware?
Click to expand...
Click to collapse
i want to buy normal OP9P
Evon88 said:
i want to buy normal OP9P
Click to expand...
Click to collapse
The OnePlus 9 pro is good for customizing!
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Evon88 said:
hello everyone, i want to buy this devie but as i see i cant install twrp!
if i can ask why? is it bc of oneplus or no devs to do it? also thx for all devs
i buy the phone for customs and roms and twrp and rooting and this things, this is my priorities
and is this device fully supported for development? any twrp coming soon?
and what about customs here? is they easy to install?
is this device good for gaming and daily use?
Click to expand...
Click to collapse
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Evon88 said:
i want to buy normal OP9P
Click to expand...
Click to collapse
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
Bugscze said:
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Click to expand...
Click to collapse
There's a user/team on the >OnePlus 6 & 6T forums<, that has had success with Android 12 and 13 decrypt, I use it on my 6T, and decrypt works flawlessly, I use it to flash Magisk when changing/updating ROMs.
It's Unofficial however, I hope it trickles to other devices.
Appreciative said:
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
Click to expand...
Click to collapse
thank you sir, what about chinese version? u recommend it? im pro at rooting and customs and msm, if the problem is just roms, i see used chinese new mobile, u recommend me to buy?
deleted
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
thank you bro for explain, what do you think about chinese OP9P? i can change the rom, 5G i dont care that much, anthing else? is quality the same like hardware and plastic and fiber and this things? i mean phone body and screen
Bugscze said:
You can in fact install and boot TWRP. But you can't do almost anything in it... But this isn't OP9P problem but every phone with Android 12 and encryprion enabled. But as other said, TWRP isn't needed for flashing custom ROMs.
Click to expand...
Click to collapse
thanks, <3
Evon88 said:
thank you sir, what about chinese version? u recommend it? im pro at rooting and customs and msm, if the problem is just roms, i see used chinese new mobile, u recommend me to buy?
Click to expand...
Click to collapse
All of them are made in china and I think will be good quality OnePlus phone. I don't know if they use anything different (except rom). You can change from colorOS to oxygenOS
twrp not needed
vincemue said:
twrp not needed
Click to expand...
Click to collapse
Needed, maybe not. Desired, definitely. It can do a lot of things that the stock and AOSP recoveries simply can't (to name just one: it can wipe data without wiping storage, as I mentioned above; stock/AOSP recoveries' "factory reset" wipe destroys everything).
MJPollard said:
@Evon88, the fact is, TWRP hasn't been updated to properly support Android 12, at least not on the 9 Pro, and I'm beginning to suspect that it never will be. IMHO, it looks to me like encryption and other issues introduced by Google have simply gotten the best of the TWRP team. I'll be happy to be proven wrong, and will be pleasantly surprised if TWRP is updated to work with Android 12 and above, but right now, that remains in the realm of wishful thinking.
The good news is that the recoveries included with most Android 12 ROMs (based on the AOSP recovery) are functional, and are capable of doing the minimum work of flashing new ROMs and upgrades (i.e. Magisk and Gapps) just like TWRP. They certainly don't have the wealth of features that TWRP has (such as the ability to wipe only the data partition without erasing the media partition; it's either all or nothing), but then, they weren't designed to have them. I keep hoping that someone will take the AOSP recovery and use it as a base for a recovery that includes more of TWRP's features. (I'd do it if I had the knowledge. I'm knowledgeable enough to poke at AOSP and cherry pick features to create a custom ROM, but the intimate knowledge required to work with the recovery code is something I don't have.)
Click to expand...
Click to collapse
I was on LE2127_11_C20 A12 with tarp and root.......the mail reason it worked was no lock screen security. I did try with setting a password is be cause a script to try and make partitions R/W but that put me in a bootloader loop. Went back to 11.2.9.9..
Did you follow a YouTube tutorial step by step guide to see if you made any mistakes?
dartballs said:
Did you follow a YouTube tutorial step by step guide to see if you made any mistakes?
Click to expand...
Click to collapse
Who are you asking?
Appreciative said:
Don't let lack of twrp hold you back. It's a fun phone. I use it for gaming (CODM) on Android 11.2.10.10 just fine. I may end up flashing an old build of crDroid for Android 11 but I'm pretty happy with how everything is set up on regular OOS now and don't want to lose L1 and start back over.
Unlocked bootloader✓
Root/Magisk✓
SafetyNet✓
Netflix, GPay, Banking apps✓
L1 Widevine✓
Real OOS✓
65w charging✓
120hz LTPO✓
No Dual Sim
The tmobile variant is still for sale on ebay at $469 brand new in the box or from OnePlus directly (also Tmo variant) for $499
Click to expand...
Click to collapse
The Indian variant has dual SIM. Maybe some others variants, too.

Categories

Resources