[Q&A] [ROM][N910W8][AOA1]Stock Rooted Deodexed (Regular/Debloated versions) - Galaxy Note 4 Q&A, Help & Troubleshooting

Q&A for [ROM][N910W8][AOA1]Stock Rooted Deodexed (Regular/Debloated versions)
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][N910W8][AOA1]Stock Rooted Deodexed (Regular/Debloated versions). 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!

work with encryption?
do you think it will allow encryption? I haven't had much luck yet with any rom except stock for root, twrc, and then encryption. my work email requires it or I'd skip it entirely...
thx

Colin Marr said:
do you think it will allow encryption? I haven't had much luck yet with any rom except stock for root, twrc, and then encryption. my work email requires it or I'd skip it entirely...
thx
Click to expand...
Click to collapse
I haven't tried but it's possible. Not sure why encryption doesn't work on other roms, but the "regular" version of this one is basically stock with root, TWRP, busybox, etc. I've disabled securestorage and added r/w permissions for SD card too, but if that's a problem you can reverse those two changes by following the steps in OP2 in my dev thread. If you test it out please report back and let us know if it worked

Deleted

resolving LTE display issue
Hi,
I believe I have replaced the Systemui.apk correctly with the correct permissions using Root Explorer but still see the 4G rather than the LTE in the bar.
Any ideas?
Thx.
Nick
ps thanks for the debloated ROM - working great for me with KT Kernel

nbogod said:
Hi,
I believe I have replaced the Systemui.apk correctly with the correct permissions using Root Explorer but still see the 4G rather than the LTE in the bar.
Any ideas?
Thx.
Nick
ps thanks for the debloated ROM - working great for me with KT Kernel
Click to expand...
Click to collapse
Check out this post from my other thread in the dev section. I think you'll also need the platform file, not just the Systemui.apk. Let us know if that does the trick.
http://forum.xda-developers.com/showthread.php?p=58766618

UPDATE!
v2.1 of the roms are now live! Based on the latest N910W8 BOC4 5.0.1 Lollipop firmware. See OP in the dev thread for updated details, instructions, notes, and download links: http://forum.xda-developers.com/showthread.php?p=58717681

Still no luck
sefrcoko said:
Check out this post from my other thread in the dev section. I think you'll also need the platform file, not just the Systemui.apk. Let us know if that does the trick.
http://forum.xda-developers.com/showthread.php?p=58766618
Click to expand...
Click to collapse
Thanks - I replaced the platform in permissions/etc/ with the updated one but at reboot still 4G.
Any other thoughts?
Thx.
Nick

nbogod said:
Thanks - I replaced the platform in permissions/etc/ with the updated one but at reboot still 4G.
Any other thoughts?
Thx.
Nick
Click to expand...
Click to collapse
What version of the rom are you flashing? Debloated v1.1 or 2.1? The files I linked were from the AOA1 base so not clear if they will work on BOC4.

1.1 and A0A1 base files
sefrcoko said:
What version of the rom are you flashing? Debloated v1.1 or 2.1? The files I linked were from the AOA1 base so not clear if they will work on BOC4.
Click to expand...
Click to collapse
A01A Base and debloated V1.1.
I appreciate you taking the time to respond - not really a big deal - just more a point of trying to figure it out for myself at this point. I will likely flash to 5.01 debloated now anyway - I have KT kernel running with the 1.1. Does the 5.01 have it's own kernel? (sorry if this is a naive question).
Thanks again.

nbogod said:
A01A Base and debloated V1.1.
I appreciate you taking the time to respond - not really a big deal - just more a point of trying to figure it out for myself at this point. I will likely flash to 5.01 debloated now anyway - I have KT kernel running with the 1.1. Does the 5.01 have it's own kernel? (sorry if this is a naive question).
Thanks again.
Click to expand...
Click to collapse
Happy to help . v2.1 (i.e. Lollipop) has the stock kernel. If you have already updated to BOC4 through Odin at least once before then the kernel will work for you when you flash v2.1. If not, you'll need to flash a compatible custom kernel (e.g. AEL, KT, etc) to avoid boot loops after installing v2.1. See OP in my dev thread for full instructions.
Not sure about the LTE icon. Maybe try copying the CSC folder from another working rom to v1.1 and try flashing that? If you're on kitkat and running xposed there is also a module you can download called LTE Switcher or something like that. I've used it before and it worked for me.

sefrcoko said:
Happy to help . v2.1 (i.e. Lollipop) has the stock kernel. If you have already updated to BOC4 through Odin at least once before then the kernel will work for you when you flash v2.1. If not, you'll need to flash a compatible custom kernel (e.g. AEL, KT, etc) to avoid boot loops after installing v2.1. See OP in my dev thread for fill instructions.
Not sure about the LTE icon. Maybe try copying the CSC fder from another working rom to v1.1 and try flashing that? If you're on kitkat and running xposed there is also a module you can download called LTE Switcher or something like that. I've used it before and it worked for me.
Click to expand...
Click to collapse
Thanks - I will install a custom kernel post-2.1 flash to get the BOC4 update. Appreciate you taking the time. I'll keep working away at the LTE issue. Let you know if I figure it out.

nbogod said:
Thanks - I will install a custom kernel post-2.1 flash to get the BOC4 update. Appreciate you taking the time. I'll keep working away at the LTE issue. Let you know if I figure it out.
Click to expand...
Click to collapse
Yes just confirming that you should be able to get the LTE icon by copying the CSC folder from stock or from the Regular version to your phone (after installing the Debloated version of course).:good:
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Debloated 2.2 released!
Notes:
Used a new debloat process and also fixed FC when using the front-facing camera.
If you get any FCs after initial setup (such as Google Maps or Samsung Link Platform), just make sure to update the problematic app from the Play Store or Samsung's Galaxy Apps store and then you should be good to go!
All details, instructions, and links can be found in the Dev thread OP:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538

Samsung Provider Codes not working
Hi there, Great Rom!
One thing that isn't working is the service provider code of *#2263# isn't working (MMI error).
Thanks again!

whoatemyling said:
Hi there, Great Rom!
One thing that isn't working is the service provider code of *#2263# isn't working (MMI error).
Thanks again!
Click to expand...
Click to collapse
Thanks!
Are you using the Regular or Debloated version of the Rom?

sefrcoko said:
Thanks!
Are you using the Regular or Debloated version of the Rom?
Click to expand...
Click to collapse
I've tried both versions and neither version can access the RF Band Selector menu. It comes up with a MMI error. I've gone through and tried manually selecting a provider and that didn't work neither. IMEI is intact, and no issues with making receiving calls or texts. Flashed back to stock via Odin and no issues with getting to that menu.

whoatemyling said:
I've tried both versions and neither version can access the RF Band Selector menu. It comes up with a MMI error. I've gone through and tried manually selecting a provider and that didn't work neither. IMEI is intact, and no issues with making receiving calls or texts. Flashed back to stock via Odin and no issues with getting to that menu.
Click to expand...
Click to collapse
Hmm that's strange...I could understand an issue with the Debloated version since things were removed, but the Regular version is basically just a rooted and deodexed version of stock. You have a N910W8, and not using any other mods or kernels, correct? Not sure why it would work on stock BOC4 but not the Regular Rom since they are essentially the same...

sefrcoko said:
Hmm that's strange...I could understand an issue with the Debloated version since things were removed, but the Regular version is basically just a rooted and deodexed version of stock. You have a N910W8, and not using any other mods or kernels, correct? Not sure why it would work on stock BOC4 but not the Regular Rom since they are essentially the same...
Click to expand...
Click to collapse
Yes I had the same thought, so I went from the debloat to the regular. I also ensured that I wiped 3x in TWRP in all required sections (all except internal storage and SD Card), before doing the flash to debloat or regular. Also made sure I waited 5 minutes post boot and then reboot before going through the setup wizard.
In any case, not a deal breaker for some, but may be fore those that are looking to enable LTE on N910W8 (Wind purchased phones).
I am running a N910W8, with no other mods or kernels. I was running straight stock w/root, before flashing the ROM's. Ensured that I was running BOC4 before flash. Not sure why, unless the base ROM you're using in the Deodex and Debloat doesn't have that menu's within it's native firmware, but I was under the impression that the firmware for canadian models were all identical with their own carrier codes attached to the firmware. (CSC Code chage *#272*IMEI#).

whoatemyling said:
Yes I had the same thought, so I went from the debloat to the regular. I also ensured that I wiped 3x in TWRP in all required sections (all except internal storage and SD Card), before doing the flash to debloat or regular. Also made sure I waited 5 minutes post boot and then reboot before going through the setup wizard.
In any case, not a deal breaker for some, but may be fore those that are looking to enable LTE on N910W8 (Wind purchased phones).
I am running a N910W8, with no other mods or kernels. I was running straight stock w/root, before flashing the ROM's. Ensured that I was running BOC4 before flash. Not sure why, unless the base ROM you're using in the Deodex and Debloat doesn't have that menu's within it's native firmware, but I was under the impression that the firmware for canadian models were all identical with their own carrier codes attached to the firmware. (CSC Code chage *#272*IMEI#).
Click to expand...
Click to collapse
Thanks for the info. Strange indeed! Yes the Canadian roms should all basically be the same as you mentioned. This one is based directly off the stock Bell BOC4 firmware from sammobile so not clear why it would on stock but not this version. I've read something about Wind phones being a little different from the other Canadian variants in some way (I forget the specifics now), but that was a while back and I'm not sure if it's actually true or even related to this lol. Either way I will take a look over the weekend and post if I find anything of interest.

Regular/Debloated 2.3 released!
Notes:
Based on new BOE1 firmware released for the N910W8.
All details, instructions, and links can be found in the Dev thread OP:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538

Related

Galaxy s2 ICS Update, Telstra AUS

Hey guys,
Long time lurker here, I flashed back to stock 2.3.6 carrier firmware (telstra in AUS) about 3 days ago because I feared my phone had the infamous USB port error (random charging without charger plugged in and other related issues) and I might have had to return it for warranty.
I got a notification popup while on my home screen (right now 8pm GMT+10) that there is a new update available which will wipe some settings in order to install ICS (215.72MB Update).
Just thought i'd update you all that are in the same boat as I havent seen any information about carriers updating to ICS.
I'll update you and let you's know how I go.
I can't show you a picture becuase i've posted less than 8 posts.
Bit late on the update..
Telstra, and Optus have already rolled out ICS for S2 a few weeks ago..
I run 2 Galaxy S2 phones, on both networks. Both upgrades are so much smoother. Although TW launcher is the same, so just flash a new launcher to suit..
I use alot of features and high power apps and no bugs as yet..
Although I am looking for a telstra DVLP4 insecure kernel to re-root. If anyone could be of assistance?? For a beer, or thanks..
markymark0055 said:
Bit late on the update..
Telstra, and Optus have already rolled out ICS for S2 a few weeks ago..
I run 2 Galaxy S2 phones, on both networks. Both upgrades are so much smoother. Although TW launcher is the same, so just flash a new launcher to suit..
I use alot of features and high power apps and no bugs as yet..
Although I am looking for a telstra DVLP4 insecure kernel to re-root. If anyone could be of assistance?? For a beer, or thanks..
Click to expand...
Click to collapse
I too am looking for the rooted Kernel. Please let me know if you find one. I flashed the new update from the wanam rom and I must say I am loving the battery life. Watching Fox on the telle from my phone is kinda cool also.
Anyone who wants an 'insecure'/CFRoot LP4 kernel should extract the stock kernel zImage from the rom package, send it to Chainfire & ask him nicely to make a CFRoot kernel.
Doubt you'll see an insecure/root kernel for this build otherwise.
Neede Kernel Bad
Hey Guys i would really like the stock kernel for this rom can any help me Please I have search for ages pleas help
---------- Post added at 01:51 PM ---------- Previous post was at 01:37 PM ----------
By the way i have tried and tested this kernel and it works great for ics on galaxy s2. And is rooted had has cwr 5 pre installed give it a try.
CF-Root-SGS2_XX_OXA_LPS-v5.4-CWM5.rar Google it new user so it wont let me post links yet sorry
CF-Root-SGS2_XX_OXA_LPS-v5.4-CWM5.rar
I tried it, and so far so good. One problem was rebooting after I flashed it. Phone says TW failed to launch than rebooted nad no worries mate!
MistahBungle said:
Anyone who wants an 'insecure'/CFRoot LP4 kernel should extract the stock kernel zImage from the rom package, send it to Chainfire & ask him nicely to make a CFRoot kernel.
Doubt you'll see an insecure/root kernel for this build otherwise.
Click to expand...
Click to collapse
I would if i could. But I decided to upgrade via Kies. And no root acess now.. So no rom package, can't get the zImage..
markymark0055 said:
I would if i could. But I decided to upgrade via Kies. And no root acess now.. So no rom package, can't get the zImage..
Click to expand...
Click to collapse
I upgrade via kies too. But if ypu flash the kernel above you will have root access again!
Does anyone know what the modem after the update is? And if this modem can be used with a GB Rom.
DVLP4 according to Checkfus. Yes. You can flash whatever modem you like. Modems originally supplied with GB stock roms will work with ICS & vice versa. However, different modems tend to work best with particular networks and sometimes even vary a bit with location (variations in equipment/bands used by the same telco in different locations).
You should be able to find a CWM flashable version of the modem via a Google search with XDA appended to your search terms, or, have a look in the AU SGS2 thread. I'm fairly sure this modem has been discussed (and posted/at least links to CWM versions) somewhat recently. If you can't find it, ask someone to post it for you in that thread.
nk7 said:
Does anyone know what the modem after the update is? And if this modem can be used with a GB Rom.
Click to expand...
Click to collapse
MistahBungle said:
DVLP4 according to Checkfus. Yes. You can flash whatever modem you like. Modems originally supplied with GB stock roms will work with ICS & vice versa. However, different modems tend to work best with particular networks and sometimes even vary a bit with location (variations in equipment/bands used by the same telco in different locations).
You should be able to find a CWM flashable version of the modem via a Google search with XDA appended to your search terms, or, have a look in the AU SGS2 thread. I'm fairly sure this modem has been discussed (and posted/at least links to CWM versions) somewhat recently. If you can't find it, ask someone to post it for you in that thread.
Click to expand...
Click to collapse
So long as it's a Telstra modem, I'm happy. I see your flag says you're with vodafone..
From Checkfus - Android/GT-I9100T/Australia (Telstra) - GTI9100LKJTEL:
I9100TDVLP4/I9100TTELLP2/I9100TDVLP3/I9100TDVLP4
The third bit is the modem. Yes, I'm with Voda. And ?
nk7 said:
So long as it's a Telstra modem, I'm happy. I see your flag says you're with vodafone..
Click to expand...
Click to collapse
MistahBungle said:
From Checkfus - Android/GT-I9100T/Australia (Telstra) - GTI9100LKJTEL:
I9100TDVLP4/I9100TTELLP2/I9100TDVLP3/I9100TDVLP4
The first bit is the modem. Yes, I'm with Voda. And ?
Click to expand...
Click to collapse
I assumed the modems were different for vodafone and telstra even if they use same frequency
What telco I use has nothing to do with anything I looked up the Telstra details with Checkfus, plus I keep an eye on the AU thread so I know it's been discussed. As per the edit to my post above, the modem is actually the 3rd bit in that string. Go back to the AU thread, I'm about to post there.
nk7 said:
I assumed the modems were different for vodafone and telstra even if they use same frequency
Click to expand...
Click to collapse
*ignorant post about not being sure how to root*
EDIT: My original post was asking a bunch of questions for how to root my Telstra specific Ice Cream Sandwhich phone. I have now done this and it was surprisingly easy.
The easiest way is to follow the following guide here (which is already Telstra specific).
However you will want to use the following kernal (pretty much first step). which is for ICS, you can find this filehere.
I was concerned I would lose my Next G speeds, but all is good. Still getting 6000kbps at home!
Cheers
Thanks Great Info

[DEPRECATED]--[AROMA][PATCH]MasterPatch Aroma for SGH-I537

ATTENTION: THIS INFORMATION IS DEPRECATED!
I am leaving the thread up for reference, but as I no longer have the device and haven't been keeping up on the development of the I537, many of these methods may not (and probably won't) apply any longer. Please search the subforums for recent information.
Standard Disclaimer: Flash this at your own risk. I am not responsible for any problems that this file may cause, up to and including bricking your device.
Current Version: MasterPatch v.0.92​
Choice of Kernel Modules for MF1, MF2, or MF3
Optional Add-Ons:
-Camera Fix - still no stock camera support
-Hardware Keys support for S4 ROMs
-Speaker-Phone Fix
-Edited "gps.conf" file for faster GPS fix in the United States
-I537 build.prop
-apns-conf.xml file - This may make it so that you do not need to manually input your APN on a ROM for another carrier
FOR NOW, ONLY FLASH AFTER A FRESH ROM INSTALL AND BEFORE FIRST BOOT
Introduction:
After making several MasterPatch zips combining patches and features (mostly to make regular S4 ROMs compatible with the S4 Active I537), things started getting tedious. I decided to make an Aroma Installer Zip which will allow for anyone to to pick and choose what he/she wants.
Note:
Immediately after installing a ROM in a new slot, flash the MasterPatch. Do not reboot in between.
PLEASE SUGGEST ANY OPTIONS THAT YOU WOULD LIKE TO SEE IN UPCOMING VERSIONS
Thanks:
Hashcode for SafeStrap
TreyLWalker & jrkruse for the S4_Active_Call_Record_Fix.zip which fixes Speaker Phone
Lejay for the Camera Fix
Darkman for the Hard Keys Fix
Ayush Singh for the incredible guide on Aroma
Devo7v for recommending I try my hand at Aroma
Instructions on editing the code:
If you want to add your own personal options to the installer, you will need to:
-Extract the zip
-Add code to /MasterPatch_v.XX/META-INF/com/google/android/aroma-config to give the option in the installer's UI
-Add code to /Masterpatch_v.XX/META-INF/com/google/android/updater-script to install the files if the option is chosen in the UI
-Place corresponding files in /MasterPatch_v.XX/AROMA/CHECKBOXx/ or /MasterPatch_v.XX/AROMA/WINDOWx/ depending on where the option is chosen in the UI
DOWNLOAD ON ANDROID FILE HOST:
MasterPatch_v.0.93
MasterPatch_v.0.92
CHANGELOG
Version 0.93 20Nov2013
- UI Improvements
- Removed APN option...still working on it
- Added Camera apk from KitKat
Version 0.92 19Nov2013
- Initial Release
reserved
Random reboots after flashing on the GPE ROM
Sent from my SAMSUNG-SGH-I537 using Tapatalk
dave5777 said:
Random reboots after flashing on the GPE ROM
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
Was it a fresh ROM install? What firmware version are you on? What options did you choose?
Sent from my GT-I9505 using Tapatalk
my-blue-snog-box said:
Was it a fresh ROM install? What firmware version are you on? What options did you choose?
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
No dirty with Dalvik and Cache wipe mf1 speaker phone, GPS, cam
Sent from my SAMSUNG-SGH-I537 using Tapatalk
dave5777 said:
No dirty with Dalvik and Cache wipe mf1 speaker phone, GPS, cam
Sent from my SAMSUNG-SGH-I537 using Tapatalk
Click to expand...
Click to collapse
Are you able to re-flash the same ROM in a new slot, flash the MasterPatch, boot, and let me know if you have the same problem? I tried dirty flashes on a few different ROMs earlier and didn't run into the problem.
Sent from my GT-I9505 using Tapatalk
my-blue-snog-box said:
Are you able to re-flash the same ROM in a new slot, flash the MasterPatch, boot, and let me know if you have the same problem? I tried dirty flashes on a few different ROMs earlier and didn't run into the problem.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
OK made a new ROM slot installed GE ROM used Aroma Master Patch selected mf1, cam, and speaker phone. Then wiped cache before rebooting. No problems yet
Sent from my GT-I9295 using Tapatalk
dave5777 said:
OK made a new ROM slot installed GE ROM used Aroma Master Patch selected mf1, cam, and speaker phone. Then wiped cache before rebooting. No problems yet
Sent from my GT-I9295 using Tapatalk
Click to expand...
Click to collapse
Wonderful! I'll make a note in the OP to only flash after a fresh install for now. I will make kernel modules optional in the next build to try and rectify the problems you had.
Sent from my Nexus 7 using Tapatalk 4
You are going to single-handedly save this phone, and I appreciate all the time you're putting into this. I've installed the GPE ROM and then flashed the Aroma package and I've noticed a couple things:
On the welcome page (the page after selecting the theme) for some reason it mentions "Xperia MFPI Devices..." I'm not sure if this is hardcoded and needs to be changed or not.
The MasterPatch Changelog need a little formatting.
Under the patches, I would say somewhere (possibly in red) that the patches are required to be flashed on first boot. This way a new user will make sure those boxes are checked and won't have a reason to complain that the ROM isn't working. I would say something like "These patches are required to be flashed before the first boot of the ROM. Make sure all three boxes are checked." Another option would be to call them "Required Patches" rather than just "Patches". Or, and I don't know if this is possible, have the boxes checked by default so that the user has to uncheck them intentionally.
I don't know if it's worth it, but maybe the option for other gps regions? I know that this is for the i537 that was pretty much only sold in the US, but if you go on Sammobile there are i537 builds for Mexico and Uruguay.
I'm not sure the confirmation box for installation is needed since there's no way to cancel it.
On first boot of GPE there are no APN's listed. I did select the option in Aroma to flash APN settings, but for some reason it didn't take.
Default camera works fine, but that is to be expected since this ROM was built for the Active. I flashed the camera fix regardless.
I hope I'm not being too critical, I think you've done a great job with this and I think it will really help the community.
The only other thing I would add is the AT&T Compatibility Pack for Hyperdrive. The only trick with that is that you would have to make sure it is the last thing that is flashed in Aroma, otherwise it won't work and the APNs will be wrong. I took a look at the pack and noticed there were a ton of files in there which I'm guessing are there because it is based off a Verizon ROM. That said there may be a couple other things in there that are needed for the APN settings and might fix the problem with your patch.
Let me know if you need me to test anything or if I can help you out with anything.
EDIT: Just noticed the LTE MMS fix for Hyperdrive isn't an option. I'm not sure if this is still needed or not since I use Google Voice, but maybe under the optional patches there should be a Hyperdrive option that will flash everything needed for Hyperdrive.
I would also make sure things are being flashed in the correct order, if that makes sense. I'm thinking the APN settings might need to be flashed last, but I could be completely wrong about that.
---------- Post added at 09:42 AM ---------- Previous post was at 09:08 AM ----------
Two other options I thought could be added to this:
T-Moble AWS fix/APN settings
Google Wallet fix. I was able to get it working on my stock slot, I'll have to find the guide I used and post back here later with it. Here are the instructions, reading over them I'm not sure that it's possible to just flash something and get it to work, but it sure would be nice.
Thanks again for doing this.
@Devo7v:
All great suggestions and I really appreciate the feedback. I hope to get to it this afternoon--I just have a few things to take care of IRL and then I will see what I can do.
my-blue-snog-box said:
@Devo7v:
All great suggestions and I really appreciate the feedback. I hope to get to it this afternoon--I just have a few things to take care of IRL and then I will see what I can do.
Click to expand...
Click to collapse
There is absolutely no rush, when you have time you have time. Everybody can get ROMs up and running, this is just more of a convenience thing. Enjoy your real life.
OP updated with new version
Sent from my Nexus 7 using Tapatalk 4
Devo7v said:
I don't know if it's worth it, but maybe the option for other gps regions? I know that this is for the i537 that was pretty much only sold in the US, but if you go on Sammobile there are i537 builds for Mexico and Uruguay.
...
The only other thing I would add is the AT&T Compatibility Pack for Hyperdrive.
...
EDIT: Just noticed the LTE MMS fix for Hyperdrive isn't an option. I'm not sure if this is still needed or not since I use Google Voice, but maybe under the optional patches there should be a Hyperdrive option that will flash everything needed for Hyperdrive.
...
Google Wallet fix. I was able to get it working on my stock slot, I'll have to find the guide I used and post back here later with it. Here are the instructions, reading over them I'm not sure that it's possible to just flash something and get it to work, but it sure would be nice.
[/LIST]
Click to expand...
Click to collapse
-The gps.conf still has all the needed code to work anywhere. It just allows for a quicker fix in the US.
-I don't think I'm going to add the Hyperdrive compatibility patch or LTE fix because they are specific to one ROM and I want to keep the size down.
-I plan on working on Google Wallet in the future.
Thanks again for the suggestions.
Sent from my GT-I9505 using Tapatalk
Btw, the newest beta build is posted in the OP.
Sent from my GT-I9505 using Tapatalk
Hi, This a really good work. But as a user of the international version of the i9295 i cannot use this patch (but i tried )... Is it possible to make it work on a normal i9295 to use regular or custom S4 roms?
Thanks in advance.
dks21 said:
Hi, This a really good work. But as a user of the international version of the i9295 i cannot use this patch (but i tried )... Is it possible to make it work on a normal i9295 to use regular or custom S4 roms?
Thanks in advance.
Click to expand...
Click to collapse
So this is something that has been bugging me for awhile. I'm not the most knowledgeable person on the subject, but it seems like you should be able to flash an S4 ROM and then flash an S4 Active kernel on top of it. It would have to be a 4.2.2 kernel for 4.2.2 ROMs and a 4.3 kernel for 4.3 ROMs, but it seems that it should work. It was possible to do this when flashing Samsung i9000 ROMs onto the Samsung Captivate. The devices had very similar internals, but the Captivate didn't have a front facing camera. This is a very similar situation to what is going on with the S4 and the S4 Active.
If anybody is adventurous, extract the kernel from the S4A Google Play Edition ROM, flash a 4.2.2 S4 ROM, then flash the S4A kernel on top of it. Make sure to flash the keys fix as well and see what happens. I feel like it should work, but please don't hold it against me if something goes wrong. You can always Odin back to stock.
If this can't be done I would like to know why.
---------- Post added at 09:25 AM ---------- Previous post was at 08:54 AM ----------
my-blue-snog-box said:
Btw, the newest beta build is posted in the OP.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I just went and flashed 0.93 (well, I didn't flash it I just ran through the installer and then quit at the end). I only have a couple comments:
The "Welcome" screen needs some minor formatting:
"You are about to Installing" should say "You are about to install:"
"VERSION" is bold, which is fine but it should have the same formatting (bold/not bold) as "UPDATED" on the next line. I think it would also look better if "VERSION" was on its own line.​
Changelog looks much better, maybe include the day along with the month and year of each version.
On the System Information page, I would make the output text for Device Name, Board Name, and Manufacturer bold just like the output text below it.
Kernel Modules page looks good
On the Other Options page I would:
Make "Required before first boot!" all caps and bold to make it stand out. It is very important that users understand this.
For the descriptions of the mods, most of them are all caps except for the Camera patch description. Pick a format and stick with it.​
I'm not sure if you can change this, but on the About screen it says "ROM Name: MasterPatch" maybe change it to "ZIP Name: MasterPatch"
Like I said above I didn't actually complete the installation, and I can't imagine you changed the functionality so I assume that functionally it works the same as the last version. Again, thanks for doing this.
I was thinking more about the Hyperdrive AT&T Compatibility Pack and I think you're right, it would make the MasterPatch needlessly big. That said I definitely think there is something in there that corrects the APN. If and when you do get the APN setting working I would have an option for the T-Mobile APN as well.
@dks21, are you willing to try what @Devo7v recommended? If so, I am willing to work with you on a project for your device.
Sent from my Nexus 7 using Tapatalk 4
Devo7v said:
If anybody is adventurous, extract the kernel from the S4A Google Play Edition ROM, flash a 4.2.2 S4 ROM, then flash the S4A kernel on top of it. Make sure to flash the keys fix as well and see what happens. I feel like it should work, but please don't hold it against me if something goes wrong. You can always Odin back to stock.
If this can't be done I would like to know why.
Click to expand...
Click to collapse
I have already tried something like this. In a total freestyle manner, i tried to flash the cyanogen 11 kitkat for i9505 ( this one: http://forum.xda-developers.com/showthread.php?t=2521384 ) and
the kernel provided here (probably not suitable) http://forum.xda-developers.com/showthread.php?t=2395242... But It didn't boot at all
dks21 said:
I have already tried something like this. In a total freestyle manner, i tried to flash the cyanogen 11 kitkat for i9505 ( this one: http://forum.xda-developers.com/showthread.php?t=2521384 ) and
the kernel provided here (probably not suitable) http://forum.xda-developers.com/showthread.php?t=2395242... But It didn't boot at all
Click to expand...
Click to collapse
So I think I know what you're problem is, you are flashing the S4 ROM which is 4.4, but then on top of that you are flashing the S4A kernel which is 4.2.2. The ROM and kernel versions need to match, so you need to either get a 4.4 version of the kernel or you need to flash the 4.2.2 of the S4 ROM.
Do me a favor, flash this ROM and then flash LeJay's kernel on top of it. Since they are both based off CM10.1 hopefully it will work. If it does than that means you need a CM10.2 kernel from LeJay to flash CM10.2 based-ROMs and a CM11 kernel from LeJay to flash CM11-based ROMs. I searched through LeJay's threads to find newer kernels but I couldn't find anything other than CM10.1. I noticed he released a CM10.2 ROM so you may be able to extract the kernel from that, but this is pretty much where my knowledge stops.
EDIT: The important thing to remember is that the ROM version and the kernel version must match to even have a chance at this working.
my-blue-snog-box said:
@dks21, are you willing to try what @Devo7v recommended? If so, I am willing to work with you on a project for your device.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
;;;
I am OK to test things. But as far as my knowledge about how to " compile, program, extract kernel and so on", is limited, I am affraid that my role would only be beta-tester...

[Q&A] [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/28]

Q&A for [AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.
NEO2598 said:
One simple question.
The builds from aospa are 4.4 sources or 4.2?
Thanks in advance.
Click to expand...
Click to collapse
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk
MeestaAytch said:
@houstonn was originally developing but stopped in June due to computer failures which is being resolved soon. His last build of 6/29 was on 4.4 sources and required the modem of stock 4.4.
The current builds supplied by @ayysir and now @jakew02 are on 4.2 sources which would require that specific modem.
Which ones exactly not sure as I am not familiar with every carrier version only sprint.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
It has been stated in the ROM thread multiple times that you must use a 4.2 STOCK JB MODEM for best compatibility. Any other modems you guys use is solely at YOUR OWN DISCRETION. @MeestaAytch they should know what to use at this point but thanks for clarifying again for those who don't want to search before posting :highfive:
@jakew02 no problem. I know it's tiring repeating the same information but from what I've seen in my time using XDA.... It'll never change.
I'm glad you devs still continue doing what you're doing for us though knowing this nonsense goes on.
Sent from my LG-LS980 using Tapatalk
A few bugs
Hi,
The thread is too big for me to go thru it post by post so I'll just make a few questions and hopefully I'll get some answers. I flashed this ROM and it was working flawlessly. I only found very few bugs like not being able to set up multiple recurrent alarms because the app would freeze and there was another bug but I can't remember. The problem I find frustrating is with the text messages or SMSs. At first I was not receiving SMSs. Then I was receiving them but I couldn't send any. I returned back to stock VS98024a and I'm still having the same problem but at least I'm getting a pop-up when "General problems: cause code 96". I have googled this several times in several ways and can't seem to find a solution, not even on the Verizon site or help app on the phone. I need help with this please.
How to keep the back home task manager buttor on the screen?
battery life? i want to install on lg d800 and its beta only..
dori kernel
Hi,
From where you get Dorimanx kernel for AOSP ROMs ?
My phone says it can't connect to the camera, and the torch. Does anyone know how to solve this?
Sent from my LG-LS980 using XDA Free mobile app
LG G2 D802 SIM not recognized
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex
a13xch1 said:
ok, so im quite familiar with flashing roms etc, ive had cyanogenmod and cloudy g3 installed on my d802 without any problems however when i flashed paranoid android 4.4 (i used the appropriate one for my model) i am left with no service, it seems that my sim is not recognised . ive tried reflashing several times and even reflashed my old rom which worked (calls, texts data) please could someone help me as i love the look and feel but cant use my phone without radio.
im using twrp recpvery aswell
Alex
Click to expand...
Click to collapse
Please state exact filename and order of wipe/flash.
Just tried the test build for D802. Booted at LG logo for a while then screen turned black with 2 red lines and one green vertical line. I was so sure I was gonna get the permanent black lines but then again I read that the damaged screens are caused by already faulty hardware under high heat.
Anyways, I panicked and then I restarted the phone by pressing power + down. Then I got the weird boot sequence like everyone above describes and it boots into the OS. Thank God I got no black lines! However it wasn't stable for me as the phone rebooted itself twice within the span of 20 minutes. I'm going back to 13/10 build for now.
Any d802 users flashing latest twitter released rom can you please report here if jdi or lgd and whether or not weird logo appeared?
I'm on jdi and had weird logo appeared after clean flash. I did not let the rom boot and reflashed previous version without further problems
FYI, houston's latest works great so far on the VS980. Clean flash, using RenderKernel R24.
So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up
jclemens23 said:
So i have the vs980 and i currently have xdabbebs rom on my phone, but i want to try PA. Can someone explain how to flash a rom over another rom, or is there something else i should do. i tried it once by flashing with twrp and it just hung on the lg sreen. luckily i had a back up
Click to expand...
Click to collapse
Migrating from one ROM to another is for me like this:
1. Nandroid backup
2. Wipe all except sdcard (yes, wipe system)
3. Flash new ROM
Be sure to always have a Nandroid backup!
And always check what baseband (aka radios or modem) your new ROM is requiring.
-___-
If you are UPDATING your current ROM, I.e. flashing a new build of let's say paranoid android, you can flash the updated file right on top of your old system. That is called DIRTY FLASHING and it's actually risky, so please, always do Nandroid backups!
-____-
Peace
Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed
jclemens23 said:
Thank you for the reply. I tried doing it the way you suggested again and i get the same results. I wipe everything that is necessary and when i try to install the zip it immediately says failed
Click to expand...
Click to collapse
Ok
I would;
Update my custom recovery to the latest
Download recommended baseband, to be on the safe side
Redownload the ROM
Check the md5-checksum
Retry to install it
Flash the recommended baseband, better safe than sorry
Never give up
Peace
Hi guys i just flashed the newest build and out of all the roms i have flashed i have never seen this problem. After i flashed i have no sim service at all. Done a clean install still no good.

[Q&A] [=ROM=][4.4.4-NI2][900V] OptimalROM (SlymHyde) R12 -=SPEED - STABLITY - SMOOTH

[Q&A] [=ROM=][4.4.4-NI2][900V] OptimalROM (SlymHyde) R12 -=SPEED - STABLITY - SMOOTH
Q&A for [=ROM=][4.4.4-NI2][900V] OptimalROM (SlymHyde) R12 -=SPEED - STABLITY - SMOOTH=- 9/23
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=][4.4.4-NI2][900V] OptimalROM (SlymHyde) R12 -=SPEED - STABLITY - SMOOTH=- 9/23. 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!
updating from 11-2
Hi
If I'm already on R11-2, how do I update? Do I just flash this to the same slot (after backing it up)? Do I need to flash the NI2 firmware tar again?
Thanks
belleguttman said:
Hi
If I'm already on R11-2, how do I update? Do I just flash this to the same slot (after backing it up)? Do I need to flash the NI2 firmware tar again?
Thanks
Click to expand...
Click to collapse
Read through the OP right before the download section. Its all there :good:
Flashing From Stock
Sorry for a total noob question, but I'm new to flashing and I'm paranoid
It says in the first post to do a full wipe if coming from a different ROM... Would stock TW count as a different rom? Or can I dirty flash this to the stock slot without doing anything else?
GoldenArcher96 said:
Sorry for a total noob question, but I'm new to flashing and I'm paranoid
It says in the first post to do a full wipe if coming from a different ROM... Would stock TW count as a different rom? Or can I dirty flash this to the stock slot without doing anything else?
Click to expand...
Click to collapse
No worries ask away. Yes stock TW would be considered a different ROM.
Not sure if anyone is having this similar problem, but I cannot seem to get the flashlight toggle to work. I flashed the fix file multiple times and still nothing. Any ideas? (I'm on R12-2)
S Health Crash
I'm having healthservices crash constantly. I went from "stock" rooted 4.4.4 to your 12-2 release with a dirty flash. Do I need to wipe anything? For now I turned off S health and everything else seems to be working fine.
xXAaron04Xx said:
Not sure if anyone is having this similar problem, but I cannot seem to get the flashlight toggle to work. I flashed the fix file multiple times and still nothing. Any ideas? (I'm on R12-2)
Click to expand...
Click to collapse
If you can't get it working, backup your apps and clean flash.
g3llings said:
I'm having healthservices crash constantly. I went from "stock" rooted 4.4.4 to your 12-2 release with a dirty flash. Do I need to wipe anything? For now I turned off S health and everything else seems to be working fine.
Click to expand...
Click to collapse
As stated in the OP, flashing from a different ROM (stock is a different ROM) you need to clean flash.
BigBot96 said:
If you can't get it working, backup your apps and clean flash.
As stated in the OP, flashing from a different ROM (stock is a different ROM) you need to clean flash.
Click to expand...
Click to collapse
Thanks! After it brought me to the q&a I saw the other post and realized this. I wiped, flashed 12-2 and updated to 12-4. Running very fast, no issues so far!
Latest update..... Can we dirty flash.?/or should we clean wipe
Sent from my SM-G900V using XDA Premium 4 mobile app
RiggsDaRuler said:
Latest update..... Can we dirty flash.?/or should we clean wipe
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Dirty should be alright.
Is there any way you could mirror the download on another site? I currently do not have a computer at my house and I have to use a work computer which has androidfilehost blocked. I would very much like to receive the latest updates to this wonderful rom.
Xxirs said:
Is there any way you could mirror the download on another site? I currently do not have a computer at my house and I have to use a work computer which has androidfilehost blocked. I would very much like to receive the latest updates to this wonderful rom.
Click to expand...
Click to collapse
Here ya go! OptimalROM_R12-5.zip
Oh my goodness thank you so much!
Is anyone else having a problem with the regular Amazon app force closing? Amazon app store works fine.
Sent from my SM-G900V using XDA Free mobile app
DarkWaveZ said:
Is anyone else having a problem with the regular Amazon app force closing? Amazon app store works fine.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Mine works. When in particular does it FC?
Works pretty well. Battery life has definitely improved.
NI2 Firmware
So, what happens if I don't flash the NI2 firmware with ODIN after flashing the ROM with safestrap? In my haste to get this up and running I may have run out of the house before flashing the firmware. As of now it's running fine and it says my build is OptimalRom. I can see Viper has installed and the volume up flashlight tweak is working. It seems to be mostly there short of the extra toggles in notifications.
Chances are I'm going to get home later and fix this, but I was just curious because at the moment my phone is running great.
jcarv85 said:
So, what happens if I don't flash the NI2 firmware with ODIN after flashing the ROM with safestrap? In my haste to get this up and running I may have run out of the house before flashing the firmware. As of now it's running fine and it says my build is OptimalRom. I can see Viper has installed and the volume up flashlight tweak is working. It seems to be mostly there short of the extra toggles in notifications.
Chances are I'm going to get home later and fix this, but I was just curious because at the moment my phone is running great.
Click to expand...
Click to collapse
It would probably work on other firmwares (since rooting NI2 requires downgrading), just not 100% stable and you'll probably get many FCs. What's your baseband say? If it ends in NI2, then you're fine. If it says NE9 or NCG or NHA, then you'll want to flash the NI2 firmware.
BigBot96 said:
It would probably work on other firmwares (since rooting NI2 requires downgrading), just not 100% stable and you'll probably get many FCs. What's your baseband say? If it ends in NI2, then you're fine. If it says NE9 or NCG or NHA, then you'll want to flash the NI2 firmware.
Click to expand...
Click to collapse
Baseband ends in NI2. But, like I said, it's running pretty much flawlessly. Being paranoid of something down the line not working correctly I'm probably just going to fix it later tonight though. Thanks for the quick response! If this is not 100% than I'm going to be extremely happy when I re-do it later and get it working correctly. Cheers.

EFIDroid for the Samsung Galaxy Note 4/Note Edge (Snapdragon Variants)

More details in the Verizon Note 4 forum here.
XDA:DevDB Information
EFIDroid, Kernel for the T-Mobile Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-20
Last Updated 2017-03-31
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
vegoja said:
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
Click to expand...
Click to collapse
Believe me, I didn't do much work. You can donate to @m11kkaa, though. He's the developer of EFIDroid (if you didn't already know that...). I believe he has a donation link in his profile...
Sent from my Samsung Galaxy Note 4 using XDA Labs
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Mtotallywired said:
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Click to expand...
Click to collapse
EFIDroid is what you would call a "second-stage bootloader". The main advantage over Dual Boot Patcher (at least for me) is that you no longer have to patch zip files before installing. Also, EFIDroid is more than just a multi-boot solution. Quoting @m11kkaa:
efidroid tries to focus on simplicity, and doesn't require any kernel modifications etc.
in general: well having such a powerful bootloader in your boot stage gives you lots of possibilities, like multiboot, replacements/additions for kernels/ramdisk/cmdline.
This project has a lot more potential than what's currently implemented. i.e. you can give samsung devices fastboot and sony devices a standalone recovery. Also you can natively boot GNU GRUB if you're into booting linux kernel's the desktop way.
Click to expand...
Click to collapse
The two solutions are similar enough that you can migrate your setup from Dual Boot Patcher to EFIDroid without losing any data. I'll try to post a guide later this week.
I was I under the impression dual boot required multiple ROMs running the same kernel... If that is the case a huge advantage efi has is each ROM having their own boot img. I'm currently running 3 ROMs a lollipop a marshmallow and of course a nougat. I really just wanted to see all 3 latest android os running flawlessly on 1 device. And I did just that hats off to the developer for this.
baharvey7817 said:
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
Click to expand...
Click to collapse
There's an uninstall button in the app. Or, you could just flash the original boot.img via TWRP (basically what the uninstall button does).
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
mlock420 said:
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
Click to expand...
Click to collapse
you can look at their website, and then decide if you want this level of control over your phone.
http://efidroid.org/
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
1freedude said:
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
Click to expand...
Click to collapse
There's no way to have two different bootloaders. EFIDroid comes between the bootloader and the boot.img, so it has no control over the bootloader.
EDIT: EFIDroid may be able to emulate the behavior of another bootloader... you would have to ask @m11kkaa for details...
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
CousinMikeyP said:
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
Here is the LINK. You can see more info HERE
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
I will have to look into it... The EFIDroid app error messages are not exactly the most helpful kind. (Good thing the app is being phased out soon). That particular error message could mean many things, but most likely it's a connection issue. We will continue this in Slack.
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
RaySCLA said:
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
Click to expand...
Click to collapse
Tried what you suggested but it didn't work either. So, I chose the 'nuclear option': I wiped the phone completely then reinstalled the stock Marshmallow ROM. using Odin. After that i installed TWRP v3.0.2 (trltetmo) and Supersu v2.79 as well as Busybox v1.26. Only then was I able to install EFIDroid successfully. Now, I'm able to boot the stock rom as well as Resurrection Remix.
It seems that if your going to install EFIDroid you must have the phone rooted using SuperSU. Using Magisk to root your phone instead of SuperSu won't work (at least it didn't work in my case).
lowkeyst4tus said:
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Click to expand...
Click to collapse
This should work anywhere, regardless of ROM... But btw, it's a stretch to say TW is just a skin on top of AOSP. In fact, TW is probably the farthest you can get from AOSP... There's a lot of significant differences that make AOSP kernels incompatible with TW ROMs...

Categories

Resources