Develop Bugs

[TUTORIAL] Flash CyanogenMod on TWRP

For CM11 Nightlies:
Find nightlies here:
http://download.cyanogenmod.com/?device=n1
If you're already on CM 10.2, just wipe cache and dalvik. Flash over your current build.
If you're coming from anything else, wipe cache, dalvik, data, and system. Then flash normally.
If you want gapps, you'll have to flash gapps as well.
No need for any modified files on nightlies. I assume that official stable builds will still be defaulted to flash on stock recovery though.
————————————————————————————————
CM 10.2 Information. Please do not use the following to flash CM11!
This is the method that I used to install CyanogenMod on TWRP.
I have tested this, and it is working perfectly on CM builds:
cm-10.2-WPPH47N-n1
cm-10.2-WPPH50O-n1
I will continue to test and update as new CM builds come out until CM flashes normally on TWRP
————————————————
First - Have TWRP as your recovery (2.6.3.1). Don't ask me how to do that.
Second - Backup your ROM! Just in-case something breaks, it's not my fault, and I'm not responsible.
————————————————
Now, we begin:
Download the newest CM build for the Oppo N1 from http://www.cyanogenmod.org/hardware/oppo-n1/#images
————————————————
After downloading your CM build from the above link, you'll need to follow these instructions to get setup for flashing in TWRP.
To modify your downloaded CM file, you can use either of the two methods below:
1: You can modify it yourself. It's actually very simple, just one line change.
2: I have attached an already modified updater-script to my post. You can use that and drop it into place (the file inside the zip, not the whole zip).[/b]
YOU ONLY NEED TO USE ONE OF THESE METHODS!
Method 1: To modify the file yourself:
First, open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Open the updater-script
Remove the first line only! You will remove:
Code:
assert(getprop("ro.product.device") == "N1" || getprop("ro.build.product") == "N1");
Do not remove anything else unless you know exactly what you're doing!
If you modified the file within the .zip, just save the file and it should save to the CM zip.
If you extracted the .zip, save the file and then go back and rebuild the zip.
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
——————————
Method 2: To download my pre-modified updater-script
Download my attached file (updater-script.zip)
Extract the file inside the zip (there's only one file)
Open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Simply copy your extracted updater-script from where you extracted it and drop it into the CM zip (It should save after)
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
————————————————
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
:victory:
I hope this all makes sense...
Basically you download the CM rom
Modify or copy the updater-script into the zip
Then you move the ROM to you phone
Then you go through the above area with wiping and flashing
* Pictures are attached
* Please let me know if there are any problems with this.
* Both versions of CM released so far have identical updater-script files. The .zip that I have attached will work on both builds.
* I will keep updating as needed
• Last updated: January 1, 2014

We're working on fixing TWRP so the asserts work properly.
https://github.com/omnirom/android_bionic/commit/4482d8513920d614e3799a214c5bad07b72580d2#diff-1 broke a lot of things.
https://github.com/omnirom/android_bionic/commit/ad76c85b9ca587084089d086f954158bc0eae905 allows flashing newer firmwares on older recoveries - but not the other way around.
The short-term fix is a TWRP build made from a 4.3 tree - this is 90% done.

@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img

Entropy512 said:
We're working on fixing TWRP so the asserts work properly.
Click to expand...
Click to collapse
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:

rayfin said:
@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img
Click to expand...
Click to collapse
BTW, I'd prefer that my personal dropbox not be directly linked. The same file is now an attachment to my post in the TWRP thread.

Harfainx said:
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:
Click to expand...
Click to collapse
i have some question can u help me :3
1. this download link is the file you already fix it right ?
https://www.4shared.com/download/UPP...N-N1_FIXED.zip - No wait - Direct download link - Full flashable ROM
Click to expand...
Click to collapse
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?

kenjilolip0p said:
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?
Click to expand...
Click to collapse
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.

Harfainx said:
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.
Click to expand...
Click to collapse
Camera orientation is handled by the camera HAL blobs.
CM does have back touchpad support but it's wonky (which is why omni hasn't merged it yet, we're still discussing whether to completely rearchitect it or just fix it.)

good work
Sent from my M045 using XDA Premium 4 mobile app

Except root it works
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.

fesar said:
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.
Click to expand...
Click to collapse
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?

nowy57 said:
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?
Click to expand...
Click to collapse
Go into SuperSU and remove it in the settings (unroot). That will get rid of all of the current SuperSU stuff.
Then flash SuperSU in TWRP.
To flash the unmodified CM, you can try the TWRP in post #3 of this thread HERE.
Or you'll have to remove the same line in the updater-script. The same method posted in the OP. Don't use the uploaded updater-script that I have there though. You'll need to change your own. It's a really simple fix. You don't have to extract all the files out. You can just modify the one file (I use Notepad++).
Sometime tomorrow I'll update the whole OP to include the newest CM version. I'm about to head out to our New Year's event, so I won't be available for the evening.
Enjoy the evening everyone. I wish you all the best! :good: :victory:

i have installed TWRP from #3 - not succes install CM newest version after this
i have unthick superSU and then install again via TWRP superSU.zip after that thick superSU on system android and no succes - root acces didnt come
happy new year
-------
I am a little dissapointed couse I downloaded CM ROM from OFFICIAL SITE http://www.cyanogenmod.org/hardware/oppo-n1/#images and I cannot install it SIMPLE on my device

OP updated! The newest release of CM has been added. I'll keep on top of it from now on, sorry about the delay.
I'm not going to host the CM builds anymore, since the modification is so small from the original CM build. Everyone flashing this should be capable of making the small change that's outlined in the OP.
:highfive:

@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy

nowy57 said:
@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy
Click to expand...
Click to collapse
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.

Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
okay , I will try it and confirm
I v got mac osx
under mac I unzip ROM , deleted first line from script then zip it , it doesent work .
but under windows - working good

Harfainx said:
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
Click to expand...
Click to collapse
What's wrong with wiping system?
You don't even wipe system if you go from ColorOS to CyanogenMod?
- Frank

cm11 nightlies are out and downloadable from cyanogenmod
Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
Cm11 nightlies are out..
Do you think we can flash on twrp
If so what would you wipe...
I was thinking about using banks minimal.. 19 MB..
Please give the community tour thoughts and a step by step tutorial..
I would download the nightly from cyanogenmod and banks gapps.. Check md5 alla onmy phone
Reboot recovery and wipe all maybe even system except sdcard
Flash cyanogen then gapps then
Rewipe cache and dalvik
Reboot
I am on omni nightlies now.. Thanks in advance

where do you see nightlies for oppo n1 ?
edit:
ohhh I see
http://download.cyanogenmod.org/?device=n1
better later than never
I just lost hope for good support and sold my oppo n1
I didnt belive for good support having it from one month and non of help from CM team

[Q] StockMOD Custom ROM 4.3 RLS2.1 Question

am I able to flash this StockMOD Custom ROM 4.3 RLS2.1 for att or tmobile, over my existing stock 4.4.2, my modem as of now is i747UCUFNE4 but the rom description says to flash the 4.3 modem or it wont get data? someone help me out
heres the rom url http://forum.xda-developers.com/showthread.php?t=2504903

do not flash the older modem. just flash the rom and youll be good to go.

DocHoliday77 said:
do not flash the older modem. just flash the rom and youll be good to go.
Click to expand...
Click to collapse
since im coming from stock 4.4.2 do I only wipe cache n dalvik before flashing

You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.

one more question
DocHoliday77 said:
You will most likely have to factory reset since you are downgrading.
You can try just wiping dalvik, but if it hangs at boot youll have to factory reset.
Click to expand...
Click to collapse
Thank You I tried wiping cache n dalvik, it hung but I went back in to twrp n wiped cache n dalvik again after install, worked like a charm!!!!!
hank you very much but can you answer me one question is there anyway you or another could port the revolutionary s5 v3 to the i747 it looks so amazing they only have it for the s3 i9300 not the s3 i747

Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....

DocHoliday77 said:
Afaik, porting from tbe i9300 is a pretty difficult process. The device is very different from ours. Not saying it isnt possible, but I dont think we've really ever had any ports from that device.
I wont be able to try as I just have too much on my plate already and not enough time as it is. Sorry....maybe someone else will tackle it....
Click to expand...
Click to collapse
well thank you very much for responding you've been a very patient n helping hand if you could maybe you could pass it around to some of the other developers you are in contact with I know of about 30 people personally that would love to have that on there i747 not counting the people ive seen on here asking for a rom from the s5 but no big deal THANKS AGAIN

I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.

plastic_green_head said:
I was watching this thread because I had the exact same question. I tried installing the "StockMOD Custom ROM 4.3 RLS2.1" and my S3 wouldn't even boot past the Samsung screen. I left it there for 15 minutes and nothing. I tried wiping dalvik/cache from recovery and then it wouldn't even get that far. From that point on when I tried to reinstall the ROM it would go by and then when it got to the rebooting stage it would tell me "No OS installed. Are you sure you want to reboot?", or something of that nature. I then installed the Deodex Debloat Version from here: http://forum.xda-developers.com/showthread.php?t=2540998 and it installed/booted on the first try. Only problem is that Wi-Fi does not work & not sure of what my next step should be to get Wi-Fi working. I came from 4.4.2 OTA. Should I install the 4.3 modem or try flashing the StockMOD Rom again? I'm confused because it was stated that it didn't need to be installed.
Edit: I installed the StockMOD ROM directly over top without wiping anything and it worked. If I just want the "Deodex Debloat" version should I wipe, reinstall that ROM, then install the 4.3 modem since it didn't work before?
Edit: Second time flashing the Deodex Debloat ROM & Wi-Fi is working but now I have no data/4G. Help! LoL.
Click to expand...
Click to collapse
if you flashed it without wiping cache n dalvik- dirty flash then it should have worked unless u came from another 4.4.2 rom mine is working fine
correct me if im wrong

If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.

DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all

DocHoliday77 said:
If ypu updated to 4.4.2, and then flashed a 4.3 rom, you have to use either the MJ2 or kt747 kernel or wifi wont work.
Click to expand...
Click to collapse
Why exactly will it not work to flash a MJB kernel?
Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.

Boston78 said:
that's not entirely true im not using either n my wifi is fine im on
kernel 3.0.31.1804024
[email protected]#1
i upgraded ota to 4.4.2 n never flashed any kernel at all
Click to expand...
Click to collapse
Are you using this rom along with the included kernel? Or something different?
plastic_green_head said:
Why exactly will it not work to flash a MJB kernel?
I would get either no wifi or no data depending on which modem was used after flashing the rom.
01 - Via TWRP (2.7.1.0) dirty flash d2att_4.3_MJB_Debloat_Deodex_v1.2.zip
02 - Reboot without wiping cache/dalvik = freeze at AT&T logo
03 - Wipe cache/dalvik = freeze at AT&T logo
04 - Factory Reset = success with the exception of no wifi
05 - Flash MJB modem = Wifi now enabled but no data. (baseband unknown/imei null)
06 - Flash NE4 modem = data/baseband/imei restored, but no wifi again
07 - Flash UCUEMJ2_Insecure_kernel.zip + wipe cache/dalvik & reboot = somplete succcess (wifi+data all working)
At least for my experience Doc is 100% correct. Not sure how you were able to flash the StockMOD ROM without having to flash a kernel. Especially when "How to flash" on the StockMOD page says "5. Flash Kernel (For WiFi)". Not saying you are lying, just that I don't understand why you didn't need to.
Click to expand...
Click to collapse
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)

DocHoliday77 said:
Are you using this rom along with the included kernel? Or something different?
As for why, starting in 4.3 (MJB) samsung moved the modules required for wifi to work. They are now included in a different partition. Custom kernels (or rather any kernel but the original stock) look for the modules (drivers) to be in /system/lib/modules (the location on earlier builds). Since they are not there, the system doesnt know how to use the wifi radio resulting in no working wifi.
We got lucky with the MJ2 kernel. It was the first 4.3 leak, and just by chance I tried it on a different leak (for the T999) while trying to figure out the wifi issue and it worked! They simply had not made the change in that test build. Pure luck! The kt747 kernel works because it was built from source and modified to use its own modules which are included in the kernel package.
It has been a good while, so as for where the modules are located now im not suren. But if you browse to /system/lib/modules and find wlan.ko, youll see it is symlinked to /system/lib/modules/prima/prima_wlan.ko. Youll also notice there is no prima folder or file. In older builds, the wlan.ko file was actually there.
Hope that made sense and hope I got most of it correct. (Going from memory)
Click to expand...
Click to collapse
whatever kernel that was built into the rom is what im on I listed it in my reply before, I haven't flashed anything else ONLY THE ROM, mine booted right up n works great,

The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.

DocHoliday77 said:
The more I think about it, it makes sense to me in both situations.
Id expect it to work on 4 4.2 because the wifi drivers are still in the same location, so as long as youre on 4.3 or above, it should work, as it apoears to do for you. But there are ithers who it did not work for and they have to use one of those other kernels. So it could be newer drivers not being compatible. Either way, if wifi is not working, I do know the kernel change will fix it.
Click to expand...
Click to collapse
well I have a twrp backup of it on my phone if you have some way of opening it, maybe somehow I could send it to you n whatever you find may be a tremendous help to you in how to fix the wifi n not having to flash the other kernels

I dont think there would be anything in a nandroid backup that would help. But tbh, right now I have no intention of digging into it any further. First because we already do have a pretty simple solution, and second because im already swamped with other projects and problems I've promised others I would work on.

Modem NE2 safe on JellyBomb V.21 - Android 4.1.2?

Hey all, haven't been keeping up on roms and updates for a while... I've been running JellyBomb rom since the first week the phone came out and had all the .zip's of MC2 / MA7 / MA5 / LK8 / LJC / LJ1 modems to run in TWRP. I got the zip for MK4 / NE2 yesterday and loaded the MK4 after a backup for safety, just looking to see if I'm safe to try the NE2 modem.
http://forum.xda-developers.com/showthread.php?t=2139889
I'm also seeing all the 4.4.4 rom's and I have a few questions, goomanager looks to be out of date these days and I'm still on TWRP V.2.5.0.1, I see on their site they are up to 2.8 (although I only see .zip for 2.7) for the Note 2 and still suggest to use goomanager. Can I just grab the .zip and load in TWRP recovery? I've got a fresh backup, so would I be able to go back to this backup from the 4.4.4 roms? Is it as easy as latest version of TWRP then wipe phone and load a 4.4.4 rom, or am I missing steps?
Thanks for any help:good:

kraftwerksfit said:
Hey all, haven't been keeping up on roms and updates for a while... I've been running JellyBomb rom since the first week the phone came out and had all the .zip's of MC2 / MA7 / MA5 / LK8 / LJC / LJ1 modems to run in TWRP. I got the zip for MK4 / NE2 yesterday and loaded the MK4 after a backup for safety, just looking to see if I'm safe to try the NE2 modem.
http://forum.xda-developers.com/showthread.php?t=2139889
I'm also seeing all the 4.4.4 rom's and I have a few questions, goomanager looks to be out of date these days and I'm still on TWRP V.2.5.0.1, I see on their site they are up to 2.8 (although I only see .zip for 2.7) for the Note 2 and still suggest to use goomanager. Can I just grab the .zip and load in TWRP recovery? I've got a fresh backup, so would I be able to go back to this backup from the 4.4.4 roms? Is it as easy as latest version of TWRP then wipe phone and load a 4.4.4 rom, or am I missing steps?
Thanks for any help:good:
Click to expand...
Click to collapse
It's safe to flash any modem for any rom including the NE2 modem. The 2.8 version of TWRP is linked in the thread here in development section. @jlmancuso posted a fixed version of 2.8 towards the last couple of pages in the thread so search for it because it's NOT on the site. It works fine but you can safely use Phil's recovery 6.07.9 or the newest version from his website (linked from the thread here in development) if you have any doubts or issues using it. Also be aware of the bootloader issue which causes the phone to not charge when powered off. If you have this problem on a MK4 or NE2 based TW rom then you will need to update your bootloader. This has been covered in the Community ROM thread. @jlmancuso posted a flashable bootloader in his thread on one of the last few pages. That pretty much sums it up.
FYI. Concerning nandroid backups, you must create and restore the backup from the same recovery. It is highly recommended to use Phil's recovery 6.07.9 or newest version for backups because TWRP backups are not cross compatible. So if you haven't done so already, use Phil's for your nandroid backup and go over the backup settings to include/exclude the items you want to include or exclude in your backup.

tx_dbs_tx said:
It's safe to flash any modem for any rom including the NE2 modem. The 2.8 version of TWRP is linked in the thread here in development section. @jlmancuso posted a fixed version of 2.8 towards the last couple of pages in the thread so search for it because it's NOT on the site. It works fine but you can safely use Phil's recovery 6.07.9 or the newest version from his website (linked from the thread here in development) if you have any doubts or issues using it. Also be aware of the bootloader issue which causes the phone to not charge when powered off. If you have this problem on a MK4 or NE2 based TW rom then you will need to update your bootloader. This has been covered in the Community ROM thread. @jlmancuso posted a flashable bootloader in his thread on one of the last few pages. That pretty much sums it up.
FYI. Concerning nandroid backups, you must create and restore the backup from the same recovery. It is highly recommended to use Phil's recovery 6.07.9 or newest version for backups because TWRP backups are not cross compatible. So if you haven't done so already, use Phil's for your nandroid backup and go over the backup settings to include/exclude the items you want to include or exclude in your backup.
Click to expand...
Click to collapse
Awesome thanks!
looks like I've got a bunch of reading to do then... everything has changed. I grabbed Philz touch 6.48.4-l900.zip, looks to be the latest/last update. I'll look into that flashable bootloader next.
I may just stay with jellybomb as the phone just works so well. After I do a fresh backup with Philz recovery can I go to a 4.4.4 rom and back to the backup of older 4.1.2 jellybomb rom? Anyway, thanks for the info and pointing me in the right direction! I'll read up and report back if need be.

kraftwerksfit said:
Awesome thanks!
looks like I've got a bunch of reading to do then... everything has changed. I grabbed Philz touch 6.48.4-l900.zip, looks to be the latest/last update. I'll look into that flashable bootloader next.
I may just stay with jellybomb as the phone just works so well. After I do a fresh backup with Philz recovery can I go to a 4.4.4 rom and back to the backup of older 4.1.2 jellybomb rom? Anyway, thanks for the info and pointing me in the right direction! I'll read up and report back if need be.
Click to expand...
Click to collapse
Yes you can flash back to an older pre 4.4 TW rom or any AOSP rom. Just stick with Phil's recovery because it's compatible with both TW and AOSP. I like the ui of TWRP better but reliability is a priority and Phil's does it all best. Good luck.
If you have ever taken the MK4 (4.3) or NE2 (4.4) OTA then your bootloader should be fine. If you've never taken the MK4 or NE2 OTA then you will most likely have the no charge issue when powered off (phone will reboot instead of charging when you plug in the charger while powered off). so you will have two choices: find and flash the bootloader that @jlmancuso posted in his Community ROM thread OR flash a stock unrooted rom with flash count reset and take all the OTA's until you are up to NE2 KK 4.4... then odin flash Phil's recovery (same version as mentioned above but its a md5.tar file) and make sure you uncheck the reboot device option in Odin and immediately pull the battery once it finishes flashing. Then reboot straight to recovery and immediately go into Phil's settings and select the re-root phone option. From that point you will be stock 4.4 unrooted WITH KNOX.. Next you will need to download and install SuperSU from the Google Play Store then immediately open SuperSU and let it remove KNOX from your phone (unless you want it). Then you can reboot to recovery and flash whatever rom you want.

tx_dbs_tx said:
Yes you can flash back to an older pre 4.4 TW rom or any AOSP rom. Just stick with Phil's recovery because it's compatible with both TW and AOSP. I like the ui of TWRP better but reliability is a priority and Phil's does it all best. Good luck.
If you have ever taken the MK4 (4.3) or NE2 (4.4) OTA then your bootloader should be fine. If you've never taken the MK4 or NE2 OTA then you will most likely have the no charge issue when powered off (phone will reboot instead of charging when you plug in the charger while powered off). so you will have two choices: find and flash the bootloader that @jlmancuso posted in his Community ROM thread OR flash a stock unrooted rom with flash count reset and take all the OTA's until you are up to NE2 KK 4.4... then odin flash Phil's recovery (same version as mentioned above but its a md5.tar file) and make sure you uncheck the reboot device option in Odin and immediately pull the battery once it finishes flashing. Then reboot straight to recovery and immediately go into Phil's settings and select the re-root phone option. From that point you will be stock 4.4 unrooted WITH KNOX.. Next you will need to download and install SuperSU from the Google Play Store then immediately open SuperSU and let it remove KNOX from your phone (unless you want it). Then you can reboot to recovery and flash whatever rom you want.
Click to expand...
Click to collapse
Yeah no over the air updates on my phone and I found that fix/thread on the community ROM encase I do run into that issue. I did swap over to that latest/last version of Philz Recovery and all is well, also ran a fresh backup, also with you on the UI but like you said as long as it works.
Let me ask you this, after I update the bootloader to NE2 that bootlader will still work with my backup of 4.1.2?
So does the procedure go - load 4.4.4 ROM/wipe and factory data reset in recovery > update bootloader in recovery > done?
Looking at the 4.4.4 Dirty Unicorns or the 4.4.4 Liquidsmooth , just want it to run solid.
Again thanks for the help/info!

tx_dbs_tx said:
so you will have two choices: find and flash the bootloader that @jlmancuso posted in his Community ROM thread OR flash a stock unrooted rom with flash count reset and take all the OTA's until you are up to NE2 KK 4.4... then odin flash Phil's recovery (same version as mentioned above but its a md5.tar file) and make sure you uncheck the reboot device option in Odin and immediately pull the battery once it finishes flashing. Then reboot straight to recovery and immediately go into Phil's settings and select the re-root phone option. From that point you will be stock 4.4 unrooted WITH KNOX.. Next you will need to download and install SuperSU from the Google Play Store then immediately open SuperSU and let it remove KNOX from your phone (unless you want it). Then you can reboot to recovery and flash whatever rom you want.
Click to expand...
Click to collapse
Is that right? or did you mean I'd be stock 4.4 rooted with KNOX? If I remember you can't run SuperSU unrooted, right?
So far I grabbed these zip's:
gapps-kk-20140606-signed.zip
NE2-screen-mirroring-fix.zip
tw-4.4.2-power-off-charge-fix.zip
Is that NE2 screen mirroring fix needed most of the time too?
I ran a titanium backup, I pulled the titanium backup and full backup using Phil'z recovery to my computer. I'd like to clear internal and external without loosing root as internal data is cluttered/full, is their a procedure to do that or do I need to do a factory data reset then reroot?
Thanks tx_dbs_tx:good:

[Q&A] [ROM]-I317UCUCNJ1 ButtNaked Post #1 AlmostNaked Uploaded - Post #2 11/28

Q&A for [ROM]-I317UCUCNJ1 ButtNaked Post #1 AlmostNaked Uploaded - Post #2 11/28
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM]-I317UCUCNJ1 ButtNaked Post #1 AlmostNaked Uploaded - Post #2 11/28. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Great rom!
dicksteele said:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Build number: KOT49H.I317UCUCNJ1
ROM is NE5 patched with the NJ1 OTA. Rooted, Deodex'd, and Zipaligned
Thanks and Credit to @Zen Arcade for his Auto-deodexer
Added Tethering patch, Screenshot edit, and Quad-MultiWindow
No N3, N4 or S5 stuff. No Theming. Not sure if I'll go there on this ROM.​
ButtNaked I317UCUCNJ1
https://www.androidfilehost.com/?fid=95784891001615960
MD5: d969d68f31c7ddb0d4b45292ada4a7a3
Almost Naked ROM IS POSTED BELOW. It has the stuff removed from ButtNaked.
Like Books, Flipboard, Magazines, SVoice, etc. All ATT crap will be stripped out. ​
I'm still learning what the changes were on NJ1. The camera feels like it takes pictures faster, a little quicker to respond for the next pic.
INSTALLATION
Instructions are the same as any other Custom ROM.
If you are on stock kernel it will probably hang. It should not if you are on AGNi kernel.
Download for AGNi kernel
http://forum.xda-developers.com/devdb/project/?id=2368#downloads
PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip
IT IS NOT RECOMMENDED TO FLASH Version 4.3.0 YET ! So use the 4.2.8 listed above
Great information is located here. Section 7 is How To Guides and References
http://forum.xda-developers.com/showthread.php?t=1987541 Credit @Bajanman
Custom Recovery
TWRP (TeamWiinProjects)
http://techerrata.com/browse/twrp2/t0lteatt (Zip is flashable, Tar is ODIN)
PhilzRecovery
http://forum.xda-developers.com/showthread.php?t=2159652
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/ (Latest version looks like 6.48.6. I have 6.41.6 on my phone. I will test with that) Either one should work fine.
Install instructions: Credit: ATT DN5 Team @sawdoctor and @Bajanman
You need to have Samsung 4.3 Bootloader or newer.
Make sure you have the latest TWRP/CWM recovery installed.
Next, remember to backup your apps and your efs folder. That's something that you always should do before flashing anything.
Go to TWRP/CWM recovery via pressing home + power + volume up button at the same time.
Make a Nandroid backup of your working system, if you haven't done so.
Its best to do a clean install for any new Rom (clean installation recommended includes internal storage)
In TWRP Recovery hit wipe, and slide to factory data reset system. (Internal won't be touched fyi)
In PHILZ Recovery Format Internal SDCard (in mounts and storage) and do Factory reset (I will install a new ROM option in PhilZ)
(Reminder) Remember that everything you flash you do it at your own risk so do your research before flashing anything!!
Now find the location of the Rom on your external and install it.
Flashing the Rom zip.
It should take less than 10 minutes till it boots...
[/QUOTE
ButtNaked is running good with the agni kernel 4.3.0 and added the viper4audio.
Click to expand...
Click to collapse

[email protected] said:
dicksteele said:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Build number: KOT49H.I317UCUCNJ1
ROM is NE5 patched with the NJ1 OTA. Rooted, Deodex'd, and Zipaligned
Thanks and Credit to @Zen Arcade for his Auto-deodexer
Added Tethering patch, Screenshot edit, and Quad-MultiWindow
No N3, N4 or S5 stuff. No Theming. Not sure if I'll go there on this ROM.​
ButtNaked I317UCUCNJ1
https://www.androidfilehost.com/?fid=95784891001615960
MD5: d969d68f31c7ddb0d4b45292ada4a7a3
Almost Naked ROM IS POSTED BELOW. It has the stuff removed from ButtNaked.
Like Books, Flipboard, Magazines, SVoice, etc. All ATT crap will be stripped out. ​
I'm still learning what the changes were on NJ1. The camera feels like it takes pictures faster, a little quicker to respond for the next pic.
INSTALLATION
Instructions are the same as any other Custom ROM.
If you are on stock kernel it will probably hang. It should not if you are on AGNi kernel.
Download for AGNi kernel
http://forum.xda-developers.com/devdb/project/?id=2368#downloads
PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip
IT IS NOT RECOMMENDED TO FLASH Version 4.3.0 YET ! So use the 4.2.8 listed above
Great information is located here. Section 7 is How To Guides and References
http://forum.xda-developers.com/showthread.php?t=1987541 Credit @Bajanman
Custom Recovery
TWRP (TeamWiinProjects)
http://techerrata.com/browse/twrp2/t0lteatt (Zip is flashable, Tar is ODIN)
PhilzRecovery
http://forum.xda-developers.com/showthread.php?t=2159652
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/ (Latest version looks like 6.48.6. I have 6.41.6 on my phone. I will test with that) Either one should work fine.
Install instructions: Credit: ATT DN5 Team @sawdoctor and @Bajanman
You need to have Samsung 4.3 Bootloader or newer.
Make sure you have the latest TWRP/CWM recovery installed.
Next, remember to backup your apps and your efs folder. That's something that you always should do before flashing anything.
Go to TWRP/CWM recovery via pressing home + power + volume up button at the same time.
Make a Nandroid backup of your working system, if you haven't done so.
Its best to do a clean install for any new Rom (clean installation recommended includes internal storage)
In TWRP Recovery hit wipe, and slide to factory data reset system. (Internal won't be touched fyi)
In PHILZ Recovery Format Internal SDCard (in mounts and storage) and do Factory reset (I will install a new ROM option in PhilZ)
(Reminder) Remember that everything you flash you do it at your own risk so do your research before flashing anything!!
Now find the location of the Rom on your external and install it.
Flashing the Rom zip.
It should take less than 10 minutes till it boots...
[/QUOTE
ButtNaked is running good with the agni kernel 4.3.0 and added the viper4audio.
Click to expand...
Click to collapse
Happy you like it. The Shift kernel works well also. Not trying to take anything away from AGNi, just pointing out another great solution.
Click to expand...
Click to collapse

dicksteele said:
[email protected] said:
Happy you like it. The Shift kernel works well also. Not trying to take anything away from AGNi, just pointing out another great solution.
Click to expand...
Click to collapse
I know shift 3.8.1 and 3.8.3 work. Is their anything that works that's higher than those.
Click to expand...
Click to collapse

[email protected] said:
dicksteele said:
I know shift 3.8.1 and 3.8.3 work. Is their anything that works that's higher than those.
Click to expand...
Click to collapse
I don't think so. He's been working on CM12 Lollipop kernels. He has one working.
Click to expand...
Click to collapse

dicksteele said:
[email protected] said:
I don't think so. He's been working on CM12 Lollipop kernels. He has one working.
Click to expand...
Click to collapse
Thanks for your quick reply.
Click to expand...
Click to collapse

No mobile connection after flashing
I've flashed PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip, Buttnaked-NJ1.zip, ATT-I317UCUBMJ4-Modem.zip (per instructions after flashing Buttnaked-NJ1.zip), and AlmostNakedFix.zip, in that order, but I get no mobile connection. I'm using CWM 6.0.4.1 and the phone is rooted. I also tried flashing CWM-I317UCUCNJ1.zip, but it didn't make any difference. I'm on AT&T.
When I go to view mobile networks, it says I need to insert a SIM, even though it is already inserted. There is no IMEI number listed, even though my SIM is inserted and mobile worked before flashing. Any help will be appreciated.
--Michael
---------- Post added at 03:34 PM ---------- Previous post was at 03:08 PM ----------
smartbean said:
I've flashed PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip, Buttnaked-NJ1.zip, ATT-I317UCUBMJ4-Modem.zip (per instructions after flashing Buttnaked-NJ1.zip), and AlmostNakedFix.zip, in that order, but I get no mobile connection. I'm using CWM 6.0.4.1 and the phone is rooted. I also tried flashing CWM-I317UCUCNJ1.zip, but it didn't make any difference. I'm on AT&T.
When I go to view mobile networks, it says I need to insert a SIM, even though it is already inserted. There is no IMEI number listed, even though my SIM is inserted and mobile worked before flashing. Any help will be appreciated.
--Michael
Click to expand...
Click to collapse
Also, in "About device" it says baseband version is "Unknown"

smartbean said:
I've flashed PSN_AGNi_pureSTOCK-v4.2.8_N7105_4.4.x_AROMA.zip, Buttnaked-NJ1.zip, ATT-I317UCUBMJ4-Modem.zip (per instructions after flashing Buttnaked-NJ1.zip), and AlmostNakedFix.zip, in that order, but I get no mobile connection. I'm using CWM 6.0.4.1 and the phone is rooted. I also tried flashing CWM-I317UCUCNJ1.zip, but it didn't make any difference. I'm on AT&T.
When I go to view mobile networks, it says I need to insert a SIM, even though it is already inserted. There is no IMEI number listed, even though my SIM is inserted and mobile worked before flashing. Any help will be appreciated.
--Michael
---------- Post added at 03:34 PM ---------- Previous post was at 03:08 PM ----------
Also, in "About device" it says baseband version is "Unknown"
Click to expand...
Click to collapse
I'm running DS_AN Rom with AGNi N7105 4.3.1r2 with no issues. Also ran on AGNi v4.2.8.... however, when I tried upgrading AGNi to v4.3.7, ran into the no SIM no data issue. See my post 2340 in the N7105 AGNi kernel thread here: http://forum.xda-developers.com/showpost.php?p=58511272&postcount=2340
Try reflashing kernel (like AGNi v4.2.4) or previous last known working boot partition from a backup if you have one. I was able to fix my issue by just reflashing last known working boot partition. .. then IMEI and SIM were again recognized. Good luck.

DoctorQMM said:
I'm running DS_AN Rom with AGNi N7105 4.3.1r2 with no issues. Also ran on AGNi v4.2.8.... however, when I tried upgrading AGNi to v4.3.7, ran into the no SIM no data issue. See my post 2340 in the N7105 AGNi kernel thread here: http://forum.xda-developers.com/showpost.php?p=58511272&postcount=2340
Try reflashing kernel (like AGNi v4.2.4) or previous last known working boot partition from a backup if you have one. I was able to fix my issue by just reflashing last known working boot partition. .. then IMEI and SIM were again recognized. Good luck.
Click to expand...
Click to collapse
Thanks for the reply.
I found (somewhere) that flashing CM10.2 would fix this, and it worked in my case. I have no clear idea why. After that, I was able to flash another Android 4.4.X ROM and it continued to work, but after flashing Buttnaked again, it stopped working again. Maybe I'll try again next week if time permits.

smartbean said:
Thanks for the reply.
I found (somewhere) that flashing CM10.2 would fix this, and it worked in my case. I have no clear idea why. After that, I was able to flash another Android 4.4.X ROM and it continued to work, but after flashing Buttnaked again, it stopped working again. Maybe I'll try again next week if time permits.
Click to expand...
Click to collapse
I found this on the Galaxy Y GT-S5360 forum thread (so don't flash the zips in the OP on the ATT Note2!)... but found it interesting and perhaps a reason a few folks are seeing "no SIM" and "unknown IMEI" issues after flashing the newer versions of the AGNi N7105 kernel on the stock (NE5 or NJ1) ATT rom.
http://forum.xda-developers.com/showpost.php?p=52952880&postcount=1
Something to do with the RIL files being mis-matched. Not sure, but perhaps the RIL files are missing/corrupted causing the problem... just not sure where to obtain the latest RIL files for the ATT stock firmware or which RIL files should be loaded on the ATT firmware to get it to work.

[How-To] Install Official I9505 Firmware on T-Mobile M919

**You must already have Root Access before you begin**
I regulary receive requests to assist in updating the T-Mobile M919 to the latest I9505 LTE Firmware. Below is a very easy process for doing it yourself:
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
Instructions:
1. Download the latest Official I9505 LTE Firmware from Sammobile.com.
2. Extract the System.img.ext4 and Cache.img.ext4, e.g. I9505_5.0.1_OB7_Official_Firmware, then place these images onto your device (use either internal or ext-sdcard).
3. Open the FlashFire app and "Agree" to the Terms and Conditions.
4. Press "(+)" twice to bring up the "Actions" menu.
5. Press "Flash firmware package" then locate and select System.img.ext4. FlashFire will scan the .img which may take several minutes to complete. Press "ok" once the scan is complete then press the checkmark to continue.
6. Press "Flash firmware package" again then locate and select Cache.img.ext4. FlashFire will then scan the .img. Press "ok" once the scan is complete then press the checkmark to continue.
7. Press “(+)” once again to bring up “Actions” and select “Wipe.” Under the “Options” menu select all partitions except “Internal storage” then press the checkmark to continue.
8. From the main menu Tap-hold-drag your "Actions" and place them in the following order:
- "Wipe"
- "Flash firmware package"(system.img.ext4)
- "Flash firmware package"(cache.img.ext4)
- "Process Cache" (Use default settings).
- "EverRoot" (Use default settings).
9. Last, press the lightning bolt then "Ok" to begin the flash.
The screen will turn black then display the contents of your system before beginning the flashes. Once complete your device will reboot and pause on the Samsung splash screen for about 3 - 4 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. You must already have a compatible custom kernel installed. Recommended Kernel: Lolli-Test-TW-07.02.2015 (source: http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/tw-lollipop-kernel-v1-t3024631).
2. After flashing I9505 firmware your wifi password may be forgotten upon reboot. To resolve this issue use ES File Explorer with root access enabled to edit the following build.prop line: ro.securestorage.support=true to "false"
3. You may also continuously receive an annoying security message. You can disable this message by using TiBu to freeze or remove the SecurityLogAgent.apk. Thanks to @Nana Ayeh

Whats inside? Is it lite ? Ooohhhh fiiirrrsssst [emoji13]

flatzki said:
Whats inside? Is it lite ? Ooohhhh fiiirrrsssst [emoji13]
Click to expand...
Click to collapse
Completely stock except for root and ausdim's kernel. Runs well on the M919 and can easily be a daily driver.

Nice! will be curious to see battery life reports on this.

After I'll restore the backup do I get OA7 modem and bootloader on my m919 device (like I odin it) ? Why mot just odin this Rom from the Leak thread ?

xperia_88 said:
After I'll restore the backup do I get OA7 modem and bootloader on my m919 device (like I odin it) ? Why mot just odin this Rom from the Leak thread ?
Click to expand...
Click to collapse
No the leak's modem will not flash on the m919. You can go flash the leak if you prefer.

muniz_ri said:
No the leak's modem will not flash on the m919. You can go flash the leak if you prefer.
Click to expand...
Click to collapse
I just wonder if I'll odin the leak that give me the new modem.

xperia_88 said:
I just wonder if I'll odin the leak that give me the new modem.
Click to expand...
Click to collapse
No, it won't. You can flash the AP file only and get a mostly working ROM except for wifi.

Thanks guys!! DL as we speak. Looks promising!!
Sent from my SGH-M919 using Tapatalk

mrbmg said:
Thanks guys!! DL as we speak. Looks promising!!
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I just noticed that it forgets my wifi pswd upon reboot. I will upload a new backup with the buildprop fix.
Edit: updated

muniz_ri said:
I just noticed that it forgets my wifi pswd upon reboot. I will upload a new backup with the buildprop fix.
Edit: updated
Click to expand...
Click to collapse
what version of twrp did you use?

det0xx said:
what version of twrp did you use?
Click to expand...
Click to collapse
I used 2.8.4.0
The rom is flawless other than the Wi-Fi PW mess up, which by the time I backed up and restored he already fixed. I have to have Wi-Fi calling but I set it up to my liking and the next time I leave I out on business I'm going to restore it. Also there was some security issue that kept wanting me to restart which I'm sure I could have figured out had I played on it a little longer and had service. Awesome job!
Sent from my SGH-M919 using Tapatalk

mrbmg said:
I used 2.8.4.0
The rom is flawless other than the Wi-Fi PW mess up, which by the time I backed up and restored he already fixed. I have to have Wi-Fi calling but I set it up to my liking and the next time I leave I out on business I'm going to restore it. Also there was some security issue that kept wanting me to restart which I'm sure I could have figured out had I played on it a little longer and had service. Awesome job!
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Well not to complain but i followed the instruction and i couldnt get it to work. TWRP told me i failed to choose a partition when i tried to restore. I used 2.8.4.0
Can someone do us others who use PHILZ recovery a huge favor and make a back up on there? if not its okay ill just be patient thanks btw.

No WiFi calling, I assume?

hella356 said:
No WiFi calling, I assume?
Click to expand...
Click to collapse
correct

I am downloading the ROM. I am halfway through. I will post my comments! Thanks a lot. I have really been hungry to taste TW Lollipop on SGS4.
EDIT:
The ROM is now my daily driver. Thank you all for the hardwork. I found a fix for the security notice bug. I installed titanium backup and with root privileges uninstalled security agent log and that was all. There was no annoying security alert afterwards.
Camera works fine except dual shot.
The 's finder in the notification drawer is awesome. Mobile data, hotspot, wifi, great battery life. I will update you if I find anything else. I will be more than glad if we get the leaked update in a flashable zip format to make things much easier.

Nana Ayeh said:
I am downloading the ROM. I am halfway through. I will post my comments! Thanks a lot. I have really been hungry to taste TW Lollipop on SGS4.
EDIT:
The ROM is now my daily driver. Thank you all for the hardwork. I found a fix for the security notice bug. I installed titanium backup and with root privileges uninstalled security agent log and that was all. There was no annoying security alert afterwards.
Camera works fine except dual shot.
The 's finder in the notification drawer is awesome. Mobile data, hotspot, wifi, great battery life. I will update you if I find anything else. I will be more than glad if we get the leaked update in a flashable zip format to make things much easier.
Click to expand...
Click to collapse
I will upload a new version of the backup with SecurityAgentLog removed. Good find, thx.
As for a flashable zip, I prefer backups as they retain samsung factory permissions and selinux contexts better than an updater script. A good updater script can get close but a backup is a mirror image of the Odin flash.
Edit: Updated

muniz_ri said:
I will upload a new version of the backup with SecurityAgentLog removed. Good find, thx.
As for a flashable zip, I prefer backups as they retain samsung factory permissions and selinux contexts better than an updater script. A good updater script can get close but a backup is a mirror image of the Odin flash.
Edit: Updated
Click to expand...
Click to collapse
I can't wait to have that update the SecurityAgentLog removed. I have subscribed to this thread so I will receive an alert once you update it. I have still not had any issues after using it for almost 24 hours. So stable. It's indeed a daily driver. Thank you for your commitment to developing our S4.
EDIT:
I did not see the changelog earlier. Thanks for removing the security violation message.

Sorry for my question...but, am new with kernels, FW, etc on Samsung devices.... I got S4 Tmo...NH7, no root, wifi doesnt work...to flash this Leak Backup first I need to flash Leak Firmware, root (Chanfire o TWRP in Odin), then into recovery restore this backup or with NH7 rootting my devices can I restore the backup? Jej sorry for my english...

great job
dears,
many thanks 4 ur great effort, its real awesome
after install the leak can go back to my previous rom 4.4.4 when i need