Long story short, I really want to experience Dynamic System Updates on my moto g power (2020, Sophia), but I want to make sure it's almost completely safe to do so and would like additional details.
So, my first question: Is it completely safe to install a DSU? This phone is my only phone and is my daily driver, so I want to be 100% sure my phone will not be bricked.
Additionally, should I choose to continue, which DSU do I install? There are four options:
{
"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"
}
Does it matter which one I pick? Will picking the wrong one put my device at risk? Have any of you successfully installed one?
Thanks,
BroJac5246
BroJac5246 said:
Long story short, I really want to experience Dynamic System Updates on my moto g power (2020, Sophia), but I want to make sure it's almost completely safe to do so and would like additional details.
So, my first question: Is it completely safe to install a DSU? This phone is my only phone and is my daily driver, so I want to be 100% sure my phone will not be bricked.
Additionally, should I choose to continue, which DSU do I install? There are four options:
View attachment 5810743
Does it matter which one I pick? Will picking the wrong one put my device at risk? Have any of you successfully installed one?
Thanks,
BroJac5246
Click to expand...
Click to collapse
Completely safe, this won't be installed over your actual firmware, it's just a kind of (non-permanent, but only for testing) dual-boot.
The 4 options are good for this device, S stands for Android 12, T is Android 13, and GMS is with Gapps (Google Mobile Services), anyway, a wrong election (in other scenario) will cause the installation failing.
SubwayChamp said:
Completely safe, this won't be installed over your actual firmware, it's just a kind of (non-permanent, but only for testing) dual-boot.
The 4 options are good for this device, S stands for Android 12, T is Android 13, and GMS is with Gapps (Google Mobile Services), anyway, a wrong election (in other scenario) will cause the installation failing.
Click to expand...
Click to collapse
Hmm... I just tried both the Android 12 and 13 options and neither worked, the phone just booted back into Android 11 as if nothing had happened (Although I still had the notification offering to discard the DSU or restart the phone). Interestingly, when the Motorola logo appeared while restarting, it disappeared and then reappeared, which doesn't typically happen. I'm no expert, but did the phone maybe try to boot into the DSU and then gave up?
Now all 6 DSUs (because they're Android 14 ones now) immediately result in an "Install failed" error when I try to install them.
Do I need an unlocked bootloader?
Related
It's finally time for me to do what every XDA user done already - root my phone and use another ROM. I haven't ever before done this that's why I'm very excited.
I'm trying to follow this noob-friendly guide http://forum.xda-developers.com/showthread.php?t=2213910 . I read it like ten times already, but I still have some questions.
1. I want to have a CM rom. Should I get Lloir's CM 12.1 or the official CM 11? The thing is, I won't be able to get another rom for almost a year and I want a quite stable rom.
2. I guess I should install the latest TWRP 2.8 recovery from this forums, am I right? But then, why on the official CM download page there is a separate "Cyanogen Recovery" file?
3. According to the tutorial, I should install SuperSu, is this the right version?
https://download.chainfire.eu/696/SuperSU/
4. The thing I'm worried about mostly - my digitizer is damaged and I sometimes get "phantom touches", I can't tap anything on screen, the only solution is screen off & on. What if phantom touches appear when I'm in recovery? From what I read most things are controlled by physical buttons (which work), but not all, some requires to swipe. What then? Can I turn the screen off or abort the process and start again?
Thanks in advance for every reply.
If you need a stable rom you should stay on stock.
1. I use CM12.1 and used CM11 before. I prefer 12.1. They all have some more or less annoying bugs -> read the threads and make your own decision
2. Use the TWRP version which is linked in the rom thread. Cyanogen recovery has less functions and is not public released for x+ afaik
3. CyanogenMod is shipped with it's own su-management app. So no need to install SuperSU
4. you can turn screen on and off in recovery
Thank you very much!
An hour ago I installed CM12.1, I may say successfully, because it booted and now Play Store is downloading GBs of apps., so I can't in fact do anything .
Maybe just one lat thing. If I'd like to install a CM12.1 update in the future, do I have to wipe everything? Or just flash the boot.img and rom and that's it?
CM says you don't need to wipe, but Lloir sometimes wants us to wipe x)
In CM12 root must be enabled in developer options btw.
crusader727 said:
but Lloir sometimes wants us to wipe x)
Click to expand...
Click to collapse
{
"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"
}
Device is a pretty much new LG V30 from verizon, running android 8.
I have done pretty much nothing with the device yet. No root, no tinkering, nothing. I accidentally accepted the software update request it showed me today, which I didn't want. I shut the device down but everytime I would turn it on it would start the update progress.
The only other option I had was booting into recovery, so I did that. I was presented with the following options:
{
"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"
}
So I went with factory reset. After that the phone won't boot anymore, and all I see is this screen:
What can I do now?
Again: No root. No unlocked bootloader. Nothing. I used LG's "require password on boot" feature though, which I assume is equal to android's full disk encryption. (?)
I talked to LG already since it's under warrenty (got it literally last week) - LG however told me the warrenty is void because there is a small crack on the back of the phone. WTF? Is that even true? I didn't drop the phone. I don't even know where the crack comes from. It's small. Shouldn't the warrenty cover that TOO instead of voiding the warrenty for everything else? Like jesus christ all I want is LG to fix my software why does a crack on the back matter?
From what I see my only option is to access fastboot and re-flash the ROM? The thing is: How do I access fastboot on this phone? Power and Vol- brings me into recovery (stock) everytime. Are there flashable images for the V30?
No one knows what I should try or what I could look into? This doesn't sound like it could be something overly complex to me.
Issue still persists. I had a talk with verzion at their store and they said I'd have to pay a $149 deductible. So what can I do now?
I'm assuming flashing a ROM via fastboot. Two questions:
1) Where can I get the ROM from?
2) How can I access fastboot on this phone? The method suggested everywhere puts me in LG's stock recovery, not in fastboot.
Hi,
Newbie here so go easy!
Ive been changing the settings on an imported chinese tablet such as boot image, remove bloatware, download apps required, etc and it works great. However, I want to be able to create a full image of one tablet and transfer that to other tablets I buy so I dont have to manually do this every time. Basically a full backup and restore of everything on the tablet.
Can anyone assist on the best process to do this.
Thanks
If device's Android got rooted then you can perform a full NANDroid backup by means of either TWRP or FlashFire. FYI: ROOT is required for mounting all partitions as RW.
TWRP:
{
"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"
}
Flashfire:
Full article here:
How to Backup Android Device Completely 2023 (Updated)
If you plan to unlock bootloader or want to flash custom ROM, this guide is for you. In today's article, I will show you how to Backup Android Device
www.rootingsteps.com
Hi,
Thanks for the help.
The device is rooted but im struggling to get a TWRP recovery image for this tablet as its a chinese import. However, its a Rockchip RK3288 tablet. Any help with where to find correct version?
Also when I down loaded flash fire its starts up but crashes after a few seconds?
duckett100 said:
Also when I down loaded flash fire its starts up but crashes after a few seconds?
Click to expand...
Click to collapse
Do a LOGCAT to get the reason why.
[Tutorial] How To Logcat
Here's how to use logcat: There are two main ways to do a logcat, within android, and through adb. Logcat within android can be done one of two ways, through a Logcat app: Here are two good examples are either: aLogcat or Catlog I prefer...
forum.xda-developers.com
Hi, I worked out why flash fire was crashing, but some of the items in the app are greyed out so it doesn't allow a back up. I think its because I still have the standard recovery that came with the tablet instead of something like TWRP. And I cant find one online that will work.
Are there any other ways to do a full back up programmatically?
Well, it's a bit of a long story, so I'll try to be as short as possible.
Last year, and after hours of searching on the internet, I found the solution for "Custom binary blocked by frp lock" on this forum (here and here). Both methods promised to fix the lock without erasing my data, but I decided to try the second one (it consists of reinstalling only the boot image with Odin).
Fortunately it worked for me on the first try, and since this method was not well known on the internet, I decided to make a video tutorial to help those who had the same problem and wanted to keep their data.
The fact is that, unfortunately, this method didn't work for everyone, and in many cases it generated bootloops or black screens of death.
And my question is: does anyone know what could be the cause of this?
I tested it on SM-J710MN and SM-G532M, both running Android Marshmallow, and the bootloops/black screens occurred on devices running Android 6, 7, 8 and (I guess) 9 and 10.
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
jwoegerbauer said:
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
Click to expand...
Click to collapse
Thanks for answering.
Maybe I did not express myself in the correct way, but actually I was referring to the block that does not even allow to boot the device and only shows words in red, as seen in this image.
{
"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"
}
But beyond that my question is about why does the bootloop or black screen happen after flashing the boot.img file? Does it have to do with a different/incompatible version of Android/binary/csc or something like that?
My phone is the CPH2459. I purchased it with the July 5, 2022/2022-07-05 Android Version.
1. I enabled developer mode.
2. I had enabled oem bootloader unlock
3. I had enabled "Disable Updates at startup
4. I has disabled automatic play store updates.
Two days go by and the phone goes behind my back and installs an Android 11 update so now I'm on Android 11 September 9, 2022/2022-09-05 update.
The phone tried to mention that it wanted to start the next update to Android S or some nonsense but I decided to stop right there and factory reset it.
After the reset, I'm still stuck on Android 11 September 9, 2022/2022-09-05 update.
Now tonight I want to try and continue rooting this phone unless there is a way to rollback to original Android 11 July 5, 2022/2022-07-05 Android Version.
What would be my next steps. I have downloaded everything I've been suggested to a usb so I can keep working on this step by step. You guys are awesome for sharing this information. Thank you for what you do.
Absolutely! And thank you. Heading home now so Ill shoot you my info.
Once I get familiar with getting this to run on one os I should be able to save copies and then jump back and forth right? I always wonder if it will be like how samsung and other manufacturers sabotage attempts to downgrade and other such annoyances.
So I would go here?
{
"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"
}
Then I would download which one of these stock boot images?
Followed by which Firmware version?
Just want to make sure I'm on track. None of them say US version, so I'm assuming Global version?
I'd like to know if he ever backed up his rom...I could use a copy.
I see. May I send you a pm?