Hey at all users of this low priced, anyway nice speced and nearly Stock android 11 providing phone! (And all others of you, too)
I noticed, that in developer options the OEM Unlock option is greyed out.
Cause this phone is very new on the market the information I could get online is really rare.
At the Motorola forum there were a few posts asking for this and one user got at least the answer to wait a week or so and let the device communicate online, so maybe there is a chance to get the OEM unlock available this way.
I asked myself what apps, in that case could realize this? I have disabled nearly all of that Motorola specific stuff (not much at all / good work in my opinion), so I can not really be sure if one of these should have been enabled for making OEM Unlock possible..
Now my question to all Moto G20 users out there, at best those who did not disable any preinstalled app, could you please enable developer options and look if OEM Unlock is still greyed out after a week (or more) of normal usage?
More than that I would really appreciate some more activity here at XDA.
Rooting this device or maybe being able to flash calyx or lineage os on it would be so damn great!!
I am using this as my daily driver for now, so I am not really able to go the dark path alone, at least until there is no backup device available for me. (My beloved SGS5 klte died the hard way)
So maybe we, the Moto G20 users could get together here and make more, or at least anything possible on this device.
First step is the OEM unlock.
Greetings from Germany,
yours ajox
{
"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"
}
ajox said:
Hey at all users of this low priced, anyway nice speced and nearly Stock android 11 providing phone! (And all others of you, too)
I noticed, that in developer options the OEM Unlock option is greyed out.
Cause this phone is very new on the market the information I could get online is really rare.
At the Motorola forum there were a few posts asking for this and one user got at least the answer to wait a week or so and let the device communicate online, so maybe there is a chance to get the OEM unlock available this way.
I asked myself what apps, in that case could realize this? I have disabled nearly all of that Motorola specific stuff (not much at all / good work in my opinion), so I can not really be sure if one of these should have been enabled for making OEM Unlock possible..
Now my question to all Moto G20 users out there, at best those who did not disable any preinstalled app, could you please enable developer options and look if OEM Unlock is still greyed out after a week (or more) of normal usage?
More than that I would really appreciate some more activity here at XDA.
Rooting this device or maybe being able to flash calyx or lineage os on it would be so damn great!!
I am using this as my daily driver for now, so I am not really able to go the dark path alone, at least until there is no backup device available for me. (My beloved SGS5 klte died the hard way)
So maybe we, the Moto G20 users could get together here and make more, or at least anything possible on this device.
First step is the OEM unlock.
Greetings from Germany,
yours ajox
View attachment 5410895
Click to expand...
Click to collapse
Did you connect it to the internet?
ajox said:
¡Hola a todos los usuarios de este teléfono de bajo precio, de todos modos, con buena velocidad y casi en stock! (Y todos los demás de ustedes también)
Noté que en las opciones de desarrollador, la opción de desbloqueo OEM está atenuada.
Debido a que este teléfono es muy nuevo en el mercado, la información que puedo obtener en línea es realmente rara.
En el foro de Motorola hubo algunas publicaciones que preguntaban por esto y un usuario obtuvo al menos la respuesta de esperar una semana más o menos y dejar que el dispositivo se comunique en línea, por lo que tal vez exista la posibilidad de que el desbloqueo OEM esté disponible de esta manera.
Me pregunté qué aplicaciones, en ese caso, podrían darse cuenta de esto. He deshabilitado casi todas esas cosas específicas de Motorola (no mucho / buen trabajo en mi opinión), por lo que no puedo estar realmente seguro de si uno de estos debería haber sido habilitado para hacer posible el Desbloqueo OEM.
Ahora, mi pregunta para todos los usuarios de Moto G20, en el mejor de los casos, aquellos que no deshabilitaron ninguna aplicación preinstalada, ¿podrían habilitar las opciones de desarrollador y ver si el Desbloqueo OEM sigue en gris después de una semana (o más) de uso normal?
Más que eso, realmente agradecería algo más de actividad aquí en XDA.
¡Rootear este dispositivo o tal vez poder flashear el cáliz o el sistema operativo del linaje en él sería genial!
Estoy usando esto como mi controlador diario por ahora, por lo que realmente no puedo ir solo por el camino oscuro, al menos hasta que no haya un dispositivo de respaldo disponible para mí. (Mi amado SGS5 klte murió por las malas)
Entonces, tal vez nosotros, los usuarios de Moto G20, podríamos reunirnos aquí y hacer más, o al menos cualquier cosa posible en este dispositivo.
El primer paso es el desbloqueo OEM.
Saludos desde Alemania,
tuyo ajox
View attachment 5410895
Click to expand...
Click to collapse
Same here i hope we'll grew in number an maybe we could activate the oem unlock. I found this but not work for me https://mytechgyangadgets.com/how-t...ac646cbae347febc951700b1759bca89#comment-1156. Tell me if u get it
Greetings from Argentine
sd_shadow said:
Did you connect it to the internet?
Click to expand...
Click to collapse
Sure. Both, WiFi and Mobile Data are and were connected. No good life without that.
Testwise I have now reenabled Moto Feedback and Device support stuff and more than that I created a Lenovo ID and registered my device. But anyway OEM Unlock still greyed out.
anoldman57 said:
Same here i hope we'll grew in number an maybe we could activate the oem unlock. I found this but not work for me https://mytechgyangadgets.com/how-t...ac646cbae347febc951700b1759bca89#comment-1156. Tell me if u get it
Greetings from Argentine
Click to expand...
Click to collapse
Nice to see some more Moto G20 users. Will give that a look later and tell you.
*Update*
This looks interesting. When I am at home later, I will definitely fire up fastboot and look for it.
Short update..
After a while i managed to get into fastboot mode, Volume Down + Power did not work for any reason, Assistant Button + Volume Down + Power did instead:
(sorry for the poor quality)
Device was than recognized but ran into problems anyway:
Greetings!
I just purchased the motorola moto g20 xt2128-1 (unlocked) from "A to Z" and I ran into these exact issues. This is what worked for me:
FASTBOOT: VOL UP + POWER
The OEM UNLOCKING option was also grayed out in my Developer Settings. After getting into FASTBOOT MODE (the exact screen in your SHORT UPDATE) on my PC, COMMAND PROMPT (admin):
fastboot devices (to verify)
fastboot flashing unlock
This worked for me. In the upper left corner on phone, I had to confirm that I wanted to unlock. WARNING!!! ALL USER DATA WILL ERASE!!! It took about 3 minutes.
The option is still grayed out in my Developer Settings, but it now says BOOTLOADER IS ALREADY UNLOCKED
I hope this helps you!
Chris776 said:
Greetings!
I just purchased the motorola moto g20 xt2128-1 (unlocked) from "A to Z" and I ran into these exact issues. This is what worked for me:
FASTBOOT: VOL UP + POWER
The OEM UNLOCKING option was also grayed out in my Developer Settings. After getting into FASTBOOT MODE (the exact screen in your SHORT UPDATE) on my PC, COMMAND PROMPT (admin):
fastboot devices (to verify)
fastboot flashing unlock
This worked for me. In the upper left corner on phone, I had to confirm that I wanted to unlock. WARNING!!! ALL USER DATA WILL ERASE!!! It took about 3 minutes.
The option is still grayed out in my Developer Settings, but it now says BOOTLOADER IS ALREADY UNLOCKED
I hope this helps you!
Click to expand...
Click to collapse
This really works. Did you install some recovery and some gsi?
Chris776's solution worked for me too, thanks! I didn't managed to get twrp on it yet, and I tried getting root through patching the boot file to no avail.
EDIT: I'm starting to feel maybe Chris766's solution doesn't work? The option is still greyed out although it says the bootloader is unlocked, however when trying to flash twrp or a modified boot image I always get the same error via fastboot:writing 'boot'...
FAILED (remote: Write img fail!)
If anyone has any idea...
Radiobuzz said:
Chris776's solution worked for me too, thanks! I didn't managed to get twrp on it yet, and I tried getting root through patching the boot file to no avail.EDIT: I'm starting to feel maybe Chris766's solution doesn't work? The option is still greyed out although it says the bootloader is unlocked, however when trying to flash twrp or a modified boot image I always get the same error via fastboot:writing 'boot'...
FAILED (remote: Write img fail!)
If anyone has any idea...
Click to expand...
Click to collapse
For moto device if the the bootloader is unlock, the OEM unlocking option in Dev options should be greyed.
That's normal
sd_shadow said:
For moto device if the the bootloader is unlock, the OEM unlocking option in Dev options should be greyed.
That's normal
Click to expand...
Click to collapse
Then would you know why I get that error with fastboot?
Radiobuzz said:
Then would you know why I get that error with fastboot?
Click to expand...
Click to collapse
Many people get that error with an unlocked bootloader.
what does this say?
Code:
fastboot getvar securestate
sd_shadow said:
Many people get that error with an unlocked bootloader.
what does this say?
Code:
fastboot getvar securestate
Click to expand...
Click to collapse
Literally nothing lol:
securestate:
finished. total time: 0.000s
Radiobuzz said:
Literally nothing lol:
securestate:
finished. total time: 0.000s
Click to expand...
Click to collapse
Ok, securestate should still be on the Phone's screen while in fastboot mode.
Maybe listed like one of these, but moto keeps changing the phrase.
It will be right under the battery state
Code:
Device is locked
OEM_locked
flashing_unlocked
Device is unlocked
sd_shadow said:
Ok, securestate should still be on the Phone's screen while in fastboot mode.
Maybe listed like one of these, but moto keeps changing the phrase.
It will be right under the battery state
Code:
Device is locked
OEM_locked
flashing_unlocked
Device is unlocked
View attachment 5427523
Click to expand...
Click to collapse
Ok this is what I get while the phone is booting and on fastboot:
https://imgur.com/a/u6IMWox
Radiobuzz said:
Ok this is what I get while the phone is booting and on fastboot:
https://imgur.com/a/u6IMWox
Click to expand...
Click to collapse
Thanks for the screenshots.
The first screenshot is while booting?
The second is fastbootd not fastboot(bootloader)
the bootloader is what I meant
Anyways, it does appear to be oem unlocked
sd_shadow said:
Thanks for the screenshots.
The first screenshot is while booting?
The second is fastbootd not fastboot(bootloader)
the bootloader is what I meant
Anyways, it does appear to be oem unlocked
Click to expand...
Click to collapse
Yes the first one is while the phone is booting up, it appears every time. The bootloader screen is all white and all it says is "Fastboot" and then a track ID, which are letters and numbers, nothing more. Do you have any idea why it doesn't allow me to flash anything on it?
Radiobuzz said:
Yes the first one is while the phone is booting up, it appears every time. The bootloader screen is all white and all it says is "Fastboot" and then a track ID, which are letters and numbers, nothing more. Do you have any idea why it doesn't allow me to flash anything on it?
Click to expand...
Click to collapse
I believe you should be flashing the patched boot.img in the bootloader mode
edit: if that fails use fastbootd
sd_shadow said:
I believe you should be flashing the patched boot.img in the bootloader mode
edit: if that fails use fastbootd
Click to expand...
Click to collapse
Ok I just tried that with no luck. I tried the fastboot getvar is-userspace command and it came back negative so I assume I'm not using fastbootd. I still tried it though and it just never connected (it kept on "waiting for device"), then I tried again flashing it from the bootloader (white screen) but I keep getting that "write img fail" error.
Radiobuzz said:
Ok, eu tentei isso sem sorte. Tentei o comando fastboot getvar is-userspace e deu negativo, então presumo que não estou usando fastbootd. Eu ainda tentei e nunca conectou (ficou em "esperando pelo dispositivo"), então tentei novamente fazer o flash do bootloader (tela branca), mas continuo recebendo aquele erro "write img fail".
Click to expand...
Click to collapse
when installing the corrected boot.img you have to use fastboot flash boot_a boot.img
Chris776 said:
Greetings!
I just purchased the motorola moto g20 xt2128-1 (unlocked) from "A to Z" and I ran into these exact issues. This is what worked for me:
FASTBOOT: VOL UP + POWER
The OEM UNLOCKING option was also grayed out in my Developer Settings. After getting into FASTBOOT MODE (the exact screen in your SHORT UPDATE) on my PC, COMMAND PROMPT (admin):
fastboot devices (to verify)
fastboot flashing unlock
This worked for me. In the upper left corner on phone, I had to confirm that I wanted to unlock. WARNING!!! ALL USER DATA WILL ERASE!!! It took about 3 minutes.
The option is still grayed out in my Developer Settings, but it now says BOOTLOADER IS ALREADY UNLOCKED
I hope this helps you!
Click to expand...
Click to collapse
working for me thanks!!!! any root method working? magisk maybe? going for it
Related
THIS TOOLS WORK ON LENOVO K910 DUAL SIM WITH ANDROID 4.4.x VERSION IF YOU FOUND THAT WORK ON OTHERS LET ME KNOWIF YOU HAVE ANY OTHER K910 REATHER THAN THIS IT'S YOUR RESPONSABILITY IF SOMETHING GOES WRONG!
Here are a few tools that could be very usefull that i've found here and there.
Please, feel free to link what you think that could be usefull and try to keep it in just one place for easy access. :good:
Root Your Lenovo K910 - Easy way to get rooted
Download THIS file
Connect your phone to PC through USB cable
Turn USB debugging ON
Run the file you just downloaded
Unlock you 4.4.x bootloader
Go to this thread and follow instructions from there.
Install TWRP Easy & Clean - Simple but effective way to install TWRP with just one click
Download THIS file
Connect your phone to PC through USB cable
Turn USB debugging ON
Run the file you just downloaded
Philz Touch CWM
Download Philz Touch
Copy Philz Touch Recovery to SDCARD
Reboot on your current recovery
Install the file you've copied
TWRP v2.7.1.5 - from master lie at 4pdu
Screenshots
Download TWRP v7.3.1.5
Copy TWRP v7.3.1.5 to SDCARD
Reboot on your current recovery
Install the file you've copied
TWRP v2.8.1.0
Here you can find the last TWRP available along with 6 themes.
important - This recovery isn't compatiblem with backups from other versions. To use it properly make a maback with this version after installation.
Copy the chosen theme to SDCARD
Reboot on your current recovery
Install the file you've copied
Latest K910 Roms
Here you'll find the latest version for our K910. At this moment VIBEUI_V2.0_1441_7.2.1_DEV_K910 it's the latest
All tools above work with this version
Question: What are the differencies between K910 and K910e?
Answer: Lenovo K910e VIBE Z, this is a little different from Lenovo K910 VIBE Z, because it's certified by Chinese Authorities in China. It's CDMA version. Therefore, the design and specs are almost similar to those of Lenovo Vibe Z K910. This smartphone (K910e) supports 3G:CDMA EVDO 800/1900MHz, and Lenovo VIBE Z K910 supports the all bands like 3G: WCDMA 850/900/1700/1900/2100MHz
Changelog 1441
[System]
Optimization into the dial pad and address book slow response
[Music Store]
First entered the music repair shop
Click installed the necessary permissions will not jump to the top of the page after page management fixes from multitasking
Press music store appeared flash back
[eggplant]
Fast pass new Customizable avatars, can and Apple, PC connection
[Music Cloud Notebook]
Repair notes classified in the input box click on the icon and press return to enter the upper left corner of the keyboard is not hidden
Repair music search cloud memo notes the contents of overlap with the date and time
[Cloud Services]
Repair recover data from SD card appear unresponsive cloud services
[Game Center]
Optimize the use Back button to exit the game center, not the background permanent memory into the game after the acceleration will pop up Game Center game download page to download the game to complete the repair stop running
Install Google Play - Recovery
Download GApps_4.4.2.zip and install it through recovery
Install Google Play - GMS TOOLS
Download GMS Tool and install it
Go to GMS Tool > Install Recommend > Install the 3 Packages
Reboot
Unlock Lenovo Weather Cities - This will unlock cities worldwide
Download and install xPosed
Download and install vibexpert
Open xPosed > Framework > Install / Update
Reboot
Open vibexpert > UI > Worldwide Weather App
Make any other change you want on the app
Reboot
Tools to Recover a Bricked Phone - Make sure you know what you're doing!
QPST - Qualcomm aplication to recover your phone
Drivers - Drivers needed to use QPST [If your PC doesn't recognize your phone, make sure you install according to your OS]
Lenovo Drivers - Drivers used to connect Phone-PC
HTC Mania guide from corion :good: - A guide with explain step by step how to use the above files
corion said:
Bien, primero de todo me gustaría dar las gracias a seergio por darme un rayito de esperanza. Él fue quien me comentó la existencia de la herramienta QPST (Qualcomm Product Support Tool). También a Stack de http://lefenbbs.lenovo.com/, a oscarxvita de http://forums.wpcentral.com/ y a otros tantos que no recuerdo, porque tras leerme sus tutoriales, tras tener un batiburrillo de ideas y muchas pruebas, he conseguido que mi K910 vuelva a la vida.
Decir que mi móvil estaba totalmente brickeado, no encendía, no arrancaba en recovery, ni en bootloader, ni cargaba.
======= PREPARACIÓN ==================
Para traer de vuelta a la vida a nuestro querido móvil vamos a utilizar la herramienta QPST (Qualcomm Product Support Tool). QPST es un conjunto de herramientas de Windows diseñado para interactuar, controlar, y testear teléfonos CDMA que lleven Qualcomm ASICs.
La herramienta QPST la podemos descargar de aquí
También necesitaremos este 7z para el flashearlo. Descargar aquí
======= COMENCEMOS ==================
Primero de todo es iniciar Windows con la opción de "Deshabilitar la comprobación de firmas de controladores digitales". Para ello cuanto iniciemos el sistema pulsamos F8 hasta que nos salga el menú de arranque de Windows, una vez dentro seleccionamos la opción que he dicho anteriormente.
Una vez iniciado Windows lo que debemos hacer es instalar la herramienta QPST, junto con QPST se instalarán los drivers de Qualcomm.
{
"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"
}
Como vemos, se nos habrán instalado varias herramientas. Nosotros para lo que nos traemos entre manos solo usaremos las dos que están en un recuadro rojo. eMMC Software Download y QPST Configuration.
El siguiente paso es conectar el móvil. Para que podamos trabajar con él es necesario que se conecte en modo download, para ello, pulsamos la tecla de volumen - y lo conectamos al pc. En el caso de que en el teléfono no se encienda el LED azul y el pc no detecte ningún dispositivo, hay que quitarle la batería y conectarlo sin ella. Aquí tenemos un vídeo de como quitar la tapa trasera.
Cuando conectemos el teléfono, si tenemos correctamente instalados los drivers de Qualcomm, nos debería de aparecer un nuevo dispositivo tal que así:
Si nos sale un dispositivo con un signo de admiración y llamado QHSUSB_DLOAD o QHSUSB_BULK, entonces debemos de indicarle a Windows que drivers instalar. Para ello ya sabéis, botón derecho sobre el dispositivo, Actualizar software del controlador --> Buscar software de controlador en el equipo, y le indicamos que busque dentro de la carpeta drivers, que está dentro de la carpeta QPST_K910, donde estaba el instalador del programa.
El siguiente paso es descomprimir el archivo 7z.
Cuando lo hayamos descomprimido, recomiendo cortar todo lo que hay dentro, crear una carpeta llamada bin en la raíz de alguno de nuestros discos duros, y pegar todo allí.
Seguidamente buscamos un archivo llamado flash_local.xml y lo abrimos para su edición.
La ruta que está señalada debemos de modificarla y poner la ruta donde tengamos los archivos que hemos descomprimido del arhcivo 7z. Por eso decía de ponerlo dentro de una carpeta llamada bin, en la raíz del disco duro, para que solo haya que cambiar la letra de la unidad. Bueno, pues una vez cambiada la ruta guardamos y cerramos.
Ahora toca trabajar con QPST . (Siempre que ejecutemos alguna de sus herramientas, lo debemos hacer con permisos de administrador).
1.- Ejecutamos QPST Configuration. Si todo ha ido bien nos debería de aparecer nuestro teléfono.
2.- Ejecutamos eMMC Software Download y hacemos lo siguiente:
Paso 1: En Sahara XML file, ponemos la ruta donde está el archivo XML que editamos anteriormente.
Paso 2: En el campo de Flash Programmer file name ponemos MPRG8974.mbn
Paso 3: En el campo de Boot Image ponemos 8974_msimage.mbn
Paso 4: Pulsamos en Load XML def... y seleccionamos el archivo rawprogram0.xml
Paso 5: Pulsamos en Load patch def... y seleccionamos el archivo patch0.xml
Paso 6: Desmarcamos la casilla Program MMC device
Paso 7: Pulsamos en Download y esperamos que acabe el proceso. Posiblemente, después del paso 7, nos saldrá uno o varios mensajes diciendo que se han detectado unos discos duros, que los formateemos para usarlos. DEBEMOS PULSAR EN CANCELAR.
Paso 8: Desmarcamos la casilla Programm Boot Loaders
Paso 9: Marcamos Program MMC device.
Paso 10: Seleccionamos nuestro teléfono de entre los dispositivos que aparezcan (los otros deben de ser el/los discos duros que tengamos).
Paso 11: Pulsamos en Download.
Cuando acabe el proceso desconectamos el móvil del ordenador, le metemos la batería e intentamos iniciarlo.
Espero que os sirva de ayuda.
Cualquier problema id posteando e intentaré ayudaros en lo que buenamente pueda.
Click to expand...
Click to collapse
Or you might prefer in English, Step-by-Step
Please don't fill this threat with thanks. A simple click and rate this thread will do :good:
Thank you
Crowds
XDA:DevDB Information
All Tools in One Place, Tool/Utility for the Android General
Contributors
Crowds, sash
Version Information
Status: Stable
Current Stable Version: 1
Created 2014-10-10
Last Updated 2014-10-10
XDA:DevDB Information
All Tools in One Place, Tool/Utility for the Android General
Contributors
Crowds, sash
Version Information
Status: Stable
Current Stable Version: 1
Created 2014-10-10
Last Updated 2014-11-07
Codes [UPDATE SET. 29th]
K910 Dual-SIM secret codes:
# # # # 1111 # : Engineer Mode (To test all hardware and sensors)
# # # # 537999 # : Developer Options (Full)
# # # # 0000 # : ROM Version
#### 3333 # or #### 8888 # : OffLineLog
####5236# : LCD display name
####2834# : Close ES325
####8899# : UMS Mode
Thanks @sash for those
####2222# show serial number
####5993# show software version
####7777# factory reset
####46361111# Network Info in Android 4.4
Apps You Can Freeze / Delete
I recomend a backup first in case you want something back
For obvious reasons i recomend freeze them first and only after you make sure everything works delete.
There are a few apps that despite they could be deleted without affectinf the system they afect others (i.e. browser makes some apps fail like play google).
Android Live Wallpaper
ANT Hal Service
Baidu IME
Basic Daydreams
Black Hole
Browser
Bubbles
Calendar
CarVoice
Downloads
Driving Apps
Face Unlock
File Browser
Game World
Google IME
Google Search
Google+
Hangouts
LASF SDK Lite
Le Wallpaper
Lenote
Lenovo Payment Service
Lenovo Service
Lenovo speech synthesis
Lenovo voice recognition
Lenovo Weather
Lenovo Weather Service
Lenovo Weather Theme
LenovoStore
Live Walpaper Picker
Magic Smoke Walpaper
Music
Music Visualisation
News & Weather
Phase Beam
Photo Screensavers
Players Tutorial
Print Spooler
Private Vault
Search
SecretCode
SECUREit
SHAREit
Street View
SYNCit
System Update
User Center
User Experience
Video
Voice
VoiceAssistant
Youyue
[Reserved for future use]
can i unroot the phone?
so that i can OTA update maybe? b ecause OTA update fails maybe because of root it is?
gimmeluck2 said:
can i unroot the phone?
so that i can OTA update maybe? b ecause OTA update fails maybe because of root it is?
Click to expand...
Click to collapse
You'll receive and be able to install OTA updates if the rom you're using is an "original" one.
If your rom was a developed one by someone you can't.
Doesn't have to do with the fact your phone is rooted or not.
I was able to do an OTA upgrade on my phone and it was rooted.
Anyway I think that RootGenious can unroot. Don't remember and I can't confirm atm.
Edit: witch version you have? Can you link it?
Crowds said:
You'll receive and be able to install OTA updates if the rom you're using is an "original" one.
If your rom was a developed one by someone you can't.
Doesn't have to do with the fact your phone is rooted or not.
I was able to do an OTA upgrade on my phone and it was rooted.
Anyway I think that RootGenious can unroot. Don't remember and I can't confirm atm.
Edit: witch version you have? Can you link it?
Click to expand...
Click to collapse
i have VIBEUI_V2.0_1435_7.2.1_ST_K910_WC3A official,
itcan see system update to
VIBEUI_V2.0_1437_7.44.1_ST_K910
it downloads it but
but it fails after restart. phone rooted and gapps flashed.
CAn it be because of the some chinesee system apps which i Uninstalled ( not freeze) by titanium pro?
gimmeluck2 said:
i have VIBEUI_V2.0_1435_7.2.1_ST_K910_WC3A official,
itcan see system update to
VIBEUI_V2.0_1437_7.44.1_ST_K910
it downloads it but
but it fails after restart. phone rooted and gapps flashed.
Can it be because of the some chinesee system apps which i Uninstalled ( not freeze) by titanium pro?
Click to expand...
Click to collapse
Don't believe that's chinese apps had any influence anyway, this time in order to have the latest rom follow this:
Install Rom from here [1437 is the latest atm for K910 witch is diferent of K910e]
Root your device [follow the steps from 1st post]
Install GMS Tools [follow the steps from 1st post]
Instal TWRP [follow the steps from 1st post]
1st freeze the apps you want and only then after confirm everything works at lest for 1 day you can delete the freezed apps.
note: Your problems with OTA updates may came from the deleted files
Good luck
Crowds
Crowds said:
K910 Dual-SIM secret codes:
# # # # 1111 # : Engineer Mode (To test all hardware and sensors)
# # # # 537999 # : Developer Options (Full)
# # # # 0000 # : ROM Version
#### 3333 # or #### 8888 # : OffLineLog
Click to expand...
Click to collapse
hello,
i have update my snapit camera(viberom_v1.0_1407) trough in app update. then i integrate update into rom by titanium backup. now camera cannot open even with other camera app.
i tried uninstall/reinstall apk but failed. then plan to try flash rom brought me to this thread and to this above post.
my phone fail camera test in engineer mode! will it possibly be ok after flash new rom? please help
adam_ridzuan said:
hello,
i have update my snapit camera(viberom_v1.0_1407) trough in app update. then i integrate update into rom by titanium backup. now camera cannot open even with other camera app.
i tried uninstall/reinstall apk but failed. then plan to try flash rom brought me to this thread and to this above post.
my phone fail camera test in engineer mode! will it possibly be ok after flash new rom? please help
Click to expand...
Click to collapse
That may be for 2 reasons as far as i am aware.
1. despite there's a new camere version (V.3.6.7) i might be incompatible with your version of VibeUI (is it 1.0_1407?!?! that's old)
2. Titanium Backup it's a great program but it's know for some years (at least 4) that some systenm apps may fail. Not sure if the programers had solved this in the last years since i've been out of xda for 2 years.
3. You may try to solve that this way:
Install any root explorer from market (i.e. Es File Explorer)
Go to settings > root > give permission > root again and in the pop up window choose RW for both
Go to system > app and rename SCG_arm_fhd_pro_sus.apk to SCG_arm_fhd_pro_sus.apk.bk
Make a copy of com-lenovo.sgc-1.apk to your sdcard (on data > app)
delete the file from data > app
Go to the file you just copied on sdcard and move it to system > app
Long press and choose permissions.
Check all the boxes available and reboot
See if this work if not an upgrade for the last VibeUI will do.
Hope it helps and you've understand :laugh:
Crowds said:
That may be for 2 reasons as far as i am aware.
1. despite there's a new camere version (V.3.6.7) i might be incompatible with your version of VibeUI (is it 1.0_1407?!?! that's old)
2. Titanium Backup it's a great program but it's know for some years (at least 4) that some systenm apps may fail. Not sure if the programers had solved this in the last years since i've been out of xda for 2 years.
3. You may try to solve that this way:
Install any root explorer from market (i.e. Es File Explorer)
Go to settings > root > give permission > root again and in the pop up window choose RW for both
Go to system > app and rename SCG_arm_fhd_pro_sus.apk to SCG_arm_fhd_pro_sus.apk.bk
Make a copy of com-lenovo.sgc-1.apk to your sdcard (on data > app)
delete the file from data > app
Go to the file you just copied on sdcard and move it to system > app
Long press and choose permissions.
Check all the boxes available and reboot
See if this work if not an upgrade for the last VibeUI will do.
Hope it helps and you've understand :laugh:
Click to expand...
Click to collapse
I understand, but the problem is, there is no com-lenovo and scg_arm. Any idea"?
adam_ridzuan said:
I understand, but the problem is, there is no com-lenovo and scg_arm. Any idea"?
Click to expand...
Click to collapse
You should have some scg file. tha't the one related with camera
Crowds said:
You should have some scg file. tha't the one related with camera
Click to expand...
Click to collapse
Then that will be the main problem I think. Proceed to flash latest rom. Tq very much
DEAD K910
Good day, please accept my apologies if this is posted in the wrong area of the forum. I have a Lenovo K910 dual SIMM unit from China. One of our employees (we sell these devices) was attempting to return the unit to factory default and has managed to completely destroy the unit. It will not show any display and will not vibrate when switched on. All that happens is the red LED will flash almost every second when plugged into a PC. The device will only show up as a fastboot device with the device listed as 'bf2b867 fastboot'. I have tried loading several different QPST drivers to try work with the QPST tools but to no avail.
Thanks for your time Any help would be most appreciated.
RASTAS12 said:
Good day, please accept my apologies if this is posted in the wrong area of the forum. I have a Lenovo K910 dual SIMM unit from China. One of our employees (we sell these devices) was attempting to return the unit to factory default and has managed to completely destroy the unit. It will not show any display and will not vibrate when switched on. All that happens is the red LED will flash almost every second when plugged into a PC. The device will only show up as a fastboot device with the device listed as 'bf2b867 fastboot'. I have tried loading several different QPST drivers to try work with the QPST tools but to no avail.
Thanks for your time Any help would be most appreciated.
Click to expand...
Click to collapse
Hi there
First of all don worry about posting here. You're at the right place.
OK, regarding your question, i can affirm by my own experience, that the phone isn't dead. I'ts almost but it isn't
Latter i will write a more detail step-by-step but for now i think this will do.
By your explanation, you must remove your battery and keep it that way. If you don't know how check this video. I had to do that
Read next post
1. It's better if you work on a complete clean PC. This was the only way i'be been able to recover mine after ONE MONTH!!! I use Win8.1 and just installed the updates from microsoft.
2. Download all the files posted on 1st post in the "Tools to Recover a Bricked Phone" section
3. Download QPST file from here. This is the original Lenovo files to restore
4. Install QPST and then rebbot with "Disable signature verification of digital controllers" checked
5. Open Device Manager
6. Connect your phone to PC through a USB cable pressing VOL-. I recommend that you use and old USB extension cable. We want this to slow down the information between phone and PC and COM port doesn't disapear in a blink of an eye.
--- If VOL- doesn't work try several combinations, like VOL+/USB cable or VOL-/VOL+/USB ---
7. By this time your PC began searching for the correct drivers. If everything went ok, device manager will see android phone as QHSUSB_DLOAD or QHSUSB_BULK
8. Install the drivers manually from the drivers folder you've just downloaded (Install accordly to your OS version)
9. Install Lenovo drivers
10. Reboot as in step 4
--- Now it's when the real work begin ---
11. Open Device Manager and QPST Configuration (as administrator) from the instaled folder
12. Connect your phone through USB extention cable again and check if Device manager are ok (Something like Qualcoom_something) and if QPST Configuration starts something. If so, you're good to go.
Now probably this is the part when you ask 700€ on your customer or send the phone back to repair
This is a trial and error work. COM port will only be visible for a breef momment. The time you pressed ENTER key is the real key to manage go further
Make sure that flash_local.xml had the right path, like:
Step 1: Sahara XML file, put the path where the XML file is edited above.
Step 2: In the field of Flash Programmer put MPRG8974.mbn
Step 3: In the field Boot Image put 8974_msimage.mbn
Step 4: Then hit def XML Load and select the file rawprogram0.xml
Step 5: Then hit def patch Load and select the file patch0.xml
Step 6: Program uncheck the box MMC device
Step 7: Then hit Download and hope to finish the process. Possibly, after step 7, we will get one or more messages saying that some hard drives have been detected, the formateemos to use. MUST CLICK CANCEL.
Step 8: Uncheck the box Boot Loaders Programm
Step 9: Mark Program MMC device.
Step 10: Select your phone from the devices that appear (the other must be / have hard drives).
Step 11: Then hit Download.
When the process ended, Insert the battery and try to start it but keep the phone connected to PC this is important because your battery is completely dead atm.
I hope this will help you.
Like i said i've been one month without my phone but after i decided to format all my driver and install Win from scratch this will only take me half an hour till i get the DW mode.
Good luck:good:
Chears
Crowds
RASTAS12 said:
Good day, please accept my apologies if this is posted in the wrong area of the forum. I have a Lenovo K910 dual SIMM unit from China. One of our employees (we sell these devices) was attempting to return the unit to factory default and has managed to completely destroy the unit. It will not show any display and will not vibrate when switched on. All that happens is the red LED will flash almost every second when plugged into a PC. The device will only show up as a fastboot device with the device listed as 'bf2b867 fastboot'. I have tried loading several different QPST drivers to try work with the QPST tools but to no avail.
Thanks for your time Any help would be most appreciated.
Click to expand...
Click to collapse
Here you can follow my Step-by-Step Tutorial.
This is a long and exhaustive one but i think it will cover all possible aspects.
In your case specifically you need to follow the instructions on post #6 before applying what's written on post #5
Read carefully or you have 2 more possibilities.
Return phone to the owner and give him my link
Sent the phone back to china and ask to your customer big, big money
:laugh::laugh::laugh:
C hears
Crowds
Crowds said:
Here you can follow my Step-by-Step Tutorial.
This is a long and exhaustive one but i think it will cover all possible aspects.
In your case specifically you need to follow the instructions on post #6 before applying what's written on post #5
Read carefully or you have 2 more possibilities.
Return phone to the owner and give him my link
Sent the phone back to china and ask to your customer big, big money
:laugh::laugh::laugh:
C hears
Crowds
Click to expand...
Click to collapse
Crowds you are a champion. I have just arrived at work and will now start as per your instructions. I can not thank you enough for the time you have put into this. I will revert when done and let you know how things pan out. Once again huge thanks for your time.
Crowds said:
Latest K910 Roms
Here & Here you'll find the latest version for our K910. At this moment VIBEUI_V2.0_1437_ST_K910 it's the latest [I said K910 not K910e]
All tools above work with this version
Question: What are the differencies between K910 and K910e?
Answer: Lenovo K910e VIBE Z, this is a little different from Lenovo K910 VIBE Z, because it's certified by Chinese Authorities in China. It's CDMA version. Therefore, the design and specs are almost similar to those of Lenovo Vibe Z K910. This smartphone (K910e) supports 3G:CDMA EVDO 800/1900MHz, and Lenovo VIBE Z K910 supports the all bands like 3G: WCDMA 850/900/1700/1900/2100MHz
Changelog
[Recommend]
New Bubble lock screen
New fantasy lock screen
Prompt notification of new fully charged
Talking Alarm Clock humane optimization improvements
The new interface optimized video and operating experience
[System]
New integrated andorid new boot animation pictures
After the new OTA upgrade was successful, increasing switching Huan Jing and bubble lock screen theme guide
[Video]
Optimize the new interface and operating experience
[Clock]
New data update holidays to get data from the clock yourself, holidays can support up to 4.2 system
Add a timer to remind expression interface adjustment and optimization of terms
New World clock search areas of the city, you need to have fuzzy search capabilities, including Pinyin, English, letters, characters
Press the home button automatically suspended new, user-friendly alarm pause
New calls during alerts
New animation timer guide
Talking Alarm Clock humane optimization improvements
[Notification Center]
Prompt notification of new fully charged
Multi-task optimization and optimization of layout adjustment, screenshots large view more user-friendly operation and use
Optimization Memory Optimization
Repair certain application multitasking interface is black thumbnails
[Lenovo lock screen]
New Bubble lock screen
New fantasy lock screen
New digital lock digital position random option
Added option to simplify operator information
Optimization of anti inadvertently specification improvements, the situation did not reduce the protection of lives
[Lenovo Services Framework]
Optimization optimized interface, maintain and vibe2.0 style consistency; code optimization to improve performance
Crowds
Click to expand...
Click to collapse
Kindly, Explain how to install the latest ROM. I just bought Vibe Z k910 and I need to update its rom from vibeui v1.5 to v2.0.
Are there other tools should I use to update the rom?
Thanks
agsao said:
Kindly, Explain how to install the latest ROM. I just bought Vibe Z k910 and I need to update its rom from vibeui v1.5 to v2.0.
Are there other tools should I use to update the rom?
Thanks
Click to expand...
Click to collapse
Download last rom and copy to sdcard
see if you have twrp installed if not dw from 1st post and follow instructions
then enter in twrp by rebooting and keep pressed 2 vol buttons till lenovo logo appear
install from there
Thanks for your cooperation, but excuse me I am new with android could you check the following steps if these are ok or there is something missing:
1. I rooted my phone with RootGenius
2. I installed TWRP and I checked it works well
3. I downloaded the latest ROM VibeUi_V2.0_1437_K910 as my phone version K910
4. I should placed the new rom in my "internal memory" on root --- I've no external SD slot ---
5. I should enter TWRP by rebooting phone and keeping 2 volume buttons pressed.
6. Should I backup something ????
7. On TWRP Wipe >> Swipe to factory reset
8. On TWRP Install >> Select the new ROM from the internal memory ????
9. On TWRP Wipe >> Advanced Wipe >> select Cache & Dalvik Cache >> Swipe to Wipe
10. Reboot
11. Install GMS Tools then Google Play
==> I don't know is the new software rooted or not? Can I delete Chinese app without rooting?
==> What is the need of "Tools to Recover a Bricked Phone" as shown in above instruction?
sorry for long questions and sorry for my language "from Egypt"
but I have to make sure that I'll follow the right steps first.
Thanks alot
THIS IS A COMPILING GUIDE FOR CREATE YOUR PACK TO UPDATE YOUR Z1 (C6943 THE BRAZILIAN VERSION WITH DTV) FOR THE 14.4.A.157 OFICIAL FIRMWARE WITH ROOT, DEODEXED AND 4K.
1 - First of all you need to create your FTF file of the 14.4.A.157 for your specefically version (C6943).
ALREADY DONE FILE HERE (JUMP TO STEP 2) THANKS TO @RHBH.
A- Download and install the Flashtool. (don't forget to update to the latest version always)
B - After installed go to the tab DEVICES -> CHECK UPDATES -> select the xperia z1 -> select the tab C6943 and double tap the 1276-7099 CUSTOMIZED BR like on the image bellow, after this you gonna start to download the firmware.
{
"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"
}
C - When conclued on the next window that will apear just move all the files from the left side (folder list) to the right side (firmware content) then click on create and wait to your FTF file be created, after this you file will be on the firmware folder of the flashtool ready to be flashed.
2 - Now it's time to flash, just open the flashtool, click on the first icon 'lightning bolt' and select the flashmode, now select the correct firmware and click on flash, don't do nothing more then that, after this connect your Z1 holding the button VOLUME DOWN, the flashing process will start.
3 - After this you will need to get root, so download this files KERNEL .108 FOR C69XX, KERNEL .157 FOR C6943 and the root tool
A - Open Flashtools, click the 'lightning bolt' icon and select the firmware 108. Click FLASH and plug the phone on computer holding the volume down.
B - In just a few seconds the app warns you that the procedure is finished and it will tell you to restart, do it.
C - Start your phone, check out on options if "USB Debugg" and "Unknown Applications" are enabled and Apply the Root with the root tool.
D - extract the root tool and plug your device into your comput.er
E - Run install.bat and follow the instructions on screen it's easy.
F - After the root process is done, check if your phone is really rooted then Turn off the phone.
G - now just repeat the step A with 157 specific firmware for C6943.
4 - Time to install the RECOVERY
A - Download the correct version from NUT'S DATABASE chose the latest version of the file "Z1-lockeddualrecovery[VERSION]-BETA.installer.zip"
B - After downloaded and extracted, plug in your phone with "USB Debugg" and "Unknown Applications" enabled and run install.bat, now just select the right option and follow the instructions, is pretty easy too.
5 - After done, it's time to deodex your rom, download this KIT.
ALREADY DONE FILE HERE, JUST IGNORE THE INSTRUCTIONS TO CREATE THE FILE.
A - Extract downloaded tool and Run main.bat.
B - Type 1 to create working folder.
C - Don't forgetting to enable the USB Debugging, Plug in your phone, then type 2 to pull files from your device. (This step can be skipped if you manually copy /system/app, /system/framework, /system/priv-app to /Kitkat_Deodexer/system)
D - Type 3 to start deodexing and Type 4 to create flashable zip.
E - Move the .zip to your sd card then turn on the phone on the recovery. (when the phone starts to boot and a green light shows up press VOLUME DOWN, the light will turn on purple and the phone will enter on the recovery mode)
F - Now just flash the .zip on the recovery and it's all done.
6 - Now it's time to install the 4K. You can use this video guide too.
A - Download this files, MOD, Serajr XPERIA and the XPOSED INSTALLER.
B - Move all the files to the sd card.
C - Just open and install the XPOSED INSTALLER and the Serajr Xperia in this order.
D - Open the XPOSED INSTALLER, go to FRAMEWORK, INSTALL and REBOOT
E - Now go to MODULES, Activate(check) the Serajr XPERIA and REEBOT AGAIN.
F - After this, go to the app menu and open the XPERIA XPOSED, go to system and ENABLE CUSTOMIZATIONS (CHECK IF SUPER USER MODE IS ENABLED TOO)
E - Now just turn off your phone and go to the RECOVERY MODE AGAIN.
F - Flash the "MOD" file on the recovery and wipe the dalvik cache.
G - ALL DONE, XPERIA Z1 ROOTED, DEODEXED and with 4K. :highfive:
IF YOU DID EVERYTHING GREAT DON'T FORGET TO COMMENT, WILL BE MY BEST REWARD.
c6943 patch please
dstrikersZ1 said:
c6943 patch please
Click to expand...
Click to collapse
This is exacly what i said... How to create the package step by step to the C6943. I just don't have how now to make the update. zip already done.
alexandre221 said:
This is exacly what i said... How to create the package step by step to the C6943. I just don't have how now to make the update. zip already done.
Click to expand...
Click to collapse
But, It's very difficult
dstrikersZ1 said:
But, It's very difficult
Click to expand...
Click to collapse
it's not dificult, just have a lot of steps cause i explained in details.
Hey @alexandre221 could you successfully create the deodex flashable zip? I tried here but something is going wrong
Can you tell me what's DTV ?
DIGITAL TV, exclusive function of the C6943
I´ve a custom kernel(trinity kernel) installed, this guide works with it? Will I lose the trinity kernel?
by the way, DTV is Digital TV.
dstrikersZ1 said:
Can you tell me what's DTV ?
Click to expand...
Click to collapse
DIGITAL TV, exclusive function of the C6943
jowjony said:
Hey @alexandre221 could you successfully create the deodex flashable zip? I tried here but something is going wrong
Click to expand...
Click to collapse
i've seeing that some users are relating some problems with this tool to deodex on this firmware version, you can try this other tool too, tell me if works properly, by the way, before you try to deodex, you followed all the steps on my guide since the beggining, creating the FTF, FLASHING AND ETC... ?
sergiopa said:
I´ve a custom kernel(trinity kernel) installed, this guide works with it? Will I lose the trinity kernel?
by the way, DTV is Digital TV.
Click to expand...
Click to collapse
yep, you gonna lost your custom kernel, maybe when you gonna flash the FTF with flashtool you can exclude the kernel from the flashing process, which i really don't recomend, but the FTF have a new whole system, this include a new kernel that btw you gonna have to change and rechange on the root process for this version on the step 3, so i can't confirm to you once that i never changed my kernel and not even unlocked my bootloader, in my opinion, if you keep wanting a custom kernel, you should do the whole process and after that you would install your custom kernel back, I think it would be less risky and easier
alexandre221 said:
i've seeing that some users are relating some problems with this tool to deodex on this firmware version, you can try this other tool too, tell me if works properly, by the way, before you try to deodex, you followed all the steps on my guide since the beggining, creating the FTF, FLASHING AND ETC... ?
Click to expand...
Click to collapse
Nope I didn't, I only want to move to 157 if I'm sure it can be deodexed. So I'm trying to make a flashable deodex patch before moving to 157. I hope @RHBH can help us with that da uma força ae brow! Valew!
jowjony said:
Nope I didn't, I only want to move to 157 if I'm sure it can be deodexed. So I'm trying to make a flashable deodex patch before moving to 157. I hope @RHBH can help us with that da uma força ae brow! Valew!
Click to expand...
Click to collapse
cara então como que você tentou deodexar se primeiro você precisa ter a ROM .157 instalada pra ai sim usar a ferramenta do tutorial, tu instala o firmware no z1 executa a ferramenta para deodexar conecta o celular no pc ja roteado e com usb debug e ai sim a ferramenta vai copiar os aplicativos do sistema do celular para deodexar e criar o arquivo zipado para depois dar flash pelo recovery sendo do mesmo jeito para a outra ferramenta para esse mesmo processo caso a primeira nao funcione.... e realmente o @RHBH sumiu da cena, ele sempre fazia os zips deodexados, por ele nao fazer pra esta versão decidi iniciar esse tópico
Hello all!
I'm not gone... Just dedicated to my work... I'll deodex this for you guys, didn't know about this new FW, what changed from .108 to .157?
Regards,
RHBH said:
Hello all!
I'm not gone... Just dedicated to my work... I'll deodex this for you guys, didn't know about this new FW, what changed from .108 to .157?
Regards,
Click to expand...
Click to collapse
Thank you very much @RHBH I hope this update make the Z1 better so maybe I can wait for Z5 lol Aeeeew valeu, espero que de certo quem sabe o z1 fica melhor e de pra aguentar até o Z5
jowjony said:
Thank you very much @RHBH I hope this update make the Z1 better so maybe I can wait for Z5 lol Aeeeew valeu, espero que de certo quem sabe o z1 fica melhor e de pra aguentar até o Z5
Click to expand...
Click to collapse
I just bought a Z3, people are saying that with Z4 Sony will stop their 6-month flasgship cycle, if this is true Z5 only in 2016.
Tem outras formas de copiar o conteúdo da rom sem ela estar instalada, e assim eu tentei o deodex mas dava erro e o meu medo seja tentar instalar esse deodex que deu erro e travar tudo igual já fiz uma vez ! Mas com a ajuda do @RHBH vou sem medo, instalei todos os deodex que ele criou e tudo funfa 100% xD
jowjony said:
Tem outras formas de copiar o conteúdo da rom sem ela estar instalada, e assim eu tentei o deodex mas dava erro e o meu medo seja tentar instalar esse deodex que deu erro e travar tudo igual já fiz uma vez ! Mas com a ajuda do @RHBH vou sem medo, instalei todos os deodex que ele criou e tudo funfa 100% xD
Click to expand...
Click to collapse
que metodo que você usa ? gostaria de saber
RHBH said:
Hello all!
I'm not gone... Just dedicated to my work... I'll deodex this for you guys, didn't know about this new FW, what changed from .108 to .157?
Regards,
Click to expand...
Click to collapse
wow, thanks dude =D, your presence here is really unexpected hahah, we all will be waiting for your version of this firm, i have tried to contact you and the people on the brasildroid forum to help with this new version, cause that forum always have good tutorials for the Z1, but the forum seems really dead, so i decided to try to make this guide for my own.
Hi All,
I locked the bootloader of my MI 9SE and after the lock device doesn't start and shows "the system has been destroyed".
I can only enter in fastboot. Is there a possibility to fix it?
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Ok, solved
I relocked the bootloader with Mi Flash by flashing latest global firmware and selecting the option "clean all and lock". It worked.
Just an hint: when a I locked the bootloader I didn't have the MI account associated to the phone, for this reason I thinked that I couldn't unlock again the phone.
This is not true, if you log in in Mi Unlock with the same Mi account you used to unlock the first time it works even if it is not currently associated to the phone
MI9 se - MAJ OTA - le système a été détruit
Bonjour,
le bug s'est produit il y a 1 mois lors d'une maj demandé par XIAOMI, l'écran après le redémarrage a indiqué " the system has been destroyed ", il y avait d'ailleurs dans le répertoire download le fichier : miui-blockota-grus-eea-global-v10.2.9.0.PFBEUXM-v10.3.9.0PFBEUXM-13f0db, c'est donc la maj de MIUI v10.2.9.0 à 10.3.9
Sur xiaomi.eu/community, il est clairement indiqué que c'est un pb provenant du fichier ota, qui date du mois juin, et que xiaomi travaille pour le résoudre. Très bizarrement, sur les discussions, des coches vertes indiquent que le pb est résolu, alors qu'aucune solution n'est proposée !
Il est aussi écrit qu'il faut contacter le SAV XIAOMI, ce que j'ai fais, il m'a demandé de réinitialiser aux paramètres d'usine, mais après le redémarrage, on retrouve " the system has been destroyed " ! Maintenant, il vont vérifier la garantie, a suivre, je vous tiendrai informé.
En attendant, avec miniADB+ fastboot, on arrive a redémarrer, mais en MIUI v10.2.9.0, mais plus de MAJ, et en cas de batterie déchargée, impossible de redémarrer sauf a avoir un ordi avec miniADB+ fastboot.
Je constate :
- MIUI est une surcouche pour ANDROID faite par XIAOMI
- c'est la MAJ de MIUI V10.3.9 qui cause ce problème
- sur MIUI, suite au post indiquant que XIAOMI travaille pour résoudre le pb, aucune solution n'est donné, les discussions sont indiquées comme étant résolus, et puis plus rien
Je pense que la MAJ MIUI a créé un bug dans ANDROID, et qu'il faut réinstaller dans la ROM du téléphone l' opérating systéme complet ANDROID avec MIUI en version 10.3.9 ou supérieure, d'ou des solutions avec MIFLASH, bootlader débloqué, mais toujours su MIUI, des posts indiquent qu'un particulier ne peut plus le faire car XIAOMI veut nous obliger à recourir à son SAV en FRANCE, si ils veulent bien, généralement le téléphone renvoyé n'est pas le votre, et probablement avec des tarifs exorbitants,
A se demander si XIAOMI est toujours fidèle à lui même !
Tous vos avis, réactions et commentaires seront les bienvenus,
Cordialement
ErriK89 said:
Ok, solved
I relocked the bootloader with Mi Flash by flashing latest global firmware and selecting the option "clean all and lock". It worked.
Just an hint: when a I locked the bootloader I didn't have the MI account associated to the phone, for this reason I thinked that I couldn't unlock again the phone.
This is not true, if you log in in Mi Unlock with the same Mi account you used to unlock the first time it works even if it is not currently associated to the phone
Click to expand...
Click to collapse
hi,
it's a long time but after you relocked the bootlooader with mi flash, can you use netflix and google pay?
thanks
Errik 89 can u help me to unlock k20 pro
ErriK89 said:
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Click to expand...
Click to collapse
Errik 89 can u help me to unlock k20 pro
ErriK89 said:
Ok, solved
I relocked the bootloader with Mi Flash by flashing latest global firmware and selecting the option "clean all and lock". It worked.
Just an hint: when a I locked the bootloader I didn't have the MI account associated to the phone, for this reason I thinked that I couldn't unlock again the phone.
This is not true, if you log in in Mi Unlock with the same Mi account you used to unlock the first time it works even if it is not currently associated to the phone
Click to expand...
Click to collapse
Hey, @ErriK89 how could you unlock the bootloader on a device showing "the system has been destroyed"?
I am facing the same issue, access possible only with "fastboot" but I am unable to flash anything.
MasterLog80 said:
Hey, @ErriK89 how could you unlock the bootloader on a device showing "the system has been destroyed"?
I am facing the same issue, access possible only with "fastboot" but I am unable to flash anything.
Click to expand...
Click to collapse
Hi, sry for late answer. It's easy: use the same procedure you use as you are unlocking the bootloader with the phone normally working.
Open Mi flash unlock and follow the procedure, enter the MI account you used to unlock the phone for the first time.
ErriK89 said:
Hi, sry for late answer. It's easy: use the same procedure you use as you are unlocking the bootloader with the phone normally working.
Open Mi flash unlock and follow the procedure, enter the MI account you used to unlock the phone for the first time.
Click to expand...
Click to collapse
Thanks @ErriK89,
I have tried to unlock by using "Mi Unlock" but per attached screenshot and I can't proceed.
I used the same account on the phone before the issue occurred, but I have never any related settings: I think you may have done something before (probably you have requested to unlock the bootloader per 3 and 4 on https://c.mi.com/thread-1857937-1-1.html ????).... Did you?
Regards,
Hello guys,
I am still unable to unlock the device or reinstall a new OS.
Most likely if the bootloader wasn't unlocked (before) by the phone, it will stay lock and it's not possible to restore the OS.
Any suggestions welcome.
Regards,
Hello guys,
After a lot of investigation I come to the conclusion that to fix the issue "the system has been destroyed" in a device unable to start on recovery and with bootloader locked, it's required a Xiaomi authorized account, which is NOT provided to normal users.
Then, it's possible to proceed with "Mi Unlock" or "SP Flash tool" to reinstall the firmware.
I have seen that some guys connect by remote with their account for money, it may worth a try.
Regards,
MasterLog80 said:
Hello guys,
After a lot of investigation I come to the conclusion that to fix the issue "the system has been destroyed" in a device unable to start on recovery and with bootloader locked, it's required a Xiaomi authorized account, which is NOT provided to normal users.
Then, it's possible to proceed with "Mi Unlock" or "SP Flash tool" to reinstall the firmware.
I have seen that some guys connect by remote with their account for money, it may worth a try.
Regards,
Click to expand...
Click to collapse
Hello,
I have same error, I tray many ways, but bootloader is locked.
How are you doing? unlock your bootloader?
ErriK89 said:
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Click to expand...
Click to collapse
Hey bro i brick my 9 se, please help me add me on Facebook:
ErriK89 said:
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Click to expand...
Click to collapse
Hey bro help me i brick my 9 se
Contact me please:
Gian Quispe Mendoza
Gian Quispe Mendoza is on Facebook. Join Facebook to connect with Gian Quispe Mendoza and others you may know. Facebook gives people the power to share and makes the world more open and connected.
www.facebook.com
Guys, if in your phone the bootloader was already unlocked before to re-lock it or to obtain the error "system has been destroyed" it can be easily fixed by unlocking it again. It's just sufficient to use Mi Unlock tool, log-in with the account with which the bootloader was unlocked and unlock it. Once unlocked you can use MiFlash to flash the latest rom and if you neet to safely re-lock the bootloader.
If you never un-locked the boot loader there is no way, you need to send the phone to assistance through an authorized xiaomi center, because only with an autorhized account the bootloader can be unlocked if it's never unlocked with standard procedure before
Hi guys, I need a little help, what happens is that I went to the settings to unlock the bootloader and then proceeded to flash a rom, but after this I got the error "system has been destroyed" Does it mean that to fix it I need to wait for my bootloader to unlock? I forgot that I had to wait a week and I'm not sure what this is because of not waiting or another error, I would also like to know if after time I can fix it since using the MI unlock tool from xiaomi tells me that wait for the time and use the my flash tool to install the stock rom it drops the error "erase is not allowed in lock state"
Hello, thanks for your explanation
I have a question :
If I remove my mi account from the settings and my mobile brick after relocking....
Can I unlock it again?
ErriK89 said:
Guys, if in your phone the bootloader was already unlocked before to re-lock it or to obtain the error "system has been destroyed" it can be easily fixed by unlocking it again. It's just sufficient to use Mi Unlock tool, log-in with the account with which the bootloader was unlocked and unlock it. Once unlocked you can use MiFlash to flash the latest rom and if you neet to safely re-lock the bootloader.
If you never un-locked the boot loader there is no way, you need to send the phone to assistance through an authorized xiaomi center, because only with an autorhized account the bootloader can be unlocked if it's never unlocked with standard procedure before
Click to expand...
Click to collapse
im sure that i have unlocked my bootloader before but i turned it off....thats why i have a mi account but, i get an error and telling me this, what should i do?
im facing the the system has been destroyed.
i got this when i was downgrading my miui from 12.0.3 to 12.0.2
there was a feature that got removed so i did downgraded, but i made a mistake... i didnt select the reset or format or erase data before installing the older version of rom 12.0.2.... i have downgraded before and it was succesful....
and now, i cant unlock my device, its asking me to do this,
please reply i really need help..
ErriK89 said:
I solved by unlocking again the bootloader, but I need to lock it.
Is there a safe procedure the relock the bootloader without get this error?
I have a global mi 9se with official firmware installed
Click to expand...
Click to collapse
how i unlock my bootload ....my bootloader was unlocked before the command......but i have not login my xioami account
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
reserved
Arobase40 said:
Ok, I feel happy for you you succeeded to root your phone with your camera working and you pass the SafetyNet test by activating Zygist with safetynet-fix v2.2.1, but what have you done differently from my guide as you as you just got updated information from my thread ?
You passed SafetyNet test and so what next ???
Have you got Samsung Secure Folder, Samsung Health or Samsung Pay working or such other protected Samsung apps ???
Are you getting Xprivacylua or AfWall+ (may be this one but not sure) working ???
Firefds kit [R] is not yet update to be compatible with Android 12, so it only partially works...
On my Galaxy Note 9, I didn't pass SafetyNet test, but Samsung Secure Folder, Google pay, Samsung Health are fully working... ^^
Samsung Pay is working but only with a Samsung Watch...
With another configuration I passed SafetyNet test but all above apps aren't working at all !!! ^^
I don't mind you created another thread and another guide on how to root the A528B but what is the interest if you don't explain how you improved mine and what new features you got ???
Click to expand...
Click to collapse
A. I didn't read your guide since your guide openly says it doesn't work with camera
B. I needed camera so I created my own guide where the camera works and it is here for everyone to read
testestestest said:
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
Click to expand...
Click to collapse
Ok, I confirm this works!! Way to go sir. Thanks so much and I encourage everyone to do this method. WooHoo
Arobase40 said:
Ok but does it changes anything since my post #218 of my own guide ?
Click to expand...
Click to collapse
not that i can tell
Arobase40 said:
UPDATED : How to root Galaxy A52S 5G (SM-A528B)
This is a highly updated tutorial on how to root the Galaxy A52S 5G (SM-A528B) phone based on new version of Magisk and from feedbacks I received from users after the release of the first guide version ! ;) This guide should work with other...
forum.xda-developers.com
As I was myself trying to use Zygist with SafetyNet 2.2.1 version even though I didn't mention it explicitely as Safetynet 2.2.1 is only working with Zygist ?
"Ok, nice try mate but Zygisk-LSPosed is even worse !!!
It broke FoxMagiskModuleManager when Zygisk-LSPosed has very poor modules list. It broke AfWall+ and it partially broke Firefds kit and no progress at all with Samsung apps !!!"
Does this still apply ?
Click to expand...
Click to collapse
yes as far as lsposed goes, never used the fox app or afwall so can't say. no gravity box for android 12 yet
Arobase40 said:
So that means that since my post #218 no one with failed camera has installed SafetyNet Fix 2.2.1 with Zygist and no one has checked if that has an impact on the camera, and thus no report to me ??? lol
I just remind you that my camera has always been working so I couldn't expected any changes on this aspect... ^^
Finally, if my guide offered "limited root", this one offers even more limited one as with the exception of AdAway what this root stands for if you can't at least protect your privacy ???
Click to expand...
Click to collapse
you are lucky enough to be in a region that allows the camera to function while boot loader is unlocked
One thing I've noticed, after a restart the camera fails until closing it and killing the app in recent apps, then it works.
testestestest said:
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
Click to expand...
Click to collapse
thank you very much )))) I will try this weekend!
Guys, can anybody explain to me , why Samsung is apparently making it so hard for the customers to root their devices? Is it a problem with Samsung or with Magisk, or both?
Not being able to root via Magisk is a real dealbreaker to this otherwise well-specced phone (at least it is to me!).
Going to try this method with Android 11 using Magisk 24.3 and safety net 2.2.1 which I hope will allow the camera to work also.
Edit: It works with android 11.
Arobase40 said:
Why wouldn't it work with Android 11 as it is not related ???
You mean you downgraded to Android 11 and got stuck with a very old security patch just to get GravityBox and probably with Firefds Kit [R] working ??? lol
Click to expand...
Click to collapse
Yes, yes and yes. LOL and better battery life too
I've had no bootloops when changing things FireFDS and I'm glad to have a working gravity box... I'll report battery after a few days.
testestestest said:
Guys, I DID IT !!!!
Click to expand...
Click to collapse
Hi, I'm new here and I bought the A528B, I don't speak English and I use google translate... maybe this is asking too much but a step by step video would be too much to ask? having to translate it costs me a lot trying to follow the guide...
I don't understand how I have to do to be able to root it and have the camera working
bobfrantic said:
Ok, confirmo que esto funciona!! Bien hecho señor. Muchas gracias y animo a todos a hacer Desbloquee el gestor de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
Click to expand...
Click to collapse
testestestest said:
Chicos, LO HICE!!!!
Samsung A52s (SM-A528B/DS) en funcionamiento con cargador de arranque desbloqueado, rooteado (Magisk), pasando SafetyNet y CÁMARA DE TRABAJO (yaaay).
El problema es que no tengo idea de cómo lo hice, porque fueron 3 días de flashear, parchear, reinstalar y bloquear el teléfono también (desafortunadamente).
Adjunto una captura de pantalla que hice con el teléfono mientras escribía esta publicación en Word. Alguien quería capturas de pantalla en pantalla dividida como prueba, así que... boom, aquí tienes.
Tengo muchas fotos que hice en los últimos 3 días, así que intentaré escribir algunas instrucciones más detalladas pronto. Pero ahora al menos prueba esto:
Esto debería funcionar para cualquier persona, incluso para las personas que no tendrán una cámara en funcionamiento después de desbloquear el gestor de arranque.
1. Descargue el último firmware y Odin de samfw.com (no sé por qué, pero estos fueron solo uno que se cubrieron para mí, bloquearon mi teléfono antes con un firmware diferente)
2. Descomprima el firmware descargado y copie AP a un teléfono con Magisk 24.1
3. Use la aplicación Magisk para parchear el archivo AP y descárguelo nuevamente a la PC
4. Desbloquee el cargador de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
5. Reiniciar
6. Vaya al modo de descarga (debería ver OEM: APAGADO (U))
7. Flashee con Odin todos los archivos de Firmware que descargó, pero a AP puso el archivo parcheado
8. Reiniciar
9. Vaya a magisk, haga lo que quiera, reinicie, en la configuración active el host integrado, active Zygisk, reinicie, descargue e instale el módulo kdrag0n's safetynet-fix v2.2.1 ( https://github.com/kdrag0n/safetynet -fix/ lanzamientos )
10. reiniciar
11. siiii
ACTUALIZACIÓN: Ok, parece que el software de la cámara fallará después de reiniciar una vez. Cuando lo cierras y lo abres de nuevo, funciona.
CONFIRMADO: Tuve que volver a flashear después de probar TWRP y ahora puedo confirmar que parchear "safetynet-fix v2.2.1" te permitirá usar la cámara después de una ejecución. La aplicación Samsung Cam fallará en la primera ejecución, por lo que cuando la elimine en el conmutador de aplicaciones y vuelva a ejecutarla, funcionará de manera normal (cambiando de cámara, frontal/trasera y todo).
Click to expand...
Click to collapse
EL DESBLOQUEO DE ARRANQUE ES ANTES O DESPUES DE PARCHEAR EL AP
Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.
ch3mn3y said:
Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.
Click to expand...
Click to collapse
Well then, there you go. You got bootloop for not following the instructions
Did i understand right?
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
Click to expand...
Click to collapse
These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?
luffy786 said:
Did i understand right?
These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?
Click to expand...
Click to collapse
You can install the Magisk app without being rooted. It's an app like any other app, you simply won't have root access. So install it on your A52s 5G and patch your files with it.
Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?
BlueChris said:
Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?
Click to expand...
Click to collapse
Well, I added these 2 lines:
wlan.wfd.hdcp=disable
wifi.interface=wlan0
On the following files:
product/etc/build.prop
system/build.prop
system/system_ext/etc/build.prop
vendor/build.prop
vendor/default.prop
I'm pretty sure not all of them are needed but I'm too lazy to figure out which prop file really needs it lmao if I had to take a guess I'd say either vendor build.prop or default.prop, who knows.
Hello XDA community!
My Motorola Moto g60 phone is bricked i.e. flashing is locked in fastboot mode and I cannot install a new ROM without entering into EDL mode.
Does anyone know how to enter EDL mode for Moto g60?
KayaNN said:
Hello XDA community!
My Motorola Moto g60 phone is bricked i.e. flashing is locked in fastboot mode and I cannot install a new ROM without entering into EDL mode.
Does anyone know how to enter EDL mode for Moto g60?
Click to expand...
Click to collapse
Unfortunately, there's no way for that. Did you find a solution though? My phone is in the exact same condition.
ankurpandeyvns said:
Unfortunately, there's no way for that. Did you find a solution though? My phone is in the exact same condition.
Click to expand...
Click to collapse
posted in this thread - https://forum.xda-developers.com/t/no-operating-system-found-brick.4422035/post-87036557
The technician has yet to buy the JTAG boot tool
KayaNN said:
posted in this thread - https://forum.xda-developers.com/t/no-operating-system-found-brick.4422035/post-87036557
The technician has yet to buy the JTAG boot tool
Click to expand...
Click to collapse
I found a shop here in bangalore named next level repair. These guys have all the tools but they still cannot recover the phone. Motherboard replacement is the only solution they have right now.
A method can be adopted, you can test it if the device is soft brick/hard bricked,(as your device requirements) then there is no harm in taking this remedy, collect information about it from the internet, I am telling you the way which is like this:-
Download:-
Qualcomm QDLoader HS-USB 9008 Driver for x64 or 32
Motorola device manager
Motorola USB driver
ADB driver
Stock firmware
Optional:- Blankflash file for honip according to your build no. [[ if device does not turn on fastboot or recovery mode in any mode just read as black dead screen.When the device is not detected by anyone, try to get the test point detected by sort and use blank flash only when needed.After that, if needed, after blank flash, device will open in boot loader mode or fastbood mode. The Boot Loader Mode menu will appear on device. ]]
Info:- Make sure that your device is getting deducted in the computer or not.
Find the test point in the motherboard of the device and try to shorten it, this information is available on the internet, Google about it that, where is test point in mother board. This method is quite a tricky, again saying tricky, sometimes the test point is supported along with attaching it to the USB device, sometimes it has been seen that even after attaching the USB, you can get the test point shot. It may not be a problem if this method is not successful in a couple of times. Try it PC will detect EDL mode.
When your device is not detected and PC detects your mobile after shorting the test point, It means EDL mode is working. After that you will be able to turn it on by flashing the stock firmware.
RajivShastri king said:
A method can be adopted, you can test it if the device is soft brick/hard bricked,(as your device requirements) then there is no harm in taking this remedy, collect information about it from the internet, I am telling you the way which is like this:-
Download:-
Qualcomm QDLoader HS-USB 9008 Driver for x64 or 32
Motorola device manager
Motorola USB driver
ADB driver
Stock firmware
Optional:- Blankflash file for honip according to your build no. [[ if device does not turn on fastboot or recovery mode in any mode just read as black dead screen.When the device is not detected by anyone, try to get the test point detected by sort and use blank flash only when needed.After that, if needed, after blank flash, device will open in boot loader mode or fastbood mode. The Boot Loader Mode menu will appear on device. ]]
Info:- Make sure that your device is getting deducted in the computer or not.
Find the test point in the motherboard of the device and try to shorten it, this information is available on the internet, Google about it that, where is test point in mother board. This method is quite a tricky, again saying tricky, sometimes the test point is supported along with attaching it to the USB device, sometimes it has been seen that even after attaching the USB, you can get the test point shot. It may not be a problem if this method is not successful in a couple of times. Try it PC will detect EDL mode.
When your device is not detected and PC detects your mobile after shorting the test point, It means EDL mode is working. After that you will be able to turn it on by flashing the stock firmware.
Click to expand...
Click to collapse
Thanks for the reply.
The technician could not find a test point on the motherboard.. We haven't found a way to force Motog60 into EDL mode yet.
ankurpandeyvns said:
I found a shop here in bangalore named next level repair. These guys have all the tools but they still cannot recover the phone. Motherboard replacement is the only solution they have right now.
Click to expand...
Click to collapse
Replacing motherboard was what the authentic Lenovo dealers had given to me as the only solution. That would cost about 3/4th the phone's original price.
I still have hopes that the technician I know might be able to perform a boot repair using the JTag boot tool that I had mentioned in the earlier posts. I'll post here immediately when its done, along with the complete step by step solution.
Maybe this video can be of some use to you because this video matches 80% of your problem, even if it did not work, then it will definitely increase your knowledge.
Try to see if something from here could help. Unless you already tried that. In which case, I don't know what else to recommend you.
Also, if you have TWRP installed, that seems to have an option to boot into EDL.
However, I'm curious how did you get in this scenario to begin with.
arsradu said:
Try to see if something from here could help. Unless you already tried that. In which case, I don't know what else to recommend you.
Also, if you have TWRP installed, that seems to have an option to boot into EDL.
However, I'm curious how did you get in this scenario to begin with.
Click to expand...
Click to collapse
I also very curious to know about result, but he must has to search about edl point. I was also stuck in this kind of problem once, But the theoretical method was all in vain. All the technicians were useless. But at last my phone booted up but I didn't even understand how it booted up. only a miracle. After getting frustrated all over the place, I used to try again and again whenever I got time, even if it was 5 minutes, I would try to flash by taking test point shots and on the 7th or 8th day my device booted in bootloader mode.
But in this case the main role will be that of Qualcomm QDLoader HS-USB 9008 Driver. This driver is designed to working + bring interface to EDL mode. After installing this driver, many times users think that the driver is installed but, it is not actually installed and is not working inside, so it is necessary to install the driver properly and needs verify. I have posted these all in his conversation section (regarding installation) pdf. This pdf also discusses some commands that forcefully brings in EDL mode. But I don't think that command will work because I don't know if their mobile has USB debugging on or not. According to me and from my knowledge/understanding this is the way to get them back in boot>>
Find edl point/test point>>short & same time attatch usb cable> pc shows device>mobile screen greets in fastboot mode, than quick flash fastboot rom with double click on .bat file
If no recovery/No bootloader mode/only dead black screen than blank flash with same version.
Things to remember before flashing ROM:-
Info:- If one have the locked bootloader then one can only install the firmware with a version equal to or higher than the version that is already on the device. In that case If one have the bootloader locked, if one wants to install a previous version or a downgrade, it is necessary to unlock the bootloader because if one try to install a previous version with the bootloader locked, there is a high chance of bricking.
www.youtube.com/watch?v=DtRZkCyp9do
Motog60/40 edl point
RajivShastri king said:
Motog60/40 edl point
Click to expand...
Click to collapse
Thanks a lot for this - I'll show this to the technician and see if it works
KayaNN said:
Thanks a lot for this - I'll show this to the technician and see if it works
Click to expand...
Click to collapse
You are welcome!!! I'm glad that, I could be of some use to you.
RajivShastri king said:
Motog60/40 edl point
Click to expand...
Click to collapse
Thanks Sir, I also have same issue and opened my G60 but above images does not match with G60 model I purchased from flipkart India. Anyone can help me to find EDL points on G60 model
asdrhyme said:
Thanks Sir, I also have same issue and opened my G60 but above images does not match with G60 model I purchased from flipkart India. Anyone can help me to find EDL points on G60 model
Click to expand...
Click to collapse
I'm not sure EDL will work with a locked bootloader.
asdrhyme said:
Thanks Sir, I also have same issue and opened my G60 but above images does not match with G60 model I purchased from flipkart India. Anyone can help me to find EDL points on G60 model
Click to expand...
Click to collapse
There's no solution to it that you can do in home. I got my device fixed at Next Level Repair in Bangalore. They replaced the UFS chip on my phone. That's the only solution
RajivShastri king said:
Motog60/40 punto edl
Click to expand...
Click to collapse
Buenas tardes,
RajivShastri king said:
A method can be adopted, you can test it if the device is soft brick/hard bricked,(as your device requirements) then there is no harm in taking this remedy, collect information about it from the internet, I am telling you the way which is like this:-
Download:-
Qualcomm QDLoader HS-USB 9008 Driver for x64 or 32
Motorola device manager
Motorola USB driver
ADB driver
Stock firmware
Optional:- Blankflash file for honip according to your build no. [[ if device does not turn on fastboot or recovery mode in any mode just read as black dead screen.When the device is not detected by anyone, try to get the test point detected by sort and use blank flash only when needed.After that, if needed, after blank flash, device will open in boot loader mode or fastbood mode. The Boot Loader Mode menu will appear on device. ]]
Info:- Make sure that your device is getting deducted in the computer or not.
Find the test point in the motherboard of the device and try to shorten it, this information is available on the internet, Google about it that, where is test point in mother board. This method is quite a tricky, again saying tricky, sometimes the test point is supported along with attaching it to the USB device, sometimes it has been seen that even after attaching the USB, you can get the test point shot. It may not be a problem if this method is not successful in a couple of times. Try it PC will detect EDL mode.
When your device is not detected and PC detects your mobile after shorting the test point, It means EDL mode is working. After that you will be able to turn it on by flashing the stock firmware.
Click to expand...
Click to collapse
-Escrito en español
Buenas tardes, yo también tengo el problema de tener el teléfono "brikeado", mire el post completo y observe que encontro los punto "EDL" del Motorola G60"XT2135-1. Mañana voy a realizar el procedimiento solo necesito configurar correctamente mi "QUALCOMM" para no tener inconvenientes , me podría pasar por este medio la dirección web para descargar los "PDF" para empezar a preparar mi computadora.
-Translated into english by google translator
Good afternoon, I also have the problem of having the phone "bricked", look at the entire post and see that I found the "EDL" point of the Motorola G60 "XT2135-1. Tomorrow I am going to carry out the procedure, I just need to configure my "QUALCOMM" correctly "In order not to have inconveniences, you could send me the web address to download the "PDF" to start preparing my computer.
RajivShastri king said:
I also very curious to know about result, but he must has to search about edl point. I was also stuck in this kind of problem once, But the theoretical method was all in vain. All the technicians were useless. But at last my phone booted up but I didn't even understand how it booted up. only a miracle. After getting frustrated all over the place, I used to try again and again whenever I got time, even if it was 5 minutes, I would try to flash by taking test point shots and on the 7th or 8th day my device booted in bootloader mode.
Pero en este caso el papel principal será el de Qualcomm QDLoader HS-USB 9008 Driver. Este controlador está diseñado para trabajar + llevar la interfaz al modo EDL. Después de instalar este controlador, muchas veces los usuarios piensan que el controlador está instalado, pero en realidad no está instalado y no funciona internamente, por lo que es necesario instalar el controlador correctamente y debe verificarse. He publicado todo esto en su sección de conversación (sobre la instalación) pdf. Este pdf también analiza algunos comandos que activan con fuerza el modo EDL. Pero no creo que ese comando funcione porque no sé si su móvil tiene la depuración USB activada o no. Según yo y según mi conocimiento/comprensión, esta es la forma de recuperarlos>>
Encuentre el punto edl / punto de prueba>> cable USB de conexión corta y al mismo tiempo> la PC muestra el dispositivo> la pantalla móvil saluda en modo fastboot, luego flashea rápidamente la rom fastboot con doble clic en el archivo .bat
Si no hay recuperación/No hay modo de cargador de arranque/solo pantalla negra muerta que flash en blanco con la misma versión.
Cosas para recordar antes de flashear la ROM: -
Información: - Si uno tiene el cargador de arranque bloqueado, solo puede instalar el firmware con una versión igual o superior a la versión que ya está en el dispositivo. En ese caso, si tiene el gestor de arranque bloqueado, si quiere instalar una versión anterior o una versión anterior, es necesario desbloquear el gestor de arranque porque si intenta instalar una versión anterior con el gestor de arranque bloqueado, existe una alta probabilidad de bloqueo. .
www.youtube.com/watch?v=DtRZkCyp9do
Click to expand...
Click to collapse
works. but without QFIL files edl mode won't make uch difference here.
Thank you for the information. In future it would be easy to identify edl points from schematics and it consists of UART and USB Boot inputs as test points.