Guest Muztek Posted July 18, 2013 Report Posted July 18, 2013 I have CWM in my device, can i update to a new version by flash the *.zip version from the old CWM i have?
Guest aleksandar069 Posted July 18, 2013 Report Posted July 18, 2013 I have CWM in my device, can i update to a new version by flash the *.zip version from the old CWM i have? YES
Guest toby0897 Posted July 19, 2013 Report Posted July 19, 2013 (edited) ClockWorkMod Touch is closed source and can only by built for official CyanogenMod devices using the CWM builder. I guess it could be hacked together in other ways too, but it would be exactly that - hacked. There's also another touch recovery, Team Win Recovery Project (TWRP), that someone could port... ok thanks for your answer Edited July 19, 2013 by toby0897
Guest toby0897 Posted July 30, 2013 Report Posted July 30, 2013 i know this is a big ask but can you write a quick tutorial on how to make stock ROMs flashable with CWM i do remember there being a thread that you explained how to do it but i cant find it (my poor searching skills) if you find the post can you link it or can you write a quick tutorial on how to do it
Guest KonstaT Posted July 30, 2013 Report Posted July 30, 2013 i know this is a big ask but can you write a quick tutorial on how to make stock ROMs flashable with CWM i do remember there being a thread that you explained how to do it but i cant find it (my poor searching skills) if you find the post can you link it or can you write a quick tutorial on how to do it But why would you need to flash stock firmware with CWM? Just use the stock recovery. I think I've explained it somewhere in Acqua's CWM thread.
Guest jakonicki93 Posted August 3, 2013 Report Posted August 3, 2013 I finally bought the phone. Immediately did the root and recovery. The only thing left is to install the ROM itself which I'm going to leave for tomorrow. Thank you for helpful posts and topics. See you around!
Guest Jaco2k Posted August 14, 2013 Report Posted August 14, 2013 For anyone having problems connecting to the device via ADB - try to disable MTP on the phone USB settings. That did the trick for me. Cheers!
Guest papars Posted August 16, 2013 Report Posted August 16, 2013 Has anybody tested desktop rom flasher? http://forum.xda-developers.com/showthread.php?t=2383148
Guest tjethroyz Posted September 23, 2013 Report Posted September 23, 2013 (edited) hello huys i am new to this a newbie too... I tried and followed the instruction on the first post and i also did installed the drivers especially the adb interface, fstboot etc. the problem is when my phone reboots after typing "adb reboot bootloader" in CMD. my phone does not boot in green android logo or in short i does not shows the green android logo when it reboots.. sill stuck in waiting for devices. hope you understand my problem. i need ur helps guys. thnx anyways i am on clockworkmod recovery installation. i already rooted my phone but i unroot it because i want to install clockwork mod for MIUI ROM. Edited September 23, 2013 by tjethroyz
Guest aleksandar069 Posted September 23, 2013 Report Posted September 23, 2013 (edited) hello huys i am new to this a newbie too... I tried and followed the instruction on the first post and i also did installed the drivers especially the adb interface, fstboot etc. the problem is when my phone reboots after typing "adb reboot bootloader" in CMD. my phone does not boot in green android logo or in short i does not shows the green android logo when it reboots.. sill stuck in waiting for devices. hope you understand my problem. i need ur helps guys. thnx anyways i am on clockworkmod recovery installation. i already rooted my phone but i unroot it because i want to install clockwork mod for MIUI ROM. Reinstall the drivers, check USB Debugging need to be ticked. Try again. Edited September 23, 2013 by aleksandar069
Guest tjethroyz Posted September 24, 2013 Report Posted September 24, 2013 i tried that over and over again. but still don't boot in green android logo.
Guest KonstaT Posted September 26, 2013 Report Posted September 26, 2013 Here's the latest ClockWorkMod 6.0.3.8 built of cm-10.2 branch. Few things have changed but everything seems to be working. recovery-cwm6038-atlas40.img https://hotfile.com/dl/247434150/3e8c9d4/recovery-cwm6038-atlas40.img.html md5:976498fdc285f1c1d5a5999c71ffa9c6 recovery-clockwork-6.0.3.8-atlas40.zip (ClockWorkMod flashable) https://hotfile.com/dl/247433911/254ef2f/recovery-clockwork-6.0.3.8-atlas40.zip.html md5:b17d30caff93bbfc674a114ba2383b6d
Guest Something Wierd Posted September 26, 2013 Report Posted September 26, 2013 Tnx for the update.Everything seams to be working fine.
Guest aleksandar069 Posted September 28, 2013 Report Posted September 28, 2013 i tried that over and over again. but still don't boot in green android logo. If your phone stuck on the android logo go to Device manager... Find the incompatible device... right click mouse... click on the upgrade drivers or something like this... I have a Disc... let me pick... and chose fastboot drivers... chose ZTE Handset device... And that's it...
Guest hyperfang8 Posted September 29, 2013 Report Posted September 29, 2013 Please can you add back support for internal storage ? Or at least some quick on how to compile with support for internal storag.
Guest KonstaT Posted September 29, 2013 Report Posted September 29, 2013 Please can you add back support for internal storage ? Or at least some quick on how to compile with support for internal storag. Why, if I may ask?
Guest theshrink89 Posted September 30, 2013 Report Posted September 30, 2013 I had a problem with the latest recovery... When i select reboot phone, it gets stuck...
Guest KonstaT Posted September 30, 2013 Report Posted September 30, 2013 I had a problem with the latest recovery... When i select reboot phone, it gets stuck... Yeah, I've noticed this too. It happend when you cold boot to ClockWorkMod (vol up or down + power). If you select reboot to recovery from ROM or use adb reboot recovery, you can boot out of ClockWorkMod just fine. There's still a link to the previous CWM image in Acqua forum.
Guest msbomberman Posted October 3, 2013 Report Posted October 3, 2013 I think this CWM killed my phone, after the reboot all I see is... black... no screen activity, no nothing. Tried to reverse it but the message is device not connected... <is there another way I can try to go back to 6.0.3.2?
Guest papars Posted October 12, 2013 Report Posted October 12, 2013 Was there somewhere a "fix permissions" menu entry?
Guest MJonMoDaCo Posted October 13, 2013 Report Posted October 13, 2013 Its in advanced menu ;) Although a relic from the days of Android Donut, and not needed, so KonstaT told me... Not sure if it'll be there this time. I haven't bothered with this version since I noticed an acqua user having issues with it (msbomberman?) The one in the Acqua forum should be good enough anyway. We'll only need to consider again when Android 5.x.x comes along, as that'll mean ClockworkMod will be up to version 7.x.x.x.
Guest KonstaT Posted October 16, 2013 Report Posted October 16, 2013 New build. recovery-cwm6044-atlas40.img https://hotfile.com/dl/250810594/f0fd114/recovery-cwm6044-atlas40.img.html md5:9ad543e2c932b20b5fde2bde08da74d1 recovery-clockwork-6.0.4.4-atlas40.zip (ClockWorkMod flashable) https://hotfile.com/dl/250809713/0a96152/recovery-clockwork-6.0.4.4-atlas40.zip.html md5:015c6115e7f89951c5a3bb7e145de65a -fixed issue with rebooting out of CWM after cold booting into CWM -ClockWorkMod 6.0.4.4
Guest osstis Posted October 20, 2013 Report Posted October 20, 2013 (edited) Hello all I got a problem with drivers. I've read whole topic and tried all possible ways to get it works but stll no lucky. I'm not new to Android phones, root, roms etc. I have all drivers installed well, problem start with bootloader when my device is not listed under adb. I'm running Windows 7 Proffesional 32Bit with auto update turned on, has no other usb drivers installed just ZTE. This is when my phone is as normal mode and conected to PC. Windows Device Manager found it as ZTE Composite ADB Interface or ZTE Handset ADB Interface depends on which usb mode is used (charging only, MTP, PTP) C:\Android>adb devices adb server is out of date. killing... * daemon started successfully * List of devices attached P772N10_VIRGIN device This is in bootloader: C:\Android>adb reboot bootloader C:\Android>adb devices List of devices attached C:\Android> In bootloader my phone under Windows Device Manager is listed as Android Bootloader Interface but adb cannot find it. Some users says that bootloader mode is when green android logo shows on the screen. In my case bootloader screen is dark (like the space with small stars around) with white/grey ZTE logo in the middle. Any suggestion? Edited October 20, 2013 by osstis
Guest aleksandar069 Posted October 20, 2013 Report Posted October 20, 2013 (edited) Hello all I got a problem with drivers. I've read whole topic and tried all possible ways to get it works but stll no lucky. I'm not new to Android phones, root, roms etc. I have all drivers installed well, problem start with bootloader when my device is not listed under adb. I'm running Windows 7 Proffesional 32Bit with auto update turned on, has no other usb drivers installed just ZTE. This is when my phone is as normal mode and conected to PC. Windows Device Manager found it as ZTE Composite ADB Interface or ZTE Handset ADB Interface depends on which usb mode is used (charging only, MTP, PTP) C:\Android>adb devices adb server is out of date. killing... * daemon started successfully * List of devices attached P772N10_VIRGIN device This is in bootloader: C:\Android>adb reboot bootloader C:\Android>adb devices List of devices attached C:\Android> In bootloader my phone under Windows Device Manager is listed as Android Bootloader Interface but adb cannot find it. Some users says that bootloader mode is when green android logo shows on the screen. In my case bootloader screen is dark (like the space with small stars around) with white/grey ZTE logo in the middle. Any suggestion? IMPORTANT!!! FIRST DOWNLOAD FASTBOOT DRIVERS AND EXTRACT IT ON YOUR DESKTOP ::http://www.mediafire.com/download/45b4aoh8dk9d48t/fastboot_driver_B3.zip If your phone stuck on the android logo(ZTE) go to Device manager... Find the incompatible device... right click mouse... click on the upgrade drivers or something like this... I have a Disc... let me pick... and chose the file when you extract the fastboot drivers on your desktop... chose ZTE Handset device... And that's it... Edited October 20, 2013 by aleksandar069
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now