I am not responsible for anything that happens to your device.
This is a port of MIUI 10 for the op6/6t
Flash at your own risk and make sure to check what's working. Logcats would be appreciated!
Instructions:
1: Flash OxygenOS 9.0.7 twice, this is very important
2: Extract the download somewhere
3: Run the OnePlus 6t flasher (make sure phone is still in fastboot/bootloader)
4: Reboot to TWRP (fastboot boot it if it dissapeared, if you install TWRP you must install Magisk)
5: Flash or adb sideload NFC fix that is included in the download
6: Reboot and install V4A Magisk module and enable headset and speaker, this fixes audio
7: Enjoy!
Download (v3):
MOD EDIT: LINK REMOVED
What works:
Everything except stuff in what doesn't work
What doesn't work:
NFC
Flashlight toggle (3rd party apps work)
MIUI camera (3rd party apps work)
Fingerprint (top priority - @nima0003 - me)
Audio fix #2:
Credits to @dougie313
Flash viper4android module
Grab root browser
Go to vendor\lib\soundfx folder and rename or delete all files in folder
Source code: https://github.com/OnePlusOSS/android_kernel_oneplus_sdm845
Credits: @nima0003 me @ProtoDeVNan0 for the current build
Dylan Neve
Omar
What is it based on? And will you keep working on it?
dennisbednarz said:
What is it based on? And will you keep working on it?
Click to expand...
Click to collapse
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
nima0003 said:
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
Click to expand...
Click to collapse
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
dennisbednarz said:
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
Click to expand...
Click to collapse
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
nima0003 said:
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
Click to expand...
Click to collapse
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier porting of features and so on? Would also make most kernels compatible.
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
champ784 said:
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
Click to expand...
Click to collapse
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
dennisbednarz said:
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier portion of features and so on? Would also make most kernels compatible.
Click to expand...
Click to collapse
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
nima0003 said:
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
Click to expand...
Click to collapse
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
I'm downloading to test, report back in a bit.
champ784 said:
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
Click to expand...
Click to collapse
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
nima0003 said:
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
Click to expand...
Click to collapse
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
champ784 said:
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
Click to expand...
Click to collapse
Yeah same thing happened to my Xperia xc, I could only flash stock rom, not even rooted.
Flashing failed, error: invalid zip file format.
Dark Nightmare said:
Flashing failed, error: invalid zip file format.
Click to expand...
Click to collapse
Great, thank you, working on it.
You would be my hero
It is great to see other types of roms, instead of only los type roms. Great to switch between them over time.
nima0003 said:
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
Click to expand...
Click to collapse
Hopefully not. Lot's of people prefer stock-based ROMs specifically for the reason that they're usually more stable, almost always better performant and always better for battery (with the exception of TouchWiz). And the whole feature thing is also useful.
Lot's of people base the ROMs of Lineage as it usually has hardware specific support, but as we don't have official lineage yet and it would still be a lesser experience than a stock ROM, I strongly advocate for the OOS base.
Wish I could help out but I'm not a developer. If you need something designed, contact someone at Xiaomi, OnePlus or Google, or if you need some piece of code some person is sitting on, let me know (on Twitter or Telegram @dennisbednarz as i don't use the forum DM system).
So basically you just ported the OS and want testers? As of now, OP6T is just 3 weeks old and hardly would anyone dare to try something that says 'I highly doubt it'll work' in the OP.
Can Not installed
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Related
WHOEVER AGREES TO THE POST BELLOW PLEASE LEAVE A COMMENT TO SHOW SUPPORT FOR THE CAMERA PORT
Hello, there Sultanxda
I'm posting this post?with the hope that you'll see what I have to say.
First of all, congrats on the work you done on CM*13 and Lineage *14. Congrats on the touches you added to both.
I love the stability, the battery life on your CM*13, BUT, your camera, or CM'S camera user interface, I just dont think its that much USER FRIENDLY as OOS camera is. I have tried so many ways to get that camera ported onto this ROM and withkut success and I'm sure others have tried it too.
Through this post I am requesting a port file or an update which provides both cameras and let us choose which one we use, or use both in diff situations.
Look, man I get it, you've put work in the camera, BUT the user interface. Please allow us to use OOS camera with no issues.
I'm sure other people would appreciate it too if you would do that. That way your ROM would be the best ROK there is for OnePlus3T. The reason I left your rom ia because of the camera. The camera is one of the most important things in my phone since i capture moments, and I there are moments that I want to capture on the spot, quick and easy, moments when I want to take a quick video and by the time I bring up the video feature its too late, the moment is gone. I hope that you can underatand me of why I want the OOS camera on your rom.
WHOEVER AGREES TO THE POST BELLOW PLEASE LEAVE A COMMENT TO SHOW SUPPORT FOR THE CAMERA PORT
This rom ships with Snap and OnePlusCamera. It is 14.1 - not 13. RAW pic saving and burst mode doesn't work, but evryting else is working.
OnePlus does not use HAL3, but HAL1 with proprietary call backs to framework/av (libcameraservice) to implement some features of HAL3 to HAL1-running OnePlusCamera. Since this is neither real HAL1, nor HAL3 - and because this is proprietary - it's not easy to implement in lineageos. @vavill is working on this:
https://github.com/kxzxxx/android_device_oneplus_oneplus3t/commits/cm-14.1
On a side node: Read, understand, respect and follow the forum rules, please. Questions belong to the Q&A forum.
Jesus save this child..just bless him..
Wrong section.. In case you ask me why u need blessings..!!
arjunarora said:
Jesus save this child..just bless him..
Wrong section.. In case you ask me why u need blessings..!!
Click to expand...
Click to collapse
I think you're exaggerating there. My bad then, how do I delete the post?
benm98 said:
I think you're exaggerating there. My bad then, how do I delete the post?
Click to expand...
Click to collapse
Not at all bud.. @stephen can you please move this to the appropriate section..
nvertigo67 said:
This rom ships with Snap and OnePlusCamera. It is 14.1 - not 13. RAW pic saving and burst mode doesn't work, but evryting else is working.
OnePlus does not use HAL3, but HAL1 with proprietary call backs to framework/av (libcameraservice) to implement some features of HAL3 to HAL1-running OnePlusCamera. Since this is neither real HAL1, nor HAL3 - and because this is proprietary - it's not easy to implement in lineageos. @vavill is working on this:
https://github.com/kxzxxx/android_device_oneplus_oneplus3t/commits/cm-14.1
On a side node: Read, understand, respect and follow the forum rules, please. Questions belong to the Q&A forum.
Click to expand...
Click to collapse
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
benm98 said:
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
Click to expand...
Click to collapse
Haha, he's the maintainer of that ROM you gave up on, lol.
benm98 said:
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
Click to expand...
Click to collapse
I completly misunderstood your question.
If your question was: "Can I use OnePlusCamera from @nvertigo's cm-14.1 rom on @Sultanxda's cm-13.0 rom?", the answer is: no, but you can use the android 6 version.
Just copy these files from stock OxygenOS 3.x.x (you need this older version for cm-13.0):
Code:
/system/priv-app/OnePlusCamera/OnePlusCamera.apk
/system/priv-app/OnePlusGallery/OnePlusGallery.apk
/system/lib64/libfilter-sdk.so
/system/lib64/libopbaselib.so
/system/lib64/libopcameralib.so
/system/lib64/libopcamera.so
If this works, make a flashable zip of it.
A private word:
Your posting feels unfair, barefaced and offending. Where are your bug reports and/or logs? Have you asked for help? I havn't found one single word on your issues in the rom thread. You demonstrate a lack of respect for my work and real bad manner.
nvertigo67 said:
I completly misunderstood your question.
If your question was: "Can I use OnePlusCamera from @nvertigo's cm-14.1 rom on @Sultanxda's cm-13.0 rom?", the answer is: no, but you can use the android 6 version.
Just copy these files from stock OxygenOS 3.x.x (you need this older version for cm-13.0):
Code:
/system/priv-app/OnePlusCamera/OnePlusCamera.apk
/system/priv-app/OnePlusGallery/OnePlusGallery.apk
/system/lib64/libfilter-sdk.so
/system/lib64/libopbaselib.so
/system/lib64/libopcameralib.so
/system/lib64/libopcamera.so
If this works, make a flashable zip of it.
A private word:
Your posting feels unfair, barefaced and offending. Where are your bug reports and/or logs? Have you asked for help? I havn't found one single word on your issues in the rom thread. You demonstrate a lack of respect for my work and real bad manner.
Click to expand...
Click to collapse
Not home right now. I appreciate your guide, will try it when I get home. Look, lad, I didn't meat to offend, I have used your rom as my daily driver for a month since I gave up on SULTAN's because there is no OOS camera on it. I enjoyed using it, but I was missing xposed and the fact that sultan's uses Android 6 which in my opinion is more stable.
Again didn't mean to offent no one, is just the fact that sultan's offers xposed due to it being 6.0 and thats why I think battery life is better on that, since it's not as heavily loaded as 7.0 or 7.1 is.
Thanks again for the guide, looking forward to giving it a try. Also what do you mean by "If this works, make a flashable zip of it.", do you mean after I drop in the files from OXYGEN OOS to sultan's OS create a zip then flash it and then see if it works?
According to Project Treble lead Iliyan Malchev,
Malchev says that Treble standardizes Android hardware support to such a degree that generic Android builds compiled from AOSP can boot and run on every Treble device. In fact, these “raw AOSP” builds are what will be used for some of the CTS testing Google requires all Android OEMs to pass in order to license the Google apps—it’s not just that things should work, they are required to work.
Click to expand...
Click to collapse
Now that there's an Oreo beta for the Essential Phone that supports Treble, perhaps this can be used to further development on the device.
/u/foremi on Reddit confirmed that simply flashing a Pixel 2 system and boot image to the device is not enough, as it fails to boot, so the question is what constitutes a generic AOSP build?
I don't have Linux installed right now or I'd build it myself, but I suspect that building it with the simple target device of "generic" might be what Malchev is referring to.
If any devs would like to test this theory or give their input as to how they think this actually works I think it'd be incredibly useful for not just Essential phone development, but Android development as a whole.
EDIT: @phhusson confirms that the target device should be aosp_arm64_ab
FWIW "generic AOSP build" is really what it says it is.
I have access to the "Google certification generic AOSP build" (that's weirdly not public, I don't know why), so I gave it a try. (Edit: So if the ROM was Treble-certified, it would work)
I get the Android bootanimation, but that's all (I have to say that's still a big step forward compared to other Android versions
Looking at the logs, I see a loop of crash because of: /vendor/bin/hw/[email protected]
Which I guess is the HAL for the accessories, but that doesn't seem to be the reason for the crash
The reason of the crash, seem to be this:
11-15 12:59:04.491 5331 5331 F MediaProfiles: frameworks/av/media/libmedia/MediaProfiles.cpp:329 CHECK(quality != -1) failed.
in CAF, frameworks/av/media/libmedia/MediaProfiles.cpp we see vendor-specific (i.e. not in AOSP) quality attributes, like "vga"
And it is defined by Essential's framework (in vendor/etc/media_profiles_V1_0.xml)
Considering there are media_profiles xml files, I'd guess that _V1_0 is supposed to only contain AOSP-capable qualities
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Edit3: the generated fingerprint is too long to build, needs to do make BUILD_NUMBER=4412360
Edit4: To make the situation more clear:
- NO, current ROM is NOT Treble capable
- BUT, almost everything is available for that. Every HAL is using "hwbinder" which is the basis, and most work needed for Treble
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
phhusson said:
Edit2: The fingerprint of "certification generic AOSP", is Android/aosp_arm64_ab/generic_arm64_ab:8.0.0/OTR1.171023.001/4412360:userdebug/test-keys
So my guess to build this is that lunch aosp_arm64_ab && make should work
Click to expand...
Click to collapse
I was gonna link to the aosp_arm64 make file but it said it was specifically for the emulator so I wasn't sure, that's good to know though.
phhusson said:
Also, I've seen some reddit comment mentioning boot.img.
Current version of Treble only concerns system.img, and NOT boot.img!
Future version are supposed to have generic boot.img as well, but that's not to be expected before at the very least Android P.
Click to expand...
Click to collapse
Thanks for this, I suspected such but couldn't find a clear answer from Google on the matter so I suggested trying the boot.img as well just in case.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2. I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
For what it's worth I only have a LG V20 right now which currently doesn't support Treble, so I'm pretty useless as far as testing anything goes, but if this is figured out it'll greatly influence what device I go with when I eventually upgrade.
Now, someone has to test this on a different Treble device such as the Pixel or Pixel 2.
Click to expand...
Click to collapse
Yup. I feel like Treble deserves its own "device" section in XDA
I'm afraid I'm working on something that other people already did on other devices...
I'm thinking MAYBE because the Oreo build for essential is just a beta its treble implementation isn't finished and hasn't passed Google's CTS requirements to boot the generic aosp image. Perhaps this will change in the final build.
Click to expand...
Click to collapse
That's my guess as well.
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
MishaalRahman said:
Interesting stuff. Excited to hear updates on this. PM me if you make a breakthrough and want a feature
Click to expand...
Click to collapse
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
PhantomGamers said:
There's not much I can do on my end sadly, without a Treble capable device, but if anyone is interested in trying this on another device with a mainline Treble-enabled Oreo build I'd install Linux and post the build up so just let me know
Click to expand...
Click to collapse
Google Pixel/Pixel 2 will do, yes?
MishaalRahman said:
Google Pixel/Pixel 2 will do, yes?
Click to expand...
Click to collapse
Yeah they should be fine
PhantomGamers said:
Yeah they should be fine
Click to expand...
Click to collapse
Alright, I'll find you some testers
MishaalRahman said:
Alright, I'll find you some testers
Click to expand...
Click to collapse
Here's the system image if you find anyone, it's a straight fresh build of aosp branch 8.0.0r34
If it doesn't work it's possible that I messed the build up, but it should be fine.
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
PhantomGamers said:
Can someone running the Oreo beta post their results running this app?
If the beta isn't CTS compliant, we should know.
Click to expand...
Click to collapse
Hero you go
TheDethEgineer said:
Hero you go
Click to expand...
Click to collapse
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
PhantomGamers said:
Thanks a lot!
This is interesting... according to Malchev, CTS testing REQUIRES a device to boot a generic AOSP image, and yet the Oreo build is CTS certified and doesn't boot the AOSP image...
Click to expand...
Click to collapse
That's true only for new devices, not for devices upgrading for nougat to oreo.
I wasn't aware there was an AMA yesterday... Too bad we could have asked.
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
How about flashing the system image directly from a Pixel 2 XL?
MishaalRahman said:
Tester with OG Pixel XL says it gives invalid zip file format error when trying to flash in TWRP
Click to expand...
Click to collapse
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
PhantomGamers said:
It's not a TWRP flashable zip, you have to extract the system.img from the zip and flash it with fastboot in the bootloader.
Also as @PresidentMcCain said, seeing the results of flashing a pixel 2 xl system image would be interesting too.
Oh and make sure the tester's OG pixel is already running Oreo before trying. Just adding that in case they didn't upgrade yet.
Click to expand...
Click to collapse
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
MishaalRahman said:
Ah, I see.
Do you happen to know the exact command? I'm not that familiar with A/B partition devices and how that changes fastboot commands.
Click to expand...
Click to collapse
I believe it should work as normal
fastboot flash system system.img
EDIT: Apparently with the A/B partitions you'd do fastboot flash system_b system_other.img to flash the b partition, but the aosp build didn't include a system_other.img so I'm assuming perhaps it's not necessary
So far I still can't find anyone willing to flash this on their Pixel haha. People are really hesitant to flash stuff on the Pixel it seems. Times are not like they used to be =\
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
androiddev - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
CessnaBroon said:
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
klimtwifi - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
Click to expand...
Click to collapse
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
prkfsz said:
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
Click to expand...
Click to collapse
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
CessnaBroon said:
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
Click to expand...
Click to collapse
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
prkfsz said:
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
Click to expand...
Click to collapse
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
CessnaBroon said:
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
Click to expand...
Click to collapse
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
prkfsz said:
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
Click to expand...
Click to collapse
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
CessnaBroon said:
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
Click to expand...
Click to collapse
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
prkfsz said:
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
Click to expand...
Click to collapse
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
CessnaBroon said:
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
Click to expand...
Click to collapse
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
prkfsz said:
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
Click to expand...
Click to collapse
This should work on stock marshmallow too. I will give it a go and get back to you.
Thank you kindly!
lafinjack said:
Thank you kindly!
Click to expand...
Click to collapse
You're very welcome!
CessnaBroon said:
This should work on stock marshmallow too. I will give it a go and get back to you.
Click to expand...
Click to collapse
Sorry for delay in answering..
Unfortunatelly the error is still present. Like i said, probably a software issue.
Bit thanx anuway!
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey there! I'll take a closer look once I'm home. Speak to you then
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
CessnaBroon said:
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
Click to expand...
Click to collapse
Just an FYI...I was reluctant to start everything over again with Odin and latest Samsung firmware, so I opted to take a chance and merely 'adb push' the LineageOS and GApps that you have on your Google drive (along with some cache erasures as you suggested) and everything seemed to upgrade properly from Resurrection Remix to LineageOS 17.1
A few minor problems so far: camera doesn't work, and initial signon to the tablet with a PIN doesn't work so well (seems to take multiple attempts). In any case, now running Android 10!
These were issues that I faced too - I never found a way to fix them. Neither did the original Dev, but apparently updating to the latest webview fixes chrome crashes. PIN you need to wait 30seconds after boot. Camera works only with clean install and even then sometimes doesn't work.
Hope this helps,
Cessna
I was trying to install TWRP but after reboot when I go to the Recovery mode there is no TWRP. I installed the LOS on my Tab Pro 8.4 and wanted to install LOS on Tab S 8.4 but can't flash the TWRP. Any ideas what I'm doing wrong?
Thanks
Does anyone know if there is any custom ROM out yet for Oneplus 10 pro?
batterylifesucks said:
Does anyone know if there is any custom ROM out yet for Oneplus 10 pro?
Click to expand...
Click to collapse
if they don't, buy another phone.
Kosta26 said:
if they don't, buy another phone.
Click to expand...
Click to collapse
HAHHAH, ok thanks
There's potentially a few in development, but it's moving along slowly.
The clear answer is "no" and I don't see any signs of that changing any time soon (if at all). Someone started working on it, but it looks like they lack the expertise to see it through, so don't count on any custom ROMs.
However, this seems to be an issue that is more widespread, not just OnePlus phones are affected. I would actually be interested if there are any new Android phones that have custom ROMs readily available. All the official Lineage OS devices seem to be older.
Too much thing is missing guys.released kernel source has missing scripts and header files.any custom rom group don't have linaro waipo built in sources.Just relax and give time to developers.
metrixx02 said:
Too much thing is missing guys.released kernel source has missing scripts and header files.any custom rom group don't have linaro waipo built in sources.Just relax and give time to developers.
Click to expand...
Click to collapse
hows that coming along?
eviling said:
hows that coming along?
Click to expand...
Click to collapse
Issue is that developers don't have a free and secure way of recovering their devices if it bricks. The MSM tool requires authentication with OnePlus which have deemed the tool as internal use only.
We're stuck until either someone cracks it or OnePlus makes the MSM tool public.
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Bwhite... said:
hello and thank you very much for this feedback. after having watched this forum for a very long time, it is time for me to buy this magnificent smartphone because I have always used gsi pixel experience roms. but I would still like to have your opinion on the sound quality of this beast because on no comment and test nobody talks about it
Click to expand...
Click to collapse
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
domineus said:
GSI depends solely on a bootloader unlock. Unless you get an older device that hasn't been updated, I wouldn't purchase the device with the assumption that root is easy...
Click to expand...
Click to collapse
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Bwhite... said:
Yes indeed I understand that. but I read on the forum that unlocking the bootloader was back on a september update. but the question I ask myself more is the sound quality of the dual speakers. anyway thank you very much for your answer.
Click to expand...
Click to collapse
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
domineus said:
I'm not sure. THere are some who tried who weren't able to bootloader unlock for the September update or afterward.
Sound quality is subjective but I had zero complaints from the speakers
Click to expand...
Click to collapse
ok thank you for all this useful information.
Sorry for the stupid question, but what is GSI? is this a custom rom?
NeoGoku123 said:
Sorry for the stupid question, but what is GSI? is this a custom rom?
Click to expand...
Click to collapse
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
domineus said:
Opening up this thread in hopes some interest can be made.
Since the beta version of Android 13 dropped, I decided to boot into GSI roms to achieve root. To my surprise, not only did the GSI rom boot, but I was able to go through the google setup like a champ. Every now and again, I load different GSI roms to test and I am currently using Google QPR2. As it stands the following works:
What Works
Opening and closing the device actually works and renders content in open and closed state
Cellular/wifi radio works
Touchscreen works but there's issues (see below)
Camera works (albeit not as well as the pixel camera ports)
Notifications fully work
Android Auto works
SMS works
There is a very big problem with using the GSI - the device detects inputs from both screens whether opened or closed. So here's a list of what doesn't work:
Not working
Touch input (as previously described)
Phone features (phone vibrates but dialer never displays)
Battery isn't optimized (given)
If you want to test it and provide some feedback, I am using this GSI rom:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
As always to install GSI roms, bootloader must be unlocked. To install, use DSU Loader. It's a rather painless process
Click to expand...
Click to collapse
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
NikG25 said:
Considering this for a x fold plus.
Were you able to fix the issues and if not, to what to extent are the effects. For example, with the battery not optimized how does it last and with the dialer not displaying are you able to answer the call? Touch input I assume is mostly an issue when using the larger screen (i.e. you accidentally input from the front screen).
Click to expand...
Click to collapse
I wasn't able to fix them but I didn't try. I don't have the dev machine to try and fix the issues and rebuild a LoS GSI to get it working. Which is a shame :/
But given that I have had a really good time with it otherwise because I like the potential of it