[ROM+Kernel][MAY 16, 2020] AOSP direct, Marshmallow 6.0 & NEW kernel, version 3.4.99
****UPDATE****
As of May 16, 2020, If you already have this ROM installed, please see this link for an updated kernel to version 3.4.99 with other various editions and Extras. If you are downloading and installing this ROM for the first time download the ROM and Flash it, and finish setting up your device before updating the kernel. You will have to flash Superuser or Magisk again (or whatever your root preference is) after installing the ROM or boot image regardless of whether you're coming from a fresh installation or updating the kernel.
The number of ROMS for the Nexus 10 has dwindled, and those that do remain, have too many bugs and not everything works. I spent a couple weeks looking for a good ROM and finally found one. I did NOT build this ROM, however I DID build the kernel from scratch.
What you get:
- Android 6.0, Marshmallow ROM built directly from the AOSP source code. (built by Dmitry.GR)
- Freshly updated kernel from 3.4.67 to 3.4.99, built by Me from source. I used the Manta kernel source (3.4.67) from Omnirom's android-6.0 branch and applied the official kernel patches 3.4.67-68 through 3.4.98-99. SELinux in the boot image provided by the ROM is disabled. Standalone updated kernel/boot image is permissive). Kernel in its original form, would not allow for a permissive selinux so the only option was to disable it.
- In the updated boot image, ADB is insecure (ro.adb.secure=0 and ro.secure=0). This allows for an automatic root shell when running 'adb shell'. It also allows you to remount the filesystem RW through ADB, using the command 'adb remount'.
- No swap or zram options on the original kernel because it was not performing properly. This is fixed on the standalone upgrades to the kernel I have been doing.
What doesn't work:
- Location services may or may not work. If they don't, let me know as I do have a fix for that. For some reason, com.google.android.gms was removed from the framework-res (android system apk). Some apps won't recognize the device GPS and may tell you location is turned off when it actually isn't.
- The camera work however oh, there is an issue with the flash. Every time you use flash the camera will crash after snapping the photo. This wouldn't be a problem except the photo doesn't get saved. I don't know what's causing it and until I can figure that out you can't use the flash on your camera.I have a suspicion or two but I haven't looked into it because I don't use the camera often enough and when I realized the problem I'm never at home to look.
Installation requirements and instructions:
Required:
1. Unlocked bootloader
2. TWRP custom recovery
3. PC with either Windows or Linux
Instructions:
1. You need to wipe the device completely. Boot to recovery, select wipe, format data and type yes and confirm. When done, tap home, wipe, advanced wipe, select all and swipe to confirm. Tap home, reboot, reboot recovery.
2. Once booted back to recovery, plug your tablet into your PC. It should be recognized.
3. Download Open Gapps, ARM, 6.0, Pico and place it on the tablet's internal storage.
4. Download the TWRP flashable zip that contains the ROM and place it on internal storage.
5. Download the boot.img which contains the new Kernel, place in storage.
6. Download SuperSU zip and place in storage.
7. Once done, tap the home button then install. Select the TWRP flashable ROM zip and install it. When done tap home again, install, install image and select image-new.img and install.
8. When finished tap home and install and install Open Gapps. When finished install SuperSU then reboot system when finished.
Kernel installation and updates ONLY
1. Download and extract the zImage from the provided zip at the end of the post.
2. You need to unpack the boot image from the ROM above. You can do this on Windows Linux or your own Android device with the Android image kitchen by XDA developer @osm0sis. After unpacking the image, open the folder named 'split image' and locate boot.img-zImage. make a copy of it and put it somewhere safe, then delete it from the split image folder.
3. Now take the zImage you extracted earlier and put it into the split-image folder, and rename it to boot.img-zImage. Repack your boot image which when done, will be default named to image-new.img.
4. Reboot the device into TWRP or the bootloader and flash your new boot image and reboot.
Screen shot below. You now have an awesome Marshmallow ROM and brand new Kernel for your Nexus 10!!
****Change Log****
February 10, 2020: Updated kernel version from 3.4.69 to 3.4.71. kernel patches not fully cooperating with the disabling of SELinux so I had to re-enable it. Simply placing a small script into /system/su.d (or locate wherever your su folder is and inside will be a su.d folder) to set selinux permissive on boot works perfectly. Create a text file called permissive.sh and copy and paste text below and save it to that folder with permissions: 777. If no su.d folder exists, create one in /system with permissions 755.
Code:
#!/system/bin/sh
setenforce 0
Can I dirty flash this with LineageOS15?
ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
I am going to take a guess and say no. Partition layout changes in Android 8 and 9 so probably won't work. I compiled the kernel with AOSP 6.0 gcc toolchain and I have no idea if this kernel can even support 8 or 9. I have to read further on updating the kernel as this is as far as I can update it for now. Any further patches say they're already added so I have to figure out what I am doing wrong. Also need to figure out how to update security patches.
ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
I am testing out another option. I will know soon enough whether or not it will work.
ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
No luck on the other option. Drats!
I'm charging my nexus right now and I'm gonna try this. I'll report in a few hours.
Update:
February 10, 2020: Update kernel from 3.4.69 to 3.4.71.
Download the zip, extract the zImage. use any one of the various tools in existence to unpack the boot image for the device and in the split-image folder delete boot.img-zImage and replace it with the zImage file and rename it to boot.img-zImage. Repack the the boot.img and flash in twrp or reboot to bootloader and flash in fastboot.
Sent from my Google Nexus 10 using XDA Labs
So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.View attachment 4946929View attachment 4946931
Sent from my AOSP on Manta using Tapatalk
Kaleshwar said:
So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.
Click to expand...
Click to collapse
Glad to hear. I have tried numerous ROMs on that device and all of them have some kind of flaw or another on a serious level. Either random reboots would occur, random shutdowns, extreme loss of memory and various other things. I got quite excited when I found this one online, with a working download link. Honestly it's exactly what I was looking for straight from AOSP. The stock ROM is also quite good, but it needs to be a bit more recent than lollipop. Because I was so used to stock AOSP on it already I was glad I can continue using AOSP. Never have been a big fan of lineage since they took over cm.and as the days go on it seems I like them less and less.
On a side note once I I'm able to update the kernel to a more recent version, then I will start experimenting with adding features. With that having been said I found it very hard to do so with this kernel. However I'm sure it can't be any more difficult then having to go through failed patches to remove commits and differences that screw up the build. Cherry picking on a whole new level. The only way I can figure out what patches do not work are by patching it and seeing which ones fail. That makes the process very timely.
Kaleshwar said:
So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.
Click to expand...
Click to collapse
PS I just caught your screen shot. Awesome home screen! I've also included mine as well as a screenshot of the device has info for the kernel version. In the meantime, kernel auditor works awesome on this device. Especially the entropy settings. This tablet seems to pay on it a bit and increasing the read and write variables a bit, does give this device a new feel.
Sent from my Google Nexus 10 using XDA Labs
I had been using LOS for a long time thinking it was the most "stable" option, but after trying this... WOW, I feel that my Nexus has been reborn. It is fluid, the boot is quite fast, battery performs quite well and so far I have not had any unexpected reboot issues, which in LOS it was a every day thing.
The only thing I miss is being able to use Magisk, but I will survive.
Thank you!
ThePx said:
I had been using LOS for a long time thinking it was the most "stable" option, but after trying this... WOW, I feel that my Nexus has been reborn. It is fluid, the boot is quite fast, battery performs quite well and so far I have not had any unexpected reboot issues, which in LOS it was a every day thing.
The only thing I miss is being able to use Magisk, but I will survive.
Thank you!
Click to expand...
Click to collapse
The saying goes they don't make them like they used to. I have found myself consistently returning to older devices and finding new means to bring brand new life into them. It's not often I get to get a case like this where the difference is so drastic. I literally turned a technically ancient device into what will soon be my new daily driver tablet. Best $50 investment ever.
One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?
ThePx said:
One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?
Click to expand...
Click to collapse
Not sure I'm using the same z image. I'll test it when I get home and see what happens it's the same one I pulled off of mine so I know it works. I don't believe it'll work on the stock ROM so I'm pretty sure you have to be on the marshmallow ROM in the OP. Other than that I'll have to test it and see what happens. You could also use any other tool that unpack and repack boot images, that just happens to be the one I use.
If you look at APK mirror, you can grab an APK for substratum that works on marshmallow ROMs. You're pretty limited in the theme number of themes for it, and there are a few good ones that still exist but are still quite limited. I use PureZ material dark. It won't turn every app into dark mode, including some Google apps, so just download 'dark mode' from the play store which takes advantage of accessibility services to darken most every other app.
Sent from my Google Nexus 10 using XDA Labs
ThePx said:
One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?
Click to expand...
Click to collapse
Sorry it took so long. Busy time at work these days. I honestly don't know what was wrong everything work fine on my end so here's what I did. Instead of using the actual zImage I went ahead repacked it to the stock boot.img from the ROM in OP. That should work but you will have to reflash SuperSU or magisk if you have systemless root.
Managed to add a few features but it's nothing much yet. Added all governors such as powersave, ondemand and userspace, etc. Disabled SELinux again, added debug info and options for GPU, and kernel same page merging (can be deactivated at boot by using kernel auditor or Franco kernel). Also deactivated the option that told the kernel it was using a "fake platform GPU". trying to get some kind of GPU options selectable inside one of the kernel applications. Let me know if it works and I will update the OP with the updated file. Just backup your current boot image and flash the new one in TWRP or push it in fastboot.
Sent from my Google Nexus 10 using XDA Labs
DragonFire1024 said:
Sorry it took so long. Busy time at work these days. I honestly don't know what was wrong everything work fine on my end so here's what I did. Instead of using the actual zImage I went ahead repacked it to the stock boot.img from the ROM in OP. That should work but you will have to reflash SuperSU or magisk if you have systemless root.
Managed to add a few features but it's nothing much yet. Added all governors such as powersave, ondemand and userspace, etc. Disabled SELinux again, added debug info and options for GPU, and kernel same page merging (can be deactivated at boot by using kernel auditor or Franco kernel). Also deactivated the option that told the kernel it was using a "fake platform GPU". trying to get some kind of GPU options selectable inside one of the kernel applications. Let me know if it works and I will update the OP with the updated file. Just backup your current boot image and flash the new one in TWRP or push it in fastboot.
Sent from my Google Nexus 10 using XDA Labs
Click to expand...
Click to collapse
3.4.71 working with the new image, thanks!
No problems so far, I'll update if I find something.
While unpacking boot.img I don't get split-image folder!! Seems the procedure described needs some clarity
ranandi said:
While unpacking boot.img I don't get split-image folder!! Seems the procedure described needs some clarity
Click to expand...
Click to collapse
See this link https://forum.xda-developers.com/showpost.php?p=81747927&postcount=15 flash boot image in TWRP or in bootloader mode. reboot your device then reboot back to recovery and flash magisk or whatever superuser you use. This is a clean boot image from stock so it is not rooted.
Sent from my Google Nexus 10 using XDA Labs
DragonFire1024 said:
See this link https://forum.xda-developers.com/showpost.php?p=81747927&postcount=15 flash boot image in TWRP or in bootloader mode. reboot your device then reboot back to recovery and flash magisk or whatever superuser you use. This is a clean boot image from stock so it is not rooted.
Sent from my Google Nexus 10 using XDA Labs
Click to expand...
Click to collapse
Yes, I could flash new boot image, following two issues:
(1) Camera sometimes shows 'not connecting', but sometimes it works fine.
(2) In clock when trying to set times of mother international zones, clock is not working error.
ranandi said:
Yes, I could flash new boot image, following two issues:
(1) Camera sometimes shows 'not connecting', but sometimes it works fine.
(2) In clock when trying to set times of mother international zones, clock is not working error.
Click to expand...
Click to collapse
1) I can look into the camera. I may know why that happens, though I never had a problem.
2) you may need to install another clock. I didn't stick with the one on the ROM. But try going to /data/used/0 and deleting the folder com.google.androud.deskclock (com.androis.deskclock?) and the contents and reboot and try again. I discovered while I've been testing kernels, that when flashing gapps, it doesn't always update the data files for Google related apps in that directory and causes some of the applications to force close, or not function at all. Also check the SD card Android/data as well and do the same.
Related
Is there a way to have 2 ROMs installed and get to choose which one you want to boot up everytime? I flashed Deck's 1.3 but I'd like to give MIUI a try, I'm too lazy to re-flash ROM, kernel, scripts, etc... If I don't prefer MIUI.
You could always backup your current ROM and flash MIUI, and after checking it out (for however long) just restore your setup if you're not feeling it. Or there is this;
https://market.android.com/details?id=com.drx2.bootmanager
I hear it takes up sizable space, but you might find it worth it. I tend to have a backup of CM7 and MIUI, just in case I want jump back for a bit or check something else out.
Have 5 diff ROMs (see sig) loaded using Boot Manager and lovin it
What I do is have a couple of different backups on my sdcard but if you plan on switching between your ROMs often I'd say go for the bootmanager
Sent from my Gruesomes Rom using XDA App
Bootmanager 3.01 is out now
Changes from v2.0 to 3.01:
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
floydie7 said:
What I do is have a couple of different backups on my sdcard but if you plan on switching between your ROMs often I'd say go for the bootmanager
Sent from my Gruesomes Rom using XDA App
Click to expand...
Click to collapse
same here. i usually make a back up and put it in a folder with the name and date - if i haven't gone back to it after a few weeks, i just delete it.
if i find myself going back and forth - bootmanager
works awesome
devnulldroid said:
Bootmanager 3.01 is out now
Changes from v2.0 to 3.01:
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
Click to expand...
Click to collapse
Is there a link to a thread explaining how to do this? I can't seen to get the search tool to work today
sitlet said:
Is there a link to a thread explaining how to do this? I can't seen to get the search tool to work today
Click to expand...
Click to collapse
Here is the Boot Manager Manual that explains what the program is and how to use it and all of its features.
Bootmanager = AWESOME.
You need to have some patience setting everything up, but once you get everything working it takes 2minutes to boot into a different ROM.
Sent from my PC36100 using XDA App
I took Boot Manager for a test drive last week. It was nice and all....but one thing I found to be very irritating was that my SD card wouldn't mount when I had it plugged into my computer. I also received errors, while in my SD ROMs, and the boot.img for my phone ROM failed to load. As did the boot.img for ALL of my other ROMs except the one I was in. Unfortunately. the one I was in was not a ROM that impressed me at all. But I couldn't go back to my default ROM so I ended up having to reflash the whole damn thing. Really irritating for me and it was a total deal breaker. I can't take a chance of Boot Manager doing that during an extremely critical time.
Ok, first mistake you made was flashing roms while plugged into a computer. That is why the boot.img were not created properly.
Second, anytime there is an issue with booting into slots or back to phonerom, boot into recovery, select install zips from sd, then select bootmanager directory, then select phonerom directory, then flash the update.zip, then reboot.
All fixed and back to original rom
Sent from my PC36100 using Tapatalk
Boot Manager is a good app...lets you install 4 additional ROMs plus your phone rom.
you should check it out, some of the roms dont work, but you can google which ones do work. Lets you Nandroid to SD as well.
eggsack said:
Ok, first mistake you made was flashing roms while plugged into a computer. That is why the boot.img were not created properly.
Second, anytime there is an issue with booting into slots or back to phonerom, boot into recovery, select install zips from sd, then select bootmanager directory, then select phonerom directory, then flash the update.zip, then reboot.
All fixed and back to original rom
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Wrong. I was at a hospital when my boot.img decided it wanted to not work. I'm not a noob when it comes to this stuff. ROMs were loaded onto my SD card, phone removed from computer, installed into Boot Manager. I could switch between the ROMs just fine for the first day or two. Then they just randomly decided they didn't want to load the boot.img files at all. The issue with my phone being attached to my computer was a completely separate issue. Whenever I did attach my phone to the computer while I was using Boot Manager it would not allow my computer to see it. Deal breaker for me even if I could reflash the phone rom. I'm not saying it isn't a useful app. But the spontaneity of the bugs is something I can't risk.
Boot manager is the way to go, also helps when trying to work on a rom that you are cooking/porting/or modding for yourself.
I have a habit of switching between MIUI, Cyanogen and often trying out random other ones. I'm gonna give Boot Manager a try. Thanks.
Bootmanager is the best app ever.
Sent from my PC36100 using Tapatalk
I can't install MIUI on any slot D:
Sent from my Classic EVO
Royalfox said:
I can't install MIUI on any slot D:
Sent from my Classic EVO
Click to expand...
Click to collapse
uninstall the app from the rom and fix permissions worked for me...i was stuck on this for a while too
It says "clean up finished" and nothing happened. I press on Stop Install and try to boot ROM, but it says " there's no Rom installed"
Sent from my Classic EVO
Just swapped out OMFGB for latest MIUI utilizing Ext2 file system and running nicely on my EVO 4G. Every day I am more and more impressed with Boot Manager
Talk about a virtual world...
TouchWiz-4.4 ROM FIXER for Developer Edition devices
WARNING: These files are for Developer Edition devices ONLY. Kernels cannot be flashed on the retail VZW Note 3 devices!
THIS PROCESS ALSO SETS KNOX 0x1
Own a DevEd? Flashed the firmware/modem bits to the new TW4.4 in hopes of seeing some of the improvements or running a stock-modded ROM?
FIRST: Big shout out to @Imoseyon who has a VERY nice kernel for unlocked devices here:
http://forum.xda-developers.com/showthread.php?t=2488082
Go over there and tell him thanks, because I had spent a day or so trying to fix up a boot.img but wasn't having much luck due to a crash in TIMA memory. But, then I read that someone had gotten the leak booted w/ Imoseyon's kernel and was able to rip it apart and pull just the absolute minimum changes to get a VERY close to stock kernel / ramdisk setup for the 4.4 leak.
WHAT IS THIS?
Several issues were noticed immediately on DevEd devices due to the fact that we can't flash certain portions of the updated ODIN files (aboot, sbls, etc):
Play Movies won't stream
External SD card won't mount
Lockscreen settings don't work
Imoseyon's kernel was the only boot.img which would run 4.4 leak due to aboot/devicetree changes and TIMA crashes
The files below fix these issues and provide a VERY close to stock boot.img for use on DevEd devices.
FIX FILES: 2 flashable .zip files (for use in recovery):
1st flash file: flash-vzw-de-4.4-kernel-v1.0.zip
This is a rebuilt boot.img containing:
New NC2 stock-based kernel with CONFIG_TIMA disabled
Rebuilt dt.img using 1st gen dtbTool for use with our 4.3 aboot
Ramdisk has default.prop changes for disabling TIMA, KNOX and securestorage (Credit: @Imoseyon / leanKernel 2.4 ramdisk)
This file only needs to be flashed once (as long as you don't swap to AOSP ROMs). You can also use leanKernel by @Imoseyon if you like his work. The difference between this kernel and his are: I used the identical settings as the stock NC2 kernel (Kernel modules are enabled, etc) in an attempt to eliminate as many differences between the DevEd and the retail device. His kernel has a TON of tweaks and updates. But, could in theory have issues running the stock NC2 VZW leak.
Kernel source: https://github.com/Hashcode/android_kernel_samsung_hlte/tree/hlteatt-kk-nc2
2nd flash.zip file: flash-tw44-sys-files-fixes-v1.0.zip
A set of system file changes which fix the issues noted above (this file should be flashed after EVERY TW-based ROM is flashed)
Downloads:
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
Instructions:
Download the above files and place them on your device's storage
Reboot into recovery
Flash flash-vzw-de-4.4-kernel-v1.0.zip if you need to fix kernel (coming from AOSP)
Flash flash-tw44-sys-files-fixes-v1.0.zip after ANY flash of TW-based 4.4 ROMs to fix system files
Reboot, no need to wipe cache, etc
XDA:DevDB Information
[DEVED/TW-ROM FIX] Developer Edition TW-4.4 ROM Fix Files, a Tool/Utility for the Verizon Samsung Galaxy Note 3
Contributors
Hashcode
Version Information
Status: Beta
Stable Release Date: 2014-04-27
Created 2014-04-27
Last Updated 2014-04-27
Reserved
Nice!
The sdcard fix worked but the screen security and play movies remains the same in captions of screen security it looks like this.
Edit: options not available due to device administration: screen lock security, encryption, credential storage type=backedup to hardware.
Great! Quick test results:
I can see my exFAT 64GB external SD card.
Cut and paste works with my password manager.
I still cannot set a screen lock PIN.
Sent from my SM-N900V DevEd using Tapatalk
I just received a PM from @oah2010 with the following fix for the screen unlock PIN/Password problem. He says:
Hi,
I don't post enough to reply to the thread in beans new dev edition kernel, but I wanted to let you and the other guys know about how I got the pin and password unlock to work for me.
I found it on a random xda thread:
In build.prop,
security.mdpp.result=None, changed to #security.mdpp.result=None
This let's you use the pin unlock as well as the other options that are currently greyed out.
This works for me with the deodex 4.4 rom and leankernel even before applying the fixes in beans new thread.
Please post this in the thread so other people will know.
Hope this helps.
Click to expand...
Click to collapse
I have not tested this yet since I have done very little file editing. Must backup first. Then I will test.
DavidFlory said:
I just received a PM from @oah2010 with the following fix for the screen unlock PIN/Password problem. He says:
I have not tested this yet since I have done very little file editing. Must backup first. Then I will test.
Click to expand...
Click to collapse
I tested this. It booted the phone up into a safe mode and reset my wallpaper/widgets. Still no luck with the lock screen.
I revered the change.
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
Big thanks to @Hashcode! SD Card (EXFAT) is working great!
I have been getting a couple lock ups/random reboots a day while on leanKernel. Going to run with this kernel for a while to see if that still happens.
stargzrr11 said:
I tested this. It booted the phone up into a safe mode and reset my wallpaper/widgets. Still no luck with the lock screen.
I revered the change.
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
Big thanks to @Hashcode! SD Card (EXFAT) is working great!
I have been getting a couple lock ups/random reboots a day while on leanKernel. Going to run with this kernel for a while to see if that still happens.
Click to expand...
Click to collapse
worked perfectly here you have to open it with text editor after mounting system r/w and delete the old copy of build properties after the new one is generated when you click save and exit, then mount the system r/o and reboot. Now get play movies going and I`m golden
mount r/w, change with text editor to #security.mdpp.result=None, click save and exit, mount r/o then reboot. Also verify that permissions are identical to the original. I hope I explained that better the second time sorry. Now I believe encryption will work too since a passcode can be set. Thanks @oah2010 and @DavidFlory .
Thepooch said:
worked perfectly here you have to open it with text editor after mounting system r/w and delete the old copy of build properties after the new one is generated when you click save and exit, then mount the system r/o and reboot. Now get play movies going and I`m golden
mount r/w, change with text editor to #security.mdpp.result=None, click save and exit, mount r/o then reboot. Also verify that permissions are identical to the original. I hope I explained that better the second time sorry. Now I believe encryption will work too since a passcode can be set. Thanks @oah2010 and @DavidFlory .
Click to expand...
Click to collapse
Thanks for the additional information.
I tried it again - I must have goofed up my build.prop somehow.
Regardless, it booted back up fine, but the swipe/pattern/pin lock options are still grayed out (just like the screenshot in the thread above). I tried wiping cache/dalvik without luck. Also tried re-applying Hashcode's sys-files-fixes zip - didn't make a difference.
I do see there is also a "security.mdpp" line in the build.prop a few lines above. Wonder if that needs commented out too.
---------- Post added at 11:39 AM ---------- Previous post was at 11:17 AM ----------
Thepooch said:
The sdcard fix worked but the screen security and play movies remains the same in captions of screen security it looks like this.
Edit: options not available due to device administration: screen lock security, encryption, credential storage type=backedup to hardware.
Click to expand...
Click to collapse
Play movies is working for me...
If it's still busted for you, try going into "Application Manager", "All", find "Google Play services" and click "Uninstall updates". Once you uninstall it, Hangouts should immediately popup saying you need to update Google Play services. Re-apply this update. Try play movies again...
Question folks: Will flashing this + Beans' kk Rom update the DE's modem to the current kk from MJE? I don't plan on running touchwiz on my DE but I'm wondering if I should just flash it to get the new modem (baseband) and then go back to AOSP.
TSman74 said:
Question folks: Will flashing this + Beans' kk Rom update the DE's modem to the current kk from MJE? I don't plan on running touchwiz on my DE but I'm wondering if I should just flash it to get the new modem (baseband) and then go back to AOSP.
Click to expand...
Click to collapse
No firmware update in this. Just ROM and kernel.
As far as I know there isn't a flashable modem firmware for that yet.
Sent from my SM-N900V using Tapatalk
I should say for my device, I'm not 100% sure if I flashed @BeansTown106's ROOT/ROM or whether I flashed the leak's system.img.ext4 file via heimdall (I remember flashing SuperSU initially to get root tho).
And I literally have no extra mods installed other than these.
So, I'd like to keep track of who has the following working and what users are doing to fix their issues:
- SD card (seems like it's fixed for most)
- Play Movies (@ThePooch it's not working -- possibly need to remove the updates / re-install?)
- Lock screen settings (Seems like I'm still the only one with working settings :/ -- possibly need a build.prop fix)
I have a theory that something in the ROOT ROM is causing the lock screen issues. My stock ROM was a direct flash of the system.img from the leak. But on rom-slot1 I installed Beans ROM. I have working lock screen setting on stock and the issues as everyone else on rom-slot1.
I'm researching the differences.
Sent from my XT1060 using Tapatalk
Thank you!
Hash,
I assume that we need to be on twrp 2.7 ( 4.3 edition).
Several people were complaining about the sd card not mounting -but fat32 wokrs.
here is a small donation 5W64555......
Thank you for keeping these devices up and running.
Hashcode said:
I have a theory that something in the ROOT ROM is causing the lock screen issues. My stock ROM was a direct flash of the system.img from the leak. But on rom-slot1 I installed Beans ROM. I have working lock screen setting on stock and the issues as everyone else on rom-slot1.
I'm researching the differences.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Rom slot ??? Wow now that is a difference I'm using TWRP 2.7.0.0 never once thought to use SS on a DE. Hmm I wonder could SS be the fix? How about running SS along side a native recovery? So your stock slot is not rooted and your running beans KK in Rom slot 1? This opens up many curious questions.
Thepooch said:
Rom slot ??? Wow now that is a difference I'm using TWRP 2.7.0.0 never once thought to use SS on a DE. Hmm I wonder could SS be the fix? How about running SS along side a native recovery? So your stock slot is not rooted and your running beans KK in Rom slot 1? This opens up many curious questions.
Click to expand...
Click to collapse
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
Not a special edition, I'm debugging the retail version of Safestrap using the new leak setup.
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
Do note that the kernel @Hashcode put up fixed the SD card problem. Exfat works fine with that kernel... I formatted my card back to Exfat.
Sent from my SM-N900V using Tapatalk
Dev Roms
Is there somewhere else we can put the Dev Roms and whatever else Dev there may be?
stargzrr11 said:
Do note that the kernel @Hashcode put up fixed the SD card problem. Exfat works fine with that kernel... I formatted my card back to Exfat.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Agreed. Are you using SS?
---------- Post added at 05:41 PM ---------- Previous post was at 05:39 PM ----------
abe_cedar said:
So we have to ss dev ed?
I have seen stargazer11 booting into the rom with lean kernel and fat32 sd card.
Any ideas?
Click to expand...
Click to collapse
I'm looking into it also thinking of the possibility of a special Odin package for the DE straight from the leak minus bootloader and plus Hashcode kernel so it will actually boot proper.
Whats MultiROM
Multirom is a ROM manager created by Tasssadar with the ability to load multiple ROMs without the need to remove your older one, giving you the ability to test/run multiple ROMs at once, you can also restore TWRP backup as Secondary ROMs allowing you to look at your backup to choose the right one, or maybe just have 2,3,4,5,6 working OS on your phone... just because it's cool.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack.
I Nuked my SDCard twice in porting this tool over, I'm not entirely sure what caused it, but I reverted few changes which might have been the reason, so I hope it wont happen again.
Still, I'll highly recommend you make backups and keep them on your computer. Always.
I've been using this for 2 weeks now with no serious problems, but just as well, don't be blaming me if anything goes wrong.
keep the "i cant get this to work" messages out of my PM i wont bother replying to them,
as almost anyone on this thread can help you.
you have a problem, read the main OP and if you still cant get it to work... post your problem here...
and be specific... "this is not working" will get you nowhere and no answers.
Special Thanks: @Tasssadar: For The MultiROM Source.
Sources:MultiROM
Modified TWRP
Download is one post below.
Requirements:
S-off/Unlocked Bootloader
Understand How KL Zeus Work*
By Flashing That Kernel, you'd need to flash a 2nd kernel to go along with it..
if you don't follow those instruction, the main ROM wont boot.
To Install MultiROM:
Flash Zeus Boot.img
Flash Multirom-20141228-v30-UNOFFICIAL-endeavoru.zip normally trough recovery.
Flash Multirom-20150430-v32-UNOFFICIAL-endeavoru.zip normally trough recovery (New Layout ONLY).
Reboot
To Fix Write To SDCard issue(flash on secondary ROM only):Not Needed with New Layout
Flash UPDATE-SuperSU-v2.40.zip(possible only needed on Lollipop, if no, no harm in switching to SuperSU)
Flash SDFix.zip
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Add ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> Add ROM
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Change Kernels:
Boot TWRP --> Advance --> MultiROM --> List ROMs --> Flash Modules Zip*
List ROMs --> Remove boot.img
List ROMs --> Add boot.img
* The Modules must be flashed 1st, as the boot.img is replaced with each flash.
Failed Install & losing memory
MultiROM -> TWRP
adb shell dosfsck -a /dev/block/mmcblk0p14
ToDo:
-- Nothing as it stands
and another one...
Amazing you did it..well done mate glad you are still with us on our dated hox.
Sent from my One X using XDA Premium 4 mobile app
Great!!! Eager to try but its very late night here
Also waiting for your Kernel
Sent from my One X using XDA Premium 4 mobile app
Wow your are just great ...... Will Test it if i have enough time.
Maybe you get tomorrow a pm
Gesendet von meinem HTC One X mit Tapatalk
Thant said:
OK one question maybe stupid but When I install MultiROM.zip from my recovery and then I will restart the phone it will directly start in TWRP and ask me which ROM I want ot boot or how I will go in TWRP recovery when it is not on the recovery partition and it will be posible to flash custom kernel on the others roms 2,3,4 and etc.?
Click to expand...
Click to collapse
It'll be better if i answer this here,
during boot, after flashing MultiROM, MultiROM starts and prompts you to choose what to boot,
Internal (Main ROM), TWRP or other ROMs you installed.
if you want to change kernel of a secondary ROM,
You boot TWRP -->Advance --> MultiROM --> Select ROM --> Remove boot.img
Select ROM --> Add boot.img, then you get to select the kernel you want.
To Flash the Zips/Modules
TWRP -->Advance --> MultiROM --> Select ROM --> Flash Zip
Ill update the OP with these now.
I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app
lalit387 said:
I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The main ROM will remain untouched..
but you'll need to know how KL Zeus works to boot it.
Great! I do not have important data in the internal storage, so I can test it.
@Thunder07 I want to test it too
The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.
Thunder07 said:
The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.
Click to expand...
Click to collapse
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.
ljjehl said:
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.
Click to expand...
Click to collapse
jeez... 1GB it is then :/
Thunder07 said:
jeez... 1GB it is then :/
Click to expand...
Click to collapse
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk
humzaahmed155 said:
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok
Thant said:
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok
Click to expand...
Click to collapse
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat
cappuccina said:
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat
Click to expand...
Click to collapse
just now deleted CM11 to many bug for me I missed important notification. The phone beep but I don't see nothing on the screen. Now for this week I think to test SlimKat to see how it works I hope to be stable and don't miss any inportant notification. Whole day I thik on the question why today I have too many free hours and in the end of the day when start main rom I understand why
So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.
humzaahmed155 said:
So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.
Click to expand...
Click to collapse
When I add a secondary Rom I also go into the advanced/Multirom/ list and select the Rom I installed. I then remove boot.img, then go back and install boot.img (the boot.img I extracted from Rom), go to the directory I saved that to and it's done. Should boot after that.
@Thunder07,
My current issue seems to be a cache issue. I seem to have to fastboot cache a lot more than I like, otherwise I can't always get to TWRP. Reboot (or from poweroff) more often than not seems to get me only the internal Rom and not the MultiRom startup. I was hoping a wipe cache from device would be sufficient, but no luck.
Original Stock and Debloated Stock Variants for the Samsung Note 12.2 Pro Wi-Fi Version
These roms are simple flashable zips that you can flash from your custom boot manager. It does not use an aroma installer. Instead I made two versions. This should avoid almost all the problems people were having because there are not modifying options in the installer before running it. It is based on the latest software out officially for this model: P900UEU1BNK1
Device and Firmware Info:
Model: SM-P900
Model name: GALAXY NotePRO 12.2 Wi-Fi
Country: Cellular south
Version: Android 4.4.2
Changelist: 2582108
Build date: Mon, 10 Nov 2014 02:08:13 +0000
Product Code: XAR
PDA: P900UEU1BNK1
CSC: P900XAR1BNK1
MODEM: P900UEU1BNK1
Originated from: http://www.sammobile.com/firmwares/download/39463/P900UEU1BNK1_P900XAR1BNK1_XAR.zip
YOU NEED TO HAVE A CUSTOM BOOT LOADER. i.e. you will need to have tripped your knox counter. There is no way for the P900 currently to have a custom bootloader and not trip knox to 0x01. Some of the non-wifi variants using the snapdragon setup can do this with TowerlRoot. We cannot
Custom Bootloader:
I use TWRP version 2.8.0 - INSTALL WITH ODIN NOT THE MANAGER.
It can be found here: Download TWRP
Once you have installed the custom bootloader you can now load roms and make and restore backups for your device. The first thing you should do at this point is boot into TWRP and immediately MAKE A FULL SYSTEM BACKUP. First, before anything else. Do this to be safe.
Next you need to choose which version you of the rom you want to flash. Both of these were built mostly from ArchiKitchen and then I did some modifying after but I need to thank JustArchi for making this easier to put together for you guys, take a look at it here. Most will probably go for the debloated version, but some people like an untouched setup.
Steps to Install:
1. Copy this version onto your device, I use my SDcard.
2. In TWRP, go to wipe, advanced wipe and check Cache, Dalvik, Data and then wipe. This seems like it takes a good 5 minutes so don’t think it’s locked up. Let it do it’s thing.
3. Go to Install, select the flashable zip. Flash.
4. You can reboot the system at this point.
5. Startup should bring you to the 4 dots google splash screen. First load takes a few minutes let it do its thing.
6. Setup your device, done. Enjoy.
Near Stock Untouched Version:
This version the system has had no debloating freezing or removal of apps. This version has simply been Rooted, Zipaligned, Deodexed, Added Init.d Support, Busybox Support, Knox has been removed, and supports custom Boot Animations. This is the closest you can get to how the device comes new. The near stock untouched version can be found here:
Click to Download the Near Stock Untouched Version
md5: b337d0b4f01e96ad869b0f7e55ebaac7
Debloated Version:
This version the system applications have been modified to greatly improve performance of the device. This version has been Rooted, Zipaligned, Deodexed, Added Init.d Support, Busybox Support, Knox has been removed, and supports custom Boot Animations. On top of this it has been debloated by removing and freezing apps. Below is a list of apps that have been frozen or removed. The debloated version can be found here:
Click to Download the Debloated Version
md5: 1993c45dc71dedd7b65e2575b9a57740
Apps that have been removed:
Books.apk
Chrome.apk
Magazines.apk
talkback.apk
Videos.apk
Blurb.apk
Flipboard.apk
FWUpgrade.apk
InteractiveTutorial.apk
MediaUploader.apk
MobileTrackerEngineTwo.apk
PickUpTutorial.apk
PreloadInstaller.apk
RoseEUKor.apk
SamsungSans.apk
sCloudBackupApp.apk
sCloudBackupProvider.apk
sCloudDataRelay.apk
sCloudDataSync.apk
sCloudQuotaApp.apk
sCloudSyncCalendar.apk
sCloudSyncContacts.apk
SNS.apk
SPPPushClient_Prod.apk
TravelService.apk
AutomationTest_FB.apk
BluetoothTest.apk
HwModuleTest.apk
WlanTest.apk
NoiseField.apk
PhaseBeam.apk
video
LowBattery.ogg
PowerOn.ogg
TW_Silent_mode_off.ogg
TW_Volume_control.ogg
Apps that have been frozen:
LocalFOTA.apk
AccuweatherTablet2014.apk
AntHalService.apk
ANTPlusPlugins.apk
ANTRadioService.apk
BBW.apk
ELMAgent.apk
eMeeting_HANCOM.apk
Kies.apk
MyMagazine.apk
NYTimes.apk
PCWClientS18.apk
Pinboard.apk
RemotePC.apk
Samsungservice_xlarge-xhdpi.apk
sCloudSyncSBrowser.apk
sCloudSyncSNote3.apk
SFinder.apk
Twitter.apk
watchON.apk
WebExMeetings.apk
If there is an APK you need that was removed, and you honestly cannot find it yourself, I can pull it from the stock folder for you, but don’t be lazy. Only ask if you really can’t find it yourself.
APKS Users May Want Back Individually
Samsung App Store thing: Samsung Store Apk
If you use the air command function with the S-pen and want back sfinder or the clipboard function.
Use Root Explorer or a similar app and browse to /system/priv-app/ rename both Sfinder.apk.bak and Pinboard.apk.bak to Sfinder.apk and Pinboard.apk (remove the .bak extensions). Reboot your tablet.
Disclaimer:
Your warranty is most likely already void if you have completed the steps to actually flash this ROM, I am not responsible for anything you do with your own device, if you can't follow directions or read that is not my problem. Follow Directions as they are listed and you should be fine. Knowing all this you do this AT YOUR OWN RISK!
Things that will make your tablet even better:
The Xposed Framework
The Xposed Framework is a custom framework using a hook that works on top of stock android systems that have root access. It is made by Rovo89 and the general thread can be read about here: Click Me!.
The Xposed Framework uses components called modules, which can be loaded on the device in various combinations to achieve many of the functions that used to only be provided by fully customized roms. I use several on my device and will list each below.
Recommended Xposed Framework Modules:
Activity Force New Task
App Settings
Boot Manager
Burnt Toast
Cool Tool
CrappaLinks
Disable Clear Dialogues Default
Disable Batter Full Alert
DitheredHoloBackground
KitKat SD Card Full Access
Remove USB Storage Warning
Samsung Keyboard Short Delay
Smooth System Progress Bars
Wanam Xposed
XVolume30
Xposed Recent Tasks Ram
YouTube AdAway
Allow Youtube Fullscreen HDMI
Old Versions:
P900UEU1BNI2 September 2014
Stock
https://www.androidfilehost.com/?fid=95747613655040578
md5: 97ba25203862f75cac18c91f44cb427c
Debloated Stock
https://www.androidfilehost.com/?fid=95747613655040601
md5: 19849ea3b143ba3f376405341764b8b3
P900UEU1ANC5 August 2014
Stock
https://www.androidfilehost.com/?fid=23622183712461879
md5: 0c2020121d2ae93dcda47acd1e4a1b04
Debloated Stock
https://www.androidfilehost.com/?fid=23622183712463362
MD5: 5eed908f12bb29f3319d56e64b09d10b
XDA:DevDB Information
Gatsrom, ROM for the Samsung Galaxy Note Pro 12.2
Contributors
Gatsrom
ROM OS Version: 4.4.x KitKat
Based On: Stock Touchwiz
Version Information
Status: Stable
Created 2014-08-27
Last Updated 2014-12-14
In case I need more room for something??
Oh I know, one thing. I'll volunteer to do this each time we get a new android version for our tablet. Time permitting.
Whats next?
1. If enough people ask for an app added back in I'll put it back in.
2. I'm experimenting with a version that has the Xposed framework and my setup cooked into the rom.
3. I'm also experimenting with some manual theming and tweaks to add into it, but I don't want to go crazy with it.
Awesome! Thanks for this!
Question: How does one go about developing these variants? Is it a matter of customizing an install through the tablet itself and then making an image of it or is development done completely offline on computer?
I'm curious because I'd like to experiment with making a debloated ROM myself just to play around with.
Thanks!
yay double post
muzzy996 said:
Awesome! Thanks for this!
Question: How does one go about developing these variants? Is it a matter of customizing an install through the tablet itself and then making an image of it or is development done completely offline on computer?
I'm curious because I'd like to experiment with making a debloated ROM myself just to play around with.
Thanks!
Click to expand...
Click to collapse
I do it on a computer completely. That way nothing from my device is taken personally like info etc. Plus it's cleaner. Main thing is you need Linux first and foremost or at least a vm setup running linux. I use ubuntu/kubuntu. That is how the image, kernel etc is compiled and smushed together. I do not think there is a possible way to build a linux kernel in windows.(?) The app removal/freezing is one of two ways. One I have a txt file with the apps names and/or dirs that I can tweak as needed and it will just rm them as it goes through the list. The other way is i go into the system/app folder before building it and modify the apks directly. This is how I do themeing changes, which I may or may not do for the note. For freezing I add .bak to them so they are not loaded.
While doing this I got our device added to the archikitchen database, so you no longer will need to manually enter the boot sector. It should autodetect the blk upon startup.
Wow, I'd love to learn how to do this so that I can tinker with making a slimmer touchwiz rom. Guess I got my work cut out for me on doing research.
Thank you!
Thanks man, this is great!
Sent from my SM-G900P using Tapatalk
Thank you SO very much ! I'm downloading the debloated version now. You rule !
Update: I'm up and running on the tweaked ROM ! I wanted to share a few things my 900 did so others will know...
... During the Dalvic cache wipe, the device suddenly rebooted! I got to the Samsung splash and it hung. I rebooted into twrp, then did the other three wipes first and waited for the 'successful' notification. Once I saw that, I rewiped the dalvic cache w/o problems and continued.
... during the actual flashing of the ROM, I expected the 5 minutes or so load time indicated by the instructions. Mine was closer to two minutes and it rebooted. The status bar had barely crept into the blue... It totally freaked me out, but I let it ride and soon was looking at the Google 4 dots screen. that lasted maybe 2 more minutes and I was up and running. So, don't panic if it happens to you too
... I saw you mention Xposed; for what it's worth I pretty much always load boot manager and App Opps; they are great! Occasionally I'll go for xPrivacy too, but haven't so far. I would suggest looking into AdAway as well ( an app, not a module )
thanks again for making this ROM!
Up and running here also! All went smooth. Nice fast rom. Looking for reboot menu but using same Samsung default color scheme!
Man!! Thanks so much! I cant wait for work to be over so I can get this cooking!!
----> Resolved......
I'm a little confused with how to get into TWRP. I downloaded the correct img and installed TWRP manager.. went thru the steps with busybox etc.. but when I reboot into recovery..
I get the following:
Android system recovery <3e>
KOT49H........... etc...
Reboot (which reboots back in normal tablet)
Apply update from ADB
Apply update from EXT storage
Wipe Data/Fac Reset
Wipe Cache
Apply update from cache
on the bottom of screen
#manual mode #
Apply Multi CSC
Applied the CSC-code : XAR
Sucessfully applied multi-CSC.
Until I know what to do, I just rebooted back into the normal factory os I been using.
I been using TWRP on other devices so I know something is going on here.. Please let me know what to do next.
Thanks!
I rooted using odin. The booted back into download and again used odin for twrp. Did my backup. Then wiped and installed the .zip. rooted and working.
amityg said:
I rooted using odin. The booted back into download and again used odin for twrp. Did my backup. Then wiped and installed the .zip. rooted and working.
Click to expand...
Click to collapse
Ok, thanks.. I used odin to root when I first rooted. But I didn't think we needed to use odin to load twrp but I guess I was wrong.
flipper2006 said:
Ok, thanks.. I used odin to root when I first rooted. But I didn't think we needed to use odin to load twrp but I guess I was wrong.
Click to expand...
Click to collapse
I just think for me it is easy. I saw three different ways to install twrp and I find Odin better then adb
amityg said:
I just think for me it is easy. I saw three different ways to install twrp and I find Odin better then adb
Click to expand...
Click to collapse
I ended up using flashify a 2nd time and it worked correctly, not sure why I had trouble the other times, but im up and runnin'
flipper2006 said:
----> Resolved......
I'm a little confused with how to get into TWRP. I downloaded the correct img and installed TWRP manager.. went thru the steps with busybox etc.. but when I reboot into recovery..
I get the following:
Android system recovery <3e>
KOT49H........... etc...
Reboot (which reboots back in normal tablet)
Apply update from ADB
Apply update from EXT storage
Wipe Data/Fac Reset
Wipe Cache
Apply update from cache
on the bottom of screen
#manual mode #
Apply Multi CSC
Applied the CSC-code : XAR
Sucessfully applied multi-CSC.
Until I know what to do, I just rebooted back into the normal factory os I been using.
I been using TWRP on other devices so I know something is going on here.. Please let me know what to do next.
Thanks!
Click to expand...
Click to collapse
Odin definitely odin. What you described is the manager not correctly installing twrp. I never use the manager for anything. Always odin. Simpler.
edit: actually going to add that to the first post.
Check out Flashify, it worked very well. I had downloaded the img ahead of time but it found the correct one anyhow..
regardless... It's now 7 hours later after flashing and loading my stuff back. 0% battery drain where before I had around 1-4% and nearly everything was greenified.
Thanks so much ...
PS. I hope we start seeing a bunch of these now that this is proven that it will work!
I get it setup and all is working. Use twrp to get a backup. Then after each reboot it will not remember my home WiFi password. Looking online now for solution
Installed backup and no longer have the problem. I did have to install the sdfix app because I could not get my mail app to export settings.
amityg said:
I get it setup and all is working. Use twrp to get a backup. Then after each reboot it will not remember my home WiFi password. Looking online now for solution
Installed backup and no longer have the problem. I did have to install the sdfix app because I could not get my mail app to export settings.
Click to expand...
Click to collapse
That's weird, I didn't have that problem, only issue was on first boot, Rom Tool Box wouldn't load, but after restarting, its been fine. No issue with Wifi here
I have been asked by several people, on the forums and via PM. I thought that I would offer a step-by-step guide.
Will This Trip Knox? Yes, it will. Installing a custom recovery such as TWRP will definitely trip Knox. From what I have read installing a ROM, even through FlashFire, will trip Knox, as will flashing a kernel.
You Don't Seem To Care About Knox That is correct. To this point the only downside is that I won't be able to use Samsung Pay and I don't plan on that anyway. BUT.....if you do care and Knox matters, stop reading now and stick with stock.
I will also recommend that you grab ODIN and a stock TAR file for your phone. You can always find the latest firmware at SamMobile, but will need to create an account and free downloads are speed capped. It will be SLOOOOW. But you will get a zip with the file that you need inside. Good to have in case of accident. Here is where I got mine: http://www.sammobile.com/firmwares/download/47474/G920PVPU1AOE2_G920PSPT1AOE2_SPR/
That said.....assume that you have a rooted S6. Install TWRP Manager from the Play store, ignore anything it says about an SD card and click on "Install TWRP." The version that you are looking for is "zerofltespr.img." You can also download that from here https://twrp.me/devices/samsunggalaxys6sprint.html and use Flashfire to install. Reboot into recovery (see http://www.androidexplained.com/galaxy-s6-recovery-mode/ for an explanation) and make sure that TWRP is installed. If TWRP doesn't come up, make sure that you used the correct file and try again.) Now you are ready to begin.
1) The ROM that I used is the SAC23 ROM from here: http://forum.xda-developers.com/spr...ment/sac23ram9200srintdeoxedmoddedv1-t3107342 Download that and copy to your phone. You should also grab the "Recent apps fix long press on home" zip file from the bottom of that post.
2) You will also NEED (!!!!!) a kernel that is designed for the S6, otherwise you will bork your phone. I use (and recommend) the Ktoonsez kernel located here: http://forum.xda-developers.com/spr...elopment/kernel-kt-sgs6-ocv-ktweaker-t3093009 Grab that and copy to your phone.
3) For fingerprint recognition and private mode, you will need the Aroma installer from here: http://forum.xda-developers.com/showpost.php?p=60112854&postcount=2 If you use the Aroma installer (and I don't so I have no experience) be sure that those are the only two things that you install.
UPDATE 7/1/2015 Just had a report that fingerprint is working with this kernel: http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-kernel-t3146127
Anyone interested should read all posts for that kernel before flashing.
Once you have those files on your phone, you are ready to begin.
Return to recovery mode. Before you do anything else....Click on "Backup." Accept the default settings and let it do its thing. I always name my backups....calling this Stock is probably a good idea. Once that is done, if you break things, you can return to this.
Okay, now go to Wipe. The old-timers will disagree, but most of the time the default "Factory Reset" is all that you need. If you are paranoid (and who isn't?) after this you can go to Advanced and choose Dalvik Cache, Cache, Data and System. But I rarely do this anymore. Complete guide for using TWRP is here: http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
Now go back to the main screen and select Install. You can select multiple zips. Flash the ROM, the kernel and that Recent Apps zip file. Be sure to set the kernel to flash after the ROM. Or you can flash them one at a time.
Once done, reboot phone and if all went well, you will see a new boot animation. First boot will take a while, let her go.
You should have a clean build so remember that you will need to reset Developers options, security (for allow Unknown sources) and other stuff.
With the Ktoonsez kernel, you will have the KTweaker app, very useful. If it doesn't install for you (and it didn't for me) the APK is located inside the zip file that you downloaded at S6\KT-SGS6-LP5.0-TW-G920P-05.28.2015.zip\system\app\ Extract that and install. I use downloaded Profiles a lot.
If all is well, but the fingerprint and private mode settings are things that you use, go back into Recovery and select ONLY those two items. I'll state again, I don't use them, have never flashed the Aroma installer and can't offer any help. I have seen that they work for some people, not for others..../me shrugs. I can't help with that.
I also use the Wicked One Theme from @dazedandconfused who is a master. See http://forum.xda-developers.com/spr...ps/theme-wicked-one-theme-s6-s6-edge-t3129822 for the theme and instructions. Be sure to follow the instructions about having the Urban theme from the Theme Store installed first. But this theme makes me very happy.
That is everything that I know....which goes to show how little I know!
EDIT: Missed a step....DOH!.... if you are using TWRP you should flash the zip file found here to address the Deep Sleep issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56
Happy ROM-ing.
Everything works except I cannot text at all
ScottBroker said:
Everything works except I cannot text at all
Click to expand...
Click to collapse
Are you using the stock messaging app or something else? Did you use the Aroma installer and, if so, was messaging working before?
koop1955 said:
Are you using the stock messaging app or something else? Did you use the Aroma installer and, if so, was messaging working before?
Click to expand...
Click to collapse
I use stock, and I tiried another as well. I did not use the aroma installer
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
ScottBroker said:
I use stock, and I tiried another as well. I did not use the aroma installer
Click to expand...
Click to collapse
I updated the PRL, rebooted and now it works, Thanks
ScottBroker said:
I use stock, and I tiried another as well. I did not use the aroma installer
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
I updated the PRL, rebooted and now it works, Thanks
Click to expand...
Click to collapse
Ah, good to know and thanks for posting the solution here.
Cheers.
koop1955 said:
Ah, good to know and thanks for posting the solution here.
Cheers.
Click to expand...
Click to collapse
Thanks for posting an alternative to the non existant development for the S6.
nice work on this Koop!!!!! I'm running Sacs rom and KToonz kernel smooth and trouble free, privacy mode and finger print scanner work 100%
sent from my S6 using tapatalk
Here's a question. Hope do you use the stock battery icon on Sac's ROM and not one of those gross 3minit or whatever ones? They're all hideous.
twiztid907 said:
Here's a question. Hope do you use the stock battery icon on Sac's ROM and not one of those gross 3minit or whatever ones? They're all hideous.
Click to expand...
Click to collapse
I have to say that it is really popular mod, but not to my taste either. Here is what I run for battery:
GSam Battery Monitor (also lets you customize the battery icon, but I don't)
Greenify and Wakelock Detector
With Ktoonsez, I have the Ktweaker installed. Click on the 3 dots upper left. Scroll down to KTweaker Shop Profiles and then pick from Conservative, Balanced or Performance (or grab some of each.) I am using the Conservative Profile "Dead By April." I love that name!
Average Per Complete Charge (now this is with light usage) 2 days 0 hours, with screen on 1 hour 41 minutes.
Not expecting to get the same battery life when I am traveling or with heavy usage, but that is still pretty remarkable.
koop1955 said:
With Ktoonsez, I have the Ktweaker installed. Click on the 3 dots upper left. Scroll down to KTweaker Shop Profiles and then pick from Conservative, Balanced or Performance (or grab some of each.) I am using the Conservative Profile "Dead By April." I love that name.
Click to expand...
Click to collapse
while I'll admit I haven't explored the KToonz settings much, I was wondering how you accessed profiles, this is good info, I'm trying out dead by April as I type this out lol
sent from my S6 using tapatalk
Missed a step
I edited the original post, but let me add this.
If you are running TWRP, you should flash the zip file found here to address the "No Deep Sleep" issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56
Hello, thank you for this great write-up! I PM'ed you the other day, and you helped me get my phone flashed and all.
However, I am still having issues with the Fingerprint scanner. If any other users do use the Fingerprint scanner, could you explain the steps in which you flashed each file? After using the Aroma installer to fix Fingerprint, I keep getting "Unfortunately, Fingerprint has stopped working." I just can't seem to get it working even with the Aroma installer. Maybe I am flashing files in the wrong order?
Thanks for any advice!
Android Attack said:
Hello, thank you for this great write-up! I PM'ed you the other day, and you helped me get my phone flashed and all.
However, I am still having issues with the Fingerprint scanner. If any other users do use the Fingerprint scanner, could you explain the steps in which you flashed each file? After using the Aroma installer to fix Fingerprint, I keep getting "Unfortunately, Fingerprint has stopped working." I just can't seem to get it working even with the Aroma installer. Maybe I am flashing files in the wrong order?
Thanks for any advice!
Click to expand...
Click to collapse
did you do a factory reset or dirty flash?
sent from my S6 using tapatalk
Another ROM Option
This is also an option for anyone having issues: http://forum.xda-developers.com/spr...ebloated-rom-samsuing-galaxy-s6-edge-t3126661
@Electronical Updates reminds all S6 users to flash the Ktoonsez kernel.
I hope to try this out this weekend.
scott_0 said:
did you do a factory reset or dirty flash?
sent from my S6 using tapatalk
Click to expand...
Click to collapse
I have tried both. I first wiped system, data, cache, dalvik and tried that. Then, I tried dirty flash from stock, flashing the ROM, kernel, and fingerprint fix, then wiped caches, and nothing. :/
Could you start the aroma installer, and on the first slide it tells you the version. Could you tell me which version you have? Maybe we have different versions, that could be the problem.. Thank you!
Edit: I also tried the other debloated ROM you mentioned, but it did not work with nor without the Aroma installer. If anybody wants to work with me to get this working, I can provide logs and information and test out whatever is needed. Thanks!
Thank you for this write up...glad to learn there is dev'ing going on for the edge.
Was hoping you could help; tried flashing twrp via odin, per instructions--root manager shows that I have TWRP 2.x.x. installed but when I try to boot into recovery I just get this crazy bright white screen. Was able to reboot normally the first time, but then tried booting into recovery with flashify and now stock on that bright white screen. I do have success with getting connections with odin, twrp flashing successfully. But now trying to flash back to stock firmware to get my recovery back and I have mixed results. PLEASE any help would be very much appreciated...might have borked my brand new s6 edge...but hope not.
Thanks in advance.
Unsuccessful
koop1955 said:
I have been asked by several people, on the forums and via PM. I thought that I would offer a step-by-step guide.
Will This Trip Knox? Yes, it will. Installing a custom recovery such as TWRP will definitely trip Knox. From what I have read installing a ROM, even through FlashFire, will trip Knox, as will flashing a kernel.
You Don't Seem To Care About Knox That is correct. To this point the only downside is that I won't be able to use Samsung Pay and I don't plan on that anyway. BUT.....if you do care and Knox matters, stop reading now and stick with stock.
I will also recommend that you grab ODIN and a stock TAR file for your phone. You can always find the latest firmware at SamMobile, but will need to create an account and free downloads are speed capped. It will be SLOOOOW. But you will get a zip with the file that you need inside. Good to have in case of accident. Here is where I got mine: http://www.sammobile.com/firmwares/download/47474/G920PVPU1AOE2_G920PSPT1AOE2_SPR/
That said.....assume that you have a rooted S6. Install TWRP Manager from the Play store, ignore anything it says about an SD card and click on "Install TWRP." The version that you are looking for is "zerofltespr.img." You can also download that from here https://twrp.me/devices/samsunggalaxys6sprint.html and use Flashfire to install. Reboot into recovery (see http://www.androidexplained.com/galaxy-s6-recovery-mode/ for an explanation) and make sure that TWRP is installed. If TWRP doesn't come up, make sure that you used the correct file and try again.) Now you are ready to begin.
1) The ROM that I used is the SAC23 ROM from here: http://forum.xda-developers.com/spr...ment/sac23ram9200srintdeoxedmoddedv1-t3107342 Download that and copy to your phone. You should also grab the "Recent apps fix long press on home" zip file from the bottom of that post.
2) You will also NEED (!!!!!) a kernel that is designed for the S6, otherwise you will bork your phone. I use (and recommend) the Ktoonsez kernel located here: http://forum.xda-developers.com/spr...elopment/kernel-kt-sgs6-ocv-ktweaker-t3093009 Grab that and copy to your phone.
3) For fingerprint recognition and private mode, you will need the Aroma installer from here: http://forum.xda-developers.com/showpost.php?p=60112854&postcount=2 If you use the Aroma installer (and I don't so I have no experience) be sure that those are the only two things that you install.
Once you have those files on your phone, you are ready to begin.
Return to recovery mode. Before you do anything else....Click on "Backup." Accept the default settings and let it do its thing. I always name my backups....calling this Stock is probably a good idea. Once that is done, if you break things, you can return to this.
Okay, now go to Wipe. The old-timers will disagree, but most of the time the default "Factory Reset" is all that you need. If you are paranoid (and who isn't?) after this you can go to Advanced and choose Dalvik Cache, Cache, Data and System. But I rarely do this anymore. Complete guide for using TWRP is here: http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
Now go back to the main screen and select Install. You can select multiple zips. Flash the ROM, the kernel and that Recent Apps zip file. Be sure to set the kernel to flash after the ROM. Or you can flash them one at a time.
Once done, reboot phone and if all went well, you will see a new boot animation. First boot will take a while, let her go.
You should have a clean build so remember that you will need to reset Developers options, security (for allow Unknown sources) and other stuff.
With the Ktoonsez kernel, you will have the KTweaker app, very useful. If it doesn't install for you (and it didn't for me) the APK is located inside the zip file that you downloaded at S6\KT-SGS6-LP5.0-TW-G920P-05.28.2015.zip\system\app\ Extract that and install. I use downloaded Profiles a lot.
If all is well, but the fingerprint and private mode settings are things that you use, go back into Recovery and select ONLY those two items. I'll state again, I don't use them, have never flashed the Aroma installer and can't offer any help. I have seen that they work for some people, not for others..../me shrugs. I can't help with that.
I also use the Wicked One Theme from @dazedandconfused who is a master. See http://forum.xda-developers.com/spr...ps/theme-wicked-one-theme-s6-s6-edge-t3129822 for the theme and instructions. Be sure to follow the instructions about having the Urban theme from the Theme Store installed first. But this theme makes me very happy.
That is everything that I know....which goes to show how little I know!
EDIT: Missed a step....DOH!.... if you are using TWRP you should flash the zip file found here to address the Deep Sleep issue: http://forum.xda-developers.com/showpost.php?p=60385577&postcount=56
Happy ROM-ing.
Click to expand...
Click to collapse
I have the SM-G920P Sprint variant I downloaded all necessary zip files even the "deep sleep"zip, backed up my stock rom, wiped and installed well at least I tried. Loaded the SAC23 ROM zip, swiped to flash but the screen just went black and I found myself back at TWRP recovery screen. Tried repeatedly and to no avail. Wondering what I missed if anything.
king_ricardo said:
I have the SM-G920P Sprint variant I downloaded all necessary zip files even the "deep sleep"zip, backed up my stock rom, wiped and installed well at least I tried. Loaded the SAC23 ROM zip, swiped to flash but the screen just went black and I found myself back at TWRP recovery screen. Tried repeatedly and to no avail. Wondering what I missed if anything.
Click to expand...
Click to collapse
First off. please edit your post to not include the entire Original Post. It is both bad form and makes it difficult to find your question.
The first thing that I would do if I were you is to make sure that I had a good download of the SAC23 ROM. That is most likely where your problem is. I will check my download later and post the MD5, but you should re-download.
I checked MD5 using WinMD5 Free (shouldn't matter, there are several MD5 checkers)and the MD5 should be 3bb8163e902769f564a2f3adb3a1b7e6. Try checking that.
Android Attack said:
I have tried both. I first wiped system, data, cache, dalvik and tried that. Then, I tried dirty flash from stock, flashing the ROM, kernel, and fingerprint fix, then wiped caches, and nothing. :/
Could you start the aroma installer, and on the first slide it tells you the version. Could you tell me which version you have? Maybe we have different versions, that could be the problem.. Thank you!
Edit: I also tried the other debloated ROM you mentioned, but it did not work with nor without the Aroma installer. If anybody wants to work with me to get this working, I can provide logs and information and test out whatever is needed. Thanks!
Click to expand...
Click to collapse
Came here to say I had the same problem. The original ROM posted here was a Deodexed ROM, and the aroma tool posted was an odex version. There's an aroma installer for Deodexed Roms that works perfectly fine, just gotta use that. I'd post the link but I've been up all night and I have work in an hour lol. Have fun, the ROM is pretty nice!
@koop1955 @scott_0 have yuo guys flashed SacsROM v3?! It seems effin' amazing!! I'm verrryyy tempted to try it lol.