Related
Right now I'm running aosp's oICSv43 on my Nexus S 4G and have been trying to flash the Speedy-3 kernel. I'll admit I'm not the most knowledgeable at this, but from what I've gathered, I need to boot into recovery, wipe the cache/dalvik cache, and install from zip, choosing the kernel. This does not work for me at all. The install will finish without error, but when I reboot I get stuck at the Google screen. Here's what I've tried:
Recoveries:
CWM V3
CWM V5
TWRP V2 (what I'm using now)
Kernels:
Matr1x
Speedy-3
Glados
I've even flashed the phone completely back to stock and tried everything again to no avail. I can root the phone and flash roms with no problem. The problem comes when I try to flash a kernel after.
Any suggestions?
cashel said:
Right now I'm running aosp's oICSv43 on my Nexus S 4G and have been trying to flash the Speedy-3 kernel. I'll admit I'm not the most knowledgeable at this, but from what I've gathered, I need to boot into recovery, wipe the cache/dalvik cache, and install from zip, choosing the kernel. This does not work for me at all. The install will finish without error, but when I reboot I get stuck at the Google screen. Here's what I've tried:
Recoveries:
CWM V3
CWM V5
TWRP V2 (what I'm using now)
Kernels:
Matr1x
Speedy-3
Glados
I've even flashed the phone completely back to stock and tried everything again to no avail. I can root the phone and flash roms with no problem. The problem comes when I try to flash a kernel after.
Any suggestions?
Click to expand...
Click to collapse
Dont wipe cache. Only dalvik cache and then flash the kernel.
Sent from my Nexus S using xda premium
Thanks for the tip (and quick reply!), but it doesn't seem to work . Here are the steps I'm going through:
Booting into recovery
Full factory wipe
Flashing oICSv43
Rebooting into OS to setup phone/account (even skipped this step completely with no luck)
Boot back into recovery
Wipe dalvik cache
Install Speedy-3 kernel (or the either of the other two)
Reboot -> Gets stuck at Google logo w/ lit buttons
Just to be sure here - you are flashing those kernels which you downloaded from the Nexus S 4G Development forum right? And you are 100% sure it is a NS4G?
You're doing everything by the book so I don't know what else could be going on, don't take the questions the wrong way
Harbb said:
Just to be sure here - you are flashing those kernels which you downloaded from the Nexus S 4G Development forum right? And you are 100% sure it is a NS4G?
You're doing everything by the book so I don't know what else could be going on, don't take the questions the wrong way
Click to expand...
Click to collapse
No worries . 100% positive I have a NS4G, and I'm 100% positive I downloaded the kernels via the NS4G Dev. forum. I downloaded the kernels from the following three threads to be exact:
Matr1x:
http://forum.xda-developers.com/showthread.php?t=1361478
Speedy-3:
http://forum.xda-developers.com/showthread.php?t=1420912
GlaDOS:
http://forum.xda-developers.com/showthread.php?t=1345032
I've tried both the BFS and CFS versions for each where applicable as well.
Can't think of much else to try besides an alternative ROM to test flashing kernels with. Hopefully someone else could give you a better answer though.
cashel said:
Right now I'm running aosp's oICSv43 on my Nexus S 4G and have been trying to flash the Speedy-3 kernel. I'll admit I'm not the most knowledgeable at this, but from what I've gathered, I need to boot into recovery, wipe the cache/dalvik cache, and install from zip, choosing the kernel. This does not work for me at all. The install will finish without error, but when I reboot I get stuck at the Google screen. Here's what I've tried:
Recoveries:
CWM V3
CWM V5
TWRP V2 (what I'm using now)
Kernels:
Matr1x
Speedy-3
Glados
I've even flashed the phone completely back to stock and tried everything again to no avail. I can root the phone and flash roms with no problem. The problem comes when I try to flash a kernel after.
Any suggestions?
Click to expand...
Click to collapse
Easy fix. Flash it dirty....meaning don't wipe anything. Once it boots up, reboot to recovery then wipe dalik cache and boot up.
Sent from my Nexus S 4G using xda premium
I'm an idiot, wasn't using the latest version of aosp's oICS like I thought. Wiped everything, flashed to the latest version, wiped dalvik cache, flashed speedy-3 kernel and all is well . Thanks guys.
cashel said:
I'm an idiot, wasn't using the latest version of aosp's oICS like I thought. Wiped everything, flashed to the latest version, wiped dalvik cache, flashed speedy-3 kernel and all is well . Thanks guys.
Click to expand...
Click to collapse
So you were flashing 3.0 kernels on a rom built for 2.6. Glad you got it working.
Sent from my Nexus S 4G using xda premium
-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?
Hello.
I have installed the Defy Red Len CM10 Nightly Build.
I know there is a 2nd boot nightly build which provided a better solution than the non 2nd boot build
Can anyone provide a step guideline to upgrade / flash installation to the 2nd boot nightly build?
Thanks a lot
reaperhk said:
Hello.
I have installed the Defy Red Len CM10 Nightly Build.
I know there is a 2nd boot nightly build which provided a better solution than the non 2nd boot build
Can anyone provide a step guideline to upgrade / flash installation to the 2nd boot nightly build?
Thanks a lot
Click to expand...
Click to collapse
Here you go
if upgrading from previous CM10 builds:
1) Wipe Cache and Dalvik.
2)Flash Rom
3)Flash Gapps
4)Wipe Cache and Dalvik again & Reboot
and if coming from different builds(like CM7,CM9 etc)
1)Wipe Data, Cache and Dalvik
2)Flash Rom
3)Flash Gapps
4)Wipe Cache and Dalvik again & Reboot
Hope this helps you and ALWAYS MAKE A NANDROID BACKUP BEFORE FLASHING NEW ROM.
Thanks a lot. It works
Do you know how to the url for the Check update repo for 2nd boot build?
if you have CM10 from 24.09. and want jump to new kernel by Quarx you don't have to flash gapps ,in the other side yes you have to ,i recommended minimal gapps
yep¡ whit out gapss, for me works like a charm... the new build is 21.10
flashing........
Sent from my MB526 using xda premium
Defy MB525 green lense
NeoAven said:
yep¡ whit out gapss, for me works like a charm... the new build is 21.10
flashing........
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Does anyone know whether this build works on a MB525 with green lense as well, and can confirm that this is one build for 525 green and red lenses as well as for MB526 ?
Greetz.
I own a MB525, red lens, and I am using CM10 by Quarx (Sep 12th). So I just have to:
1) Wipe Cache and Dalvik.
2)Flash Rom
3)Flash Gapps
4)Wipe Cache and Dalvik again & Reboot
And, in today's release, then the update?
What about the kernel? Which one, and when? Thanks
EDIT: Oh, is it incluided in the ROM file now? Sorry, I don't quite understand what the differences are between classic CM10 nightlies and CM10 2ndboot nightlies (I know something about the custom kernel, but haven't found much information exclusively about it).
Please ask all questions in the Q&A section. Thread moved there.
I just followed these steps and now can't boot. I am able to enter the boot menu, but custom recovery just brings me back to the main menu, stable recovery does the same thing and stock recovery brings me to an android with a exclamation point in a triangle.
In fact anything I tap just brings me back to the main menu except boot and reboot.
Any ideas?
so the usual wipe and flash rom works even for earlier cm10 builds? i thought there was more than that (to install new custom rom.. flash some other files as well etc).. just making sure..
can u tell me the advantages? faster? more battery life? ........
General rulez to upgrade from CM10 24.09. to new qkernel :
1. Wipe's all data/cache/dalvik
2. install zip the newest/upgrede v4 from 27.10.
3. install gapps (all or minimal ) (the same gapps as 24.09. version)
4. do wipe's but only cache and dalvik
5. reboot
it's all enjoy
Question:
Whats the difference between 2nd boot builds and "non"2nd boot builds?
the new kernel gives as new possibility ,i can tell you technical staff ,but i use ROM before and after and i think that 2nd boot is faster and more stabile
Hi.
I'd like to upgrade to upgrade my Motorola Defy+ MB526 from Quarx CM10 24-09 (non-2ndboot) to 27.10 (2ndboot), but I'm not really sure of the steps. So I have to:
Open Stable Recovery
Wipe Cache, Dalvik and Data
Install zip from sdcard - 18.10 2ndboot build for MB526
Install zip from sdcard - update_for_18.10_v4.zip
Install zip from sdcard - gapps
Reboot
Is that right?
EDIT: Worked, done the following:
- Start Stable Recovery (of last Quarx non-2ndboot ROM)
- Backup all (Nandroid)
- Wipe data/factory reset
- wipe cache
- wipe dalvik cache
- install zip from sdcard -> 2ndboot ROM>100MB.zip
- install zip from sdcard -> update_for_xxxx_vx.zip
- install zip from sdcard -> GAPPS (I used PicoTTS (all))
- wipe cache
- wipe dalvik cache
- exit recovery
- shutdown
- Start Bootmenu
- shutdown
- Power on
- After first boot it rebooted but then it booted 2ndboot ROM perfectly.
Why is it that it should be shut down and restarted twice? Any particular reason?
Conzo427 said:
I just followed these steps and now can't boot. I am able to enter the boot menu, but custom recovery just brings me back to the main menu, stable recovery does the same thing and stock recovery brings me to an android with a exclamation point in a triangle.
In fact anything I tap just brings me back to the main menu except boot and reboot.
Any ideas?
Click to expand...
Click to collapse
same problem here...........
prashant_ch said:
same problem here...........
Click to expand...
Click to collapse
do this:
goto recovery,
choose stable recovery>wipe data>wipe cache>advanced>wipe dalvik
than flash http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/CM10-20121018-NIGHTLY-mb526.zip
wipe cache and dalvik again
now flash http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/update_for_18.10_v4.zip
wipe cache and dalvik again.
and reboot
it should boot normaly,if not,than remove battery,and reinsert it after 10 mins,
first boot will take a little time,so dont worry.
if it boots perfectly than u can go into the recovery again and install gapps :good:
..
I normally updated CM9 to CM10 i dont wiped the data just cashes and then i updated to 2ndboot , Its like you instal a new rom from any kind , just you dont wipe the data . This worked for me.... I dont know it that will work for you , I have a defy + mb526 , hope it will work for you . But dont broke your phone .
defyus3r said:
Why is it that it should be shut down and restarted twice? Any particular reason?
Click to expand...
Click to collapse
its not necessary
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
battlepower said:
I normally updated CM9 to CM10 i dont wiped the data just cashes and then i updated to 2ndboot , Its like you instal a new rom from any kind , just you dont wipe the data . This worked for me.... I dont know it that will work for you , I have a defy + mb526 , hope it will work for you . But dont broke your phone .
Click to expand...
Click to collapse
DEFY cant be broken merely by flashing rom :fingers-crossed:
About the updates for 18/10, i need to flash zip or apply update?
Hello,
I currently have defy with the later lens with the latest Quarx CM10 nightly installed. While CM10 is generally awesome, it turns out to be not stable enough (radio crashing, sudden restarts) and a bit too slow. Now I would like to downgrade to CM7.2.
I tried just flashing CM7.2 after a wipe which yielded a non booting device and me flashing back CM10.
Does anyone have any experience with reverting the Defy to CM7.2?
Thanks for your help!
You should change ext4 format of data to ext3 before flashing cm7.
1. Boot to recovery
2. Wipe Delvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3. It don't show any progress. Wait for few time. It shows done.
5. Flash cm7
IMPORTANT don't attempt another wiping of data/cache after filesystem conversion.
Sent from my MB525 using Tapatalk 2
pradeeppk said:
You should change ext4 format of data to ext3 before flashing cm7.
1. Boot to recovery
2. Wipe Delvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3. It don't show any progress. Wait for few time. It shows done.
5. Flash cm7
IMPORTANT don't attempt another wiping of data/cache after filesystem conversion.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I want to do the same with my green lenses. I have CM10-2nd boot, should I install CM7.2 for defy+ or just regular defy?
thanks in advance.
I don't know WHY all this redundant question? Is so hard to search a little? This problem was debated by enough time.
Sorry, I did search and found just this thread...
Just tried here, and cm7.2 for Defy+ worked just fine.
Hmmmm, last time I had to do this I reflashed a stock Froyo rom and did the whole process of rooting/installing 2ndinit/installing CWM again. Installing CM7 then wiping dalvik/cache/data did not work.
If a simple flash/wipe doesn't do the job, reflash Froyo again and follow the instructions to install CM7.
I haven't got the option in Tools to format in EXT3, there's only options to share SD, drivers, systems... Why?
I'm using a Quarx CM10-20120924-NIGHTLY-mb525.
Maybe I need to upgrade to CM10.1 to have that option? Which ROM could be good?
I'm using a Defy (mb525)
Miguemiguemigue said:
I haven't got the option in Tools to format in EXT3, there's only options to share SD, drivers, systems... Why?
I'm using a Quarx CM10-20120924-NIGHTLY-mb525.
Maybe I need to upgrade to CM10.1 to have that option? Which ROM could be good?
I'm using a Defy (mb525)
Click to expand...
Click to collapse
Just wipe from STOCK recovery .. it will format partitions to EXT3 and CM7 should boot =)
yzeroy said:
Just wipe from STOCK recovery .. it will format partitions to EXT3 and CM7 should boot =)
Click to expand...
Click to collapse
Wipe from STOCK recovery and then go to Custom recovery and flash directly the rom?
Miguemiguemigue said:
Wipe from STOCK recovery and then go to Custom recovery and flash directly the rom?
Click to expand...
Click to collapse
No just install CM7, GAPPS, and reboot to Stock recovery and there do Factory reset and reboot.
Now your CM7 should boot
Similar, but a little different
My requirement is to give CM 10.x one more try, this time with a clean install.
So, what should I do?
I posted here: http://forum.xda-developers.com/showthread.php?t=2192807
Do I need to use stock recovery, format, install SBF and then install the latest nightly?
Or something else as well?
s_u_n said:
My requirement is to give CM 10.x one more try, this time with a clean install.
So, what should I do?
I posted here: http://forum.xda-developers.com/showthread.php?t=2192807
Do I need to use stock recovery, format, install SBF and then install the latest nightly?
Or something else as well?
Click to expand...
Click to collapse
Any thoughts?
CM 10.1 to stock
I have gathered the following instructions so far:
1. Boot to recovery
2. Wipe Dalvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3.
5. Flash stock ROM (Where can I find this?)
Once I am with stock ROM, I would like to install CM 10.1 again, since I am not happy with the performance of the current CM 10.1 (perhaps 2 months old), so I would like to start from scratch.
Am I missing anything important?
Once you wipe data, system and cache in TWRP(of your current installation), your new installation is clean(as it would after stock rom/sbf flash)
You can cross check using the inbuilt file explorer in TWRP
Sent from my MB526 using Tapatalk 2
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