Develop Bugs

[DEVED/TW-ROM FIX] Developer Edition TW-4.4 ROM Fix Files [2014-04-27]

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.

UPDATED 12/15 [ROM][P900][P900UEU1BNK1] Original Stock and Debloated Stock Variants

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

Viper4Android Help

I've been trying to get Viper4Android driver installed but it keeps failing.
I've tested CM11 and Stock but no go when I hit install driver. I'm guessing it may have something to do with SE Linux as I have to set it to permissive but haven't had any luck with trying to change it as apps do not detect it.
Just looking to see if anyone else had any luck with the app on their Fire Phone?

I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here, no need to change anything...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
I had to use SELinuxModeChanger on other devices (they used "enforcing") because they didn't offer a setting to change the SELinux mode.

Bingo Bronson said:
I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
Click to expand...
Click to collapse
I've reviewed the following thread
http://forum.xda-developers.com/showthread.php?t=2191223
I've tested 2.4.0.1 & 2.3.4.0 but can't install the driver. I have BusyBox Pro installed and running and reviewed the logs in SuperSU but i have no idea whats going on when I try the driver install.
Screenshot of Super SU Log: http://postimg.org/image/wdhvthr73/
I am currently back on CM-11 if you have any steps for me to try...

Kerrona said:
I have BusyBox Pro installed and running [...] I am currently back on CM-11 if you have any steps for me to try...
Click to expand...
Click to collapse
Hm, well that's interesting... I also used Stericson's busybox (non pro) and it worked right away... (I also used "ViPER4Android_FX_v2401_A4.x-A6.x.apk")
Maybe reinstall busybox... why isn't it able to find the "toolbox" / why is it calling the path with failsafe?
I see you have some security / privacy / permission tools running... can't really vouch for a hassle free install in such an environment.
You could try to flash this zip from safestrap recovery, this worked for me on other devices and the driver is already integrated, no need for a separate install from within the app.

This has something to do with superSU Binaries updated from normal method, if you have updated super su from playstore then you have to wipe the system partition reflash the rom and latest superSU zip. Otherwise you can flash the pre-build V4a zip as suggested above.

Thanks guys.
I got the driver installed and enabled now with the flash version.
Will probably wipe and start fresh and try the apk again.

[ROM] [B207] Simply Google M2 8.0 **Update 1/15/17**

Here is my stock based B207 rom, Simply Google. This is great for those of you who have a hard time getting the Google Apps to work and want some extra mods and features. You must have an unlocked bootloader and TWRP installed. This rom is tested on the M2-803L. Flashing it on other versions (801L, 802L) should work but you're flashing it at your own risk. All Google Apps you can download from the Play Store have been removed from the rom. I also heavily debloated it and removed a lot of Huawei apps. Please don't ask me to add anything in as I want to keep this rom slim. Open up Tablet Manager, hit the settings icon and uncheck Smart Tune-up if Permissions Manager force closes when you open it. Please hit the Thanks button if you like the ROM.
Features & Mods:
-AdAway
-Cust Mods
-Dark M2 Theme
-Deodexed
-GBoard
-Google Play Store, Google Contacts Sync
-Heavily Debloated
-Insecure boot.img
-Marshmallow Boot Animation
-Nova Launcher
-Region Mods
-SuperSU Preinstalled
Instructions:
1. OTA or Dload to B2xx first before flashing. The ROM will not boot if you're still on anything lower than B2xx
2. Download ROM and put it on the phone's internal storage or SDCard
3. Boot into TWRP recovery.
4. Performing a factory reset using TWRP is recommended.
5. Flash the ROM
6. Reboot System
7. Profit!
Bugs:
-You tell me
Simply Google B207:
https://www.androidfilehost.com/?fid=817550096634797575
​

Many thanks! What a nice surprise. This seems to be the first custom rom for the m8.
Appears that it is for the 802l. Would it also work for the 801l?
At the moment I have 5.1 reverted to stock. BL unlocked.

Demianis said:
Many thanks! What a nice surprise. This seems to be the first custom rom for the m8.
Appears that it is for the 802l. Would it also work for the 801l?
At the moment I have 5.1 reverted to stock. BL unlocked.
Click to expand...
Click to collapse
It should work on both versions provided you update to stock B2xx first. After someone updates to B2xx on their 802L I need them to send me two things.
1) Their cust folder so I can integrate it into the rom.
2) Their system/emui folder. There should be a folder called oversea in there which I need to integrate into the rom.

Sorry, I don't have the b215 yet. There was no update to 6.0 till now and i can't find even a newer version for the 801l then the one attached.

Demianis said:
Sorry, I don't have the b215 yet. There was no update to 6.0 till now and i can't find even a newer version for the 801l then the one attached.
Click to expand...
Click to collapse
The B215 update posted in one of these threads is for the 801L because when I flashed it I had no cellular data option at all.

Just tried to install the b019. But again it's a incompatible version. I guess it's because it's for the m2 803l.
Anyway, thanks for your help. I'll have to wait until until the official update hits my tab.
I tried with hisuite, but i have already the latest version available.

Hi. Thanks for the rom. I have 802l - b006 with unlock bootloader. Can I use your rom without updating to b219? I dont have any ota update that I can installl
Thanks
Sent from my HUAWEI M2-802L using XDA-Developers mobile app

budif said:
Hi. Thanks for the rom. I have 802l - b006 with unlock bootloader. Can I use your rom without updating to b219? I dont have any ota update that I can installl
Thanks
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
Click to expand...
Click to collapse
No, things like wifi won't work unless you upgrade to B211 first. Hold off on flashing until I sort out the root issue. Systemless root causes freezes. I'm working on porting the kernel from the X2 so I can use regular root which will fix the freezing issues.

New build up. Fixed root causes freezing in apps.

Do you know where to get the b011? The b006 is the latest rom that I can find for my m2.
Sent from my HUAWEI M2-802L using XDA-Developers mobile app

budif said:
Do you know where to get the b011? The b006 is the latest rom that I can find for my m2.
Sent from my HUAWEI M2-802L using XDA-Developers mobile app
Click to expand...
Click to collapse
You're gonna have to wait until you get the OTA to B215. Then you can flash this rom.

Installed this last night after updating to B207 from the other thread. Works perfectly, thanks!!

how can i remove 3g above my signal? my data is turned off and it still shows

New update. Fixed Multi-Screen not working. Rebased the rom to the International B207 version. Deodexed and added more mods.

ajsmsg78 said:
New update. Fixed Multi-Screen not working. Rebased the rom to the International B207 version. Deodexed and added more mods.
Click to expand...
Click to collapse
Currently I'm using your rom with xposed included.
Is the update also for this version available?
Lots of thanks for your work!

Demianis said:
Currently I'm using your rom with xposed included.
Is the update also for this version available?
Lots of thanks for your work!
Click to expand...
Click to collapse
I didn't integrate xposed this time because I figured if someone wanted it they can install it separately. You can grab it here:
https://drive.google.com/folderview?id=0B5I_q70mNuR4OWRaejdUdE1fcjA

ajsmsg78 said:
I didn't integrate xposed this time because I figured if someone wanted it they can install it separately. You can grab it here:
https://drive.google.com/folderview?id=0B5I_q70mNuR4OWRaejdUdE1fcjA
Click to expand...
Click to collapse
Ok, many thanks for the links. I will uninstall xposed, then dirty flash and after the first boot install xposed again.

my 801w was detected during installation as 802l. Don't know if this is what's causing the trouble, but after installing via TWRP, coming from some b2xx official ROM, i'm stuck at the Huawei Bootscreen for about 10 minutes now. I know that the first start could take a lot of time, but this seems a bit unusual to me. I'll keep it watching for another 15-20 minutes and see if it boots up fine or is frozen in any way.
[Update] so it was stuck in a loop for sure. I tried flashing a clean b2xx from another thread, which booted fine, and dirty flashing your ROM over, but same behaviour. What actually DID work is flashing the boot.img from stock over your ROM, so keeping the other partitions from Simply Google Installation. At least it's booting up now, showing the proper Android Nougat loading screen. Let's see how it works out...

toxic_garden said:
my 801w was detected during installation as 802l. Don't know if this is what's causing the trouble, but after installing via TWRP, coming from some b2xx official ROM, i'm stuck at the Huawei Bootscreen for about 10 minutes now. I know that the first start could take a lot of time, but this seems a bit unusual to me. I'll keep it watching for another 15-20 minutes and see if it boots up fine or is frozen in any way.
[Update] so it was stuck in a loop for sure. I tried flashing a clean b2xx from another thread, which booted fine, and dirty flashing your ROM over, but same behaviour. What actually DID work is flashing the boot.img from stock over your ROM, so keeping the other partitions from Simply Google Installation. At least it's booting up now, showing the proper Android Nougat loading screen. Let's see how it works out...
Click to expand...
Click to collapse
I need the /cust folder from the 801w so I can add it to the rom so it shows up correctly.

ajsmsg78 said:
I need the /cust folder from the 801w so I can add it to the rom so it shows up correctly.
Click to expand...
Click to collapse
Hello
same for me, i have a W, and i'm stuck on logo menu.
I have backup my tablet in trwp before, can you send me your email ???
Thank you.
(PS: is it complicated to deoxed the huawei rom ?) Ty

[D5503]Prerooted Customized IN 14.6.A.1.236 Flashable Zip for Sony Xperia Z1 Compact

Hello mates, Here is
D5503_Customized IN_1281-0184_14.6.A.1.236_R3D Prerooted Flashable Zip for Sony Xperia Z1 Compact Locked Bootloader
Made by PRFCreator_v1.3
You need only rooted phone and TWRP
For Root Xperia Z1C : https://forum.xda-developers.com/xperia-z1/general/root-xperia-z1-lollipop-5-1-1-build-14-t3246373
Or you can any well known and safe method for rooting. I have use kingroot 4.5.2.apk, after root I installed Z1C-lockeddualrecovery2.8.26.
For Dual Recovery : https://forum.xda-developers.com/showthread.php?t=2647480
In this creation you will get Stock Sony Rom 5.1.1.{ rooted with SuperSu (2.46) and Z1C-lockeddualrecovery2.8.26 }
How to Install:
1. Download file
2. Copy this zip in your sd card or internal memory( In recovery you can change default storage )
3. Boot to recovery (Use TWRP)
4. Wipe data,Cache and Dalwik Cache
5. install flashable-prerooted-signed.zip
6. Reboot to System
I have flashed on Stock Sony 14.6.A.1.236 in my Xperia Z1 Compact and tested everything is working good. There isn’t any problem in this rom. After installation this rom we can remove System apps, Ringtones etc… which are we don’t use.
In this rom I didn’t added Xposed. So you can install later.I have installed xposed-v84-sdk22-arm after flash rom.
Download Link : https://drive.google.com/open?id=0B2DnyFUiK93lZW1ncXlLd19JSDg
MD5: 3137f4b552a991d8cb8936749b772528
Download Link for Prerooted Zip with Xposed and SU 2.79 : https://1drv.ms/u/s!AqRWEkw4JbcJhBZESlNAZ2S-H0gJ
MD5: a36e3db078d8f8c0b0cca46f675f3259

how to install
How to install including md5?

jmcatamora said:
How to install including md5?
Click to expand...
Click to collapse
How to Install:
1. Download file
2. Copy this zip in your sd card or internal memory( In recovery you can change default storage )
3. Boot to recovery (Use TWRP)
4. Wipe data,Cache and Dalwik Cache
5. install flashable-prerooted-signed.zip
6. Reboot to System
There is no need to including md5, it is for checking purpose is your downloaded file is corrupted or not.

thank you
Can you help me . How to install xpose .??plz show me the download file xposed-v84-sdk22-arm and the framework.

jmcatamora said:
Can you help me . How to install xpose .??plz show me the download file xposed-v84-sdk22-arm and the framework.
Click to expand...
Click to collapse
Thanks to rovo89 for xposed support .
This is the link for download xposed framework
http://dl-xda.xposed.info/framework/sdk22/arm/
Detailed instructions for installation go to this link
https://forum.xda-developers.com/showthread.php?t=3034811

Thanks a ton for this! Worked awesome!
Since I went from stock 5.0.2 -> 5.1.1 ... I tried not wiping data and it seems everything still works fine! My apps, settings and data are all there =) ... so far w/o bugs.
I installed cyberian 7.1 camera(primary reason for my attempt at the upgrade) ... and seems to be working 100% w/o issue =)

GenTarkin said:
Thanks a ton for this! Worked awesome!
Since I went from stock 5.0.2 -> 5.1.1 ... I tried not wiping data and it seems everything still works fine! My apps, settings and data are all there =) ... so far w/o bugs.
I installed cyberian 7.1 camera(primary reason for my attempt at the upgrade) ... and seems to be working 100% w/o issue =)
Click to expand...
Click to collapse
Happy to know it is working on without wiping data.

PARESH AHAR said:
Happy to know it is working on without wiping data.
Click to expand...
Click to collapse
An update, its still working amazingly bug free!!! (w/o data wipe)
Also, *I think* battery life has much improved ... but that may be because I wiped cache and also turned off Stamina mode after reading it sucks battery life rather than help it lol!
I did run into some battery level quirkiness within the first few days of install, but hoping it was just some learning curve the OS had to do w/ battery ... time will tell =)
I do have a question tho, just noticed you state the bootloader/recovery is "locked"? Does this overwrite my previous "unlocked" state and its relocked now? Or does an unlocked state persist? Thanks

GenTarkin said:
I do have a question tho, just noticed you state the bootloader/recovery is "locked"? Does this overwrite my previous "unlocked" state and its relocked now? Or does an unlocked state persist? Thanks
Click to expand...
Click to collapse
No,this doesn't overwrite your unlocked bootloader. your unlocked state is persist.You can check by dialing *#*#7378423#*#* /Service info/Configuration/Rooting status:

Sad update, seems my phone has fallen victim to the "LP upgrade & damaged battery" coincidence =( ... I know its not a fault of ur ROM. Phone works fine from 100% to 50% then a 50% it rapidly drops to 1% and shuts off =/
That being said, ordered a replacement battery kit + back door + NFC tag. Hopefully normal battery functionality will be restored after its replaced =)
Seems to be a widespread problem =/ Its weird because I had LP 5.0.2 on it previously.

Battery replacement went well, back to full expected usage time!

blank screen after sony logo what should i do i have an unlock bootloader TWRP 3.0.2 on FotaKernel

nhicko95 said:
blank screen after sony logo what should i do i have an unlock bootloader TWRP 3.0.2 on FotaKernel
Click to expand...
Click to collapse
Bro I have tried locked bootloader. But I think GenTarkin installed on unlocked bootloader successful. First you should flash stock.ftf and after go further as first post.

Dirty flash I love you dirty flash blahblahblah
Thanks for this, just what I needed without the hasle as Gen said I just flashed over the rom I was using (mx 8.5), wiped dalvik and that other thing but kept data and now my phones overheating has stopped, installed xposed and my tweaks reinstalled themselves... Because of the dirty flash some of the apps needed updating but apart from that its ask good... Nice one

Update Zip
Zip is updated with Xposed and SU 2.79
Download Link : https://1drv.ms/u/s!AqRWEkw4JbcJhBZESlNAZ2S-H0gJ

Is there an Arabic language?

azoga said:
Is there an Arabic language?
Click to expand...
Click to collapse
Stock languages

There is a problem with Facebook and Messenger app (normal, not lite versions). When my girlfriend is trying to run these apps the screen just is just blinking (black&white) every 0,5 of sec. and nothing else is happening. Reinstalling those apps does not solve the problem.

watchoutbehindyou said:
There is a problem with Facebook and Messenger app (normal, not lite versions). When my girlfriend is trying to run these apps the screen just is just blinking (black&white) every 0,5 of sec. and nothing else is happening. Reinstalling those apps does not solve the problem.
Click to expand...
Click to collapse
You need to install an older version of facebook.

14.3.b.0.310
Can i flash this rom from stock rom 14.3.b.0.310?