Database Users

[Q] Noobish Doubt Regarding TWRP backup !

Hi,
This is my story :
Bought Nexus 4 16GB Unlocked and rooted on the same day. Then i took a TWRP backup of stock rooted ROM. After that i flashed PA 3.60 ROM. Now my phone is running with PA 3.60(with Stock PA Kernel which comes in ROM). Now i want to go back to my Stock ROM (and yeah wait for 4.3 official update). I know that restoring the TWRP backup which i took first time will restore my Stock ROM. But does it contains the Kernel too ? Or do i need to flash the stock Kernel separate ?
Simply my doubt is this, TWRP backup will include the Kernel too or just ROM ?

Yeah the full nandroid backup does contain the stock kernel.

jithuelad said:
Hi,
This is my story :
Bought Nexus 4 16GB Unlocked and rooted on the same day. Then i took a TWRP backup of stock rooted ROM. After that i flashed PA 3.60 ROM. Now my phone is running with PA 3.60(with Stock PA Kernel which comes in ROM). Now i want to go back to my Stock ROM (and yeah wait for 4.3 official update). I know that restoring the TWRP backup which i took first time will restore my Stock ROM. But does it contains the Kernel too ? Or do i need to flash the stock Kernel separate ?
Simply my doubt is this, TWRP backup will include the Kernel too or just ROM ?
Click to expand...
Click to collapse
Backups should included the kernel also known as the boot image. I don't use TWRP but yeah, unless you have a option to not backup the kernel selected you should be good.
In other words whatever kernel you had when you created your backup should be restored

trentreed said:
Backups should included the kernel also known as the boot image. I don't use TWRP but yeah, unless you have a option to not backup the kernel selected you should be good.
In other words whatever kernel you had when you created your backup should be restored
Click to expand...
Click to collapse
Thanks for the reply. Rally appreciated. But i don't have a image file though. See this screen shot. Is this enough ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jithuelad said:
Hi,
This is my story :
Bought Nexus 4 16GB Unlocked and rooted on the same day. Then i took a TWRP backup of stock rooted ROM. After that i flashed PA 3.60 ROM. Now my phone is running with PA 3.60(with Stock PA Kernel which comes in ROM). Now i want to go back to my Stock ROM (and yeah wait for 4.3 official update). I know that restoring the TWRP backup which i took first time will restore my Stock ROM. But does it contains the Kernel too ? Or do i need to flash the stock Kernel separate ?
Simply my doubt is this, TWRP backup will include the Kernel too or just ROM ?
Click to expand...
Click to collapse
a nandroid backup is the full image of the backed up rom, it restores the entire rom to the backed up time stage. Its like system restore in windows. If you have not changed your kernel before backup, you will get back your original kernel back. If you are still doubtful wipe everything before restoring nandroid backup, and then restore your backup. it will boot. :laugh:

josinpaul said:
a nandroid backup is the full image of the backed up rom, it restores the entire rom to the backed up time stage. Its like system restore in windows. If you have not changed your kernel before backup, you will get back your original kernel back. If you are still doubtful wipe everything before restoring nandroid backup, and then restore your backup. it will boot. :laugh:
Click to expand...
Click to collapse
Thanks for the clarification bro. However i know about nandroid back up as i used it on my Xperia. But the doubt was it includes the Kernel or not.
Thanks for the explanation. Cheers :victory:

Getting "internal" or "system" error when trying any ROM

I managed to get the stock google MDB08M build on and rooted, but I have tried several different ROMs and each time I get constant "system" or "internal" error messages when first booting up. It makes the ROMs unusable.
On top of that, if I try to restore a previous nandroid it just gets stuck at the animated android logo. In order to get it to work again I have to complete re-image the phone back to stock, re-root, re-install custom recovery.
Any ideas what could be causing this?
Thanks,
Craig

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this the message? I get the same ****
Sent from my Nexus 6P using Tapatalk

csh8428 said:
I managed to get the stock google MDB08M build on and rooted, but I have tried several different ROMs and each time I get constant "system" or "internal" error messages when first booting up. It makes the ROMs unusable.
On top of that, if I try to restore a previous nandroid it just gets stuck at the animated android logo. In order to get it to work again I have to complete re-image the phone back to stock, re-root, re-install custom recovery.
Any ideas what could be causing this?
Thanks,
Craig
Click to expand...
Click to collapse
Have you tried flashing the MDB08M vendor image after flashing the ROM? Are you wiping properly (system, data, cache, dalvik cache)? In regards to your nandroid backup, what partitions did you back up and what partitions are you restoring?

Heisenberg said:
Have you tried flashing the MDB08M vendor image after flashing the ROM?
Click to expand...
Click to collapse
I would say no, since the only thing I flashed as the ROM. Should this be done before or after flashing the downloaded ROMs? I'm not sure where to get/which vendor image I should use either.
Heisenberg said:
Are you wiping properly (system, data, cache, dalvik cache)?
Click to expand...
Click to collapse
Here's what I did.
Complete format and wipe device
install google stock picking option 9 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Wipe dalvik and cache
Boot into android, enable dev options
Boot to fast boot
install TWRP using option 6 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Root using option 4 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Reboot to OS to check for root
make nandroid in TWRP
install custom ROM in TWRP
Wipe dalvik and cache
Reboot
After the reboot is where it gets stuck on those pop-upis. I've tried several different ROMs starting at step 1 each time and get the same result
Heisenberg said:
In regards to your nandroid backup, what partitions did you back up and what partitions are you restoring?
Click to expand...
Click to collapse
I don't remember. I think I checked all the boxes available when backing up and restoring the whole nandroid of whatever was backed up.

csh8428 said:
I would say no, since the only thing I flashed as the ROM. Should this be done before or after flashing the downloaded ROMs? I'm not sure where to get/which vendor image I should use either.
Here's what I did.
Complete format and wipe device
install google stock picking option 9 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Wipe dalvik and cache
Boot into android, enable dev options
Boot to fast boot
install TWRP using option 6 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Root using option 4 from [TOOL] SKIPSOFT ANDROID TOOLKIT - NEXUS 6P
Reboot to OS to check for root
make nandroid in TWRP
install custom ROM in TWRP
Wipe dalvik and cache
Reboot
After the reboot is where it gets stuck on those pop-upis. I've tried several different ROMs starting at step 1 each time and get the same result
I don't remember. I think I checked all the boxes available when backing up and restoring the whole nandroid of whatever was backed up.
Click to expand...
Click to collapse
Ok, it looks like you didn't wipe (system, data, cache, dalvik cache) before installing the ROM, so there's one problem. Also, when creating your backup you don't need to check all options, only system, data, and boot. You flash the stock vendor after flashing the ROM. I'd recommend you take a look at my guide, it should clear a few things up:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You'll also find a recovery flashable version of the vendor image in my index thread under the stock firmware section:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583

I was getting the same error, but it didn't seem to affect he devices functions in any way.
Anyways I flashed the new vendor image since i installed a MMB29P ROM and didn't update it before.
Without wiping it did nothing the error was still there.
Then I wiped everything and started with vendor image, then the ROM, the kernel and SU.
NO ERROR.

Samsung Galaxy S7 bootloop

I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)

k1ng0fqu33n5 said:
I tried to root my phone using odin to flash TWRP. Through that i installed SuperSU and rebooted the phone. Now it is stuck in a bootloop. What went wrong?
btw i can't wipe dalvik cache via the advanced wipe (it says invalid partition)
Click to expand...
Click to collapse
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.

TheSproker said:
First of all, boot into download mode, then install your stock firmware via odin to get out of the bootloop. Then use chainfire's autoroot to get root, then with flashify install twrp.img and you should be good to go.
Click to expand...
Click to collapse
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.

k1ng0fqu33n5 said:
Thanks. Though i hoped there was another method cause as far as i know installing stock firmware wipes the device and i didn't make a backup beforehand.
Click to expand...
Click to collapse
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)

TheSproker said:
Yep, the most important thing is to always make a backup. Because without that, the only way is re-installing the stock firmware. And when you have installed twrp, be sure to format data, so that twrp could decrypt and access your internal storage (that's why you were not able to wipe cache)
Click to expand...
Click to collapse
If i do a factory reset with TWRP, will it wipe any of the internal data? (pictures, messages etc.)
because the factory reset screen says that it's not included:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, i just tried a factory reset and that fails too. Unable to mount /data.

k1ng0fqu33n5 said:
Well, i just tried a factory reset and that fails too. Unable to mount /data.
Click to expand...
Click to collapse
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?

EasyAndroidPro said:
There is a guide you should have followed here if you have exynos s7e
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Did you flash this file ?
Click to expand...
Click to collapse
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.

k1ng0fqu33n5 said:
That's the guide i have been using to root, yes. And yes, i flashed that file along with SuperSU.
Click to expand...
Click to collapse
I see.. if that file did not fix the bootlooping then I'm afraid the only fix is like the previous poster said
Either flash stock again with Odin
Or format data in twrp

Ok, i somehow made it so the phone booted up and initialized. Now i got the problem that the google play store keeps crashing.
Edit: I also can't download my whatsapp backup data (says insufficient storage, which is not the case)

I also can't download files with the chrome browser (it says no sd-card found). If i use the stock samsung browser it works though.

[GUIDE] Twrp Remove decryption password Xperia XZ

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide is for your twrp to recognize your internal memory and the available memory that is in it since we all face this problem that presents twrp in internal storage.
Warning: This procedure will erase all the data of your device such as google accounts, messages, root, that is to say it will remain factory mode, so you will need to reconfigure the device, I add images of the steps so that it is as comprehensible as possible to understand.
When you install twrp and start it for the first time we will get the following information we just need to confirm the action Swipe to Allow Modifications.
So we visualize the following menu with the options offered by twrp, we will only focus on the option Wipe.
We choose the option Advanced Wipe.
Check the Data box and we choose the option Repair or Change File System
We choose the option Change File System
We choose the option EXT4
We choose the option Swipe to Change, When confirming the action your device will erase all your data stored in the internal storage
Twrp will recognize your internal storage and capacity
Warning: You must re-flash Drm-fix.zip. magisk.zip to be root on your device

Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.

omaison said:
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
Click to expand...
Click to collapse
No you have do it again after fresh installation

Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.

omaison said:
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
Click to expand...
Click to collapse
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.

awadnisar said:
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
Click to expand...
Click to collapse
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]

omaison said:
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
Click to expand...
Click to collapse
Means updating OmniROM is wiping data partition?

awadnisar said:
Means updating OmniROM is wiping data partition?
Click to expand...
Click to collapse
Not automatically. But it seems that I don't have the choice to format it manually to have the possibility to flash the new version of the ROM.
Otherwise TWRP generate an error with saying that the data partition is encrypted.
I will try again on the next week when the new version of the OmniIROM is released.

redundant

TWRP : Bootloop after restoring SYSTEM on A205F

I was debloating my phone and some deleted wrong file in the system. And now when I restored System using Skyhawk TWRP Recovery my phone got stuck into a bootloop. I had to flash the ROM again and got all the bloatware back.
Is there any way to get this fixed? None of the tutorials have helped me so far.

Hello, Have you seen this?
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com

Buckythereporter said:
I was debloating my phone and some deleted wrong file in the system. And now when I restored System using Skyhawk TWRP Recovery my phone got stuck into a bootloop. I had to flash the ROM again and got all the bloatware back.
Is there any way to get this fixed? None of the tutorials have helped me so far.
Click to expand...
Click to collapse
Use TWRP / OrangeFox in the future. I recommended TWRP but I use OrangeFox because of password protection feature.

sercari said:
Hello, Have you seen this?
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
Click to expand...
Click to collapse
I have everything working right now. But the phone goes into a bootloop if I restore the System. I used to just flash the rom again if something goes wrong. This was the first time I tried to restore a system backup.
Recovering Data partition works properly tho.

KineSight said:
Use TWRP / OrangeFox in the future. I recommended TWRP but I use OrangeFox because of password protection feature.
Click to expand...
Click to collapse
Does the backup and restore feature work for you? Do I need to flash something else to restore the System?

Buckythereporter said:
Does the backup and restore feature work for you? Do I need to flash something else to restore the System?
Click to expand...
Click to collapse
Yes. Backup's and Restore's work perfectly for me. I highly doubt either one can restore the other's backup data. (Yes, OF is based on TWRP.)

KineSight said:
Yes. Backup's and Restore's work perfectly for me. I highly doubt either one can restore the other's backup data. (Yes, OF is based on TWRP.)
Click to expand...
Click to collapse
So no one fixed this even in modded recoveries. Maybe they didn't face any issue and it's only my phone.

Just found this guide here, trying this.
Backup and Restore - a Hybrid Method (Android 9) | XDA Developers Forums (xda-developers.com)

restoring system.img is not recommend since it might trigger dm-verity. they say it better to flash the full stock rom

ineedroot69 said:
restoring system.img is not recommend since it might trigger dm-verity. they say it better to flash the full stock rom
Click to expand...
Click to collapse
Doesn't flashing a GSI do the same?

Buckythereporter said:
Doesn't flashing a GSI do the same?
Click to expand...
Click to collapse
here's the list of partition that is supposed to be dm-verity protected https://source.android.com/security/verifiedboot
"to the bootloader, to the boot partition and other verified partitions including system, vendor, and optionally oem partitions"
my phone has already dm-verity trigger i don't see much difference except i need to deal with 2 boot animation on start lmao
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ineedroot69 said:
here's the list of partition that is supposed to be dm-verity protected https://source.android.com/security/verifiedboot
"to the bootloader, to the boot partition and other verified partitions including system, vendor, and optionally oem partitions"
my phone has already dm-verity trigger i don't see much difference except i need to deal with 2 boot animation on start lmao
Click to expand...
Click to collapse
Seems like there's no permanent solution for this. Buying Mi next time.

Buckythereporter said:
Seems like there's no permanent solution for this. Buying Mi next time.
Click to expand...
Click to collapse
if you can start twrp get dmesg.log upload that file see if we can help you.