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
Version: 3.1 (19 January 2020)
RevengeOS is a custom based on AOSP and CAF designed to provided a elegant and modern UI combined with customisation, performance and stability.
You can find the screenshots below
Changelog:
19/01/2020
- Fixed bootloop
- Fixed fingerprint sensor
14/01/2020
- Initial build
- exFAT support built in
Bugs:
- Bluetooth audio
How to install:
- Make sure you're using ZUI
- Wipe /data
- Flash the ROM
- Flash the gapps
It's very hard to work without the device. You can help me with a donation to bring a better custom ROM experience to you. Thank you !
Money pool: https://paypal.me/pools/c/8kU7dpKNmZ
PayPal: https://paypal.me/lucchetto
DOWNLOAD ROM HERE
DOWNLOAD GAPPS HERE
Kernel source: https://github.com/Lucchetto/android_kernel_lenovo_sm8150
XDA:DevDB Information
RevengeOS 3.1, ROM for the Lenovo Z5 Pro GT
Contributors
Lucchetto00
Source Code: https://github.com/RevengeOS
ROM OS Version: Android 10
ROM Firmware Required: ZUI vendor
Version Information
Status: Testing
Created 2020-01-17
Last Updated 2020-01-20
can you post antutu benchmark score?
Why i have a bootloop ? can you help please ?
hvssyne said:
Why i have a bootloop ? can you help please ?
Click to expand...
Click to collapse
Yeah sorry, you also have to flash the patched vbmeta
Lucchetto00 said:
Yeah sorry, you also have to flash the patched vbmeta
Click to expand...
Click to collapse
ok thanks, where is he ?
hvssyne said:
ok thanks, where is he ?
Click to expand...
Click to collapse
In twrp, go to advanced, close avb
cant wait antutu score/ bluetooth fix... android 10 dark mode is needed....!
What would the Bluetooth audio problems be?
would Bluetooth work?
I followed all the steps, including flashing vbmeta and don't boot. I'm using ZUI 11.1. Any ideias?
lukasads5461 said:
I followed all the steps, including flashing vbmeta and don't boot. I'm using ZUI 11.1. Any ideias?
Click to expand...
Click to collapse
Hi! Thank you very much Lucchetto00! I installed it! Solution:
1. Delete the kernel_v1.0_PERMISSIVE archive (path META-INF/kernel)!
2. Install as GSI ROM plus Permissiver_v5!
The solution to the auto brightness and NFC!
Hello guys, I've managed to fix the In screen fingerprint sensor and the bootloop, now ready to be your daily-driver. The updated link is on the first post
It's very hard to work without the device. You can help me with a donation to bring a better custom ROM experience to you. Thank you !
Money pool: https://paypal.me/pools/c/8kU7dpKNmZ
PayPal: https://paypal.me/lucchetto
info
good evening, multi-language (italy??) thanks
Buonasera, la rom supporta il multi lingua?? che purtroppo vorrei provare questa rom. Grazie
matrix_77 said:
good evening, multi-language (italy??) thanks
Buonasera, la rom supporta il multi lingua?? che purtroppo vorrei provare questa rom. Grazie
Click to expand...
Click to collapse
Certamente
perfetto
Perfetto, ma sei italiano?? cerco qualche guida in quanto almeno tolgo questo rom cinese (in quanto quella globlale non l'ho mai trovata) speriamo che funzioni tutto (ho letto solo bluetooth qualche problema il resto sembra funzionare correttamente). Grazie e buona serata Alessio. In più con questa rom originale ho problemi con le notifiche, che non arrivano quasi mai.
isaias19 said:
can you post antutu benchmark score?
Click to expand...
Click to collapse
Does the fingerprint already work in this version?
Luisds2110 said:
Does the fingerprint already work in this version?
Click to expand...
Click to collapse
Yessssss
Lucchetto00 said:
Yessssss
Click to expand...
Click to collapse
Fingerprint not working for me. Scanner lights up but doesn't recognize any of my fingers.
Also a couple of things I noticed.
1. Status bar - Icons are cut off when you change your DPI. Without changing the DPI the battery icon and the time is almost at the edge of the curve part of the screen.
2. Screen - Notice the sides of the screen? It has a force-like curve by software (not the real curve part of your screen), you can see the real curve of the screen not fill up. (sorry I can't explain it much better) I found a setting to change the curve but it doesn't work.. changing values doesn't do anything.
3. Built-in camera not working
4. No option to switch back button and menu button, I'm used to have back button on the right side and menu button on the left side which is a big downside for me.
Reverting back to ZUI for now. But thanks for your hard work even you don't own this device
Bugs:
- Bluetooth audio
Lucchetto00 Thank you very much for your build! I fixed the Bluetooth audio! EDIT 3 method:! Please lucchetto00 correct this in the next build!
hristcroixqwerty said:
Fingerprint not working for me. Scanner lights up but doesn't recognize any of my fingers.
Click to expand...
Click to collapse
It happens the same here, but I really don't care about fingerprint scanning for now...
hristcroixqwerty said:
I found a setting to change the curve but it doesn't work.. changing values doesn't do anything.
Click to expand...
Click to collapse
Where is this setting?
OK, I found it, and it's working. It's on Settings -> Device specific settings -> Misc options -> Set rounded corners diameter -> Set to 15 and it's perfect (to me, at least)...
hristcroixqwerty said:
3. Built-in camera not working
Click to expand...
Click to collapse
Actually, it works, but you need to change to front-camera and rear-camera again. It looks like it needs 'to refresh' some stuff...
ivan.cwb said:
It happens the same here, but I really don't care about fingerprint scanning for now...
Where is this setting?
OK, I found it, and it's working. It's on Settings -> Device specific settings -> Misc options -> Set rounded corners diameter -> Set to 15 and it's perfect (to me, at least)...
Actually, it works, but you need to change to front-camera and rear-camera again. It looks like it needs 'to refresh' some stuff...
Click to expand...
Click to collapse
Thanks for the infos!
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.
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.
I recently got a Realme C21-Y RMX3263 and when I was checking on how to unlock the Bootloader, it said I needed to install the In-Depth app. I downloaded it but when I clicked install it would not work. Anyone help please!
this might work:
How to root C21 with locked bootloader
https://github.com/bkerler/mtkclient please note that I will make a proper procedure in this post shortly. but in the mean time, you WILL need linux to be able to root your phone, as windows process does not work., while using linux, need to...
forum.xda-developers.com
Sto cercando di rimuovere il bootloader e il root con il metodo MTK; dopo aver avviato il loro .iso su VM ho seguito i passaggi aprendo la gui mtkClient, ma dopo aver collegato il telefono alla vm non viene rilevato; qualcuno ha già avuto questo problema, devo installare altri driver? (il debug e lo sblocco OEM sono abilitati)
View attachment IMG_20220316_173748_751.webp
PhotonIce said:
this might work:
How to root C21 with locked bootloader
https://github.com/bkerler/mtkclient please note that I will make a proper procedure in this post shortly. but in the mean time, you WILL need linux to be able to root your phone, as windows process does not work., while using linux, need to...
forum.xda-developers.com
Click to expand...
Click to collapse
I've tried it, I have high hopes for it but not a single combination would work on my phone. Not even for recovery mode. I have to use ADB to make it work. Is there an alternative way to boot the phone in BROM mode?
yetser77 said:
I've tried it, I have high hopes for it but not a single combination would work on my phone. Not even for recovery mode. I have to use ADB to make it work. Is there an alternative way to boot the phone in BROM mode?
Click to expand...
Click to collapse
Hi mate, the way i use is completely poweroff device and hold 3 key at the same time and plug usb cable while mtkclient is running.
It is quite easy actually.
Note that there are some users with realme C21Y, but it is not using a mediatek soc, so this way wont work for C21Y.
MrMiyamo said:
Hi mate, the way i use is completely poweroff device and hold 3 key at the same time and plug usb cable while mtkclient is running.
It is quite easy actually.
Note that there are some users with realme C21Y, but it is not using a mediatek soc, so this way wont work for C21Y.
Click to expand...
Click to collapse
How can I check if it's a Mediatek Socket though?
Realme C21 - Full phone specifications
www.gsmarena.com
(Mediatek Helio G35)
Realme C21Y - Full phone specifications
www.gsmarena.com
(Unisoc T610)
PhotonIce said:
It just is..
Realme C21 - Full phone specifications
www.gsmarena.com
(Mediatek Helio G35)
Click to expand...
Click to collapse
According to MrMiyamo, some people's C21Y does not use the Mediatek socket...
yetser77 said:
According to MrMiyamo, some people's C21Y does not use the Mediatek socket...
Click to expand...
Click to collapse
Just be sure your device does not have "Y" letter in production name. (Realme C21Y)
MrMiyamo said:
Just be sure your device does not have "Y" letter in production name. (Realme C21Y)
Click to expand...
Click to collapse
Oh well, mine does have the Y.
yetser77 said:
I recently got a Realme C21-Y RMX3263 and when I was checking on how to unlock the Bootloader, it said I needed to install the In-Depth app. I downloaded it but when I clicked install it would not work. Anyone help please!
Click to expand...
Click to collapse
Same problem, with the same phone, I can't unlock it either, did you unlock it ?
taccitua1 said:
Sto cercando di rimuovere il bootloader e il root con il metodo MTK; dopo aver avviato il loro .iso su VM ho seguito i passaggi aprendo la gui mtkClient, ma dopo aver collegato il telefono alla vm non viene rilevato; qualcuno ha già avuto questo problema, devo installare altri driver? (il debug e lo sblocco OEM sono abilitati)
View attachment 5562711
Click to expand...
Click to collapse
Please English only as per XDA rules
Mamo_grag17 said:
Same problem, with the same phone, I can't unlock it either, did you unlock it ?
Click to expand...
Click to collapse
Try follow the mtkclient guide, and make sure follow step by step. Be on android 10, and before booting phone for first time, hold vol- and power and then enter the fastboot flashing unlock command for full unlockd
Edit: as stated only for mediatek devices and this forum is for realme c21 not c21y