Database Develop

Downgrade method still works after August patch

hey guys, been a painful 3 days lol( busy looking for a nokia 5 stock rom instead of a nb0 rom lmao!!).
The method works am now on 7. so guys go right ahead and downgrade if you wanna do it.
P.s 1. search for nbo and not stock rom
2. When the setting up comes what you need to do is click setup with no network. this way you will prevent the system from taking you straight to updates!.
Next step root and enjoy?

Please provide the link of nb0 ROM for Nokia 5 ta -1053

its also safe to downgrade Nokia ta-1024 from pie to nougat with nost bootloader will still be unlocker .

jason_l367 said:
its also safe to downgrade Nokia ta-1024 from pie to nougat with nost bootloader will still be unlocker .
Click to expand...
Click to collapse
Greetings;
I've been out from Android Modding and Development for quite some time and I'm a little bit lost at the moment.
Where do you guys find the nb0 files and how do you select them for your devices?
I'm looking for a source for several Nokia devices; but most specific for the TA-1024
Thanks in advance.
Best regards;

rgxHost said:
Greetings;
I've been out from Android Modding and Development for quite some time and I'm a little bit lost at the moment.
Where do you guys find the nb0 files and how do you select them for your devices?
I'm looking for a source for several Nokia devices; but most specific for the TA-1024
Thanks in advance.
Best regards;
Click to expand...
Click to collapse
Here is the nougat nb0 file that I use (with nost). It may fail midway through btw but don't worry if it does it happen to me often, just start again & select the wipe user data option
I m not sure you can downgrade with locked BL but I downgrade from pie with unlock easily

jason_l367 said:
Here is the nougat nb0 file that I use (with nost). It may fail midway through btw but don't worry if it does it happen to me often, just start again & select the wipe user data option
I m not sure you can downgrade with locked BL but I downgrade from pie with unlock easily
Click to expand...
Click to collapse
Greetings;
Thanks for the prompt reply.
Regarding that error, before you flash any room you should always clean Dalvik cache, Cache and Wipe user data. That prevents errors, and duplicate data or applications.
I couldn't find "unlock easy" to see if I can manage do unlock the bootloader. Is this a tool that can be found on the forum?
As far as I know without bootloader unlocked you're not able to flash anything, including recovery.
Fastboot will refuse any flashing options.

rgxHost said:
Greetings;
Thanks for the prompt reply.
Regarding that error, before you flash any room you should always clean Dalvik cache, Cache and Wipe user data. That prevents errors, and duplicate data or applications.
I couldn't find "unlock easy" to see if I can manage do unlock the bootloader. Is this a tool that can be found on the forum?
As far as I know without bootloader unlocked you're not able to flash anything, including recovery.
Fastboot will refuse any flashing options.
Click to expand...
Click to collapse
As far as I know this is the only way to unlock BL on the Nokia 5, if you wanna root on pie. See this thread for all the info you'll need. Good luck!

jason_l367 said:
As far as I know this is the only way to unlock BL on the Nokia 5, if you wanna root on pie. See this thread for all the info you'll need. Good luck!
Click to expand...
Click to collapse
Greetings;
Already tried that.
OEM Unlock option returns 0 (even when enabled and toggled on).
Bootloader Unlock option is not present.
I see that nowadays is quite difficult to get root & unlock the bootloader.
Fastboot OEM Report:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
...
The first thing that occurrs to me is that the phone is carrier locked (even though) I can use any SIM.

rgxHost said:
Greetings;
Already tried that.
OEM Unlock option returns 0 (even when enabled and toggled on).
Bootloader Unlock option is not present.
I see that nowadays is quite difficult to get root & unlock the bootloader.
Fastboot OEM Report:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
...
The first thing that occurrs to me is that the phone is carrier locked (even though) I can use any SIM.
Click to expand...
Click to collapse
That's wierd. My 1024 was piece of cake to root. I think you right that the carrier modél is a lot different to unlocked variant

Bootloop after recent Android OTA Update

Hello Community,
i have a Problem after the installation of the newest android Update (OTA).
The A2 just Boot till the white AndroidOne Logo and it hangs there after a time it seems it shut down itself.
My Device:
-USB Debugging is disabled, its a new testing device.
-I cant boot in recovery mode (vol-UP+Power) just boots to the white androidOne Screen and there it hangs
- I can enter fastboot(VOL-Down+power) mode and the device is listed when i type fastboot devices in my terminal on pc
- when i fire up MiFlash tool it list my device after clicking refresh, if i want flash the latest FW (http://en.miui.com/download-353.html) i get the error:
error:"Flash bluetooth_a error"
- My bootloader is locked.
Question:
How can I flash a offical Android with a locked bootloader?
is it a good idea? or better send it back for a warranty solution (i dont want wait)
is there another way to solve my problem? i really dont know whats the problem is. i did not rooted the device or anything.
would be lovely if someone could help me. with an instruction what i can try.
Thank you very much and have a nice day
Regards

If you have enabled 'OEM Unlock' setting in Developer settings, you will probably be good, you can unlock bootloader(oem/flashing/critical) and flash the official ROM ( as per now, 10.0.2.0 )
If not, you have 2 options
-Boot into EDL using short points and flash from there
-Warranty
Same thing happened to a friend's phone, it wasn't touched and just went brick after 10.0.2.0 OTA.
Guess everyone should enable 'OEM Unlock' in case this happens(Data Encrypted anyway, worst case stolen phone better than the chance of brick every time an OTA comes)
edit: If you want to save your data, you obviously shouldn't try the bootloader unlock way...EDL flashing allows flashing without wiping data, but haven't tested that personally

wow really? that are bad news...
thank you anyway :crying:
maybe someone other got a idea?
regards

Lot of users faced this after today's update including myself. Since my bootloader is locked, only option left is EDL flashing by connecting motherboard test points.

Just an advice for everyone reading this message from a Xiaomi Android One device: ALWAYS KEEP UR BOOTLOADER UNLOCKED, IT DOESNT MATTER IF USB DEBUG ISNT ACTIVE, JUST UNLOCK BOOTLOADER
sorry for caps, is just an important thing, i also had the issue but with unlocked bootloader i solved it easily

Just flash using fastboot
Sent from my LG-V930 using Tapatalk

Abrilabr said:
Just an advice for everyone reading this message from a Xiaomi Android One device: ALWAYS KEEP UR BOOTLOADER UNLOCKED, IT DOESNT MATTER IF USB DEBUG ISNT ACTIVE, JUST UNLOCK BOOTLOADER
sorry for caps, is just an important thing, i also had the issue but with unlocked bootloader i solved it easily
Click to expand...
Click to collapse
Yea, but if you want use it as enterprise Device the open Bootloader is a problem.
ilyas111 said:
Just flash using fastboot
Sent from my LG-V930 using Tapatalk
Click to expand...
Click to collapse
that seems not possible with a locked Bootloader (very new phone)
or can you provide a working solution with a locked bootloader? i wont use this EDL thing because its just new and i dont want open it.
Thank you all anyways

Try with this tool : https://forum.xda-developers.com/mi-a2/development/tool-mi-a2-xtrem-toolkit-t3879660
(edl included)

Same trouble here, we are fu...ed!

With Xiaomi mi flash tool, you can re active bootloader protection !
Simple flash with this tool with the option "clean and lock critical"
Works for me !

xotob said:
With Xiaomi mi flash tool, you can re active bootloader protection !
Simple flash with this tool with the option "clean and lock critical"
Works for me !
Click to expand...
Click to collapse
you had bootloader unlocked, i dont, i cant flash nothing with bootloader locked and i have unchecked the option in debug menù.

Reptant said:
If you have enabled 'OEM Unlock' setting in Developer settings, you will probably be good, you can unlock bootloader(oem/flashing/critical) and flash the official ROM ( as per now, 10.0.2.0 )
If not, you have 2 options
-Boot into EDL using short points and flash from there
-Warranty
Same thing happened to a friend's phone, it wasn't touched and just went brick after 10.0.2.0 OTA.
Guess everyone should enable 'OEM Unlock' in case this happens(Data Encrypted anyway, worst case stolen phone better than the chance of brick every time an OTA comes)
edit: If you want to save your data, you obviously shouldn't try the bootloader unlock way...EDL flashing allows flashing without wiping data, but haven't tested that personally
Click to expand...
Click to collapse
After got OTA update to 10.0.3.0 and Today i try to unlock bootloader but I can't unlock_critical and I can't flashing unlock

boonc said:
After got OTA update to 10.0.3.0 and Today i try to unlock bootloader but I can't unlock_critical and I can't flashing unlock
Click to expand...
Click to collapse
Same problem here, does anyone have a solution?

Does fastboot mode is detected in pc?
Sent from my MI 6X using Tapatalk

ilyas111 said:
Does fastboot mode is detected in pc?
Sent from my MI 6X using Tapatalk
Click to expand...
Click to collapse
yes, but i cant use more of fastboot comands, cause bootloader is locked, cant use "flashing unlock/unlock_critical"

Cizzle4 said:
you had bootloader unlocked, i dont, i cant flash nothing with bootloader locked and i have unchecked the option in debug menù.
Click to expand...
Click to collapse
I'm in your same situation

Exactly the same situation here... Waiting for a solution without losing warranty.

I think if your bootloader is not unlocked, the only possible solution left is to shorting the test points on motherboard. Those who have warranty can return the unit for claim. Yet another mess up from Xiaomi and this will be my last phone from them.

UnlimitedBB said:
I think if your bootloader is not unlocked, the only possible solution left is to shorting the test points on motherboard. Those who have warranty can return the unit for claim. Yet another mess up from Xiaomi and this will be my last phone from them.
Click to expand...
Click to collapse
I can understand that. I will claim warranty because its new and i dont want do that test point thing.
on private i would buy and recommend xiaomi anyways but if you want these hardware for some enterprise things then better not.
Iam out of this Thread now but if you want talk here some more feel free.. maybe somebody can bring a solution for all you guys who face this problem but i think its not possible without a open BL or the TestPoint Method.
Regards and have a nice day

Hi. I'm with locked bootloader. I received new January update. No change - stock variant updated to Pie. So it's safe to update or waiting for new one? Mi A2 4/64 micron ram

Unlocking bootloader: definitive bye-bye to automatic updates?

With the Moto Z, after I returned the phone to stock (flashed stock firmware and locked the bootloader), I'd be able to flash stock firmware with the flashing locked.
Not so with the Motorola One Zoom. In other words, flashing stock and re-locking didn't return the phone to its pristine state. Even when flashing stock firmware over stock firmware, I have to unlock the bootloader.
Differences I observed: on the bootloader screen, when re-locked the Z would show "oem_locked" again. On the One Zoom, it shows "flashing_locked" instead. I'm pretty sure it showed "oem_locked" before unlocking.
WIth the Z, every time I wanted to unlock the bootloader, I had to issue "fastboot oem unlock" followed by the unlock code. The code isn't necessary with the re-locked One Zoom.
In other words, maybe it was a one-way trip. It seems that the phone won't return to its original state, it looks it's modified for good. And I'm afraid this means bye-bye to automatic updates.
Am I missing something here?

My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.

rafikowy said:
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
Click to expand...
Click to collapse
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.

Whammamoosha said:
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Click to expand...
Click to collapse
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.

rafikowy said:
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
Click to expand...
Click to collapse
Don't bother, I have mine. Thanks.

I would like the flash script if someone would share it

Help with unlocking bootloader
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.

Bodeman12345 said:
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Click to expand...
Click to collapse
In the settings for developers you gave permission for Factory Unlock?

ilia3367 said:
In the settings for developers you gave permission for Factory Unlock?
Click to expand...
Click to collapse
I enabled the setting to unlock oem bootloader is that the same?

Bodeman12345 said:
I enabled the setting to unlock oem bootloader is that the same?
Click to expand...
Click to collapse
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
Code:
fastboot devices
If the device is detected, enter the command:
Code:
fastboot getvar all
And copy the result here.

ilia3367 said:
yes.
Click to expand...
Click to collapse
Yes I did that

Bodeman12345 said:
Yes I did that
Click to expand...
Click to collapse
Answer the other questions, please!

diculpe por que mi pc no ve el fastboot de mi one zoom?

ilia3367 said:
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
If the device is detected, enter the command:
And copy the result here.
Click to expand...
Click to collapse
I used this youtube video
I dont know where it is manifactured but I live in the netherlands.
I dont get the 3th question
I will do the commands in a couple minutes

Hey all,
I have the Moto One Zoom running on Android 9.
Also, It's Rooted with Magisk and have Riru EdXposed installed, can I install my OTA updates without bootloop or do I have to Uninstall Magisk, relock bootloader and factory reset/flash stock firmware to get latest OTA updates?
Any feedback is appreciated.
Thanks

Wrong persist.img and widevine L3 issues on Asus ROG Phone 2 (Tencent version)

Dear everyone, i'm just a newbie on Phone and stuffs like coding or decoding.
Let me explain clearly what happen to my phone recently and why i have open this thread for asking for seriously help.
From the very beginning i have follow instruction from this thread:
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
It said we could change the vendor code from CN to WW by edit COUNTRY from persist in 9008 mode (mnt/vendor/persist) or lately called persist.img without Root or unlock bootloader the device (which lately breached the fuse by using command fastboot oem check-fuse in fastboot).
Anything not gone wrong until i reach the step called "1.ReadPersist.bat" and it return the "persist.img" with not correct size of the file;
less than 32.768 Kb, but i didn't recognize until finish using Ultra Edit (hex edit) and write back persist.img (which has wrong size of package).
That make my device show not correct serial number as is: C4ATAS00000
Also recognize that the device is triggered Widevine Security from L1 to L3, Device is not certified in Google Playstore and other annoying problems.
My phone is not rooted and not unlocked bootloader then i have no reason why they show me L3 widevine even i have reflash raw firmware, unlock and relock bootloader.
After get contact with other Asus ROG phone 2 user, i have able to get a new persist.img and start to looking deep down what has contain inside persist.img
First effort, i have identified that in persist.img contains:
1. IMEI (second imei) (able to find it via command fastboot oem device-info)
2. Serial number (SSN) (able to find it via command fastboot oem device-info)
3. ISN (able to find it via command fastboot oem device-info)
4. Wifi MAC Address pool (able to find it via command fastboot oem system-info)
5. Bluetooth MAC Address. (not able to find it anywhere )
Use the same way as before, entering 9008 mode, edit new persist.img to match with items 1,2,3 above; then write back file persist.img to my device.
My phone now has gained back Serial Number, able to unlock bootloader via Official Asus apk on Homepage, resolve some major issue such Device is certified...etc
I also have tried to unlock - relock bootloader to perform root or so on but no luck to restore widevine L1.
A lot of people in my country has same problem as mine, i will be very thanks if anyone has any idea what has triggered widevine from L1 to L3 when we flashed wrong persist.img into Device.
If anyone concern about my persist.img which has L3 widevine security and L1 could contact direct to me via inbox/pm.
Thanks.

Anyone? Please?

tuannghia1985 said:
Anyone? Please?
Click to expand...
Click to collapse
I don't think you can get the widevine back because you have changed your system. I did a similar guide and now I don't have signal.
You can try this guide here
https://forum.xda-developers.com/ro...-l3-issues-t4049411/post81742183#post81742183
I would really appreciate it if you could send me yours so I can get my signal back

Sk1t said:
I don't think you can get the widevine back because you have changed your system. I did a similar guide and now I don't have a signal.
You can try this guide here
https://forum.xda-developers.com/ro...-l3-issues-t4049411/post81742183#post81742183
I would really appreciate it if you could send me yours so I can get my signal back
Click to expand...
Click to collapse
Many people have lost signal due to flash raw ROM via QFILs, I and my friend is working on this problem and try best to work it out. We have Qcn backup right now and try to edit, convert it to correct imei/meid. No signal right now. For EFS, both of us is not rooted/unlocked bootloader yet (it takes us a lot of time for backup and restore those 40Gb data on phone - during day works) then please wait until we get new things.

tuannghia1985 said:
Many people have lost signal due to flash raw ROM via QFILs, I and my friend is working on this problem and try best to work it out. We have Qcn backup right now and try to edit, convert it to correct imei/meid. No signal right now. For EFS, both of us is not rooted/unlocked bootloader yet (it takes us a lot of time for backup and restore those 40Gb data on phone - during day works) then please wait until we get new things.
Click to expand...
Click to collapse
Yes I believe I followed this guide here.
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
I mounted the persist image in this and it's basically empty with no actual files. I don't know enough about this and don't want to go pointing fingers but I suspect that is where I messed it up.

Sk1t said:
Yes I believe I followed this guide here.
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
I mounted the persist image in this and it's basically empty with no actual files. I don't know enough about this and don't want to go pointing fingers but I suspect that is where I messed it up.
Click to expand...
Click to collapse
thanks for sending me a guide, I will follow that instruction. for persist.img you could use mine for find and editing by ultraedit.
https://drive.google.com/drive/folders/1k8EbD_mdLoIifauW9WORVVA6VIMupmmP?usp=sharing

tuannghia1985 said:
thanks for sending me a guide, I will follow that instruction. for persist.img you could use mine for find and editing by ultraedit.
https://drive.google.com/drive/folders/1k8EbD_mdLoIifauW9WORVVA6VIMupmmP?usp=sharing
Click to expand...
Click to collapse
https://forum.xda-developers.com/rog-phone-2/how-to/rog2-android10-twrp-wzsx150-t4027313
Thank you very much sir! I've tried this while this does contain more files than my current persist which is just empty folders it has not fixed my signal issue.
https://forum.xda-developers.com/rog-phone-2/how-to/rog2-android10-twrp-wzsx150-t4027313
This TWRP tool has more backup partitions and I think it could be useful in your quest.
I'm not sure which partitons I need but I suspect efs is one of them.
ALSO:
I assume you edited the persist image and edited some things as I the SSN number I put my own one in. It still has no signal , was there anything else you have changed?. I have and cannot power on the phone's modem with the phone code *#4636#*.

Help me sir, i cant update dan unlock my bootloader since my phone show wrong serial number C4ATAS00000

I also did the tutorial for this topic 9008, serial number lost asus tool gave widevine L3 network error persist all changed.
I was already trying to fix it for 2 months. I went back to CN ww for many times without counting the raw RAW wink countless times, several versions and nothing.
Until I found your topic that really saved me and I believe it will help many because in that period I saw many reports of people trying to use the Asus unlocking tool and reporting a network error as well as me this occurs when I lose Rog's serial number .C4ATAS00000.
I recovered the serial number, IMEi, ISN. And it was even converted from CN to WW.
Grateful friend for your effort.

hi i have the same problem with my asus rog phone zs600kl
tuannghia1985 said:
Dear everyone, i'm just a newbie on Phone and stuffs like coding or decoding.
Let me explain clearly what happen to my phone recently and why i have open this thread for asking for seriously help.
From the very beginning i have follow instruction from this thread:
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
It said we could change the vendor code from CN to WW by edit COUNTRY from persist in 9008 mode (mnt/vendor/persist) or lately called persist.img without Root or unlock bootloader the device (which lately breached the fuse by using command fastboot oem check-fuse in fastboot).
Anything not gone wrong until i reach the step called "1.ReadPersist.bat" and it return the "persist.img" with not correct size of the file;
less than 32.768 Kb, but i didn't recognize until finish using Ultra Edit (hex edit) and write back persist.img (which has wrong size of package).
That make my device show not correct serial number as is: C4ATAS00000
Also recognize that the device is triggered Widevine Security from L1 to L3, Device is not certified in Google Playstore and other annoying problems.
My phone is not rooted and not unlocked bootloader then i have no reason why they show me L3 widevine even i have reflash raw firmware, unlock and relock bootloader.
After get contact with other Asus ROG phone 2 user, i have able to get a new persist.img and start to looking deep down what has contain inside persist.img
First effort, i have identified that in persist.img contains:
1. IMEI (second imei) (able to find it via command fastboot oem device-info)
2. Serial number (SSN) (able to find it via command fastboot oem device-info)
3. ISN (able to find it via command fastboot oem device-info)
4. Wifi MAC Address pool (able to find it via command fastboot oem system-info)
5. Bluetooth MAC Address. (not able to find it anywhere )
Use the same way as before, entering 9008 mode, edit new persist.img to match with items 1,2,3 above; then write back file persist.img to my device.
My phone now has gained back Serial Number, able to unlock bootloader via Official Asus apk on Homepage, resolve some major issue such Device is certified...etc
I also have tried to unlock - relock bootloader to perform root or so on but no luck to restore widevine L1.
A lot of people in my country has same problem as mine, i will be very thanks if anyone has any idea what has triggered widevine from L1 to L3 when we flashed wrong persist.img into Device.
If anyone concern about my persist.img which has L3 widevine security and L1 could contact direct to me via inbox/pm.
Thanks.
Click to expand...
Click to collapse
hi i flash me rog phone zs600kl afther flash with Qfil me serial and imei has chanced serial is now c4atas000000 i need to restore it back too JCAZGV040926299 i dont have root and no bootloader unlocked cant unlock help me how i can get me seral back to restore i dont know howto edit persist

Serial number wrong
Hi
My device was flashed via a third party supplier and the serial number is wrong, so i cannoy unlock the bootloader. Can you please explain what steps do I need to take to amend the serial number?
Thanks

tuannghia1985 said:
Dear everyone, i'm just a newbie on Phone and stuffs like coding or decoding.
Let me explain clearly what happen to my phone recently and why i have open this thread for asking for seriously help.
From the very beginning i have follow instruction from this thread:
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
It said we could change the vendor code from CN to WW by edit COUNTRY from persist in 9008 mode (mnt/vendor/persist) or lately called persist.img without Root or unlock bootloader the device (which lately breached the fuse by using command fastboot oem check-fuse in fastboot).
Anything not gone wrong until i reach the step called "1.ReadPersist.bat" and it return the "persist.img" with not correct size of the file;
less than 32.768 Kb, but i didn't recognize until finish using Ultra Edit (hex edit) and write back persist.img (which has wrong size of package).
That make my device show not correct serial number as is: C4ATAS00000
Also recognize that the device is triggered Widevine Security from L1 to L3, Device is not certified in Google Playstore and other annoying problems.
My phone is not rooted and not unlocked bootloader then i have no reason why they show me L3 widevine even i have reflash raw firmware, unlock and relock bootloader.
After get contact with other Asus ROG phone 2 user, i have able to get a new persist.img and start to looking deep down what has contain inside persist.img
First effort, i have identified that in persist.img contains:
1. IMEI (second imei) (able to find it via command fastboot oem device-info)
2. Serial number (SSN) (able to find it via command fastboot oem device-info)
3. ISN (able to find it via command fastboot oem device-info)
4. Wifi MAC Address pool (able to find it via command fastboot oem system-info)
5. Bluetooth MAC Address. (not able to find it anywhere )
Use the same way as before, entering 9008 mode, edit new persist.img to match with items 1,2,3 above; then write back file persist.img to my device.
My phone now has gained back Serial Number, able to unlock bootloader via Official Asus apk on Homepage, resolve some major issue such Device is certified...etc
I also have tried to unlock - relock bootloader to perform root or so on but no luck to restore widevine L1.
A lot of people in my country has same problem as mine, i will be very thanks if anyone has any idea what has triggered widevine from L1 to L3 when we flashed wrong persist.img into Device.
If anyone concern about my persist.img which has L3 widevine security and L1 could contact direct to me via inbox/pm.
Thanks.
Click to expand...
Click to collapse
How do you edit persist.img and where's the position of the imei and others in persist.img? Because I tried to open persist.img using Hex editor, but I'm confuse because I don't know where's the imei, ssn, isn, wifi and bt. I lost baseband, imei and wifi.

can someone please help me ? my ROG2 is dead, but lineage and omni roms boot the phone but no sim card and no touch screen, i have to connect OTG mouse !!! so i think it's caused by a corrupted persist file, and when i write : fastboot oem device-info the phone returns random numbers !!!
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) ABL : CS1.2(00125)-8-WW-user
(bootloader) SSN : 111111111111111
(bootloader) ISN : FFAABBCC123456789
(bootloader) IMEI : 111111111111111
(bootloader) CID : ASUS
(bootloader) Project : ZS660KL_L
(bootloader) DT ID : 91
(bootloader) CPU ID : 0 (12LAYER)
(bootloader) Feature ID : 6 (AC_12LAYER)
(bootloader) JTAG ID : 5 (0x300A50E1)
(bootloader) SB=Y
(bootloader) TotalDMCounter : 14
(bootloader) DMCounter : 4
(bootloader) SlotARetryCounter : 68
(bootloader) SlotAUnbootableCounter : 4
(bootloader) SlotBRetryCounter : 15
(bootloader) SlotBUnbootableCounter : 1
(bootloader) BOOT_COUNT : 2478
(bootloader) LOCK_COUNT : 4
(bootloader) Check_APDP : 0
(bootloader) Check_MSADP : 0
(bootloader) rawdump_en : false
(bootloader) Current Slot : a
(bootloader) Slot_a bootable : Bootable
(bootloader) AVB Verity : Enable
(bootloader) Verify vbmeta ret : 5
(bootloader) CN Low Cost Tar Status : false
(bootloader) UART ON : false
OKAY [ 0.146s]
can someone please provide a clean persist file, and tell me where i can find SSN ISN and IMEI numbers other than this command ??

Please refresh the persist.img link if you can, i have the same problem

tuannghia1985 said:
thanks for sending me a guide, I will follow that instruction. for persist.img you could use mine for find and editing by ultraedit.
https://drive.google.com/drive/folders/1k8EbD_mdLoIifauW9WORVVA6VIMupmmP?usp=sharing
Click to expand...
Click to collapse
Can you re upload the persist.img? My phone still got issue no imei, no wifi and no baseband thanks

Hey guyz i have a lg v40 thinq. It is the verizon one

My phone was already unlocked for the bootloader when i bought it and now i want to relock it. I tried to relock it Using ADB but it doesn't work the phone just restarts and i cannot enter fastboot mood either no matter what i do. And the special codes like *#06# and the other ones also don't work pls help

Faizan._.Akhtar said:
My phone was already unlocked for the bootloader when i bought it and now i want to relock it. I tried to relock it Using ADB but it doesn't work the phone just restarts and i cannot enter fastboot mood either no matter what i do. And the special codes like *#06# and the other ones also don't work pls help
Click to expand...
Click to collapse
to relock the bootloader, the device has to have a 100% stock rom on it, no modifications at all.
ADB isn't used to relock the BL, it has to be done with fastboot.
To get fastboot on the device you have to use qfil and flash the engineering abl and then go directly to fastboot from qfil.
Look in the guides section and you'll find threads how to get the above done.

AsItLies said:
to relock the bootloader, the device has to have a 100% stock rom on it, no modifications at all.
ADB isn't used to relock the BL, it has to be done with fastboot.
To get fastboot on the device you have to use qfil and flash the engineering abl and then go directly to fastboot from qfil.
Look in the guides section and you'll find threads how to get the above done.
Click to expand...
Click to collapse
Hey bro i cannot find the guide can you pls give me the link for it. Thank you

Faizan._.Akhtar said:
Hey bro i cannot find the guide can you pls give me the link for it. Thank you
Click to expand...
Click to collapse
there are multiple guides in the guides section re this. They may be for unlocking the bootloader, but in your case you follow it and instead of oem unlock, you type oem lock.