Related
hi
im on 2.3.4 stock and rooted and i have converted file system to ext4 before backing up.(is that safe) or should i convert to rfs? and then backup?
im kind of scared to flash custom roms, i wana flash ics onecosmic.
i did a backup in CWM now if i flash ics rom and something goes wrong can i just revert back to previous firmware by doing a restore in CWM?
Sure!
If you had backup everything (most important thing is ROM) and with the term everything I mean EVERYTHING (mp3, images on SD etc etc) you can now flash from CWM the .zip you want.
I'm on teamhacksung's one (still ICS) so I don't know well the procedure to flash it,
but on the thread it's all documented!
Hope to have another ICS soon !
ext4 doesnt matter?
i just flash roms thats it?
If you wanna be 100% sure "downconvert" to RFS again, backup again, then flash what you want!
2 backups is better than 1.
xunair said:
hi
im on 2.3.4 stock and rooted and i have converted file system to ext4 before backing up.(is that safe) or should i convert to rfs? and then backup?
im kind of scared to flash custom roms, i wana flash ics onecosmic.
i did a backup in CWM now if i flash ics rom and something goes wrong can i just revert back to previous firmware by doing a restore in CWM?
Click to expand...
Click to collapse
I suggest you to revert back to rfs before flashing any custom ROM.
Lagfixes can cause problems when flashing and go back to rfs isn't harmfull or complicated.
Than follow exactly what is written on the OP of the Rom of your choice and you're ready to go.
When you have everything backed up, in the worst case of a bad flash you can always go backwhit your NANAD backup or to stock with Odin and Download mode. I was scared like you but now I flash ROMs like crazy even if I'm not so experinced!
ok im gona do it now
thanks alot guys
stesancri said:
I suggest you to revert back to rfs before flashing any custom ROM.
Lagfixes can cause problems when flashing and go back to rfs isn't harmfull or complicated.
Than follow exactly what is written on the OP of the Rom of your choice and you're ready to go.
When you have everything backed up, in the worst case of a bad flash you can always go backwhit your NANAD backup or to stock with Odin and Download mode. I was scared like you but now I flash ROMs like crazy even if I'm not so experinced!
Click to expand...
Click to collapse
man we are all crazy!!
flashing ROM is kind of a second job 4 me!!
bedo1987 said:
man we are all crazy!!
flashing ROM is kind of a second job 4 me!!
Click to expand...
Click to collapse
True! Once you try that...you'll never come back!
be sure
just be sure of what you were doing read understand all of the instructions, im a bit confuse lately but the urge of me having a custom ROMs running on my GS make's me realize i can do it, but of course by the help of our fellow android user..if i can do it u can also..anyways give it shot...
you are now entering a new and fantastic world,
dont be shocked when you struggle to keep the same Rom installed for a whole week
pzayx said:
you are now entering a new and fantastic world,
dont be shocked when you struggle to keep the same Rom installed for a whole week
Click to expand...
Click to collapse
Hehe, more like 2 days it seems for me..
Good luck.
I did it yesterday for the first time... (flashing a Rom ofcourse ) And it was easier than I thought! Just do it.
It's just about follow the instructions!
bedo1987 said:
It's just about follow the instructions!
Click to expand...
Click to collapse
And experience.
jsolhac said:
And experience.
Click to expand...
Click to collapse
bedo1987 said:
It's just about follow the instructions!
Click to expand...
Click to collapse
And self research with the help of XDA and Google
People are saying its hard to brick SGS.
There is 1 golden rule backup whatever you can before flashing (most important thing is backing up /efs partition because there are all data describing your individual phone egz IMEI number).
When I flashed ICS I couldn't get network signal so I had to restore my /efs and it worked.
It is hard to brick when you can get inside recovery & download mode, otherwise not so much ;-)
Only play around with ROM's if the 3 buttons combo work
Well i got my I9000 3 days ago and i already bricked it twice!
Well after you do the same thing with more than 2 phones, you set lol
josueciz said:
Well i got my I9000 3 days ago and i already bricked it twice!
Well after you do the same thing with more than 2 phones, you set lol
Click to expand...
Click to collapse
Twice same phone? then it look like you didn't bricked it at all.
For me and probably most of people definition of bricking is:
-you cant get into download mode (semi brick)
-you cant get into download mode using a jig plug (only service can help you then but warranty doesn't cover this so it depends on luck)
-you lost your /efs (no backup anywhere) (only service can help you then but warranty doesn't cover this so it depends on luck)
-and I guess other option could be you messed up with bootloader and cant reflash it ;/
Hello,
I recently flashed my Galaxy Note with a stock rom and i got it root and also got the CWK installed. Now I want to try to install the Android 4.0.
I read the instructions and it says:
1. Make sure you're on the latest CWM
2. MAKE A NANDROID
3. wipe data/factory reset in recovery
4. flash ROM
5. flash Gapps
6. reboot
Click to expand...
Click to collapse
All i can understand is 1, 3, 4 and 6. Can anyone elaborate or give me some links to "Make a Nandroid" for example or what a "Gapps" is?
Thanks in advanced,
Alexw
You should do some searching and some reading before u try 4.0 if u are not familiar with how to do a back up u should probably leave ics alone for now it has been harder for people to get back from ics to gb then it is to get Ics on your phone in th first place and to do a back up u boot in to cwm go back and restore and choose back up not much to it and gapps are google apps which would be provided in download links in the main page of the rom or already in rom
Sent from my GT-N7000 using XDA Premium HD app
Nandroid = backup: boot into CWMR and hit Backup and restore/Backup
gapps = Google apps
ttibbetts83 said:
You should do some searching and some reading before u try 4.0 if u are not familiar with how to do a back up u should probably leave ics alone for now it has been harder for people to get back from ics to gb then it is to get Ics on your phone in th first place and to do a back up u boot in to cwm go back and restore and choose back up not much to it and gapps are google apps which would be provided in download links in the main page of the rom or already in rom
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Is it not possible to use a stock ROM with odin and check re-partition if I want to go back to GB?
Also I can't find a Gapps link at that topic. Can you recommend a other good Android 4 ROM?
Thanks,
Alexw
alexwijn said:
Is it not possible to use a stock ROM with odin and check re-partition if I want to go back to GB?
Also I can't find a Gapps link at that topic. Can you recommend a other good Android 4 ROM?
Thanks,
Alexw
Click to expand...
Click to collapse
hi there
just that you know so far ICS roms for galaxy note come all from a leacked ICS version who is quite unstable....so you need hard work (if you are not confident with odin) to install ICS, hard work to use it and hard work to return to Gingerbread.....when you will be fed up...
i did it and now after 2 weeks of testing on ics i returned back happily to Gingerbread....but many of the folks around even bricked their note on ICs so i recommend a lot of care prior to do any ics stuff.....
if you accept an advice....wait for ICS rom ....when a proper ics with souces will be released for our note dev will work on it and it will be ok
for now install Leomar checkrom v6 who still is gingerbread and add from kitchen their huge ICS domination theme.........you will be happy and with no big worries.....
lorekarf said:
hi there
just that you know so far ICS roms for galaxy note come all from a leacked ICS version who is quite unstable....so you need hard work (if you are not confident with odin) to install ICS, hard work to use it and hard work to return to Gingerbread.....when you will be fed up...
i did it and now after 2 weeks of testing on ics i returned back happily to Gingerbread....but many of the folks around even bricked their note on ICs so i recommend a lot of care prior to do any ics stuff.....
if you accept an advice....wait for ICS rom ....when a proper ics with souces will be released for our note dev will work on it and it will be ok
for now install Leomar checkrom v6 who still is gingerbread and add from kitchen their huge ICS domination theme.........you will be happy and with no big worries.....
Click to expand...
Click to collapse
Alright, I'll wait then. Samsung delayed the release of the ROM for the Galaxy Note to April.
leaked ics roms is lots of trouble!
just stay away from that and wait for the official version.
alexwijn said:
Alright, I'll wait then. Samsung delayed the release of the ROM for the Galaxy Note to April.
Click to expand...
Click to collapse
If u really want try i would recommend midnote 2.0 very stable for me and has all u need i main post and step by step on flash process
Sent from my GT-N7000 using XDA Premium HD app
1. Pretty Explanatory!
2. NANDROID Backup: It backs up your CURRENT system as it is. All the settings, applications, everything is backed up! If you ever experience any problems, you can restore to this backup through CWM Recovery menu or the CWM app. I really recommend you to make a backup of your stock ROM. Always create backups!
It is pretty easy to do so too. If you have the CWM app, just open it and create a backup through the backup option. Alternatively, open CWM Recovery, scroll to backup and restore, hit backup and your backup will be created!
3. Before jumping from one ROM to another, ALWAYS perform "wipe data/factory reset". It clears everything on your phone so you won't have any problem in installing the new ROM. Also, go to advanced and perform "Wipe Dalvik Cache".
4. Search for any ROM for your note. TeamRocket ROM, RoMow ROM are some good ICS ROMs. Download them, put the .zip file to the root of your sd card and select "install zip from sd card" option in CWM Recovery AFTER you do number 3.
5. Flash GAPPS. This is just a .zip file to download all the google apps to your phone (market, etc.). Google for it! But, apart from CMX ROMs, I never needed to do this. TeamRocket, RoMow, CheckROM etc include GAPPS by default.
6. Reboot your phone through the recovery menu.
7. Enjoy! XD
Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961
Hi there,
Bootloops happen every now and then, if something collides or is misconfigured.
In my very own experience most boot loops happen to be script related.
This is why you should´t worry too much.
You still can enter CWM?
If so enter CWM and wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If it still is in boot loop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodels which slightly differ from original)
In case you do not have a rooted device without CWM only thing you can do, is to begin from scratch by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device including you´ll keep all your private stuff.
Flashing the Samsung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #
DJ-Tumor said:
Hi there,
Bootloops happen every now and then, is somethine collides or is misconfigured.
In my very own experience most boot loops happen to be skript related.
This is why you should´t worry too much.
You still can enter CWM?
If so Enter CWM, wipe completely (factory, cache, dalvik) and after that (NO REBOOT!!!) just reflash the ROM which just didn´t happen to work properly.
If ist still is in bootloop there might be something wrong with the ROM.
> Rom is guarantied completet? No broken Download?
> Rom is really for the exact telephone model you got? (Galaxy S for example has several submodel which slightly differ from originall)
In case do not have a rooted device without CWM only thing you can do, is to begin from scrath by flashing an official ROM from Samsung via odin.
With that you should flash a kernel with CWM next time, cause it much easier to recover your device incl. you keep all your private stuff.
Flashing the Sasmung-Rom via odin will kill anything saved but the external SD.
hope this helps
# Rodger #
Click to expand...
Click to collapse
Have done as you said, but still problems.
One of the problems maybe can be that it isn't CWM but RedPill.
Yes, I did download the whole file, so no strange abort of the download.
And this is the correct ROM for the Galaxy Note.
If I still have this problems in 24 hours I will contact my store and let them know what I think. I want my money back. I can also add that I'm studying law, so I let the lawbook speek for itself.
But thanks for a fast answer!
Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of
DJ-Tumor said:
Well sad to hear that. Laws have to be different from those in germany
You´re obviously trying to flash inofficial stuff on your own. There is no way the shop could be made resposible for.
So take my advice and reflash official ROM before you return the device.
That will help enormously.
But before runnign too fast, try to give some more information to us here:
What ROM are you trying to flash?
What ROM is installed before trying to flash?
What Kernel is used to flash?
Are you using mobile Odin?
Try to answer questiones I just dind´t think of
Click to expand...
Click to collapse
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?
MinnesotaVikings1961 said:
Good evening guys!
So I'm stuck in a bootloop, and it doesn't look that I will come out of it. I'm running ROCKET ROM V22, and the Abyss3.9 kernel.
So what do you recomend me to do?
I'll now over the night keep my phone on, to try to get out of the bootloop. But I would need som advice what I shall do.
The problem is that the phone won't mount as a storage device in the computer. And I have no backup in my phone, only on the computer, so I can't restore it easy.
Help me! *said with panic on my voice*
Best regards MinnesotaVikings1961
Click to expand...
Click to collapse
You need to flash rocket rom v20 before v22 that i belive is or problem if u can mount sdcard to computer u may have to take sdcard out of your phone and put in something else to load the program on the card then put back on phone and then flash v20 of rocket rom and then see if it boots up if it dose then u can flash v22
Sent from my GT-N7000 using XDA Premium HD app
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?[/QUOTE]
U could in download mode with odin pc
Sent from my GT-N7000 using XDA Premium HD app
Quick google search shows boot loops are pretty well known with this rom.
No you only can flash original rom with odin.
If there are important data on the device connect it cia usb and boot into cwm.
Now wath what happens. If you´re lucky mass storage mode is enables in the kernel and you got your storage mounted automated.
If not it´s time to cross fingers and search for an option to mount by hand.
I´m completely new to NOTE - all my knowledge comes from my i9000 which is a mega active community compared to the one of the NOTE
There is have the choice between 5 different ICS kernels alone
Each one has it´s abilities, so does one have the option to mount storage by hand.
This option can be found in "advanced". Hope this menu option is present in your rom
good luck!
# Rodger #
MinnesotaVikings1961 said:
The laws are maybe a little bit diffrent. For example, the first 6 months, the seller or shop needs to prove that the product was working when the sold it. Something that they have very hard to prove.
I'm trying to install the ROCKET ROM V22 for SGN.
I had the MidNote V2.0
The Abyss3.9 kernel (I think that it's the correct way of spelling it).
No, I'm not using mobile Odin.
Edit: Can I install a stocket ROM, with my phone in bootloop, and non mountin as a drive in the computer?
Click to expand...
Click to collapse
Yeah you can. Just go to this thread. Get a rootable rom downloaded. Just follow the instructions to the word of how to flash via odin. And you will have stock rom. And you can again root and install custom rom!! No need to run back to store !
Links-
Roms and guide- http://forum.xda-developers.com/showthread.php?t=1424997
Rooting and odin - http://forum.xda-developers.com/showthread.php?t=1329360
Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?
chasmodo said:
Midnote 2, as in ICS Midnote? You couldn't have been on AbyssNote 3.9, because it's a gingerbread kernel.
Perhaps it was Angelom's stock ICS rooted kernel?
Or did you flash AbyssNote 3.9 from Recovery, trying to go back to GB?
Click to expand...
Click to collapse
Well, I had been using ICS MidNote for a short time, due to a friend mine wanted to see ICS for the Note.
Now I tried to get back to my regular GB ROM.
/ Jimmy
You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
chasmodo said:
You have me utterly confused here...What is the latest rom you were on before this bootloop? Midnote 2 or RR 22?
If Midnote 2 (ICS) with Angelom's kernel, and you did a factory reset at some point, there's hardly anything you can do except take your phone to Samsung service. If you had CF--Root ICS kernel, then try to follow this little set of instructions:
http://forum.xda-developers.com/showpost.php?p=22758543&postcount=6
Click to expand...
Click to collapse
Sorry for being confusing you!
Before this bootloop I was running MidNote V2.0, ICS. I then tried to flash ROCKET ROM, V22. And when I started up, this bootloop came up, and isn't solved in writing moment, very many hours later.
/ Jimmy
Case closed
I can now say that the case is closed. What I did is very simple. In fact, so simple I never thinked about it. The only thing I did was to unroot my phone using Odin.
But thanks for all tips and support!
/ Jimmy
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