yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] ZRK_NanDRD:
Hi. Sorry for asking here, were can I get a custom Recovery for Vodacom Power Tab 10" (MT6580)?
[Miscellaneous Android Development] blakegriplingph:
Could you get me the stock recovery and boot images so I can look into it when I have time?
[Miscellaneous Android Development] eddycorez:
hello bro . i have same problem too . can i have the new twrp recovery link for it . my fon is j7+ clone mt6580 and kernal is 3.10.72 . :D
[Miscellaneous Android Development] blakegriplingph:
Send me the ROMs for it mate. That or PM me and I might be able to help you dump the ROM so I can build a TWRP image.
[Miscellaneous Android Development] taya6519:
S7 clone bricked

Hi bro.

I also have an S7 clone that I believe may have originated in Korea. It got bricked, and am having trouble finding he right firmware to flash to it, as it is not easy to find. Cannot boot into recovery mode, and when I turn it on I just get a brighter version of the black screen it has when off.

This is the only info I was able to get off the phone:

JDQ39.ANDROIDXXUAMDL

ALPS.L1.MP6.V2

A800ZCUEAOE2

A1000017F1000D

3.10.28-4933931 dpi@SWDD3017 #1 Mon May 18 18:14 KST 2015

I do know it has an MT6580 chip, but that's about it.

Any chance anything can be done about this? Or do I need to dump it in the basura?
[Miscellaneous Android Development] blakegriplingph:
Care to give me any pics of the phone in question?
[Miscellaneous Android Development] taya6519:
This forum is not allowing me to upload the photo links. On Needrom, the image is exactly the same, and hte page title is "SANNO A800 MT6580 THE REAL CPU IS MT6572"

There is a stock ROM for it at Needrom, but it does not work. (sanno-a800-mt6580-the-real-cpu-is-mt6572) When I try to load and flash the ROM I get this error message:

ERROR: S_FT_ENABLE-DRAM-FAIL (4032)

[EMI] Enable DRAM Failed!

[HINT]:

Please check your load matches your target which is to be downloaded.

I know the CPU is an MT6580, not the MT6572 that the Needrom page says it is, as I have checked that already, and anything but an MT6580 flash ROM fails with the error message that it is the wrong chip type.
[Miscellaneous Android Development] blakegriplingph:
Well you could PM me the pics if you want.
[Miscellaneous Android Development] taya6519:
Hi,

Sorry I have worked it out now. Please forgive the noob here.

Here are the pictures.

This is the error I get:

https://xdaforums.com/picture.php?albumid=15128&pictureid=58024

And this is the phone:

https://xdaforums.com/picture.php?albumid=15128&pictureid=58019

https://xdaforums.com/picture.php?albumid=15128&pictureid=58020

https://xdaforums.com/picture.php?albumid=15128&pictureid=58021

https://xdaforums.com/picture.php?albumid=15128&pictureid=58022

As you can see, it is a Samsung S7 clone. Had to peel away added layers of IMEI number stickers in the back of the phone to find out that it was originally a Sanno. Unfortunately, most of the last label got ripped, but I could see it said "A800" underneath.

This is the Needrom image:

https://xdaforums.com/picture.php?albumid=15128&pictureid=58023

I have tried the stock roms from needrom, but keep getting the same error messages. The same thing happens with all the A800 MT6580 stock roms I try.

I checked the MTK USB port using the device manager and plugging the phone in holding the V+ key, and it shows in dev man.

I have another clone that runs off the MT6580 rom, and i extracted it and built a custom rom, both with and without preloader, and it loads fine, but it still does not boot the phone, just has a brightened black screen when I turn it on.

Unfortunately, I am now at a loss, as this is the total extent of my knowledge on these things. I hope you can help.

Thank you.
[Miscellaneous Android Development] alecxs:
No matter if MT6580 or MT6572 you can make a full ROM dump with MediaTek SP Flash Tool for further analysis. Make sure you have MediaTek MT65xx USB VCOM Preloader USB Drivers installed.

Use any scatter file, select PRELOADER, start Readback, connect phone, then insert battery.

If this work, repeat a full ROM Readback without scatter file. You need to specify ROM length for this.

Install WwR MTK v2.30 and analyze the preloader. Then analyze the ROM. This program creates a new scatter file based on results.

With this scatter file, make a readback of boot and recovery. Provide this files for analysis, or try to unpack with CarlivImageKitchen-Linux-DnD-yuweng.zip by yourself.

If you flashed a wrong ROM, of course nothing of this is useful anymore
[Miscellaneous Android Development] taya6519:
USB VCOM Preloader drivers are loaded, and PRELOADER readback comes back ok. However, when I try to do a readback without a scatter file loaded I get an error asking me to load a scatter file first.

Edit -

When I change the scatter file to a different one, I get the same DRM failure message again when I do a PRELOADER Readback.

What I need here is a way to load the scatter file that apparently should be in the phone, which, accoding to my research, I now have. I downloaded the MT6580 scatter file from Needrom for the Sanno A800. Unfortunately, all I get is the same error message telling me that the DRAM Enabling has failed.
[Miscellaneous Android Development] alecxs:
You are right. You need a dummy scatter file. Just use the one you have. On Readback screen: Remove all Entries, Add a new Entry. Save the file name ROM_1, select Region: EMMC_USER, Start Adress: 0x0000000000000000, Length: 0x0000000390000000 (example size). This will fail when the size is wrong. perform a RAM test to get the length needed. There is a Tutorial How to use Wwr_MTK + SP Flash tool to backup Mediatek rom

to cut short this - if wrong ROM flashed in Firmware Upgrade mode, there is no chance to get the old scatter back from phone. if flashed in Download Only mode, you should be able to create a new scatter file - or you already have working one!

Please do a readback of boot and recovery with working scatter file. this is needed for creating TWRP recovery - which you can ask in this thread. concerning fix your bricked phone please open a new one (we will find all threads started by your member name)
[Miscellaneous Android Development] Eleazarjohn:
Recovery

Please help me find custom recovery for my phone ALPS.L1.MP6.V2_YUANDA6850.WEG.L_P2

Mt6580 kernel ver 3.10.72
[Miscellaneous Android Development] blakegriplingph:
Apologies if I am unable to do TWRP images for your phones as I've been incredibly busy lately. I'll see if I could accommodate you guys though.
[Miscellaneous Android Development] Voxely:
Hello !

Is it work on Wiko Sunny 2 ?
[Miscellaneous Android Development] blakegriplingph:
I don't think so, unless I find the time to port it to your phone. Been extremely busy lately so apologies if I am unable to fulfil requests for a recovery.
[Miscellaneous Android Development] Voxely:
Thank :)

You have at least taken the time to answer me and if you can not port in to my phone, it does not matter :)

Good day !
[Miscellaneous Android Development] itsmemario:
Hi there,

I have a "Alcatel OneTouch Star Pop" (5022D) here.

Beeing aware its crap and there is nothing like root or custom recovery...stumbling across this thread gave me hope

and I wonder if there is the slightest chance to mod TWRP for it ?

It also uses the MT6580, running Lollipop MR1 (5.1). If you need further infos, feel free to reply here.

If you still dont have time, no problem. :)
[Miscellaneous Android Development] blakegriplingph:
I might look into it some time. Can you send or at least direct me to a firmware dump of this so I can try and churn out a recovery for you?
[Miscellaneous Android Development] itsmemario:
Hey and thanks for the quick reply ! :)

All I can offer is the OTA 5.1 (Stock) update via mediafire : (havent checked it ny myself yet, but downloading)

https://alcatelfirmware.com/alcatel-onetouch-pop-star-5022d

http://www.mediafire.com/file/lg6iip1k9ejgp8y/TCL_5022D_MT6580_5.1_OTA.zip

Today I stumbled across this site, which claims it has a modified TWRP 3.0.2. for the 5022D only !

It links to some russian forum, but the download is a 404 :

https://www.getdroidtips.com/twrp-recovery-alcatel-5022d/

And this site says it has Android 6.0 for it...but it leads nowhere...Im not even sure it had officially Android 6.0 :

https://blogthetech.com/flash-file-alcatel-one-touch-pop-star-5022d-firmware-download-stock-rom/

And here it a simialr one, offering Lineage 13 : Havent tried yet

https://www.getdroidtips.com/lineage-os-13-alcatel-5022d/

https://www.getdroidtips.com/lineage-os-13-alcatel-5022d/
[Miscellaneous Android Development] blakegriplingph:
Thanks for the firmware link mate, think I might make a TWRP for you over the weekend or when I'm not busy. ;)
[Miscellaneous Android Development] rallithil:
s92 mtk6580 s9 clone

any advice on converting img file to flash onto device
[Miscellaneous Android Development] a7chris:
Please will it work with this device?

Device info:

device verykoolS6005 cyprus ll

platform mt6580

android version 6.0

kernel linux version 3.18.19+

vendor mediatek

vendor arm

machine arm7l

resolution 1280x720

Thanks as I look forward for your support.
[Miscellaneous Android Development] blakegriplingph:
See if you could send me the boot and recovery images so I can port TWRP to your phone.
[Miscellaneous Android Development] Alvin50:
TWRP for Wiko Sunny

Hi,

I'm unsuccessfully trying to install TWRP 3.2.1 on a rooted Wiko Sunny Marshmallow Android 6.0 [46] kernel 3.18.19. The problem is that, after flashing, I have no touch working.

I know that this is a classical bug, but despite all my online research in the last month, I couldn't fix it.

I have tried various ways, form original update and from a Wiko Sunny-tailored Philz recovery, that works well.

Running on win 7-64 I made use of Android Kitchen 2.4 win32 and Carliv Image Kitchen 1.3 W64 to patch the recovery.img, as TWRP.apk's don't work on Sunny, like more recent similar apps, but despite all my efforts I always end stuck on a no touch TWRP display.

My sources are the official Wiko Sunny upgrade "Wiko Sunny V46.zip" with kernel 3.18.19 date 2017-07-21 09:59 recovery.img, 7336KB date 2017-07-15 16:31 as stock

and "PitchBlack V2.6 TWRP Recovery For H60 CrossPorted By Tanvir Ahmed.zip" recovery.img, 14648KB date 2018-04-22 19:25 as port.

Following a suggestion I found on line, after unpacking both images, I replaced port image files recovery.img-kernel and recovery.img-kernel_offset with the corresponding stock image ones.

Then, on ramdisk, I replaced fstab.mt6580 and ueventd.rc. It was told to also replace meta_init.modem.rc, meta_init.project.rc, meta_init.rc, but in my stock image they weren't and I left them as they were.

On myself, I also changed default.prop file with that of my stock, as most lines were related to the phone model it was ported before.

I then repacked this arranged port with Android Kitchen and flashed it with SP Flashtool 5.1.904.

Rebooting on recovery it appeared the trwp screen, but I couldn't wipe it.

Any hint?

Best regards
[Miscellaneous Android Development] blakegriplingph:
You mean you couldn't use the wipe feature? Try checking fstab and see if it's any different from what I used.
[Miscellaneous Android Development] alecxs:
If you can not swipe, you can use twrp from adb shell. If touchscreen works when you boot from pc, then you need to patch the kernel. Try

fastboot boot twrp.img
[Miscellaneous Android Development] Alvin50:
Thank you for your kind reply.

Can you please give me a link to your fstab?

Which line should exist there to have touch enabled?

TIA
[Miscellaneous Android Development] blakegriplingph:
Sorry, I kind of misunderstood you on that one. Thought you have a problem with mounting partitions and such.

Does touch work somewhat, i.e. you tap on one spot and it ends up on another, or does it refuse to work at all?
[Miscellaneous Android Development] Alvin50:
blocked at all...
[Miscellaneous Android Development] blakegriplingph:
I see. I haven't covered that yet, and from what I've read it's no small endeavour. An easier way out would be to port Philz or CWM instead, but you could also try what LosTigeros did in this thread if you're brave enough:

https://github.com/minimal-manifest-twrp/READ_ME_FIRST/issues/1
[Miscellaneous Android Development] Alvin50:
Yes, I already saw what you say, I already use Philz recovery, but want to install instead TWRP, as I see it's the most used in installing Lineage OS, that I would give a try.

I generally understand what Los Tigeros said, but am not so skilled to manage such a situation. Moreover, as Philz recovery works, I'm wandering if I could borrow some configuration from it. I know very little about Android, though I have used Linux for some time. Can you please point me to some reading that teaches how to configure its configuration files? I'm presently tampering with config.prop, but feel as an elephant in a crystals shop...

Best regards
[Miscellaneous Android Development] alecxs:
If you have working philz/cwm you can try to use this kernel for twrp (not sure if that works)
[Miscellaneous Android Development] Alvin50:
Do you mean the Philz kernel?

I'm just trying this way too, but, as per my latter messages, I need more knowledge than I presently have, I'll very happy if you can suggest me some reading on better understanding Android configuration files. Btw I have read the link you gave me, and quite agree. I'm mainly interested in understanding "howto" than in having all done by someone else, it's over one month that I'm searching all the day on the net. But, apart some "quick and dirty tricks", that mostly do not work at all, I never got a systematic approach to shed some light on system administration on Android. As I told, I have some experience on Linux dialects, but I see that I can apply it on Android only minimally, as I miss the general configuration picture and habits. Please, if you can, tell me where to look to understand at least the fstab and config lines, otherwise it's blind working.

Best regards
[Miscellaneous Android Development] alecxs:
i never used IDA Pro because it is payed software. i did not manage to fix it, i have no working solution. i still have stock recovery on MT6580. each time i do a backup i have to connect usb and boot twrp from fastboot with above command. i can assist with unpacking the kernel, and you can ask [MENTION=5935148]LosTigeros[/MENTION] for patching it with IDA Pro. But before you should try if touch is working with above method. If yes, then the problem is kernel related and can not be fixed by config. Maybe the kernel from Philz can be used for TWRP, we can assist for testing
[Miscellaneous Android Development] poetadastrevas:
Help

First of all I would like to congratulate you on the excellent work you have done! friend sorry for bothering you I have a very good replica of the Motorola Moto G6 plus. mtk 6580 Android 6.0.

I wonder if you could edit the twrp for me? Or teach me?
[Miscellaneous Android Development] Alvin50:
In the meantime I followed your suggestion, performing a lot of trials substituting other kernels in the TWRP porting instead of stock. None did solve the problem. The only that, to say it, performed better, was the one coming from the "[Hovatek] Philz for Wiko Sunny" used (recovery.img) on the "[Hovatek] Mediatek Auto TWRP Recovery Porter V1.4 by Team Hovatek", that gave any of the compatibility problems other recoveries did, for example changing the device name displayed when connected to the pc, or jumping into endless bootloop. Anyway, no touch yet.

This bunch of trials convinced me that the problem cause isn't kernel related, as I have the same in Philz (touch working) and in TWRP (touch not working), moreover being the TWRP recovery size larger than the Philz one. Without any other suggestion, I'm planning to perform an analysis from scratch of the differences between the two recoveries, as all other files are the same in both cases.

To be noted that, using the Philz recovery.img on TWRP recovery porter avoids the "DM_verity found" message that the original stock recovery had.

As a last note, on the trials made on PhilZ for Wiko Sunny recovery, I have found a problem in the backup/recovery: the backup seems to be performed correctly, and can be downloaded to PC, but when used to restore, when the restore is terminated and reboot is launched, Philz enters a bootloop that can be stopped only extracting the battery.

Best regards
[Miscellaneous Android Development] alecxs:
Thanks for your testing and report. just don't know the answer of one question (maybe you told already): is touch screen working when twrp is booted from fastboot (above method)? :)
[Miscellaneous Android Development] Alvin50:
"fastboot boot twrp.img"... Not sure I did what you requested...

I opened the console, and after connecting the phone typed

<adb devices>, receiving the correct answer

<adb reboot bootloader > to put the phone in fastboot mode

<fastboot boot recovery.img>, using my ported twrp recovery.img, the same I used with flashtools, if I have understood what you meant. I don't know of a twrp.img...

Were this right, it didn't work. The phone threw two lines acknowledging the tranfer at half of a black screen. Nothing else happened for about one minute. On this time the connection to the pc was missing and I could not send other commands. Then the phone rebooted on itself to normal state. I have tried this twice, first starting with a Philz recovery, secondly using the same twrp recovery installed with flashtools. If I'm missing anything, please redirect me where I can learn and better understand your suggestion.

Best regards
[Miscellaneous Android Development] alecxs:
exactly. the file name doesn't matter. but the question was about the "working" recovery - the first one you claim it is booting but you can not swipe...
[Miscellaneous Android Development] Alvin50:
Well... As I already told, no boot from fastboot, only a black screen with the transfer acknowledge...

I'm going to repeat the test using the PhilZ recovery, that, when installed, boots correctly, as for a blind test.
[Miscellaneous Android Development] alecxs:
ok then you have a new problem, if twrp was booting when flashed, then it must boot from fastboot also! flash back stock recovery, wipe cache, then try again
[Miscellaneous Android Development] Alvin50:
(continuation from my latter post): Philz recovery too behaves the same way!

I'm now going to test your current suggestion
[Miscellaneous Android Development] Alvin50:
No way...

At first I tried to only recovery the stock recovery. It did as before.

Then I reinstalled from scratch the kernel 3.18.19 official update through their official downloader and set again all the developer's crap... Then I again started adb devices, again tried fastboot boot recovery.img (Philz), same behaviour, at half the black screen the usual two lines :USB transferring... USB transmission OK... Then BOOT FAILED! Device is locked(OF COURSE!) ... Fastboot OEM unlock, then again fastboot boot recovery.img... Same two lines... then the phone starts to the reboot with the little robot "adjusting its internals" until it appears the normal configuration screen. If I force power off and then reboot holding vol+, I have the normal stock recovery. I shall say that, on the PC cmd terminal, after I gave the <fastboot boot recovery.img>, I have back a line saying "Sending 'boot.img'" ... [OKAY] [0.406s]

and a next one saying

"Booting " ... [OKAY] [0.047s]

"Finished. Total time :0.515s"

So, it seems to me that it is the recovery.img file itself that cannot be used for booting and though the boot aborts, to successively restart from the stock recovery.

That's all... :(
[Miscellaneous Android Development] alecxs:
thats curious, but i was wrong. after doing a research i found this may be expected behaviour. so nevermind.

if you want, you can use this app to make a request:

[V20] TwrpBuilder | Provides opportunity to have TWRP for your device
[Miscellaneous Android Development] Alvin50:
In the meantime I lurked around, learning a little more on adb and fastboot commands, and then experimenting on the phone.

I discovered that

fastboot flash recovery recovery.img works and changes the recovery on the phone, but

fastboot boot filename.img

fastboot reboot recovery

shall have a wrong entry point for their respective targets, as both fail to launch them and end with a normal high level boot after a timeout of about 60 s.

Now I'll look for your suggestions, thanks a lot for your patience ! :good:

edit:

fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img doesn't work for me: "-c unknown option" :(
[Miscellaneous Android Development] Zdendav:
Custom TWRP for Aligator S5065 Duo

Can someone please build a custom TWRP recovery image for me?

Phone - Aligator S5065 Duo, Android 7.0, kernel 3.18.35+

Additional Info:

BB Chip : mt6580

MS Board. : ALIGATORS5065

Build Time : Tue Jan 23 15:35:41 CST 2018

Krenel Ver. : 3.18.35+ (server@droi) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018

Android Ver. : 7.0

SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n

Custom Build Verno. : unknown

IMEI1 : xxx

IMEI2 : xxx

Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123

Bar code : 010901MT000000000000003891_155648

Recovery images: https://ulozto.net/!xdJM9EOid1zh/aligator-zip

The archive contains two files:

1) recovery.img - recovery image from my phone read back using SP Flash Tool and scatter file form a downloaded firmware, which I don't really know if it is correct

2) from_zip.img - recovery image from the mentioned downloaded firmware, which should be for my phone but I'm not sure

Thank you very much :)
[Miscellaneous Android Development] Matty1993:
Ill see what i can do for you :)
[Miscellaneous Android Development] blakegriplingph:
Thanks for the aid mate, I could've honestly done a quick port on my VPS, but looks like you beat me to the punch lol. :P
[Miscellaneous Android Development] Matty1993:
All good mate would have liked to help out more but with 8 projects on the go myself time is hard to find :) how did you got with it did you end up getting it to boot ?

---------- Post added at 07:05 AM ---------- Previous post was at 07:03 AM ----------

Link to recovery.imgs isnt working for me mate any chance you can upload somewhere else for me to download and ill have it up as soon as i can,

Just need your recovery.img mainly
[Miscellaneous Android Development] Zdendav:
No problem: https://webshare.cz/file/113Ia46f6e/aligator-zip
[Miscellaneous Android Development] Matty1993:
Ok try this may possibly be like 200kb to big but i cant slim it down anymore and this uses the same fs layout in fstabs so if it dosent boot ill have to build another with a smaller base to it hopefully not but :) this is twrp 3.2.3 which i built a while ago for my MT6737M ive just converted it for your 6580 boards fs layout.

https://drive.google.com/file/d/1Tq8228mGH5quWFNxP-fWykIbj-8OQKld/view?usp=drivesdk