I remember seeing over in the Dev. forums that CWM recovery isn't restoring the kernel properly when people try to restore their backup of the stock ROM
Does this happen with TWRP as well? Or is the issue with the stock ROM / Kernel?
I'm hesitant to try CM9 and would like a clean way to recover to the stock ROM without having to use the downgrade method and reinstall everything.
edgemaster191 said:
I remember seeing over in the Dev. forums that CWM recovery isn't restoring the kernel properly when people try to restore their backup of the stock ROM
Does this happen with TWRP as well? Or is the issue with the stock ROM / Kernel?
I'm hesitant to try CM9 and would like a clean way to recover to the stock ROM without having to use the downgrade method and reinstall everything.
Click to expand...
Click to collapse
From what I read in the CM9 thread someone had the same issue when using TWRP.
Nandroids don't include the kernel i believe it must be restored seperately
It should, wouldn't that be in boot.img? I know on my Droid Inc I have gone between sense and aosp backups, both using different kernels.
Sent from my ADR6300 using Tapatalk 2
Related
I am new to the nexus s , but have been a heavy galaxy s user. I noticed that flashing roms etc is a bit different from what I am used to on my galaxy s .. I did not see any thread containing stock kernels ... So how can I return to stock after I have flashed another kernel ? I have installed the voodoo kernel with ext4, sound and colour enhancement .. But suppose I want to return to my stock gri54 kernel , how can I do that ? Have read allready about fastboot etc etc but then I should have an .img of the stock kernel , correct ?
By flashing back to stock rom, you will get back your stock kernel automatically.
Sent from my Nexus S using Tapatalk
navlem said:
By flashing back to stock rom, you will get back your stock kernel automatically.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
So by flashing back to stock ROM via recovery, does it mean that it will be locked and un-rooted as factory default [like when you first purchase the device]?
navlem said:
By flashing back to stock rom, you will get back your stock kernel automatically.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
But will i not loose everything if i do it like that? And where can i find stock rom. I only found an odin package
Sent from my Nexus S using XDA Premium App
johnkim0011 said:
So by flashing back to stock ROM via recovery, does it mean that it will be locked and un-rooted as factory default [like when you first purchase the device]?
Click to expand...
Click to collapse
It will be unrooted, but still with unlocked bootloader.
Bandis710 said:
But will i not loose everything if i do it like that? And where can i find stock rom. I only found an odin package
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
The Odin package can put you back to stock rom too.
So what you are saying there is no way to flash only the stock kernel ?? Very confusing .. I am able to flash just another kernel using fastboot but I am not able to flash back the stock kernel using fastboot ? Odin is a last resort method .. haven't seen fastboot .img files of the stock here in the forums ?
I'm not sure if anybody posted any stock kernel file in the forums. If there is any, you can easily download it and install via recovery or fastboot.
Otherwise you can only revert to stock roms because stock roms links are easily available through the forums or samsung firmware website.
Or after you have failed everything, may want to consider Odin. It seems to touch the phone at a lower level compare to other techniques.
follow the instruction on this
http://www.samfirmware.com/WEBPROTECT-i9023.htm
work great for me after all
Samsung i9023
Good luck
Yeah , I also mentioned odin allready .. Used it a lot when I had my galaxy s .. Just thought that since the nexus s can use fastboot I could get rid of odin ..
I am also not used that all has to be flashed to achieve a single goal .. On the galaxy s I could flash the kernel separately and also stcok kernel were easy to find .. I think it is kind of a hassle to reflash a whole rom just because you want stock kernel back ..
Voodoo has stated that his kernel is 'almost' stock, with only voodoo addon to the pure stock kernel. Maybe you can use that?
Some news here?
Hi there!
I was also wondering about this same situation. Let's say I want to stick with the original ROM and try some non-stock kernels. After some tests I know there is an OTA available but I don't want to backup and restore everything (using TB or similar). From what I understood I wouldn't be able to flash stock kernel (in other words, back to full stock ROM + Kernel) and apply OTA update...
What if we just flash boot.img from a nandroid of stock rom+kernel?
RM
Here you go: http://forum.xda-developers.com/showpost.php?p=20442919&postcount=3
Sent from my Nexus S using XDA App
Hoo great!
but, can you tell us where to find or how to get it from the stock ROM and make it flashable? It might be useful for upcoming releases of stock ROM/Kernels.
Thank you once again,
RM
edit: after searching by the filename you gently provided I found this:
hxxp://www.android-hilfe.de/2277361-post1.html
hxxp://www.michalurban.cz/Nexus_S_i9023/Kernel/
seems to be a good compilation, and stock is in the list!
The file I posted is already flashable through CWM. Just wipe dalvik first. Of course make sure you have a Nandroid backup just in case.
Hi,
sure, I noticed that. What I was wondering was how to get this flashable kernels. From the stock ROM full installation file? From a nandroid backup of a stock ROM??
RM
Hi, is any chance to get stock kernel for Jelly Bean 4.1.1? I've got stock rom, Air Kernel and OTA is buzzing me multiple times a day. No luck in upgrade, Error Status 7. I think it's Air Kernel's fault.
0mn1us said:
Hi, is any chance to get stock kernel for Jelly Bean 4.1.1? I've got stock rom, Air Kernel and OTA is buzzing me multiple times a day. No luck in upgrade, Error Status 7. I think it's Air Kernel's fault.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1572307
Flash factory. Easy.
Sent from my Nexus S using xda premium
RESOLVED!
I flashed cm7, but not without making a nandroid of the stock rom. I tried restoring the backup and it would not make it to the boot animation. No errors or anything, same version of clockwork as before.
The only thing I didn't try was advanced restore. Would that do anything differently?
Sent from my HTC Glacier using XDA App
kimbernator said:
I flashed cm7, but not without making a nandroid of the stock rom. I tried restoring the backup and it would not make it to the boot animation. No errors or anything, same version of clockwork as before.
The only thing I didn't try was advanced restore. Would that do anything differently?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Being that you flashed CM7, and having troubles going back to 2.2.x you must be using 3.0.0.5 as a recovery image. You need 3.0.0.6, or a 2.x recovery image.
This thread [http://forum.xda-developers.com/showthread.php?t=986522] will help explain the ins and outs and how to flash 3.0.0.6.
Hey! I figured it out! And this should apply to all of us with mytouch 4gs.
The issue was that i was on clockwork 3.0.0.5, which i was on even when i backed up the stock rom. 3.0.0.5 allows for gingerbread flashing, but not froyo. So if you experience an issue like this, downgrade to 2.5.1.2 in rom manager and try recovering - lucky for me, even nandroids made in 3.0.0.5 were compatible with 2.5.1.2
kimbernator said:
Hey! I figured it out! And this should apply to all of us with mytouch 4gs.
The issue was that i was on clockwork 3.0.0.5, which i was on even when i backed up the stock rom. 3.0.0.5 allows for gingerbread flashing, but not froyo. So if you experience an issue like this, downgrade to 2.5.1.2 in rom manager and try recovering - lucky for me, even nandroids made in 3.0.0.5 were compatible with 2.5.1.2
Click to expand...
Click to collapse
That's what the thread i posted earlier explained. and showed you how to fix. It's sticked in the Q&A section.
What a breakthrough that was...I better write that down.
So I'm about to flash a custom rom an I'm confused about flashing the roms an kernels. I'm already rooted and know to flash recovery via ez recovery. I plan on running Synergy. Is there anything else I should do prior to flashing roms, specifically synergy? I know these roms are built for the what was locked bootloader so do these roms just flash the stock kernel when you flash the rom? Thanks
Sent from my SCH-I535 using xda app-developers app
Boot into recovery and Make a backup of your current setup. Then wipe data and cache and dalvik. Then flash the Rom. If it asks you to skip or disable recovery flash upon trying to reboot click yes.
Thanks. Yeah I got all that but more concerned if I need to flash a kernel with the rom. I also here about backing up the IMEM or something like that.
Sent from my SCH-I535 using xda app-developers app
You don't need to flash a kernel with Synergy. Just flash the ROM (with proper backup and recovery of course)! You also don't need to worry about IMEI for now. There was a backup process with the efs partition, but people have just been rewriting it with QPST if they lose it. Have fun!
Bleelas said:
You don't need to flash a kernel with Synergy. Just flash the ROM (with proper backup and recovery of course)! You also don't need to worry about IMEI for now. There was a backup process with the efs partition, but people have just been rewriting it with QPST if they lose it. Have fun!
Click to expand...
Click to collapse
Thank you!
Sent from my SCH-I535 using xda app-developers app
No prob! Just for a little more information, you CAN backup your efs partition and restore it still, but the issues have been with AOSP ROMS. It probably a good idea to do it, but considering you're talking about Synergy and there's a way to rewrite it, you probably don't NEED to. Also, as far as flashing kernels, the ROM threads usually say if they also come with a kernel or not, whether they need kexec or not (soon a thing of the past!), and what kernels they are compatible with. Generally speaking, a TW ROM needs a TW kernel (like the stock kernel), and an AOSP ROM needs an AOSP kernel.
The last option to backup your IMEI is:
http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/
I'd go ahead and do it and then you don't need to worry
All good information I've been exactly looking for lol. But yeah the whole kexec thing has really confused me.
Sent from my SCH-I535 using xda app-developers app
tu3218 said:
So I'm about to flash a custom rom an I'm confused about flashing the roms an kernels. I'm already rooted and know to flash recovery via ez recovery. I plan on running Synergy. Is there anything else I should do prior to flashing roms, specifically synergy? I know these roms are built for the what was locked bootloader so do these roms just flash the stock kernel when you flash the rom? Thanks
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Look in the developer forum for this phone, droidstyle did an amazing step by step for doing a few things for the sgs3
Sent from a Galaxy far, far away...
I just recently installed an official cyanogen mod for my phone and I wanted to restore my system, files, everything.
Don't get me wrong though.. I tried using Nandroid Backups I back it up before flashing, installed the rom properly after flashing.
My problem is, what should I use in restoring my system files without reverting back to my old rom?
Thanks.
kliff39 said:
I just recently installed an official cyanogen mod for my phone and I wanted to restore my system, files, everything.
Don't get me wrong though.. I tried using Nandroid Backups I back it up before flashing, installed the rom properly after flashing.
My problem is, what should I use in restoring my system files without reverting back to my old rom?
Thanks.
Click to expand...
Click to collapse
I do not understand you. Make a backup in CWM and then when you want to restore the ROM, in CWM make a restore.
ZmisiS said:
I do not understand you. Make a backup in CWM and then when you want to restore the ROM, in CWM make a restore.
Click to expand...
Click to collapse
Okay imagine this.. My current rom is cyanogen by tj styles and i wanted to use the official cyanogen rom.
So what I did, I backed up my files using CWM and tried to flash another rom (official cyanogen) . When I did successfully, I tried restore using CWM and after that.. I'm only back to my old rom. (cyanogen by tjstyles)
So my question is, how can i switch to a new ROM without losing my files?
Titanium backup
- Via xda premium
a.cid said:
Titanium backup
- Via xda premium
Click to expand...
Click to collapse
but apps gives fc ....isn't it?
Suranjan16049 said:
but apps gives fc ....isn't it?
Click to expand...
Click to collapse
Only system apps will give fc if you restore them + their data...
On most roms, normal apps will not give fc...
They fc the most if the rom has some memory hack implemented...
- Via xda premium
First of all, forgive my sluggishness as i didn't use TWRP to backup the previous rom and flash the new one.. I used clockworkmod..
So now other than having /0/ folder, i can't restore the backup because cwm recovery can't find it..
But apart from that im still fine with this aosp rom.. I was going to give it a try after all..
So what are my options? Is there a way to get cwm to read the backup?
Or, If that's not possible, if i flash twrp recovery then use it to cleanly flash a TW based rom, can it read the new storage format?
EDIT: i had the CWM backup copied to my SDcard, it restored fine now, carry on
Mod please close..
Sent from my GT-N8000 using XDA Premium HD app