Database Info

[Q] need some help about "ClockworkMod Recovery "

I wanna flash cm7.1 into my Nexus s(i9023).Someone says I should flash “ClockworkMod Recovery” first then CM7.1.
I did not get it but CWM4.0.1.5.
It works, and got success to flash CM7.1
Is there will be some bad effect on my cellphone soon？

CWM = ClockWorkMod recovery.
There is a newer version of CWM available but it doesn't matter which one you used, if the operation was succesful. CWM 4 works just as well as CWM 3 and CWM 5 to update ROMs, don't worry and enjoy!
Here's the CWM changelog if you want to know what's going on:
https://github.com/CyanogenMod/android_bootable_recovery/commits/gingerbread
Greetz

[Q] Device keeps booting into recovery I9001 jelly beans

Device info: Samsung galaxy s plus (I9001)
I tried to install the custom ROM DOOMNEXUS V2 20121012, before i did this i rooted my device (checked it with the rootchecker to make sure it had worked), installed CWM v5.5.0.4, wiped the cache and data/factory reset.
After i rebooted my device after i had done the above, my device would straight into recovery mode.
I tried installing the custom rom with team power 2.2.1 recovery but with the same result. Each time the device booted straight into recovery mode and i had to use odin to reinstall my stock firmware.
I also tried using other custom roms for jelly beans like cm 10 alpha, but also with the smae result as stated above.
I have no idea what i did wrong or how i can fix it, so that it boots into jelly beans
Do any of you guys know how to fix it?

Plz help
I'm also having the same issue with same device.. Please help us get out of this...

I have had same problem with... was it CM9 alpha2? Anyway, then there was a flashable zip and that fixed the problem
I have always also formatted dalvic cache.
Anyway, new Doomnexus is out: http://forum.xda-developers.com/showthread.php?t=1936749
Mine DoomNexus V3 works awesome well, i have the kernel 3.0-version. I am using CWM 6.0.1.4 recovery http://forum.xda-developers.com/showthread.php?t=1843825

You had a bootloop.
Read here: http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001 under point 3.5.

CWM & CM10/10.1 problem (hung on "The device is unlocked")

Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!

cyaneo said:
Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!
Click to expand...
Click to collapse
What is your bootloader version? Si it fresh enough?

Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!

cyaneo said:
Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!
Click to expand...
Click to collapse
Yeap,.. Bloody bootloader
No problem

Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?

cyaneo said:
Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?
Click to expand...
Click to collapse
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1

szulco said:
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1
Click to expand...
Click to collapse
- now I formatted data and system and also wiped all possible parts
- flashing cwm 6.0.2.3 and installing asus stock ROM (ww_epad-user-10.4.2.20), reboot
- cannot access cwm recovery, so I reeflash it with fastboot method
- access cwm recovery and install latest 10.1 nightly, reboot, done.
Thank you so much!

I'm having the same issue.
I bought my TF300T when if first came out. I finally decided to play around with it.
I unlocked it with the Google Play app.
Used fastboot to push the latest ASUS JB4.2 firmware (US_V10.6.1.8)
My bootloader says: (1.00 e) released by "US_epad-10.6.1.8-20130225" A03
I rooted and installed TWRP v2.4.4.0
Everything is working fine for me and I have taken a solid backup, so I'm able to restore back to that when things fail.
I loved using CM7 on my phone, so I wanted to try CM10 on my tablet.
I have tried installing the stable CM 10.0, and I've tried all of the CM 10.1 Nightlies.
Every single time, the install goes perfectly fine, but when I reboot I just get the plain white Asus screen and then it freezes.
I have tried installing with and without installing the gapps.
Every time I install I do a Factory Reset, wipe the Cache, Dalvik Cache, and System. The only thing I didn't do is wipe Data as I'd prefer not to lose my files. (is that the problem, is the data-wipe required?)
Is there something obvious that I'm missing or a step I left out?
Any help would be greatly appreciated.

I tried doing it again with wiping all my data too...that didn't make a difference either. Still freezes on the white asus screen.

Hi, I just registered to reply, as seems noone did. And Ive been there myself, also with the 10.6.1.8 bootloader. Thats the issue. Cyanogenmod isnt compatible yet with the newest bootloader 10.6.1.8.
I hope it will in the future, Im awaiting it too. Until then I just rooted the stock rom, and using it that way. You could try the CROMI-X rom, but its also stock based, I havent tried it yet, maybe ill give the newest update a try (4.3) which will be available in a couple of days, as I really love their newest boot animation(wich I believe isnt included in the 4.2 version)
Till then, no Cyanogenmod for us with the newest bootloader.....also downgrading is not worth the risk if you ask me,,, even if its possible. So Ill wait for the Cyanogenmod team to update their version to ours.
Advice: dont mess with the bootloader nor the recovery img files. Always read carefully if you wanna change recovery if its compatible with your bootloader. If its not, and you flash it...tada....youre the owner of a cool and expensive brick. Dont wipe data in the bootloader, cuz as I understood reading posts here at xda, it will wipe your entire device, including bootloader...then your kinda screwed. So stick to what you have and let the devs do their work to update their roms for the 10.6.1.8 bootloader...MOST importantly, DONT store your device with the keyboard dock closed...(like a laptop)...your screen will crack eventually.I gathered this info on youtube as well as here, and Ive a friend, who was using the device with the dock till last month like that, had it from last august...result, screen cracked 3 weeks ago...its a design flaw in the transformers, the screen is under heavy pressure while in the keydock..I just got my dock last week,, Im storing it separately, and I never close it, only use it for typing, battery and usb.
im writing all this as I think I wont find this post again to reply if you read it.

Help Needed. Rom Installation

After I rooted my pico and installed CWM and took a nand backup. After that i tried Jaggy Dzire rom which installed perfectly but i don't know how it got bootloop. so i restored my backup and now i can't install any other rom than stock.. even if i try it will get stuck at boot logo or will go in bootloop.
i also managed to get lastet asia_india stock rom and to my wonder it works very well although i can't get link2sd work even if i try different 2nd partition formats( fat, fat32, ext3/4). on doing ext2 it will get stuck on boot.
and i'm curious about do i have nand burnt? ( pico is barely 1 week old).
and would also like to get a better ics/sense rom to use with and yeah, no overclock and stuff. as i can't get anything else than stock rom or my nand back up to boot normally !!.
Current Setup : Philz CWM || pico_asia_1.43.720.2_rev3 (rom).

Qmarks said:
After I rooted my pico and installed CWM and took a nand backup. After that i tried Jaggy Dzire rom which installed perfectly but i don't know how it got bootloop. so i restored my backup and now i can't install any other rom than stock.. even if i try it will get stuck at boot logo or will go in bootloop.
i also managed to get lastet asia_india stock rom and to my wonder it works very well although i can't get link2sd work even if i try different 2nd partition formats( fat, fat32, ext3/4). on doing ext2 it will get stuck on boot.
and i'm curious about do i have nand burnt? ( pico is barely 1 week old).
and would also like to get a better ics/sense rom to use with and yeah, no overclock and stuff. as i can't get anything else than stock rom or my nand back up to boot normally !!.
Current Setup : Philz CWM || pico_asia_1.43.720.2_rev3 (rom).
Click to expand...
Click to collapse
Nope no band burnt
U need to flash recovery again ( I recommend latest twrp )
And try formatting everything
But don't format sd card
Then flash the rom and u will be good to go
Sent from my HTC Explorer using xda premium

I got my phone working again. Running Cyanogenmod 9 with TWRP Recovery.
Here's what i did.
Installed pico_asia_1.43.720.2_rev3.
Installed twrp-2.5.5.0.
then copy-pasted flash_erase file in system/xbin and did ADB command.
reboot.
formatted partitions all of them ( except SDCARD and SD-EXT, can't format it, error occurs as "can't mount SD-EXT || can't format with mk2fs" ).
Installed cm-9-20130304-UNOFFICIAL-pico. and reboot.
And now, Working like a charm.
Thanks for Replying.

Great Work Guys
Qmarks said:
I got my phone working again. Running Cyanogenmod 9 with TWRP Recovery.
Here's what i did.
Installed pico_asia_1.43.720.2_rev3.
Installed twrp-2.5.5.0.
then copy-pasted flash_erase file in system/xbin and did ADB command.
reboot.
formatted partitions all of them ( except SDCARD and SD-EXT, can't format it, error occurs as "can't mount SD-EXT || can't format with mk2fs" ).
Installed cm-9-20130304-UNOFFICIAL-pico. and reboot.
And now, Working like a charm.
Thanks for Replying.
Click to expand...
Click to collapse
So there is no need of ClockWorkMod Recovery to flash CM9 or 10? I thought that was necessary. I never tested cyanogenmod because I never had CWM Recovery installed. But maybe I will give a try. Now I am on NextGen 1.5 and is running great. I changed it 3 days ago. Back than I had derefas's HTC Sense 4.0a Build #8, but had some problems with this and because I have 0 Thanks, I can't post in the actual thread. I would appreciate everyone giving me some "Thanks", if that's possible, so I can post in developement threads. Anyway, wainting for akya's new build. For me it's the best ROM, although it's GingerBread, but hey, it works flawlessly. I begin to think that HTC know what they are doing since they didn't updated the Pico's software to ICS. Gingerbread run's great. Anyways, appreciate derefas, shekhutanwar, Apex-Predator and other's efforts for trying to bring ICS to Explorer. Great work guys. Keep it up!

A custom recovery is must, it's upto you which one you choose. I have TWRP because it's recommended here for our pico and is really easy to use. CWM is none less though and I forgot to mention that I had CWM prior to flashing pico_asia_1.43.720.2_rev3 and after it I flashed TWRP. And as for CM, I used to have it on my Galaxy Note and have liked it since I noob-ly flashed it on my Galaxy Y. CM is way better than Sense/Touchwiz ( although Sense has more appealing UI and TouchWiz is just b.llsh.t). Anyway, Its upto you to decide and yeah, thanks to all our devs here for there precious works.

Qmarks said:
After I rooted my pico and installed CWM and took a nand backup. After that i tried Jaggy Dzire rom which installed perfectly but i don't know how it got bootloop. so i restored my backup and now i can't install any other rom than stock.. even if i try it will get stuck at boot logo or will go in bootloop.
i also managed to get lastet asia_india stock rom and to my wonder it works very well although i can't get link2sd work even if i try different 2nd partition formats( fat, fat32, ext3/4). on doing ext2 it will get stuck on boot.
and i'm curious about do i have nand burnt? ( pico is barely 1 week old).
and would also like to get a better ics/sense rom to use with and yeah, no overclock and stuff. as i can't get anything else than stock rom or my nand back up to boot normally !!.
Current Setup : Philz CWM || pico_asia_1.43.720.2_rev3 (rom).
Click to expand...
Click to collapse
By which method you made your sd-ext partition
Bcoz it seem to like, there is some problem with your sd-ext partition
Sent from my HTC Explorer using xda premium

At first I tried it with MiniTool Partition wizard( Space>512 Mb and tried all recommended partition format. didn't worked) and then again tried through CWM also this time it didn't worked.it showed that partition creation was successful but upon loading the card on my pc it would still displayed as 1 single partition having all the available memory space ie. 1.83 gb.
but then after installing TWRP and CM9 , I tried again through TWRP and made ext3 partition sized 512 MB and using Link2SD .working good since then.
i suppose its an issue on cwm side and the rom which was not able to detect and mount second partition.

[Q] cyanogenmod bootloop

i installed cm 11 unofficial from this thread http://forum.xda-developers.com/showthread.php?t=2608377 but when i turn my moto g on it gets stuck in the cyanogenmod loading screen if anyone can help it will be great

You didn't want to post your issue in that thread?

I'm having same problem.. Also same problem for bam ROM
Sent from my XT1032 using xda app-developers app

managed to get out of the CM11 bootloop after applied Fix Permissions (or something similar) in TW's Custom Recovery.

Seems that only TW recovery can fix this through a permissions fix.
Got the same problem last night and the only thing to do to get it works was to re-flash the stock firmware, flash the recovery and reinstall the CM build. Latest build seems to be pretty good.

Simply wiping the cache before and after flash worked for me.
Sent from my XT1032 using Tapatalk

imxdot said:
Simply wiping the cache before and after flash worked for me.
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Not for me, sadly.
I've also tried to re-flash the rom through the recovery but the only fix that worked for me was to flash the stock firmware and then install the CM via recovery.

Same here, had difficulties getting Cyanogen to boot.
What I did is :
- roll back to stock 4.3 : http://forum.xda-developers.com/showthread.php?t=2546251 (yes, you can roll back, read the end of the post)
- allow OTA update to 4.4.2
- install CWM
- in CWM : format /system, /data and /cache, install cyanogen from ZIP, wipe dalvik cache
Mysteriously it worked like a charm after many unsuccessful tries and a softbrick ^^
Btw, no need to root the stock ROM to install CWM or a custom ROM, just skip this step

Do you have the XT1032 version?
xavier66 said:
Same here, had difficulties getting Cyanogen to boot.
What I did is :
- roll back to stock 4.3 : http://forum.xda-developers.com/showthread.php?t=2546251 (yes, you can roll back, read the end of the post)
- allow OTA update to 4.4.2
- install CWM
- in CWM : format /system, /data and /cache, install cyanogen from ZIP, wipe dalvik cache
Mysteriously it worked like a charm after many unsuccessful tries and a softbrick ^^
Btw, no need to root the stock ROM to install CWM or a custom ROM, just skip this step
Click to expand...
Click to collapse
I´m tired of the mess made it because of the three different Moto G versions, i'm waiting for official Recovery from CWM, maybe 3 months it's to early but I wanna try this method. (I hope to don´t hardbrick haha)

I was having the same problem with every rom i tried. After going back complete stock with Alonsoch's tool in the original Dev thread, I was then able to get past the boot on any rom
Sent from my XT1034 using Tapatalk

stuck in loop after installation
Hi everyone
I have tried to install cyanogen mode date : 23, 22 nightly roms on my moto g xt1033 KK vesion using twrp as well as cyanomod recoveries but after installation my phone stuck on boot window. I waited for 20 min but nothing happens. I read throgh so many posts and orignal rom thread and found that its supporting 4.3 and 4.4 both versions and I want to test it with only 4.4. (Dont want to downgread).. Any solution?
I am newbee and want to take part in rom devlopment as tester. Sorry if i asked somethin silly or may be twice.

sandeepg9 said:
Hi everyone
I have tried to install cyanogen mode date : 23, 22 nightly roms on my moto g xt1033 KK vesion using twrp as well as cyanomod recoveries but after installation my phone stuck on boot window. I waited for 20 min but nothing happens. I read throgh so many posts and orignal rom thread and found that its supporting 4.3 and 4.4 both versions and I want to test it with only 4.4. (Dont want to downgread).. Any solution?
I am newbee and want to take part in rom devlopment as tester. Sorry if i asked somethin silly or may be twice.
Click to expand...
Click to collapse
please use the thread for the ROM you have issues with.
thread closed