Question Bypass OEM unlock - Asus Zenfone 9

Has anyone used the payload dumper to pull out the boot.img from stock firmware, modified it with Magisk, put it back into the payload file to then upload the pre-rooted firmware using Qualcomm tools?
Would this work so that my IMEI/Serial isn't blacklisted by ASUS?

Just for clarification, I'm talking about steps 1-3 (from the incredible write-up here: https://forum.xda-developers.com/t/rooting-zenfone-9-with-magisk.4484715/)
Instead of part/step four, take the file moved back to the PC and put it back into payload.bin, then into the zipped ROM file.
part/step five would be to use QFIL to load that onto the device (https://www.techswizz.com/asus-zenfone-9-stock-rom-firmware/).
Or is it impossible to update the payload_properties.txt so that it reflects any changes to the payload.bin file?
Thank you.

rootlessabroad said:
Has anyone used the payload dumper to pull out the boot.img from stock firmware, modified it with Magisk, put it back into the payload file to then upload the pre-rooted firmware using Qualcomm tools?
Would this work so that my IMEI/Serial isn't blacklisted by ASUS?
Click to expand...
Click to collapse
In other words: you're trying to bypass the need to unlock the bootloader through ASUS (thus invalidating your phone's warranty)?
I have not tried it, though with them claiming security, I doubt it would work. While the bootloader is locked, they have expectations for exactly what can be used. Variations on that are likely to lead to errors.

In reading their EULA, the hardware warranty is only invalidated when using their unlock. It is a specific clause in the unlock agreement, not in the normal EULA. As such, if the phone is unlocked any other way than their unlock program, the warranty is still applicable.
That is why I am looking for any other mechanism to unlock it.

rootlessabroad said:
In reading their EULA, the hardware warranty is only invalidated when using their unlock. It is a specific clause in the unlock agreement, not in the normal EULA. As such, if the phone is unlocked any other way than their unlock program, the warranty is still applicable.
That is why I am looking for any other mechanism to unlock it.
Click to expand...
Click to collapse
Well, this method might very well brick your phone. If you're willing to give it a try, then let us know how it goes!

I can safely say this won't work, assuming ASUS implemented dm-verity and Android Verified Boot properly. A modified boot image will fail verification; in the best case, you'll get this screen:
{
"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"
}
In the worst case, bootloader will fail to load the boot image.
What are you trying to accomplish by bypassing the "correct" OEM unlocking process?

I'm trying to avoid having ASUS not warrant their hardware.
And an unrooted phone is completely useless to me.

rootlessabroad said:
I'm trying to avoid having ASUS not warrant their hardware.
And an unrooted phone is completely useless to me.
Click to expand...
Click to collapse
Actually, if you are in the European Union, your device is under warranty even if you have the bootloader open with their method. For this reason, when you use the app to unlock, it does not say that you lose the warranty, but that you may lose the warranty.

I sent my Zenfone 8 back to Asus after having had unlocked the bootloader and they still serviced in under warranty. They may have given me a hard time about it, I can't remember (it was a year ago).

Related

[Q] Atrix 4G Update Error

All I get is this screen:
{
"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"
}
Please help its been like that for awhile after the update is done downloading and I try to install it!
Sent from my HTC Sensation 4G using XDA App
it seem you have some mods in /system or /webtop partition
Did you ever unlock your bootloader?
ATT right?
mramirezusa said:
it seem you have some mods in /system or /webtop partition
Did you ever unlock your bootloader?
ATT right?
Click to expand...
Click to collapse
if you Answer are NO
and YES
this is the way to do it follow this link and you need a PC and your phone attached to it by USB:
"http://direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSummary.asp?country=USA&language=ENS&web_page_name=SUPPORT&strCarrierId=ATT&strPhone=Motorola%20ATRIX%28TM%29%204G&strCable=Micro%20USB%20Data%20Cable&strURL=https://rsddownload.motorola.com/download/SoftwareUpdateforATTATRIX4Gversion.4.5.91.pdf"
I believe i just rooted it with gingerbreak but then i followed this tutorial: http://atrix4ghacks.com/atrix-4g-hacks/how-to-enable-webtop-without-laptopusb-dock/
it edited my webtop stuff so how do i fix it so i can update
lol don't panic! (....I have a towel =D)
You just entered the recovery menu. To see the error message, you need to un-hide it by touching the screen on the bottom right corner (right above the search button). This will show you what error you encountered.
If you're OTAing up, then you probably had Titanium or something that removed bloatware or modded the system with a theme or custom files. If that's the case, any OTA will fail because you will not have passed the pre-install check. You have three options:
1.) Go here and get the Automated Upgrade for PC Users. That will allow you to upgrade and bypass the test, while also keeping your data. This doesn't require any mods or unlocked bootloaders. (BE WARNED THAT IF YOU USE THIS, YOUR BOOTLOADER WILL BE BLOWN. DON'T DOWNGRADE WITH SBFs AND STICK TO EATING YOUR FRUITCAKE! However, Radio and Bootloader SBFs are still considered safe. As any wise man would do, proceed with caution.)
OR
2.) Unlock your bootloader, install CWM from Tenfar, and then get KP's 2.3.4 ROM Beta 4 and put it in your SD card. Boot up CWM and install it. That easy. =] (BE WARNED SOME PEOPLE BRICKED THIS WAY.)
ORRRRRR
3.) Using the fastboot from Motorola and unlocking your bootloader, just flash the images here. (Currently the best method and seems to produce the best results, but if you don't know how to do it, then don't do it.)
If you need instructions on how to do any of the above, use this noob bible. And lastly, if you want to root, use the preinstall method (also in bible.)
Happy upgrading!
~jojojohnson7410~
I had the same problem and also had only used gingerbreak and webtop mod. I tried using pc update software but it thought I was on orange france (mine is AT&T) so I didn't proceed. Decided to flash the gingerbread plus pudding sbf in pudding thread, worked perfect and kept all data, you don't need to unlock bootloader before updating
Same problem
I'm having the exact same problem.
Except my bootloader is unlocked.
Any help would be greatly appreciated.
Thanks!

"This is a development device not intended for production use"

Hello,
After unrooted and re-locked (bootloader) my Nexus 9.
When i boot it, i got this:
{
"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"
}
"This is a development device not intended for production use"
After that, I have flashed the stock rom 6.0.1,so I'm 100% stock now, but I still get this message when the device boot
Is it a bug, or my seller sold me a tablet supposed to be not sold?
Do you think I can ask for a replacement? Because I would like to sell it and buy a other tablet... But with this weird message at the boot, I can't expect a lot from it...
Thanks
Strange. I am interested and want to know more.
The warning only recently appeared?
dmantilal said:
Strange. I am interested and want to know more.
The warning only recently appeared?
Click to expand...
Click to collapse
Just after re-locked my device. So i have unlocked it again to flash the last 6.0.1 stock rom, locked the bootloader, and the red message is still here. But I have seen that, if I unclock the bootloader, the message disappears, and if I lock it, the message appear... Strange.
One other thing, (with bootloader locked), I have an ota update, 7,7mb, but when I update, it fail each time
So if I send it to HTC, I think they will change it with a new one, because even with a factory reset, flash stock rom, I don't know what more they can do.
And I have light bleed on the screen, so i really hope they will give me a new one!
That's strange. I don't know whether that red message appears even if you lock the bootloader with everything being stock, but you may try this method: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Edit: If OTA update fails, your device may not be completely stock. Try troubleshooting by consulting the recovery log, or use the "flash-all.bat" to flash stock ROM again.
LeoYL said:
That's strange. I don't know whether that red message appears even if you lock the bootloader with everything being stock, but you may try this method: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Edit: If OTA update fails, your device may not be completely stock. Try troubleshooting by consulting the recovery log, or use the "flash-all.bat" to flash stock ROM again.
Click to expand...
Click to collapse
Ok thanks for your help
I have send an email to HTC to ask for a replacement. I have seen that some people who got the same issue, (even without root or unlock bootloader) got a replacement :fingers-crossed: . And I have ugly light bleed on the screen, so I really hope I will got a replacement too
If the OTA fails then you aren't full stock..
DITTO to downloading the google stock image and flashing using the included flash-all.bat.

Question Error when trying to unlock bootloader

Hi all.
I'm trying to unlock the bootloader of my 8 Flip but am having a couple of issues. First one is that there's no "OEM Unlock" option in my Dev settings. I've tried running the official unlock tool anyay, and it errors out saying "Failed to unlock your device, please try again later.[11006]"
Any ideas?
Thanks.
Solved it - Just had to turn wifi off and use mobile data and it worked
My friend has an error code when unlocking the Bootloader. Do you know why?
{
"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"
}
Why are you trying to unlock the bootloader? Are there custom roms available?
lew4man said:
Why are you trying to unlock the bootloader? Are there custom roms available?
Click to expand...
Click to collapse
To root the phone
where did you buy the phone? Some vendors sell phones that cannot be rooted.
You can see it with the app CPU-Z in System section if you see bootloader : no, you can't root
I was just about to unlock the bootloader to try to dump the recovery.img and use that to create a twrp image.
But there is a big warning saying:
Before you download, install, and use the Unlock Device App (“Service”), you understand that you need to take all risks in terms of quality and performance of the Service, including but not limited to: once you trigger the Service, you’re not able to recover your ASUS products to the original status at the time of manufacturing (“Original Product”) anymore. Original Products which is used with the Service (“Changed Product”) will no longer be regarded as the Original Products. The software updates will not be available to the Changed Product, and the digital content in the Changed Product may no longer be used. (...)
Click to expand...
Click to collapse
Does this mean I would not get security updates and later the Android 13? I only want to get twrp to be able to root the device. but losing the OS updates would be a big no-no.
Are those who have unlocked it getting updates? Can anyone confirm this?
iceinsight said:
I was just about to unlock the bootloader to try to dump the recovery.img and use that to create a twrp image.
But there is a big warning saying:
Does this mean I would not get security updates and later the Android 13? I only want to get twrp to be able to root the device. but losing the OS updates would be a big no-no.
Are those who have unlocked it getting updates? Can anyone confirm this?
Click to expand...
Click to collapse
Would also like to know the answer to this. Did you ever find out?

Question Error in locking bootloader.

Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?
{
"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"
}
Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection
foobar66 said:
Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I don't recommend using the Pixel Repair Tool unless absolutely necessary.
If you are trying to return your device to absolute stock, I recommend using the Android Flash Tool. You can choose which factory build to flash, whether to wipe the device, and whether to relock the bootloader.
aymuhamm said:
Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?
View attachment 5475895
Click to expand...
Click to collapse
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.
Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.
After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader.
VozerCozer said:
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.
Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.
After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader
Click to expand...
Click to collapse
This is why I like to recommend the Android Flash Tool - simply from a perspective of ease of use, and the fact it's practically impossible to get wrong; additionally, the user can elect to lock the bootloader during the process when choosing the flash options. This removes the need to do anything else manually; the tool takes care of the entire process.
It's also very useful for updates.

Stuck in Bootloader menu!

Hello, so I decided to try an root this junky phone I have which is a moxee m2160. I followed a guide on youtube, I unlocked the bootloader, then got magisk. I then created the patched-magisk.img then used my computer & fastboot to flash it too the device. I was pretty sure I had gotten it until I rebooted it an it booted back too the bootloader. I'll upload pics of my screen to show you where Im stuck. Am I able to fix the phone with my pc somehow? I probably should've gathered more info before I did it. Thanks for any answers in advance.
{
"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"
}
This Is the name
e..
Is there anything I can do through adb or fastboot to fix it?
whisper42000 said:
Is there anything I can do through adb or fastboot to fix it?
Click to expand...
Click to collapse
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Something like this part I forgot the part with the empty vbmeta or from stock. Search. Good luck more I don't can help. I read it only somewhere
I've done the same thing to this phone every option on that screen doesn't do anything just reboots to the same screen. Does anyone out there have this phone and have the stock ROM or anything at all that would help restore this phone. I found out it is made by KonnectOne it is a government assistance phone from Assurance Wireless and that is pretty much all I can come up with. Any assistance at all would help a noob like myself, learning as I go. Thanks.
Specs for this devices are here https://phonedady.com/moxee-m2160
Greetings members. The support team over at KonnectOne has granted my request for factory firmware for this smartphone. I am presently in the process of establishing a secure file transfer protocol with support to download the package. I will have it later this week if any members are in need of it
I have the stock Firmware.. just got it today. Who needs it
dexscam37 said:
I have the stock Firmware.. just got it today. Who needs it
Click to expand...
Click to collapse
It's been officially released by the manufacturer, after weeks of haggling with KonnectONE's office of general counsel. Here's the link.
File on MEGA
mega.nz
I have three earlier builds as well if anybody needs them.
Now to go root my moxee
What about a twrp ?
Viva La Android said:
I have three earlier builds as well if anybody needs them.
Click to expand...
Click to collapse
how to i flash the stock firmware???
dexscam37 said:
how to i flash the stock firmware???
Click to expand...
Click to collapse
QFIL (Qualcomm Flash Image Loader)
Download Qualcomm Flash Image Loader (QFIL) - Qualcomm Tool
Download Qualcomm Flash Image Loader (QFIL) to flash stock firmware on Qualcomm based Smartphone and Tablets easily in few clicks.
androidmtk.com
You will find a how-to guide in the link I sent. You will need to install the Qualcomm EDL drivers and boot your phone into EDL mode in order to use QFIL. To boot into EDL, hold volume up and down simultaneously while connecting your phone and PC.
I will be posting a full QFIL guide this weekend.

Categories

Resources