Zlink solution all errors mfi 2021/20XX MTCD MTCE - MTCD Android Head Units General

Zlink solution all errors mfi 2021/20XX MTCD MTCE - MTCD Android Head Units General

Hello.If I rebooted the unit, either by disconnecting from constant power or using RST button zLink would then connect, but would fail to connect after next sleep phase. I thought it must be a power issue so I worked through the power options on the factory settings menu put password m123456, Changing the default power mode from "On" to "Memory Status of Last".
Try disabling WiFi and USB initialization.
Settings MOD - Mod Settings - Car - Check WiFi after reboot and USB initialization.
Settings...Car...Extra Settings...Shutdown delay when ACC off
I have it set to 30 seconds.
Fixed the problem and zLink now connects automatically on start up.

Virus1988 said:
Hello.If I rebooted the unit, either by disconnecting from constant power or using RST button zLink would then connect, but would fail to connect after next sleep phase. I thought it must be a power issue so I worked through the power options on the factory settings menu put password m123456, Changing the default power mode from "On" to "Memory Status of Last".
Try disabling WiFi and USB initialization.
Settings MOD - Mod Settings - Car - Check WiFi after reboot and USB initialization. Fixed the problem and zLink now connects automatically on start up.
Click to expand...
Click to collapse
Is it an MTCD/E/P/H unit?

marchnz said:
Is it an MTCD/E/P/H unit?
Click to expand...
Click to collapse
Try first in your unit

Where to find this setting?
"Try disabling WiFi and USB initialization.
Settings MOD - Mod Settings - Car - Check WiFi after reboot and USB initialization. Fixed the problem and zLink now connects automatically on start up."
Are you running a custom ROM (e.g. Hal9k, Malaysk)? I am not seeing this on stock SYGAV/Dasaita PX6.
To get ZLink to consistently connect wirelessly every time, I disabled the Auto Sleep function. Basically this forces a full boot up every time the car is started. Unit boots up pretty fast anyway and to not have to mess with head unit when it fails to connect is worth it.

jlbooth said:
¿Dónde encontrar esta configuración?
"Intente deshabilitar la inicialización de WiFi y USB.
Configuración MOD - Configuración de Mod - Coche - Verifique WiFi después de reiniciar e inicializar USB. Se solucionó el problema y zLink ahora se conecta automáticamente al inicio ".
¿Está ejecutando una ROM personalizada (por ejemplo, Hal9k, malayo)? No veo esto en stock SYGAV / Dasaita PX6.
Para que ZLink se conecte de forma inalámbrica de forma constante cada vez, desactivé la función Auto Sleep. Básicamente, esto obliga a un arranque completo cada vez que se enciende el automóvil. La unidad se inicia bastante rápido de todos modos y vale la pena no tener que meterse con la unidad principal cuando no se conecta.
Click to expand...
Click to collapse
Malay Rom bro

jlbooth said:
Where to find this setting?
"Try disabling WiFi and USB initialization.
Settings MOD - Mod Settings - Car - Check WiFi after reboot and USB initialization. Fixed the problem and zLink now connects automatically on start up."
Are you running a custom ROM (e.g. Hal9k, Malaysk)? I am not seeing this on stock SYGAV/Dasaita PX6.
To get ZLink to consistently connect wirelessly every time, I disabled the Auto Sleep function. Basically this forces a full boot up every time the car is started. Unit boots up pretty fast anyway and to not have to mess with head unit when it fails to connect is worth it.
Click to expand...
Click to collapse
Autosleep? Where find this?

Settings...Car...Extra Settings...Shutdown delay when ACC off
I have it set to 30 seconds. This means that the head unit will fully shutdown 30 seconds after key off. This essentially forces a full boot every time I start the car.

jlbooth said:
Settings...Car...Extra Settings...Shutdown delay when ACC off
I have it set to 30 seconds. This means that the head unit will fully shutdown 30 seconds after key off. This essentially forces a full boot every time I start the car.
Click to expand...
Click to collapse
Work !!! +1

Related

[Lenovo K910] All Tools in One Place

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

OTG working on P8000

Hello,
S7yler reported OTG not working on P8000.
Could owners of the P8000 please check, if OTG is working on their phone by plugging in a USB stick or external USB to ethernet adaptor?
Thank you so much!

Definitely not working for me on the 20150725 build (root or no root) - fat32 format. No led notification either! 4g doesn't seem to work for me either and the wifi/3g tends to drop out occasionally for no reason.

Thanks for your feedback. You've got a first batch phone and LED and OTG was definitely not working there.
Maybe it will work on later batches/software upgrades (OTG).

and maybe otg is only working with an additional power source. when i remember correctly the kernel config shows if otg is enabled. its location should be /proc/config.gz, tar gz compressed. but it's only there, when the person who compiled the kernel enabled the config being written to this location.
good luck

edit: oops sorry, wrong thread :/
(mods pls delete this post)

I've got the newest rom installed. Still no otg working.

Elephone P8000 OTG not working
I bought 1 on the 25/8/2015 build 20150725 and my OTG is not working either the rest of the phone is great especially the battery life over 2 days

OTG is not working on mine either.
I've been trying to compile a new kernel to enable OTG but cust_gpio_usage.h is missing the pin definition for GPIO_OTG_DRVVBUS_PIN. So this pin is not routed on the pcb and the p8000 will never support OTG or Elephone didn't enable this feature and didn't want us to enable it.... Without the phone schematic trying to find this pin is like looking for a needle in a haystack.

zaphodatreides said:
OTG is not working on mine either.
I've been trying to compile a new kernel to enable OTG but cust_gpio_usage.h is missing the pin definition for GPIO_OTG_DRVVBUS_PIN. So this pin is not routed on the pcb and the p8000 will never support OTG or Elephone didn't enable this feature and didn't want us to enable it.... Without the phone schematic trying to find this pin is like looking for a needle in a haystack.
Click to expand...
Click to collapse
I don't know if it's working, but theres a github kernel fork: https:// github .com/ Clust3r /P8000-Kernel which has(sry for the messed up link - not allowed to post outside links)
" [Personal use] Alpha test
+ Verbose USB
+ OTG VErbose
+ LED Drivers
+ USB Serial driver"
in it's commit message.
Regards,
Lukas

sakulstra said:
I don't know if it's working, but theres a github kernel fork: https:// github .com/ Clust3r /P8000-Kernel which has(sry for the messed up link - not allowed to post outside links)
" [Personal use] Alpha test
+ Verbose USB
+ OTG VErbose
+ LED Drivers
+ USB Serial driver"
in it's commit message.
Regards,
Lukas
Click to expand...
Click to collapse
Thanks for the information, but it seems that this commit is just a defconfig mod.
Cheers

I'm using p8000 with custom rom eragon v3.8. Tried using otg usb with fat32, exfat and ntfs with no success. hope developer for eragon can check into this.

Mi pregunta:
realmente nuestro móvil no tiene OTG, o solo es que no tiene alimentación el cable OTG para alimentar el pendrive, por ejemplo.
Si es solo que no tiene alimentación el conector OTG, ¿SE LE PODRIA ALIMENTAR CON UNA FUENT EXTERNA?
E visto varios tuturiales en internet de otros móviles y dicen que si que solo hay que alimentar con 5V el cable OTG y ya si funcionarían los aparatos que conectara , por ejemplo mi endoscopio, pendrive etc.….
yo me quiero arriesgar a alimentar el cable OTG con una fuente externa para ver si funciona, pero me gustaria que me ayudaran y me dieran su opinión,
gracias

My question:
really our mobile does not have OTG, or just do not have the OTG power cable to power the flash drive , for example.
If it's just not feeding the OTG connector , you may be feeding a EXTERNAL POWER ?
E seen several tuturiales in other mobile Internet and say that if you just have to feed the OTG cable 5V and whether they would work to connect devices , such as my endoscope , pendrive etc. ... .
I want to risk me to feed the OTG cable with an external source to see if it works, but I would like to help me and give me your opinion,
Thank you

No this will not work, I have tried feeding 5v using a special adaptor and still nothing

Thanks then not proved, continue to investigate , some other option .

How To Guide How to root Samsung A52s (SM-A528B/DS) with working Camera

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.

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.

Question Moto G60 EDL mode (How to enter?)

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.

Extend your battery life - Smart debloat and optimize S20FE

{
"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"
}
***Works on ONE UI 4, 4.1 and 5 for all versions of s20, s21 and s22 (except for S22U)***
Due to some bad optimizations by Samsung , we are facing a lot of battery issues and a couple of random lags. With this script, I have got something between 7h and 9h of SOT.
In a few tests in Brasil, the users are getting a much better battery life. This script have some things like:
=> Removing items that can sometimes be undesirable according to the user, so you can select wich services will be disabled, such as bixby, AR camera features, microsoft apps, google apps (not the main like gmail and photos, but the secondary ones like bookmar provider, docs), ANT (there are people who don't even know what it is so this is usually useless here in Brazil).
=> Disable the Camera Light Sensor which is a bug on One UI 4.0 and 4.1, galaxy S have a light sensor to calculate the automatic brightness, however, since One UI 4.0 it ends up using the front camera for this, annihilating the screen time of the device. When camera light sensor are disbled, the device will properly use the dedicated light sensor and the automatic brightness be more responsive and battery friendly.
=> Enable the option to disable Ram Plus, where the 0GB option will appear in the options above 2GB, which you can disable if you want (Recomended only on ONE UI 4, because One UI5 comes with disable RAM Plus option available) .
Throughout the script, it will ask which item you want to be removed, so if you use DEX, just answer "n" when it asks if you want to remove it.
Resetting the device to factory defaults will completely reverse everything the script does, so it is not permanent and does not void your device's warranty. If you want, there are a Revert back script too.
The procedure is simple:
In your cellphone:
1 - Enable Developer options and USB Debug:
Go to Settings > About Phone > Software Information click on "build number" several times until it appears that developer mode is enabled.
2 - Now go to Settings > Developer Options and click enable right at the top of the page and look for the USB Debugging option and enable it too.
3 - Connect your phone to the computer and if a window appears asking for permission, grant it (you will be granting permission for your computer to access your phone in developer mode. If it doesn't appear now, no problem, this window may appear later when we run the script, but it usually appears right here.
On your PC:
4 - Download the script:
ONE UI 4.1+: Debloat and optimize Galaxy S20 S21 AND S22 except S22U v2
ONE UI 5: Debloat and optimize Galaxy S20 S21 AND S22 for ONE UI 5
5 - Extract it and run the "debloat and optimize" file (perhaps at that time the aforementioned window will appear on the cell phone asking for permission).
The script will guide you asking for all possible options which are 10:
Remove Microsoft apps?(You can reinstall the app later from the playstore)[Y/N]?
Remove Netflix?(You can reinstall the app later from playstore)[Y/N]?
Remove Facebook?(You can reinstall the app later from playstore)[Y/N]?
Remove Google Apps?(You can reinstall the app later from playstore)[Y/N]?
Remove DEX?(You will no longer have the DEX function)[Y/N]?
Remove ANT?(If you don't know what it is, you can remove it without fear)[Y/N]?
Remove Bixby?(You will still have the bixby routines, but no longer the voice assistant)[Y/N]?
Remove Augmented Reality Functions from Camera?(You will no longer have AR Sticker in Camera)[Y/N]?
Apply adaptive brightness correction? (by disabling the camera light sensor, improving auto brightness response and increasing battery life)[Y/N]?
Enable Ram Plus extra options? (enable options to increase or disable Ram Plus in Settings, Device and Battery Support, Memory) [Y/N]?
6 - When it finishes, the phone will restart. All options can somehow be reversed by downloading the apps from the Play Store again, except for DEX, Bixby and Sticker AR mode, but which can be reversed with another script that I'm still building or resetting your device to factory defaults.
Any doubt I will be available
My personal options are: ONE UI 4 - Y for all except dex (because I use dex, if you won't use, you can safe remove)
ONE UI 5: Y for all except Dex
After the script you can safe reinstall some apps back like Facebook and Google from Playstore, but now this will comes without Samsung bloatware.
Edit1: the link are updated to a new version fixing one hand mode
Edit2: release of a version to apply on ONE UI5.
and finaly the link to rollback the script: Rebloat ONE UI 4.1+ and 5 (works on ONE UI 5 too)

Hello.
I would like to ask you if this script would work also with other Samsung devices? I have a Tab S4, would this script work?
Thank you for your help

alec_trikki said:
Hello.
I would like to ask you if this script would work also with other Samsung devices? I have a Tab S4, would this script work?
Thank you for your help
Click to expand...
Click to collapse
This can work, but I dont recomend, because this stops any Spen integration. If you dont use Spen, and use OneUI 4 or 5, you can test it safely.

Olá amigo, ja pensou em postar isso em um grupo do facebook? Aquele do "pessoas pobres com celulares ruins" seria de grande ajuda para muitas pessoas!

Anyone facing an issue with Samsung Health? I have OneUi 5. I am getting an error 0x2700010, i cannot start this app. I tried clearing cache/data/uninstalling/reinstalling to older or modded app - without any positive result.

I found solution.
You have to reinstall com.samsung.klmsagent
To do it you can install sdk on your computer with usb drivers and in windows PowerShell type as follow:
./adb shell cmd package install-existing com.samsung.klmsagent
This helped me to run Samsung Health with no issue after debloat my phone with this method.

Friend my phone isn't being recognized by the cmd prompt opened by the script, I tested on platform-tools and adb is working fine, usb debugging enabled and all but it won't show my device
Detected device: ()
Firmware: ()
_________________________
The system cannot find the path specified.

Do you have Samsung USB driver installed? Can you see your phone listed in file explorer?

Mirdar said:
Do you have Samsung USB driver installed? Can you see your phone listed in file explorer?
Click to expand...
Click to collapse
I do, but I opened your scripts and manually deleted everything using pm uninstall, all good

Aadamusek said:
I found solution.
You have to reinstall com.samsung.klmsagent
To do it you can install sdk on your computer with usb drivers and in windows PowerShell type as follow:
./adb shell cmd package install-existing com.samsung.klmsagent
This helped me to run Samsung Health with no issue after debloat my phone with this method.
Click to expand...
Click to collapse
I will add a selectable option for Samsung health (thanks for your feedback), Android auto and Samsung Wallet

luis_guerreiro said:
Friend my phone isn't being recognized by the cmd prompt opened by the script, I tested on platform-tools and adb is working fine, usb debugging enabled and all but it won't show my device
Detected device: ()
Firmware: ()
_________________________
The system cannot find the path specified.
Click to expand...
Click to collapse
Some users are facing this issue when try run the script as admin. run with double click only and your device must have screen on.

luis_guerreiro said:
I do, but I opened your scripts and manually deleted everything using pm uninstall, all good
Click to expand...
Click to collapse
Esse é o espírito brasileiro, salve brother xD
It's a true brazilian xD

Is this confirmed to work on snapdragon?

danilomazzaro said:
View attachment 5782455
***Works on ONE UI 4, 4.1 and 5 for all versions of s20, s21 and s22 (except for S22U)***
Due to some bad optimizations by Samsung , we are facing a lot of battery issues and a couple of random lags. With this script, I have got something between 7h and 9h of SOT.
In a few tests in Brasil, the users are getting a much better battery life. This script have some things like:
=> Removing items that can sometimes be undesirable according to the user, so you can select wich services will be disabled, such as bixby, AR camera features, microsoft apps, google apps (not the main like gmail and photos, but the secondary ones like bookmar provider, docs), ANT (there are people who don't even know what it is so this is usually useless here in Brazil).
=> Disable the Camera Light Sensor which is a bug on One UI 4.0 and 4.1, galaxy S have a light sensor to calculate the automatic brightness, however, since One UI 4.0 it ends up using the front camera for this, annihilating the screen time of the device. When camera light sensor are disbled, the device will properly use the dedicated light sensor and the automatic brightness be more responsive and battery friendly.
=> Enable the option to disable Ram Plus, where the 0GB option will appear in the options above 2GB, which you can disable if you want (Recomended only on ONE UI 4, because One UI5 comes with disable RAM Plus option available) .
Throughout the script, it will ask which item you want to be removed, so if you use DEX, just answer "n" when it asks if you want to remove it.
Resetting the device to factory defaults will completely reverse everything the script does, so it is not permanent and does not void your device's warranty. If you want, there are a Revert back script too.
The procedure is simple:
In your cellphone:
1 - Enable Developer options and USB Debug:
Go to Settings > About Phone > Software Information click on "build number" several times until it appears that developer mode is enabled.
2 - Now go to Settings > Developer Options and click enable right at the top of the page and look for the USB Debugging option and enable it too.
3 - Connect your phone to the computer and if a window appears asking for permission, grant it (you will be granting permission for your computer to access your phone in developer mode. If it doesn't appear now, no problem, this window may appear later when we run the script, but it usually appears right here.
On your PC:
4 - Download the script:
ONE UI 4.1+: Debloat and optimize Galaxy S20 S21 AND S22 except S22U v2
ONE UI 5: Debloat and optimize Galaxy S20 S21 AND S22 for ONE UI 5
5 - Extract it and run the "debloat and optimize" file (perhaps at that time the aforementioned window will appear on the cell phone asking for permission).
The script will guide you asking for all possible options which are 10:
Remove Microsoft apps?(You can reinstall the app later from the playstore)[Y/N]?
¿Eliminar Netflix? (Puedes reinstalar la aplicación más tarde desde Play Store) [S/N]?
¿Eliminar Facebook? (Puedes reinstalar la aplicación más tarde desde Play Store) [S/N]?
¿Eliminar Google Apps? (Puedes reinstalar la aplicación más tarde desde Play Store) [S/N]?
¿Eliminar DEX? (Ya no tendrá la función DEX) [S/N]?
¿Eliminar ANT? (Si no sabe qué es, puede eliminarlo sin miedo) [S/N]?
¿Eliminar Bixby? (Todavía tendrá las rutinas de bixby, pero ya no el asistente de voz) [S/N]?
¿Eliminar las funciones de realidad aumentada de la cámara? (Ya no tendrá la etiqueta AR en la cámara) [S/N]?
¿Aplicar corrección de brillo adaptable? (deshabilitando el sensor de luz de la cámara, mejorando la respuesta de brillo automático y aumentando la duración de la batería) [S/N]?
¿Habilitar las opciones adicionales de Ram Plus? (Habilitar opciones para aumentar o deshabilitar Ram Plus en Configuración, Soporte de dispositivo y batería, Memoria) [S/N]?
6 - Cuando termine, el teléfono se reiniciará. Todas las opciones se pueden revertir de alguna manera descargando las aplicaciones de Play Store nuevamente, excepto el modo DEX, Bixby y Sticker AR, pero se puede revertir con otro script que todavía estoy construyendo o restableciendo su dispositivo a los valores predeterminados de fábrica.
Cualquier duda estaré disponible
Mis opciones personales son: ONE UI 4 - Y para todos excepto dex (porque uso dex, si no lo usa, puede eliminarlo de forma segura)
ONE UI 5: Y para todos excepto Dex
Después de la secuencia de comandos, puede reinstalar de forma segura algunas aplicaciones como Facebook y Google desde Playstore, pero ahora viene sin el bloatware de Samsung.
Edit1: el enlace se actualiza a una nueva versión que corrige el modo de una mano
Edit2: lanzamiento de una versión para aplicar en ONE UI5.
y finalmente el enlace para revertir el script: Rebloat ONE UI 4.1+ y 5 (también funciona en ONE UI 5)
Click to expand...
Click to collapse
Hola, lo trate de hacer en mi Samsung s20 Fe y no me salio,
Translation by Moderator
Hello, I tried to do it on my Samsung s20 Fe and it didn't work out,

madhatter57 said:
Is this confirmed to work on snapdragon?
Click to expand...
Click to collapse
Yes, it works on Snapdragon.

Andskin89 said:
Hola, lo trate de hacer en mi Samsung s20 Fe y no me salio,
Click to expand...
Click to collapse
This happens when you try run the script as admin (just do a double click, don't run as admin) or you don't have the proper permissions for USB debugging. 1- unplug your device and go to developer options
2- click on revoke all USB permissions
3 - disable and reenaable is debugging
4 - run the script, connect your device and a window asking is permissions will apear on your device. Click on grant.
Now this will work well.

Andskin89 said:
Hola, lo trate de hacer en mi Samsung s20 Fe y no me salio,
Click to expand...
Click to collapse
@Andskin89 be advised that English is required on XDA. Please use a translator. As a courtesy, I have translated your post, but going forward you must either post in English or include an English translation.
Thank you

Is that camera sensor bug also presemt on OneUI 5?Because I am getting horrible battery life on S20FE 5G even on OneUI5 and have not factory resetted once in almost 2 years since purchase

Nishant Hada said:
Is that camera sensor bug also presemt on OneUI 5?Because I am getting horrible battery life on S20FE 5G even on OneUI5 and have not factory resetted once in almost 2 years since purchase
Click to expand...
Click to collapse
I have did some tests (about a week) and looks fixed. You can disable two tap to wake up device. It won't solve all, but can improve a bit your battery.
Disable fingerprint when screen are off can improve a bit too, but some users miss this feature.

will this work with l8est One UI 5.1 for S20 FE 5G?

Develop Bugs

welcome