Okay so to begin, my device is a us cellular moto z2 force. I had rooted my device with magisk using twrp successfully and everything was working fine.
Where i ran into problems was when i tried to figure out how to get a new boot animation to work. Originally I tried using a rooted file manager to edit /oem/media/ for the boot animation there. I had already placed a new boot animation in /system/media and it still showed the normal boot animation on boot, so i looked it up and /oem/media seemed to be where it checks first.
I tried to use the twrp file manager to rename the file in /oem/media since the root file manager was not working.
What happened was that it still showed the normal boot animation on start up and while twrp showed the one in /oem/media to be renamed, the root file manager did not. This is where i got confused.
I ended up looking around in twrp some more to try and figure out why when i noticed an /oem in /system. I thought (somewhat badly) that this may have been the place where the boot-animation was, even though I couldn't see it. This is the part where everything went wrong.
I deleted /system/syestem/oem because i didn't see the bootanimation.zip in it to delete individually, i just deleted the whole thing because of something i saw about /oem not being needed.
After this my phone still booted but a notification came up saying "finishing updating android" and I knew i did something wrong. Also the check in magisk came back with basic integrity but not the other one. I also noticed magisk was not installed anymore.
This is when I decided to restore from a backup in twrp and bricked my phone. After restoring I restarted my phone and it got stuck in a loop of the screen fromthis guide on how to remove the boot loader unlocked splash screen, which was working fine before.
Any help would be appreciated.
Okay so Managed to boot by switching partitions and clearing cache and data in twrp.
Now my issue, SafetyNet ctsprofile and basic integrity are both false, and I still have no idea how to change the boot animation without bricking my device.
So I was able to download magisk manager then re-download install the magisk framework directly from the app. It seems it was on some middle ground where it didn't work properly but I still had root and could grant superuser to apps, but couldn't install modules or have safety net.
Still have not figured out how to change bootanimation or anything in /oem without it coming right back on boot or while android is running, may give up if it ends up taking too long.
You should use a flashall to get yourself back to stock and unbroken. If you cant find the flashall for usc here google for Nash flashall, its definitely out there. I've been messing with OEM today and it looks like dm-verity is undoing all of our changes.
Related
What exactly does TWRP recovery do as part of its start-up routine? Because whatever it does just broke my phone's ability to boot successfully. I have a Sprint Note II (SPH-L900) running CM12.1.
Backstory: My phone was working fine with CM12.1 and Clockwork Recovery installed, except that I discovered today that I couldn't launch the default Android "Messaging" app. I found a post elsewhere on XDA that suggested deleting the files mmssms.db and mmssms.db-journal from the /data/data/com.android.providers.telephony/databases/ directory. My phone was not rooted, so I couldn't do this with a userspace file manager, and CWM Recovery doesn't have a file manager, but TWRP does. So I rebooted to bootloader, flashed TWRP, rebooted to TWRP, and used its File Manager to add ".old" to the end of the filenames of the two files just mentioned. Then I rebooted the phone.
Very unpleasant surprise: The CM boot animation just went on forever. Repeated attempts, even after flashing back to CWM recovery, yield the same result: the phone no longer boots successfully. This is exactly the same problem that I struggled with for several days recently while trying to install CM12.1 using TWRP recovery. (It never worked. I could only get it to work by flashing it with CWM recovery.)
It appears that TWRP does something as a routine part of its normal startup or shutdown that is breaking my CM12.1 installation. But what could that be? And how can I undo or fix it?
Hey,
I wanted to create an nandroid backup in TWRP and got error 255 in the process.
I got the log of the failed update:
cloud.directupload.net/dfZq
So i searched for a solution, and the internet said that i should remove the file wich causes backup to fail. The logs said it was '/system/app/AndroidPay'
This is a file, not a folder.
So i removed the file, keeping an backup of it, booted into TWRP and the backup still failed.
To my surprise the boot into OxygenOS fails now. It shows the Oneplus Powerd by Android logo, turns black and reboots into twrp. Recovery and Bootloader seems to work fine.
So I connected my device with my computer and tried to get the file back to '/system/app' using adb.
I tried 'adb push AndroidPay /system/app' and it seems to be transferred succesfully, however the boot into oxygenOS is still not working.
I think it can be fixed by formatting the device and flash OxygenOS new to it, but I really don't wanna do that.
General Information:
Oneplus 3
OxygenOS 3.3.4
Rooted
Xposed Installed
No custom kernal
TWRP 3.0.2-0
File wich may be broken: cloud.directupload.net/dfZs
Is there an easyer way than resetting my whole phone to get it to work ?
I'm sorry for language mistakes or maybe leaving relevant information.
Thank you for help
I've had same problem today, my solution is restore "System" part (only system) from old backup, it saved my data and OP3 works fine after that
Wipe system, then flash OOS and it should work fine. If it doesn't Im afraid you need to do a full clean install since it isn't system related then.
Hi,
I wanted to update my Pixel C to the most current factory image with flashfire as i did it before a few times without problems.
So I DL'd current factory image from https://developers.google.com/android/images#ryu, opened it in flashfire and said it should flash the normal partitions except recovery as i don't want that it overwrites my TWRP.
Flashfire analyzed the zip file and after i said "flash" it restarted my Pixel into a black screen. At this point i was wondering that nothing more happened.
I waited for 10 minutes so that maybe something in the background could happen, but there was no further action. The screen kept black.
After these 10 minutes i restarted the device but now it always runs into TWRP directly instead of starting the system
I also tried to install the zip manually in TWRP but it tells me
"Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing the zip file '/usb-otg/ryu-n2g48c-factory-0bc0ee15.zip'"
As you can see from the error message i also tried to dl the file again and install it via OTG but the same thing.
If I go into the file manager in TWRP i can still access the folders from the sdcard.
The bootloader is unlocked of course.
Anyone an idea what i can do without loosing all the data?
Thanks in advance
Download the full system image and extract it. There should be a flash_all-file (bat for windows of sh for linux). Open it with an editor and remove the "-w" option in fastboot. "-w" is the switch for wipe. After you removed it, you can flash the complete image and your system should boot again into android. After that you can install a custom recovery, etc. again.
Thank you peter, worked like a charm for the system flash. Now follows the TWRP etc again
EDIT: ok, the system flash was the only thing that worked like a charm. I tried flashing TWRP with NRT but didn't work. I am stuck now at a "no command" screen when i start the device.
To install the custom recovery NRT tells me that i will loose all my data, so i wanted to backup everything.
Unfortunately i can't backup everything now as the temp booted TWRP demands a password to decrypt the sdcard, but i only have a pattern and no password set.
So now i try to flash everything again and to install twrp without loosing all the data.
Hey everyone I have flashed android 7.1.2 August again and android started afterwards without any problems. I was able to restore the backup of all the apps from Google.
Than I wanted to get back root and flashed TWRP with Nexus Root Toolset, but now only TWRP starts every time I switch on the tablet. Any ideas what I can do?
EDIT: I fixed it somehow with flashing the whole firmware package again and than the TWRP wich broke the startup again so i ended up in a TWRP bootloop. Therefore i flashed android again and TWRP 3.0.0.0 than TWRP 3.0.2.4 (something like that) and after like 3 to 4 different flashing steps it worked again. I have no idea what happened during the first flash of Andoir 7.1.2 but i think that something broke there.
I was trying to uninstall systemless xposed from my phone and while looking for how to do so, I deleted app_process32 from system/bin using twrp's file manager. Everything worked fine but I found the real way to uninstall it (deleting it from magisk), it put my phone in a boot loop. Is there a way for me to download this file and put it back? I do not have a backup file.
update: I tried to flash Lineage 15.1 ROM and now I only have access to bootloader. I've tried flashing other ROMS but it gets stuck on a T-Mobile screen. Everything flashes except for bootloader.xml
I upgraded my 8 Pro to Android 11 (11.0.1.1 IN11BA) and was able to keep root using Magisk's feature "patch to inactive slot".
However, after two-three reboots on Android 11 (activating some Magisk modules, and installing some apps) the phone suddenly got stuck in a boot loop.
I figured it might be helpful for someone else to know how I recovered my phone without losing any data.
First, I needed to get access to the phone, so I entered fastboot mode by pressing volume button during boot.
Then I downloaded my firmware dump from XDA and patched the recovery.img using this tutorial:
https://forum.xda-developers.com/on...ecovery-oxygen-os-stock-recovery-adb-t4084487
My patched recovery image is linked in post #46 of that thread.
I fastboot flashed (since fastboot boot didn't work) the recovery image to my phone and rebooted to recovery.
Using the patched recovery image I was able to get root access to all partitions, including /data.
When investigating a boot loop on this phone I found the following path useful:
Code:
/mnt/vendor/op2/boot_log/
In that directory you will find logs from the last five or so boots, and at the end of the "android_boot.log" file I found this message:
Code:
StagingManager: Failed to install sessionId: 664232199 Error: APEX activation failed. Check logcat messages from apexd for more information.
I'm not familiar with "StagingManager" and "APEX sessions", but after digging through PackageInstallerService.java it seems this error is caused by some kind of app installation that is done during reboots (now I'm guessing).
Anyway, I didn't care much about the reason for the error, I just wanted my data back, so I deleted this file (containing the failed APEX session):
Code:
/data/system/install_sessions.xml
After deleting that file I was able to boot my system and access all my data again!
Nvm..
dladz said:
Don't need with the recovery is still intact so no need to touch it you'll cause more issues.
So you got the bootloop when you installed some magisk modules.
Click to expand...
Click to collapse
My boot loop was not caused by a magisk module. I did remove all magisk modules and even re-flashed stock boot.img, but that did not help.
adb wait-for-device didn't work since the boot loop occurred before adbd start (it seemed).
And, I absolutely didn't want to wipe my system from recovery.
nilezon said:
My boot loop was not caused by a magisk module. I did remove all magisk modules and even re-flashed stock boot.img, but that did not help.
adb wait-for-device didn't work since the boot loop occurred before adbd start (it seemed).
And, I absolutely didn't want to wipe my system from recovery.
Click to expand...
Click to collapse
No worries man I got the wrong end of the stick. Dw
I've Updated and it's stuck at bootloop . What I can do?
My mobile is the T-Mobile version that I have converted to Android 10 International.
this will help someone, for sure
nice work writing down your expirience
Just to be clear with what I said earlier.
If it fails after a magisk module installation then just boot to safe mode then reboot and all magisk modules will be deactivated.
According your post that's how it happened.
"However, after two-three reboots on Android 11 (activating some Magisk modules, and installing some apps) the phone suddenly got stuck in a boot loop"
1. Safe mode
2. Reboot
3. Remove last module and activate other modules.
Done
PS: I do a lot of module testing and this is my safety net so yes it 100% works.
You're method will help people for sure though
just so you know, you just saved my ass.
i expirienced the same problem
i did cleard data of google, google services, google framework and google play store
after that - google downloaded some kind of update and that's it
at android boot log there was same error
adb shell rm /data/system/install_sessions.xml using modded stock recovery rocks