Hello i have flash TWRP on my Redmi 9
and on my computer i have typed this command
"fastboot reboot fastboot"
for acces to the fastbootd mode
and now i have
REDMI
Powered By Android
black screen
and
Redmi
Powered By Android
and this loop
my english is very bad
bye
I have this problem too!!! could you fix it? it happened to me when I did this too
try to hard reset
I had the same problem after trying to flash the TWRP custom recovery on my Redmi 9 (lancelot).
In case that someone still needs to know, following was my solution:
I needed to flash back the stock firmware on my device with SP Flashtool. For that you of course need to download the firmware and take the scatter file of it. Then grab a custom Download Agent File and an authentication file from the web.
Also you need the MTK_bypass utility with the right payloads from the github website (Redmi 9 is MT6768, just take the master collection payload, it worked for me). You need that tool to disable the DAA und SLA protection on your Redmi 9. (Except you have access to an authorized Mi account of course, then you can just flash it with Mi Flash tool, but usually, one doesn't have that.) Follow the instruction on the web, there are detailed ways how to install the right drivers and run the bypass utility correctly.
In my case I had to format my device with the automatic flashing in SP Flashtool before the flashing worked, but that was it - my Redmi 9 is working fine again.
thank you for the input as it really cleared my head after i took a break at trying to get this thing out of a bootloop.
this does work, using sp flash tool but the device will auto detect through usb and you've gotta have the scatter file and firmware for the device. after using the brom utility don't restart the phone, you will reverse the process.
iReebu said:
I had the same problem after trying to flash the TWRP custom recovery on my Redmi 9 (lancelot).
In case that someone still needs to know, following was my solution:
I needed to flash back the stock firmware on my device with SP Flashtool. For that you of course need to download the firmware and take the scatter file of it. Then grab a custom Download Agent File and an authentication file from the web.
Also you need the MTK_bypass utility with the right payloads from the github website (Redmi 9 is MT6768, just take the master collection payload, it worked for me). You need that tool to disable the DAA und SLA protection on your Redmi 9. (Except you have access to an authorized Mi account of course, then you can just flash it with Mi Flash tool, but usually, one doesn't have that.) Follow the instruction on the web, there are detailed ways how to install the right drivers and run the bypass utility correctly.
In my case I had to format my device with the automatic flashing in SP Flashtool before the flashing worked, but that was it - my Redmi 9 is working fine again.
Click to expand...
Click to collapse
if my phone is bootloop and can't go into recovery mode either fastboot mode, can it be done ?
my phone bootloop after installing twrp and there you go bootloop until the end. can't go any mode also can't turn off the phone. any suggestion ?
daniel04222 said:
if my phone is bootloop and can't go into recovery mode either fastboot mode, can it be done ?
my phone bootloop after installing twrp and there you go bootloop until the end. can't go any mode also can't turn off the phone. any suggestion ?
Click to expand...
Click to collapse
I had the same issue, I was not able to enter neither recovery mode nor fastboot mode. But you are able to enter EDL mode, the Emergency Download Mode - in my case at least. From there I was able to unbrick the phone. I was able to enter EDL mode without opening the phone and using test points. Turning the phone on and connecting it to the computer in the same second as the screen goes on let me enter for some seconds, it was enough to let me run the tool to bypass the DAA and SLA protection of the device. Then I was able to flash back the stock firmware with SP-Flashtool. In my case I needed to format the device before the flashing worked, but then it booted back up alive.
Just be aware you probably need to install the proper drivers first to bypass DAA and SLA protection with LibUSB.
I have the same problem, help
I already tried all the methods in this post, my phone cannot access fastboot or recovery mode, and when I connect it via usb it starts immediately
iReebu said:
I had the same issue, I was not able to enter neither recovery mode nor fastboot mode. But you are able to enter EDL mode, the Emergency Download Mode - in my case at least. From there I was able to unbrick the phone. I was able to enter EDL mode without opening the phone and using test points. Turning the phone on and connecting it to the computer in the same second as the screen goes on let me enter for some seconds, it was enough to let me run the tool to bypass the DAA and SLA protection of the device. Then I was able to flash back the stock firmware with SP-Flashtool. In my case I needed to format the device before the flashing worked, but then it booted back up alive.
Just be aware you probably need to install the proper drivers first to bypass DAA and SLA protection with LibUSB.
Click to expand...
Click to collapse
Can you tell us how did you unbricked your device step - by - step? Sorry I am a newbie and do not know how to do it.
Alfredo_One said:
Tengo el mismo problema, ayuda
Ya probé todos los métodos en esta publicación, mi teléfono no puede acceder al modo de arranque rápido o de recuperación, y cuando lo conecto a través de USB, se inicia de inmediato.
Click to expand...
Click to collapse
Si hablas español podría ayudarte, te dejo mi FB
Log into Facebook
Log into Facebook to start sharing and connecting with your friends, family, and people you know.
www.facebook.com
Cualquiera que tenga ese problema en cualquiera de los dispositivos Xiaomi que hable español puede comunicarse conmigo y con gusto los ayudaré
Related
Hi, I got a Mi5 64gb with MIUI 7.2. 13.0 everything stock and with BL locked (I assume because I can't get into recovery mode). When I try vÃa Settings to factory Reset it, the process starts but suddenly turns of and it is difficult to turn it on again, but when it turns on, nothing was erased. Any help with this problema?
Also, I'm wondering, do I need any special requirements to update it to MIUI 8 vÃa the update app on the phone? Might this get the problem solved?
Any help is welcomed, thanks.
try with my bat file
- Download file, Extract it
- boot device to recovery mode
- connect to PC and Check adb devices
- if device connected in adbsideload mode , run "format-data.bat" . It will wipe user data [ Factory Reset ]
- Some Xiaomi Devices with locked bootloader can factory data reset from adb . command is "adb format-data" .
Note ....... Only I uploaded adb.exe can support this command and I got it from MI Suit
if any help need , please contact me from facebook . my profile is https://www.facebook.com/kyawkyarnyu
Here is Download file >
https://my.pcloud.com/publink/show?code=XZ1mTwZlz8R5TErL3m7xaQlJMBgUmi9euuy
Gracias hermano me fue de mucha ayuda tu aporte
Hi,
I'm trying flash my mi a2 in miflash but cant, still error flash right at the beginning in Bluetooth. Anyone can help?
In fast boot doesn't appear the bunny, only black. But I can flash if boot in edl, only in fastboot this error happen.
Sorry my English
do you have an error in fastboot mode: "press any key to shutdown"? I have same problem
rmbplacido said:
Hi,
I'm trying flash my mi a2 in miflash but cant, still error flash right at the beginning in Bluetooth. Anyone can help?
In fast boot doesn't appear the bunny, only black. But I can flash if boot in edl, only in fastboot this error happen.
Sorry my English
Click to expand...
Click to collapse
*you probably need to unlock flashing critical, there is a tool on the forum to do that, is a fastboot command.
*probablemente necesitas desbloquear el flashing critical (algo así), usa la herramienta del foro para hacerlo, es un comando de fastboot
I have the critical unlock and I can flash in edl mode, only on the fasboot give a error in flash, the error begin in moment I flash and say Bluetooth can't flash
Hello.
I was on the September update, unlocked and rooted, but I wanted to update to the october one, so I uninstalled magisk and flashed the september boot and system images.
Unfortunately that didn't work (I still couldn't install the OTA), so I' ve decided to flash manually all the images of the october update (I got them on the OTA thread).
After that my device went on bootloop, so I decided to flash again all the images of the September update (V9.6.13.0).
When I run "fastboot flash system_a system.img" I got the error "Invalid argument" and after that my device turned off.
Now IT IS TOTALLY BRICKED, I can't turn it on and I can't even enter fastboot.
I really don't know what to do, do you have any idea?
If you have working fastboot try to Flash full September update with Mi flash tools, wipe everything and Lock bootloader.
After that you will receive ota from October.
Sent from my Mi A2 using Tapatalk
tomgv said:
If you have working fastboot try to Flash full September update with Mi flash tools, wipe everything and Lock bootloader.
After that you will receive ota from October.
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
As I've said, I can't enter fastboot mode.
My device is bricked
Lurensu said:
As I've said, I can't enter fastboot mode.
My device is bricked
Click to expand...
Click to collapse
Open your phone and flash through EDL mode by shorting test points...
Yep, your last hope is attempt to flash through edl mode by shorting those pins, that's why I always re-install stock rom using Mi flash through edl mode booted from fastboot
Thanks guys, I hope to find a method which doesn't require to open the device.. if I fail I'll try the test points one.
However my device is still recognized by Windows and by MiFlash as Qualcomm QDLoader 9008 and I've read that some people managed to flash a fastboot rom in this mode (on the Mi A1).
Isn't this EDL mode already?
Looking at this guide it looks like the whole point of "test points" is to get the device recognized as QDLoader 9008, isn't it?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267
Lurensu said:
Thanks guys, I hope to find a method which doesn't require to open the device.. if I fail I'll try the test points one.
However my device is still recognized by Windows and by MiFlash as Qualcomm QDLoader 9008 and I've read that some people managed to flash a fastboot rom in this mode (on the Mi A1).
Isn't this EDL mode already?
Looking at this guide it looks like the whole point of "test points" is to get the device recognized as QDLoader 9008, isn't it?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267
Click to expand...
Click to collapse
When phone is recognized as qualcomm it means it's bricked so it entered edl by itself, you can use mi flash to get back to september patch, then boot into fastboot and flash it again, then ota
EDIT: anti rollback is still not activated in october patch
Nebrassy said:
When phone is recognized as quallcomm it means it's bricked so it entered edl by itself, you can use mi flash to get back to september patch, then boot into fastboot and flash it again, then ota
EDIT: anti rollback is still not activated in october patch
Click to expand...
Click to collapse
Whoaa that's great! (well, obviously it isn't, but at least I don't have to open the phone)
Are you sure about the anti rollback? So am I safe flashing the September fastboot images?
Thank you very much, I really appreciate your help
Lurensu said:
Whoaa that's great! (well, obviously it isn't, but at least I don't have to open the phone)
Are you sure about the anti rollback? So am I safe flashing the September fastboot images?
Thank you very much, I really appreciate your help
Click to expand...
Click to collapse
Yes, all A2 firmwares got ARB set to 2, I'm on 9.6.15
also, I was on first october build 9.6.14 but I had modified vendor, so I flashed september patch then got the ota to 9.6.15 so I'm sure, there's no ARB yet
Nebrassy said:
Yes, all A2 firmwares got ARB set to 2, I'm on 9.6.15
also, I was on first october build 9.6.14 but I had modified vendor, so I flashed september patch then got the ota to 9.6.15 so I'm sure, there;s no ARB yet
Click to expand...
Click to collapse
Thank you so much, I'll try to flash the september update then, let's hope everything goes right!
EDIT:
well, everything went smoothly and I'm now on the october update
I can enter un fastboot mode but my PC doesn't recognized my device, Someone can help me?
I have all drivers installed but always the same issue.
Hi guys.. Thanks for this article!!!. It was very useful. I had my Mi A2 bricked, I was in QDLoader 9008 state, but I didn't need to disassemble the MI A2, I think as Lurensu my device was already in the QDLoader state. I reached this state trying to manually update to the November patch, then "fastboot" didn't flash the aboot_b image, yes sure; I didn't realize this until the reboot.
I had the error "Cannot receive hello packet" with fails trying to flash with MiFlash, but the solution finally, was to have pressed the Power button for various seconds then the device was again ready for flash, and finally this was flashed to the September patch. I had this image files from some tools for rooting and updating.
Thanks again!...
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
kevin2546 said:
I can enter un fastboot mode but my PC doesn't recognized my device, Someone can help me?
I have all drivers installed but always the same issue.
Click to expand...
Click to collapse
I'm pretty sure your problem is more simple than you think. Perhaps this is not the more adequate Thread, you need the windows drivers for Mi A2. This trouble is easily "googleable" :good:
yisao said:
Hi guys.. Thanks for this article!!!. It was very useful. I had my Mi A2 bricked, I was in QDLoader 9008 state, but I didn't need to disassemble the MI A2, I think as Lurensu my device was already in the QDLoader state. I reached this state trying to manually update to the November patch, then "fastboot" didn't flash the aboot_b image, yes sure; I didn't realize this until the reboot.
I had the error "Cannot receive hello packet" with fails trying to flash with MiFlash, but the solution finally, was to have pressed the Power button for various seconds then the device was again ready for flash, and finally this was flashed to the September patch. I had this image files from some tools for rooting and updating.
Thanks again!...
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
I'm pretty sure your problem is more simple than you think. Perhaps this is not the more adequate Thread, you need the windows drivers for Mi A2. This trouble is easily "googleable" :good:
Click to expand...
Click to collapse
hola amigo me puedes dar una mano tengo mi a2 en estado EDL no prende solo lo reconoce
gian789 said:
hola amigo me puedes dar una mano tengo mi a2 en estado EDL no prende solo lo reconoce
Click to expand...
Click to collapse
Con la herramienta Mi Flash de Xiaomi lo puedes recuperar fácilmente, todo está en Google. En parte es tener el programa MiFlash y que te bajes una ROM OEM de este sitio, lo flashees y queda como nuevo; todo esto suponiendo que no tenga un daño peor, pero eso es raro
Lurensu said:
Hello.
I was on the September update, unlocked and rooted, but I wanted to update to the october one, so I uninstalled magisk and flashed the september boot and system images.
Unfortunately that didn't work (I still couldn't install the OTA), so I' ve decided to flash manually all the images of the october update (I got them on the OTA thread).
After that my device went on bootloop, so I decided to flash again all the images of the September update (V9.6.13.0).
When I run "fastboot flash system_a system.img" I got the error "Invalid argument" and after that my device turned off.
Now IT IS TOTALLY BRICKED, I can't turn it on and I can't even enter fastboot.
I really don't know what to do, do you have any idea?
Click to expand...
Click to collapse
09
Hello Community
I hope you can help me.
I bought the redmi note 10 5g a week ago, so far everything went well.
then I should do an update from miui 12.5 to miui 13 or from android 11 to android 12.
I did that but it hasn't been since the starter (also no recovery mode or fastboot mode)
when you want to start it, the redmi logo appears as if it were going to start normally, but then a gray "gravel stripe" appears in the bottom row of the screen and the cell phone restarts
if someone could help me what it could be I would be very grateful
lg
Mod edit - translated by https://www.deepl.com/translator
The SP Flash Tool solves this problem quickly, first use a bypass tool and then pass the ROM fastboot by sp flash Tool, already saved my phone many times with it and look that mine got much worse.
*****************************************************************
A ferramenta SP Flash Tool resolve esse problema rapidinho, primeiro use uma ferramenta de bypass Tool e depois passe a ROM fastboot pelo sp flash Tool, já salvei meu celular muitas vezes com ele e olha que o meu ficou muito pior.
Very important dont put All Format All + Download, you miss Imei + Barcode
Only use Download
Use SPFlash Tool 5.22 + Rom Full Aka Fastboot "camellian_global_images_V12.5.5.0.RKSMIXM_20220330.0000.00_11.0_global_8456991101" and Bypasser
if you dont enter to Recovery mi assistance
What do You mean with bypasser?
Toxictorben3 said:
Hello Community
I hope you can help me.
I bought the redmi note 10 5g a week ago, so far everything went well.
then I should do an update from miui 12.5 to miui 13 or from android 11 to android 12.
I did that but it hasn't been since the starter (also no recovery mode or fastboot mode)
when you want to start it, the redmi logo appears as if it were going to start normally, but then a gray "gravel stripe" appears in the bottom row of the screen and the cell phone restarts
if someone could help me what it could be I would be very grateful
lg
Click to expand...
Click to collapse
are you sure you cant enter into fastboot mode???? i have updated my phone from miui 12.5 via ota to miu13 without problems
Toxictorben3 said:
Hello Community
I hope you can help me.
I bought the redmi note 10 5g a week ago, so far everything went well.
then I should do an update from miui 12.5 to miui 13 or from android 11 to android 12.
I did that but it hasn't been since the starter (also no recovery mode or fastboot mode)
when you want to start it, the redmi logo appears as if it were going to start normally, but then a gray "gravel stripe" appears in the bottom row of the screen and the cell phone restarts
if someone could help me what it could be I would be very grateful
lg
Click to expand...
Click to collapse
the same case as I had a while ago.
What you do after that?
shinobusensui said:
Very important dont put All Format All + Download, you miss Imei + Barcode
Only use Download
Use SPFlash Tool 5.22 + Rom Full Aka Fastboot "camellian_global_images_V12.5.5.0.RKSMIXM_20220330.0000.00_11.0_global_8456991101" and Bypasser
if you dont enter to Recovery mi assistance
Click to expand...
Click to collapse
@Toxictorben3 this. But you should connect your phone into brom mode first.
because in the current state of your device, you can only enter brom mode.
@Toxictorben3 if you don't understand what I mean, and it's the first time doing this. better go to a service center, if your device is still under warranty.
Toxictorben3 said:
Hello Community
I hope you can help me.
I bought the redmi note 10 5g a week ago, so far everything went well.
then I should do an update from miui 12.5 to miui 13 or from android 11 to android 12.
I did that but it hasn't been since the starter (also no recovery mode or fastboot mode)
when you want to start it, the redmi logo appears as if it were going to start normally, but then a gray "gravel stripe" appears in the bottom row of the screen and the cell phone restarts
if someone could help me what it could be I would be very grateful
lg
Click to expand...
Click to collapse
Hi Dear
Flash with given link Mi Flash tool and given firmware version, its 100% solution. If your boot loader not unlocked inform me.
https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
https://bigota.d.miui.com/V12.5.3.0.RKSINXM/camellia_in_global_images_V12.5.3.0.RKSINXM_20220210.0000.00_11.0_in_7f8fba4c4c.tgz
Hi bro my bootloader is locked.. can You help me
Hi, I'm having the same problem. I can't connect to SP Flash Tools, it gives an error. Where am I wrong?
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
THINGS U HAD TO KNOW BEFORE FLASH:
DEVICE CODE: CAMELLIAN
BOOTLOADER UNLOCKED
A PC (WINDOWS BUT THE BEST IS LINUX) WITH XIAOMI DRIVERS ADB AND FASTBOOT INSTALLED
A BRAIN FOR USE GOOGLE AND FOLLOW STEP BY STEP THE FLASH GUIDES THAT YOU CAN FIND ON XDA OR OTHER THOUSANDS SITES
THE PROCEDURE ERASE ALL DATA
It all started when I decided to unroot my phone. First I backed up my data. Second, I formatted the cell phone directly through its settings. So root was removed. So far, everything was fine. The cell phone turned on normally and I did the initial settings. After that I decided to lock the bootloader again. I put the phone in bootloader mode and gave the command to block (Fasboot flashing lock). A confirmation message appeared on my cell phone and I accepted it. After that the phone was like this... Blinking at boot. I can't enter fasboot or bootloader through the buttons.
Heelp please!!
See the problem (video link)
Diguinho76 said:
It all started when I decided to unroot my phone. First I backed up my data. Second, I formatted the cell phone directly through its settings. So root was removed. So far, everything was fine. The cell phone turned on normally and I did the initial settings. After that I decided to lock the bootloader again. I put the phone in bootloader mode and gave the command to block (Fasboot flashing lock). A confirmation message appeared on my cell phone and I accepted it. After that the phone was like this... Blinking at boot. I can't enter fasboot or bootloader through the buttons.
Heelp please!!
See the problem (video link)
Click to expand...
Click to collapse
Pretty sure factory resetting the phone from the settings doesn't remove root. You root by flashing a patched boot.img but the factory reset doesn't touch the boot partition at all. So you locked the bootloader and now the phone won't boot because the boot partition is not signed by the OEM. If you can't enter bootloader mode you only have two solution.
- Flashing in EDL mode through MSM tool. However, since this phone OnePlus requires an authorized account to flash through MSM tool. You can try requesting a remote session through the official support (probably they won't do it) or find someone on telegram or somewhere else who sells tokens for MSM tool.
- Shipping the phone to OnePlus for repair or going to a local repair center of your choice.
Did you complete unninstalled magisk or just have formatted?
TheNewHEROBRINE said:
Pretty sure factory resetting the phone from the settings doesn't remove root. You root by flashing a patched boot.img but the factory reset doesn't touch the boot partition at all. So you locked the bootloader and now the phone won't boot because the boot partition is not signed by the OEM. If you can't enter bootloader mode you only have two solution.
- Flashing in EDL mode through MSM tool. However, since this phone OnePlus requires an authorized account to flash through MSM tool. You can try requesting a remote session through the official support (probably they won't do it) or find someone on telegram or somewhere else who sells tokens for MSM tool.
- Shipping the phone to OnePlus for repair or going to a local repair center of your choice.
Click to expand...
Click to collapse
I can't believe I did this... All I wanted was to remove root and I forgot to do it through magisk. I just ****ed myself
Diguinho76 said:
I can't believe I did this... All I wanted was to remove root and I forgot to do it through magisk. I just ****ed myself
Click to expand...
Click to collapse
Just to confirm, holding vol + and vol - together at boot doesn't do anything?
Machad3x said:
Did you complete unninstalled magisk or just have formatted?
Click to expand...
Click to collapse
No.... just formatted
TheNewHEROBRINE said:
Just to confirm, holding vol + and vol - together at boot doesn't do anything?
Click to expand...
Click to collapse
Nop. nothing
Diguinho76 said:
Nop. nothing
Click to expand...
Click to collapse
I just remembered that with this phone you can't boot into EDL mode by holding the volume buttons like in the old days. To get into EDL mode you would need to disassemble the phone and short two pins and I immagine you don't want to do that at all. There are some special cables that can boot Qualcomm phones into EDL, although I don't know if they work with the OP10 Pro specifically.
I think your best option at the moment is to send it for repair to OnePlus or to whichever repair center you prefer.
Diguinho76 said:
No.... just formatted
Nop. nothing
Click to expand...
Click to collapse
When you can not boot to booloader (fastboot) or fastbootd you need a Services Center (for flash over edl with msm tool )
I got it. Payed 15$ and a guy from vietnam solved the problem for me.
FIXED!!! Flashed over edl.
Diguinho76 said:
I got it. Payed 15$ and a guy from vietnam solved the problem for me.
FIXED!!! Flashed over edl.
Click to expand...
Click to collapse
How did you put the phone into EDL?
TheNewHEROBRINE said:
How did you put the phone into EDL?
Click to expand...
Click to collapse
Vol+ Vol- Power Button ( All of them at the same time) plugged on the pc
Diguinho76 said:
Vol+ Vol- Power Button ( All of them at the same time) plugged on the pc
Click to expand...
Click to collapse
ah so it still works! I thought it wouldn't.
TheNewHEROBRINE said:
ah so it still works! I thought it wouldn't.
Click to expand...
Click to collapse
But now im trying to go to 2213... I flashed a 2213 payload.bin from fastboot enhance and its not booting the system. I can acess bootloader. Do you have any suggestion to change the region from bootloader now ?
Diguinho76 said:
But now im trying to go to 2213... I flashed a 2213 payload.bin from fastboot enhance and its not booting the system. I can acess bootloader. Do you have any suggestion to change the region from bootloader now ?
Click to expand...
Click to collapse
I would have installed the update through the settings. I don't think switching slot can help this time. The only thing I think you can do is extract the payload.bin with payload-dumper-go and flash the partitions manually through fastboot but this procedure doesn't have a 100% success rate. If you write me the partitions you extracted from the payload.bin I can write you the commands to do as I'm not used to the partition layout of the 10 Pro specifically.
TheNewHEROBRINE said:
Eu teria instalado a atualização através das configurações. Eu não acho que mudar de slot pode ajudar desta vez. A única coisa que acho que você pode fazer é extrair o payload.bin com payload-dumper-go e atualizar as partições manualmente por meio do fastboot, mas esse procedimento não tem uma taxa de sucesso de 100%. Se você me escrever as partições extraídas do payload.bin, posso escrever os comandos a serem feitos, pois não estou acostumado com o layout da partição do 10 Pro especificamente.
Click to expand...
Click to collapse
Ok. Ill try. But do you know any way to do this using fastboot enhance ?
Diguinho76 said:
Ok. Ill try. But do you know any way to do this using fastboot enhance ?
Click to expand...
Click to collapse
When you flashed the payload.bin in fastboot enhance were you in fastbootd or bootloader mode?
TheNewHEROBRINE said:
When you flashed the payload.bin in fastboot enhance were you in fastbootd or bootloader mode?
Click to expand...
Click to collapse
fastbootd
Diguinho76 said:
fastbootd
Click to expand...
Click to collapse
I don't know why it has failed then. Can you still boot to fastbootd? Or does it say something like userspace not bootable?
TheNewHEROBRINE said:
I don't know why it has failed then. Can you still boot to fastbootd? Or does it say something like userspace not bootable?
Click to expand...
Click to collapse
Yes, i can. I tried to flash the payload again but havent success
Diguinho76 said:
Yes, i can. I tried to flash the payload again but havent success
Click to expand...
Click to collapse
In the fastboot mode the touch is not working. so i cant format data etc. Only buttons working