Related
[Help] fastboot error "Loading keystore failed status 5 [600] USB init ept @0x8f2270"
ok so i have a device, LG spirit H440n.
and i cant get it work.
if im trying to get into download mode, make a factory reset through the stock "recovery" mode or to boot normally i get this:
boot certification verify
Secure bootung Error!
Cause: boot certification verify.
i just cant do anything.
but i can enter fastboot mode. but when i enter i get the following:
fastboot_init()
Loading keystore failed status 5 [600] USB init ept @0x8f2270
udc_start()
-- reset --
-- portchange --
fastboot: processing commands
from there i cannot apply fastboot comands. if ill send "fastboot devices" i can see the device attached.
if i send "fastboot reboot" i dont get any error but device doesnt reboot, i just see in the device screen a new line "fastboot: reboot".
and if im trying to flash somthing i get an error "failed remote unknown command".
any solution?
Shlomi93 said:
ok so i have a device, LG spirit H440n.
and i cant get it work.
if im trying to get into download mode, make a factory reset through the stock "recovery" mode or to boot normally i get this:
boot certification verify
Secure bootung Error!
Cause: boot certification verify.
i just cant do anything.
but i can enter fastboot mode. but when i enter i get the following:
fastboot_init()
Loading keystore failed status 5 [600] USB init ept @0x8f2270
udc_start()
-- reset --
-- portchange --
fastboot: processing commands
from there i cannot apply fastboot comands. if ill send "fastboot devices" i can see the device attached.
if i send "fastboot reboot" i dont get any error but device doesnt reboot, i just see in the device screen a new line "fastboot: reboot".
and if im trying to flash somthing i get an error "failed remote unknown command".
any solution?
Click to expand...
Click to collapse
Fastboot commands are disabled on lk user builds (LittleKernel (Bootloader most of qcom devices use)) That means while you can see device in fastboot mode you cant interact with it since it has no commands implemented there is no way around it but why dont you just use lg flash tool? from my experience you should still have access to it also more info about lk here check out page 14 for info about fastboot and how it is disabled, No this doesnt mean we can recompile lk before someone asks since we dont have sign keys
Ivan_Meler said:
Fastboot commands are disabled on lk user builds (LittleKernel (Bootloader most of qcom devices use)) That means while you can see device in fastboot mode you cant interact with it since it has no commands implemented there is no way around it but why dont you just use lg flash tool? from my experience you should still have access to it also more info about lk here check out page 14 for info about fastboot and how it is disabled, No this doesnt mean we can recompile lk before someone asks since we dont have sign keys
Click to expand...
Click to collapse
can i use LG flash tool when device is in fastboot mode?
how?
and i will take a look on what you send me. thanks!
Shlomi93 said:
can i use LG flash tool when device is in fastboot mode?
how?
and i will take a look on what you send me. thanks!
Click to expand...
Click to collapse
No not really but you should be able to put it in lg's download mode, That file just documents lk quite interesting stuff but cant help in unlocking bootloader in anything before somebody asks
Ivan_Meler said:
No not really but you should be able to put it in lg's download mode, That file just documents lk quite interesting stuff but cant help in unlocking bootloader in anything before somebody asks
Click to expand...
Click to collapse
no matter what i send i get the same error. and according the guild that you gave me these commands should work..
i just cant get rid off this error.
any idea??
examples:
C:\Users\Shlomi>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.010s
C:\Users\Shlomi>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.008s
C:\Users\Shlomi>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.006s
Shlomi93 said:
no matter what i send i get the same error. and according the guild that you gave me these commands should work..
i just cant get rid off this error.
any idea??
examples:
C:\Users\Shlomi>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.010s
C:\Users\Shlomi>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.008s
C:\Users\Shlomi>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.006s
Click to expand...
Click to collapse
According to what i sent you nothing will work in fastboot actually it just explains every single command is disabled just wanted to clearify fastboot commands are completely disabled
Ivan_Meler said:
According to what i sent you nothing will work in fastboot actually it just explains every single command is disabled just wanted to clearify fastboot commands are completely disabled
Click to expand...
Click to collapse
goddammit
so im basically fu*ked?
Shlomi93 said:
goddammit
so im basically fu*ked?
Click to expand...
Click to collapse
Power Off your device
Now press the Volume Up button and hold it
Plug in your device into your computer using a microUSB cable
After a few seconds it should jump into download mode
try to reproduce those steps you should see lg's download mode apear on the screen
Ivan_Meler said:
Power Off your device
Now press the Volume Up button and hold it
Plug in your device into your computer using a microUSB cable
After a few seconds it should jump into download mode
try to reproduce those steps you should see lg's download mode apear on the screen
Click to expand...
Click to collapse
when im trying to get into download mode i get this again:
boot certification verify
Secure bootung Error!
Cause: boot certification verify.
UP
I have the same issue with lg spirit 4g (h440n) on hutchison three uk. boot certification verify in download mode, and then off in 3-4 seconds. fastboot mode stays on without going off, with the same error as the original poster. But no fastboot commands do anything. Annoying because nothing dodgy has been done with this phone, and it is always treated with the utmost care. Need to fix because settings produces "unfortunately settings has stopped", after a factory reset, even in safe mode.
Shlomi93 said:
[NORMAL][Ayuda] error de arranque rápido "Error en el estado de carga del almacén de claves 5 [600] USB init ept @ 0x8f2270"[/NORMAL]
ok, entonces tengo un dispositivo, LG espíritu H440n.
y no puedo hacer que funcione.
Si estoy tratando de ingresar al modo de descarga, realice un restablecimiento de fábrica a través del modo de "recuperación" de stock o para iniciar normalmente obtengo esto:
verificación de certificación de arranque
¡Error de arranque seguro!
Causa: verificación de certificación de arranque.
simplemente no puedo hacer nada
pero puedo entrar en modo fastboot. pero cuando entro me sale lo siguiente:
fastboot_init()
Estado de error al cargar el almacén de claves 5 [600] USB init ept [MENCIÓN = 1163592] 0x8 [/ MENCIÓN] f2270
udc_start()
-- Reiniciar --
-- cambio de puerto --
fastboot: procesamiento de comandos
desde allí no puedo aplicar comandos fastboot. Si envío "dispositivos de arranque rápido", puedo ver el dispositivo adjunto.
si envío "reinicio de arranque rápido" no obtengo ningún error pero el dispositivo no se reinicia, solo veo en la pantalla del dispositivo una nueva línea "arranque rápido: reinicio".
y si estoy tratando de flashear algo, aparece el error "comando remoto desconocido fallido".
¿alguna solución?
Click to expand...
Click to collapse
Please, please, someone solve it? I have the same problem after trying to install twrp on my lg leon lte h340ar and I can only access fastboot mode and factory data reset, which only allows me to restore it but the "secure booting error" message reappears
Hello Guys,
Before Starting, i'm French, so i apologize for my bad English
Anyway, i had a very big problem with my phone.
I was on the rom CM13 and because it's an alpha Rom, i wanted to return to the official rom. I didn't do a backup btw and i tried to change but it didn't work. After a few manipulations which all failed, i'm now in this precise case:
-Only Twrp revolution for nougat work, i tried others twrp with others versions but no one works. But the problem with this twrp is that when i want to install a rom or wipe something, it says a lot of errors :
Failed to Mount /Product
Failed to Mount /Versions
Failed to Mount /Vendor
And
Failed to Mount /data
-I tried to flash boot.img, system.img and recovery.img ( Files in Update.App ) with adb-fastboot but it failed at the flash system
-With the dload method, the installation of the software stucks at 5% and i tried with differents versions but always official rom for my phone
In fact, i need you to help me with this big problem, you are my last hope so don't tell me to go give back my phone with the guarantee
Thank you
Wolfgangux said:
Hello Guys,
Before Starting, i'm French, so i apologize for my bad English
Anyway, i had a very big problem with my phone.
I was on the rom CM13 and because it's an alpha Rom, i wanted to return to the official rom. I didn't do a backup btw and i tried to change but it didn't work. After a few manipulations which all failed, i'm now in this precise case:
-Only Twrp revolution for nougat work, i tried others twrp with others versions but no one works. But the problem with this twrp is that when i want to install a rom or wipe something, it says a lot of errors :
Failed to Mount /Product
Failed to Mount /Versions
Failed to Mount /Vendor
And
Failed to Mount /data
-I tried to flash boot.img, system.img and recovery.img ( Files in Update.App ) with adb-fastboot but it failed at the flash system
-With the dload method, the installation of the software stucks at 5% and i tried with differents versions but always official rom for my phone
In fact, i need you to help me with this big problem, you are my last hope so don't tell me to go give back my phone with the guarantee
Thank you
Click to expand...
Click to collapse
Ok I have some news, i installed another twrp for nougat, and i have no more the " Failed to mount /data " error, i think it's a good begin but i need you for tell me what to do now !
Salut, je suis français aussi
Mon VNS L31 s'est aussi brick à cause de ça, j'ai réussi a le reparer
Faut que tu ai accès au recovery ou au bootloader pour pouvoir flash le recovery :
- Placer le update.app de EMUI 4.1 (il existe un topic pour le télécharger) dans le dossier /dload de la carte sd (le créer si il existe pas)
- Flasher Oeminfo (telecharge ici : https://www.dropbox.com/s/noar1nvfxp6xary/C432OemInfo-DUALSIM-P9LITE.zip?dl=0 )
- Eteint
- Allume le telephone (avec la carte sd) en restant appuyer sur les 3 bouttons , ça devrait installer et fonctionner
Les gens parlent souvent de la methode des 3 bouttons, mais elle ne marche souvent pas si on ne flash pas Oeminfo avant
PS: Oeminfo Relock le bootloader !
J'espère avoir pu t'aider
Je te remercie de ta réponse, content de trouver un français
Bref, j'ai essayé ta méthode en flashant oeminfo par adb ( parce que si je flash avec twrp, le bootloader se lock et je peux plus flash le recovery stock avec le dload)
Mais le problème c'est qu'en essayant de flasher avec ADB, la console me dit :
"target reported max download size of 471859200 bytes
sending 'oeminfo' (65536 KB)...
OKAY [ 1.667s]
writing 'oeminfo'...
FAILED (remote: Command not allowed)
finished. total time: 1.687s"
Donc voila
Ok finally i installed the firmware nougat with the dload method and it worked.
bro i have same problem please help me.have you got the solution?
..
Wolfgangux said:
Hello Guys,
Before Starting, i'm French, so i apologize for my bad English
Anyway, i had a very big problem with my phone.
I was on the rom CM13 and because it's an alpha Rom, i wanted to return to the official rom. I didn't do a backup btw and i tried to change but it didn't work. After a few manipulations which all failed, i'm now in this precise case:
-Only Twrp revolution for nougat work, i tried others twrp with others versions but no one works. But the problem with this twrp is that when i want to install a rom or wipe something, it says a lot of errors :
Failed to Mount /Product
Failed to Mount /Versions
Failed to Mount /Vendor
And
Failed to Mount /data
-I tried to flash boot.img, system.img and recovery.img ( Files in Update.App ) with adb-fastboot but it failed at the flash system
-With the dload method, the installation of the software stucks at 5% and i tried with differents versions but always official rom for my phone
In fact, i need you to help me with this big problem, you are my last hope so don't tell me to go give back my phone with the guarantee
Thank you
Click to expand...
Click to collapse
http://ministryofsolutions.com/2017/01/huawei-p9-lite-vns-l31-bricked-nougat-update.html
Check this guide
http://ministryofsolutions.com/2016/12/huawei-p9-lite-convert-dual-simdebrand.html
and this guide
may work for you if you merge both
Redmi 3 note pro special edition (kate)
Wonder-full pleasant use of my phone on resurrection remix rom (android 6),
No problem for years but a couple of days ago, in an app (each time the same) the phone get stuck, this happened 1 or 2 times / day but the rest of time I fully can use my phone.
This morning, the phone was stuck on Mi.com logo. (I don't modify or update the ROM for years)
It stay on logo about 60 seconds (less or more) and reboot and the same again and again
I can't go to recovery menu cause I get the recovery icon and 60 seconds later (less or more) it reboot and same problem with Mi.com logo...
(I wanted to try https://forum.xda-developers.com/showthread.php?t=2426426)
But I can go in fastboot system,
And my computer can communicate with fastboot.
Questions:
- Any knowed issue for my symptoms?
- Is the stuck app problem correlate with the new problem occurring? Can it be the internal phone memory becoming old and causing problems
- Is there a way to know more informations about this issue with fastboot?
Thank you for reading,
Sorry for my poor english level,
If I don't put my message at the right place, tell me, I will correct.
ROUGE13 said:
Redmi 3 note pro special edition (kate)
Wonder-full pleasant use of my phone on resurrection remix rom (android 6),
No problem for years but a couple of days ago, in an app (each time the same) the phone get stuck, this happened 1 or 2 times / day but the rest of time I fully can use my phone.
This morning, the phone was stuck on Mi.com logo. (I don't modify or update the ROM for years)
It stay on logo about 60 seconds (less or more) and reboot and the same again and again
I can't go to recovery menu cause I get the recovery icon and 60 seconds later (less or more) it reboot and same problem with Mi.com logo...
(I wanted to try https://forum.xda-developers.com/showthread.php?t=2426426)
But I can go in fastboot system,
And my computer can communicate with fastboot.
Questions:
- Any knowed issue for my symptoms?
- Is the stuck app problem correlate with the new problem occurring? Can it be the internal phone memory becoming old and causing problems
- Is there a way to know more informations about this issue with fastboot?
Thank you for reading,
Sorry for my poor english level,
If I don't put my message at the right place, tell me, I will correct.
Click to expand...
Click to collapse
Question is
did u unlock ur bootloader officially using miunlock tool ?
Whats ur bootloader unlock status now?
Now Check bootloader unlock status using below fastboot command.
If Unlock = false then ur bootloader is accidentally relocked. Put ur phone in fastboot mode and connect to pc and Use below command to check output.
fastboot oem device-info
And reply to me about the status.
Hi, thanks for your answer
naik2902 said:
Question is
did u unlock ur bootloader officially using miunlock tool ? .
Click to expand...
Click to collapse
I remember that I used MiFlash tool, but not sure that I wait the time Xiaomi send me the unlock code as I found some other ways.
I first put this ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137.tgz
I followed this procedure:
Pré-requis
- ROM Fastboot (6.9.29) pour le kate http://bigota.d.miui.com/6.9.29/kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137.tgz
- AnF_MM.zip file: https://www.androidfilehost.com/?fid=24588232905724247
- emmc_appsboot.mbn_UNLOCK_MARSHMALLOW.zip file: https://www.androidfilehost.com/?fid=24588232905724248
- Miflash du 30 août 2016 (32 et 64 bits) http://api.bbs.miui.com/url/MiFlash Installez l'application puis redémarrez votre PC.
En cas de souci de reconnaissance avec MiFlash, installez la version beta (bien désinstaller la précédente avant d'installer cette version) MiFlash beta de mai 2016. Pour les 64bits (uniquement), vous avez également la version du 01 avril 2016
- Drivers adb (surtout pour Windows 64 bits) + désactivation signature des pilotes (pour x64 bits) : voir tuto RN3P (dans les pré-requis)
http://forum.frandroid.com/topic/24...-global-dev-stable-et-xiaomieu-miui-8/?page=1
- Un PC Windows (Win 7/8/10 32 bits ou 64bits) ne pas flasher votre Redmi Note 3 Pro via une "machine virtuelle" : forte probabilité de problèmes ou brique.
- Câble de liaison USB livré avec votre RN3P.
- Téléchargez les drivers adb + Mi PC Suite + nouveau MiFlash (32 bits et 64 bits)
- Conseil : quand vous mettez votre appareil en mode edl + flash de la ROM, connectez le sur un port USB à l'arrière de votre PC (directement sur la carte mère). Pour les ordinateurs portables, le port n'a pas d'importance.
Nouveau Miflash du 30 août 2016 (pour Windows 32 bits et 64 bits) http://api.bbs.miui.com/url/MiFlash Installez l'application puis redémarrez votre PC.
En cas de souci de reconnaissance avec MiFlash, installez la version beta (bien désinstaller la version précédente avant d'installer cette version) MiFlash beta de mai 2016
Pour Windows 32/64 bits, installez UniversalAdbDriver sur votre PC https://drive.google.com/file/d/0B3Zvk_paJVX1V2g1c1dMbTVqczA/view
MiPCSuite https://drive.google.com/file/d/0B3Zvk_paJVX1YkZJajJzVFRxbTQ/view (c'est la dernière version 3.2.1.3111)
Optionnel : pour Windows 64 bits, QDLoader (drivers Qualcomm 32 bits et 64 bits) ou ceux-là
Optionnel : alternative pour installer les drivers adb (32bits et 64 bits) https://drive.google.com/file/d/0B3Zvk_paJVX1Y3FFRHF0SEdpZ00/view avec des explications pour bien les installer sur Windows 64 bits http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
MiFlash et MI PC Suite vous installe les drivers Qualcomm et Xiaomi (pensez à redémarrer votre PC après l'installation des 2 softs).
Pour les utilisateurs de Windows 7/8/10 64 bits, désactiver la signature des pilotes (voir chapitre "petites recommandations").
Les différentes versions de MiFlash
- Version MiFlash 2016.04.01.exe (01 avril 2016 - uniquement pour les systèmes 64 bits).
- Version MiFlash beta de mai 2016 (32 et 64 bits) recommandée si la version finale ne fonctionne pas
- Version finale de MiFlash (30 août 2016). Version recommandée (32 et 64 bits)
- Conseil : quand vous mettez votre appareil en mode edl + flash de la ROM, connectez le sur un port USB à l'arrière de votre PC (directement sur la carte mère). Pour les ordinateurs portables, le port n'a pas d'importance.
- Activer "Débogage USB" + "Déverrouillage OEM" (dans les options développeurs).
Procédure
- Clic-droit sur l'archive de la ROM Fastboot 6.9.29 avec Winrar (ou 7-Zip) et décompressez la.
- Renommez l'archive en global et placez là à la racine de C:
- Cliquez sur le dossier images (vous devez voir la même chose que sur la capture d'écran suivante).
Notez bien le fichier "emmc_appsboot.mbn" (c'est lui qui va être remplacé par le fichier emmc_appsboot.mbn que vous avez téléchargé et mis de côté).
- Faire un copié collé du nouveau emmc_appsboot.mbn (en sélectionnant ce fichier depuis l'archive emmc_appsboot.mbn_UNLOCK_MARSHMALLOW.zip et en le faisant glisser comme dans la fenêtre ci-dessus).
Votre ROM Fastboot contenant le Bootloader déverrouillé est prête
Il n'y plus qu'à la flasher (via MiFlash) et écrire une petite commande fastboot après le flash de la ROM Fastboot.
Première étape : installer les drivers et donner les autorisations à ADB
Pour les utilisateurs de Windows 7/8/10 64 bits, pensez à désactiver la signature des pilotes (voir chapitre "petites recommandations").
Au préalable, il faut activer débogage USB et déverrouillage OEM dans les options développeurs de votre RN3 Pro.
Activer l'onglet développeur en allant dans les "Settings"(Paramètres) / About Phone (à propos de l'appareil) / cliquez 5-6 fois sur "version MIUI". Vous voila développeur (voir captures d'écran plus bas). La nouvelle option développeur se trouve dans : Paramètres / paramètres additionnels / option de développeur. Vous activez "débogage USB" et "déverouillage OEM".
2. téléchargez l'archive adb sur ce lien
3. Décompressez l'archive dans un nouveau dossier et allez à l'emplacement du dossier
4. Inscrivez cmd (invite de commandes) puis entrée.
N.B. Vous pouvez aussi faire Maj + Clic droit dans le dossier adb puis "ouvrir une fenêtre de commande en mode administrateur"
5. Inscrivez ces commandes :
adb devices
Instantanément, le téléphone se retrouve avec un écran noir et la LED rouge clignote.
En cas de souci, méthode pour retrouver le mode EDL "How to reboot to EDL from fastboot"
Reveal hidden contents
Le moment est venu de lancer MiFlash.exe que vous pouvez télécharger ici C:\XiaoMi\XiaoMiFlash\XiaoMiFlash.exe
Le logiciel va installer les pilotes Qualcomm sur votre PC et vous demandera auparavant l'autorisation d'installer les pilotes.
drivers Qualcomm QDLoader (drivers Qualcomm 32 bits et 64 bits)
Win 64 bit C: \ Program Files (x86) \ Xiaomi \ MiPhone \ Qualcomm \ Driver
Win 32 bit C: \ Program Files \ Xiaomi \ MiPhone \ Qualcomm \ Driver
Vous devez voir le driver installé dans le gestionnaire de périphériques (section Ports) comme étant Qualcomm QDLoader 9008 ou Relink.
En cas de souci au Flash, modifiez le Port COM = ou supérieur à 20. Rebootez également votre PC
Deuxième étape : Flasher la ROM
- Si ça n'est pas déjà fait, décompressez l'archive de la ROM Fastboot à la racine de C: (avec Winrar).
- Renommez l'archive en "global"
Retournez dans le gestionnaire de périphériques et vérifiez que votre RN3P est bien détecté comme sur l'image en dessous
Les drivers Qualcomm doivent être bien installés (Relink parfois à la place de Qualcomm, c'est bon également)
- Lancez le programme MiFlash.exe
Dans l'outil de Flash, sélectionner (en bas à droite) : "clean all"
- Cliquez sur la touche "refresh" (votre appareil va être reconnu)
- Sélectionnez la ROM Fastboot (que vous avez téléchargé et décompressé sur votre PC) en cliquant sur "select" puis pointez sur le dossier "images"
Cliquez sur la touche "Flash" et l'installation démarre.
- Attendre la fin du flash (success).
- Éteignez votre appareil et relancez le en mode Fastboot (Vol - et Power simultanément pendant 10-20 secondes. Un petit bunny apparaît.
- Connectez votre kate au PC. Téléchargez et décompressez l'archive suivante dans un nouveau dossier (plutôt sur C AnF_MM.zip file: https://www.androidfilehost.com/?fid=24588232905724247
- Ouvrir une commande cmd.exe à partir du dossier AnF_MM (Majuscule + clic droit = ouvrir une fenêtre de commandes ici")
- Ecrire fastboot oem device-info (vous verrez l'état du Bootloader (lock)
- Ecrire fastboot oem unlock-go
Le Bootloader est déverrouillé. Vous pouvez le vérifier en écrivant fastboot oem device-info
Retirez le câble USB et rebootez au moins une fois sur Miui avant d'installer le TWRP. Si vous ne le faites pas, vous n'aurez que 7Go de mémoire
- Ecrivez fastboot reboot pour qu'il sorte du mode fastboot et redémarre.
Click to expand...
Click to collapse
naik2902 said:
Whats ur bootloader unlock status now?
Click to expand...
Click to collapse
unlocked : true
naik2902 said:
Now Check bootloader unlock status using below fastboot command.
If Unlock = false then ur bootloader is accidentally relocked. Put ur phone in fastboot mode and connect to pc and Use below command to check output.
fastboot oem device-info
And reply to me about the status.
Click to expand...
Click to collapse
Here:
Code:
sudo fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
ROUGE13 said:
Hi, thanks for your answer
I remember that I used MiFlash tool, but not sure that I wait the time Xiaomi send me the unlock code as I found some other ways.
I first put this ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137.tgz
I followed this procedure:
unlocked : true
Here:
Click to expand...
Click to collapse
Looks ur bootloader is outdated. U unlocked unofficially on old miui version.
U need to upgrade ur bootloader.
So Download and Flash latest kate fastboot miui 10 rom. Below.
http://bigota.d.miui.com/8.12.13/ka...13_20181213.0000.00_6.0_global_304fc0692b.tgz
Since ur bootloader shows its unlocked.
U can flash rom in fastboot mode using latest miflash tool.
But ur phone will relock after flashing latest miui10. U cant avoid it. So just flash coz bootloader upgrade is required.
After flashing miui 10 and relock . u can unlock again officially. U dont need permission. Nowadays xiaomis permission is not required.
Just go to dev option and click miunlockstatus to bind ur account under developer option. When added succesfully. U can unlock it using xiaomis unlock tool using pc.
Jast fash rom with "CLEAN ALL "option.
naik2902 said:
Looks ur bootloader is outdated. U unlocked unofficially on old miui version.
U need to upgrade ur bootloader.
Click to expand...
Click to collapse
My phone was working for about 2 years without issues, why today is the bootloader causing problems? (I don't try to upgrade, put a new ROM or doing anything else than using my phone normally)
Is there a mechanism that lock the startup until a certain time without upgrade?
Or worse, a communication mechanism that do the same?
naik2902 said:
So Download and Flash latest kate fastboot miui 10 rom. Below.
http://bigota.d.miui.com/8.12.13/ka...13_20181213.0000.00_6.0_global_304fc0692b.tgz
Since ur bootloader shows its unlocked.
U can flash rom in fastboot mode using latest miflash tool.
But ur phone will relock after flashing latest miui10. U cant avoid it. So just flash coz bootloader upgrade is required.
After flashing miui 10 and relock . u can unlock again officially. U dont need permission. Nowadays xiaomis permission is not required.
Just go to dev option and click miunlockstatus to bind ur account under developer option. When added succesfully. U can unlock it using xiaomis unlock tool using pc.
Jast fash rom with "CLEAN ALL "option.
Click to expand...
Click to collapse
Will I loose my configuration/apps/data? Or will it simply solve my startup problem (I hope so )
ROUGE13 said:
My phone was working for about 2 years without issues, why today is the bootloader causing problems? (I don't try to upgrade, put a new ROM or doing anything else than using my phone normally)
Is there a mechanism that lock the startup until a certain time without upgrade?
Or worse, a communication mechanism that do the same?
Will I loose my configuration/apps/data? Or will it simply solve my startup problem (I hope so )
Click to expand...
Click to collapse
U said u cant go in twrp
Download latest twrp 3.2.3 version.
And rename it to recovery.img
https://dl.twrp.me/kenzo/twrp-3.2.3-0-kenzo.img.html
put ur device in fastboot mode
And flash the above recovery.img using below command.
fastboot flash recover recovery.img
And go to recovery to check twrp is installed.
naik2902 said:
U said u cant go in twrp
Click to expand...
Click to collapse
Yes I get stuck at TWRP logo (Alien head + "Recovery Project 3.0.2-X by BY~XM" text) for some time and then reboot to mi.com logo.
But I think as I see the logo, TWRP is still there, just something making the phone reset (watchdog or something?)
naik2902 said:
Download latest twrp 3.2.3 version.
And rename it to recovery.img
https://dl.twrp.me/kenzo/twrp-3.2.3-0-kenzo.img.html
Click to expand...
Click to collapse
Should I put kate or kenzo twrp? (I found both on my computer, my phone is the special edition (snapdragon + 152mm case))
naik2902 said:
put ur device in fastboot mode
And flash the above recovery.img using below command.
fastboot flash recover recovery.img
And go to recovery to check twrp is installed.
Click to expand...
Click to collapse
This will not erase anything else than TWRP right? Will my old TWRP backups still work after that?
ROUGE13 said:
Yes I get stuck at TWRP logo (Alien head + "Recovery Project 3.0.2-X by BY~XM" text) for some time and then reboot to mi.com logo.
But I think as I see the logo, TWRP is still there, just something making the phone reset (watchdog or something?)
Should I put kate or kenzo twrp? (I found both on my computer, my phone is the special edition (snapdragon + 152mm case))
This will not erase anything else than TWRP right? Will my old TWRP backups still work after that?
Click to expand...
Click to collapse
Ok I know ur phone is kate.
3.0.2 old
Flash the 3.2.3 the one i gave u . it works for both kenzo and kate.
And flash it and check if twrp can be successfully flashed in recovery partition.
If u can flash img and boot into recovery then good. Else sorry u cant recover app data through twrp backup. It is lost.
And one thing i m straight to tell u that this type of bootloop happens when u unlock bootloader by unethical or unappropariate way. Now u cant go in twrp.
Always unlock officially.
naik2902 said:
And flash it and check if twrp can be successfully flashed in recovery partition.
If u can flash img and boot into recovery then good. Else sorry u cant recover app data through twrp backup. It is lost.
Click to expand...
Click to collapse
Code:
$ cat twrp-3.2.3-0-kenzo.img.md5
a8e4b592bc9dfad1ad3509266c945fcc twrp-3.2.3-0-kenzo.img
$ md5sum twrp-3.2.3-0-kenzo.img
a8e4b592bc9dfad1ad3509266c945fcc twrp-3.2.3-0-kenzo.img
$ sudo fastboot flash recover recovery.img
target reported max download size of 536870912 bytes
sending 'recover' (18580 KB)...
OKAY [ 0.585s]
writing 'recover'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.588s
:crying:
ROUGE13 said:
:crying:
Click to expand...
Click to collapse
Ur recovery partition is write protected.
Ur phone is relocked?
Since it unofficiallly unlocked it showing incorrect info as unlock = true.
Flash latest miui 10 kate rom in EDL mode.
I hope u know how to put in fastboot mode to EDL mode and flash rom.
Follow this
https://forum.xda-developers.com/re...oot-to-edl-mode-fastboot-test-t3398718/page20
I tried this:
Code:
$ sudo fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.587s]
booting...
OKAY [ 0.616s]
finished. total time: 1.203s
Then I see the TWRP logo... stuck at it... same time after ... reboot to mi.com logo
I'm more and more thinking there is some material failure no?
naik2902 said:
Ur recovery partition is write protected.
Ur phone is relocked?
Since it unofficiallly unlocked it showing incorrect info as unlock = true.
Click to expand...
Click to collapse
Code:
$ sudo fastboot oem device-info
< waiting for device >
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
$ sudo fastboot flash recover recovery.img
target reported max download size of 536870912 bytes
sending 'recover' (18580 KB)...
OKAY [ 0.586s]
writing 'recover'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.589s
$ sudo fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
Is there a way to list all remote partitions?
naik2902 said:
Flash latest miui 10 kate rom in EDL mode.
I hope u know how to put in fastboot mode to EDL mode and flash rom.
Follow this
https://forum.xda-developers.com/re...oot-to-edl-mode-fastboot-test-t3398718/page20
Click to expand...
Click to collapse
By doing this I will loose all things on phone, right?
ROUGE13 said:
Is there a way to list all remote partitions?
By doing this I will loose all things on phone, right?
Click to expand...
Click to collapse
Yes. May be. Stop crying.
Now U can only flash rom in EDL mode.
flash latest miui 10 rom which i gave u.
Also Miflashtool latest.
In miflash before u flash. u will have 3 options
1Clean except user data
2Clean all
3Clean all and lock.
Select 1st option to keep user data and flash.
After flash If phone is boooting with 1st option then lucky.
Else try 2or 3 option.
naik2902 said:
Now U can only flash rom in EDL mode.
flash latest miui 10 rom which i gave u.
Also Miflashtool latest.
Click to expand...
Click to collapse
Ok I finally found a windows computer (Miflashtool still doesn't support linux right?)
I don't see instructions on your link (page 20) but if they are same as the one I do previously it must be :
Install muiflashtool and reboot
Unpack official ROM at C: root, rename it to "global"
Start phone in fastboot mode
Connect phone to computer with usb cable
Start muiflashtool with admin rights
Refresh click
Select ROM unpacked "images" folder
Flash
But I also see something directly with fasboot command on the web like :
Code:
Fastboot oem edl
Better? (I did'nt try now)
naik2902 said:
Now U can only flash rom in EDL mode.
flash latest miui 10 rom which i gave u.
Also Miflashtool latest.
Click to expand...
Click to collapse
Shouldn't I better try with the version of muiflashtool and initial ROM I used two years ago? (I still keep them. To be sure it's still compatible with my old recovery, kernel and RR ROM?)
Or as you think my problem if coming from the way I had unlocked the bootloader (maybe unofficially), can I now try to get my unlock code to unlock it on the right way? (if still possible?)
Or unlock it again the same way I do 2 years ago before trying anything else?
Anyway, thank you for you support
ROUGE13 said:
Ok I finally found a windows computer (Miflashtool still doesn't support linux right?)
I don't see instructions on your link (page 20) but if they are same as the one I do previously it must be :
Install muiflashtool and reboot
Unpack official ROM at C: root, rename it to "global"
Start phone in fastboot mode
Connect phone to computer with usb cable
Start muiflashtool with admin rights
Refresh click
Select ROM unpacked "images" folder
Flash
But I also see something directly with fasboot command on the web like :
Better? (I did'nt try now)
Shouldn't I better try with the version of muiflashtool and initial ROM I used two years ago? (I still keep them. To be sure it's still compatible with my old recovery, kernel and RR ROM?)
Or as you think my problem if coming from the way I had unlocked the bootloader (maybe unofficially), can I now try to get my unlock code to unlock it on the right way? (if still possible?)
Or unlock it again the same way I do 2 years ago before trying anything else?
Anyway, thank you for you support
Click to expand...
Click to collapse
Follow the instruction on my previous page. Also i gave u thread link to how to put phone in edl mode.
Black_Stark said:
Looks ur bootloader is outdated. U unlocked unofficially on old miui version.
U need to upgrade ur bootloader.
So Download and Flash latest kate fastboot miui 10 rom. Below.
http://bigota.d.miui.com/8.12.13/ka...13_20181213.0000.00_6.0_global_304fc0692b.tgz
Since ur bootloader shows its unlocked.
U can flash rom in fastboot mode using latest miflash tool.
But ur phone will relock after flashing latest miui10. U cant avoid it. So just flash coz bootloader upgrade is required.
After flashing miui 10 and relock . u can unlock again officially. U dont need permission. Nowadays xiaomis permission is not required.
Just go to dev option and click miunlockstatus to bind ur account under developer option. When added succesfully. U can unlock it using xiaomis unlock tool using pc.
Jast fash rom with "CLEAN ALL "option.
Click to expand...
Click to collapse
Black_Stark said:
Now U can only flash rom in EDL mode.
flash latest miui 10 rom which i gave u.
Also Miflashtool latest.
In miflash before u flash. u will have 3 options
1Clean except user data
2Clean all
3Clean all and lock.
Select 1st option to keep user data and flash.
After flash If phone is boooting with 1st option then lucky.
Else try 2or 3 option.
Click to expand...
Click to collapse
Black_Stark said:
Use windows pc. And follow page1 instruction. Dont put too much stress on brain.:laugh:
Click to expand...
Click to collapse
Sorry I'm still stressing brain a little more :
When I will flash with miflash tool, will I loose my Ressurection Remix Rom and all apps/configurations ? Even with option 1? (1Clean except user data)
If yes, any way to avoid this? Flash my ROM again ? (I kept it)
No way to flash only bootloader and don't touch anything else?
I found This but it seems to be same as your procedure
If not can I use fastboot to make a backup through computer before flashing? And then restore after following your instructions?
ROUGE13 said:
Sorry I'm still stressing brain a little more :
When I will flash with miflash tool, will I loose my Ressurection Remix Rom and all apps/configurations ? Even with option 1? (1Clean except user data)
If yes, any way to avoid this? Flash my ROM again ? (I kept it)
No way to flash only bootloader and don't touch anything else?
I found This but it seems to be same as your procedure
If not can I use fastboot to make a backup through computer before flashing? And then restore after following your instructions?
Click to expand...
Click to collapse
No option 1 wont loose ur backup.
Black_Stark said:
No option 1 wont loose ur backup.
Click to expand...
Click to collapse
Backup or actual ROM/configuration/apps/data ?
I have three options in MiFlash (2017.4.25.0) :
"clean all"
"save user data"
"clean all data and lock"
The n°2 seems to correspond to your reply right?
ROUGE13 said:
Backup or actual ROM/configuration/apps/data ?
I have three options in MiFlash (2017.4.25.0) :
"clean all"
"save user data"
"clean all data and lock"
The n°2 seems to correspond to your reply right?
Click to expand...
Click to collapse
Option 2.
Black_Stark said:
Option 2.
Click to expand...
Click to collapse
I am currently flashing but I see the bat file lunched is called "flash_all_except_data.bat"
It is running for more than 300s, I'm not sure it is only flashing the bootloader.
Good morning.
A friend who also have a Moto RAZR M XT907 said what his phone somehow abruptly stopped working one day. Now, he took his phone to my house and now I have the dead phone on my hands.
The first thing I noticed is what the only way I'm able to charge the battery was doing a trick for putting it into Fastboot mode. If you try to charge it in the normal way, screen keeps black after the Motorola logo.
Finally after Fastboot saying "Battery OK", I tried to flash VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF, using RSD Lite v6.1.5. (yes, I edited the xml file for being able to flash, so that's discarded). Got this responses:
RSD Lite:
Failed flashing process. 2/20 flash partition "gpt.bin" -> Phone returned FAIL.
Phone:
failed to read signature for partition aboot
Somehow knows how to fix this issue?
Pedreo1997 said:
Good morning.
A friend who also have a Moto RAZR M XT907 said what his phone somehow abruptly stopped working one day. Now, he took his phone to my house and now I have the dead phone on my hands.
The first thing I noticed is what the only way I'm able to charge the battery was doing a trick for putting it into Fastboot mode. If you try to charge it in the normal way, screen keeps black after the Motorola logo.
Finally after Fastboot saying "Battery OK", I tried to flash VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF, using RSD Lite v6.1.5. (yes, I edited the xml file for being able to flash, so that's discarded). Got this responses:
RSD Lite:
Failed flashing process. 2/20 flash partition "gpt.bin" -> Phone returned FAIL.
Phone:
failed to read signature for partition aboot
Somehow knows how to fix this issue?
Click to expand...
Click to collapse
Setup Mfastboot
see
https://forum.xda-developers.com/ge...ng-mfastboot-exe-to-unbrick-motorola-t3203518
and run
Code:
fastboot oem fb_mode_clear
fastboot reboot
sd_shadow said:
Setup Mfastboot
see
https://forum.xda-developers.com/ge...ng-mfastboot-exe-to-unbrick-motorola-t3203518
and run
Code:
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Good evening!
I tried your instructions, and process apparently went fine.
This is what CMD said:
El sistema no puede encontrar el texto del mensaje para el mensaje número 0x2350 en el archivo de mensajes para Application.
(c) 2019 Microsoft Corporation. Todos los derechos reservados.
No hay suficientes recursos de memoria disponibles para procesar este comando.
C:\Mfastboot>fastboot oem fb_mode_clear
OKAY [ 0.038s]
Finished. Total time: 0.039s
C:\Mfastboot>fastboot reboot
Rebooting
Finished. Total time: 0.000s
C:\Mfastboot>
Click to expand...
Click to collapse
However, after rebooted... Fastboot mode is now gone :crying:
After pressing the 3 buttons and selecting the AP Fastboot option, screen is completely dark.
Any idea why that happened?
sd_shadow said:
Setup Mfastboot
see
https://forum.xda-developers.com/ge...ng-mfastboot-exe-to-unbrick-motorola-t3203518
and run
Code:
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Okay, with the previous Fastboot dissapear, after a lot of reboots I could make it appear, but...
...
Battery Low.
I can now only wait, and try to charge the phone using Fastboot mode :silly:
Arrived ! Red Magic 5S { Android 11 } Root { Guide } Now
1 - Device Must Be Unlocked !
2 - How To Unlocking Device Example Red Magic 5S
Device FASTBOOT mode : VOLUME DOWN + POWER BUTTON
3 - Open CMD Typie And Enter : fastboot oem nubia_unlock NUBIA_NX659J
4 - Copy And Enter : fastboot flashing unlock
Select Unlock Bootloader With Volume Buttons On Device
All Data Will Be Erased When Unlock Bootloader !
5 - Finally Enter : fastboot reboot
Nice Your Device Unlocked !
After :
Need Download Last Firmware On Link
US - V8.57 : Nubia Link Thanks To
Patrick Morgan For Link
After Download Exrates Firmware
Copy boot.img From Folder Exrates To Device
Download Magisk v22.1 Last Version Install On Device
Open Magisk Select Patch Boot.img Click Let is Go
rename patch to magisk_patched.img from download folder device
Copy magisk_patched To PC ( Adb Folder )
1- Open CMD Typie And Enter Again : fastboot oem nubia_unlock NUBIA_NX629J
2 - fastboot flash boot magisk_patched.img
3 - fastboot reboot !
you need to wipe all data ( Factory Reset ) from recovery mode
Completed !
{KurdistaN}
red magic 5s android 11 root
This can be done without unlocking your bootloader.
Also you lose finger print calbration when bootloader is unlocked. Not worth it if you use fingerprint.
Patrick Morgan said:
This can be done without unlocking your bootloader.
Also you lose finger print calbration when bootloader is unlocked. Not worth it if you use fingerprint.
Click to expand...
Click to collapse
i am tested on bootloader locked but not work
A bricked Software device '
thanks for info
AkOViP100 said:
Llegado! Red Magic 5S {Android 11} Root {Guide} ahora
1 - ¡El dispositivo debe estar desbloqueado !
2 - Cómo desbloquear el dispositivo Ejemplo Red Magic 5S
Modo FASTBOOT del dispositivo: BAJAR VOLUMEN + BOTÓN DE ENCENDIDO
3 - Abra CMD Typie e ingrese: fastboot oem nubia_unlock NUBIA_NX659J
4 - Copiar e ingresar: desbloqueo de flasheo fastboot
Seleccione Desbloquear el cargador de arranque con botones de volumen en el dispositivo
¡Todos los datos se borrarán alar desbloquear el gestor de arranque!
5 - Finalmente ingrese: reinicio fastboot
¡Agradable su dispositivo desbloqueado!
Después:
Necesita descargar el último firmware en el enlace
EE. UU. - V8.57: Nubia Link gracias a
[USER = 894978] Patrick Morgan [/ USER] para el vínculo
Después de descargar el firmware de Exrates
Copiar boot.img de la carpeta Exrates al dispositivo
Descargar Magisk v22.1 Última versión Instalar en el dispositivo
Abra Magisk Select Patch Boot.img Haga clic en Let is Go
cambiar el nombre del parche a magisk_patched.img desde la carpeta de descarga del dispositivo
Copiar magisk_patched a la PC (carpeta Adb)
1- Abra CMD Typie y vuelva a ingresar: fastboot oem nubia_unlock NUBIA_NX629J
2 - arranque flash fastboot magisk_patched.img
3 - reinicio de fastboot!
necesita borrar todos los datos (restablecimiento de fábrica) del modo de recuperación
¡Completado!
{Kur dist aN}
Click to expand...
Click to collapse
podrías ser más explícito
alguien lo puede explicar mejor ?
AkOViP100 said:
Arrived ! Red Magic 5S { Android 11 } Root { Guide } Now
1 - Device Must Be Unlocked !
2 - How To Unlocking Device Example Red Magic 5S
Device FASTBOOT mode : VOLUME DOWN + POWER BUTTON
3 - Open CMD Typie And Enter : fastboot oem nubia_unlock NUBIA_NX659J
4 - Copy And Enter : fastboot flashing unlock
Select Unlock Bootloader With Volume Buttons On Device
All Data Will Be Erased When Unlock Bootloader !
5 - Finally Enter : fastboot reboot
Nice Your Device Unlocked !
After :
Need Download Last Firmware On Link
US - V8.57 : Nubia Link Thanks To
Patrick Morgan For Link
After Download Exrates Firmware
Copy boot.img From Folder Exrates To Device
Download Magisk v22.1 Last Version Install On Device
Open Magisk Select Patch Boot.img Click Let is Go
rename patch to magisk_patched.img from download folder device
Copy magisk_patched To PC ( Adb Folder )
1- Open CMD Typie And Enter Again : fastboot oem nubia_unlock NUBIA_NX629J
2 - fastboot flash boot magisk_patched.img
3 - fastboot reboot !
you need to wipe all data ( Factory Reset ) from recovery mode
Completed !
{KurdistaN}
Click to expand...
Click to collapse
hi. when i go fastboot and enter fastboot oem nubia_unlock NUBIA_NX629J
my device give me fail this is give me when i update to A11 . it is ok on A10.
what do u thing problem
thanks it worked for me Europe edition
faiz999 said:
hi. when i go fastboot and enter fastboot oem nubia_unlock NUBIA_NX629J
my device give me fail this is give me when i update to A11 . it is ok on A10.
what do u thing problem
Click to expand...
Click to collapse
try
fastboot flashing unlock