Related
My Nexus 5 is running Cyanogenmod 11 and seems to be working just fine. However, when I get a prompt to install a Cyanogenmod update, the phone reboots to recovery, attempts to install the update, and fails. I have found that this seems to be caused TWRP showing 0 MB internal storage and not being able to mount Data. Again, the phone works fine except for this weirdness.
I should also add that it does strange things after I reboot from recovery. First, the Phone app continually stopped, then was fine a while after. Then Google Play Services was constantly crashing, so I uninstalled the updates and it started working. And finally, Cyanogenmod gave the initial setup screen the last time I rebooted from recovery, though it only went through language and time zone.
As a final note, I don't really know a whole lot about Android in terms of the more advanced things, so try to keep any suggestions relatively noob friendly. Thanks.
Please can you open the zip you're flashing and get the updater-script from meta-inf/com/Google/android, rename to a .txt file and upload here?
I think cm updates are using wrong /sdcard location.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Please can you open the zip you're flashing and get the updater-script from meta-inf/com/Google/android, rename to a .txt file and upload here?
I think cm updates are using wrong /sdcard location.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
There ya go.
windoge said:
There ya go.
Click to expand...
Click to collapse
Thanks.
That looks fine actually...
What's the actual error message you get? Are there any logs in /cache/recovery?
restorecon sdcard
su
restorecon -rF /data/media/0
rootSU said:
Thanks.
That looks fine actually...
What's the actual error message you get? Are there any logs in /cache/recovery?
Click to expand...
Click to collapse
Here's a log.
Should also mention that, since posting this thread, the details of the issue seem to have changed. TWRP now shows the proper amount of space rather than 0MB and is able to mount all partitions. At this point, installing the update just fails for some reason.
hrbwaxdoll said:
su
restorecon -rF /data/media/0
Click to expand...
Click to collapse
Not sure what to do with that. Terminal editor? TWRP?
windoge said:
Here's a log.
Should also mention that, since posting this thread, the details of the issue seem to have changed. TWRP now shows the proper amount of space rather than 0MB and is able to mount all partitions. At this point, installing the update just fails for some reason.
Not sure what to do with that. Terminal editor? TWRP?
Click to expand...
Click to collapse
Download the zip and dirty flash it. Skip the updater
http://download.cyanogenmod.org/?device=hammerhead
Sent from my Nexus 5 using XDA Free mobile app
windoge said:
Here's a log.
Should also mention that, since posting this thread, the details of the issue seem to have changed. TWRP now shows the proper amount of space rather than 0MB and is able to mount all partitions. At this point, installing the update just fails for some reason.
Not sure what to do with that. Terminal editor? TWRP?
Click to expand...
Click to collapse
Download the zip and dirty flash it in recovery. Skip the updater
http://download.cyanogenmod.org/?device=hammerhead
Sent from my Nexus 5 using XDA Free mobile app
windoge said:
Here's a log.
Should also mention that, since posting this thread, the details of the issue seem to have changed. TWRP now shows the proper amount of space rather than 0MB and is able to mount all partitions. At this point, installing the update just fails for some reason.
Not sure what to do with that. Terminal editor? TWRP?
Click to expand...
Click to collapse
Download the zip and dirty flash it in recovery. Skip the updater
http://download.cyanogenmod.org/?device=hammerhead
Sent from my Nexus 5 using XDA Free mobile app
windoge said:
Here's a log.
Should also mention that, since posting this thread, the details of the issue seem to have changed. TWRP now shows the proper amount of space rather than 0MB and is able to mount all partitions. At this point, installing the update just fails for some reason.
Not sure what to do with that. Terminal editor? TWRP?
Click to expand...
Click to collapse
Download the zip and flash it in recovery. Skip the updater http://download.cyanogenmod.org/?device=hammerhead
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
Wtf?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Download the zip and dirty flash it. Skip the updater
http://download.cyanogenmod.org/?device=hammerhead
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Still doesn't work, causes same problem.
Also, here's the error message:
Code:
assert failed: apply_patch_check("/system/priv-app/SystemUI.apk","db0ed1023cv7e3ef6b1a02beab40a3042e078b68","78af477050e20251e9f5eebb39bf57b68ca8ad74")
E:Error executing updater binary in zip '/cache/cm-hammerhead-1f023a4eca-to-a3225bddbd-signed.zip'
Updating partition details...
windoge said:
Still doesn't work, causes same problem.
Also, here's the error message:
Code:
assert failed: apply_patch_check("/system/priv-app/SystemUI.apk","db0ed1023cv7e3ef6b1a02beab40a3042e078b68","78af477050e20251e9f5eebb39bf57b68ca8ad74")
E:Error executing updater binary in zip '/cache/cm-hammerhead-1f023a4eca-to-a3225bddbd-signed.zip'
Updating partition details...
Click to expand...
Click to collapse
Are you using the latest version of twrp?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you using the latest version of twrp?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Must be. I just reinstalled it and get the same error.
windoge said:
Must be. I just reinstalled it and get the same error.
Click to expand...
Click to collapse
I got the same error in my Samsung Galaxy S3. Either TWRP 2.8.1.0 or 2.6.3.1 didn't work. It may be some securities don't allow to read storage.
I got my phone rooted by towelroot and install TWRP using Flashify.
same problem
I have j710F with stock android 6.0.1,I flashed twrp two but when i booted into recovery I was facing the problem of 0 mb internal storage so I formatted the data and the problem was fixed but when I rebooted my phone into system and made the whole setup again and after that I again booted into recovery the problem was again the same so i again repeated the whole process and the result is same....
I wamt to flash a custom rom but couldn't due to this problem can anybody help me?
I cant restore from a nandroid backup.
I get error messages
E: Unable to find file system (first period)
E: Cannot restore system -- mounted read only
Can anybody help? Please!
david_inuk said:
I cant restore from a nandroid backup.
I get error messages
E: Unable to find file system (first period)
E: Cannot restore system -- mounted read only
Can anybody help? Please!
Click to expand...
Click to collapse
Fixed by updating to the latest version of TWRP
Sent from my MI 4i using XDA-Developers mobile app
david_inuk said:
Fixed by updating to the latest version of TWRP
Sent from my MI 4i using XDA-Developers mobile app
Click to expand...
Click to collapse
Can you share link for latest version of TWRP?
0967894983 said:
Can you share link for latest version of TWRP?
Click to expand...
Click to collapse
I used the TWRP app which downloaded and flashed the correct version for me automatically.
The app is however slightly confusing to use!
You need to click on the + icon to get at the options.
As the Dev isn't able to share it directly to this sub forum, I'll attach the link to his thread below :
https://forum.xda-developers.com/re...igrate-root-fixed-version-unofficial-t3944054
Here's the link : https://drive.google.com/file/d/1HUvqwmAH-qKTd0YMAg-Vc_9e8jeAPZDg/view
Your doing great jobs for rn 7 pro user please keep doing this.
yay..finally work 100% in peter twrp
important note ;
1. before make backup with migrate>>>go to preference>uncheck "use new method to calculate size"
2. in peter twrp flash migrate backup after flash rom,gapps, magisk and disable encryption
if error 7 still appears, just reboot to recovery and flash migrate backup again
thanks for make work again in our violet..
tested
aosp (100% work to restore all apps)
miui (some apps with split data failed to restore) fixed by reinstall app via playstore
afah_me said:
yay..finally work 100% in peter twrp
important note ;
1. before make backup with migrate>>>go to preference>uncheck "use new method to calculate size"
2. in peter twrp flash migrate backup after flash rom,gapps, magisk and disable encryption
if error 7 still appears, just reboot to recovery and flash migrate backup again
thanks for make work again in our violet..
tested
aosp (100% work to restore all apps)
miui (some apps with split data failed to restore) fixed by reinstall app via playstore
Click to expand...
Click to collapse
Yep totally works.
Works with encryption?
Sent from my Redmi Note 7 Pro using XDA Labs
adriansticoid0312 said:
Works with encryption?
Click to expand...
Click to collapse
Yes, I backed up on MIUI and restored from Pixel Experience while I was encrypted. Even though most apps and data were restored properly, it failed with a few apps (I don't remember their names).
Mine says nothing to restore after flash. Anyone with a fix?
Naveenthemi said:
As the Dev isn't able to share it directly to this sub forum, I'll attach the link to his thread below :
https://forum.xda-developers.com/re...igrate-root-fixed-version-unofficial-t3944054
Here's the link : https://drive.google.com/file/d/1HUvqwmAH-qKTd0YMAg-Vc_9e8jeAPZDg/view
Click to expand...
Click to collapse
Hmmm. ?
I uninstalled Google Playstore using ES file explorer's root uninstaller and rebooted my phone. Then I reinstalled Google Playstore with an apk file (now shown as user app. The re-installation was success but the app keeps crashing after I tried to download an app with it.
I uninstalled Google Playstore in the first place because I encountered the "waiting for download" bug (apps stuck on that messages without downloading at all).
I cannot flash GApps in TWRP because it says /system partition not found.
I'm using Rooted Asus ROG phone, stock ROM 15.1630.1903.89, magisk
Please help
GphonePrince said:
I uninstalled Google Playstore using ES file explorer's root uninstaller and rebooted my phone. Then I reinstalled Google Playstore with an apk file (now shown as user app. The re-installation was success but the app keeps crashing after I tried to download an app with it.
I uninstalled Google Playstore in the first place because I encountered the "waiting for download" bug (apps stuck on that messages without downloading at all).
I cannot flash GApps in TWRP because it says /system partition not found.
I'm using Rooted Asus ROG phone, stock ROM 15.1630.1903.89, magisk
Please help
Click to expand...
Click to collapse
Anytime you uninstall/remove system files and apps or anytime you reinstall/replace system files and apps, it is best to boot into recovery then wipe cache and dalvik cache then reboot. The reason why this must be done is because when you remove/add stuff from/to system, the OS is looking for stuff that is there when it shouldn't be or is not finding stuff that should be there but isnt.
Wiping cache and dalvik then rebooting allows the device to rebuild cache as it should be for what is currently in system.
The most effective fix with the least possible issues in your situation is to reflash your stock firmware then flash TWRP on the device again then root the device again using Magisk.
Next time, before you add/remove system files/apps, boot into TWRP and create a nandroid backup of your current ROM, then, if you encounter issues when you add/remove system files/apps, you can boot into TWRP and restore the backup and you'll be restored to exactly what you had before you added/removed the system files/apps.
The ability to create and restore backups via TWRP is the main purpose for using TWRP, the ability to flash ROMs and such is a minor secondary feature or purpose of TWRP.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Anytime you uninstall/remove system files and apps or anytime you reinstall/replace system files and apps, it is best to boot into recovery then wipe cache and dalvik cache then reboot. The reason why this must be done is because when you remove/add stuff from/to system, the OS is looking for stuff that is there when it shouldn't be or is not finding stuff that should be there but isnt.
Wiping cache and dalvik then rebooting allows the device to rebuild cache as it should be for what is currently in system.
The most effective fix with the least possible issues in your situation is to reflash your stock firmware then flash TWRP on the device again then root the device again using Magisk.
Next time, before you add/remove system files/apps, boot into TWRP and create a nandroid backup of your current ROM, then, if you encounter issues when you add/remove system files/apps, you can boot into TWRP and restore the backup and you'll be restored to exactly what you had before you added/removed the system files/apps.
The ability to create and restore backups via TWRP is the main purpose for using TWRP, the ability to flash ROMs and such is a minor secondary feature or purpose of TWRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the detailed reply. I have re-flashed the stock ROM and re-rooted the phone now.
Now, I am just wondering why I am still encountering the "/system partition not mounted" error in TWRP for both (now and the previous time) rooting procedures? This prevents me from installing busybox and flash anything with TWRP.
PS: I am following the rooting guide here, since it is the most detailed one for newbies like myself. According the the screenshots shown in this guide, the OP also encountered the "/system partition not mounted" error in TWRP (system shown as 0MB, and before booting to system with TWRP, the message "no OS found" appeared). Hence I suspect his guide was not perfect despite getting root successfully. Mind having a look at the guide for me to see whether you could spot any missing/wrong steps please? (I know it is in Chinese but it does have loads of screenshots) I would really appreciate it. Thanks so much!
GphonePrince said:
Thanks for the detailed reply. I have re-flashed the stock ROM and re-rooted the phone now.
Now, I am just wondering why I am still encountering the "/system partition not mounted" error in TWRP for both (now and the previous time) rooting procedures? This prevents me from installing busybox and flash anything with TWRP.
PS: I am following the rooting guide here, since it is the most detailed one for newbies like myself. According the the screenshots shown in this guide, the OP also encountered the "/system partition not mounted" error in TWRP (system shown as 0MB, and before booting to system with TWRP, the message "no OS found" appeared). Hence I suspect his guide was not perfect despite getting root successfully. Mind having a look at the guide for me to see whether you could spot any missing/wrong steps please? (I know it is in Chinese but it does have loads of screenshots) I would really appreciate it. Thanks so much!
Click to expand...
Click to collapse
Is your device an A/B partition device?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Is your device an A/B partition device?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
It's Asus ROG phone. seems like it is according to here: https://www.xda-developers.com/list-android-devices-seamless-updates/
GphonePrince said:
It's Asus ROG phone. seems like it is according to here: https://www.xda-developers.com/list-android-devices-seamless-updates/
Click to expand...
Click to collapse
That is the problem then, the process of rooting and flashing TWRP on A/B devices is very much different than how it is done on other non A/B devices.
Look for instructions on how to use TWRP on devices that have A/B partitions.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
That is the problem then, the process of rooting and flashing TWRP on A/B devices is very much different than how it is done on other non A/B devices.
Look for instructions on how to use TWRP on devices that have A/B partitions.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I will look into it thanks
Hello dear devs and professionals, I'm stuck with my lovely poco x3 pro because of not being able to restore my twrp backup from my nokia 8 android 8 to my poco x3 pro android 11, I have tried all kinds of tricks I could but none of them were succeeded, below are the methods I tried:
1 using twrp restore
2 using twrp restore with renaming backups from ext4 to f2fs
3. Using migrate app
4. Using titanium backup
5 using migrate restore twrp function
6 using titanium backup with restore nandroid function
I am really frustrated and hopeless, please if anyone knows what should I do, please please help all my apps data are necessary to me, without them poco x3 pro is useless to me
OAndBackupX
Swift backup
Backup and restore apps one by one to avoid issues.
There's no perfect backup restore app.
pl1992aw said:
OAndBackupX
Swift backup
Backup and restore apps one by one to avoid issues.
There's no perfect backup restore app.
Click to expand...
Click to collapse
The problem is that my nokia phone is ext4 partition while my poco x3 pro is in f2fs file system, and every time I tried to restore my backups it's ended in force encryption state and data inaccessible error.
Is there any way to disable force encryption lock?
I tried dm-verity disabler and I faced /odm partition not found error
Please help me disable it.
error748 said:
The problem is that my nokia phone is ext4 partition while my poco x3 pro is in f2fs file system, and every time I tried to restore my backups it's ended in force encryption state and data inaccessible error.
Is there any way to disable force encryption lock?
I tried dm-verity disabler and I faced /odm partition not found error
Please help me disable it.
Click to expand...
Click to collapse
Leave data unencrypted
Hello! Is there any possibility now to leave data partition unencrypted? Tried to install miui.eu with PBRB with dfe toggles enabled - no result. Tried to install same through TWRP + latest dfe - no result Tried to install havoc treble + dfe - no...
forum.xda-developers.com
Thanks for your swift and honest reply but the problem is that my rom is global rom not eu version and it is in 12.04 right now
Is this post you mentioned earlier work for my situation as well?
Thanks again
pl1992aw said:
Leave data unencrypted
Hello! Is there any possibility now to leave data partition unencrypted? Tried to install miui.eu with PBRB with dfe toggles enabled - no result. Tried to install same through TWRP + latest dfe - no result Tried to install havoc treble + dfe - no...
forum.xda-developers.com
There's another one in Telegram group.
Poco X3 Pro | Updates
@PocoX3ProUpdates
Click to expand...
Click to collapse
error748 said:
Thanks for your swift and honest reply but the problem is that my rom is global rom not eu version and it is in 12.04 right now
Is this post you mentioned earlier work for my situation as well?
Thanks again
Click to expand...
Click to collapse
I don't know. I didn't use it.
Since you are using MIUI, another way to try is install Mi Mover in your Nokia and then backup from it, then restore in MIUI.
Still don't expect it can backup and restore apps fully functional, it's just another try and error.
No no I'm using Crdroid 11 the latest version