Database Users

[Tutorials] How To Root Lenovo K8 Note & Install TWRP(UnOfficial) + Stock Rom

Warning
Before Proceeding backup your data
TRY at OWN risk I'm NOT Responsibe if you BRICK YOUR DEVICE
Update- This method is tested & working with latest ota update NMB26.54-74
[/CENTER][/B][/SIZE][/COLOR]
IF ANYTHING GOES WRONG Download & Flash Stock ROM
Stock ROM link
SPFlashTool link
Updated Stock ROM 54-74 GDrive - here
New Oreo 27.43-20 Link
Old version Stock ROM Google Drive Link Stock Rom
nvram backup file by @peacelover94 - here
Solution For
>Tool img DL fail
Just check/tick these option in spflashtool settings & Flash stock rom again
{
"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"
}
Video Guide For Stock Rom Flashing - Youtube
How to Flash Stock Rom via Fastboot Method -
1. Open CMD by Shift + Right Click in Folder where your stock firmware .img files are.
2. Reboot to Fastboot Mode by using cmd command
adb fastboot reboot​Or
Switch off then Press & Hold Vol Up + Power button for while once menu appeared Select fastboot by using Vol Up key & confirm by pressing Vol Down Key
3. In fastboot type following command in CMD Window
For checking devices is connected in fastboot enter
fastboot devices​If Connected then proceed following commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img​ flashing system takes 10+ mins
fastboot flash data userdata.img
fastboot reboot​
Download & Install ADB from here
First Unlock your bootloader
1. First of all, enable the Developer Option
To Enable the Developer Option, Go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2. Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3. Now connect your phone to Computer using USB Cable.
4. When you connect your Phone to Computer, please wait until all the drivers get installed.
5. Open a command prompt window by pressing Shift Key + Right Mouse Click.
6. Now type the command below to reboot your phone to bootloader
adb reboot bootloader​7. If you see a pop up to allow USB Debugging on your phone, Click OK.
8. proceed to unlock the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
fastboot oem unlock​Say Yes to unlock bootloader and then it will some time format your data
9. Reboot Your Device , You will see Orange Status bla bla bla Don't panic Its normal thing now setup your device but do not restore backup yet
Flashing TWRP and ROOT
Updated Black Screen Fix TWRP - Download
Old Download TWRP
Download latest Magisk zip from here
Or
SuperSu zip from here
Flahed & Tested SuperSU v2.82 works fine but SafetyNet Fails
Sock Recovery if needed Link
1. Connect your device to PC
2. Open CMD by Shift+Right click open cmd where your TWRP_3.1.1.0.img is downloaded.
3. Reboot to Bootloader by
adb reboot bootloader​4. Now enter following command in fastboot
fastboot flash recovery TWRP_3.1.1.0.img​5. DO NOT USE fastboot reboot
Use "vol up + down + power button" to manually switch off you k8 note, otherwise twrp will restore to stock if you use fastboot reboot command.
6. After Switch Off Press & hold vol up + power button then select recovery by vol up & press vol down key to enter in recovery.
7. Now Wait for 30 Sec/ till phone vibrates, Then press power button + vol up simultaneously until you see twrp lock screen.
8. Just Cancel if It asks for Enter password to decrypt and Allow modification by swipe.
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
10. GoTo install browse and select Magisk.zip or SuperSU.zip & flash.(optional if needed install Busybox for Android NDK by osm0sis magisk module for busybox)
11. Reboot Enjoy.
Known bug in TWRP-
Battery always shows 50% in TWRP
Video Guide https://youtu.be/HrbppEWlOhs
Join Lenovo K8 Note Development Group on Telegram for direct Conversation Link
WhatsApp Group Link
Enable Wireless Display/MiraCast Magisk Module - Video
Thanks to:
@andy_zhang - for stock rom post link
and me @ysalunke007 for TWRP
NEXT CUSTOM ROM

Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?

Yes
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link

ysalunke007 said:
yes, there is stock ROM
link also provided in this post end.
btw here's direct link Stock ROM
FlashTool link
Click to expand...
Click to collapse
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.

flash via adb fastboot methoad i have succesfully flash adb method
peacelover94 said:
Big Thanks for the Tutorial. If anything happens wrong while rooting like boot loop or something worse, is there stock rom or firmware to flash or push through adb ?
Click to expand...
Click to collapse

Nice Job
Finally rooting tutorial for Lenovo K8 Note has become available.

Does SuperSu work fine?

Anas Rahman said:
Does SuperSu work fine?
Click to expand...
Click to collapse
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.

peacelover94 said:
Thank you very much. The flash tool link does not seems to work. Hope its SP flash tool you are talking about.
Click to expand...
Click to collapse
Yes it's SP flash tool but you can use adb fastboot also

ysalunke007 said:
Not tested by me but some user says in original rom post that he flashed superSU from old twrp also works fine.
Click to expand...
Click to collapse
I'll confirm it tomorrow

ysalunke007 said:
Yes it's SP flash tool but you can use adb fastboot also
Click to expand...
Click to collapse
Please tell me how to flash firmware.Im new to this device firmware flashing

lenrussel said:
Please tell me how to flash firmware.Im new to this device firmware flashing
Click to expand...
Click to collapse
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1

Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.

peacelover94 said:
Does the rom link given here unzips perfectly?
Because i saw in another thread of Lenovo K8note titled firmware, users unable to unzip due to error in system img. Also downloading from baidu needs a user id. If its possible could you or anyone else reading this upload it in some other online storage drive. Im little bit worried about getting a worse situation while rooting. Even if it goes wrong i can use the stock firmware to make it back.
Click to expand...
Click to collapse
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000

lenrussel said:
There is mega download link available too
https://forum.xda-developers.com/an...8note-original-firmware-t3679499/post73946000
Click to expand...
Click to collapse
Thanks for the reply. Anyhow got a work around for downloading from baidu using chrome extension, without account. Just wanted to confirm whether the firmware zip is working fine. If some one used it and been successful, please do tell me.

ysalunke007 said:
It's easy bro check this guide
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Fastboot Guide
http://www.stupdroid.com/2016/08/flash-stock-rom-via-fastboot-on-android.html?m=1
Click to expand...
Click to collapse
Do i have to unlock bootloader again after flashing the firmware in order to root the device?

lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.

peacelover94 said:
Yes, I think so. Anyhow there is no need to unlock oem again if you are flashing the rom via TWRP. Anyhow let someone confirm about it.
Click to expand...
Click to collapse
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also

lenrussel said:
Do i have to unlock bootloader again after flashing the firmware in order to root the device?
Click to expand...
Click to collapse
No need to unlock bootloader again if you use fastboot method to flash stock firmware , & for spflashtool I'm not sure but I think it remains unlocked

lenrussel said:
There is a error while extracting zip file of the firmware .just checked, I downloaded it from mega.i want to confirm if its the same for baidu also
Click to expand...
Click to collapse
No error while extracting firmware downloaded from baidu

this aint a phone.. Its Spawn from the darkest most vile debths of confusion!

First off i am not a noob. kinda.
the story:
I received this phone its a xt1625 prime variant (i think) already booting straight into boot loader (no system, recovery, bpmode, qmode)
just right into boot loader. So i figured it just needs flashed lets hit xda, get knowledge. it is now going on 6 months of off and on trying to flash this evil entity. this boot loader on here is like herpes, you cannot get rid of it (so i have heard). I have attempted every tutorial, downloaded every rom, twrp, firmware, etc possible to even imagine. Even tried all this in windows. ubuntu, etc. by every firmware i mean every link from here firmware.center/firmware/Motorola/Moto G4 (plus), add your own http, for every variant. and yet this boot loader remains. Even put it under a magnet from a 12' sub woofer over night. Taken the battery out for a week, overloading the chip with a car battery, nothing, the evil thing remains.
so my question is did i miss anything? also does anyone know the name and address of whomever wrote the coding for the gpt.bin,oem.img,modem,boot.img?
i'd like to have a chat with them personally.
oh and just for the record motorola will gladly replace the $159 dollar phone for $125 dollars, but have no idea how to fix it.
some of the firmware AMZ_NPJS25.93-14-7 through 14-10 will flash all the way then reboot into boot loader like nothing happened.
no blur or ota updates will flash/sideload stating that they are looking for athene and not athene_amz. yet no retail athene firmware will flash just athene_amz. absolutely no Mp firmware at all just Npjs. but only 7,8,10. which does nothing as i said before.

Can you post the get var info for this device please?
1) boot the device to bootloader
2) connect to your computer via USB
3) in the ADB terminal, type 'fastboot getvar all' without quotes and post the output here please, should be a list of device variables
Up to you if you wish to blank out the imei.

Have you unlocked your bootloader first?

motorola will not unlock the bootloader, which led me to believe its a prime.

i will do the getvar when i am home from work tonight.

and. thanks for responding

{
"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"
}

http://tinypic.com/r/qz554x/9

https://drive.google.com/file/d/1eF_el1N2Ve_APninuzEqvOlTSG1kSXCE/view?usp=drivesdk

those are getvar results.. or sad attempts at displaying them.

Thanks for the getvar log. According to the log:
The bootloader is locked (OEM_locked secure state), so no flashing any old ROMs. Also expected from devices with Amazon firmware, Motorola unlock keys won't work. G4 XT1625 as you mentioned
Unfortunately, the device is flashed with the latest NPJ25.93-14.7 US firmware for Amazon devices. Unfortunately we don't have access to that firmware (not been leaked on firmware.center or the Motorola Firmware Team on Android File Host), and because of the above locked bootloader, other firmware will be rejected as you've discovered. Therefore, you likely will have to wait for a leak of NPJ25.93-14.7 or later Amazon firmware for another try.
Can I ask what you mean by the device booting straight to bootloader - do you mean that powering on you'll only get the bootloader, and attempts to boot to recovery/start just send you back to the bootloader?

how would one go about formatting a phone like a hard drive just totally wipe it. Start new i am guessing it couldn't be that easy or every one would.

yes no attempt to start at all. everything leads back to fastboot mode.

its like the other partitions are not even there.

@Saul-66 as echo92 has previously said there is no latest stock images available to flash on your Amazon device,
but i have a little experiment to test,
you can try flashing older firmware but with latest gpt and Bootloader,
Also keep in mind if it boots, don't take OTA, it will brick again your device.
For safety, i will go steps by steps after confirmation of result.
First clean adb/fastboot folder if you have extracted any firmware in it, keep adb/fastboot files, or extract again in new folder, (Just for clean work and confusion)
Get OTA Update zip of September patch for Amazon device from here: https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-ads-moto-g4-september-t3703034
Take gpt.bin and Bootloader.img from that zip. (Delete remaining) put in adb/fastboot folder.
For now, use gpt and Bootloader commands only:
- fastboot flash partition gpt.bin
- fastboot flash bootloader bootloader.img
Tell us if those are getting flashed ?
Put screenshot of command prompt screen.
Then i will tell you next thing to go..

echo92 said:
Thanks for the getvar log. According to the log:
The bootloader is locked (OEM_locked secure state), so no flashing any old ROMs. Also expected from devices with Amazon firmware, Motorola unlock keys won't work. G4 XT1625 as you mentioned
Unfortunately, the device is flashed with the latest NPJ25.93-14.7 US firmware for Amazon devices. Unfortunately we don't have access to that firmware (not been leaked on firmware.center or the Motorola Firmware Team on Android File Host), and because of the above locked bootloader, other firmware will be rejected as you've discovered. Therefore, you likely will have to wait for a leak of NPJ25.93-14.7 or later Amazon firmware for another try.
Can I ask what you mean by the device booting straight to bootloader - do you mean that powering on you'll only get the bootloader, and attempts to boot to recovery/start just send you back to the bootloader?
Click to expand...
Click to collapse
Well if nothing else at least part of the mystery is solved. thank you for the light at the end of the tunnel!

____Mdd said:
@Saul-66 as echo92 has previously said there is no latest stock images available to flash on your Amazon device,
but i have a little experiment to test,
you can try flashing older firmware but with latest gpt and Bootloader,
Also keep in mind if it boots, don't take OTA, it will brick again your device.
For safety, i will go steps by steps after confirmation of result.
First clean adb/fastboot folder if you have extracted any firmware in it, keep adb/fastboot files, or extract again in new folder, (Just for clean work and confusion)
Get OTA Update zip of September patch for Amazon device from here: https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-ads-moto-g4-september-t3703034
Take gpt.bin and Bootloader.img from that zip. (Delete remaining) put in adb/fastboot folder.
For now, use gpt and Bootloader commands only:
- fastboot flash partition gpt.bin
- fastboot flash bootloader bootloader.img
Tell us if those are getting flashed ?
Put screenshot of command prompt screen.
Then i will tell you next thing to go..
Click to expand...
Click to collapse
There is no bootloader.img in Blur_Version.25.231.5.athene_amz.amz.en.US.zip
so i would have to probably take it out of ATHENE_AMZ_NPJ25.93-14.5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ?
Edit: they both say BL:B1.06 so should be the same in theory.

Saul-66 said:
There is no bootloader.img in Blur_Version.25.231.5.athene_amz.amz.en.US.zip
so i would have to probably take it out of ATHENE_AMZ_NPJ25.93-14.5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ?
Click to expand...
Click to collapse
In above post, you said, mystery is solved!
Then there is no need of those files right ? Or i didn't get it?
(Additionally: Bootloader wasn't updated in September patch, so it may be not included in that zip.)

____Mdd said:
In above post, you said, mystery is solved!
Then there is no need of those files right ? Or i didn't get it?
(Additionally: Bootloader wasn't updated in September patch, so it may be not included in that zip.)
Click to expand...
Click to collapse
part of the mystery is solved. tis what i said.

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"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"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

[Z00T/ZE551KL] Frustrating Bootloops -- Hardware issue?

Update: Someone suggested battery replacement. I installed my brother's phone "good" battery and it didn't fix the problem.
Having a weird situation with bootloops that worsened over time. I'm thinking it could be due to failed hardware? Maybe someone has experienced this and we can all benefit from this.
So, I kept going into random bootloops for the last 6 months. Happens during normal usage on lineage ROM AND stock ROM.
It boots into first boot screen, after ~10 seconds it blinks blue screen and reboots again.
Video:
https://youtu.be/4yCeb1J7jcs
I was sometimes able to get out of bootloop by placing phone in charger until the bootloop stops and the phone boots.
When this failed sometimes, I would go back to stock by either back2stock.zip by the great LuK1337 and sometimes from fastboot by doing the following:
While in fastboot I would boot into TWRP from adb >> wipe everything then flash stockrecovery.img >> boot into stock recovery >> while in stock recovery I flash oldest stockfirmware zip from there >> perform factory reset from within recovery then reboot.
It would always boot successfully.
Now my bootloop has worsened and no method is working out for me.
Is my phone defective? Any idea what part would be defective?
Note that it suffered from excessive heat in its recent months.
I can get into fastboot/TWRP/stockrecovery. But that's it.
Bootloader is apparently still unlocked:
{
"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"
}
Thanks a lot.

Have you flash back to original Asus image & slowly up the firmware versions?
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that, you can them use custom roms to your pleasing.
Good place to start.
https://www.asus.com/Phone/ZenFone_Selfie_ZD551KL/HelpDesk_BIOS/

TroyBar said:
Have you flash back to original Asus image & slowly up the firmware versions?
Asus firmware updates hardware issues...after that you can them using custom roms to your pleasing.
Good place to start.
https://www.asus.com/Phone/ZenFone_Selfie_ZD551KL/HelpDesk_BIOS/
Click to expand...
Click to collapse
Which version should I install? I've tried it before and it didn't work.
Also should I install it via TWRP or via Stock Recovery?
Thanks very much!

Install latest TWRP
https://dl.twrp.me/Z00T/
A good start is follow the link of the back2stock.zip you posted, follow the instructions, zip it back up to back2stock.zip with the files mention & then flash it in TWRP.
https://asus.kremowka.xyz/categories/show/2
Zenfone 2 Selfie — ZD551KL
This will rule out any issues you have, as you will have the latest firmware from Asus.

TroyBar said:
Install latest TWRP
https://dl.twrp.me/Z00T/
A good start is follow the link of the back2stock.zip you posted, follow the instructions, zip it back up to back2stock.zip with the files mention & then flash it in TWRP.
Once done, check if your bootloader is still unlock if so you need to find out how to lock it to install Asus official firmware.
Continue the next firmware version above Version WW-21.40.1220.2056 2017/03/16 (from the posted link) located at above Asus website.
This will rule out any issues you have as you have the latest firmware from Asus.
Click to expand...
Click to collapse
The ROM you mentioned does not exist in the link you shared, maybe it's a regional effected page.
Screen of the webpage:
https://i.imgur.com/3WaSs5G.png
However, I downloaded the latest available ROM [Version WW_21.40.0.2214] from November 2017,,
I applied the back2stock steps and flashed via TWRP successfully.
After that I checked my bootloader via fastboot and it was still unlocked.
I could not re-lock it using any of the following commands:
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Always gives me a "FAILED" message.
Also found this thread about "relocking" the bootloader:
https://forum.xda-developers.com/ze...guide-ze500kl-bootloader-unlock-lock-t3655340
I flashed "relock_bootloader.zip" via TWRP and it didn't lock bootloader.
Then I thought maybe it will would work if I flashed RAW rom via Asus Flasher [from same thread].. So I googled for a ZE551KL RAW firmware and found it here:
https://drive.google.com/file/d/0B43Ue6xY9MmdRVdDRWtSSVNUdDg/view
Tried flashing it via the Asus Flash Tool and got an error "Phone is protected". See screenshot:
What do you suggest we should try next?
The phone is still having the same bootloop.

So after a little digging, it appears that my Bootloader is *NOT* unlocked.
But how come it gives an *unlocked* result for the command "fastboot oem device-info" ???
Is it possible to have a "locked" Bootloader in reality and showing otherwise in fastboot checking command??
To add, I can't install TWRP from fastboot using:
fastboot flash recovery twrp.img
I can boot the img, then install it as recovery from within TWRP.
Is this also "locked" bootloader behavior?
So many questions.

Sorry was tired last night, not the below version as it is for ZE551KL
Version WW-21.40.1220.2056 2017/03/16
You need the one(s) for Zenfone 2 Selfie — ZD551KL
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that, you can them use custom roms to your pleasing.

TroyBar said:
Sorry was tired last night, not the below version as it is for ZE551KL
Version WW-21.40.1220.2056 2017/03/16
You need the one(s) for Zenfone 2 Selfie — ZD551KL
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that you can them using custom roms to your pleasing.
Click to expand...
Click to collapse
So, I should install latest ZD551KL stock firmware on my ZE551KL ? Is that correct?
Could you please message me on Telegram? I have the same username.

shmaiz3r said:
So, I should install latest ZD551KL stock firmware on my ZE551KL ? Is that correct?
Could you please message me on Telegram? I have the same username.
Click to expand...
Click to collapse
Sorry is your phone ZD551KL (ZOOT) or ZE551KL, choose the one that is yours, mine is ZD551KL (ZOOT).

I have tried the above back2stock method, placed the files inside & also outside the meta-inf folder, re-zipped it up to back2stock.zip (2 separated folder zips (one for inside & other outside)) & flashed it (inside zip errors out, will outside zip works with update system, but is stuck there.
Another possibility below for an unlock bootloader, but requires you to have the stock OS installed, this has not work for me with a custom rom. I will need to find my ZD551KL (ZOOT) stock OS to try.
https://www.asus.com/support/FAQ/1009748?SearchKey=ota/

TroyBar said:
I have tried the above back2stock method, placed the files inside & also outside the meta-inf folder, re-zipped it up to back2stock.zip (2 separated folder zips (one for inside & other outside)) & flashed it (inside zip errors out, will outside zip works with update system, but is stuck there.
Another possibility below for an unlock bootloader, but requires you to have the stock OS installed, this has not work for me with a custom rom. I will need to find my ZD551KL (ZOOT) stock OS to try.
https://www.asus.com/support/FAQ/1009748?SearchKey=ota/
Click to expand...
Click to collapse
I tried flashing back2stock with both the New stock ROM and the Old stock ROM. No dice.
Thanks for your time.

[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!

*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. Screenshots and MSM logs will be best.
!!! I have officially retired my 8T, and can no longer provide additional support on this device !!!​
It's finally here! A MSM tool that will convert your T-Mobile OnePlus8T+5G to EU KB05BA. From here you can local upgrade to any OOS flavor you want. This gives you Local Upgrade option, faster upgrades, open betas, dual SIM, and more! In fact, after conversion, you can unlock the bootloader without the unlock token (still need to be SIM unlocked, but in case you don't want to wait for the unlock token or if OnePlus's website is broken)!
If you are still SIM locked, you lose the Unlock app for when your device becomes unlocked, it's only available in the stock TMO ROM. If you want to go back to TMO ROM at any point, flash back with the TMO MSM: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/
Steps:
Download the MSM Conversion package:
AFH
MD5: 5ddb543c8a5e7587e0b2ad24d2025e77
Run MsmDownloadTool V4.0.exe (Windows 7 users may need to run the win7 version included)
Select User type: "Other" and press Next.
Press "Start". Don't mess with the default settings.
Put your phone in EDL mode.
Code:
adb reboot edl
or completely turn off your device, hold vol up + vol down and plug in the cable.
Wait about 5 minutes while it works.
Done! If you keep the bootloader locked and run it stock, the About Phone page will be missing some fields.
If you run into any MSM tool issues, most likely you have a driver problem. See the FAQ in @Some_Random_Username's post
Instructions to Bootloader Unlock a SIM locked device:
In ADB:
Code:
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
Reboot
Go to dev settings and enable OEM Unlock
Reboot to bootloader
Code:
fastboot oem unlock
No unlock.bin needed
Old fastboot method
*** Know how to use the MSMTool, Don't start before figuring it out.
*** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH THE STEPS DESCRIBED IN THIS GUIDE
* The steps in this guide will convert your TMO KB2007/KB05CB to Global 11.0.5.6.KB05AA, or EU 11.0.3.4.KB05BA
* NR and LTE bands are flashed in nvRAM, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
* Instructions are the same as running any other MSM unbrick tool.
* You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. See manual instructions towards the end.
* Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools, https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445. DO NOT USE MINIMAL ADB, it has not been updated for years and will cause a crash where you'll need to MSM back to stock.
* Make sure your drivers are up to date. This guide will not walk you through setting up platform tools or updating drivers. When encountering fastboot issues, make sure to include the output of fastboot --version in your post.
* Do not ask for OTAs, MSMs, or anything else not related to the steps described herein. There are plenty of threads around for those.
* This guide does not pertain to Cyberpunk conversion. See other threads.
* This guide converts you to an older firmware so you can take a FULL OTA via Oxygen Updater. Do not skip this step if you want a stable build.
Steps to convert your device to Global or EU
As simple as possible:
You need your device bootloader and SIM unlocked. Follow the instructions here (It says 6T, but applies to all OP devices): https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-(t-mobile-edition)
Download and unzip the conversion package:
Global 11.0.5.6
EU 11.0.3.4
Boot to fastbootd.
From adb:
Code:
adb reboot fastboot
From fastboot/bootloader:
Code:
fastboot reboot fastboot
If you are having trouble booting into fastbootd, and have a FC number at the bottom of the bootloader screen, you'll need to MSM to factory first.
[*]You should be at a screen that says "fastbootd" on top. DO NOT CONTINUE IF YOU ARE NOT HERE. SEE HIDDEN FOR AN EXAMPLE.
{
"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"
}
Execute "flash_all.bat" for Windows, or "flash_all.sh" for Linux, from the unzipped directory from step 2 as cwd.
Optional: Flash magisk'd boot
Code:
fastboot flash boot boot_magisk_patched.img
Reboot into recovery, and wipe everything.
Once fully booted, download Oxygen Updater, set your device to OnePlus 8T of your regional choice and local upgrade to the latest OTA of your regional choice.
Optional: You can re-lock your bootloader at thois point. DO NOT TRY before the full OTA upgrade above, or you'll have to MSM.
Manually:
Unlock bootloader
Download the full OTA of your choosing
Extract the OTA payload with https://github.com/vm03/payload_dumper or https://androidfilehost.com/?fid=818070582850510260
With the output of the payload as your cwd, execute:
Code:
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Replace boot.img with your magisk'd boot if desired
Reboot to recovery and wipe everything
Troubleshooting
Error: "remote: no such file or directory"
You are not in the correct cwd. Fastboot needs to be accessible from the same directory as the .img files, so fix your PATH or make a copy fastboot.exe in the same directory as the .img files
Error: "remote: Flashing is not allowed for Critical Partitions"
You are not in fastbootd. Check step 4.
Error: "Invalid sparse file format at header magic"
Ignore this message, not an error
Special thanks to:
@jwarrior319 for the initial linux script
@cammykool and @awr128 for helping debug some of the steps and clarifying pain points
@radiohead7778580 for a better Global conversion
Fixing the About Phone page
These steps are optional, and will fix the "About Phone" page. There are no performance differences.
You need to rooted with Magisk
Download the fix: here
In the Modules page in MagiskManager, Install the downloaded zip file via "Install from storage"
Reboot, the About Phone page is filled out.
Issues so far (please post if you run into more):
In OOS11, "About phone" page does not work properly.
Use the magisk module above to fix it.
In OOS12, Dual SIM is not supported.
A11 based A12 ROMs support Dual SIM after conversion, use my enable_dsds module.
Unlocked bootloader without unlock_token must be done while in OOS11, as OOS12+ ABL will check that a token is needed

craznazn said:
*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Know how to use the MSMTool, in case you do soft brick anything
*** DO NOT ATTEMPT THIS IF YOU ARE EASILY OFFENDED WHEN THINGS DON'T WORK PERFECTLY
* I've done this with the EU KB05BA.
* You can patched the boot.img prior to doing all this, to make things easier if you want root in your target build.
* This method should work for other builds, if you can find a full OTA of KB05AA (for Intl/Global)
Download the EU Full OTA. Or use another FULL OTA if you have it:
11.0.1.2
11.0.3.4
Extract the payload.bin, and dump the payload using Payload Dumper
The "About Phone" screen seems to be broken: Processor, Camera, and Screen all show "None"
5G
AOD
Fingerprint sensor
Click to expand...
Click to collapse
Nice! Thank you. So aside from the "About Phone" info not displaying correctly, am I understanding everything else appears to be working? My apologies if I missed something, reading this from mobile on XDA Labs.
Edit: I am SIM unlocked & I do have my bootloader unlock token so I should be good (just haven't actually unlocked my bootloader YET). I think you may want to mention those requirements in the OP, hopefully to help avoid unnecessary questions. It seems obvious, but you know... it's the internet.
Sent from my OnePlus 8T using XDA Labs

stmims1124 said:
Nice! Thank you. So aside from the "About Phone" info not displaying correctly, am I understanding everything else appears to be working? My apologies if I missed something, reading this from mobile on XDA Labs.
Sent from my OnePlus 8T using XDA Labs
Click to expand...
Click to collapse
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.

craznazn said:
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.
Click to expand...
Click to collapse
Perhaps an update to the very latest Magisk Canary & Magisk manager might help? Canary gets updated often, and I ran into that a few times on my 7 Pro. It's also entirely possible it may take extra work...I don't know, but I hope not!
Sent from my OnePlus 8T using XDA Labs
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
craznazn said:
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.
Click to expand...
Click to collapse
Oh, also I'm sure this is pretty obvious but I've also made this mistake... Forgot to turn on Magisk Hide and then scratch my head wondering why it won't pass.
Sent from my OnePlus 8T using XDA Labs

stmims1124 said:
Oh, also I'm sure this is pretty obvious but I've also made this mistake... Forgot to turn on Magisk Hide and then scratch my head wondering why it won't pass.
Click to expand...
Click to collapse
LOL that was it... feels like a dummy man

craznazn said:
LOL that was it... feels like a dummy man
Click to expand...
Click to collapse
Dude, I've doing this s**t since 2010 with the HTC Evo and still do that type of s**t all the damn time. I just get comfortable (cocky is more accurate), like, "oh I know what to do, I can do this in my sleep"...and then yeah, scratching my head, wiping my phone or some dumb s**t because I didn't do the easy trouble shooting stuff.
Sent from my OnePlus 8T using XDA Labs

SafetyNet is fine if you do the global Magisk Hide

So if I opt to not root. Will I just get OTAs like the normal global variant? I assume so. But just curious.

craznazn said:
*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Know how to use the MSMTool, in case you do soft brick anything
*** DO NOT ATTEMPT THIS IF YOU ARE EASILY OFFENDED WHEN THINGS DON'T WORK PERFECTLY
* I've done this with the EU KB05BA.
* You can patched the boot.img prior to doing all this, to make things easier if you want root in your target build.
* This method should work for other builds, if you can find a full OTA of KB05AA (for Intl/Global)
You need your device bootloader unlocked. Follow instrustions here (It says 6T, but applies to all OP devices): https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-edition)
Download the EU Full OTA. Or use another FULL OTA if you have it:
11.0.1.2
11.0.2.3
11.0.3.4
Also check this thread
Extract the payload.bin, and dump the payload using Payload Dumper
Execute the following starting from ADB and in the payload output directory. You can start at Fastboot if you are already there:
I haven't used it much yet, but here's what I know so far:
Issues (please post if you run into more):
The "About Phone" screen seems to be broken: Processor, Camera, and Screen all show "None"
What appears to work:
5G
Dual SIM, though I can't test without a proper 2-SIM tray
AOD
Fingerprint sensor
Click to expand...
Click to collapse
If you have the dual SIM tray from the the 7T it will work in the 8T, doesn't fit perfectly flat to the body (if you have a case, probably wouldn't he able to tell) but it will read the sim card 1, I can't confirm it will read sim 2, maybe someone could try, or see if an 8 sim tray would work.

awr128 said:
If you have the dual SIM tray from the the 7T it will work in the 8T, doesn't fit perfectly flat to the body (if you have a case, probably wouldn't he able to tell) but it will read the sim card 1, I can't confirm it will read sim 2, maybe someone could try, or see if an 8 sim tray would work.
Click to expand...
Click to collapse
The dual sim tray made for the 8t can be bought on ebay
Sent from my OnePlus KB2007 using XDA Labs

jwarrior319 said:
The dual sim tray made for the 8t can be bought on ebay
Click to expand...
Click to collapse
Nice, I looked for one a few days ago and couldn't find any.

LLStarks said:
SafetyNet is fine if you do the global Magisk Hide
Click to expand...
Click to collapse
Whats going on buddy, nice to see you! Broke down and bought the 8t as well I see

I am successfully on the European. I extracted the payload before but I wasn't flashing correctly in fastboot, had everything working except the phone.
Now all good..
Thing to test is to see if I lose data like I did randomly with the 8.

cammykool said:
So if I opt to not root. Will I just get OTAs like the normal global variant? I assume so. But just curious.
Click to expand...
Click to collapse
Not sure yet, it might not but the local upgrade option is now available, at least in the EU version. I tested that to install the EU version on the second slot and it worked fine.

After we follow the guide can we just do the local upgrade option as normal

jwarrior319 said:
The dual sim tray made for the 8t can be bought on ebay
Sent from my OnePlus KB2007 using XDA Labs
Click to expand...
Click to collapse
I couldn't find one, but it looks like the 8 tray may fit so I got one of those. Even if it doesn't work, it's not that expensive until I can find a dual-tray 8T

cammykool said:
After we follow the guide can we just do the local upgrade option as normal
Click to expand...
Click to collapse
The option is there.

This doesn't seem as simple, I think I'll wait for a easier way using the MSM Tool method to convert like it was with the other T-Mobile OP devices

SmileBigNow said:
This doesn't seem as simple, I think I'll wait for a easier way using the MSM Tool method to convert like it was with the other T-Mobile OP devices
Click to expand...
Click to collapse
If ur BL is unlocked u shld be able to just dl oxygen updater, select whichever variant u want to convert to, dl the local upgrade apk and after dl'ing the update to internal go into an activity launcher and launch the local upgrade apk and install. Then once converted extract ur boot img from the OTA zip and patch magisk if u want root u don't even have to be rooted to covert

Shooter7889 said:
If ur BL is unlocked u shld be able to just dl oxygen updater, select whichever variant u want to convert to, dl the local upgrade apk and after dl'ing the update to internal go into an activity launcher and launch the local upgrade apk and install. Then once converted extract ur boot img from the OTA zip and patch magisk if u want root u don't even have to be rooted to covert
Click to expand...
Click to collapse
if this works ill do this, BUt currently bsdiff4 is kicking my ass and refuses to install