Was wondering if it is safe to restore NAND backup that was made with CM9 on CM9 recovery?
1st i installed CM9
2nd i made backup
3th i want to change DPI but if something goes wrong can i back up via CM9 or do i have to flash GB and CM9 and start again?
I heard that CM9 is "safe"
I'm wondering too, since I wanted to try MIUI (based on CM9) from CM9, and was thinking of doing a backup if MIUI doesn't do it for me.
My guess is that it's "safe", since once you installed CM9 with the proper instructions (from GB and all), you have a proper CWM, buuuut a second opinion would help.
Neomatt said:
I'm wondering too, since I wanted to try MIUI (based on CM9) from CM9, and was thinking of doing a backup if MIUI doesn't do it for me.
My guess is that it's "safe", since once you installed CM9 with the proper instructions (from GB and all), you have a proper CWM, buuuut a second opinion would help.
Click to expand...
Click to collapse
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
SoonHD2 said:
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
Click to expand...
Click to collapse
In my opinion it's safe guys. The problem with the procedures in CWM was mostly caused by Wipes. Also the cf-root kernel was definitely something to be afraid.
Therefore in CM9s' CWM there's nothing harmful.
Sent from my GT-N7000 using Tapatalk 2
SoonHD2 said:
True that. Well at least BackUp went fine but still have no balls to try restore it. And was wondering also that should i install abyssrecovery (red touch) or can i use stock CWM on CM9...
Click to expand...
Click to collapse
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Neomatt said:
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Click to expand...
Click to collapse
The theory is true again!!!
I told you, there was nothing dangerous there.
Sent from my GT-N7000 using Tapatalk 2
Neomatt said:
Well, since MIUI didn't flash (I need to look more into this), I grabbed my balls and tried the whole backup + restore thing, with the "stock" CWM.
And it all went fine. No loss of data, booting up into CM9 like before, all set.
So it's safe.
Click to expand...
Click to collapse
Good to know. Luckily i dont need to use it yet coz romtoolbox dpi cjange went fine and os booted normally and dpi was changed
Related
I want to try some kernels for cm 7.1 to see if ocing could help speed up some games. If I don't like them I would like to get stock kernel back and I know I can't use sgs kernel flasher to back up current kernel because cm7 is different. I think I read that you could do a Nandroid and this would back up the current complete setup. Is this true? (sorry can't seem to search efficiently on this Tapatalk and don't have access to a computer). If so does it also backup apps, data and all? Is it done on the backup rom from rom manager or recovery? Thank you for your help.
Sent from my SGH-I897 using Tapatalk
nandroid backs up everything just as it is. definitely use cwm not rom manager.
you could also just put d/l the stable kernel as a cwm flashable zip.
2 cents
fractaline said:
nandroid backs up everything just as it is. definitely use cwm not rom manager.
you could also just put d/l the stable kernel as a cwm flashable zip.
2 cents
Click to expand...
Click to collapse
Thank you for your help. Where can I find the kernel?
Sent from my SGH-I897 using Tapatalk
Don't know for sure (I don't run cm7), but I would check the op of the cm7 thread.
fractaline said:
nandroid backs up everything just as it is. definitely use cwm not rom manager.
you could also just put d/l the stable kernel as a cwm flashable zip.
2 cents
Click to expand...
Click to collapse
nandroids do not backup kernel or modem.
have you ever made a backup of one set up and tried to restore onto a completly different rom? well if you have then you know there is a high chance that it will bootloop because of a now incompatible kernel. the procedure for a proper nandroid restore is to flash the rom it was backed up on (thus flashing the kernel that is compatible with it) and THEN restoring the nandroid. then it will be like you never flashed away from that rom at all. (this is speaking of tw roms as i have never run an aosp so i could be mistaken about it not backing up kernel on cm7)
studacris said:
nandroids do not backup kernel or modem.
have you ever made a backup of one set up and tried to restore onto a completly different rom? well if you have then you know there is a high chance that it will bootloop because of a now incompatible kernel. the procedure for a proper nandroid restore is to flash the rom it was backed up on (thus flashing the kernel that is compatible with it) and THEN restoring the nandroid. then it will be like you never flashed away from that rom at all. (this is speaking of tw roms as i have never run an aosp so i could be mistaken about it not backing up kernel on cm7)
Click to expand...
Click to collapse
Yea, I kinda thought that, but thought it worked for cm7.
Sent from my SGH-I897 using Tapatalk
I was wondering how perfect of a restore a CWM restore is.
I was running a custom GB ROM (rocket rom to be exact) and it was running flawlessly. I then decided I might try this new CM9 ICS ROM.
So to be sure about the CM9 install, I figure I'd install from a stock GB Rom. So I first did a CWM backup of my current rocket rom and then I restored an older stock (rooted) ROM. It seemed to work fine. Then.... after reading about the (few) issues wit this new CM9 rom I decided I'd wait a bit longer until a few more of the quirks are worked out.
So I then restored back my Rocket rom backup and even doing the flash cache and davik cache also. But now I notice my once working Rocket ROM is experiencing a lot of SODs.
So now I'm wondering how perfect my restore was. I really don't have a lot of apps or wireless networks and can easily restore my contact list. For that reason, do you think it'll help if I do a factory reset wipe and then reinstall everytyhing....or even go so far as reinstall rocket rom and then reinstall everything else manually without any restores...would that be really the best clean install....or would any of this not make a difference at all and wiping/reinstall a toatl waste of time and my prob is actuaully something else....
Thanks
I could do with knowing the answer to these questions too.
It would be good to get a detailed idiots guide to CWM, do's and don't's etc.
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
abhisahara said:
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
Click to expand...
Click to collapse
Sorry for the noob question.... what are SOD's?
adrok76 said:
Sorry for the noob question.... what are SOD's?
Click to expand...
Click to collapse
sleep of death, its the device not waking up properly from sleep
Pus it doesnt include efs, so its not complete backup. Handy if yu stay n same rom version, but thats likely not.
Squicky clean install is always best. Even only app and data recovering thought titanium can mess things up. Make it laggy and nonfunctional etc, Blegh
Sent from my GT-N7000 using Tapatalk 2
1. Install abyssnote42
2. Factory wipe, cache, dalvik
3. Restore your rocketrom backup
That's what i do with my rocketrom v23 backup
Zapped through server hops to XDA forums
its not perfect but its the best so far
all i can say is that cwm is the best and simple thing for me so far and if u get trouble some times while trying to shift from CM9 to normal ics or from gb to ics all I suggest is use redpill recovery from abbysnote
Richy99 said:
sleep of death, its the device not waking up properly from sleep
Click to expand...
Click to collapse
Yeah, mine does that from the clock on Dragon ICS 2.4 when charging it didn't use to, started since I started Dual Booting. 2.5 is out in the next hour or so according to the Dev page. Hope it fixes an otherwise awesome ROM.. Otherwise it's back to single booting and possibly on to Omega 12 until CheckROM is released..
I am currently using the latest RocketROM V7.
I wanna know... if I am to backup and restore a ROM with ClockworkMod Recovery... how should I do it?
I flash Abyss Kernel 4.2, reboot recovery (so I am in the CWM modified by Abyss), backup the ROM... and when I wanna restore, I do the same?
If that's the way to go, when I restore, I'll have Abyss Kernel 4.2, and not the one that the ROM has... Erm... Can somebody shed some light?
I'm asking because I'm aware of all this talk about the eMMC bug (and the fact that it actually exists), and since CWM formats the internal memory... it'd result in a hard brick, haha...
if you backup on Abyss kernel you will be on Abyss kernel AFTER the restore, So ideally you should flash abyss BEFORE restoring, and then change the kernel AFTER (if you want to)
The brickbug is not to be taken lightly, Its a serious issue, so if you have to do things a certain way (I have a ritual for wiping lol) and it takes a little longer, So be it, at least you know you will be safe.......ish
azzledazzle said:
if you backup on Abyss kernel you will be on Abyss kernel AFTER the restore, So ideally you should flash abyss BEFORE restoring, and then change the kernel AFTER (if you want to)
The brickbug is not to be taken lightly, Its a serious issue, so if you have to do things a certain way (I have a ritual for wiping lol) and it takes a little longer, So be it, at least you know you will be safe.......ish
Click to expand...
Click to collapse
Hmm... so... forget about RocketROM for now.
Let's say I am on Half-Illusion, which has two kernels (optionally) : CM and AOKP.
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-backup.
When I restore, I do this :
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-restore.
-flash desired kernel.
azzledazzle said:
The brickbug is not to be taken lightly
Click to expand...
Click to collapse
You don't say . First time I heard about it and was about to wipe/flash for the first time, I was like http://www.youtube.com/watch?v=Y9KyBdPeKHg
-----
What's your wiping ritual? Could it better than mine ? Hope it doesn't involve summoning a lightning strike or anything like that...
Formhault said:
Hmm... so... forget about RocketROM for now.
Let's say I am on Half-Illusion, which has two kernels (optionally) : CM and AOKP.
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-backup.
When I restore, I do this :
-flash jBroid's Kernel Cleaning Script.
-flash Abyss 4.2 kernel.
-reboot recovery.
-restore.
-flash desired kernel.
You don't say . First time I heard about it and was about to wipe/flash for the first time, I was like http://www.youtube.com/watch?v=Y9KyBdPeKHg
-----
What's your wiping ritual? Could it better than mine ? Hope it doesn't involve summoning a lightning strike or anything like that...
Click to expand...
Click to collapse
HAHAHAAAA That video is epic, I can imagine you saying that lol, I too was like that.
And my ritual is similar to yours, Only for TW ROMs
Dont forget that your backup will be a GB ROM, so you cannot restore it if you venture on to TW ICS ROMs ! But im sure you knew that anyway !
Other than that, Your steps are spot on !
azzledazzle said:
And my ritual is similar to yours, Only for TW ROMs
Dont forget that your backup will be a GB ROM, so you cannot restore it if you venture on to TW ICS ROMs ! But im sure you knew that anyway !
Click to expand...
Click to collapse
Erm... what? Lol, explain.
What do you mean it will be a GB ROM? You mean the KERNEL, right?
What do you mean I can't restore it if I venture on to TW ICS ROMs (like RocketROM, for example)?
azzledazzle said:
HAHAHAAAA That video is epic, I can imagine you saying that lol, I too was like that.
Click to expand...
Click to collapse
Actually, it was like this.
So I first hear about the brick bug. http://tinyurl.com/69cc7we http://tinyurl.com/buvmsep
I decide oh well, can't stick with stock ROM. http://tinyurl.com/2at2ad4
So I go on with the wiping / flashing process. http://tinyurl.com/bmoff37
And once it was all done... http://tinyurl.com/4h7lp8q
Formhault said:
Actually, it was like this.
So I first hear about the brick bug. http://tinyurl.com/69cc7we http://tinyurl.com/buvmsep
I decide oh well, can't stick with stock ROM. http://tinyurl.com/2at2ad4
So I go on with the wiping / flashing process. http://tinyurl.com/bmoff37
And once it was all done... http://tinyurl.com/4h7lp8q
Click to expand...
Click to collapse
What I mean is, if your now on a gb rom such as cm9 or aokp And you create a nandroid backup, that backup is going to be a complete clone of your current set up. So you cannot restore that nandroid on a Samsung ics rom you can only restore it on a gb rom
Sent from my GT-N7000 using Tapatalk 2
azzledazzle said:
What I mean is, if your now on a gb rom such as cm9 or aokp And you create a nandroid backup, that backup is going to be a complete clone of your current set up. So you cannot restore that nandroid on a Samsung ics rom you can only restore it on a gb rom
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I didn't know AOKP had GB builds, too...
Anyway. I know what a CWM backup is, I've been in the Android world since exactly 13 months.
What do you mean I can't restore that NANDROID on a Samsung ICS ROM? As far as I know, a CWM restore erases all the contents (system, data, cache) and restores the respective data from the backup... so it's not like it would OVERWRITE on the current TW ICS ROM, for example.
What I wanna know is... I can back up everything, except for the kernel (since I'd flash Abyss 4.2 w/ recovery), and when I restore, I flash the kernel manually. That's all there is to it... right?!
When you are creating a backup...just drop into CWM and create backup. When restoring the backup you can flash the Abyss kernel first > reboot recovery > and then restore. So now when the restoring happens the kernel which was in your rom will automatically get restored and abyss will vanish once rebooted.
@azzledazzle CM9 is ICS and not a GB rom I know you know this and u just slipped your fingers while typing ...but just correcting so that no confusion arises to other readers
And if you are on any CM9 based rom or any AOKP based rom which is based on CM kernel then you dont require Abyss at all. Just forget about it when on any of the roms.
Hope this helps!
Cheers!
Yeah I know its an ICS ROM, But dont you have to be on GB to flash it ? What I mean is you cant flash it from Stock Samsung ICS can you? (thats how i understand it anyway)
And I didnt know CWM erases partitions, I thought it just overwritten the existing ones, Hence why I said dont restore a GB (AOSP ICS) on Samsung ICS (if that makes sense?)
But I guess ive learned something new from you Hopefully I can pass this new found knowledge onto someone else lol
azzledazzle said:
Yeah I know its an ICS ROM, But dont you have to be on GB to flash it ? What I mean is you cant flash it from Stock Samsung ICS can you? (thats how i understand it anyway)
Click to expand...
Click to collapse
Yeah you cant directly flash the CM9 or AOKP based on CM kernel directly over the Stock Samsung ICS. Its a sure shot brick you have in your hand if you do that. The stock ICS kernels cannot handle the "format" command in the updater script, CM is working on trying to use delete_recursive instead but still its not complete fixed. Hence you have to be on GB or on GB kernel (like Abyss) if you want to flash the CM9 based rom.
abhisahara said:
When you are creating a backup...just drop into CWM and create backup. When restoring the backup you can flash the Abyss kernel first > reboot recovery > and then restore. So now when the restoring happens the kernel which was in your rom will automatically get restored and abyss will vanish once rebooted.
Click to expand...
Click to collapse
Oh... you're right, lol. Backing up doesn't format/wipe anything. Only restoring does .
But... the CWM I have right now (was flashed among with RocketROM) is a different version, non-touch-driven, than the CWM that is included in Abyss 4.2 kernel (touch-driven). Are backups compatible?
abhisahara said:
And if you are on any CM9 based rom or any AOKP based rom which is based on CM kernel then you dont require Abyss at all. Just forget about it when on any of the roms.
Click to expand...
Click to collapse
So... you're saying that both CM9 and AOKP kernels have the eMMC thing removed, so wiping data when using those kernels is safe?
-----
Thanks for joining, abhi
abhisahara said:
Yeah you cant directly flash the CM9 or AOKP based on CM kernel directly over the Stock Samsung ICS. Its a sure shot brick you have in your hand if you do that. The stock ICS kernels cannot handle the "format" command in the updater script, CM is working on trying to use delete_recursive instead but still its not complete fixed. Hence you have to be on GB or on GB kernel (like Abyss) if you want to flash the CM9 based rom.
Click to expand...
Click to collapse
Bottom line... Better flash Abyss 4.2 before any full wipe .
-----
This thing in the Samsung ICS kernels... this brick bug... Is Samsung aware of it? Is a fix on the way? Or nobody knows?
Or perhaps it's been made on purpose
-----
Retorical question : WHY POSTS NO LONGER MERGE? -.- :headbang:
Formhault said:
Oh... you're right, lol. Backing up doesn't format/wipe anything. Only restoring does .
But... the CWM I have right now (was flashed among with RocketROM) is a different version, non-touch-driven, than the CWM that is included in Abyss 4.2 kernel (touch-driven). Are backups compatible?
The CWM you have with RocketRom comes from the kernel of ICS which is included in the rom. The Abyss 4.2 is a GB kernel hence it has it own touch recovery. Not sure what you meant by - "Are backups compatible?"
So... you're saying that both CM9 and AOKP kernels have the eMMC thing removed, so wiping data when using those kernels is safe?
Yeah its perfectly safe wiping data on these kernels.
-----
Thanks for joining, abhi
Click to expand...
Click to collapse
Formhault said:
Bottom line... Better flash Abyss 4.2 before any full wipe .
-----
This thing in the Samsung ICS kernels... this brick bug... Is Samsung aware of it? Is a fix on the way? Or nobody knows?
Or perhaps it's been made on purpose
They know. They might be fixing it. Not date from them.
-----
Retorical question : WHY POSTS NO LONGER MERGE? -.- :headbang:
Click to expand...
Click to collapse
Hope the above helps!! In bold are the answers
abhisahara said:
Hope the above helps!! In bold are the answers
Click to expand...
Click to collapse
Yup. Thanks.
What I meant by "Are backups compatible" was... are backups made with the CWM that comes with RocketROM (not touch-driven) compatible with the CWM that is included in Abyss 4.2 (touch-driven)? I mean... can I restore the backups made with one CWM, using ANOTHER CWM?
I always forget their versions...
-----
They KNOW? Good. Oh well, they also know their SAMOLED screens suck, but didn't do anything to fix it... Let's hope they're gonna fix this brick bug soon; although it seems highly unlikely... I mean, we already got 4.0.4, and that didn't fix it. The next update is probably going to be JellyBean (if we even get that officially!), some 5+ months from now on :/
This brick bug is utmost retarded. I mean... on the Note, and recently, on the SGS2 as well... they're either stupid, either it was on purpose - to prevent at least some devs on working on those devices...
Formhault said:
Yup. Thanks.
What I meant by "Are backups compatible" was... are backups made with the CWM that comes with RocketROM (not touch-driven) compatible with the CWM that is included in Abyss 4.2 (touch-driven)? I mean... can I restore the backups made with one CWM, using ANOTHER CWM?
I always forget their versions...
-----
They KNOW? Good. Oh well, they also know their SAMOLED screens suck, but didn't do anything to fix it... Let's hope they're gonna fix this brick bug soon; although it seems highly unlikely... I mean, we already got 4.0.4, and that didn't fix it. The next update is probably going to be JellyBean (if we even get that officially!), some 5+ months from now on :/
This brick bug is utmost retarded. I mean... on the Note, and recently, on the SGS2 as well... they're either stupid, either it was on purpose - to prevent at least some devs on working on those devices...
Click to expand...
Click to collapse
Yeah you can restore backup made with some other CWM while using another CWM.
Intrestin ^^
Sent from my GT-N7000 using XDA Premium App
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse
sorry I'm just going to post twice so I can post to development...
yeah... 10char
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse
I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?
same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse
Am on criskelo 11.2 with speedmod kernel 3.13.
All is fine, it appears I have root (titanium etc works) and a check with 'got root' returns an ok response.
The phone is behaving itself nicely and is nice and smooth.
The problem comes when I try and do a nandroid backup using cwm.
It gets a liitle way in and then freezes (forever!)
Things I've tried to cure this...
1) Rolling back to stock GB and then re-rooting, then full 3 wipes, then reinstall criskelo rom.
2) Rolling back to a pre-rooted GB rom, then all 3 wipes, then re-install croskelo
2) Flashing other kernels, notecore etc
3) Installing superuser 3.1.1.zip with cwm and its binary update.zip
4) Installing SuperSU app from play store - it says needs to update binaries, and when I try it just says 'installation failed!'
5) Installing superuser app from play, this time when I try and update binaries it does helpfully say ' remounting /system as rw... fail!'
which leads me to believe this is a root problem, even though no other app is complaining.
6) doing a search on this forum (before you all tell me to do this!)
I have been trying to solve this for over a week now, and it feels like I have read everything on this forum but I may have missed something.
Can anybody steer me in the right direction please?
Maybe you dont need a nandroid backup, it doesnt backup efs anyway.
Could be a kernel issue, or space issue. Not sure.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Maybe you dont need a nandroid backup, it doesnt backup efs anyway.
Could be a kernel issue, or space issue. Not sure.
Click to expand...
Click to collapse
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?
jonnybruce said:
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?
Click to expand...
Click to collapse
Have you tried updating cwm? I believe older versions had this problem.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Have you tried updating cwm? I believe older versions had this problem.
Click to expand...
Click to collapse
No I haven't Spyder, although I have tried a few different roms whic all have differing versions of cwm right?
which one is the latest then, and how do I install it, would it be an update zip?
jonnybruce said:
Cheers, you might be right, but I have always used nandroid before flashing a new rom,
may I ask what you use to backup then, when you change rom?
Click to expand...
Click to collapse
I am a heavy flasher and prevent issues caused by restores to get a clean taste of roms. Nandroids I tried, but I havent found a rom I wanted to go back on always, flash so much that it just takes to long.
Efs with a tool in one if my threads, suggestion by Chasmodo. DrKetan has a good toolbox thread in general section.
I manually backup photos and such with a file explorer. Calander/Contacts/email in gmail,
whatsapp and special app stuff also manually transfer folder from sdcard and back.
Messages I dont care for. Neither made calls list.
Occasionally I do restore app if dissapeared from market with Titanium, but only app, not data. I save backups on external. Cause I clean sdcard also.
Sent from my GT-N7000 using Tapatalk 2
jonnybruce said:
No I haven't Spyder, although I have tried a few different roms whic all have differing versions of cwm right?
which one is the latest then, and how do I install it, would it be an update zip?
Click to expand...
Click to collapse
The latest version for Note N7K is 6.0.1.2.. chek the below link... download option is there
http://www.clockworkmod.com/rommanager/
jonny, i feel your problem is due to partial root.
could you copy files into system in root explorer ?
did adaway work in applying hosts file ?
for criskelo rom too you should choose CF root kernel during the flashing process, then later you may change to your preference
Thanks baz & nokia, much appreciated.
I am running PA 1.99 now and it has the new cwm (you can tell because it has a grey background now!)
And rraaka, you are correct, I cannot copy anything to system
Not sure how I can get full root back though, I have used Dr Ketans rooting tool many times to try and cure this issue as well as flashing pre-rooted GB roms with Odin.
Not sure what else I can do.
But am starting to agree with baz now, I can do without nandroid (it takes ages anyway) and just use titanium to restore.
Everything is working fine with my partial root (except nandroid) anyway so not sure I care anymore!
Am enjoying Paranoid Android by the way, JB is fun.
I do miss the samsung apps though, I don't suppose those have been jellybeaned yet??
nope not yet, nothing Touchwizz like spen etc.
There is a cwm flashable of samsung apps that works pretty good on cm9, not sure if it works on cm10 or jb.
gaining full root shouldnt be to difficult, update binaries and then you know for sure.
The one that has worked wel for me is the ssu only zip from this post but then again thats on stock stuff.
http://forum.xda-developers.com/showthread.php?t=1841288
For custom roms/kernels the ones supplied with it are build in to work out of the box.
Once fully clean install, a nandroid can work but thats fully clean
Sent from my GT-N7000 using Tapatalk 2
Thanks baz, am going to go back to the start (stock ICS) and try that link to try and get my full root back, looks interesting.
Ok, I have full root again now!
here's what I think I remember what I did...
Downloaded the first two Su & busybox zips using method1 on the link that Baz kindly shared with me and popped them on my sd card ready.
http://forum.xda-developers.com/showthread.php?t=1746794
Downloaded and flashed the latest UK Carphone Warehouse stock ICS rom with odin.
Rebooted to stock recovery - applied update zip - flashed first the SU and then Busybox zips downloaded earlier.
Rebooted phone to check all was ok.
Located superSU app and ran it to check - and first it said it didn't recognise my phone model, hmmm...
So I downloaded mobile odin from play and flashed abyss 4.2 kernel
Rebooted to recovery, full 3 wipes and rebooted system.
Ran superSU again and magically it updated binaries and for the first time in 2 weeks it said 'sucessful', I was very pleased!
Rebooted to recovery and flashed Criskelo 11.2 again (have gone back to this from PA until things are a bit more stable)
Restored all my apps from TB all good.
Checked Adaway and it was more than happy to replace host file, and root explorer is also happy.
Cool