hi, i am requesting for the kernel from the CM6 liberty froyo rom. Please help! thnx in advance!
please i flashed a oc kernel in android development and now wifi is broken and so is wifi hot spot please help!i didnt do a nandroid backup
I'm assuming your running a cm6 froyo rom. If so just flash the rom again from attn1 with a full wipe. Its going to suck losing all yet sh*t but atleast you'll get yet wifi back. In another forum script will be coming out with a new kernal soon.
damnit....
I never did a wipe after installing the OC kernel, just wiped Cache partition and Dalvik then reflashed whatever version of CM6 I was using, I haven't had any problems that I have noticed.
Just reflash the rom ad wipe the cache. You wont lose anything.
Sent from my Liberty using XDA App
i did just that thanks everybody for your help!
Hi all,
sorry if this has been asked before - I've had a look but found nothing definitive.
Last week I upgraded from stock froyo to Quarx's CM10, which although looking good, makes my phone too hot and the battery is not impressed. Having recently had my phone out of action due to a battery issue while using CM9, I'm now concerned enough to have made the decision to move backwards.
So, not wanting to go back to Froyo, I'd like to go back to a CM7 variant. As far as I know, I'm still on a Froyo kernel - so can I just flash a CM7 ROM (with a wipe etc), or do I need to go back to bootloader stage to restore the original SBF?
Thanks for your help.
wipe data + cache is enough
Sent from my MB526 using xda premium
Really? I'd have thought a full wipe at least - will give it a go. Thanks.
simon211175 said:
Hi all,
sorry if this has been asked before - I've had a look but found nothing definitive.
Last week I upgraded from stock froyo to Quarx's CM10, which although looking good, makes my phone too hot and the battery is not impressed. Having recently had my phone out of action due to a battery issue while using CM9, I'm now concerned enough to have made the decision to move backwards.
So, not wanting to go back to Froyo, I'd like to go back to a CM7 variant. As far as I know, I'm still on a Froyo kernel - so can I just flash a CM7 ROM (with a wipe etc), or do I need to go back to bootloader stage to restore the original SBF?
Thanks for your help.
Click to expand...
Click to collapse
yap just wipe data/ factory reset and wipe cache partition and flash zip !
Hit thanks button if i helped you :good:
Just to let you know I downgraded today to Motorola Ice Gun rom and everything has gone smooth.
Full wipe + cache + dalvik cache will be fine.
It's actually a very fast and stable rom if you were considering trying it
Its actually a full wipe, effectively
Sent from my MB526 using xda premium
Does wireless internet sharing work? Thinking about reverting CM10>CM9 back to CM7, as 7 was the last one I could share internet.
And no, apps from the market dont work either.
Why does only CM10 not work for me?
Known facts:
-Unimportant, but: All ROM I tried worked (many variants of CM 7.x, many variants of CM9, MIUI, WIUI), except the JB ROMs.
-Neither of the working ROMs have, had 2nd boot. (I did not find not-CM10 roms with 2nd boot...)
-With CM10 nightlies before 2013 ~january: after installing CM10 I could not wipe dalvik cache. the screen refreshed when I clicked on it.
-I tried the march 26 nightly, i could wipe dalvik, but it won't boot the same way it did not before.
What happens:
-Switch on, Motorola logo, blue, than red led (which signals it is 2nd boot) and it stucks for a minute, NO boot animation, bootloop
-Overinstalling (CM9 wipe data, cache, dalvik, flash CM10, than flash another CM10 over CM10 without wiping) won't help. For some phones it worked, don't think im so bad.
-I tried clean install from stock
Thoughts:
-It seems like it's losing some kind of permissions about R/W internal memory (thinking from the previous dalvik wipe issue)
-It has (had???) problem with dalvik wiping (before the screen just refreshed upon clicking the menu, now it seems to do what it should)
-It installs really fast...
-It has problem with 2nd boot? Maybe that's why it won't start
-It does not have boot animation. Does not freeze either, so: can it be, that it does not install properly? Problems with drive format?
Something that also came to my mind (idk why):
-Can ext3/ext4 f__k it up?
-How 2nd boot can make it not to start?
Manners I do know nothing about:
-Kernel (can it cause problems?)
-BL version (does it matter?)
Firstly what phone model (MB525 green or red/MB526).
I would highly recommend flashing your stock sbf, re-rooting your phone, installing the latest 2ndInit (2.3), and then flashing CM10.
As far as I know CM10 is ext4, so format to that if you encounter any further problems.
Kernel - stick with what comes in the CM10 nightlies.
BL - depends on your phone.
z3ro-grav1ty said:
Firstly what phone model (MB525 green or red/MB526).
I would highly recommend flashing your stock sbf, re-rooting your phone, installing the latest 2ndInit (2.3), and then flashing CM10.
As far as I know CM10 is ext4, so format to that if you encounter any further problems.
Kernel - stick with what comes in the CM10 nightlies.
BL - depends on your phone.
Click to expand...
Click to collapse
1:MB525 bayer module
2:Tried, same problem
3:format from CWM before flash?
4:should i pre-install any kernel, or not then?
Hi!
I've had the same problem. Also on MB525, red lense. I have not managed to make it work either. Preinstalling kernel does not work for me. Formatting does not work either.
However, there is a possible solution, which I have not had the time to try out yet, and was suggested to me in this thread:
http://forum.xda-developers.com/showthread.php?t=1782832&page=132
Simply put, you can try flashing a custom SBF with CM10 pre-loaded on it through RSDLite, and then update to the latest versions. Just head over to this thread over here:
http://forum.xda-developers.com/showthread.php?t=1691901
And try with one of the 2nd boot SBFs. I will also be trying this method out shortly. If you manage to get anything done with this method, please report here, so that I know as well!
-----
If you find this helpful, please hit the Thanks! button! :highfive:
Eneekay said:
Hi!
I've had the same problem. Also on MB525, red lense. I have not managed to make it work either. Preinstalling kernel does not work for me. Formatting does not work either.
However, there is a possible solution, which I have not had the time to try out yet, and was suggested to me in this thread:
http://forum.xda-developers.com/showthread.php?t=1782832&page=132
Simply put, you can try flashing a custom SBF with CM10 pre-loaded on it through RSDLite, and then update to the latest versions. Just head over to this thread over here:
http://forum.xda-developers.com/showthread.php?t=1691901
And try with one of the 2nd boot SBFs. I will also be trying this method out shortly. If you manage to get anything done with this method, please report here, so that I know as well!
-----
If you find this helpful, please hit the Thanks! button! :highfive:
Click to expand...
Click to collapse
are you saying that 2ndboot SBFs exist? where have I been? under a rock? my god..
gonna try it in a few days, but i'm scared about the failure as it never worked before, but now you gave me hope thnx. :good:
gyorgyszemok said:
are you saying that 2ndboot SBFs exist? where have I been? under a rock? my god..
gonna try it in a few days, but i'm scared about the failure as it never worked before, but now you gave me hope thnx. :good:
Click to expand...
Click to collapse
Even if you fail, you can always wipe/flash an SBF if necessary and revert to your nandroid backup. I might try it today, if I have enough time, but no promises. When you try, please report here.
It seems I have BL version 5, but from an SBF with a size of ~35mb
Each time my phone went so bad I couldn't get to CWM:
-RSD Lite Flash: Éclair (JORDN_U3_97.21.51.sbf)
-Stock Recovery wipe cache, data
-Root
-install 2nd init
-Restore with cwm backup&restore "2011-06-11.14.14.27" which I downloaded from a guide
-Wipe data, cache, dalvik
-Reboot instantly into Bootloader
-RSD Lite Flash: firmware.sbf with CG31.smg version 5 (downloaded from the same site where "2011-06-11.14.14.27" cwm backup was)
-This flash it fast, cuz the firmware.sbf is ~35mb
-Reboots (via RSD Lite) to Froyo and it's rooted...
So, my BL version is...? 5? How important is this?
I started trying out some of the SBFs. From now on I will be reporting everything on this Thread:
http://forum.xda-developers.com/showthread.php?t=1782832&page=132
Eneekay said:
I started trying out some of the SBFs. From now on I will be reporting everything on this Thread:
http://forum.xda-developers.com/showthread.php?t=1782832&page=132
Click to expand...
Click to collapse
It seems like our phones are more alike then the others. Do you usually recover with the fixed sbf and the 2011. dated nandroid backup? whats your cg version? mine's 5. so it's more likely the cause that we have gingerbread CG version...
gyorgyszemok said:
It seems like our phones are more alike then the others. Do you usually recover with the fixed sbf and the 2011. dated nandroid backup? whats your cg version? mine's 5. so it's more likely the cause that we have gingerbread CG version...
Click to expand...
Click to collapse
Yes, I recover the same way you do, and the CG version is the same... This is what I thought as well, that it is because of the Gigerbread CG. I have no idea about any workarounds though...
Eneekay said:
Yes, I recover the same way you do, and the CG version is the same... This is what I thought as well, that it is because of the Gigerbread CG. I have no idea about any workarounds though...
Click to expand...
Click to collapse
-But I don't know if we have the Gingerbread CG like many others, why don't they have this problem? I could guess pretty much people recovered their phone the same way like us...
-It must be something about the kernel the CM10 uses, and the CG version! ...or the drive format (ext3,4)?
-I also read about your failures (in the other topic) flashing modded SBFs, so I definitely won't try them until we have a solution.
-Months earlier I found something about this problem (CMX bootloop), and the user could flash 2nd init CMX, but not 2nd boot. I haven't found that entry since then... And neither did I find 2nd init CMX ROMs.. Quarx must have took it down rendering them useless.
Argh! It's just so annoying! Stuck at ICS, the highest ROM available... And that's so buggy! I use Euroskank CM 7.2 now... But it's ugly (was... I modded it...), and it's like mentally disabled compared to a JB rom...
Are there any other JB defy ROMs out there? Which do not rely upon Quarx's build?
gyorgyszemok said:
-But I don't know if we have the Gingerbread CG like many others, why don't they have this problem? I could guess pretty much people recovered their phone the same way like us...
-It must be something about the kernel the CM10 uses, and the CG version! ...or the drive format (ext3,4)?
-I also read about your failures (in the other topic) flashing modded SBFs, so I definitely won't try them until we have a solution.
-Months earlier I found something about this problem (CMX bootloop), and the user could flash 2nd init CMX, but not 2nd boot. I haven't found that entry since then... And neither did I find 2nd init CMX ROMs.. Quarx must have took it down rendering them useless.
Argh! It's just so annoying! Stuck at ICS, the highest ROM available... And that's so buggy! I use Euroskank CM 7.2 now... But it's ugly (was... I modded it...), and it's like mentally disabled compared to a JB rom...
Are there any other JB defy ROMs out there? Which do not rely upon Quarx's build?
Click to expand...
Click to collapse
CM10 uses ext4, in bootmenu (after you press volume down at the blue led during boot) go to tools and then file systems (something like that) then you can format to ext4 (wipes data and cache).
At the moment that's all I can really help you with because my model (defy+) works differently to yours.
All I can recommend is working from stock. Also isn't there a fix for some MB525 models?
http://forum.xda-developers.com/showthread.php?t=2124536
Sent from my MB526 using xda premium
thekguy said:
http://forum.xda-developers.com/showthread.php?t=2124536
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks! Will check it out.
z3ro-grav1ty said:
CM10 uses ext4, in bootmenu (after you press volume down at the blue led during boot) go to tools and then file systems (something like that) then you can format to ext4 (wipes data and cache).
At the moment that's all I can really help you with because my model (defy+) works differently to yours.
All I can recommend is working from stock. Also isn't there a fix for some MB525 models?
Click to expand...
Click to collapse
I know how to format, but thanks for answering.
It seems the root of the problem comes from the fixed sbf (so called firmware.sbf) with the CG version 5, which does something about downgrading. As stated in the other link we should upgrade to BL7 with a Defy + SBF, but I don't want to make that risk...
SO: The problem, why we can't make CM10 works is that our Defy MB525 has CG31.smg version of 5 from the downgrading fixed SBF!
How to fix that? Should I really upgrade to BL version 7? What can it do with my device?
gyorgyszemok said:
I know how to format, but thanks for answering.
It seems the root of the problem comes from the fixed sbf (so called firmware.sbf) with the CG version 5, which does something about downgrading. As stated in the other link we should upgrade to BL7 with a Defy + SBF, but I don't want to make that risk...
SO: The problem, why we can't make CM10 works is that our Defy MB525 has CG31.smg version of 5 from the downgrading fixed SBF!
How to fix that? Should I really upgrade to BL version 7? What can it do with my device?
Click to expand...
Click to collapse
+1
It seems to me that our beloved Defy is not much worth the trouble anymore... I am staying on CM7 which is amazingly fast and stable, and thinking about grabbing a new Android headset soon...
If you've got a red lens, you can upgrade boot loader version, and you'll have to flash a battery fix for gb and ics roms, and jb will work fine without it. If you have a green lens, then you will not be able to use camera with stock. It will work with jb roms though
Sent from my MB526 using xda premium
thekguy said:
If you've got a red lens, you can upgrade boot loader version, and you'll have to flash a battery fix for gb and ics roms, and jb will work fine without it. If you have a green lens, then you will not be able to use camera with stock. It will work with jb roms though
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Bootloader? Could you point us to the right direction?
You mentioned that the flashing is fast. So i think it may not flash properly. So flash 2 or 3 times with same rom. This happend to my old captivate. Captivate devs suggesting a second flash for their roms. (Only formating was occur during first flash in some devices. Thats why they suggest second flash)
Thanks
Sent from my Motorola Electrify using Tapatalk 2
Eneekay said:
Bootloader? Could you point us to the right direction?
Click to expand...
Click to collapse
You can try flashing a newer sbf( with higher bl version). It seems to work for some people
Hello,
I am having issues with my navigation and GPS locking when using KitKat ROMs. I have tried three ROMs so far to no avail (LiquidSmooth, Plain-Andy, and OSE). My current workaround is to flash to my Malladus ROM whenever I need to navigate, as that is my most stable ROM so far. I really wish I didn't have to do this, though!
If anyone has any insight, it would be greatly appreciated. I wipe my phone's cache, dalvik, and data before every flash, should I do an advanced wipe and wipe everything?
AOKP 4.3 works fine with the GPS fix in the thread.
http://forum.xda-developers.com/showthread.php?t=2546994
khaytsus said:
AOKP 4.3 works fine with the GPS fix in the thread.
http://forum.xda-developers.com/showthread.php?t=2546994
Click to expand...
Click to collapse
Appreciate this, thanks!