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
Related
Hello,
I tried looking everywhere for the stock (default) 2.3.3. kernel (i don't want to flash an entire rom) if anyone know where i can find a link ,i would be most thankful.
thank you.
Goes in Q&A section I think.
Try Q & A thread
Sent from my LG-P999 using xda premium
crazy_agent said:
Hello,
I tried looking everywhere for the stock (default) 2.3.3. kernel (i don't want to flash an entire rom) if anyone know where i can find a link ,i would be most thankful.
thank you.
Click to expand...
Click to collapse
Did you do a backup of the rom before changing the kernel. It is contained in the boot.img in the backup. Just use one of the flashable zips that flash the kernel and replace the boot.img and wireless.ko files from an original nandroid with the one in the flashable zip (ones I looked at the boot.img as in the kernel subdirectory). wireless.ko goes in /system/lib/modules directory. Just use 7-zip and open archive. Delete the boot.img and paste in the one you want. Cloese out 7-zip and then you have a flashable zip with the stock kernel. I have attached the boot.img from the stock GB rom. Make sure you unzip the file and remove the boot.img. Do not try to flash this zip. It won't work.
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
jboxer said:
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
Click to expand...
Click to collapse
If this works it should def go in the dev section, unless it's already there.
Mister Hat said:
If this works it should def go in the dev section, unless it's already there.
Click to expand...
Click to collapse
I will post a thread in the development section once somebody confirms it works. I am pretty confident it will work. Using the same method that is used to flash custom kernels, but I used the boot.img and wireless.ko from the stock GB rom flash.
jboxer said:
I went ahead and made a flashable zip to restore the stock GB kernel. A big caveat here is that I have not tested it out myself as I am currently already rocking the stock kernel. If you are a brave soul you can try it out. Based on my experience it should work with no problems. If it does work please report back here and I will make a new thread in the development section. Many people have been looking for this, including myself. Once I venture out to another kernel to overclock, I wanted to have a way to restore to stock if I needed it. For now I am sticking with the stock kernel as I find the phone fast enough as it is.
Make sure you clear the Dalvik cache before rebooting or you might hang during boot or get a boot loop. The first boot will take several minutes due to Dalvik cache being rebuilt.
Click to expand...
Click to collapse
Not sure if I done anything wrong but here are the steps that i did:
- clear cache
- clear Dalvik cache
- flashed the zip file
- reboot
All I got was a black screen. I waited for about 15 mins but still black screen.
saotua said:
Not sure if I done anything wrong but here are the steps that i did:
- clear cache
- clear Dalvik cache
- flashed the zip file
- reboot
All I got was a black screen. I waited for about 15 mins but still black screen.
Click to expand...
Click to collapse
Did you flash it over the stock GB 2.3.3 rom? This is the original kernel and ony compatible with the stock rom. If you are running another rom that would result in a black screen due to incompatibility issues.
I'm using Xboarder's Stock Tweaked OTA Gingerbread build v1.2.2. I don't have the original stock rom. (stupid me, i didn't backup the stock rom before flashed another rom )
Edit: I tried again and it works beautiful. Thank you.
Thank you.
thank you all for your help.
Hi All
Finally plucked up the courage to register and ask a question after lurking for the good part of 2 years.
I've an i9020A and have flashed CyanogenMod 9 v4.0.3 v1.0 which is great, however I wanted to try Steve Garon's kernel which just wont take.
I reboot into Recovery, wipe Dalvik Cache a couple of times, install Steve's kernel which apparently flashes no problem.
I reboot and get the optimising Android applications screen then check my kernel under settings.
It is still the original KalimochoAz kernel and I cannot turn on my wireless.
Now this has happened previously when trying to also update my kernel under CDTDroid's AndroidMe 1.2 which I could only fix by restoring back to 1.1.
Any idea on what may be wrong here guys?
Appreciation in advance.
Lally
Have you tried just flashing again? A bad flash often results in wifi not working and may be the cause of the about page showing the old kernel. Remember to wipe dalvik cache again, too.
Thanks for the reply Harbb, do you mean a re flash of the Kernel or ROM? If Kernel then yeah I have done, same scenario. I'll also try a re download of the Kernel to see if that improves anything but this is much akin to me trying to update from Speedy3 to Speedy4 under AndroidMe 1.2 which was unsuccessful.
Just the kernel, as you've already tried. Just remember to do a NANDroid backup (CWM --> backup & restore --> backup) when you have a stable, working ROM. Can save you alot of trouble if you don't have a relatively recent one.
Also, are you using CWM 5.0.2.0? And could it be that your phone isn't particularly happy about the 1100mhz OC with Steve Garon's kernel?
I'd suggest updating CWM recovery to the latest version.
Sent from my Nexus S using xda premium
Cheers for the help guys.
Yes, using 5.0.2.0, but something is not right cause I just tried to flash CWR again from within Rom Manager (4.8.1.3) and it gets to around 95% and the app gives 'Rom Manager is not responding.
Looks like I'll have to try a complete wipe and reflash.
Will report back the results.
Forget rom manager all together.
Download the recovery you want to use.
Flash it via fastboot
flash kernel.
I'd do what albundy said - flash a new recovery through fastboot and make sure the bootloader is unlocked (vol. up + power --> bootloader: unlocked)
Ok, downloaded CM9 1.1, redownloaded Steves kernel, reinstalled recovery from fastboot.
Wiped and formatted everything twice then installed from scratch.
So far everything is good, still getting errors on Superuser, but installing again via recovery seems to fix that issue.
Cheers chaps.
Good to know Lally, happy you got it sorted out.
Cheers Harbb, the test will be when I want to change the kernel again I suppose, one complete wipe and install a day is enough
Hi guys, I'm using the CM9 ICS with my transformer and I was trying to install a different kernels without any success at all. I've booted into CWM (V5) and installed from sd card but when I restart the machine, It's always with the same kernel. Can someone suggest how to make it work?
How long does the install take? That should give some insight onto what it is doing
yosi199 said:
Hi guys, I'm using the CM9 ICS with my transformer and I was trying to install a different kernels without any success at all. I've booted into CWM (V5) and installed from sd card but when I restart the machine, It's always with the same kernel. Can someone suggest how to make it work?
Click to expand...
Click to collapse
Just to be sure, CWM v5 will not read external uSD card, only the internal storage /sdcard. May I know the kernel you are installing?
It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.
have u tried wiping the cache and dalvik before flashing them?
scottyf79 said:
have u tried wiping the cache and dalvik before flashing them?
Click to expand...
Click to collapse
Yes I have... no good
yosi199 said:
It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.
Click to expand...
Click to collapse
A minute is way too long. Kernels only take like 3 seconds cuz they are small.
Try mount /system under mounts and storage before flashing the kernel.
yosi199 said:
It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.
Click to expand...
Click to collapse
Flashing a new kernel takes a few seconds. After reboot please pay attention to the blue indicator below the Android figure. It this not appears something went wrong with the first stage of the flashing process, invalid image/zip file etc.
Please use the customized CWM version, just not the flashed one from the Rom manager. I'v good experiences with the R2 (internal sdcard only) as well with the R1 (external micro-sdcard only). I preferred the R1 version.
Btw I'v have the best experiences with my TF101G with the CM9 build of March 29 combined with the quevor-test8 (just NOT from the guevor thread but ONLY from the thread of Richard because it's compiled for CM9) kernel, no reboots and no deep sleeps anymore while 3G and Wifi is working fine. Please do not wipe or clear something before flashing the new kernel to prevent Wifi problems. And I'v the best experiences not using the reboot system now from CWM but using power down and switch on the TF manually.
antond57:
i too have been having trouble getting kernels to allow overclocking...i flash one, all looks ok but when i get to tablettop the kernel info appears unchanged and setcpu wont clock past 1000.
could you maybe please post links to the rom and kernel you used? im having trouble locating the Richards R1 and R2 versions. i would like to see if i can repeat your success w/ these versions.
much appreciated.
I have same issue except worse yesterday. I'm on latest CM9. I tried to flash guevro test 9 and I did wipe both cache. Using roach 2 recovery. Just stayed on Asus screen. Blue bar did pop up and take a second or so but nothing. Checked md5 and all was good.
I had to totally flash ROM again after a full wipe because even a restore from recovery wouldn't go past very first Asus screen. I'm not sure what happened but I'm definitely now worried about trying a new kernel again
Sent from my Transformer TF101 using xda premium
eminembdg said:
I have same issue except worse yesterday. I'm on latest CM9. I tried to flash guevro test 9 and I did wipe both cache. Using roach 2 recovery. Just stayed on Asus screen. Blue bar did pop up and take a second or so but nothing. Checked md5 and all was good.
I had to totally flash ROM again after a full wipe because even a restore from recovery wouldn't go past very first Asus screen. I'm not sure what happened but I'm definitely now worried about trying a new kernel again
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Yap, I have the same problem. Nandroid restore did not restore to the previous state. For me, re-flash the ROM fixed the problem (no full-wipe).
Try Using clockwork recovery
I have just flashed guevor kernel as well with no problems. I'm using clockwork mod recovery. Have you tried it?
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.
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck
dandydon414 said:
you need the latest recoveries to flash kk roms. cwm is here https://www.clockworkmod.com/rommanager
and twrp is here http://teamw.in/project/twrp2/102. make sure you download the d2vzw version
if you're rooted you should have no problems flashing 4.4 rom. I recommend beanstalk from here http://forum.xda-developers.com/showthread.php?t=2354113. has worked great for me. you have to also update the modem to ML1 from here http://forum.xda-developers.com/showthread.php?t=1788313
as always do a nandroid before you do anything and you should backup your sd card to your computer. they probably will move post this to another thread.
good luck
Click to expand...
Click to collapse
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar
aholeinthewor1d said:
ahh I didn't even think of that? I do know for a fact whatever version of CWM i had was not recent..Are you sure that is the only issue? so with a newer recovery...like I have now that I fixed my phone..I can flash a 4.4 ROM no problem? I could have sworn I remember hearing something about needing a certain modem...or something similar
Click to expand...
Click to collapse
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.
dandydon414 said:
yes. flash the ML1 modem. I provided the link in my previous post. it's a fact that earlier recoveries won't flash kk roms. I found out the hard way myself. hopefully you'll have titanium or rom toolbox to backup your apps with data.
Click to expand...
Click to collapse
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you
aholeinthewor1d said:
Thanks a lot!!.. So how do I know if my recovery is new enough? I was never a fan of the touch recoveries because I felt like it would be easier to do something on accident so I haven't tried one in a while...I am using clockwork mod recovery 6.0.4.5. Is that new enough??
Also one lasttttt question I swear...can someone give me a quick list of the different recovery options that are out there now...and maybe list some features of each...thank you
Click to expand...
Click to collapse
that recovery is fine. i've only used cwm and twrp.. had some problems with philz recovery so I ditched it. basically they're all the same. twrp lets you name your back where as cwm just uses some default name which of course you can change with a file manager. twrp also wipes all 3 (system, cache and dalvik) with one swipe where as cwm requires 3 separate operations. I really haven't done much in recovery other than wiping and flashing. I'm actually on the latest twrp and have had no problems flashing kk roms. keep in mind that you can't backup in cwm and restore it using twrp and vice versa. it's really more a personal preference as far as I'm concerned.