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
Related
Hi, I don't exactly know since when it's showing wrong, but I believe it has to do something with my latest "activities".
First here my storage of my 16 GB N4 device:
{
"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"
}
Okay, I decided to fully wipe my device and go back to stock 4.2.2 before flashing latest AOKP PUB rom.
Therefore I went into fastboot and used following commands to erase old data
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase system
fastboot erase recovery
Then I started with stock factory image 4.2.2 (JDQ39)
Flashed userdata, boot, system and a customrecovery (TWRP 2.4.2.0)
Rebooted phone, downloaded supersu 1.10 zip, AOKP PUB rom, and Trinity Kernel (TF107)
Booted into recovery --> wiped cache/dalvik cache --> factory reset --> flashed AOKP and TF107 --> rebooted --> set up wifi etc
Booted into recovery --> flashed supersu --> rebooted installed busybox --> rebooted into recovery and fixed permissions.
Now I was starting to set up everything like my apps etc. until I noticed my storage is too small.
What is the problem and what can I do to get my storage back?
The only unusal thing which I never did before, was the erasing stuff, could this be the problem?
Thanks!
Hi,
I think you should take a look here: [url=" http://forum.xda-developers.com/showthread.php?p=35119185'' ]
[HOW-TO] Fix internal storage if 16GB now shows 8GB[/url]
Restart from scratch... Weird it's what you done apparently...
viking37 said:
Hi,
I think you should take a look here:
[HOW-TO] Fix internal storage if 16GB now shows 8GB
Restart from scratch... Weird it's what you done apparently...
Click to expand...
Click to collapse
okay thanks, started from scratch again and with all stock it's working now.
I'll try to flash my custom recovery, rom and kernel again and hopefully it works this time.
laba86 said:
okay thanks, started from scratch again and with all stock it's working now.
I'll try to flash my custom recovery, rom and kernel again and hopefully it works this time.
Click to expand...
Click to collapse
Same thing happened to me. A total pain in the ass...
Sent from my Nexus 4 using xda premium
All I did was back up my sdcard, boot into recovery, format the sdcard, then copy everything back on to it.
Worked for me.
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:
Hi,
Today I was trying to root my Nexus 10 (android 4.4.2), following this tutorial I had found earlier: au.ibtimes.com/articles/530367/20131216/root-android-4-2-kot49h-kitkat-install (add .htm, can't post urls yet).
Everything went fine until I tried to backup my system to the SD card with CWM. In CWM I got the message that several points in the filesystem could not be mounted. Not knowing how to proceed, I tried to reboot - since then I am stuck in a loop and would like to at least be able to boot into my stock rom again. Googling around for a while, I found several posts suggesting a factory reset might do the trick, however, since CWM is unable to mount anything, I can't perform such a reset. I tried wiping cache and all that, did not work.
Then I flashed TWRP (2.6.3.1 for nexus 10) using the fastboot flash recovery command. Again, I tried to perform a factory reset, which fails (the log just says
updating partition details...
Formatting Cache using make_ext4fs function.
So, I don't quite know what to do. Could anyone tell me how to best proceed? How can I get the Nexus 10 to boot again?
Thanks in advance!
EDIT: Ok, just fixed it by flashing the re-flashing the stock rom from the google page. So, how do I root the device now without running into the same troubles once again?
Wugfresh nexus root toolkit has always worked for me:
http://www.wugfresh.com/nrt/
tjupille said:
Wugfresh nexus root toolkit has always worked for me:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
+1 safe and easy
Thanks, that worked great!
Seems that same issue happened to me, but even after restoring Factory Image and re-flashing custom recovery I still have this problem:
{
"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"
}
Tried also on TWRP with no luck..any suggestions?
Inviato dal mio LG-D802 utilizzando Tapatalk
AleCai said:
Seems that same issue happened to me, but even after restoring Factory Image and re-flashing custom recovery I still have this problem:
Tried also on TWRP with no luck..any suggestions?
Inviato dal mio LG-D802 utilizzando Tapatalk
Click to expand...
Click to collapse
Hi,
I will suggest you to try formatting cache again, as it is the problem there. If it doesn't work, and you don't mind refashing the stock rom, then I'd like to ask you trying wiping every partition and install the after this.
I had a similar issue with Xoom, I needed to reboot several times in recovery and after some many times it finally mounted system (I had a bootloop) and I formatted it.
Good luck,
~Lord
"This Story Ends Where It Began"
Sent from my monstrous Xperia Z1
Hey everyone,
So I have been using Oreo beta B12 on my A2017U for a few weeks and wanted to check out Lineage and after having some qualms about Oreo and stability, decided to go for Lineage 14.1.
Using TWRP I wiped (standard wipe) and flashed the bootloader, modem, lineage, gapps, and Magisk. In that order. Upon finish and reboot it tells me, Decryption unsuccessful, I must reset my phone. But when it goes to wipe it fails, i see the following:
{
"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"
}
It seems to be stuck like this, and I don't know what to do to proceed. I could try some things, but I don't want it to get worse because I wiped something crucial.
Thanks in advance.
Tre916 said:
Hey everyone,
So I have been using Oreo beta B12 on my A2017U for a few weeks and wanted to check out Lineage and after having some qualms about Oreo and stability, decided to go for Lineage 14.1.
Using TWRP I wiped (standard wipe) and flashed the bootloader, modem, lineage, gapps, and Magisk. In that order. Upon finish and reboot it tells me, Decryption unsuccessful, I must reset my phone. But when it goes to wipe it fails, i see the following:
It seems to be stuck like this, and I don't know what to do to proceed. I could try some things, but I don't want it to get worse because I wiped something crucial.
Thanks in advance.
Click to expand...
Click to collapse
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
atakan33 said:
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
Click to expand...
Click to collapse
Thanks, that worked. I appreciate your help!
atakan33 said:
Flash B12 Beta again and flash 3.2.1-8 and decrypt data (format data )with 3.2.1-8 and flash LOS14.1( bootloader.modem,los,twrp 3.2.2-0 ) you must install twrp before reboot system.
Click to expand...
Click to collapse
So, would you mind explaining what actually went wrong? Did I just fail to decrypt/format the data before imaging? Should I just be sure to format /data every time I flash a new rom?
Tre916 said:
So, would you mind explaining what actually went wrong? Did I just fail to decrypt/format the data before imaging? Should I just be sure to format /data every time I flash a new rom?
Click to expand...
Click to collapse
in oreo you must decrypt data with 3.2.1-8 thats it ( if you are encrypted )
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.