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.
Related
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
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
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
t1op said:
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Click to expand...
Click to collapse
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
WayTooGosu said:
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
Click to expand...
Click to collapse
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
lumin30 said:
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
Click to expand...
Click to collapse
Ah I see. But my point was that some ROMs state that the user must be on an ICS ROM/Kernel to flash this. I guess I wasn't very clear as I am new here and lack understanding.
champ1919 said:
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I used Odin to return to stock. I used Super One Click to root. I used root explorer modify the recovery to allow me to boot into "CWM final for Froyo". That much each and every time.
The first time I installed
[TFQ - 30/12/2012]X.A.O.K[Kanged - Xperia Style]
That is an ICS rom. Installed fine with a new CWM.
The second time I installed the same.
The third time I installed
ROM-MTD-TWRP-ICS-4.x-Audiophile
That is another ICS rom. Installed fine with TWRP.
Each and every time, when returning to recovery to flash more, I got stuck. I can't boot to anything except recovery.
My brother suggested that the problem is using the Volume up and down and power button ("three finger salute") to return to recovery instead of from OS power down menu.
For a fourth time I started over again. Now, using the reboot>recovery, everything works fine.
One thing, you need to have ginger bread bootloaders. So, when you say Odin back to stock, are you referring to kj6?
You could cut down some of the work by using Odin to flash a kernel with recovery & root in it. Antonx & drhonk both have kernels that will do that with odin.
I flash bhundven's cm9 Rom before jumping to any of the others(and wipe between). I believe some of the Rom authors have that in their instructions.
Sent from my SGH-T959V using xda app-developers app
Yeah... GB bootloaders, not Froyo. Your return to stock should be a return to GB stock, not Froyo... and your return to stock can be a return to a rooted stock. If you want to make your life less painful.
It's about MTD to BML, not really about the base version. You just don't want to wipe out what allows later stuff to actually work properly...
Thanks for the advice. I haven't used custom roms very much. Trying to figure out which ones to choose was difficult. I started on stock Gingerbread, but everything I encountered in searching indicated that I needed to go back to Froyo to get CWM then go from there. ...Perhaps I kept running into very old instructions? In any case, should I need to go back to stock again some day, I'll try to figure out which GB roms I could use, including root and custom recovery.
I guess the solution to my problem is: 1) flash back to Froyo or Gingerbread; 2) after flashing an ICS+ rom, only go to recovery from OS reboot menu (never "three finger salute").
I'm actually surprised that people don't run into this problem more often, enough to create a sticky about it. I'm sure I'd still be pulling my hair out if my brother hadn't run into the problem on his Fascinate a year ago.
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Theraze said:
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Click to expand...
Click to collapse
Interesting... Perhaps if I went back to a gingerbread stock then upgraded to ICS the problem wouldn't occur?
I'll have to try that the next time I might need to return to stock.
Hello,
First I just want to say thank you to the mods for running a great forum and to the devs for keeping this device current.
I just struggled over a period of days with this issue.
The end result being, that you need to go to CM9 BEFORE you try JellyBean or later!
Just hope this helps someone else who missed that instruction.
Thanks devs/mods/everyone for keeping this device alive!!!! :good::good::good:
*EDIT* correction... i THINK you need to go CM9 Before trying something else
Not all ICS ROMs require CM9, but you must have at least CWM5 recovery to be able to flash CM9 or these ROMs. Follow ROMs' OP instructions.
I personally tested HebMIUI flash over Stock GB with CWM5 (Basic with a twist kernel) without going through CM9.
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.
I am about to flash my nexus 5 device.
I was wondering.. if i unlock the bootloader and install a custom recovery plus create a backup.. that means ill have basicly a backup on my phone of a factory ROM and kernel right ?
So If i play around with custom roms and Kernels does that mean if I want to go back to stock kernel or/and ROM I can just recover my backup files from ,for example, CWM ?
And also if anyone here knows... how big difference can a kernel for battery life extension make ?
Then..
If I want to flash both.. Custom ROM and Kernel.. Rom comes first ? And if after that .. lets say I have flashed Cyanogenmod , and I have decided to change ROMs , Do I have to flash factory ROM ? Or I can just factory reset and Flash ir over the Cyanogenmod ?
For example.. for elementalX kernel I read this line... "You should only flash ElementalX over the kernel that came with your ROM!!!" I assume that means I do flash the ROM first... and what if I want to change Kernels later on? I re-flash the factory kernel ? And how do I do that?
For now that would be it
Thanks
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
audit13 said:
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
Click to expand...
Click to collapse
Thanks!
What advantages does TWRP has over CWM ? And also does it recover other files as well or just the system ones ?
And I guess its safer to just extract the original ROMs kernel.. Just how do i do that ?
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help: https://www.youtube.com/watch?v=rLhprnOF6-U
audit13 said:
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help:
Click to expand...
Click to collapse
Thanks!
So.. If, lets say, I flash cyanogenmod. Then Flash custom kernel. In order to change other kernel which is also custom , I should first flash the factory ROM which will have kernel on it ? And then reflash the ROM and then flash the new kernel ?
Im sorry , I also read a lot about this and somewhere on the way got really confused , haha.
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
audit13 said:
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
Click to expand...
Click to collapse
Thank you. Made things much clearer. Dirty flash means just flashing over the existing custom ROM and Kernel right?
And also.. What about if i have CM and Kernel B ... But i want to go change to ParanoidAndroid and still keep the Kernel B? This ROM would remove the Kernel and I would have to re flash ir right?
And also if I am just switching around ROMs only.. I can just flash them one over another? Perhaps a factory reset is healthy in between though.
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
audit13 said:
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
Click to expand...
Click to collapse
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
rihz said:
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
Click to expand...
Click to collapse
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
wangdaning said:
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
Click to expand...
Click to collapse
Okay, thanks!
And Happy New year to you all!