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
I have recently acquired TCL 40E5800. It's a good Android TV at a very decent price. But the problem is that it came with its own App Store will less than 300 apps. From posts I read from Chinese sites and other brand of TVs. I have found out a solution to install / sideload GApps to this TV. And this is possible for it is running on Android based platform. So, this guide should also be applicable to any China TV running on Android.
DISCLAIMER:
I am not responsible if anything goes wrong with your Android TV. I am making this tutorial for future reference in case I have bricked my TV.
Click to expand...
Click to collapse
You will need the following for this guide:
1. ES File Manager
2. Droid Info
3. Package Installer
4. Total Commander with ADB Plugin
5. TCPUDP
6. gapps-jb-20121212-signed
STEP BY STEP GUIDE:
1. You will need to download ES File Manager from the TV App Store.
2. Connect Android smartphone to the same WiFi as TV. Install ES File Manager and Droid Info from Play Store in your smartphone. The reason you need to do this is that you cannot install app or apk from ES File Manager if your TV because it doesn't have Package Installer. It will just return an error saying "No application found."
3. From your smartphone, browse to APP folder, find Droid Info and click Install to TV. This will install Droid Info into your TV.
4. Go to your TV and run Droid Info. And look for this information:
{
"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"
}
5. Take note of the Model, OS Version, SDK, Density and Architecture.
Model and OS Version will help you determine the Google Play Services you need to install. You need to install specific version of Google Play Services for this to work. In my case, my TV model says: rtd299x_tv030. The last three digit or character usually determine the file version of Google Play Services you need to install. (This is just for future references. You don't need to worry information right now.)
To figure out the right version of Google Play services for your Android device, download Play Services info or go to Settings -> Apps -> Google Play services, and look at the last 3 numbers in the parentheses. You'll see something like -XYZ where:
* X defines Android version:
0 for Android <5.0
2 for Android 5.0 and 5.1 starting with Play Services v8
4 for Android 5.0 and 5.1 before Play Services v8, Android >= 6.0 after
5 for Android Wear
7 for Android 5.0
8 for Android TV
* Y defines CPU architecture:
1 for armeabi
3 for armeabi-v7a
4 for arm64-v8a
7 for x86
8 for x86_64
* Z defines DPI:
0 for universal
2 for 160
4 for 240
6 for 320
8 for 480
Notes:
It seems that -7YZ builds became -4YZ with Google Play services v6.5. If you were on -7YZ before, you should now install -4YZ.
It seems that -4YZ builds got split into -2YZ for Lollipop and -4YZ for Marshmallow with Google Play services v8. If you were on -4YZ before, you should now install -2YZ in Lollipop and -4YZ in Marshmallow.
Click to expand...
Click to collapse
SDK means the API level. Any app with API level above your SDK will not install it.
6. Now that you have all that info. Next thing you need to install is Package Installer. You need to search it and download the Package Installer that is for Android 4.2.1 for my TV Android OS Version is 4.2.1. Mine is attached below. Or you can browse Package Installer from your smartphone through ES File Manager. Go APP folder and select System App and you should see Package Installer and install it on TV. If this method, doesn't work for you, you can try ADB (Android Debugging Bridge) or Total Commander.
View attachment PackageInstaller.apk
7. Skip this step if you have managed to install Package Installer. For this guide, let us use Total Commander. For this step, just refer to this post here. You need to download the Document and read the Document for the link to Total Commander with ADB plugin is there. Just in case, you are confused, then you just need to open Total Commander and from the right side pane, choose ADB as the directory and then click the IP address of your TV and then browse to the [apps] folder. Here are some screenshot for your reference.
8. Now that you have able to install Package Installer, you can now install any apk file from ES File Manager. How cool is that, right? This is optional: You can now browse to XMBC, now Kodi website and download the apk version of Kodi (or you can download it here - ARM version for my TV has an Architecture of ARMv7). As you can see in my screenshot before that I have manage to install Kodi (look at the icon beside Package Installer, it's Kodi). See how cool is Kodi:
9. Next is installing GApps. You need to install the specific GApps version for your TV. Any other version will fail. This step is critical. Do not think if you have a TV running Android 4.2.1 that installing 4.1.2 or 4.2.2 are the same and it will work. You need to search the right GApps version for you. For this to work, you do not need to install just certain GApps. You need to install the WHOLE package. What I used was a package from a custom ROM, Cyanogen. This GApps package will install entire GApps to your TV. Choose the right GApps for you here. Mine was gapps-jb-20121212-signed.zip
10. Download and extract the GApps package. We can't install the package through flashing it from recovery. So, we need to install it manually through Total Commander and ADB. First is by Total Commander. For the left side pane, browse to the directory where you have extracted the GApps package and copy everything in the system folder to the root folder of your TV. From the screenshot before, it should be like this:
The left side pane is where you extracted the GApps package. The right side pane should be the root folder of your TV, i.e. "\\\ADB\TV IP Address:5555\*.*" Then click "F5 Copy". If there are files that need to be overwritten then just select "Skip". DO NOT OVERWRITE. This way you did not just install GApps into the system folder but you also installed its needed library for it to work.
11. The next step should be to correct its permission. We will do this through ADB. Connect PC to the same WiFI as your TV. And use TCPUDP for this to work. How to make this work, you can read it from the same Document (about Total Commander) that you have downloaded. Or you can simply install ADB to your PC (search how to install ADB) and then type in the command "adb connect (tv IP address:5555)". What I did: I used TCPUDP. Click "CreateConn" and a dialogue appears. Be sure to select UDP under Type box. Then enter TV IP address in DestinationIP box. Leave Port box to 8090. Then click "Create". After that, under Client Mode, you can see the connection to your TV. Select it, and then select TCP for the Type. Then click "Connect'. After that, type "start adb" in the first big box. Then click "Send". After that you will see "ok" into the second big box. For your reference, here are some screenshots:
12. Open Command Prompt. Navigate to where you installed your ADB. If you downloaded the Total Commander from the Document, then you can find ADB installed in its Plugin folder, i.e. "TotalCmd\Plugins\wfx\ADB". Then type the following commands:
Code:
adb remount
adb shell pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
adb shell chmod -R 0644 /system/app/*.*
adb reboot
13. Let your TV reboot. After reboot open Google Play Store. DO NOT OPEN ANY OTHER GApps. Then you may have to log in your Google Account. Then enjoy installing millions of apps from Google Play Store, as well as in Google Play Games.
14. If you however opened some GApps that is not Google Play Store. Then it will create some error. You may find some error regarding some certain GApps failed to respond. Just click "OK". And you may also found out that Google Play Store is no longer listed in your TV App main page. Just use ES File Manager and browse to System Apps and open it there.
15. Updating and downloading apps from the Google Play Store may be take too long but just wait. It will download eventually. Enjoy GApps. I have finally cracked this one.
Don't forget to say thanks.
#TCL
#40E5800
#E5800
#GApps
#4.2.1
#Android TV
#China TV
#Play Store
#Google
#sideload
#install
Since this Android TV does not have Settings app... in case you are stuck:
To clear data:
Code:
adb shell pm clear "packageName"
To enable system apps:
Code:
adb shell pm enable "packageName"
Package Name for Google Play Services is "com.google.android.gms"
Package Name for Google Services Framework is "com.google.android.gsf"
Package Name for Google Play Store is "com.android.vending"
Package Name for Download Manager is "com.android.providers.downloads"
To clear Dalvik cache:
Code:
rm -r /data/dalvik-cache
rm -r /cache/dalvik-cache
To bypass Setup Wizard:
Code:
Tap four corners of screen starting from top-left corner then top-right corner and so on...
merci
j ai une tv chinoise dont les caracteristique sont identique a la TCL 40E5800 sauf que la mienne est un 50 pouces,j ai donc suivit scrupuleusement votre tutoriel et j ai reussi a installer les service google play donc j ai pu me connecter a gmail et youtube avec mon compte google,c est vraiment genial;merci beaucoups.
cependant j ai un probleme le google play store ne s afficge pas sur ma tv quand j accede via es explorer je peut le lancer mais ne telecharge pas les applications,et je voudrais aussi si c est possible de rooter ma tv je vous serai gré s il ya une possibilité de le faire
de m aider merci mille fois
ma tv est monter en algerie elle porte la reference suivante Condor U 8100 50u8100
You're welcome. I'm thinking that this is French. I used Google Translate. Well, about Google Play Store... This TV model is really outdated now... I can't find any Google Services version now that will work for this TV. The solution is just to sideload everything.
About rooting, I tried KingoRoot, King Root, any quick rooting apps works here. However, these kind of rooting apps contains a lot of ads and bloatwares.
Bonjour
Désolé de vous déranger une fois de plus et je vous remercie de votre patience
Ma tv à les même caractéristiques que la vôtre et comme elle est obsolète j aimerai savoir si c est possible de changer de carte mère pour avoir un cpu plus puissant est une mémoire interne de plus grande capacité si oui quel carte mère utiliser je vous remercie infiniment
Cordialement
No worries. But for that question, I am sorry I do not know the answer. I have a very little knowledge about hardware. However, in my own point of view, its better to buy or use a TV box rather than replacing the motherboard.
hi my android tv has android 6.0
Which gapps should i use?
thanks
You may find the right version here:
https://opengapps.org/
May I understand your instruction on installing Google services on Android TV is meant to be for a rooted TV ? That is to say, I need to Root or no root required ? I just owned a TCL China Android TV and since google services are blocked. This is something that i need to try out.
Not necessarily root. You can apply it even without root.
Hi, one question. It's not letting me copy to the root folder of my Android TV. Am I missing something? Do I need root privileges on Total Commander or something like that?
---------- Post added at 10:01 PM ---------- Previous post was at 09:48 PM ----------
Nevermind, I was missing the root permissions explained on the Document from the other thread.
I do have a question. I can't edit "system" on Total Commander, even having adb root enabled. I can paste stuff on the root folder but system is not letting me place files, create folders or anything.
---------- Post added at 11:46 PM ---------- Previous post was at 11:28 PM ----------
Nevermind, I just noticed that you need to mount system as RW to edit it. There's a lot of misinformation in this thread.
Skex506 said:
I do have a question. I can't edit "system" on Total Commander, even having adb root enabled. I can paste stuff on the root folder but system is not letting me place files, create folders or anything.
---------- Post added at 11:46 PM ---------- Previous post was at 11:28 PM ----------
Nevermind, I just noticed that you need to mount system as RW to edit it. There's a lot of misinformation in this thread.
Click to expand...
Click to collapse
After running adb root... you need to change permission for "system" folder... change it so that you cannot just read but also write into it.
Hey @pancit, my tv is running android 6.0, I downloaded gapps from opengapps but I coudn't figure out how to install this using Total Commander, as the file tree is completely different than the Android 5.0 you used in the example.
i'm sorry for the late reply... and i'm sorry I really can't answer your question... i have a different setup now... i bought SHIELD and its working for me... no more hassle... no more working around... the bad news for almost all android tv is that they almost come with OS or android version that they set up.... and its fixed.. no more updates... and also the apps are limited... it is just how they programmed it... thats why you need to workaround with it just to sideload apps...
Hi,
i didn't really understand from 10. to 13.
I allowed developers option on the TV.
i downloaded gapps to my tv using a browser, and extracted it on the tv using es file explorer, so does it mean I don't need total commander?
also, i didn't understand what to do after the files are extracted on the TV. can you please explain? I have ADB on my PC.
Hello...
I'm really sorry.... I cannot help you... I no longer have my China Android TV with me... So, I could no longer assist you... And this post is already old. It's no longer updated. Maybe, there are lots of factors now to be considered.
pancit said:
Hello...
I'm really sorry.... I cannot help you... I no longer have my China Android TV with me... So, I could no longer assist you... And this post is already old. It's no longer updated. Maybe, there are lots of factors now to be considered.
Click to expand...
Click to collapse
I tried to follow your instruction for my android tv 9 (a xiaomi vogue projector) which could not go to fastboot mode. When I follow your instructions, I could not execute the following. for some reasons adb root is ok.
--------
Code:
C:\totalcmd\plugin\bin>adb root
C:\totalcmd\plugin\bin>adb remount
Not running as root. Try "adb root" first.
----------------------------
also this one is throwing error
Code:
C:\totalcmd\plugin\bin>adb shell pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
Exception occurred while executing:
java.lang.IllegalArgumentException: Unknown package: com.google.android.gms
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1400)
at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2102)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5442)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21368)
at android.os.Binder.shellCommand(Binder.java:634)
at android.os.Binder.onTransact(Binder.java:532)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2796)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3883)
at android.os.Binder.execTransact(Binder.java:733)
I also want to know if you have tried those steps for Android 9? It would be great if you could maybe assist.
I'm curious if the copying gapps on total commander is actually working(see attachment). How do I verify that it's been copied?
Thanks
I'm not sure about that adb root.... maybe you can try "adb shell su" command instead...
I don't know what's the cause of the error.. Did you try to make sure you got the right app? right OS version, architecture, etc...
Nope... I wasn't able to try it with Android 9...
From that screenshot, I'm afraid it is not just simple as copying the files. You may need to run that command script installer to install that GApps. You will know you have copied or install the GApps correctly if you can see the actual Google Apps in your TV.
Yup I have checked that I have the right APKs and sadly I didn't the Google Apps on my projector. I highlighted all on Total commander and clicked F5 to copy. I wonder if that's the still the same button.
adb shell su is not available because I don't have root access.
I can use "adb install" to install the apks from my computer to the projector but those other certs and xmls on gapps.zip can't be installed through that way sadly.
Windows 10 Build 15035 Media Builder:
{
"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"
}
This media builder will download Windows 10 Build 15035, apply common modifications, install apps, install drivers and generate custom installation media ready for use on the selected device.
Windows 10 Build 15035 is now six years old and it should not be considered as suitable for daily use, in addition to being outdated it has numerous bugs and other issues expected of an expired pre-release build. Consider running Windows 10 Build 15035 as novelty value only, it will not make any Windows RT device useful.
Spoiler
The use of this media builder or the media it produces is entirely at your own risk.
User Guide
- Device Support
- Known Issues
- Version History
10/05/2023 - Windows_10_15035_Media_Builder_v2.4j.zip
- Tegra Jailbreak USB updated to v1.6.
- Office 2013 RT Home & Student Plus update lists updated to May 2023.
- Minor fix to QEMU output when the source install.wim exceeded 4GB in size.
Download: Open-RT / Archive.org
27/04/2023 - Windows_10_15035_Media_Builder_v2.4i.zip
- Minor fixes.
15/04/2023 - Windows_10_15035_Media_Builder_v2.4h.zip
- Updated device notes for Lenovo IdeaPad Yoga 11 & ASUS VivoTab RT.
- DISM now uses the Media Builder temporary folder for scratch space where possible.
- Added check to prevent Media Builder from offering any of the drive(s) it is using from being offered as an output destination.
- Added file system check.
- Minor fixes.
19/03/2023 - Windows_10_15035_Media_Builder_v2.4g.zip
- Corrected an issue which caused the output for ASUS VivoTab RT to be unbootable.
- ASUS VivoTab RT driver pack updated.
- Install.wim larger than 4GB will now be split correctly.
- Office 2013 RT Home & Student Plus update lists updated to March 2023.
20/02/2023 - Windows_10_15035_Media_Builder_v2.4f.zip
- Possible workaround to the issue of hanging on the UEFI boot logo when attempting to install Windows using Windows Media Builder output on the Surface 2.
15/02/2023 - Windows_10_15035_Media_Builder_v2.4e.zip
- Office 2013 RT Home & Student Plus update lists updated to February 2023.
- Nokia Lumia 2520 driver pack updated (Working output still not available).
10/01/2023 - Windows_10_15035_Media_Builder_v2.4d.zip
- Office 2013 RT Home & Student Plus update lists updated to January 2023.
- Surface RT & 2 Jailbreak USB updated to v1.5b.
- Minor update to App Pack.
- Minor fixes.
29/12/2022 - Windows_10_15035_Media_Builder_v2.4c.zip
- Corrected an issue with the optional Windows OEM:NONSLP activation method.
- Minor fixes.
20/11/2022 - Windows_10_15035_Media_Builder_v2.4b.zip
- Office 2013 RT Home & Student Plus update lists updated to November 2022.
- Added alternative Product Key/Activation options for Windows 10 & Office 2013.
13/10/2022 - Windows_10_15035_Media_Builder_v2.4a.zip
- Office 2013 RT Home & Student Plus update lists updated to October 2022.
- Minor update to App Pack.
- Surface RT & 2 Jailbreak USB updated to v1.5a.
17/09/2022 - Windows_10_15035_Media_Builder_v2.4.zip
- Added option to create a "Windows To Go" bootable USB drive. ^
- Office 2013 RT Home & Student Plus update lists updated to September 2022.
- DISM logs are now being saved correctly.
- Minor fixes.
^ This isn't real Windows To Go but it will write a USB with a bootable installation of Windows. The option is disabled by default and has to be enabled from Media Builder Settings if required. If enabled this option will be offered either after creating an image or when writing an existing one. There are no guarantees that this is stable but it might be useful if you want to test something without touching the local installation.
I have only tested this on a Surface 2 and cannot predict how or even if it will work on other devices, in the tests I have done the installation was usable when installed to a USB 2 Western Digital 250GB conventional hard drive or a USB 3 SanDisk Extreme 64GB flash drive. If a drive with inadequate performance is used then at best the installation will take an hour or two or in the worst case the installation will fail.
Click to expand...
Click to collapse
Depending on the options selected, the result will look like one of the pictures below or something in-between.
@jwa4 please mirror Windows_10_15035_Mod_Kit_v1.2_Appx coz I can't grab it from there, connection is breaks.
hooddy said:
@jwa4 please mirror Windows_10_15035_Mod_Kit_v1.2_Appx coz I can't grab it from there, connection is breaks.
Click to expand...
Click to collapse
Download Mirror
how to install this package please?
richietnt said:
how to install this package please?
Click to expand...
Click to collapse
See "How to use" in first post. Let me know if you have any issues.
do you still need to disable Secureboot for this build to work properly? (i.e. without bricking the device etc.)
twister2000 said:
do you still need to disable Secureboot for this build to work properly? (i.e. without bricking the device etc.)
Click to expand...
Click to collapse
That's an interesting question. I only have a Surface RT and a Surface 2 and it seems an RT can install and run this build without requiring secure boot to be disabled or otherwise bypassed but the Surface 2 seems to require it. No idea why there appears to be a difference but you can apply the Longhorn jailbreak and use Yahallo to permanently disable secure boot on both devices if needed.
thank you for your reply!
the package worked like a charm! great work on that!!
Cheers!
twister2000 said:
thank you for your reply!
the package worked like a charm! great work on that!!
Cheers!
Click to expand...
Click to collapse
Excellent, glad it worked!
hi,
i have a surface rt with 8.1.
i should upgrade to windows 10 or i can upgrade it from 8.1?
yarco89 said:
hi,
i have a surface rt with 8.1.
i should upgrade to windows 10 or i can upgrade it from 8.1?
Click to expand...
Click to collapse
Clean install only, although I have never tested it personally I have been told an in place upgrade does not work.
the store does not work for me, how can I solve it? or how to install apps without the store?
is there a way to go back to w8.1?
Quinobautis said:
the store does not work for me, how can I solve it? or how to install apps without the store?
is there a way to go back to w8.1?
View attachment 5267847
Click to expand...
Click to collapse
Store is working here, is it possible the store has been updated on your installation? The last version of the Store that will work normally is 11706.1001.26.0. For manual installation you can grab Appx files using https://store.rg-adguard.net/
To go back to 8.1 you can grab the official recovery image for your device from https://support.microsoft.com/surfacerecoveryimage
jwa4 said:
La tienda está funcionando aquí, ¿es posible que la tienda se haya actualizado en su instalación? La última versión de la Tienda que funcionará normalmente es 11706.1001.26.0. Para la instalación manual, puede capturar archivos de Appx usando https://store.rg-adguard.net/
Para volver a 8.1, puede obtener la imagen de recuperación oficial para su dispositivo en https://support.microsoft.com/surfacerecoveryimage
Click to expand...
Click to collapse
jwa4 said:
Store is working here, is it possible the store has been updated on your installation? The last version of the Store that will work normally is 11706.1001.26.0. For manual installation you can grab Appx files using https://store.rg-adguard.net/
To go back to 8.1 you can grab the official recovery image for your device from https://support.microsoft.com/surfacerecoveryimage
Click to expand...
Click to collapse
I did the process 3 times everything is fine, the apps appear but not the store I tried to install the store manal but I get an error, do you know how I can solve it? I attach the photo of how it looks
I have the recovery image, I downloaded it from the page, I created the usb and everything as they mark it incia and it asks for the language but then it only gives me the option to format and if I give it it gives me an error, could you guide me in what I do wrong?
jwa4 said:
La tienda está funcionando aquí, ¿es posible que la tienda se haya actualizado en su instalación? La última versión de la Tienda que funcionará normalmente es 11706.1001.26.0. Para la instalación manual, puede capturar archivos de Appx usando https://store.rg-adguard.net/
Para volver a 8.1, puede obtener la imagen de recuperación oficial para su dispositivo en https://support.microsoft.com/surfacerecoveryimage
Click to expand...
Click to collapse
Ya lo logré, fue mi culpa, todo funciona bien, solo tengo una pregunta, ¿cómo puedo cambiar el idioma? no me da opciones para cambiarlo
Quinobautis said:
Ya lo logré, fue mi culpa, todo funciona bien, solo tengo una pregunta, ¿cómo puedo cambiar el idioma? no me da opciones para cambiarloView attachment 5268761View attachment 5268763
Click to expand...
Click to collapse
Unfortunately English is the only option. The language packs for this build did not leak, there has been some attempt to modify language packs from builds that are close but it doesn't work perfectly and has only been done in Chinese and Russian as far as I have seen.
Quinobautis said:
I did the process 3 times everything is fine, the apps appear but not the store I tried to install the store manal but I get an error, do you know how I can solve it? I attach the photo of how it looks
I have the recovery image, I downloaded it from the page, I created the usb and everything as they mark it incia and it asks for the language but then it only gives me the option to format and if I give it it gives me an error, could you guide me in what I do wrong?
Click to expand...
Click to collapse
That's 15035 in its default state, I should probably have clarified that the store is contained in the optional app pack. Glad to see you got it working.
If the 8.1 recovery is failing its usually faster to use the command prompt option on the recovery media and use diskpart to wipe the disk fully before trying recovery again.
jwa4 said:
Eso es 15035 en su estado predeterminado, probablemente debería haber aclarado que la tienda está contenida en el paquete de aplicaciones opcional. Me alegra ver que lo hizo funcionar.
Si la recuperación 8.1 falla, generalmente es más rápido usar la opción del símbolo del sistema en el medio de recuperación y usar diskpart para limpiar el disco por completo antes de intentar la recuperación nuevamente.
Click to expand...
Click to collapse
I've been looking but I'm not sure how to do it
by chance you will have the commands I do not want to break anything
Quinobautis said:
I've been looking but I'm not sure how to do it
by chance you will have the commands I do not want to break anything
Click to expand...
Click to collapse
Unfortunatley I have never used any of them, I did briefly try to add the option of applying the Russian Language pack to the mod kit but it caused various issues.
trying everything again, hope i can have the store,
Is there a way of transform the RT in to IPTV,
i already have the url - m3u file.
Premise: I performed all the operations by raspberry (I have driver problems on windows).
Today I decided to install the official twrp for my mi 11 lite 5g (renoire); and then install the MiuiMix android 12 rom in fastboot.
I download the img file from the official site, put it on a key, connect the fastboot phone to my raspberry (after giving it usb debugging permissions) and launch the command:
"fastboot devices" from the terminal.
"fastboot random number" ... ok phone recognized.
"fastboot flash recovery /home/meda/usb/twrp.img" ...
the recovery flash starts.
"Sending recovery OKAY"
"Writing recovery FAILED (remote '(recovery_a) No such partition')"
"fastboot: error: Command Failed"
Do you know what happened? and how can I solve?
C0DEX0 said:
Premise: I performed all the operations by raspberry (I have driver problems on windows).
Today I decided to install the official twrp for my mi 11 lite 5g (renoire); and then install the MiuiMix android 12 rom in fastboot.
I download the img file from the official site, put it on a key, connect the fastboot phone to my raspberry (after giving it usb debugging permissions) and launch the command:
"fastboot devices" from the terminal.
"fastboot random number" ... ok phone recognized.
"fastboot flash recovery /home/meda/usb/twrp.img" ...
the recovery flash starts.
"Sending recovery OKAY"
"Writing recovery FAILED (remote '(recovery_a) No such partition')"
"fastboot: error: Command Failed"
Do you know what happened? and how can I solve?
Click to expand...
Click to collapse
dude your wrong woth your command fastboot boot ****.img because mi 11x has a/b partitions you need to first boot it and then install via recovery ramdisk
TeckySairam said:
amico, hai sbagliato con il tuo comando fastboot boot ****.img perché mi 11x ha partizioni a/b devi prima avviarlo e poi installarlo tramite recovery ramdisk
Click to expand...
Click to collapse
moddo i miei telefono da 4 anni ma non ho mai sentito parlare di questa cosa, potresti spiegarti meglio gentilmente?
Okay so, I followed this guide step by step and everything worked until:
Once I sent the command "fastboot boot twrp.img", and navigated to the twrp to get to the zip file that is needed to not have the recovery, I noticed that there is no trace of the internal memory (where I had just downloaded the aforementioned file ).
I thought "okay the download on a usb stick with usb-c connection and the meat from the" NO. HE DOESN'T EVEN SEE THE KEY.
I don't know how to do it, I can't get the twrp the phone memory can't see me
C0DEX0 said:
Okay so, I followed this guide step by step and everything worked until:
Once I sent the command "fastboot boot twrp.img", and navigated to the twrp to get to the zip file that is needed to not have the recovery, I noticed that there is no trace of the internal memory (where I had just downloaded the aforementioned file ).
I thought "okay the download on a usb stick with usb-c connection and the meat from the" NO. HE DOESN'T EVEN SEE THE KEY.
I don't know how to do it, I can't get the twrp the phone memory can't see me
Click to expand...
Click to collapse
Hi, first you are on the wrong section, the correct one for your phone model is this:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Where maybe you will find the answer to your question.
I can advise you to follow the instructions that you find on the official twrp website to the letter:
Xiaomi Mi 11 lite 5G
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
RollDload said:
Ciao, prima sei nella sezione sbagliata, quella corretta per il tuo modello di telefono è questa:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Dove forse troverai la risposta alla tua domanda.
Posso consigliarti di seguire alla lettera le indicazioni che trovi sul sito ufficiale di twrp:
Xiaomi Mi 11 lite 5G
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Click to expand...
Click to collapse
hello thanks for your answer, I followed the guide you had left me (the official twrp and it worked) (amazing how I did not see it alone). But although I managed to install the recovery correctly, I still have the problem that does not show me the files of the phone (eg download folder, DCMI etc...). Even by connecting a usb. does not detect it, keeps showing me 0Mb on each partition
C0DEX0 said:
hello thanks for your answer, I followed the guide you had left me (the official twrp and it worked) (amazing how I did not see it alone). But although I managed to install the recovery correctly, I still have the problem that does not show me the files of the phone (eg download folder, DCMI etc...). Even by connecting a usb. does not detect it, keeps showing me 0Mb on each partition
Click to expand...
Click to collapse
Very good!
What rom did you flash? Android 11 or 12?
It could solve, on android 11, complete the initial configuration after flashing the rom with data format. Also try disabling pin \ password \ fingerprint as a screen lock. Or check the mtp driver in the raspberry.
With Android 12 as far as I know this is normal because decryption does not work yet, and it is not fully supported.
RollDload said:
Molto bene!
Che rom hai flashato? Android 11 o 12?
Potrebbe risolvere, su Android 11, completare la configurazione iniziale dopo aver flashato la rom con il formato dei dati. Prova anche a disabilitare pin \ password \ fingerprint come blocco schermo. Oppure controlla il driver mtp nel lampone.
Con Android 12, per quanto ne so, è normale perché la decrittazione non funziona ancora e non è completamente supportata.
Click to expand...
Click to collapse
here's why... I installed the MiuiMix, fastboot version android 12. Is it known about how much it will affect before they resolve? will one month be enough?
C0DEX0 said:
ecco perché... ho installato il MiuiMix, versione fastboot Android 12. Si sa quanto influenzerà prima che si risolvano? basterà un mese?
Click to expand...
Click to collapse
Hopefully soon! But having two different phones, I don't know, I haven't researched the model you have mi 11 lite, I have poco F3, so they have two different development paths. I recommend that you deepen your research on the section dedicated to your phone, here.
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.