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.
Related
The phone has been working great on Android 4.1.2 as I describe in the thread ( Optimizing [Rom][I605VRAMC3][4.1.2])
Found Here: http://forum.xda-developers.com/note-2-verizon/help/rom-optimizing-t2817294
EXCEPT NOW, every time I boot the phone, I get a message that says All the APPS are upgrading automatically . I think the problem is related to me Using Titanium Backup to Freeze SDM 1.0 . The reason I froze SDM 1.0 was to stop the Nag from Verizon for a firmware update .
Anyone know what I need to freeze to stop the auto upgrading on every boot? It really slows down the boot time.
Thanks in advance
You probably did this already, but double check to make sure Play Store is not set to Auto Update apps. Can. be found in Play Store. settings. I don't believe that freezing SDM would play a role here, but I've been wrong before.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
You probably did this already, but double check to make sure Play Store is not set to Auto Update apps. Can. be found in Play Store. settings. I don't believe that freezing SDM would play a role here, but I've been wrong before.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks , Play Store was set to auto update so I changed it , I just tried your suggestion and I rebooted . I'm still getting the same message while booting: Android is updating.............................................................................
doctor-cool said:
Thanks , Play Store was set to auto update so I changed it , I just tried your suggestion and I rebooted . I'm still getting the same message while booting: Android is updating.............................................................................
Click to expand...
Click to collapse
Hmmmm.... It's probably still working on updating apps that it started working on previous to disabling the auto update.
This might work..... Toggle off your wifi and data, then try going to phone Settings, Application manager, All Apps... then force close the Play Store and wipe the app data. Then open the Play Store again and it should go straight to settings area. Set it to " Do not Auto Update apps " and then back out of Play Store, turn wifi/data back on, and go back into Play Store and sign into the app again/change any other settings back to how you like them . I hope that will stop the auto update.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
Hmmmm.... It's probably still working on updating apps that it started working on previous to disabling the auto update.
This might work..... Toggle off your wifi and data, then try going to phone Settings, Application manager, All Apps... then force close the Play Store and wipe the app data. Then open the Play Store again and it should go straight to settings area. Set it to " Do not Auto Update apps " and then back out of Play Store, turn wifi/data back on, and go back into Play Store and sign into the app again/change any other settings back to how you like them . I hope that will stop the auto update.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
doctor-cool said:
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
Click to expand...
Click to collapse
For a test,
I cleared data and disabled the Play Store, Turned off data and wifi . REBOOTED I'm still getting the same message while booting: Android is updating.......................................... ...................................
Now I'm thinking the problem is due to me flashing Gapps.
I flashed (HDPI / MDPI / TINY: gapps-jb-20121011-signed.zip) for Android 4.1.1 – 4.1.2 – Jelly Bean, from http://www.teamandroid.COM/gapps/
I probably shouldn't have flashed it on top of the official stock 4.1.2 Verizon ROM. I probably have two version of Gapps on my phone competing with each other. The quickest thing would probable be to re-flash to the OEM [Rom][I605VRAMC3][4.1.2]
doctor-cool said:
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
Click to expand...
Click to collapse
Ok.... I just realized that this has nothing to do with the Play Store App or updating your apps.... Your actual phone system is optimizing at boot screen.... like this pic, right?
Sent from my SCH-I605 using XDA Premium 4 mobile app
I'm not in any way a developer or expert.... this stuff is just a hobby for me...so please understand these are just my thoughts to hopefully help and not make things worse for you. With that said, I suspect you have an app or script (or something) that is doing something like wiping the Dalvik cache with each reboot, which is triggering your phone to run through the optimization process each time you boot. I am pretty confident this has nothing to do with SDM being frozen. I'm not sure about gapps with stock. Why do you need that if your running stock?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Anyhow, What ROM do you recommend ? I'm using my phone to do Wave Accounting and Pay Pal transactions so I cant have down time.
doctor-cool said:
Anyhow, What ROM do you recommend ? I'm using my phone to do Wave Accounting and Pay Pal transactions so I cant have down time.
Click to expand...
Click to collapse
Sorry for being off base with my initial thought on your above post... It's been a long week at work and I'm tired.... so that's my excuse...
I hope you get it sorted out with what's causing your phone to upgrade/optimize apps at each reboot. I did a Google search just now and apparently, this is common issue asked on XDA. I found several comments from people saying they think something causes the Dalvik/Cache to get wiped on reboot. I also read where someone reported that flashing Gapps did the same thing to them. If you're going to flash a new ROM, that should take care of the problem when you wipe things for the new flash.
On the XDA forums, it's generally frowned upon to ask for ROM recommendations. But for me personally, I have decided to settle (for now) on Beanstown106's JellyBeans ROM Build 22 which is based off of 4.1.2. I think this was the last 4.1.2 based Rom (for our SCH-I605's) that he did for his JellyBeans ROM before he moved on to developing for 4.3 MJ9, so I think a lot of the bugs were worked out of it.
I love the ROM and I've tried out several others. I always end up coming back to it because it's really stable and (pretty much) everything works. And with Xposed Modules and his built in options, I can tweak everything to how I like it.
You can still grab his older JellyBeans ROM build 22 by going to the current Alliance Rom Thread here: ( http://forum.xda-developers.com/showthread.php?t=2032447 ), and then going to the "Downloads" area right above the thread title. The ROM Filename is: note2_JellyBeans_B22.zip.
There's tons of great ROM's for our phone and there's so many talented developers..... so I truly think you have to read through the threads on each of the ROM's to make a decision for your personal needs... but I know that JellyBeans Build 22 is very stable if that's what you're wanting. If you decide to try out JellyBeans Build 22, let me know if you need help with instructions for flashing it. I saved the install instructions for future reference when I flashed it the first time last year, but I don't see those old install instructions any place now that he's moved on to developing for the updated 4.3 build.
mattnmag said:
Sorry for being off base with my initial thought on your above post... It's been a long week at work and I'm tired.... so that's my excuse...
I hope you get it sorted out with what's causing your phone to upgrade/optimize apps at each reboot. I did a Google search just now and apparently, this is common issue asked on XDA. I found several comments from people saying they think something causes the Dalvik/Cache to get wiped on reboot. I also read where someone reported that flashing Gapps did the same thing to them. If you're going to flash a new ROM, that should take care of the problem when you wipe things for the new flash.
On the XDA forums, it's generally frowned upon to ask for ROM recommendations. But for me personally, I have decided to settle (for now) on Beanstown106's JellyBeans ROM Build 22 which is based off of 4.1.2. I think this was the last 4.1.2 based Rom (for our SCH-I605's) that he did for his JellyBeans ROM before he moved on to developing for 4.3 MJ9, so I think a lot of the bugs were worked out of it.
I love the ROM and I've tried out several others. I always end up coming back to it because it's really stable and (pretty much) everything works. And with Xposed Modules and his built in options, I can tweak everything to how I like it.
You can still grab his older JellyBeans ROM build 22 by going to the current Alliance Rom Thread here: ( http://forum.xda-developers.com/showthread.php?t=2032447 ), and then going to the "Downloads" area right above the thread title. The ROM Filename is: note2_JellyBeans_B22.zip.
There's tons of great ROM's for our phone and there's so many talented developers..... so I truly think you have to read through the threads on each of the ROM's to make a decision for your personal needs... but I know that JellyBeans Build 22 is very stable if that's what your wanting. If you decide to try out JellyBeans Build 22, let me know if you need instructions for flashing it. I saved the install instructions for future reference when I flashed the first time last year, but I don't see those old install instructions any place now that he's moved on to developing for the updated 4.3 build.
Click to expand...
Click to collapse
Thanks and right on time, After I did my return to stock I thought I needed to wipe both caches' and the system to be able to do a Titanium backup.
I lost my operating system and Odin didn't recognize my phone, I was looking for a 4.1.2 zip file at the time I found your post. THANKS!
I'm downloading now
doctor-cool said:
Thanks and right on time, After I did my return to stock I thought I needed to wipe both caches' and the system to be able to do a Titanium backup.
I lost my operating system and Odin didn't recognize my phone, I was looking for a 4.1.2 zip file at the time I found your post. THANKS!
I'm downloading now
Click to expand...
Click to collapse
When you say you returned to stock, I'm hoping you didn't ODIN flash a full stock version of 4.1.2, because that would have relocked your bootloader and removed the custom recovery and root. If you were able to use Advance wiping features, you must still have some sort of custom recovery on your phone.
Hopefully, you do so you can flash a zipped ROM back onto it. If you've still got an unlocked bootloader and have a custom recovery, you may want to try to flash this root/modified version of "stock" 4.1.2:
( http://forum.xda-developers.com/showthread.php?t=2261478 ). It was also made by Beanstown106 and the thread still has instructions.
Also, you may do some Google searching to find tips on how to get your computer/ODIN to recognize your phone in download mode again... the most common tips I've seen are to try to uninstall and reinstall the Samsung drivers on your computer...and to try different USB cables and different USB ports on the computer.
I'm exhausted and I'm going to bed, but here are the original install instructions posted by Beanstown106 for JellyBeans ROM Build 22 if needed.
------------------------
"(INSTRUCTIONS) YOU MUST BE UNLOCKED
Step 1-
Make sure u are unlocked
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom (flash it in your custom recovery)
Step 4-
Reboot and Enjoy!"
-------------------------------------
Hope that helps. (Also, if Beanstown's stuff helps you... I'd encourage you hitting the thanks button for all his hard work )
mattnmag said:
When you say you returned to stock, I'm hoping you didn't ODIN flash a full stock version of 4.1.2, because that would have relocked your bootloader and removed the custom recovery and root. If you were able to use Advance wiping features, you must still have some sort of custom recovery on your phone.
Hopefully, you do so you can flash a zipped ROM back onto it. If you've still got an unlocked bootloader and have a custom recovery, you may want to try to flash this root/modified version of "stock" 4.1.2:
( http://forum.xda-developers.com/showthread.php?t=2261478 ). It was also made by Beanstown106 and the thread still has instructions.
Also, you may do some Google searching to find tips on how to get your computer/ODIN to recognize your phone in download mode again... the most common tips I've seen are to try to uninstall and reinstall the Samsung drivers on your computer...and to try different USB cables and different USB ports on the computer.
I'm exhausted and I'm going to bed, but here are the original install instructions posted by Beanstown106 for JellyBeans ROM Build 22 if needed.
------------------------
"(INSTRUCTIONS) YOU MUST BE UNLOCKED
Step 1-
Make sure u are unlocked
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom (flash it in your custom recovery)
Step 4-
Reboot and Enjoy!"
-------------------------------------
Hope that helps. (Also, if Beanstown's stuff helps you... I'd encourage you hitting the thanks button for all his hard work )
Click to expand...
Click to collapse
Thanks I used JellyBeans ROM build 22 just to have a system so that I could get to Odin. Then I did flash the full stock version of 4.1.2 then I used the Casual method to unlocked the boot-loader and reinstall WIN recovery and root. As explained here http://forum.xda-developers.com/note-2-verizon/help/rom-optimizing-t2817294. ( I ran into some driver issues between Casual and Odin but they were resolved)
Actually I have three Samsung i605's.
I have one that has got all the Verizon OTA updates, never tampered with it's on 4,4,2.
I have the one we have been talking about I have restored it to the fully stock version of 4.1.2 with Root.
And the last one I am experimenting with DN3 (Ditto Note 3) for fun and knowledge.
doctor-cool,
That's great. Glad you got it fixed.
And that's pretty cool to have extra devices to work with. Must be nice.
Sent from my SCH-I605 using XDA Premium 4 mobile app
S6.Port-Version.V1 ,
there may be things that are not completely functional. I NOT responsible for any damage to your device or your information.
I can not scream loud enough YOU MUST INSTALL CLEAN NO DIRTY FLASH . .
I know you will have to set up all your apps oh well get over it !
wipe ALL and FORMAT (backup any needed data cuz format will erase it) [/SIZE] [/SIZE] [/SIZE][/COLOR][/COLOR][/SIZE]
ROM Information
**S6 Edge 5.1.1 Base
**Dev options on boot
** 5 Way Reboot Menu
***********************
From the stock N4 Edge
Added The Edge Screen ( Not all Options Working)
Added Adway
Added Dolby
Added kernel Adiutor (Test AT YOUR OWN RISK:silly:
Build Properties Tweks
Google DNS
camera_tweaks
Improve_battery
And More
SPECIAL THANKS TO THESE GUYS WITHOUT THEM THIS WOULDN'T BE POSSABLE
FREEZA =KERNEL
SAC23=FOR THE ROM
GEITI94
R-MILLER
GABESIR
Installation:
FOR ALL YOU NOOBS FLASHING ROM AFTER YOU DO A FULL CLEAN YOU NEED TO REBOOT YOUR RECOVERY OR WILL GIVE ERROR ......
(2) THE STATUS BAR CLOCK IS NOT MISSING ---YOU NEED TO GO TO SETTING /NORMA/SETTING/POTATO/CLOCK/CLOCK COLOR...PICK YOU COLOR /NEXT ALIGMENT..MOVE THE CLOCK TO THE LEFT /CENTER/ OR RIGHT
Make a backup ( dont come crying if you didn't)
NO DIRTY FLASH
Copy the rom to your phone
Install ROM (recommended clean wipe)
Wait for the initial boot ( takes 10-15 Mints )
Do Not Use Any Part From This Rom Without Sac23 OR My Permission
ROM LINK
REMOVE LINK WORKING ON A NEW PORT
AFTER YOU DO A FULL CLEAN YOU NEED TO REBOOT YOUR RECOVERY OR WILL GIVE ERROR
LINK
********my****
Good job paco [emoji106]
Downloaded Zip thru phone then redownloaded @ home Via PC still Error'd n TWRP after I transfer'vs zip 2 SDcard
Tried flashing via Twrp & it Error'd again
Said unable to FLASH ZIP due 2 binary error,
So I decide to flash sdcardfix & 'What do you know! Darn thing flash'd and is working perfect....!
1. Issue I've found there's a RED Border that flashs around Google Chrome when browsing
2. Staus bar Clock is missing .........Fix'd
3. I've been driving this ROM for a few hours now it SMOOTH!
It's reboot'd twice on me outta the blue & Top Right corner of phone been getting real hot , if That means anything 2 you. Its still alot better than stock rom heck I couldnt even gain root on stock 4 some reason so no complaints here
Awesome bro! looks nice! =)
Good Job!:good:
have you tried to use the SSU apk in this rom??, i have seen some other have manage to make it work on custom roms and android Lollipop
Tried to flash a few different times, md5 is good. If I Idont wipe anything and flash it boots fine. After that though I get systemUI and phone crashes. How ever though if I wipe there will be an error about symlinks not there.
Bump re'edit'ed 1st Post
Nice ROM
Ty 4 building this 4 us Sprinter's
whoppe862005 said:
Tried to flash a few different times, md5 is good. If I Idont wipe anything and flash it boots fine. After that though I get systemUI and phone crashes. How ever though if I wipe there will be an error about symlinks not there.
Click to expand...
Click to collapse
ok you need to to reboot the recovery before you flash the rom TWRP recovery give error the the flash zip is ok
ickyz said:
downloaded zip thru phone then redownloaded @ home via pc still error'd n twrp after i transfer'vs zip 2 sdcard
tried flashing via twrp & it error'd again
said unable to flash zip due 2 binary error,
so i decide to flash sdcardfix & 'what do you know! Darn thing flash'd and is working perfect....!
1. Issue i've found there's a red border that flashs around google chrome when browsing
2. Staus bar clock is missing or inoperable
Click to expand...
Click to collapse
(2) the status bar clock is not missing ---you need to go to setting /norma/setting/potato/clock/clock color...pick you color /next aligment..move the clock to the left /center/ or right
Wanna try it ....
Thanks. Finally got it up and running. So far so good. Got xposed and V4A working. Appreciate the work put into getting this over to this sprint variant. Will report back with logs should any issues arise.
i need you guys to test the hotspot see if working and connecting
paco_1 said:
i need you guys to test the hotspot see if working and connecting
Click to expand...
Click to collapse
I don't know if you included the Hotspot mod in this but if you use the method of adding the "dun" to the to APN'S through the sqlite editor the Hotspot works fine.
http://forum.xda-developers.com/not...roid-development/mods-sprint-hotspot-t3086579
This is the mod I am referencing.
Has anyone had any issues with lots of random reboots? Or any issues when using the camara?
kcnlos7 said:
Has anyone had any issues with lots of random reboots? Or any issues when using the camara?
Click to expand...
Click to collapse
Yes I have the same issues & after a few hours of phone being on it constantly rebootes
PEOPLE BE SURE & BACKUP YER PHONE + DATA + EFS & ANY OTHER FILES I know how hard this phones been if you dont backup ur file(s)You will have a paper weight
Is there any other user(s) experiencing the same REBOOTING issue after a few hours of use
I had 2 Backup to stock ROM because soon as it starts this issue , can't do anything but restore
When I ran this rom seemed good than I couldn't get Bluetooth to pair on my vehicle and than I couldn't get it to show anything on the homepage just the wallpaper and I could pull my notifications down but couldn't get settings to open.
I've been a huge fan of sac_23 on my S4 - sooo excited to try this out
Anybody get it to work?
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
1. Must backup your data. You are gonna wipe it
2. Use flashtool and downgrade to a rootkitXperia rootable firmware. I used 26.1.A.1.112 but other rootable should be the same. (wipe data may not be necesary in this step but i did it just in case)
3. When flashing done, root the device with rootkit, and install TWRP
4. Use xperifirm to download the 3.111 FW then create the prerooted with its system.ext4 and kernel.elf
5. Flash the zip via TWRP, wipe dalvik, then start the phone and check that you have superuser, and go about phone to make sure everything went well and your in 3.111 with its kernel also.
6. Use flashtool again to flash 26.1.A.3.111 but you this time you must EXCLUDE SYSTEM and KERNEL to keep the root, in other words your gonna flash everything but kernel and system so be sure you ticked them, also should wipe data so you can start fresh and avoid possible incompatible things.
7. Let the phone starts, mine took around 10 - 15 min. You should now be in 26.1.A.3.111 with root and no random reboots. So far im using it since 12 days and no reboots nor system hangs, ive updated all apps via playstore, and even downloaded several 500Mb+ games and its working really fine
Click to expand...
Click to collapse
Sorry for this guide that isnt noob friendly, im doing it quite hurry because im too busy with work but i wanted to share what worked for me with everyone. If this works for you too and someone wants to do a better noob friendly guide with links and such go ahead it is ok.
[NOTE]Random reboots seems to happen when there are diferent modem versions. Special thanks to @sergioslk who discovered this.
Of course, all credits to the respective developers who worked really hard on this tools for us. Thanks devs.
Hey, thanks. I had 26.1.A.2.167 rooted, so I just installed 3.111 with data wipe through prerooted zip on top of 2.167, and then reflashed everything except for kernel and system (also data wipe here) like you wrote in your post. So far so good - almost 30h without reboot, which is far better than before.
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
fpghost84 said:
Hm, didn't work for me also with 3.111 I reflashed (using stock 3.111 from xperifirm) excluded kern and system but it is still randomly rebooting when installing gapps.
Click to expand...
Click to collapse
Did you first flashed via TWRP the prerooted zip you created with system.ext4 and kernel.elf extracted from 3.111 FW? did you wiped data after completing flash? which version of FW you had just before flash 3.111?
Yeah, I did as you say. My phone orig had 2.167, but it upgraded itself recently to 3.111, then I downgraded to 1.128 to root, before using the prerooted TWRP zip (with system.ext4 and kernel.elf extracted from 3.111 ftf) to upgrade back to 3.111.
EDIT: I think something went wrong when I created the ftf bundle from the files downloaded from xperifirm. I repeated the whole process and now I'm not seeing the random reboots (at least for an hour with quite a few apps installed and updated) ....So yeah in summary many thanks for this ...It would be nice if it was mentioned on the main how to thread.
thewailer said:
Hello.
I was able to fix the random reboots i had with flashing prerooted zip via TWRP, this apply also on the new 26.1.A.3.111, only tested on E2306.
Click to expand...
Click to collapse
Thanks so much for posting this. I had thought of doing this myself but quickly ruled it out because I thought it was a dumb idea (no offense) and wouldn't work, but after hearing of your success I thought I'd give it a try anyways and I've been powering through a ton of app installs/updates and haven't had a single reboot so far. It sounds to me like this is the key.
I'll post an edit after a few days to let you guys know how it holds to my personal test of time.
Thanks again!
Update:
Well, it's been nearly a week now and I've yet to experience a random reboot. This is definitely the fix we've all been waiting for! I hope this knowledge can be spread to all who have been plagued with this issue!
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Hey @sergioslk,
Thanks so much for your contribution. I found your post about this problem but it was kind of hard to read whereas the original poster here went into a bit more detail. Sometimes that's all people need, is a little more information. I'm sure you've made other contributions to the community that have been extremely valuable.
To reitterate, this is definitely the fix to the problem we've all been facing when it comes to using the pre-rooted zip to get root on the latest version. I had suspected this to be the problem awhile ago but couldn't really figure out how to fix it.
Thanks everyone for all your hard work!
sergioslk said:
the random reboots are related to different modem versions, that is why phone reboot when using a hi-speed wifi connection, i said this previously but no one matters :'(
Click to expand...
Click to collapse
Oh dude many thanks for this contribution, i havent readed your post before, but now i can say theres a know reason why the random reboots occurs. Im not an expert in android, i just tried this as a last hope, ive tried everithing, no google account, no wifi, no moibile data, no sdcard, deleting all bloatware, untouching bloatware, a lot of wipes..... and this last one for some reason worked but i wasnt sure why untill now. Thanks again!
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.
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!