How to Build new recovery modded for Zopo Speed7 Mtk 6753

[ghost45]

How to Build new recovery modded for Zopo Speed 7 (Zp951/952) Mtk 6753


In this thread we will discuss how to create or build new recovery modded for Zopo Speed 7
​

Everybody are Welcome!
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://xdaforums.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​

XDA:DevDB Information
How to Build new recovery modded for Zopo Speed7 Mtk 6753, Tool/Utility for the Zopo Speed 7 Plus

Contributors
ghost45, Carliv, Yuweng, Marsapa,Codelover,Bigrammy,SevenMaxs,HypoTurtle,

Version Information
Status: Testing

Created 2015-08-22
Last Updated 2015-08-22

 

[ghost45]

Software section​

Firmware

http://xdaforums.com/devdb/project/?id=11352#downloads

Recovery

CWM Base no touch
https://copy.com/Of0epSHxRkpwoJkX

 

[ghost45]

Section Procedure​

Details

zz

 

[ghost45]

Video Procedure​

Details

zz

 

[ghost45]

During the my last attempt to decript the boot and the recovery images from one new Zopo called Speed 7 (Zp951) octa core Mtk 6753 3gb Ram,
i receive this message from the Carliv v.1 program:

This errors appear during the boot decripting and during the recovery decripting.
If i Check well with other tools like "Bigrammy tools or also Yuweng tools" but i do not remember well who is the owner, i see that in the new boot and recovery is present the Kernel compressed and the ramdisk compressed.
kernel.gz
and
ramdisk.gz
If i decompress them the kernel became too big more than the 15 mb.
I tryied to leave it so big in new recovery but flashtool not recognize the files recovery,maybe i'm have passed the memory block ...but i don't know well.
These are the two files:
http://d-h.st/a380
What happened in these new two files?
Possible that mediatek create new compression?
Why these two files are compressed?
...

According The Great Carliv seems that in the Images (recovery and boot) probably isn't present anymore Mediatek header .

 

[AP756]

Still have no Speed7 (waitingfor it), so I can't help right now. This message is just to let you know I will be contributing to this thread as soon as possible .

 

[bigrammy]

TWRP

@ghost45 ported my UMi TWRP v2.8.7.0 so give it a try :fingers-crossed:
Download Here from Copy.com

 

[AP756]

@bigrammy: Original recovery is 8.27 MB, yours is 13.47 MB. Do you think this fits? Right now I don't know the structure of the Speed7-ROM, but I think other parts of the ROM have to be moved. Can you upload the scatter you used so we can have a look at the allocation? Thanks.

 

[bigrammy]

@bigrammy: Original recovery is 8.27 MB, yours is 13.47 MB. Do you think this fits? Right now I don't know the structure of the Speed7-ROM, but I think other parts of the ROM have to be moved. Can you upload the scatter you used so we can have a look at the allocation? Thanks.

64bit SoC recovery partitions are generally 16mb in size.
I do not have the zopo speed myself. Maybe ghost45 could upload the scatter as I assume he got the .img's from a stock rom.
EDIT: Scatter here http://xdaforums.com/devdb/project/?id=11352#downloads

EDIT EDIT: Confirmed recovery partition is 16mb in size

 

[ghost45]

64bit SoC recovery partitions are generally 16mb in size.
I do not have the zopo speed myself. Maybe ghost45 could upload the scatter as I assume he got the .img's from a stock rom.
EDIT: Scatter here http://xdaforums.com/devdb/project/?id=11352#downloads

EDIT EDIT: Confirmed recovery partition is 16mb in size

Thanks to arrive here Big!
I have check inside your recovery and i saw that you are able to leave the file compressed inside (kernel.gz) ...but you have update your repack and unpack tool?
:silly:

 

[ghost45]

64bit SoC recovery partitions are generally 16mb in size.
I do not have the zopo speed myself. Maybe ghost45 could upload the scatter as I assume he got the .img's from a stock rom.
EDIT: Scatter here http://xdaforums.com/devdb/project/?id=11352#downloads

EDIT EDIT: Confirmed recovery partition is 16mb in size

Big this is the result:
The twrp start but i receive this message:


And the touch seems do not respond at all......but this is first step ....

To the contrary i have tryied again my cwm base (not touch) sorry but i'm fixed for the cwm...and run well but i must see the memory sector to understand why i can't able to see the sd ext card.
see you and thanks for your work.
:good:

 

[bigrammy]

Thanks to arrive here Big!
I have check inside your recovery and i saw that you are able to leave the file compressed inside (kernel.gz) ...but you have update your repack and unpack tool?
:silly:

Sorry I am working now and the PC at work blocks images

 

[ghost45]

Have you deleted a post

Does my recovery work or not

No i do not deleted no one post....
but before i have had problem with see my last post, maybe xda forum have some problems today!

Your recovery start but do not run the touch at all and do not run also with the volume button.
So is unusable for now.

To the contrary my cwm run well but i must check well the memory sectors to understand why the sd ext is not seen.
(The memory internal is visible the sd ext not)

https://www.copy.com/s/t:CSIJeykJT1iaUKQP;p:%2Frecovery_Cwm_Speed7_102530_Roby.img;oid:1

 

[bigrammy]

No i do not deleted no one post....
but before i have had problem with see my last post, maybe xda forum have some problems today!

Your recovery start but do not run the touch at all.

No problem we both have PC issues :laugh:
The company PC's block lot's of content :crying:
It sounds like you have the same issue as our Elephone P6000 with no touch function.
You will need to ask zopo to fix the touch in the kernel...

 

[ghost45]

hi,
2° test Cwm modded :
https://copy.com/QQxDjuqIf0CCzA2S

in this second is not visible no one memory...(no SD internal and SD ext)
But i must have more time to check the memory sector!

 

[ghost45]

Hi ,
finally i have decompressed the Big Kernel and i have reduce the real dimension.
I Have attached in Download Section.

 

[flavien317]

Hi ,
finally i have decompressed the Big Kernel and i have reduce the real dimension.
I Have attached in Download Section.

Ok, great.
You can do a thread about CWm and TWRP on speed 7 developement. By the way when the source will be release, i will creat cm12.1 rom, you will help to do this if there some bug ? (i will received my zopo about 10 sept)

 

[ghost45]

Ok, great.
You can do a thread about CWm and TWRP on speed 7 developement. By the way when the source will be release, i will creat cm12.1 rom, you will help to do this if there some bug ? (i will received my zopo about 10 sept)

Hi Flavien,
I have already opened this thread about the recovery.. I not think is good to open one other about the recovery.
About the source... I know that Mediatek seems will release them in the next month... But i don't know the real date.
About the help to build one new rom is always one great and good idea to change opinions and to change hands.. Yes.

Sent from my GT-I9505 using XDA Free mobile app

 

[bigrammy]

Hi Flavien,
I have already opened this thread about the recovery.. I not think is good to open one other about the recovery.
About the source... I know that Mediatek seems will release them in the next month... But i don't know the real date.
About the help to build one new rom is always one great and good idea to change opinions and to change hands.. Yes.

Sent from my GT-I9505 using XDA Free mobile app

Hi bro,
Just some advice here as we have already been down this road with the Elephone P6000.
1. CWM recovery is pretty much dead as of KitKat 4.4.4 and is not supported in Lollipop 5.0 > so any CWM recovery's are likely to have been compiled using KK. This means they will never be 100% perfect for your Lollipop 5.1 device.
2. The TWRP I have ported for you is obviously working and has been compiled for Lollipop so If you had a working touch I am sure it would be 100% perfect. :good:
So what should you do ??
1. Get on to Zopo and demand they fix the touch in the Kernel I would guess it's a goodix GT9xx touch screen the same as the Elephone :laugh:
2. You could still use the CWM to do most things like flash supersu.zip to root etc etc.
3. You could probably use TWRP with a Mouse and OTG cable too.
4. Once rooted you can use wanam's Partitions Manager Here To back and even restore you partitions but it's a little slow Thread Here :good:
5. Last but not least use SPFlashtools for backup and restore. :good:

Regards bigrammy.

 

[ghost45]

Hi bro,
Just some advice here as we have already been down this road with the Elephone P6000.
1. CWM recovery is pretty much dead as of KitKat 4.4.4 and is not supported in Lollipop 5.0 > so any CWM recovery's are likely to have been compiled using KK. This means they will never be 100% perfect for your Lollipop 5.1 device.
2. The TWRP I have ported for you is obviously working and has been compiled for Lollipop so If you had a working touch I am sure it would be 100% perfect. :good:
So what should you do ??
1. Get on to Zopo and demand they fix the touch in the Kernel I would guess it's a goodix GT9xx touch screen the same as the Elephone :laugh:
2. You could still use the CWM to do most things like flash supersu.zip to root etc etc.
3. You could probably use TWRP with a Mouse and OTG cable too.
4. Once rooted you can use wanam's Partitions Manager Here To back and even restore you partitions but it's a little slow Thread Here :good:
5. Last but not least use SPFlashtools for backup and restore. :good:

Regards bigrammy.

Hi Bro,
Thanks for the answer, but actually we are waiting for the source from Mediatek.
When i will have some little time ...first, i want to create a new porting with cwm to have, almost, one recovery usable.
After yes probably we must studied these new sources....when their will arrive.