[help] ResurrectionRemix doesn't boot anymore - Moto G4 Plus Questions & Answers

Hello, yesterday I runned out of battery on my moto g4 plus so then I charged the phone and booted it stucks on boot animation.
How can I fix it without losing files?

osmak said:
Hello, yesterday I runned out of battery on my moto g4 plus so then I charged the phone and booted it stucks on boot animation.
How can I fix it without losing files?
Click to expand...
Click to collapse
Can you boot into recovery?

Dhanush-raj said:
Can you boot into recovery?
Click to expand...
Click to collapse
I can boot into recovery, and adb shell to make a log when booting. In /system I only had /bin so I made a backup of /system and /data the I wipe, dalvik, cache, data, system and reinstalled RR so now it works

Related

Bootloop after installing Naptime

I installed Naptime (rooted phone). Put my 6P into standby. Worked for 15 minutes. I went away and came back and the device was in a bootloop. Can't believe naptime could be the cause of this, but things were fine before this was installed. Symptoms sounds like the bootloop others are complaining about.
Wiped the Davlik cache. Made no difference.
Tried to restore my TWRP backup and that reboots after about 90MB. If I choose verify the MD5 backup, TWRP reboots after about 30 seconds of verification. So it seems like any I/O attempt on the system partition is causing the 6P to reboot. Is there anything else I can try before resorting to an RMA w/Google?
mrlad said:
I installed Naptime (rooted phone). Put my 6P into standby. Worked for 15 minutes. I went away and came back and the device was in a bootloop. Can't believe naptime could be the cause of this, but things were fine before this was installed. Symptoms sounds like the bootloop others are complaining about.
Wiped the Davlik cache. Made no difference.
Tried to restore my TWRP backup and that reboots after about 90MB. If I choose verify the MD5 backup, TWRP reboots after about 30 seconds of verification. So it seems like any I/O attempt on the system partition is causing the 6P to reboot. Is there anything else I can try before resorting to an RMA w/Google?
Click to expand...
Click to collapse
Wipe everything except internal, and not only the cashes, and try your restore again.
You can also try to install a full factory image from the Google website using flash-all.bat command.
jhs39 said:
You can also try to install a full factory image from the Google website using flash-all.bat command.
Click to expand...
Click to collapse
Tried a full factory install of 7.1.2 (was on 7.1.1). Didn't help. Shows the Google boot logo and then reboots.
What is interesting is fastboot was able to write the system image for 7.1.2.
coremania said:
Wipe everything except internal, and not only the cashes, and try your restore again.
Click to expand...
Click to collapse
I'm on TWRP 3.1. Just noticed its crashing wiping any of the items (cache, Dalvik cache etc.). The reboot happens after it shows updating partition table.
Was finally able to get a clean Dalvik cache wipe. I noticed that in all cases, there are three TWRP errors about mounting the cache partition before it does the wipe. Is this normal?
mrlad said:
Was finally able to get a clean Dalvik cache wipe. I noticed that in all cases, there are three TWRP errors about mounting the cache partition before it does the wipe. Is this normal?
Click to expand...
Click to collapse
I don't know if it's normal but I've seen the same errors on my device after installing the 7.1.2 factory images and wiping the cache in TWRP 3.1. I assumed it might have to do with no cache partition being included with 7.1.2.
Sent from my Nexus 6P using XDA Labs
mrlad said:
Tried a full factory install of 7.1.2 (was on 7.1.1). Didn't help. Shows the Google boot logo and then reboots.
What is interesting is fastboot was able to write the system image for 7.1.2.
Click to expand...
Click to collapse
I still get a constant reboot too.
I also have naptime but this issue wasn't an immediate problem after any form of installation. I was just scrolling through facebook and then phone freezes and reboots and then gets stuck in reboot lol.
HELP
jono0402 said:
I still get a constant reboot too.
Click to expand...
Click to collapse
What does your reboot loop look like? I see the Google logo for a few seconds then the device reboots. I never see the animation start.

Bootloop after app uninstall - A5 2016

Hello guys!
My phone is stuck in bootloop (Samsung animation and a few vibrations every 10 secs).
This happend after I uninstalled a battery stats helper app (rootuninstaller.bshelper) installed in the /system partition. I believe it messed up some files in /system :silly:
I would like to recover the phone without losing the app data, if possible. What are my options?
I have OS 6.0.1 with SuperSU root and stock recovery.
I can connect with ADB but I don't have the keys, so I'm locked out.
Should I flash the stock ROM with Odin? Will it delete the /data partition?
Or will it overwrite just /system?
Thanks!
aand16 said:
Hello guys!
My phone is stuck in bootloop (Samsung animation and a few vibrations every 10 secs).
This happend after I uninstalled a battery stats helper app (rootuninstaller.bshelper) installed in the /system partition. I believe it messed up some files in /system :silly:
I would like to recover the phone without losing the app data, if possible. What are my options?
I have OS 6.0.1 with SuperSU root and stock recovery.
I can connect with ADB but I don't have the keys, so I'm locked out.
Should I flash the stock ROM with Odin? Will it delete the /data partition?
Or will it overwrite just /system?
Thanks!
Click to expand...
Click to collapse
I would first try with flash TWRP and wipe cache/dalvik from there, before flashing anything else.

Failed installing Lineage 14.1, wiped system, now restoring stock won't boot

Attempt 1 to install Lineage
Tried installing the Lineage 14.1, it kept doing a blank-but-illuminated screen, then turned off and back on, resulting in a boot loop.
We tried a couple of things - first the more conservative wiping of just data, dalvik and cache.
This did the boot loop described above. I then restored the stock backup and all was well.
Attempt 2 to install Lineage
The second time we wiped the system partition in addition to the above. Same bootloop.
Went to restore the backup of stock again, but now it's getting stuck at "I'm not a phone I'm a comprehensive yada yada" screen. It never progresses past this.
Attempts to get Stock Restore working
We've tried restoring just the system, data and dalvik
We've also tried System Image in addition to these.
No joy.
We don't have a laptop or other device to hand for a few days so we have just what's on the phone - the Lineage 14.1 zip, the stock backup and TWRP.
Any ideas how we can get back to a working phone with either OS?
What type of LePro3 do you have?
X720,X722,X727?
It's the X722
kenbw2 said:
It's the X722
Click to expand...
Click to collapse
The X722 model is not supported by Lineage.
I think that you have a problem. Hope anyone can help you to go back to stock successfully.
When doing the stock restore, we didn't restore the boot image.
Is that something worth trying?
kenbw2 said:
When doing the stock restore, we didn't restore the boot image.
Is that something worth trying?
Click to expand...
Click to collapse
Yes, you could try it. Please, write, was it useful or not)
Success!
Restored System,. System Image, Cache, Data and Boot partitions and all is now back to normal.
Phew!
kenbw2 said:
Success!
Restored System,. System Image, Cache, Data and Boot partitions and all is now back to normal.
Phew!
Click to expand...
Click to collapse
That is great. So, is bluetooth works fine after that?

I have a question I recently flash the rom "PixelExperience for Moto G5 Plus [Potter]

I have a question I recently flash the rom "PixelExperience for Moto G5 Plus [Potter]
Hello Everyone,
I have a question I recently flash the rom "PixelExperience for Moto G5 Plus [Potter]" in my phone now the problem is on reboot from TWRP mode my phone is booting and get stuck at the logo "G" with a line image indicating Loading. So Can anyone help me how to over come this problem? I had faced issue of memory formate. So I had change it to ext 4. And flashed the rom. Everthing worked while installing it was showing "Patching system unconditional" .
Please help me out.:crying::crying::crying:
Neel_bhatt said:
Hello Everyone,
I have a question I recently flash the rom "PixelExperience for Moto G5 Plus [Potter]" in my phone now the problem is on reboot from TWRP mode my phone is booting and get stuck at the logo "G" with a line image indicating Loading. So Can anyone help me how to over come this problem? I had faced issue of memory formate. So I had change it to ext 4. And flashed the rom. Everthing worked while installing it was showing "Patching system unconditional" .
Please help me out.:crying::crying::crying:
Click to expand...
Click to collapse
In TWRP go to advanced wipe option and select dalvik, system, cache, then swipe to wipe. Now flash the ROM again and it should work fine.
I tried but in vain
Roary358 said:
In TWRP go to advanced wipe option and select dalvik, system, cache, then swipe to wipe. Now flash the ROM again and it should work fine.
Click to expand...
Click to collapse
Hello...... thank you for quick response but it didn't work. Still facing the same issue. Do I have to root my device i.e. supersu?
:crying::crying::crying:
Neel_bhatt said:
Hello...... thank you for quick response but it didn't work. Still facing the same issue. Do I have to root my device i.e. supersu?
:crying::crying::crying:
Click to expand...
Click to collapse
It's very unlikely that it didn't fix the issue, the first boot always takes a considerable amount of time so try waiting for a few minutes, if that doesn't work it might be because your data partition was encrypted, if you don't mind loosing the data wipe and format it and try the same steps as before again, if not just flash the January build.
Roary358 said:
It's very unlikely that it didn't fix the issue, the first boot always takes a considerable amount of time so try waiting for a few minutes, if that doesn't work it might be because your data partition was encrypted, if you don't mind loosing the data wipe and format it and try the same steps as before again, if not just flash the January build.
Click to expand...
Click to collapse
There is no need to wipe the data partition, if the data partition corrupts it would corrupt everything all together.
Anyways can you tell me everything you've flashed in the progress?
With PE you only need to flash the rom itself. (Gapps are already included) and try to shut down the phone after flash (Using shut down option in twrp) and power on with power button
Try to flash PE again but before you do, wipe Data, Dalvik, Cache, and System
Dont worry about losing important data on the /Data/ partition. That is the partition where your.. well, app data is held. (Internal storage is the place of where all your personal data lies such as pictures and videos)
(edit meant something else)

Galaxy Tab A 8 (SM-T350) stuck on boot loop after trying to recover stock firmware

Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
skorpien said:
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
ashyx said:
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
Click to expand...
Click to collapse
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
skorpien said:
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
Click to expand...
Click to collapse
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
ashyx said:
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
Click to expand...
Click to collapse
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
skorpien said:
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
Click to expand...
Click to collapse
Did you back up the efs partition with twrp?
If so try restoring it.
ashyx said:
Did you back up the efs partition with twrp?
If so try restoring it.
Click to expand...
Click to collapse
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
skorpien said:
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
Click to expand...
Click to collapse
Don't restore everything just EFS No need to keep wiping dalvik it serves no purpose when formatting or wiping the data partition.
Also FORMAT not wipe the data partition (note this wipes internal storage)
If it still doesn't boot install the combo firmware. Let it boot, factory reset from settings then reboot to download mode and install the stock firmware again.

Categories

Resources