I no longer have this phone!
---
** Debloater for KitKat **
I decided to create a Debloater script for those that want a clean system.
I've used bits from NoMoto - Stock ROM Debloat Scripts (Moto G) by lost101
As with my previous debloater for JB, I've kept the stock launcher (and circle widget + weather).
Steps:
Prepare/flash your preferred KitKat Stock ROM
Flash + Boot into latest TWRP recovery
Flash Moto Razr i XT890 KitKat Debloater - v0.1.zip (attached below)
Flash the latest SuperSU (CWM / TWRP / MobileODIN installable ZIP)
Reboot.
What you should end up with after rebooting:
Have fun!
I no longer have this phone!
---
** Debloater for JB & ICS Stock ROMs **
This debloater was created using scripts from arman68's infiniROM Debloater v2 and bits from Motorola launcher remover v2.
I've also used a few bits & bobs from Razri-Cleaner v0.7, by GalaxyUser.
Steps:
Prepare your preferred JB Stock ROM to flash using RSD Lite (See here and here)
Boot into fastboot and flash custom recovery - I use the latest TWRP
Make a backup of the untouched stock ROM (so you don't have to keep using RSD Lite)
Flash Razr i [XT890] - Stock Lite 4.1.2.zip (attached in first post)
Flash the latest SuperSU (CWM / TWRP / MobileODIN installable ZIP)
Reboot.
What you will end up with after rebooting:
Enjoy. :good:
~
Note:
This works with Omar's ROM. :good:
This will also work for ICS. If you're using the Xposed Framework, you will get a Segmentation Fault upon installing the framework - You will need this.
~
I decided it would be best to keep the stock launcher (and circle widget + weather).
They can be disabled if you're using another launcher. If you disable gallery, you will need to install an alternative.
The following are safe to freeze/disable:
thanks buddy,what browser do you suggest?chrome is really laggy...
Try Dolphin Browser.
hi ! can i use it on an "used" ROM? i dont want to deleite muy files
Script in Kit Kat
Thankx ! :good:
it works in my Kit Kat , all appz working...
Does anybody know what the full dependencies of the Google Now Launcher are? For some reason after stripping the BR 4.4 ROM with this script, I can't get it to run after installing the dependencies it makes you install and tells you you're missing (e.g. Play Services, Google Search, Voice Search, etc). It just brings up the message about setting the default launcher by clearing the defaults for Moto home if you try to launch it.
I've got close enough I can almost convince myself it's real AOSP now just by freezing most of the Moto stuff (aside from that damn H/3G indicator in the status bar), but it'd be nice to have a 'one shot' solution like this if I have to wipe again.
Azurael said:
Does anybody know what the full dependencies of the Google Now Launcher are? For some reason after stripping the BR 4.4 ROM with this script, I can't get it to run after installing the dependencies it makes you install and tells you you're missing (e.g. Play Services, Google Search, Voice Search, etc). It just brings up the message about setting the default launcher by clearing the defaults for Moto home if you try to launch it.
I've got close enough I can almost convince myself it's real AOSP now just by freezing most of the Moto stuff (aside from that damn H/3G indicator in the status bar), but it'd be nice to have a 'one shot' solution like this if I have to wipe again.
Click to expand...
Click to collapse
I'm in the same situation with my moto g after running the debloat script from lost101. have you found whats been missing? it seems like the phone isnt recognizing GNL as a launcher
aben.dc said:
Im in the same situation with my moto g after running the debloat script from lost101. have you found whats been missing? it seems like the phone isnt recognizing GNL as a launcher
Click to expand...
Click to collapse
Had it last with mine too. Clear the cache of Google services. Of try to format cache in recovery.
Thanks for the suggestion i tried but didn't help i think there is some files missing that's been removed by the debloat script that's causing this
aben.dc said:
Thanks for the suggestion i tried but didn't help i think there is some files missing that's been removed by the debloat script that's causing this
Click to expand...
Click to collapse
hmm, strange.
Non off the stuff the script deletes is from google play services. So sry, i dunno then
Hi,
I am (was) a beta tester for the KitKat update release. During my test I also tried your KK debloater, I'm a big supporter of debloated roms.
I was on the last KK beta (before final) when I applied the debloater zip: all it was ok (super fast phone!), but when final OTA came out, the debloated KK rom did not receive any update. I wait till today and it is clear that the update will never come. I reinstalled the last Kk beta without debloating and the update came immediately.
I'have done more times the test and I can confirm that the KK debloater inhibits the Motorola updates.
OK, now final KK has been released...but if Moto decided to release another update (like small bugfix), with a debloated KK rom you do not never know the update is ready. The problem is not the installation (it is clear that is better to apply the update on a stock rom), the problem is that you do not receive any notification that tell you a new update is ready.
Do you have any idea how to fix the debloater script in order to be able to still receive system update notification?
Related
Hi!
Does anybody know if it would be possible to install the 'settings.apk' from any android ROM to the Gear using a stock ROM?
I've seen some custom ROMs have already included it (like Null ROM) but I don't really need a full custom ROM for the moment, just that little piece of software... So, would it be possible to take the deodexed apk file from one of those and install it directly to the Gear?
I tried this naive idea and extracted the .apk from the Null ROM, I tried to install it using ADB but unfortunately it didn't work (I would had been so lucky :silly: ). I got this message:
Code:
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]
I hope there's some easy way to achieve this :fingers-crossed:
Thank you!
The stock gear rom is a stripped down version of the samsung TW 4.2.2 rom, which has a lot of the dependencies in the setting removed already. If you tried to install any settings.apk, it will not work as it cannot find the dependencies that is required to run.
If you want to get into a new stock rom without pairing first, there is a way to do that. You will need to install the mk7 stock rom (via odin), and then install twrp recovery (via odin), then go into twrp recovery, mount system folder, then delete the secsetupwizard.apk, reboot, then you are at the clock, and can go into settings.
So, mk7 stock ROM is the stripped down version TW 4.2.2 ROM used in our Galaxy Gear by default, right?
Following your instructions I would get the stock ROM, a custom recovery and I would skip the initial pairing with mobile configuration but I wouldn't get the full settings application.
From what I have understood, the only way to get full settings in our watch is by installing a full custom ROM, right?
Thanks for answering quickly
yup, thats my understanding.
Then I suppose I'll have to consider that
You won't regret it. I am running null_23 now. With everything installed, I am getting about 3-4 days battery life. Though I am just using it as a notification unit, no internet(I find it too slow on the watch), no phone calls, and maybe some spy pictures , but to me I think this little watch is perfect for my needs.
Good luck.
I'll give it a try.
Btw, are you using Gear Manager for the notifications? I've noticed some trouble having installed apps on stock ROM and using Gear Manager on its lastest version (apps kept disappearing from the launcher, although were still installed).
Right now I am using ATN manager for notifications. Yes The latest gear manager does sort of "uninstall" the 3rd party apps. I have read in one of the other threads here that earlier versions of GM does not do this. So you may want to download one of the earlier GM versions and give it a try.
I have a VZW DE on 4.4.2, unlocked bootloader, rooted, no custom ROM.
Was wondering if there is any way to hide the system update prompts/notifications as I'd rather wait for a more substantial upgrade (Android L).
Using root explorer I did go to etc/security/ and renamed otacerts.zip to otacerts.zip.bak to no avail. Also, there didn't seem to be anything for me to freeze in TiBu.
Not only is this a marginal upgrade imo, I just don't want to mess with going back to stock recovery, upgrading to 4.4.4, flashing TWRP, re-root, do system tweaks (e.g. replace ugly vzw 4G Icon and bars, but first check to see if someone made one compatible to 4.4.4), research whether wifi tether from xposed module still works on 4.4.4, etc. Just plain don't have the time to do all that at the moment.
Thanks in advance!
I thought I had replied to this exact question yesterday...
use a root capable file explorer, got to /system/priv-apps and rename 3C_OTA.APK
Of course, if your phone has already downloaded the file, navigate to /cache and remove it.
Reboot after making the changes.
that has prevented getting prompted in the past.
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Schaweet said:
Out of curiosity, why wouldn't you take the update?
Click to expand...
Click to collapse
I can say for my two Non-DE Verizon Moto X phones running 4.4.2 and TowelPieRoot that I'm not taking the update for root reasons first and foremost. Until the time when a 4.4.4 root method is developed, if ever, I'll remain on 4.4.2.
I appreciate the suggestions in this thread however because I'm looking to hide these notices myself.
doitinthedirt said:
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Click to expand...
Click to collapse
Thanks, all! I went ahead and renamed the odex as well. Rebooted and good to go!
Schaweet said:
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
jamespark said:
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Click to expand...
Click to collapse
Schaweet said:
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
EDIT: I do see that you have the "Old" gravitybox installed, so this might require setting up the new version. But everything else stated is completely relevant.
I froze MotorolaOTA 1.0
samwathegreat said:
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
Click to expand...
Click to collapse
HUGE. I haven't been following any forums for several months and was not aware of this FXZ. Great to know, thanks!
Mayze23 said:
I froze MotorolaOTA 1.0
Click to expand...
Click to collapse
same
A thread already exists for this exact thing here. Please post question in Q&A in future and search before creating new threads.
Thread closed
Have anyone succesfully got Xposed Framework running on stock 5.0.2 L90 D415??
I think you have to get a new recovery (twrp) in order to install xposed and then install the rom again.
Correct me if I'm wrong.
I flashed the zip file, wiped cache, and reboot. My phone booted up but i got com.android.phone force closing. Weather app also force closes. And since com.android.phone force closes you get no signal.
My experience...did the lollipop ota for tmo, didn't really care for it much. Used one click root, added flashify and twrp custom recovery and did a nandroid backup. Installed xposed arm zip and it just stuck on the lg logo for quite a long time. Second attempt i did the wipe after installing xposed and it made it past lg logo to tmo boot and hung up. In my reading, saw something about xposed will not work on stock firmware. But isn't xposed for people that want to mod stock roms? Main thing is...back up before anything. Have already used mine 4 times.
So I originally flashed the latest xposedv66 and was not successful. Found xposed-arm-20150213b.zip everything looked good, even had signal. Like you, weather app stopped. So, I tried file manager to get to the installer and it stopped also..
If you're going to do it, BACK UP BEFORE YOU INSTALL. I cannot get it to work, reason why? I do not have the logs but if you install liveboot and activate it, then install the zip and reboot, liveboot will show you a command that is supposed to activate but fails and retries. Its essentially a bootloop but without the reboot. It will not allow you to boot without that feature being activated. Do it for yourself but remember to back up all system partitions and restore them. When you reboot after restore, the system will do the whole 'optimizing apps 1 out of 200' thing so don't worry if it takes a while to boot. Will have more on this when I get home to my laptop.
Xblackberryuser said:
So I originally flashed the latest xposedv66 and was not successful. Found xposed-arm-20150213b.zip everything looked good, even had signal. Like you, weather app stopped. So, I tried file manager to get to the installer and it stopped also..
Click to expand...
Click to collapse
Can you share that xposed? Because im trying to find one that works and can only find latest version..
Enviado do meu LG-D405 através de Tapatalk
Warimation said:
Can you share that xposed? Because im trying to find one that works and can only find latest version..
Enviado do meu LG-D405 através de Tapatalk
Click to expand...
Click to collapse
Here you go.
Found another one from March and April, but I haven't tried them.
Xblackberryuser said:
Here you go.
Found another one from March and April, but I haven't tried them.
Click to expand...
Click to collapse
I tried the one you suggested and I successfully rebooted. However, Lollipop ran slower and then I opened the alpha apk that came on the official thread. It said alpha 3.0 was installed but not activated. So I just decided to restore to before I installed. Xposed is being worked on and its in its alpha stage. Its bound to have bugs. Since THE D415 already has root, I'm fine to wait for an official version of Xposed that works to come out. Also, Even though I had 2 Gigs of data left on internal, there was a notification pestering me saying there was little to no storage left on my phone. Otherwise, no app crashes.
jesuita said:
I think you have to get a new recovery (twrp) in order to install xposed and then install the rom again.
Correct me if I'm wrong.
Click to expand...
Click to collapse
Flashing the ROM again will only wipe/remove xposed.
It's a known fact that lg weather doesnt work on xposed lollipop i also found that file manager didnt work during my period of testing, i don't know if i experienced com.android.phone force closing since I restored from my backup but xposed is definitely not usable on stock lollipop.
Newest xposed version v68 works great! No phone FCs. Now go download it!!!
Where can I download the newest version at because all of them up to this point are not stable on my lg 90 415d , I tried v71 and everytime I try to open my gmail Google Play services force closes
Sent from my LG-D415 using XDA Premium 4 mobile app
jbonilla51 said:
Newest xposed version v68 works great! No phone FCs. Now go download it!!!
Click to expand...
Click to collapse
Weather app, File manager app works on Lollipop D415 no problem or still buggy with some apps but fixed some others?
krchi said:
Weather app, File manager app works on Lollipop D415 no problem or still buggy with some apps but fixed some others?
Click to expand...
Click to collapse
There are newer versions of xposed that fix compatibility issues with LG's encrypted apps (weather, etc) since my post, so they should work with the newer versions of xposed. I only recommended version v68 because I never really use LG apps so I went ahead with such an update. Hope this helps!
Xposed for visually impaired users
Hi, everyone!
I'm visually impaired and I've been "adapting" and customizing my stuff (for a better, more comfortable usability) since 1998 (for Win and Mac) and 2010 for mobile devices, with great success.
I could install the Xposed framework to my Galaxy Tab 3 running KK 4.4.2 (Serbian Stock) back in 2012. But I cannot find a way to install it to my LG L90 D410 running Lollipop 5.0.2.
The option for those specific brands and models in based on the need for good cost-benefit ratio pieces of equipment, so that anyone can benefit from my findings, even those running on a low budget.
I'm preparing a podcast and an YouTube channel on accessibility.
All that put, I'd appreciate any input on how to make the Xposed framework to work on the LG L90. Suggestions o modules that can be useful for vision impaired people will be very welcome too.
Thanks in advance for any help I can get.
I was able to install Chinese ZTE Axon Elite (A2015) Marshmallow rom to my international version of Axon Elite (A2016). Wifi, mobile data network and calling works. All Google apps are working too, Chinese rom has google services installed but those are needed to be activated by allowing them run in a background. Only Chinese and English languages available, but system is working in your local language after installing More Locale 2 from Google Play.
This ROM is not rooted, so you need to install Super User in TWRP right after installing this ROM.
Changes:
Added modem files (modem.b00-modem.b22, modem.mdt) from international B06 NON-HLOS.bin.
Minor build.prop changes (e.g. changed English as default language).
Removed stock recovery.
Added Google Play, Google Contact sync, Google Calendar sync, Google Gmail, Google Exchange sync, Google Phone, More Locale 2.
Removed all possible Chinese ZTE bloatware (over 200MB). I had to leave Mi-Assistant so that it can be used for allowing apps running in a background (example Google Play, Super SU).
[*]Added stock Marshmallow boot animation and removed boot sound.
Features:
Latest Google Security patch
MiFavor UI 4.0 with new themes and fonts
Applications Avatar (I have no idea what it is)
Toolbox - including compass, noise test, ruler, protractor, level meter, paintings
Calendar, shows weather for five next days
New Desktop backup and recovery capabilities
Long screenshots
More system Sleep functions
Smoother UI animations
SMS two-finger zoom
New power limits
Enhanced ZTE lock screen
...and some more which might not be useful in other countries than China (please check more details from: http://www.myzte.cn/thread-270646-1-1.html)
Working:
Wifi, mobile network, mobile data, bluetooth.
Fingerprint scanning.
Google Play services + other Google apps are working too (like Calendar, Contacts sync), but must be activated in Mi-Assistant Auto-start manager and allowing permissions in apps. Please see attached images for example.
Bugs and limitations:
NFC doesn't work.
Only Chinese and English languages, but it is possible to use More Locale 2 app (included in ROM) to change locale settings. Then apps (and part of the system) are working on your defined language. On my opinion it works just like in B06. More Locale requires Root access and executing ADB command (app shows the needed command) to change locale.
Download (B15M beta, updated 09.09.2016):
Mega https://mega.nz/#!cRAXTbqQ!UYTEzWb4AH5yZbcI4fK_09QBM5TYgvCCMMl1uTijetE
Based on the tip from @martas.vavra, I removed stock Chinese recovery so TWRP is not deleted after installing this rom.
Working Super user can be downloaded here https://cloud.tapatalk.com/s/57550023717f4/SuperSU_V2.62-3.zip. Thanks again @martas.vavra.
Quick steps:
(optional) Backup all apps by using ZTE own backup/restore app. It's then possible to restore apps after rom installation.
Install TWRP+root by using the method by @acer73: http://forum.xda-developers.com/zte-axon/development/zte-axon-elite-a2016-twrp-root-t3237760
Copy ZTE_Axon_Elite_A2016_unofficial_B15M_09092016 to SD card.
Boot to TWRP recovery.
Do full backup in TWRP.
Do factory reset in TWRP.
Install ZTE_Axon_Elite_A2016_unofficial_B15M_09092016 from SD card in TWRP. NOTE! Status bar is not progressing at all when installation is ongoing! Don't panic. Just wait, it will complete.
Install Super User .zip again.
Reboot. Please be patient, first boot will take minutes to complete.
After first boot is complete, start Mi-Assistant and enable apps (Google Play, Google Contacts, SuperSU... etc) in Auto-run Manager.
Enable app permissions for Calendar, Contacts, Phone, SMS, Storage in Settings -> Apps, App permissions.
Reboot.
(optional) Restore apps by using ZTE own backup/restore app. ZTE has removed Backup/restore app but here's download link for backup/restore app from B12M: https://mega.nz/#!hZQ2HTbb!IvTJu17kjibXGSJBsRUutz0wwPZL0XlruDVAyExqsC8
Note to users: I'm not responsible if you brick your phone, so please be careful!
Thank you for your efforts! Great to hear that there are only minor bugs. :fingers-crossed:
Leaves me thinking about why ZTE does not provide this update by themselves if there are only few things needed to be adjusted in order to make this work...
There is a CM 13 for chinese Axon http://www.myzte.cn/thread-263527-1-1.html It should work
martas.vavra said:
There is a CM 13 for chinese Axon http://www.myzte.cn/thread-263527-1-1.html It should work
Click to expand...
Click to collapse
I am afraid it does not work, as @brainmaster already tried booting it - without success.
Please refer to his post here:
http://forum.xda-developers.com/showpost.php?p=66497035&postcount=5
This is great! Thanks a lot
GalaxyFan88 said:
I am afraid it does not work, as @brainmaster already tried booting it - without success.
Please refer to his post here:
http://forum.xda-developers.com/showpost.php?p=66497035&postcount=5
Click to expand...
Click to collapse
But maybe it will work using the same method the opener of the thread used! (aka replacing the radio). I don't know though...
Dapalm said:
This is great! Thanks a lot
But maybe it will work using the same method the opener of the thread used! (aka replacing the radio). I don't know though...
Click to expand...
Click to collapse
You can read here. Its not just about the radio partition.
Like already mentioned, when trying to add PIN lock, settings will force close. I also compared international B05 and Chinese marshmallow rom files and noticed differences on fingerprint modules and apps, so I believe we are out of luck here.
suunnittelija said:
Like already mentioned, when trying to add PIN lock, settings will force close. I also compared international B05 and Chinese marshmallow rom files and noticed differences on fingerprint modules and apps, so I believe we are out of luck here.
Click to expand...
Click to collapse
I think that copying that files, modules and apps would be possible, from one to another, won't you? I have no idea of how to doing it, but maybe it is easy for someone experimented in rom's modding.
@suunnittelija how about the batttery life?
Mononitoto said:
how about the batttery life?
Click to expand...
Click to collapse
Unfortunately I don't know, because I was testing this rom just half day. On that time I didn't notice battery drain. I returned back to B06 because my phone has to be password protected and I just can't live anymore without fingerprint scanner.
suunnittelija said:
Unfortunately I don't know, because I was testing this rom just half day. On that time I didn't notice battery drain. I returned back to B06 because my phone has to be password protected and I just can't live anymore without fingerprint scanner.
Click to expand...
Click to collapse
What would be necessary to do, to port fingerprint scanner etc to this rom?
Mononitoto said:
What would be necessary to do, to port fingerprint scanner etc to this rom?
Click to expand...
Click to collapse
Probably it's nothing to do with fingerprint scanner. I checked logcat file and settings will force close before that. Settings will force close right after trying to enable PIN code lock.
Code:
FATAL EXCEPTION: AsyncTask #3
Process: com.android.settings, PID: 8191
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:309)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.NullPointerException: Attempt to read from field 'int com.android.server.LockSettingsStorage$CredentialHash.version' on a null object reference
With cyanogenmod there has been similar issues with some devices and error has been caused by wrong baseband (https://forum.cyanogenmod.org/topic/118507-cant-enable-screen-lock/?page=3), which means that users have not been updating the baseband before updating the latest version of cyanogenmod. This might be the same issue, I used lollipop baseband to get this work.
I created new version based on latest Chinese B10M (previous was B09M):
https://mega.nz/#!1QgxVbza!9S0ugYNp3QmJvPxzNvcb2XB_YCsHygf3NPdohVisSg4
I don't know what kind of changes they have done for this version, but in our A2016 it has the same issues than previous version (security settings force closing etc.).
suunnittelija said:
I created new version based on latest Chinese B10M (previous was B09M):
https://mega.nz/#!1QgxVbza!9S0ugYNp3QmJvPxzNvcb2XB_YCsHygf3NPdohVisSg4
I don't know what kind of changes they have done for this version, but in our A2016 it has the same issues than previous version (security settings force closing etc.).
Click to expand...
Click to collapse
Continue your great work !
How to restore 5.0.1 ?
kacsa105 said:
How to restore 5.0.1 ?
Click to expand...
Click to collapse
Easiest and the best way is to take full twrp backup first before installing this rom. Then it can be restored in twrp and phone is restored to the state it was before.
If backup is not made, then stock B05 update.zip needs to be installed in recovery (in stock or twrp).
@kacsa105 pointed out that adb root method doesn't work anymore with B10M. I didn't notice it because I installed recovery + supe su in right after I installed B10M in twrp.
If you are now in stock Chinese recovery, then follow these steps to restore stock B05 in stock (Chinese) recovery:
1. download B05 from:
http://download.ztedevice.com/UpLoadFiles/product/643/6549/soft/2016042111364202.zip. Unzip it and find update.zip
2. place update.zip to phone internal SD card
3. shut down your phone
4. reboot to recovery: Press and hold Volume up button then Press and hold Power button. When ZTE logo appears, stop pressing Power button but continue pressing Volume up until it goes to recovery.
5. It should be now in stock Chinese recovery. You need to use volume up/down buttons and move it to the selection where is written something on Chinese but with letters SD (which means your internal SD card). Press Power button to select it.
6. Use vol down to navigate until you see update.zip and choose it with power button. If I remember correctly, you need to confirm Yes (it should be in English if I remember it correctly).
7. After it has been updated, recovery asks something again in Chinese. Don't change the selection, just use power button to select what it proposes, and system will boot.
Just wait until your phone boots back to system. If it keeps crashing, just power it down and reboot again to recovery. Recovery should be in English now. Then clear cache and dalvik (or was it factory reset?) and boot to system again.
Google play crashed, when download big data games. Solution pls
Are known any major issues with this ROM? Tired of Mi-sh*t, I'm thinking about install TWRP, make a backup and later this or CM. Is worth it?
hik4ru said:
Are known any major issues with this ROM? Tired of Mi-sh*t, I'm thinking about install TWRP, make a backup and later this or CM. Is worth it?
Click to expand...
Click to collapse
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
suunnittelija said:
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
Click to expand...
Click to collapse
How to flash recovery in recovery? I have tried to flash it via ADB, but there was stock recovery after reboot. And when I flash supersu zip the system won't boot.
Odesláno z mého ZTE A2016 pomocí Tapatalk
suunnittelija said:
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
Click to expand...
Click to collapse
What modules are you using with Xposed?
Enviado desde mi ZTE A2016 mediante Tapatalk
Nothing is more stable than Stock ROM with Stock kernel. so I've debloated stock ROM (Sept 2016 Updates) and added SuperSu to it. Result is stable and faster 295mb ROM
Changes made to MOB31E:
1. Removed Google Apps; for more space and less RAM usage.
2. @Chainfire's SuperSu added; No need to root; just flash the ROM.
3. Added Amaze file manager; Preloaded with root browser. Thanks to https://github.com/arpitkh96/AmazeFileManager
4. Added android browser (2mb); works like charm
5. Added E-mail app replacing G-mail; Gmail still works.
6. Replaced prebuilt keyboard app with another; No need to download language after fresh install.
see Screenshots attached;
Thanks to @Ali_Hasan, Pakistan for guidance ! :good:
Thanks to https://plus.google.com/+JosephGodslave for Stock ROM Zips.
Hope this will be useful
Link for Download:
https://drive.google.com/file/d/0BzM_54MLRSxkdDM3RHg1cGFNcUk/view?usp=sharing
Wew, Nice. :good:
Old debloated thread did not had September, thanks a lot (with thanks pressed too)
hp5942 said:
Old debloated thread did not had September, thanks a lot (with thanks pressed too)
Click to expand...
Click to collapse
I'm glad you liked it.
this rom is sprout 4 or sprout 8 ??
i flashing the rom, but error popup always appear in setup wizard. how to resorve it?
You replaced the default keyboard with what keyboard?
Sent from my Micromax AQ4501 using XDA-Developers Legacy app
svckid said:
this rom is sprout 4 or sprout 8 ??
i flashing the rom, but error popup always appear in setup wizard. how to resorve it?
Click to expand...
Click to collapse
Which language do you use ? I think it's because I've deleted prebuilt Korean and hindi keyboard apps. I'll try to fix this. :good:
I replaced Google keyboard with Google keyboard. Different version. Old app needed to download language pack every time after reset or fresh install.:laugh:
I tried your rom, it's clean and faster, thank you. But though you say supersu is included, still it says not rooted (supersu launcher is not present). I had to install supersu zip from the recovery. It worked
A stock rom without google play & google apps (Including google launcher, use CM launcher instead) and other apps or with pico gapps without any apps would be more leaner and faster, Let the user install the apps from the play store. I would appreciate if you try to make a barebone version with the above requirements
thank you
DNA_Uncut said:
I tried your rom, it's clean and faster, thank you. But though you say supersu is included, still it says not rooted (supersu launcher is not present). I had to install supersu zip from the recovery. It worked
A stock rom without google play & google apps (Including google launcher, use CM launcher instead) and other apps or with pico gapps without any apps would be more leaner and faster, Let the user install the apps from the play store. I would appreciate if you try to make a barebone version with the above requirements
thank you
Click to expand...
Click to collapse
Very nice of you to reply. Good suggestions. I would like to work on that. Currently caught up in preparation on exams. Very tight schedule.
How's the battery life in this rom?
kushal9968 said:
How's the battery life in this rom?
Click to expand...
Click to collapse
Haven't tried it yet, but it's safe to assume that this rom as same as stock rom, Cuz he removed the bloatware and its pre-rooted.
Flash a custom kernel and tweak it
sachin n said:
Haven't tried it yet, but it's safe to assume that this rom as same as stock rom, Cuz he removed the bloatware and its pre-rooted.
Flash a custom kernel and tweak it
Click to expand...
Click to collapse
I tried this, it was working fine, but once I rebooted it was not booting into system and it was a bootloop. I tried rebooting many times but still it remains the same. What must have happened? Pls help.
kushal9968 said:
I tried this, it was working fine, but once I rebooted it was not booting into system and it was a bootloop. I tried rebooting many times but still it remains the same. What must have happened? Pls help.
Click to expand...
Click to collapse
Working fine with others and me.
kushal9968 said:
I tried this, it was working fine, but once I rebooted it was not booting into system and it was a bootloop. I tried rebooting many times but still it remains the same. What must have happened? Pls help.
Click to expand...
Click to collapse
Eww.
Just turn off your device and enter into recovery mode, wipe data / system /cache /dalvik cache except SD card & flash a rom.
That's the step to get rid off bootloop.
Or only wipe dalvik / Cache and try booting your device, if it's boots then you're good.
after I plug stock rom debloated why internal memory and sd card is unreadable please help me
rom not installing on spice dream uno ..stuck on installing in recovery
Hi
can you add galery apps in this debloated stock rom?
btw nice rom. thanks
Good try to present here this debloated rom, earlier i used almost all roms after then i was on snapshot for two months...but after flashing this i must say ..very smooth..
Just checked download link... So this won't work for sprout8?