Develop Bugs

[Q] Now CM 10, 4.1.2 going to 4.2.2. How easy to go back?

I've been running CM 10, 4.1.2, on Verizon gn. Works fine.
But I can't leave well enough alone, and want to try 4.2.2.
That should be easy right, just flash the recent CM 10.1. No cache wiping. Right?
But if I do that and I don't like it. how do I go back? Is it as simple as just flashing CM 10?
Also, I have Ti backup. The backup folder is sdcard/TitaniumBackup. I've read that 4.2.2 creates /sdcard/0/ for data. Does this mean that my present backup will be deleted?
Any help appreciated.

Since you are migrating Android versions, I would recommend that you do a full wipe, so system, data, and cache (and restore apps from TiBu if you must). You can do a nandroid backup from recovery; if you don't like 4.2 just restore it. When restoring a nandroid backup everything will be exactly the same.

seandarcy said:
Also, I have Ti backup. The backup folder is sdcard/TitaniumBackup. I've read that 4.2.2 creates /sdcard/0/ for data. Does this mean that my present backup will be deleted?
Click to expand...
Click to collapse
I just upgraded from 4.1.2 to 4.2.2 and had the same concern about being able to go back if I had problems and knowing that the partitioning of internal storage would be changed.
I recently got my GN back from Samsung after getting the screen replaced. Before sending it off, I totally wiped and reset the phone to stock. I made sure I did a full Ti backup first, then a Nandroid backup, and finally copied the entire contents of internal storage via "adb pull" to my desktop computer. When I got the phone back, I reversed the process and was able to restore the phone entirely to where it was before the wipe.
I did the same operation before upgrading to 4.2.2, without wiping the phone. So if I'd have wanted to go back to 4.1.2, I'd have wiped the phone, including internal storage, and restored as described above. I'm pretty confident that this would have removed the new partitioning from 4.2.2 and reset it to where it was before the 4.2.2 upgrade.

Sorry to be dense, but...
So I do a nandroid backup from TWRP 2.4.4.0, system, data and cache
From TWRP flash the CM 4.2.2.
Do nandroid restore from TWRP?
Flash gapps, restore apps from TiBu.
Now if want to go back to 4.1.2:
Flash 4.1.2, wipe system data cache.
Flash gapps, restore apps from TiBu
Do I have this correct?

Nandroid the entire thing from TWRP, wipe system, data and cache from TWRP, flash CM10.1 and gapps from TWRP, restore apps from TiBu in ROM. If you don't like it just restore the nandroid from TWRP. TiBu only restores apps, nandroid restores everything: ROM, account, system settings, apps, etc.

The only extra thing I referred to was making a full copy of your phone's internal storage to your computer using "adb pull". This would allow you to wipe the internal storage and restore it, in case the partitioning change from "/storage/sdcard0" to "/storage/emulated/0" needed to be removed. But if TWRP's nandroid backup and restore takes care of this, this step isn't necessary.

How easy? Dead easy.
Sent from my Nexus

TWRP - is DATA backup necessary?

Hi,
So the official 4.3 ROM UEMK8 was released today for my Note 2 n7100.
I'm currently running UEMK4 4.3, so I thought of backing up everything through TWRP before backing up, as the file I used to flash Odin with (the leaked 4.3) is no longer available as I deleted it by mistake.
so as I'm backing up, everything works but DATA gives me error tarring split files.
so is DATA backup necessary? can't I simply just install the K8 ROM , then if something fails I just wipe my data/cache then restore System and Boot? as I don't need the DATA inside, unless DATA is part of the OS and I MUST have it.
thanks

No one replied.
Conclusion:
No, just perform full wipe.

[Q] Unable to restore Nandroid backup

I took a Nandroid backup of my stock phone (all partitions) before I flashed a new ROM (DN3). Then I decided to return to stock ROM, so I wiped phone and restored Nandroid backup (all partitions except bootloader and recovery).
Now the phone will not boot, it just shows a logo and then a black screen. I can connect to it via ADB however.
I thought Nandroid backup was a safe way of preserving phone, but it seems it cannot actually be trusted?

number_thirty_two said:
I took a Nandroid backup of my stock phone (all partitions) before I flashed a new ROM (DN3). Then I decided to return to stock ROM, so I wiped phone and restored Nandroid backup (all partitions except bootloader and recovery).
Now the phone will not boot, it just shows a logo and then a black screen. I can connect to it via ADB however.
I thought Nandroid backup was a safe way of preserving phone, but it seems it cannot actually be trusted?
Click to expand...
Click to collapse
depends on bootloader i guess, but maybe try wipe data and preload / cache and dalvik and reflash, make sure ROM to flash is on external sdcard as may lose all data on phone

Having the same issue after re-partitioning my phone. My nandroid backup is about 2.3gb and it took about 200 seconds to restore. Nothing was actually restored when I booted up. (This nandroid was made to my SD-Card, wonder if that makes any difference.
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!

I took a TWRP nandroid, now android loads then reboots itself

Every time I take a nandroid backup in TWRP and boot the phone up, I seem to get boot loops.
Yesterday
------------------
I was running HTC's factory 4.4.2 firmware that came with my phone when I bought it. It was rooted and I was using XPosed. I wanted to upgrade to 4.4.3 via OTA, but I wanted a roll-back method. So I took a nandroid, all is well.
I flash stock recovery and take the OTA. All is well. I re-root, install xposed, tinker with some modules and then the phone reboots itself.
I did the upgrade from 4.4.2 to 4.4.3 again after restoring my nandroid backup. All is well. I decide not to tamper with root stuff, but the su binary has been flashed. I restored a majority of my apps and app data by using titanium backup to load application data from my TWRP backup. Everything is STILL fine.
Today
------------------
My TWRP backup of 4.4.2 was at work so I had to wait until I got back to move the backup back onto my phone. So here I am. I decide to do the following:
1. I shut my perfectly working 4.4.3 ROM down so I can take a nandroid before I load the 4.4.2 nandroid and try another fresh update
2. I make the nandroid backup and boot the OS back up so I can copy the TWRP folder over to my computer
3. Phone boot loops again.
What is causing this? I've tried a bunch of things like fixing permissions from TWRP, clearing the dalvik and cache. I tried sending "adb logcat" to a file on my computer to examine the output but nothing sticks out before it reboots.
Only fix I know is to factory reset and start the long process all over again.
M8_UL
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
Carrier: Wind Mobile (Canada)

Have you tried fastboot erase cache, and flash TWRP again?

No I have not. Once I try that, what point will I be at? Will I be able to boot into my OS or will I need to restore my backup again?
What does fastboot erase cache do? Is it the same cache I can clear from TWRP?
One thing I just remembered... I'm using TWRP 2.7.1.0, where prior to upgrading I was using TWRP 2.7.0.2 from Hasoon2000's toolkit. Not sure if this matters or not yet.

ninjai117 said:
No I have not. Once I try that, what point will I be at? Will I be able to boot into my OS or will I need to restore my backup again?
Click to expand...
Click to collapse
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.

redpoint73 said:
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
Click to expand...
Click to collapse
OK well I reverted back to my nandroid I created with my previous version of TWRP, and did the OTA again. Have not bothered to root or create further nandroids. So far everything is great. Just wish I could create a nandroid without the thing going crazy on me.

ninjai117 said:
Just wish I could create a nandroid without the thing going crazy on me.
Click to expand...
Click to collapse
I haven't had this happen to me. Only issue with TWRP for me so far on this device, is a backup failed to restore on an earlier TWRP version (so I had to flash a ROM and setup again) and I haven't had this issue on more recent TWRP versions.
Again, I'd suggest downloading TWRP again, and doing a fresh install of it and see if the problem persists. Or try CWM.

redpoint73 said:
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
Click to expand...
Click to collapse
redpoint73 said:
I haven't had this happen to me. Only issue with TWRP for me so far on this device, is a backup failed to restore on an earlier TWRP version (so I had to flash a ROM and setup again) and I haven't had this issue on more recent TWRP versions.
Again, I'd suggest downloading TWRP again, and doing a fresh install of it and see if the problem persists. Or try CWM.
Click to expand...
Click to collapse
I instead flashed TWRP from Hasoon2000's HTC M8 All In One Kit, which is what I previously had and created my 4.4.2 nandroid with. Every time after that I was using the latest version from TWRP's website. I suspect that is the culprit, but I have no evidence yet as I have not created a nandroid again. I'm currently on 4.4.3 with SuperSU.zip flashed. No problems yet.

ninjai117 said:
Every time after that I was using the latest version from TWRP's website. I suspect that is the culprit, but I have no evidence yet as I have not created a nandroid again.
Click to expand...
Click to collapse
I always get TWRP from their website.

TWRP Restore Issue

Hi guys,
I seem to have this problem where my nandroid backup from TWRP won't boot. I can only get it to boot after flashing the Rom over again after the store (this doesn't erase the data and all my file are still there, I just have to make sure I'm flashing the same Rom version as was part of the backup to avoid issues . But I was wondering if there is something else I should be doing here. I've used TWRP in the past and was just able to back up and restore no problem.
When I back up I make sure my system partition is mounted and I usually backup the default selections (boot/data/system, EFS) . My feeling is somehow the boot partition gets corrupted and won't allow the phone to continue booting, but I'm not sure why?
Any ideas? I'm using TWRP version 3.0.2-0. This happens when restoring nandroid for any rom (so far tried with oxygen/hydrogen/miui and cm14).
Thanks in advance.

I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?

borijess said:
I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?
Click to expand...
Click to collapse
Standard factory reset on TWRP will erase data, cache and Calvin cache without wiping internal SD card. That's what most people use.

piotrus22 said:
Hi guys,
I seem to have this problem where my nandroid backup from TWRP won't boot. I can only get it to boot after flashing the Rom over again after the store (this doesn't erase the data and all my file are still there, I just have to make sure I'm flashing the same Rom version as was part of the backup to avoid issues . But I was wondering if there is something else I should be doing here. I've used TWRP in the past and was just able to back up and restore no problem.
When I back up I make sure my system partition is mounted and I usually backup the default selections (boot/data/system, EFS) . My feeling is somehow the boot partition gets corrupted and won't allow the phone to continue booting, but I'm not sure why?
Any ideas? I'm using TWRP version 3.0.2-0. This happens when restoring nandroid for any rom (so far tried with oxygen/hydrogen/miui and cm14).
Thanks in advance.
Click to expand...
Click to collapse
I don't have any solution for you but I can certainly concur. I've seen this behaviour as well but not as consistently as what you are describing. About 1/3rd of the time my restores don't work as you mentioned and I have to dirty flash the rom to get it to boot. Sometimes the restore even errors out while restoring the System partition in which case I just dirty flash. This is like my 9th or so Android device since Samsung released the SGS1 in whatever year that was and this is the first phone I've ever had this problem with. On previous phones it would happen rarely but nothing like it does on the OP3.
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
borijess said:
I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?
Click to expand...
Click to collapse
You can either not wipe internal storage (that is what I do usually) or you can buy an OTG adapter. I think TWRP supports it for our device. You can always copy off your backups via USB then wipe internal then copy your backups back too I think.

Did you for once try wiping the complete device after backing up nans on external storage and thn trying restoring? That would make a difference

Dr-Hack said:
Did you for once try wiping the complete device after backing up nans on external storage and thn trying restoring? That would make a difference
Click to expand...
Click to collapse
What?

piotrus22 said:
What?
Click to expand...
Click to collapse
I think he is asking to do below procedure -
1.Copy your nandroid backup and other imp stuff to computer
2.boot into TWRP
3.wipe all partitions including internal storage
4.copy nandroid backup to phone
5.restore backup through TWRP

Did you mount system to restore backup?

null0seven said:
Did you mount system to restore backup?
Click to expand...
Click to collapse
Yep of course.

JumboMan said:
I think he is asking to do below procedure -
1.Copy your nandroid backup and other imp stuff to computer
2.boot into TWRP
3.wipe all partitions including internal storage
4.copy nandroid backup to phone
5.restore backup through TWRP
Click to expand...
Click to collapse
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?

piotrus22 said:
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?
Click to expand...
Click to collapse
its one time procedure. Subsequent restore will be fine.
May be different versions of TWRP will help you with this problem

is this issue had been resolved? because i have also the same problem.. whats the fix for this?

piotrus22 said:
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?
Click to expand...
Click to collapse
How did you fix your problem? I cant restore my backup also..
it says restore complete but stock in boot logo after... any fix?

toto_vanir said:
How did you fix your problem? I cant restore my backup also..
it says restore complete but stock in boot logo after... any fix?
Click to expand...
Click to collapse
Hey man. No I never fixed it. Just flash your Rom over it and it should boot fine.