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.
I love AOSP and Lineage OS Based roms because i hate all the Google Apps that are preinstalled in Google Based Roms except Google Keyboard because GBoard support all Indian Languages and i like to install it as a system app so i made the Magisk Module for make things easy
so just flash it in Magisk Manager and enjoy Google Keyboard as System APP
Download
ranjodhricky said:
Me encanta AOSP y el Linaje de sistema operativo Basado roms porque odio a todas las Aplicaciones de Google que vienen preinstalados en Google Basado Roms excepto Google Teclado porque GBoard apoyo a todos los Idiomas de la India y me gustaría instalarlo como una aplicación del sistema así que he hecho el Magisk Módulo para hacer las cosas fáciles
tan sólo flash en Magisk Manager y disfrutar de Google Teclado como APLICACIÓN del Sistema de
Descargar
Click to expand...
Click to collapse
works perfect, can you update the gboard version?
alexda2323 said:
works perfect, can you update the gboard version?
Click to expand...
Click to collapse
just extract the zip file and replace LatinIME.apk with latest version then repack zip file and flash it in Magisk.
ranjodhricky said:
I love AOSP and Lineage OS Based roms because i hate all the Google Apps that are preinstalled in Google Based Roms except Google Keyboard because GBoard support all Indian Languages and i like to install it as a system app so i made the Magisk Module for make things easy
so just flash it in Magisk Manager and enjoy Google Keyboard as System APP
Download
Click to expand...
Click to collapse
first thank you for your package, i replaced the apk with a newer one and now i am able to use gboard on my custom rom on the work profile (our it has restricted any other store apps except the company ones...)
until here everything is fine.
but can we also make this system app update able from the play store?
it would be tedious to manually removing this package from magisk -> reboot -> update package -> install from magisk -> reboot again
every month, b/c google is updating the application?
gboard is now installed as system app but play store is not detecting it, and if i try to install it from play store it fails with an unknown error (that maybe is obvious)
i tried to comment out the detach commands in the install.sh file because i thought this was preventing the detection, but that did not help
or maybe i should try to use another approach and try the addon package like from FlameGApps gboard that maybe is update able? I mean i dont know if this will result in app crashes if my custom rom is installed with MindTheGApps and now i am trying to add another app from another GApps package...?
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
reserved
Arobase40 said:
Ok, I feel happy for you you succeeded to root your phone with your camera working and you pass the SafetyNet test by activating Zygist with safetynet-fix v2.2.1, but what have you done differently from my guide as you as you just got updated information from my thread ?
You passed SafetyNet test and so what next ???
Have you got Samsung Secure Folder, Samsung Health or Samsung Pay working or such other protected Samsung apps ???
Are you getting Xprivacylua or AfWall+ (may be this one but not sure) working ???
Firefds kit [R] is not yet update to be compatible with Android 12, so it only partially works...
On my Galaxy Note 9, I didn't pass SafetyNet test, but Samsung Secure Folder, Google pay, Samsung Health are fully working... ^^
Samsung Pay is working but only with a Samsung Watch...
With another configuration I passed SafetyNet test but all above apps aren't working at all !!! ^^
I don't mind you created another thread and another guide on how to root the A528B but what is the interest if you don't explain how you improved mine and what new features you got ???
Click to expand...
Click to collapse
A. I didn't read your guide since your guide openly says it doesn't work with camera
B. I needed camera so I created my own guide where the camera works and it is here for everyone to read
testestestest said:
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
Click to expand...
Click to collapse
Ok, I confirm this works!! Way to go sir. Thanks so much and I encourage everyone to do this method. WooHoo
Arobase40 said:
Ok but does it changes anything since my post #218 of my own guide ?
Click to expand...
Click to collapse
not that i can tell
Arobase40 said:
UPDATED : How to root Galaxy A52S 5G (SM-A528B)
This is a highly updated tutorial on how to root the Galaxy A52S 5G (SM-A528B) phone based on new version of Magisk and from feedbacks I received from users after the release of the first guide version ! ;) This guide should work with other...
forum.xda-developers.com
As I was myself trying to use Zygist with SafetyNet 2.2.1 version even though I didn't mention it explicitely as Safetynet 2.2.1 is only working with Zygist ?
"Ok, nice try mate but Zygisk-LSPosed is even worse !!!
It broke FoxMagiskModuleManager when Zygisk-LSPosed has very poor modules list. It broke AfWall+ and it partially broke Firefds kit and no progress at all with Samsung apps !!!"
Does this still apply ?
Click to expand...
Click to collapse
yes as far as lsposed goes, never used the fox app or afwall so can't say. no gravity box for android 12 yet
Arobase40 said:
So that means that since my post #218 no one with failed camera has installed SafetyNet Fix 2.2.1 with Zygist and no one has checked if that has an impact on the camera, and thus no report to me ??? lol
I just remind you that my camera has always been working so I couldn't expected any changes on this aspect... ^^
Finally, if my guide offered "limited root", this one offers even more limited one as with the exception of AdAway what this root stands for if you can't at least protect your privacy ???
Click to expand...
Click to collapse
you are lucky enough to be in a region that allows the camera to function while boot loader is unlocked
One thing I've noticed, after a restart the camera fails until closing it and killing the app in recent apps, then it works.
testestestest said:
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
Click to expand...
Click to collapse
thank you very much )))) I will try this weekend!
Guys, can anybody explain to me , why Samsung is apparently making it so hard for the customers to root their devices? Is it a problem with Samsung or with Magisk, or both?
Not being able to root via Magisk is a real dealbreaker to this otherwise well-specced phone (at least it is to me!).
Going to try this method with Android 11 using Magisk 24.3 and safety net 2.2.1 which I hope will allow the camera to work also.
Edit: It works with android 11.
Arobase40 said:
Why wouldn't it work with Android 11 as it is not related ???
You mean you downgraded to Android 11 and got stuck with a very old security patch just to get GravityBox and probably with Firefds Kit [R] working ??? lol
Click to expand...
Click to collapse
Yes, yes and yes. LOL and better battery life too
I've had no bootloops when changing things FireFDS and I'm glad to have a working gravity box... I'll report battery after a few days.
testestestest said:
Guys, I DID IT !!!!
Click to expand...
Click to collapse
Hi, I'm new here and I bought the A528B, I don't speak English and I use google translate... maybe this is asking too much but a step by step video would be too much to ask? having to translate it costs me a lot trying to follow the guide...
I don't understand how I have to do to be able to root it and have the camera working
bobfrantic said:
Ok, confirmo que esto funciona!! Bien hecho señor. Muchas gracias y animo a todos a hacer Desbloquee el gestor de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
Click to expand...
Click to collapse
testestestest said:
Chicos, LO HICE!!!!
Samsung A52s (SM-A528B/DS) en funcionamiento con cargador de arranque desbloqueado, rooteado (Magisk), pasando SafetyNet y CÁMARA DE TRABAJO (yaaay).
El problema es que no tengo idea de cómo lo hice, porque fueron 3 días de flashear, parchear, reinstalar y bloquear el teléfono también (desafortunadamente).
Adjunto una captura de pantalla que hice con el teléfono mientras escribía esta publicación en Word. Alguien quería capturas de pantalla en pantalla dividida como prueba, así que... boom, aquí tienes.
Tengo muchas fotos que hice en los últimos 3 días, así que intentaré escribir algunas instrucciones más detalladas pronto. Pero ahora al menos prueba esto:
Esto debería funcionar para cualquier persona, incluso para las personas que no tendrán una cámara en funcionamiento después de desbloquear el gestor de arranque.
1. Descargue el último firmware y Odin de samfw.com (no sé por qué, pero estos fueron solo uno que se cubrieron para mí, bloquearon mi teléfono antes con un firmware diferente)
2. Descomprima el firmware descargado y copie AP a un teléfono con Magisk 24.1
3. Use la aplicación Magisk para parchear el archivo AP y descárguelo nuevamente a la PC
4. Desbloquee el cargador de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
5. Reiniciar
6. Vaya al modo de descarga (debería ver OEM: APAGADO (U))
7. Flashee con Odin todos los archivos de Firmware que descargó, pero a AP puso el archivo parcheado
8. Reiniciar
9. Vaya a magisk, haga lo que quiera, reinicie, en la configuración active el host integrado, active Zygisk, reinicie, descargue e instale el módulo kdrag0n's safetynet-fix v2.2.1 ( https://github.com/kdrag0n/safetynet -fix/ lanzamientos )
10. reiniciar
11. siiii
ACTUALIZACIÓN: Ok, parece que el software de la cámara fallará después de reiniciar una vez. Cuando lo cierras y lo abres de nuevo, funciona.
CONFIRMADO: Tuve que volver a flashear después de probar TWRP y ahora puedo confirmar que parchear "safetynet-fix v2.2.1" te permitirá usar la cámara después de una ejecución. La aplicación Samsung Cam fallará en la primera ejecución, por lo que cuando la elimine en el conmutador de aplicaciones y vuelva a ejecutarla, funcionará de manera normal (cambiando de cámara, frontal/trasera y todo).
Click to expand...
Click to collapse
EL DESBLOQUEO DE ARRANQUE ES ANTES O DESPUES DE PARCHEAR EL AP
Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.
ch3mn3y said:
Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.
Click to expand...
Click to collapse
Well then, there you go. You got bootloop for not following the instructions
Did i understand right?
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
Click to expand...
Click to collapse
These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?
luffy786 said:
Did i understand right?
These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?
Click to expand...
Click to collapse
You can install the Magisk app without being rooted. It's an app like any other app, you simply won't have root access. So install it on your A52s 5G and patch your files with it.
Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?
BlueChris said:
Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?
Click to expand...
Click to collapse
Well, I added these 2 lines:
wlan.wfd.hdcp=disable
wifi.interface=wlan0
On the following files:
product/etc/build.prop
system/build.prop
system/system_ext/etc/build.prop
vendor/build.prop
vendor/default.prop
I'm pretty sure not all of them are needed but I'm too lazy to figure out which prop file really needs it lmao if I had to take a guess I'd say either vendor build.prop or default.prop, who knows.
Hello everyone I am using the mega cloned app but from the latest update and for the restrictions of Android 11 the aforementioned app does not save the files I try to download, I see that it tries to download up to 100%, then it gives me the notification that the operation has failed, it would seem that the cloned apps can no longer save in the "space for cloned apps" position how can I get around this problem?
Canna77 said:
Hello everyone I am using the mega cloned app but from the latest update and for the restrictions of Android 11 the aforementioned app does not save the files I try to download, I see that it tries to download up to 100%, then it gives me the notification that the operation has failed, it would seem that the cloned apps can no longer save in the "space for cloned apps" position how can I get around this problem?
Click to expand...
Click to collapse
This looks like A11/12 crap
try this :
Thanks but I don't have rooted device
Canna77 said:
Thanks but I don't have rooted device
Click to expand...
Click to collapse
go to settings/apps/ find ExternalStorageProvider force stop it and clear it's data
reboot to recovery (twrp/ofox) mount the system and make a bkp of "ExternalStorageProvider.apk" (usually in system/priv-app)
replace it with the one inside the zip according to your OS (A11=R / A12=S / A13=S2)
reboot
loopypalm said:
vai su impostazioni/app/ trova ExternalStorageProvider forza l'arresto e cancella i suoi dati
riavviare in recovery (twrp/ofox) montare il sistema e fare un bkp di "ExternalStorageProvider.apk" (di solito in system/priv-app)
sostituiscilo con quello all'interno della zip in base al tuo sistema operativo (A11=R / A12=S / A13=S2)
riavviare
Click to expand...
Click to collapse
my note 8 no root no twrp Is android stock
Canna77 said:
my note 8 no root no twrp Is android stock
Click to expand...
Click to collapse
i can hear your phone crying
Altre soluzioni?
Canna77 said:
Altre soluzioni?
Click to expand...
Click to collapse
No soluzioni , you have to root or have custom recovery to write on the system
or use A10