Hi all,
Okay, so I tried to mess with the build.prop file in order to get Netflix. I made a copy of the original file. I also have a backup using the Clockwork recovery mod. I tried restoring the file via Root manager but I must have deleted it because the phone will not start. The Motorola logo shows but then the phone goes into a dimly lit gray blank screen. I can go to the bootloader by pressing start and up on the volume switch. How can I access the system folder so I can replace the build.prop file? Do I use RSDlite or SuperOneClick? I have the OTA 2.2 Froyo - no ROMS. Is there a file manager app so that I can access the phone files via my pc? Do I have to flash?
Thanks!
If you cannot access the adb shell anymore and the phone cannot start, the only way I know is to flash it. It's possible to can send build.prop back to it's location, but you cannot access to it under bootloader
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?
hello
I was editing "user" files in system directory
after edit I reboot my tablet but my tablet went on a boot loop
I can't delete my data because I need them all and can't make a factory reset or etc
Is there any way to edit files from pc or with recovery menu to restore all changes back?
or any file to install and exit from boot loop?
thank you all
I am new to android.
I Had temp rooted my phone using king root app.
I tried to download and install the OTA but while installing it would take me to the Fastboot mode and not update.
so I downloaded the flashify app from the play store and flashed the ota.
now my phone wont boot into the system even if I select factory reset it just comes back to fastboot mode.
I unlocked my phone and flashed twrp and using filemanager in twrp I saw that all my files are intact.
Is there any way I can boot into the system without loosing my data.
I read somewhere that all the options are mapped to flashboot so it is not rebooting to system, so is there any file I can edit to set the reboot option back to system .
Please help me.
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