I am looking for a blank flash or alternative method for recovering my phone (Moto G8 Power). no bootloader, no fastboot, no recovery. only edl mod
Need help please
I AM DESPERATE TO FIND THE SOLUTION
need your help please?, I need a blank flash or a mmcblk0.img
Skib32 said:
I am looking for a blank flash or alternative method for recovering my phone (Moto G8 Power). no bootloader, no fastboot, no recovery. only edl mod
Need help please
I AM DESPERATE TO FIND THE SOLUTION
Click to expand...
Click to collapse
You can download the sofia blankflash package from lolinet:
https://mirrors.lolinet.com/firmware/moto/sofia/blankflash/
The one available is for the verizon variant.
Among other things, it includes the star binary that enables you to extract and recompile the components of singleimage.bin.
You will need the default.xml, index.xml, pkg.xml, and programmer.elf from the verizon singleimage.bin.
Then you will need the bootloader.img and gpt.bin from your current or newer software version, which you can also find on lolinet:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
You can use the star binary to extract the contents of bootloader.img, however you have to rename bootloader.img to singleimage.bin first.
Once you have the above mentioned components collected, you can use the star binary to compile them into a custom singleimage.bin.
See "star -help" for more on how to use.
Q9Nap said:
You can download the sofia blankflash package from lolinet:
https://mirrors.lolinet.com/firmware/moto/sofia/blankflash/
The one available is for the verizon variant.
Among other things, it includes the star binary that enables you to extract and recompile the components of singleimage.bin.
You will need the default.xml, index.xml, pkg.xml, and programmer.elf from the verizon singleimage.bin.
Then you will need the bootloader.img and gpt.bin from your current or newer software version, which you can also find on lolinet:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
You can use the star binary to extract the contents of bootloader.img, however you have to rename bootloader.img to singleimage.bin first.
Once you have the above mentioned components collected, you can use the star binary to compile them into a custom singleimage.bin.
See "star -help" for more on how to use.
Click to expand...
Click to collapse
Problem solved. thank you. don't try to use command fastboot set_active b in your moto g8 power
Skib32 can u help me ? im facing a similar problem
[QUOTE = "Skib32, publicación: 83645209, miembro: 6116259"]
Estoy buscando un flash en blanco o un método alternativo para recuperar mi teléfono (Moto G8 Power). sin cargador de arranque, sin arranque rápido, sin recuperación. solo edl mod
Necesito ayuda por favor
ESTOY DESESPERADO POR ENCONTRAR LA SOLUCIÓN
[/CITAR]
Hola, ¿sabes dónde están los puntos EDL del moto g8 power?
I made this blankflash for the RetBR variant, it should be what you need. And Q9nap, congratulations for the great explanation!
uwu1312 said:
[QUOTE = "Skib32, publicación: 83645209, miembro: 6116259"]
Estoy buscando un flash en blanco o un método alternativo para recuperar mi teléfono (Moto G8 Power). sin cargador de arranque, sin arranque rápido, sin recuperación. solo edl mod
Necesito ayuda por favor
ESTOY DESESPERADO POR ENCONTRAR LA SOLUCIÓN
[/CITAR]
Hola, ¿sabes dónde están los puntos EDL del moto g8 power?
Click to expand...
Click to collapse
Well, I have a slightly different situation, a user with Hardbrick, passed the device's blankflash, a more recent one, however, even after passing without errors, the device does not start in fastboot, this is something unusual for me because I have never seen a device that after a blankflash flash it did not start, even when passing without errors.
The most intriguing thing is that the owner of the device tried random blankflashes and with Hanna's he managed to start in fastboot, he didn't have the green robot but he still entered the fastboot screen, but with the device's own blankflash even after the blankflash flash, it's as if it remained in edl mode, it doesn't start.
Has anyone been through a similar situation and managed to resolve it?
Allexwin50 said:
Well, I have a slightly different situation, a user with Hardbrick, passed the device's blankflash, a more recent one, however, even after passing without errors, the device does not start in fastboot, this is something unusual for me because I have never seen a device that after a blankflash flash it did not start, even when passing without errors.
The most intriguing thing is that the owner of the device tried random blankflashes and with Hanna's he managed to start in fastboot, he didn't have the green robot but he still entered the fastboot screen, but with the device's own blankflash even after the blankflash flash, it's as if it remained in edl mode, it doesn't start.
Has anyone been through a similar situation and managed to resolve it?
Click to expand...
Click to collapse
I'm suffering the same thing, did you manage to solve it?
OBSCURO!!5 said:
I'm suffering the same thing, did you manage to solve it?
Click to expand...
Click to collapse
try to charge your battery for 1 or 2 hours
Skib32 said:
tente carregar sua bateria por 1 ou 2 horas
Click to expand...
Click to collapse
how to charge battery in hard brick?
Adonibezeque said:
how to charge battery in hard brick?
Click to expand...
Click to collapse
try blankflash first, and you can charge your moto g8 power when it pass.
Thank you so much @Q9Nap, you just saved my phone! To everyone else in this thread who wasn't successful yet: blankflash only works for the exact same model/region it was made for. Mine is RETEU so I had to build my own. Follow Q9Nap's tutorial and it'll work.
Q9Nap said:
You can download the sofia blankflash package from lolinet:
https://mirrors.lolinet.com/firmware/moto/sofia/blankflash/
The one available is for the verizon variant.
Among other things, it includes the star binary that enables you to extract and recompile the components of singleimage.bin.
You will need the default.xml, index.xml, pkg.xml, and programmer.elf from the verizon singleimage.bin.
Then you will need the bootloader.img and gpt.bin from your current or newer software version, which you can also find on lolinet:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
You can use the star binary to extract the contents of bootloader.img, however you have to rename bootloader.img to singleimage.bin first.
Once you have the above mentioned components collected, you can use the star binary to compile them into a custom singleimage.bin.
See "star -help" for more on how to use.
Click to expand...
Click to collapse
Thank you a lot, I was able to unbrick a hardbrick with your tips.
All I want is to recover my data, but I'm still stuck back where everything started: bootloop, bootloader locked, no ADB, sloots seems unbootable or /System may becorrupt.
Flashing stock rom didn't change the bootloop.
Can you help me with that?
here is my full post:
[REQUEST][RECOVER DATA][BOOTLOOP][SOFT BRICKED][LOCKED BOOTLOADER][SOFIAR][XT2041-1][ANDROID 11]Moto G8 Power - please help!
Moto G8 Power bricked alone (probably after an update). I need a help recovering the data please! -SOFIAR, XT2041-1, Android 11, SOFIAR RETAIL 11 RPES31.Q4U-47-35-11. - Soft bricked (bootloop). - Locked bootloader (oem_locked). - Adb/debugging...
forum.xda-developers.com
Allexwin50 said:
I made this blankflash for the RetBR variant, it should be what you need. And Q9nap, congratulations for the great explanation!
Click to expand...
Click to collapse
hello friend, my device of the RETBR moto g8 power variant I've done everything, I've installed the motorola drivers and the computer does not recognize the device, I also tried using ADB with the command "ADB DEVICES" and the computer does not recognize the device, can you or anyone help me?
Here i've created blankflash for Moto G8 Power RETAIL Argentina:
BlankFlash
BDGaamer said:
Here i've created blankflash for Moto G8 Power RETAIL Argentina:
BlankFlash
Click to expand...
Click to collapse
hello friends, it flashes correctly but it restarts with a white led without response. any solution? thanks geniuses
emmanuelsonn21. said:
hello friends, it flashes correctly but it restarts with a white led without response. any solution? thanks geniuses
Click to expand...
Click to collapse
Probá con este de ultima
BDGaamer said:
Aqui eu criei o blankflash para o Moto G8 Power RETAIL Argentina:
Flash em branco
Click to expand...
Click to collapse
Related
I got this tutorial online of network unlocking for Samsung Galaxy J1:
Tool's
Z3X Box
Micro usb cable
Procedure's:
Root Phone First tnx to orig. uploader
Odin (Odin3 v3.09) sorry iforgot d ss
power off your phone then (press home button + vol.down+ power w/ usb cable to enter the odin mode press vol. up. click AP and select boot.tar.md5 and tick start )
open SAMSUNG TOOL v18.9
select correct model (SM-J100H)
Read Info
Read Codes
Disconnect your phone insert local sim card
power on your phone and ENTER NET lock (DONE)
Click to expand...
Click to collapse
I flashed and rooted my phone according to the instructions. Now I can't unlock it because it needs a extra device or card. I've installed Samsung Tool v18.9 but as I don't have the card, it won't connect to my phone. It's a $120 phone, so I don't want to spend much to buy unlock code or buy a card! So, is there any way I can read the unlock info directly from my PC connecting to the phone without any extra device or card?
I apologize if the question was dumb...I'm new here. Thanks in advance!
Hi,
I would like to know if there is any unlocked ROM for the model Samsung Galaxy J1 (SM-J100H). I found multiple Rom's but all of them asked for a pin network unlock code.
Thanks.
Boas,
Gostaria de saber se há alguma ROM desbloqueada para o modelo Samsung Galaxy J1 (SM- J100H ) . Encontrei várias Rom mas todas pedem um código de desbloqueio de rede.
Obrigado.
I think you need an Samsung Galaxy J1 unlock code.
Hi!
Well, I have tested something on my friend's Amazfit and noticed interesting thing.
After getting to fastboot via buttons (so no commands in cmd) I accidentaly wiped everything, including bootloader, cause I thought it would wipe only data on watch.
Well, I thought I have bricked it for good. But found a way to get out from JZ4785 USB Boot Devic as that was detected in computer's devices (more instructions: here, works on Windows too)
So I flashed 4-file1.3.1m rom and after that I had unlocked bootloader and could install anything.
Maybe someone wants to try it, but be aware - it can possibly brick your device.
Correct me if I'm wrong but I believe the newer versions will only boot on the newer bootloader? So if you used this method and then with your now open bootloader flashed say the latest Paceified, it would update the bootloader and you would not be able to flash anything again?
Yes, it worked on watch with 1.3 version, so before new bootloader.https://forum.xda-developers.com/editpost.php?do=editpost&p=75508742
After flashing Pacified it became locked again.Just wanted to say that we have alternative method of unlocking bootloader that doesn't require 3rd party involvement.
But if we wipe bootloader and well... just have a straight device with SOC flash mode maybe it's possible to overcome the new bootloader? I don't have a spare watch to test it, so maybe someone can? It'd be like: You can't lock something you don't even have
hola, tengo un stratos 3 con el bootloader bloqueado, el codigo de desbloqueo no guardado, necesito generar un codigo nuevo, como lo puedo hacer?
ROM xiaomi.eu_multi_MINote2_8.8.30_v10-8.0(oreo)MIUI-WEEKLY-RELEASES
multilanguage
Installed and working very well
It no longer encrypts the data or the twrp
ROM xiaomi.eu_multi_MINote2_8.8.30_v10-8.0 for twrp: https://androidfilehost.com/?fid=1322778262903994652
regards
Thanks for sharing, will try it soon.
Flashing and testing done. Very fast responsive ui aand camera quality improved a lot!. Not gcam portrait Mode but very decent results with low noise and improved color quality and contrast. HAL 3 its not enabled by deafault and gcam still didnt work yet but 3.2 with HAL 3 enabled
bugs?
I installed this ROM and when restarting the phone showed a warning saying "phone locked". I can not put PIN to verify the phone with my "Mi" account and the phone is useless ...
Enviado desde mi MI Note 2 mediante Tapatalk
strumbol said:
I installed this ROM and when restarting the phone showed a warning saying "phone locked". I can not put PIN to verify the phone with my "Mi" account and the phone is useless ...
Enviado desde mi MI Note 2 mediante Tapatalk
Click to expand...
Click to collapse
It happened to me too. Ive just fixed puttin off the simcard and restart again without It. After that i put the sim again and restart and ley me put the sim Code for 2 seconds so you must be quick (if not try again till the phone lets you introduce your key) After that you are able put your password from Xiaomi account and let you finish the rest of the sinitial setup. If you Sony have a Xiaomi account you must get back to your ROM and create the account cos is a must.
Sorry for my terrible and crappy english
Soyerniji said:
It happened to me too. Ive just fixed puttin off the simcard and restart again without It. After that i put the sim again and restart and ley me put the sim Code for 2 seconds so you must be quick (if not try again till the phone lets you introduce your key) After that you are able put your password from Xiaomi account and let you finish the rest of the sinitial setup. If you Sony have a Xiaomi account you must get back to your ROM and create the account cos is a must.
Sorry for my terrible and crappy english
Click to expand...
Click to collapse
Thanks for your advice, but I've tried that and more... The problem is that my operator's APN does not exist in this ROM, so there is no internet connection. Also, when I press the button to configure the WiFi connection, the configuration screen is behind the "blocked phone" warning and is useless.
Enviado desde mi MI Note 2 mediante Tapatalk
strumbol said:
I installed this ROM and when restarting the phone showed a warning saying "phone locked". I can not put PIN to verify the phone with my "Mi" account and the phone is useless ...
Enviado desde mi MI Note 2 mediante Tapatalk
Click to expand...
Click to collapse
Same here!
I have to put the simcard pin súper fast
KahunaMoreno said:
Same here!
I have to put the simcard pin súper fast
Click to expand...
Click to collapse
Same here.
I had to install a previous Nougat ROM and then flash this ROM.
Also, anyone else with a Wear OS ROM, can you find your smartwatch with the app? I can't. The only way to connect the watch is just under the general configuration > Bluetooth, but as the device has not been added using the Wear OS app, it's useless. It happened to me also with other ROMs in this forum, and it's the reason why I always come back to the official releases from MIUI.
realjumy said:
Same here.
I had to install a previous Nougat ROM and then flash this ROM.
Also, anyone else with a Wear OS ROM, can you find your smartwatch with the app? I can't. The only way to connect the watch is just under the general configuration > Bluetooth, but as the device has not been added using the Wear OS app, it's useless. It happened to me also with other ROMs in this forum, and it's the reason why I always come back to the official releases from MIUI.
Click to expand...
Click to collapse
It doesn't ask you for mi account password on first boot with this rom?
I installed stock global beta 7.9.22 with Miflash and solve the problem, sim card is activated and Mi cloud working fine.
Now I'm not sure if it won't happen the same again if I install this update...
FontesR said:
It doesn't ask you for mi account password on first boot with this rom?
I installed stock global beta 7.9.22 with Miflash and solve the problem, sim card is activated and Mi cloud working fine.
Now I'm not sure if it won't happen the same again if I install this update...
Click to expand...
Click to collapse
It happened to me, but I went to a very old version, then applied the update. You will have to unlock your phone from your account if you want to avoid that message in the future.
Tried the ROM. Had the same thing happen 'activate account locked' ' activate wifi' activated wifi 1st then activated account 'already had permission'
Apart from minor Android 8.0 MIUI issues (region change from China locked. Developer options locks again with reboot an no Roehsoft ram expander-i just use swapper ram). No major issues.
Sticking with this ROM as it solves the Oreo playback volume issues.
ROM has zero sound issues.
I chose the globerom version as it gets the best bench's at room temp when cooled overnight.
Fantastic with zero overclock
Hello everyone, flashing the ROM no problem, when starting is a bit heavy. But I found a problem, for some reason the device's sensors do not work.
I hope they solve it in the future.
Using globe ROM version have some crashes here and there system tuner crashes from within app info pages. System ui crashes or stutters occasionally rebooting workings.
Like the new camera though.
sgt_peppers said:
Hello everyone, flashing the ROM no problem, when starting is a bit heavy. But I found a problem, for some reason the device's sensors do not work.
I hope they solve it in the future.
Click to expand...
Click to collapse
For me the gyro and the acceleration sensors were not working...
Gesendet von meinem Mi Note 2 mit Tapatalk
Wipe system data cache And dalvik...And last firmware of course if your last ROM were older
FontesR said:
It doesn't ask you for mi account password on first boot with this rom?
I installed stock global beta 7.9.22 with Miflash and solve the problem, sim card is activated and Mi cloud working fine.
Now I'm not sure if it won't happen the same again if I install this update...
Click to expand...
Click to collapse
It does, but when you press on the button to connect to the WiFi, previous to the login into your account, the message still overlays the content of the screen. This prevents you from selecting the WiFi and entering the credentials. I need to manually change the APN configuration before having internet from my SIM card, so I don't know if those with working data connection have the same problem.
realjumy said:
It does, but when you press on the button to connect to the WiFi, previous to the login into your account, the message still overlays the content of the screen. This prevents you from selecting the WiFi and entering the credentials. I need to manually change the APN configuration before having internet from my SIM card, so I don't know if those with working data connection have the same problem.
Click to expand...
Click to collapse
Yes, happened the same with me and my Sim don't connect automatically to network on boot. Really don't know how to fix this to install last rom update...
FontesR said:
Yes, happened the same with me and my Sim don't connect automatically to network on boot. Really don't know how to fix this to install last rom update...
Click to expand...
Click to collapse
Just unlink the phone from your MIUI accounts before flashing it...
tuve el mismo problema, pero no de esta ROM en concreto, sino al volver a cualquier ROM de miui desde otra ROM.
Solucion? ir a i.mi.com, loguearte y darle a find deice, cuando cargue, eliminas tu dospositivo de micloud, hecho esto, como no te deja conectarte a internet, tienes que flashear una rom antigua(yo use la primera estable que habia de miui8) hecho esto cuando arranca, te deja conectar a internet, comprueba el micloud y listo. Una vez hagas la configuracion inicial, ya puedes volver a borrar el movil e instalar esta version.
una vez configurado puedes volver activar el micloud.
Por algun motivo, en alguna parte de la memoria se almacena el micloud. Sorprendente para bien en seguridad, mal en cuanto al bug que no te permite conectarte al wifi para verificar que es tu movil.
English(translator).
I had the same problem, but not of this ROM in particular, but to return to any ROM of miui from another ROM.
Solution? go to i.mi.com, log in and give find deice, when you load, you delete your micloud dospositive, done this, since it does not let you connect to the internet, you have to flash an old rom (I used the first stable that I had to miui8) done this when it starts, lets you connect to the internet, check the micloud and voila. Once you do the initial configuration, you can re-delete the phone and install this version.
Once configured you can re-activate the micloud.
For some reason, micloud is stored somewhere in the memory. Surprising for good in security, bad in terms of the bug that does not allow you to connect to the Wi-Fi to verify that it is your cell phone.
Hi Guys.
After I bricked my phone during the first Android 11 rollout last year, I managed to restore my phone via EDL mode but immediately noticed that my fingerprint scanner does not work anymore.
It lights up when fingers put on to it but does not responds. Already flash the Mi A3 stock A11 ROM via fastboot but still the same.
Anybody knows how to fix this problem or anybody experiencing this problem also?
Thanks.
donedos said:
Hi Guys.
After I bricked my phone during the first Android 11 rollout last year, I managed to restore my phone via EDL mode but immediately noticed that my fingerprint scanner does not work anymore.
It lights up when fingers put on to it but does not responds. Already flash the Mi A3 stock A11 ROM via fastboot but still the same.
Anybody knows how to fix this problem or anybody experiencing this problem also?
Thanks.
Click to expand...
Click to collapse
@donedos
Try to downgrade to android 10 or unlock bootloader and install custom rom
Sherzaman Khan said:
@donedos
Try to downgrade to android 10 or unlock bootloader and install custom rom
Click to expand...
Click to collapse
He definitely should not do that! If he does he will hard brick again. You cannot revert back to a10 once stock a11 is installed.
garylawwd said:
He definitely should not do that! If he does he will hard brick again. You cannot revert back to a10 once stock a11 is installed.
Click to expand...
Click to collapse
@garylawwd
Bro When bootloader is unlocked Every thing is allowed!
Sherzaman Khan said:
@garylawwd
Bro When bootloader is unlocked Every thing is allowed!
Click to expand...
Click to collapse
I do believe you are misinformed here. You cannot downgrade from stock a11 to stock a10 without hard bricking your device.
Don't believe me? Then just try and give it a shot, you will hard brick your device 100%
You can downgrade from a10 to a9 no problems now but not from a11 to a10
Having an unlocked bootloader doesn't matter in this case xiaomi have implemented some sort of anti roll back which prevents you from downgrading even with the bootloader unlocked
garylawwd said:
I do believe you are misinformed here. You cannot downgrade from stock a11 to stock a10 without hard bricking your device.
Don't believe me? Then just try and give it a shot, you will hard brick your device 100%
You can downgrade from a10 to a9 no problems now but not from a11 to a10
Having an unlocked bootloader doesn't matter in this case xiaomi have implemented some sort of anti roll back which prevents you from downgrading even with the bootloader unlocked
Click to expand...
Click to collapse
@garylawwd
Ok agreed
Hi, this is a bit offtopic, but how did you flashed from EDL? do you know if that fix is only for A11 brick or does it work for "other brick reasons"?
@Bysholo
Yes flash with qcom sahara flash if pc detect qdloader.
More search on youtube edl flash mi a3
donedos said:
Hi Guys.
After I bricked my phone during the first Android 11 rollout last year, I managed to restore my phone via EDL mode but immediately noticed that my fingerprint scanner does not work anymore.
It lights up when fingers put on to it but does not responds. Already flash the Mi A3 stock A11 ROM via fastboot but still the same.
Anybody knows how to fix this problem or anybody experiencing this problem also?
Thanks.
Click to expand...
Click to collapse
Hello, I'm from Brazil and I have the same problem after recovering my phone via EDL. I already tested with custom rom and the same problem continues.
did you have any solution?
An easy fix; just don't use the fingerprint function.
I have never used the one on my 10+, lol don't even know if it functions
Personally I don't see this an issue but it is suspicious. Is it clean?
That be my only concern...
donedos said:
Hi Guys.
After I bricked my phone during the first Android 11 rollout last year, I managed to restore my phone via EDL mode but immediately noticed that my fingerprint scanner does not work anymore.
It lights up when fingers put on to it but does not responds. Already flash the Mi A3 stock A11 ROM via fastboot but still the same.
Anybody knows how to fix this problem or anybody experiencing this problem also?
Thanks.
Click to expand...
Click to collapse
Hello, I managed to solve the problem, follow the tutorial:
enter the phone dialer and enter the following code: * # * # 64663 # * # *
then press on the 3 points above and go to FingerPrint_C
Press on start, then it will ask to put "FLESH_FLAT" you need to put a white sheet on the sensor and support with your finger on top of the sensor.
then you will ask to put "BLACK_FLAT", then you put something black on the sensor and support it with your finger, after completing just restart the cell phone.
* Gave me a "performance_test failed" error, but after a few attempts the calibration worked and the sensor returned to work.
*Only in Stock ROM.
Sorry for my bad English.
Essentially your calabrating the sensor.
Pcb1997 said:
Hello, I managed to solve the problem, follow the tutorial:
enter the phone dialer and enter the following code: * # * # 64663 # * # *
then press on the 3 points above and go to FingerPrint_C
Press on start, then it will ask to put "FLESH_FLAT" you need to put a white sheet on the sensor and support with your finger on top of the sensor.
then you will ask to put "BLACK_FLAT", then you put something black on the sensor and support it with your finger, after completing just restart the cell phone.
* Gave me a "performance_test failed" error, but after a few attempts the calibration worked and the sensor returned to work.
*Only in Stock ROM.
Sorry for my bad English.
Click to expand...
Click to collapse
Thanks bro.
This is legit. I've been looking for a solution to this problem. My fingerprint is now working perfectly.
thank you so much.
Pcb1997 said:
Hello, I managed to solve the problem, follow the tutorial:
enter the phone dialer and enter the following code: * # * # 64663 # * # *
then press on the 3 points above and go to FingerPrint_C
Press on start, then it will ask to put "FLESH_FLAT" you need to put a white sheet on the sensor and support with your finger on top of the sensor.
then you will ask to put "BLACK_FLAT", then you put something black on the sensor and support it with your finger, after completing just restart the cell phone.
* Gave me a "performance_test failed" error, but after a few attempts the calibration worked and the sensor returned to work.
*Only in Stock ROM.
Sorry for my bad English.
Click to expand...
Click to collapse
Thanks dude it's work, I can't find any solution for this since hard brick at new year, thanks again
Pcb1997 said:
Hello, I managed to solve the problem, follow the tutorial:
enter the phone dialer and enter the following code: * # * # 64663 # * # *
then press on the 3 points above and go to FingerPrint_C
Press on start, then it will ask to put "FLESH_FLAT" you need to put a white sheet on the sensor and support with your finger on top of the sensor.
then you will ask to put "BLACK_FLAT", then you put something black on the sensor and support it with your finger, after completing just restart the cell phone.
* Gave me a "performance_test failed" error, but after a few attempts the calibration worked and the sensor returned to work.
*Only in Stock ROM.
Sorry for my bad English.
Click to expand...
Click to collapse
Thank you very much, this was really the thread's question and with it solved.
Hi Guys.
I've tried this alternative but i keep getting this performance_test failed. Does any one can help me describing what kind of white/black sheet you used? It is a thick sheet, thin sheet??? I need to press my finger strongly or just soft???
Thanks.
Pure genius! My fingerprint sensor was defunct for more than a year now, now restored. Many thanks!!!!
Help, Guys ....
Pcb1997 said:
Olá, consegui resolver o problema, siga o tutorial:
digite o discador do telefone e digite o seguinte código: * # * # 64663 # * # *
em seguida, pressione os 3 pontos acima e vá para FingerPrint_C
Pressione em start, então vai pedir para colocar "FLESH_FLAT" você precisa colocar uma folha branca no sensor e apoiar com o dedo em cima do sensor.
então você vai pedir para colocar "BLACK_FLAT", aí você coloca algo preto no sensor e apóia com o dedo, após completar basta reiniciar o celular.
* Gerou um erro "performance_test failed", mas depois de algumas tentativas, a calibração funcionou e o sensor voltou a funcionar.
* Somente em estoque ROM.
Desculpe pelo meu péssimo inglês.
Click to expand...
Click to collapse
Thank you man, I was trying to find solutions for a long time, luckily this procedure worked out, thank you very much
leonardo_evaldy said:
Socorro pessoal ....
Click to expand...
Click to collapse
Então, eu tive um pouco de dificuldade no começo devido à repetição do erro "performance_test falhou", mas dps insistir muito que funcionou, sugiro colocar o papel logo após clicar no próximo, usei white paper legal padrão a4 , para o preto usei um papel mais rígido, não apliquei muita força. Espero que você chegue aí mano boa sorte
Desculpe pelo péssimo inglês, (nós)
Hi guys, managed to recalibrate the sensor but still no luck in recognising the finger print. Any other suggestions? Flashed to standard Rom via EDL and then auto updated to September A11 updates.
Hey Guys,
i have the Redmi 9S Curtana Smartphone. Buyed in Germany. So i dont know if i have Global or Europe Version.
Modelnumber on the Backside: M2003J6A1G
I had Lineageos 18.1 official installed with Lineageos 18.1 Recovery along with it.
Today i decided to install MIUI again.
Used Miflash Tool and curtana_global_images_V12.5.4.0.RJWMIXM_20220211.0000.00_11.0_global_c3215d4c09.tgz
And now i have a Bootloop that i cant fix. (it shows "Redmi powered by android", vibrates, and then restarts)
Even if i reinstall lineageos recovery and then lineageos self, boot loop still persists...
Tried XiaoMiTool V2 too. Tried other recoverys and ROMs. No single one works any more.
Could somebody help me?
Thanks.
tomekk228 said:
Hey Guys,
i have the Redmi 9S Curtana Smartphone. Buyed in Germany. So i dont know if i have Global or Europe Version.
Modelnumber on the Backside: M2003J6A1G
I had Lineageos 18.1 official installed with Lineageos 18.1 Recovery along with it.
Today i decided to install MIUI again.
Used Miflash Tool and curtana_global_images_V12.5.4.0.RJWMIXM_20220211.0000.00_11.0_global_c3215d4c09.tgz
And now i have a Bootloop that i cant fix. (it shows "Redmi powered by android", vibrates, and then restarts)
Even if i reinstall lineageos recovery and then lineageos self, boot loop still persists...
Tried XiaoMiTool V2 too. Tried other recoverys and ROMs. No single one works any more.
Could somebody help me?
Thanks.
Click to expand...
Click to collapse
IDK if you already did it, you should use format data.
Try with other ROM version
SubwayChamp said:
IDK if you already did it, you should use format data.
Click to expand...
Click to collapse
Have it done it every time. No luck with that.
SubwayChamp said:
Try with other ROM version
Click to expand...
Click to collapse
I try a Android 10 Miui one, and then i give report.
Ok, tried now to Flash curtana_global_images_V11.0.3.0.QJWMIXM_20200318.0000.00_10.0_global with no luck.
All Flashtools says that the Device is locked. And cant unlock again because MIUI dont boot...
Edit:
Tried it anyway:
{
"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"
}
tomekk228 said:
Ok, tried now to Flash curtana_global_images_V11.0.3.0.QJWMIXM_20200318.0000.00_10.0_global with no luck.
All Flashtools says that the Device is locked. And cant unlock again because MIUI dont boot...
Edit:
Tried it anyway:
View attachment 5584687
Click to expand...
Click to collapse
It seems you did relock your device. As it is locked, can't be flashed through fastboot, only EDL, but you probably need an authorized account to use Mi Flash tool.
SubwayChamp said:
It seems you did relock your device. As it is locked, can't be flashed through fastboot, only EDL, but you probably need an authorized account to use Mi Flash tool.
Click to expand...
Click to collapse
So, i can throw it into garbage... I already searched in the internet, the repair cost to much. for that money i can get a new one...
But that wasnt the goal. Indeed i relocked it. The Goal was to reflash it to stock MIUI ROM (wich is really easy and already did it with the note 8 one in the past), and to sell it, because i got a new phone.
So, **** happens
tomekk228 said:
So, i can throw it into garbage... I already searched in the internet, the repair cost to much. for that money i can get a new one...
But that wasnt the goal. Indeed i relocked it. The Goal was to reflash it to stock MIUI ROM (wich is really easy and already did it with the note 8 one in the past), and to sell it, because i got a new phone.
So, **** happens
Click to expand...
Click to collapse
Actually is very tricky to flash a Xiaomi powered with Qualcomm, specially when the bootloader is locked, even in unlocked devices, sometimes is required an authorized account to proceed to flash.
It is highly advised to not re-lock bootloader when attempting to recover the device, otherwise you'll be forced to use only EDL mode.
I had similar problem, goes to bootlop after flashing.
my problem is now the device show FASTBOOOT on the screen but the device is not propery in fastboot mode because if i try to do same fasboot command the prompt show me <waiting for device>
alessio.bacconi said:
I had similar problem, goes to bootlop after flashing.
my problem is now the device show FASTBOOOT on the screen but the device is not propery in fastboot mode because if i try to do same fasboot command the prompt show me <waiting for device>
Click to expand...
Click to collapse
It's not that your device "is not properly in fastboot" most likely, that you need to update the drivers correctly, so your PC can detect your device.
no, there is no unknow peripheral on the pc
alessio.bacconi said:
no, there is no unknow peripheral on the pc
Click to expand...
Click to collapse
This may mean drivers are not installed or missed. Instead, you have to see if there is some hardware variations while you attach the device to the PC.
Find the problem, open the mobile and was broken the flat from usb to the mainboard
Hello guys i have a problem with a redmi note 9s (curtana) is in loop! And the bootloader is locked (no mi account) yesterday star with the loop he has the miui 12.5, today i can install miui 13 until several wipes and plug on the pc, everithing does ok but when i turn off start again with the problem and i wish no to wipe again anybody knows how can it be? Thanks im new user in this amazing comunity
tomekk228 said:
Assim, posso jogar no lixo... Já pesquisei na internet, o conserto custou caro. com esse dinheiro posso comprar um novo...
Mas esse não era o objetivo. Na verdade, eu o bloqueei novamente. O objetivo era reflash para armazenar MIUI ROM (o que é muito fácil e já fiz isso com o note 8 no passado) e vendê-lo, porque ganhei um telefone novo.
Então, **** acontece
Click to expand...
Click to collapse
Eu consigo recuperar seu aparelho, porém tem um custo do apk que eu utilizo, cerca de $25 /30 usd , depende da situação que seu celular ficou
SubwayChamp said:
It seems you did relock your device. As it is locked, can't be flashed through fastboot, only EDL, but you probably need an authorized account to use Mi Flash tool.
Click to expand...
Click to collapse
from where i would get an authorized account
Azee9822 said:
from where i would get an authorized account
Click to expand...
Click to collapse
Usually, they are paid-services.
You didn't mention in this post which device you have, this would ease the answer, anyway, if you have a MediaTek device, actually, you, eventually, wouldn't need it, but, if you have a Qualcomm device, you may search for a "Patched firehose file for your device model/the code name of your device model", and you'll find something like this example https://www.bypassfrpfiles.com/2022/12/redmi-note-9s-no-auth-loader-firehose-file/ Or, you can search for an engineering ROM/firmware for your device model/the code-name of your device model, sometimes the ENG ROM contains no restrictions for flashing.
SubwayChamp said:
Usually, they are paid-services.
You didn't mention in this post which device you have, this would ease the answer, anyway, if you have a MediaTek device, actually, you, eventually, wouldn't need it, but, if you have a Qualcomm device, you may search for a "Patched firehose file for your device model/the code name of your device model", and you'll find something like this example https://www.bypassfrpfiles.com/2022/12/redmi-note-9s-no-auth-loader-firehose-file/ Or, you can search for an engineering ROM/firmware for your device model/the code-name of your device model, sometimes the ENG ROM contains no restrictions for flashing.
Click to expand...
Click to collapse
my cell phone is redmi note 9s, i already tried this method and i was not successful
roohdriguinho10 said:
my cell phone is redmi note 9s, i already tried this method and i was not successful
Click to expand...
Click to collapse
A post without the exact description of your issue, won't help you at all, also for other users to try to help you.
Based on what, we can add something?
Just to know it, If the eMMC/motherboard is not damaged, at hardware level, it is fixable in a 100%.
SubwayChamp said:
Usually, they are paid-services.
You didn't mention in this post which device you have, this would ease the answer, anyway, if you have a MediaTek device, actually, you, eventually, wouldn't need it, but, if you have a Qualcomm device, you may search for a "Patched firehose file for your device model/the code name of your device model", and you'll find something like this example https://www.bypassfrpfiles.com/2022/12/redmi-note-9s-no-auth-loader-firehose-file/ Or, you can search for an engineering ROM/firmware for your device model/the code-name of your device model, sometimes the ENG ROM contains no restrictions for flashing.
Click to expand...
Click to collapse
Yeah bro i had redmi note 9s curtana, thanks men i'll search for it too
SubwayChamp said:
A post without the exact description of your issue, won't help you at all, also for other users to try to help you.
Based on what, we can add something?
Just to know it, If the eMMC/motherboard is not damaged, at hardware level, it is fixable in a 100%.
Click to expand...
Click to collapse
I had redmi note 9S ( curtana ), which eventually turn off of it's own & stuck to black screen only led blink upon connecting charger, hence it's also not going to fastboot or recovery mode, therefore i used EDL mode to flash but mi flash tool gives edl authentication error although even after login it's not flashing.