yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] ghost45:
This is the fstab that i find in the boot file when i unpack it.

# 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/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

/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

This file says MF CHECK?????

boot.cfg in boot file that is the same of the file recovery.cfg in recovery file

bootsize = 0x705000

pagesize = 0x800

kerneladdr = 0x40008000

ramdiskaddr = 0x44000000

secondaddr = 0x40f00000

tagsaddr = 0x4e000000

name = 1416065144

cmdline =

This is the recovery.stab

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

I try also to patch the boot ...but nothings...after flash it the phone enter in boot loop.

:confused::confused:
[Upgrading, Modifying and Unlocking] bigrammy:
I assume you cannot use adb as biobio76 has suggested. :confused:
[Upgrading, Modifying and Unlocking] ghost45:
Infact i receive error!

I have tried to mod the boot but according me there is something that advice that the files are not the original.

Some strange check.

Soon arrive Carlive in person... To help this situation... He has created new carlive V3.tools.
[Upgrading, Modifying and Unlocking] bigrammy:
Yes I know I told you I had ask carliv to drop in on this thread to see if he could help. :confused:

Please don't pester him on his recovery thread he is very busy with the new updated recovery bro. :eek:

I know Carliv and he is a man of his word :angel: and does not need any prompting so just be cool. :cool:

Hopefully [MENTION=5238428]superdragonpt[/MENTION] will also drop in too and give us the benefit of his vast MTK SoC knowledge :fingers-crossed:

I would love him to expand a little on his comments regarding the Kernel compression and methods.

But again do not pester him if he wishes to help/advise us he will without any prompting. :good:

If you want these Top Dev's to help you have to be COOL bro. :cool: :cool: :cool: :highfive:

I have added the STOCK unedited recovery and "shoe" .img files for testing and investigation purposes.
[Upgrading, Modifying and Unlocking] ghost45:
HI Bro,

ok i receive the meaning..i'm remaining COOL!

Thanks for your help....

I have tested your two files :

the boot run well

and the recovery run(but is stock) i think that you have unpack anf repack without mod?

is true?

I wait YOU!

Thanks Bro.

see you:good:
[Upgrading, Modifying and Unlocking] Andrey_koftun:
Russian video

Add russian video with test antutu, 3dmark and test camera - youtube.com/watch?v=yofJHA4tHoU
[Upgrading, Modifying and Unlocking] bigrammy:
:laugh: They are both Stock images bro & Untouched by me. :) see the edit comment in that post.

I uploaded uploaded them so If a dev wants to take a look at them they can without having to download the whole ROM.

I will edit the post again to make it more clear bro.

Thanks
[Upgrading, Modifying and Unlocking] ghost45:
Ok Big,

i Haven't read carefully.

I thought that you have recompiled them without mod!

Okk we wait!:laugh:
[Upgrading, Modifying and Unlocking] bigrammy:
Hi ghost45,

I finished my shift now so I can spare a little time for this problem. :eek:

We could do with making a sticky check list that's is kept up to date in the first or second post of the things that have been tried so we do not keep repeating the same things.

Our mission list should be first to simply unpack and repack the boot/recovery.img without any changes so we can see if it's this that's breaking the .imgs

eg:

1: The Methods Used to Unpack Re-pack boot/recovery.img with no changes.

Author: ( Person/Dev)

Tool: (eg Michfood's MTK Unpack Re-pack Utilities. (Place a Link Here) )

OS: (Windows/Window Cywin/Linux/distro version etc.)

Tested By: (Person's Testing )

Flash Method: (eg: SPFlashtool plus Version. Type single .img flash / firmware upgrade etc)

Boot Success or Fail: Y/N ?

Image Link: (Link to .img)

Your Thoughts welcome.

Regards. bigrammy
[Upgrading, Modifying and Unlocking] ghost45:
Hi Big,

To rewrite all the several steps that i did is too hard.

But consider that all the procedure that i did not have realized no one recovery.

Because i think if is real that there is this xz compression is not possible to realize one recover until the cript system will be discovered.

Also the great Seven Max was not able to realize one good recovery.
[Upgrading, Modifying and Unlocking] bigrammy:
Hi,

Are you Linux based or Windows Based or both did you use VM or dual boot etc etc?

Did you try build the recovery/boot using linux?

I and any dev who may drop by will not want to go over things that have been tried already as this will be silly :silly: and because we do not have the phone to test things It will mean you would be very busy testing things that have already been done. :laugh:

XZ Compression is only the compression format and not encryption.

I could try build the boot/recovery.img using XZ Compression but I do not want to waste time if this has already been tried. :confused:

I must say Encryption seems a little extreme for Zopo and unless Zopo have said they use some sort of security encryption it seems unlikely to me :fingers-crossed:
[Upgrading, Modifying and Unlocking] bigrammy:
Rooted ROM

I see Marsapa over on Androidiani Has managed to make a rooted system.img for flashing with SPflashtool. :victory:

This is a big step forward and hopefully will lead to a custom recovery been made very soon. :fingers-crossed:
[Upgrading, Modifying and Unlocking] ghost45:
Hi Big,

I think we must start with new tools that have this compression... If is true that is present in that recovery this type of compression .

So i have spoken about the criptage because me and other friends are not able to understand well if there is present also one cript system.

Nobody are able to repack this recovery.

Or better.. Nobody are able to repack this recovery because if i only open with any modify and i repack it after the recovery not start.

Me and others dev.... Also with Marsapa, Seven, and so on, have tried in Windows and in Linux but the results are the same.

This is the real situation now.

See you..

P. S.

About the Zopo company i do not want to enter in a strange dialogue... So stop this subjects.. Please!
[Upgrading, Modifying and Unlocking] ghost45:
In this phone seem have Fake memory or not connected memory blocks to the scatter file

Mtk droid tools not run but show me this situation very strange:

The recovery fstab according me is wrong...

these are what it says:

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

but according me is not correct
[Upgrading, Modifying and Unlocking] bigrammy:
I spotted and changed that early on but I was guessing at the actual partitions at least we now have a fighting chance with the proper ones. :)

This is how the recovery-fstab should probably look according to the new correct info. :good:

SDcard management will still be a little trial and error though so read the #comments I have made :confused:

# mount point	fstype	device	[device2]	[length=]
/proinfo emmc /dev/block/platform/mtk_sdcc.0/by-num/p1
/nvram emmc	/dev/block/platform/mtk_sdcc.0/by-num/p2
/protect1	emmc	/dev/block/platform/mtk_sdcc.0/by-num/p3
/protect2	emmc	/dev/block/platform/mtk_sdcc.0/by-num/p4
/boot	emmc	/dev/block/platform/mtk_sdcc.0/by-num/p7
/recovery	emmc	/dev/block/platform/mtk_sdcc.0/by-num/p8
/secro	ext4	/dev/block/platform/mtk_sdcc.0/by-num/p9
/logo	emmc	/dev/block/platform/mtk_sdcc.0/by-num/p11
/system	ext4	/dev/block/platform/mtk_sdcc.0/by-num/p13
/cache	ext4	/dev/block/platform/mtk_sdcc.0/by-num/p14
/data	ext4	/dev/block/platform/mtk_sdcc.0/by-num/p15

#How to Handle SDcards???
#eg 1: Taken From Boot.img fstab
#/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

#Or a better way is direct or by Number Once Identified

#Notice size of flashinfo is this really internal_sdcard???? need to compare the sizes:
#/flashinfo	(???)	/dev/block/platform/mtk_sdcc.0/by-num/p16
# We could try this if it matches.
#/internal_sd vfat /dev/block/platform/mtk_sdcc.0/by-num/p16

#Notice size of bmtpool is this really external_sdcard????:
#/bmtpool

# I Recommend to try use this first because this seem's to be the standard for most recoverys that use this type of layout:
#/external_sd	vfat	/dev/block/mmcblk1p1	/dev/block/mmcblk1

Regarding unpack and repack of the recovery/boot.img I have noticed all the tools seem change the very first lines when viewed with hex and remove the number that seems to be there is in all untouched .img's . I am not sure if this has anything to do with why they do not boot but maybe worth checking. :confused: (See attached images)

PS: Can you tell me your version of MTKDroid Tools and give me the log.txt after you try make a backup. Thanks.
[Upgrading, Modifying and Unlocking] ghost45:
Hi Big,

The app mtkdroid tools do not run at all... But the only thing that do is to show the sector of the partition that point to this new blocks with named emmc+ numbers.

So these blocks do not are present in that phone. I check them... But there aren't at all.

The blocks that i found are the old block with the old names but with the new numbers that are shown with this new emmc shown by mtkdroidtools.

I make also others tests and i see now that the old block named for example... mmcblk0p_p13 is now the system

mmcblk0p_p15 is now the userdata....

And so on.

so the old blocks are different to the actual new blocks.

Also there are other sectors named:

Proinfo =?

flashinfo=?

Para=?

Bmtpool=?

These are the problems of these sectors... But the problem that not start the recovery at all.. according YOU.. Is connected to this problems or there are others mistakes?
[Upgrading, Modifying and Unlocking] bigrammy:
Please read the code again I have commented # there about flashinfo etc. Now you are rooted it should be easy to navigate to this stuff with file explorer to check what actually lives in these areas.

As for the recovery/boot not booting again please read my post again. I think it's related to the repack methods used by all the tools because they all cut the header when unpacking and seem to repack without it. So maybe something is missing in them. again see last post and images I posted.
[Upgrading, Modifying and Unlocking] marsapa:
Carliv, with this command do the wipe cache: format("ext4", "EMMC", "/dev/block/mmcblk0p14", "0", /cache);

Carliv, with this command do the wipe Dalvik Cache: delete_recursive("/data/dalvik-cache");

but if I give the command to wipe data instead I formatted everything, that also deletes the files in the internal memory: format("ext4", "EMMC", "/dev/block/mmcblk0p15", "0", /data);

what I think is that if you can format the system should also do the wipe data
[Upgrading, Modifying and Unlocking] :
I really don't get your point. Yes you can format cache, also you can wipe dalvik cache (is a folder not a partition), but you can't format data if your internal sdcard is in it; I told you that so many times... Any other partition, cache, system, doesn't have the sdcard in it. If you install from internal sdcard and then you wipe the data with internal sdcard in it, how could install process to continue? I told you look for other phones (HTC One m7 for example) with same internal sdcard on data. Do you see any format data in their updater-scripts? They delete specific folders from data, but not whole partition. Ex:

format("EXT4", "cache");
format("EXT4", "system");
delete("/data/local");
delete("/data/app");
delete_recursive("/data/data/com.android.vending/cache");

So, I hope it's clear this time: this is what I know about wiping data in a phone with internal sdcard on data partition. No matter how many times you will ask me, my answer is still this.
[Upgrading, Modifying and Unlocking] marsapa:
this is for 5 nexus that has everything on the internal memory

format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0", "/system");

mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");

run_program("/sbin/mount", "/dev/block/mmcblk0p10", "/data");

run_program("/sbin/mount", "/dev/block/mmcblk0p7", "/cache");
[Upgrading, Modifying and Unlocking] :
Ok, and where do you see format data? I only see mount data...

We really should stop here with these discussion. Clearly I can't make myself understood, and I think it's better to ask an Italian developer to explain you ;)

Cheers!
[Upgrading, Modifying and Unlocking] yuweng:
i've seen this all the time at PhilZ Touch development thread, users including ROM Cooker blaming custom recovery is the cause for their ROMs not to install & most of the time Phil3759's reply is Ask your ROM developer to fix his installer/ update-binary/ updater-script/ brush up his knowledge on the latest formatting . . . :cowboy:

---------- Post added at 06:18 PM ----------

More info here . . . :good:
[Upgrading, Modifying and Unlocking] marsapa:
I extrapolated the part devoted to wipe, still does the same, I understand what you mean, but I am convinced that it is feasible, in fact there are multiple versions of wipe feasible in Aroma:

Megawipe: Use this zip to completely format your phone. It will delete everything in your phone and will bring it to bare bones. After it install any ROM for a fresh experience without any conflicts with in the frame work.It deletes the Data, Cache, System and Preload partitions of your internal memory. So Beware!

SuperWipe: This is a simple factory reset and you can use it to move from one ROM to another without bothering about framework conflicts.It deletes the Data Folders and Cache partitions of your internal memory.Will not affect the Internal SD card.

Factory Reset: Use it to do a Factory Reset, which wipes your Data partition, Cache Partition and Dalvik Cache. It will delete everything on your Internal SDcard.

SimpleWipe: A simple wipe is as the name suggests a Simple Cache and Dalvik wipe. You can use it to clear the said partitions before updating to a newer version of your ROM. Also, You can use it before you have flash a new ROM.

I miss only the super wipe, the rest are able to get them
[Upgrading, Modifying and Unlocking] :
Well, that "SuperWipe" you are talking about is not native Aroma function, it is a customized script integrated by zoot1 in his version of aroma. And if you read his thread you will see that these don't work in all new recoveries (philz, cwm, twrp) - I guess in all compiled on CM11 or other kitkat environment. What does his script? It will use "rm" function in bash to delete all content of data folder except media folder:

#!/tmp/bash
# Remove content of /data partition excluding data/media files

#Navigate to /data folder
cd /data

#Regular expression, FILES==Everything in the current folder
FILES=(*)

#For loop, for files in FILES, do...
for i in *; do

#If file isn't in the media folder
if [ "$i" != "[COLOR="Red"]media[/COLOR]" ]

#Then delete it
then rm -R "$i"

#Finish when there are no more files that aren't in the media folder
fi
done
[Upgrading, Modifying and Unlocking] megthebest:
Sorry guys for OT, do you know if the new 64bit cpu 6732 and 6752 have similar recovery structure, like this? Anyone start to study elephone p6000 recovery? Any threads? . Thanks and excuse me for OT

If someone wants to help, i open new thread

http://xdaforums.com/showthread.php?t=2998980
[Upgrading, Modifying and Unlocking] marsapa:
I know, in fact I'm doing various tests, let's see what I pull out, however, someone has provao to install the recovery directly from recovery? The scripts is always the same? package_extract_file ("recovery.img", "/ dev / recovery");
[Upgrading, Modifying and Unlocking] mailman77:
Rooting stock zp999 firmware

Hi,

I want to root my zp999 with the stock rom i mean without changing the rom,

I have read here the thread and other threads as well and i am confused.

I understand that i need to flash a custom recovery and then flash SuperSU, right?

Can someone publish the latest links to the custom recovery and to the superSU with instructions how to do it?

Thanks,
[Upgrading, Modifying and Unlocking] ghost45:
Hi mailman,

Sorry but this is not the correct thread...here you are "ot"..

See in the official thread...
[Upgrading, Modifying and Unlocking] marsapa:
Excuse me, where are the sources of lenovo vibe x2?
[Upgrading, Modifying and Unlocking] MrRimmer:
Identification of phone

I don't know if this is going to be an issue, but during the process of reinstalling my phone (so many problems), I note that the standard recovery identified the device as vanzo95_lwt_ds_kk but Carliv v3 recovery presents ZP999, which is causing the update.zip (from 20141206 to 20141218) to not install. I had to revert to standard recovery in order to bring the phone up to 20141230.
[Upgrading, Modifying and Unlocking] juliotec:
I tested aroma file manager v1.91 and 1.90 in the last carliv recovery in my zp999 and dont work the touch, but the version 1.80 works good
[Upgrading, Modifying and Unlocking] mrjavum:
http://support.lenovo.com/us/en/downloads/ds101342
[Upgrading, Modifying and Unlocking] Razmote:
Hello,

I want download recovery for update ZP999, but the 4 files does not exist :

Can't find it!

Seems like that URL doesn't exist. Or at least we can't seem to find it. We've even looked under the seat cushions and zip, nada, nothing.

Anybody have a another link for download ?

Thank You.
[Upgrading, Modifying and Unlocking] ghost45:
These are the links

CWM Modd ZP999 v2

Carliv Touch Recovery 3.0 ZP999 v2

TWRP 2.8.4.0 ZP999

PHILZ Recovery ZP999 v2

:laugh:
[Upgrading, Modifying and Unlocking] tigrouille:
Hi,

I just get my new phone : zopo ZP3X.

Can you tell me how to have TWRP and root ?

Can you explain procedure ?
[Upgrading, Modifying and Unlocking] MrRimmer:
New update 20150212

I've just had a notification to say that a new update is available but it is unable to download. Has anyone got theirs to share?
[Upgrading, Modifying and Unlocking] tigrouille:
Finally, I succed to put the last TWRP on ZP3X.

But, when I try to install SU zip, error : unable to mount /cache.

How to fix it ?

I try to mount partition cache, no way.

Repair partition cache failed...

Help please.
[Upgrading, Modifying and Unlocking] bigrammy:
Use spflashtool to reflash the cache with the stock cache.img :fingers-crossed:
[Upgrading, Modifying and Unlocking] bouboulethai:
To install the update of 12-02-2015, I had to revert to standard recovery with flashtools

But now i want to come back to Carliv Recovery.

I flash like usual, all is ok for flash recovery with flashtools but ... impossible to go to recovery with buttons or with Rebooter Application

I have a blackscreen with Android message "No command"

i tried with all recovery files V2 and V1 ...

????
[Upgrading, Modifying and Unlocking] portucale:
Flash recovery and Boot image too.

Worked for me. Attention, I lost IMEI and Mac address, but restore then in engineer mode.
[Upgrading, Modifying and Unlocking] bouboulethai:
thanks Portucale

I will try

but before can you indicate me how can i restore Mac adress ? And Mobile Uncle Tools no works in MTK engineer mode with this ROM.
[Upgrading, Modifying and Unlocking] bouboulethai:
EDIT : i falshed boot + recovery and it is ok !!

Thanks

i no loose anything !!! IMEI - MAC all was not erased :)
[Upgrading, Modifying and Unlocking] portucale:
Good to know
[Upgrading, Modifying and Unlocking] paveltrufi:
/cache error :(

When I try to make a full-wipe from any of the Carliv's recoveries, it gets stuck in the "Formatting /cache" step. I need to remove the battery; and the next time I try to re-enter the recovery, it logs me some cache errors. Because of this, I can't install any ROM trough the recovery. Any solution for this?
[Upgrading, Modifying and Unlocking] ghost45:
[MENTION=371528]Everybody[/MENTION],

This thread like the others Zopo's threads opened from me will not receive from me any others posts cause problems connected to the Zopo heads.

I apologize to all my followers...
[Upgrading, Modifying and Unlocking] ghost45:
Hi Big,

Sorry... But you are Great... I'm noob near you!

So tell me what i must do... Is not easy for me to understand.

Tell me step by step that you want that i do!

Yes of course now i'm navigate easy with root.... But to create new recovery i'm noob...

Thanks for your big work

I wait you
[Upgrading, Modifying and Unlocking] chmac7:
How were you able to get root on the ZP999? I've read all 5 pages but I can't see the point where somebody explains how to root this phone. It just arrived in the post today, and I'd like to root it so I can use TitaniumBackup to move all my apps from the old phone to this one. If you can tell me the steps you needed to get root, that would be really awesome, thanks a lot.
[Upgrading, Modifying and Unlocking] ghost45:
Hi Chmac.... This thread do not about the root... But how to create new recovery mod in this phone.

The root procedure is hard but is based in decompiling the stock firmware...
[Upgrading, Modifying and Unlocking] chmac7:
Ah, sorry, wrong thread. I couldn't find a thread here about rooting the phone. Are there instructions on how to do that somewhere?
[Upgrading, Modifying and Unlocking] megthebest:
good, very interesting smartphone, i'm following this thread...
[Upgrading, Modifying and Unlocking] bigrammy:
Please try get proper mount points confirmed

Hi,

Sorry I have been quite of late but very busy with Christmas on the way. :laugh:

Could you please try run this adb command on your rooted device so we can confirm the partitions by /block

Make sure drivers are installed and ADB Debugging is checked/on :good:

adb shell
ls -al /dev/block/platform/mtk_mmc/by-name

Paste the output results in this thread :good:

If this does not work due to secure kernel then reffer to this thread HERE Thanks. ;)
[Upgrading, Modifying and Unlocking] ghost45:
Hi Big,

Here you are:

http://www.4shared.com/office/bHTMsrtgba/dev-block-platform.html

I copy in this file all the steps to arrive to folder "by-Name"

But the path is wrong, this is the right:

/dev/block/platform/mtk_msdc.0/by-name.

thanks.:good:

P.s.

Carliv is arriving here!