Related
Since everyone always loves MOAR VERSION NUMBAH...
Android 4.3 for the Xperia Z. With a BIG shout out to Sony Mobile for hosting their own git repository for their deviceshttps://github.com/sonyxperiadev/device-sony-c6603.
This is compiled from AOSP, and has nothing done beyond that. Simply added the Sony repo to Android 4.3 AOSP, and built. As per the Sony AOSP releases, this does not have functional Radio (no phone calls or SMS!!!) or indeed any connectivity.
Working:
Wifi
Not Working:
Mobile network
Bluetooth
I will not tell you how to make mobile network work, but it is not difficult and just involves some binary blobs from memory... Sony don't have the right to distribute those officially, so I won't do it either
In light of this not being a working build, I will not post it as a zip, but as fastboot flashable images. Unlocked bootloader only. C6603 was used to test, other models entirely at your risk (ie. don't bother).
Links:
All files needed are in
http://goo.im/devs/pulser/XperiaZ/4.3AOSP
and will appear there shortly (upload done, it's still propogating)
Feel free to mirror, share, modify, edit, tweak, fix, etc etc etc. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this It's really not that good, but hey...
Top secret information:
Yes, you are also permitted to use this... Yes... that's right, you can use it!
To install:
fastboot flash boot boot.img
fastboot flash system system.img
(optionally, I did it, shouldn't be needed)
fastboot flash userdata userdata.img
fastboot flash cache cache.img
Build instructions to replicate :
Get android 4.3 sources.
Get sony c6603 information on repositories and add to local_manifests for 4.3
Get latest v3 blobs for phone and tablet Z
Put them into vendor/sony/
Repo sync
Make
You sir are 1 step ahead of me. Thanks man. Is it ok if i can use these?
Taylor_Swift said:
You sir are 1 step ahead of me. Thanks man. Is it ok if i can use these?
Click to expand...
Click to collapse
Feel free to mirror, share, modify, edit, tweak, fix, etc etc etc. I am not like certain individuals who go ZOMG NO MIRRORS PLEASE... Go on, mirror, make a torrent if you want, and share it if anyone actually cares about this It's really not that good, but hey...
Click to expand...
Click to collapse
Oops, I forgot to add "use" to that list.
Yes, they can also be used! I shall add "use" to the list
Links not working yet, but I gave them a kick
pulser_g2 said:
Oops, I forgot to add "use" to that list.
Yes, they can also be used! I shall add "use" to the list
Links not working yet, but I gave them a kick
Click to expand...
Click to collapse
Oh i sent you a PM too lol. Sorry but XDA members are really tight when it comes to sharing so when I read that I couldnt believe you said it lol
Taylor_Swift said:
Oh i sent you a PM too lol. Sorry but XDA members are really tight when it comes to sharing so when I read that I couldnt believe you said it lol
Click to expand...
Click to collapse
Lmao... They might be, I'm not... I just typed a few commands, tweaked a couple of stupid errors I made, and it was done.
You are also missing the Camera and getting RIL to work requires more than dropping in some blobs.
I already merged 4.3 in my repo: https://github.com/adrian-bl-yuga
pabx said:
You are also missing the Camera and getting RIL to work requires more than dropping in some blobs.
I already merged 4.3 in my repo: https://github.com/adrian-bl-yuga
Click to expand...
Click to collapse
Yeah, camera blobs are not "officially" made available by sony.
I had just spotted your repo actually and was going to see if it had the RIL etc
So glad I ditched Samsung for Sony :beer:
Sent from my C6603 using xda app-developers app
Congrats on the first non-nexus release of 4.3 I do not have this device but would like to congratulate you
Nicely done! I am happy i bought this device!
when it will be a coumpleterom?
Someone provide galaxy s3 to this AWESOME guy
LegendM said:
Someone provide galaxy s3 to this AWESOME guy
Click to expand...
Click to collapse
No thanks, got plenty of devices, and I have the N7100 (Note 2), which is very similar in hardware to the S3. Exynos is nothing like as easy to do this to, that's why Sony devices are first!
Honestly, it was easier to get this booting on my Z phone and Z tablet, than it was on a Nexus 10 (an official Nexus device!)
pulser_g2 said:
No thanks, got plenty of devices, and I have the N7100 (Note 2), which is very similar in hardware to the S3. Exynos is nothing like as easy to do this to, that's why Sony devices are first!
Honestly, it was easier to get this booting on my Z phone and Z tablet, than it was on a Nexus 10 (an official Nexus device!)
Click to expand...
Click to collapse
We welcome you to the xperia z development scene with open arms
spazzy1912 said:
We welcome you to the xperia z development scene with open arms
Click to expand...
Click to collapse
Thanks Though actually I've been here since the very start, around the very start of the shipments of the Z
FYI: I uploaded my first 4.3 based build:
http://forum.xda-developers.com/showthread.php?p=42084058
I got all hardware working, there are only some minor issues (no 4.3 gapps (using a patched 4.2) and the AOSP voice dialer is hanging (known aosp bug on BT devices).
pabx said:
FYI: I uploaded my first 4.3 based build:
http://forum.xda-developers.com/showthread.php?p=42084058
I got all hardware working, there are only some minor issues (no 4.3 gapps (using a patched 4.2) and the AOSP voice dialer is hanging (known aosp bug on BT devices).
Click to expand...
Click to collapse
Nice to see! You are aware you should be able to make a new GApps package from the factory images? I don't use GApps though, so I haven't done it. But it should be easy enough to do.
I had to see, the recovery is not accessible .... this risk is all the same and no current mod will work with this rom, I'll wait another is, I think,
but thank you for your great job :good: !
In light of there being a supported/maintained 4.3 AOSP for Xperia Z, consider this discontinued.
Indeed, @pabx 's ROM makes the Xperia Z pretty much Nexus standard, in terms of the hardware support. Most impressive from Sony! As such I will close this thread now.
Good evening, in recent days the project Oreo 15.1 for the G5S (montana) has begun. My friend Pedro Kalil was able to make a tree common that supports all motorola devices that use msm8937 or msm8953. The first compilation was started for testing, but we are facing major problems with the sensors and the camera.
At the moment the sensors and the camera are not working, we already made several compilations with the exchange of the libs. But it still does not work.
We need the help of you montana developers so that the Oreo project works.
I had to use xda to communicate this because I could not get the number of some dev's.
Contact me, telegram: therssxda
Lineage 15.1 - It works, but we have problems., ROM for the Moto G5S
Contributors: @rssxda -- @KalilDev
ROM OS Version: 8.1.0 Oreo
Version Information
Status: Testing
Created 2018-07-19
Last Updated 2018-07-18
Reserved
@lohanbarth @kaylansundhar @govind1233
Screenshots:
Good, waiting for news...
I hope the devs actually see this. I dont own montana, but i feel so sorry for the users that i had to do sommething about it. unfortunately i dont know anything about how montana handles sensors.
O Will wainting ...
When it will come out?
@rssxda If basic things like Wi-Fi, touchscreen (and maybe the fingerprint sensor) work, then I'd be very happy to test the ROM. PM me with any info
rssxda said:
@[email protected]@govind1233
Click to expand...
Click to collapse
Already working to fix stuff
Do you have any previews for downloading rom?
WandresJersey said:
Do you have any previews for downloading rom?
Click to expand...
Click to collapse
I won't release it until it's 100%. Look at some ss tho:
good, we waiting the best
The ROM is 64-Bit? Have support to Treble?
KalilDev said:
I hope the devs actually see this. I dont own montana, but i feel so sorry for the users that i had to do sommething about it. unfortunately i dont know anything about how montana handles sensors.
Click to expand...
Click to collapse
First of all I apologize for a too late reply.
Main problem is cedric sensor and camera libraries would not work with montana sensors and camera. Initially for LOS7, I tried this way of making a montana build using cedric libraries. Same problem I ended up with. Whatever change I do, there would be something preventing it from working. Try to use sensor and camera libraries from G5S stock.
Mainly,
system/bin/sensors.qcom
system/lib/hw/sensors.rp.so
system/lib/hw/sensors.montana.so
system/lib/lib_motsensorlistener.so
system/lib/hw/camera.msm8937.so
system/bin/mm-qcamera-daemon
system/lib/libcamerabgprocservice.so
And there is a whole bunch of libmmcamera*.so in vendor/lib directory of stock Nougat ROM.
But my gut feel is these libraries would not work as such in OREO build. We may require to write a SHIM layer.
Please don't take it as discouragement. I am just outlining what problems you would face using a mix of CEDRIC and MONTANA (STOCK) libraries.
Thanks
KS
kalyansundhar said:
First of all I apologize for a too late reply.
Main problem is cedric sensor and camera libraries would not work with montana sensors and camera. Initially for LOS7, I tried this way of making a montana build using cedric libraries. Same problem I ended up with. Whatever change I do, there would be something preventing it from working. Try to use sensor and camera libraries from G5S stock.
Mainly,
system/bin/sensors.qcom
system/lib/hw/sensors.rp.so
system/lib/hw/sensors.montana.so
system/lib/lib_motsensorlistener.so
system/lib/hw/camera.msm8937.so
system/bin/mm-qcamera-daemon
system/lib/libcamerabgprocservice.so
And there is a whole bunch of libmmcamera*.so in vendor/lib directory of stock Nougat ROM.
But my gut feel is these libraries would not work as such in OREO build. We may require to write a SHIM layer.
Please don't take it as discouragement. I am just outlining what problems you would face using a mix of CEDRIC and MONTANA (STOCK) libraries.
Thanks
KS
Click to expand...
Click to collapse
We could fetch these libraries from the 8.1 soak test firmware... If such firmware had been leaked to begin with.
I'm not criticizing the testers, they're doing what they're supposed to be doing, by not leaking anything. However, had someone done that, they would've made you guys' lives a bit easier.
Anyhow, I wish you luck. It's nice to see the G5S get the attention it deserves. It's a nice phone, actually. But it looks like it's the forgotten middle child of the G5 family. lol
Me too waiting..
For stable
Any rumors/news about this rom???
any news
nice to actually have 8.1 in moto g5s??
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
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
THIS ROM IS DISCONTINUED. LEAVING IT UP FOR ARCHIVAL PURPOSES.
As usual, you and you ALONE are responsible for what you do with your device. If something goes wrong by flashing this mod or any other mods, don't blame it on the dev.My buddy just told me about this ROM that was Touhou based so I was like "oh god yes I gotta port this ASAP". This is my first ROM I've built in a while. Built it and rushed here really quick to make a post about it so maybe I can score some juicy Internet Points.
What is exthm-UI:
It's a combination of Lineage and ArrowOS features with Touhou based themes on it. So if you like AOSP and want your bullet-hell waifus loaded by default, this may be the ROM for you.
What works:
Identical to Lineage 18.1 since it was made with those trees
What doesn't work:
AudioFX not included, because I hate that thing
Terminal app not included, it was giving me build errors that I couldn't get around
Default browser (Via browser) seems to be in Chinese, just have F-Droid or something handy so you can install it right away and get another browser
Charging LED doesn't work, even if you enable the light to come on while plugged in it still wont (but the LED itself works for other things)
You tell me
Source Code:
ROM Source: https://github.com/exthmui
Roomservice manifest (device tree, kernel tree, vendor tree can all be found in here): https://pastebin.com/XGE185jY
Kernel source alone: https://github.com/S4muel007/kernel_motorola_trinket
You'll want to delete the highlighted line in the following file before you build: LINK HERE
You'll want to delete Terminal (and probably AudioFX too because it sucks) in packages/apps/ before building
Screenshots:
does the status bar hovers over the punch hole camera on rav variant? it annoyed me so much on other ROMs
LOLCATpl said:
does the status bar hovers over the punch hole camera on rav variant? it annoyed me so much on other ROMs
Click to expand...
Click to collapse
Yes the status bar is over the camera hole, but the icons go next to it
Abandoning this thread. Literally one freakin' week after I build this, the GitHub repo goes into read only and the project is abandoned. Jeez, talk about bad luck.
Previously, this ROM just dropped support for Android 11. Now I found out that the entire ROM is dead altogether.
And yes, I am still running this by the way (as of writing this post). I was waiting for A12 or A13 to finally upgrade, and now it looks like we have that.
Anyway, this was probably the last device that was ever ported to this ROM... spooky!
jasonmerc said:
Previously, this ROM just dropped support for Android 11. Now I found out that the entire ROM is dead altogether.
And yes, I am still running this by the way (as of writing this post). I was waiting for A12 or A13 to finally upgrade, and now it looks like we have that.
Anyway, this was probably the last device that was ever ported to this ROM... spooky!
Click to expand...
Click to collapse
so you do have an a12 or 13 rom?
spiral777 said:
so you do have an a12 or 13 rom?
Click to expand...
Click to collapse
Nope