yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] vbdss:
yuweng thanks for your prompt answer

If i post the scatter file, would it help, i see in the build.prop that everything is symlink with emmc

i ve downloaded the 3 files from the OP, do i need something ele?
[Miscellaneous Android Development] yuweng:
Hmm, a quick search shows that RSD uses sbf extension instead of standard img... :cowboy:

Does your stock firmware has this recovery.sbf then upload it & i'll have a look at it... ;)
[Miscellaneous Android Development] vbdss:
it uses .mzf file format

RSD for non-MTK use the .sbf, for MTK devices it uses .mzf

I have a 4shared link for the stock firmware, its about 330mb,

http://www.4shared.com/zip/geKWufnF/XT920_2_310_2009_A02_MPmzf.html
[Miscellaneous Android Development] yuweng:
Hmm, there is a /flex partition which i think its the internal sdcard...

So it might not properly backup/ restore so use at your own risk however you can re-flash your stock recovery at any time... :o
[Miscellaneous Android Development] vbdss:
Should i use mobileuncle app to install the recovery?

Enviado de meu XT920 usando o Tapatalk 2
[Miscellaneous Android Development] vbdss:
Using mobileuncle i have installed the file but the phone will not reboot to recovery or to the system, had to reflash the firmware.

Enviado de meu XT920 usando o Tapatalk 2
[Miscellaneous Android Development] pratikmore:
You installed recovery for your phone or other phones recovery？
[Miscellaneous Android Development] vbdss:
For my phone of course, using the recovery.img that yuweng posted for my device

Enviado de meu XT920 usando o Tapatalk 2
[Miscellaneous Android Development] vbdss:
Well even though it's not working the recovery done with the tools, I know the bootloader isn't locked since it flashes the recovery using the mobileuncle tool

Enviado de meu XT920 usando o Tapatalk 2
[Miscellaneous Android Development] yuweng:
As i always said, you never try it, you'll never know... :cowboy: Many has reported recent Mobileuncle tools doesn't even flash it correctly on standard MTK devices & i believe its not compatible for your device... :o

TWRP has been ported to your XT919 so now its up to you to find ways to flash it in... :cowboy:

Try it with SP_Flash_Tool_v3.1224.01 & Driver_Auto_Installer_v1.1236.00.rar, copy your scatter.txt & ported TWRP recovery-sign.img to a new folder then point SPFT to that folder scatter.txt & hit Download... :fingers-crossed:

If it says Need Download all images then copy everything from XT920_2_310_2009_A02_MP_USBALL\USB\001 except the stock recovery-sign.img to this new folder & hit download again & hope it works this time... :cool:

The last step that i can think of is copy TWRP recovery-sign.img to XT920_2_310_2009_A02_MP_USBALL\USB\001 to replace the stock & use RSD Lite to flash it... :fingers-crossed:
[Miscellaneous Android Development] vbdss:
The thing is, when I use SPFT , it says that the band-chip is secure ERRO 5000 and then it stops.

The phone have the bootloader with the option to go to recovery which is 3e.

Tried fastboot too, using fastboot flash recovery recovery.img but an error come up too.

Maybe it needs a updated SP flash tool to work with it, or maybe a way to pack the firmware again to mzf format but replacing the stock recovery with TWRP.

Enviado de meu XT920 usando o Tapatalk 2
[Miscellaneous Android Development] yuweng:
Final one i can think of is adb . . .

copy recovery-sign.img to your sdcard & execute below command . . . :fingers-crossed:

adb remount
adb shell su -c "dd if=mnt/sdcard/recovery-sign.img of=/dev/recovery"
adb reboot recovery
[Miscellaneous Android Development] vbdss:
I will try

EDIT tried that but the same thing happens, the phone will boot, but after a while it will turn off on the bootanimation

i think the problem is with the recovery, maybe when flashing the ported CWM or TWRP without further tweaks, it will screw up something, because of course it is right, but maybe because of the way the phone system works, like the flex folder which comes with google apps and some more apps.

Maybe the blocks, i dont know, maybe an expert can find what is, since i dont have this kind of knowledge, i will leave it alone.

Anyway thanks for your help, but can i ask one more thing? can you somehow extract or decompile the recovery file that comes with the stock firmware that i sent you the link ?

Enviado de meu XT920 usando o Tapatalk 2
[Miscellaneous Android Development] yuweng:
AFAIK, there are only two tools to unpack/ repack MTK boot/ recovery.img & it has been mention on this thread before... :cowboy:

Linux version shared by Master Shifu bgcngm here & Win version shared by Russian Master Shifu Michfood here... Lately, my porting tool is based on the latter... :cool:

As for unpacking mzf file, i thought we are using the same RSD Lite... :confused: It unpack mzf into SPFT file format & thats how i ported TWRP to your device...
[Miscellaneous Android Development] vbdss:
Unpack mzf is fine, I was thinking about repacking the files again but using the modded recovery. Thanks for your help

But anyway, I will try to look into the decompiled recovery file and see what I find.

Right now I can only think that the recovery done using your tools, is somehow affecting the way the phone works.

The phone boots but when comes the bootanimation, it halts and the phone turn off.

I think the problem is the flex partition which have some system files, apks and other stuff.

Enviado de meu XT920 usando o Tapatalk 2
[Miscellaneous Android Development] yuweng:
First, you must understand that all software needs to be in unpack format to be installed, just like any other Win OS Setup.exe... :cowboy:

So i think what RSD Lite does is that it unpack mzf & flash it like SPFT, the only different i presume is that there must be some check-sum so it doesn't let you install when any one of the file has changes... :cool: It has nothing to do with /flex partition... :cool:

As for the ported TWRP, i think may be it is installed to the wrong partition thats why it doesn't boot ( overwrite to system partition )... :o By right, even if it not compatible, it should only corrupt your recovery but not whole OS... :o

Try check it with below command...

adb shell
cat /proc/dumchar_info

i presume recovery is not at /dev/block/mmcblk0 ( /dev/recovery )... :D
[Miscellaneous Android Development] vbdss:
I understand the RSD deal and I thought about the files having a check sum, buy it was only a thought.

The screen with the code issued on the android terminal app

Enviado de meu XT920 usando o Tapatalk 2
[Miscellaneous Android Development] arnabbiswasalsodeep:
could you port this recovery for karbonn a11 or mtk6575 devices

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

If I helped then press thanks
[Miscellaneous Android Development] yuweng:
Sorry bro, can't port it as non of it are compatible for our MTK devices... :cool:

And PhilZ has make it too custom, i don't think even PhilZ himself or any other DEVs are willing to look into those source code to it make compatible for our MTK devices...

it might even require to write the whole codes all over again from grounds up to support MTK devices... :eek:
[Miscellaneous Android Development] alley23:
hi,

will this work on my LG optimus L5 II - E450?
[Miscellaneous Android Development] yuweng:
Hmm, as i always says, you never try it, you'll never know... :o

Having said that, i believe L5 CWM will have better chances of booting up on your L5 II... :fingers-crossed:

Use Master Shifu Michfood's Drag & Drop Utils here...

Just unpack both, delete the whole rmdisk folder on your L5 II & replace it with L5 CWM rmdisk folder & repack it back... :cool:
[Miscellaneous Android Development] andrman1:
I tried to port recovery from Alcatel 6030D to Alcatel 6010X but nothing ?
[Miscellaneous Android Development] tvcat-xda:
Hi, im using the Auto Port CWM for my lenovo s820 with CWM by C3C076

but after i click ok button then nothing happen at all

i did put the compatible recovery image into the cwm folder

its all good when im using "CWM 6.0.3.0 for MT6575/ 77/ 89"
[Miscellaneous Android Development] yuweng:
double-click it again, the adb root checking part sometimes doesn't work properly... :o And it wouldn't work if your boot.img is secured ( ro.secure=1 )
[Miscellaneous Android Development] tvcat-xda:
thanks for the help.

double click again and all good but i think that cwm is not compatible with lenovo s820 because it stuck at the boot logo

but i can boot into android just fine

i think i have to keep searching again
[Miscellaneous Android Development] rnovino:
tutorial

hi [MENTION=4478781]yuweng[/MENTION] hopefully you can create a quick tutorial on how to use the lastest Auto porting of the CWMR and also note the things that needs to do in order for it to work, and precautions like you said that if the boot.img is secure.ro=1 it will not work? because not all of the users here are followers of every update of the auto porting and like me I usually check this if i have a new MTK mobile phone :) thanks in advance and keep up the good work :)

so far what I did is copy the stock recovery of my phone to the STOCK folder and copied also the CWMR recovery that I have converted using the other porting tools that you provided but then it showd ADB SHELL not working? so thus this mean I need to update first the recovery.img? kindly advice thanks
[Miscellaneous Android Development] yuweng:
i've tried to make the tool as n00b/ newbie friendly as possible that's why i take out the manual-port part b'cos everyone will just use it & corrupt their recovery... :cowboy:

The new program will detect if you are using MT6573, Alcatel or any other non-MTK devices then it will prompt not compatible... :cowboy:

But obviously many still uses secured boot.img in spite of getting root access on their device, thats why adb will fail to pull recovery.img directly from your device... :o

i'll have to look at the whole program all over again... :o
[Miscellaneous Android Development] rnovino:
base on my understanding ,

in order for this to work it need to change the ro.secure=1 to ro.secure=0

to achieve that is we need to use the kitchen and extract the boot.img of our device and port it back again to our device is that right?

and then we can now proceed on using the AutoPort CWM?
[Miscellaneous Android Development] yuweng:
Yes, as simple as that but many n00b/ newbie wouldn't know how to do that... :o

Hmm, i think i might need to bring back the manual-port feature... :laugh:
[Miscellaneous Android Development] rnovino:
I already did the modified boot.img of ro.secure=0 and repacked it but still it says adb not working :( I am also already on a stock recovery and putted the cwmr compatible recovery on the CWM folder still it didn't worked :(
[Miscellaneous Android Development] yuweng:
try adb remount & see what it says, that how the program detect whether your adb shell is working & you should be at a fully booted up Android OS & not at CWM when using this tool... :cowboy:
[Miscellaneous Android Development] rnovino:
Thus my phone need to be in

Normal boot mode?

Recovery mode?

Fastboot mode?

When using the autoport cwn
[Miscellaneous Android Development] yuweng:
And i thought you're a seasoned modder, unless specified, mostly android tools are for fully booted up or as you said Normal boot mode use... :cool:
[Miscellaneous Android Development] rnovino:
I am just making sure I am doing the right procedure because I have tested it on a recovery mode, fastboot mode and normal mode but it seems I can't make it worked and I also followed your instructions but still it does not continue the process very weird

thus in any point there have been a discussion of someone successfully made this worked because this is a very long thread hopefully you can linked it so it will be easier :) thanks again for the patience :)
[Miscellaneous Android Development] yuweng:
As Master Shifu dsixda once told me, many uses his tool but not many feedback when something is not working... He has even ask users for beta testing but non come back with feedbacks, the same for me here too...

Tools are made to make certain task easier & it needs users feedback to improve & thank you so much for show up & your feedback too... ;)

Yes, you can link that page here too, i might learn a trick or two from them... :laugh:
[Miscellaneous Android Development] rnovino:
this is the tutorial I made base on what I learned here :) http://www.slideshare.net/randolphnovino/how-to-root-the-cherry-mobile-omega-hd-2

I also created a video tutorial, http://www.youtube.com/watch?v=2H_zGqCD7dc, If ever I make this Autoport CWM work on my end I will create another tutorial for it as for a contribution for this wonderful tool :)

because when I converted our stock recovery to the cwm via MTK droidtools latest build it had some issues of it cannot backup large amount of file ex. 6gb of data. so we thought that if ever we used the cwm v6 it will fix the issue but it turn out it had another problem of the overlapping issues, so I think the solution for this one is the new autoport version but i still can't make it work hmmm :(
[Miscellaneous Android Development] yuweng:
Yeoh bro, you already look like an android geek...

Nice video, very clear...
[Miscellaneous Android Development] BaSch83:
Many thanks to you (yuweng) and all the devs you mentioned.

I tryed your Auto Port Tool for v6032 it will run thru the whole process without any errors but at the end the new modified recovery.img it exactly the same.

The recovery.img i use is a v5504 created with MTKdroidTools v246.

If i try Auto Port Tool for v6030 manual not automated it seems to work correctly but the file which is created is to big 6156KB

What i am doing wrong?
[Miscellaneous Android Development] yuweng:
this new tool is meant for you to hunt for compatible MTK CWM yourself; two example i found working, mentioned at the OP or any other newer version... :cowboy:

If the original you're already using is v5504 & you use v5504 recovery.img to port then obviously you will get back the same v5504...

You can also use ported v6030 recovery.img for the new tool, it will tell you if its over-size, as long as its not over 6,291,456 bytes then it should work... :fingers-crossed:
[Miscellaneous Android Development] BaSch83:
I think i missunderstood the function of that tool.

I thought it will update my already existing CWM to the latest Version6032.

But it will port a CWMv6032 from other device to my Phone, i am wrong?
[Miscellaneous Android Development] mmrehman555:
Yo...bro u always rock...just downloaded the recovery tools..awesome....

Following u just right here....
[Miscellaneous Android Development] yuweng:
i've just explained to you at the previous post & it was mentioned at the OP & you asked the same question again...

Yes, it will port any new or old compiled CWM for MTK devices to your device, of course HTC or Samsung CWM wouldn't work on MTK... :cowboy:

Having said that, you gotta test it yourself whether it works; other than the two mentioned at the OP which i've tested & confirmed everything working... :cool:

Yeoooh bro, you have been MIA for quite awhile now...

So glad you're back at the scene here... ;)
[Miscellaneous Android Development] Thomas Vaccarini:
http://sourceforge.net/motorola/razrd/home/Home/
[Miscellaneous Android Development] spit85:
I solved the problem to use MtkDroidTools and select to connect the phone with root access to adb, then let MtkDroidTools run in the background and then run your porter, then it will run.

The latest version from MtkDroidTools you can download here

If you open MTK Droid Root & Tools and connect your phone, you will see in the left bottom that the phone is in root shell (see the first picture below). If you don't see that your phone is in root shell, click on root (see the second picture below). It's possible that you will prompted on the phone by your superuser app, to give ADB root access. Of course you will give the root right. Leave MTK Droid Root & tools in the background and open AUTO PORT CWM from yuweng

To see the pictures, click to show the content.
[Miscellaneous Android Development] farenheith:
yuweng, I followed the support you gave to vbdss about the RAZR D3.

I have one too and I'm trying to get a custom recovery working on it.

About the problems experienced before by vbdss, I think the thing is the recovery size. The stock recovery is 4461 kb, while the trwp you ported have 5776 kb...

Looking into the scatter file, I could see that the space for recovery is 4460 (idk if is kb as i don't understand much about this, but I think so).

Maybe if we create a recovery.img that fits this size we'll be able to flash it even through mobileuncle.

I'll try to do it by myself, but as I'm starting with this, if you have some tip or think it's the wrong way please tell me :)
[Miscellaneous Android Development] yuweng:
All branded devices are known for locking their bootloader especially Motorola & i believe its the same for MTK Razr D3 however its non-in-existence yet... :cowboy:

As for the recovery size, its the same as standard MTK devices except for the /flex partition, MTK custom recoveries should work as long as it doesn't exceed 6Mb... :cool:

i may be wrong about the lock bootloader so somehow you gotta find a way to download/ push/ install this TWRP as it is confirmed working on MTK devices... :cowboy:

What i did was unpack Razr D3 recovery-sign.img repack its kernel with MTK TWRP 2.5.0.0 ramdisk, thats all & it should work... :fingers-crossed:
[Miscellaneous Android Development] farenheith:
Thanks, dude.

About the locked bootloader, I think this device have some equivalent protection, idk.

Just after I ask you about I tried a junk recovery of just 3,5 kb and I got the same issue. I was discussing with a friend and they suggest that maybe exists some kind of uboot validation, like a checksum of the partitions. As the normal boot in theory don't touch the recovery partition, then this is the only explanation that make sense to me :/. But if this is the problem and the sp flash tools requires a authorization file to flash on our device, then it's look like a dead-end for now.

I'll try to find a way to repack the mfz file as [MENTION=4182895]vbdss[/MENTION] suggested, but I think this will not work either because the process probably will valid a signature of the files. The only way I can imagine is to find out if this checksum validation we suppose really exists and try to disable it or discover how it's working.

As soon as I can I'll take a look in the open sources of our device to see if there are some clue. Thanks to [MENTION=3138674]cmgonzalez[/MENTION] to provided me.

If anyone is interested in research about this too or have some idea is very welcome :)
[Miscellaneous Android Development] yuweng:
i've actually asked vbdss to test it out here presumably its not locked but he never really fully tested it... :o

You may wanna try out with this version too, many have success on MTK while other version fail to download... :good:

if its not locked then SPFT is the key as i've seen this on LeWa Software Flash Tool similar to RSD...

What i found out was at C:\Program Files\Motorola\RSD Lite\MTK there is a Download_Agent folder & SPFT dll files, i remember asking him to copy all those dll & replace it to SPFT folder...

Load the scatter.txt, you only need to tick recovery & load Download_Agent bin one at a time & hit Download then only plugin device USB to pc & download should work... :fingers-crossed:

Fyi, most MTK devices download without battery & some with it...

i've tried it on my MTK with RSD's MTK FlashToolLib.dll it doesn't crash when load D3 scatter.txt without it, it crash... Try with existing D3 USB driver first, if it doesn't work then only try it with MTK...

Good Luck but be WARN it may brick your device too... :fingers-crossed:
[Miscellaneous Android Development] farenheith:
RSD does have a download_agent, indeed. Also, this program unpack the mzf in an usual MTK ROM folder with scatter file and stuff, and generate an authorization file called <something>0031.auth.

I already tried to flash the own stock recovery using sp flash tools in the normal way, pointing to this auth file and also pointing to the rsd download_agent, with no success,

Also, I tried the point to a file called <something>0031.bin as certificate, this file is inside the download_agent folder of the RSD, but I got a security fail either :/. When I get home I'll tell what error is.

Finally, I notice that the RSD have a folder with the same sp flash tools dlls (I don't remember now if it's a subfolder or the main folder). The difference is that the RSD have a newer version of the dlls. I tried to replace the dlls from SP with these ones but then I get an error when tried to execute, so this new version is incompatible with the older one :/

My shot is that I need a RSA private key to make worth the authorization file, or something like that, but I still don't know how to use it.

The the fact is: we succeed in flash a recovery using *dd if of*, but the phone doesn't boot properly after that. This can be for two things:

1 - The validation I theorized before

2 - Did you notice that the bootimg and recovery have a conflict in the section area? Maybe we can't trust in the /dev/recovery to write it, maybe we can only do this in download/flash mode. If so, or we must supply properly the validation for the sp flash tools, or we need a up to date one, that uses the same version of the mtk dlls that RSD does.

In this second case, also, repack the mzf file is a good shot, regardless I don't trust in this method too much
[Miscellaneous Android Development] yuweng:
Thats not the way to use SPFT however i donno if it will work on D3 thats why you gotta test it all... :o

On MTK, you only need two parameter for it to download, 1) Download Agent 2) Scatter-loading ( Refer to previous pic )

You only need to change the Download Agent if it doesn't work scatter.txt remain the same...

Copy all from RSD Lite\MTK to SP_Flash_Tool to replace it...

Then load the Download Agent from MTK\Download_Agent starting from MOTDEVARIMA000002.bin then download, if it doesn't work then move on to the next one until you try all until the last one MOTPRDCELLON000004.bin...

i believe one of those DA should work... :fingers-crossed:
[Miscellaneous Android Development] farenheith:
I see.

Worth a try. As RSD creates a file called ***0031.auth, I think it will be the 31 one.

When I get home I'll try and tell you! Thanks for the discussion!

Edit: Oh, about replace from RS lite\MKT to sp_flash_tool, I already tried that...It's not compatible with sp flash tools I got an error :(. But I'll try with each one of the bins

And I know that no MTk before had such a secure level like that... but you know, it's a Motorola phone, probably they increased the security on that one.

Edit2: Maybe If I try with a new version of sp flash tool... this one, maybe.. the one I'm using is 2.4.7 I think

I just confirmed: the version of FlashtoolLib.dll is the same of the RSD in that one :o
[Miscellaneous Android Development] farenheith:
The only usable bins are the 31, 30, 28 and 26. With all I have the same error when I point just the scatter:

When I point the authorization file

Look that the authorization file is called MOTPRDARIMA000031.auth, and this file was generated by the RSD itself. In that way, I think the correct one is the 31 for my device. Also, I think this authorization is applied over the whole firmware, probably is a signature generated for some private key and will only match if I do a firmware upgrade. I didn't try that as I'm afraid of the consequences, I read somewhere advices to not flash the PRELOADER and the DSP_BL partitions :p

But if this is the thing, then we can't do something like flash the whole firmware changing only the recovery.img as the signature will not match :(. But this device does need a authorization file, unfortunately. I'll think and research about it to see if I can find a way...

If you have some idea Il'll very appreciate.

Thanks for the support, dude :)