Database Info

For Devs: A new possible way to root the T-Mobile variant???!!!!!

https://threatpost.com/another-linux...access/137800/

Would be awesome if that works

I played around a little and this happened...
https://photos.app.goo.gl/TiEXrdKmWydRM8RZ9

S8ntsHaz3 said:
I played around a little and this happened...
https://photos.app.goo.gl/TiEXrdKmWydRM8RZ9
Click to expand...
Click to collapse
Unlock critical is allowed and already known thing but this is for flashing bootloader and stuff. It doesn't help us at all for now.

There are already many rooted tmobile g7 sold in China.

I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html

curster said:
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
Click to expand...
Click to collapse
anyone tried it yet?

kasuma_asuma said:
anyone tried it yet?
Click to expand...
Click to collapse
So it's a fake post for one (actually not exactly fake I would say more clickbait then anything) two I believe the T-Mobile version is the G710TM, three we have a gimped fastboot as in it doesn't work at all. And four I think our only option is something to do with LAF
---------- Post added at 11:22 AM ---------- Previous post was at 11:21 AM ----------
curster said:
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
Click to expand...
Click to collapse
No it's not the case see my previous answer

We should be able to get around this gimped fastboot by incorperating that boot.img from the EM varient into an "update" once the phone is cross flashed. To 710EM it will have "adb update" command (it will also think the update is for itself since the firmware matches what were flashing we can put this into a flashable.zip (im like 75% sure this is how its done). Then use the command "adb update boot /path to patch boot/" alternatively could we incorperate our patched boot.img into a kdz and flash it with a patched LGup? Once the phone is rooted with magisk we could use the twrp app to flash twrp and fastboot commands wont be extremely relevant
The problem is, how to remove or get around the correct oem unlock allowed verification system. Unpacking a .img and editing is not a problem, i am just not exactly sure what to edit.

alecthenice said:
We should be able to get around this gimped fastboot by incorperating that boot.img from the EM varient into an "update" once the phone is cross flashed. To 710EM it will have "adb update" command (it will also think the update is for itself since the firmware matches what were flashing we can put this into a flashable.zip (im like 75% sure this is how its done). Then use the command "adb update boot /path to patch boot/" alternatively could we incorperate our patched boot.img into a kdz and flash it with a patched LGup? Once the phone is rooted with magisk we could use the twrp app to flash twrp and fastboot commands wont be extremely relevant
The problem is, how to remove or get around the correct oem unlock allowed verification system. Unpacking a .img and editing is not a problem, i am just not exactly sure what to edit.
Click to expand...
Click to collapse
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)

LameMonster82 said:
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
Click to expand...
Click to collapse
So for dm-verify I know how to manually get around that and the patch thats floating around via flashable.zip. What do we need to extract from the .up or .kdz? Im pretty sure there is a full kdz dump for the 710EM in a thread I read through just last night? I really believe the only obstacle we have is making the bootloader unlock through a command line independent of the official unlock code. This should be able to be acheived by editing that in a way to where it doesnt check much like dm-verity. Then you can flash your (patched by deletion) boot.img run fastboot oem unlock ( btw did you know that "fastboot oem flashing unlock critical works) **could run that then flash an unlock.bin, then fastboot oem unlock unlock.bin** I am working with a 710pm varient. And am speaking from experience rooting the v30 ls version currently using G7 as daily driver
This leaves me thinking that we have lots of wiggle room here (also leaves me thinking how weird LG is for having a lot of variation within G7)

LameMonster82 said:
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
Click to expand...
Click to collapse
I use LG Firmware Extract to get the DLL's out, the problem is theres no firmware yet for the LG G7 Sprint version:
View attachment 4667707

GROOVYJOSHCLARK said:
I use LG Firmware Extract to get the DLL's out, the problem is theres no firmware yet for the LG G7 Sprint version:
Click to expand...
Click to collapse
Amazingly this week I was able to extract everything from any kdz file. The problem is that repacking requires certificate and we don't have it.

LameMonster82 said:
Amazingly this week I was able to extract everything from any kdz file. The problem is that repacking requires certificate and we don't have it.
Click to expand...
Click to collapse
Yes but we will figure it out eventually. I'm on Sprint myself and actively trying to figure out the LG cross flashing issue.

GROOVYJOSHCLARK said:
Yes but we will figure it out eventually. I'm on Sprint myself and actively trying to figure out the LG cross flashing issue.
Click to expand...
Click to collapse
So, do you want to cross flash or just the Sprint firmware

LameMonster82 said:
So, do you want to cross flash or just the Sprint firmware
Click to expand...
Click to collapse
There is no cross flashing on the G7 (or V35 or V40) unless you want a brick. LG got smart after the V30 WTF exploit and now uses a different RSA cert for every model.
Don't take my word for it, please feel free to try -- make sure you have insurance
-- Brian

runningnak3d said:
There is no cross flashing on the G7 (or V35 or V40) unless you want a brick. LG got smart after the V30 WTF exploit and now uses a different RSA cert for every model.
Don't take my word for it, please feel free to try -- make sure you have insurance
-- Brian
Click to expand...
Click to collapse
Yes but we will figure it out eventually so we can flash the EM firmware and unlock the bootloader then root and install TWRP then AOSP. I am waiting on my octoplus box to arrive then I'll be testing cross flashing for others to sort out what's needed.

GROOVYJOSHCLARK said:
Yes but we will figure it out eventually so we can flash the EM firmware and unlock the bootloader then root and install TWRP then AOSP. I am waiting on my octoplus box to arrive then I'll be testing cross flashing for others to sort out what's needed.
Click to expand...
Click to collapse
Awesome! But octoplus will not allow you to cross flashing, right?

any news on this ? would love to change my T-mobile software. and get the fingerprint to work for that matter

Question the boot.img file was downloaded to my phone to root it and then it has no identifiable imei number

the boot.img file was loaded into my phone in order to get root after that it could not detect imei numbers. Although they are in fastboot. I tried many different firmwares for this phone, but there is no result! I ask for your help. I was left without communication (sorry for not being very clear. I don't understand Russian and don't understand English at all, that's why I'm writing through a translator

The first thing you want to do is STOP FLASHING random images. It sounds like you are going to cause more harm than good if you keep going.
Figure out which firmware you started on (WW, EU, CN) and get the raw firmware for it. Follow the instructions to flash the raw firmware.
If that doesn't work, then you may need to contact the manufacturer, BUT at least you will be restored to stock. I cannot promise they will help you, but it sounds like you did more than flash a boot image. The IMEI is not stored there.

twistedumbrella said:
The first thing you want to do is STOP FLASHING random images. It sounds like you are going to cause more harm than good if you keep going.
Figure out which firmware you started on (WW, EU, CN) and get the raw firmware for it. Follow the instructions to flash the raw firmware.
If that doesn't work, then you may need to contact the manufacturer, BUT at least you will be restored to stock. I cannot promise they will help you, but it sounds like you did more than flash a boot image. The IMEI is not stored there.
Click to expand...
Click to collapse
Tell me where you can find the pure CN firmware? This phone was presented to me in this form already. And they told what happened to him. I doubt that ASUS support will help me, since in addition to everything according to the owner, the EMMCCDL_GUI utility was used. So I ask for help from knowledgeable people here.

And most importantly, what to flash and how?

Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com

twistedumbrella said:
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
did not help(

What? So no one will help ???

Return the phone or wait until the methods exist.
Those are the only quick answers left.

twistedumbrella said:
Return the phone or wait until the methods exist.
Those are the only quick answers left.
Click to expand...
Click to collapse
It was opened. This is not an option either

If you purchased it used and the seller refused a return, it sounds like they were trying to recover what they could by selling their problem to someone else. It's likely they knew there wasn't a self-service fix right now.
Just to be clear, what you need is a low-level EDL restore. As it stands, one of the files required is not available to the public. If you have a local repair shop, they may be able to do it (and will likely charge a fee).
Do NOT pay someone over the internet. It CANNOT be done remotely.

Question Raw file for 5s/5s pro?

Dose anyone have the Raw firmware for Asus rog phone 5s or 5s Pro?

Same question here..
Does anyone have? My 5s pro is down T_T
Thanks anyway

wcx19911123 said:
Same question here..
Does anyone have? My 5s pro is down T_T
Thanks anyway
Click to expand...
Click to collapse
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
This thread by johnny886 has the entire firmware files. Follow the video in the first post so you minimize any issues.
You will need to download a few drivers.
I also posted some stuff related to any issues on a few of my threads and on johnny886 thread.
I hard bricked my phone, and managed to fix my phone only using his files.
Other people posted firmware threads as well but it isn't complete like this one is. The others are missing major components to actually fix the phone. The other threads also do not have software to save your phone imei, which if you don't save and you try to install firmware on your phone. You could end up permabricking your phone and no one can fix it at that point. This is because the phone doesn't have a serial or a lot of identifying information, so it will refuse to load the firmware.

Donlavon1 said:
Dose anyone have the Raw firmware for Asus rog phone 5s or 5s Pro?
Click to expand...
Click to collapse
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Trash.umu said:
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
This thread by johnny886 has the entire firmware files. Follow the video in the first post so you minimize any issues.
You will need to download a few drivers.
I also posted some stuff related to any issues on a few of my threads and on johnny886 thread.
I hard bricked my phone, and managed to fix my phone only using his files.
Other people posted firmware threads as well but it isn't complete like this one is. The others are missing major components to actually fix the phone. The other threads also do not have software to save your phone imei, which if you don't save and you try to install firmware on your phone. You could end up permabricking your phone and no one can fix it at that point. This is because the phone doesn't have a serial or a lot of identifying information, so it will refuse to load the firmware.
Click to expand...
Click to collapse
No firmware package is incomplete, but some of the older EDL restore packages don't have all the files to perform a full restore. There is a difference between flashing raw firmware and performing an EDL restore.
Raw firmware is like reinstalling Windows. It's a factory reset with the factory image. This fixes most OS issues, such as deleting important files.
EDL restore is like flashing the BIOS. It formats all of the partitions and does a clean install as if the phone never had any firmware at all.
It's important to know the difference, since flashing raw firmware is far less dangerous and much easier. It might be worth asking what the problem is before jumping right to EDL restore.

<Moderator Edit>: Post edited. I will PM you as to why shortly.
My rog phone 5s pro was hardbrick because I Flash the wrong firmware like rog phone 5 raw file.. then my phone detect on my pc only on edl mode qualcomm not turning on.. after few hours of research I revive my phone if someone softbrick rog phone 5 series.

Question Pixel 7 pro system firmware needed

I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.

Doesn't exist. Ideally, you would dump the firmware yourself from the phone.

Now that the phone is released, stock images should be available soon here:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

kobiandy said:
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Click to expand...
Click to collapse
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?

Morgrain said:
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Click to expand...
Click to collapse
No it was never locked to begin with. Does this mean even original stock firmware( when released) won't work?

kobiandy said:
Does this mean even original stock firmware( when released) won't work?
Click to expand...
Click to collapse
That is highly likely, but don't let me stop you from trying. Maybe you will have success. Also keep your eyes out for the Android Flash tool or the Pixel Repair tool, once Google updates them for the P7 Pro. Big companies usually not have all the tools interconnected, so chances are that the Repair tool won't check for blacklisted hardware IDs, it's just important that under no circumstances you may connect to the Internet with that thing, IF you manage to get it running and as long as it runs stock.

Need help to find out which phone is this and its stock rom (or at least a custom rom)

I've been looking for a way to "fix" this phone for almost 1 week now. I've disassembled it and managed to note an alphanumeric sequence on its motherboard which I believe is its model.
First things first: this phone's touch screen is not working, but I've checked the motherboard and it seems just fine, which led me to believe there's a problem with the firmware, then I've checked the firmware using recovery mode and it seemed odd, it seemed like the phone isn't using its original firmware.
Here's the info that I found using recovery mode:
SW Ver.
alps-mp-m0.mp1-V2.39 _magc6580.we.c.m_P32
Custom Build Veno. :
V207IF3_QHD1200_M_V1.0_2_16_20200808_1758_V1.0.5_B125_HUAX_V50C3_WELCOME_S20_PLUS_PRO_DS
I'm attaching pictures too.
This phone was handed to me, so I have no reference at all. I've searched everywhere I could online and I couldn't find this model for sale, I couldn't even find a phone that looks exactly like this, but some were pretty close, like the Huawei P40 and the S20+ Pro clone, but after searching for that alphanumeric sequence, which I believe it's the actual model number, I've come across the WOLKI WS680, but I couldn't find its firmware for downloading.
FLASHING A FLASHY PHONE​
I've downloaded and tried to flash the ROM MT6580__MFT__I7__I7__6.0__alps-mp-m0.mp1-V2.39_magc6580.we.c.m_P21, which seems to be the same that was in the phone, but the phone didn't turn on anymore after this (I believe it bricked). I didn't take backup before doing this, please don't blame me, It's been many years since I've done this kind of thing on a Chinese phone.
Any other rom that I tried just throws a DRAM error in SP Flash Tools, I'm also not able to format the phone (it also throws an error).
The error:
ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
WHAT I AM LOOKING FOR:​1 - I need to find the right ROM firmware for this phone, please somebody give me a download link. A custom rom would be good too.
2 - I need to know which exactly is this phone's brand and model (because I need to know its hardware specs).
Please help me find at least the firmware.

Anyone?

Maybe it's the
Leioa Vapio Summilux (Mate 33 Pro) - Black Smart Phone 2021​
but I don't know

xXx yYy said:
Maybe it's the
Leioa Vapio Summilux (Mate 33 Pro) - Black Smart Phone 2021​
but I don't know
Click to expand...
Click to collapse
got the firmware with scatter file?

Just as it says on the sticker, this phone is a Leioa Vapio summlux h1. It looks like some kind of Chinese clone or something.

Cool, but how can I find its firmware? The phone here is bricked.

jackbauer said:
Cool, but how can I find its firmware? The phone here is bricked.
Click to expand...
Click to collapse
I don't know and that's the problem with exotic phones. Good luck with that.

This kind of copied / rebranded phones can also be found outside of China. So, whenever you buy a smartphone be sure to reach an authorized seller or take a closer look at the phone’s aspects.
My recommendation: Ask phone's seller for help.

"This phone was handed to me, so I have no reference at all."
There's nothing I can do about talking to a seller. I'm here just asking for a rom that might work with this mediatek, it doesn't mean that it needs to be the Stock ROM.

Can anyone tell me a workaround for this? it doesn't need to be the stock rom.

these fake phones are low end trash devices running android 6 no LTE. you bricked working ROM for no reason so what?
https://www.gem-flash.com/vb/threads/837178
https://androidfilehost.com/?fid=673791459329059944
https://androidhost.ru/Xe8

aIecxs said:
these fake phones are low end trash devices running android 6 no LTE. you bricked working ROM for no reason so what?
https://www.gem-flash.com/vb/threads/837178
https://androidfilehost.com/?fid=673791459329059944
https://androidhost.ru/Xe8
Click to expand...
Click to collapse
You really want to know why I'm still insisting in this phone? It's a pride thing. Some douche needs to see this working. That's why. After I "fix" this, I'll take some photos of it, send them to the person and then I'll just get rid of it.

What's the password for MT6580__Q_MOBILE__V15_PRO__V15_PRO__6.0__ALPS-MP-M0.MP1-V2.39_MAGC6580.WE.C.M_P30.RAR? I'm not finding it in the list.

https://drive.google.com/uc?id=1kjQZT6d8Yz2UBEERQnE68ZEm5h7uSLg7&export=download
You should try downloading this.
jackbauer said:
SW Ver.
alps-mp-m0.mp1-V2.39 _magc6580.we.c.m_P32
Click to expand...
Click to collapse
This is what I found from the sw ver.

notnoelchannel said:
https://drive.google.com/uc?id=1kjQZT6d8Yz2UBEERQnE68ZEm5h7uSLg7&export=download
You should try downloading this.
This is what I found from the sw ver.
Click to expand...
Click to collapse
This one is password protected.

sorry, seems one must pay $2 for password. however, I doubt any of this ROMs will work...
https://mafirmware.blogspot.com/2019/12/mt6580qmobilev15prov15pro60alps-mp.html

maybe this one will work?
Pineapple 6.0 alps-mp-m0.mp1-V2.39 Stock Firmware ROM (Flash File)
Download the official Pineapple 6.0 alps-mp-m0.mp1-V2.39 Stock Firmware ROM (Flash File) for your Unknown Mobile. We also provide all other Unknown Stock Firmware for free.
firmwarefile.com

notnoelchannel said:
maybe this one will work?
Pineapple 6.0 alps-mp-m0.mp1-V2.39 Stock Firmware ROM (Flash File)
Download the official Pineapple 6.0 alps-mp-m0.mp1-V2.39 Stock Firmware ROM (Flash File) for your Unknown Mobile. We also provide all other Unknown Stock Firmware for free.
firmwarefile.com
Click to expand...
Click to collapse
Download quota exceeded.
Please upload that file somewhere else. Google Drive is as*.

jackbauer said:
Download quota exceeded.
Please upload that file somewhere else. Google Drive is as*.
Click to expand...
Click to collapse
I'll mirror it to you (edit: i can't)

Here's another. they aren't password protected:
MT6580_____6.0__alps-mp-m0.mp1-V2.39_nb6580.we.m.7z | by GSM iNFO for Galaxy S6 Edge+
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
MT6580__X30__X30__X30__6.0__alps-mp-m0.mp1-V2.34_droi6580.weg.m_P29 Without Password - GSM-Forum
Download: Oppo Clone R11 Stock ROM Flash File. Oppo Clone R11 Flash File Without Password MT6580__X30__X30__X30__6.0__alps-mp-m0.mp1-V2.34_droi6580.weg
forum.gsmhosting.com