Related
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Thank You
I'm surprised to be the first user to say this, thank you.
Due to Sony's incredible hardware and open software I have not only converted many fans to Sony, but I have started a project to modify one of your phones.
This would note be possible without you and your teams corporation, so again, thank you.
Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/
Happy cooking
http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
enjoy
J
Hi all
We have published a new snapshot, zip v14, with camera update (improved quality and stability)
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Enjoy
J
Hi all
I have some more exciting news
http://developer.sonymobile.com/kno...s/how-to-access-uart-ports-on-xperia-devices/
PS.if devices are not listed here they dont have the connector !
Br
J
New updates
http://developer.sonymobile.com/201...wider-range-of-unlocked-xperia-devices-video/
Enjoy
J
We have published new binaries
http://developer.sonymobile.com/downloads/tool/software-binaries-for-aosp-lollipop-android-5-1/
Br
J
Damn, just doing a repo sync... -> back to start
Do you know if that fixes the AOSP video and camera issues on the Z2 Tablet (SGP521)? Someone tested it on a Z Ultra (c6833)?
EDIT: The kernel instructions just vanished from http://developer.sonymobile.com/kno...ld-aosp-lollipop-for-unlocked-xperia-devices/ - I guess I should wait a little while till kernel is updated
Hi all
Blobs v17 are public
Happy easter
J
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
2016-04-22: AOSP Marshmallow binaries for Android 6.0 and AOSP Lollipop binaries for Android 5.1 updated with improved connectivity, stability and camera functionality. We’ve also added the second camera actuators for Xperia Z3 and Xperia Z4 tablet. In addition, we’ve added the camera actuator for the Xperia Z5 family for Android 6.0.
Hi all,
We have updated the build guide to support the latest features and security updates
http://developer.sonymobile.com/kno...aosp-marshmallow-for-unlocked-xperia-devices/
Enjoy
J
This talk probably belongs here instead of in the AICP thread.
Having flashed the: AOSP_M_160604_togari.zip
http://uploaded.net/file/lxsa2oqy/from/53n94q
The rom works by it self. I doubt anyone would run the rom this naked.
I have tried flashing various Gapps zip files before first boot and after first boot.
1a. Flashing rom in fastboot
1b.Reboot to twrp-3.0.2-0-togari
1c.Flash open_gapps-arm-6.0-pico-20160629.zip or open_gapps-arm-6.0-mini-20160629.zip
1d.reboot
Either gapps give the almost the same result. First try I used the mini gapps. I got to the setup wizard. When I came to the Wifi step.
The phone went black. I booted again and raced against the clock. Even if I finished the setup wizard half a second before the phone killed I always came back to the wizard on next boot.
Next try I erased all partition in fastboot and tried again with clean flash. Now flashed pico gapps. This time I came to "optimizing apps 1 of 68".
And the phone killed it self.
Flashing gapps after first boot and then rebooting to recovery does not work. It will give me a flood of force close on booting.
Same result with pico as mini.
Then I found a-gapps. A thread focusing on the issue when meeting the force close on setup wizard.
Also focusing on solving "google service stopped working".
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
This works.
But after flashing xposed-v85-sdk23-arm.zip in recovery. With a-gapps. The phone kills it self when booting again.
Right after the Android boot animation is finished.
Earlier this afternoon I ran a seperate test with a clean install.
I used the microG GmsCore project. Which did work flawless with google apps syncing fine!
I also had SuperSU Root BETA v2.67.zip installed along with xposed-v85-sdk23-arm.zip
http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
What I am unsatisfied with is the fact that the phone turns off. Completely.
Without any warning. With a smooth transition to black like you lock the phone. And it is off.
I can't troubleshoot what is wrong when it just turns off. I need something to look at. A log.
edit1:
My issue is probably related to this
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
Patch need to be included when compiling the rom.
Sources:
http://fxpblog.co/aosp/aosp-6-0/
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-recovery-2-8-7-0-2016-02-03-t3307043
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
http://forum.xda-developers.com/showthread.php?t=3034811
http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
http://www.supersuroot.com/download.html
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
Other sources:
http://forum.xda-developers.com/cro...one-general/fix-setup-wizard-stopped-t3274219
I also had the force closing issue after installing open gapps pico. Just did a factory reset in TWRP and the issue was gone.
Loukiz said:
I also had the force closing issue after installing open gapps pico. Just did a factory reset in TWRP and the issue was gone.
Click to expand...
Click to collapse
It would be strange if the issue did not go away when you made a factory reset
yes but the Google Apps stayed and were fully functional after the factory reset.
Loukiz said:
yes but the Google Apps stayed and were fully functional after the factory reset.
Click to expand...
Click to collapse
Can you tell me the specific partitions you wiped in twrp?
in TWRP, if you press the wipe button, another button appears called "wipe data". On the next page there is some important information highlighted in red. That worked for me.
Loukiz said:
in TWRP, if you press the wipe button, another button appears called "wipe data". On the next page there is some important information highlighted in red. That worked for me.
Click to expand...
Click to collapse
looking at the download mirror there is a new build out. I will test tomorrow morning and see how things work
Loukiz said:
in TWRP, if you press the wipe button, another button appears called "wipe data". On the next page there is some important information highlighted in red. That worked for me.
Click to expand...
Click to collapse
An update: Flashed the AOSP_M_160717_togari.zip and open_gapps-arm-6.0-pico-20160731.zip
There is no force closes on boot. But the phone shuts down after a few seconds.
Edit2:
Wiped cache, dalvik cache, data. Still the rom shuts down.
Is your phone fully functional with gapps installed?
Hello fellow members of XDA,
As most of you know, our beloved F version has not recieved the official Marshmallow update, yet.
So, the past 72 hours I have been flashing, trying and testing my a$$ off.
And the result... A stable, non-ported 6.0.1 stock based ROM for our F version! Hooray! [also a dead battery but that's fine]
A special thanks to @Senthil360 for helping me with this.
Before I start this guide, I want to say I am NOT a developer, I am just another tech enthousiast and really wanted to get 6.0.1 working on our phone.
Second of all, I want to thank all the developers on our Note 4 section for providing me the right files to get this working.
I do not want to take credit for their hard work, I just want to tell how I booted Nameless ROM using their files. I do not want to take any credit for their files and or hard work!
And the final disclaimer: I am not responsible for a bricked phone, failures or anything else. This is experimental, and you shouldn't be doing this if you have no idea what you're doing.
But, if you do want to test it... Follow these instructions..
Part 0) Prerequisites
Make sure your phone has TWRP 3.0.0.0 installed. Any other version is not tested.
Make sure your phone has POK1 bootloader and modem! Other versions are NOT tested.
Make sure your phone has enough battery (I recommend 80%+) and enough storage to create a FULL backup and store the files you need.
Part 1) A full back-up
I highly recommend making a full back-up with TWRP, and copy any personal or important data on another storage, just in case.
Part 2) Collecting the files.
I used the following files:
The namelessROM 6.0.1 ROM, which can be found here: http://forum.xda-developers.com/note-4/snapdragon-dev/rom-nameless-mm-n910gdtu1dpb6-stock-t3360776
Another big-ups to the nameless team for their hard work!
The AEL kernel from friedrich, which can be found on the EchoeROM website/forum.
Big-ups to friedrich and the AEL kernel team, thanks for amazing kernel.
MM_Stuff.zip. This has files that makes the phone boot correctly.
Big ups to wcoast for creating this file.
The file can be found in the attachments!
MarshMallow_Fix.zip, this fixes problems like connecting to WiFi, camera etc.
The file can be found here: http://forum.xda-developers.com/not...twn910f6-0-1-sprint-marshmallow-port-t3361605
Big ups to KeTur for providing this file!
Part 3) Flashing and booting.
So after you created a full back-up, collected all the files, charged ur battery to 80% etc, you're ready to flash.
This is how I did it, and recommend doing it.
First, do a FULL wipe (/system, /data and all caches)
Then, flash Nameless ROM and wait for it to finish.
Clear/wipe all caches.
Next, flash AEL kernel and wait for it to finish.
Clear/wipe all caches.
And finally, flash MM_Stuff.zip and wait for it to finish
Clear/wipe all caches.
Now reboot!
IMPORTANT NOTICE
Your phone will reboot several times, and sometimes before it reaches the Samsung Logo.
I recommend not looking/waiting for it for a while and return later to check on it. It takes atleast 20 minutes, up to 1 hour!
I know it is a long time, but I rather wait a bit longer then bricking my phone.
Just wait and don't touch it, untill it booted!
Part 4) Finalizing your phone.
So, after it booted and cooled down a bit, you can start setting up your phone.
If you experience any bugs like no WiFi, no camera, then flash MarshMallow_Fix.zip. and wipe caches. This file fixes most of the problems, IF they occur.
And finally, feel free to edit the build.prop file to get the right model-number again (it changes with some of the zips! but shouldn't effect ur system, at all.)
Known bugs to ME:
The system is fully stable and shouldn't have any problems.
The only thing I havent got working yet is my S pen - commands. The S pen works, but the menu for the shortcuts etc do not appear. I am trying to fix this today.
Feel free to share your experiments below, or ask an question.
Thank you for reading the long story, and have fun flashing!
Good job!
RIP battery
Sent from my SM-A710F using XDA-Developers mobile app
Link kernel?
chichareal said:
Link kernel?
Click to expand...
Click to collapse
It's on the Echoerom website.. I do not have permission to upload it or provide any mirrors, so I suggest you download it from the official source.
netban said:
Good job!
RIP battery
Sent from my SM-A710F using XDA-Developers mobile app
Click to expand...
Click to collapse
May it rest in peace... But for now, it has to survive for a little longer until I have a new battery
Thanks man !!!
But you can use the stock kernel also ?
Hi,
just to make sure I flash the correct Kernel can you please confirm the name of the zip file: N4_AELKernel_MM_Ed_N910F_N910G_v10_FORMMROMS_16041 6.zip
maze00 said:
Thanks man !!!
But you can use the stock kernel also ?
Click to expand...
Click to collapse
Nope, it will bootloop with stock kernel.
cyvr1 said:
Hi,
just to make sure I flash the correct Kernel can you please confirm the name of the zip file: N4_AELKernel_MM_Ed_N910F_N910G_v10_FORMMROMS_16041 6.zip
Click to expand...
Click to collapse
I can confirm that is the file u need.
Thanks for the confirmation. I will try my luck and start flashing.
works with OL1 + DrketanMM. Thanks
Inviato dal mio SM-N920G utilizzando Tapatalk
Doesn't work with POK 1 bootloader and modem goes onto Samsung's for a few minutes them restarts was doing that 10 times is that normal ? And I did all above in the instructions
Where did you find the kernal? Every link on the rubbish echo forum is dead. Thanks for the guide though, I'd like to give this a go later
Edit: found it, search google for ael kernal rather than echoerom
any result for booting ?
samueldewit said:
Hello fellow members of XDA,
As most of you know, our beloved F version has not recieved the official Marshmallow update, yet.
So, the past 72 hours I have been flashing, trying and testing my a$$ off.
And the result... A stable, non-ported 6.0.1 stock based ROM for our F version! Hooray! [also a dead battery but that's fine]
A special thanks to @Senthil360 for helping me with this.
Before I start this guide, I want to say I am NOT a developer, I am just another tech enthousiast and really wanted to get 6.0.1 working on our phone.
Second of all, I want to thank all the developers on our Note 4 section for providing me the right files to get this working.
I do not want to take credit for their hard work, I just want to tell how I booted Nameless ROM using their files. I do not want to take any credit for their files and or hard work!
And the final disclaimer: I am not responsible for a bricked phone, failures or anything else. This is experimental, and you shouldn't be doing this if you have no idea what you're doing.
But, if you do want to test it... Follow these instructions..
Part 0) Prerequisites
Make sure your phone has TWRP 3.0.0.0 installed. Any other version is not tested.
Make sure your phone has POK1 bootloader and modem! Other versions are NOT tested.
Make sure your phone has enough battery (I recommend 80%+) and enough storage to create a FULL backup and store the files you need.
Part 1) A full back-up
I highly recommend making a full back-up with TWRP, and copy any personal or important data on another storage, just in case.
Part 2) Collecting the files.
I used the following files:
The namelessROM 6.0.1 ROM, which can be found here: http://forum.xda-developers.com/note-4/snapdragon-dev/rom-nameless-mm-n910gdtu1dpb6-stock-t3360776
Another big-ups to the nameless team for their hard work!
The AEL kernel from friedrich, which can be found on the EchoeROM website/forum.
Big-ups to friedrich and the AEL kernel team, thanks for amazing kernel.
MM_Stuff.zip. This has files that makes the phone boot correctly.
Big ups to wcoast for creating this file.
The file can be found in the attachments!
MarshMallow_Fix.zip, this fixes problems like connecting to WiFi, camera etc.
The file can be found here: http://forum.xda-developers.com/not...twn910f6-0-1-sprint-marshmallow-port-t3361605
Big ups to KeTur for providing this file!
Part 3) Flashing and booting.
So after you created a full back-up, collected all the files, charged ur battery to 80% etc, you're ready to flash.
This is how I did it, and recommend doing it.
First, do a FULL wipe (/system, /data and all caches)
Then, flash Nameless ROM and wait for it to finish.
Clear/wipe all caches.
Next, flash AEL kernel and wait for it to finish.
Clear/wipe all caches.
And finally, flash MM_Stuff.zip and wait for it to finish
Clear/wipe all caches.
Now reboot!
IMPORTANT NOTICE
Your phone will reboot several times, and sometimes before it reaches the Samsung Logo.
I recommend not looking/waiting for it for a while and return later to check on it. It takes atleast 20 minutes, up to 1 hour!
I know it is a long time, but I rather wait a bit longer then bricking my phone.
Just wait and don't touch it, untill it booted!
Part 4) Finalizing your phone.
So, after it booted and cooled down a bit, you can start setting up your phone.
If you experience any bugs like no WiFi, no camera, then flash MarshMallow_Fix.zip. and wipe caches. This file fixes most of the problems, IF they occur.
And finally, feel free to edit the build.prop file to get the right model-number again (it changes with some of the zips! but shouldn't effect ur system, at all.)
Known bugs to ME:
The system is fully stable and shouldn't have any problems.
The only thing I havent got working yet is my S pen - commands. The S pen works, but the menu for the shortcuts etc do not appear. I am trying to fix this today.
Feel free to share your experiments below, or ask an question.
Thank you for reading the long story, and have fun flashing!
Click to expand...
Click to collapse
Thanks so much i have flash dr.ketan m2 then ael kernel mm 10. And then mm stuff and update superuser 2.46 befor flash all full wipe and last wipe dalvik and cache thanks for mm stuff zip great work
Sent from my SM-G935F using XDA-Developers mobile app
axel87 said:
Doesn't work with POK 1 bootloader and modem goes onto Samsung's for a few minutes them restarts was doing that 10 times is that normal ? And I did all above in the instructions
Click to expand...
Click to collapse
Did you read the first post?
It clearly states that it can take somewhere between 20 minutes and 1 hour. It also said that it can boot multiple times.
Great job Mr Zwitsal
Going to try it as soon as I get home
Deleted
_elina_ said:
Deleted
Click to expand...
Click to collapse
Look at 1st post...
Sent from my SM-N910F using XDA-Developers mobile app
Any chance you could make a flashable data fix for marshmallow..like the ones that are available on lollipop
Done with TWRP 3.0.2 and COK1 Thanks for job, samueldewit
Hi,
has anyone installed Xposed on this ROM? I tried with Wanams v81 Framework for MM ARM API23 but that did not work. Phone was stuck on Samsung logo for 45 Minutes before I removed the battery and did an uninstall of the framework which worked.
I have a Samsung Galaxy S III that I purchased on eBay. It have TWRP on it, and I know absolutely nothing about it except how to open it and get back to the phone. I'm looking for someone who can be patient enough to answer questions and give advice
Ok, to help you with this, in case you haven't fully understood TWRP yet.
It is a very powerful tool that has many features. It can create(backup button in TWRP) and restore(restore button in TWRP) backups(most important feature), it can save those backups to whatever storage location you choose, you have to find the option and select where you want the backup to be stored. You can also choose to backup other partitions along with the default partitions.
It can install(Install button in TWRP) various recovery flashable .zip files including ROMs, Kernels, Modems, newer recoveries, and various other mods/tweaks such as the Xposed framework. It can flash .img files also, provided those .img files are for your device.
It has the ability to wipe(format) the various partitions on the device to clear all data in the selected partition(s), these include the normal wipes when flashing ROMs and such, To do the normal wipes, select the Wipe option in TWRP, you'll see at the top it says Factory reset/wipe data, wipe cache partition and wipe dalvik/ART cache(newer ROM and recoveries use ART, dalvik is older stuff(swipe the slider to wipe). In addition to the normal wipes there are the advanced wipes(select Wipe option, then select Advanced Wipe), typically the advanced wipes are only used when doing a "clean install", it is used to wipe only the System partition and the Data partition to clear any junk that might cause issues with a new ROM you want to use, some ROMs even require a system wipe/clean install to use the ROM. You must be careful when using advanced wipes, if you wipe the wrong thing you'll be screwed. To be safe, only wipe System, Data, Cache, Dalvik/ART, and maybe internal storage(this erases everything you have on internal such as pictures, other media and other downloaded content). Also, when you wipe system partition it removes your OS completely and will have to be flashed with a ROM before rebooting, if you reboot without flashing you'll have nothing to boot to and in some cases it is difficult to revive the device.
It has a file manager that you can use to browse through the folders and files on your device while in recovery.
It can be used to connect the device to ADB where you can do all manner of things with the device. ADB can be used to boot the device to whatever mode you want, it can be used to push or pull files to and from the device, it can be used to capture logcats from the device that give technical live data of what the device is doing below all the layers of software to pinpoint bugs and issues. ADB is used to flash .img files to the device and even pull .imgs from the device using the dd command line, it has many, many things it can do, its all pretty advanced though.
There are other minor, rarely used features as well such as fix permissions, mount and unmount various partitions, etc. You can learn all of them by googling the various features to find descriptions of them.
If you have questions, just ask.
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you againView attachment 3891814
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
You should be able to flash any of the sprint S3(d2spr) ROMs, recoveries, kernels and mods for d2spr and of course the general mods that can be used by virtually any device such as the Xposed framework for ARMv7 devices. I have an S3 that uses the (d2vzw) stuff so I can help you a lot with your S3.
Actually all of the US variant S3(d2vzw, d2spr, d2att, d2usc, d2tmo, etc..)devices can use the d2lte ROMs, on top of that, the d2 devices can all flash each others ROMs without harming the device, they just won't have signal or buttons will be backwards and little things like that, the S3 ROMs can easily be converted from one device to another, the d2 devices are 95% the same.
You could easily flash the newest TWRP and then choose a d2spr lollipop or marshmallow ROM from the Sprint S3 forum as these are the most up to date and readily available ROMs, there's very little support for Kit Kat and older stuff.
And of course, you could always go back to full stock with no root or TWRP if you just want the device to work and would rather avoid all of this custom stuff and its complexities.
For that you just need to do a google search for:
"Return to stock (your model number)"
Or you can go to Sammobile .com or samsung-updates .com and use your model number to find the stock firmware for your device, download it then download the newest version of Odin and install it on PC then boot your phone to download mode(volume down+home+power, press up at the caution screen to enter download mode), connect to Odin, if you get a blue or yellow comm# box you're connected. Click the AP button then browse to your stock firmware .tar.md5 file, select it, back in Odin click start and it will flash the device and reboot into the restored stock firmware, sometimes it bootloops and you have to boot to stock recovery(volume up+home+power) then factory reset and wipe cache in stock recovery then reboot.
I can help you any direction you want to go, just say the word and I'll get you there. Do you want custom or stock? If you want custom, do you want Kit Kat(4.4.x) lollipop(5.x)or marshmallow(6.x), maybe even a Nougat(7.0) ROM?
Droidriven said:
You should be able to flash any of the sprint S3(d2spr) ROMs, recoveries, kernels and mods for d2spr and of course the general mods that can be used by virtually any device such as the Xposed framework for ARMv7 devices. I have an S3 that uses the (d2vzw) stuff so I can help you a lot with your S3.
Actually all of the US variant S3(d2vzw, d2spr, d2att, d2usc, d2tmo, etc..)devices can use the d2lte ROMs, on top of that, the d2 devices can all flash each others ROMs without harming the device, they just won't have signal or buttons will be backwards and little things like that, the S3 ROMs can easily be converted from one device to another, the d2 devices are 95% the same.
You could easily flash the newest TWRP and then choose a d2spr lollipop or marshmallow ROM from the Sprint S3 forum as these are the most up to date and readily available ROMs, there's very little support for Kit Kat and older stuff.
And of course, you could always go back to full stock with no root or TWRP if you just want the device to work and would rather avoid all of this custom stuff and its complexities.
For that you just need to do a google search for:
"Return to stock (your model number)"
Or you can go to Sammobile .com or samsung-updates .com and use your model number to find the stock firmware for your device, download it then download the newest version of Odin and install it on PC then boot your phone to download mode(volume down+home+power, press up at the caution screen to enter download mode), connect to Odin, if you get a blue or yellow comm# box you're connected. Click the AP button then browse to your stock firmware .tar.md5 file, select it, back in Odin click start and it will flash the device and reboot into the restored stock firmware, sometimes it bootloops and you have to boot to stock recovery(volume up+home+power) then factory reset and wipe cache in stock recovery then reboot.
I can help you any direction you want to go, just say the word and I'll get you there. Do you want custom or stock? If you want custom, do you want Kit Kat(4.4.x) lollipop(5.x)or marshmallow(6.x), maybe even a Nougat(7.0) ROM?
Click to expand...
Click to collapse
Wow, you are my hero! I don't know how to thank you enough.
First off, I promise I have put in lots of work on my own trying to find answers. Also, I may be underestimating my own understanding.
As far as ROMs, I haven't worked this hard to give up now! Not only do I want custom, I want to know what kernel does, what a governor does, what mods are. I think everyone else thought I wanted to be told what system to install while I only wanted to be educated so I could decide for myself. Basically, I'm asking for a teacher
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you againView attachment 3891814
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Mablemae said:
Wow, you are my hero! I don't know how to thank you enough.
First off, I promise I have put in lots of work on my own trying to find answers. Also, I may be underestimating my own understanding.
As far as ROMs, I haven't worked this hard to give up now! Not only do I want custom, I want to know what kernel does, what a governor does, what mods are. I think everyone else thought I wanted to be told what system to install while I only wanted to be educated so I could decide for myself. Basically, I'm asking for a teacher
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Thank you. My dilemma in finding one is that I read where you need a certain firmware or modem. How do I know if I need it? I looked at the section in my phone that I sent the pic of. Where is the information I need, and how do I know if I can install something?
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Thank you. My dilemma in finding one is that I read where you need a certain firmware or modem. How do I know if I need it? I looked at the section in my phone that I sent the pic of. Where is the information I need, and how do I know if I can install something?
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't know of the d2spr devices requiring flashing a modem. Can you give me a link to see what you're talking about? If not I'll see if I can find what you're talking about. Or I might get in private chat with the d2spr guys on the OctOS team to see if they know.
You do know that there is a d2spr device and the d2spr refresh device, don't you? You can't use the d2spr refresh stuff, that's a different variant. I think it is the one with the certain modem because it is a tri band device I think.
Droidriven said:
I don't know of the d2spr devices requiring flashing a modem. Can you give me a link to see what you're talking about? If not I'll see if I can find what you're talking about. Or I might get in private chat with the d2spr guys on the OctOS team to see if they know.
You do know that there is a d2spr device and the d2spr refresh device, don't you? You can't use the d2spr refresh stuff, that's a different variant. I think it is the one with the certain modem because it is a tri band device I think.
Click to expand...
Click to collapse
I am going to try out the one you sent me the link for. If I think I want more bells and whistles, I'll let you know and see what else is available. I have no reason to look elsewhere. I'm just so thankful for your help. Do you have a link where I can send money to your team or an address where I can send a pie? Lol
Sent from my SPH-L710 using XDA-Developers mobile app
Droidriven said:
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Click to expand...
Click to collapse
I just want to be sure I'm doing the right thing. I went to the link you sent and clicked the link for "stable", then "Samsung", then s3 lte, then sprint gs3. I assume that since you have my current phone information to know what I'm running, you gave me something that is compatible and doesn't need me to modify any of my current settings in order to install, but I'm just double checking. Also, how important is gapps if I use titanium to backup any apps I want to carry over? I've never downloaded gapps before a wipe
Sent from my SPH-L710 using XDA-Developers mobile app
Droidriven said:
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Click to expand...
Click to collapse
Ok here goes. I'm about to do this. I will be back shortly with how it went either from this phone or my backup phone.
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Ok here goes. I'm about to do this. I will be back shortly with how it went either from this phone or my backup phone.
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Tell me what you are flashing first and I'll verify it for you if you want.
Droidriven said:
Tell me what you are flashing first and I'll verify it for you if you want.
Click to expand...
Click to collapse
I flashed this and the screen flashed the whole time with the TWRP screen and the file images over it. I could see an "ok" option and pressed it. When I went to reboot, TWRP said there was no os installed, so I went back and wiped and reinstalled MOAR. Now I can't install titanium. I get some kind of error. Did I lose root?
Droidriven said:
Tell me what you are flashing first and I'll verify it for you if you want.
Click to expand...
Click to collapse
I didn't download the md5 file because I didn't see one
Mablemae said:
I didn't download the md5 file because I didn't see one
Click to expand...
Click to collapse
The file may have its own md5 sum attached to it instead of a separate md5.
As for the issue with Titanium Backup, you don't need root to install it but you do need root to restore the stuff you backed up in Titanium Backup.
When I asked about what you flashed, I was asking for links to what you used so I could go there to where you got it and see if its for your device or not and what might need to be done with it to make sure it comes out right, in other words, I'll check to see if requires the modem you spoke of.
If you think you lost root, download SuperSU.zip and flash that in recovery like you did the ROM and you should have root.
When I ask you questions I need the answer, not partial responses. If you don't give me the answers I need about exactly what you're using and what you're doing, it makes understanding any issues you might have a little harder to understand and troubleshoot. Work with me and I'll work with you.
Mablemae said:
I didn't download the md5 file because I didn't see one
Click to expand...
Click to collapse
That screenshot you gave me is not a ROM. That is a flashable zip to fix your APNs so you that your mobile data works.
This should be your ROM.
https://www.teamoctos.com/download/M_release/d2spr/OCT-M-R2-6.0.1-20160812-d2spr.zip
For the gapps you'll need, do a google search for:
Open Gapps
When you get to their page, select ARM(not ARMx64), then select 6.0, then select mini, pico or nano packages then download.
You have to flash the Gapps with your ROM, they are system apps, apps you install aren't system app, they're user apps, different animal. When flashing a ROM different than what you have you can't use Titanium Backup to back up system apps because they won't restore properly in your new ROM, especially when going from one android version to another.
Flash the Gapps and then only restore apps that you downloaded from Playstore.
The link I gave you was to the thread for your ROM, it should the info you need to know to flash it.
By the way, when you flashed and it said you had no OS, that's because of the advanced wipe when you wiped system partition in recovery, I told you that it removes your OS and that you'll have to flash the ROM AFTER doing the wipe, you can't flash and then do the wipe, that wipes what you flashed.
Droidriven said:
That screenshot you gave me is not a ROM. That is a flashable zip to fix your APNs so you that your mobile data works.
This should be your ROM.
https://www.teamoctos.com/download/M_release/d2spr/OCT-M-R2-6.0.1-20160812-d2spr.zip
For the gapps you'll need, do a google search for:
Open Gapps
When you get to their page, select ARM(not ARMx64), then select 6.0, then select mini, pico or nano packages then download.
You have to flash the Gapps with your ROM, they are system apps, apps you install aren't system app, they're user apps, different animal. When flashing a ROM different than what you have you can't use Titanium Backup to back up system apps because they won't restore properly in your new ROM, especially when going from one android version to another.
Flash the Gapps and then only restore apps that you downloaded from Playstore.
The link I gave you was to the thread for your ROM, it should the info you need to know to flash it.
By the way, when you flashed and it said you had no OS, that's because of the advanced wipe when you wiped system partition in recovery, I told you that it removes your OS and that you'll have to flash the ROM AFTER doing the wipe, you can't flash and then do the wipe, that wipes what you flashed.
Click to expand...
Click to collapse
Yes I wiped, then flashed. This is the path I took that got me to what I flashed
http://forum.xda-developers.com/showthread.php?t=3033797.
On the first page in the thread, I found a link that said it was stable and followed it for my phone.
I only backup user apps to titanium because I did read that system apps can cause problems when carried over to a different rom. Sorry about the lack of information.
Mablemae said:
Yes I wiped, then flashed. This is the path I took that got me to what I flashed
http://forum.xda-developers.com/showthread.php?t=3033797.
On the first page in the thread, I found a link that said it was stable and followed it for my phone.
I only backup user apps to titanium because I did read that system apps can cause problems when carried over to a different rom. Sorry about the lack of information.
Click to expand...
Click to collapse
OK, I'll check out some details and see what might have happened when you flashed. Doing the wipes a d then flashing ROM then Gapps should have worked with no issue, let me do some digging to see why it didn't.
Droidriven said:
OK, I'll check out some details and see what might have happened when you flashed. Doing the wipes a d then flashing ROM then Gapps should have worked with no issue, let me do some digging to see why it didn't.
Click to expand...
Click to collapse
Stop digging. The apps started downloading, but I'm going to try what you sent me tonight when I get off
Mablemae said:
Stop digging. The apps started downloading, but I'm going to try what you sent me tonight when I get off
Click to expand...
Click to collapse
Ok, I'm chatting with my OctOS colleagues, some of them have had d2spr, hopefully they remember whether there is anything special you need to do. I have helped others with d2spr but its been a year or more so I don't remember details.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey how's it goin' guys! This is my first ever ROM I built, so here it is! Introducing AeroROM!
DISCLAIMER: You should bear in mind that flashing this Custom ROM will void your warranty. Therefore, I am not in any way responsible for any damages (Bricks, Fried Accessories, etc.) that may occur from performing these modifications. You are choosing to do this, it's not me forcing you to flash this ROM, lol
FEATURES
Systemless Root w/ SuperSU (Which is why you don't see "KERNEL IS NOT SEANDROID ENFORCING" at boot)
Built In BusyBox
Killed Knox
Obliterated all unnecessary Samsung bloat
DeOdexed apps
DPI Tweak for more screen real-estate
More under-the-hood build.prop tweaks for improved overall performance
Minimal AeroROM breathing boot animation so it doesn't attack your eyes
Lightweight, Fluid, and Snappy
INCLUDED APPS
Viper4Android FX | A feature-packed EQ app For an enhanced audio experience
Nova Launcher | One of the most widely used launchers
ES File Explorer | An advanced file explorer app, includes root browsing
UC Mini | A reliable web browser
SuperSU | Root management
(New with v1.1) AdAway | Blocks Ads
COMPATIBLE DEVICES
Samsung Galaxy Core Prime MetroPCS variant (SM-G360T1)
And *possibly* the T-Mobile variant (SM-G360T), I do not own it so I would definitely appreciate someone confirming that for me.
INSTALLATION
1 Make sure you have the right device, if you do then you may proceed.
2 Install Root and TWRP if you haven't already
3 Copy the ROM and GApps .zip files to your Internal SDCard
4 Now this is the fun part, lol. Reboot into your recovery, swipe to allow modifications if you haven't already. Then perform a factory reset by wiping the Data, Dalvik/ART Cache, Cache, and System. Once that's out of the way, flash the ROM itself first, then the GApps package.
5 Hit Reboot. Then STOP RIGHT THERE! Once the part that says SuperSU doesn't appear to be installed, hit the Do Not Install button. SuperSU does come with this ROM, it's just the method of installation.
6 Proceed with rebooting, and give it a couple of minutes. It takes this long to boot because of the DeOdexed nature of the ROM, but don't worry, this only happens once!
7 Now it's all yours to enjoy!
You can use either TWRP 2.8.70 or 3.0.1, they both work well in flashing this ROM
GAPPS
To keep a minimal file size, GApps were removed as part of the debloat process. You can get some really good GApps packages from Opengapps.org. Be sure to choose ARM as the Platform, 5.1 as the Android Version, then the GApps flavor is all up to you!
DOWNLOAD
v1.1b
https://mega.nz/#!c1AngIqb!_ZD3kHda2EmvrI9tvqgwPPuu7n2w4nCl9SWMTFiF-9U
SPECIAL THANKS
@ShinySide | TrapKernel Root Kernel
@SuperR | For his Kitchen
@Chainfire | For SuperSU
@ViPER520 | For the Viper4Android FX Mod
XDA:DevDB Information
AeroROM, ROM for the Samsung Galaxy Core Prime
Contributors
FazPhantom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 5.1.1 Stock w/ Root & TWRP
Based On: TouchWiz Stock [AOFA]
Version Information
Status: Stable
Created 2017-05-07
Last Updated 2018-03-31
LATEST
v1.1b - This update reverts the Google WebView debloat which causes some users to stay stuck in the checking info screen. Hopefully this update resolves everything.
KNOWN ISSUES
WiFi Calling + VoLTE unavailable.
PREVIOUS
v1.1 - Fixes broken Mobile Hotspot and adds AdAway Ad blocker
v1.0 - Initial Release
KNOWN ISSUES
Mobile Hotspot doesn't work. Will be fixed ASAP.
EXTRAS
Get the newest emojis on your device!
Samsung's firmware for this phone in particular comes with a set of outdated emojis that may interfere with how you see various emojis, new and old, that may be on your screen. Some new emojis come as black boxes, which isn't really good. Therefore, I'll walk you guys through updating the emojis on this ROM (or whatever ROM you may be using on this device)
Prerequisites: Any root explorer app and root access.
1: Choose your emoji flavor. Some of them are...
EmojiOne (Select emojione-android.ttf)
Android Oreo
You are not limited to these options!
Now, make sure the emoji file you downloaded is a font file (.ttf) and rename it to NotoColorEmoji (That should already be the case if you downloaded the Android Oreo emojis)
Head into system/fonts and back up the existing NotoColorEmoji to somewhere else. Then go back to the new emojis you just downloaded, and move that over to system/fonts.
Lastly, set the permissions of the font file to rw-r-r so the system can detect the new set of emojis. This is important, otherwise it won't work.
Now restart your device, and boom, enjoy your brand new emojis! Use with Gboard for best results.
Any New User Interface? Screen shots please?
Kani08 said:
Any New User Interface? Screen shots please?
Click to expand...
Click to collapse
Screenshots are now in the screenshots tab.
I will try it when I have time however I can say rather confidently that this will work on the SM-G360T. The two phones are exactly the same with different branding.
FazPhantom said:
Screenshots are now in the screenshots tab.
Click to expand...
Click to collapse
OK kool, I am waiting for more users to test before I try it.
Anyone tried it as yet? How's it going so far?
Kani08 said:
Anyone tried it as yet? How's it going so far?
Click to expand...
Click to collapse
I'm personally running my own ROM on my own Core Prime and so far so good! Didn't notice any issues with calling or LTE or WiFi or any of the much needed stuff.
FazPhantom said:
I'm personally running my own ROM on my own Core Prime and so far so good! Didn't notice any issues with calling or LTE or WiFi or any of the much needed stuff.
Click to expand...
Click to collapse
Where is the link to download? If it's that good then share it. Thanks.
Kani08 said:
Where is the link to download? If it's that good then share it. Thanks.
Click to expand...
Click to collapse
Lol it's in the post itself, the link with the mega.co.nz, that's where you can download the ROM
35 Minutes, and still only see AEROROM. Vibrations occur every few seconds, like 15s. Tried first without wiping DATA, and then was taking excruciatingly long, so I went back and wiped everything twice, and then re installed without GAPPS, and 35 minutes so far. Will report any further changes. BUt honestly, this phone bootloops for literally nothing mostly. Haven't had such an unstable Samsung device ever. Kinda hate this phone now, always fixing, never can get calls or anything. Bout to just toss it in the trash. I appreciate the work you've done op, thank you. I've been looking, but is there anyway to port Resurrection Remix 5.7.4 from the 360h over to this phone, It's my personal favorite rom, and on every device since it dropped. I dont mind spending a few hours trying, but I can't build it from source.
Lucairian said:
35 Minutes, and still only see AEROROM. Vibrations occur every few seconds, like 15s. Tried first without wiping DATA, and then was taking excruciatingly long, so I went back and wiped everything twice, and then re installed without GAPPS, and 35 minutes so far. Will report any further changes. BUt honestly, this phone bootloops for literally nothing mostly. Haven't had such an unstable Samsung device ever. Kinda hate this phone now, always fixing, never can get calls or anything. Bout to just toss it in the trash. I appreciate the work you've done op, thank you. I've been looking, but is there anyway to port Resurrection Remix 5.7.4 from the 360h over to this phone, It's my personal favorite rom, and on every device since it dropped. I dont mind spending a few hours trying, but I can't build it from source.
Click to expand...
Click to collapse
That's not good, I think I gotta take this down if it isn't very stable. Weird though, I flashed it on my G360T1 and it booted up just fine. If a few more people report instability in this ROM then I'm taking it down, I've given up hope, CM or lineage won't be built for it at all, I doubt it'll happen at all.
But yeah what I would do is wipe every single thing including internal storage, then turn the phone off, flash stock firmware via Odin, and it should be able to fix things up
FazPhantom said:
That's not good, I think I gotta take this down if it isn't very stable. Weird though, I flashed it on my G360T1 and it booted up just fine. If a few more people report instability in this ROM then I'm taking it down, I've given up hope, CM or lineage won't be built for it at all, I doubt it'll happen at all.
But yeah what I would do is wipe every single thing including internal storage, then turn the phone off, flash stock firmware via Odin, and it should be able to fix things up
Click to expand...
Click to collapse
Went go take a bath, and phone is still on AEROROM, slowly fading in and out. I'm going to put stock and try from there. I'd really like a different rom other than SLIM PICKINS. Effing gravitybox causes bootloop, can't theme it black like every other device, even though I do a bit of **** for TBO, but not offically, I just want evrything to be black, but everything I try crashes and bootloops. Good thing I got this phone for free from a repair job. I appreciate your working on a new rom though, hopefully I can get it to work. I'll see if I could pull a logcat for you. Someone needs to dev a phone emulator so people like us could test on devices. I was all excited to see this, so I'll blow through a few hours, and anything I can devise from it, I'll post for you. Maybe together something might happen. I'd hate to see you have to pull it.:crying:
EDIT: Does the versions of twrp that are available work well on your device? Any twrp3 I put, the touch refuses to work. So I'm stuck on 2.8.7.0. blows dogs for quarters...
Lucairian said:
Went go take a bath, and phone is still on AEROROM, slowly fading in and out. I'm going to put stock and try from there. I'd really like a different rom other than SLIM PICKINS. Effing gravitybox causes bootloop, can't theme it black like every other device, even though I do a bit of **** for TBO, but not offically, I just want evrything to be black, but everything I try crashes and bootloops. Good thing I got this phone for free from a repair job. I appreciate your working on a new rom though, hopefully I can get it to work. I'll see if I could pull a logcat for you. Someone needs to dev a phone emulator so people like us could test on devices. I was all excited to see this, so I'll blow through a few hours, and anything I can devise from it, I'll post for you. Maybe together something might happen. I'd hate to see you have to pull it.:crying:
EDIT: Does the versions of twrp that are available work well on your device? Any twrp3 I put, the touch refuses to work. So I'm stuck on 2.8.7.0. blows dogs for quarters...
Click to expand...
Click to collapse
I'm not necessarily developing a totally AOSP-based ROM as this is a totally different case for me, but I'm getting used to making these stock-firmware based ROMs
And the twrp 3.0.1 I used was made by another dev, not downloaded from the official twrp site so I can give you the link to it if you're interested:
https://www.androidfilehost.com/?fid=24459283995316038
I need a rom for my galaxy core prime that will change the UI and optimize performance. I need more ram free. I have version 360gt1 core prime.. Any Miui roms etc available?
Kani08 said:
I need a rom for my galaxy core prime that will change the UI and optimize performance. I need more ram free. I have version 360gt1 core prime.. Any Miui roms etc available?
Click to expand...
Click to collapse
What's really stupid is that it's 2017, it's been rooted, and there still hasn't been any AOSP ROMs such as Lineage or MiUI made for it yet. Like, has this phone been abandoned?
FazPhantom said:
I'm not necessarily developing a totally AOSP-based ROM as this is a totally different case for me, but I'm getting used to making these stock-firmware based ROMs
And the twrp 3.0.1 I used was made by another dev, not downloaded from the official twrp site so I can give you the link to it if you're interested:
https://www.androidfilehost.com/?fid=24459283995316038
Click to expand...
Click to collapse
Dude, thank you. I had already visited and downloaded that one, but it never worked, until last night. OK, so I tried multiple things, wiped every single partition clean, installed stock, (and didn't on the 2nd try) and tried using my own boot.img, and multiple other files, ended up falling asleep with phone in hand, Woke up to still AEROROM fading in and out.
I have a few jobs (I do pc, cell phone repair) and then gotta go sight in a rifle for my cousin today, so I won't be back and able to continue testing today. So sorry I cannot help further for the day.
I have a favor to ask, although technically, you've done a eff-ton for me by the twrp3 thing, but I would completely understand if you don't have time, or would rather not. You know the themes for twrp, fichl's flashable? If you know them, there's a multitude of colors, and bird333's darker purple theme, is my ****, ya knoso if you could possibly get me a flashable version of your bootanimation of AEROROM, (esp with the O with the slash, as that's how I write mine irl) in that color, I would be frigging ecstatic. And I feel like an ass, but if you would do that, I have a very small request to add to that, if you could possibly add my logo to the bottomof the bootanimation, I would flip out. I custom the **** out of everythingbut have yet to work on sammys, so it would be a massive learning curve for something so "simple" and I only ask because you technically have all the resources available to do so. If it's too much trouble, No problem, I totally totally, understand, but grateful is not strong enough of a word to express how I would feel. It's not that I want to "take" your work, it's just that it's an extra thing that gets people wanting me to do those type of things for them, since I'm unemployed,trying to start a small busisness, but I'm a total recluse, so pimped out phone is a great convo starter for me. Geez, Ik I'm rambling, but just woke up. I'll attach my emblem which is just the matrix font, on a matrix bgrnd, of XIIIMACHINE, because I'm not artistic. Sorry to type your, or rather everyone's head off here. sorry! Hopefully, this Rom can get sorted out, and as soon as I get home tonight, I will jump on it, give a hand wherever possible.
Thank you very much for your work, and effort. Keep it up.
https://drive.google.com/open?id=0B5n3TgqFg-TyWEM1aDdxTVRfN2s
https://drive.google.com/open?id=0B5n3TgqFg-TycGF6cTFReWpaYVU
Please make Lineage OS for Samsung Galaxy Core Prime SM-360T1
Doesn't pass
On the tmobile varient (SM-G360T), it doesn't get passed on the "checking info" transition when setting up the device for the first time.
This ROM is Going to be Primary Based on LineageOS 15.0 source or ROM compiled with Base as LineagesOS 15.0
I am going to regularly compile it and going to share it with community over here
Features of This ROM Based on LineagesOs 15.0
Customizable Theme Engine (Blend with Substratum)
Picture in Picture Mode of Android Oreo
Notification Dots
New user interface in Settings
Split Screen
Improved battery life
Notification Snoozing
Android Oreo Navbar
New UI in Status Bar and Quick Tiles
New Emojis based on Android Oreo
And much more.
Download
For Nexus 6 Android file Host
Gapps For Oreo
Opengapps You can get that from Oppengapps.org
Gaapps For 8.1 Till Open gapps start official Build
The Build is from @Nezorflame And Gapps downlod from
Do NOT expect daily builds. I'll build when I'm free.
Do NOT use this unofficial build and ask for support at the official threads.
Do NOT be rude.
Respect all users
If you see a NOOB question and you don't feel like replying, DON'T, just ignore that post. If you do reply, good for you.....and be nice in your reply.
1st Time Installing
You Need To have Rooted and Custom Recovery Installed Phone To Use This ROM
If you are New Just Go To This Thread and Download Wug's Nexus Tool Kit And Follow Instructions.
Once Custom Recovery Installed. TWRP 3.1.x recommended
Download the zip
Download Gapps
WIPE DATA/FACTORY RESET
Install Modem/Firmware Update
Install the update zip from recovery
Install Gapps
flash Magisk14.1 or 14.0 .zip
Reboot
Already Using the Previous Version of Same ROM
Download the zip
Install latest zip from recovery
wipe Cache
Reflash Gapps
Flash Magisk
Reboot
Credits:
LineagesOs team
CRdroid Team
ScottHeart BTi
He][razor
Vortex 1969
neobuddy89
XDA Developers community
The users and all developer of XDA who has helped me direct or indirect way
Google for Android.
If I miss someone Here please point it out to me.
Source
https://github.com/LineageOS/
https://github.com/crdroidandroid
XDA:DevDB Information
SourceBuilt ROM for Nexus 6, ROM for the Nexus 6
Contributors
chineel, chineel
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Beta
Created 2017-10-28
Last Updated 2017-10-28
Hi everyone The ROM Upload is still On
I have two build Ready One is LineagesOs unofficial and second One CrDroid4.0 which is also based on LineageOs 15.0
Both Got Uploaded
first is Crdroid
crDroidAndroid-8.0-20171028-shamu-v4.0.zip
Second One is LineagesOs-15.0
lineage-15.0-20171028-UNOFFICIAL-shamu.zip
Both Rom are unofficial nothing official about it.
For best error free opration you need to have it Clean Installed
means
Factory reset
wipe
System, Cache,
Flash ROM
Flash Gapps
Flash Magisk / Super Su for rooting
Wait for a while
let it get settled
Enjoy the New Oreo 8.0
11/07 Build Onwards forced encryption is removed so your data by default is not encrypted anymore.
For all those having trouble booting should follow below steps.
get ADB fastboot installer from here
Take back up of everything including DCIM and TWRP or TITANIUM or SMS contact backup or any other.
reboot to bootloader.
open command prompt.
fastboot format userdata (This will format everything on internal storage and will recreate data partition)
wait till success message.
reboot to recovery
wipe system cache data (if you like to but not needed this time)
flash ROM
Flash Gapps of your choice.
wipe dalvick and cache
Reboot
wait for a while
let your phone settle for some time.
reboot to recovery again
flash magisk
reboot
Enjoy your phone unencrypted and fresh as new. Connect to pc copy back your data
restore back whatever you want to restore enjoy.
3rd one
i may Need this one also
Great work! Had any issues with random reboots?
rebel1699 said:
Great work! Had any issues with random reboots?
Click to expand...
Click to collapse
No No reboot since yesterday on my phone
chineel said:
No No reboot since yesterday on my phone
Click to expand...
Click to collapse
Good deal. Will install in the morning and test it out. Again, great work to help keep shamu alive
Hey man thanks for the efforts, a little OT question tho, i saw you got a crDroid build on AFH, are you the new maintainer? edit: Oops, just read the 2nd post ^^ .
gr3ud said:
Hey man thanks for the efforts, a little OT question tho, i saw you got a crDroid build on AFH, are you the new maintainer? edit: Oops, just read the 2nd post ^^ .
Click to expand...
Click to collapse
I am going to request for that if I can continue compiling this ROM but till then Unofficial only
Downloading now. Pretty excited since I'm currently running crdroid.
Do you keep a changelog you're willing to share?
Schiben said:
Do you keep a changelog you're willing to share?
Click to expand...
Click to collapse
For CRdroid already in ROM About section attached here also
Lineageos changelog https://www.lineageoslog.com/15.0
Thank you very much for your great work ? I like this rom
I will try LOS version tonight. Any known bluetooth or Mobile data issues so far ?
Thanks for the effort and appreciate the continued update for Nexus 6.
Hi, I appreciate the effort. Mind telling us the differences between ROMs though? Does the CR one have more features than the stock based Lin one? Still going to test them both but was just wondering, thanks.
mobile data is ON by default, and even when you're connected with Wifi, it still uses your data. Blew thru my 200meg Free T-mobile trying to finish an install. Also, found that NFC is turned off. Might be a driver issue.
Battery life is OK. Sound is bad on my device. Playing some youtube videos, and the sound goes from very loud, to I can barely hear it, plus the only speaker working, is the top, the bottom one cuts in and out. (at least in youtube)
not a bug report, or any disrespect to the dev. but, its just what I've had happen while using this rom.
newsguy99 said:
mobile data is ON by default, and even when you're connected with Wifi, it still uses your data. Blew thru my 200meg Free T-mobile trying to finish an install. Also, found that NFC is turned off. Might be a driver issue.
Battery life is OK. Sound is bad on my device. Playing some youtube videos, and the sound goes from very loud, to I can barely hear it, plus the only speaker working, is the top, the bottom one cuts in and out. (at least in youtube)
not a bug report, or any disrespect to the dev. but, its just what I've had happen while using this rom.
Click to expand...
Click to collapse
Mobile data can be stopped from developer options and untick mobile data always on
steps
1 Open about Phone
2 Go to build number
3 Tap continuous till you got message you are now developer.
4 Tape on Back button
5 You will be seeing Developer options now
6 scroll down till you see mobile data always on toggle it off
Bluetooth issue was found for me when connected to my head unit in my truck. It connects, blurps sound out for half a second and then nothing the songs/videos(videos also go down to like 2 fps while paired) are still playing during but no audio. It's late I just got home will try to capture a log tomorrow. Other than that this rom is butter smooth, thanks for your hard work keeping our old whale swimming. Plz remove if it needs to be I won't be butthurt about it.
Xd great work!