FORUMS
Remove All Ads from XDA

[CWM][6.0.4.5] Latest nontouch Clockworkmod recovery for I8552

3,166 posts
Thanks Meter: 7,601
 
By k2wl, Senior Member on 3rd December 2013, 12:14 AM
Post Reply Email Thread
I just compiled new cwm recovery for i8552.
this is needed if you are going to see cm-10.2 on this device.(some of us working on it...)
also this is faster in flashing roms.

THIS HAS SAME GRAPHIC ISSUES AS THE PREVIOUS VERSION OF CWM.

Instructions
1.Boot in ODIN mode(Vol Down+Menu+Power ...leave Power after phone vibrates)
2.select Vol Up to go in download mode.
3.open odin 3.04 or up.
4.Uncheck auto reboot option.
5.connect phone to the pc.
6.select recovery.tar.md5 in PDA tab.
7.click start.
8.when PASS notification come --> unplug phone from pc-->remove battery and restart the phone in recovery(Vol Up+Menu+Power..leave Power after phone vibrates)

DOWNLOAD LINK
http://d-h.st/2rQ

WARNINGS
DO NOT USE APPS TO REBOOT TO RECOVERY -->BOOTLOOP
DO NOT REBOOT RECOVERY IN RECOVERY -->BOOTLOOP

Report any errors ..in following posts.


Credits
Cyanogemod
Koush for CWM & it's builder for making device tree

The Following 13 Users Say Thank You to k2wl For This Useful Post: [ View ] Gift k2wl Ad-Free
 
 
3rd December 2013, 12:14 AM |#2  
OP Senior Member
Thanks Meter: 7,601
 
Donate to Me
More
reserved#
3rd December 2013, 12:32 AM |#3  
vikasjangra's Avatar
Senior Member
Flag Hisar Haryana India
Thanks Meter: 46
 
More
Quote:
Originally Posted by k2wl

reserved#

Is graphics issue solved and all functions are working correctly and how this one is different from default cwm.

Sent from my GT-I8552 using Tapatalk
3rd December 2013, 01:37 AM |#4  
OP Senior Member
Thanks Meter: 7,601
 
Donate to Me
More
Quote:
Originally Posted by vikasjangra

Is graphics issue solved and all functions are working correctly and how this one is different from default cwm.

Sent from my GT-I8552 using Tapatalk

graphic issue not solved yet but use it see the difference.
3rd December 2013, 03:55 AM |#5  
Senior Member
Flag Kolkata
Thanks Meter: 265
 
More
Nice work...

Sent from my GT-I8552 using Tapatalk
3rd December 2013, 06:01 AM |#6  
Arinio's Avatar
Senior Member
Flag Kolkata
Thanks Meter: 98
 
More
[QUOTE=k2wl;48078197]I just compiled new cwm recovery for i8552.
this is needed if you are going to see cm-10.2 on this device.(some of us working on it...)

Please do inform whose Device Tree (Shabbypenguin/Ankur/Gilati) is used for this CWM.

Also if this CWM is created without the above Trees then the Master Files (boardconfig.mk, vendor.sh etc) used by you.

Regards
3rd December 2013, 09:20 AM |#7  
OP Senior Member
Thanks Meter: 7,601
 
Donate to Me
More
[QUOTE=Arinio;48085863]
Quote:
Originally Posted by k2wl

I just compiled new cwm recovery for i8552.
this is needed if you are going to see cm-10.2 on this device.(some of us working on it...)

Please do inform whose Device Tree (Shabbypenguin/Ankur/Gilati) is used for this CWM.

Also if this CWM is created without the above Trees then the Master Files (boardconfig.mk, vendor.sh etc) used by you.

Regards

this is made with plane mkvendor.sh tree.
nothing special in it.
all the device trees you mention already have those files you want .\i havenot added anything more to it.
i just compiled it to the latest as it is better.
3rd December 2013, 11:42 AM |#8  
Arinio's Avatar
Senior Member
Flag Kolkata
Thanks Meter: 98
 
More
[QUOTE=k2wl;48089478][QUOTE=Arinio;48085863]
this is made with plane mkvendor.sh tree.
nothing special in it.


Thanks for clarifying. The bootloop issue can be taken care of by deleting the file inside /system/recovery.

However for the graphics issue you need to put the device frame buffer size.

For any developement purpose you are welcome to join my forum.

Currently I am working over the device tree of Grand Quattro.

Regards
The Following 2 Users Say Thank You to Arinio For This Useful Post: [ View ] Gift Arinio Ad-Free
3rd December 2013, 03:11 PM |#9  
OP Senior Member
Thanks Meter: 7,601
 
Donate to Me
More
[QUOTE=Arinio;48092187][QUOTE=k2wl;48089478]
Quote:
Originally Posted by Arinio

this is made with plane mkvendor.sh tree.
nothing special in it.


Thanks for clarifying. The bootloop issue can be taken care of by deleting the file inside /system/recovery.

However for the graphics issue you need to put the device frame buffer size.

For any developement purpose you are welcome to join my forum.

Currently I am working over the device tree of Grand Quattro.

Regards

there is no folder named recovery in system...????
i try to put correct frame buffer for recovery.
give me link to your device tree..
The Following 2 Users Say Thank You to k2wl For This Useful Post: [ View ] Gift k2wl Ad-Free
3rd December 2013, 05:52 PM |#10  
Arinio's Avatar
Senior Member
Flag Kolkata
Thanks Meter: 98
 
More
Till now no Device Tree is created by me.

However in Github search by delos3geur. You will find three device tree of Galaxy Grand Quattro. Ankur and Shabbypenguin created both indivisually. Chirag forked from Shabbypenguins.

Before you developed CWM others use Shabbypenguins CWM.

I am somewhat astonished as Android.mk; AndroidBoard.mk;AndroidProducts.mk;device_xxxxx.mk and BoardConfig.mk files are not used by you to develop your CWM.Actually according to my concept the Device tree will look like:

arm/
+-- armboard_v7a
| +-- Android.mk
| +-- armboard_v7a.kl
| +-- BoardConfig.mk
| \-- system.prop
+-- armboard_v7a_noneon
| +-- Android.mk
| +-- armboard_v7a_noneon.kl
| +-- BoardConfig.mk
| \-- system.prop
+-- another_product
| +-- Android.mk
| +-- another_product.kl
| +-- BoardConfig.mk
| \-- system.prop
\-- products
+-- AndroidProducts.mk
+-- armboard_v7a.mk
+-- armboard_v7a_noneon.mk
\-- another_product.mk

Also as far as I recall that there is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1.

Please do correct me so that i can update my knowledge.
3rd December 2013, 06:11 PM |#11  
OP Senior Member
Thanks Meter: 7,601
 
Donate to Me
More
Quote:
Originally Posted by Arinio

Till now no Device Tree is created by me.

However in Github search by delos3geur. You will find three device tree of Galaxy Grand Quattro. Ankur and Shabbypenguin created both indivisually. Chirag forked from Shabbypenguins.

Before you developed CWM others use Shabbypenguins CWM.

I am somewhat astonished as Android.mk; AndroidBoard.mk;AndroidProducts.mk;device_xxxxx.mk and BoardConfig.mk files are not used by you to develop your CWM.Actually according to my concept the Device tree will look like:

arm/
+-- armboard_v7a
| +-- Android.mk
| +-- armboard_v7a.kl
| +-- BoardConfig.mk
| \-- system.prop
+-- armboard_v7a_noneon
| +-- Android.mk
| +-- armboard_v7a_noneon.kl
| +-- BoardConfig.mk
| \-- system.prop
+-- another_product
| +-- Android.mk
| +-- another_product.kl
| +-- BoardConfig.mk
| \-- system.prop
\-- products
+-- AndroidProducts.mk
+-- armboard_v7a.mk
+-- armboard_v7a_noneon.mk
\-- another_product.mk

Also as far as I recall that there is also another important file you should know about. In /system/recovery.img there is a full copy of everything that is loaded on mtd1. This file is automatically flashed onto mtd1 every time you shut down. That means two things: 1. Any changes you make directly to /dev/mtd/mtd1 get blown away on reboot and 2. If you want to change /dev/mtd/mtd1 you're probably better off just sticking the image in /system/recovery.img and rebooting. When creating your own custom update.zip files (especially when adapting the stock images), you can get tripped up if you forget to replace /system/recovery.img and it ends up overwriting /dev/mtd/mtd1.

Please do correct me so that i can update my knowledge.

my friend --->
1.there is no mtd partitions on our device. our recovery partition number is p13.
2. i currently making device tree of my own and also contributing to chirag's repository
3.actually i used Android.mk; AndroidBoard.mk;AndroidProducts.mk;device_xxxxx.mk and BoardConfig.mk to make cwm.
you can't build cwm without working device tree.
4. device tree you listed is not used in cm device tree.
to make a sample device tree just make it with mkvendor.sh, found in build/tools /device
5. our chipset is msm7x27a which some what problematic for flashing recovery and roms.
neverthless we will overcome that in next few days!!
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes