The Quarx CM10 24 October build with new kernel is the sign of things to come...
But it can't be soft unlocked yet so no wi-fi tether on my Defy, which is a major reason for my rooting/upgrading.
Is there a guide to reverting to the 9 October build (or even CM7.2)?
I can't get to any recovery/boot menu and the USB port on my Defy hasn't worked for some time. Wifi is fine so I've downloaded the 9 October build again.
Thanks!
I think there is a soft unlock for the cm10, check the defy custom kernel thread in general section . But if you really want to go back to cm7.2, flash + data wipe is enough. Same for 9th Oct build
Sent from my MB526 using xda premium
thekguy said:
I think there is a soft unlock for the cm10, check the defy custom kernel thread in general section . But if you really want to go back to cm7.2, flash + data wipe is enough. Same for 9th Oct build
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Ok, I'll check. Thanks... I think I meant 9 Sept build BTW!
I'm not sure how you flash under 7.1.2 - the old menus don't come up in the same way.
To flash cm or any cm build go to custom recovery via boot menu, flash zip and wipe data. What do you mean by your last statement that the menus don't come up the same way?
The soft unlocking is at: http://forum.xda-developers.com/showthread.php?t=1909242
Sent from my MB526 using xda premium
My boot menu doesn't work - whichever option I choose it just restarts the M525. Strange. Perhaps it's tied in to the faulty micro-USB port... the port certainly worked when I rooted it a month or so ago.
Until I can get the UK Three network on the M525 I'm using an unrooted M526 I'd hoped to have on ebay by now.
>>>UPDATE<<< Ah, put SIM card back from M526 and am holding down volume switch at the blue light and that lets me get to boot menu.
I'm going back to CM7.2 as that should give me BBC iPlayer function (doesn't work with ICS/JB) and soft unlock which doesn't need to be reset each reboot.
OK, it's not loadng yet (stuck at red M) but I'll have another go tomorrow!
brunc said:
My boot menu doesn't work - whichever option I choose it just restarts the M525. Strange. Perhaps it's tied in to the faulty micro-USB port... the port certainly worked when I rooted it a month or so ago.
Until I can get the UK Three network on the M525 I'm using an unrooted M526 I'd hoped to have on ebay by now.
>>>UPDATE<<< Ah, put SIM card back from M526 and am holding down volume switch at the blue light and that lets me get to boot menu.
I'm going back to CM7.2 as that should give me BBC iPlayer function (doesn't work with ICS/JB) and soft unlock which doesn't need to be reset each reboot.
OK, it's not loadng yet (stuck at red M) but I'll have another go tomorrow!
Click to expand...
Click to collapse
I've followed http://forum.xda-developers.com/showthread.php?t=1054447 but am stuck either at the blue skateboarding Android or the red M depending on which course I follow...
This evening I'll be trying the May 6 build of CM7 as there weren't any revisions to that for months, so I take it to be very reliable.
I think you forgot to wipe data before flashing, hence the bootloop
Sent from my MB526 using xda premium
I've tried every alternative I can think of but no joy.
Last week I tried reverting to earlier versions of CM10 and I can get them to load but I have to go through setup every reboot.
Looking at other answers here I think this could mean my Froyo is corrupted, which is a bit of a problem as my micro-USB port doesn't work (making flashing a replacement sbf an issue).
I'm growing to like Holo on the M526 though. It's small, quick and looks like JB - if only the M526 would tether!
>>>>Edit: I had hoped that FoxFi latest version: 1.91.3 might work but it doesn't.<<<<
Related
Hi I just got my new droid 2 and flashed cm7 2.3.7 onto it. I was sad to find out that the camera doesn't work on this version at all. I was hoping to flash liberty but i don't know if i can just flash it over cm7 or if i have to flash my rom back to stock. Any help or advice would be great!
Thanks,
Albinoman
The lastest version of CM7 has a working camera. It's said not to let the screen lock though with the camera app open or it will FC. Dumb I know, but they are making progess.
Can I just flash the new one over my current one? Do I have to wipe data/cache?
Sent from my DROID2 using xda premium
So ive had my droid R2D2 for about 5 months now, and im just starting to experiment with custom roms. So far ive been trying to use ROM manager, and i used it to install clockwork recovery mod, but it didn't take nearly as long as it seemed to have taken other people to flash. On top of that, no matter what i try whether i try to boot into recovery from ROM manager, or just turn my phone off and then hold the power button with the x hard button on my keyboard, it takes me to a picture of the android guy with an exclamation point, and when i try to hit the search hard button on my keyboard to bring up menu options it doesnt do anything. As for right now im just trying to back up my current stock ROM, but i would eventually like to install a custom rom as well. Any suggestions or highly recommended ROM's either? I was gonna go with cm7 but if there were others someone highly suggested i would like to know about them.
Albinoman said:
Can I just flash the new one over my current one? Do I have to wipe data/cache?
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Wipe cache and delvik cache and you can flash over it.
Awesome thanks!
Sent from my DROID2 using xda premium
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.
I seem to be having problems with flashing the 2nd boot quarx roms
I do a full data + cache + dalvik wipe, install the rom + gapps, then wipe cache + dalvik and restart the phone..
It boots up and is laggy as hell but it shouldn't be because no one else has such problems.
Do I have to flash a kernel or something? I've never flashed one before and all my previous cm7, cm9, cm10 (not 2nd boot) worked perfectly without it
Any help? I'm still on a very old build and wanna use the current ones but can't seem to get it to work
I'm using a regular green lens 525
Sent from my MB525 using Tapatalk 2
I've been installing these roms on 2nd init.. Do I HAVE to install it on 2nd boot only?
Sent from my MB525 using Tapatalk 2
sixaxis94 said:
I seem to be having problems with flashing the 2nd boot quarx roms
I do a full data + cache + dalvik wipe, install the rom + gapps, then wipe cache + dalvik and restart the phone..
It boots up and is laggy as hell but it shouldn't be because no one else has such problems.
Do I have to flash a kernel or something? I've never flashed one before and all my previous cm7, cm9, cm10 (not 2nd boot) worked perfectly without it
Any help? I'm still on a very old build and wanna use the current ones but can't seem to get it to work
I'm using a regular green lens 525
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I can't even get my green lens to boot into any build past 0912... I've had no problem with cm7, cm9 or cm10 until 0924 and later. I'm sorry I can't help but I'm throwing my hat in the ring..
bulbouscorm said:
I can't even get my green lens to boot into any build past 0912... I've had no problem with cm7, cm9 or cm10 until 0924 and later. I'm sorry I can't help but I'm throwing my hat in the ring..
Click to expand...
Click to collapse
Many ppl have/had this problem (me too).
The workaround is flashing another sbf.
Could you gave details of your parent sbf?
sixaxis94 said:
I've been installing these roms on 2nd init.. Do I HAVE to install it on 2nd boot only?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
No, 2ndboot is set automatically after flash. And the only thing u should change in bootmenu is vsels. Governor must be interactive - don't change it
Your workaround might be similar as above, especially if u your last stock ROM was froyo 2.2.1
sixaxis94 said:
I seem to be having problems with flashing the 2nd boot quarx roms
I do a full data + cache + dalvik wipe, install the rom + gapps, then wipe cache + dalvik and restart the phone..
It boots up and is laggy as hell but it shouldn't be because no one else has such problems.
Do I have to flash a kernel or something? I've never flashed one before and all my previous cm7, cm9, cm10 (not 2nd boot) worked perfectly without it
Any help? I'm still on a very old build and wanna use the current ones but can't seem to get it to work
I'm using a regular green lens 525
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
To get rid of the laggs you should also install the kernel update http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/update_for_18.10_v4.zip after flashing the Nightly from 18th-Oct
Then you should be fine
corrinti said:
Many ppl have/had this problem (me too).
The workaround is flashing another sbf.
Could you gave details of your parent sbf?
No, 2ndboot is set automatically after flash. And the only thing u should change in bootmenu is vsels. Governor must be interactive - don't change it
Your workaround might be similar as above, especially if u your last stock ROM was froyo 2.2.1
Click to expand...
Click to collapse
I've never messed with sbfs before so I have no idea.. Right now I don't even have a pc on me to use rsdlite or anything (traded mine for an ipad, haha)
Is it difficult to flash a new sbf?
Swift2603 said:
To get rid of the laggs you should also install the kernel update http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/update_for_18.10_v4.zip after flashing the Nightly from 18th-Oct
Then you should be fine
Click to expand...
Click to collapse
I flash this right after I flash the rom right?
A random question, does anyone have this problem: when someone calls, it sometimes takes like 10 seconds for the phone to match the number to an existing contact.. As in, if my mom calls, it shows up her phone number and takes around 10 seconds for "mom" to appear as the caller
Sent from my MB525 using Tapatalk 2
sixaxis94 said:
I've never messed with sbfs before so I have no idea.. Right now I don't even have a pc on me to use rsdlite or anything (traded mine for an ipad, haha)
Is it difficult to flash a new sbf?
I flash this right after I flash the rom right?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Yes flash it right after the ROM.
Flashing an sbf is not difficult, but you will need a PC.
Regarding your random question: It should be fixed in the latest Nightly. I just tried it
Swift2603 said:
Yes flash it right after the ROM.
Flashing an sbf is not difficult, but you will need a PC.
Regarding your random question: It should be fixed in the latest Nightly. I just tried it
Click to expand...
Click to collapse
The only sbf I've heard of is something like 'Nordic deblur'.. Is that what I'm supposed to flash?
And also, is it worth doing all that? I mean, should I just stay with the stuff I have now and wait for a rom that's compatible without the sbf stuff? I don't really have much of a problem since I'm only using my phone for calling, texting and playing music
Regarding the side question, thanks.. It is kinda irritating, but I can live with it
Another side question.. Has epsylon stopped working on the defy permanently?
sixaxis94 said:
The only sbf I've heard of is something like 'Nordic deblur'.. Is that what I'm supposed to flash?
And also, is it worth doing all that? I mean, should I just stay with the stuff I have now and wait for a rom that's compatible without the sbf stuff? I don't really have much of a problem since I'm only using my phone for calling, texting and playing music
Regarding the side question, thanks.. It is kinda irritating, but I can live with it
Another side question.. Has epsylon stopped working on the defy permanently?
Click to expand...
Click to collapse
Well, with a limited usage you can stay with your last built. Don't suppose that newer CM10, at least till any bigger change in the system, will be again compatible with some old kernels.
And no, Epsylon just has temporary other job but probably will be back this year, sooner or later
Ps. Flashing sbf is not difficult, what requires some knowledge or just reading is choosing of a proper sbf file
Another ps. if u don't want now to mess with sbf but need fast, reliable system with great battery why not give a chance to CM7.2?
corrinti said:
Many ppl have/had this problem (me too).
The workaround is flashing another sbf.
Could you gave details of your parent sbf?
Click to expand...
Click to collapse
p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
corrinti said:
And the only thing u should change in bootmenu is vsels. Governor must be interactive - don't change it
Click to expand...
Click to collapse
Why not? I changed it to Smartass without problems. (Now I changed it back to Interactive)
Sent from my flying overclocked Motorola Defy+ MB526 with CyanogenMod 10 and custom kernel using XDA app
I have got defy green lense.
earlier I was on cm7.2 with cm7 froyo kernel. after that cm10-nightlies, then aokp-kayant.
I recently flashed 18/10quarx v4-update as below:
1.data-cache-dalvik wipe
2.flash18/10, then flashv4, then flash gapps.
3.wipe cache-dalvik
4.reboot.
its all working well.
In the above sequence I have noticed many times that if cm10 is not working, first flash cm7.2 with cm7 froyo kernel & then flash cm10, it happened to be working on three defys I know.
also my boot logo is "Google" which I think is related to cm7 froyo kernel.
all these are observations, no technical expertise? do try?
I forgot to mention one thing that on first boot it appeared as if I have stucked on boot loop. after boot animation again on boot logo then again boot animation. but it booted finally.. so have patience.. first boot is different from earlier night lies.
nastys said:
Why not? I changed it to Smartass without problems. (Now I changed it back to Interactive)
Sent from my flying overclocked Motorola Defy+ MB526 with CyanogenMod 10 and custom kernel using XDA app
Click to expand...
Click to collapse
I didn't say you cannot, I meant you shouldn't as the phone will most probably work not so stable or more laggy or will not take your changes into account etc etc
---------- Post added at 09:26 PM ---------- Previous post was at 09:17 PM ----------
bulbouscorm said:
p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
Click to expand...
Click to collapse
This is a standard problem for US T-mobile users. In your case to go past 12/09 build (as even 24/09 could not work for you) flash CEE 2.2.2 build - than you will be able to flash the newest builds and do not lost your warranty if you have one valid
See also here
sasays said:
I have got defy green lense.
earlier I was on cm7.2 with cm7 froyo kernel. after that cm10-nightlies, then aokp-kayant.
I recently flashed 18/10quarx v4-update as below:
1.data-cache-dalvik wipe
2.flash18/10, then flashv4, then flash gapps.
3.wipe cache-dalvik
4.reboot.
its all working well.
In the above sequence I have noticed many times that if cm10 is not working, first flash cm7.2 with cm7 froyo kernel & then flash cm10, it happened to be working on three defys I know.
also my boot logo is "Google" which I think is related to cm7 froyo kernel.
all these are observations, no technical expertise? do try?
I forgot to mention one thing that on first boot it appeared as if I have stucked on boot loop. after boot animation again on boot logo then again boot animation. but it booted finally.. so have patience.. first boot is different from earlier night lies.
Click to expand...
Click to collapse
I'll check it out
Sent from my MB525 using Tapatalk 2
This is a standard problem for US T-mobile users. In your case to go past 12/09 build (as even 24/09 could not work for you) flash CEE 2.2.2 build - than you will be able to flash the newest builds and do not lost your warranty if you have one valid
See also here
Click to expand...
Click to collapse
This worked perfectly. Thank you so much.
sasays said:
I have got defy green lense.
earlier I was on cm7.2 with cm7 froyo kernel. after that cm10-nightlies, then aokp-kayant.
I recently flashed 18/10quarx v4-update as below:
1.data-cache-dalvik wipe
2.flash18/10, then flashv4, then flash gapps.
3.wipe cache-dalvik
4.reboot.
its all working well.
In the above sequence I have noticed many times that if cm10 is not working, first flash cm7.2 with cm7 froyo kernel & then flash cm10, it happened to be working on three defys I know.
also my boot logo is "Google" which I think is related to cm7 froyo kernel.
all these are observations, no technical expertise? do try?
I forgot to mention one thing that on first boot it appeared as if I have stucked on boot loop. after boot animation again on boot logo then again boot animation. but it booted finally.. so have patience.. first boot is different from earlier night lies.
Click to expand...
Click to collapse
I tried this method twice but it's not working :/
I guess I'll have to do that sbf thing sometime.. Crap
Okay so I've managed to get hold of a computer and I've read up on how to flash an sbf but I have a few questions..
1. If I flash a full sbf, will I have to root my phone, put clockwork mod etc again?
2. How do I know what my parent SBF is? I bought my defy in India, if that helps
3. Which SBF should I flash? I saw walter's link to all the stock SBFs but do I have to flash one of those or something else?
Sent from my iPad using Tapatalk HD
sixaxis94 said:
Okay so I've managed to get hold of a computer and I've read up on how to flash an sbf but I have a few questions..
1. If I flash a full sbf, will I have to root my phone, put clockwork mod etc again?
2. How do I know what my parent SBF is? I bought my defy in India, if that helps
3. Which SBF should I flash? I saw walter's link to all the stock SBFs but do I have to flash one of those or something else?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
So we know you have green lens, now we need your BL version. It is required to find proper sbf file (I'm not sute about Asian sbfs, usually for Europe green lense are BL4).
Thus go to this thread and download BL See and Root tool for use with your PC - as it is Chinese, then see post #309 in this thread how to use it.
And yes, if you flash full sbf then you have to root it with SuperOneClick and install 2ndInit - that's all.
But you can also try to flash directly one of the sbfs from above mentioned thread - you can find there also newest 2nd boot builds in sbf form
corrinti said:
So we know you have green lens, now we need your BL version. It is required to find proper sbf file (I'm not sute about Asian sbfs, usually for Europe green lense are BL4).
Thus go to this thread and download BL See and Root tool for use with your PC - as it is Chinese, then see post #309 in this thread how to use it.
And yes, if you flash full sbf then you have to root it with SuperOneClick and install 2ndInit - that's all.
But you can also try to flash directly one of the sbfs from above mentioned thread - you can find there also newest 2nd boot builds in sbf form
Click to expand...
Click to collapse
Ran it, it says BL version is 4.
I checked the stock SBF page again, and noticed something. My baseband is set to 3.4.3-331 and there are only 2 SBFs with that number ("Taiwan" and "Hong Kong/Taiwan"). Should I flash one of them?
Also, my phone came unlocked. It didn't come with a contract or anything, if that helps
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
Hi all, I've been reading DEV section for few months by now, in order to get confident in getting CM10 on my defy+.
Yet, I haven't well understood wether my current configuration will ease the process or not.
Would someone kick in with very appreciated info?
Here's my current setup:
defy+ with stock 2.3.4
kernel 2.6.32.9
build 4.5.1-134_DFP-89
the phone has been rooted with SuperOneClick, and has 2ndInit v.2.3 installed.
I have access to bootmenu, and have already performed a "backup all".
I've heard rumors about BL5 systems not being straigtforward to be flashed with CM10.
Neither is available a FullSBF for this particular version of android for me to restore the phone as it was when I bought it (so I'm a little worried).
Thanks in advance, manuele
Try directly flashing cm10 first, wiping data and dalvik cache first. Then sometimes cm10 may reboot once without loading up fully, so just let it be. If still stuck then flash dfp 231(your region/carrier one) and repeat above steps
Sent from my MB526 using xda premium
This sounds like trial&error, tnx anyhow. I will be more specific with my question:
is it possible to operate CM10 in defy+ from a BL5 stock?
Some people have, some people couldn't. I understand your question but it is a probability at best
Sent from my MB526 using xda premium