yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] bigrammy:
(Solved finger trouble) Userdata!!!! Wrong size????

WARNING!!! The Start Address of the USERDATA is WRONG or NOT WHAT I WANT!!! IT will give you a 12GB Backup THIS NEEDS TO BE CORRECTED it also needs to be corrected on the SCATTER FILE!!!

I have noticed while making a Backup of the USERDATA it produced a 12GB backup using the /partinfo information from the phone. :eek: This is just a full Phone Backup pretty much. ROM Dump It may be handy to Restore a device but must be wrong for just capturing the actual userdata info :eek:

So How do we find the ACTUAL Userdata :confused: Maybe this is the reason why MTKDroidTools stopped doing userdata backups in later versions :eek:

So I need to do some more digging around.

Any Help regarding this will be appreciated :good:

Panic over guys I forgot to Name the readback userdata.img It seems when you forget to name it eg: leave it as ROM_0 the flashtool will ignore your inputs and just dump the whole ROM. :laugh: Still 6GB though :eek:

You can use this handy online Hex converter which will give you the hex value of a size or vice versa. Here and thanks to them for the easy to use tool :good:
[Android Q&A, Help & Troubleshooting] enr88:
Hi bigrammy, another noob/dumb question regarding how to make full backup of my device... What I have to backup with spflashtool to have a complete backup of the phone?

I have to proceed individually for each "partition" boot, recovery etc ..?

And sorry for the first question..thinking of post it on q&a thread :D
[Android Q&A, Help & Troubleshooting] bigrammy:
Yes bro you can and probably should readback all partitions manually just once for safe keeping :good:

MTKDroidtools used to do everything for you but with our phone you must do it manually now :crying:

Remember to increase the system.img size to at least 1GB to be sure you capture all the data mine is around 0.95GB actual size at the moment but remember it will increase as you install more things app updates etc etc ;)

I have attached a picture below.
[Android Q&A, Help & Troubleshooting] enr88:
i'm trying to do a test backup of cache.img, after 12min it's still with read download( i put my battery in phone when i saw the red download bar), also the speed seem blocked at 1,20 mb/s..

https://onedrive.live.com/redir?res...authkey=!AJbyot7NvHpg3_k&v=3&ithint=photo,png
[Android Q&A, Help & Troubleshooting] bigrammy:
Just stop it and retry in a different usb port also make sure you run the flashtool as administrator (Right click flashtool.exe select run as administrator)
[Android Q&A, Help & Troubleshooting] enr88:
No luck tried different usb port, 2.0 and also 3.0 usb. also tried to backup recovery.img like you do in your video tut but no luck again..

Can u address me to a correct driver file, and all necessary files, maybe i download and install different one..

Ps. i have a windows 8.1 x64 laptop
[Android Q&A, Help & Troubleshooting] bigrammy:
Sorry bro this is the sort of thing I did not want to get into :(

Use Google search "SPFlashtool and windows 8.1" also read my OP again and follow the other SPflashtool tuts linked there I state drivers are there. :rolleyes:
[Android Q&A, Help & Troubleshooting] flux1000:
CWM port for MT6752

Hello Bigrammy

Thank you very for the Tutorial video, I've learnt a lot from it.

I've seen you managed to port a CWM from Carliv to your MT6732 device. I own a MT8752 device (the same as MT6752 but intended for tablets), a Teclast T98 MT8752 4G (a very good device BTW), and as you know these chips are very new and there is not much information about how to port CWM for them.

I've read several threads form Carliv and yuweng, and I couldn't find a method, guide, a way to the port a existing CWM to a MT6752/6732 device. I think i could use your CWM for my device.

I have a complete rooted ROM here ( I've already flashed it), in SP flash tools format...with boot.img, recovery.img (the stock ones, as they weren't modified to get root access...).

Would you be so kind to tell me the steps for doing it? Where should I read,...? Any hint would be very much appreciated.

Thank you and sorry for my english...;)
[Android Q&A, Help & Troubleshooting] bigrammy:
I dont know what level you're at bro as it can sometimes be a little challenging :eek:

I think the easy solution for you would be to use one already ported for your SoC http://xdaforums.com/showpost.php?p=58210147&postcount=8 !!! DO NOT FLASH THE BOOT.IMG THATS INCLUDED IN THAT POST/DOWNLOAD!!! it's not for your device and will probably brick it.

Just use that recovery for your base unpack it and swap the Kernel with one from your phone repack and give it a try.

more on porting recoverys is of course on carlivs threads here. http://xdaforums.com/search.php?searchid=336608874

This is not a porting thread so no more questions about porting as everything you need to know is in carlivs threads :good:
[Android Q&A, Help & Troubleshooting] tasos01:
thanks for your work :good:
[Android Q&A, Help & Troubleshooting] bayad:
Custom Rom for Elephone P6000

Hello to all,

Is there a Custom Rom for the Elephone P6000 ?

Thanks in advance for your answers.
[Android Q&A, Help & Troubleshooting] bigrammy:
Not just yet but I am sure there will be very soon now we have a custom recovery. :fingers-crossed:
[Android Q&A, Help & Troubleshooting] enr88:
Yeah. Hope in a custom ROM :)

THX For porting Carliv recovery [emoji106] [emoji106]
[Android Q&A, Help & Troubleshooting] bayad:
Many thanks to you Master Bigrammy for all your efforts to make a better Elephone P6000 :good:
[Android Q&A, Help & Troubleshooting] bayad:
Hello Master Bigrammy, the new update for Elephone P6000 creates many problems with your Recovery. Can you find a solution please ?

Thanks in advance.
[Android Q&A, Help & Troubleshooting] bigrammy:
See OP ;)
[Android Q&A, Help & Troubleshooting] bayad:
With the arrival of the experts (Master Bigrammy, Master Carliv and Master Santhosh M) on our Elephone P6000 smartphones, can we expect Kitkat Custom Roms soon ? :fingers-crossed:

Thank you very much to all of you :good:
[Android Q&A, Help & Troubleshooting] jag123123:
Recovery for Elephone P6000 How To

Hello. I read the post of Carliv (http://xdaforums.com/android/development/elephone-p6000-mtk6732-64bit-sp-flash-t3007070) in which he explains how to install the CWM Recovery. I just received my elephone P6000 which has the firmware 8.4_20150131. Unfortunately I was not able to understand and wanting to avoid making some mistakes wanted to better understand what I need to do:

1. Should I use flashtool, scatter and P6000CWM3.img?

2. Do I have to use the file update.zip?

3. When you use the file patch.zip?

4. Can I use instead Flashify?

Sorry but I would avoid brick my smartphone. Thank you for your cooperation and clarification.
[Android Q&A, Help & Troubleshooting] HypoTurtle:
For recovery you can use flashify/rashr.
[Android Q&A, Help & Troubleshooting] RussianBeny:
Del
[Android Q&A, Help & Troubleshooting] bigrammy:
To ALL,

OP Updated with the official compiled CWM recovery by [MENTION=5186178]carliv[/MENTION] :good:
[Android Q&A, Help & Troubleshooting] jag123123:
Questions for recovery install

Hello very tanks for your job and contribute. I read your post in which explains how to install the CWM Recovery. My Elephone P6000 has the firmware 8.4_20150131. Unfortunately I was not able to understand completely and wanting to avoid making some mistakes wanted to better understand what I need to do:

1. Should I use flashtool, scatter and recovery-CWM-Modd-P6000-2.img or I can use Flashify?

2. Do I have to use always the file patch.zip?

3. It's recovery tested and safe for Elephone P6000?

Sorry but I would avoid brick my smartphone. Thank you for your cooperation and clarification.
[Android Q&A, Help & Troubleshooting] bayad:
Many thanks to all of you for your work on our Elephone P6000 :good:

Now, we look forward to a Custom ROM to improve software part of P6000 and fix its many bugs.

We are counting on you Master Bigrammy and all the developers ! :fingers-crossed:

Again, thank you to you !

---------- Post added at 01:37 PM ---------- Previous post was at 12:40 PM ----------

For me, I used Flashify to install the Carliv's CWM (recovery-CWM-Modd-P6000-2) and everything is working fine.

Have you tried to install by Flashify ?
[Android Q&A, Help & Troubleshooting] jag123123:
No, I have not tried it, because in the last week there have been several date nature on the home page and I'm a bit confused as to which to use recovery... but I try to do it hoping everything goes well.
[Android Q&A, Help & Troubleshooting] nemo232:
Hi, you can use flashify to install cwm. For me it worked well, nothing bad happen :)

Odoslané z Elephone P6000 pomocou Tapatalku
[Android Q&A, Help & Troubleshooting] jag123123:
I just installed the recovery and it went well. When I do the rebot asks me to do or not the root fix ... What to do? Yes or no? For now, I always said no.
[Android Q&A, Help & Troubleshooting] bigrammy:
If all is working fine and you do not lose the recovery on rebooting then continue to say no ;)
[Android Q&A, Help & Troubleshooting] jag123123:
Ok, all works fine, I continue to say no, tank you all ;)
[Android Q&A, Help & Troubleshooting] bayad:
I say "Yes" always but i don't know really what is the difference between the two choice :confused:

Maybe Master Bigrammy can answer us ;)
[Android Q&A, Help & Troubleshooting] bigrammy:
This is my take on what's happening :laugh:

I think it's a bit of a fight with which is the best way to maintain root/superuser. :mad: :laugh:

In /etc/ there is a script file called install-recovery.sh under stock conditions if you install a custom recovery then after rebooting the system will replace your custom recovery with the stock one again :(

So you just delete it right :silly:

Wrong our kernel checks for the file and will just replace it if its missing on your next reboot :rolleyes:

CWM also checks and it wants to remove it thinking it's a stock install-recovery.sh and when you say yes it deletes it.

Now depending on root method superuser version etc this is where the loop starts superuser/root script checks the file and reinstalls the install-recovery.sh but with it's own scripting inside. So now CWM see's that dam install.recovery.sh again and asks to fix it (delete it) and round and round you go :laugh:

So if root is good and su is working fine and your recovery is not been replaced when rebooting then just say no. :good:
[Android Q&A, Help & Troubleshooting] bayad:
Thanks for your answer Master. Have you heard about this Cyanogen Custom ROM : https://www.youtube.com/watch?v=AvXnNPw2YPs.

Maybe the first Custom ROM for our P6000 :fingers-crossed:
[Android Q&A, Help & Troubleshooting] bigrammy:
Thanks looks cool so lets hope he makes a good job of it :fingers-crossed:

I have the Stock CM11 but not even had a chance to do anything with it yet. :(

Good thing with CM11 is that it can be patched to use sony xperia z3 themes see here for that http://xdaforums.com/android/software/guide-how-to-port-real-xperia-z3-t2987476
[Android Q&A, Help & Troubleshooting] bayad:
Thanks Master but I don't know why it is so difficult to port a Rom to our P6000 ? :confused:
[Android Q&A, Help & Troubleshooting] bigrammy:
SoC to SoC it's not hard but all the ROM's I see look just the same as ours so pretty pointless porting anything for now :(

Different SoC to ours SoC is a lot more difficult :eek:

The best option for now would be the way I pointed out above as this will give our ROM a different look and feel :good: without breaking things like sims, gps, wifi, screens etc etc etc.

The video only proves he has a working Ui things like the list just mentioned are not proven but he may of managed the port :fingers-crossed:

I am sure there are plenty of cooks already working on this phone so just wait a while longer. :cool:
[Android Q&A, Help & Troubleshooting] bayad:
Ok, I see. For now, we have to wait only :fingers-crossed:

Many thanks Master for all your answers :good:
[Android Q&A, Help & Troubleshooting] HypoTurtle:
Any chance you know how to unpack/repack the boot.img/ramdisk without it becoming unbootable?

I wrote this script:

#!/sbin/sh
rmdsksplt(){
bpn=${bpn:-count}
dd if=/tmp/boot.img-ramdisk.gz of=/tmp/boot.img-${bpn} bs=1 ${bpn}=${count:-512}
bpn=skip
}
makenewboot(){
if [ -e "/tmp/boot.img-skip-new" ]; then
cat /tmp/boot.img-skip-new >> /tmp/boot.img-count
mv /tmp/boot.img-count /tmp/boot.img-ramdisk.gz
fi
cd /tmp
./mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --base `cat boot.img-base` --cmdline `cat boot.img-cmdline` --output /tmp/${1}.img
}
openramdisk(){
mkdir /tmp/work
cd /tmp/work
gzip -d -c ../boot.img-skip | busybox cpio -i -d
}
closeramdisk(){
cd /tmp/work
find . | cpio -o -H newc | gzip -9 > /tmp/boot.img-skip-new
}
ramdisksplit(){
rmdsksplt
rmdsksplt
openramdisk
echo "modify what you need to in /tmp/work then"
echo "press enter y to continue or any key to exit"
read cntn
}

chmod 777 /tmp/unmkbootimg
chmod 777 /tmp/mkbootimg
cd /tmp
./unmkbootimg boot.img
if [ ${2:-NA} = "split" ]; then
ramdisksplit
fi
if [ ${cntn:-y} = "y" ]; then
closeramdisk
else
exit 0
fi
makenewboot ${1:-new}
echo "Would you like to flash ${1}.img? y/n"
read flshbt
if [ ${flshbt:-n} = "y" ]; then
dd if=/tmp/${1:-new}.img of=/dev/block/mmcblk0p7
else
exit 0
fi
rm -rf /tmp/work
rm /tmp/boot.img-*

But the resulting .img causes a bootloop. I'm thinking it's the repack that's the issue - or is there something in the boot.img header that's needed???
[Android Q&A, Help & Troubleshooting] bigrammy:
Use [MENTION=5186178]carliv[/MENTION] tools for Windows or the linux version Here ;)
[Android Q&A, Help & Troubleshooting] HypoTurtle:
Thanks I'll take a look - my way was a on device script (run over adb while in recovery). It should be similar to the kitchen.

Kitchen works fine, as expected - just need to see what's wrong with my script.

Just to break mine down:

unmkbootimg splits boot.img into boot.img-zImage and boot.img-ramdisk.gz; and makes boot.img-cmdline and boot.img-base.

The boot.img-initrd.gz is split into the 512kb header and the rest is the initrd.gz. Initrd.gz is unzipped/rezipped then cat'ed onto the 512kb header and the boot.img is remade with mkbootimg.
[Android Q&A, Help & Troubleshooting] bigrammy:
Hi bro,

It's a bit beyond me to be honest :eek:
[MENTION=5186178]carliv[/MENTION] figured out just how to unpack/repack the newer MTK boot/recovery images correctly :good:

All his sources are on the kitchen tool thread but I am not too sure how you would do it on device or why you would need to :confused:

Maybe [MENTION=4478781]yuweng[/MENTION] or [MENTION=5186178]carliv[/MENTION] will view your code and see what's missing if they drop by :fingers-crossed:

Sorry I can't be of more help regarding this but I would be only guessing bro :silly:
[Android Q&A, Help & Troubleshooting] killkenny80:
Stock Recovery menu acting strange

I believe there is something wrong in my recovery menu...

Steps i did:

- turn off phone

- "volume +" and "power"

- shows me "dead" droid... waited, nothing happens! pushed "power" and recovery menu appeared (is this normal?)

in menu, "volume -" moves down, "power" does nothing, "volume +" selects... wtf????
[Android Q&A, Help & Troubleshooting] bigrammy:
Your using the the Stock 3e recovery thats why :laugh: And yes thats normal for that recovery.

Flash the Offcial: Compiled recovery-CWM-Modd-P6000 Download from OP. ;)
[Android Q&A, Help & Troubleshooting] killkenny80:
Thanks for your reply.

Just a question, Flashing the Offcial: Compiled recovery-CWM-Modd-P6000 Download will interfere with a future OTA update?
[Android Q&A, Help & Troubleshooting] enr88:
Yes, but you can easily flash stock recovery before ota update

Inviato dal mio m1 note utilizzando Tapatalk
[Android Q&A, Help & Troubleshooting] gooddvc@gmail.com:
CyanogenMod 12 for ELEPHONE P6000

[YOUTUBE]Zpl7J2_6S8M[/YOUTUBE]

bbs.elephone.hk/thread-3093-1-1.html#.VQRpyo6UcdI
[Android Q&A, Help & Troubleshooting] bigrammy:
Looking forward to the release of that. Thanks :fingers-crossed:
[Android Q&A, Help & Troubleshooting] mihalis341:
Do you know how can i make scatter file of my 64bit chipset? (mt6732)
[Android Q&A, Help & Troubleshooting] TImmih:
Hey guys.

I have a little problem.

I try to flash the "TWRP V2" with the tool from PlayStore "Flashify"

No i get a Bootloop and when i try go into TWRP i get this Screen....

I have added the Screen as attachment.

Who can i fix it? Or can i use my Handy now as Door stoptool? ;)

Greetings.
[Android Q&A, Help & Troubleshooting] bigrammy:
Thats the stock recovery in your picture not TWRP so probably flashed the TWRP to your boot partition. :rolleyes:

If this is the case you will need to flash the stock boot.img with spflash tool

TWRP and all the recovery's in this thread are for KitKat 4.4.4 only as stated in the OP

Don't flash anything unless you know what you're doing and have carefully read all the details.
[Android Q&A, Help & Troubleshooting] gioser6996:
thanks
[Android Q&A, Help & Troubleshooting] algre1:
recovery

i need you help pleas

to recovery
[Android Q&A, Help & Troubleshooting] bigrammy:
Drivers :rolleyes:

Better still just download Flashify from the playstore and use that to flash the recovery on that prerooted KK rom ;)
[Android Q&A, Help & Troubleshooting] mrsim:
[MENTION=3924647]bigrammy[/MENTION],

great tutorial on youtube...love the live ones they are always the best...just wanted to ask you...what do i need to do in order the physically create a scatter file..as the device i am trying to create a full backup for (Kingzone Z1) is also a 64bit mtk SoC...and does not have a stock rom available for it ATM,so using your guide i am going to try to create one myself...but have never created a scatter out of nothing before as i always downloaded one...your expert advice would be much apreciated mate....sorry for the off topic
[Android Q&A, Help & Troubleshooting] bigrammy:
LOL Yes it was live as you can tell mistakes and all :laugh:

Ok You will likely need

1. Root or working adb shell.

2. A base scatter from a device with the same SoC mt6732/6752 are the same and use the mt6752 title :good:

3. On your phone Now.

You need 1 file in /proc

ADB method:

adb shell

cat /proc/partinfo (best one to use)

File manager on device:

Just navigate to /proc/partinfo

It's safer to use the partinfo as this will ensure the full partition is backed up.

Now take your scatter (KK Scatter attached) and open it in Notepad ++ and compare the said file against it.

You will see the pattern and most likely 90% will match your partinfo :fingers-crossed:

eg:

Change the device name to yours found in you build.prop

ro.product.device=?????

From scatter.

- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6752
project: k01q_e [COLOR="Red"] < Change this to your device.[/COLOR]
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000

This is the format the scatter uses for each partition.

- partition_index: SYS3
partition_name: nvram
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x380000 [COLOR="red"]< Change these to match your partinfo[/COLOR]
physical_start_addr: 0x380000 [COLOR="red"]<[/COLOR]
partition_size: 0x500000 [COLOR="red"]<[/COLOR]
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00

The partinfo format is slightly different in that it has extra 0's after the 0x

so partinfo start looks like 0x0000000000380000 so just edit these out same for the size.

Go through the entire scatter and make any changes you need to for the partitions
[Android Q&A, Help & Troubleshooting] mrsim:
thanks for this [MENTION=3924647]bigrammy[/MENTION],

need this as ghost45,(i hope),will be able to help with this devices crappy 3gb app limitation partition once i get the scatter file up n running and able to flash a stock rom to the device
[Android Q&A, Help & Troubleshooting] bigrammy:
Ok bro :good:

Just on a side note the p6000 as a custom partition which is reflected in the scatter so maybe your phone will not have one :eek:

So just reorder the

- partition_index: SYS??

in the scatter and remove the custom entry ;)

adb shell

cat /proc/partitions

will give you a partition number and block number that should match up with the SYS??

adb shell

ls -al /dev/block/platform/mtk-msdc.0/by-name

will give you all your blocks and their name PS: dont change the "by-name" in the code as some people do :laugh:
[Android Q&A, Help & Troubleshooting] mrsim:
hey [MENTION=3924647]bigrammy[/MENTION],

just thought i would post and let you know i will be using a jiayu S3S scatter,(same SoC), so i was just wondering if there is anything else i should change before going ahead and attempting to create a new scatter for my Z1

please be aware that i am at level NOOB where this is concerned i have never before attempted to create a scatter and already i am finding your instructions hard to understand and implement

so my product name in ro.product.name is Z1 so in the scatter title i rename....project: k01q_e to project: Z1

this part below i am sure i will be able to get done without hiccups

"linear_start_addr: 0x380000 < Change these to match your partinfo

physical_start_addr: 0x380000 <

partition_size: 0x500000 <"

and i tried to enter those ADB commands,(cat /proc/partitions), but minimal fastboot and ADB recognized the device but not the command 'cat' in this line when i entered it into the command box....?

i didn't even bother to try these comands,(ls -al /dev/block/platform/mtk-msdc.0/by-name),as i thought the other commands above,(cat /proc/partitions), needed to input first before trying those....sorry for my noobishness
[Android Q&A, Help & Troubleshooting] bigrammy:
Yes thought as much bro but no worries :laugh:

Z1 is fine :good:

As for adb you could try adb shell > then su > then the cmd if not then just wing it as I did :eek:

When I did mine i had nothing to work with at all so having the scatter gets you 90% of the way there :fingers-crossed:

I suspect the SYS??? will be be the same if you dont have a custom partition

e
[Android Q&A, Help & Troubleshooting] bigrammy:
Hi,

Check/tick Usb Debugging on the phone.

Plug phone into PC

Type adb devices

If your phone is listed

Type "adb shell" (without the quotes) Hit enter.

Then type "su" (This may or may not work if it says cmd not recognized/found just move on) Hit enter.

Then type the "cat /proc/partitions" (without the quotes) Hit enter.

Then all the other ones I gave you.

All are from the "adb shell"

If you cant use adb shell then you will need to use a on device file explorer like ES File Explorer to read the said file on device.

Edit: I already replied above LOL I will leave this anyway :D
[Android Q&A, Help & Troubleshooting] laiding:
ELEPHONE P6000 android 4.4_android 5.0_CyanogenMOD 12_Flyme OS_LENOVO OS_Color OS

ELEPHONE P6000 android 4.4_android 5.0_CyanogenMOD 12_Flyme OS_LENOVO OS_Color OS

[YOUTUBE]oY7OLZl5ork[/YOUTUBE]
[Android Q&A, Help & Troubleshooting] mrsim:
hey bigrammy,

thought i would post some info here so's maybe you can have a look see as the vidoe tutorial is kinda all over the place in terms of where to put what because of your live recording

here i will attach a scatter i found over at needrom which seems to have been made without the edited real partition sizes for the kingzone Z1...also some parts seem a little different so am not sure how it was compiled by the person who posted it but some things like SYS13 (expdb)...have no actual size but this instead "0xa00000" yet as you can see from my other attachments,(screen shots from emmc),there is an actual size there..so looking for a little extra advice on this matter

p.s. also noticed in this scatter that the start and end address are all 0x0 and that's it