Related
Would be grateful if someone could shed some light on this for me.
My situation is this:
1. I download a new ROM, or an updated version that I would like to try out.
2. I reboot in to recovery (CWM based recovery v5.0.2.7) and create a back-up.
3. I install new ROM, wiping where necessary, or keeping my data if an updated ROM dictates that I can.
4. The new install goes well, boots fine, and no problems etc....
5. I then decide, id like to go back to what I had before...
6. I reboot to recovery, select to restore, and choose my back-up that I had just made
7. Recovery fails stating "Error while restoring /system!
I then find myself not being able to reinstall my ROM, load any back-ups or anything, and my only way out is to go to download mode, and flash a ROM through odin.
What gives? and where am I going wrong?
Moved To Q&A
Please post all questions in the Q&A section
Is you Note running an ICS Rom now? What you are describing sounds very much what happens when you want to do a restore from our wonky ICS CWMR.
If yes, this is the way to get your restore to work:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
chasmodo said:
Is you Note running an ICS Rom now? What you are describing sounds very much what happens when you want to do a restore from our wonky ICS CWMR.
If yes, this is the way to get your restore to work:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
Click to expand...
Click to collapse
if that recovery is better than CWMR, why dont we all use that?
I'm not sure, but I might have read on some issues with going from GB to ICS and then recovering back to GB.
Was that your scenario?
Sent from my GT-N7000
panyan said:
if that recovery is better than CWMR, why dont we all use that?
Click to expand...
Click to collapse
Because CWMR always comes together with a specific kernel (CF--Root has standard CWMR, AbyssNote has Redpill Recovery etc.).
The only two ICS kernels we have ATM are CF-Root ones, hence the standard CWMR in all ICS Roms.
---------- Post added at 04:32 PM ---------- Previous post was at 04:30 PM ----------
Markuzy said:
I'm not sure, but I might have read on some issues with going from GB to ICS and then recovering back to GB.
Was that your scenario?
Sent from my GT-N7000
Click to expand...
Click to collapse
This little guide posted in the link above is the only way for you to successfully revert from ICS to GB. Every other scenario is hit-and-miss (more miss than hit, though).
chasmodo said:
Because CWMR always comes together with a specific kernel (CF--Root has standard CWMR, AbyssNote has Redpill Recovery etc.).
The only two ICS kernels we have ATM are CF-Root ones, hence the standard CWMR in all ICS Roms.
---------- Post added at 04:32 PM ---------- Previous post was at 04:30 PM ----------
This little guide posted in the link above is the only way for you to successfully revert from ICS to GB. Every other scenario is hit-and-miss (more miss than hit, though).
Click to expand...
Click to collapse
Hmmmm ,and I was just wondering why every ICS revert to GB was done with abyssnote 3.9 kernel?
what I understood from your post above is that CWM recovery not compatible with ICS? And if so then is abyssnote the only kernel that contains red pill recovery?
one learns new things every day , that's the beauty of life.
+1
EDIT: what about mobile ODIN?
Can't we just flash a stock rooted GB ROM using it ,and afterwards boot to recovery and flash a nandroid restore
Will that work?
I'm having the same issue;
Some days ago I tried CM10 and Paranoid CM10, could flash them both with succes.
I had like 20 back up on my sd and wanted to revert back to Paranoid CM9 0.5.
While I was trying to restore I got the same error like in the OP.
Not one of all my back ups was usable to revert back.
So I searched and read a bit overhere and saw it necessary to use the approriate kernel to revert back.
If I understood right, when being on CM10 you first had to flash a CM9 kernel to restore a CM9 ROM.
I tried this but I never succeeded, no big harm anyway. I did a clean install and moved on.
Till today when I made a back up from my CM9 Paranoid CM9 0.5 ROM, with stock kernel.
The back up went fine and I flashed 0.4, I played a bit with 0.4, went back to recovery and tried to restore my latest back up, which again, did not succeed, same error like in OP.
With the first problem I understand there was issue between CM9 and CM10, but the second time I don't. I had a CM9 back up, flashed a CM9 ROM and tried to restore a CM9 ROM;
Does anyone know what could cause this problem ? Am I doing something wrong ?
Thanks in advance.
Hey all, been cruising just fine on Hellybean with devil recovery. It started acting funky so I went to a backup back in August that was a fresh, perfect install. Well I forgot it was the next to last backup and not the latest backup. The first backup was an accident backup that never backed up correctly. Well after it not booting I tried the "3rd" backup thinking that was the correct one. That put me back to ICS. Well after I booted into ICS I went back to recovery but it was CWM recovery instead. So I determined the "2nd" backup was the right one after the former ones didn't either. Well unless my backups changed when It went from Devil recovery to CWM recovery then I have no clue what happened. I selected the "2nd backup" and I guess that was from a complete different backups from a different recovery.
Sorry if my post is confusing. Hard to explain all of it on text.
As of now the phone is sitting at the splash screen for whatever OS it has on it now. Want to say a year old or so. I can't get into the recovery by turning it off and holding the volume buttons while turning it on so I'm a little stuck.
Any advice to get back to my JB backup or did I lose any JB backup I had when devil got replaced with CWM?
blackinches said:
Hey all, been cruising just fine on Hellybean with devil recovery. It started acting funky so I went to a backup back in August that was a fresh, perfect install. Well I forgot it was the next to last backup and not the latest backup. The first backup was an accident backup that never backed up correctly. Well after it not booting I tried the "3rd" backup thinking that was the correct one. That put me back to ICS. Well after I booted into ICS I went back to recovery but it was CWM recovery instead. So I determined the "2nd" backup was the right one after the former ones didn't either. Well unless my backups changed when It went from Devil recovery to CWM recovery then I have no clue what happened. I selected the "2nd backup" and I guess that was from a complete different backups from a different recovery.
Sorry if my post is confusing. Hard to explain all of it on text.
As of now the phone is sitting at the splash screen for whatever OS it has on it now. Want to say a year old or so. I can't get into the recovery by turning it off and holding the volume buttons while turning it on so I'm a little stuck.
Any advice to get back to my JB backup or did I lose any JB backup I had when devil got replaced with CWM?
Click to expand...
Click to collapse
Since you have no idea what you've currently got running and you can't seem to get into recovery then my only suggestion is to get it into download mode. From there get yourself the KK4 one click and take it back to stock. Then flash back to helly bean. As far as your backups go if you're sure of which one is which at this point you should be able to restore from it. But you might just start from scratch and forego the potential issues again.
The backups should all be there though, unless your internal and/or external storage got wiped by accident at some point.
UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff
Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.
CM 10.2 Build removed due to errors.
jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.
@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4
I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.
Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.
Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.
motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.
When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2
Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.
I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.
It works with the xt902 too. Thanks!
What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
wrswldo said:
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
Click to expand...
Click to collapse
I believe it's because your 25b isn't bumped. Xdabbeb's newest ROM is bumped. You'll have to downgrade to non-bumped kernel to restore that backup.
Fixed it?
wrswldo said:
Let me start by saying that after the error, through the use of the power and volume down buttons (the timing was different, seemed a little slower, if that makes sense), I was able to get my phone to boot into TWRP and restore the nandroid I made just prior to the error, so I'm up and running fine. What I don't understand is 1.) Why it happened and 2.) How to restore my other nandroid.
After flashing xdabbeb's 26A Bootstack and his VS982.5 ROM and all was running well, I wanted to go back to my nandroid prior to flashing the VS982.5, which is simply the stock Verizon ROM on 25b. I made a backup of VS982.5, then went and restored my previous stock backup. After I restored my stock backup, I got the following error when I tried to boot, and then the phone would go black.
boot certification verify
--------------------------------
secure booting error!
cause: boot certification verify
Based on the other threads I have read regarding the error, it seems like I was very lucky to get back into recovery. Can anyone tell me why this happened so I understand what I did wrong and avoid it in the future and what I might be able to do to restore my previous backup should I want or need to go back to Stock?
I didn't think this was specific to xdabbeb's ROM so I put it under general help instead.
Click to expand...
Click to collapse
Were you able to fix this? I did a similar thing. I am stuck on the on the black screen and can't in recovery.
Thanks!
So recently i finally unlocked my bootloader and started teaching my self how to deal with A/B partition scheme, wanted to find out if data could be restored after making a nandroid in twrp, since on the twrp thread another user was never able to restore data after many attempts, and i went head and setup my stock rom how i like it installing apps/logins etc etc the usual, and i went ahead and flash twrp on my opposite slot in my case A(stock is on Sot B for me) and went ahead switch to my stock slot B and made a nandroid back of boot/data, then went and flashed a few gsi's trying to boot a few but long story short i managed to restore data from a nandroid backup, the only issue is you will loose fingerprints and app defaults settings not a big issue(for me atleast) so here it is:
(Before doing these steps YOU NEED TO HAVE MADE A NANDROID ON TWRP!!)
1.After your done flahshing gsi's/zips and want to go back to stock, go to your stock active slot and boot into stock recovery wipe data, and boot stock until you see the setup wizard.
2.Now go into your bootloader switch to were twrp is, once in twrp switch to your asus stock slot, then go to restore select your nandroid and only restore /data.
3.Once thats done you can go ahead and boot your stock slot with all of your working data intact! =], if your pin does not work go back to twrp switch to your stock slot then go to "advance" then "file manager" then navigate to /data/system and tab on locksettings.db and delete it, then reboot system(your stock slot!)
4.Enjoy!!
rafyvitto said:
1.After your done flahshing gsi's/zips and want to go back to stock, go to your stock active slot and boot into stock recovery wipe data, and boot stock until you see the setup wizard.
Click to expand...
Click to collapse
This means, GSIs has to be installed in a different slot than the Stock ROM. Like, Slot A = Stock ROM, Slot B = TWRP and Custom ROM.
Am I correct?
---------- Post added at 04:51 AM ---------- Previous post was at 04:50 AM ----------
Thanks for the guide.
hamzain said:
This means, GSIs has to be installed in a different slot than the Stock ROM. Like, Slot A = Stock ROM, Slot B = TWRP and Custom ROM.
Am I correct?
---------- Post added at 04:51 AM ---------- Previous post was at 04:50 AM ----------
Thanks for the guide.
Click to expand...
Click to collapse
That's what works for me yes.
rafyvitto said:
That's what works for me yes.
Click to expand...
Click to collapse
Thanks.?
Thanks for the guide. A life saver .!!
Successfully restored all data.