Hi Guys,
I was running stock CM12S version: '12.0-YNG1TAS17L' which i got with the last OTA update. I believe it is the newest CM12S update.
The phone had never been unlocked or rooted previously, 100% stock from new.
I decided I wanted to unlock the Bootloader/install TWRP & Root.
I followed the One Plus One 6.0 Toolkit.
I have heard time and time again that once you unlock your Bootloader that your phone will wipe your current OS, However, this did not happen to me.
After unlocking the Bootloader and installing TWRP I rebooted and I got the Android is optimizing screen, my phone booted into my normal OS, nothing was wiped. Exactly how I had it in stock.
I assumed I screwed something up and did not unlock the Bootloader but I can confirm that running the "fastboot oem device-info" command I get the following:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.011s
I'm a little confused, Is this a new feature in CM12S? Where you don't need to wipe to unlock bootloader/Install Recovery & Root?
Right now I have the message above showing the bootloader unlocked, SuperSU installed and working (Also checked with Root Checker, showing root access)& TWRP is working 100%
Appreciate any help.
Cheers
millzyy said:
Hi Guys,
I was running stock CM12S version: '12.0-YNG1TAS17L' which i got with the last OTA update. I believe it is the newest CM12S update.
The phone had never been unlocked or rooted previously, 100% stock from new.
I decided I wanted to unlock the Bootloader/install TWRP & Root.
I followed the One Plus One 6.0 Toolkit.
I have heard time and time again that once you unlock your Bootloader that your phone will wipe your current OS, However, this did not happen to me.
After unlocking the Bootloader and installing TWRP I rebooted and I got the Android is optimizing screen, my phone booted into my normal OS, nothing was wiped. Exactly how I had it in stock.
I assumed I screwed something up and did not unlock the Bootloader but I can confirm that running the "fastboot oem device-info" command I get the following:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.011s
I'm a little confused, Is this a new feature in CM12S? Where you don't need to wipe to unlock bootloader/Install Recovery & Root?
Right now I have the message above showing the bootloader unlocked, SuperSU installed and working (Also checked with Root Checker, showing root access)& TWRP is working 100%
Appreciate any help.
Cheers
Click to expand...
Click to collapse
Okay, so what is the issue? Because everything is working as I see. Unlocking the bootloader never wipes your OS, maybe does a factory reset (on Nexus series) or removes proprietary software (Xperia line). When I was unlocking HTC devices and OPO the OS, DATA remained untouched.
davebugyi said:
Okay, so what is the issue? Because everything is working as I see. Unlocking the bootloader never wipes your OS, maybe does a factory reset (on Nexus series) or removes proprietary software (Xperia line). When I was unlocking HTC devices and OPO the OS, DATA remained untouched.
Click to expand...
Click to collapse
No issue, im interested to know why it didn't perform a factory wipe, that's all.
millzyy said:
No issue, im interested to know why it didn't perform a factory wipe, that's all.
Click to expand...
Click to collapse
So it didn't wipe any user data? Like apps and the internal storage? It's never wiped the system but it usually does wipe user data. It's possible that the bootloader was already unlocked, did you purchase it directly from OnePlus?
XDA Moderator
Transmitted via Bacon
Yeah, didn't wipe any user data at all.
It's the chinese version purchased from a wholesaler who flashed cm11 33R (it had color os)
Good point, maybe it was already unlocked.
Thanks for your reply mate.
millzyy said:
Yeah, didn't wipe any user data at all.
It's the chinese version purchased from a wholesaler who flashed cm11 33R (it had color os)
Good point, maybe it was already unlocked.
Thanks for your reply mate.
Click to expand...
Click to collapse
It was definitely already unlocked then. The only way they can get CM onto the Chinese version is by unlocking the bootloader.
Related
In a stupid attempt to try to root my Moto G, I followed the instructions here up to step 6, rebooted, and was greeted in fastboot with a "failed to validate boot image" message. I have tried flashing a new boot image but I get a remote failure saying "Preflash validation failed", presumably because the phone's bootloader is locked.
The phone is from Cricket/AIO/ATT or whatever and does NOT qualify for bootloader unlocking.
Is there any way to fix this, or have I bricked my phone?
If you still have a warranty, USE IT. (Your warranty isnt void until the bootloader is unlocked, and if the warranty period hasnt expired yet)
1. Try to enter stock recovery and Factory Reset the phone.
2. Try to do a tethered root and then try unlocking the bootloader. (This is probally why the root failed) (If it does not qualify, try using sunshine: http://theroot.ninja/)
3. SKIP THIS STEP IF YOU DID AN OTA UPDATE TO 4.4.4 - watch this video: http://youtu.be/laU6NQ0LxR0
4. Try to enter stock recovery and Factory Reset the phone.
5. Flash a custom recovery such as ClockWorkMod
6. Try flashing stock rom with a flashable zip.
7. Try flashing a custom rom such as cyanogenmod
DISCLAIMER: YOU THE USER ARE TO TAKE FULL RESPONSIBILITY FOR ANY OF YOUR ACTIONS. I AM NOT TO BLAME IF YOUR DEVICE DIES.
skyguy126 said:
If you still have a warranty, USE IT. (Your warranty isnt void until the bootloader is unlocked, and if the warranty period hasnt expired yet)
1. Try to enter stock recovery and Factory Reset the phone.
2. Try to do a tethered root and then try unlocking the bootloader. (This is probally why the root failed) (If it does not qualify, try using sunshine)
3. SKIP THIS STEP IF YOU DID AN OTA UPDATE TO 4.4.4 - watch this video
4. Try to enter stock recovery and Factory Reset the phone.
5. Flash a custom recovery such as ClockWorkMod
6. Try flashing stock rom with a flashable zip.
7. Try flashing a custom rom such as cyanogenmod
DISCLAIMER: YOU THE USER ARE TO TAKE FULL RESPONSIBILITY FOR ANY OF YOUR ACTIONS. I AM NOT TO BLAME IF YOUR DEVICE DIES.
Click to expand...
Click to collapse
Thanks for the reply. Will definitely look into warranty if all else fails, I've only had the device for about a month.
The stock recovery factory reset doesn't fix the boot image. It successfully wipes everything but it still reboots right back to fastboot.
I cannot unlock the bootloader as it has been locked by the carrier and does not qualify for bootloader unlocking according to Motorola, and it looks like sunshine is a paid service, which even if I paid for I would have to be able to get into the phone to install the apk anyway.
It fails flashing any boot images or custom recoveries with a "(bootloader) Preflash validation failed" error.
To do any flashing you need an unlocked bootloader. Sunshine is a bootloader unlocking utility, its a paid app for a reason, the amount of time the devs put into making an app like that requires payment. You do not need root for installing sunshine as the app will root for you. You need to go to settings > security > and check install from unknown sources. Then download the app and run it. You can just download sunshine to check if your bootloader can be unlocked as at first it will not do anything but run a sieres of compatability tests to see if the bootloader is unlockable. Only then will it ask you for payment. But I highly suggest sending it into warranty and then try the rooting process again, but this time with an unlocked bootloader.
skyguy126 said:
To do any flashing you need an unlocked bootloader. Sunshine is a bootloader unlocking utility, its a paid app for a reason, the amount of time the devs put into making an app like that requires payment. You do not need root for installing sunshine as the app will root for you. You need to go to settings > security > and check install from unknown sources. Then download the app and run it. You can just download sunshine to check if your bootloader can be unlocked as at first it will not do anything but run a sieres of compatability tests to see if the bootloader is unlockable. Only then will it ask you for payment. But I highly suggest sending it into warranty and then try the rooting process again, but this time with an unlocked bootloader.
Click to expand...
Click to collapse
Yes, that's all fine and dandy, but like I said I'm stuck in fastboot so I wouldn't be able to use it anyway. At this point I don't even care about rooting, I'd just like to get my device working.
You do not need an unlocked bootloader to fastboot flash a Motorola firmware image.
You will get a 'Preflash Validation' error when flashing a firmware image older than 4.4.4.
Can you provide more information about your phone. Is it the LTE version? Do you know the exact model number?
lost101 said:
You do not need an unlocked bootloader to fastboot flash a Motorola firmware image.
You will get a 'Preflash Validation' error when flashing a firmware image older than 4.4.4.
Can you provide more information about your phone. Is it the LTE version? Do you know the exact model number?
Click to expand...
Click to collapse
It's an XT1032 and was running on 4.4.2. Maybe I tried with the wrong stock firmware, I used "AIO_XT1032_4.4.2-KXB20.9-1.10-1.9_CFC_1FF.xml", which I found in this thread. The version matched the info I found using "getvar all" in fastboot so I figured it was the correct one. The http://sbf.droid-developers.org site seems to be down at the moment so I guess I can try a few more when it comes back up.
That would appear to be the correct firmware. However it would also appear your bootloader is preventing you from flashing it. As I said, the best solution would be to flash the 4.4.4 firmware image for your carrier, however there isn't one at this time.
You can always try flashing the XT1032 EU Retail 4.4.4 firmware image. It doesn't matter where you are in the world, it will should work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
Hello dear forum users.
I am new to Huawei but not to Android, having had (and rooted) devices since Eclair.
Yesterday, (Oct. 1st) I received my TL10 (European version). Looking through these forums I was excited to see that Lollipop had just been made officially available, so before doing anything else I upgraded. As I was on B125SP02 I had to first install B130, then B324.
Now, here's the thing. The rooting guides for Lollipop on these forums are for old stock ROMs and I don't want to risk bricking my new baby. I tried Kingroot, but it failed, so does anyone know if one of the rooting methods here will root B324?
Thanks in advance.
Install twrp recovery ..
Sent from my GT-P7320 using Tapatalk
Got it to work
paulopais said:
Install twrp recovery ..
Sent from my GT-P7320 using Tapatalk
Click to expand...
Click to collapse
Thanks.
I had to unlock first, which involved various running back and forth to find the unlock page on the HUAWEI site, then finding SN, IMEI and product ID. But I got there in the end.
:cyclops:
nope
afzal_b said:
Thanks.
I had to unlock first, which involved various running back and forth to find the unlock page on the HUAWEI site, then finding SN, IMEI and product ID. But I got there in the end.
:cyclops:
Click to expand...
Click to collapse
Well, I spoke too soon. TWRP detects that the phone isn't rooted and proposes swipe to root. I did it and there is a small screen that flashed too fast to read, then the phone reboots, but unfortunately with out being rooted.
afzal_b said:
Well, I spoke too soon. TWRP detects that the phone isn't rooted and proposes swipe to root. I did it and there is a small screen that flashed too fast to read, then the phone reboots, but unfortunately with out being rooted.
Click to expand...
Click to collapse
you have twrp installed ? if so, download https://download.chainfire.eu/supersu and install zip over twrp and its done
how did you unlock bootloader? the online tool need huawei id to register with me phone number and my country is not listed.
By email
Sent from my GT-P7320 using Tapatalk
Thanks again
Thanks - worked
You don't have to login with phone number
apopet26 said:
how did you unlock bootloader? the online tool need huawei id to register with me phone number and my country is not listed.
Click to expand...
Click to collapse
You can also login using with a Facebook login, which is how I did it.
afzal_b said:
You can also login using with a Facebook login, which is how I did it.
Click to expand...
Click to collapse
Yes I discovered that too after hours of struggling. Now I'm rooted and flashed back stock recovery. First time in these things and I feel proud I didn't brick anything [emoji13] After days of reading everything looks super clear I can root anything now [emoji41]
Still waiting for working xposed version though...
Send from Mate 7 using tapatalk
I got the Bootloader Unlock code and I unlocked my Mate 7 using the command "Fastboot oem unlock <code>" and it showed "done". I repeated the command and it showed "remote: already user unlocked", which convinces me that the bootloader is finally unlocked.
However, when I tried to flash TWRP recovery using "fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img", I still get the same error "FAILED (remote: image verification error)". I have checked the XDA pages and the TWRP version seems to be right, as I used the link (https://basketbuild.com/devs/asyan4ik/hwmt7_l09) given on this post only.
Sequence as follows:
Fastboot Flash Recovery twrp_2.8.7.0_mate7_5.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (12644 KB)...
OKAY [ 1.384s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.404s
Is there a separate TWRP version for MT7-TL10 version? If yes, can someone provide the link, please?
This is very frustrating because it's a great phone and not being able to root is very limiting!
Xposed runs but not all modules as the Huawei theming messes with it.
As for TWRP, I don't like it and only use CWM which is what I have in my Mate7.
I tried various ways including moving back to KitKat. That landed me on a bricked device.
I then went to the website of Huawei to download the rescue package. After lot of struggle, I could get the phone to boot.
The Problem: I have been thrown off to a Chinese KitKat ROM (See attached) and no matter what I do, I am unable to flash an official International Channel ROM. The flash fails every time.
I am looking for a way to move back to either KitKat 4.4.2 or 5.1.1 B324 version of Android 5.1.1 (MT7 TL10 Model). If there is no root for 5.1.1, I would prefer to stick to the latest KitKat ROM with root.
Help.
Back to Stock Lollipop with the help of @acbka
Now need to root it with a locked bootloader. No way to unlock bootloader - even though 'Phone Unlocked' is shown on bootloader screen, yet I can't flash custom recovery through Fastboot.
Hi
My X2 GEM-702L bootloader us unlocked. I verified by "fastboot oem get-bootinfo" already.
I prefer to root it using the customer recovery method as I'd prior experience using this method on other Android smartphone.
However at the point of flashing the custom recovery I encountered an error:
C:> fastboot oem get-bootinfo
(bootloader) unlocked
C:> fastboot flash recovery twrp_recovery.img
sending recovery (2672 KB)......
OKAY [ 0.609s]
writing recovery
FAILED (remote: Command not allowed)
Where did I go wrong ?
kpcheang2 said:
Hi
My X2 GEM-702L bootloader us unlocked. I verified by "fastboot oem get-bootinfo" already.
I prefer to root it using the customer recovery method as I'd prior experience using this method on other Android smartphone.
However at the point of flashing the custom recovery I encountered an error:
C:> fastboot oem get-bootinfo
(bootloader) unlocked
C:> fastboot flash recovery twrp_recovery.img
sending recovery (2672 KB)......
OKAY [ 0.609s]
writing recovery
FAILED (remote: Command not allowed)
Where did I go wrong ?
Click to expand...
Click to collapse
Try renaming the twrp to recovery. img. If not download a newer version of Android Tools.
Ok after trying for several hours on various updated drivers, adb tools etc still no success.
I suspected the X2 though stated as "unlocked" it may not be fully unlocked properly for whatever reason.
So I did the "fastboot oem unlock xxxxxxxxxxxxxxxx" one more time and after this I mamanged to flash the custome recovery.
Success finally and I've custom recovery now running ! Thanks.
kpcheang2 said:
Ok after trying for several hours on various updated drivers, adb tools etc still no success.
I suspected the X2 though stated as "unlocked" it may not be fully unlocked properly for whatever reason.
So I did the "fastboot oem unlock xxxxxxxxxxxxxxxx" one more time and after this I mamanged to flash the custome recovery.
Success finally and I've custom recovery now running ! Thanks.
Click to expand...
Click to collapse
You know what's funny? When I got my second X2 and went into the Bootloader it said it was unlocked. After I did a factory reset on it, it then said it was locked. I don't know how that could be. Then I used the DC Unlocker program that you mentioned and it unlocked perfectly. I'm glad you got TWRP installed. So TWRP works right? Let me know if you flash SuperSU in TWRP and you have root. Then I'll update my thread to include your version of X2.
Yes....I managed to flash the SuperSU (Beta-v2.49) using the "KangVIP" version of the TWRP.
Now my X2-GEM702L rooted and I can uninstall certain system bloatware and do full backups using the Titanium Pro.
The only thing is to await the 5.11 Android EMUI 3.1 update which is not available yet.
kpcheang2 said:
Yes....I managed to flash the SuperSU (Beta-v2.49) using the "KangVIP" version of the TWRP.
Now my X2-GEM702L rooted and I can uninstall certain system bloatware and do full backups using the Titanium Pro.
The only thing is to await the 5.11 Android EMUI 3.1 update which is not available yet.
Click to expand...
Click to collapse
Thanks for the info! Did you try flashing the 703L stock 5.1.1 ROM on your 702L? I'm curious to see if it works.
Flash 703L stock 5.11 ROM ? No haven't tried it.
I wonder whether it will work because the only difference I could see between 702L and 703L is the former has 4 more LTE bands. The other specs looks similar to me.
kpcheang2 said:
Flash 703L stock 5.11 ROM ? No haven't tried it.
I wonder whether it will work because the only difference I could see between 702L and 703L is the former has 4 more LTE bands. The other specs looks similar to me.
Click to expand...
Click to collapse
Yeah I know. If I had a 702L I would try it. Everyone has been asking on here if it would work.
This is a newest MIUI 9 China Beta "s TZ &Modem
Baseband:BO.2.6.c1.2-0818_1948_87b78d2
Link:https://yadi.sk/d/wdmLsruk3MSQJr
Flashable ZIP File
Please Use TWRP
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: DO NOT flash this on official Lineage with Lollipop bootloader, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot which is also pretty useless, since your bootloader is locked
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Code:
fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (40704 KB)...
OKAY [ 1.343s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.362s
PeterMarkoff said:
more info about updates?
is it safe, nothing to do with root/bootloader?
EDIT: do not flash this on official Lineage, you will end up bootlooping on start, unable to get even into recovery after restart, only possible to get into fastboot
any idea how to recover back without going through flashing all the ROM and everything? is it possible to flash just firmware through fastboot?
EDIT 2: wanted to flash at least recovery in case it was overwritten, but I am getting
Click to expand...
Click to collapse
kindly type, fastboot oem device-info on fastboot mode with phone pluged in,hope it didnt lock your bootloader.
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
PeterMarkoff said:
yes, that piece of **** locked my lollipop bootloader, had to flash fastboot miui rom to unlock it and lost my data
Click to expand...
Click to collapse
Have you unlocked your phone officially?
Because i flash this too and had no problem at all.
?
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
PeterMarkoff said:
unofficially, but that never caused problems with previous updates, I guess this firmware us somehow compatible only with Nougat bootloader and locks lollipop bootloader
Click to expand...
Click to collapse
YES,This is a Nougat Bootloader,you must unlock bootloader in official tools after you install this file in twrp
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
buktore said:
Put on a BIG ****ing warning about it being incompatible with lollipop bootloader..
And I was like "huh, my phone very smooth today, maybe I'll do a backup and try that new firmware out, shouldn't be a big deal, I've done it before np" — now it's ****ed....
(Yes I unlock the bootloader, but if I go back to marchmellow it's constant restart+bootloop.
Click to expand...
Click to collapse
****ing ask before do something if you're not so sure about it.
Has anyone noticed any improvement with the new radio?
Hello. Has anyone got a link to the latest firmware available for a MI4C. I'm not after the official ROM, just firmware workable with ROMs. I think the last update I done was through andropax link https://androidfilehost.com/?w=files&flid=155424 is there a way I can also find out which firmware I have installed I forgot.
Is this the latest > https://androidfilehost.com/?fid=890278863836288705
fw_libra_miui_MI4c_V9.5.2.0.NXKCNFA_81f363e363_7.0
& will it run dev ROMs?
This is not a method to relock Bootloader
I see many threads opened on the same topic and closed!
I hope those threads fixed things for you guys.
My situation is Different!
This is not a duplicate Thread.
I just unlocked bootloader on my Zenfone 3 [ZE552KL 4GB 5.5' Model]
After flashing TWRP and using ROMs based on 9.0, I found that we cannot use
UPI [Payment Interface in India (GooglePay)] in the device!
I tried many methods to flash the stock ROM and lock the Boot loader again, But I cant lock it anyway!
I found a thread by @Saktis_Impreza on this topic but I get:
adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.014s
I would like to share an idea which helped me Regain Warranty after rooting
and flashing over several times on the device ZUK Z2 Plus.
I'm not sure if this applies to ASUS devices.
In Z2Plus we can make the device tampered flag to false by flashing an
older Chinese Firmware on the phone using QPST Flash Tool.
Afterwards we can flash the latest firmware to get back to stock with locked Bootloader.
I know I wont get OTA since I unlocked using the OFFICIAL Method.
I just need to Relock the Bootloader.
I Hope someone would Help.
Thank You
:laugh::laugh::laugh:
rameeskr said:
This is not a method to relock Bootloader
I see many threads opened on the same topic and closed!
I hope those threads fixed things for you guys.
My situation is Different!
This is not a duplicate Thread.
I just unlocked bootloader on my Zenfone 3 [ZE552KL 4GB 5.5' Model]
After flashing TWRP and using ROMs based on 9.0, I found that we cannot use
UPI [Payment Interface in India (GooglePay)] in the device!
I tried many methods to flash the stock ROM and lock the Boot loader again, But I cant lock it anyway!
I found a thread by @Saktis_Impreza on this topic but I get:
adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.014s
I would like to share an idea which helped me Regain Warranty after rooting
and flashing over several times on the device ZUK Z2 Plus.
I'm not sure if this applies to ASUS devices.
In Z2Plus we can make the device tampered flag to false by flashing an
older Chinese Firmware on the phone using QPST Flash Tool.
Afterwards we can flash the latest firmware to get back to stock with locked Bootloader.
I know I wont get OTA since I unlocked using the OFFICIAL Method.
I just need to Relock the Bootloader.
I Hope someone would Help.
Thank You
:laugh::laugh::laugh:
Click to expand...
Click to collapse
Hello anyone pls help
Actually you can relock bootloader by reflashing factory raw, typing in cmd "fastboot oem unlock" and then, with bl locked, reflashing the latest oreo raw.
My tool does it automatically.
Giovix92 said:
Actually you can relock bootloader by reflashing factory raw, typing in cmd "fastboot oem unlock" and then, with bl locked, reflashing the latest oreo raw.
My tool does it automatically.
Click to expand...
Click to collapse
Thanks for your reply
I found 2 RAW images available in the internet.
I tried flashing both.
But I get the same result.
Anyway I'll try again and update.
Can you pls guide me to your tool/method.
rameeskr said:
Thanks for your reply
I found 2 RAW images available in the internet.
I tried flashing both.
But I get the same result.
Anyway I'll try again and update.
Can you pls guide me to your tool/method.
Click to expand...
Click to collapse
Here you are.
https://forum.xda-developers.com/zenfone-3/development/auto-tool-ze5xxklmodder-t3861558
rameeskr said:
This is not a method to relock Bootloader
I see many threads opened on the same topic and closed!
I hope those threads fixed things for you guys.
My situation is Different!
This is not a duplicate Thread.
I just unlocked bootloader on my Zenfone 3 [ZE552KL 4GB 5.5' Model]
After flashing TWRP and using ROMs based on 9.0, I found that we cannot use
UPI [Payment Interface in India (GooglePay)] in the device!
I tried many methods to flash the stock ROM and lock the Boot loader again, But I cant lock it anyway!
I found a thread by @Saktis_Impreza on this topic but I get:
adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.014s
I would like to share an idea which helped me Regain Warranty after rooting
and flashing over several times on the device ZUK Z2 Plus.
I'm not sure if this applies to ASUS devices.
In Z2Plus we can make the device tampered flag to false by flashing an
older Chinese Firmware on the phone using QPST Flash Tool.
Afterwards we can flash the latest firmware to get back to stock with locked Bootloader.
I know I wont get OTA since I unlocked using the OFFICIAL Method.
I just need to Relock the Bootloader.
I Hope someone would Help.
Thank You
:laugh::laugh::laugh:
Click to expand...
Click to collapse
Found a method to do it Finally
Pls check this thread.
https://forum.xda-developers.com/zenfone-3/development/auto-tool-ze5xxklmodder-t3861558/page4
:laugh: