Database Develop

Hard Brick on Asus ZenPad S8 (Z580CA) or Z580C

HARD BRICK NO MORE!!! Asus ZenPad S8.0 Fix
I made the sad retarded mistake in updating a manual zip file thru CMW... I know retarded... anyways this caused the tablet to Hard Brick bootloader only with very little options, you might even have your serial number showing up as all 1's.
Usually this isn't a big deal sadly this tablet gets little to no love on the internet it seems... This is a guide to help anyone un-brick their tablet
Step 1. First this is more of a windows 10 issue than anything but some driver installs thru the Asus Flash Tool might fail.. something to do about Driver Certificates, so you'll want to disable that on your Win 10.. here a tutorial link for more youtube link HERE
Step 2. Installing the proper Drivers if you haven't already, which will all be in this zip folder HERE
Make sure you installed the ADB-Setup | Intel Android Drv Setup | Asus Android USB Drivers | Asus Flash Tool Installer 1.14
Step 3. Next you'll want to download the .raw file for the ZenPad can be found HERE
Step 4. Open your Asus Flash Tool Installer, boot up your device in the boot mode. (Hold Down the Volume Up + Power ) till you see a little android man with a hardhat.
Step 5. Plug in your device and you should see your device show up as shown HERE, next you'll want to select the model in the model drop down.... Z580C or Z580CA.. then select file. Now if it only lets you select zip thats okay. On the open file dialog box you'll see you can type in the file, simply type in the file path of the .raw file. Once you have that check on Erase Content which will erase all your internal content, and hit flash... let it run until the blue light on the program is green and has flashed succefully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you may still get on a bootloop when it restarts, if that happens simply again restart in boot loader screen and do a hard reset and you'll be good to go! Afterwards just throw that new Marshmallow update in the internal and restart .. and you'll device will ask if you want to update now u got your tablet back and Marshmallow!!! I hope this helps if you have any troubles with the links, images please feel free to let me know pm or reply to this post!!! Best of Luck!
.RAW File was provided by Portzebie! Thanks again bud!!

Thanks for this guide. You mentioned .img file, but the file has a .raw extension. Do I need to change the extension from .raw to .img ? Yor response will be highly appreciated. my device is Z580CA.
Thanks again.

tfq535 said:
Thanks for this guide. You mentioned .img file, but the file has a .raw extension. Do I need to change the extension from .raw to .img ? Yor response will be highly appreciated. my device is Z580CA.
Thanks again.
Click to expand...
Click to collapse
Just followed the guide and after a little tinkering was able to get it to work. You don't need to change the file extension.
A few additional notes:
-to install the asus android drivers (not sure if it's even necessary but), open the ASUS_Android_USB_Drivers folder, then the android folder, then right click android_winusb.inf and select install.
-in the asus flash tool, after you select model, the location of the raw file and wipe, make sure you click on the SN to select the device. I didn't do this the first few times and it didn't do anything.

portezbie said:
Just followed the guide and after a little tinkering was able to get it to work. You don't need to change the file extension.
A few additional notes:
-to install the asus android drivers (not sure if it's even necessar but), open the ASUS_Android_USB_Drivers folder, then the android folder, then right click android_winusb.inf and select install.
-in the asus flash tool, after you select model, the location of the raw file and wipe, make sure you click on the SN to select the device. I didn't do this the first few times and it didn't do anything.
Click to expand...
Click to collapse
Thanks again, it worked like a charm.

bert_747 said:
Step 5. Plug in your device and you should see your device show up as shown HERE, next you'll want to select the model in the model drop down.... Z580C or Z580CA.. then select file. Now if it only lets you select zip thats okay. On the open file dialog box you'll see you can type in the file, simply type in the file path of the .img file. Once you have that check on Erase Content which will erase all your internal content, and hit flash... let it run until the blue light on the program is green and has flashed succefully.
Click to expand...
Click to collapse
Thanks for the guide.
The link to your screenshot is missing.

PMikeP said:
Thanks for the guide.
The link to your screenshot is missing.
Click to expand...
Click to collapse
Sorry bout that, screen shots should be working.

a little question,
is it possible to get xfstk files to restore a corrupt bootloader?
thx,,,

ASUS Flashtool doesn't start flashing
Hi all, apprechiated all the posts above however, came across another issue when trying to downgrade from MM 6.0.1 to Lollipop
1. Hooked up my Z580CA tablet as described above.
2. ASUS flashtool recognized my device (right serial number and blue light on)
3. I was not able to put in the raw-file location, only (neither with backslash or without)
4. When pasting path and including backslash I was able to select the raw file (H:\EDV\Tablet\Android 5 LP\RAW\Z580C_all_WW_user_V4.6.1.raw was quoted in the file name window)
5. When I hit start, the flashtool ask for confirmation upon wiping data.
6. Nothing happens
Does anybody have a clue what went wrong

These instructions do not work for Ubuntu. I find it very hard to believe that there is only a Windows version of the flash tool available.

Does anyone know how to upgrade again to MM after flashing this rom?
EDIT: CAUTION People, there seems to be no way to upgrade back to MM after flashing this ROM.

Yes you can upgrade
Servaas said:
Does anyone know how to upgrade again to MM after flashing this rom?
EDIT: CAUTION People, there seems to be no way to upgrade back to MM after flashing this ROM.
Click to expand...
Click to collapse
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles

edu47 said:
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
Click to expand...
Click to collapse
And you did this by downloading the .zip file from Asus Support? Then you placed it on the internal memory of the Zenpad? Unzipped or zipped?
EDIT: Until someone more senior comes to this thread and confirms that they have a. Used the provided .raw file, and b. updated afterwards with the precise steps i'm very much questioning this .raw file legitimately.

Servaas said:
And you did this by downloading the .zip file from Asus Support? Then you placed it on the internal memory of the Zenpad? Unzipped or zipped?
EDIT: Until someone more senior comes to this thread and confirms that they have a. Used the provided .raw file, and b. updated afterwards with the precise steps i'm very much questioning this .raw file legitimately.
Click to expand...
Click to collapse
download on asus homepage the file "UL-P01M-WW-5.4.3.0-user.zip", just copy it like it is on the root of your internal sdcard.
restart your zenpad and it will show you the message, upgrade available.
Edit:are you sure you on lollipop? If you are on Marshmallow ,the device wont recognize the systemupgrade.
if you re rooted it may also wont work

edu47 said:
I downgraded from marshmallow to lollipop with this instrucción and then upgraded again todo mm. It worked without any troubles
Click to expand...
Click to collapse
edu47 said:
download on asus homepage the file "UL-P01M-WW-5.4.3.0-user.zip", just copy it like it is on the root of your internal sdcard.
restart your zenpad and it will show you the message, upgrade available.
Edit:are you sure you on lollipop? If you are on Marshmallow ,the device wont recognize the systemupgrade.
if you re rooted it may also wont work
Click to expand...
Click to collapse
All of it does nothing for me. I'm stuck on 5.0. To people reading this use this .raw file at your own risk.

Servaas said:
All of it does nothing for me. I'm stuck on 5.0. To people reading this use this .raw file at your own risk.
Click to expand...
Click to collapse
Did you made an factory reset after installing lollipop on fastboot mode?
Switch your device off. Turn it on by pressing volume up and powerbottom at the same time.
When the little androidman appears you can stop pressing both bottoms.
Choose factory reset with volume bottom and confirm with power bottom.

edu47 said:
Did you made an factory reset after installing lollipop on fastboot mode?
Switch your device off. Turn it on by pressing volume up and powerbottom at the same time.
When the little androidman appears you can stop pressing both bottoms.
Choose factory reset with volume bottom and confirm with power bottom.
Click to expand...
Click to collapse
I just did this, this is my second tablet by the way, I returned the other one and this second one also does NOTHING when trying to update.
Its a shame really, its a great product but the lousy support on Asus side does little to inspire to again purchase from them. Honestly who rips out multiple user support on a tablet?
I'm all out of options to be honest, I have tried everything even variations on suggested sulotions but nothing works to make the update pop up.
This .raw file to me is broken when there is no way to update beyond that. But I need multi user support so I guess ill just stay on 5.0.

Servaas said:
I just did this, this is my second tablet by the way, I returned the other one and this second one also does NOTHING when trying to update.
Its a shame really, its a great product but the lousy support on Asus side does little to inspire to again purchase from them. Honestly who rips out multiple user support on a tablet?
I'm all out of options to be honest, I have tried everything even variations on suggested sulotions but nothing works to make the update pop up.
This .raw file to me is broken when there is no way to update beyond that. But I need multi user support so I guess ill just stay on 5.0.
Click to expand...
Click to collapse
Probably you still on lollipop by this version "Z580C_all_WW_user_V4.6.1.raw" from the tutorial . Get from asus usa website the "UL-P01M-WW-4.7.1.0-user.zip" and update to latest lollipop version . Then it might update again to mm.
Here the link
h ttp://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_Download/

edu47 said:
Probably you still on lollipop by this version "Z580C_all_WW_user_V4.6.1.raw" from the tutorial . Get from asus usa website the "UL-P01M-WW-4.7.1.0-user.zip" and update to latest lollipop version . Then it might update again to mm.
Here the link
h ttp://www.asus.com/us/Tablets/ASUS_ZenPad_S_80_Z580CA/HelpDesk_Download/
Click to expand...
Click to collapse
This zip file also doesnt register, nothing pops up and no, when pushing the update button it also does nothing.
It would seem that the OP provided a nice 5.0 raw file that renders your tablet un updateble.
I'll be returning this tablet and going for the only available option in the netherlands the samsung 8 incher.

Z580C tablet is bricked, it happened on update, I think battery was too low. Screen is black all the time, under windows device manager it connects as other devices, MOOREFIELD device with no drivers and I can hear from windows sounds that it reboots after some time. All post #1 drivers are installed.
Please help.
Thank you

magnus_bn said:
Hi all, apprechiated all the posts above however, came across another issue when trying to downgrade from MM 6.0.1 to Lollipop
1. Hooked up my Z580CA tablet as described above.
2. ASUS flashtool recognized my device (right serial number and blue light on)
3. I was not able to put in the raw-file location, only (neither with backslash or without)
4. When pasting path and including backslash I was able to select the raw file (H:\EDV\Tablet\Android 5 LP\RAW\Z580C_all_WW_user_V4.6.1.raw was quoted in the file name window)
5. When I hit start, the flashtool ask for confirmation upon wiping data.
6. Nothing happens
Does anybody have a clue what went wrong
Click to expand...
Click to collapse
Had the same problem and what I did to make it work was.
1. Lunch Asus Flash Tool
2. Connect device in download mode (volume up + power)
3. Wait for device to be visible in Asus Flash Tool ( Serial number + blue dot) - you may need to restart tablet using reboot droidboot
4. Select model number
5. Point to raw file and choose to erase data (accept the prompt )
6 Hit Start
What I also did prior to that was factory reset of tablet
hope that helps you

.backup file

Hello,
So my phone was stuck in bootloop and thus, I created a backup in my SD card. The files are shown as 13 files of 2GB size each with an extension ".backup" Anyone has any idea on how to combine these files and access the data inside on PC. The data is very important. Thank you!

deadmanspeaks said:
Hello,
So my phone was stuck in bootloop and thus, I created a backup in my SD card. The files are shown as 13 files of 2GB size each with an extension ".backup" Anyone has any idea on how to combine these files and access the data inside on PC. The data is very important. Thank you!
Click to expand...
Click to collapse
Crosspost from https://forum.xda-developers.com/t/moto-e4-plus-restart-loop.4241427/
I've had numerous Moto devices and have never seen any backup options in stock recovery., so I haven't any idea what format these are using.

readback stock recovery from SP Flash Tool and flash TWRP. also readback metadata partition (crypto footer). do not unlock bootloader because encryption is bonded to bootloader state. if you are lucky TWRP will work on locked bootloader. TWRP will decrypt your data so you can backup everything

aIecxs said:
readback stock recovery from SP Flash Tool and flash TWRP. also readback metadata partition (crypto footer). do not unlock bootloader because encryption is bonded to bootloader state. if you are lucky TWRP will work on locked bootloader. TWRP will decrypt your data so you can backup everything
Click to expand...
Click to collapse
How to do this? USB debugging and OEM are not ON in my phone. I saw some tutorial on YouTube, but it requires USB debugging.
Can't I use those userdata_*****.backup files?

usb-debugging is another option to access your data (can be enabled in boot.img)
SP Flash Tool is for preloader mode, no usb-debugging required
https://android.stackexchange.com/q/203283

wait, you did factory reset already? in that case crypto footer is reset too. backup is encrypted and therefore useless unless crypto-footer is restored.
you said you restored backup, are you sure? does the phone boot into lock screen like before and is pattern still the same?

aIecxs said:
wait, you did factory reset already? in that case crypto footer is reset too. backup is encrypted and therefore useless unless crypto-footer is restored.
you said you restored backup, are you sure? does the phone boot into lock screen like before and is pattern still the same?
Click to expand...
Click to collapse
Yes, the password is still the same. It's like the phone is again in the same condition with the same issue of boot loop.
I saw some tutorial on SP flash tool and what I did was:
1. Downloaded the SP flash tool
2. Downloaded TWRP recovery specific to my phone
3. Opened flash tool, went to download, clicked on scatter loading, selected the file and then clicked on download and connected my switched off device to the PC via USB
But, nothing happened after that.
My phone started charging, but nothing else happened.
I thought drivers weren't installed, so I went Driver Autoinstaller folders (there were 2 of them) and clicked on Driver Install, but it showed me this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I clicked on finish and it showed this
When I went to the second folder, it showed me this
Is it because of this, that my device is not detected by this flash tool, and if yes, what can I do?

Yes it's driver issue. Disable driver signature enforcement and reboot. open device manager, connect phone and immediately select yellow triangle. install inf manually with let me pick option
you should not flash TWRP without a backup of stock recovery. Do a readback first. Also it is important the scatter file is matching your current partition layout. therefore you should analyze the result. if you are able to extract ramdisk with AIK then you have successfully dumped stock recovery (and can proceed with next step flashing twrp)

aIecxs said:
Yes it's driver issue. Disable driver signature enforcement and reboot. open device manager, connect phone and immediately select yellow triangle. install inf manually with let me pick option
you should not flash TWRP without a backup of stock recovery. Do a readback first. Also it is important the scatter file is matching your current partition layout. therefore you should analyze the result. if you are able to extract ramdisk with osm0sis' AIK then you have successfully dumped stock recovery (and can proceed with next step flashing twrp)
Click to expand...
Click to collapse
Understood before the readback thing. What is readback? I saw the tab in flash tools, but didn't get what it was? Can you please tell how to do that? (sorry for irritating, as I said I am a noob )
And how to analyse the result part? I didn't get the "extract ramdisk with osmosis AIK"
Is there any tutorial video that you know of, if yes, kindly send the link please coz I don't understand these terms.
And thanks a ton for this!!!

on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done

aIecxs said:
on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done
Click to expand...
Click to collapse
Okay, thank a ton!
I'll do all of this and get back to you.

aIecxs said:
on readback tab delete all entries. add one entry for EMMC_USER. give meaningful file name recovery.img. enter length and start address in hex (refer to scatter file). start readback and connect phone.
Disable Antivirus program and download AIK. copy recovery.img into AIK directory and execute unpackimg.bat. enable Antivirus when done
Click to expand...
Click to collapse
So, what length and start address am I supposed to enter in hex?
And you shared the link AIK, in that there are so many options, which one do I have to select?

What can I do now?

deadmanspeaks said:
So, what length and start address am I supposed to enter in hex?
Click to expand...
Click to collapse
refer to scatter file
check your model name owens (XT1774 XT1775 XT1776) or nicklaus (XT1771 XT1772 XT1773)
download scatter file matching to your device model
https://motostockrom.com/motorola-moto-e4-plus-xt1770
https://motostockrom.com/motorola-moto-e4-plus-xt1771-dual-sim
https://motostockrom.com/motorola-moto-e4-plus-xt1772
https://motostockrom.com/motorola-moto-e4-plus-xt1773
https://motostockrom.com/motorola-moto-e4-plus-xt1775
deadmanspeaks said:
And you shared the link AIK, in that there are so many options, which one do I have to select?
Click to expand...
Click to collapse
Android.Image.Kitchen.v3.7-Win32.zip
Code:
S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] can not pass bootrom start command! Possibly target power up too early.
deadmanspeaks said:
What can I do now?
Click to expand...
Click to collapse
pretty much self explaining.
why flash boot.img? are you sure that scatter matches your partition layout (you will erase wrong area if not)!?

aIecxs said:
refer to scatter file
View attachment 5281905
check your model name owens (XT1774 XT1775 XT1776) or nicklaus (XT1771 XT1772 XT1773)
download scatter file matching to your device model
https://motostockrom.com/motorola-moto-e4-plus-xt1770
https://motostockrom.com/motorola-moto-e4-plus-xt1771-dual-sim
https://motostockrom.com/motorola-moto-e4-plus-xt1772
https://motostockrom.com/motorola-moto-e4-plus-xt1773
https://motostockrom.com/motorola-moto-e4-plus-xt1775
Android.Image.Kitchen.v3.7-Win32.zip
Code:
S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] can not pass bootrom start command! Possibly target power up too early.
pretty much self explaining.
why flash boot.img? are you sure that scatter matches your partition layout (you will erase wrong area if not)!?
Click to expand...
Click to collapse
Thanks a lot here it is written nma26.42-169/300 and my phone is xt1770. The link you gave shows the file can't be downloaded, can you please give any other link. I googled the same, it gave me NMA26.42-169 INDIA something but those files are paid

drive.google.com links working fine to me

aIecxs said:
drive.google.com links working fine to me
Click to expand...
Click to collapse

tested all links. must be something about your country. you should get something like
Couldn't preview file. You may be offline or with limited connectivity.
click on -> Download
Google Drive can't scan this file for viruses
click on -> Download anyway

aIecxs said:
tested all links. must be something about your country. you should get something like
Couldn't preview file. You may be offline or with limited connectivity.
click on -> Download
Google Drive can't scan this file for viruses
click on -> Download anyway
Click to expand...
Click to collapse
Yes, I did that, after that only it shows this.
I am about to cry, it's been 14 months trying to get those files. Every time, I get too close and then bam! back to square one. Can't access those userdata***.backup files, can't access the phone, as soon as it starts, it gets stuck in a reboot loop, can't flash TWRP because not able to download the file. You have no idea how painful this is. Still thanks a lot, you helped me a lot, but I guess it's a lost cause now. Earlier lost the person, now lost the memories. Thanks anyways

deadmanspeaks said:
can't flash TWRP because not able to download the file.
Click to expand...
Click to collapse
https://twrp.me/motorola/motorolamotoe4plus.html

Hardbricked Redmi 9 mt6769

Hello yesterday i bricked my phone when i tried to install twrp recovery. Now my phone is bootlooping from last night. I can't get into fastboot or recovery and the spflashtool does not read the COM port. Can someone help please!!

How to install:
1. Download the attached file: VD171_MTK-bypass.zip.
2. Extract the file and open the folder.
3. Run and install python: python-3.9.1-amd64.exe.
Keep atention: You need to select "Add Python to PATH" before starting the installation.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Open cmd or powershell and execute this command:
pip install pyusb pyserial json5
5. Go to the Driver folder and right-click on the cdc-acm.inf file, then click Install and then, close window.
6. Run and install filter wizard: libusb-win32-devel-filter-1.2.6.0.exe.
7. Launch filter wizard.
8. Select Install a device filter and click Next.
9. Connect powered off phone with volume- button to boot in EDL mode.
10. Once you see new MediaTek USB Port in the list, select it and click Install.
Now, you are ready for bypassing EDL !
How to bypass:
1. Go to the Bypass folder. Run the script: bypass.bat.
2. Connect powered off phone with volume- button to boot in EDL mode.
3. Once you get "Protection disabled" at the end, without disconnecting phone and usb, run SP Flash Tool.
4. Once the SP Flash Tool opens, click Options > Options > Connection.
5. Select UART mode and select Baud rate to 921600.
Now, you are ready for flashing !
How to update the tool:
1. Download latest release of the tool: https://github.com/MTK-bypass/bypass_utility/releases/latest
2. Download latest release of payloads: https://github.com/MTK-bypass/exploits_collection/releases/latest
3. Extract the content of both files to the Bypass folder.
It is updated now.
https://forum.xda-developers.com/attachments/vd171_mtk-bypass-v1-5-zip.5228529/

well there it is follow those steps..

well there it is follow those steps
Stefy1337 said:
Hello yesterday i bricked my phone when i tried to install twrp recovery. Now my phone is bootlooping from last night. I can't get into fastboot or recovery and the spflashtool does not read the COM port. Can someone help please!!
Click to expand...
Click to collapse
you did try booting into EDL right?

Keno_I said:
well there it is follow those steps
you did try booting into EDL right?
Click to expand...
Click to collapse
no, I didn't try. If you refer to edl points I tried to press them but nothing happens. And the spflashtool does not detect the com port.

What port did you connect through, try changing usb ports.
And plugging into usb 2.0

Keno_I said:
What port did you connect through, try changing usb ports.
And plugging into usb 2.0
Click to expand...
Click to collapse
i got only 3.0

You need usb 2.0 it isnt recognized on 3.0.....

Keno_I said:
You need usb 2.0 it isnt recognized on 3.0.....
Click to expand...
Click to collapse
I'll try to get it. Does it work if I use an external USB connected to 3.0?

Im not sure, but try it, all i know that spflashtool doesn't work nicely with USB 3.0 idk why

Keno_I said:
Im not sure, but try it, all i know that spflashtool doesn't work nicely with USB 3.0 idk why
Click to expand...
Click to collapse
Ok thanks a lot <3

Keno_I said:
Im not sure, but try it, all i know that spflashtool doesn't work nicely with USB 3.0 idk why
Click to expand...
Click to collapse
i will update you if i fix it

Stefy1337 said:
i will update you if i fix it
Click to expand...
Click to collapse
Okay, good luck!

Kenora_I said:
Okay, good luck!
Click to expand...
Click to collapse
got this error when open bypass
Traceback (most recent call last):
File "D:\shared folder vmware\VD171_MTK-bypass-v1.5\Bypass\main.py", line 3, in <module>
from src.exploit import exploit
File "D:\shared folder vmware\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 2, in <module>
from serial.serialutil import SerialException
ModuleNotFoundError: No module named 'serial'

Stefy1337 said:
got this error when open bypass
Traceback (most recent call last):
File "D:\shared folder vmware\VD171_MTK-bypass-v1.5\Bypass\main.py", line 3, in <module>
from src.exploit import exploit
File "D:\shared folder vmware\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 2, in <module>
from serial.serialutil import SerialException
ModuleNotFoundError: No module named 'serial'
Click to expand...
Click to collapse
pip install pyserial
Do that if you have python 2
Python 3 may be
pip3 install pyserial

Kenora_I said:
pip install pyserial
Do that if you have python 2
Python 3 may be
pip3 install pyserial
Click to expand...
Click to collapse
hey dude its me again .. i did it .. i bypassed the protection but can you teach me how to use sp flash tool and update frimeware so i can unbrick my device.. please

Update : somehow i managed to get back the recovery and fastboot but still not booting.. idk how to reinstall the rom

Update : Unbricked using mi flash tool and this tutorial https://c.mi.com/oc/miuidownload/detail?guide=2
Love Kenora for help <3

Sorry I was busy but nice to hear it worked!

General [GUIDE][UNBRICK] Realme 8 Unbrick/Upgrade/Downgrade [RMX3085]

Hello everyone! So after the new MediaTek DAA and SLA protection bypasses you can find GitHub repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX3085 (Realme 8) ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
Requirements:
PC or Laptop
Internet connection
Realme 8
USB cable
Windows Method
Requirements:
Bypass Tools Pack - (DRIVER AND BYPASS FILES)
SP Flash Tool
Decrypted OFP (OPPO FIRMWARE PACKAGE) :
Indian
A.22 (Indian) - GDrive
A.24 (Indian) - GDrive
A.26 (Indian) - Gdrive
C.05 (Indian) - GDrive
C.09 (Indian) - GDrive
C.11 (Indian) - GDrive
Global
A.22 (Global) - GDrive
A.24 (Global) - GDrive
A.26 (Global) - GDrive
Install Python from Windows Store
libusb-win32 - Having Issues? Use this.
Get usbdk installer (.msi) from here and install it
Steps:
1) Extract the zip
2) Go to driver folder, find the .inf file right click and press install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Download this file and install it, after installing power off phone and connect to pc while holding Vol+- (don't leave the buttons after connecting) . You might need this driver as well if it's not detected.
4) Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off, and don't leave the buttons) and you will see the mtkdriver down below. Install it.
5) Choose MediaTek USB Port and install it.
6) Then run the brom.bat under Bypass folder.
7) Now power off the phone and connect the phone while holding volume + and - (Don't leave the buttons until the bypass is done)
8) After the above step Go into Flash Tool folder and open the SPFlash tool go to Options>Option
9) Click on Connections and select UART and set Baud Rate to 921600
10) After that choose scatter file and also if not set, set your download-agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Select all the Partitions except opporeserve2 and cdt_engineering. otherwise you will get errors.
*11) If you want to flash super.img partition also then download this scatter.txt file and replace it with the another scatter file which is present in the decrypted firmware folder. After that select it again in sp flash tool.
Again Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
After flashing it should look like this. Download has been complete. Enjoy!
"Congrats Now your Realme 8 is Unbricked "
Credits :
https://github.com/bkerler/ for decryptor and for creating the tool.
If you face any issues write them down below...

Some people having this problem so I want to add one more thing to the guide. If you are not having any issues related to boot then don't follow these steps.
After waiting more then 10 minutes, if it doesn't boot up/bootloop. Or shows DM-Verity corrupt error then do this.
1) Try boot into stock recovery by pressing volume up + power button after that when your screen flashes quickly unpress buttons.
2) Now press volume down + power button, by pressing these you will boot into stock recovery.
3) Go to format option and do a full format.
4) Your phone will definitely boot up after that.

Hi
I would like to ask how you obtained the system for realme 8 in the latest version.
Can you download somehow from your device?

HowWof said:
Hi
I would like to ask how you obtained the system for realme 8 in the latest version.
Can you download somehow from your device?
Click to expand...
Click to collapse
From realme offical site

Could you send a link because there is no information on the Polish realme site

HowWof said:
Could you send a link because there is no information on the Polish realme site
Click to expand...
Click to collapse
Realme 8 Firmware (RMX3085) - Realme Firmware
Realme 8 Firmware RMX3085 Official Flash File (Stock ROM). flash your phone using realme flashtool or MSM Download tool.
realmefirmware.com

if "Brick" occured in rooting process - then can recovery be done without data loss :
Prerequisite: firmware version on the body must the same as downloaded "Decrypted OFP" (as example both is A.22 )
HowTo:
at step of SPFlashing (currently that is 10-th)
- check ONLY next partitions in SPFlash to restore :
PRELOADER RECOVERY VBMETA LK LK2 BOOT
... and NO any of other
(as thats only are touched by currently described rooting processes)

after recovery exist on every boot:
"dm-verify corrupted..."
how to get out of this message?
Reset with clearing data not helps ...

DaLiV said:
after recovery exist on every boot:
"dm-verify corrupted..."
how to get out of this message?
Reset with clearing data not helps ...
Click to expand...
Click to collapse
Wait for 10mins if it didn't boot then.
Format with mtk client
python mtk e metadata,userdata,md_udc

that boots ... BUT
on every boot thet alerts about "corruption"
ok cleared partitions with python...
still the same alert ...

DaLiV said:
that boots ... BUT
on every boot thet alerts about "corruption"
ok cleared partitions with python...
still the same alert ...
Click to expand...
Click to collapse
Try booting into stock recovery and format from there

Ok. format from recovery menu solves ...
now that boots normally =
- no alert
-no boot allowing by pressing key required
good behaviour to see when boot subsystem altered, as at every boot alerted and required to press longer power button to confirm/allow starting ...
interesting, that is something new on mine (device versions) or overall ...

I have it anyway. have you solved it yet? Do I understand correctly?

after doing the insstruction, mine bootlooping and enters recovery mode

XCentrialG said:
after doing the insstruction, mine bootlooping and enters recovery mode
Click to expand...
Click to collapse
Maybe you missed some step. Can u explain ur problem briefly. What u did and what happened.

niki.rsb said:
I have it anyway. have you solved it yet? Do I understand correctly?
Click to expand...
Click to collapse
I Think that is not so solvable /possible if someone decode debug and finds /... but that is quite acceptable for rooting /if you don't want to make illegal spionage and so on/ ... also as if your device will be rooted by someone - you will see alert of changes on boot ... that is good ...
if you are rooted - you must be alerted .
but if you will going to stock rom and have protection - then flashing "stock" (surely without 3 partitions that IMEI-and-so-on-related ) and then format from recovery menu helps return to "factory" operation

Tony Stark said:
Maybe you missed some step. Can u explain ur problem briefly. What u did and what happened.
Click to expand...
Click to collapse
just a casual day to update my firmware, reboot and my phone refused to boot anymore, and then i came here, following all the steps very carefully (i read every steps twice so i dont make any mistake), and no luck.

XCentrialG said:
just a casual day to update my firmware, reboot and my phone refused to boot anymore, and then i came here, following all the steps very carefully (i read every steps twice so i dont make any mistake), and no luck.
Click to expand...
Click to collapse
There should be some mistake in your process. Because this guide is working and tested by many people.

Does global firmware have realme dialer instead of google dialer?
Can I flash Global firmware my indian device?

on your firmware package, it does not flashes super.img by default. Because in scatter file
- partition_index: SYS48
partition_name: super
file_name: super.img
is_download: false
changing false to true helps fixing destroyed super partition

Question Hardbrick no recovery or fastboot

Forgot how it got to this point, i think i flashed wrong boot.img or something, but my device just reboots constantly on the redmi sign. Tried following the guides on here but i got lost at some point. I've installed the driver filter and done the mtk bypass thing, but I'm confused on where i should go from here?

first of all, install MTK preloader/brom vcom drivers for your PC be able to detect your phone in BROM mode (attached below)
install MiFlashPro, you will need it to fill the Download-Agent in sp tool so you can write the boot images to recover your phone.
then, use the miui ROM that you used before bricking it, or download it from any website (my favorite is mifirm.net, it downloads faster)
now open sp tool from MiFlashPro.
now you will need to fill out 3 spaces:
download-agent (DA for short), scatter-loading file & authentication file.
DA is to have access to the devices internal storage, scatter-loading shows you the mapping of the partitions it will flash on the mtk & authentication is just MTK protection for newer mtk devices that you need to be able to flash (its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
to find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
to find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
finally, to find the scatter-loading file, it is in the rom folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). the scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Now, you need to edit the "MT6833_Android_scatter.txt", or else when you use to flash you will get this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open it (located at your MIUI ROM folder at \images), then use the locate tool to find "combo_partsize_check: true". You will probably find a few lines set as true, just replace every one with false (if it doesnt find it, just put "combo_partsize_check", but you will waste more time finding those that are set to true)
Alright, we finished our sp tool settings. now we have to bypass MTK Auth protection.
(Dont close sp tool yet!)
Ive annexed the tool below (mtkauthbypass.zip), download it and extract it.
It looks like this:
After you are ready, press the "Disable Auth" button, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompts appearing in the blank (i dont have a screenshot to show how it looks like, sorry)
after it bypasses, go to sp tool and click download immediately, then your device should come to life.
if it didnt work, i recommend selecting every mapping excluding your data, or do a full reflash if you wish or as last resort

1lopes said:
first of all, install MTK preloader/brom vcom drivers for your PC be able to detect your phone in BROM mode (attached below)
install MiFlashPro, you will need it to fill the Download-Agent in sp tool so you can write the boot images to recover your phone.
then, use the miui ROM that you used before bricking it, or download it from any website (my favorite is mifirm.net, it downloads faster)
now open sp tool from MiFlashPro.
now you will need to fill out 3 spaces:
download-agent (DA for short), scatter-loading file & authentication file.
DA is to have access to the devices internal storage, scatter-loading shows you the mapping of the partitions it will flash on the mtk & authentication is just MTK protection for newer mtk devices that you need to be able to flash (its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
to find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
to find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
finally, to find the scatter-loading file, it is in the rom folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). the scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Now, you need to edit the "MT6833_Android_scatter.txt", or else when you use to flash you will get this error:
Open it (located at your MIUI ROM folder at \images), then use the locate tool to find "combo_partsize_check: true". You will probably find a few lines set as true, just replace every one with false (if it doesnt find it, just put "combo_partsize_check", but you will waste more time finding those that are set to true)
Alright, we finished our sp tool settings. now we have to bypass MTK Auth protection.
(Dont close sp tool yet!)
Ive annexed the tool below (mtkauthbypass.zip), download it and extract it.
It looks like this:
After you are ready, press the "Disable Auth" button, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompts appearing in the blank (i dont have a screenshot to show how it looks like, sorry)
after it bypasses, go to sp tool and click download immediately, then your device should come to life.
if it didnt work, i recommend selecting every mapping excluding your data, or do a full reflash if you wish or as last resort
View attachment 5860063
Click to expand...
Click to collapse
I was having errors with 'verified boot', managed to reflash everything with mtkclient, how do i get back to stock rom from here? Phone boots to fastboot mode but 'fastboot reboot fastboot' or 'fastboot reboot bootloader' just reboots device

HollyMarijuanna said:
I was having errors with 'verified boot', managed to reflash everything with mtkclient, how do i get back to stock rom from here? Phone boots to fastboot mode but 'fastboot reboot fastboot' or 'fastboot reboot bootloader' just reboots device
Click to expand...
Click to collapse
use mi flash pro, open mi flash, download miui rom and flash it thru there while on fastboot. you dont need dynamic fastboot for it, dont worry

1lopes said:
use mi flash pro, open mi flash, download miui rom and flash it thru there while on fastboot. you dont need dynamic fastboot for it, dont worry
Click to expand...
Click to collapse
Thank you! I was trying to fix this phone in December and gave up.. I appreciate your help

HollyMarijuanna said:
Thank you! I was trying to fix this phone in December and gave up.. I appreciate your help
Click to expand...
Click to collapse
glad to help