Related
IMPORTANT UPDATE : I have observed that when mounting system R/w device restarts. It means that even after rooting successfully, system is blocking the app. So rooting will not be complete as of now,till further corrections. Rest of the operations are normal, quick reboot apps work properly. and device works normally. So please bear with me.
Freinds , this thread is basically for what the title suggests. After a long time I was able to do it.
I'll update as required, so be patient. and keep watching.
1. Unlock Bootloader
a. Boot device in bootloader from adb in cmd terminal. (To go in fastboot mode, press power and volume down button ).
Please enter these commands, one at a time.
Code:
adb devices
(this will show your device)
adb reboot-bootloader
( device will reboot to bootloader). Then enter this...
fastboot devices
(this will show your device)
fastboot oem unlock-go
( If it shows already unlocked, go to twrp flash. If it is not, It will ask for erasing data, so backup all your data. This will unlock your bootloader.)
2. Flash TWRP
In fastboot mode: continue.......
Code:
fastboot flash recovery twrp.img
(Flash the image I have provided)
You can also try
fastboot boot twrp.img
( to try this image file, if you are scared of bricking the phone.)
3. Flash patched boot.
Code:
fastboot flash boot boot.img
(Flash the image I have provided. This is necessary as otherwise the su zip may not work )
4. Rooting
Please copy the SuperSu zip file to your micro sd card. Now boot to Twrp recovery. My advice is to backup of your system and boot. Then wipe data, dalvik-cache,cache, Internal storage. (Sometimes, format option is required.)
Now flash this zip.
If there are errors anywhere, please tell me and I shall try to correct them.
Updates :
1. Twrp stable added on 8/6/2018
2. Twrp_3.1.0.1 added on 11/6/2018, Removed Old Twrp link.
3. Twrp_3.1.0.1 Link updated on 13.6.2018.
4. Twrp_3.1.0.1 Link updated on 9.7.2019. Removed Old Twrp 3.1.0.1 link.
Downloads
1. Twrp_Stable_3.0.2.0.img: Link
2. TWRP_3.1.0.1_unofficial_SwipeEliteMax : https://drive.google.com/open?id=1n-DfHwC4_WRn_Jlr5FosOb6lW827M5ho
Remember first thing before rooting, do a backup of system and boot.img. Rest is your choice.
2. SuperSu zip: http://www.supersu.com/download Or you can download from anywhere on the net.
3. Patched Boot : Link
Stock Reflash and subsequent Update:
1. Stock Version V12 Reflash :
Remember , boot takes 5-10 mins to come on. So don't panic when device doesn't boot.
If the need arises due to any reason device hangs in logo, first restore only boot which you backed up. If still no change, restore system also.
But if you want to flash stock version , then read ahead.
The FOTA zip did not work for me from adb sideload. So I will recommend the QFIL download.
1. Download Stock Rom and Qualcomm downloader from here
Extract the zip. Install the drivers.
2. QFIL install : Download and install Qualcomm downloader.
It should look like the image in attachments
1. If it shows Flat Build / Meta Build, choose Flat Build.
2. Click "browse" and select "prog_emmc_firehose_8937_lite.mbn" , in the Extracted Stock rom folder
3. Click Load XML and select "rawprogram_unsparse.xml" in the Extracted Stock rom folder.
4. Click Load Patch and select "patch0.xml" in the Extracted Stock rom folder.
5. Click Download. If device is in adb mode, no problem, it will go in download mode automatically.
If it is not, just connect and shutdown device . While it is shutting down, it will connect automatically andf flash will begin.
Do not disconnect while process is on. Be patient.
2. Update to V15 :
After Stock reflash, the update to V15 comes immediately after connecting to internet.
Just incase someone wants to flash it offline , here is the process and file.
1. Recovery Method : Place gobi zip in adb folder . Go to stock recovery. Press Volume up and Power button. Once in recovery, choose "update from adb" .
Enter the following command in cmd console :
Code:
adb sideload update-gobi.zip.
Downloads : Update zip for Version Update from V12 to V15. Link
Yogesh1969 said:
Freinds , this thread is basically for what the title suggests. After a long time I was able to do it.
I'll update as required, so be patient. and keep watching.
1. Unlock Bootloader
a. Boot device in bootloader from adb in cmd terminal, Please enter these commands, one at a time.
2. Flash TWRP
In fastboot mode: continue.......
You can also try
3. Flash patched boot.
4. Rooting
Please copy the SuperSu zip file to your micro sd card.
My advice is to backup your data, then wipe data, dalvik-cache,cache, Internal storage. Sometimes, format option is required.
Now boot to Twrp recovery and flash this zip.
If there are errors anywhere, please tell me and I shall try to correct them.
Downloads
1. TWRP : https://drive.google.com/open?id=0BztfiMqkQrCaQVA4T01pRmlmYXc
Remember first thing before rooting, do a backup of system and boot. Rest is your schoice.
2. SuperSu zip: http://www.supersu.com/download
3. Boot : https://drive.google.com/open?id=19StfSorHM8T89uX07epstCWIUnMsITjz
Click to expand...
Click to collapse
Thanks for help bro. But the tarp zip file u shared needs a password to be opened.
Sorry
partha_h said:
Thanks for help bro. But the tarp zip file u shared needs a password to be opened.
Click to expand...
Click to collapse
Sorry Parth. I linked a wrong image . I now have updated the link. please check and tell me. Dont' hurry in any process. Take care.
Yogesh1969 said:
Sorry Parth. I linked a wrong image . I now have updated the link. please check and tell me. Dont' hurry in any process. Take care.
Click to expand...
Click to collapse
Thanks
Rooted my device successfully. Solved the twrp data decrypt password issue. Mounted super su via usb and my device is successfully rooted.
Thanks again
Now it's time to search for custom roms. Suggest me any ROM u recommend
partha_h said:
Thanks
Rooted my device successfully. Solved the twrp data decrypt password issue. Mounted super su via usb and my device is successfully rooted.
Thanks again
Now it's time to search for custom roms. Suggest me any ROM u recommend
Click to expand...
Click to collapse
Glad to hear that. I don't have any information about specific roms for swipe but we may have to port any aosp or lineage roms for our chipset (msm8937). Once I'm free, I'll get to search that. ....
partha_h said:
Thanks
Now it's time to search for custom roms. Suggest me any ROM u recommend
Click to expand...
Click to collapse
I have ported an AOSP for Redmi 3s. But it has flaws,(wifi, etc.) will take time. Also, I have removed all unwanted apps from the stock. So it is now smaller.
Sorry repeated msg
Yogesh1969 said:
I have ported an AOSP for Redmi 3s. But it has flaws,(wifi, etc.) will take time. Also, I have removed all unwanted apps from the stock. So it is now smaller.
Click to expand...
Click to collapse
Pls share if there is any . Thanks
partha_h said:
Pls share if there is any . Thanks
Click to expand...
Click to collapse
Actually, AOSP and lineage Os ,both are ported successfully. But there are some flaws. Time is a major factor.
Also, I think Our Rom is better than these roms. From twrp I removed all useless apps. So memory has increased a bit.
So, i think instead of marshmallow I should try Nougat or Oreo if possible. Of course time is an enemy . Just hope.
Yogesh1969 said:
Actually, AOSP and lineage Os ,both are ported successfully. But there are some flaws. Time is a major factor.
Also, I think Our Rom is better than these roms. From twrp I removed all useless apps. So memory has increased a bit.
So, i think instead of marshmallow I should try Nougat or Oreo if possible. Of course time is an enemy . Just hope.
Click to expand...
Click to collapse
Hi. U r doing great. Android 7 or 8 would be gud option. Keep up the good work. Thanks
Some one plz send build.prop file of swipe elite max
Some one plz send build.prop file of swipe elite max
Your build.prop attached.
Sachin2015 said:
Some one plz send build.prop file of swipe elite max
Click to expand...
Click to collapse
Is something wrong with your phone or just experimenting ?
Anyways, there are two build.prop files in the system folder, so attached both. good luck.
Yogesh1969 said:
Is something wrong with your phone or just experimenting ?
Anyways, there are two build.prop files in the system folder, so attached both. good luck.
Click to expand...
Click to collapse
Thanx Dude.
How to enable VoLTE for airtel user in this phone ?
How to write imei on this phone ?
and can u send a updated baseband file for this ?
Sachin2015 said:
Thanx Dude.
How to enable VoLTE for airtel user in this phone ?
How to write imei on this phone ?
and can u send a updated baseband file for this ?
Click to expand...
Click to collapse
Hi. This is a very late reply . Sorry for that.
To enable volte, you have to go to
Settings>More>Cellular networks.
Here, you have to enable/On Enhanced 4G Lte mode.
But, you have to remember, few things. Our phone has only one 4g and one 2g slot. You can use any slot for 4g. The other will automatically turn to 2g. This happens when you choose data for that sim.
Another problem you will face if you have the other sim of JIO. It works only in 4g. So if you awnt volte /4g on Airtel and other sim is Jio, you will have no network on Jio as it does not work in 2g/3g.
For Imei , just google SN / IMEI writing softwares from the net. But mind you enter the right IMEIs, as you mind land in trouble if non-matching one is written.
What base band file do you want ? The firmware folder ?
Yogesh1969 said:
Hi. This is a very late reply . Sorry for that.
To enable volte, you have to go to
Settings>More>Cellular networks.
Here, you have to enable/On Enhanced 4G Lte mode.
But, you have to remember, few things. Our phone has only one 4g and one 2g slot. You can use any slot for 4g. The other will automatically turn to 2g. This happens when you choose data for that sim.
Another problem you will face if you have the other sim of JIO. It works only in 4g. So if you awnt volte /4g on Airtel and other sim is Jio, you will have no network on Jio as it does not work in 2g/3g.
For Imei , just google SN / IMEI writing softwares from the net. But mind you enter the right IMEIs, as you mind land in trouble if non-matching one is written.
What base band file do you want ? The firmware folder ?
Click to expand...
Click to collapse
not showing any network..need the modem files
Sachin2015 said:
not showing any network..need the modem files
Click to expand...
Click to collapse
Did you get the files ? If you want the firmware folder, im attaching here.
This is Generic guide for Unbricking or Downgrading Huawei devices with Kirin 960 CPU. Most probably very similar steps can be done for Kirin 970, but i don't have device to test. At the end i did attach my files, that i used for CMR-W09.
This WILL WORK even if you have Black Screen with permanent Fastboot - this is common issue for those, who tried to downgrade from EMUI 9 to EMUI 8. Yes, this is also unbrickable!
Have Fun!
1. Prerequisites
- Linux installed on your PC/laptop or as Virtual Machine, with fastboot tool on it
- Board Software for your device – you can find on easy-firmware.com (about $15 for pass and reach collection) or gem-flash.com (has cheap $3 pass but less firmwares in collection)
HiKey_IDT linux tool – can be found there https://github.com/96boards-hikey/tools-images-hikey960/
- Knowledge about test point location to interrupt CPU loading routine – ask google or look on this forum
http://forum.gsmhosting.com/vbb/f1022/huawei-test-point-gallery-2291781/index17.html
- Opened device – you need access to motherboard
2. Booting device in force update mode
Small intro. Hisilicon Kirin CPUs has special mode, when they are interrupting normal boot process and opening COM port on USB to accept commands. You have chance to load your own binaries directly to device RAM before boot process will continue (still, this images has to be signed by Huawei private key)
- Disconnect battery connector from motherboard
- Short test point to ground (any big metal shield on board will work for that)
- Having test point shorted – connect USB cable. Run “lsusb” command – you should see device “USB SER” in devices
- Open folder with Board Software. Find xml file with model name in name, for ex. “CMR-W09-BD_1.0.0.19_Download.xml”. In that xml file – check section for “bootloaderimage” – you will find paths and memory addresses for all needed boot stages. Keep that open.
- Find all three boot img files – copy them to Linux machine. Note: For me, this three files didn’t work. But I found files with same names in other folder of Board Software – and that did a trick. You have to experiment a little bit.
- Go to folder, where you have HiKey_IDT tools downloaded. Copy three boot files from Board Software to same folder as hikey_idt. Edit “config” file – you should specify correct address and file name – according to Board Software
- Check “dmesg” command output – look for GSM Modem connected messages – you will see port name attached – like ttyUSB0
- Run next command “./hikey_idt -c config -p /dev/ttyUSB0”. You should see information about loaded all boot stages, with “Finish downloading” message after each. If you did everything fine – in 5-15 seconds you will have your device ready for downgrade/unbrick/killing_your_cat
- To verify that everything is fine – run “fastboot devices” command. If it will show device with proper serial number in output – you are fine to continue
3. Fixing your device
On that step – you have special fastboot booted, that has no security/validation on it. You can unbrick your device, or kill it. Do all steps carefully.
- Flash proper partition table information. You can take it from OTA package (from inside of UPDATE.APP) – normally, it has name HISIUFS_GPT. Run “fastboot flash ptable HISIUFS_GPT.img”
- Flash other partitions one by one. Skip files CRC.img, SHA256RSA.img, CURVER.img, VERLIST.img, PACKAGE_TYPE.img and HISIUFS_GPT.img (it was already flashed on previous step). To flash this files, run “fastboot flash” with partition name and image file name after it – for ex. “fastboot flash recovery_vendor RECOVERY_VENDOR.img”. Note: Partition names should be written in lowercase. You can see partition names in Huawei Update Extractor, as extracted image files sometimes has shortened names.
- Run few more commands to cleanup things around:
Code:
fastboot erase misc
fastboot erase modemnvm_factory
fastboot erase bootfail_info
fastboot erase dfx
fastboot erase rrecord
fastboot erase patch
- Flash few more files – from Board Software:
Code:
fastboot flash splash2 splash2.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot erase version
fastboot flash version version.img
fastboot flash reserved4 gpu_test_data_all_v2.bin (may be different for other devices – look into XML file from Board Software package for any “reserved” partitions)
- Remove USB cable, connect battery back and boot your device. Most probably your device will boot now! Or at least it will try
4. Final steps
- Make factory reset from stock recovery!
- Make 3-button flash of same or newer firmware just after restoring device!
- Make backup of your NVME and OEMINFO! Use next commands for that:
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img
dd if=/dev/block/bootdevice/by-name/nvme of=/storage/emulated/0/nvme.bak
Above commands are for adb shell with root. If you will do that under TWRP – you can use “of=/sdcard” in dd commands
Note: If your device is in bootloop, but runs recovery/eRecovery fine. If recovery is showing error during factory reset – maybe, you have screwed your nvme during previous upgrades/downgrades. In that case – make NVME backup using TWRP, take nvme.img from Board software package. Using any HEX editor – open both files, and copy all variable values from your backup to nvme.img from Board – manually. After doing that – repeat all steps from beginning until getting forced fastboot mode, and flash this image with “fastboot flash nvme”
P.S. In above links you may find lovely-prepared files for CMR-W09 tablet with region C432 for recovering to b161 firmware (includes recovery.sh script to flash everything in one command) - it can be used to get $4 unlock code with DC Unlocker.
HiKey_IDT => https://drive.google.com/open?id=1EdNfHVc8japoVSe2k4iTWdyp5JyPa1LR
Recovery Files for CMR-W09 C432 B161 => https://drive.google.com/open?id=1YgwwwFITjbJ8vIepcCt0O5w_RRJcKV8F
Board Software for CMR-W09 => https://drive.google.com/open?id=1w3mfVt8ObsViiv5ov3cUAog-M8hHMaSF
Testpoint location on Mediapad 10.8 (should be same on both Pro and non-Pro)
Reserved
Damn! I sent my tablet to a repair center two days ago...
Thank you for this great guide!
crckmc said:
Damn! I sent my tablet to a repair center two days ago...
Thank you for this great guide!
Click to expand...
Click to collapse
Nah, i'm not looking for fast ways! Decided that i can do it by my own ))) Btw, service center will not even try to repair your tablet - they will replace whole logic board or whole tablet.
For me It gives errors, I used my own device board fw.
Which device do you use? Did you boot it with testpoint?
If it is any of M5/M5 Pro (even if it is 8.4") - you can use files that i attached - hikey_idt is preconfigured. For other kirin960 devices that may need different boot files from own board
goodwin_c said:
Which device do you use? Did you boot it with testpoint?
If it is any of M5/M5 Pro (even if it is 8.4") - you can use files that i attached - hikey_idt is preconfigured. For other kirin960 devices that may need different boot files from own board
Click to expand...
Click to collapse
Booted with testpoint, and I used the Huawei P10 (It's a kirin960) and used my own boot files from the board fw. From what I know, I did a wrong downgrade, I did not know about the xloader thing going on, I had B386 installed, and tried do downgrade to B369a, different xloaders both of them. Now the screen is black, can't get into fastboot this way, I used DC-Phoenix too, managed to get somehow into fastboot, but these flashing errors still happened saying partition lenght get error, my logicboard may be already damaged tho.
yoghurt13 said:
Booted with testpoint, and I used the Huawei P10 (It's a kirin960) and used my own boot files from the board fw. From what I know, I did a wrong downgrade, I did not know about the xloader thing going on, I had B386 installed, and tried do downgrade to B369a, different xloaders both of them. Now the screen is black, can't get into fastboot this way, I used DC-Phoenix too, managed to get somehow into fastboot, but these flashing errors still happened saying partition lenght get error, my logicboard may be already damaged tho.
Click to expand...
Click to collapse
But the first - try hikey_idt with my files (it is preconfigured in attached archive). If it will be still throwing errors (i had same errors with wrong boot files) - take own files from your board. But not from "bootloaderimg" or "fastbootimage" folders - i got success with files from "update_nv_bootloader_block" folder of my board software package.
Next step - after you will boot board with hikey_idt and willl have fastboot loaded (screen will be still black - this is normal) - you will have to write partition table to device eMMC. For that - extract HISIUFS_GPT.img from UPDATE.APP and flash it as "ptable" - run "fastboot flash ptable HISIUFS_GPT.img". If that will go without errors - you can flash other images one by one.
What linux should i have? It's not possible under windows?
lukastob said:
What linux should i have? It's not possible under windows?
Click to expand...
Click to collapse
Any distro that you like - will work for you. If you are newbie - you can take Ubuntu for ex. Also, virtual machine with linux will be totally fine - just you should check everytime that USB is passed from host to VM. And no - i don't know about alternative tool for hikey_idt under WIndows, and service version of IDT - is bad-bad-bad. So, Linux is your choice.
Good jobs man ))) thanks from all users for testpoint
Well I managed to get into the special fastboot, and I could flash a few thing, but at least 5 images fail the verification, including Xloader, It's strage, as the Xloader still tries to verify things.
yoghurt13 said:
Well I managed to get into the special fastboot, and I could flash a few thing, but at least 5 images fail the verification, including Xloader, It's strage, as the Xloader still tries to verify things.
Click to expand...
Click to collapse
Try to flash xloader from OTA, not from board. From UPDATE.APP. Did you flash ptable in that mode?
goodwin_c said:
Try to flash xloader from OTA, not from board. From UPDATE.APP. Did you flash ptable in that mode?
Click to expand...
Click to collapse
I was doing that, I tried the ota xloader, and I tried the board sec_xloader too, they did not work, both of them has verification errors. Flashing DTS, fastboot, trustfirmware gives this error FAILED (remote: 'image verification error'). And yes, I flashed the Ptable too.
yoghurt13 said:
I was doing that, I tried the ota xloader, and I tried the board sec_xloader too, they did not work, both of them has verification errors. Flashing DTS, fastboot, trustfirmware gives this error FAILED (remote: 'image verification error'). And yes, I flashed the Ptable too.
Click to expand...
Click to collapse
from which folder did you take boot files for hikey_idt? maybe, you could try to take older board firmware? Or try to flash files from "fastbootimage" folder of your board.
goodwin_c said:
from which folder did you take boot files for hikey_idt? maybe, you could try to take older board firmware? Or try to flash files from "fastbootimage" folder of your board.
Click to expand...
Click to collapse
I literally have only 1 board firmware version the VTR-AL00, and I tried those stuff already, only your hikey-idt preconfigured got it into fastboot, after that I tried to flash my own board fw stuff onto it. So this whole thing might not work in my case.
yoghurt13 said:
I literally have only 1 board firmware version the VTR-AL00, and I tried those stuff already, only your hikey-idt preconfigured got it into fastboot, after that I tried to flash my own board fw stuff onto it. So this whole thing might not work in my case.
Click to expand...
Click to collapse
Can you share somewhere files from your board? i'll look into it.
goodwin_c said:
Can you share somewhere files from your board? i'll look into it.
Click to expand...
Click to collapse
Yeah, I'll upload the thing, I'll PM you the link.
Okay, I somehow managed to get it to work, found the perfect rom for the reset, BUT, the thing is, I lost my IMEI number from the phone, is there any way to reset it?
Amazing, thank you for this
---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------
yoghurt13 said:
Yeah, I'll upload the thing, I'll PM you the link.
Click to expand...
Click to collapse
I think because of the relocked bootloader
Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** 1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!
Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.
Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto
kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.
Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.
kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!
Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...
Hi everyone,
I have rooted my last few smartphones and was always happy with it. Now I got new Blackview BV9800 PRO and I want to root it with Magisk. but as the phone is new, there is lack of information on the internet, Anyway, I have found some information, but it is not complete and I believe You, smart guys, can help me to root my smartphone
This is the information I got:
How to root it with Magisk :
Download your rom from : viewtopic.php?f=285&t=532354 (you can alternatively extract it with SP Flash Tool and WWR)
Download and install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/rel ... v7.5.0.apk
Patch the boot image with Magisk Manager
Unlock the bootloader. (Wipe the phone! )
Flash the patched boot image with SP Flash Tool or Fastboot. (ONLY the boot image)
Reinstall Magisk Manager
This is what I did and what happened:
I installed latest Magisk apk from official sources. I opened the app, clicked on "Install Magisk", then via this app I downloaded the zip file, then tried to installed it via Magisk but got an error "Unsupported/Unknown image format".
Any ideas what have I done wrong? Did I have to flash boot image from the ROM, and not the one Magisk downloaded? P.S., the smartphone is new, nothing more then I written above is done to it (no oem unlocking, no usb debugging, etc).
RESERVED
I let Magisk manager patch the original boot.img. After flashing it with fastboot or SP Flash the phone stuck with message that verified boot didn't accept the signature.
Hm... Is there anyone who rooted BV9800 Pro successfuly and could guide us? ?
update fail.
I greet you, I accidentally deleted it when I updated, Nvram. on my phone. BV9800pro. It is possible to provide me with firmware recovered from a similar phone. I also posted on the forum at Blackview but without answer
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
update fail
LGZACRO said:
Isn't there a full firmware download on Blackview website available? I thought I've seen it there
Click to expand...
Click to collapse
Hello
Yesterday during an update, by accident, my equipment, BV9800pro, performed a complete formatting, "Full Format + Dowload", it seems that Nvram has also been rewritten. it is possible to provide us with a solution or file with this data, specific to our equipment. i need a original nvram.bin, and nvram.data, in firmware from Blackview site this its not exist..
if someone wants to help me, I send them a private message with their email address
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
LGZACRO said:
My phone is not rooted unfortunatelly, if I can help in anyway (if there is a way) I would pull out the files for You.
Do You know how to guaranteed root BV9800 Pro without running into problems?
Click to expand...
Click to collapse
who guarantees this?
rooting worked for me with that solution given to the PM. I wanted to install AOSP, but I found that the thermal image did not work anymore, there were some problems when previewing the video files from Facebook, and I gave up. from the mistake as I mentioned I format + dowload and delete all important partitions. nvram .bin si nvdata. Nothing works properly, TEE and Google Key are inactive, the thermal image fails, some applications are closed immediately. This is the experience with rooting and installing AOSP on the BV9800Pro
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
make total firmware dump and send the bakup , or nvram.bin nvdata.bin file,
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
i dont now. i dont install twrp.
Ok, pm me your skype or signal or wickr or fb. We will try to do this in few hours
LGZACRO said:
Oh man... Sounds bad... have You emailed blackview after sale support (via email, not forum)? No response from them?
And let's say I only root my BV9800Pro, will I be able to send You the files You need?
Click to expand...
Click to collapse
I posted in their forum a detailed error report but the moderator deleted my post.
Don't bargain for help by them.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
LGZACRO said:
I must root to be able ro do this, right? Does TWRP works well on BV9800Pro?
Click to expand...
Click to collapse
As I mention there's no TWRP available for this phone yet.
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
I rooted it exactly like You and it worked perfectly! Thanks for auch detailed rooting guide!
By the way guys, I think we Should open the request for TWRP for BV9800Pro. How do You think?
After you unlocked bootloader, it changed to orange state, and it always shows "Your device has been unlocked and can't be trusted..Your device will boot in 5 seconds", it could be resolved by modified LK image.
Refer to
1. https://forum.hovatek.com/thread-31664.html
2. http://bbs.blackview.hk/viewtopic.php?f=286&t=532899 -- included modified LK image
Of course, you could reflash by fastboot, no need to use SP flash tool.
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
james35888 said:
I just rooted BV9800 pro yesterday.
You don't need to SP flash tool or others, just need adb and fastboot.
Quick steps:
1. set OEM unlock to allow
2. connect phone to windows
3. use adb to check if connecting. command: adb devices
4. using adb to reboot to bootloader, command: adb reboot bootloader
5. And then the phone will enter fastboot mode ( you could see small string at left bottom corner)
6. use fastboot command to unlock bootloader. command: fastboot flashing unlock
7. If fastboot program is waiting, please check windows device manager, there should be an unknown device, let windows search driver automatically. it needs android interface driver.
8.Using volume up or down to agree unlock.
9. If agree, all data will be disappeared.
10. Install Magisk manger
11. Download stock ROM from blackview forum. it is zip file. Unzip it and copy boot-verified.img to phone.
12. patch boot.img by Magisk manger.
13. Copy patch image file to windows
14. use adb to reboot phone to fastboot mode
15. reflash boot image file. command: fastboot flash boot patched file name (normally, I would put patch image file in the same folder of fastboot)
16. reboot (fastboot reboot) and reinstall Magisk manager
There are many Magisk root steps instruction in internet. You could refer to other steps, they should be clear than mine. I prepared lots of drivers and application. Finally, I only used adb and fastboot to root this phone.
Click to expand...
Click to collapse
zlatkomas said:
hi if u have back up on your phone could u provide for me link. I had some problems with my loudspeaker and i thought its from the root, or software and i did full format and download. and now it show some watermark and probably is because i l deleted NVRAM.
i download already official version but didn't help ... thank u upfront.
Click to expand...
Click to collapse
Hi, I'm not rooted (yet) and my BV9800 PRO is having some issues with the loudspeaker, any media like YouTube or Spotify, play audio for a second or two and then just go mute, volume can be high but no audio at all, phone calls last longer but also go mute and have to go back to regular "ear-speaker" to keep listen to the other side. Are this the same problems you refer to? I can't remember if this happened after the OTA update tho. Thank you.
Finally got root on LG-Velvet LM-G900EM
Here is how i did.
I know...this is finally little bit complicated, but i dont want to copy something that possibly affects copyrights or other stuff.
Here is all that i've learned and done.
So you should be able to root also.
Prerequisites:
(allways have a valid backup)
- Unlocked LG-Velvet-Bootloader (on android device)
- Installed Python (on pc):
https://www.python.org/
- Unpacked Steadfast kdz-tools (on pc):
https://github.com/WildOne69/kdztools
(Modify the undz.py: Put a # in line 26. This should look like this:"#import zstandard as zstd"
Otherwhise you will get an error:"ModuleNotFoundError: No module named 'zstandard'"
- Downloaded Velvet Stock-Rom (kdz) (on pc)
http://lg-roms.com/lg-firmware/lmg900em/g900em10c/9081
1. Download the kdz-rom from lg-roms (on pc)
(this uses a special download-tool which may be spain)
Finally you should have something like:
G900EM10f_00_0716.kdz
2. Extract a dz-file from the kdz-file. (on pc)
Go to the directory where you've stored the kdz-tools.
example:
python unkdz.py -f G900EM10f_00_0716.kdz -x
(this gains something like G90010f_0_user-signed-ARB0_COM1_EU_OP_0716.dz in a subdirectory)
3. Extract the boot.img from the extracted dz-file. (on pc)
example:
python undz.py -f c:G90010f_0_user-signed-ARB0_COM1_EU_OP_0716.dz -s 40
..now you've got a boot_a.image hopefully in a subdirectory.
This is the original boot.img
4. Copy the boot.img to your mobile. (from pc to android device)
5. Run Magisk and patch the extracted boot.img (on android device)
6. Copy the magisk_patched.img to your computer again. (from android device to pc)
7. adb reboot bootloader (on pc)
Keep in mind that the Velvet is an A/B device, so we need to flash the boot.img twice.
8. fastboot flash boot_a magisk_patched.img
(on pc)
9. fastboot flash boot_b magisk_patched.img
(on pc)
10. fastboot reboot
(on pc)
11. Open Magisk and pray that you've root.
(on android device)
Have fun.
BR
Mike
PS:
Be careful locking your bootloader afterwards. As i've observed locking the bootloader again resets the mobile back to factory-defaults...so all your work has been gone.
I'm not responsible if you brick your device or it takes harm in any case.
Updates: As LG launched updates twice meanwhile i was forced to patch the boot-partitions again.
Simpliest way to do the updates with root:
- Start the update with LG-Bridge.
- After the download of the new KDZ is complete copy it out of the temp-directory (to extract the boot_a.img later)
- Do the phone-update with LG-Bridge. (Now your phone is in an unrooted state again)
- proceed with steps 2-11
- Jobs done (Actual android-version rooted)
Is there anyway to get this to work with lg-G900UM
Catrock31 said:
Is there anyway to get this to work with lg-G900UM
Click to expand...
Click to collapse
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.
MikGx said:
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.
Click to expand...
Click to collapse
Guys, can you upload the stock ringtones ?
Thks
Nice work OP. Works like a charm. I remember the pre-Nougat days when rooting an Android device was, for the most part, a simple affair. Nowadays, with A/B partitions, Forward Error Correction (FEC), system-as-root, etc., rooting is tedious to say the least. Nice job figuring this one out. :good:
Hi!
The undz.py returs this error message :
File "undz.py", line 173
if cmd.batchMode:
^
TabError: inconsistent use of tabs and spaces in indentation
Can you help?
Bandetos said:
Hi!
The undz.py returs this error message :
File "undz.py", line 173
if cmd.batchMode:
^
TabError: inconsistent use of tabs and spaces in indentation
Can you help?
Click to expand...
Click to collapse
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.
MikGx said:
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.
Click to expand...
Click to collapse
it doesn't working
maybe attach the boot.img file
if you check the version of python you got:
Python.3.8_3.8.1776.0
?
to be honest...dont want to take care on a file-store in the internet.
LG launchned a new FOTA...and a new kdz.
Turned out that flashin the old magisk_patched.img (boot.img) extracted from the old kdz causes UI-performance problems if you reflash it after update.
Usually magisk-SU should work if you prevent reboot after install the FOTA and then flashing magisk in the newest app version to the inactive slot.
Failback: if you run into this performance-issues, you can use lg bridge (!!!hopefully have an existing LG-Switch-Backup!!!) to set back your Velvet to defaults.
You can copy out the new kdz during the extraction-phase of LGBridge (so you dont need to download it extra) from your win-userprofile (c:\users\username\AppData\Local\LG.....\Update(something)\*.kdz
...and extract the new boot.img as described in the first article.
Install magisk and root the boot.img also as described first.
Then restore your latest LGSwitch backup and all is fine.
At the moment im working on a twrp-solution based on the work of mauronofrio from twrp-team. I can boot TWRP (based on avicii .13) but i am only able to backup (metadata and super).
Not gettin userdata and boot(recovery). Thi is hard as the velvet seems to be treble&A/B.
...i'm no dev...just like to play lego. )
Either way, it's good to see that we at least have a few people trying to figure out things with this device. Honestly, I still carry my Redmi Note 7 Pro with me every day because of how much I miss being able to download a custom rom etc.
MikGx said:
LG launchned a new FOTA...and a new kdz.
Turned out that flashin the old magisk_patched.img (boot.img) extracted from the old kdz causes UI-performance problems if you reflash it after update.
Usually magisk-SU should work if you prevent reboot after install the FOTA and then flashing magisk in the newest app version to the inactive slot.
Failback: if you run into this performance-issues, you can use lg bridge (!!!hopefully have an existing LG-Switch-Backup!!!) to set back your Velvet to defaults.
You can copy out the new kdz during the extraction-phase of LGBridge (so you dont need to download it extra) from your win-userprofile (c:\users\username\AppData\Local\LG.....\Update(something)\*.kdz
...and extract the new boot.img as described in the first article.
Install magisk and root the boot.img also as described first.
Then restore your latest LGSwitch backup and all is fine.
At the moment im working on a twrp-solution based on the work of mauronofrio from twrp-team. I can boot TWRP (based on avicii .13) but i am only able to backup (metadata and super).
Not gettin userdata and boot(recovery). Thi is hard as the velvet seems to be treble&A/B.
...i'm no dev...just like to play lego. )
Click to expand...
Click to collapse
Catrock31 said:
Is there anyway to get this to work with lg-G900UM
Click to expand...
Click to collapse
Hello.
I have a LG from Freedom Mobile.
Does this procedure work on their phones?
I'd like to use the dual sim capabilities.
JackTheMan18 said:
Hello.
I have a LG from Freedom Mobile.
Does this procedure work on their phones?
I'd like to use the dual sim capabilities.
Click to expand...
Click to collapse
I did that on an LM-G900EM. (No dual sim)
As i did it just usin the stock-rom, theoretically dual sim capability shoudnt get lost.
All this stands and falls with the possibility to unlock the bootloader.
If LG provides an unlock-code the rest should work.
Good
Very good, you are very good. As a LG velvet Chinese user, I sincerely hope that you can develop a ROM compatible with China’s 5G
BruceLee131 said:
Very good, you are very good. As a LG velvet Chinese user, I sincerely hope that you can develop a ROM compatible with China’s 5G
Click to expand...
Click to collapse
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.
MikGx said:
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.
Click to expand...
Click to collapse
I'm also getting this error. I did try a second time following your steps to a tee and still getting the same error.
MikGx said:
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.
Click to expand...
Click to collapse
Hi, I have bought LG Wing. I have entered into Developer Mode and I have activated OEM unlocked option. So do I need a bootloader unlock code? Can I root LG Wing with your instructions?
How did you get adb to recognize your device once you put it in download mode?
MikGx said:
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.
Click to expand...
Click to collapse
I'm sorry if this is a dumb question, but if it isn't possible to get an unlock code for the G900UM (U.S. model), is there a way to gain SU status/root without unlocking the bootloader? I'm sure there's no exploit to unlock the bootloader without LG code, but I saw in some other threads (different makes/models) discussion of gaining SU via fastboot without unlocking the bootloader? So if my main concern is knowing everything that is on my phone and eliminating privacy/security vulnerabilties, can I gain SU status without unlocking the bootloader?
MikGx said:
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.
Click to expand...
Click to collapse
I got the unlock.bin file from LG.
I'm not afraid to flash any partition...
it's simply impossible to flash twrp-3.4.0-g900em-dom133.imgù
writing 'recovery'...
FAILED (remote: Cannot flash this partition in unlocked state)
And even boot with that recovery
downloading 'boot.img'...
OKAY [ 0.718s]
booting...
FAILED (remote: BootImage is Incomplete)
Finally i'm not able to extract boot.img form LG kdz stock rom