yashsingh1/xdaforums huggingface dataset:
[LG Optimus L90] mikeypinhas:
How to make it work for CM13:

Backup through TWRP 3.0

Flash TWRP 2.7

Use the tool with the "optimal" setting

Flash TWRP 3.0

Restore the backup

There ya go!

You won't be able to update, you'll have to restore to the "stock" partition scheme to update.

I don't care if you screw the process up, I won't help you. Use logic.
[LG Optimus L90] terrorizer84:
I'll try your idea tomorrow.

Which TWRP you tecomended?

Wysłane z mojego LG-D405n przy użyciu Tapatalka
[LG Optimus L90] mikeypinhas:
I just updated the post with that info.
[LG Optimus L90] terrorizer84:
I confirm the way running on the partition optional but the smallest partition unfortunately is impossible to restore the backup .

As for me, is not enough free memory

Wysłane z mojego LG-D405n przy użyciu Tapatalka
[LG Optimus L90] wizzardsk:
Please, where can I get the correct TWRP 2.7 and 3.0 from?
[LG Optimus L90] wizzardsk:
It means that after using this process I will not be able to use the OTA update?
[LG Optimus L90] Tejas tedi:
Yeah you can not update because flashing an update checks the system partition & it will not get flashed as the partition is changed.

For updates you have to revert back to stock partition.!
[LG Optimus L90] wizzardsk:
This is not good. There must be a way to avoid this limitation, otherwise this CM13 ROM becomes unusable...
[LG Optimus L90] Tejas tedi:
that correction should be made from ROM's side:(

or

we should stay with snapshots:good:
[LG Optimus L90] wizzardsk:
Yes, but what do you mean by snapshots? Every nightly is a snapshot, isnt it?
[LG Optimus L90] Tejas tedi:
Snapshots are stable version of the ROM

Which will be released on monthly basis.
[LG Optimus L90] jackson_c:
Why did you switch to TWRP 3? I do everything by 2.7 and it works.
[Galaxy S3 Neo Q&A, Help & Troubleshooting] MarJar:
Hi,

I'm experiencing problems with second SIM when i install Exposed Framework.

The problem is that i can't listen the other person during a call; and when i uninstall the framework, the sound work well again.

Someone have experienced this problem too?

Thanks
[Galaxy S3 Neo Q&A, Help & Troubleshooting] felipevr15:
without the xposed

my problem is different i can't call with the sim 1 even it showing all the things is working good it does not make anny call he jus don't start a call and stops without anny error i dont know what to do
[Galaxy S3 Neo Q&A, Help & Troubleshooting] CecoM:
Same with my I9300i - can't listen the SIM2 person during a call. This happens at least one time per week. At same time rear camera fails also.

XPosed FrameWork installed, but cant confirm if it is the reason. Will try next two weeks without it.

Xposed Framework deinstalled:

-Camera perblems still exists

-today SIM2 problem again

So, will try another ROM.

[MENTION=4438591]maxx35000[/MENTION]

TWRP installed
[Galaxy S3 Neo Q&A, Help & Troubleshooting] maxx35000:
hi guy's can someone just tell me if you have Cwm recovery for your device ? with 4.4.4
[Upgrading, Modifying and Unlocking] ghost45:
How to Build new recovery modded for Zopo zp999 or 3X Mtk 6595M ​

In this thread we will discuss how to create or build new recovery modded for Zopo zp999 Mtk 6595M.

Everybody are Welcome!

​

MANY THANKS TO OUR MODERATOR 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

​
[Upgrading, Modifying and Unlocking] ghost45:
Software section​

Firmware

http://www.needrom.com/download/zopo-3x/
[Upgrading, Modifying and Unlocking] ghost45:
Procedure Section

In this new Phone there are new memory sectors!​
[Upgrading, Modifying and Unlocking] ghost45:
Thread under construction​
[Upgrading, Modifying and Unlocking] marsapa:
Hello everyone, alllora 999 has one partition , I tried to compile several times TWRP but with the classic method for mtk does not work. Even the cwm works , you accept advice
[Upgrading, Modifying and Unlocking] megthebest:
I'm following the thread, interested to understand the new recovery for mediatek 6595 cpus
[Upgrading, Modifying and Unlocking] csdhhong:
MTKtools doesn't seem to work at the moment, either.
[Upgrading, Modifying and Unlocking] ghost45:
Yes this is true.

Mtkdroid tools maybe not compatible with the mtk 6595
[Upgrading, Modifying and Unlocking] bigrammy:
Hi [MENTION=4945206]ghost45[/MENTION],

I know very little about this phone and I do not have one. :( so I can only offer some observations.

Questions.

1. Has anyone got their hands on an update.zip yet?

2. Does spflashtool still work with this phone?

Thought: :confused:

If there is only 1 partition then maybe the ROM is in fact more like a .ISO or live DVD :confused:

Has anyone tried to Mount the partition in such a way?

Just thinking out loud guys.
[Upgrading, Modifying and Unlocking] ghost45:
Hi Big,

Yes flashtool have problems... Run only the last version n. 5.xxxx

There is only one partition.. So i think, probably, this big primary partition is not good for the recovery mod that try to find the sd memory and sd internal memory..

I must study too much.

Thanks for your help... You know are always welcome.... Elsewhere!

Understood?
[Upgrading, Modifying and Unlocking] hopeayaska:
Can someone please explaie how to root this model? I don't want to flash a custom ROM, just to root it.
[Upgrading, Modifying and Unlocking] ghost45:
Custom rom?

Where is it?

There isn't any recovery modded for this phone.
[Upgrading, Modifying and Unlocking] hopeayaska:
I don't think there are any custom ROMs yet, but since the space in the device has only one partition and without root you can't transfer the apps in the SD card. DO you think Vroot will work with it?
[Upgrading, Modifying and Unlocking] ghost45:
According me there isn't reason to transfer the app in the sd card... The space is too big and there isn't internal memory like internal sd like before.

In this phone there is only one partition system =data.

Vroot and all the type of root aren't able to receive right root.

We wait for the great Russian Seven Max that could create new recovery mod for this mtk 6595.

After this step we will try to start to all the root procedure under recovery to mod this phone.
[Upgrading, Modifying and Unlocking] bigrammy:
According to the fstab in the official recovery you definitely have partitions

boot	/boot emmc defaults defaults
/dev/block/mmcblk0p2 /cache ext4 defaults defaults
/dev/block/mmcblk0p3 /data ext4 defaults defaults
misc	/misc emmc defaults defaults
recovery	/recovery emmc defaults defaults
/dev/block/mmcblk0p4 /sdcard vfat defaults defaults
/dev/block/mmcblk0p6 /system ext4 defaults defaults
# Vanzo:songlixin on: Wed, 22 Feb 2012 18:31:03 +0800
# To support external sdcard
/dev/block/mmcblk1p1 /sdcard2 vfat defaults defaults
# End of Vanzo:songlixin

Of course I suppose these could be fake but I do not know why they would put in a fake recovery. :eek:

Please try these ;)

You flash At your own risk of course as I do not have a phone to test it on. :crying:

Mods are made to the needrom .img's that you posted in the first post so do not flash if in any doubt that this rom is incorrect.

CWM Recovery modded by me so now should hopefully support sdcard internal (emmc) external sdcard (vfat) sd-ext (auto) and maybe even usb-otg (auto) :fingers-crossed:

(init.rc edited and recovery.fstab)

/boot	dev/bootimg emmc defaults defaults
/misc	dev/misc emmc defaults defaults
/recovery	dev/recovery emmc defaults defaults
/logo dev/logo emmc defaults defaults
/misc dev/misc emmc defaults defaults
/nvram dev/nvram emmc defaults defaults
/uboot dev/uboot emmc defaults defaults
/dev/block/mmcblk0p2 /cache ext4 defaults defaults
/dev/block/mmcblk0p3 /data ext4 defaults defaults
/dev/block/mmcblk0p6 /system ext4 defaults defaults
/dev/block/mmcblk0p4 /sdcard vfat defaults defaults
/dev/block/mmcblk1p1 /sdcard2 vfat defaults defaults
/dev/block/mmcblk1p2 /sd-ext auto defaults defaults
/dev/block/sda1 /usb-otg auto defaults defaults

It will be almost impossible to make TWRP fit in the recovery partition of this phone as it is just too small. :( Maybe later you can workout how to resize the partitions.

I modded the shoe image too so now unsecured with adb

boot=shoe

for rename hope you understand.

Warning!! Only flash this if the recovery works fine and you have made a successful backups.
[Upgrading, Modifying and Unlocking] ghost45:
Hi big,

your recovery mod not boot remaining in black boot like the recovery of Seven.

I see the block in the files but i do not understand if them are fake or i can't able to see these new sectors.

i see only one partition system=data

I try also:

rename the file shoe in:

boot.img

and the recovery that you have made

but not run at all the phone remaining in boot!

see you and thanks for your great help.
[Upgrading, Modifying and Unlocking] bigrammy:
Ok bro Sorry it did not work :( it's difficult to help without actually having the phone in my hands. :eek:

If what you say is true then I would ask someone with linux to try mount the single partition as you would mount an .iso

I read some place that Total Commander for pc maybe able to mount the entire drive without the need of root. :fingers-crossed:

Regards bigrammy.
[Upgrading, Modifying and Unlocking] ghost45:
Thanks big... Yesterday i work to hard together other friends that we known.. But nothings..
[Upgrading, Modifying and Unlocking] bigrammy:
Ok I have done some more research and changed the recovery fastab's to this.

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/vendor /vendor ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/boot /boot emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/misc /misc emmc defaults defaults
/devices/platform/mtk-msdc.0/mmc_host auto vfat defaults voldmanaged=sdcard0:emmc@intsd,noemulatedsd
/devices/platform/mtk-msdc.1/mmc_host auto vfat defaults voldmanaged=sdcard1:auto
/devices/platform/xhci-hcd auto vfat defaults voldmanaged=usbotg:auto

You can now retry and see if this will now work it may require a little more editing but lets see what works and what does not first. :fingers-crossed:
[Upgrading, Modifying and Unlocking] ghost45:
Thanks... I will try it.

But according me the problem is connected with the repack operation... Or as someone sayed pack operation.
[Upgrading, Modifying and Unlocking] :
:laugh: Thanks, but I think you're just being modest. I know you have done and you do great things. My device folder for zopo phone is on github and if it is at any help you can check it.

Now about recovery, it was (at first look) what I suspected. Any CWM based recovery, and AOSP or TWRP also, has this define:

#define NUM_BUFFERS 2

but the new cyanogenmod recovery has this:

// triple buffer
#define NUM_BUFFERS 3

-> better explanation here.

So, clearly the issue is as codelover suspected, with the framebuffer. I'm sorry [MENTION=4893922]codelover[/MENTION] my friend that I didn't pay more attention at that time to what you said. Now I know where to digg further. I'll see if I can improve the cwm code to match this modern version from cyanogenmod. It doesn't help just to set NUM_BUFFERS to 3 in cwm, because the rest of the code doesn't use it as it should.

Now for all of you guys, who work to solve this issue, let's focus on graphics and graphics overlay area. :highfive:

PS: Many of you deserve a thanks from me today but this damn limit just keep showing me: "Sorry, you are limited to 8 thanks per day"
[Upgrading, Modifying and Unlocking] ghost45:
Yes , Sure Graphics BY CARLIV!!!:laugh:

thanks
[Upgrading, Modifying and Unlocking] bigrammy:
Chinese cwm

Hi all,

I notice the base working cwm recovery was by [MENTION=4477466]cofface[/MENTION] :)

I did infact PM him on the 24th Dec to ask him about the bootimg.exe tool on his blog/web page because the link is down for that particular tool. :(

He does say it handles MTK images now so I thought it would be nice to have :D cofface blog bootimg.exe need to translate with google

Anyway still no reply as yet but then again he seems not to reply to many at all :( Maybe he is busy cracking these strange SoCs mediatek keep releasing :laugh:

Hopefully he will drop by and offer some advice tips etc. :fingers-crossed:
[Upgrading, Modifying and Unlocking] codelover:
Modded CWM recovery for zp999 V2 with external sdcard support

LOL, ofcause it didn't work! I have not fix anything! I just repack because we don't know if it work, but yes it works!

Ok now i fixed more, let's see now if external sdcard mounting or not, remember, we do not have the phone, so more tests needed.

Now download the new repacked here: CWM_MX4_CN_zp999_v3.img Get latest HERE

EDIT: Post the recovery log for us to debug, it should be saved in /tmp/.

This recovery is for fun only, i am sure Carliv or mrjavum will be able to come up with a fully working recovery very soon! really soon!

As for the zip signature, carliv can easily turn off that when compiliing, so for sure you will get a fully working custom recovery!

Fix your /etc/recovery.fstab, /cache is ext4, NOT emmc!

No problem my friend, glad to be able to help! :highfive: i too ran out of thanks for today. :(

Ah btw cofface CWM old source is HERE.

Not necessary as [MENTION=455439]bgcngm[/MENTION] already did that, with [MENTION=5186178]carliv[/MENTION] added MT6595 support, you can get it HERE. ;)

-
[Upgrading, Modifying and Unlocking] marsapa:
now works install from sd

edit:

installs in recovery but in fact did not install anything
[Upgrading, Modifying and Unlocking] ghost45:
Hi Code,

the cwm run but not install all the zip files!

Seems that all are installed but if someone check is not true!

Check well inside because this cwm not run correctly!

BUT must be translated is impossible to understand the chinese languages.....seems to go ahead with closed eyes!

thanks:laugh::good:
[Upgrading, Modifying and Unlocking] split52:
backup my system:), but dont understand this backup
[Upgrading, Modifying and Unlocking] :
It is the "stock" Cyanogenmod recovery, and is intended to work with cyanogenmod ROM, that's why it has signature check always enabled. It's not a custom recovery like CWM, and I think it was Cyanogenmod intention to develop their own recovery since they are a company now. The speed I don't think is an issue. Anyway that was only for testing, because, as I said, it's not a "custom" recovery.

I think if michfood will take my built module for mtk-tools (the exe one for windows) and make few changes to his tool, that will work too.

:laugh: Thanks, I know about that repo, but I don't think he builds with it. I think he has an improved unpublished version.

My friend [MENTION=4893922]codelover[/MENTION], I think there is a mistake in recovery fstab. This is yours:

/dev/block/mmcblk0p7 /boot emmc defaults defaults
/dev/block/mmcblk0p15 /cache ext4 defaults defaults
/dev/block/mmcblk0p16 /data ext4 defaults defaults
/dev/block/mmcblk0p8 /recovery emmc defaults defaults
/dev/block/mmcblk0p14 /system ext4 defaults defaults
/dev/block/mmcblk0p13 /preload ext4 defaults defaults
/dev/block/mmcblk1p1 /external_sd vfat defaults defaults

and this is how it should be:

/dev/block/mmcblk0p7 /boot emmc defaults defaults
/dev/block/mmcblk0p14 /cache ext4 defaults defaults
/dev/block/mmcblk0p15 /data ext4 defaults defaults
/dev/block/mmcblk0p8 /recovery emmc defaults defaults
/dev/block/mmcblk0p13 /system ext4 defaults defaults
/dev/block/mmcblk0p16 /sdcard vfat defaults defaults
/dev/block/mmcblk1p1 /external_sd vfat defaults defaults

This phone doesn't have a preload partition. And what [MENTION=4560967]split52[/MENTION] has in his backup as preload is in fact the system (check the size) and his system backup is actually the cache. Probably if you correct these the recovery will be able to install and backup correct. :good:
[Upgrading, Modifying and Unlocking] mrjavum:
Yes, this is stupid mistake. And CMR uses fstab2 format. Thanks!

I think, that fd 3 - it's number of framebuffer device. And stock Lenovo recovery has double buffer and it works.
[Upgrading, Modifying and Unlocking] :
Hmm, I saw that too, and now I keep searching.... Thanks!
[Upgrading, Modifying and Unlocking] codelover:
lol, feel like i want to knock my head on the wall. I was searching for the complete blocks here and found this, didn't realize it wasn't for zp999.

I guess that's what happen if you try to do something without the device in your hand, and sleep less than five hours a day. :silly:

I guess many don't even know even sharing the same chip, oem can customize the emmc with different mount id & size to suits their needs,

they thought they could just use the same scatter from the same chip found on the internet, and then complaint it didn't work, lol.

Ah thanks for the correction, the stock recovery one should be correct!

I see, fstab2... thanks for the info.

Wish you good luck solving the mission impossible! :good:

For those interested, here you go for the fixed but 'temporary' one: CWM_MX4_CN_zp999_v4.img

Also please check if adb is now working with root access (in recovery), thanks.

.
[Upgrading, Modifying and Unlocking] marsapa:
now i test

edit:

adb it's ok in recovery but no root access (su: not found) and now installs well as external sd
[Upgrading, Modifying and Unlocking] SevenMaxs:
I tried to compile with the NUM_BUFFERS 3 - recovery still not started.

Here is the source code for the stock recovery & stock_bionic from Lenovo X2.
[Upgrading, Modifying and Unlocking] mrjavum:
I already saw the log from devices with nonworking fb - recovery starts, adb works, but there is no image on the screen.

Starting TWRP 2.4.4.0 on Tue Jan 20 22:30:20 1970
I:=> hardware id from cpuinfo: 'Qualcomm MSM 8610 (Flattened D'
I:=> product model: 'Lenovo A560'
I:=> using device id: 'Lenovo_A560_QualcommMSM8610FlattenedD'
I:Internal path defined: '/emmc'
I:External path defined: '/sdcard'
TW_DEFAULT_EXTERNAL_STORAGE := true
SP1_NAME := uboot
SP2_DISPLAY_NAME := nvram
TW_NO_REBOOT_BOOTLOADER := true
I:Lun file '/sys/devices/platform/mt_usb/gadget/lun0/file' does not exist, USB storage mode disabled
Starting the UI...Pixel format: 480x854 @ 32bpp
Pixel format: BGR_565
[B]failed to mmap framebuffer: Invalid argument
Unable to get framebuffer.[/B]
: Invalid argument
Starting TWRP 2.4.4.0 on Tue Jan 20 22:30:26 1970
I:=> hardware id from cpuinfo: 'Qualcomm MSM 8610 (Flattened D'
I:=> product model: 'Lenovo A560'
I:=> using device id: 'Lenovo_A560_QualcommMSM8610FlattenedD'
I:Internal path defined: '/emmc'
I:External path defined: '/sdcard'
...

But in our case, recovery does not start, no working adb...

And something more - using double buffering instead of triple makes artifacts in animations, nothing more critical...
[Upgrading, Modifying and Unlocking] bigrammy:
Windows Boot Recovery tool

Hi Tester's

Can someone please test this Windows Boot and Recovery unpack repack tool for me on your STOCK images. Tool Here.

Just unpack and then repack flash to the phone and check it still boots.

You will have to rename the recovery.img to boot.img before unpacking the rename it back after repack ;) .

Read Me txt instructions are in the folder. :fingers-crossed:

Thanks In Advance bigrammy
[Upgrading, Modifying and Unlocking] marsapa:
now i test for you

edit:

It's all ok
[Upgrading, Modifying and Unlocking] marsapa:
backup and restore with cwm cn of MX4 works perfectly, of course, everything goes with the sd but it works ;)
[Upgrading, Modifying and Unlocking] :
Now you know why I just keep asking ghost45 for all kind of commands with adb for this phone. When I need to find something I go few pages back, find the output of command that interest me and info is there. :highfive:

Sorry guys, I had to take care of some business today, but now I'm back and I'm working on few ideeas. I'll post soon something for tests.
[Upgrading, Modifying and Unlocking] marsapa:
ready to test :)
[Upgrading, Modifying and Unlocking] ghost45:
Hi Big,

the tool run very well!

the repack is good ....but how to translate the chinese languages in the actual "cwm code v4" ?:good:
[Upgrading, Modifying and Unlocking] marsapa:
however I tried to compile the 6.0.5.1 in English but I get black screen
[Upgrading, Modifying and Unlocking] bigrammy:
Many Thanks [MENTION=4729462]marsapa[/MENTION] for testing this most excellent multi purpose bootimg tool which supports all kinds of .img not just MTK :good:

Just to be clear this tool is the work of [MENTION=4477466]cofface[/MENTION] and not me :o

Here is the full list of supported commands.

C:\Users\wayne\Desktop\Windows Boot_recovery Tool>bootimg
bootimg:
Update Date:20140420
Modified:weibo.com/cofface
supported arguments:
--add-head
--cml
--cpio-list
--czlib
--dml
--dzlib
--remove-head
--repack-565
--repack-bootimg
--repack-ramdisk
--repack-rle
--repack-zte-bin
--rml
--to-ext4
--to-img
--uml
--unpack-565
--unpack-bootimg
--unpack-qsb
--unpack-ramdisk
--unpack-rle
--unpack-updata
--unpack-yafffs
--unpack-yaffs
--unpack-yaffs2
--unpack-zte-bin

C:\Users\wayne\Desktop\Windows Boot_recovery Tool>

I need to explore more the full use of this tool when I get the time but seems very useful indeed. :good:
[Upgrading, Modifying and Unlocking] split52:
yes, the same after compile, but the navbar bottons lights on, and black screen:p
[Upgrading, Modifying and Unlocking] :
Ok, I'll give you some work to do :

This is the list:

CM1 - for control

CM2 - accept unsigned zips

COT

CTR2.7

CTR3.0

CWM1

CWM2

TWRP2700

TWRP2830

tests done.

There are few of them compiled in CM10.1. I want to test something.
[Upgrading, Modifying and Unlocking] marsapa:
Ok now test all recovery
[Upgrading, Modifying and Unlocking] split52:
twrp 2700 black screen and boot ok

twrp 2830 black screen and boot ok

cwm2 logo zopo white screen no boot

cwm1 black screen and boot ok

i cant test the all, my battery is dead:(

for you marsapa
[Upgrading, Modifying and Unlocking] marsapa:
Ok now test all recovery

edit:

only cm 1 and 2 go in recovery

cm1 and cm2 does not install the zip

ctr2.7 and cwm m2 stop to logo the other recovery black screen
[Upgrading, Modifying and Unlocking] ghost45:
Good ..others Cm thanks Great!
[Upgrading, Modifying and Unlocking] ghost45:
So i want to recapitulate.........

Actually we have these recovery that running good :

1) CM Stock:

2) CM1 - for control

3) CM2 - accept unsigned zips

4) CWM V.4 (ACTUALLY THE BEST) But in Chinese Language

:laugh: