Related
I figure this is a development question but if this needs to be moved feel free to do so mods. I compiled AOSP GB no problem but now it's bootlooping whenever I try to start it up. It doesn't even get past the first boot screen so ADB isn't even available. I thought it might be a kernel issue but I tried the CM7 kernel, stock kernel and stock GB kernel. No avail. I compiled GB for the Evo no problem before but it's not working now. Any ideas?
chuckhriczko said:
I figure this is a development question but if this needs to be moved feel free to do so mods. I compiled AOSP GB no problem but now it's bootlooping whenever I try to start it up. It doesn't even get past the first boot screen so ADB isn't even available. I thought it might be a kernel issue but I tried the CM7 kernel, stock kernel and stock GB kernel. No avail. I compiled GB for the Evo no problem before but it's not working now. Any ideas?
Click to expand...
Click to collapse
You have been around dd for awhile, so I will not ask if you did a full wipe before you flashed the ASOP GB (faux?).
But if you have tried flashing all those other ROM' it may be time to do it again. Also, after flashing an Ext4 kernel, you will generally not be able to flash successfully any of the Ext3 kernel ROM's you mentioned above. You would have to restore an Ext3 nandroid first
You did not say if you had a nandroid on you SD. If not, you may have to put one on - the only one I know of is on a thread in the development section. But this will take you back to square one - unless you had an app backup program on the SD like titanium.
gaww said:
You have been around dd for awhile, so I will not ask if you did a full wipe before you flashed the ASOP GB (faux?).
But if you have tried flashing all those other ROM' it may be time to do it again. Also, after flashing an Ext4 kernel, you will generally not be able to flash successfully any of the Ext3 kernel ROM's you mentioned above. You would have to restore an Ext3 nandroid first
You did not say if you had a nandroid on you SD. If not, you may have to put one on - the only one I know of is on a thread in the development section. But this will take you back to square one - unless you had an app backup program on the SD like titanium.
Click to expand...
Click to collapse
Yeah I had a nandroid and everything. I'm thinking it has to be a kernel thing so I'm going to try a nandroid backup to the stock rom and then see if flashing works. I'll keep ya'll updated. Thanks.
So i was just wondering but how does CM9 have a kernal if we dont have an ICS kernal?
bradman117 said:
So i was just wondering but how does CM9 have a kernal if we dont have an ICS kernal?
Click to expand...
Click to collapse
It is in the boot.img. So far all Infuse cm9 is based of jt or entropy branching off jt. If you want just the kernel, after you f flash the ROM, you can dump the kernel from bml 7 using dd commamd.
Jt recover ics is such a kernel. Check my thread for the heimdall packed.
Jscott also extracted entropies kernel and i packed into a heimdall 1 click also. I haven't had a chance to test it yet. Pm me if you want a shot at it.
I think having these kernel in a heimdall makes flashing and recovery from cm9 simple.
Dl mode. Flash. factory reset. And it's ready for cm9 ROM.
qkster said:
It is in the boot.img. So far all Infuse cm9 is based of jt or entropy branching off jt. If you want just the kernel, after you f flash the ROM, you can dump the kernel from bml 7 using dd commamd.
Jt recover ics is such a kernel. Check my thread for the heimdall packed.
Jscott also extracted entropies kernel and i packed into a heimdall 1 click also. I haven't had a chance to test it yet. Pm me if you want a shot at it.
I think having these kernel in a heimdall makes flashing and recovery from cm9 simple.
Dl mode. Flash. factory reset. And it's ready for cm9 ROM.
Click to expand...
Click to collapse
I've used your heimdal package of the ics kernel multiple times as I constantly brick my phone trying to port and have to go back to stock...I then flash the ics kernel and I'm back up and running ready for ics...I just wish I could only flash the kernel...always gotta go back to stock first...but with your heimdal I'm back up and running in no time
Sent from my SGH-I997 using XDA
As for the kernel...as far as I know it isn't a full on ics kernel...it is a gingerbread kernel that has been heavily modified to run ics however it will not work with gingerbread any longer...
So its an ics kernel created from a gingerbread kernel...insane development going on there...got tons of respect for jt and entropy getting that done...
Sent from my SGH-I997 using XDA
mg2195 said:
I've used your heimdal package of the ics kernel multiple times as I constantly brick my phone trying to port and have to go back to stock...I then flash the ics kernel and I'm back up and running ready for ics...I just wish I could only flash the kernel...always gotta go back to stock first...but with your heimdal I'm back up and running in no time
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
I don't think you need to go back to stock with system files that you will overwrite anyway.
Flash just the kernel. Wipe.
And flash the ics.
Maybe use entropy kernel flash then a jt kernel if you can't recover with only jt.
qkster said:
I don't think you need to go back to stock with system files that you will overwrite anyway.
Flash just the kernel. Wipe.
And flash the ics.
Maybe use entropy kernel flash then a jt kernel if you can't recover with only jt.
Click to expand...
Click to collapse
What do you mean by an entropy kernel flash then a jt? I've tried just flashing the jt one you have and no matter what rom I flash...when I hit that reboot button it will always boot back to recovery...
Anyways im back up and running in under 10 minutes...so its nothing to complain about...
Sent from my SGH-I997 using XDA
mg2195 said:
What do you mean by an entropy kernel flash then a jt? I've tried just flashing the jt one you have and no matter what rom I flash...when I hit that reboot button it will always boot back to recovery...
Anyways im back up and running in under 10 minutes...so its nothing to complain about...
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
I'm not sure if we're talking about the same thing but:
Let say you tried a port or build and got into a boot loop. Or lost recovery, you don't necessarily have to flash the whole stock package.
In my kernel root thread, post #3. Flash the Jt kernel in download mode. That should bring you n back to recovery from boot loop or lost recovery with the three finger combo.
I've noted that since Jt kernel has the cwm 5.xxx sometimes it doesn't do the trick. If that was the case, I would flash the entropy in download mode..post #2..in the uclb3 thread.
That will also give you cwm recovery without having to flash the whole stock base.
Boot into recovery, wipe and/or mount and you are set to flash the next experimental build. Just be sure to have a couple of different builds to test on your sdcard.
Once you flash what ever build or ROM, it had it's own kernel and system file to write over your current. In this case, it would not matter, as you are not working with a system file...only the recovery.
Edit: it would also make sense of you created a mg_lite ROM for debug if you needed to have the phone system. Make a ROM with minimal stuff. Turn off boot ani. Have only minimal apps..no email or gmail or bt fb or any crap that would allow down the boot and dalvik process. Only a few system files and libs are needed. That way you can save some time instead of going back to the whole stock process
qkster said:
I'm not sure if we're talking about the same thing but:
Let say you tried a port or build and got into a boot loop. Or lost recovery, you don't necessarily have to flash the whole stock package.
In my kernel root thread, post #3. Flash the Jt kernel in download mode. That should bring you n back to recovery from boot loop or lost recovery with the three finger combo.
I've noted that since Jt kernel has the cwm 5.xxx sometimes it doesn't do the trick. If that was the case, I would flash the entropy in download mode..post #2..in the uclb3 thread.
That will also give you cwm recovery without having to flash the whole stock base.
Boot into recovery, wipe and/or mount and you are set to flash the next experimental build. Just be sure to have a couple of different builds to test on your sdcard.
Once you flash what ever build or ROM, it had it's own kernel and system file to write over your current. In this case, it would not matter, as you are not working with a system file...only the recovery.
Edit: it would also make sense of you created a mg_lite ROM for debug if you needed to have the phone system. Make a ROM with minimal stuff. Turn off boot ani. Have only minimal apps..no email or gmail or bt fb or any crap that would allow down the boot and dalvik process. Only a few system files and libs are needed. That way you can save some time instead of going back to the whole stock process
Click to expand...
Click to collapse
Taking a vacation for memorial weekend...but I'll give what you suggested a try Monday night...if I happen to soft brick...
Sent from my SGH-I997 using XDA
I'm having a problem flashing marmite 4.4 to the newest miui build (2.9.7).
Basically in cwm recovery and flashed the kernel.
Will say "ununderstandable message 3" and "lid is licked"
Reboot the device and it will get stuck on the miui boot screen.
Tried installing both the "stock OTA" and "All other ROM" version of marmite.
Same message comes up.
Already tried performing a full wipe (actual full restore, format system, format boot), reload the ROM.
Tried wipe cache and dalvic (even though it is not needed)
Just wondering if there is something incompatible or not.
I was able to flash air kernel without issues.
I haven't tried an older version of marmite yet, but will try later.
I'm not blaming marmite, it could be miui as well, or it could be just me.
I'm certain I'm flashing correctly.
I read bedalus' marmite post and saw 2 others with this issue (not same version of kernel or ROM).
The suggestion was that they didn't use the correct kernel for ROM.
I would assume miui would not be categorized as "stock OTA", so I tried "all other ROM" version first"
Am I doing something wrong?
There is a new version 4.5 the message you get I believe is like a joke. It does show however that the installation was successful.
Never experienced boot loops flashing his kernels.
Sent from my Nexus S
Actually, I downloaded that one just now to try and same issue.
It will just stall at the miui (ROM) boot screen.
I am trying some other stuff right now as well.
Really want to use this kernel. :good:
I'll report back later.
Thanks for the help.
Good luck. His kernel offers great speed and stability!
Sent from my Nexus S
For marmite 4.5, did a full wipe again, even formatted the SD partition.
So flashed miui 2.9.7.
Booted to the ROM.
Made sure things seem normal in the ROM.
Restarted just to be sure.
Boot back to recovery.
Flashed marmite 4.5
And it is stuck on the miui loading screen again.
Only thing I haven't tried this time is to fix permissions. (didn't wipe cache or dalvic either)
I'll try it again. :laugh:
Since I formatted the SD partition, it should rule out that it was something on the SD card right?
It's time consuming to copy things back to the NS.
I'll try an older version of marmite afterwards and then an older version of miui.
It should tell me what is causing the lock up by then. I think. :silly:
.... yes I have a lot of time ....
I forgot to mention one thing.
I'm flashing the official Chinese version of miui 2.9.7.
Wonder if that's the cause.
I guess I will download the US or UK version to try as well.
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
kwibis said:
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
Click to expand...
Click to collapse
Took some time to test, but sort of found my answer.
It's the official Chinese miui that's causing the issue.
Well at least some component in the ROM.
I tested with the MIUI UK (miuiandroid) version 2.9.7 and it installed like a charm.
Before flashing the UK version, I tested with earlier versions of marmite (4.3 and 3.5) on the Chinese 2.9.7.
All failed at the ROM boot screen.
I should check with the miuiandroid team and see what they changed that made it different.
When I was testing I did a full wipe, installed ROM, booted ROM, boot to recovery and flashed the kernel.
I didn't even wipe cache or dalvic (which is not needed anyways).
I had to do a full wipe because the ROM just wouldn't boot back up afterwards.
I'm tempted to test with an earlier version of the official Chinese miui and see if it makes any difference.
... too much time and/or no life ... :laugh:
Lol, well it's good you found your answer So its not a waste lf time as you learn from this
Sent from my Nexus S
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Articudos said:
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Not sure what the boot.img type is, but I'll look it up. Thanks.
I posted on miuiandroid forums and someone replied saying that the Chinese version is odexed and not busyboxed.
UK and US version is definitely deodexed, I downloaded them and checked. I haven't found out how to check busybox.
I have a few choices.
1. I can use the UK or US version, since I was able to flash marmite on them... easy way out.
2. Find out how to deodex the ROM and, I guess, how to add busybox (?)... I get to learn more stuff.
3. Use a way faster ROM (eg. Paranoid Android - great ROM by the way!) and flash marmite on it as well... but really want to use miui again.
Thanks guys for your help though. Really appreciate the information. :good:
Glad you found a solution
Hi xda. I just installed (flashed) cyanogenmod 9 on my nexus s, after getting bored with the stock kernel so I flashed trinity ics kernel. Now when I try and flash a new kernel nothing changes, cwm recovery said it flashed successfully. The procedure I did when I installed it was:
1) install zip from SD card
2) choose zip
3) yes
4) reboot system
Is there anything I did wrong? Do i need to clean the cache and dalvik cache?
Sent from my Nexus S using xda premium
How are confirming that it did not flash?
Clockwork recovery said it was successfully installed. Also the version of the kernels are right for my rom (ics)
Sent from my Nexus S using xda premium
You missed understood me.
How are you checking/confirming that the kernels you flashed after trinity are not actually flashing/ booting/being used or how ever you want to phrase it?
cm changed their ramdisk(again). so now custom kernels without cm ramdisk wont boot cm. as always, cm likes to "break" things. complain to cm. i recommend other non cm based roms, like rasbean jelly. it doesnt have as much junk included and is a faster/smoother experience than cm. many kernel developers arent willing to cater to cm anymore because of these changes they constantly make. enough is enough.
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
maybe so, bit i dont see a mention of a boot animation
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
ah, ok. i reread the op very slowly.
op, did you check the kernel version in your about phone? other kernels wont get rid of the boot animation unless they offer a boot animation or include a script to delete it.
Yeah. But he is saying he doesn't see a change. Implying the phone boots up as it did prior.
He is also on cm9 , not the new cm10 that botched things up again.
That is why I am trying to get him to confirm how he is checking if the kernel changed. Almost certain its the op just seeing the boot animation and thinking that it didn't change due to that.
Op. Go to settings /about phone and look at kernel version. Flash a different kernel again. Check again.
I am confirming that it did not flash by going to settings and then about phone. In kernel it still says Trinity kernel rather that matrix kernel or air kernel (2 roms I've tried flashing).
Sent from my Nexus S using xda premium
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
[/QUOTE]
albundy2010 said:
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
Click to expand...
Click to collapse
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.[/QUOTE]
albundy2010 said:
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
Click to expand...
Click to collapse
Ok ll try that
You can flash my cm compatible kernel.
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I gave up and flash a new rom and kernel thanks for the help.
My Samsung Galaxy S 4G is going through some pretty awesome times in its life right now. However, I'm worried that flashing/restoring the wrong way is going to cut its winning streak short. I mainly stick to the Cyanogenmods found here. ClockworkMod will be abbreviated as CWM, Cyanogenmod as CM. Below is the full history of this device in chronological order:
>Samsung Stock KJ6 (Gingerbread 2.3.6, BML)
>Root w/SuperOneClick
>Bhundven's Subtly Modified Stock with CWM5 + Voodoo Lagfix (kernel w/CWM5.0.2.7)
>Valhalla Black Edition (Gingerbread, BML, CWM5, bhundven's KJ6 Beta2 kernel)
>Cyanogenmod 7.2 (Gingerbread, MTD, CWM5.0.2.8, cyanogenmod-GB kernel)
>Cyanogenmod 9 (Ice Cream Sandwich, MTD, CWM6.0.1.0, 2.6.35.7-cyanogenmod-ICS kernel w/Hefe Kernel changes)
>Cyanogenmod 10 (Jellybean 4.1.x, MTD, CWM6.0.1.9, 2.6.35.7-cyanogenmod-JB Proton kernel)
>Cyanogenmod 9 (Ice Cream Sandwich, MTD, CWM6.0.1.0, 2.6.35.7-cyanogenmod-ICS kernel w/Hefe Kernel changes)
>Cyanogenmod 10.1 (Jellybean 4.2.2, MTD, CWM6.0.3.2, Aries 3.0.84 kernel)
After flashing CM10, I got caught in a bootloop (a confirmed bug in the ROM), and I had to use CWM to restore a CM9 nandroid/backup. I then flashed to CM10.1, and this is where I'm currently at. However, I want to go back to CM9 once again, the GPS only works on the ICS ROMs.
Can I restore CM9 using my current version CWM, or does the recovery version have to be the exact same build? I didn't seem to have any problems restoring CM9 from CM10, and I'm still not sure if there were any consequences in doing that.
From what I've read, restoring has to be done on the same Recovery version as the Nandroid. I've watched many Youtube videos of people suggesting that they flash ROMs on "a daily basis", I'm trying to figure out how they are comfortable with this, given such a restrictive restore environment.
Double44 said:
My Samsung Galaxy S 4G is going through some pretty awesome times in its life right now. However, I'm worried that flashing/restoring the wrong way is going to cut its winning streak short. I am only running unofficial Cyanogenmods found here. ClockworkMod will be abbreviated as CWM, Cyanogenmod as CM. Below is the full history of this device in chronological order:
>Samsung Stock KJ6 (Gingerbread 2.3.6, BML)
>Root w/SuperOneClick
>Bhundven's Subtly Modified Stock with CWM5 + Voodoo Lagfix (kernel w/CWM5.0.2.7)
>Valhalla Black Edition (Gingerbread, BML, CWM5, bhundven's KJ6 Beta2 kernel)
>Cyanogenmod 7.2 (Gingerbread, MTD, CWM5.0.2.8, cyanogenmod-GB kernel)
>Cyanogenmod 9 (Ice Cream Sandwich, MTD, CWM6.0.1.0, 2.6.35.7-cyanogenmod-ICS kernel w/Hefe Kernel changes)
>Cyanogenmod 10 (Jellybean 4.1.x, MTD, CWM6.0.1.9, 2.6.35.7-cyanogenmod-JB Proton kernel)
>Cyanogenmod 9 (Ice Cream Sandwich, MTD, CWM6.0.1.0, 2.6.35.7-cyanogenmod-ICS kernel w/Hefe Kernel changes)
>Cyanogenmod 10.1 (Jellybean 4.2.2, MTD, CWM6.0.3.2, Aries 3.0.84 kernel)
After flashing CM10, I got caught in a bootloop (a confirmed bug in the ROM), and I had to use CWM to restore a CM9 nandroid/backup. I then flashed to CM10.1, and this is where I'm currently at. However, I want to go back to CM9 once again, the GPS only works on the ICS ROMs.
Can I restore CM9 using my current version CWM, or does the recovery version have to be the exact same build? I didn't seem to have any problems restoring CM9 from CM10, and I'm still not sure if there were any consequences in doing that.
From what I've read, restoring has to be done on the same Recovery version as the Nandroid. I've watched many Youtube videos of people suggesting that they flash ROMs on "a daily basis", I'm trying to figure out how they are comfortable with this, given such a restrictive restore environment.
Click to expand...
Click to collapse
I think that you'll just need to be on one recovery at all times. I don't recommend updating your recovery.
Smack that thanks button If I helped!
Always make a nandroid backup before trying anything risky
Sent from my fabulous N7105 powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Thanks for the quick response
I'm not sure how it's possible to stick with one recovery? A new recovery version comes with each ROM I flash on the T959V, it's impossible to keep recovery the same.
Double44 said:
Thanks for the quick response
I'm not sure how it's possible to stick with one recovery? A new recovery version comes with each ROM I flash on the T959V, it's impossible to keep recovery the same.
Click to expand...
Click to collapse
Keep the recovery file in your sd-card. Flash it everytime u flash a new rom. (Make sure the rom you're using is compatible with that recovery though)
Smack that thanks button If I helped!
Always make a nandroid backup before trying anything risky
Sent from my fabulous N7105 powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Short answer, "I just flash with whatever recovery I have on my phone. In the rare cases that doesn't work, I flash a different recovery manually."
Long answer:
On the SGS4G, it is non-trivial to keep the recovery as it is integral with the run-time boot image. Flash a kernel, you flash recovery as well. You almost always get the kernel in a ROM.
Within a given Android release, you should be able to use "any" recovery to flash any well-built ROM. I regularly flash TWRP-based ROMs using CWR and vice versa.
I haven't looked into getting CWR to recognize a TWRP backup or vice versa though. They should both hold the same information, but I don't know how well they "play with others" on their naming, locations, and formats.
There sometimes are differences in how the ROM's "install me" code runs in different Android versions and occasionally, for example, a JB-era recovery won't flash a GB-era ROM or vice versa. When that happens, you can generally flash a kernel of the "target" ROM by itself, then flash the rest of the ROM. It is pretty easy if you have a Mac or Linux machine, a bit more complicated if you're running Windows. Making cross-version upgrades reliable are one of the more challenging things a custom-ROM maker needs to deal with.
You generally don't want to try to mix a /data partition from one Android version with a /system from another. Some of the user-space backup utilities like Titanium Backup can do a decent job of upgrading data from one Android version to another. I've never tried to downgrade.
jeffsf said:
Short answer, "I just flash with whatever recovery I have on my phone. In the rare cases that doesn't work, I flash a different recovery manually."
Long answer:
On the SGS4G, it is non-trivial to keep the recovery as it is integral with the run-time boot image. Flash a kernel, you flash recovery as well. You almost always get the kernel in a ROM.
Within a given Android release, you should be able to use "any" recovery to flash any well-built ROM. I regularly flash TWRP-based ROMs using CWR and vice versa.
I haven't looked into getting CWR to recognize a TWRP backup or vice versa though. They should both hold the same information, but I don't know how well they "play with others" on their naming, locations, and formats.
There sometimes are differences in how the ROM's "install me" code runs in different Android versions and occasionally, for example, a JB-era recovery won't flash a GB-era ROM or vice versa. When that happens, you can generally flash a kernel of the "target" ROM by itself, then flash the rest of the ROM. It is pretty easy if you have a Mac or Linux machine, a bit more complicated if you're running Windows. Making cross-version upgrades reliable are one of the more challenging things a custom-ROM maker needs to deal with.
You generally don't want to try to mix a /data partition from one Android version with a /system from another. Some of the user-space backup utilities like Titanium Backup can do a decent job of upgrading data from one Android version to another. I've never tried to downgrade.
Click to expand...
Click to collapse
Twrp backups won't work with cwm and vice versa. I've tried it.
Smack that thanks button If I helped!
Always make a nandroid backup before trying anything risky
Sent from my fabulous N7105 powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
I feel like a more simple way is to go back to stock, re-root, and then go back to CM9.
I'm suddenly bursting at the seams with questions.
Irwenzhao said:
Keep the recovery file in your sd-card. Flash it everytime u flash a new rom. (Make sure the rom you're using is compatible with that recovery though)
Click to expand...
Click to collapse
Where would I look to find ROM/recovery compatibility? If I'm not mistaken, none of the ROMs I've used go into these details.
How would I backup a recovery? I would use ROM Manager, but ROM Manager is not compatible with the SGS4G. I've been doing my work manually through CWM only (which is recommended anyway), and I don't think CWM can be backed up through CWM itself.
I am planning to restore a CM9 backup eventually. If I were to backup a recovery, would I backup the current Jellybean recovery I have (CWM6.0.3.2), or would I be better off to backup the recovery that comes with the CM9/ICS nandroid (CWM6.0.1.0)? Both CWM's have software version 6, which almost makes sense that I was able to restore from CM10 before (CWM6.0.1.9); the only differences between the two recoveries are their build numbers.
If I were in need of a specific SGS4G kernel, where would a person look? I may need the kernel to CM9 (2.6.35.7-cyanogenmod-ICS kernel w/Hefe Kernel changes). Now that I think about it, what's the most important factor when restoring, the kernel or the version of recovery?
jeffsf said:
Short answer, "I just flash with whatever recovery I have on my phone. In the rare cases that doesn't work, I flash a different recovery manually."
Long answer:
On the SGS4G, it is non-trivial to keep the recovery as it is integral with the run-time boot image. Flash a kernel, you flash recovery as well. You almost always get the kernel in a ROM.
Within a given Android release, you should be able to use "any" recovery to flash any well-built ROM. I regularly flash TWRP-based ROMs using CWR and vice versa.
I haven't looked into getting CWP to recognize a TWRP backup or vice versa though. They should both hold the same information, but I don't know how well they "play with others" on their naming, locations, and formats.
There sometimes are differences in how the ROM's "install me" code runs in different Android versions and occasionally, for example, a JB-era recovery won't flash a GB-era ROM or vice versa. When that happens, you can generally flash a kernel of the "target" ROM by itself, then flash the rest of the ROM. It is pretty easy if you have a Mac or Linux machine, a bit more complicated if you're running Windows. Making cross-version upgrades reliable are one of the more challenging things a custom-ROM maker needs to deal with.
You generally don't want to try to mix a /data partition from one Android version with a /system from another. Some of the user-space backup utilities like Titanium Backup can do a decent job of upgrading data from one Android version to another. I've never tried to downgrade.
Click to expand...
Click to collapse
How would you manually flash a different recovery if you've already wiped the device? Are you restoring the current ROM, then downloading a different kernel, and trying again?
You wouldn't want to flash a BML ROM with an MTD ROM's recovery. You may know this already, but there are Gingerbread ROMs with both BML & MTD layouts. Luckily this trend disappears on the ICS ROMs by keeping it MTD, I don't plan on flashing any lower than ICS because of this.
Regarding your last sentence, isn't this why a person would wipe data and format /system before flashing?
AnAznBoy9724 said:
I feel like a more simple way is to go back to stock, re-root, and then go back to CM9.
Click to expand...
Click to collapse
I may not need to go down that route just yet.. though I could be wrong.
Double44 said:
I'm suddenly bursting at the seams with questions.
Where would I look to find ROM/recovery compatibility? If I'm not mistaken, none of the ROMs I've used go into these details.
Click to expand...
Click to collapse
Most ROM builders seem to be happy about just getting their ROM to flash over common other ROMs in use for the phone when they release them. It's more a case of "I tried it and it didn't work" for most ROMs. Clear exceptions include at least:
Froyo and Gingerbread had different boot loaders
Some MTD ROMs can't be flashed from a BML kernel
I don't know of any BML ROM that can be flashed from an MTD kernel
SELinux throws a wrench into cross-kernel flash compatibility
How would I backup a recovery? I would use ROM Manager, but ROM Manager is not compatible with the SGS4G. I've been doing my work manually through CWM only (which is recommended anyway), and I don't think CWM can be backed up through CWM itself.
Click to expand...
Click to collapse
/mnt/sdcard/TWRP or /mnt/sdcard/Clockwork have the backups in them. If you look at them in detail (and ignore the suffix) /data and /system and your android-secure are generally something manageable like tar or cpio format. Titanium Backup (Pro, at least) can read both CWR and TWRP backups.
I am planning to restore a CM9 backup eventually. If I were to backup a recovery, would I backup the current Jellybean recovery I have (CWM6.0.3.2), or would I be better off to backup the recovery that comes with the CM9/ICS nandroid (CWM6.0.1.0)? Both CWM's have software version 6, which almost makes sense that I was able to restore from CM10 before (CWM6.0.1.9); the only differences between the two recoveries are their build numbers.
Click to expand...
Click to collapse
You backup "recovery" every time you backup boot on the SGS4G. The recovery partition, as I understand the early bootloaders, is never used. It is the same image in both partition.
If I were in need of a specific SGS4G kernel, where would a person look? I may need the kernel to CM9 (2.6.35.7-cyanogenmod-ICS kernel w/Hefe Kernel changes). Now that I think about it, what's the most important factor when restoring, the kernel or the version of recovery?
Click to expand...
Click to collapse
If you wanted just the boot image from a ROM installer, which includes both the kernel and recovery, pretty much inseparably bound together, then you can un-zip the ROM and look for boot.img in the extracted files. It should also be the contents your "nandroid" backup of the boot or recovery partition (though I haven't confirmed that it is bit-for-bit equivalent, I would be surprised if it wasn't). You can grab the current Hefe Kernel which is what I generally use as my "go to" kernel for ICS. Then again, I'm arguably biased.
How would you manually flash a different recovery if you've already wiped the device? Are you restoring the current ROM, then downloading a different kernel, and trying again?
Click to expand...
Click to collapse
heimdall is your friend, along with a "recovery jig" or "download jig" (under $5 to make, or off eBay). You can flash a soft-bricked device with it.
Code:
heimdall flash --KERNEL path/to/boot.img
@bhundven thinks that 1.3.1 is the latest you should use.
http://forum.xda-developers.com/showthread.php?t=755265
http://glassechidna.com.au/heimdall/
https://github.com/Benjamin-Dobell/Heimdall/downloads
It can also be done from the command line, for example using adb into recovery. As a mis-typed command using that approach could potentially blow away boot loaders or the like, I tend not to use it myself.
You wouldn't want to flash a BML ROM with an MTD ROM's recovery. You may know this already, but there are Gingerbread ROMs with both BML & MTD layouts. Luckily this trend disappears on the ICS ROMs by keeping it MTD, I don't plan on flashing any lower than ICS because of this.
Click to expand...
Click to collapse
You can always use one of the one-click installers to get back to GB, if you want or need. I tend to be slow to upgrade as you can't reliably go back with your data, even with backups.
Regarding your last sentence, isn't this why a person would wipe data and format /system before flashing?
Click to expand...
Click to collapse
A ROM shouldn't care what's on /data though some are apparently unhappy with the cruft of others. Other have not been as lucky as I seem to have been. I always back up before flashing, and immediately go back if it didn't seem to go right, before I put in my SIM or turn on WiFi. (I always try to remember to turn off WiFi and pull my SIM card so that I don't have important changes in my app data when changing ROMs.)
I guess how many ROMs a day you are flashing, how likely you think it is that the ROM is "functional" and how easily you can recover from a bad one impacts how you make your personal decision about what your process is.
On the other hand, if you are changing Android versions, yes, wipe, clean install, and carefully restore app data, with frequent backups so you don't have to start over if something goes wrong.