Related
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Mr.Clark said:
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Click to expand...
Click to collapse
1) No, you should not wipe anything before flashing a kernel. You should however do a NANDroid backup.
2) You should be able to but it will wipe your kernel.
3) Restore your backup from #1
Mr.Clark said:
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Click to expand...
Click to collapse
flashing a kernel doesnt wipe your phone, it simply replaces whatever kernel is in your phone at the moment.
kenvan19 said:
1) No, you should not wipe anything before flashing a kernel. You should however do a NANDroid backup.
Click to expand...
Click to collapse
Right. Guess what my next question will be
kenvan19 said:
2) You should be able to but it will wipe your kernel.
3) Restore your backup from #1
Click to expand...
Click to collapse
2) Is fine, as once I've figured out how to NANDroid backup, re-flashing it should be easy enough. 3) Is fine, once I've taken the backup in the first place.
simms22 said:
flashing a kernel doesnt wipe your phone, it simply replaces whatever kernel is in your phone at the moment.
Click to expand...
Click to collapse
Excellent, thanks!
Ok. So all the NANDroid guides I've seen here start with ADB and Fastboot (which I remember doing when I rooted the phone), but then they say about flashing alternative recovery images... is that necessary? Or is that what the fastboot thing was?
I've just checked and ADB still works, so if fastboot is an alternative recovery image, am I good to take a NANDroid backup, and if so, how do I do that?
If Fastboot is not an appropriate recovery image, do I need Clockwork Recovery (is that different to the "CWM" I see mentioned around here?)?
The Nexus S guide I read said that there was a NANDroid option in the Clockwork Recovery. Now this isn't in my recovery options, obviously, but I assume with ADB, a command prompt and a few instructions, I can do it manually. Maybe.
Bear with me guys, I'll get there eventually...
Ok, scratch the NANDroid questions. NANDroid is a backup tool contained in the Clockwork Mod recovery image.
Using Fastboot, you can boot from the recovery image without flashing it (using this guide here), so I've still got whatever recovery image I got when I did Paul's rooting technique, but have booted into CWM once to do the NANDroid backup.
I may flash CWM later, that's a task for another day.
So. Now I've got the backup (and thus, booting from that image again later, the ability to restore from it), I can try flashing the kernel. Which I can do from the regular recovery image.
Mr.Clark said:
Ok, scratch the NANDroid questions. NANDroid is a backup tool contained in the Clockwork Mod recovery image.
Using Fastboot, you can boot from the recovery image without flashing it (using this guide here), so I've still got whatever recovery image I got when I did Paul's rooting technique, but have booted into CWM once to do the NANDroid backup.
I may flash CWM later, that's a task for another day.
So. Now I've got the backup (and thus, booting from that image again later, the ability to restore from it), I can try flashing the kernel. Which I can do from the regular recovery image.
Click to expand...
Click to collapse
To flash from the stock recovery you must rename files update.zip just FYI. I've said it before and I'll say it again; there are no possible negative repercussions from flashing a non-stock recovery image.
Apparently it was unsigned, so the stock recovery wouldn't do anything with it.
Back in CWM and it worked fine. I may have to flash that, it's damned useful...
So now I have a new kernel!
Thanks for all your help
Mr.Clark said:
Apparently it was unsigned, so the stock recovery wouldn't do anything with it.
Back in CWM and it worked fine. I may have to flash that, it's damned useful...
So now I have a new kernel!
Thanks for all your help
Click to expand...
Click to collapse
It is very useful indeed! Enjoy your kernel
Ah, am I right in thinking that if I flash CWM, I can't revert back to stock if I want to?
I'm hoping to do nothing permanent at this point...
Mr.Clark said:
Ah, am I right in thinking that if I flash CWM, I can't revert back to stock if I want to?
I'm hoping to do nothing permanent at this point...
Click to expand...
Click to collapse
Yes, you can flash back. Not only can you but depending on how you did flash the recovery the phone may revert it on your behalf. I know mine has several times, like any time I reboot. There's ways to stop it from doing that but I don't mind.
To get the stock recovery back if it isn't automatically restoring means flashing an NAND from the Dev section here.
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
nicholasbgr said:
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I use overclocked with voodoo and setcpu...you can keep it set to 1000 and not over the stock limit.
Bionix 1.3 is solid and no OC
Sent from my Nexus S using XDA App
nicholasbgr said:
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you flash the Trinity max kernel and do not adjust the clock you will have everything your asking for. This kernel boots at stock and has Voodoo and ext4 built in.
icandy75 said:
If you flash the Trinity max kernel and do not adjust the clock you will have everything your asking for. This kernel boots at stock and has Voodoo and ext4 built in.
Click to expand...
Click to collapse
So your saying the trinity max kernel has voodoo built in?
Sent from my bionix nexus s
mrnexus said:
So your saying the trinity max kernel has voodoo built in?
Sent from my bionix nexus s
Click to expand...
Click to collapse
That is exactly what he is saying, yes =)
Thanks guys, I'm gonna take a look at your recommendations as soon as I get some spare time.
Do all the trinitys have voodoo
Sent from my bionix nexus s
mrnexus said:
Do all the trinitys have voodoo
Sent from my bionix nexus s
Click to expand...
Click to collapse
No, only the most recent ones.
kenvan19 said:
No, only the most recent ones.
Click to expand...
Click to collapse
Such as:
Sent from my bionix nexus s
Hello,
I tried looking everywhere for the stock (default) 2.3.3. kernel (i don't want to flash an entire rom) if anyone know where i can find a link ,i would be most thankful.
thank you.
Goes in Q&A section I think.
Try Q & A thread
Sent from my LG-P999 using xda premium
crazy_agent said:
Hello,
I tried looking everywhere for the stock (default) 2.3.3. kernel (i don't want to flash an entire rom) if anyone know where i can find a link ,i would be most thankful.
thank you.
Click to expand...
Click to collapse
Did you do a backup of the rom before changing the kernel. It is contained in the boot.img in the backup. Just use one of the flashable zips that flash the kernel and replace the boot.img and wireless.ko files from an original nandroid with the one in the flashable zip (ones I looked at the boot.img as in the kernel subdirectory). wireless.ko goes in /system/lib/modules directory. Just use 7-zip and open archive. Delete the boot.img and paste in the one you want. Cloese out 7-zip and then you have a flashable zip with the stock kernel. I have attached the boot.img from the stock GB rom. Make sure you unzip the file and remove the boot.img. Do not try to flash this zip. It won't work.
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
jboxer said:
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
Click to expand...
Click to collapse
If this works it should def go in the dev section, unless it's already there.
Mister Hat said:
If this works it should def go in the dev section, unless it's already there.
Click to expand...
Click to collapse
I will post a thread in the development section once somebody confirms it works. I am pretty confident it will work. Using the same method that is used to flash custom kernels, but I used the boot.img and wireless.ko from the stock GB rom flash.
jboxer said:
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
Click to expand...
Click to collapse
Not sure if I done anything wrong but here are the steps that i did:
- clear cache
- clear Dalvik cache
- flashed the zip file
- reboot
All I got was a black screen. I waited for about 15 mins but still black screen.
saotua said:
Not sure if I done anything wrong but here are the steps that i did:
- clear cache
- clear Dalvik cache
- flashed the zip file
- reboot
All I got was a black screen. I waited for about 15 mins but still black screen.
Click to expand...
Click to collapse
Did you flash it over the stock GB 2.3.3 rom? This is the original kernel and ony compatible with the stock rom. If you are running another rom that would result in a black screen due to incompatibility issues.
I'm using Xboarder's Stock Tweaked OTA Gingerbread build v1.2.2. I don't have the original stock rom. (stupid me, i didn't backup the stock rom before flashed another rom )
Edit: I tried again and it works beautiful. Thank you.
Thank you.
thank you all for your help.
If I am using this forum improperly or asking too many questions on one thread that don't fit together, please inform me kindly.
Stock on 2.3.4 hboot 1.18 I rooted with revolutionary, and installed teamwin recovery. I am using the newest CM7 from the rootzwiki I believe. This is what I flashed anyway - update-cm-7.1.0-SelfKANG10-Sensation-signed.zip. Now I am 2.3.7 kernel ver 2.6.35.13_CyanogenMod+ [email protected] #1
ROM Manager app is now on my phone, but it says I need Clockwork recovery to use it. I also read through google and forums that just flashing between ROMs you have to have like same kernels and stuff like that, which I am very noob too.
I'm having Google framework FC issues and no GPS on CM7.
I think I want to switch from CM7 to this MIUI zip I got at MIUI.us - MIUI.us_pyramid_1.12.9.01_Eng_Deo_ZipA_Signed.zip
Which recovery SHOULD I be using? If clockwork is way to go, can I just go to my ROM manager app where it says, "flash Clockwork to this phone"?
If I want to change ROMs, what do I need and NOT need to backup? What exactly is "nandroid" back up, is it better than backup apps? Do I need to backup ROMs, and what exactly is that and what is proper way?
Do I have to wipe then restore everytime? Had some issues with this first time from stock sense to CM7, couldn't get Titanium or mybackup pro to restore my apps, and my contacts are quadrupled in size and organized oddly.
What is the best way to switch ROMs, flashing, ROM Manager, something else?
IF I wanted to run only one ROM for lets say 6 months, after I flash it, can I delete that zip from sd card, and phone will still work?
Suggest a ROM for me if you like also
_DavidWebb said:
If I am using this forum improperly or asking too many questions on one thread that don't fit together, please inform me kindly.
Stock on 2.3.4 hboot 1.18 I rooted with revolutionary, and installed teamwin recovery. I am using the newest CM7 from the rootzwiki I believe. This is what I flashed anyway - update-cm-7.1.0-SelfKANG10-Sensation-signed.zip. Now I am 2.3.7 kernel ver 2.6.35.13_CyanogenMod+ [email protected] #1
Click to expand...
Click to collapse
So standard CM7, use the CM7 thread here on XDA as the reference.
ROM Manager app is now on my phone, but it says I need Clockwork recovery to use it. I also read through google and forums that just flashing between ROMs you have to have like same kernels and stuff like that, which I am very noob too.
Click to expand...
Click to collapse
I personally don't use ROM Manager but use ClockworkMod alot. There is a thread here on CWM 5.0.2.0 somewhere, if I remember I'll add it.
Kernels need to be Compatible with the ROM. This compatibility requitement is in terms of Kernel revision (i.e. old Kernel might not work with a newer ROM). More importantly though there are two basic typed of ROM on the Sensation, namely Sense and AOSP based ones. These two varieties have completely different Kernels so you will need one from that branch. For example Faux makes two Kernel types AOSP (e.g. for CM7 and MIUI) and all the Sense derivatives.
I'm having Google framework FC issues and no GPS on CM7.
I think I want to switch from CM7 to this MIUI zip I got at MIUI.us - MIUI.us_pyramid_1.12.9.01_Eng_Deo_ZipA_Signed.zip
Which recovery SHOULD I be using? If clockwork is way to go, can I just go to my ROM manager app where it says, "flash Clockwork to this phone"?
Click to expand...
Click to collapse
I'd just install CWM directly from the PG58IMG.zip file, but as I said I don't use ROM Manager.
If I want to change ROMs, what do I need and NOT need to backup? What exactly is "nandroid" back up, is it better than backup apps? Do I need to backup ROMs, and what exactly is that and what is proper way?
Click to expand...
Click to collapse
The Nandroid backup performs a backup of the various phone partitions onto the SD-Card. This allows for a point in time backup and recovery of the phone.
ALWAYS do a Nandroid backup before playing with a new ROM or Kernel, JUST IN CASE **** happens.
Do I have to wipe then restore everytime? Had some issues with this first time from stock sense to CM7, couldn't get Titanium or mybackup pro to restore my apps, and my contacts are quadrupled in size and organized oddly.
Click to expand...
Click to collapse
Never had this issue with contacts, I keep all mine synced with gmail. New ROM and they automatically update. I don't often use TB, others can probaby advise.
What is the best way to switch ROMs, flashing, ROM Manager, something else?
Click to expand...
Click to collapse
I manually install the ROM Zip from CWM then wipe cache, Dalvik Cache and Fix permissions, YMMV.
IF I wanted to run only one ROM for lets say 6 months, after I flash it, can I delete that zip from sd card, and phone will still work?
Click to expand...
Click to collapse
Yes
Suggest a ROM for me if you like also
Click to expand...
Click to collapse
Depends if you want a Sense or ASOP based phone.
Ok ill try to hit all the points for you. First you can use any recovery you like (cwm, twrp, 4ext) but Rom manager will only work with cwm. You can get to your recovery 2 ways, either hold the power button and select reboot then recovery (note some roms don't have this) second power off your phone completely and hold vol down and power until you get to hboot and select recovery (note fastboot must be turned off in settings). Personally I don't recommend using Rom manager to flash your roms go to the recovery itself.
Flashing roms: it is recommended to wipe data wipe cache and wipe dalvik cache (its sometimes found under advanced like in cwm) and when you get that part down it isn't always neccesary but wipe system partition... Never ever wipe anything else... Unless your cleaning your battery stats but let's stick to the basics.
If you are just flashing an update to a Rom sometimes you don't have to wipe anything (i.e. cm7 v9 flashing to cm7 v10) but anytime you change Rom bases always wipe. Especially if you are going from cm7 to a sense 3 Rom and also sense 3.5 and vice versa. Also there are several superwipe files from several devs. I suggest using one of these. All you do is flash it like a Rom in recovery. They automatically wipe for you.
Kernels are labeled with the base you need I.e cm7 or sense review the kernels threads for more info.
Next, if you haven't wiped and tried a couple Roms that explains the contact problems and GPS issues.
A nandroid put simply is just a backup of your current Rom. Go to backup in your recovery and backup your current Rom. Is saves every little bit of your current Rom. You need to do this in case something goes wrong or if you don't like the new one. Then you can simply restore it if you need to.
After you flash a Rom it is in your phones memory. You can delete it off your sdcard no problems, unless you want to flash it again at another time. You can also delete old nandroids if you need to just keep at least the last one you made. They are large sometimes.
I have used about every Rom here I suggest mikes hdrevolution or cdtdroids Roms if you don't want cm7 (which is often referred to as aosp) if you want to try another aosp Rom try hypersensation it works good too.
And you used this forum perfectly asking questions in the q&a good job some people don't get that.
Edit: he beat me to the answers while I was typing lol. Also I hate autocorrect had to clean up my post hope it didn't confuse you.
Sent from my HTC Sensation XE with Beats Audio using xda premium
gol_n_dal;20335770
The Nandroid backup performs a backup of the various phone partitions onto the SD-Card. This allows for a point in time backup and recovery of the phone.
ALWAYS do a Nandroid backup before playing with a new ROM or Kernel said:
I also can't get the multi quote to work like you did, how does that work lol?
Click to expand...
Click to collapse
Ok, this forum is awesome, and I will defintely check out the other forums for kernels and other topics. I am understanding most of your replies, but as you see I get other questions from some answers lol. I did just wipe everything(data factory reset) again, and installed the MIUI and when I signed in my google on setup, all my apps started downloading from market and my contacts were all there in a little bit better fashion than before. Also, when I put CM7 that was my FIRST ROM and immediately after my FIRST time attempting and successfully doing a root s-off. Now MIUI makes my 2nd ROM. I'm sure if I hang around here enough I'll get the hang of it all and start to figure it all out better. I vultured around these forums for 4 months with a stock phone before I did anything, and my phone isn't bricked so I'm happy about that.
For some more detail try checking out the stickies in the development section there are some awesome guides and answers there too.
Sent from my HTC Sensation XE with Beats Audio using xda premium
RESOLVED
This is 4th brick and i normally know how to fix it but this time i cant fix it
Ok so one day my phone was acting up it wouldn't turn on
I flashed repartioned and flashed csc/phone/froyo from hawk (ODIN) - everything was ok
Then i flashed gingerbread (odin)- phone turned on everything worked
Afterwards i rooted it (super one click)- it worked
got sgs kernel flasher
Flashed antonx kernel for gb
when i tried to install cm9 it didnt work i checked logs and got this (im using cmr 6.0.1.2)
I: Cant partition unsafe device: /dev/block/mmcb1k0p
I:Cant format unknown volume :/external_sd
I: cant format unknown volume: /emmc
Any ideas?
Also i was trying to do this
flash froyo + everything from hawk
Flash gingerbread
root
get sgs kernel flasher
flash kernel
install cm9
install cm10
restore my cm10 backup
That's a lot of steps that aren't needed.
http://forum.xda-developers.com/showthread.php?t=1358498 2nd post, eollie's one click to stock.
1)Run that, you have stock GB, root, and CWM all in 1 click.
2)Reboot to recovery, wipe and install CM9
3)Profit??
Ill try that
getochkn said:
That's a lot of steps that aren't needed.
http://forum.xda-developers.com/showthread.php?t=1358498 2nd post, eollie's one click to stock.
1)Run that, you have stock GB, root, and CWM all in 1 click.
2)Reboot to recovery, wipe and install CM9
3)Profit??
Click to expand...
Click to collapse
Thanks for the quick reply ill try that
What CM where you trying to install? Are phone doesn't use /emmc or /external_sd. That's why it failing. Wrong zip from the wrong phone. Look under your battery and tell us what the model number says before you go any further and end up with a true brick.
cmr
... after i installed antonx's kernel i tried to install cyanogen mod 9 and i was using the recovery included in that
And yes i know what phone i have.. sgs4g (sgh-t959v)
What Cm9? It's trying to write to partitions that this phone doesn't use. Link the ROM please.
link
Here you go
http://forum.xda-developers.com/showthread.php?t=1730954
That's really weird that your getting those errors. We don't use emmc or external_sd. Heimdall will get you set back up but I've never seen ANYONE in all the time I have had this phone report that error. That's why I was trying to make sure you had the right phone and ROM before you went any further.
now what?
hechoen said:
That's really weird that your getting those errors. We don't use emmc or external_sd. Heimdall will get you set back up but I've never seen ANYONE in all the time I have had this phone report that error. That's why I was trying to make sure you had the right phone and ROM before you went any further.
Click to expand...
Click to collapse
Ok so im back onto stock 2.3.6 and rooted... what kernel do i install? oh yea and hermdal doesnt want to work something net framework isnt installing (keeps on failing) and ive tried downloading it from microsoft too
Well, since antons didn't seem to work for you, flash the other one. lol
http://forum.xda-developers.com/showthread.php?t=1828171
-
how do i go from stock to mtd rom? (im on the "other one" i have a 32 gig sd card with EVERY single rom on that list, every kernel, every modem so basicly i dont have to download them)
before i just installed it through cmr but is that right?
I want to go from stock to cyanogen mod 9 MTD
Im creating a backup right now incase i mess up later
That's will work as long as the recovery is CWM 5.x or later. You used to have to flash CM7 first but I'm pretty sure Team Acid fixed it in the new CM9 build. Just check the MD5 of that zip you where trying to flash. Those errors are very strange and I'm thinking you might have accidentally gotten the wrong CM9.
hechoen said:
That's will work as long as the recovery is CWM 5.x or later. You used to have to flash CM7 first but I'm pretty sure Team Acid fixed it in the new CM9 build. Just check the MD5 of that zip you where trying to flash. Those errors are very strange and I'm thinking you might have accidentally gotten the wrong CM9.
Click to expand...
Click to collapse
Ok im installing..
Also if this works can i just restore my cm10 backup? or do i have to install cm 10 then the backup?
You can try to restore it. If it's the same version of CWM that you backed up from it should work. Just do all the wipes including system and data before you restore. If that doesn't work for some reason just flash CM10 than do an advanced restore of data only.
Works
ok it works... cid kinda scares me
I guess im going to restore my cm10 backup then...
And thanks for all the help
wow i have to wait five minutes between posts that sucks
restore
got an err when trying to restore E:/format_volume: format_rfs_decive failed on system
Guess im going to install cm10 then restore
What an exciting day... i went from froyo to gingerbread to ics and now to jb
Ahh
Ok so i found out that when i flashed kc1 to kc6 on odin i left the repartiton checked... so some files were missing and i guess that was the problem... what is phone efs clear on odin again? isnt it have to do with something with celluar communications
ok everything is back to normal (except a few apps) And thanks for helping out!
Some apps don't restore. Like xda for example. If I restore a backup it will say app not installed. When I reDL it from Play all my settings are still there though. So it's saving the cache and not the app. I've never really cared enough to look into it. lol
I backed up my sgh t959v before installing custom rom. When i wanted to restore it error comes can't mount cache. please give me solution. i have already done cwm updat.
How did you back it up?
What ROM did you have previously?
What ROM did you install?
Why do you believe that the backup can be restored over the new ROM?
i backed up my phone by cwm recovery. I have custom kernel installed 5.x.x . I used the rom slimsaber 4.4.2 . Help me cause I'm not a pro like u. Thanx in advance
Sent from my SGH-T959V using xda app-developers app
My first guess is that the kernel from Slim doesn't partition the disk the same way as most other ROMs for our phone.
If you can be very specific about what you've done and what you want to accomplish, we can probably get you there. ROMs and versions will be very important
---
Posted from whatever phone booted today
SlimSaber-galaxys4gmtd-4.4.2-20140207
This is the rom i used and
my kernel version was 2.6.35.7-T959VUVKJ6-antsvx.v1.1.3
help man @jeffsf . U r a pro man plz figure out my prob
Sent from my SGH-T959V using xda app-developers app
Both Roms use different partitions. Kj6 is bml and saber is mtd. It ain't gonna happen.
In order to restore you'll first need to flash back to stock kj6. Then install antonx's kernel (or blastoff) and then you'll be able to restore using cwm.
That's about the long and short of it. All ICS, JB, and KK ROMs use a low-level way ("MTD") of accessing the internal "disk" that isn't compatible with the older "BML" method found in OEM ROMs and other Froyo and many GB ROMs. Additionally, Dao's recent KK ROMs use a subtly different version of MTD than other MTD ROMs.
While you could restore /system and /data from one major release to another, this is not recommended. It's dicey going up in version and then restoring (for example, from ICS to JB), and likely impossible going back. A tool like Titanium Backup (Pro) can help, but sometimes you're just stuck.
The general way of dealing with an internal "disk" change is (not including backup/restore):
Boot to recovery
Install the new kernel (can be "flash the ROM")
Reboot to recovery
Format all internal partitions
Install the ROM
Boot into the ROM
You generally will need app-level backups (for example Titanium Backup) to transition your data.
Going from BML to MTD worked on Team Acid MTD ROMs, such as CM9. I can't comment on other ROMs.
To go from MTD to BML a full re-flash using heimdall or the like is recommended.
To go between Froyo and Gingerbread absolutely requires re-flash -- see other threads for details.