I made this guide with my C5303 running .254 o2 branded firmware. Should work on all other SP variants. (02,03,06) and even other Xperia phones. AFAIK this was made for the Xperia U and works on the S.
ORIGINAL THREAD http://forum.xda-developers.com/showthread.php?t=2301489
At the end, you will have a like new phone with BE2, root, and recovery...even the offline charging bug will be gone.
This is not n00b friendly, If you unlocked the bootloader I think you know what we are talking about. Post any questions before you start.
Last night this was a PITA. I hate my new VAIO Fit 14e...it's a great computer but runs on 64-bit Windows 8. I can't install ADB drivers. So this morning I borrowed my father's Win7 PC (Old but reliable, as an old man's Buick)
Suggestions before attempting to do this:
GRAB A SNACK. This will take about 20 minutes
Download everything you may need (I'll provide some downloads)
Make sure the phone is charged up to 100%
We will be using SuperSU
If possible,delete ALL pictures,videos and music on the external microSD card. We don't want any data in Album,Movies or WALKMAN.
We are going to use some .zips, put them on the external microSD, so they wont be deleted.
Optional: Use a Windows 7 PC, it's easier to do this.
MUST USE THE NEWEST FLASHTOOL Download from the official site: http://flashtool.net/
STEP 1
If you are on a custom ROM or Kernel, Flash a stock .FTF. Remember: BRAVIA Engine only works on the stock firmware and LOCKED Bootloader. After Flashing the stock firmware relock the Bootloader and turn on the phone and wait for it, Do not update, install or login into any app,we need to do a clean install of everything. An example of how Flashtool should look like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
STEP 2
After the phone turns on its time to prepare it for Rooting. Go to the Settings>Xperia>USB Connectivity and uncheck Install PC Companion. Now on the Settings menu go to Security and check Unknown Sources Last step: Go back to the main menu and scroll down to Developer Options and turn them on.Scroll down a bit and enable USB debugging. Now you are ready to root the phone, follow this instructions: http://forum.xda-developers.com/showthread.php?t=2405933 BUT do not put the correct kernel, not at this moment. Just root the phone and then check for proper root access. Download this .apk, It's an older version of ES File explorer that works better than the new one
http://www.mediafire.com/download/n81418pco8d6igw/ES_File_Explorer_1.6.2.5.apk
Put it on the external microSD or whatever you want. o2 firmware has File commander preinstalled
Be sure the SuperSU app is installed. If not, run the rooting tool kit one more time.
STEP 3
Now we need a recovery. Check out this thread on how to install the recovery for locked bootloader: http://forum.xda-developers.com/showthread.php?t=2352920
STEP 4 Optional: Install any other apps you want. Install cerberus, my xperia or any other ones. Check my thread for some interesting ones: http://forum.xda-developers.com/showpost.php?p=45840764&postcount=11
Update SuperSU by downloading a .zip http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
After updating SuperSU check that you have proper root access. If you downloaded the old ES file explorer, open it and go to it's settings to enable it as a root explorer, see the picture
If you can delete system apps, such as chrome.apk or facebook you can continue. If not try again.
STEP 5
Now for the real fun: It's time to put the correct kernel for our firmware. Remember, these kernels are .sin so they are installed via flashmode. See the picture, SELECT AL THE WIPES AND NO FINAL VERIFICATION, BUT WE ARE GOING TO EXCLUDE SYSTEM, SO WE CAN KEEP THE ROOT AND RECOVERY. THIS IS A CRITICAL STEP!!
After the flashing is done turn on the phone, It will take some more minutes. As before, dont waste time updating or installing apps, avoid logins
STEP 6
After a few minutes if everything goes OK we are going to need a root explorer, It's a good idea to reinstall the Es File explorer, to avoid loggin in the playstore. Go to Settings>Apps>All and CLEAR THE DATA FROM ALBUM, CREDENTIAL MANAGER SERVICE, DOWNLOAD MUSIC INFO,MOVIES AND ALL WALKMAN APPS (3)
STEP 7
After clearing the data from those apps, immediately go to System/App and DELETE CredentialManagerService.odex
STEP 8
Immediately turn off the phone and get into recovery and flash the BE_and_music_info_fixes .zip No need to clear cache or dalvik cache. After the phone restarts, let it stand a minute or two...now do a reset: Go to Settings>Backup&Reset and perform a Factory data reset. After this...this is the last one...now you can use the phone in a regular way, doing every step of the setup guide, updating apps and more important: Upload your media and see the BE2
Here is a mirror of the BE fix from the original thread: http://www.mediafire.com/?6gm9jb0lnwvvlfm
THE END
So this is for users who have lost their DRM files/TA Partition after unlocking bootloader? I will give it a try and see if it works.
This will get you back the Mobile BRAVIA Engine, along with the Download Music Info option in WALKMAN, but other things that rely on DRM keys will not work, like the location sharing option on MMS
So after this we cant unlock the bootloader again.. Right? If we unlock BE2 will b lost.. Right?
How to relock 2.254 firmware?
Any one tried this? Success??
Rajeev said:
So after this we cant unlock the bootloader again.. Right? If we unlock BE2 will b lost.. Right?
How to relock 2.254 firmware?
Any one tried this? Success??
Click to expand...
Click to collapse
You can lock and unlock the bootloader easily with Flashtool, as many times you wish. It doesnt matter what firmware..it should be done by Flashtool if you unlocked by the official sony method.
BOOTLOADER UNLOCKING/RELOCKING GUIDE http://forum.xda-developers.com/showthread.php?t=2354721
2 Full size screenshots (Lingerie models, SAFE FOR WORK)
BRAVIA Engine ON
BRAVIA Engine OFF
cachanilla86 said:
2 Full size screenshots (Lingerie models, SAFE FOR WORK)
BRAVIA Engine ON
BRAVIA Engine OFF
Click to expand...
Click to collapse
I like your choice of pictures for demoing :laugh:
Sent from my C5303 using XDA Premium 4 mobile app
So after this BE2 will work in Videos too.. Right?
Rajeev said:
So after this BE2 will work in Videos too.. Right?
Click to expand...
Click to collapse
Yes, BE2 works on Album and Movies, check out these screenshots from BATMAN BEGINS
BRAVIA Engine ON
BRAVIA Engine OFF
Ok thank u for ur hard work.. Gonna try this today. I dont have my TA partitian backup.. Is it ok?
Rajeev said:
Ok thank u for ur hard work.. Gonna try this today. I dont have my TA partitian backup.. Is it ok?
Click to expand...
Click to collapse
Dont worry, you dont need anything more. Just a stock, rooted phone with locked bootloader, delete the .odex,clear the data and flash the fix...and optional a factory reset
cachanilla86 said:
Dont worry, you dont need anything more. Just a stock, rooted phone with locked bootloader, delete the .odex,clear the data and flash the fix...and optional a factory reset
Click to expand...
Click to collapse
Yes i got it... First i read the tutorial.. I think its hard. But after reading i understand that its easy as hell... Simple.. I will let u know the result soon..
Btwn how can i check my BE2 is working? Any proper way?
Rajeev said:
Yes i got it... First i read the tutorial.. I think its hard. But after reading i understand that its easy as hell... Simple.. I will let u know the result soon..
Btwn how can i check my BE2 is working? Any proper way?
Click to expand...
Click to collapse
Upload just one picture and take screenshots. If it fails, you may get a message about "credential manager service has stopped", that happnes if you dont clean the data or forget to delete the .odex
What about if i want to use a custom rom after enabling bravia engine successfully? can i keep it after unlocking bootloader again? please help.
cachanilla86 said:
Upload just one picture and take screenshots. If it fails, you may get a message about "credential manager service has stopped", that happnes if you dont clean the data or forget to delete the .odex
Click to expand...
Click to collapse
I did all the steps correctly u written there. All things ok
But seriously i dont know how to check the different ?
I done like u said..
I opened one image from my Album with Bravia Engine ON and take a Screenshot. I dont get any error msgs about " Credential Manager Service Stopped ".. :good::good::good:
So i think i done all the things correctly..
But pls describe how to check the Difference in details.....
Open a picture you like. Take a screenshot. By default, BRAVIA its ON Go to settings>display and disable BRAVIA engine, open that picture again and take a screenshot if you can't see the difference. Put them on your computer and compare them side by side.
cachanilla86 said:
Open a picture you like. Take a screenshot. By default, BRAVIA its ON Go to settings>display and disable BRAVIA engine, open that picture again and take a screenshot if you can't see the difference. Put them on your computer and compare them side by side.
Click to expand...
Click to collapse
Bravia ON
Bravia OFF
U can See any difference ?
No. Can't see any difference.
cachanilla86 said:
No. Can't see any difference.
Click to expand...
Click to collapse
Mmmm. So BE2 is not working in ma SP. Right ?
I cant ,see any diff.
with the pics that have been uploaded in the other post by the op you can see the image gets lighter when bravia on.
Sent from my C5303 using xda premium
Related
I would like to thank Androxyde for the FlashTool!!
***BEFORE YOU FOLLOW THIS TUTORIAL MAKE SURE THAT YOU HAVE INSTALLED SONY PC COMPANION ON YOUR PC***
HOW TO FLASH STOCK FIRMWARE (.FTF/ROM) ON YOUR XPERIA Z
1: First of all you need to make sure you download the LATEST Flashtool from here http://forum.xda-developers.com/showthread.php?t=2162907
If it is your first time for your phone on the PC, install the flashmode driver, and then get the HW detection to work. Eg, install the driver, then turn off your phone, and then hold down the Down volume button and plug it in – windows will then go into hw detection and install the driver for the phone. It will try to check online, so skip that, and it will install the proper driver you just locally installed. Thanks to Mobe1969 from the Whirlpool forumNOTE: Been seeing people having problems flashing stock .253 based ROMs. Thanks to gm007 for suggesting to use the beta4 version of FlashTool if flashing stock .253 ROMs. You can download beta4 version from here http://goo.im/devs/jerdog/sony
Install Flashtool and install the drivers for the XZ Please see picture below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2: Once installation is complete, navigate to the folder where FlashTool is installed as shown in the picture below
2a: This is optional if you want to create a shortcut to the desktop
3: Now install the driver for the Xperia Z. The driver installer can be found in the FlashTool folder See pictures below:
4: Now for Flashing your Xperia Z. You will need to download the STOCK .ftf (firmware/ROM) and place it in the firmware folder located in the flashtool folder
Here are a list of UNBRANDED .434 ROMs I could find:
UNBRANDED STOCK .434 ROMs
Australia Stock .434 http://forum.xda-developers.com/showthread.php?t=2209281
German Stock .434 http://forum.xda-developers.com/showthread.php?t=2216743
Greek Stock .434 http://forum.xda-developers.com/showthread.php?t=2275794
Hong Kong Stock .434 http://forum.xda-developers.com/showthread.php?t=2201801
India Stock .434 http://forum.xda-developers.com/showthread.php?t=2212694
Netherlands Stock .434 http://forum.xda-developers.com/showthread.php?t=2200945
Singapore Stock .434 http://forum.xda-developers.com/showthread.php?t=2233312
UK Stock .434 http://forum.xda-developers.com/showthread.php?t=2221475
Here's a list of UNBRANDED .253 ROMs I could find:
Australia Stock .253 http://forum.xda-developers.com/showthread.php?t=2280329
Global Stock .253 http://forum.xda-developers.com/showthread.php?t=2283170
India Stock .253 http://forum.xda-developers.com/showthread.php?t=2278993
Netherlands Stock .253 http://forum.xda-developers.com/showthread.php?t=2200945
Sweden Stock .253 http://forum.xda-developers.com/showthread.php?t=2282728
5: Now for flashing. Run the FlashTool app. Make sure that it's in "Flashmode" and click "Ok"
6: This window should show up. Please select the ROM you are gonna flash. And follow the prompts
**NOTE** Please FOLLOW the prompts! The picture below says:
1:Unplug your device from your PC
2:Power OFF the device (Turn your phone OFF)
3:Hold down the VOLUME DOWN button
4:While holding the VOLUME DOWN button plug your phone back to your PC
The process should look like this. Please wait until it is finished See pictures below:
And that is it, you are all done. Power up your Xperia Z and enjoy your new stock ROM
PART 2: Driver installation in Windows 8
Okay since people are having trouble installing drivers for the Xperia Z in Windows 8. I made a tutorial on how to install the Xperia Z driver using the FlashTool in Windows 8.
As shown in the picture below when you try to install the drivers for the Xperia Z in Windows 8 for the first time this is what happens:
As you can see the drivers didn't install:
So here are the steps to install the drivers:
Step 1: Go to "Settings" (if you don't know how to do this, place your mouse pointer in the upper right corner or bottom right corner of your screen and the sidebar should pop out as shown in the picture below):
Step 2: Click on "Change PC settings" as shown in the picture below:
Step 3: When you get to this screen, scroll down to "Advanced start-up" and click the "Restart now" tab. See picture below:
Step 4: When your PC restarts and goes to this screen click on "Troubleshoot" as shown in the picture below:
Step 5: Now click on "Advanced options" as shown in the picture below:
Step 6: Now click on "Start-up Settings" as shown in the picture below:
Step 7: When you get to this screen, click on the "Restart" tab as shown in the picture below:
Step 8: Okay when you get to this screen just hit the "F7" on your keyboard:
Step 9: Now go and reinstall the driver for the Xperia Z. When you get this pop-up window, please select "Install this driver software anyway" as shown in the picture below:
The process will look like this:
As you can see in the last picture that the drivers are now installed.
I hope that helps out people who are new to flashing the Xperia Z
Good work,just add tutorial in the title.
Sent from my C6603 using xda premium
I think you should add why we need flashing, as some ppl might ask what to do if we got a boot loop.
Other than that, this tutorial is great
Sent from my C6602 using xda app-developers app
Thanks for this! as a first time user of Sony devices, this will help me.
Thank you
Nice & tidy :good: bookmarked
Maybe a link to unbranded ROM download in point 4. Or are they country specific?
Natakranta said:
Nice & tidy :good: bookmarked
Maybe a link to unbranded ROM download in point 4. Or are they country specific?
Click to expand...
Click to collapse
Well the stock ROMs are all over the place. Some are in the Android development thread and some in general thread. So people will have find the what stock ROM they want.
Awesome tutorial!
Great tutorial, you have my thanks :good:
Now a bit off topic if I may: having a carrier branded phone, if i flash one of the generic ROMs does it mean that:
1. I'll get rid of all the carrier bloatware?
2. My updates won't be conditioned by the carrier anymore (as in I will get my updates whenever the region the FTF is from gets them)?
My apologies if this has been clarified somewhere else (I couldn't find any definitive answers)
I have the attached problem, Can any one help?
KP_ said:
Great tutorial, you have my thanks :good:
Now a bit off topic if I may: having a carrier branded phone, if i flash one of the generic ROMs does it mean that:
1. I'll get rid of all the carrier bloatware?
2. My updates won't be conditioned by the carrier anymore (as in I will get my updates whenever the region the FTF is from gets them)?
My apologies if this has been clarified somewhere else (I couldn't find any definitive answers)
Click to expand...
Click to collapse
Hi, yes if you flash any stock ROM you will get rid of the carrier branding and any bloatware.
skywalker1970 said:
I have the attached problem, Can any one help?
Click to expand...
Click to collapse
Okay I will try my best.
Is your XZ stock? I meant unrooted.
Is everything stock?
Bootloader locked?
Are the drivers installed?
Did you turn the phone OFF and connect the USB cable while holding down the volume DOWN button?
EDIT:
Looks like your device is not recognised as you can see in the picture below:
Look at this picture below:
skywalker1970 said:
I have the attached problem, Can any one help?
Click to expand...
Click to collapse
Use beta5 from here , and apply update to beta6 from here. With previous beta, loader was not included in the FTF, in such case, loader is deducted from phone infos. In your case, your phone infos are not present.
loader is selected with this priority list : first ftf bundle then phone infos.
in beta6, I added a fallback to device list user input to select the right device manually and such the right loader.
Androxyde said:
Use beta5 from here , and apply update to beta6 from here. With previous beta, loader was not included in the FTF, in such case, loader is deducted from phone infos. In your case, your phone infos are not present.
loader is selected with this priority list : first ftf bundle then phone infos.
in beta6, I added a fallback to device list user input to select the right device manually and such the right loader.
Click to expand...
Click to collapse
Thanks, it worked.
---------- Post added at 02:23 PM ---------- Previous post was at 02:21 PM ----------
shadowboy23 said:
Okay I will try my best.
Thanks for your help. Appreciate it.
Click to expand...
Click to collapse
Going to try now, stock ROMs won't allow me to capture screenshots. Will report
23Six said:
Going to try now, stock ROMs won't allow me to capture screenshots. Will report
Click to expand...
Click to collapse
I have always used stock ROMs and I can do screen capture on my XZ.
shadowboy23 said:
I have always used stock ROMs and I can do screen capture on my XZ.
Click to expand...
Click to collapse
Yeah, I think I may have corrupted some system data or changed permissions down the line because I was able to capture 4-5 days ago. No biggie.
Flashing...
---------- Post added at 06:14 PM ---------- Previous post was at 05:54 PM ----------
23Six said:
Yeah, I think I may have corrupted some system data or changed permissions down the line because I was able to capture 4-5 days ago. No biggie.
Flashing...
Click to expand...
Click to collapse
Edit: screen captures working like normal again :good:
23Six said:
Edit: screen captures working like normal again :good:
Click to expand...
Click to collapse
That's good to hear it's all fixed.
Hi thanks for this tutorial i cant seem to get the drivers ro install tho any help would be appreciated!
Nicely Presented Thanks For your Effort Bro :good:
Hi any help with the driver issue i just cant get them to install i m running windows 8
DO NOT TRY TO USE THIS TO FLASH CUSTOM ROMS/RECOVERIES/KERNELS. THIS IS ONLY TO INSTALL TWEAKS THAT COME IN THE FORMAT OF A FLASHABLE .ZIP! READ THIS AND THE DEVELOPER'S THREAD BEFORE YOU PROCEED WITH THIS! I'M NOT RESPONSIBLE FOR BRICKS!
I thought all S4 active users should be aware of this -- you CAN flash CWM/TWRP .zip files WITHOUT a custom recovery. Albeit the app is a proof-of-concept/beta. It still does work and people with locked-down xperia phones use it to flash .zips
If you're on a regular S4 you'd be better off using CWM or TWRP so stop reading this.
You also cannot flash custom ROMs with this. Certain system files are critical to maintaining stability and if they are overwritten while the device is powered on it'll crash and you'll have a bricked franken-ROM phone. Don't try to flash kernels or recoveries with this either. You're just asking for trouble.
By clicking "Show" below you agree that I'm not responsible for your phone exploding or bricking when you do this. You could easily end up in a boot-loop and have to restore with odin. As a matter of fact, even if you do everything correctly you could still end up with a bricked phone. It won't be my fault. There is no way to do nandroids as of now so you will have to restore to out-of-box state with odin and start from square one.
From your phone:
1) Visit the developer's thread here
2) Read his thread and make sure you understand any warnings/consequences of using his tool.
3) Scroll to the bottom of the page, download and install the APK
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4) Download your favorite flashable mod .zips. There's some links at the bottom of the OP.
5) Click "Select zip.." and then use your favorite file explorer to navigate to the location of your .zipped mod/tweak/whatever
6) Flash Gordon will request superuser, choose "accept"
7) Double check that you selected the correct .zip and have the correct options
8) Click "Flash Now!". Don't worry if your phone hangs, give it a few minutes to do its thing. Mine lagged very bad as I flashed acid audio mod. Do not hit the home button or do anything to cause the app to exit.
9) Once flash gordon is done a notification will appear telling you to reboot - Click that notification and your device will reboot. If the app hangs at "Installing" give it a good 10 minutes and if it's still "Installing" just manual reboot. If your mod requires you to wipe the cache partition I reccomend booting to the stock 3e recovery by holding vol up + power + home and wiping it that way so you don't experience FC's from clearing cache while device is running.
10) Once device is powered on it should take you through that "Android upgrading" message and then you can enjoy your mod!
11) Optional: Throw money at/thank "Androguide.fr" for his awesome app.
Confirmed working:
Acid Audio Mod - Use the one here - V7 will bootloop you or cause a glitch where your device is "Upgrading applications" every boot
Going to try more later -- post a picture of your favorite mod/tweak running and I'll add it to this OP!
Thank you for posting this. I am sure it will help many Active users, but I wonder how long it will be before people ignore your warnings and try to flash a kernel or ROM or custom recovery with this?
Please people READ and READ some more so you don't mess up your phones. I don't know if it will do any good but maybe putting that part at the top in Red letters might help.
Again. thanks.
scott14719 said:
Thank you for posting this. I am sure it will help many Active users, but I wonder how long it will be before people ignore your warnings and try to flash a kernel or ROM or custom recovery with this?
Please people READ and READ some more so you don't mess up your phones. I don't know if it will do any good but maybe putting that part at the top in Red letters might help.
Again. thanks.
Click to expand...
Click to collapse
Thanks and done.
I am tempted to see if the following mod will work... http://forum.xda-developers.com/showthread.php?t=2320427
NVM the mod I would really love to see is this http://forum.xda-developers.com/showthread.php?t=2335635 anyone willing to try it out
joshuadjohnson22 said:
I am tempted to see if the following mod will work... http://forum.xda-developers.com/showthread.php?t=2320427
NVM the mod I would really love to see is this http://forum.xda-developers.com/showthread.php?t=2335635 anyone willing to try it out
Click to expand...
Click to collapse
I don't see why it wouldn't work. Just try it
thatbigmoose said:
I don't see why it wouldn't work. Just try it
Click to expand...
Click to collapse
Lol i really want to but I don't feel like re-setting up my phone if it messes up lol.
I have already rooted my parent's S4 Active and regular S4 and I did a lot of mods for them... Just tired of re-setting up my phone. Are you not interested in CM10.1 MMS? It rocks... one of the only stock messaging apps I would like to use all the time
joshuadjohnson22 said:
Lol i really want to but I don't feel like re-setting up my phone if it messes up lol.
I have already rooted my parent's S4 Active and regular S4 and I did a lot of mods for them... Just tired of re-setting up my phone. Are you not interested in CM10.1 MMS? It rocks... one of the only stock messaging apps I would like to use all the time
Click to expand...
Click to collapse
I did 3 Odin flashes today from messing with flash Gordon and trying to install acid audio
I made a bloat killer based off the one found here: http://forum.xda-developers.com/showthread.php?t=2250403
Kills all S-Apps including note, memo, browser, sync services, ATT updater, flipboard, facebook, Samsung stock file explorer, "Simple" launcher, Swype
Leaves allshare play and all the stuff with wifi-direct, all google apps, group play, mobile hotspot, Samsung stock video app, TW launcher, ChatON because that ****er is invincible, Samsung keyboard, all of the apps that looked vital that I couldn't be bothered toying around with
Use this at your own discretion, I could've ****ed up and deleted a bad file, but my system is running great. As usual I'm not responsible for bricks.
Here's a list of ALL the apps it takes care of:
Code:
delete("/system/app/wssyncmldm.apk");
delete("/system/app/wssyncmldm.odex");
delete("/system/app/YPMobile_ATT.apk");
delete("/system/app/YahoostockPhone2013.odex");
delete("/system/app/YahoostockPhone2013.apk");
delete("/system/app/YahoonewsPhone2013.odex");
delete("/system/app/YahoonewsPhone2013.apk");
delete("/system/app/wssyncmlnps.odex");
delete("/system/app/wssyncmlnps.apk");
delete("/system/app/wssyncmlds.odex");
delete("/system/app/wssyncmlds.apk");
delete("/system/app/wssyncmldm.odex");
delete("/system/app/WlanTest.odex");
delete("/system/app/WlanTest.apk");
delete("/system/app/TripAdvisor.apk");
delete("/system/app/TravelWidget.apk");
delete("/system/app/TravelService.odex");
delete("/system/app/TravelService.apk");
delete("/system/app/Telenav_ATT.apk");
delete("/system/app/Swype.apk");
delete("/system/app/S-Voice_Android_phone_J.apk");
delete("/system/app/StoryAlbumWidget.odex");
delete("/system/app/StoryAlbumWidget.apk");
delete("/system/app/SPlannerAppWidget_NAmerica.odex");
delete("/system/app/SPlannerAppWidget_NAmerica.apk");
delete("/system/app/SNoteProvider.odex");
delete("/system/app/SNoteProvider.apk");
delete("/system/app/SMemo2.odex");
delete("/system/app/SMemo2.apk");
delete("/system/app/SmartWifi_vpl_ATT.apk");
delete("/system/app/SHealth2.apk");
delete("/system/app/SecNoteMyFiles.apk");
delete("/system/app/sCloudSyncSNote.apk");
delete("/system/app/sCloudSyncSBrowserTabs.apk");
delete("/system/app/sCloudSyncSBrowserBookmark.apk");
delete("/system/app/sCloudSyncContacts.apk");
delete("/system/app/sCloudSyncCalendar.apk");
delete("/system/app/sCloudQuotaApp.apk");
delete("/system/app/sCloudDataSync.apk");
delete("/system/app/sCloudDataRelay.apk");
delete("/system/app/SBrowser.odex");
delete("/system/app/SBrowser.apk");
delete("/system/app/SamsungWidget_ProgramMonitor.odex");
delete("/system/app/SamsungWidget_ProgramMonitor.apk");
delete("/system/app/SamsungTTS.apk");
delete("/system/app/SamsungMusic.apk");
delete("/system/app/SamsungHubUpdater.apk");
delete("/system/app/SamsungHub.apk");
delete("/system/app/SamsungGames.apk");
delete("/system/app/S_Translator_CSLi.odex");
delete("/system/app/S_Translator_CSLi.apk");
delete("/system/app/PolarisOffice5.apk");
delete("/system/app/PageBuddyNotiSvc2.odex");
delete("/system/app/PageBuddyNotiSvc2.apk");
delete("/system/app/myATT_ATT.apk");
delete("/system/app/MusicPlayerWT.apk");
delete("/system/app/MobilePrintSvc_Samsung.apk");
delete("/system/app/MobilePrintSvc_HP.apk");
delete("/system/app/MobilePrintSvc_CUPS_Backend.apk");
delete("/system/app/MobilePrintSvc_CUPS.apk");
delete("/system/app/MobilePrint2.odex");
delete("/system/app/MobilePrint2.apk");
delete("/system/app/MMAppFramework.odex");
delete("/system/app/MMAppFramework.apk");
delete("/system/app/Match3VS.apk");
delete("/system/app/LiveTv_vpl_ATT.apk");
delete("/system/app/KNOXAgent.odex");
delete("/system/app/KNOXAgent.apk");
delete("/system/app/kieswifi.odex");
delete("/system/app/kieswifi.apk");
delete("/system/app/FamilyMap_vpl_ATT.apk");
delete("/system/app/EasyLauncher.odex");
delete("/system/app/EasyLauncher.apk");
delete("/system/app/EarCare.apk");
delete("/system/app/DriveMode_ATT.apk");
delete("/system/app/digitalLocker_ATT.apk");
delete("/system/app/Com2usPoker_ASGC.apk");
delete("/system/app/attMessages_vpl_ATT.apk");
delete("/system/app/AccuweatherPhone2013.apk");
delete("/system/app/AccuweatherPhone2013.odex");
delete("/system/app/ChatON_feature.apk");
delete("/system/app/Samsungservice.apk");
delete("/system/app/SecCalendar_NAmerica_SPen.apk");
delete("/system/app/SecCalendar_NAmerica_SPen.odex");
delete("/system/app/DioDict3Service.apk");
delete("/system/app/HealthContentProvider.apk");
delete("/system/app/CHS_J_Device_only.apk");
delete("/system/app/SamsungApps_J_Only.apk");
delete("/system/app/SamsungBooks.apk");
delete("/system/app/Flipboard.apk");
delete("/system/app/MusicLiveShare.apk");
This is sweet, big props to the developer on this one. Gonna play with this more tomorrow.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
joshuadjohnson22 said:
I am tempted to see if the following mod will work... http://forum.xda-developers.com/showthread.php?t=2320427
NVM the mod I would really love to see is this http://forum.xda-developers.com/showthread.php?t=2335635 anyone willing to try it out
Click to expand...
Click to collapse
It doesnt even let me flash it. It keep saying "the package is not a flashable zip"
tisaznpimp said:
It doesnt even let me flash it. It keep saying "the package is not a flashable zip"
Click to expand...
Click to collapse
Try installing busybox?
Just search "busybox" on the market.
thatbigmoose said:
Try installing busybox?
Just search "busybox" on the market.
Click to expand...
Click to collapse
Also doesnt work, says the same error.
just to be sure... you did run the busybox installer after you installed it, correct? Both BusyBox apps are just installers. You have to run them and tell them to perform the actual install.
I just tried flashing CM 10.1 with this and now my phone's bricked. Wtf man
aturbs said:
I just tried flashing CM 10.1 with this and now my phone's bricked. Wtf man
Click to expand...
Click to collapse
You have to be trolling. If so, I hope you get banned.
aturbs said:
I just tried flashing CM 10.1 with this and now my phone's bricked. Wtf man
Click to expand...
Click to collapse
Yeah at the very most you softbricked your phone. Which probably means you flashed the wrong zip for the mms. Just odin your phone back...
How can we edit this to keep any apps we want? Thanks !
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
rhkean said:
just to be sure... you did run the busybox installer after you installed it, correct? Both BusyBox apps are just installers. You have to run them and tell them to perform the actual install.
Click to expand...
Click to collapse
awesome, thanks for the info. I successfully flash it. Thank you so much. =))
tisaznpimp said:
awesome, thanks for the info. I successfully flash it. Thank you so much. =))
Click to expand...
Click to collapse
Did you install cm10.1 mms? If so which zip files did you install? Is everything working?
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4 Beta
joshuadjohnson22 said:
Did you install cm10.1 mms? If so which zip files did you install? Is everything working?
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I flashed the one from here: http://forum.xda-developers.com/showthread.php?t=2335635
Make sure you use the 'Pre-MEA_AOSP_MMS_CPA-Poke-v2.zip'. Reboot phone and go to system/app with root explorer and rename KeyguardWidget.apk to KeyguardWidget.apk.bak. Done.
Everything, including both sms/mms works perfectly. You can even theme the conversation list and messages with custom background and different test color. I included screenshot to show you what I meant. =)
attached:
READ THIS FIRST:After downloading "oxygenos_1.0.0.zip" you will notice that it contains a folder with two files:
oxygenos_1.0.0_flashable.md5
oxygenos_1.0.0_flashable.zip
Extract oxygenos_1.0.0_flashable.zip first, then copy it to the SD card, wipe, flash, etc.
MultiROM works!
Check here and click thanks for MMWolverine.
New touchscreen driver to fix ghost touches:
Click here.
__________________________________________
Just a weeeee bit late.
https://oneplus.net/de/oxygenos
__________________________________________
Download it here:
Official:
https://forums.oneplus.net/threads/oxygen-1-0-2-release-with-stagefright-security-patches.340711/
There is a pre-rooted and de-bloated version by @CraZY_BoY^ right here:
[ROM][MOD] OxygenOS - Rooted | Cleaned | Some apps from CM
Features
Screen-off gestures like double-tap to wake, music controls, and shortcuts for the camera and flashlight
Hardware and software navigation keys
Quick settings feature, tiles can be added, removed, and re-organized
Their own file manager, though it's pretty buggy ATM (see below).
Missing features:
Privacy guard
Double tap to sleep
Display color settings
Theming support
Custom camera app (uses Google camera app)
MaxxAudio and Swiftkey (coming in a future update)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation steps:
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
If you find yourself wanting to rollback to CM, Make sure you have TWRP or CM recovery on the device. Another factory reset will be needed before flashing unfortunately so make sure you backup all of you data.
Click to expand...
Click to collapse
Source
To revert back to CM11/CM11s:
Flash the latest CM11/CM11s modem from here.
Restore CM11/CM11s from a backup or flash new.
There is no need to reboot between steps 1 & 2.
Rooting Instructions:
Just like CM11s, download SuperSU-v2.xx.zip to your SD card and flash from recovery.
Known issues:
Reported by OnePlus:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
Reported here & elsewhere:
4k video is non-functional with Google camera.
Google Play Services wakelocks. Check here for a fix.
Other Stuff
Wallpapers
Boot animation
Modem
Please click thanks for the guys that posted these for you.
CafeKampuchia said:
Just a weeeee bit late.
https://oneplus.net/de/oxygenos
Click to expand...
Click to collapse
Downloadning now! Lets see
very slow..hope for a mirror soon!
CoreGaming said:
very slow..hope for a mirror soon!
Click to expand...
Click to collapse
Its 700 MB
Nice to know, but I'll wait CM12s and then I choose what to do
I'm getting an average 100-150kbs using Firefox and DownloadThemAll. 1 hr 22 minutes left :/
Edit
Mine's shot up to >300kbs - 20 minutes left
Nothing like flashing a new ROM at 1:30AM!
Downloading now - Cant wait to get this thing running!
I am downloading on both my pc and my opo. on my the opo, it's taking 1 hour or so to download. on my pc it took 10 minutes. both on wireless on the same network.
Uploading to mega now, nearly half way, will post a link when finished.
gsmyth said:
Uploading to mega now, nearly half way, will post a link when finished.
Click to expand...
Click to collapse
Send me the link and I'll update the OP ASAP.
3rd feature according to this video is FILE MANAGER ARE YOU KIDDING ME
MEANWHILE STOCK BUG LIST:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
HOPING TO ROOT IT AGAIN VIA RECOVERY AND provide my feedback with xposed, viper sound mod etc
I'm really happy with cm12 nightlies, I'll wait for the reviews whats the battery like?
aravindhramachandran said:
3rd feature according to this video is FILE MANAGER ARE YOU KIDDING ME
MEANWHILE STOCK BUG LIST:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
HOPING TO ROOT IT AGAIN VIA RECOVERY AND provide my feedback with xposed, viper sound mod etc
Click to expand...
Click to collapse
Bug list in OP already, friend. Good point on the file manager. I'll add that to the OP as well. :good:
vacenzo said:
I'm really happy with cm12 nightlies, I'll wait for the reviews whats the battery like?
Click to expand...
Click to collapse
Dude, nobody even has it installed yet. And even if they do, it's been <1 hr. We'll know something tomorrow. :highfive:
mirror please. cant flash beacuse my download was corrupted and now the download is super slow. :crying::crying:
saar120 said:
mirror please. cant flash beacuse my download was corrupted and now the download is super slow. :crying::crying:
Click to expand...
Click to collapse
Read the comments.
Transmitted via Bacon
Guys, it keeps giving me error when trying to flash. Im on cm nightlies the latest one but for some reason it wont flash... i can flash other roms just fine
this is what happend to me as well. in the middle of the download i switched from wifi to 3g . i thought it was beacuse of that.
zee24 said:
Guys, it keeps giving me error when trying to flash. Im on cm nightlies the latest one but for some reason it wont flash... i can flash other roms just fine
Click to expand...
Click to collapse
Did you extract the zip? There is a flashable zip in the zip you downloaded.
There is a zip inside downloaded zip! Flash that.
I seen a lot of Discussion On this topic, and found a really simple way to disable Forced Encryption and it also removes the warning at boot. This in NO WAY is my work at all. I am sharing this [FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher) which was posted by @gladiac. Absolutely make sure you head over to his forum and hit the Thanks button. This works great
Screenshots Below
I have the option to encrypt the phone as you can see circled. I went into system with Root Explorer and was prompted for R/W access and obviously I granted it. Everything is working great!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Preparation
Before proceeding, enable Developer options and MAKE SURE USB DEBUGGING IS ENABLED!!!
1. Download fed_patcher_v7-signed.zip and check here to verify the latest version
2. Download [BETA][2015.10.10] SuperSU v2.52 by @Chainfire
3. Download Whatever ROM you are going to use. I am currently running [ROM]【6.0】LightROM - Marshmallow【MRA58K】- 10/08/15
Instructions
1. Backup your SD Card, during this process, everything will be erased during the process
2. Reboot into TWRP, this is important that you actually have TWRP
3. Perform a Full Wipe by doing the following:
Press Wipe
[*] Press Advanced
[*] Click every check Box
[*] Wipe 3x for good measure
[*] Press Home button
[*] Press Wipe
[*] Press Format Data
[*] Type yes in the box to perform the format
[*] Perform this 3x for a good full wipe
4. Reboot TWRP (Do Not Install Super Su Yet)
5. Once Back In Recovery, On the computer, open My computer
6. Navigate to and open the Nexus 6 Drive
7. Drag the Zip files below to your Phone -
1) fed_patcher_v7-signed.zip
2) BETA-SuperSU-v2.50.zip
3) ROM Zip
If You are Having Trouble, take a look at the screen shots below
You Want to make sure you mount data if it is not, and make sure MTP is not disabled! Thanks @jamiejames and @aliasferno
8. Flash your ROM 1st (DO NOT BOOT AFTER FLASHING)
9. Wipe Dalvick Cache/Cache 3x
10. Flash fed_patcher_v7-signed.zip
11. Wipe Dalvick Cache/Cache 3x
12. Flash BETA-SuperSU-v2.52.zip
13. Reboot and Enjoy with no more red error sign during boot and no encryptionhttps://source.android.com/devices/tech/security/verifiedboot/verified-boot.html#user_experience
Supported Devices
Motorola Nexus 6 (shamu)
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.
What Do I need To Make This Work?
A supported device (Your nexus 6)
[*]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?
Follow Instructions above - This is the basic need to know information
[*]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.
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.
All Thanks To:
@gladiac - For Putting the OP together for the Nexus 9 and sharing this
[*]@rovo89 - for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
[*]@pbatard - for making (un)mkbootimg (dunno if he is on xda)
good work mate
Danvdh said:
good work mate
Click to expand...
Click to collapse
Thanks Bro...Thanks for the ROM, I saw it's already updating. Thanks
Thanks for this! :good:
Herk718 said:
Thanks for this! :good:
Click to expand...
Click to collapse
No Problem...
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
TY you for this info. Exactly what I was looking for. Thanks a milion
spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I am decrypted, I have super user ...I was able to restore with titanium backup, I will see if I can edit the build.prop or just mount rw
edit: I was able to mount rw successfully in root explorer no issues
simunovic said:
TY you for this info. Exactly what I was looking for. Thanks a milion
Click to expand...
Click to collapse
No problem
Sent from my Nexus 6 using Tapatalk
spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me
bdorr1105 said:
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me
Click to expand...
Click to collapse
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose
spunks3 said:
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose
Click to expand...
Click to collapse
It won't work unless you remove root
Sent from my Nexus 6 using Tapatalk
Moved this from the development forum as there is no development, this is not your work, and it is a guide for this; this is better suited to a General forum.
Thread reopened on the basis that this is a guided collection of work.
Ok, this OP is more of a guide on how to use this tool, I am going to edit the OP and redirect it to the Forum that was in the Nexus 6...There was a mis-understanding on my part, I did not realize this was in the Nexus 6 Android Development already, this is just how to run it, and the steps to successfully flash and get rid of the warning before booting Android 6.0 and having a force decrypted set up form boot...
bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse
atrix4nag said:
bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse
bdorr1105 said:
atrix4nag said:
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse
atrix4nag said:
bdorr1105 said:
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse
I do not have the warning at boot doing this method. So yes, you should no longer have the warning
Click to expand...
Click to collapse
If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.
Hucklebury said:
If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.
Click to expand...
Click to collapse
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again
bdorr1105 said:
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again
Click to expand...
Click to collapse
ok, thanks for the reply. i have tried many times to get rid of that ugly screen without success, ended up going completely stock M.
HI ALL XPERIANCED
Since i use android, after a new installation, i was always trying to erase all unwanted applications. Manually from system or with titanium_backup.
But over time that was laborious, so i find this solution to do it by myself .
THE SCRIPTS AIM TO
FIRST
After flashing a new rom, totaly debloat applications from google and sony, then appropriating you your device.
Personnaly, i just need essential app like :
android : Phone; sms/mms/email; usb, multitask, gps, net browsing
sony apps : Album; music; video; radio; cybershot
google apps : Nothing ( natively a bloatware ? )
NEXT
It will move all bloatware under a new directory into /system/_keep_safe; which is easy to reinstall manually with a root explorer or with the restoration package.
/data/app
/etc/customization
/etc/product
/system/app
/system/media/audio/
/system/media/bootanimation.zip
/system/priv-app
/system/vendor
FINALY
You can install your own apps from external_sd and get a super leggera xperia device . Just check from attached image before and after the script.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BEFORE LAUNCHING
YOU NEED A SONY XPERIA DEVICE
Tested ok on my xperia z1compact d5503 with stock/prerooted/dual-recovery lp .236
To download the debloating script and his restoration package
A working recovery
Working flash via TWRP and philz-touch; but after flashing always wipe cahe and dalvik-cacheWorking flash via FlashFire
YOU CAN ADD YOUR OWN APK
Applications will be copy to data/app so there can be uninstalled and media will be copy to there default location.
The easyest way is by dropping them into debloating package, under package.zip /system/app then /system/media
The second way is by editing the script called :SET_MY_MOD.sh in the front of package
Indeed, i prefer this solution which lightens the package and thus change the least possible file.
Code:
YOU JUST NEED TO EDIT YOUR APK LOCATION, IN MY CASE, ALL COME FROM EXTERNAL_SD
### set your medias location
alarm="/external_sd/alarms/alarm.ogg"
notification="/external_sd/notifications/notification.ogg"
ringtone="/external_sd/ringtones/fired_up_feels_good.mp3"
bootanimation="/external_sd/_app/bootanimation.zip"
### set your applications location
launcher="/external_sd/_app/xmarshmallow_10.0.a.0.5.apk"
theme="/external_sd/_app/black_5.0.2.apk"
file_manager="/external_sd/_app/total commander_2.80b1.apk"
browser="/external_sd/_app/maxthon_4.5.6.1000.apk"
TEST IN ALL RISK KNOWLEDGE. PLAN A BACKUP BEFORE.
I join a restoration script in case of something doesn't work, it will restore all from debloating script.
All actions are logged into /system/_keep_safe/bloatwares.log
ALL CREDITS GO TO
xda community
sony mobile
android
amarullz
moly82
SUPPORTED DEVICES
sony xperia z1 compact .108 .757 .368 .236
TELL ME !?
UPDATE 08-06-2016
Aroma, available options stable !
Updated download link then you can vote for the poll
Thank you for the " thanks button " but I have mostly need confirmation on functioning ? and on which device ?
Aroma experimental option don't do anything; they are test fonction
XDA:DevDB Information
[SCRIPT] XPERIA BLOATWARES, Tool/Utility for the OEM Cross Device Development
Contributors
elshur
Version Information
Status: Stable
Current Stable Version: 2016-06-08
Created 2016-04-29
Last Updated 2016-06-08
hi,
this is a great idea.
first debloat the rom and move the apk´s to an separate folder
and after that install the personal apk´s on the external sd card.
And all of that in only one step by flashing this zip...
Since now it took a long time to do that manually after flashing a new rom.
:good::good::good:
moonryder said:
hi,
this is a great idea.
first debloat the rom and move the apk´s to an separate folder
and after that install the personal apk´s on the external sd card.
And all of that in only one step by flashing this zip...
Since now it took a long time to do that manually after flashing a new rom.
:good::good::good:
Click to expand...
Click to collapse
Thanks mate :fingers-crossed:
In fact i spend how many time with titanium backup, so with this script, notepad and 2minutes you can copy your defaults apps into data/app.
I'm trying to find a way to create a link to own apps ( maybe like Link2sd ), and the same for KK and MM, then the aroma package for later.
UPDATE 04 2106
feed back ?
elshur said:
UPDATE 04 2106
feed back ?
Click to expand...
Click to collapse
Tried it with my Sony Tablet and MM. Got some issues:
- can't access developer settings
- menu/home button doesn't work
elshur said:
HI ALL XPERIANCED
FIRST
After flashing a new rom, totaly debloat applications from google and sony, then appropriating you your device.
Personnaly, i just need essential app like :
android : Phone; sms/mms/email; usb, multitask, gps, net browsing
sony apps : Album; music; video; radio; cybershot
google apps : Nothing ( natively a bloatware ? )
Click to expand...
Click to collapse
I think it's better to keep it like this:
Android: only essetial apps like the ones you listed
sony app:remove all sony apps besides those essential ones to keep the rom working and not forced close/crash (even more bloat removal)
Google apps: play store and manager and maybe other essential ones to dl stuff from google
i think the idea here is to keep it as vanilla as possible like a nexus device i guess.
i think the debloatscript might need an update since MM has some new apps and some files might have changed names.
you've got a pretty good project going on there.
thanks for the hard work!!
JLowe said:
Tried it with my Sony Tablet and MM. Got some issues:
- can't access developer settings
- menu/home button doesn't work
Click to expand...
Click to collapse
I just flashed the custom rom and afterwards the debloat script. Then you get these mentioned issues. If you flash the Rom, boot system and afterwards use the script it works fine for me. I am using the non-aroma zip.
How I can install an apk from internal storage?
BACKUP="/storage/emulated/0/download/Install/TB.apk"
...
cp $BACKUP /data/app
doesn't work
I can post an updated MM Script in the next days
frostmore said:
I think it's better to keep it like this:
Android: only essetial apps like the ones you listed
sony app:remove all sony apps besides those essential ones to keep the rom working and not forced close/crash (even more bloat removal)
Google apps: play store and manager and maybe other essential ones to dl stuff from google
i think the idea here is to keep it as vanilla as possible like a nexus device i guess.
i think the debloatscript might need an update since MM has some new apps and some files might have changed names.
you've got a pretty good project going on there.
thanks for the hard work!!
Click to expand...
Click to collapse
Thanks for the support
In fact i just need a lightweight device. Finally i have found a Marshmallow list from Xperia X, then i will update the scripts.
Once the aroma script is finished, you can select the various apps that you wish to keep :highfive:
JLowe said:
I just flashed the custom rom and afterwards the debloat script. Then you get these mentioned issues. If you flash the Rom, boot system and afterwards use the script it works fine for me. I am using the non-aroma zip.
How I can install an apk from internal storage?
BACKUP="/storage/emulated/0/download/Install/TB.apk"
...
cp $BACKUP /data/app
doesn't work
I can post an updated MM Script in the next days
Click to expand...
Click to collapse
* I hope you managed to restore from the script ?
BTW you must take care of the syntax or you can try :
/sdcard
/storage/sdcard0
/storage/emulated/0
* Thanks for the proposal, i have found a list for MM
* I will take a look at the develloper setting but from Lollipop there is no problems.
(The aroma doesn't do anything, it's under construction) Drop your script here
Thanks for the script, really useful.
Posting my experience on Z1 with rooted [ZIP][C6903] 14.6.A.1.236 Custom. DE, Pre-Rooted, XZDR-LB, Xposed Framework By motorazrv3 (thanks to him)
I used the script to manually remove some things to start with (Google Play apps) and all was ok
Then I moved priv-apps and most of apps (kept a few I wanted)
On reboot went into setup. Rebooted from there and hung on starting apps.
Then bootloops etc, all sorts of issues. In recovery moved the whole of the folders back and still had same problem (cleared davlik and cache)
Lost TWRP recovery to touchwiz (not sure how!). TWRP had a compressed backup, so needed that
I have always had a problem getting into fastboot and couldn't flash the TWRP img. Still no fastboot, tried everything searching xda and other sources
Sony flashtool connected OK, but couldn't see it let me flash .img, adb is fine. Use vol up to get into bootloader with blue led. Connected to usb with volume up etc, nothing no fastboot (waiting for device)
Anyway, rebooted to recovery again, and WTF - TWRP ! So restored last backup and all OK
Don't blame your script, but just letting others know, if you run on Z1 (.236 anyway) make sure you have a backup and are prepared for some hassle
But thanks elshr, I know a bit of linux scripting and it was good for learning. Have gone back to freeze / disable for now until I have some more time
UPDATE 01 06 2106
Aroma installer package is compatible with JB-KK-LP-MM-NP and is build with this 3 options :
DEBLOATING
Just chose which option you need to debloat ! then they will be move into /system/_keep_safe
Original build.prop is keep safe into /system/_keep_safe
The logging file goes into the same folder. If you need help, you should drop it in the thread @ xda
SET YOURS
If you have dropped your app & media in the package, they will move into /system/app & /system/media
If you have edited the set_yours.sh, it will be read then install your app into /data/app
If you have dropped your modded build.prop in the front of package, it will overwrite original build.prop
RESTORATION
Original build.prop will be restored then the bloatwares too, all at they default location.
UPDATE 06-06-2016
Aroma, available options stable !
Updated download link then you can vote for the poll
Thank you for the " thanks button " but I have mostly need confirmation on functioning ? and on which device ?