Related
Here is a link to STOCK firmware images for the Oppo A5s
Link: https://mega.nz/#F!pkpwhKIS!2sZ7JA5IG1XFQhyBMvDMuQ
If anyone is an expert. They could port a working twrp for possible opening of the bootloader and rooting.
I can provide the whole stock firmware images of this device in the future as I have limited disk space.
Hi, I can make twrp for this phone can you unlock bootloader and test it for me?
I can also make a twrp for this. I just shared it if anyone wants to do it on their own. I'm not into experimenting my phone anymore
share the file here and tell me how to do it,
I will try directly in my phone
Any luck? Any update guys?
Hey Guys, This is Aryan (TechyMinati @An ASP) as We know, These days everyone is keen to install Custom ROMs & Recovery in their Devices, Sometimes the thing goes well and sometimes the devices HardBricks. Here we are basically talking about the Xiaomi Mediatek Devices & Their Fate.
Mediatek Devices have Download Mode or DA Mode, Which allows you to revive your devices even if it is hardbricked, So whats the error now ?
The case with Xiaomi Mediatek devices is entirely different, you cant flash your device without Mi Authorized Account or can be simply called Server Side SLA(Serial Link Authorization)
Lets Take a Deep Insight into working of this Mi Authorized Account
For those unaware, SP Flash Tools, short for SmartPhone Flash Tool is a tool that MediaTek distributes that allows flashing the OEM firmware back onto a MediaTek device, in case something goes wrong. Now, in this “hard-brick” condition, the device is able to enter the BROM “emergency-download” mode (EDL, for short). If you remember, BROM may implement security to prevent unauthorized modification to the device.
Most manufacturers implement very basic security; there are 2 main BROM security implementations:
SLA (Serial Link Authorization)
DAA (Download Agent Authorization)
A MediaTek device can have none, either or both. Usually a slightly modified version of the flash tool which contains a few secrets is enough to let anyone re-flash the device. Let’s quickly understand what these implementations are like and how they differ.
BROM exposes UART to communicate. In both cases, the device will generate a few random bytes which must be “decrypted” or simply processed to create a new string. If BROM validates the string, it’ll allow the host to issue many more instructions without errors, such as jumping to addresses or writing partitions. The difference between the two is, in SLA, BootROM performs the checks and in DAA, Download Agent (DA) performs the check. Download Agent is loaded by SP Flash Tool. On devices that implement SLA, you cannot load a DA file without completing the SLA challenge. On devices that implement DAA, the challenge is done by DA and a modified DA file is enough to bypass security (That is, assuming you manage to reverse things or have the BSP).
Whats Worse Now? Xiaomi Mediatek Devices Have SLA !
Xiaomi has special accounts (called Mi Authorized Accounts) that are given to service centers for repairing devices. These accounts are capable of requesting Authorization tokens to unlock BROM download on MediaTek devices (and other EDL equivalents for Qualcomm devices). Something that can be very easily fixed by a consumer and/or developer, is locked to service centers.
So How This Mi Authorized Account Work? How data exchange takes place to allow BROM to Proceed ?
Well with Mi Auth, The device generates 16 bytes of data and sends it to the server. The server checks if your account has authorization and returns 256 bytes of data. If the data is correct, BROM continues. Else it traps itself in an infinite loop, until it times-out due to no-command and reboots.
Our Beloved Friend @Agent_fabulous created a python script that imitates the same way the Mi Auth Works, But Sadly it doesnt work as of now. Your Can find the script here
A Ray Of Hope : Modified Preloader
Back in March 2020, When I got my Redmi 6A Bricked , I tried alot of ways to revive it , I ended up paying some bucks to shady guys on internet who revived my device via Mi Auth Over Remote Session Using TeamViewer. And More Sad part is most Xiaomi Service Centers don't know a single thing about Mi Auth, All they know is to replace motherboard LOL. Ah Noobs Everywhere.
After I revived my device , I began to think of making Antibrick that begonia already have ( Ah again thanks to @Agent_fabulous for his works) , Meanwhile, I found out the factory firmware for Redmi 6 & 6A., You see, every OEM receives a BSP for their platform of choice from the SoC manufacturer. Usually, the OEM will boot a clean version of this BSP on their hardware to get everything working, before the product team can start porting out the “skin” of Android that they advertise and ship their products with. This clean-version of the BSP build is often referred to as the “final factory firmware”.
We have factory firmware now ! Whats Next ?
After getting the factory rom, The thing you need to do first is boot that ROM safely in your devices (Note : If your phone is already hardbricked than this factory fw doesnt help, its for creating antibricks and other stuffs. ).
-You can boot your device to fastboot and fastboot flash all partitions from factory ROM
-after that turn off the device, attach it to your PC or Linux Machine)
-And Run dmesg on your device
-And Let device automatically power On.
Now if you see it register a cdc_acm device with description as MT65XX Preloader, Man You have Succeeded & Can flash without Mi Auth on that preloader.
After that try installing Any Other ROM, Say MemeUi 11, (Remember Dont Flash MIUI Preloader), Now extract Preloader & You Can Make a Flashable Zip xD. As Long as You are on that preloader, You have no worries , You can flash any ROM via SP Flash tool without any fancy auth.
Hope You Understood that What is Mi Auth & How it works on Mediatek Devices & How you can prepare a AntiBrick.
Press Thanks On this Thread xD
Credits:-
@Agent_fabulous (Mr. Kshitij ) for making me aware about Antibrick and How to prepare it. [He is developer from begonia Who Implemented VoLTE on Mediatek Chipset Based Device Redmi Note 8Pro ; He made antibrick too ; His Article Here (from which I've learned alot about Mi Auth)]
@An ASP (Aryan Sinha ; also known as TechyMinati) Making this article & Gathering info about Mi Auth .
I recommend you to give this XDA article a read, too!
We have factory firmware now ! Whats Next ?
After getting the factory rom, The thing you need to do first is boot that ROM safely in your devices (Note : If your phone is already hardbricked than this factory fw doesnt help, its for creating antibricks and other stuffs. ).
-You can boot your device to fastboot and fastboot flash all partitions from factory ROM
-after that turn off the device, attach it to your PC or Linux Machine)
-And Run dmesg on your device
-And Let device automatically power On.
Now if you see it register a cdc_acm device with description as MT65XX Preloader, Man You have Succeeded & Can flash without Mi Auth on that preloader.
After that try installing Any Other ROM, Say MemeUi 11, (Remember Dont Flash MIUI Preloader), Now extract Preloader & You Can Make a Flashable Zip xD. As Long as You are on that preloader, You have no worries , You can flash any ROM via SP Flash tool without any fancy auth
Click to expand...
Click to collapse
Can you please make an "easy-to-understand" step-by-step guide for noob like me? With download link of course xD, like this one https://forum.xda-developers.com/redmi-note-8-pro/development/rom-crdroid-6-x-t4124805/amp/
Thanks
adi4ntn said:
Can you please make an "easy-to-understand" step-by-step guide for noob like me? With download link of course xD, like this one https://forum.xda-developers.com/redmi-note-8-pro/development/rom-crdroid-6-x-t4124805/amp/
Thanks
Click to expand...
Click to collapse
Hey There, Here I'm talking about all Mediatek Devices, Creating Antibrick for all devices is a tough task. And I cannot do it alone. Show this guide to your respective device related developer. He will understand it for sure. Thanks
TechyMinati said:
Hey Guys, This is Aryan (TechyMinati @An ASP) as We know, These days everyone is keen to install Custom ROMs & Recovery in their Devices, Sometimes the thing goes well and sometimes the devices HardBricks. Here we are basically talking about the Xiaomi Mediatek Devices & Their Fate.
Mediatek Devices have Download Mode or DA Mode, Which allows you to revive your devices even if it is hardbricked, So whats the error now ?
The case with Xiaomi Mediatek devices is entirely different, you cant flash your device without Mi Authorized Account or can be simply called Server Side SLA(Serial Link Authorization)
Lets Take a Deep Insight into working of this Mi Authorized Account
For those unaware, SP Flash Tools, short for SmartPhone Flash Tool is a tool that MediaTek distributes that allows flashing the OEM firmware back onto a MediaTek device, in case something goes wrong. Now, in this “hard-brick” condition, the device is able to enter the BROM “emergency-download” mode (EDL, for short). If you remember, BROM may implement security to prevent unauthorized modification to the device.
Most manufacturers implement very basic security; there are 2 main BROM security implementations:
SLA (Serial Link Authorization)
DAA (Download Agent Authorization)
A MediaTek device can have none, either or both. Usually a slightly modified version of the flash tool which contains a few secrets is enough to let anyone re-flash the device. Let’s quickly understand what these implementations are like and how they differ.
BROM exposes UART to communicate. In both cases, the device will generate a few random bytes which must be “decrypted” or simply processed to create a new string. If BROM validates the string, it’ll allow the host to issue many more instructions without errors, such as jumping to addresses or writing partitions. The difference between the two is, in SLA, BootROM performs the checks and in DAA, Download Agent (DA) performs the check. Download Agent is loaded by SP Flash Tool. On devices that implement SLA, you cannot load a DA file without completing the SLA challenge. On devices that implement DAA, the challenge is done by DA and a modified DA file is enough to bypass security (That is, assuming you manage to reverse things or have the BSP).
Whats Worse Now? Xiaomi Mediatek Devices Have SLA !
Xiaomi has special accounts (called Mi Authorized Accounts) that are given to service centers for repairing devices. These accounts are capable of requesting Authorization tokens to unlock BROM download on MediaTek devices (and other EDL equivalents for Qualcomm devices). Something that can be very easily fixed by a consumer and/or developer, is locked to service centers.
So How This Mi Authorized Account Work? How data exchange takes place to allow BROM to Proceed ?
Well with Mi Auth, The device generates 16 bytes of data and sends it to the server. The server checks if your account has authorization and returns 256 bytes of data. If the data is correct, BROM continues. Else it traps itself in an infinite loop, until it times-out due to no-command and reboots.
Our Beloved Friend @Agent_fabulous created a python script that imitates the same way the Mi Auth Works, But Sadly it doesnt work as of now. Your Can find the script here
A Ray Of Hope : Modified Preloader
Back in March 2020, When I got my Redmi 6A Bricked , I tried alot of ways to revive it , I ended up paying some bucks to shady guys on internet who revived my device via Mi Auth Over Remote Session Using TeamViewer. And More Sad part is most Xiaomi Service Centers don't know a single thing about Mi Auth, All they know is to replace motherboard LOL. Ah Noobs Everywhere.
After I revived my device , I began to think of making Antibrick that begonia already have ( Ah again thanks to @Agent_fabulous for his works) , Meanwhile, I found out the factory firmware for Redmi 6 & 6A., You see, every OEM receives a BSP for their platform of choice from the SoC manufacturer. Usually, the OEM will boot a clean version of this BSP on their hardware to get everything working, before the product team can start porting out the “skin” of Android that they advertise and ship their products with. This clean-version of the BSP build is often referred to as the “final factory firmware”.
We have factory firmware now ! Whats Next ?
After getting the factory rom, The thing you need to do first is boot that ROM safely in your devices (Note : If your phone is already hardbricked than this factory fw doesnt help, its for creating antibricks and other stuffs. ).
-You can boot your device to fastboot and fastboot flash all partitions from factory ROM
-after that turn off the device, attach it to your PC or Linux Machine)
-And Run dmesg on your device
-And Let device automatically power On.
Now if you see it register a cdc_acm device with description as MT65XX Preloader, Man You have Succeeded & Can flash without Mi Auth on that preloader.
After that try installing Any Other ROM, Say MemeUi 11, (Remember Dont Flash MIUI Preloader), Now extract Preloader & You Can Make a Flashable Zip xD. As Long as You are on that preloader, You have no worries , You can flash any ROM via SP Flash tool without any fancy auth.
Hope You Understood that What is Mi Auth & How it works on Mediatek Devices & How you can prepare a AntiBrick.
Press Thanks On this Thread xD
Credits:-
@Agent_fabulous (Mr. Kshitij ) for making me aware about Antibrick and How to prepare it. [He is developer from begonia Who Implemented VoLTE on Mediatek Chipset Based Device Redmi Note 8Pro ; He made antibrick too ; His Article Here (from which I've learned alot about Mi Auth)]
@An ASP (Aryan Sinha ; also known as TechyMinati) Making this article & Gathering info about Mi Auth .
I recommend you to give this XDA article a read, too!
Click to expand...
Click to collapse
Thank you for this information. I have hard bricked my Redmi 6. It requires 'Authorized Mi Account' while flashing. Can you please help me out by providing a solution with steps and links?
sarthak_iitd23 said:
Thank you for this information. I have hard bricked my Redmi 6. It requires 'Authorized Mi Account' while flashing. Can you please help me out by providing a solution with steps and links?
Click to expand...
Click to collapse
Hey since You were on MIUI Preloader , You'll need Mi Authorised Account to flash it , Or Visit Service Center ! Thanks
TechyMinati said:
Hey since You were on MIUI Preloader , You'll need Mi Authorised Account to flash it , Or Visit Service Center ! Thanks
Click to expand...
Click to collapse
where can i find a trusted user?
Thx
UPDATE!
We can disable SLA and DAA with https://github.com/MTK-bypass/bypass_utility
See It’s now easy to bypass MediaTek’s SP Flash Tool authentication
Dev thread is at MediaTek / MTK - Auth Bypass (SLA/DAA) - Utility
https://megafon929.github.io/mtk
A tutorial can be found at [Tutorial] How to flash an MTK secure boot device without a custom DA
and tutorial for Xiaomi Redmi Note 9(merlin) can be found at https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
Thanks
Hello guys, I'd like to ask if Poco X3 Pro will ever get a Patched (No Auth) Firehose file?
I'm not new to modding however it has been a couple of years since I last installed custom roms on my phone (Way back Android 6.0 days) and based on experience, unbricking has always been easy and accessible.
But with my new Poco X3 Pro, I read that Xiaomi requires Authorized Account when flashing with EDL. I've seen in some forums that some managed to patch the Firehose (Loader) file of other Xiaomi devices. Hence, I'm asking if there would ever be a possibility that someone could patch a Firehose file to bypass Auth.
I also looking for the patched
prog_ufs_firehose_sm7150_ddr.elf
the original (non patched) file is attached
prog_ufs_firehose_sm7150_ddr
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
lyqas said:
I also looking for the patched
prog_ufs_firehose_sm7150_ddr.elf
the original (non patched) file is attached
prog_ufs_firehose_sm7150_ddr
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
This kinda confused me a bit after downloading the official firmware. As far as I know (correct me if I'm wrong) our device should be SM8150 (not sure if it is SM8150AC) but I'm confused as to why it ks SM7150 in the firmware of our device.
But regardless, it would be nice if someone is able to modify the firehose file to no longer require authorization when it comes to flashing through edl.
It would be nice to save a lot of bricked Poco X3 Pros in the community without having people be at risk of getting scammed by "people with auth accounts."
Via hex-mode we can see in the elf file:
IMAGE_VARIANT_STRING=SDM855LA
OEM_IMAGE_VERSION_STRING=c5-xm-ota-bd031.bj
QC_IMAGE_VERSION_STRING=BOOT.XF.3.0-00571-SM8150LZB-4
just found our files here
GitHub - Chernobylll/FireHouse_UFS
Contribute to Chernobylll/FireHouse_UFS development by creating an account on GitHub.
github.com
but no success with them yet
and all elfs there are identical
lyqas said:
just found our files here
GitHub - Chernobylll/FireHouse_UFS
Contribute to Chernobylll/FireHouse_UFS development by creating an account on GitHub.
github.com
but no success with them yet
and all elfs there are identical
Click to expand...
Click to collapse
I've been really busy with school lately and can't really focus efforts on understanding the programmer file, let alone patching them. Wish someone would take a dip into patching it (which is difficult as the flash tool checks for the signatures of the programmer file).
jalter1213 said:
Hello guys, I'd like to ask if Poco X3 Pro will ever get a Patched (No Auth) Firehose file?
I'm not new to modding however it has been a couple of years since I last installed custom roms on my phone (Way back Android 6.0 days) and based on experience, unbricking has always been easy and accessible.
But with my new Poco X3 Pro, I read that Xiaomi requires Authorized Account when flashing with EDL. I've seen in some forums that some managed to patch the Firehose (Loader) file of other Xiaomi devices. Hence, I'm asking if there would ever be a possibility that someone could patch a Firehose file to bypass Auth.
Click to expand...
Click to collapse
Hi
You Can Request Bootloader Unlock and after 7 days unlock your phone you can flash everything in fastboot mode.
as alternative i can suggest you Xiaomi Pro tool it cost 5 credits and flash what you want to your phone
I have Unbricked My poco X3 pro From EDL with this tool 3 Days Ago
jalter1213 said:
I've been really busy with school lately and can't really focus efforts on understanding the programmer file, let alone patching them. Wish someone would take a dip into patching it (which is difficult as the flash tool checks for the signatures of the programmer file).
Click to expand...
Click to collapse
This is 64-bit arm ELF static stripped executable with vxworks RTOS signature, maybe it executed in that OS. It will be rather hard to understand how it works. I think firstly you need to get symbols names from vxworks symbol table, which is included in firehose, according to binwalk output
But still there can be firehose verification on the phone side(likely there is, because I cant load edited firehose with one edited byte in one of strings)
dashti.95 said:
Hi
You Can Request Bootloader Unlock and after 7 days unlock your phone you can flash everything in fastboot mode.
as alternative i can suggest you Xiaomi Pro tool it cost 5 credits and flash what you want to your phone
I have Unbricked My poco X3 pro From EDL with this tool 3 Days Ago
Click to expand...
Click to collapse
Where buy credit with PayPal for this tool?
ajanco said:
Where buy credit with PayPal for this tool?
Click to expand...
Click to collapse
Google this *Xiaomi Pro tool credit*
dashti.95 said:
Hi
You Can Request Bootloader Unlock and after 7 days unlock your phone you can flash everything in fastboot mode.
as alternative i can suggest you Xiaomi Pro tool it cost 5 credits and flash what you want to your phone
I have Unbricked My poco X3 pro From EDL with this tool 3 Days Ago
Click to expand...
Click to collapse
it depends on the exact case. For ex. if integrity of low-level systems such as chain loaders is broken, you MUST flash all this things in edl mode and then you will be able to boot to fastboot and flash other components
.
I need patched firehose (without auth account) for x3 nfc.
dashti.95 said:
Hi
You Can Request Bootloader Unlock and after 7 days unlock your phone you can flash everything in fastboot mode.
as alternative i can suggest you Xiaomi Pro tool it cost 5 credits and flash what you want to your phone
I have Unbricked My poco X3 pro From EDL with this tool 3 Days Ago
Click to expand...
Click to collapse
I'm not able to register to xiaomi pro tool
Can I borrow your pro tool.I'll refill the credits please.
I need to unbricked my poco x3 pro.
I also have a bricked poco x3 pro. are you able to find a patched firehose?
I have bricked phone and its backup data. This phone was only released in Japan, so there is little (or no) information available. I want to unbrick but don't have the Firehose Programmer and Firmware to do it in EDL mode. is there any way to create them in TWRP backup?
where you got that funny idea from? that file is not even on phone. for Xiaomi devices pay authorized xiaomi account and flash from Mi flash.
for other devices search for that file. you may find some collection here.
https://forum.xda-developers.com/t/...ithout-losing-your-data.4383255/post-86321813
Hi all,
I need a N976V U7 (USB only) DEAD-BOOT file / DEAD-FIX file / DEBUG EMERGENCY / 9008 / UnBrick / firehose programmer
The SM-N976V is a Verizon variant of the Note 10+ 5G positioned for the US market.
PLEASE PLEASE PLEASE !!!
Thank you.
Network_Pro said:
Hi all,
I need a N976V U7 (USB only) DEAD-BOOT file / DEAD-FIX file / DEBUG EMERGENCY / 9008 / UnBrick / firehose programmer
The SM-N976V is a Verizon variant of the Note 10+ 5G positioned for the US market.
PLEASE PLEASE PLEASE !!!
Thank you.
Click to expand...
Click to collapse
you dont need that as far as you can get into EDL mode you can flash with miracle tool box
So the Miracle Tool support SM-N976V SW Rev . bit7 (U7) ? I didn't find it specifically mentioned anywhere. In the EDL mode the Qualcomm sm8150 requires the firehose programmer. For other models this file seems to available so there is hope that for this model it can also be obtained from GSPN USA probably or from a guy who knows a guy who knows a guy who passed by a Samsung building once wink wink.
Network_Pro said:
So the Miracle Tool support SM-N976V SW Rev . bit7 (U7) ? I didn't find it specifically mentioned anywhere. In the EDL mode the Qualcomm sm8150 requires the firehose programmer. For other models this file seems to available so there is hope that for this model it can also be obtained from GSPN USA probably or from a guy who knows a guy who knows a guy who passed by a Samsung building once wink wink.
Click to expand...
Click to collapse
am telling you from experience it happened to my device i bricked it and i used miracle tool crack with just stock rom i did the EDL i just selected scatter file etc and i flashed and that was it
Anyways Good luck unbricking
Which update was it? I think the problem is the bit7 / U7 the firehose for that is another one if it worked for previous versions.
Gudaji said:
am telling you from experience it happened to my device i bricked it and i used miracle tool crack with just stock rom i did the EDL i just selected scatter file etc and i flashed and that was it
Anyways Good luck unbricking
Click to expand...
Click to collapse
Gudaji please give more info how did you do it exactly? Which 'scatter' file did you write to the device ?
Network_Pro said:
Gudaji please give more info how did you do it exactly? Which 'scatter' file did you write to the device ?
Click to expand...
Click to collapse
Okay,
I unpacked the firmware got the scatter file put the device in edl mode (with pins) and flashed the device .
But make sure you watch legit tutorials on YouTube how to get miracle tool box crack
Gudaji said:
Okay,
I unpacked the firmware got the scatter file put the device in edl mode (with pins) and flashed the device .
But make sure you watch legit tutorials on YouTube how to get miracle tool box crack
Click to expand...
Click to collapse
I've deleted your other post in this thread for the same reasons I already provided you here:
[RELEASED] TWRP FOR REDMI 12C/Poco C55
So I've started development for device trees, TWRP and custom for Redmi 12C (earth) and by the end of may we should also have a rom and custom recovery for our Redmi 12C. So stay tuned
forum.xda-developers.com
Please read my message as a friendly warning!
Regards
Oswald Boelcke
Senior Moderator
Which firmware and which scatter file? It won't work with wrong ones. More specifics please.
Did you have a pre-made scatter file, that you have made before bricking/EDL ?
It is important to be precise.
Network_Pro said:
Which firmware and which scatter file? It won't work with wrong ones. More specifics please.
Did you have a pre-made scatter file, that you have made before bricking/EDL ?
It is important to be precise.
Click to expand...
Click to collapse
Your stock rom it is in your stock rom just unpack it or use ODIN to unbrick
Odin does not see the phone because the phone is in 9008 EDL mode and the driver for that one is from Qualcomm. Odin wants a mode and driver from Samsung. For the Samsung download - Odin mode to work, the later Boot stages need to load. Those are messed up by wrong etoken bypass for the wrong Update version or wrong BL or tripepd knox erasure of the entire flash or something of that sort.
In the stock ROM I do not know which file you can call a scatterfile? Is it the PIT file which is used for formatting?
This is the 'stock ROM' correct ? https://samfw.com/firmware/SM-N976V/VZW/N976VVRU7HWB2
Well for sure the Miracle Box has a huge collection of loaders in the distribution, as well as XML files. Very interesting.
@Gudaji, it seems, however that with U7 there may be needed a new loader. The update "bit" is somehow set inside the CPU, which, from my understanding, prevents older loaders from working?
Network_Pro said:
Well for sure the Miracle Box has a huge collection of loaders in the distribution, as well as XML files. Very interesting.
@Gudaji, it seems, however that with U7 there may be needed a new loader. The update "bit" is somehow set inside the CPU, which, from my understanding, prevents older loaders from
Click to expand...
Click to collapse
First of all do you have miracle tool box?
If so go to the Qualcomm tab and you will se flash tab under and then you select the files from your “extracted” firmware and flash while in EDL mode
The "Miracle Box Update 3.39 to 3.40 only for PS" informs me there is a new version and does not start. Maybe I do not have the right one.
Network_Pro said:
The "Miracle Box Update 3.39 to 3.40 only for PS" informs me there is a new version and does not start. Maybe I do not have the right one.
Click to expand...
Click to collapse
There is a bypass for it but you have to look for it
I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.
Network_Pro said:
I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.
Click to expand...
Click to collapse
Reply in my pm asap
Network_Pro said:
I am not finding it yet give me more clues on PM please.
If someone can share a working Miracle tool or sell me a license please PM me.
Click to expand...
Click to collapse
First off how did you brick your device
Spammed the download mode with some wrong files. older etoken bypass, vbmeta disabled, KG disabled , eng. files, modem from other model, boot from other model, twrp recovery not sure which exactly was a successful flash and which were rejected due to checksum mismatch.
Network_Pro said:
Spammed the download mode with some wrong files. older etoken bypass, vbmeta disabled, KG disabled , eng. files, modem from other model, boot from other model, twrp recovery not sure which exactly was a successful flash and which were rejected due to checksum mismatch.
Click to expand...
Click to collapse
hayahe sorry your mobile is dead kek
MIRACLE TOOLBOX IS YOUR 1 AND ONLY SOLUTION IF YOU DONT WANT TO PAY ANYONE IVE GIVEN YOU GUIDE IN YOUR PM SO GOODLUCK KEK