[Q] Noobish Doubt Regarding TWRP backup ! - Nexus 4 Q&A, Help & Troubleshooting

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:

Related

[Q] [SmoothROM v5.2] Does A Nandroid Backup Contain The Kernel?

If I make a nandroid backup of SmoothROM with the Franco kernel, is it possible to reinstall SmoothROM, choose a new kernel (Motley), and then go back into Recovery and restore the nandroid backup? Will this result in a SmoothROM install with the Motley kernel or will the backup restore the Franco kernel as well? Using TWRP v2.5.0.0 to create the nandroid backup with all boxes checked (System, Cache, Data, Boot, Recovery). Any help is greatly appreciated!! :fingers-crossed:
You can't restore irom backup if you change kernel. You backed up for sustem, data etc. but not for kernel. You need to flash new kernel if you want to change
Sent from my SPH-D710 using xda premium
{
"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"
}
The boot option is the kernel. When I restored my backup, it also restored the stock kernel I was using when I made it.
Username invalid said:
The boot option is the kernel. When I restored my backup, it also restored the stock kernel I was using when I made it.
Click to expand...
Click to collapse
If I make a nandroid backup without the Boot checkbox checked, would that still be a perfect mirror image? Can I just flash a new kernel on top of a SmoothROM install? Like restore the nandroid backup, then hop into TWRP and flash (Install) a new kernel? SmoothROM is the first custom ROM I've used and it allows you to choose one at boot. I'm not familiar with selecting a kernel for a custom ROM otherwise.
Mulsiphix said:
If I make a nandroid backup without the Boot checkbox checked, would that still be a perfect mirror image? Can I just flash a new kernel on top of a SmoothROM install? Like restore the nandroid backup, then hop into TWRP and flash (Install) a new kernel? SmoothROM is the first custom ROM I've used and it allows you to choose one at boot. I'm not familiar with selecting a kernel for a custom ROM otherwise.
Click to expand...
Click to collapse
Yes, it will make a clone of the ROM that you can restore over the new kernel. I have installed SmoothROM a few times and it did not install the included kernel over the one I was using at the time.
---------- Post added at 10:25 PM ---------- Previous post was at 10:21 PM ----------
This seems like an odd method just to change to a new kernel. Installing a new kernel literally takes 2 seconds to flash.
Username invalid said:
This seems like an odd method just to change to a new kernel. Installing a new kernel literally takes 2 seconds to flash.
Click to expand...
Click to collapse
Thank you! It is more confusion on my part than deliberate intention

[Q] Root newbie, can you change between roms?

Hi i am looking to root for the 1st time i have seen how to do it, i have already unlocked bootloader for updating reasons.
My question is if i put a rom on for instance JellyBAM can i if i choose to switch between that and the stock android or would i have to re install the stock android.
I enjoy the features of the stock android on my nexus 7 (2013) but am looking to just tweak it a little but i dont want to put the factory image back on if i dont like JellyBAM as it will wipe my device again.
Thanks for any help
Joe
http://www.indiegogo.com/projects/multirom-for-nexus-7-2013
Flashing a new ROM would only overwrite your current system, system data and cache. Your internal storage where your files, pictures, videos, etc are would be intact.
Username invalid said:
http://www.indiegogo.com/projects/multirom-for-nexus-7-2013
Flashing a new ROM would only overwrite your current system, system data and cache. Your internal storage where your files, pictures, videos, etc are would be intact.
Click to expand...
Click to collapse
thanks for the reply and answer
to get the stock android system back do you remove the rom you have flashed or do you just flash the stock rom back on?
Thanks for any help again
Also if you flash the stock rom back on where can i download the rom from?
joeyt90 said:
thanks for the reply and answer
to get the stock android system back do you remove the rom you have flashed or do you just flash the stock rom back on?
Thanks for any help again
Also if you flash the stock rom back on where can i download the rom from?
Click to expand...
Click to collapse
The custom recovery automatically wipes the old ROM when you flash a new one.
Stock ROM - https://developers.google.com/android/nexus/images
Username invalid said:
The custom recovery automatically wipes the old ROM when you flash a new one.
Stock ROM - https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
If i flashed a stock rom would it wipe my tablet to new?
I recently had to fastboot the new android os 4.3 (jss15q) and would that be the same way to get it back on after flashing a custom rom? using flash-all.bat?
Thanks for the great help so far!!
joeyt90 said:
If i flashed a stock rom would it wipe my tablet to new?
I recently had to fastboot the new android os 4.3 (jss15q) and would that be the same way to get it back on after flashing a custom rom? using flash-all.bat?
Thanks for the great help so far!!
Click to expand...
Click to collapse
If just flashed the stock ROM images (system, userdata, cache), your internal storage, custom recovery and kernel would remain.
Username invalid said:
If just flashed the stock ROM images (system, userdata, cache), your internal storage, custom recovery and kernel would remain.
Click to expand...
Click to collapse
I think i am starting to undertand it all now, so using flash-bat.all just uploads the rom its the unlocking of the bootloader that wipes your memory (which i have already done)
now for a personal opinion what is a good rom to start with for someone who wants to learn but not get chucked in at the deep end (in terms of the changes you can do to the device not the flashing which i know makes no difference which rom you put on its always the same method)
Thanks
joeyt90 said:
I think i am starting to undertand it all now, so using flash-bat.all just uploads the rom its the unlocking of the bootloader that wipes your memory (which i have already done)
now for a personal opinion what is a good rom to start with for someone who wants to learn but not get chucked in at the deep end (in terms of the changes you can do to the device not the flashing which i know makes no difference which rom you put on its always the same method)
Thanks
Click to expand...
Click to collapse
When you first unlocked the bootloader, it wiped the userdata, cache and internal storage. Flash a new ROM in the recovery replaces the stock system, userdata and cache without wiping your internal storage. You can start off with Minimus or CleanROM which is the closest to stock with minimal changes.
Username invalid said:
When you first unlocked the bootloader, it wiped the userdata, cache and internal storage. Flash a new ROM in the recovery replaces the stock system, userdata and cache without wiping your internal storage. You can start off with Minimus or CleanROM which is the closest to stock with minimal changes.
Click to expand...
Click to collapse
Thanks again i have flashed cleanROM and its worked great, but now that i have rooted and installed the rom can i delete the files of my nexus 7 internal storage?
Thanks
Joe
joeyt90 said:
Thanks again i have flashed cleanROM and its worked great, but now that i have rooted and installed the rom can i delete the files of my nexus 7 internal storage?
Thanks
Joe
Click to expand...
Click to collapse
Yes, you can wipe your internal storage or format your device in the recovery which would accomplish the same thing.
{
"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"
}
Username invalid said:
Yes, you can wipe your internal storage or format your device in the recovery which would accomplish the same thing.
Click to expand...
Click to collapse
worked a treat although i now cannot stop changing things
Thanks

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.

I can't back up after restoring a backup- please help

Hello all,
I recently bought a brand-new ZE552KL and have since unlocked the bootloader, flashed TWRP 3.2.1, flashed ViperOS 7.1.2, flashed Magisk 15.3, flashed Xposed v89r5-v90b2, and made several backups. However, each time I restore one, I lose all progress in the most evil manner I've encountered to date: Any time I try to back up my install after restoring from a backup, it fails, claiming my system partition is only 7MB in size.
Now, at first I thought this was simply a bug in the latest TWRP- 3.2.1 is so new, after all- so I flashed back to 3.1.1, reflashed ROM/GApps, went through first boot, and began making backups as normal. Only, when I tested one of them by restoring, booting to system, changing things, booting back into recovery, and attempting to back up, well, you guessed it... 7MB system partition. I have no idea what's causing this, but it kinda invalidates the point of having backups in the first place. Any help would be appreciated.
Hi, i never find a solution for backup / restore with TWRP. Always doing all from begining.
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Sorry for the late reply. It's been a rough, long day at work.
I have no issues restoring either. As I mentioned in my post, the trouble comes from trying to back up what I've restored- say, restoring at a previous point and changing things from how I'd previously set it up. As soon as I try to back up a restored system, it tells me my system partition is only 7MB in size.
However, to answer your question, no, I back up everything. I always have, ever since I first got TWRP on my Motorola Xoom. (CWM on that thing was just awful.) Is there some reason a full backup is wrong on this device?
auroraPLG said:
Sorry for the late reply. It's been a rough, long day at work.
I have no issues restoring either. As I mentioned in my post, the trouble comes from trying to back up what I've restored- say, restoring at a previous point and changing things from how I'd previously set it up. As soon as I try to back up a restored system, it tells me my system partition is only 7MB in size.
However, to answer your question, no, I back up everything. I always have, ever since I first got TWRP on my Motorola Xoom. (CWM on that thing was just awful.) Is there some reason a full backup is wrong on this device?
Click to expand...
Click to collapse
Try to flash twrp 3.1.1 (20171023) from here https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA
[email protected]@ said:
Try to flash twrp 3.1.1 (20171023) from here
Click to expand...
Click to collapse
Okay, got it downloaded. Wish me luck.
EDIT: Old TWRP flashed and backup made. Gonna bite the bullet.
EDIT 2: So... now an error restoring. First time for everything, eh? (Not saying I've never had a failed restore, just not with this device- until now, of course....)
Code:
Restoring Data (excl. storage)...
extractTarFork() process ended with ERROR: 255
Gonna reflash 3.2.1 for now just to get a system running. Any ideas for in the meantime?
auroraPLG said:
Okay, got it downloaded. Wish me luck.
EDIT: Old TWRP flashed and backup made. Gonna bite the bullet.
EDIT 2: So... now an error restoring. First time for everything, eh? (Not saying I've never had a failed restore, just not with this device- until now, of course....)
Gonna reflash 3.2.1 for now just to get a system running. Any ideas for in the meantime?
Click to expand...
Click to collapse
1. Old twrp make your device bootloop?
2. The data you backup is from nougat stock and you want to restore it in viperos?
[email protected]@ said:
1. Old twrp make your device bootloop?
2. The data you backup is from nougat stock and you want to restore it in viperos?
Click to expand...
Click to collapse
1. No. No bootloop. I don't understand where you got this idea. As I said, old TWRP failed to restore Data. However, I'm pretty sure it was the Data partitions in my latest backups, due to making files immutable- not the recovery itself.
2. No, I want to restore ViperOS.
wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Hi, this is the right configuration for a backup ?
Please confirm me
{
"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"
}
Picture from howtogeek.com
@dekson9
Yes, that is the correct. System partition is the OS, and the data partition is your apps and config data.
So, when you make a backup, can you confirm the size of the backup files, should be something like system.ext4.win000, 001, 002.
Maybe try unmounting and remounting the system partition while in twrp before the restore? You can toggle the button at the bottom right (4 horizontal lines) to see if there were any errors.
wang1chung said:
I don't have any issues restoring, are you following the procedure as outlined in this twrp backup guide?
Click to expand...
Click to collapse
Well, I tried it your way. Not gonna lie, I don't understand why a full backup would cause that problem. But it turns out you're right. I've gotten that kink worked out thanks to you. Now if I could just fix the hardware clock... but that's another adventure for another party, I'm sure. I'm off to press that thanks button.
@auroraPLG
Glad you got it sorted, happy flashing!
@wang1chung
Thank you! I think I'm gonna play around with backups and pull logs and see if I can't figure out what causes this particular bug.

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.

Categories

Resources