Related
Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.
The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse
i get a message saying "cant update from sd card?"
yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard
Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.
JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse
Want to buy this phone. Need it rooted to do a couple things. Has anybody gotten TWRP and root on it yet?
You can root it by first unlock the bootloader then install magisk via patch boot image method.
How should I get the boot image to actually use that method?
You can download the firmware here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/
Inside zips, find boot.img
Does anyone know anything about custom recovery TWRP yet that's what I'm looking for
there is no custom recovery
ahalol said:
You can root it by first unlock the bootloader then install magisk via patch boot image method.
Click to expand...
Click to collapse
What is the way to unlock the bootloader? I don't believe Motorola officially released it for the phone yet. Have you rooted this phone?
Thereplierbro said:
What is the way to unlock the bootloader? I don't believe Motorola officially released it for the phone yet. Have you rooted this phone?
Click to expand...
Click to collapse
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
wraith1932 said:
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
Click to expand...
Click to collapse
Does the Verizon one have a greyed out "OEM Bootloader unlock"
Because I bought one off offer up that had the button available but it was purchased from Verizon
Also I asked Motorola for the unlock website an they said they haven't released it yet for Moto z4
Can't say for sure myself, I got the carrier unlocked version. But I believe that button in the options is there no matter what, I remember it on my original Z Force Droid (Verizon only version, no bootloader unlock, official or not).
I would bet that, if it was bought at Verizon, then there won't be a bootloader unlock available - ever.
Dunno what that last part is supposed to mean... Never saw a device-specific Moto Bootloader Unlock page, going all the way back to the original Moto X. There's the page explaining the unlock process, a disclaimer ("anything you do from here isn't our fault, or responsibility to fix" basically), and a link to the next step (with a "log in to Moto" in between). After login, it brings you to instructions to get a code to put in, and the button to check if the device is eligible for unlocking the bootloader.
I would include a link to the first page if I could. Almost there, just one more post...
wraith1932 said:
Official unlock from Motorola is available, as long as you aren't referring to the Verizon version.
Click to expand...
Click to collapse
wraith1932 said:
Can't say for sure myself, I got the carrier unlocked version. But I believe that button in the options is there no matter what, I remember it on my original Z Force Droid (Verizon only version, no bootloader unlock, official or not).
I would bet that, if it was bought at Verizon, then there won't be a bootloader unlock available - ever.
Dunno what that last part is supposed to mean... Never saw a device-specific Moto Bootloader Unlock page, going all the way back to the original Moto X. There's the page explaining the unlock process, a disclaimer ("anything you do from here isn't our fault, or responsibility to fix" basically), and a link to the next step (with a "log in to Moto" in between). After login, it brings you to instructions to get a code to put in, and the button to check if the device is eligible for unlocking the bootloader.
I would include a link to the first page if I could. Almost there, just one more post...
Click to expand...
Click to collapse
All other phones, if the button is not greyed out and you can press the option (and it asked for your password) then it's unlockable. I know because I got a few freaking pixel phones with non usable Bootloader. Wasted about $1,000 looking for a cellphone to use with Sprint that I can root. Every one of them is Verizon.
https://support.motorola.com/us/en/solution/ms87215
DM Verity disabled too?
What about DM verity? Has anyone figured out how to disable that? I need to add a couple of lines to the build.prop file, but can't seem to change the write permissions even with root; any edits made directly on the phone using an editor with root permissions, don't persist after a system reboot. Edits made to the build.prop file externally, and pushed pre-boot via ADB, result in boot loop due to DM verity failing.
(For clarity, I do not have this phone, yet, I have a Z2 Play, but I faced these challenges with that device too)
Jade Eyed Wolf said:
What about DM verity? Has anyone figured out how to disable that? I need to add a couple of lines to the build.prop file, but can't seem to change the write permissions even with root; any edits made directly on the phone using an editor with root permissions, don't persist after a system reboot. Edits made to the build.prop file externally, and pushed pre-boot via ADB, result in boot loop due to DM verity failing.
(For clarity, I do not have this phone, yet, I have a Z2 Play, but I faced these challenges with that device too)
Click to expand...
Click to collapse
I hope a real dev jumps on board to this cellphone. It's pretty decent for what it is honestly
Thereplierbro said:
I hope a real dev jumps on board to this cellphone. It's pretty decent for what it is honestly
Click to expand...
Click to collapse
One of my main reasons for waiting to get one
Jade Eyed Wolf said:
One of my main reasons for waiting to get one
Click to expand...
Click to collapse
It's basically useless until then
Could I get a little guidance on how to patch and flash the boot image? I have ADB/Fastboot setup as well as the XT1980-4 firmware downloaded.
Do I just place the boot.img file on my phone, patch it in Magisk Manager, and flash with fastboot? Anything I need to be careful of?
Also, how should I go about backups here? I've only messed with this stuff when I had a Galaxy S4, everything was super simple with easy bootloader unlock and custom recovery.
battleof3 said:
Could I get a little guidance on how to patch and flash the boot image? I have ADB/Fastboot setup as well as the XT1980-4 firmware downloaded.
Do I just place the boot.img file on my phone, patch it in Magisk Manager, and flash with fastboot? Anything I need to be careful of?
Also, how should I go about backups here? I've only messed with this stuff when I had a Galaxy S4, everything was super simple with easy bootloader unlock and custom recovery.
Click to expand...
Click to collapse
What you said was correct. That's how you patch and flash. Nothing particular to be careful. The only thing would be in order to receive future OTA, you should not modify you /system and /vendor partition during your use of the phone.
ahalol said:
What you said was correct. That's how you patch and flash. Nothing particular to be careful. The only thing would be in order to receive future OTA, you should not modify you /system and /vendor partition during your use of the phone.
Click to expand...
Click to collapse
Dug a little deeper and bootloader is locked tight, no flashing for me. Returning and buying a secondhand LG V30 for cheap. It's unfortunate that carriers love their walled gardens.
See, this is why I was asking about DM Verity. You need to disable that first before flashing anything via ADB/Fastboot.
With DM Verity on, at system startup, the device generates a hash of the /system and /root directories. If the hash does not match the one from the factory, due to changes pushed via ADB or Fastboot or patching other system files with something different, the system reboots, again and again.
I had this same issue with my Z2 Play, which is why I brought it up here.
Rooting these devices is useless, unless you also disable DM Verity.
I tried to follow this method and ended up flashing the wrong boot image (I did go to the right software variant but it was outdated) so i had to go through and try all the images they had and none of them worked so i had to look elsewhere.
After some digging i found a VERY handy tool made by lenovo themselves that lets you update and recover the firmware.
If you use the rescue option and enter your phones info (it seems to verify your phones info so you can only download for devices you have) and it'll download the latest zip for you so you can get the boot image.
Here's the link to the smart assistant
TL;DR Open smart assistant, click flash, click "Go rescue", Click "Moto Phone", enter your phone's info (make sure your phone is connected in fastboot mode), click the download icon next to the file name.
Make sure you DO NOT click the rescue button when the download is finished as that will factory reset your phone, just copy the zip or boot image and close it
Hello Guys,
long i searched for a method of unlocking the bootloader of eml-l29 Huawei P20. No i didnt find any, and qu1ckr00t didnt prove to be useful either.
it is not relevant anymore. since i did use testpoint too often in research of what is possible and what not, the device died just a few minutes ago. it always enters now only the usb huawei com mode. probably i used to much pressure on the testpoints or what or i accidentally short circuited other points with the screwdrivers.. but as a matter of fact, it is hardware bricked and the board is done for i think. so i dont search for a solution anymore.
people, see this thread as a resource what is possible without unlocking the bootloader and what not. i figured out following things are fact without unlocking the bootloader, so that you all doesn't have to try instead of me:
- you can flash with the testpoint short circuited and the software dc-phoenix and the right chipset/cpu bootloader chosen in temporary bootloader the twrp to erecovery_ramdisk and recovery_ramdisk, it will be permanently available after the process
- you cannot install magisk on it, since xloader seems to block the bootup and always sends you to recovery-mode (which means twrp if you flashed this)
- you cannot install a custom rom like OpenKirin with the testpoint recovery mode, as it - like with magisk, always will send you to recovery mode - i tried it exactly how it is explained on openkirin.net and it always turned out the same
- there is no bootloader unlock code in the nvme partition, i checked it - it seems there is encryption going on there
- the exploit qu1ckr00t is not usable, since the kernel is compiled with spinlock_debug
- and i forgot first: if you have the idea of soldering a cable for testpoint short circuit - no, letit be. you will only hang forever in huawei usb com 1.0 mode - it wont boot normally as long as you're in tp mode
so basically, there is way to get root, it is a way to get to direct data from the partitions. but at the end, the question that arises is - how much profit are you gaining from root or custom roms on this device at the end? in my case, the many tries costed my time, my nerves and now the device itself. it is gone for good. maybe this is for the best, as i never treated it right since i bought it (it had to be repaired two times in 2 years, which is a lot for a normal device at this amount of time) and i only have bad memories in my life with it (lots of things happened, but this is not the right place for such tellings).
my final message for this part of this board (not the board i damaged thou) - leave it alone, don't waste your time anymore on this. move on, there are cheap devices that are better, faster and unlockable too at this day and time. i moved on to my new Nokia 7.2, which is awesome.
so stay healthy guyz.
my journey of exploring the depths of huaweis device huawei p20 eml-l29 ends here. its sad, but at the same time i'm happy that the "horror" of an unlockable bootloader is finally over.
Thanks for your effort and sharing the info. Good luck with new phone
Note: my next phone won't be Huawei, for sure, due to bootloader locking, I am fed up with them
Yes,
I even have no sorry with them if they go down because of the Google lockout. Their strategy is to pull people away from Google PlayStore? Yes, sure. Good luck.
Unlock bootloader and promise to keep it open for P10 upwards and we are happy. Otherwise... byebye and fcku.
FearFac said:
Thanks for your effort and sharing the info. Good luck with new phone
Note: my next phone won't be Huawei, for sure, due to bootloader locking, I am fed up with them
Click to expand...
Click to collapse
What if I have my unlock code? Can I still unlock it or it's impossible now? I requested my code before they stop the bootloader unlocking, but never did anything with it.
ElChe said:
What if I have my unlock code? Can I still unlock it or it's impossible now? I requested my code before they stop the bootloader unlocking, but never did anything with it.
Click to expand...
Click to collapse
You are the lucky one who can root your phone.
FearFac said:
You are the lucky one who can root your phone.
Click to expand...
Click to collapse
Yeah I guess haha. I haven't got around doing it yet. But now I know it's a possibility! So I'll eventually do it!
FearFac said:
You are the lucky one who can root your phone.
Click to expand...
Click to collapse
How do you root it? AFAIK anything newer than EMUI8 is no longer rootable.
I'm on EMUI 10, with an unlocked bootloader, please tell me how to root.
zgomot said:
How do you root it? AFAIK anything newer than EMUI8 is no longer rootable.
I'm on EMUI 10, with an unlocked bootloader, please tell me how to root.
Click to expand...
Click to collapse
I do a query you have emui 10 with bootloader open?how did you do it ?it was not the problem that emui 10 closed the bootloader?can't root with magisk?
zgomot said:
How do you root it? AFAIK anything newer than EMUI8 is no longer rootable.
I'm on EMUI 10, with an unlocked bootloader, please tell me how to root.
Click to expand...
Click to collapse
Where did you get this info from?
I was just thinking of rooting my CLT L09 Emui 9.1.0
So you got the Edge S and want GApps? Basically you unlock your bootloader, root with Magisk, then install MagiskGApps.
DISCLAIMER: UNLOCKING YOUR BOOTLOADER MAY VOID YOUR WARRANTY, AND DOING ALL THESE THINGS IN THIS GUIDE MAY RESULT IN DAMAGE/BRICKING YOUR PHONE. I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. PROCEED AT YOUR OWN RISK.
1. Unlock the bootloader: that should be doable with their global bootloader unlock website here.
2. Download Lenovo Motoroa Smart Assistant (Rescue and Smart Assistant), and follow its instructions to "rescue" your device. It will lead you to boot into bootloader mode and download the firmware. Find the firmware file via the LMSA's downloads (should have a "show folder" button). You'll need the boot.img file for Magisk.
3. Download Magisk, then follow its instructions. You'll have to copy the boot.img to your device, then use Magisk to patch the boot file, then copy the modified one to your PC.
4. You'll need fastboot. If you don't have it already, you can download the Android SDK platform tools here. Then go into the folder, Shift+Right Click the folder, then "Open Command Prompt" or "Open PowerShell," you should have something close to one of those two. Copy your Magisk modified .img file to that folder, then you'll want to input:
fastboot flash boot [modified .img file]
Once that completes, you should see in large text, "Start" on your phone next to the power button. Press the power button, and it should boot, and you should have root now.
5. Download MagiskGApps to your phone, open Magisk on your phone, click the button that looks like a puzzle piece at the bottom of the screen, "Modules." Click "Install from storage," locate the MagiskGApps file, and install it. After that it will ask you to restart your phone, do that, then you'll just have to be patient as it takes time once its restarted to load everything. You also may need to update some or all of the apps, then you should be able to use the notification to finish setting up the phone with Google Setup.
Thanks to Motorola for making it easy to unlock their bootloaders
Thanks to the whole Magisk team for making an easy, awesome root (and more!)
Thanks to Wacko1805 (and team?) for making MagiskGApps. This is really awesome.
unlock the BL and get root is will make some apps fingerprint and face ID fail?
kimker said:
unlock the BL and get root is will make some apps fingerprint and face ID fail?
Click to expand...
Click to collapse
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
HopelesRomantc91 said:
Magisk has a "Magisk Hide" which will allow it to pass SafetyNet, and most things which check on device security will think the device is secure. But unlocking BL and rooting does make the device less secure, and therefore incurs its own risks apart from bricking or damaging the device.
Click to expand...
Click to collapse
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
kimker said:
yes, i knew the unlock and root will take risk.. but not sure is Payment business apps using fingerprint will work normal.
Click to expand...
Click to collapse
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
HopelesRomantc91 said:
Google Pay works. But according to the Motorola website you should be able to relock the bootloader if yours doesn't work. But there's never any guarantee. If you need your device secure, recommend don't unlock bl or root, or wait to see if there's a root option without bootloader unlock that can be easily undone.
Click to expand...
Click to collapse
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
That's not good. Hopefully they can restore it back somehow. With this guide to unlock and flash gapps why would you need to flash G100 though? This seems to be itright now without one of rom developer's releases to get root & apps. For me this is all i would look for. Titanium backup on it and restore.. done until PE rom comes out.
kimker said:
I saw that someone’s edge s had unlocked the BL and Flash G100 firmware and everything worked normally, and then tried to lock the BL again, but it was unsuccessful and the system could not start. The flashing tool does not recognize the machine.
Click to expand...
Click to collapse
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
thank you. They did not ask for help. It seems that the lock BL is a self-verification switch, and then performs a verification system integrity.
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
kischde said:
Mine doesn't let me unlock its BL. I've got unlock code from moto and did a factory reset with SIM card in slot 1. After enabling developer mode and debugging the switch still is greyed out. So no chance to unlock it.
Has anyone got an idea what to try now?
Moto support answered yesterday to my request but also no solution since I told them that it doesn't work
Device is not branded. I got it from Amazon so no provider branding.
If this won't be able to be unlocked and rooted I'll have to return it and switch to a Google Pixel.
Click to expand...
Click to collapse
I had the same issue, you need to factory reset WITH your sim card in the phone, this will let you open the OEM unlock slide thing in the dev mode.
Then once its done you can fastboot and unlock the bootloader.
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
kischde said:
I did so, maybe I explained not so well. SIM was inserted and then I did factory reset by starting it from settings. After restart it's still the same - switch / unlock slider greyed out.
Click to expand...
Click to collapse
On my OG Pixel XL, I had to wait 7 days for the slider to become normal. By the time I got around to do it on the Edge S it was about the same time.... could be related
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
kischde said:
Now as you said that I remember that thingy with another device. Maybe a Xiaomi I think... With that I had to wait several days until the unlock code was delivered.
But there was a message, too, when trying to get it sooner, which said you needed to wait some more time.
Not sure if it's the the same for Moto devices? Then again, when thinking that you experienced the same with a Pixel, too...
Did anyone else make such an experience with his/her g100?
Click to expand...
Click to collapse
Make sure your on the latest OTA, Lenovo made a mistake on previous versions with the OEM Unlocking function not being enabled. They fixed it in latest ota.
RSA tool said the file I uploaded yesterday is the latest one available (and it's exactly the same as the installed version).
The device was released just a few days ago in Europe. Perhaps they fixed the unlock switch in other regions and still need to fix it in Europe..
Will wait until weekend if they come up with a solution. If not I'm afraid I have to return the device as I need it personally AND professionally, too - I'm field agent, so.... :/
HopelesRomantc91 said:
I would think yes, if you flash different firmware, locking the BL would likely cause problems. It's very difficult to do anything w/o unlocked bootloader, except sometimes rooting is doable. That's pretty much the behavior I expect. If they come to this subforum, we might be able to help.
Click to expand...
Click to collapse
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
kimker said:
The poor guy whose phone turned bricks went to the after-sales department of moto, and the answer was that he needed to replace the phone motherboard. .
Click to expand...
Click to collapse
Ouch...
kimker said:
I'm curious,If you unlock and flash other firmware and then flash back to the original firmware, can it be locked again?
Click to expand...
Click to collapse
I would assume so, but I don't really know why anyone would want to relock.
Hi, i am looking more styles for EdgeLighting. before, we could use EdgeLighting+ but now its not working on android 12.
there is an app called muviz edge that contains excellent styles but app does not work properly. so i am looking for a better app for replacing edgelighting+ with beautiful styles.
can we install S21 or something else edge lighting app on our A51?
do you have any recommended app?
Funny thing is, your phone already has all the edge lighting effects built in, the only problem is that there is a specific file called floating_feature that's missing one text line that would make all those extra edge lighting effects appear
So to answer your question, to get more styles for edge lighting you need to root your phone and edit the following file:
system/etc/floating_feature.xml
And add the following line inside the features:
<SEC_FLOATING_FEATURE_SYSTEMUI_CONFIG_EDGELIGHTING_FRAME_EFFECT>frame_effect</SEC_FLOATING_FEATURE_SYSTEMUI_CONFIG_EDGELIGHTING_FRAME_EFFECT>
Save, reboot and your phone should now have all the effects available that Samsung enables on their flagship phones.
And before you ask, no, there is no way to do this without root.
Tnx, but with root, secure folder will be disabled. and i cant root my phone.
in android 10 We could install edgelighting+ that installs additional styles. (without root).
so Did EdgeLighting+ somehow edit this file?
mahdi72 said:
Tnx, but with root, secure folder will be disabled. and i cant root my phone.
in android 10 We could install edgelighting+ that installs additional styles. (without root).
so Did EdgeLighting+ somehow edit this file?
Click to expand...
Click to collapse
I have no clue. But as you said, edge lighting+ no longer works so on newer Android versions, rooting is your only choice.
ShaDisNX255 said:
I have no clue. But as you said, edge lighting+ no longer works so on newer Android versions, rooting is your only choice.
Click to expand...
Click to collapse
Can i Edit Stock Rom in Linux (add Floating_Feature, remove apps, add new apps) and flash it in my A51 phone?
Do I need root to install this modified rom?
mahdi72 said:
Can i Edit Stock Rom in Linux (add Floating_Feature, remove apps, add new apps) and flash it in my A51 phone?
Do I need root to install this modified rom?
Click to expand...
Click to collapse
You will need to root, yes. Since you will edit it, it will lose Samsung's trusted signature and will therefore count as a custom ROM
ShaDisNX255 said:
You will need to root, yes. Since you will edit it, it will lose Samsung's trusted signature and will therefore count as a custom ROM
Click to expand...
Click to collapse
As far as I have researched, it does not seem to require root, but we have to open the bootloader or OEM Option in Developer Mode.
People are also talking about a tool called Odin Patched, which can bypass some verifications.
Is it possible to flash only the edited CSC file with this tool? Sorry to take up your time
mahdi72 said:
As far as I have researched, it does not seem to require root, but we have to open the bootloader or OEM Option in Developer Mode.
People are also talking about a tool called Odin Patched, which can bypass some verifications.
Is it possible to flash only the edited CSC file with this tool? Sorry to take up your time
Click to expand...
Click to collapse
Hey no worries, XDA is meant for a place to learn and I'm happy to try and help/educate in any way I can.
Opening the bootloader is step 1 in getting root access. You may think that root is the equivalent of installing Magisk and that's what root is but it's a lot more than that. By installing something custom you've in some way obtained root access by editing your stock ROM.
But anyway, going back to your original question/answer, the patched Odin can only bypass some verifications on Odin's side but it can't bypass the verification that the phone does itself. The patched Odin is mainly for installing U firmware on U1 variants and vice-versa, something that you can't do on the original Odin. It can't really bypass checking the validity of Samsung's signature on stock firmware. Even if it could bypass that check, the phone also checks the firmware it's being installed so it will detect it as a custom fw file
So, long story short, if you edit stock FW with any tool it will break Samsung's trusted signature and both phone and Odin will pick it up as a custom firmware (i.e. custom ROM) and you will only be able to install it by unlocking the bootloader. Flashing anything custom will break/trip Knox and it will be broken forever
Let me know if you have any more questions I can help you with.
ShaDisNX255 said:
Hey no worries, XDA is meant for a place to learn and I'm happy to try and help/educate in any way I can.
Opening the bootloader is step 1 in getting root access. You may think that root is the equivalent of installing Magisk and that's what root is but it's a lot more than that. By installing something custom you've in some way obtained root access by editing your stock ROM.
But anyway, going back to your original question/answer, the patched Odin can only bypass some verifications on Odin's side but it can't bypass the verification that the phone does itself. The patched Odin is mainly for installing U firmware on U1 variants and vice-versa, something that you can't do on the original Odin. It can't really bypass checking the validity of Samsung's signature on stock firmware. Even if it could bypass that check, the phone also checks the firmware it's being installed so it will detect it as a custom fw file
So, long story short, if you edit stock FW with any tool it will break Samsung's trusted signature and both phone and Odin will pick it up as a custom firmware (i.e. custom ROM) and you will only be able to install it by unlocking the bootloader. Flashing anything custom will break/trip Knox and it will be broken forever
Let me know if you have any more questions I can help you with.
Click to expand...
Click to collapse
Thank you, now many things are clear.
I want to know if unlocking the bootloader is worth it?
I have no problem with the warranty, I have the phone for more than 2 years and Samsung has no after sales service in our country. But for me, the use of banking app, Secure Folder, Samsung Pass are very important.
Is there a way to make all these apps work without problems by unlocking the bootloader?
Surely the OTA updates will also fail with this work, right?
can i unlock bootloader, flash edited files and relock bootloader?
mahdi72 said:
But for me, the use of banking app, Secure Folder, Samsung Pass are very important.
Click to expand...
Click to collapse
Some banking apps are harder to trick than others. I have no problems hiding root from my banking app but I've seen others struggle to hide from theirs, can't really comment on it. Secure Folder has a fix in Android 12 so it should be able to be fixed. Samsung Pass is something that still has no fix as far as I know so if you decide to root/blow knox fuse, this will never work again even if you lock your bootloader again. I've made my change to Google Pass which works with root so Samsung Pass isn't important to me anymore.
mahdi72 said:
Surely the OTA updates will also fail with this work, right?
Click to expand...
Click to collapse
This is correct, OTA updates stop working when you unlock your bootloader but if you re-lock your bootloader, you may get OTA updates again.
mahdi72 said:
can i unlock bootloader, flash edited files and relock bootloader?
Click to expand...
Click to collapse
No, this will lock your phone. Once you edit anything with root or install a custom fw (rom) then it will always count as custom for the phone. If you lock your bootloader while you have custom fw installed, your phone will be stuck in download mode telling you that your phone has custom fw and will refuse to boot until you flash stock fw.
Thank you very much for your very detailed explanation
So, for this part, I need Magisk, which probably Hide all banking apps in Iran
ShaDisNX255 said:
Some banking apps are harder to trick than others. I have no problems hiding root from my banking app but I've seen others struggle to hide from theirs, can't really comment on it.
Click to expand...
Click to collapse
According to your explanation, This is my decision: I can unlock the bootloader and flash the modified ROM (I can apply the necessary fixes for Secure Folder and other changes to the ROM (Can i?)). The only thing I miss is the Samsung Pass feature, which I can replace with Google Pass, OTA updates can be ignored and do not have much priority for me.
The only important thing is the banking apps.
When the bootloader is unlocked, is the root status rooted or un-rooted? Because I feel that some banking apps only check root access and have nothing to do with bootloader (At least in Iran).
If the root status has not changed after Unlocking the bootloader (I think the root status changes after installing Magisk or SU) I think that I can do the above steps and reach my goal
mahdi72 said:
This is my decision: I can unlock the bootloader and flash the modified ROM (I can apply the necessary fixes for Secure Folder and other changes to the ROM (Can i?))
Click to expand...
Click to collapse
You can, yeah.
mahdi72 said:
When the bootloader is unlocked, is the root status rooted or un-rooted?
Click to expand...
Click to collapse
With unlock bootloader alone it's still un-rooted
mahdi72 said:
When the bootloader is unlocked, is the root status rooted or un-rooted? Because I feel that some banking apps only check root access and have nothing to do with bootloader (At least in Iran).
If the root status has not changed after Unlocking the bootloader (I think the root status changes after installing Magisk or SU) I think that I can do the above steps and reach my goal
Click to expand...
Click to collapse
This is where it can get a little tricky and depends on each app because it's not a standard. If your banking app checks if your bootloader is unlocked then you pretty much need Magisk to hide your bootloader unlocked. Without Magisk, any app will be able to check that you have an unlocked bootloader
If your bank app checks to see if you have Magisk only then you can certainly avoid having to flash Magisk if you're not going to use it anyway
If your bank apps checks safetynet then you will again need to flash Magisk and flash a patch to pass safetynet tests
Again, it's not a standard so it all depends on the bank app in question. You can certainly try to unlock your bootloader and stay in stock and check if your bank apps detects your unlocked bootloader. Just unlocking bootloader shouldn't blow knox yet.
ShaDisNX255 said:
You can, yeah.
With unlock bootloader alone it's still un-rooted
This is where it can get a little tricky and depends on each app because it's not a standard. If your banking app checks if your bootloader is unlocked then you pretty much need Magisk to hide your bootloader unlocked. Without Magisk, any app will be able to check that you have an unlocked bootloader
If your bank app checks to see if you have Magisk only then you can certainly avoid having to flash Magisk if you're not going to use it anyway
If your bank apps checks safetynet then you will again need to flash Magisk and flash a patch to pass safetynet tests
Again, it's not a standard so it all depends on the bank app in question. You can certainly try to unlock your bootloader and stay in stock and check if your bank apps detects your unlocked bootloader. Just unlocking bootloader shouldn't blow knox yet.
Click to expand...
Click to collapse
thank you so much Now everything became clear to me