Related
Q&A for [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [STOCK][D58XX][5.0.2] Firmware 23.1.A.0.690 Generic [ROOT/XZDR/SuperSU]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can i flash zip or ftf via adb? i'm using cm12 rom.
hi guys,
I bought a Z3C and I just checked the bootloader is not locked .
pen the dialler and enter #*#7378423#*# to access the service menu.
Tap Service info > Configuration > Rooting Status. Bootloader unlock allowed says Yes
I wanted to know if I could flash via Flashtool software directly ?
OK, so I've used the method described in the thread, flashed firmware.zip from recovery on rooted 4.4.4. (.77), after flashing I wiped cache and dalvik, rebooted, android was upgraded, system booted, and all of my apps and settings remained intacted. Is this normal? I expected clean start. I used D5803_23.1.A.0.690_Generic_NCB-Root-XZDR2.8.3-SuperSU.
savudin said:
OK, so I've used the method described in the thread, flashed firmware.zip from recovery on rooted 4.4.4. (.77), after flashing I wiped cache and dalvik, rebooted, android was upgraded, system booted, and all of my apps and settings remained intacted. Is this normal? I expected clean start. I used D5803_23.1.A.0.690_Generic_NCB-Root-XZDR2.8.3-SuperSU.
Click to expand...
Click to collapse
If you didn´t wipe data in recovery, then no data should be wiped. That´s normal.
Yes, that's it. But, did I had to wipe data? I've read that clean install is recommended. I've noticed no problems in the last couple of hours of usage.
Dirty Flash from 23.0.1.A.5.77
I dirty flashed 23.1.A.0.690 from Greatslon MIUI v5 23.0.1.A.5.77 and still have root.
The phone froze and bootlooped a couple of times when i installed and restarted it, but patience was rewarded, as it finally booted.
I can still mount /system as rw both via adb shell, "onboard" terminal and through Root Browser.
Can i be of some help with a logcat, and in case how?
I am a software developer myself, but in a different branch than android. I just can't see through how i should get started with android development.
Great work guys
I guess i should add, that i still have my bootloader locked.
So to summarize:
>Bootloader locked (never unlocked)
>Firmware 23.1.A.0.690 from this thread
>Full root
>System R/W
Hey,
is there a chance to change the carrier name on the lockscreen? In the upper left corner it says "no service" but my carrier is already set up successfully.
Maybe its just because im from germany and its a generic rom or something. so is there a option to set up manually?
greets
Interesting, I did exactly the same but only have partial root, meaning that my system indicates root but I don't have writing permissions. Tried the ADB fix but did not work. Any other suggestions for getting full root again?
FYI: Nut has mentioned that he fixed recovery in his main development thread and will be working on releasing it to everyone soon.
Tnx for ur great work... but i have problem to download from mega site.. and specialy from the folder...
can anyone give me the direct link of [5.0.2] Firmware 23.1.A.0.690 Generic and A.5.77... not the folder link...
and can anyone tell me where exactly save the file we download from mega site ?
i cant find it anywhere...
Tnx alot.. :xX
How to delete recovery when it not working, thanks
Can't try new xposed for lollipop because it require install from recovery. And recovery not working in 5.0.2
air32 said:
Hey,
is there a chance to change the carrier name on the lockscreen? In the upper left corner it says "no service" but my carrier is already set up successfully.
Maybe its just because im from germany and its a generic rom or something. so is there a option to set up manually?
greets
Click to expand...
Click to collapse
edit the build.prop
what if I restore the TA Backup after that?
AndreDNA said:
what if I restore the TA Backup after that?
Click to expand...
Click to collapse
You would only need to restore the TA backup if you've unlocked your bootloader in the past.
I'm locked now, but it seem that I have to be unlocked to manage in upgrading to LP and keep the R/W is that right?
Sent from my D5803 using XDA Free mobile app
AndreDNA said:
I'm locked now, but it seem that I have to be unlocked to manage in upgrading to LP and keep the R/W is that right?
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
No, system rw is working atm with the newest(2.8.3) release from nut with locked bl. At least for Z3C . the system rw not working refers to other devices.
So when he manages to get the new recovery working you should just be able to install it. That is my hope at least. Anyway in case it doesnt you can backup with titanium backup and after flashing everything again just restore.
2mal16 said:
No, system rw is working atm with the newest(2.8.3) release from nut with locked bl. At least for Z3C . the system rw not working refers to other devices.
So when he manages to get the new recovery working you should just be able to install it. That is my hope at least. Anyway in case it doesnt you can backup with titanium backup and after flashing everything again just restore.
Click to expand...
Click to collapse
oh!
Really thanks for the answers, but I'm not sure to have understand (first sony for me).
I have kk, rooted and with locked bootloader. I have no recovery (I can't manage in flashing that without unlock), so how can I flash the preeroted LP?
I understand that if I backup TA, unlock BL, flash a recovery, flash a pre-rooted LP (after a full wipe), flash the last NUT recovery and then relock the BL restoring TA, I should finally have LP with root, R/W, and drm feature right? Am I missing something? Sorry for the High Noob Lvl xD
AndreDNA said:
oh!
Really thanks for the answers, but I'm not sure to have understand (first sony for me).
I have kk, rooted and with locked bootloader. I have no recovery (I can't manage in flashing that without unlock), so how can I flash the preeroted LP?
I understand that if I backup TA, unlock BL, flash a recovery, flash a pre-rooted LP (after a full wipe), flash the last NUT recovery and then relock the BL restoring TA, I should finally have LP with root, R/W, and drm feature right? Am I missing something? Sorry for the High Noob Lvl xD
Click to expand...
Click to collapse
Go to the thread of NUT dual recovery and (assuming your on a windows pc) download the installer for nut dual recovery. it will let you install the recovery on locked bootloader by running the install.bat file. with this recovery you can then flash a prerooted lollipop zip (you can do it yourself with prf creator, include the newest SuperSU zip and the newest dual recovery zip together with stock lollipop rom) after wiping your phone. people also just flashed over KK but i prefer to do it clean and set up my phone newly again. you will then end up with a phone which has system rw and root on lollipop but the recovery will be gone until NUT fixes it. That is what everybody is waiting for.
So unlocking BL wont really gain you anything except sonys DRM keys not working. it will just introduce an additional step to relock them.
Here is the thread: http://forum.xda-developers.com/showthread.php?t=2261606
to get into recovery just spam the volume up button(or down since it has two recoveries ) when your phone boots and lights up the led.
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.
RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.
RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/
For anyone who has an unlocked bootloader and wants to update to Fire OS 4, here's a stock 4.5.2 ROM that won't overwrite your current unlocked bootloader or recovery partition.
DOWNLOAD HERE
All credit goes to Cpasjuste for the current version - I might be uploading 4.5.5 here soon.
bmccoy11 said:
For anyone who has an unlocked bootloader and wants to update to Fire OS 4, here's a stock 4.5.2 ROM that won't overwrite your current unlocked bootloader or recovery partition.
DOWNLOAD HERE
All credit goes to Cpasjuste for the current version - I might be uploading 4.5.5 here soon.
Click to expand...
Click to collapse
Any feedback on this ROM?
Can this be installed on its own? Can I wipe /system and install? Downloading now but figured I'd ask here.
riggsandroid said:
Any feedback on this ROM?
Can this be installed on its own? Can I wipe /system and install? Downloading now but figured I'd ask here.
Click to expand...
Click to collapse
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
bmccoy11 said:
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
Click to expand...
Click to collapse
Right so when I borked my previous rom (ooooops) without a backup, this will give me stock Amazon rom back.
Thanks.
@bmccoy11
Ok so it flashed fine and I noticed you already did otacerts.old in /system/etc/security and I don't see the dcp apk in /system/app, however it tried DL'ing an update right away.
How do you recommend stopping OTAs?
Trying this method - http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550 - seems to work
Thanks.
bmccoy11 said:
Yes, it can be installed over a cleanly wiped system partition. This is just the stock ROM that doesn't overwrite unlocked bootloaders when flashed.
Click to expand...
Click to collapse
Is the 4.5.5 build far away? Might give it a crack over the weekend if it will be up.
Yes, the 4.5.5 is available here, already OTA blocked. I had to do a factory reset after flashing it (use ONLY the factory reset within TWRP, NOT the native factory reset) to get it to work, but after that, clear sailing, works great.
Ok, I'm a little confused about the process. My kindle fire is sitting at 4.5.4. I have refused to turn it on, because I don't want it to take 4.5.5. I want to re-establish root. I understand there is a downgrade process that allows you to move back to 4.5.2, then you can install root.
My question is, how do I unlock the boot loader at this point? Do I need to have an unlocked boot loader to install new images. I really want to be able to root and have the google play store installed, and not have all the bull**** errors like before with the playstore crashing.
Thanks to all you guys that have the answers and knowledge.
rlkellyjr said:
Ok, I'm a little confused about the process. My kindle fire is sitting at 4.5.4. I have refused to turn it on, because I don't want it to take 4.5.5. I want to re-establish root. I understand there is a downgrade process that allows you to move back to 4.5.2, then you can install root.
My question is, how do I unlock the boot loader at this point? Do I need to have an unlocked boot loader to install new images. I really want to be able to root and have the google play store installed, and not have all the bull**** errors like before with the playstore crashing.
Thanks to all you guys that have the answers and knowledge.
Click to expand...
Click to collapse
You can not unlock the bootloader on that device as it can not be rolled back to a version of FireOS (3.2.3.2 or below) containing the vulnerability that the unlock procedure exploits. The lowest you can go is 3.2.8. Any attempt to go further will result in a brick.
To get to 4.5.2 you rollback to 3.2.8 first using the procedure in this thread. Follow instructions precisely or you can damage/brick your device. Understand there are risks involved; this is not a task for the uninformed. There are no step-by-step guides or slick videos. Copious reading is your best friend along with the community servicing HDX forums.
Once on 3.2.8 you can upgrade to 4.5.2, block OTA, root, install Safestrap v4 and then Nexus v4 or cm11 both of which give full access to the Google Play Store. I strongly advise against attempting to install the play store under FireOS. Amazon and Google components do not play nice. Best use a different rom.
Do some reading and decide if you are up for the adventure. Ask questions before acting. Make sure you fully understand the relevant tasks, expected outcomes and things you should never do (like enable WiFi while on 3.2.8 - instant brick).
Edit: Fixed typos...
Thanks! but i have a question, why CM ROM the sound quality is very bad, even i install Dolby.
a442509097 said:
Thanks! but i have a question, why CM ROM the sound quality is very bad, even i install Dolby.
Click to expand...
Click to collapse
Search the HDX LineageOS 14.1 thread; many claim Viper4 is a better solution. Seems a bit complicated to obtain/install but that may be a faux impression. I am satisfied with Dolby but don't demand much from my device from an audio performance perspective.
how to delete this reply…
a442509097 said:
Viper4 is same too, i think this is about audio drive problem, because i try 4.22 or 4.4.4 system(however custom) sound quality has enough bass.
Click to expand...
Click to collapse
Might reach out to those who have installed (and presumably customized) Viper4 for this device. They claim sound quality is equal to if not superior to stock FireOS v4 (4.4.x base). I did notice a mild degradation going from Fire Nexus KTU84Q (4.4.4) to Android 5+ but not enough to warrant additional actions beyond installation of Dolby for noise reduction (random pops during quiet passages) and extended volume range. The builds were heavily customized when development resources were heavily focused on ROM enrichment. Things are different now; you'll likely have to roll your own if you believe this issue is with core binaries. Third gen devices have been out of production for 2+ years.
You sure about that? Wikipedia page for the series is under the impression they're still producing and selling the 7 inch HDX (which never got a 4th gen release), at least for LTE users.
Insidious622 said:
You sure about that? Wikipedia page for the series is under the impression they're still producing and selling the 7 inch HDX (which never got a 4th gen release), at least for LTE users.
Click to expand...
Click to collapse
LOL - since when did Wikipedia become the definative resource for Amazon devices? 3rd gen HDX is definitely out of production and has been for quite some time.
Fair enough, I just wasn't sure. Sometimes it's accurate, sometimes it isn't
Hi guys i need a zip or a backup. fore the orginal apollo room. i delet the backup fore safetrap and now i stuck at cm 4.4.4 and i will unlock my bootloader and install a other room but i need a orginal apollo backup or a zip to flash.
Serbest955 said:
Hi guys i need a zip or a backup. fore the orginal apollo room. i delet the backup fore safetrap and now i stuck at cm 4.4.4 and i will unlock my bootloader and install a other room but i need a orginal apollo backup or a zip to flash.
Click to expand...
Click to collapse
Bootloader can be unlocked while using CM 11 (KitKat 4.4.4) under Safestrap. Just follow the instructions. No need to reload FireOS.
Davey126 said:
Bootloader can be unlocked while using CM 11 (KitKat 4.4.4) under Safestrap. Just follow the instructions. No need to reload FireOS.
Click to expand...
Click to collapse
I need help while I understand the service not quite? How do I create this unlock file?
i follow this instruktion https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 and i have now install twrp and need now the unlock file.
texmexdud said:
Yes, the 4.5.5 is available here, already OTA blocked. I had to do a factory reset after flashing it (use ONLY the factory reset within TWRP, NOT the native factory reset) to get it to work, but after that, clear sailing, works great.
Click to expand...
Click to collapse
Links to that one are dead, could you please give up to date links?
Hi,
So i have a Moto G 2 XT-1068 with Android 5.0.2 and system version 22.21.28.titan_retaildsds.retaildsdsall.ex.03 reteu.
I rooted it and installed Xposed.
Since some days, my phone notify me that there is a new (official) update avalaible :
22.56.3.en.03
My first reflex was to post in the Xposed forum :
I have a Motorola Moto G 2nd edition (2014 XT-1068) with Android 5.0.2 and these xposed versions installed :
XposedInstaller_3.0_alpha4.apk
xposed-v75-sdk21-arm-1
This morning, my phone notify me that there is a newsoftware update available :
22.56.3.en.03
Can i update ?
Will Xposed still running or do i have anything to do before or after update ?
Click to expand...
Click to collapse
then :
Yes i'm rooted (i didn't know i could install exposed without root ?!) and i ask the question to rooted users : what is the recommended behavior to have when we are rooted and there is an official update like this one ? Should i ignore it ? Should i wait ? Should i update (with one of your solutions) ?
Click to expand...
Click to collapse
and this is the reply i had :
You'll have to ask how an OTA works for that in your device forum.
For Google Android (untouched by OEM) in Kitkat, OTA used to check each important file individually and if one was modified, OTA would fail. This did not check all existing files or added files such as root, so as long as you uninstalled Xposed properly (restoring the original app_process files etc) then an OTA would be fine.
Since Lollipop, OTA checks the /system partition as a single item so any modification in any file, or any additional file will make the OTA fail. In which case, the only way to update would be to flash a stock ROM.
You will need to find out in your device forum which of these applies to your device.
Click to expand...
Click to collapse
So this is it, i make a post in this Moto G 2014 forum
Doing the OTA will most likely delete the XposedBridge.jar so you will have to flash it again.
Else the Xposed app will still be available but the Framework won't be installed.
If it doesn't update because the /system partition has been modified, you'll have to flash the whole rom to update.
Ok, so i can try without risk ?
And what about my root ?
nonobio said:
Ok, so i can try without risk ?
And what about my root ?
Click to expand...
Click to collapse
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Hi
TheKill69 said:
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Click to expand...
Click to collapse
Ok.
Seriously said:
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Click to expand...
Click to collapse
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
nonobio said:
Hi
Ok.
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
Click to expand...
Click to collapse
You might have to flash the whole stock firmware back to get the stock recovery. Big waste of time.
Then rooting back means using CF Auto Root Commands again..
You have to update to it though if you want Android 6.0.
Since it won't be soon, you rather go for CM13 once it gets really stable.
Also by the way, Xposed is already supported on MM.
Thanks for these precisions.
So if i can resume : a custom rom is easier for enjoy Android updates than just Xposed.
Hi,
Can you confirm :
For someone searching advanced features like customize status bar, quick settings, shutdown menu, hardware buttons, etc : customs roms and "stock rom + exposed" are two solutions. BUT, for someone searching these same advanced features but also keep his device up to date : custom rom is really a better solution. Isn't?
I was happy when i discovered xposed as it seemed to be a easier process that flashing a custom rom, but i didn't know that i couldn't update easily..
So, what is the advantage to use xposed instead of custom rom?
Hi,
I am always thinking if i will update my stock rooted xposed rom, or if i will install a custom rom prerooted like Cyanogen mod (o have easier future updates).
i have some questions :
1- Is it possible to install xposed and modules on a custom rom like cyanogen mod ? I think yes but can you confirm ?
I know that CM come with inbuilt tweaks but i discover some great xposed module i would continue to use, even if i install CM.
2-If i keep my stock rooted xposed rom, and don't make this "little" Android 5 OTA update, will be i notified for "Android 6" ?
(i don't want to lose my time to reflash my rom, reroot mydevice, etc.., just for a little update, but i could do that for a more important update like Android 6...
3- We are agree that if i flash a custom rom like CM, it will resolve my "ota update" problem, cause there won't be "Motorola OTA" anymore, but there will be CM updates easy to make, isn't ? If yes, what could be the advantage to use stock rom rooted + xposed vs custom rom + xposed ?
Thanks
So this Morning I woke up to find I had lost Root. Previously I had installed the Marshmallow update about a week ago with no problems. My bootloader has been unlocked for sometime now via the sunshine .apk and I had even regained root and installed all my favorite ( and absolutely ESSENTIAL ) rooted apps including Viper, TWRP, SE Linux changer. You know all the normal apps that go along with root. I'm kicking myself now because i didn't install TB or make a back up in TWRP. Anyways this morning when I didn't have root I didn't panic I got on XDA here and searched the problem and found a thread where someone had lost root during the initial flashing of marshmallow. ( https://forum.xda-developers.com/droid-turbo/help/help-recquiring-root-flashing-mm-update-t3515393 ). It was recommended that he should flash a beta version or chainfires SU ( https://www.androidfilehost.com/?fid=457095661767121356 ). It was the same SU that I had used a week ago when flashing Marsmellow on my phone so I redownloaded the file booted into recovery ( TWRP 3.0.0.0 ) and flashed the zip. I then went to reboot and viola. My phone now wont get passed the bootloader is unlocked warning screen. It just flashes that screen then goes blank and then flashes the screen again and over and over again.. bootlooped ! uck !!
My questions are
1- What are my options ?
2- Why would I have lost root over night ?
3- Is there any way to save my data or do i just reset the phone and start fresh?
Thank you in advance for any help you can provide me or for just taking the time to read about my issue. I hope its just me and not something like the Motorola Camera app fiasco for the UltraMaxx of a few years ago.. Did I mention a few apps updated last night. I don't remember exactly which ones and I can't get into the playstore because of my afore mentioned bootloop.. I think they were some google apps mainly. Anyways thanks for your help I super appreciate it.
Very strange. Luckily you have TWRP.
Try either/both flashing via TWRP...
* TWRP-flashable version of the Verizon Marshmallow update, then the beta SuperSu.
[ROM] MCG24.251-5 100% Stock
https://forum.xda-developers.com/showthread.php?t=3512949
Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
Click to expand...
Click to collapse
Or
*ComputerFreak274's tweaked version of that update, and the beta SuperSu.
Computerfreek274_MM_1.0.4 Marshmallow 6.0.1 Stock rooted VOLte Debloated
https://forum.xda-developers.com/showthread.php?t=3503634
Based from Newest Stock 6.0.1 From MCG24.251-5 Verizon Stock OTA.
1.0.4 Change Log
Native Tether. (Tested and Working)
Audio Boost In call volume. "Fixed in 1.0.4 Lowed down from 94 to 90 Stock is 84 to avoid echo when volume was up to full."
Audio Boost Media Audio.
De-Bloated.
Removed Some Google apps like YouTube ,books,games,videos,Google Photos, Slacker radio, NFL Game,Verizon Cloud, Google pay and and some Verizon apps. Plus the demo stuff and mp4's also removed all amazon junk.
init.d Support.
Tweaks for speed.
Tweaks For battery life.
Click to expand...
Click to collapse