My N7000 stays stuck at the "Samsung Galaxy Note" screen when I try restarting after a restore using TiBu. This is the case with both CM 10.2 as well as Stock ROM. However, If I get into the recovery and wipe data and cache (Factory Reset) it boots back normally.
I am on the latest DBT German ROM with latest Philz Kernel in case of Stock.
In case of CM 10.2 there is no kernel or recovery change.
Any suggestions to fix this?
Maybe you'll tell us what you restored with TB first?
TB Back up order
ThaiDai said:
Maybe you'll tell us what you restore with TB first?
Click to expand...
Click to collapse
Step 1: Restoring the messages and call logs (XML Format)
Step 2: Followed by restore of User Apps and Data.
Step 3: Finally System Apps Data.
I have shuffled between CM and Stock several times in the past and have followed this order without issues.
Now, as soon as I restore User Apps and do a reboot, it gets stuck.
Step 3: not difficult to guess why this is your problem. Try without.
ThaiDai said:
Step 3: not difficult to guess why this is your problem. Try without.
Click to expand...
Click to collapse
Right now it is getting stuck after step 2 but before executing step 3. I was also aware that step 3 could be an issue so i let it stay minimal or rare.
Fixed
Can the Admins close the thread please? This has been fixed now.
Solution the way i closed the issue:
I did not perform the App restore. I downloaded the apps afresh and then did the data restore alone for the really necessary apps.
Never restore system apps. Don't even use TiBU to back up system apps. This causes conflicts within the OS and will cause a boot loop.
normaltusker said:
Step 1: Restoring the messages and call logs (XML Format)
Step 2: Followed by restore of User Apps and Data.
Step 3: Finally System Apps Data.
I have shuffled between CM and Stock several times in the past and have followed this order without issues.
Now, as soon as I restore User Apps and do a reboot, it gets stuck.
Click to expand...
Click to collapse
Never restore system data. If the rom has other structure there's no way it can boot. You have to set up whole settings by yourself. And for the messages use program from Google store to backup and restore them. This won't brick Your phone
Sent from my GT-N7000 using xda app-developers app
Related
Hi,
I wipe my device yesterday to make a fresh install because my o2x has gotten laggy for the past few weeks, I made a titanium backup + CWM backup.
Sadly, some of my apps Data was not backed up for some reason, although the app is able to be restored by titanium, but no previous data backup. The most important apps for me, the LG Memo app and color notes which both i use to record memo. Now lost.
Then i tried to restore from CWM which supposed to be last resort, and it failed to restore halfway through the SYSTEM partition. So now i am totally lost.
This is my second time in a few months cwm failed to make a proper backup (i rarely use it anyway), and the sad thing is i will not know that it is a bad backup until i tried to restore it to see it fails.
So my question is, is there a recommended version of CWM i should use? I flashed my cwm from rom manager, i think it is version 4.0.2.0.
Secondly, is there a way to extract and restore my app + data from raw cwm backup?
Thanks.
Current cwm version is 5.0.2.8. I have installed it directly and never experienced a problem.
I think that you can manually extract your app and push it to your phone.
It's not much of the app itself, but the DATA that is associated with the app. Like i said, the LG Memo i can just get back by reinstalling the rom, but the memos i saved for the past year or so is what i want to get back.
I am daily user of cwm instaled thry RomMenager and it works perfectly. You can try application Appextractor to extract app from your cwm backup
You can also try restoring your /data partition only. CWM has an option to selectively restore parts of your backup. That way you can get your info back.
Sent using some sticks and gum, just as McGyver would
DrummerMuppet said:
You can also try restoring your /data partition only. CWM has an option to selectively restore parts of your backup. That way you can get your info back.
Sent using some sticks and gum, just as McGyver would
Click to expand...
Click to collapse
I tried that... it ends up with bootloop.
@all
Thanks for all your help. I manage to restore the cwm backup after updating my cwm. It got stuck at boot but then i tried reinstalling the Spica's HP custom kernel.. everything's back again. Lucky~
I hope someone can help me.
I just got my GT-N7000 back from Samsung after a repair to the audio socket. The phone was rooted but Samsung returned the phone to the stock JB 4.1.2 ROM. All was working as it should when I got it back.
Now, I wish to re-root the phone and restore my choice of custom ROM - Ultimate _N7000_XXLT4_JB_4.1.2. v6.0 with all my apps and data. This is the ROM I've been using ever since it was published without issue.
I have managed to re-root the phone with the PhilZ Touch 5 recovery + safe kernel and CWM Base Version v6.0.3.7 which I think is the version I was using before. This part of the procedure appears to have worked correctly and I can now boot into the PhilZ Touch 5 recovery without any issue.
However, after restoring the backup I made prior to the audio jack problem and rebooting, he phone hangs after a few initial swipes through the screens ie I can no longer swipe screens or start apps and the phone is non-responsive. All I can do then is remove the battery. No errors are being reported during the Restore and I've taken care to Wipe data/Factory reset, Wipe Cache Partition and then Advanced >Wipe Dalvik Partion.
I tried the Restore several times but the result is the same. One thing that may be related is that my lockscreen image is not the one I was using when I did the backup. Nor is it the stock image of the book and quill pen that the stock ROM uses (it's a picture of a kid leaping into the air with a big bunch of balloons which I've never seen before). This could mean that something isn't being wiped properly.
Any advice from the experts would be most welcome as I'm out of my depth.
Trevor
Did you check in Philz recovery if the restore of Preload partition is enabled..?
nokiamodeln91 said:
Did you check in Philz recovery if the restore of Preload partition is enabled..?
Click to expand...
Click to collapse
Thanks for the reply. No, I didn't know to check that but will do so in future. I have never encountered that setting before. Is it usually enabled by default?
I think the trouble was that at least one of my backup files was corrupt. I tried an earlier one and this one seemed to have fewer problems so concluded that this was the source of trouble.
In the end, I downloaded a fresh copy of the Ultimate ROM I was using which got the phone fully working again and then let Google download all my apps automatically. So I'm out of trouble now.
Thanks again.
Trevor
I have tried this numerous times still no result.
Cm 10.1.3 works perfectly fine. But once i flash it with my Titanium backup update.zip file. There will be errors, and after i reboot it, it iwll just get stuck at the spinning blue circle. I have tried everything, from apps+data to only app data. Nothing works.
I would have to factory reset and reflash it again.
I use clockworks mod recovery.
My phone is a odin rooted Galaxy S3 Lte (i9305)
Shinny123 said:
I have tried this numerous times still no result.
Cm 10.1.3 works perfectly fine. But once i flash it with my Titanium backup update.zip file. There will be errors, and after i reboot it, it iwll just get stuck at the spinning blue circle. I have tried everything, from apps+data to only app data. Nothing works.
I would have to factory reset and reflash it again.
I use clockworks mod recovery.
My phone is a odin rooted Galaxy S3 Lte (i9305)
Click to expand...
Click to collapse
use recovery to flash roms not TB, its much more reliable.. i think the problem is because of apps and data you trying to restore with the update.zip. i know you use tb because you want to restore your apps+data easily while flashing new rom, but tb seems to give problems with this method
MaHo_66 said:
use recovery to flash roms not TB, its much more reliable.. i think the problem is because of apps and data you trying to restore with the update.zip. i know you use tb because you want to restore your apps+data easily while flashing new rom, but tb seems to give problems with this method
Click to expand...
Click to collapse
Nah, i didnt flash my rom with tb, i flashed it with recovery. Then once everything was done, i would go back into recovery and flash the update.zip file
Shinny123 said:
Nah, i didnt flash my rom with tb, i flashed it with recovery. Then once everything was done, i would go back into recovery and flash the update.zip file
Click to expand...
Click to collapse
yes i see, but that seems to be the problem ''restoring apps, data with tb'' and from what i know it occurs that this sometimes gives errors, fc's and bootloops like in your case
MaHo_66 said:
yes i see, but that seems to be the problem ''restoring apps, data with tb'' and from what i know it occurs that this sometimes gives errors, fc's and bootloops like in your case
Click to expand...
Click to collapse
So is there no way to go through with this? Maybe export my backups to another software or something? or am i supposed to start fresh?
Shinny123 said:
So is there no way to go through with this? Maybe export my backups to another software or something? or am i supposed to start fresh?
Click to expand...
Click to collapse
you could try to export your backups (only data) to pc temporary and after having flashed the rom with full wipe, install the apps again and put the backups manually in corresponding directories and see how that is gonna work out. I gave up on TB because of this problem and usually i always start fresh with new flashed roms. I only put my personal files on pc and put it back manually after rom install.
MaHo_66 said:
you could try to export your backups (only data) to pc temporary and after having flashed the rom with full wipe, install the apps again and put the backups manually in corresponding directories and see how that is gonna work out. I gave up on TB because of this problem and usually i always start fresh with new flashed roms. I only put my personal files on pc and put it back manually after rom install.
Click to expand...
Click to collapse
Thanks so much, I dont really need all my apps to be backed up, just important ones, has the manual method worked out for you?
Shinny123 said:
Thanks so much, I dont really need all my apps to be backed up, just important ones, has the manual method worked out for you?
Click to expand...
Click to collapse
yes, most of the times works fine but cant guarantee it will work with every app, i guess has something to do with permissions i.m.h.o
Hi, so I have Moto G 2014 XT1068. It's rooted, and TWRP is installed. I flashed the Nexus dialer (the one with Nearby Places, and Caller ID by Google) from recovery using a zip file, and uninstalled the original one (Big mistake, I know.)
Then I couldn't get calls UI to work, so I reinstalled the original stock dialer using a backup. Now calls work, but everytime I try to open the stock dialer, it shows up as "Dialler has stopped working."
The Nexus UI, however, still works.
I could live with this current scenario, as I can make, pick up, and break calls without problems, but I might need to access the call settings from the stock dialer's menu, which I can't.
All help appreciated - I'm not open to reflashing the firmware / resetting it. I have a backup of the stock dialer made using Titanium, but restoring it does not fix the issue.
Cheers!
Uninstall the Nexus dialer app and then wipe cache and dalvik-cache from TWRP.
sharkymyn said:
Uninstall the Nexus dialer app and then wipe cache and dalvik-cache from TWRP.
Click to expand...
Click to collapse
EDIT : Thank you for your reply. Sadly, this did not work.
I have also tried booting in Safe Mode, but the app did not work there either.
Cheers!
Did you take a full system backup via TWRP?. Try restoring it else flashing factory firmware is the only option left.
Follow this thread : http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
sharkymyn said:
Did you take a full system backup via TWRP?. Try restoring it else flashing factory firmware is the only option left.
Follow this thread : http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
I think I'll wait it out, see if somebody else has another solution, or until I really need to open the settings
Thanks again.
Go to setting>app>stock dialer>clear data n cache> reboot. Njoy
gauravrai said:
Go to setting>app>stock dialer>clear data n cache> reboot. Njoy
Click to expand...
Click to collapse
Thanks, but that didn't work. I fixed it, but it was quite long, though not complicated.
Remove Nexus dialer using Titanium.
Take Nandroid / Titanium backup of all apps and data.
Flash stock - without clearing user data. This will remove recovery as well. Boot and install any OTA updates available.
Reinstall recovery and reroot. Restore stuff using Titanium.
Moral of the story : Have a nandroid backup before messing around.
Cheers!
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3
bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.
isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .