Database Users

[Q] Help with Defy (green lens) and custom ROMS

I am currently on a stock Android 2.1-update1 TMobile US ROM on my Defy (green lens) ROM. I would like to try out CyanogenMod 7.1 (or 7.2 RC) and need help confirming my understanding of the process. I am already rooted and have installed the GoAPK recovery.
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade).
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
I've searched and read as much as I can, I feel like I "got it" but I just wanted a little confirmation before I start hacking this phone apart =)
Thanks for any help you can give me =)

Here is the explanation from all that I know:
1. I need to flash my kernel to froyo to 2.2. In order to be able to downgrade back to 2.1 I need to use a "fixed" sbf. If I run the smgver.exe utility on the sbf file and it says "no version found" than this is a safe sbf to flash (can still downgrade). Ya, that is true. But after flashing fixed SBF you also need Nandroid backup to be restored.(This is not your nandroid backup. Its the nandroid backup supplied with the fixed sbf)
2. Before I flash this new kernel I need to (should) do a full nandroid backup of my current rom so I can restore it if things go wrong. I might need to install SuperOneClickFor2.x to do the backup and future recoveries.
Yes Nandroid backup is always recommended. Superoneclick is a software needed to root your phone. That answers the rest.
3. Once I flash one of these "fixed" sbf I can then do the "update.zip" process to flash CM7 onto my defy. I will need to do a factory reset and wipe the data/cache partitions. This will cause me to lose my contacts/calendar/etc AND my installed applications (and their data, so I need to back them up using something like TitaniumBackup).
Yes, however its not update.zip but its <ROM NAME>.zip Your contacts,calender can be backed up in your google account and if you use gapps(google apps. Needs to be installed separately by install .zip in CM) in your CM those will come again. Your installed apps and data yes can be restored from TB. You can backup SMS using SMS backup+
4. Once I've got CM7 (with froyo kernel) I can flash one of the CM9 builds for the defy green lens that is built specifically for the froyo kernel
Yes either that or you can even directly flash CM9 for Froyo kernel.
Hope that helps...

Problems with CM9 on Red lens Defy

-Solved btw-
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
How To Flash ICS(Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install ZIp from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash Gapps and CM7 Kernel
7:Clear Cache and Dalvik Cache
Click to expand...
Click to collapse
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
FAQ:
Q: I installed 08/12 build(or newer), but it gets stuck at the CM boot logo. What do I do?
07/12 contains the required 2.3 kernel. 08/12 and newer do not. If you have installed 08/12 or newer, enter recovery and flash the 2.3 kernel, then reboot. This applies only to Defy owners; Defy+ owners already have 2.3 stock ROM and kernel, so they do not need to apply the kernel.
In fact, the kernel zip for Defy owners is the kernel from Defy+.
Click to expand...
Click to collapse
I've tried everything I can think of. Can anyone help?
Thanks.

pk92 said:
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
I've tried everything I can think of. Can anyone help?
Thanks.
Click to expand...
Click to collapse
Hi,
Can you also provide the following info:
Which ROM did you have as stock?(Was it a froyo kernel or GB kernel as stock)
If you already had GB ROM in your phone you don't need the kernels to be installed!

It was a Froyo kernel

He's right. U don't have to flash a kernel if u were on froyo (2.6.32.9-gb08c3c8). Just make a wipe after installing the cm9 rom.
U only have to pick the right version. There are froyo-cm9 builds and GB-cm9 builds (so if u are on GB-kernel right now, take a GB-Build).
Or try the "codename android 1.5.5"... (froyo-kernel!) it's ported from the nexus
I'm testing this rom right now and for me it's working much better than cm9 builds.
Greetz

I recieved a pm suggesting installing cm7 then cm9 over, but more bootloop..
Sent from my Huawei_8100-9 using XDA

Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA

pk92 said:
Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA
Click to expand...
Click to collapse
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.

I have no idea if it's Quark or Epsy :S

hboy1337 said:
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.
Click to expand...
Click to collapse
pk92 said:
I have no idea if it's Quark or Epsy :S
Click to expand...
Click to collapse
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....

pranks1989 said:
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....
Click to expand...
Click to collapse
What I usually do when installing roms is this:
-Enter Stable Recovery
-Factory reset & clear data
-Install Zip from SD Card (Defy CM9.zip)
-Wipe cache
-Wipe dalvik cache.
So I need to do a Factory reset & data wipe in stock before flashing CM9?

I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)

pk92 said:
I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)
Click to expand...
Click to collapse
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!

pranks1989 said:
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!
Click to expand...
Click to collapse
I eventually decided to flash a froyo SBF (2.2.2), and flashed CM9 Defy from here. Suggested to me by Pottkopp.
I didn't flash any kernel and it worked fine.
Also installed Pottkopp's AIO.
So, all solved

Can someone help me?
Ok!
So i have green lensed defy. I already had CM9 installed( installed it using normal procedure). So i decided i will return to stock, by recovering backup. So i did. After a while on stock, i decided to go back to CM9. I forgot to do factory reset, and after install wipe chache and dalvik.I booted phone, and entered requesting data. I after that got back to recovery and did factory reset via custom recovery, and installed it again using correct method. My phone seems a bit slower than before, and did i damaged my phone?

[Q] Restoring clockoworkmod backup

I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!

Can anyone help me? I did as I wrote (switched for a while to CM9 GB build from CM7.2 FROYO) then wanted to restore CM7 backup, tried both with and without wipes (data, cache, dalvik) but it just gets stuck on boot logo and won't move on. What am I doing wrong?

You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..

neo.ank said:
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
Click to expand...
Click to collapse
Thanks for an answer! I made a backup with CM7 (froyo) recovery and was restoring with the one that was installed along with CM9 (gb). So that was the cause?

You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..

MarcinRN said:
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Click to expand...
Click to collapse
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
---------- Post added at 11:09 PM ---------- Previous post was at 11:09 PM ----------
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.

neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Yes, i flashed CM9 through recovery.
Rajneeshgadge17 said:
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?

MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Sent from my MB526 using Tapatalk 2

Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
Well as I said..this phone definitely acts senseless sometimes.. a data wipe in my case didn't remove the recovery or bootmenu.
Even reported it in the app thread..
Sent from my MB526 using Tapatalk 2

neo.ank said:
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Click to expand...
Click to collapse
It was second time it failed to restore a backup I was trying to do the same a while ago and was unsuccesfull too. Seems like my phone is cursed
Thanks for trying anyway!

MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Now, I understand your issue.
Try using below mentioned steps:
1. Boot into latest/custom recovery;
2. Wipe data/cache;
3. Restore the complete Nandroid backup;
4. Now from advance wipe dalvik cache and battery logs;
5. Now reboot the phone.
Please use above mentioned steps and share the results.
Hope this helps!!

Also try to install latest clockwordmod backup.
check this website for more detail http://www.clockworkmod.com/

@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.

RATTAR said:
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
Click to expand...
Click to collapse
That's the problem. You can find the kernels on epsy's site. Flash the kernel and restore the nand (there are also options in advanced restore if it still doesn't work, don't know if you need them)
Sent from my MB525 using XDA

Thanks guys I'll try it next time. However, I read somewhere that backup contains kernel too, don't know how much true is in that.

[HELP] - Soft bricked? -SOLVED-

Hi guys, I think I soft bricked a galaxy note, this is the things I did (I was trying to install ICS Stunner)
It came with the kernel KK8 that is non rootable, so I downgrade it to KJ1 (SGN_XX_OXA_KJ1_FACTORYFS) and it worked fine.
Flashed the Abyss kernel (AbyssNotekernel42CWTouchCustomLogo) via CWM and rebooted again to recovery
Flashed ICS Stunner (ICS_Stunner_Beta5.0) via CWM and FORGOT to wipe data/cache so it got in a boot loop
Booted again to CWM and wiped data/cache and still the rom wouldn't boot, so I decided to flash again the rom
The rom wouldn't flash via CWM I mean I selected the zip but the process wouldn't advance, same with the abyss kernel
So decided to start all over again and reflashed KJ1 via Odin (it was sucessfull), but now stock rom won't boot, if I shut down the phone and connect the charger the battery animation stays emtpy, I mean no green bar filling or nothing
The device can get to download mode, but I don't know what to do now, reflash another stock rom?
flash with heimdall?
If anyone can help it would appreciate.
Oh by the way, all this stuff was with the battery at like 20% (I know, pretty stupid)

You lost root during the process.Can you go again in download mode and flash with pc odin stock gb rom?
try this one 3*Files Wipe N7000XXLC1_N7000OXALC1 Open Europe (02/03/2012) from here
http://forum.xda-developers.com/showpost.php?p=23357737&postcount=1
if the flash is succesfull you may go in boot loop.remove the battery put it again in,with volume up+home+power go to stock recovery and do wipe cache and wipe data/factory reset .reboot
Sent from my GT-N7000 using Tapatalk

thanx man, downloading now

Dude i think u forgeted to flash ics repack before flashing ics stunner. .
Sent from my GT-N7000 using XDA

damn I tought it was not necesary on ics stunner 5.
Anyways the battery is full dead, had to go to buy an external charger and now is charging

maxthebest685 said:
Dude i think u forgeted to flash ics repack before flashing ics stunner. .
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Actually yes (this is the method i prefer) but he followed the instructions
"NEW STEPS BETA 4.3 ONWARDS:
Backup data apps.
Download and copy latest Stunner ROM on your SD Card.
Make sure you are on Rooted ROM. Reboot in recovery.
ONLY IF YOU ARE ON GINGERBREAD: Flash Abyss Kernel. Goto Advanced and Reboot Recovery.
Wipe Data (Recommended but not mandatory if you on Stunner ROM already)
Flash ROM.
Flash suitable Modem (Optional, recommended ICS LP5 modem)(not included in ROM)
Reboot and Read Caution.
Do not restore system apps or system data."
one think that may brake the procedure is he may come from a not properly rooted gb rom.I always mount system and always copy-paste some test files to /system in order to be sure sure that i did not lost root.I hope to solve your problem

i had the same issue two days ago nothing serious tried wiping factory but each and every move got the process stock at the beginning so at last i got it charged about 60% then went to download mode and flashed a GB ROM (STOCK) after all with the stock packages odin doesn't inscrease flash count so not to worry just get it to work again and next time wipe cache (preferable factory reset too) i recommend this step, then flash a repack LP1 of Chainfire to get things moving wouldn't take too long with a 90% power you can do all of these steps without any problem dont be paranoid......

oh god this -> Rooted_Stock_Odex_N7000XXLC1 saved me, thanx guys, the phone has booted, I have a captivate and never had this kind of issues the GNote its not even mine.
So just to know, for ics stunner 5 I need to flash first the ics repack

Yep. If you're properly rooted (and with that pre-rooted rom you are) then just install CWM recovery and Mobile Odin, flash the ICS repack, reboot to recovery, flash Stunner and then wipe data/cache/Dalvik, reboot and you should be good to go.

stunner 5.0 beta
what a rum the best is the Stunner beta 5.0 LP6_Kernel_repack may recommend a different kernel is not as happy with a repack
MIDNOTE2.1_BASE or Stunner beta 5.0

[q] is there twrp recovery for mortorola bravo?

in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???

hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.

skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.

hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.

skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.

hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .

skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries