Related
CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded
I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.
Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Any comments from people that have this applied (and working with full root)?
Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
That worked Thanx
Kernel's working just fine with Avalaunch's Froyo ROM.
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.
lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!
Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.
Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk
With Sunshine unlocking droid Turbo Bootloader I will be moving on to making ROM's not just an img. please see my Forum on XDA here and my Website Computerfreek.com Here for more info.
I will continue to do MOFO support for the next month or so as users make the switch.
Computerfreek274_Turbo_lollipop (SU4TL-44)
Also On my website Computerfreek.com Now has updated help and support how to setup stuff like adaway,Boot anamation, Dpi and more. Also I will be posting Pre-Released images there days be for there on XDA. There will also be images some custom images that will not ever be listed on here on XDA for I will not support them. So please check out the site it is still a work in progress but it is getting there. As of right now I did not get custom IMG listed and the newest ver is still 1.6 and it is listed below.
This Firmware upgrade to 5.1 SU4TL-44 from 4.4.4! VIA Mofo.
If you took the OTA 5.1 update you out of luck as you where told not to on here over and over. Go check out sunshine root maybe coming soon for locked 5.1 users.
If this software somehow kills your phone I am not to be held liable.
PLEASE BACKUP YOUR DATA 1st For the best speed and no bugs if you are coming from 4.4.4 for the 1st time I recommend that you backup your photos,music and other data. and when you get to step 3 wipe Data and cache. It is not a must but for me to give you support this is a must.
Thanks to @firstEncounter for his great post and images. Thank you @mattlgroff for his help and everyone who sent me links to the OTA and Full ver.
Thanks to http://motofirmware.center/files/ for hosting stock lollipop IMG's so I an update missing or outdated system files I had.
Big Thanks for PON-3 Audio mod from @mrchezco1995 and his forum is here
Please support better battery stats and give a big thanks over on there forum here. The better battery stats companion app installed in 1.4 will only work with paid ver of bbs from google play.
Thank you guys so much.
Features:
Stable! - I don't publish images without exhaustively testing them. If you have any issues to report, reply to this post and either myself or the community will rally to help fix the issue.
Much better battery life! - This image focuses on battery savings without compromising performance. Your phone will last much longer while running this system image.
Multiple versions - Custom version from DPI dpi higher resolution to Custom fonts
Fast! - This image is lean, fast, and enhanced for performance.
No bloat! - All bloat that is available on the Play Store has been removed. Extra files (like help videos and help audio files) have also been removed.
Optional adblocking! - Adblocking via AdAway that can be toggled on and off.
Now with Pon-3 Audio/ V4A - Increase the volume and the quality of audio output from the Droid Turbo by enabling VIPER4Android which comes bundled in this system image.
Enabled for XPOSED Updated to newest ver. - This system image has been enabled for the XPOSED framework as well as includes BusyBox.
For better support I have removed old versions on here my focus is to have better support for all of you starting from 1.5+
Please Read! If your not on Kernel Version 3.10.40-perf-g90ddf4a Sept 1st 2015 Please Download and flash all .IMG files in this zip here. To find the kernel build go to settings > About phone. Most of you guys will need to update!
Computerfreek274_TurboPop_1.6 Update. 11/07/2015
Now With Turbo 2 Command Center. Screenshot
Download 1.6 Here
Change Log.
Updated .img files in 1..6 No need to download Img pack when upgrading from KK or to update your kernel,modem,etc... all files are updated 1.6 Zip.
Cleaned up some more junk from system
Updated some apps.
Removed music2 aka google music.
Samsung Sans Font IMg's has the IOS9 emojis.
Turbo 2 Command Center
Download 1.5B Here Updated 10/16/2015 Base on SU4TL-44
Download 1.5 Here 10/5/2015
Custom fonts in 1.4 I will update 1.5 as needed.1.4 Download Here.
All Files and IMG's files that are needed to install my IMG are Zipped with all my system images from ver 1.3 and up Just download 1.4 or 1.3 and unzip open the help file and do a step by step install.
Please Read 09/12/2015 For Android Pay support and Setup please see Post #3
You can still download 1.3 and 1.3A here.
[/URL].
1.5B Change Log 10/16/2015.
Updated to SU4TL-44
Updated Xposed
Boosted overall audio and mixer profile updated
Fix Pon-3 audio buffer for large audio high bit rate files buffer from 32m to 48m
Few other tweaks also see 1.5 for more info. This has all the tweaks from 1.5 and 1.5 is the best battery and fast running ver to date.
1.5 Change Log 10/5/2015
Removed more junk like maps and stuff as you have updated ones from market.
Added for more Tweaks for faster GPU and CPU and more memory.
In call VOL boosted default was max 3 now max 10.
Better GPS.
Battery Seems much better with memory fixes.
1.4 Change Log 6/12/2015
Android Pay Support Please see post #3 For more info.
Custom Fonts There will be 1.4 img with custom fonts. More to come check one of the last post for more info.
Some Of the changes listed here is from 1.3A
PowerSave Is in all from 1.3A and up.
Removed some more bloat.
SuperSU is the stable ver.
Xposed to newest ver Please uninstall your old xposed.apk be for you flash.
HDR Camera setting is fixed as of 1.3A
Updated some system files.
Tweaked GPS a bit for faster lock.
PON-3 updated
Fixed audio profiles for PON-3 to match are turbo for a more stable PON-3 audio.
Updated Mixer Profiles for better audio.
mixer_paths updated louder audio as we had in my ver of KK. 09/02/2015 I had to make a new one for Lollipop as the old mods did not work.
updated to work better with the turbo Pon-3.
There is now a set of 1.4 Pure/MAX IMG's also for none Verizon users only.
More help and support can be found on my website at Computerfreek.com for full install and updates Or read below.
How to install
See Post number 2. http://forum.xda-developers.com/showpost.php?p=61636340&postcount=2.
To setup DPI,Adaway and more.
To install system img via mofo see post 2.
Setup Adaway Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/host Then go back and hit update host files.
Xposed In Pre-installed and setup just install the mods you like to use.
On Pon-3 V4A Open Pon 3 and check the sound devices you like to enable.
Setting up an custom boot animation place bootanimation.zip under /data/local/moodle/bootanimation.zip for more info or watch this small video on how to. https://www.dropbox.com/s/lom6zduant...rding.mp4?dl=0
For 493 Builds to fix the ambient display being off set you must install xposed MOD app settings found here or download it from inside of xposed. and set moto diplay to 640 DPI. If you need more help check the forums here.
Flashing from KitKat to Lollipop
This is a nice well written guide by @Purpeltendire Thank you @Purpeltendire Thank you for this great guide.
If you are new or upgrading and need more help I updated help and info on my website also at computerfreek.com
Steps to flash from KitKat to Lollipop - This assumes that you're currently using a rooted KitKat image already, and have used mofo to get root.
BACK UP ANY DATA YOU DO NOT WISH TO LOSE.
YOU ARE ULTIMATELY RESPONSIBLE FOR ANY LOST FILES OR DEVICE PROBLEMS.
Make sure you have a good hour or two set aside, at the minimum. It’s probably not a great idea to try this right before work or class.
Install mofo, ADB, and fastboot on your computer if you haven't already. On Windows, I like using this for ADB/fastboot.
Download the image of your choice.
Download 5.1_images.zip. Extract the files, and put them into the same directory as fastboot. Next, boot into your phone's bootloader (turn the phone on by holding power and volume down), and flash each file seperately using fastboot:[/FONT]
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Now open mofo_gui.bat, and flash the system image you downloaded:
Code:
mofo flash Your_imagename_here.img
Once that finishes, you want to try to boot the phone. Select Boot to System from the bootloader and then go grab a snack - chances are, it will sit at the Motorola boot screen for some time. After about five minutes, press and hold power to turn the phone off.
Next, boot into the bootloader again and select Recovery. You will likely get a "Dead Android" screen with "No Command." To bypass this, hold power and tap volume up (if that method does not work after a few tries, hold volume up and press power).
Now that you're in recovery, you're wiping both data (factory reset) and cache. Wipe cache first - this may take a very long time (20-30 minutes), especially if you've never done it before. Wipe data/factory reset second. If you're feeling paranoid, wipe everything again.
From recovery, boot to the bootloader. From bootloader, boot to system. This first boot might take some time as well.
Assuming all went well, you should see a Lollipop setup screen within 10-15 minutes. Congratulations!
Remember that your device is now in “like new and improved” mode. You’ll need to restore your apps and settings from wherever you backed them up to, and you'll still need to get the APKs for Xposed and AdAway. Again, nobody else is responsible for any of your lost data.
[FONT=Arial[/FONT]
For more help see Computerfreek.com
Android Pay Setup and Support. 9/28/2015
Update The updated android pay from google market is no longer working with root so if you flash back to an rooted img after setting up this one android pay will stop working.
9/30/2015
For Working android play and info please go to this forum I have made an IMG with tweaks and more here with working android pay.
Tomsgt said:
just talked with the dev behind moforoot and he said that mofo was patched in android 5.1 but he may look into other ways to get around it.
Click to expand...
Click to collapse
This was stated in another thread. I don't know if you heard, but I'm holding on that there's still hope. Is there still a possibility to be able to make a rooted image? I'm really hoping that we'll be able to have root with lollipop, but at the same time, I don't want you to put in all this time and effort for nothing.
Sent from my XT1254 using XDA Free mobile app
There's a lot of places with the ota, try one of them
Jaocagomez said:
There's a lot of places with the ota, try one of them
Click to expand...
Click to collapse
he needs the firmware img's
Michaelmansour1997 said:
he needs the firmware img's
Click to expand...
Click to collapse
Those will be released in the following days
Jaocagomez said:
Those will be released in the following days
Click to expand...
Click to collapse
noooo i need them today to fix my paperweight
Ahhhhh! I can barely wait!
Downloading the update NOW.. How do I get a dump and copy of the firmware OFF the turbo? Where is it located.. Using ES File Explorer to access /
MoPhoMike said:
Downloading the update NOW.. How do I get a dump and copy of the firmware OFF the turbo? Where is it located.. Using ES File Explorer to access /
Click to expand...
Click to collapse
I am far from the skill level of any rom creator but every google guide I've found seems to indicate root (even temporary root) is required to do a system dump. Is temporary root possible on the lolipop update? If theres another way, please post a guide @computerfreek274 so one of the people who has updated is able to easily help us out and get the ball rolling.
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
TheSt33v said:
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
Click to expand...
Click to collapse
Yes but I like to get ahold of a system dump. I been working on the ota today.
Pretty stoked!
Sent from my XT1254 using Tapatalk
siegesoldier said:
I am far from the skill level of any rom creator but every google guide I've found seems to indicate root (even temporary root) is required to do a system dump. Is temporary root possible on the lolipop update? If theres another way, please post a guide @computerfreek274 so one of the people who has updated is able to easily help us out and get the ball rolling.
Click to expand...
Click to collapse
If you Google it there was a way to do it without root. I do not care if it is a system.img dump like that. If you can just copy the system folder to your sd card i do not think you will need root for that use es file man and send it my way that will be great.
Want to make sure so if you have root via MOFRO then you should wait and not install the OTA and wait for new System Image from the Freek!!!
computerfreek274 said:
Yes but I like to get ahold of a system dump. I been working on the ota today.
Click to expand...
Click to collapse
Gotcha. Well unless someone has had luck with Kingroot (early reports said that it didn't work), I don't think that will be possible.
EDIT: Nevermind. It's totally possible. I'll try to track down someone who can get it to you.
computerfreek274 said:
If you Google it there was a way to do it without root. I do not care if it is a system.img dump like that. If you can just copy the system folder to your sd card i do not think you will need root for that use es file man and send it my way that will be great.
Click to expand...
Click to collapse
Pulling /system with adb should be easy and noob-proof.
Sent from my LG-E400 using XDA Free mobile app
TheSt33v said:
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
Click to expand...
Click to collapse
there are no system img's in the ota, its a flashable zip not an xml
Is this what we're looking for?
http://forum.xda-developers.com/droid-turbo/general/lollipop-5-1-coming-23-11-38-t3146663/page4
I have the restore firmware ... where should I host it?
VRZ_XT1254_SU2-12_12_1FF.xml.zip
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/general/droid-turbo-lolipop-firmware-t3147979
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for other devices too. (See the list below to see if your device is supported)
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the features in this tool
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Background
The Android CDD (Compatibility Definition Document) suggests demands that all devices with the appropriate horse power SHOULD MUST enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. Full-disk-encryption comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in current devices it's the CPU's task. Even though modern devices have quite fast CPU cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any scientific measurements though)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome. Additionally, Google's stock ROMs always have forced encryption enabled on newer devices.
Because performance is important to me and at least my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher).
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then, if necessary, it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
LG Nexus 5X (bullhead)
Huawei Nexus 6P (angler)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
v8 - Added support for LG Nexus 5X (bullhead) and Huawei Nexus 6P (angler)
What do I need to make this work?
A supported device
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
GibHub: https://github.com/gladiac1337/fed-patcher
XDA:DevDB Information
FED-Patcher, Tool/Utility for all devices (see above for details)
Contributors
gladiac, rovo89
Version Information
Status: Beta
Current Beta Version: v8
Beta Release Date: 2015-10-27
Created 2015-10-27
Last Updated 2016-10-23
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently running stock Marshmallow on my Nexus 6 and i plan to stay like that, but would like to test my device with ForceEncrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
cyberon said:
Hi @gladiac and first of all thanks for the work and time spent developing this amazing tool.
I'm currently on stock Marshmallow and i plan to stay like that, but would like to test my device with forcencrypt disabled. Here are my doubts.
1 - Does this work on stock?
2 - Would i be able to flash the monthly security update images without having to wipe my device every time?
3 - In your opinion, do the speed gains justify the all the work?
Thanks in advance.
Click to expand...
Click to collapse
Hi @cyberon,
good questions!
Yes, FED-Patcher works on stock! Marshmallow made it necessary to do a new release, v7, to get rid of an error message at boot but other than that, FED-Patcher works just fine on Android 6.
Well, I don't know how the monthly security-updates will be deployed. I guess it will be done by OTA (Over the Air) updates. OTA will probably not work after modifying the boot-image. However, flashing factory images should work just fine. Additionally, most of the time, OTA-zips are being posted here on xda or androidpolice whenever they become available so doing manual OTA updates is another possibility to do updates.
To get back to your question - wiping should not be necessary after an upgrade - be it via OTA or factory images. Google did a fantastic job with the upgrade-functionality in newer Android versions. However, whenever you do an update, be sure to run FED-Patcher afterwards because, in case the boot-partitions got updated, forced encryption will be in place again and on the first boot it will encrypt you device.
Well, I do all my tests on a HTC Nexus 9 (flounder). It is a pretty fast beast. However, on an unmodified stock rom, it was clearly tangible that the GUI had more latency than necessary. Apps loaded pretty slowly - compared to my Sony Xperia Z1 (honami) it took like twice as long to start youtube - and in general it just did not behave like a beast. This was why I started writing FED-Patcher. In my opinion it was worth my time. (it wasn't that much actually)
I hope I could help.
Enjoy, gladiac
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Am i missing something?
cyberon said:
Thanks for the quick and detailed answer @gladiac, now regarding point number 2.
I never wait for the OTA, but always flash the images manually.
As far as i understand from your answer, it would it be ok to flash all the img files manually, then flash TWRP and finally flash FED without booting the OS.
Click to expand...
Click to collapse
That's pretty much how I would do it. You don't even have to flash TWRP if you just skip flashing the recovery.img which is included in the factory-image package.
Thanks @gladiac, will try that way.
PS: I have a feeling that if we had this option added to a toolkit like Wugfresh Nexus Root Toolkit, it would be an instant success.
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Worked on my N9 - thanks!
provolinoo said:
hi @gladiac
first of all thanks for your patch
I'm on Nexus 6 with stock Marshmallow and all I want to do is disable encryption and enable root.
Is your patch + SuperSU enough or I need something else?
Thanks a lot
Click to expand...
Click to collapse
Hi @provolinoo,
well, FED Patcher will disable the forced encryption for you. However, SuperSU will not work so easily. The reason for that is that the stock ROM has SeLinux enabled in "enforcing" mode. SuperSU does not work without adding more SeLinux Policies to the stock ROM. Unfortunately, it's not in the scope of FED Patcher to add SeLinux policies for SuperSU. This should be done inside the flashable ZIP of SuperSU instead.
The last time I tested SuperSU with marshmallow stock was with version 2.52 BETA. It did not work. The result was a boot-loop because of one or more SeLinux denials. A little more info on that matter is here.
So, to get SuperSU working you would have to set SeLinux to "permissive" mode. Alternatively, you can use @Chainfire's boot.imgs to make SuperSU work.
Have fun, gladiac
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9. Edit: I am using TWRP 2.8.7.1
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
dmantilal said:
Thank you gladiac. Your FED patcher (v8) works flawlessly on my Nexus 9.
The gerrit conversation you linked is interesting. I am grateful that someone with your skills decided to support our ability to choose whether or not to encrypt. CM thinks I am smart enough for root priveleges but I am too stupid to be trusted with decryption?
Don't some major vendors allow the disabling of encryption from within Android?
Anyway, thanks for the patcher.
Click to expand...
Click to collapse
I agree, I love CM roms but their decision to force encryption when most of cm users are power-user is a nonsense
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
jamesalfred said:
Sooo....basically, I cannot use a stock Marshmallow that is FEDpatched and with root (using SuperSU, unless there is alternative)? If I want those, I have to get one of the custom ROMs?
EDIT: also, I tried using Chainfire's modified boot. It is stated that it will disable the forceencrypt. It didn't work in mine, still encrypted.
Click to expand...
Click to collapse
Did you follow the directions and format the entire "data" partition?
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
nextelbuddy said:
I too have the same problem didnt work for me.
im on the the new 6.0 L build but went ahead and flashed the modified boot image for K build just so I could flash the TWRP img.
Once TWRP was installed, I installed the Fed path ZIP and that went well supposedly. and then after that I did a factory reset, then I WIPED the DATA, CACHE and Dalvik.. I rebooted setup my device and it still shows encrypted.
Click to expand...
Click to collapse
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
dmantilal said:
Did you follow the directions and format the entire "data" partition?
Click to expand...
Click to collapse
dmantilal said:
It did not work because you did not follow the directions.
Flash TWRP. Flash FED. Full wipe (or format, depending on your choice of terminology). OP goes on to clarify by saying "This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before.", meaning if you did not lose everything on data, which includes "/sdcard", you most likely did it wrong.
Give us more info so we can help (assuming you fid it right initially).
P.S. - 6.0 is M(arshmallow), not L(ollipop).
Click to expand...
Click to collapse
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
nextelbuddy said:
i solved my issue. i was wiping DATA but not choosing internal storage. i did that and rebooted and now it says ENCRYPT not ENCRYPTED
THANKS!
so currently I have a modified boot image from the K build, TWRP and now a modifier boot.img kernel for no force encrypt BUT I am not rooted and dont plan on it. does this mean I can still get OTAs?> i would guess not since my boot image has been modified and i am unlocked? would i even want an OTA? wouldnt that just give me a stock boot.img again causing me to get encrypted on the next boot after OTA?
Click to expand...
Click to collapse
Side-loading the OTA then following that with a FED flash seems much safer.
Loading an OTA directly would over-write the boot.img with a ForceEncrypt boot.img, logically Forcing Encryption (derp) at boot.
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
jamespat93 said:
I am using chroma ROM which doesn't force encryption and my device is still encrypted. Can I still use this?
Click to expand...
Click to collapse
You can if you want But if you want to unencrypt your phone, backup your ROM, copy sd content to your computer, wipe everything! in recovery (twrp) including Format Data, Factory reset, internal storage etc. Connect your phone while in recovery to your computer (you'll see 25.98GB instead of 23.03GB), copy sd content back to your phone, restore your rom backup and you'll be fine.
I can't get it work on Nexus 6 and chroma rom r26.
My steps: wipe everything, push folder (rom,patcher and gapps), flash chroma, flash gapps, flash patcher, wipe everything but system
after boot in setting/security it is again encrypted. what I am doing wrong?
Note: None of these files have been tested mainly because I want to keep root on my device. If someone (preferably a recognized developer) can confirm that you can still root the device on this update, I will edit the thread to appear safe to novice/semi-inexperienced users. Because I haven't tested these files, I'm gonna assume its a January security patch.
Here I have pulled the latest FOTA update for the SM-T337A. I know right, I thought this device would never get another update, but it did! Down below I have uploaded the original, untouched .CFG update file and my own compiled .ZIP update file. Not that any of them are different, but if one fails to flash, there's the other file to try.
New PDA Version: T337AUCU2BOH5
New CSC Version: T337AATT2BOH5
Bootloader Version: Bootloader V2 (So you can downgrade back to the BOH4 firmware)
Please feel free to ask any questions or report any problems down below.
EDIT: I will begin creating Odin packages for this update and release them in place of the zip files if/when they are completed.
--Download Links--
Original .CFG File: https://mega.nz/#!r940XJLB!OUne16ltPYkOqfNBbzA5W08f8LwvYT_os--agbGzFq4
Compiled .ZIP File: https://mega.nz/#!fkoW0JKB!aR2uZYlthtmW7Us0uBmP6-BZrmhKiJrRaVrbdkq-bx8
Cheers!
Thank you very much as always @KingOfTheNet , is there any chance you can make an Odin firmware file too, or would that require you taking the update (which I understand very much why you wouldn't want to, without knowing for sure)?
Also I shall mirror the update.zip file on AFH if you'd like (it doesn't accept cfg files)
thisisapoorusernamechoice said:
Thank you very much as always @KingOfTheNet , is there any chance you can make an Odin firmware file too, or would that require you taking the update (which I understand very much why you wouldn't want to, without knowing for sure)?
Also I shall mirror the update.zip file on AFH if you'd like (it doesn't accept cfg files)
Click to expand...
Click to collapse
I'm 99% sure it's just a January security patch, so I'm not sure if it would be worth making an Odin file for it. If AT&T where to release a Marshmallow or Nougat update (which we all know isn't gonna happen) then I would make one for that. Making the Odin file for the Lollipop firmware took me like 4 months
Also feel free to mirror the file(s) to AFH, please be sure to credit me though, assuming they flash without issues. I didn't test it on mine because I want to keep root until I can verify that it can still be achieved on this new update. I'm just surprised AT&T is still updating this thing.
Cheers!
Do you have patch notes, what was fixed?
Thanks.
KGB7 said:
Do you have patch notes, what was fixed?
Thanks.
Click to expand...
Click to collapse
I would imagine AT&T or Samsung would release them somewhere on their website. In my opinion, security updates are made to keep your device guarded against new root methods and viruses, which is exactly why I didn't flash the update myself, to keep root.
[OBSOLETE] @yshalsager As of 8.8.16 flashable TWRP non ARB Firmware now available see thread.
[GUIDE] Updating Modem, Bluetooth and DSP! ~~~ Without triggering ARP on WHYRED!
For anyone on customs rom and need to updated the above partitions?
The commands to flash them in fastboot are: -
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
pause
I just created a bat file (windows) with the above content.
All I need do in future is download a firmware from here, extract the three files and place the bat file in the same folder, and run it.
^^^ Note I have adb/fastboot setup with a global path in windows.
Haven't tested in operation yet but in theory should work. I'm on 8.7.5 Beta firmware at present and see no need to update until the custom rom in use requires update files.
Above 3 files have been reported safe to flash here (Thanks @aank) , without effecting the bootloader, so not to trigger ARP.
First two files are self explained.
DSP (Digital Signal Processor)
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
Attached is a sample bat file, just remove the .txt from the end of the file name.
I posted this before in the Everything About Anti Roll-back [Whyred] by @AL_IRAQI , but would probably get lost there.
Edit: - Edited the batch file to include a "pause", in case you double click instead of running in CMD/POWERSHELL window.
Cool, hope it works if i ever need it. Thanks
thx tested it, it works, i am still on anti 3 after updating these 3
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
rizdar said:
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
Click to expand...
Click to collapse
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
@corkiejp Do you recommend flashing the firmware files from 9.5.19 or the ones from 8.7.26 when moving to a custom rom?
corkiejp said:
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
Click to expand...
Click to collapse
I'm on Arrow OS right now.
But after I do the steps above, it seems like nothings changed.
The signal is still the same.
It's happening on all custom ROMs, is it because my providers?
Edit: I was on 8.7.26 (Masik U 2.2)
@eyebiz
I would stick with whatever firmware your device has at present. It is probably more recent than firmware recommend by custom roms.
There is really no reason to update firmware, if your device is working well with what you have!
If the rom recommends a specific firmware, then you may need to upgrade, but don't downgrade firmware to match.
If I'm flashing firmware, I usually use the version from beta roms, as that is often the more recent firmware.
I only update roms, once a month when security patches included. And patch the firmware at the same time.
@rizdar Your network provider maybe the problem, check your APN settings with the recommend settings of your provider.
The three files mentioned in this thread, may not be alter from one firmware to the next. It is usually the bootloader (which we need to avoid for ARP) that regularly changes.
You could compare files and hashes from different firmware to see if there is changes.
Hi @corkiejp
I've created TWRP flashable .zip with latest stable modem, dsp and bluetooth here :
https://drive.google.com/file/d/1eYys31FFgdxz4GyMFgMiuvoTWwwgER1Y/view?usp=drivesdk
The ARB should be fine as well,
I've tried myself, flashed it on top of 9.6.3 fw less ROM.
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
corkiejp said:
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
Click to expand...
Click to collapse
Oh, no, am not on xiaomi.eu. Just happen to look around the fw less thread, and it seems there's a need for a TWRP flashable zip for radio only update,
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
I didnt delete too much files from firmware update folder, only one i think is really safe to delete.
Alright, i will modify the file name.
It contain 8.8.16 Global files.
otonieru said:
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
Click to expand...
Click to collapse
Have you a link to git, it would be easier to just download the three files for me, than extracting them from Firmware zips.
Apparently those firmware files are safe. I flashed them with a .zip file I put together. For anyone that wants to try you can download it from here.
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
lol. you spoiled the surprise, it was a test. I'll release it soon
corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
I edited the original one and signed the .zip, it seems to be working. Although the cell power consumption is still quite high so far.
deleted
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
ahsnali said:
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
Click to expand...
Click to collapse
It may or may not help your situation. If your worried about your anti version, there is non arb firmware zips available with just them files.
VoLTE is broken on most PIE roms (I believe based on discussions in TE) , check your rom thread and see if anyone else has it working. Or if there is Patch to enable it.