yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] AlexZap:
That's perfect... I can probably even build a scatter file from it. But damn, if that isn't a f*cked up partition table. OK, I'll need to scrap that last backup script... I guess the recovery puts things in different places. Anyway, its late here. After work tomorrow I'll try to make you a scatter and a backup script that will put this thing to bed...

But now that you are unlocked you should have no problem installing twrp anyway. And unlocking your bootloader always wipes your device... Part of how Android was designed.
[Android Software/Hacking General [Developers Only]] bobl61:
Agreed. I ASSumed my bootloader was unlocked. I was frustrated, and did not follow your suggestions :o. Lesson learned. I very much appreciate all the efforts provided here and hopefully we can get a backup and custom recovery that we can share with the community :good:

BTW - Edited Post ;)
[Android Software/Hacking General [Developers Only]] yuweng:
My tool uses dumchar_info for armv7 & partinfo for armv8. After seeing so many still couldn't back up Factory ROM on the latest MTK armv7 devices, i guess MTK did change something, some headers i presume & MTK Droid Tool does that checking & when found different it aborts to take Factory ROM back up... :cowboy:

As my Master Shifu Carliv once said... :cool:
[Android Software/Hacking General [Developers Only]] bigrammy:
I Just finished my last night shift and logged in to find the Master yuweng rides to the rescue again Thanks bro :highfive:
[MENTION=5384442]bobl61[/MENTION]

Why did you not give that info in the first place it would of saved us all soooo much time and head scratching :crying:

You probably owe [MENTION=5726442]AlexZap[/MENTION] a new Keyboard now. :laugh:

Anyway onwards and upwards.
[Android Software/Hacking General [Developers Only]] bobl61:
I ummmm... I mean I uhhhhh... :o :angel:
[Android Software/Hacking General [Developers Only]] bigrammy:
See here ;) http://xdaforums.com/showpost.php?p=62666628&postcount=44
[Android Software/Hacking General [Developers Only]] yuweng:
i've unsubscribed most of my threads here on XDA & now that i checked back your previous post here & got into some tinkering at why Droid Tools doesn't work on some MTK armv7, could it be just a simple adb updates & it'll work... :cowboy: [MENTION=5384442]bobl61[/MENTION] Extract & replace the files at Droid Tools's adb folder & see if it is detected now... :fingers-crossed:
[Android Software/Hacking General [Developers Only]] amscorpions:
masters and seniors..... help me to solve my device problem...

device: Dupad K1 without camera and gps

have root access too

installed boot animation app and installed a boot logo... after restart devices stuck on boot screen...

didnt find any cwm for this device...

find stock rom and updates in http://www.needrom.com/download/dupad-k1/

have backup using online nandroid but dont know how to recover it.

please help me to unbrick my device...

advance thanks to all devz
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=4478781]yuweng[/MENTION]

Most of time the problem is very simple.

If you didn't run adb devices command didn't show on the phone the trust certificate that you have to accept to enable MTKDroid to connect o the phone.

[MENTION=5733951]amscorpions[/MENTION]

Please avoid in the forum to quote an entire post. You make the thread longer without any positive aadditional point.

Just post your question.

You are completly OT (off topics)

This thread is JUST about MTKDroid.

Is not a generic thread about fix bootloop of device or other issues.

For this scope there are specifc thread. Not this.
[Android Software/Hacking General [Developers Only]] bobl61:
Thanks. Will have a look tonight when I get home ;)
[Android Software/Hacking General [Developers Only]] bobl61:
[MENTION=4478781]yuweng[/MENTION]

Replaced the files in adb folder :confused:
[Android Software/Hacking General [Developers Only]] bobl61:
I have adt-bundle-windows-x86_64-20140702 on my system and used those adb files :cowboy:

Can we do backup now?
[Android Software/Hacking General [Developers Only]] yuweng:
i always treat everyone as an Android modder pardon me...:o

MTK Droid Root & Tools is a standalone app, it doesn't depend on Android SDK (adb.exe) to operate, it has its own adb folder.

So if you extract MDRT to d: drive then it will be d:\MtkDroidTools\adb

Inside adb folder there are three files, adb.exe, AdbWinApi.dll & AdbWinUsbApi.dll. Previous post here( adb updates ) contains a direct link to the latest platform-tools_r23-windows.zip. You can either replace the three files at d:\MtkDroidTools\adb or just rename it to d:\MtkDroidTools\adbORI then extract it there & rename platform-tools to adb.

MDRT v2.5.3 was shared by OP back in 20th January 2014 & your device was launched like 2/ 3 months ago, thats why i suspect its adb couldn't support your device being the reason it is not detected.

Hopefully it works & if it doesn't then bug AlexZap, he has better experience than me on backing up of MTK Factory ROM... :laugh:

Whoops, after replying then only saw your attached photo then only realize that you got it working already... :o
[Android Software/Hacking General [Developers Only]] bobl61:
[MENTION=5726442]AlexZap[/MENTION] [MENTION=3924647]bigrammy[/MENTION] [MENTION=2472806]vampirefo[/MENTION] [MENTION=4478781]yuweng[/MENTION] Hey... look what I have :D :cowboy: :good:
[Android Software/Hacking General [Developers Only]] AlexZap:
Sweet!! I know bovirus had been providing moded copies of mtkdrt with updated adb. I think it is time he put out another version.

[MENTION=4478781]yuweng[/MENTION]: just goes to show you that sometimes the simplest answer is the best. You still rock, as always!!
[Android Software/Hacking General [Developers Only]] bobl61:
[MENTION=5726442]AlexZap[/MENTION] I'll gladly supply (upload) any files (if needed) to help out :good:
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5384442]bobl61[/MENTION]

Please make this try.

Check che in Device management your phone is right detected.

Download adb platform tool (https://mega.nz/#!TVYDxQBC!4tvA5u8QEWAbbvWMSu4WmolwuXhJaw_FCOxxtquIV20)

Decompress it and open a DOS prompt where you decompress it.

run the command

adb devices

if your device is unauthorized you will and anser on dos windows

unathorized

and check in your phone if you can see a prompt of authorization and confirm on your device.

Please try.
[Android Software/Hacking General [Developers Only]] bobl61:
C:\New folder>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.

C:\New folder>

There is no adb.exe in the Android-build-tools-v23.zip file.
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5384442]bobl61[/MENTION]

Sorry. I posted the wrong link.

Infact I talk about android platform tools and I posted the link of android build tools. Sorry.

The link for the android platform tools is

https://mega.nz/#!zFhHBRjY!DKeE-26zw5EGNLUlakhy8YVOO-GuSI9HK-lQjloEBmY
[Android Software/Hacking General [Developers Only]] bobl61:
C:\Android-platform-tools-v23.0.0>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0123456789ABCDEF device

C:\Android-platform-tools-v23.0.0>
[Android Software/Hacking General [Developers Only]] bovirus:
On the device didn't appear any request about certificate?
[Android Software/Hacking General [Developers Only]] bobl61:
Nope
[Android Software/Hacking General [Developers Only]] axesa:
how can i do to backup scatt file?
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=6915092]axesa[/MENTION]

Pelase didn't post generic question (for thsi there are some guides on first post).

Please post the details (Brand/model of the device, CPU of device, Android version, etc)
[Android Software/Hacking General [Developers Only]] AlexZap:
Can't with this phone... Ulefone be touch is a 64 bit mediatek device and mtkdrt won't work with it.

Just go to needrom and download a ROM, extract the scatter file, and there you go.
[Android Software/Hacking General [Developers Only]] Muad.Dib:
Hello Guys,

I am all new around here, and to be honest I think I would need some assistance ( plz be kind! ;) )

I have read most of the 177 pages of this thread and I likely missed a few things since I am not fully familiar with all what I am reading here, reason why I am posting for some assistance if possible.

Ok so I am trying to figure out why I cannot make a scatter file of my device.

My partitions are ext4.

My device is already properly rooted, su given to ADB shell and all, it *seems* I am able to make full Rom backup with MTK Droid Tool , no errors, goes smooth (even if I know the chip is not really supported... which might explain the inability of making a scatter file even from backup)

When I try to make a scatter file from the first tab of the application, I cannot save it, however it shows exactly like it should.

I think I have read somewhere it could be because of a locked bootloader, but is it not only a matter to root the device?

If not how could I unlock it if doable?

I did try to make a scatter file out of the backup made with MTK Droid tools, the 'boot.img' if I recall correctly, using MTK Rom Studio but it does not seem to be working with SP Flash Tools.

Is not it possible to make one by 'hand'?

Again please apologies if I made some non sense out of all this, but I do not understand why I cannot backup/restore a device which is already rooted... Not to mention I can find some ROM of that same devices, which makes me wonder how they were able to it by themselves.

I made some researches and did some reading before posting, but by all means feel free to point me in the right direction, it would be greatly appreciated.

Having a rooted device can make it very easy to mess it all up, reason why I would like some backups/restore method I could use in case of emergency.

Many thanks in advance for all the help I can get!
[Android Software/Hacking General [Developers Only]] bigrammy:
Use the scatter file from this ROM http://www.needrom.com/download/lenovo-tab-a8-a5500/ Check the partitions start address and lengh against the info from device. ;)
[Android Software/Hacking General [Developers Only]] Muad.Dib:
Many thanks for your reply [MENTION=3924647]bigrammy[/MENTION]. I indeed got that ROM (and some others) but what I do not understand, is why i cannot make my own scatter file by myself stripped from my very one device. Pick those who actually made those ROMs now available online, how have they managed to do their own scatter files to start with? Would you have any ideas maybe?

There must be some kind of a way is it not?

I would greatly appreciate if someone with more experience could point me to some directions.

Thanks ;)
[Android Software/Hacking General [Developers Only]] bigrammy:
As far as I know the "actual" scatter is produced on the PC when you build the MTK ROM :confused:

If knew how to do it any other way I would share it but I do not know :laugh:

Most people just probably do what I suggested for you to do which is to use one from a device as close to yours as possible.

Then get the partitions from your device and edit the scatter accordingly ;)

Sorry for the short answer but in kind of a rush and I would need a long time to explain in full :o
[Android Software/Hacking General [Developers Only]] hamzairshad:
ok i got that. ive done backup. now can i download it back to phone through spft?[/QUOTE]

i think its gonna work now. im happy coz i just found the stock rom :)

i need another favor to ask if u see the attached images. there is app drawer with icon Qapps and have apps in it. the second image shows whats in it. all i wanna do is remove that Qapps folder and extract all the apps in the qapps folder to the main drawer thats when u click menu
[Android Software/Hacking General [Developers Only]] azha4flat:
Hye developers. Step 1-6 i have succesfully by refer to picture. Erm. I have questions...

During the To process file ROM, it appear message,

DSP_BL - The signature isnt found

ERROR of signature, ROM file is read from phone incorrectly.

I also repeat the first until the 7th step, same problem still occurs.

Tq in advance
[Android Software/Hacking General [Developers Only]] rua1:
@azha4flat

look at 5.jpg also pay attention on Read Page Only
[Android Software/Hacking General [Developers Only]] Vings:
Eboot error 16008

Hi rua1,

Thanks for providing this great tool.

I tried flashing recovery image using this tool but i have the following error pls help..
[Android Software/Hacking General [Developers Only]] rua1:
@Vings
[Android Software/Hacking General [Developers Only]] ninonirvana:
Hi @rua, you found a solution? :confused::confused:
[Android Software/Hacking General [Developers Only]] Vings:
Thank you Rua1 for replying..

I have attached the log files.

And one more doubt, my phone is a clone of the following phone

http://www.vatgia.com/438/2599900/gionee-pocket-black.html

I created scatter file using your tool and when i used that scatter file to read back it displayed the error

"S_BROM_CMD_STARTCMD_FAIL"

I read your solution below:

But what is meant by BOOTROM mode..? is it same as fast boot mode..?

Because my phone cant boot in fast boot mode. Please help.
[Android Software/Hacking General [Developers Only]] ninonirvana:
I found the stock rom and continues the same error, is there a way to force load
[Android Software/Hacking General [Developers Only]] rua1:
@ninonirvana

You didn't answer my question in a pm. You tried other SPFT versions? For example v3.1304.0.119?

pmt scatter doesn't become the program since in this phone the non-standard structure of the table is used.

@Vings

oh... pictures of your phone aren't necessary to me ;) , the log.txt file from the folder with droidtools is necessary. Attach it here.
[Android Software/Hacking General [Developers Only]] Vings:
@Vings

oh... pictures of your phone aren't necessary to me ;) , the log.txt file from the folder with droidtools is necessary. Attach it here.[/QUOTE]

I have attached the log files below rua1
[Android Software/Hacking General [Developers Only]] rua1:
@Vings

I don't see there the log.txt file from the folder with droidtools.
[Android Software/Hacking General [Developers Only]] Vings:
I am sorry i didn't see clearly that you requested for that log file.

Here it is. Thanks for your patience.
[Android Software/Hacking General [Developers Only]] rua1:
@Vings

judging by a log you already made ReadBack and your previous issue is already resolved
[Android Software/Hacking General [Developers Only]] Vings:
Yes i have been able to read back using an OTG cable. I used that rom dump in MTK droid tool and it created the recovery file. But when i try to flash that file i get the following error.
[Android Software/Hacking General [Developers Only]] Mawe79:
@Vings

try a diffrent USB Cable!

If you don't have diffrent one use diffrent USB Port!

think than it should work
[Android Software/Hacking General [Developers Only]] The Solutor:
Hi.

I've successful rooted a freshly released, and "unrootable" Alcatel One touch Star (6010D), so thanks for your efforts.

Btw I still have some doubts

#1 this is the scatter file I got

PRELOADER 0x0
{
}
DSP_BL 0x40000
{
}
MBR 0x1000000
{
}
EBR1 0x1004000
{
}
__NODL_PMT 0x100c000
{
}
__NODL_NVRAM 0x140c000
{
}
__NODL_SECCFG 0x190c000
{
}
UBOOT 0x192c000
{
}
BOOTIMG 0x198c000
{
}
RECOVERY 0x1f8c000
{
}
SEC_RO 0x258c000
{
}
__NODL_MISC 0x2b8c000
{
}
LOGO 0x2bec000
{
}
__NODL_EXPDB 0x2eec000
{
}
__NODL_PRO_INFO 0x30ec000
{
}
CUSTPACK 0x33ec000
{
}
MOBILE_INFO 0x1d0ec000
{
}
ANDROID 0x1d8ec000
{
}
CACHE 0x375ec000
{
}
USRDATA 0x4aeec000
{
}
__NODL_RSV_OTP 0xffff0200
{
}
__NODL_BMTPOOL 0xffff00a8
{
}

Anything worked perfectly but there is the custpack partiton (that contains vital infos) that I can't see in the backup folder (I have just a __nodl_custpack file), nor is backed up by the recovery itself, so I'm still worried about experimenting further with the phone, is dd my only hope to dump that partition ?

#2 I flashed the recover only altough I have the patched boot image too.

Is there any advantage trying to flash the boot image too ?

#3 Both the patched recovery and boot are actually smaller than the original ones, is that the expected behavior ?

Thanks in advance for your reply.
[Android Software/Hacking General [Developers Only]] Vings:
Thanks for responding, I tried it through 3 different cables (one was an OTG cable) in all the USB ports available in my Laptop but still the same error.

I'll uninstall the drivers and try again today. BTW is it possible to flash with a standard micro usb cable or should i use an OTG cable.

Because when i plug in my device using an OTG cable it is detected as MTK USB port but with a normal micro USB cable i get MTK pre loader.

Which one should i use..? :confused:
[Android Software/Hacking General [Developers Only]] hamzairshad:
Only for qmobile a2

If your in pakistan and have qmobile a2 v3 then follow this tutorial to root and flash cwm

http://xdaforums.com/showthread.php?t=2235562

strictly for the mentioned model

credit goes to rua1

---------- Post added at 12:34 PM ---------- Previous post was at 12:08 PM ----------

what is patched boot @rua1
[Android Software/Hacking General [Developers Only]] rua1:
@The Solutor

1# rename it manually, I will correct in upcoming version

2# if you ask such question, it means to you it isn't necessary ;)... permanent root shell is necessary to me and I always load it

3# everything is all right, all contents of block are read from phone and in the tail it is filled with empty bytes

@Vings

It can be not set the driver on DA_HIGHSPEED VCOM port. Read here: http://xdaforums.com/showpost.php?p=38369102&postcount=11
[Android Software/Hacking General [Developers Only]] Vings:
Hi rua1,

So the next time i connect my phone i should install the MediaTek DA USB VCOM Port right...?

when i connect my phone to my Computer it detects the device as USB VCOM Preloader for 2 seconds and then disappears, Is it because i use a normal USB cable (Not OTG). I installed ADB drivers (able to see attached device using ADB commands) Please help.
[Android Software/Hacking General [Developers Only]] AlexZap:
You can build a scatter file by reading /proc/partinfo, and knowing what the specs are for each partition. The file gives you partition names and sizes, you just have to know all the other info for each partition that goes in the scatter. Luckily it is all identical from ROM to ROM (system always has the same properties regardless of what ROM, tho size and position on disk may change). I have the beginnings of a script that does it, but there are a lot of custom partitions out there. I need scatter files to keep the script up to date.
[Android Software/Hacking General [Developers Only]] bigrammy:
:confused: Not sure if this aimed at me but just incase yes bro I know I was the first to make a scatter for the P6000 mt6732 before any mt67xx rom's were available then about one week later Elephone forum released the "Official Rom" who's scatter was identical to the one I shared btw :rolleyes: :laugh:

I made a video TUT on how to do it I but pulled it after the official release due to noob's possibly screwing up their phones if they got things wrong. :eek: I announced it on the elephone forum after making the video tut.

I think that [MENTION=6922230]Muad.Dib[/MENTION] was asking if there was a kinda generic way to do it as comes in the factory ROM's ie: some kind of cmd or option to make one on the device :confused:

I just thought I would give him the easy way since there is a 99% identical device to his own already :laugh:

On a side note:

I have been messing with my new Siswoo mt6753 and testing things out so I will post the things I have found out so far tomorrow but I think the one click solution of mtkdroidtools is long gone :crying:
[MENTION=4478781]yuweng[/MENTION] may also be interested as it will affect his recovery tools too :eek:
[Android Software/Hacking General [Developers Only]] yuweng:
As explained by Carliv ( link deleted due to DCMA ), it is define at ptgen.pl that actually reads the partition table from a xls template file... :cowboy:

i'm more concerned of his well-being but nobody knows what happened to him, i guess life still move on... :angel:

To others

Behind the front end of MDRT, it is still running adb command line & most of the manual techniques has been covered here on XDA, such as IMEI, a quick search will lead you to it with the correct keyword, as for Factory ROM backup on latest armv8, use AlexZap's script... :good:
[Android Software/Hacking General [Developers Only]] yuweng:
In fact, its actually Carliv that taught me how to look for stuff at github... :o :good:

Thanks for the update my friend, it seems that your bootloader is also locked, hmm, i think all latest MTKs are like that, better unlock it first or you'll brick it... :laugh:

(bootloader) warranty: yes
(bootloader) unlocked: [COLOR="blue"]no[/COLOR]
(bootloader) secure: yes

As for the recovery tool, getting lazy to updating it since i don't own any latest MTK, may be when i really got nothing else better to do.... :laugh: But then again, you guys are experts now at porting custom recoveries... :good:

i wonder why nobody use the very same techniques here item 6, upload only the recovery, port custom recoveries then root it via recovery... :good: In fact you can use any scatter.txt, it doesn't matter, just input the correct size & length that you got from proc/partinfo & upload will work, tips from syserr... :good:

Updates

Hmm, how do you download it without a valid scatter.txt.... :D
[Android Software/Hacking General [Developers Only]] jrm1213:
N/A
[Android Software/Hacking General [Developers Only]] bigrammy:
Hi yuweng I was working as total stock and not rooted so I could confirm the things mentioned work on stock user phones :good:

To unlock fastboot is easy with the option OEM unlocking in developer setting followed by the oem unlock cmd from fastboot. This does wipe your data though ;)

So I guess your method of using a random scatter editing it for the recovery/boot then doing a readback would work with a fastboot unlocked :confused:

I will test it to see if it works :fingers-crossed:

Working for me bro :eek: Maybe I was editing my post at the time you tried plus this site has been acting crazy lately :laugh:
[Android Software/Hacking General [Developers Only]] yuweng:
No need to unlock bootloader to read back, you need to unlock bootloader when you download it. You'll need AlexZap's script to generate a valid scatter.txt to be able to download your ported custom recovery... :cool:

Updates

On 2nd thought, you might even be able to backup all the partitions including preloader on MTK armv8 devices via custom recoveries, i donno, you'll have to R&D it.... :laugh:

recovery.fstab

/preloader	emmc	/dev/block/mmcblk0boot0

init.rc

mkdir /preloader

Though the backed up preloader needs cleaning up of the unused header & footer for use with SPFT, restoring it via custom recoveries will brick your device... :cowboy:

You won't even be able to boot if preloader is miss-match or corrupted.... :D