Database Develop

Nougat on N920G

I've tried upgrading to Nougat with the Bangladesh firmware via Odin. Whenever I try, the following error appears:
{
"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"
}
After that, I turn on the N920G and it asks me to try to recover the mobile with Smart Switch (and it does not work). I can only use it by flashing Marshmallow again.
Any solution?

I happen exactly the same, probe to install the nougat India version and always the same error, I have the 920G, I am from Argentina.
As far as I read the 920G latin america would not be compatible with this version ....
regards

superchizo said:
I happen exactly the same, probe to install the nougat India version and always the same error, I have the 920G, I am from Argentina.
As far as I read the 920G latin america would not be compatible with this version ....
regards
Click to expand...
Click to collapse
Yo también soy de Argentina. En el foro de Sammobile, uno de los moderadores me dijo que al parecer hace falta flashear el firmware junto con el PIT, pero no me da mucha confianza hacerlo y no lo veo necesario para actualizar a Nougat
---
I'm from Argentina, too. In the Sammobile forum, one of the moderators told me that I seem to need to flash the firmware together with the PIT, but it does not give me much confidence to do so and I do not see it necessary to upgrade to Nougat

axelitooavila said:
Yo también soy de Argentina. En el foro de Sammobile, uno de los moderadores me dijo que al parecer hace falta flashear el firmware junto con el PIT, pero no me da mucha confianza hacerlo y no lo veo necesario para actualizar a Nougat
Click to expand...
Click to collapse
estoy de acuerdo, no creo que se justifique probar instalando un PIT, tiene que haber otra solución, no entiendo por que no funciona si es el mismo modelo, la primera vez que me pasa algo asi.
También probé de instalar la 6.0.1 India y después hacer el upgrade por OTA, pero tampoco funciono, me dio el mismo error que al tratar de instalar la nougat directamente, asi que no creo que instalando el PIT funcione.
Si te enteras de alguna forma de realizar el upgrade avisame, me mata la ansiedad.... ejejejeje.
Saludos,
I agree, I do not think it is justified to try installing a PIT, there has to be another solution, I do not understand why it does not work if it is the same model, the first time something like that happens to me.
I also tried to install 6.0.1 India and then upgrade to OTA, but it did not work either, it gave me the same error as when trying to install nougat directly, so I do not think installing PIT works.
If you find out some way to do the upgrade, let me know, it kills my anxiety .... ejaculation.
Regards,

superchizo said:
I happen exactly the same, probe to install the nougat India version and always the same error, I have the 920G, I am from Argentina.
As far as I read the 920G latin america would not be compatible with this version ....
regards
Click to expand...
Click to collapse
superchizo said:
estoy de acuerdo, no creo que se justifique probar instalando un PIT, tiene que haber otra solución, no entiendo por que no funciona si es el mismo modelo, la primera vez que me pasa algo asi.
También probé de instalar la 6.0.1 India y después hacer el upgrade por OTA, pero tampoco funciono, me dio el mismo error que al tratar de instalar la nougat directamente, asi que no creo que instalando el PIT funcione.
Si te enteras de alguna forma de realizar el upgrade avisame, me mata la ansiedad.... ejejejeje.
Saludos,
I agree, I do not think it is justified to try installing a PIT, there has to be another solution, I do not understand why it does not work if it is the same model, the first time something like that happens to me.
I also tried to install 6.0.1 India and then upgrade to OTA, but it did not work either, it gave me the same error as when trying to install nougat directly, so I do not think installing PIT works.
If you find out some way to do the upgrade, let me know, it kills my anxiety .... ejaculation.
Regards,
Click to expand...
Click to collapse
Solo queda esperar y ver si hay una solución
---
Just wait and see if there is a solution

Trataron abriendo en el Note la opcion de desarrollador y desbloqueando el USB Debugging?
Have u tried enabling developer options, and USB debugging?

Ferxcito said:
Trataron abriendo en el Note la opcion de desarrollador y desbloqueando el USB Debugging?
Have u tried enabling developer options, and USB debugging?
Click to expand...
Click to collapse
por lo menos yo lo probe y no funciono,
Desbloqueo de OEM y depuracion de USB, me arroja el mismo error.
--
At least I tried it and it did not work,
Unlock OEM and USB debugging, I throw the same error.

superchizo said:
por lo menos yo lo probe y no funciono,
Desbloqueo de OEM y depuracion de USB, me arroja el mismo error.
--
At least I tried it and it did not work,
Unlock OEM and USB debugging, I throw the same error.
Click to expand...
Click to collapse
Then we are lost =(
On the same post and video they said that u need to open or unblock the Bootloader with some kind of command.
Im unnable to do it atm.

axelitooavila said:
I've tried upgrading to Nougat with the Bangladesh firmware via Odin. Whenever I try, the following error appears:
After that, I turn on the N920G and it asks me to try to recover the mobile with Smart Switch (and it does not work). I can only use it by flashing Marshmallow again.
Any solution?
Click to expand...
Click to collapse
Did you try downloading the firmware from this software? (https://www.androidsage.com/2016/03...firmware-files-directly-from-samsung-servers/)
It seems your firmware is corrupt while downloading. Try to Flash it again.

If you read changelog you can see
1.md5 checking finished successfully
This means download is not corrupt. When you flash any file ending with .md5 with odin, it never flash if file is corrupted and will throw error - md5 mismatched, flashing aborted.
2.Bootloader,kernel and recovery flashed successfully
Usually bootloader samsung makes blacklisted for some device and that can fail but here that is not the case as it was already flashed accoeding odin log
3.Flashing failed at system.img
Common cause is sometimes system.img size varies on different regional model though model is same. So in case you are flashing a Bangladesh ROM on on other region device it can fail
Flashing with pit (must be from same region you are trying to flash ROM) will change partition size and that may able to finish system.img in case said is the reason. Keep in mind flashing md5 should be keep reserve only to revive device in case of soft brick
Recommend
- Flash ROM from same region of device
- Flash with pit in case of device and ROM are from same region and still giving error.

ROM Resurrection Remix Android P GSI para Moto Z2 Play

{
"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"
}
Resurrection Remix P
Hello team, I share the great work you have done to make the GSI Resurrection Remix already with some of the Fix collected in this forum with the rom havooc:
The installation method is quite simple like any GSI:
• Install Treeble recovery.
• Make Wipes
• Install RR Oreo Treeble
• install image RR Android P as system Image
• Install oreo kernel
• and restart normally
• Once the restart is complete, go back to the recovery and install GAAPS nano android 9 arm64
• After that if you like you can install Magisk and ready
What will not work in the first instance are:
• Rotation
• camera and flash light
• gestures on sensor
but do not worry here I'll leave you the fix
for rotation, copy the sensor folder that I leave here in the path of / system / etc and place the permissions 0755 for the folder and 0644 for the files inside the folder
For camera copy the file Lib_mot_app6_metadata.so in the path in / vendor / lib and place permissions 0644
Par manager in sensor sticks the usr folder that I leave you in the path / vendor keeping the permissions for 0755 folder and for the files contained in 0644
and ready restart and you will have to enjoy this wonderful rom
if you like you can install Gcam for better camera experience
A STRONG EMBRACING AND APPRECIATION TO THE DEVELOPERS WHO ACHIEVED TO DO THIS POSSIBLE

Wow. how is battery compare to oreo?

I've been using it for the past two days. I think the system still need some uptime for the new battery management really kicks in but I think that's already better than Oreo. Specially on standby

+1 better than oreo in standby. On august ppr1 I've got a great sot
Inviato dal mio Moto Z2 Play utilizzando Tapatalk

Now, I've installed, almost everything works. Good Job.
Bugs:
- Clock widgets are unavaiable
- how to disable fp gestures without unlocking?

Grande aporte amigo, llevo tiempo siguiendo tus post por G+, el único problema es que los moto mods no funcionan
crees que en alguna update funcione ?
-excelente duración de batería

For anyone running the gsi: download the Kernel adiutor app and check the battery tab. Anyone else getting a 4000 mAh battery reported?

Castro27 said:
For anyone running the gsi: download the Kernel adiutor app and check the battery tab. Anyone else getting a 4000 mAh battery reported?
Click to expand...
Click to collapse
+1 I get 1000 mAh battery

ujtsan said:
Grande aporte amigo, llevo tiempo siguiendo tus post por G+, el único problema es que los moto mods no funcionan
crees que en alguna update funcione ?
-excelente duración de batería
Click to expand...
Click to collapse
Gracias se hace lo que se puede..!! hasta el momento no he visto en algun GSI espero en algun update salga algo, en la havooc funcionan los gestos de shok shok de la lampara y la camara es el mismo procedimiento de RR pero con la imagen de havooc, si gustas te paso la IMG , es la que llevo actualmente en mi movil.

In the "install image RR Android P as system Image" link there are 3 files, which one should I get?
En el 4to paso, cual de los 3 archivos img tengo que bajar, o son los 3?

ramelco said:
In the "install image RR Android P as system Image" link there are 3 files, which one should I get?
En el 4to paso, cual de los 3 archivos img tengo que bajar, o son los 3?
Click to expand...
Click to collapse
Y en lo del kernel como lo hago por que después del restart regresa a modo boot loader

Gamboa13 said:
Y en lo del kernel como lo hago por que después del restart regresa a modo boot loader
Click to expand...
Click to collapse
Try this one system-190120-arm64-aonly-vanilla-nosu.img you'll boot to bootloader if you flash the wrong one.
twrp treble
oreo treble
system-190120-arm64-aonly-vanilla-nosu.img on system partition
boot-radium-fpkeys on boot partition

Please discuss in english.

After installing the system img, i restart but a decription error msg appear asking forma a password. Entering any word make it restarts and again, the same error. Any help please?

I installed everything perfect. THANK YOU

Dj_AlexBarrera said:
Instalé todo perfecto... pero las opengapps me estan dando problema... no sé porqué.
1. Primero de dió error 70 y lo solucione reparando el sistema de archivos.
2. Ahora me salió error 20 y no tengo idea que es eso...
Agradezco si alguien puede ayudarme. GRACIAS
Click to expand...
Click to collapse
Dice que tienes una room como de nougat,por la versión..
Yo la instale después de pasarlo a oreo y no tuve problema en la instalación,pero si esta lenta...
---------- Post added at 04:50 AM ---------- Previous post was at 04:46 AM ----------
juanepichio said:
Try this one system-190120-arm64-aonly-vanilla-nosu.img you'll boot to bootloader if you flash the wrong one.
twrp treble
oreo treble
system-190120-arm64-aonly-vanilla-nosu.img on system partition
boot-radium-fpkeys on boot partition
Click to expand...
Click to collapse
Bello,again..i installed without problem, but when run system ROM this slow..someone solution...

lsolis293 said:
Gracias se hace lo que se puede..!! hasta el momento no he visto en algun GSI espero en algun update salga algo, en la havooc funcionan los gestos de shok shok de la lampara y la camara es el mismo procedimiento de RR pero con la imagen de havooc, si gustas te paso la IMG , es la que llevo actualmente en mi movil.
Click to expand...
Click to collapse
Could you sharebus the IMG, please?

please write in english, xda has rules about this / por favor escriban en inglés, xda tiene reglas sobre esto.
just try to follow instructions as noted on first post. let me explain a bit how I did it:
1- flash treble recovery
2- make wipes, how to do this?
a. first, format data, then restart to recovery
b. second, wipe each partition except micro-sd (i'm assuming your files are there), then restart to recovery again
3- flash RR oreo treble
4- flash RR android P image on /system partition
5- flash oreo kernel image on /boot partition
6- restart, mandatory. you won't have navigation bar or fingerprint gestures, let the system boot.
7- after first boot, reboot to recovery and flash gapps nano android 9 arm64
8- enable navigation bar by going to settings > resurrection tools > navigation tab > navigation > enable navigation bar. if not present then you'll have to do it by build.prop or manage yourself to get fingerprint gestures working by copying usr folder. this can be done rooting and using a file manager or doing it all on twrp file manager.
to get root working: install MagiskManager-v6.1.0.apk (can be found on magisk forum), then reboot to recovery and flash Magisk-v18.0.zip
8- fingerprint gestures: extract usr.zip and copy usr folder to /vendor folder on root
9- camera: extract libs.zip and copy both files to /vendor/lib
10- rotation sensors: extract sensors.zip and copy sensor folder to /system/etc
make sure permissions for folders and files are set ok: 0755 on folders, 0644 on files
hey, give it some time. you will find yourself on doing trial/error to understand how to follow each step and make them work but I assure you it works.

ramelco said:
In the "install image RR Android P as system Image" link there are 3 files, which one should I get?
En el 4to paso, cual de los 3 archivos img tengo que bajar, o son los 3?
Click to expand...
Click to collapse
Our Moto z2 play is arm64 with A only

First flash rom, then reboot system. Then reebot recovery and flash gapps.
Dj_AlexBarrera said:
Instalé todo perfecto... pero las opengapps me estan dando problema... no sé porqué.
1. Primero de dió error 70 y lo solucione reparando el sistema de archivos.
2. Ahora me salió error 20 y no tengo idea que es eso...
Agradezco si alguien puede ayudarme. GRACIAS
Click to expand...
Click to collapse
Inviato dal mio Moto Z2 Play utilizzando Tapatalk

g.co/ABH

SOLVED: This happens when one flashes V2.x(EU) images to V1.x(NON-EU) phones! See below.
NX627J keeps indicating "<!>\nYour device is corrupt. It can't be trusted and will not boot\nVisit this link on another device:\ng.co/ABH" after I've attempted to flash magisk, since then all attempts to flash Official ROMs downloaded from nubia.com don't change the condition. I've emailed [email protected] and am awaiting a reply. It's been since late Friday.
I fixed my phone. I was using V2.x files, but my phone is V1.x. The major version numbers are more like part of the model number than like a version indicator. Here is the full dump where I got the boot and recovery images, it's 2.2GB compressed
https://www.filehosting.org/file/details/835328/NX627J_NubiaEmergencyDownload_V103.7z
I'll try and post just the boot/recovery images here: https://mikemestnik.net/archives/
Code:
SHA256 (NX627J_NubiaEmergencyDownload_V103.7z) = bd412eeab191c001a4ee5b11bda8a2ec7273257ccd2e1d024e60e8c6a1bd174b
SHA256 (NX627J-stock-1_03.7z) = f53a120dc7e8029bf2bb0fb7a462d027376d63bb39e4b7f2ae2f55ae2bcba9ae

Por si te sirve, a mí me ocurrió lo mismo y lo solucione flasheando por ADB el Boot.img "fastboot flash boot boot.img" y el recovery.img "fastboot flash recovery recovery.img" de la ROM que tenía instalada en el momento de flashear magisk, que era la Global 203. Después de eso me permitió acceder al recovery original de nubia de nuevo y desde ahí con un USB por OTG le instale la ROM CN 2.21 y desde ahí ya lo puedes volver a actualizar a la versión global si quieres.
Espero que te sirva.
Saludos

newdroy said:
Por si te sirve, a mí me ocurrió lo mismo y lo solucione flasheando por ADB el Boot.img "fastboot flash boot boot.img" y el recovery.img "fastboot flash recovery recovery.img" de la ROM que tenía instalada en el momento de flashear magisk, que era la Global 203. Después de eso me permitió acceder al recovery original de nubia de nuevo y desde ahí con un USB por OTG le instale la ROM CN 2.21 y desde ahí ya lo puedes volver a actualizar a la versión global si quieres.
Espero que te sirva.
Saludos
Click to expand...
Click to collapse
Why doesn't XDA do the translation?
newdroy said:
In case it works for you, the same thing happened to me and I solved it by flashing ADB the Boot.img "fastboot flash boot boot.img" and the recovery.img "fastboot flash recovery recovery.img" of the ROM that was installed in the moment of flashing magisk, which was Global 203. After that it allowed me to access the original nubia recovery again and from there with a USB by OTG I installed the CN 2.21 ROM and from there you can update it back to the version Global if you want.
Hope this can help you.
Cheers
Click to expand...
Click to collapse
It may be laughable but I wasn't expecting to flash the system, just the boot. I would like to avoid erasing my system. This is Android after all and without root there aren't any backup systems, so you'll have to forgive me for not having one.
I found 3 versions of OEM boot.img and flashed them all without success. Recovery works.

I fixed my phone. I was using V2.x files, but my phone is V1.x. The major version numbers are more like part of the model number than like a version indicator. Here is the full dump where I got the boot and recovery images, it's 2.2GB compressed
https://www.filehosting.org/file/details/835328/NX627J_NubiaEmergencyDownload_V103.7z
I'll try and post just the boot/recovery images here: https://mikemestnik.net/archives/
Code:
SHA256 (NX627J_NubiaEmergencyDownload_V103.7z) = bd412eeab191c001a4ee5b11bda8a2ec7273257ccd2e1d024e60e8c6a1bd174b
SHA256 (NX627J-stock-1_03.7z) = f53a120dc7e8029bf2bb0fb7a462d027376d63bb39e4b7f2ae2f55ae2bcba9ae

Hi, I have the same problem when trying to update from V2.03 Encommon to V2.21 Encommon. How could I fix that? Tks alot!

Can you explain the full process

My Nubia z20 phone is corrupt
How to solve this problem? Please suggest me. And fastboot links or flashtool links please send me. Total process send me step by step please.

HELP please
Hi, I have the same problem with this f*****g message "your device is corrupt and will not boot", I really don't know what to do. please help!

please complete this topic i have this problem
i live in iran and that phone is very Expensive for me.
please help me. teach me how recover my phone step by step
please please

[TWRP][ 3.2.3-1][ Recovery for flash Android Q]

Hi !
{
"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"
}
TWRP Recovery 3.2.3-1 For Huawei P9 Lite & Honor 5c
This TWRP recovery is intended to be used ONLY for flash LineageOS 17.1 Android Q on your device and also GApps packages !​
Downloads
twrp-3.2.3-10.img md5: 245a15b538d8b2fded4d5b944c66592a
Installations
your device must be already bootloader & FRP unlocked
put your device in bootloader mode ( adb reboot bootloader )
flash TWRP by this command :
fastboot flash recovery twrp-3.2.3-10.img
fastboot reboot ( reboot device from bootloader mode )
Source code
android_device_huawei_vns
Credit
TWRP TEAM

*** reserved ***

Hi, sorry, how do you go about installing TWRP. I cannot establish a connection between my pc and the smartphone!
I tried Kingo Root
Salut, désoler mais comment faites vous pour installer le TWRP. je n'arrive pas a établir une connexion entre mon pc et le smartphone !
J'ai essayer Kingo Root

brasdeplume said:
Salut, désoler mais comment faites vous pour installer le TWRP. je n'arrive pas a établir une connexion entre mon pc et le smartphone !
J'ai essayer Kingo Root
Click to expand...
Click to collapse
Maybe you need to use Google for help about how you can connect via USB your device to PC !

Hello, can the TWRP be installed on any P9 Lite? It is that I find little information and I do not know how to do it, I already have experience in roms but not with Huawei, excuse the Spanish
Hola, el TWRP se puede instalar en cualquier P9 Lite? Es que encuentro poca información y no se cómo hacer, ya tengo experiencia en roms pero no con Huawei, disculpa el español

jesusgamerYT46 said:
Hola, el TWRP se puede instalar en cualquier P9 Lite? Es que encuentro poca información y no se cómo hacer, ya tengo experiencia en roms pero no con Huawei, disculpa el español
Click to expand...
Click to collapse
As seen if, only the bootloader procedure is the detail once you are with the adb sending the twrp and then executing the commands lines above you can install the rom compatible with this device, I will also do it today on the twrp and the rom lineage os
Segun lo visto si, solo el procedimiento del bootloader es el detalle una vez ya estes con el adb enviando el twrp y luego ejecutando los comandos lineas arriba ya puedes instalar la rom compatible con este dispositivo, tambien me pondre a hacerlo hoy sobre el twrp y la rom lineage os

Tony Ccorimanya said:
As seen if, only the bootloader procedure is the detail once you are with the adb sending the twrp and then executing the commands lines above you can install the rom compatible with this device, I will also do it today on the twrp and the rom lineage os
Click to expand...
Click to collapse
Thanks for the information, I see that the bootloader is difficult, I will do what I can and thanks

surdu_petru said:
Hi !
TWRP Recovery 3.2.3-1 For Huawei P9 Lite & Honor 5c
This TWRP recovery is intended to be used ONLY for flash LineageOS 17.1 Android Q on your device and also GApps packages !​
Downloads
twrp-3.2.3-10.img md5: 245a15b538d8b2fded4d5b944c66592a
Installations
your device must be already bootloader & FRP unlocked
put your device in bootloader mode ( adb reboot bootloader )
flash TWRP by this command :
fastboot flash recovery twrp-3.2.3-10.img
fastboot reboot ( reboot device from bootloader mode )
Source code
android_device_huawei_vns
Credit
TWRP TEAM
Click to expand...
Click to collapse
can i flash this recovery on huawei mate 7 MT7-L10. HiSilicon Kirin 925??
i have already installed twrp recovery 3.0.2-2.

mqrafique said:
can i flash this recovery on huawei mate 7 MT7-L10. HiSilicon Kirin 925??
i have already installed twrp recovery 3.0.2-2.
Click to expand...
Click to collapse
I'm sorry, I don't know !

this recovery doesnt boot at all on my phone
P9 lite L21

Logan_Mac said:
this recovery doesnt boot at all on my phone
P9 lite L21
Click to expand...
Click to collapse
does your device run stock android 7 emui 5.x before to flash this twrp ?

help spflashtool status error (0xC0010001)

hello I recently failed to install twrp and got into bootloop so i search here how to unbrick my phone and I found a solution but the spflash tool always have this error. I already did bypassbrom and successfully get the protection disabled status the only problem is when I am trying to flash the rom to my device it will always show like 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"
}

kazuhiko23124 said:
hello I recently failed to install twrp and got into bootloop so i search here how to unbrick my phone and I found a solution but the spflash tool always have this error. I already did bypassbrom and successfully get the protection disabled status the only problem is when I am trying to flash the rom to my device it will always show like this
View attachment 5394419
Click to expand...
Click to collapse
Uncheck preloader and check again. Let me know, probably you are missing something more.

SubwayChamp said:
Uncheck preloader and check again. Let me know, probably you are missing something more.
Click to expand...
Click to collapse
still not working

kazuhiko23124 said:
View attachment 5394575
still not working
Click to expand...
Click to collapse
OK, you said you passed the unauthorized verification, I guess you installed the devel filters and so on.
Now you have to set the SP Flash tool in Options/General Check LIB DA match and Check Storage Life Cycle and in Connection; UART/Baud Rate to 921600

kazuhiko23124 said:
View attachment 5394575
still not working
Click to expand...
Click to collapse
Do you know you have to relaunch the bypass each time you try to use SP Flash tool and after each error too?

lobothefoots said:
Do you know you have to relaunch the bypass each time you try to use SP Flash tool and after each error too?
Click to expand...
Click to collapse
I don't know that, thank you sir

kazuhiko23124 said:
hola, recientemente no pude instalar twrp y entré en bootloop, así que busqué aquí cómo desbloquear mi teléfono y encontré una solución, pero la herramienta spflash siempre tiene este error. Ya hice bypassbrom y obtuve con éxito el estado de protección desactivada. El único problema es que cuando intento actualizar la rom a mi dispositivo, siempre se mostrará así.
kazuhiko23124 said:
no lo se gracias señor
Click to expand...
Click to collapse
kazuhiko23124 said:
hola, recientemente no pude instalar twrp y entré en bootloop, así que busqué aquí cómo desbloquear mi teléfono y encontré una solución, pero la herramienta spflash siempre tiene este error. Ya hice bypassbrom y obtuve con éxito el estado de protección desactivada. El único problema es que cuando intento actualizar la rom a mi dispositivo, siempre se mostrará así.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
y tenia el mismo problema, lo SOLUCIONE, es un problema de Driver, tus driver preloader estan desactualizado, anda al administrador de dispositivos, busca el puerto donde esta conectado el telefono y dale clic derecho y luego actualizar controlador, la Pc debe hacer el proceso de actualizarlo y luego vas a Flashtool y le das Start, listo. repito: Actualiza el Controlador o Driver

SubwayChamp said:
Desmarque el precargador y vuelva a verificar. Déjame saber, probablemente te estás perdiendo algo más.
Click to expand...
Click to collapse
HatoryHanzo said:
y tenia el mismo problema, lo SOLUCIONE, es un problema de Driver, tu driver preloader esta desactualizado, anda al administrador de dispositivos, busca el puerto donde esta conectado el telefono y dale clic derecho y luego actualizar controlador, la Pc debe hacer el proceso de actualizarlo y luego vas a Flashtool y le das Start, listo. repito: Actualiza el Controlador o Driver
Click to expand...
Click to collapse
entonces tengo que actualizar preolader de mi celular para que funcione en flash tool

mario 1 said:
entonces tengo que actualizar preolader de mi celular para que funcione en flash tool
Click to expand...
Click to collapse
English is required here, if you want, you can write both.
Not sure what exactly is your issue, if you want to describe it better, it'll be useful.

SubwayChamp said:
English is required here, if you want, you can write both.
Not sure what exactly is your issue, if you want to describe it better, it'll be useful.
Click to expand...
Click to collapse
Hi guys, I get the same error on a Xiaomi Redmi Note 8 Plus, installed the MTK USB Drivers, Bypassed the usb, loaded the global begonia miui 10 flashboot for it, DA/ Scatter/ Auth loaded up, i see the MTK Port in my device manager but i cant find it in SP Flash tool Options/ Connection/ UART .. why ? Is that the problem ? It may be a driver problem, are my drivers bad (MTK Usb Driver v1.0.8) ? Can you guys give some tips on good drivers for this operation ? Thank you in advance.

Dr4kunov said:
Hi guys, I get the same error on a Xiaomi Redmi Note 8 Plus, installed the MTK USB Drivers, Bypassed the usb, loaded the global begonia miui 10 flashboot for it, DA/ Scatter/ Auth loaded up, i see the MTK Port in my device manager but i cant find it in SP Flash tool Options/ Connection/ UART .. why ? Is that the problem ? It may be a driver problem, are my drivers bad (MTK Usb Driver v1.0.8) ? Can you guys give some tips on good drivers for this operation ? Thank you in advance.
Click to expand...
Click to collapse
Once you bypassed restriction, then keep connected to the PC, and just run SPFT, take a look how your device appears on device manager and upload the screenshot here.

I forgot to mention.. the device is locked on miui cloud and i dont have the account, so i cant unlock the dev mode, is that the problem ? Do i need to enter edl test state ? shorting the motherboard test pins ? The device only appears in libusb as Redmi Note 8 plus, i install the mediatek driver but .. no succes.

SubwayChamp said:
Uncheck preloader and check again. Let me know, probably you are missing something more.
Click to expand...
Click to collapse
can you help me as well ? i am having the same issue , the port com12 is getting detected but no luck so far

kazuhiko23124 said:
hello I recently failed to install twrp and got into bootloop so i search here how to unbrick my phone and I found a solution but the spflash tool always have this error. I already did bypassbrom and successfully get the protection disabled status the only problem is when I am trying to flash the rom to my device it will always show like this
View attachment 5394419
Click to expand...
Click to collapse
flash tool in the C:\ ??

SubwayChamp said:
OK, you said you passed the unauthorized verification, I guess you installed the devel filters and so on.
Now you have to set the SP Flash tool in Options/General Check LIB DA match and Check Storage Life Cycle and in Connection; UART/Baud Rate to 921600
Click to expand...
Click to collapse
I have same error. how can i post for the question please guide me

My system says, (unknown USB device), even with drivers

zoalmat said:
My system says, (unknown USB device), even with drivers
Click to expand...
Click to collapse
The thing is that the drivers must be updated in the communication before your device and the PC, not your PC only.
This means you have to see where it is the change on the device manager when you plugged your device, if you need the preloader mode, firstly you have to see your device under COM Port, to can update it. You can provide some screenshot from the list at this exact time, to see it.