yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Iftekhar.itu:
Someone help me. I'm begging :crying:
[OnePlus 3 Guides, News, & Discussion] RKBD:
Original twrp not working and I can't flash it via fastboot becouse my pc can't see my phone.

(when i booting to fastboot/bootloader its only show white led)
[OnePlus 3 Guides, News, & Discussion] marf28101995:
If your phones boots just install flashify and flash last modified twrp from eng.stk and it'll work

If your phone doesn't boot into the rom just check the mega unbrick thread here
[OnePlus 3 Guides, News, & Discussion] RKBD:
WOW flashify works great! THANKS!!! :victory:
[OnePlus 3 Guides, News, & Discussion] toto_vanir:
Why is it that i cant back up my rom? What is this error?
[Miscellaneous Android Development] blakegriplingph:
DISCLAIMER: I am not responsible if your device gets messed up royally, explodes or causes you to go nuts because you couldn't get this thing to work. I'm no expert coder either, but I am willing to fix things as much as I can.

I actually did this as there's practically no support whatsoever for that counterfeit phone of mine (yeah I know, you get what you pay for, but I bought this Galaxy S7 clone mostly for science). None of the existing porting tools work for the MT6580, and while manually porting an existing TWRP image to my phone works, it simply isn't cutting it as most of these recoveries are designed for a conventional framebuffer setup, not on devices with flipped LCDs. Fortunately there's this source tree for the Infinix Hot 2 TWRP port, and as the partition setup seems to be largely the same apart from differing capacities and the aforementioned LCD issue, this had to be done.

This should theoretically work on HDC S7 clones and a few others albeit with a few modifications, though I ported this from source with the Z6U030/GXQ6580 in mind. I know the latter isn't as widely known as the HDC model, let alone the original, but oh well...

SCREENSHOTS:

DOWNLOADS:

You may download the initial recovery release here: https://github.com/huckleberrypie/android_device_alps_z6u030_twrp/releases

The recovery should work best on this ROM, but may also work on other devices provided you replaced the kernel with the one that came with your device:

http://www.4shared.com/rar/6mMhYIk5ce/Galaxy_S7_mt6580_Z6U030HA_V105.html

And as for the sources, you can download the device tree here: https://github.com/huckleberrypie/android_device_alps_z6u030_twrp

Credits

My biggest props to the TeamWin team for making this little project of mine possible, as they're basically the ones who made this in the first place; I merely forked it to account for my device's configuration anyway. I'd also like to thank my pals over at American Girl Adult Collectors especially Amy and Molly, Arnee Libelo and Arturo of Driving Passion, and my buds Andy Vandjick and HardcoreHacker for the fun and expertise they shared. :D
[Miscellaneous Android Development] alinjeb:
plz rom

MT6580_alps_gxq6580_weg_l_Android5.1_Z6U030HA_V107En

---------- Post added at 02:23 PM ---------- Previous post was at 02:01 PM ----------

How to install twrp
[Miscellaneous Android Development] blakegriplingph:
Here are the /lib and /usr files that you requested.
[Miscellaneous Android Development] PAPalinskie:
hi. did USB Storage is working on yours? I tried to port another version of this recovery(Jemmeni's port) and seems to work fine except for error in mounting USB Storage. I need to work on that.
[Miscellaneous Android Development] blakegriplingph:
Yup, everything works apart from the lack of USB-OTG.
[Miscellaneous Android Development] PAPalinskie:
maybe i'll try your copy. maybe it work. and also, after screen time out, the screen was turned on again. how to fix that? i removed otg from mount points. that is the only solution if your kernel didn't support otg
[Miscellaneous Android Development] blakegriplingph:
Not sure what to do with the screen issue tbh; I just wanted a recovery for this rather obscure knockoff I use. Feel free to post your fork when you're done with it, aight?
[Miscellaneous Android Development] PAPalinskie:
i cant download the file at dev-host and it prompts as dangerous website warning instead. please upload to another file hosting site or attach here instead.
[Miscellaneous Android Development] blakegriplingph:
I posted it on my Github page - there are two releases, one for v105 and another for v106.
[Miscellaneous Android Development] PAPalinskie:
thanks brother.
[Miscellaneous Android Development] blakegriplingph:
No problem mate. ;)
[Miscellaneous Android Development] aksthecount:
custom recovery mt6580

Hey will it work on my swipe konnect plus mt6580
[Miscellaneous Android Development] blakegriplingph:
If your device has a similar partition scheme, just change the kernel and a few other settings, and it should work.
[Miscellaneous Android Development] kessaras:
i just test it on a g930f with a mt-6580 processor and it doesn't work
[Miscellaneous Android Development] reynanregodon:
need twrp scatter file

MT6580__samsung__A9__A9__5.1__Z8054_5.1_V2.9_20161017-193505. .twrp scatter file for this . .thanks
[Miscellaneous Android Development] PieNs7:
Bro I have a Yezz 5E3 with Chipset Mediatek MT6580M, can this work in it?
[Miscellaneous Android Development] blakegriplingph:
Try extracting the stock recovery off your phone, then open it using Carliv's IMG Kitchen. Then see if you could add the mount points from your phone to the recovery I compiled. Beware though, the recovery I made is for a flipped LCD so I am not sure if it will work without removing the flipped LCD flag and recompiling TWRP from source.
[Miscellaneous Android Development] phoenixpb:
hi

i have an archos 101 3g platinum with mt6580 (android nougat)

any chance to succeed to install twrp on it ? i already have a samsung a5 and an asus zenphone 2 rooted with twrp installed

adb shell is working and i have access to bootloader mode

and fastboot is working too, i only need a valid twrp.img

ty :)
[Miscellaneous Android Development] blakegriplingph:
I don't have access to a build environment atm, so I am not sure if I could do a TWRP source port for you. :/
[Miscellaneous Android Development] phoenixpb:
well thanks for your reply anyway :)

i continue digging ;)
[Miscellaneous Android Development] blakegriplingph:
NVRAM data must have been wiped off somehow, as that's one reason as to why your serial numbers have gone kaput.
[Miscellaneous Android Development] Zdendav:
"Ok try this may possibly be like 200kb to big" - meaning the recovery image, could this be the culprit?

I thought, if it was too big, I would get an error message?

But to me it seems, that the recovery partition is not near the NVRAM partition, I've attached the scatter from the downloaded zip.
[Miscellaneous Android Development] Matty1993:
Glad my TWRP is working well for you glad i used 3.2.3 as its got latest decryption features :)

Anyhow the extra 200kb wont do that to nvram if it was to big for the BOOTIMG partition fastboot would have stopped the flash before it began and given an error message of check the load image size is correct or not

Only thing i can think of is that you installed magisk before decrypting the encrytable storage and then trying to boot, as for orange state format /data in wipe menu it will unencrypt the storage.

As for getting your imei back you need to flash your stock firmware back and it will come back no problem ive had it dissapear on my MT6737M more times than i can count stock flash always brings it back, i noticed you mentioned about your pmt info being changed for the rom this means that your scatter is not absolute correct in all aspects,

Load each file individually to see if any will give you any errors on any partitions, dont format to change the pmt either youll be stuck on infinite bootlogo with little hope of fixing it more than likely,

And dont flash preloader, or lk with that scatter you will only make things worse rule number 1 with TWRP also always backup EFS/NVRAM before doing anything especially with magisk and all the patching it does.

hope this info helps :)
[Miscellaneous Android Development] Zdendav:
First, let me thank you for the recovery image :)

You confirmed, what I thought, that flashing the recovery image is not the culprit.

Could this be the culprit:

fastboot erase cache (it was in the tutorial, I was following)

******** Did you mean to fastboot format this ext4 partition?

Erasing 'cache' OKAY [ 0.109s]

Finished. Total time: 0.125s

After this I rebooted with this command:

fastboot reboot

Rebooting OKAY [ 0.000s]

Finished. Total time: 0.016s

Then came the orange status message, started booting and then it was stuck in the "POWERED BY android" logo.

By a long power button press I made it to reboot and this time I selected recovery by holding the volume button, it booted successfully to TWRP, so I used the opportunity a flashed magisk, I also selected the choice erase cache/dalvik during the magisk flashing.

I rebooted (from the TWRP menu) and again orange status (I thought it is because I unlocked the bootloader) and then stuck in the "POWERED BY android" logo.

I didn't encrypt anything - is it encrypted by default?

I have a full backup - readback in SP Flash tool using the scatter file from the downloaded zip. Flashing it back (without preloader) using the same scatter should bring my phone back, at least I think so ...

But I would like to know the culprit, because after flashing it back, I have to repeat the whole procedure and I want to avoid the error which caused this problem.
[Miscellaneous Android Development] Matty1993:
All good mate :) yeah orange state is because you unlocked bootloader and didnt factory reset and format /data before installing magisk and rebooting

Your device comes with out of the box encryption in your boot.img fstab your system path will be /dev/block/platform/mtk-msdc/******/msdc/by-name/system /system ext4 ro wait, "verify"

You will also more than likely have a .file called verity key in the Initrd,

Wiping cache wouldnt have caused it, its only because you didnt format the data once bootloader was unlocked so the verity key has been flagged as tampered and will not allow boot,

To clear this up boot to TWRP tap the wipe tab, then tap the format tab, type yes & format this will format the encryption from the device

Run a factory reset once the format of /data is complete to wipe magisk as it will have patched the boot.img and it should boot up no problems,

If it dosent its probably because theres magisk parts in boot.img still as magisk patches init.rc and a few other places so flash your stock boot.img with fastboot, then boot to TWRP, as soon as it boots go to wipe and format then run factory reset,

Reboot after to see if the orange state is cleared up as very rarely but sometimes magisk can cause issues on some MTK devices so dont flash the before reboot, once /data if formatted in TWRP it stays unencrypted until stock firmware is flashed back and re encrypted,

If you still get dramas with orange state let me know ill manually patch the dm-verity out of your boot.img for you
[Miscellaneous Android Development] Zdendav:
I did all the steps:

- wipe, format

- factory reset

hangs on the "POWERED BY android" logo, when trying to boot

- flashed boot.img in fastboot

- reboot

I was not fast enough to go onto TWRP, it tried to boot, hangs on the "POWERED BY android" logo

-reboot into TWRP

- wipe, format

- factory reset

still hangs on the "POWERED BY android" logo, when trying to boot

I can borrow exactly the same phone from a relative (fully working) - maybe I should do a full backup of it, then I'll have "clean" images of boot, recovery etc.

Meanwhile I did another full backup and this time I used WwR MTK v2.30 to create a correct scatter.

I attach both scatter files.
[Miscellaneous Android Development] osefstoo:
Hi when you have time can you try this boot+recovery+scatter : mega.nz/#!rZ8ngSDA!aV0yUC2CithDxqdkVIxcG7xlh_YNL9CGWk6FW5NA58E
[Miscellaneous Android Development] Zdendav:
Thank you, but the link asks for a decryption key ?

The problem is already solved (with great help of aIecxs), more info here: https://xdaforums.com/android/help/help-rooting-aligator-s5065-duo-mt6580-t3926132
[Miscellaneous Android Development] mbnshq:
Qmobile S8 Mt6580

Any here Who can tell me that How can i root this phone I have used this all soft but cant root this phone kingroot,kingoroot,iroot,360root,faramaroot please help me how i can root this device thanks
[Miscellaneous Android Development] blakegriplingph:
Sounds a little off-topic here, eh? But have you tried Magisk? At least with that you don't have to mess with the system partition, just boot.img.
[Miscellaneous Android Development] mbnshq:
bro i send you my Phone details as ss can you please guide me [IMG="Ss of About Phone"]https://hostr.co/Z71bvGiVzBy1[/IMG]

---------- Post added at 02:04 AM ---------- Previous post was at 02:02 AM ----------

bro can you please guide me [IMG="SS OF About Phone Qmobile S8"]https://hostr.co/Z71bvGiVzBy1[/IMG]

---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------

i have done twrp for mt6580 from sp flash tool but it was installed but mobile can't go in recovery mode

---------- Post added at 02:10 AM ---------- Previous post was at 02:07 AM ----------

[IMG="QMobile S8"]https://hostr.co/Ge3Eph7jI4v5[/IMG]
[Miscellaneous Android Development] blakegriplingph:
Mind if I refer you to this thread? Don't have the time and/or patience to do TWRP recoveries by request anymore, sorry:

https://xdaforums.com/android/general/unofficial-twrps-devices-source-code-t3833338
[Miscellaneous Android Development] htc_unenthusiast:
I recently received a counterfeit MT6580 clone of a K20 Pro. I am happy to struggle through the TWRP porting process for this guy. I cloned your repo but ran into build problems concerning the omni device not being immediately found. Are there any other steps I should try outside of your compilation bullets on github?

If you are detached from supporting this type of port I could definitely use a pointer to a TWRP porting guide. I am comfortable building Android/Lineage environments but TWRP builds are new to me.
[Miscellaneous Android Development] alecxs:
maybe a bit outdated but MT6580 is old device https://xdaforums.com/showthread.php?t=2798257 (you can use Generic TWRP v3.3.1-0 from Samad Segmane as base i have ported MT6580 myself too)
[Miscellaneous Android Development] htc_unenthusiast:
Thanks for the link. I looked into EasyMagic quite a bit but ran into the "Aborting: Img too big. Partitions overlap." I've attempted the fixes listed in the forum topic but nothing seems to ever change during the process and the tool does not provide much more than the same abort strings in a log.txt file.

When you say you used Samad Segmane as a base and ported do you mean I could clone that TWRP source down and follow this guide?
[Miscellaneous Android Development] alecxs:
with porting i mean just replace kernel file from your stock recovery, no need to compile from source
[Miscellaneous Android Development] htc_unenthusiast:
This bit of advice worked perfectly. I unpacked the twrp image "twrp-3-3-1-0-recovery-for-MT6580_cubot_king_kong.zip" and then replaced the existing zImage with the kernel I lifted from my device. I pulled the mkbootimg source and fixed the address offsets mentioned during the unpacking phase of my original recovery. After rebuilding the new TWRP image I flashed it down and it booted!

Now onto building a kernel image.
[Miscellaneous Android Development] alecxs:
just a hint AIK is very noob friendly one-klick-tool. all you need to do is disable Antivir (will give false heuristic for sudo.exe but you can trust osm0sis) download the zip, extract it run the unpackimg.bat
[Miscellaneous Android Development] htc_unenthusiast:
I wanted to test out using AIK but I use Linux 95% of the time for the build environment and the descriptions implied it was a Windows tool. Most of the random Android kernels I have experience with are a lot less painful to build in the Linux environment.

Unfortunately my clone's kernel tag, "ALPS.L1.MP6.V2.19_FLYCOM6580.WE.9.L_P1", doesn't seem to return any hits and there is no config built into the image. The closest thing I have found to kernel source are instructions on building the clone's kernel in a foreign language and this github repository. I have no idea how close or far off this might be for building but I think I can use TWRP to get /proc/last_kmsg out after a build attempt.
[Miscellaneous Android Development] alecxs:
just scroll down to bottom of OP and download AIK for linux.

why do you want to build the kernel?
[Miscellaneous Android Development] htc_unenthusiast:
I woke up to my mt6580 phone completely bricked. After some poking around it seems the preloader has gotten out of whack and lucky me I have backed up everything except that partition through dd commands. Is using another mt6580 preloader something I should try?
[Miscellaneous Android Development] alecxs:
i doubt you meant preloader, SP Flash Tool won't work without
[Miscellaneous Android Development] htc_unenthusiast:
You are correct. This was a false alarm. It seems the stars aligned on my multimeter being dead and my open kernel not properly charging the battery while running. As a result the battery was drained well below the point where even the bootloader could let me know what the issue was. The Chinese clone merely threw a massive error picture synonymous with corrupt preloader images or water-damaged phones.

I am not sure how to obtain the preloader from my device in case it is corrupted at a later point though. I will work on backing up everything I can in case something gets corrupted later.
[Miscellaneous Android Development] alecxs:
backup is useless because corrupt preloader is unrecoverable. it's not even on region EMMC_USER but has it's own region. therefore always uncheck preloader in SP Flash Tool before flashing any ROM. just don't touch it and nothing can harm it
[Miscellaneous Android Development] htc_unenthusiast:
Are you sure the preloader is unrecoverable? Many informative videos and writeups I pulled yesterday suggested using META mode to re-write the preloader area through SP Flash Tool. I confirmed this mode by removing the battery, holding volume up, and then plugging in the usb cable. In Linux it enumerates as an MT USB device.

I agree it should be left alone. Unfortunately when there is a dead battery present the screen flashes a "plug out usb" error message which is not a good indicator of state. Most search results online relate that error message to a corrupt preloader.
[Miscellaneous Android Development] kirichen:
Try flash fix preloader first. then flash one of the preloaders (MT6580) . If there is support of your chip of memory in the preloader. you can make a memory test in SP flash tool ( uncheck all items exept upper)
[Miscellaneous Android Development] QMC:
Hi, I have DuoDuogo P8 tablet (MT6580) do you think this could work?
[Miscellaneous Android Development] blakegriplingph:
It should, so as long as it's built similarly to the one in the code.
[Miscellaneous Android Development] QMC:
Hello!

Which code would you be referring to? (sorry I'm super new to the world of flashing and root)

This is my tablet information:

Andiord version 9.0

Kernel Version:

3.18.79

anything else would I need to include?
[Miscellaneous Android Development] blakegriplingph:
It could be built differently from the codebase I used, so I honestly have some doubts on whether my recovery will work or not.
[Miscellaneous Android Development] jackbauer:
Hello, can you shed a light on this

https://xdaforums.com/t/need-help-t...ts-stock-rom-or-at-least-a-custom-rom.4508783 ???

I tried many different roms, I even tried flashing only the recovery and boot images, no success.
[Miscellaneous Android Development] kirichen:
try to hold vol - ( or vol + or power button on some devices) and connect your phone to computer.... release the button after the computer find the phone and the flashing starts
[Miscellaneous Android Development] kirichen:
1) change the usb cable, change the usb port on computer

2) low charge of battery, connect your phone to the charge device for few hours

3) may be the hardware problem with flash memory in phone

4) use fresh , new version of SPFlashtool
[Miscellaneous Android Development] jackbauer:
Before using the preloader fix, I've flashed the phone just fine and it was both with a newer and an older version of SP Flash Tools, so it's not the cable and I'm using the newest version SP Flash Tools, which currently is SP_Flash_Tool_v5.1924_Win. This last error started after flashing the rom together with the preloader fix that you've provided.
[Miscellaneous Android Development] kirichen:
I don't think that the errror is due to the preloader fix. Preloader fix is just universal preloader which support a lot of memory chips, I used it succesfully since 2019 5 or 6 times. I know tens of users who used the preloader fix for clones( MT 6580) and had no your type of error. Usually I flash only the preloader fix and the next step was a firmware flashing. I used it when I receive the error 4032
[Miscellaneous Android Development] jackbauer:
SP FL wasn't allowing me to flash only the preloader fix, so I flashed it altogether with the entire ROM, then this error came when I tried to flash again.

PS: I forgot to tell, it's throwing a 16 bits error now.
[Miscellaneous Android Development] jackbauer:
So?
[Miscellaneous Android Development] Peter12205:
Some way to port twrp to a Chinese cell phone called inco eco_s with android 8.1 go and that works on android 10 gsi. it has the same mediatek chip I would love to create a recovery for that cell phone in my free time.
[Miscellaneous Android Development] blakegriplingph:
Sorry about that. I might try to edit the one I forked this recovery from though, assuming you can send me the stock firmware from your phone so I can look into the recovery image.
[Miscellaneous Android Development] phoenixpb:
Well stock rom is available here :)

https://www.needrom.com/download/archos-101-platinum-3g/
[Miscellaneous Android Development] glen.ricky:
Hi,

Recently I bought a fake phone with MT-6580 and also with a flipped screen. Would the specs matters? as mine has 512MB of RAM and only 2GB storage? thanks
[Miscellaneous Android Development] Tantarado:
Hi Guys,

I have a clone Samsung S7 Pro (SM-G930F MT-6580), will it work for the unit?

I have used CPU-Z into it and it describes the phone as ALPS Brand, 4k plus RAM and 64Plus internal memory.

Thanks in advance!

Cheers!

p.s. the reason i wanted to do this is to make the phone's response time faster, it lags most time and if i hit a quick back button - it stalls the phone. also, i wanted to have the phone rooted so i could remove the apps i know i will never be using that always processes.

Cheers!
[Miscellaneous Android Development] blakegriplingph:
Can you take some pics of the stock recovery please? Well since there are a number of clones which are mutually incompatible with each other and all. If it's a GXQ6580 clone like mine it would work, but as I said I need to get more about your device's internals first.
[Miscellaneous Android Development] Tantarado:
how do i do that? and where can i find this stock recovery? is it the one that appear every time i press the up vol + power + home button all at the same time?

Cheers!
[Miscellaneous Android Development] blakegriplingph:
Yup, that's the one I am referring to. Just take a pic of it so I could see the internal build number.
[Miscellaneous Android Development] Tantarado:
Here's what you requested.
[Miscellaneous Android Development] blakegriplingph:
From the looks of it, it's a different model from mine then. I *might* do a port if you could dump the recovery image, but I don't have a Linux distro atm so no guarantees.