Database Users

[Q] cyanogen mod 9 or 7.2 install on a stock firmware of 2.1 update 1 tecl mexico

hi everyone right now im on an errand for a friend of mine, i've been searching and i haven't found something that can serve me, i have found that i need to upgrade to froyo to install cm9, well in fact my friend will be fine if i just can put gb on his defy so if it is a real mess to install ics on this phone i think i will stick to cm 7.2 or 7 it doesnt matter i just need it to work fine and that he is able to install some apps that my firend isnt able to, i havent done root so if someone provide me with a good way to do it i would apreciate it a lot.

Does not mind whether you want CM7 or CM9 - first you should upgrade to froyo, best way through moto RSDLite program.
Upgrading to froyo will let you always downgrade to froyo again and you will have a way to any proper CM7 or CM9.
All info u can find here and here
U have to root, install sndInint, check whether u have green or red lens and choose any proper CM7 or CM9 to flash
Always do all steps as in threads - then u will not get into trouble

[Q] Toolkit V3.4.0 + PA 2.2

I just got my Nexus7 yesterday and i have been reading alot about rooting, but there are still some questionmarks before jumping in.
I want to install Paranoid Android 2.2 and im confused:
1. Do i need to update to 4.1.2 before or just skip it alltogheter?
2. Should i wait for the Toolkit V3.4.0 or just use the V3.2.0?
3. Do i need to update the bootloader to the latest one, 3.41?

[Q] Please check my approach - Flashing right from UK stock Defy to Quarx CM10 4.1.2

Hi All,
I've done literally weeks of research on this, so hopefully I've not missed any easy posts, but I want to check my approach and ask a final question. This is my daily phone, and while I know the risks and issues with custom roms, I want to get it right. Hope someone can advise.
ROM I want to install is Quarx's JB 4.1.2 CM10.
Phone I have is UK Motorola Defy (Red Lens, original):
System version: Blur_Version_2.21.0.MB525.Retail.en.GB
Model Number: MB525
Firmware version: 2.1-update1
Baseband version: EPU93ST2_U_03.02.00
Kernel version: 2.6.29 [email protected] #1
My plan is:
1. Official upgrade to Froyo - it seems this is not yet done on mine, and custom ROMs require its Kernel, I read
2. Root phone - SuperOneClick
3. Titanium Backup - Needs Root
4. ClockWorkMod Recovery - Needs Root, and gives me Nandroid Backup capability in BootLoader
5. Nandroid Backup - this should provide me a route back to stock (* see question below)
6. Flash ROM - this will give me CM10 based on Jelly Bean 4.2.1
Question is, despite reading many threads, I'm still confused on CG versions and SMG file versions (CG##.smg). I do want to be able to flash back to stock after this, in case I want to sell the phone - if I flash up to Quarx's CM10 JB 4.1.2, what CG version is it and is it higher than I can possibly get back to stock from? Or can I find a Fixed SBF of a Stock ROM that will let me go back? How can I best prepare for this?
Anything else to be aware of or concerned about?
Thanks very much.
Steve.

The easiest approach is to directly flash cm10 first and check off it works(you can flash back your stock sbf if there's any problem) because CM10 WILL NOT INCREASE YOUR CG VERSION
The potential problem you can face(which can not stop you from stock sbf flash) is an incompatibility of 2ndboot with your stock kernel.
If you run into that problem (which I think should not occur) you will have to flash a compatible sbf, with higher cg version and a compatible stock kernel.
Sent from my MB526 using xda premium

Thanks - good to know CM10 has no CG version. I expected the developers to want to get rid of that kind of limitation as soon as they could!
Hmmm, so could someone confirm, that Quarx's CM10 will flash directly over the stock 2.1 Eclair ROM as listed above (with root/CWM), and doesn't need Froyo deployed as a base? That would really help if so - then I have no further considerations and I can just get on with it. I'll take it carefully and I'd rather not be faced with non-booting etc the first time round.
I believe wifi tethering doesn't work on it, though, or there's some problem with restarting regarding wifi tether. That's a shame, but maybe an app like Barnacle or OpenGarden can work instead...?

You could try it yourself by taking a Nandroid backup and if you face the non booting problem then flash stock sbf+ restore. Beware that sometimes first boot hangs or bootloops and in such cases you can fix the problem with a battery pull, or data wipe respectively
Open garden works without issues
Hit thanks!

jelly bean

can anyone tell me why jelly bean wont work on x5 can yoll give me the os jelly bean or honey comb any os cause my phones bricked

You haven't stated your problem properly. You have only requested for OS. Please explain your problem; there might be an alternative way to fix your problem.

look
rqmok said:
You haven't stated your problem properly. You have only requested for OS. Please explain your problem; there might be an alternative way to fix your problem.
Click to expand...
Click to collapse
look i tell how it got bricked
first my froyo os got bricked i gave it to service center and got gingerbread then i wanted to install cynogen mod first i had to install clockworkmod recovery so i did so but it dint work at the last step to change the boot.img file after that i restarted my phone did all stuff then it dint boot there the problem starts so i did a solution an os or something i want to directly install jelly bean or any thing:crying:

[Q] Can I install Omni KK over the stock Rooted Lolipop Nexus 7 (2013) FLO

Hey guys I have not seen this in the Q&A section and I want to make sure I do it right.
I only recently rooted my Nexus 7, been running stock but decided I wanted to have Multi Windows like I have on my Note 4. I have not decided on a ROM as I was looking for the best one so I am still running Stock Rooted 5.0.2 I saw Omni ROM and I think that this would be the best ROM to attempt this as I tried the Xposed method and of course got the boot loop.
I see that currently on OmniROM.com that this device is still running on KK 4.4.4 according to the nightlies. I assume I would need to find a KK stock ROM and flash it on to my Nexus to downgrade back to KK in order to install this ROM, or will this install with TWRP even though I'm running Lollipop?
If so does someone have a quick link to the Stock KK files? I used Wug's Nexus Root Toolkit to root my device as I did not feel like going through the same hassel as when I rooted my Droid RAZR so I would just tell that to use those files instead.
I am always flashing ROMs on my Note 4 but I have never gone backwards and I think it was possible to install KK ROM once you upgrade to lolly but not use a lolly ROM if your still on KK.

Soulforged666 said:
Hey guys I have not seen this in the Q&A section and I want to make sure I do it right.
I only recently rooted my Nexus 7, been running stock but decided I wanted to have Multi Windows like I have on my Note 4. I have not decided on a ROM as I was looking for the best one so I am still running Stock Rooted 5.0.2 I saw Omni ROM and I think that this would be the best ROM to attempt this as I tried the Xposed method and of course got the boot loop.
I see that currently on OmniROM.com that this device is still running on KK 4.4.4 according to the nightlies. I assume I would need to find a KK stock ROM and flash it on to my Nexus to downgrade back to KK in order to install this ROM, or will this install with TWRP even though I'm running Lollipop?
If so does someone have a quick link to the Stock KK files? I used Wug's Nexus Root Toolkit to root my device as I did not feel like going through the same hassel as when I rooted my Droid RAZR so I would just tell that to use those files instead.
I am always flashing ROMs on my Note 4 but I have never gone backwards and I think it was possible to install KK ROM once you upgrade to lolly but not use a lolly ROM if your still on KK.
Click to expand...
Click to collapse
I don't think anyone has done a compatibility check to see what happens if you run a 4.4 build on a device with 5.x bootloaders. It might work, it might do weird things (usually with sensors/wifi)
Multiwindow never got merged, if you want it you'll have to build for yourself and cherrypick it. There were some remaining issues with the patch we never had time to fix, we got too busy with other stuff, and xplodwild wants to rewrite the whole thing after finding a better way to implement it.