Currently my phone is stuck in a boot loop, I assume for too little space to create the dalvik cache.
http://pastebin.com/kzTtDwET
I need to overwrite the framework and service files with their _backups. However, I can't as it is read only, and when I try to invoke su, it fails even though I have the superuser apk installed.
How can I solve this?
Related
I installed SlaidyBoost-V2.3 (http://forum.xda-developers.com/showthread.php?t=1574322) on my GIO running Particle ROM. Before doing that I deleted the pre-installed RAM-script by juwe11. After the restart, my phone hang while booting so I had to restore system via my nandroid backup. Is there any way to track down the error besides installing one script a time to see which one is causing the error? Can i force my phone to create a detailed log of thee boot-process on the sdcard so it doesn't get deleted when restoring /system?
I can't post in the developer's thread as I don't have the necessary 10 helful posts to be allowed to post there ...
Any help is greatly appreciated.
madelgijs
That happened to me too after i've installed slady-boost scrip my phone was stuck every boot 3-4 minutes at splash screeen and then boot-up..
So just as the title says i decided to root my n7. Everything seemed to go smooth until my nexus 7 was stuck on the boot animation screen for about 20 minutes. I tried doing a factory reset in TWRP and it said wipe failed. I decided to flash CWM instead and do a factory reset but i couldn't. It said error mounting /data. I'm not sure what to do googling around didn't seem to work.
TWRP gave me a message saying SU is not installed after i installed the recovery so i clicked instal SU. I'm not sure if that contributed to my problem or not. Any help would be greatly appreciated.
Ok so i figured this out.
So for anyone who ever gets into an endless bootloop with the inability to wipe data you need to do the following.
1. Download the latest Factory image from google.
2. Exctract the files into your platform-tools folder an run the "flash-all" command this video illustrates it perfectly http://www.youtube.com/watch?v=bsss9e71bKo
3. And you're done! hopefully this helps someone out
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.
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
I'm trying to install LineageOS 17 on a OnePlus 6.
I can boot into twrp and the install process appears to work successfully. I can swap slots and install into either slot.
When I reboot the phone I get to the screen that says "Start" and "Fastboot mode" at the top. If I try to start the phone it comes back to this screen. When I go back into twrp, the contents of /sdcard is empty. I can copy over files using adb push, install the rom and then reboot. However, every time I reboot it seems like it completely wipes the phone including the install it's just done and /sdcard is also wiped.
When I booted into twrp previously, it required my unlock code. It now no longer does that. I wonder if this is part of the problem?
If I install just oxygenos, it takes me to the oxgenos recovery screen but I cant' do anything from there. I'm guessing that won't allow me to boot with an unlocked bootloader?
Can anyone advise how I can get out of this? Installing anything using twrp looks like it works, but it's like it gets wiped every time I reboot.
I can't even seem to get OxygenOS back to working.
Can anyone give me some tips on where to go from here? Nothing I can do from TWRP seems to help. I have tried wiping everything in both slots and reinstalling oxygen, no luck
Still stuck?