As the title says, every time I do a cwm backup, I get the unable to generate md5 sum.
By googling this, It seems that many people have issues restoring from cwm due to md5 mismatch
But my case is I cannot even create the backup,since it cant generate the md5.
I tried using both backup format, and tried the internal and external storage. Also also get unable to generate md5 .
I have no idea why this happens.
I am currently using aokp milestone one.
The default kernel and default recovery that comes with it
Previous ROM was Samsung leak lsj jellybean ROM.
mtxx1 said:
As the title says, every time I do a cwm backup, I get the unable to generate md5 sum.
By googling this, It seems that many people have issues restoring from cwm due to md5 mismatch
But my case is I cannot even create the backup,since it cant generate the md5.
I tried using both backup format, and tried the internal and external storage. Also also get unable to generate md5 .
I have no idea why this happens.
I am currently using aokp milestone one.
The default kernel and default recovery that comes with it
Previous ROM was Samsung leak lsj jellybean ROM.
Click to expand...
Click to collapse
It's a known problem with the default kernel, try another such as dorixmanx or siyah. The backup function works fine
Sent from my GT-I9100 using xda app-developers app
Hayth said:
It's a known problem with the default kernel, try another such as dorixmanx or siyah. The backup function works fine
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Really? Thanks for the info. I've look thought aokp thread but no mention of the backup problem.
Is it possible to use cm10 kernel for aokp?
mtxx1 said:
Really? Thanks for the info. I've look thought aokp thread but no mention of the backup problem.
Is it possible to use cm10 kernel for aokp?
Click to expand...
Click to collapse
Yes, u can use CM10 kernel, but the best bet is with 'Siyah' or 'Dorimanx' Kernel though
Sun90 said:
Yes, u can use CM10 kernel, but the best bet is with 'Siyah' or 'Dorimanx' Kernel though
Click to expand...
Click to collapse
i really prefer cm10 kernel, dont want to get hooked with these kernel stuff and their tweaks.
but i cant seem to find cm10 kernel. still looking.
do you know where can i download latest stock cm10 kernel?
mtxx1 said:
i really prefer cm10 kernel, dont want to get hooked with these kernel stuff and their tweaks.
but i cant seem to find cm10 kernel. still looking.
Click to expand...
Click to collapse
well then all u can do is.
1) search the CM10 thread and see if anybody has posted a CWM flashable zip file.
2) u can extract the kernel Zimage file from one of the latest builds of CM10 and flash the same from recovery and see
Sun90 said:
well then all u can do is.
1) search the CM10 thread and see if anybody has posted a CWM flashable zip file.
2) u can extract the kernel Zimage file from one of the latest builds of CM10 and flash the same from recovery and see
Click to expand...
Click to collapse
i got it!
wow what an interesting mini adventure. this is what i did.
i cannot find the Zimage of cm10 anywhere, i downloaded the cm10 scour all folders but no zimage.
so i download resurrection rom, under the folder RR, there is a cm10 folder that has the boot.img,
i extracted it, send to my phone, and flash using mobile odin lite.
done!
Sun90 said:
well then all u can do is.
1) search the CM10 thread and see if anybody has posted a CWM flashable zip file.
2) u can extract the kernel Zimage file from one of the latest builds of CM10 and flash the same from recovery and see
Click to expand...
Click to collapse
Hello Sun90,
CM10 kernel is NOT compatible with aokp
i am able to boot after flashing the kernel, but i cant turn on my wifi anymore.
there is no wifi mac address in my settings>about phone>status
i flash back aokp stock kernel and able to on wifi again.
so nope, cannot use cm10 kernel. sad...
mtxx1 said:
Hello Sun90,
CM10 kernel is NOT compatible with aokp
i am able to boot after flashing the kernel, but i cant turn on my wifi anymore.
there is no wifi mac address in my settings>about phone>status
i flash back aokp stock kernel and able to on wifi again.
so nope, cannot use cm10 kernel. sad...
Click to expand...
Click to collapse
thats the problem with some version of CM10 kernel for sure ma8 either there will be a 'wifi' issue or the 'Sd mount' issue
Sun90 said:
thats the problem with some version of CM10 kernel for sure ma8 either there will be a 'wifi' issue or the 'Sd mount' issue
Click to expand...
Click to collapse
this is strange, anyway, my main objective is to create cwm backup,
the default kernel in aokp milestone 1 is not working.
i need to try other kernel then.
i would prefer avoiding siyah, dorimanx etc, because i lurk in many forums, and the use of those kernel and their tweaks, will cause SOD.
i hate SOD. i tried siyah before and got numerous SOD.
never once had SOD with cm10 kernel.
mtxx1 said:
this is strange, anyway, my main objective is to create cwm backup,
the default kernel in aokp milestone 1 is not working.
i need to try other kernel then.
i would prefer avoiding siyah, dorimanx etc, because i lurk in many forums, and the use of those kernel and their tweaks, will cause SOD.
i hate SOD. i tried siyah before and got numerous SOD.
never once had SOD with cm10 kernel.
Click to expand...
Click to collapse
You might want to try an app called Online Nandroid Backup, it makes a nandroid backup whilst the phone is on without going into recovery. Although, I'm not sure whether the problem with the kernel would surface. Might be worth a shot if your dead set on not using another kernel.
Sent from my GT-I9100 using xda app-developers app
Related
Hi I'm currently on the root box ROM with the siya kernal and wanted to flash a different one but no matter what I do I get an error before unloading the package. I came across this problem before and the solution was to just reflash aokp. I believe the logic was, siya was not compatable to open the package or something and needed cwm. However I can't find a flashable zip of cwm default kernal and I do not have a computer to access for Odin at the moment. Someone please, point me in the right direction...
aspen1135 said:
Hi I'm currently on the root box ROM with the siya kernal and wanted to flash a different one but no matter what I do I get an error before unloading the package. I came across this problem before and the solution was to just reflash aokp. I believe the logic was, siya was not compatable to open the package or something and needed cwm. However I can't find a flashable zip of cwm default kernal and I do not have a computer to access for Odin at the moment. Someone please, point me in the right direction...
Click to expand...
Click to collapse
I would use Heimdall to flash if possable also i would flash Siyah's new kernel also check the md5 to verify the rom you are trying to flash sometimes during download things get goofed after that make sure you wipe everything data/cache/dalvik and then try flashing your rom
You're trying to say yer getting the status 7 error. I think that's what I've gathered. Just do the same thing you did before, if u happen to have Tasks 7.3 version available flash that. It's a build. Prop problem with your phone showing a different model number than i777 because you are /were on a ported rom with i9100 showing as the model number. Flashing this version of tasks rom sets your build. Prop back to i777. U could actually use any rom that is based on i777 firmware although they may have scripts to check if your current build. Prop is i777 or not and may not let u flash it. The 7.3 version of tasks AOKP has those script asserts removed and it doesn't check what yer running which makes it great for situations like this. U can download tasks 7.3 AOKP by googling dev.host task AOKP I think. I haven't tried but someone said it's still up there. Or I could be completely wrong and status 7 error isn't what yer getting. In which case ignore this wall of text and go about your day. Lol,
Sent from Team Pirate Headquarters.
This link explains how to edit build prop to get rid of status errors.
http://forum.xda-developers.com/showpost.php?p=24266658&postcount=471
Status 7 = incompatible CWM
Just flash the STOCK kernel.
Sent from my SGH-I777 using xda app-developers app
Phalanx7621 said:
You're trying to say yer getting the status 7 error. I think that's what I've gathered. Just do the same thing you did before, if u happen to have Tasks 7.3 version available flash that. It's a build. Prop problem with your phone showing a different model number than i777 because you are /were on a ported rom with i9100 showing as the model number. Flashing this version of tasks rom sets your build. Prop back to i777. U could actually use any rom that is based on i777 firmware although they may have scripts to check if your current build. Prop is i777 or not and may not let u flash it. The 7.3 version of tasks AOKP has those script asserts removed and it doesn't check what yer running which makes it great for situations like this. U can download tasks 7.3 AOKP by googling dev.host task AOKP I think. I haven't tried but someone said it's still up there. Or I could be completely wrong and status 7 error isn't what yer getting. In which case ignore this wall of text and go about your day. Lol,
Sent from Team Pirate Headquarters.
Click to expand...
Click to collapse
First off, this was the reply I was kinda looking for, thnx. Second, don't tell me what to do *****. third, if what your saying is true, I should be able to flash the shoshock ROM and then have no problems with flashing anymore?
aspen1135 said:
First off, this was the reply I was kinda looking for, thnx. Second, don't tell me what to do *****. third, if what your saying is true, I should be able to flash the shoshock ROM and then have no problems with flashing anymore?
Click to expand...
Click to collapse
Cause I'm trying right now. Wish me luck I'll report after I'm done with excessive flashing
RatusNatus said:
Status 7 = incompatible CWM
Just flash the STOCK kernel.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Why you keep stating this garbage? its caused by build.prop.
flashing from CWM 5.xxx to 6.xxx is not a problem.
MotoMudder77 said:
Why you keep stating this garbage? its caused by build.prop.
flashing from CWM 5.xxx to 6.xxx is not a problem.
Click to expand...
Click to collapse
Are you telling me that flashing the stock CM kernel wont solve the problem? Are you sure?
The Instalation checks the build.prop to know if your cwm image is good to go.
If not, it MEAN that your version of CWM is unsupported.
Did you flashed the ROM ??? LOL
gregsarg said:
Unsupported CWM image ...
Your CWM or TWRP is not compatible with your rom...
Flash the CWM from the "everything " thread ...
Then try again ....it seems this version is the most stable ....IMHO
Edit :
It's non touch ...but it's rock solid ...g
Click to expand...
Click to collapse
This is from closed threats:
"You are most likely using an unsupported recovery refer to OP for proper recovery"
http://forum.xda-developers.com/showpost.php?p=30623016&postcount=218
"I'm pretty sure that the solution for this problem is to update CWM. Or even better, use TWRP."
http://forum.xda-developers.com/showpost.php?p=30622934&postcount=217
RatusNatus said:
Are you telling me that flashing the stock CM kernel wont solve the problem? Are you sure?
The Instalation checks the build.prop to know if your cwm image is good to go.
If not, it MEAN that your version of CWM is unsupported.
Did you flashed the ROM ??? LOL
This is from closed threats:
"You are most likely using an unsupported recovery refer to OP for proper recovery"
http://forum.xda-developers.com/showpost.php?p=30623016&postcount=218
"I'm pretty sure that the solution for this problem is to update CWM. Or even better, use TWRP."
http://forum.xda-developers.com/showpost.php?p=30622934&postcount=217
Click to expand...
Click to collapse
This problem has been occurring for a long time now. And has nothing to do with your version of cwm. It has to do with the script IN THE ROM YOU ARE FLASHING. If it has the script in the rom to check what phone model u have, and it detects something other than what it should, it basically says "hey! This guy doesn't have our phone! Stopppp!" And won't let u flash. Status 7 error. To fix this, either manually remove the script that checks for this in the rom yer flashing, modify the build.prop in the rom yer currently ON to reflect the model number of the rom u want to flash, or flash another rom that already has this script checking removed to get your build.prop to reflect the new model number u want it to show. Either way none of it has to do with your version of cwm.
Sent from my SGH-I777 using Tapatalk 2
So why flashing the cm9 kernel and Not the ROM deal with that?
Are you sure that a kernel hás nothing to do with?
Im not just telling that, thats what i did and it works.
Im here sharing this info.
Tell me, did you tryed that to tell here that it wont work?
Just flash another kernel without the touch cwn.
...and thanks for unresume my resume.
Sent from my SGH-I777 using xda app-developers app
RatusNatus said:
So why flashing the cm9 kernel and Not the ROM deal with that?
Are you sure that a kernel hás nothing to do with?
Im not just telling that, thats what i did and it works.
Im here sharing this info.
Tell me, did you tryed that to tell here that it wont work?
Just flash another kernel without the touch cwn.
...
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
You had a different issue then. most likely just a corrupt recovery. as there are NO problems flashing from one version of CWM to the next.
The common status 7 error, is caused by the updater.script searching the build.prop. as stated a million times in almost every thread.
Hey can anyone provide me the link with the stock cm 10 kernel, i was on cm10 but then i flashed a different kernel n i wanna go back to the cm10 stock kernel. how can i do this? does anyone have the link to it? thanks
Flash CM10 again without wiping; the kernel will overwrite your existing kernel. Once you've done that, get kTool from Google Play (and buy Hellcat a beer) & dump the CM10 kernel to your internal SD card.
That way, in the future, if you try out other kernels & want to go back to to the CM10 kernel you'll be able to flash just the kernel (with Mobile Odin or Odin) without having to flash the whole rom (whenever you flash a new CM10 build, do this step immediately afterwards so you have a copy of the latest kernel).
Or....you could ask in the CM10 discussion thread, tho you'd be able to do the above 50 times in the time you'd wait to get an answer/a link to just the kernel
Nice, didn't realise there was such app that can do that. Thanks
Of and do you think it will work with stock Ics kernel? I don't see why not tbh
Sent from my sexy Galaxy SII
Yep. You can dump any kernel with kTool & then flash the kernel with Odin/Mobile Odin.
*boy*racer* said:
Nice, didn't realise there was such app that can do that. Thanks
Of and do you think it will work with stock Ics kernel? I don't see why not tbh
Sent from my sexy Galaxy SII
Click to expand...
Click to collapse
I have flashed paranoidandroid 3.15 on my galaxy s3 a couple weeks ago, aside the occasional screen that win't turn on I haven't had any problem, but I set my mind on flashing a new kernel in order to be able to change thez governor. I tried to flash air kernel on, I did exactly what I was told: Boot into recovery, clear cache/delvik, installed kernel from sd card, and rebooted. But after the phone being rebooted, I still had the stock kernel.
My question is, why did this happen, and how do I fix it?
All help is appreciated
what recovery? link to the kernel?
Glebun said:
what recovery? link to the kernel?
Click to expand...
Click to collapse
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
vonniel said:
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
Click to expand...
Click to collapse
Kernel is for nexus s not galaxy s3
Sent from my GT-I9300 using xda premium
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Glenbun. Only mismatched, corrupted, or missing boot loaders can kill a phone.
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Glebun said:
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Click to expand...
Click to collapse
Glebun u have a point, even other incompatible components of recovery zip packages can brick the phone.
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Glebun said:
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Click to expand...
Click to collapse
Wow, I feel so dumb ^^' I'll be more careful next time around.
What kernel would you recommend for me?
I recommed stock mb5 or speedmod k2-12 kernels for you
Bahadirafro said:
I recommed stock mb5 or speedmod k2-12 kernels for you
Click to expand...
Click to collapse
Well, I don't really know either of them, I don't mind stock, but I want to change things, sometimes it just isn't up for the task, or uses up battery when I would rather it didn't, without even knowing what they do, and looking around, I found the perseus kernel, I would like some opinions on the kernel, I would be very grateful if you told me if it fits me, if it's compatible with ParanoidAndroid, and finally if you have a better suggestion for a kernel.
http://forum.xda-developers.com/showthread.php?t=1691401
read the first post of the thread to find out if it's compatible with your ROM.
and try it to see if it suits you
If I'm running TWRP can I still download kernels that say they are meant for CWM?
yes
My phone just gets stuck in a black screen when I try to boot into recovery. It happend once a few days ago, and i soloved it by going again to stock by odin and rooting it again. It booted to recovery the first time, i flashed carbon rom nightly 26 and now when I try to update, it doenst boot again. What is happening?
Info+New Kernel/Recovery
francantabria said:
My phone just gets stuck in a black screen when I try to boot into recovery. It happend once a few days ago, and i soloved it by going again to stock by odin and rooting it again. It booted to recovery the first time, i flashed carbon rom nightly 26 and now when I try to update, it doenst boot again. What is happening?
Click to expand...
Click to collapse
Firstly: Please give more detailed information (which kernel do you use, which ROM did you use before the problem occurred?)
Secondly: It is possible that you can't acess recovery mode anymore when flashing new updates. Happens with CM 10.2 OTA Update right now. The solution would be to flash a new recovery using Heimdall (Open-Source ODIN alternative) [Didn't try that, but should theoretically work] or, mor simple, a new kernel. Dorimany v9.34 is suited perfectly for that. Download here: http://dorimanx.shine.sk/ .
H3llwar said:
Firstly: Please give more detailed information (which kernel do you use, which ROM did you use before the problem occurred
Secondly: It is possible that you can't acess recovery mode anymore when flashing new updates. Happens with CM 10.2 OTA Update right now. The solution would be to flash a new recovery using Heimdall (Open-Source ODIN alternative) [Didn't try that, but should theoretically work] or, mor simple, a new kernel. Dorimany v9.34 is suited perfectly for that. Download here: http://dorimanx.shine.sk/ .
Click to expand...
Click to collapse
Well, i used Carbon Rom for a few weeks, so that was definitly the rom. Talking about the kernel, I dont even know how to install one.. haha Now in kernel version it says..
3.0.64 CM gb07657a
[email protected] #1 (I dont know what kernel it is)
Yeah but even if I dont want to flash an update, just boot recovery, I cant. Have you any link to know about Heimdall? Or how to install Dorimany? Im a beginner I have to say.
Thanks
francantabria said:
Well, i used Carbon Rom for a few weeks, so that was definitly the rom. Talking about the kernel, I dont even know how to install one.. haha Now in kernel version it says..
3.0.64 CM gb07657a
[email protected] #1 (I dont know what kernel it is)
Yeah but even if I dont want to flash an update, just boot recovery, I cant. Have you any link to know about Heimdall? Or how to install Dorimany? Im a beginner I have to say.
Thanks
Click to expand...
Click to collapse
You installed a Kernel while rooting your phone: Its the .tar that you have to put into the PDA section in ODIN. There are Kernels with .tar and .zip: .tar files are only flashable using Odin while .zip files are flashed using the recovery just like you flash ROMs. I guess your Kernel is a custom CM Kernel (CM for Cyanogen Mod). Carbon ROM is probably based on CM. There is currently no other workaround to get your recovery back then flashing a new kernel/recovery. I am currently working on an easy workaround for this problem, but it will take a while.
Dorimanx is downloadable here http://dorimanx.shine.sk/ and should be compatible: Just flash it like you did when rooting your phone in the beginning, just with Dorimanx .tar in PDA. Recovery should work again afterwards.
My mistake: It's Dorimanx, not Dorimany
Hit Thanks and just ask if you need additional help!
H3llwar said:
You installed a Kernel while rooting your phone: Its the .tar that you have to put into the PDA section in ODIN. There are Kernels with .tar and .zip: .tar files are only flashable using Odin while .zip files are flashed using the recovery just like you flash ROMs. I guess your Kernel is a custom CM Kernel (CM for Cyanogen Mod). Carbon ROM is probably based on CM. There is currently no other workaround to get your recovery back then flashing a new kernel/recovery. I am currently working on an easy workaround for this problem, but it will take a while.
Dorimanx is downloadable here http://dorimanx.shine.sk/ and should be compatible: Just flash it like you did when rooting your phone in the beginning, just with Dorimanx .tar in PDA. Recovery should work again afterwards.
My mistake: It's Dorimanx, not Dorimany
Hit Thanks and just ask if you need additional help!
Click to expand...
Click to collapse
Yeah, I remember.. it was siyah kernel.
So in your opinion I should flash Dorimanx by Odin then? No other way to fix isnt it? and.. in dorimanx page, which one of all them should I download?
francantabria said:
Yeah, I remember.. it was siyah kernel.
So in your opinion I should flash Dorimanx by Odin then? No other way to fix isnt it? and.. in dorimanx page, which one of all them should I download?
Click to expand...
Click to collapse
1. Yes you should
2. Not right now, maybe in the future, flashing recovery.img using Heimdall would probably help, but I didn't try it myself and using Heimdall is quite complex
3. In General: The newest .tar (9.34/8.34) as you can't use .zip files
When you want to use Stock Samsung ROM: Version 8
When you want to use CM/AOKP based ROM: Version 9
Remember: No ICS Support!
Hit Thanks and just ask if you need more help.
H3llwar said:
1. Yes you should
2. Not right now, maybe in the future, flashing recovery.img using Heimdall would probably help, but I didn't try it myself and using Heimdall is quite complex
3. In General: The newest .tar (9.34/8.34) as you can't use .zip files
When you want to use Stock Samsung ROM: Version 8
When you want to use CM/AOKP based ROM: Version 9
Remember: No ICS Support!
Hit Thanks and just ask if you need more help.
Click to expand...
Click to collapse
Ok.
But every aosp rom, like Carbon PA and these are based either in AOKP or CM, isnt it?
The newest one is 9/39, is that the one?
francantabria said:
Ok.
But every aosp rom, like Carbon PA and these are based either in AOKP or CM, isnt it?
Click to expand...
Click to collapse
CM & AOKP are actually based on AOSP, so Yes, every AOSP ROM should work.
H3llwar said:
CM & AOKP are actually based on AOSP, so Yes, every AOSP ROM should work.
Click to expand...
Click to collapse
I did what you said and after installing Carbon Rom again recovery is gone.. so I suposse it is Carbon problem. I will do it again and install a different rom
francantabria said:
I did what you said and after installing Carbon Rom again recovery is gone.. so I suposse it is Carbon problem. I will do it again and install a different rom
Click to expand...
Click to collapse
I agree, the problem results of the ROM: But you have to flash dorimanx after carbon because carbon replaces the current kernel with its own CM custom Kernel. It should work just fine with carbon when it's flashed after installing carbon.
I searched a lot but nothing found. On Gingerbread I had no problems. Now on Jellbean there is a problem. CWM gives bootloop and PhilZ kernels are for specified roms, which actually don't match my kernel XXMS7 XEO. Is there any other way to make nandroid backup or just through custom recovery? I don't need any other functionality just full backup in case I screw something or occasionally refresh everything with all set up.
blackfire74 said:
I searched a lot but nothing found. On Gingerbread I had no problems. Now on Jellbean there is a problem. CWM gives bootloop and PhilZ kernels are for specified roms, which actually don't match my kernel XXMS7 XEO. Is there any other way to make nandroid backup or just through custom recovery? I don't need any other functionality just full backup in case I screw something or occasionally refresh everything with all set up.
Click to expand...
Click to collapse
Did you try dorimanx by GreekDragon or Chhapil?
And I think that you may flash latest Philz kernel cause I did it and had no problem.... But try using dorimanx and also there's another option... Apolo by pedestre....
PS this is a development thread... Questions must be asked in question answer forum
JB Kernels
Here's the link to the kernels I use for my S2
Apolo Kernel - Here (Thread here)
Dorimanx by @GreekDragon Here (Thread Here)
Philz XWMS3 Kernel Here
How about Jeboo kernel? Are these three kernels above match XXMS7 rom?
blackfire74 said:
How about Jeboo kernel? Are these three kernels above match XXMS7 rom?
Click to expand...
Click to collapse
As per what I know, if you're on Stock Jellybean GT I9100 then they should work... I've not used jeboo and hence don't have idea about it
There is no way i can experiment. I just need to know what will exactly work with my firmware as i can't loose anything set up on my phone. So, i need working kernel, custom recovery and be able to make a nandroid backup without any risk of bootloop or whatever, then i may experiment.
blackfire74 said:
There is no way i can experiment. I just need to know what will exactly work with my firmware as i can't loose anything set up on my phone. So, i need working kernel, custom recovery and be able to make a nandroid backup without any risk of bootloop or whatever, then i may experiment.
Click to expand...
Click to collapse
If you have already rooted then use titaniumbackup to backup your apps and data....additionally you can use third party apps like superbackup to backup contacts call logs and sms...then you should have your important stuffs backed up....then flash Apolo kernel...you should be done....
Sent from my Xperia J using XDA Labs