Related
K6 POWER SOFTWARE UPDATE LINKS
s156 to s223 download link: http://phonedl.ota.lenovomm.com/dls/v6/K33_S156_170220_ROW_TO_K33_S223_170610_ROW_WC460DDB76.zip
(Thanks to NanuZn)
s222 to s223 download link:
http://phonedl.ota.lenovomm.com/dls/v6/K33_S222_170523_ROW_TO_K33_S223_170610_ROW_WCD418A4CF.zip
(Thanks to EthannSiva)
s156 to s222 download link: https://www.androidfilehost.com/?fid=745425885120738879
(Thanks to Karthick)
s150 to s156 download link:
http://phonedl.ota.lenovomm.com/dls/v6/K33_S150_161114_ROW_TO_K33_S156_170220_ROW_WCB6723108.zip
( Note: 1.Use stock recovery to flash... Rename ota.zip to update.zip... Put that update.zip file in root of sd card. 2. If you want to flash using twrp recovery, you need to edit updater-script to do so.)
UNLOCK BOOTLOADER SIMPLE GUIDE
Enable adb and OEM options in developer settings and conect your k6 via usb(also you need to download adb and fastboot utilities for your PC).
in CMD or a GNU/Linux Terminal you will need paste one per one line.
Code:
adb reboot bootloader
fastboot -i 0x17ef oem device-info echo "check bl"
fastboot -i 0x17ef oem unlock-go
INSTALL RECOVERY
You can get the recovery from karthick thread:
https://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-lenovo-vibe-k6-t3618912
Code:
fastboot -i 0x17ef flash recovery <recovery Name>.img
ROOT
just flash super su zip from chainfire in your recovery
You can find it here:
http://www.supersu.com/download
How to flash stock s156-s223 nougat OTA zip using TWRP recovery?
1. open OTA zip file in X-plore file manager..
2. Go to folder meta-inf/com/google/Android where updater-script has been located
3. Open updater-script as a txt(text) file in X-plore file manager & delete first & second line. (Stop when word ui-print come)
4. Go to menu, save it.. it will take several seconds/minutes to get saved changes.
5. Go to TWRP recovery & flash.
6. Enjoy stock nougat 7.0 for Lenovo k6 power.
OUR TELEGRAM GROUP
https://t.me/joinchat/AAAAAEPrej6nmzca5GK_fw
MANY THANKS FOR OUR COMMUNITY ON TELGRAM AND; @siva1234
STR4NG3R-GUY said:
K6 POWER SOFTWARE UPDATE LINKS
s156 to s223 download link: http://phonedl.ota.lenovomm.com/dls/v6/K33_S156_170220_ROW_TO_K33_S223_170610_ROW_WC460DDB76.zip
(Thanks to NanuZn)
s222 to s223 download link:
http://phonedl.ota.lenovomm.com/dls/v6/K33_S222_170523_ROW_TO_K33_S223_170610_ROW_WCD418A4CF.zip
(Thanks to EthannSiva)
s156 to s222 download link: https://www.androidfilehost.com/?fid=745425885120738879
(Thanks to Karthick)
s150 to s156 download link:
http://phonedl.ota.lenovomm.com/dls/v6/K33_S150_161114_ROW_TO_K33_S156_170220_ROW_WCB6723108.zip
( Note: 1.Use stock recovery to flash... Rename ota.zip to update.zip... Put that update.zip file in root of sd card. 2. If you want to flash using twrp recovery, you need to edit updater-script to do so.)
UNLOCK BOOTLOADER SIMPLE GUIDE
Enable adb developer settings and conect your k6 via usb(also you need to download adb and fastboot utilities).
INSTALL RECOVERY
You can get the recovery from karthick thread:
https://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-lenovo-vibe-k6-t3618912
ROOT
just flash super su zip from chainfire in your recovery
How to flash stock s156-s223 nougat OTA zip using TWRP recovery?
1. open OTA zip file in X-plore file manager..
2. Go to folder meta-inf/com/google/Android where updater-script has been located
3. Open updater-script as a txt(text) file in X-plore file manager & delete first & second line. (Stop when word ui-print come)
4. Go to menu, save it.. it will take several seconds/minutes to get saved changes.
5. Go to TWRP recovery & flash.
6. Enjoy stock nougat 7.0 for Lenovo k6 power.
OUR TELEGRAM GROUP
https://t.me/joinchat/AAAAAEPrej6nmzca5GK_fw
MANY THANKS FOR OUR COMMUNITY ON TELGRAM AND; @siva1234
Click to expand...
Click to collapse
:good:
Useful guide. Do you think bootloader re-lock and flashback stock recovery are also possible?
roti86 said:
Useful guide. Do you think bootloader re-lock and flashback stock recovery are also possible?
Click to expand...
Click to collapse
Yes and yes.
Sorry for the to late reply, if you want install stock recovery download your firmware and flash the recovery via fastboot, but if you want go back to stock flash the firmware via qfil(be careful and make a backup on your external storage if you lost the imei(efs, baseband) you can restore via your backup of TWRP).
recently bought k6 power,It came with marsmallow s150 and asked to update marshmallow s156.It was about 75mb.
After it,asked for nougat s223 which i know that has lots of bugs now.So ignored the update and simply disabled update notification
I'll stick with s156 till there is a clear cut bug free nougat version.No need to install unless i want headache
Lenovo has bad reputation for updating their devices.They ruin the next version of android.Simply disaster.
So I would all advise you to stick with s156.
Bro update to S229 .it has fixed some bugs nd ui becomes smoother then previous.
Hello
I have updated to s229 by system update, i want to go back to s156.
I m on official rom. Can you guys please help?
Can i use the full ota zip to downgrade? If no then, is there any way to get the official link to download rom, i don't trust the rom from other sources and file sharing sites.
Thanks
I never had issue on s 223 even just reset your device after upgrading android ....
Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Root
Tested on "GQ3085DH1_KSP2E_Ulefone_EEA_20200312_V01（Eu）" (Baseband version MOLY.WR8.W1449.MD.WG.MP.V237.4,2019/10/28 09:26, Kernel version 4.9.117 #2 Mon Oct 28 09:48:24 CST 2019)
Unlocking bootloader and disable verification (fastboot - min. version 1.8, vbmeta.img from stock rom):
fastboot flashing unlock
(volume up)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
On Android - Mtk-easy-su-v1.1.3.apk & MagiskManager-v7.5.1.apk.
Mtk-easy-su:
1. Run on boot
2. Magisk.v20.4.zip (assets-r22) - install
3. "Activate bootless root"
Restart phone. After start, wait to see "Success" on screen (bottom). Magisk work.
After root, if adb is needed:
adb shell
su
mount -o rw,remount /
Do you have made any progress?
Im sitting here on my armor x6 and have the same problems.
ahaff said:
Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Click to expand...
Click to collapse
Yo, can you send me the port of TWRP for this phone please?
Please read this guide fully before attempting to follow it. It requires some knowledge of how to use a Terminal and basic ADB/Fastboot operation. I don't think this guide is thorough enough for a person who's modifying their phone for the very first time. Feel free to ask for help though!
I am not reliable for any adverse effects this guide might have on your phone. If something breaks, that's your responsibility. However: if your phone doesn't boot anymore, but you can still get into fastboot, you should be able to flash the Stock Firmware OFP using the Realme Flash Tool. To get into fastboot, power off your phone, wait a few seconds, and hold power and volume down until you see the fastboot logo.
This guide was cobbled together using various other tutorials and my own attempts. I've used it on my RMX2075. It should also work for the RMX2076. The files Realme provides for the RMX2075 are named "RMX2076", so I assume they're the same device. I have no idea how the RMX2071 fits into this. Curiously, the TWRP version used here is intended for the RMX2071, although it works flawlessly on my RMX2075. However: if you're using it on an RMX2075/2076 TWRP thinks you're using an RMX2071, so it won't flash packages intended for the RMX2075/2076. Hence the following warning:
!!! YOU WON'T BE ABLE TO INSTALL OTA UPDATES AFTER INSTALLING TWRP !!!
If you attempt to install an OTA Update downloaded from within the Settings.app, the phone will reboot, TWRP will attempt to install the OTA Update and fail with an error. This does not break anything, it just doesn't update.
DOWNLOADS:
- Realme Flash Tool
- Stock Firmware OFP
- OTA Update OZIP
- TWRP 3.4.1b for RMX2071 by wzsx150 and LR. Team
Spoiler: further details
The licensing of this TWRP is pretty unclear, so I can't provide a download link. If you search for it Online, make sure to find a version that includes both "recovery.img" and "misc.bin"
- Realme DeepTesting App
- Magisk Manager by topjohnwu
- oppo ozip decrypt
PREPARATION:
- install ADB & Fastboot on your computer
- enable "USB debugging" on your phone
- install the oppo ozip decryption tool by following the instruction on the GitHub page
UNLOCKING
- follow the unlock instructions provided by the official Realme Tutorial
RESTORING AND UPDATING - if you're on firmware A42, skip this step
- follow the restore instructions provided by the official Realme Tutorial
- go to the Realme Software Update page, click on "How to update?" and follow the instructions
FLASH TWRP
- open a Terminal window and cd into the folder that holds recovery.img and misc.bin
cd /path/to/folder
- enter the following commands and hit enter after each
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash misc misc.bin
fastboot reboot recovery
- your phone should now reboot into TWRP
- enter your phones unlock code if you have one
- go to "Advanced" -> "Disable Replace TWRP"
- reboot phone
ROOTING
DO NOT use "Install Root" in TWRP, it'll "destroy" the bootloader and you'll have to flash the stock firmware
Follow this instead:
- decrypt the OTA .ozip using the oppo ozip decrypt tool (instructions on its GitHub page)
- unzip the resulting decrypted file
- copy "boot.img" onto your phone
- copy "/firmware-update/vbmeta.img" into a folder of your choice
- install Magisk Manager on your phone
- open Magisk Manager, tap on "Install" followed by "Select and Patch a File"
- select the "boot.img" you've previously copied onto your phone and let Magisk do its thing
- the patched "boot.img" is called "magisk_patched_XXXX.img" or something similar. Make note of the resulting file name which is specific to you.
- copy the patched "magisk_patched_XXXX.img" into the same folder that holds your "vbmeta.img"
- open a terminal and cd into the folder that holds the patched "boot.img" and "vbmeta.img"
- enter the following commands and hit enter after each
adb reboot bootloader
in the following step, replace "magisk_patched_XXXX.img" with whatever your patched "boot.img" is called
fastboot flash boot magisk_patched_XXXX.img/ICODE]
[ICODE]fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
- your phone should now be rooted
I have also uploaded the stock boot.img along with the rooted version as well as vbmeta.img here. They were created using the method described above with OTA update A42. I would recommend creating your own though, since this has a higher chance of success.
Another method to get the stock boot.img and vbmeta.img is creating a TWRP backup, renaming "boot.emmc.win" to "boot.img", and "vbmeta.emmc.win" to "vbmeta.img". I have NOT TESTED this method.
I don't know if this will work for Android 11 / ColorOS 2.0. My theory is that if you can get the RMX2076PU_11.C.16.ozip somewhere, you could just follow this guide using it instead of the A42 one. Again, I have NOT TESTED this method.
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
corneo said:
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
Click to expand...
Click to collapse
Android 11twrp brush Android 10, and then brush Android 10twrp, you can boot
can u using volte with stock ofp eu version?
Hey guys, since I couldn't find a tutorial for downgrading the Nord 2, here is my way how i did it:
[IMPORTANT: @EricH7001 replied that there is an easier workaround to install android 12 (https://community.oneplus.com/wap/thread?id=1170930960406413321) where you don't have to flash A.20. I would still recommend doing a TWRP backup before trying this method. Some people in that thread said that they couldn't install the C.10 afterwards so proceed at your own risk]
Quick disclaimer: you WILL lose ALL your data so I would strongly recommend that you do a twrp backup now
files you need:
partitionsbackupper
adb (pllatform-tools)
A.20 firmware (donwload here)
unlocked bootloader
how to preceed:
1. place the extracted firmware file (folder named PartitionsBackup) and the partionsbackupper.bat in the platform-tools folder
2. boot the phone into fastboot mode
3. run the partitionsbackupper.bat file and select restore
4. after the installation the phone should reboot.
5. reboot to recovery if not already in (if you end up in fastboot mode just type "fastboot reboot recovery)
6. in recovery mode select wipe and then wipe data
7 after that format data
8. the phone will now reboot into oxygenOS 11 A.20
There you go! You can now install the android 12 C.01 from the oxygen updater app
Thanks for your tutorial, I'll do it on my phone tomorrow when I get to work
Eriksen_ said:
Hey guys, since I couldn't find a tutorial for downgrading the Nord 2, here is my way how i did it:
Quick disclaimer: you WILL lose ALL your data so I would strongly recommend that you do a twrp backup now
files you need:
partitionsbackupper
adb (pllatform-tools)
A.20 firmware (donwload here)
unlocked bootloader
how to preceed:
1. place the extracted firmware file (folder named PartitionsBackup) and the partionsbackupper.bat in the platform-tools folder
2. boot the phone into fastboot mode
3. run the partitionsbackupper.bat file and select restore
4. after the installation the phone should reboot.
5. reboot to recovery if not already in (if you end up in fastboot mode just type "fastboot reboot recovery)
6. in recovery mode select wipe and then wipe data
7 after that format data
8. the phone will now reboot into oxygenOS 11 A.20
There you go! You can now install the android 12 C.01 from the oxygen updater app
Click to expand...
Click to collapse
https://community.oneplus.com/wap/thread?id=1170930960406413321 [Nord 2 A21 EU solution]
EricH7001 said:
https://community.oneplus.com/wap/thread?id=1170930960406413321 [Nord 2 A21 EU solution]
Click to expand...
Click to collapse
Thanks for the reply, I couldn't find this post anywhere before posting this thread. I will add this url to my thread.
i'm a sound lover, so i rooted my Samsung to get Viper4AndroidFx working.
I guess that this method is almost universal for Samsung devices, bit i'm not sure about that so be careful with this.
-you will void warranty for your device-
--Root access on the SM-A21F with the newest Firmware(A217FXXU8DVG4) update and Android 12--
if you are new to all of this search for all the things need first.(I used just heimdall for flashing, because JOdin3CASUAL throws error at me because of a corrupted pit file, don't know how to workaround this)
MAKE SURE YOU HAVE THE RIGHT FIRMWARE FOR THE FLASH!!!
Needs:
-Linux Machine for flashing tool Heimdall(try ubuntu studio for sound experience)
sudo apt install heimdall
There is also a frontend(GUI) for this tool:
sudo apt install heimdall-frontend
(install heimdall first, then the frontend)
-samloader Firmware tool(search for instructions to get the right Firmware)
-lz4 compression librarys to decompress the boot.img from stock firmware
-Magisk app(magisk from f-droid works)
-USB debugging allowed and OEM unlock enabled on your Samsung phone(search for developer options to do this and long press vol-up in Download mode)
1. get the firmware with samloader, decode,decompress,rename to ZIP and open the archive.Decompress the AP section, decompress the boot.img.lz4
2.put the boot.img on your phones storage to patch it with Magisk.
3.put the patched boot.img back on your Computer in a new folder and rename it back to it's original name boot.img
-make sure your phone is charged before you flash the image!
4.connect your device in download mode to the Computer(for SM-A217F:turn off the phone, press vol+ and vol- hold it both and connect the USB cable)
5.open a terminal window in the new folder where the patched and renamed boot.img is placed and type sudo heimdall print-pit, it shows the partition table of your device, for --BOOT you can also type the number of the partition as it's shown in the pit file)
sudo heimdall flash --BOOT boot.img
If anything goes wrong you can always flash back the original boot.img from downloaded stock firmware or unroot your device this way.
After this your device is rooted but there is no Twrp custom recovery for ths model yet.
The unofficial release which can be found on xda doesn't work for me. I've flashed it but got stuck in download mode.
Flashing works fine with other rooting tools but there is no way to get rid of the unrooted stock recovery yet.
I cannot guarantee you that this guide won't Brick your phone. Just be careful with the re-partition options in Odin, if you want to use it. All the work can be done with linux, heimdall and magisk.
heimdall print-pit will show the partititition table from your device.
--+no warranties. What works for me must not work for others.
For everyone who wants to root and no method has worked for him, or you have errors, or your device has not booted after the root.
You can follow the following explanation
Firstly, I used sm-a217f/ds phone
The baseband version is A217FXXU8DVG4
And its protection is U8
Android 12
First of all, you must disable the bootloader ... and this is very important so that no errors occur ... and also do a factory reset for your phone. So you should transfer all your important files before that
1- Get your official ROM from any trusted site
2- Decompress the ROM file and it will show you all the ROM files AP - BL - CP - CSC - HOME_CSC
3- Take the AP file and transfer it to your phone
4- Then download the latest version of the Magisk application
5- Then open the application and inject the AP file into it
6- The injection process takes a relatively long time. I think it takes five minutes or less, depending on the size of the AP file
7- After the injection process is complete, you will find the file that was injected with Magisk in the download files
8- Take the injected file and put it into the computer
9- Then open the Odin application and put the file that was injected into the AP box
10- Put all the rest of the files in your ROM file into Odin
11- We cancel the autorun mode from Odin
12- Then press Start
13- After the process is completed, restart the phone and remove the USB cable, and the phone will ask you to do a factory reset again, and press OK
14- Now the phone supports root
15- After unlocking the phone, install the Magisk app again
16- The application will ask you to download an additional component, click OK, and the phone will restart again
17- Now you have a rooted phone that has been linked to the Magisk application
I think this is the easiest explanation of rooting in detail
And good luck to all of you.
hamada2001 said:
For everyone who wants to root and no method has worked for him, or you have errors, or your device has not booted after the root.
You can follow the following explanation
Firstly, I used sm-a217f/ds phone
The baseband version is A217FXXU8DVG4
And its protection is U8
Android 12
First of all, you must disable the bootloader ... and this is very important so that no errors occur ... and also do a factory reset for your phone. So you should transfer all your important files before that
1- Get your official ROM from any trusted site
2- Decompress the ROM file and it will show you all the ROM files AP - BL - CP - CSC - HOME_CSC
3- Take the AP file and transfer it to your phone
4- Then download the latest version of the Magisk application
5- Then open the application and inject the AP file into it
6- The injection process takes a relatively long time. I think it takes five minutes or less, depending on the size of the AP file
7- After the injection process is complete, you will find the file that was injected with Magisk in the download files
8- Take the injected file and put it into the computer
9- Then open the Odin application and put the file that was injected into the AP box
10- Put all the rest of the files in your ROM file into Odin
11- We cancel the autorun mode from Odin
12- Then press Start
13- After the process is completed, restart the phone and remove the USB cable, and the phone will ask you to do a factory reset again, and press OK
14- Now the phone supports root
15- After unlocking the phone, install the Magisk app again
16- The application will ask you to download an additional component, click OK, and the phone will restart again
17- Now you have a rooted phone that has been linked to the Magisk application
I think this is the easiest explanation of rooting in detail
And good luck to all of you.
Click to expand...
Click to collapse
Root achieved with your method, thanks!
Is there any way to remove software installation warning boot message not recognized by samsung and bootloader unlocked message?