Related
Hey guys !
For my part, i love Sony Xperia UI. So, what do you think about porting it ?
I found this rom : Xperia Z2 stock, Zipaligned and Deodexed, and rooted.
I open this thread, so we can chat about this. I'm not the best guy to mod kernel, so any help is very apreciated.
I know Lollipop is released few days ago and you're still in love on it
Cheers
Good night, and good luck
dekefake said:
Hey guys !
For my part, i love Sony Xperia UI. So, what do you think about porting it ?
I found this rom : Xperia Z2 stock, Zipaligned and Deodexed, and rooted.
I open this thread, so we can chat about this. I'm not the best guy to mod kernel, so any help is very apreciated.
I know Lollipop is released few days ago and you're still in love on it
Cheers
Good night, and good luck
Click to expand...
Click to collapse
while the idea of a nexus running the finest OEM UI on the market does intrigue me,
The thought of this thread turning into a troll fest and off topic discussion is screaming in my face.
I am going to allow this thread on the basis that it is a thread for the development work of porting Sony UI to the phone.
If I find unneeded posts or off topic chit-chat this thread will be closed. I have subscribed to this thread for observations
If you have any issues with this just PM me.
DO NOT REPLY HERE.
Please stay on -topic of development ONLY.
Thanks for the cooperation,
~JAB
XDA Mod
Link is broken.
kidrobot52 said:
Link is broken.
Click to expand...
Click to collapse
Yep for me too.
He gave the link to his in-progress download, not a shareable link
Sent from my Sony Xperia ION
Toledo_JAB said:
while the idea of a nexus running the finest OEM UI on the market does intrigue me,
The thought of this thread turning into a troll fest and off topic discussion is screaming in my face.
I am going to allow this thread on the basis that it is a thread for the development work of porting Sony UI to the phone.
If I find unneeded posts or off topic chit-chat this thread will be closed. I have subscribed to this thread for observations
If you have any issues with this just PM me.
DO NOT REPLY HERE.
Please stay on -topic of development ONLY.
Thanks for the cooperation,
~JAB
XDA Mod
Click to expand...
Click to collapse
I opened this thread to have help and discussion to port it because i'm in love on Sony UI and it would be awesome to see it running on Nexus 5. It's not a troll.
kidrobot52 said:
Link is broken.
Click to expand...
Click to collapse
You're right. Link fixed to OP
I think the most difficult thing is porting the UI, because other things only require to copy the apk, for example the launcher, sony apps...
Sony widgets only work with sony launcher at least on my old xperia arc. Good luck
We've been through this before, people have tried porting ROM's from other devices and it's always been a dead end. Proprietary libs will always be the one road block unless we know any devs with exceptional knowledge in decompiling and patching libs. Don't want to be a downer but that's the truth
jlmcr87 said:
I think the most difficult thing is porting the UI, because other things only require to copy the apk, for example the launcher, sony apps...
Sony widgets only work with sony launcher at least on my old xperia arc. Good luck
Click to expand...
Click to collapse
No. The apk copy is useless if you dont copy the entire framework folder with apk's. For my part, i started, and can't see the bootanimation. The phone reboots.
topgeardave said:
We've been through this before, people have tried porting ROM's from other devices and it's always been a dead end. Proprietary libs will always be the one road block unless we know any devs with exceptional knowledge in decompiling and patching libs. Don't want to be a downer but that's the truth
Click to expand...
Click to collapse
Know that. Porting is hardcore. For now, i didn't obtained anything nice.
Have some news :
Flashed a Xperia Z2 kernel to my phone (Attempting to get working my port as secondary rom) on Multirom.
After it, flashed Uber kernel. Now, the phone still stuck to Google logo, but 5 seconds after, i've got a little vibration. I remember my old Xperia X10 did a vibration when it boots, indicating you can access the recovery pressing back button.
If somebody has skills on editing kernel, and want to contribute to this project, thanks to contact me.
dekefake said:
Have some news :
Flashed a Xperia Z2 kernel to my phone (Attempting to get working my port as secondary rom) on Multirom.
After it, flashed Uber kernel. Now, the phone still stuck to Google logo, but 5 seconds after, i've got a little vibration. I remember my old Xperia X10 did a vibration when it boots, indicating you can access the recovery pressing back button.
If somebody has skills on editing kernel, and want to contribute to this project, thanks to contact me.
Click to expand...
Click to collapse
That's dangerous mate, you're lucky you didn't brick your phone as the Z2 has different mount points
dekefake said:
Have some news :
Flashed a Xperia Z2 kernel to my phone (Attempting to get working my port as secondary rom) on Multirom.
After it, flashed Uber kernel. Now, the phone still stuck to Google logo, but 5 seconds after, i've got a little vibration. I remember my old Xperia X10 did a vibration when it boots, indicating you can access the recovery pressing back button.
If somebody has skills on editing kernel, and want to contribute to this project, thanks to contact me.
Click to expand...
Click to collapse
That little vibration was most likely the boot loop recycling after the boot failed. My S3 would do that too when stuck in a boot loop
DigitalUnderground said:
That little vibration was most likely the boot loop recycling after the boot failed. My S3 would do that too when stuck in a boot loop
Click to expand...
Click to collapse
Yeah, it was like a start up vibrate. Common on my GT-i9300
topgeardave said:
That's dangerous mate, you're lucky you didn't brick your phone as the Z2 has different mount points
Click to expand...
Click to collapse
Know it, it's why i did it on Multirom, and edited updater-script
rootSU said:
Yeah, it was like a start up vibrate. Common on my GT-i9300
Click to expand...
Click to collapse
I think so.. 10 seconds after that, it reboots. I'm sure the reboot loop it's related to kernel. I think i must contact somebody to help me with the kernel.
Cheers guys.
OMG found something awesome will try to build 19.2.A.0.344 for hammerhead right now guys
dekefake said:
OMG found something awesome will try to build 19.2.A.0.344 for hammerhead right now guys
Click to expand...
Click to collapse
Best of luck! Continuing to watch this thread. This one is the only OEM skin I wouldn't mind having ported over to our N5. Thanks for your continued development, keep us posted!
RoyJ said:
Best of luck! Continuing to watch this thread. This one is the only OEM skin I wouldn't mind having ported over to our N5. Thanks for your continued development, keep us posted!
Click to expand...
Click to collapse
Yes i think i can yes ! Look here
Launched repo init -u ... android-4.4.4_r2 branch of AOSP. once repo init finished, downloaded it and unziped to root of my android source tree. Created .repo/local_manifests/shinano.xml like Sony says, and now running repo sync. After, will build, but for hammerhead. Hope it will work
That is only for AOSP. Sony releases the bits and pieces for their devices. This is going to only get you an aosp build, nothing more.
The got repo you listed is only the device information for building. It is not going to net you anything.
Dameon87 said:
That is only for AOSP. Sony releases the bits and pieces for their devices. This is going to only get you an aosp build, nothing more.
The got repo you listed is only the device information for building. It is not going to net you anything.
Click to expand...
Click to collapse
Are you sure ? repo sync already has downloaded 35Go.. and no i don't think it's normal.
Very much so. And 35GB is normal for a repo sync. I believe my sync for 5.0 was like 40GB.
But back to your question. Just look at the files that are in the bits you linked. Sony's OEM skin and enhancements are not open source. Most OEMs release source for the modified items related to the kernel, and some software. Sony is rare in that they actually release enough to build an actual aosp build. The files you are using are going to net you nothing more than an AOSP build.
Dameon87 said:
Very much so. And 35GB is normal for a repo sync. I believe my sync for 5.0 was like 40GB.
But back to your question. Just look at the files that are in the bits you linked. Sony's OEM skin and enhancements are not open source. Most OEMs release source for the modified items related to the kernel, and some software. Sony is rare in that they actually release enough to build an actual aosp build. The files you are using are going to net you nothing more than an AOSP build.
Click to expand...
Click to collapse
Ok thanks so much. I don't want to build AOSP so i'll search a little more
Cheers
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
First thanks o.o
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Brawn_Sg said:
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Click to expand...
Click to collapse
Philz doesn't support --block flashing or the new method of flashing LP.our twrp has not properly implemented fstab for installation and I'm not able to make twrp with new fstab in cm-12.0 tree as it is throwing a lot of error messages and I currently don't have any kitkat based ROM tree due to my computer corruption few days ago.
I will be trying a clean build 2day.
ashwin007 said:
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
Click to expand...
Click to collapse
Which version of cwm recovery is in the build?
gud work
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
goutamniwas said:
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
Click to expand...
Click to collapse
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
EDIT:Well @ace312 its no more cwm in cm tree.its cyanogen recovery made by cm
ashwin007 said:
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
Click to expand...
Click to collapse
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
goutamniwas said:
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
Click to expand...
Click to collapse
nevermind.i think i made a dirty build by replacing cmr with twrp without mka clean.so rebuilding now.hopefully it'll work.
Hey,
Why don't you flash system.img and boot.img with fastboot?
ace312 said:
Which version of cwm recovery is in the build?
Click to expand...
Click to collapse
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
GeekyDroid said:
Hey,
Why don't you flash system.img and boot.img with fastboot?
Click to expand...
Click to collapse
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
okay. it's been months I left ROM development. Sorry about that.
ashwin007 said:
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
Click to expand...
Click to collapse
Well, sorry I thought it is less than 215MB. I didn't think of it.
My last device was a motorola defy and developer @Quarx has a booting 5.0 lolipop build. perhaps he could enlighten us on how to make a booting build for out device.
Moto defy came with android 2.1 and kernel 2.6 so he should be able to help.
Now even moto e has received the "motorola update services app" update!! So maybe we are pretty close enough to get android L now!!! I think rather than rushing up things for condor cm12 and getting a buggy build after soo much hardwork wouldn't feel good!! Maybe we can wait a while for the android L to hit moto e ans then finally build cm12 which would be more stable too!!
•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•
see the attachment...
Lolipop is more closer...
This is a development thread.Refrain from posting those monotonous posts.I would like to keep this thread clean.
http://www.stjsgadgets-portal.com/2015/02/moto-e-users-start-getting-lollipop.html?m=1
I've received several reports for this thread in the past 2 days, so now it's time to issue a global warning here:
Let's keep this thread on topic, DEVELOPMENT, which is clearly stated in the title AND in the OP.
If you have a question, SEARCH FIRST, per the Forum Rules
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?
Motorola Things That Matter:
How to unlock your bootloader:
https://forum.xda-developers.com/z2-force/how-to/how-to-unlock-bootloader-t-mobile-t3654657
Where to obtain unlock code for bootloader:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Source Code + Proprietary libraries for building AOSP :
https://source.android.com/source/building
Motorola Mods / Developer portal:
https://developer.motorola.com/
XDA TOOLS FOR ROOT/UNLOCK/BUILDING (ALL UNTESTED AS OF 8/11/17, But many should work )
1.) https://forum.xda-developers.com/mo...l-windroid-universal-android-toolkit-t3048093
2.)https://forum.xda-developers.com/z-force/development/motorola-moto-one-tool-v1-0-t3397687
My Preferred Rom Kitchen(s)
Windows - Assayed Kitchen
https://forum.xda-developers.com/ch...-android-roms-editor-assayyedkitchen-t3410545
Linux - SuperRs Kitchen ( only kitchen that will deodex 7.0+ correctly)
https://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
Google Apps Packages:
http://opengapps.org/
DualBoot Patcher (SnapShot)
https://forum.xda-developers.com/sho....php?t=2447534
Viper4Arise
https://forum.xda-developers.com/and...earch-t3379709
Magisk OFFICIAL
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk UNOFFICIAL Snapshots
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Shortcut Master Lite
https://play.google.com/store/apps/d...cutmaster.lite
Make ANY Quick Setting Tile
https://play.google.com/store/apps/d...mquicksettings
SystemUI tuner - Universal UI MODS (root/non-rooted)
https://play.google.com/store/apps/details?id=com.zacharee1.systemuituner&hl=en
Just a small snip-it of who I am and why im providing any info for this device.
Im a small developer who builds stock based roms, with some mods and focuses on building a battery friendly, debloated and stable rom.
Adding in the best mods from every device and removing anything and everything that is not essential and can free up speed and space.
I am always open to ideas and suggestions but there is no guarantee that it ever will become a added feature.
Im prepping my kitchen to start building roms for the Moto z2 force. I will primarily be building for the Sprint Variant only, BUT
I will make any and all attempts to make this as universal or share my knowledge and work with T-Mobile devices as they also are un-lockable.
My rom's will be built to pass safety-net, and to continue to keep as much if not all of the stock staple features alive and working. With that being said, I DO NOT BUILD FOR SUPER SU/ Ill be building directly for MAGISK rooted rom's to achieve this, but in 99% of my devices flashing SuperSu over my build will add SuperSU and become the primary root method but will not be supported for safety-net moving forward once you've injected SU.
What i wont do:
I wont be building some special custom AOSP/CAF etc rom, and I dont build from source code directly
I wont be providing help for other brands that can not be rooted/unlocked nor will I be working to provide a un-lock for those devices,
you should submit a bounty and crowdfund a devs time and work to provide such a task, if one can even do so for the device in question.
I will NOT be asking for donations or provide a donations option, I only provide my personal builds so others can enjoy something new.
I dont mind requests for features but i do not build for others, i build for myself and share the joy with the community. PLEASE post bugs on my post for the rom/roms i build,
do not re-post the same thing 10x, and make sure you TAG me in the bug report with full details, device being used and what was being done before/during the crash etc to be able to understand the issue. LOG CATS, SCREENSHOTS ETC are GREAT TOOLS TO GET THINGS FIXED!!
With all that being said, If you locate a mod used on other Motorola devices, please post the links here and ill move them to the OP for easier access.
As development grows ill continue to update this page to reflect a easy place to keep all the good stuff. Any relevant info for us will help continue to attract more users, more developers and more options for everyone!!
Pleasure to meet you guys and hope you enjoy the Motorola as much as I will!
Can't wait man!
This is great news thank you
Sent from my SM-N930F using XDA-Developers Legacy app
I am itching for TWRP to be released for this thing
Same
Wait, this phones been out for a week, and there's no lineageOS, TWRP, custom kernels, or multiboot? I'm out.
Just kidding . Can't wait to see what kind of development comes in time. Loving the phone so far though!
Android FTW!
Thanks @Team DevDigitel for all you do for the community! I had the LG V20 and you ROM was the tits. Cant wait to see what you will bring to the Moto Z2 Force!
Here is the boot.imgs from T-Mobile, ATT, US Cellular and Sprint
https://drive.google.com/folderview?id=0B1tqDJm_qQf4UDYwN3FRbmVuNG8
---------- Post added at 04:53 AM ---------- Previous post was at 04:49 AM ----------
Stock Roms
Verizon
https://androidfilehost.com/?fid=889764386195919695
AT&T
https://androidfilehost.com/?fid=889764386195919694
Sprint
https://androidfilehost.com/?fid=889764386195919693
US Cellular
https://androidfilehost.com/?fid=889764386195919692
T-Mobile
https://androidfilehost.com/?fid=673368273298975455
T-Mobile OTA link https://drive.google.com/file/d/0B1tqDJm_qQf4Z2QyLS10YVNLWWM/view?usp=drivesdk
Sweet
Sent from my SM-N930F using XDA-Developers Legacy app
dead links.
Discontinued.
Awaiting for thread deletion.
Thanks...Nice work after your miui 5 ROM
Help please..
Need someone who can risk his device by testing this ROM......
Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.
Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.
Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.
Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!
Last build not installed,error 7.
mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!
Hey, I would like to help out, can I have the link to the ROM?
theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Links
Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid
Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.
Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!