Hey guys,
I have been flashing to different rom lately and loving not using the stock standard samsung roms anymore. I am using a Galaxy S2 with Resurrection Remix v1.0 with using the CWM.zip that came with it.
Now when im trying to install the RR v1.1zip packages *on my SDCard* through CWM. It tries mount the sd card and just comes with a message saying e:signature not enabled or something about it being unable to verify the signature..and just aborts the installation.
Any ideas?
Try toggling the signature verification, or flash some other kernel temporarily and flash resurrection 1.1
Sent from my GT-I9100 using xda premium
Ahhh ive noticed since i went to rr v1.1. It is only using the stock recovery. Which is a good kernal to use with ressurection v1.1. Ill have to see how to install a new kernal too. Before ressurection i was using lightning and that had cwm.
Cheers
May be try flash Lightening rom via Odin..and try back this rom..it will work...
rajaa_sekaran said:
May be try flash Lightening rom via Odin..and try back this rom..it will work...
Click to expand...
Click to collapse
That worked a treat, thanks a bunch mate!
Related
I had been running the official Samsung version of ICS on my phone for a few months with no problems (updated via Kies).
Last weekend I rooted my phone but afterwards WiFi stopped functioning. When I tap the icon in the pull down menu it goes green, and then greys over. In settings it says Wifi is turning on, but it never does.
I tried flashing a new custom ROM, new Kernel, reverting to stock ICS from Samsung, unrooting. All with no success. Same issue.
Finally I flashed back to gingerbread in the hope that it was an ICS issue. That didn't work either!
I've searched and searched but found very little info. For the record, yes I've factory reset and wiped cache etc etc.
I'm open to any suggestions at this stage. Thanks.
Try a different baseband/modem.
TheStickMan said:
Try a different baseband/modem.
Click to expand...
Click to collapse
Thanks I'll give it a try. Is that not more to do with the mobile network though than with wifi?
cork-spotters said:
Thanks I'll give it a try. Is that not more to do with the mobile network though than with wifi?
Click to expand...
Click to collapse
I think changing baseband will not do anything.wifi is controlled via kernal i guess.
http://code.google.com/p/android/issues/detail?id=28036#makechanges
Try methods mentioned there.if you are lucky enough you might get your wifi back.good luck.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
wi fi after resurrection 2.6
nuwanmw1988 said:
I think changing baseband will not do anything.wifi is controlled via kernal i guess.
http://code.google.com/p/android/issues/detail?id=28036#makechanges
Try methods mentioned there.if you are lucky enough you might get your wifi back.good luck.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
I had that probem after I upgraded to resurrection 2.6 from 2.5.1. The problem persisted even after I restored the 2.5.1. (The camera also stopped working) I solved the problem with flashing the phone with the stock ROM. I am also interested to know why it happened? (Problem with 2.6 resurrection?)
suchiqaz said:
I had that probem after I upgraded to resurrection 2.6 from 2.5.1. The problem persisted even after I restored the 2.5.1. (The camera also stopped working) I solved the problem with flashing the phone with the stock ROM. I am also interested to know why it happened? (Problem with 2.6 resurrection?)
Click to expand...
Click to collapse
Very interesting actually. Thinking about it I flashed to Resurrection Remix 2.5.3 almost immediately after rooting, and I think this is when my problems started. Only thing is that I've since flashed backwards and forwards through various ROMs, Kernals and versions of Android to no avail. Have you a link to the stock ROM you used?
I had this problem when I first got Resurrection remix 2.5.3, the problem lied in the siyah kernel I was using. I proceeded to wipe my phone (factory,dalvik,etc) and reinstalled the resurrection remix. But this time I went to custom installation and changed the siyah to the newer version or fluxi and wi fi started working again.
Samzung said:
I had this problem when I first got Resurrection remix 2.5.3, the problem lied in the siyah kernel I was using. I proceeded to wipe my phone (factory,dalvik,etc) and reinstalled the resurrection remix. But this time I went to custom installation and changed the siyah to the newer version or fluxi and wi fi started working again.
Click to expand...
Click to collapse
Thanks for the reply. I'm running Resurrection Remix version 2.6 at the moment and flashed the Siyah 3.4.1. Still the same problem.
Almost certainly the problem first happened when I installed RR last weekend, but nothing I do seems to solve it!
Any further suggestions?
Hi guys,
I'm using jelly Blast ROM on 2.6.35.7 kernel and have lost GPS function; anyone any clues on what could have gone wrong?
Cheers
Do a Google search to see if this is a widespread problem, or a one off case. If only you are facing this problem, then try dirty flashing a new kernel, or else switching roms (after a nandroid backup of course)
Sent from my GT-I9100
If I helped you, please hit the thanks button!
may be it's a bug in that rom
srt99 said:
may be it's a bug in that rom
Click to expand...
Click to collapse
I've switched rom to Simplicity V5 and still no GPS. It would seem to follow the problem may be with the kernel. I've tried re-flashing 2.6.35.7 with clockwork recovery but I'm getting installation aborted message each time (side loading error). What am I doing wrong?
chubster1960 said:
I've switched rom to Simplicity V5 and still no GPS. It would seem to follow the problem may be with the kernel. I've tried re-flashing 2.6.35.7 with clockwork recovery but I'm getting installation aborted message each time (side loading error). What am I doing wrong?
Click to expand...
Click to collapse
Are you flashin it with cwm or e3 ??
I got similar error when i try to flash stock kernel with cwm..
Try with stock recovery mode...
Sent from my GT-S5830i using xda app-developers app
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.
Hi everyone,
I have a Galaxy S2 i9100.
I just came from a RootBox (forgot which version - one the newest anyway). Did not suit me. I went to install the Resurrection Remix ROM from here.
I do all the right steps in the guidelines, but I don't encounter the AROMA installer. It just flashes the ROM. It work, but I can't apply any customizations.
Any ideas why it goes wrong?
Other people with same problem here: here but I don't have write permissions there yet.
Thanks!
stairCase said:
Hi everyone,
I have a Galaxy S2 i9100.
I just came from a RootBox (forgot which version - one the newest anyway). Did not suit me. I went to install the Resurrection Remix ROM from here.
I do all the right steps in the guidelines, but I don't encounter the AROMA installer. It just flashes the ROM. It work, but I can't apply any customizations.
Any ideas why it goes wrong?
Other people with same problem here: here but I don't have write permissions there yet.
Thanks!
Click to expand...
Click to collapse
I think it's a ROM problem if other people experience this too.Try flashing DorimanX 9.38 kernel,then reflash ROM.
GamingDj said:
I think it's a ROM problem if other people experience this too.Try flashing DorimanX 9.38 kernel,then reflash ROM.
Click to expand...
Click to collapse
Weird. Did what you said. Flashed the new kernel (after cleaning the old one). Then flashed the ROM.
Same effect. No AROMA installer.
So, any idea for other kernels?
Anyone? --^
Maybe the ROM file's corrupted or broken? Try redownloading it, or do a checksum test.
Same problem for me aswell. I took the last .zip from here: http://www.androidfilehost.com/?a=show&w=files&flid=6564 but no Aroma for me aswell.
Hi Guys,
even i faced the same proble while installing KitKat on my SII.
it works fine but not satisfied after flashing ROM..
Kindly hepl me...
There is nothing wrong with your device/download: Aroma is just not used anymore.
So if you want to flash a different kernel, you'll have to do it manually.
Hello I need your help about installing gustavos kernel to my galaxy S2. I flash resurrection rom which is awesome and I also want to change my kernel. But when i try to flash it, I stuck at boot screen. I try also kernel wipe before flashing but it is still same. Can anybody help me please??
Thanks indeed...
ottoasd said:
Hello I need your help about installing gustavos kernel to my galaxy S2. I flash resurrection rom which is awesome and I also want to change my kernel. But when i try to flash it, I stuck at boot screen. I try also kernel wipe before flashing but it is still same. Can anybody help me please??
Thanks indeed...
Click to expand...
Click to collapse
I am using RR as well and as far as I saw in ROM's topic, many users have faced problems with custom kernels. Especially Dorimanx versions. I only once tried Gustavo and installed it without any problem. Just flashed it in CWM and that was all. I can say that make a full wipe, install RR first and then Gustavo. That should be OK.
But after a few days with Gustavo, I returned back to the original kernel of RR. Because it is stable and no major problems. So my advice is use the ROM with it's own original kernel.
Maybe the flash wasn't clean.. Try Kernel wipe script.
banjara said:
Maybe the flash wasn't clean.. Try Kernel wipe script.
Click to expand...
Click to collapse
sertahn said:
I am using RR as well and as far as I saw in ROM's topic, many users have faced problems with custom kernels. Especially Dorimanx versions. I only once tried Gustavo and installed it without any problem. Just flashed it in CWM and that was all. I can say that make a full wipe, install RR first and then Gustavo. That should be OK.
But after a few days with Gustavo, I returned back to the original kernel of RR. Because it is stable and no major problems. So my advice is use the ROM with it's own original kernel.
Click to expand...
Click to collapse
I already try kernel wipe script but the result is same. Generally i flash with full wipe ı dont know where i make a mistake. Maybe i should wait for stable kernel)
I have flashed Gustavo's 26/3 kernel many times before but recently the same kernel file gave me status 7 error.
Try downloading your kernel file again. Maybe the file has gone corrupt.