HELP! I was trying to re-lock my bootloader so I went into Developer options and turned off the OEM unlocking option, which told me to restart my device. restarting it brought me to the bootloader so I then issued the fastboot.exe flashing lock command and after that I'm getting the message No valid operating system could be found. The device will not boot. what are my options??
dimm0k said:
HELP! I was trying to re-lock my bootloader so I went into Developer options and turned off the OEM unlocking option, which told me to restart my device. restarting it brought me to the bootloader so I then issued the fastboot.exe flashing lock command and after that I'm getting the message No valid operating system could be found. The device will not boot. what are my options??
Click to expand...
Click to collapse
The correct command is fastboot flashing lock. If you can get into bootloader reflash the factory image and it should reboot
If you want to re-lock the bootloader, you need to have a completely stock ROM or have a ROM with a custom avb key flashed. Anything else will show the error you noted.
You should be able to solve this by flashing the stock OTA in recovery mode.
K1nsey6 said:
The correct command is fastboot flashing lock. If you can get into bootloader reflash the factory image and it should reboot
Click to expand...
Click to collapse
I can get into the bootloader, however here I'm seeing the message that the bootloader is already locked! tried flashing the November update, but getting the failed message that I need to be unlocked
craigacgomez said:
If you want to re-lock the bootloader, you need to have a completely stock ROM or have a ROM with a custom avb key flashed. Anything else will show the error you noted.
You should be able to solve this by flashing the stock OTA in recovery mode.
Click to expand...
Click to collapse
when I try to get to recovery mode through the bootloader, it immediately spits me back out to the message that there's no valid operating system and to press the power button to power off
Seems like you messed up and bricked your device try seeing if you can unlock your bootloader still if not contact whoever you got device off and report for warranty
dimm0k said:
when I try to get to recovery mode through the bootloader...
Click to expand...
Click to collapse
FYI, the bootloader is one of the functional recovery modes.
Try the online Google flash tool. This is what I used to flash back to stock after unrooting my device to run some tests. Although in my case, as you're meant to, I performed the flash prior to re-locking the bootloader, so it might not work for you.
Android Flash Tool
flash.android.com
minidude2012 said:
Seems like you messed up and bricked your device try seeing if you can unlock your bootloader still if not contact whoever you got device off and report for warranty
Click to expand...
Click to collapse
NippleSauce said:
FYI, the bootloader is one of the functional recovery modes.
Click to expand...
Click to collapse
Beefheart said:
Try the online Google flash tool. This is what I used to flash back to stock after unrooting my device to run some tests. Although in my case, as you're meant to, I performed the flash prior to re-locking the bootloader, so it might not work for you.
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
unfortunately that was a no go for me as well... tells me I need to unlock to perform any of the functions
that said, any possibility the guys at Ubreakifix would be able to get this fixed?
dimm0k said:
unfortunately that was a no go for me as well... tells me I need to unlock to perform any of the functions
that said, any possibility the guys at Ubreakifix would be able to get this fixed?
Click to expand...
Click to collapse
Unlikely. This now needs a logic board swap I suspect. You can't unlock the bootloader as you toggled the OEM switch in developer options then relocked the bootloader before flashing stock, you can't boot to Android to untoggle that switch to allow another fastboot unlock command because you have a non-stock image installed with a locked bootloader, and you can't flash back to stock.
Sorry to say, your phone appears to be bricked.
Send it back for a warranty swap. The bootloader is listed as being locked, so unless they delve deeper, it's not obvious the end-user is at fault rather than the device simply refusing to boot one day for no apparent reason.
Beefheart said:
Send it back for a warranty swap. The bootloader is listed as being locked, so unless they delve deeper, it's not obvious the end-user is at fault rather than the device simply refusing to boot one day for no apparent reason.
Click to expand...
Click to collapse
should I try sending it back for a warranty swap or would sending it into Google for repairs not be a good idea?
Did you buy it direct from Google? If so that could be an issue, as they're likely going to try to diagnose the fault prior to sending out a replacement, and will discover it's caused by you before refusing a replacement. Where as if you bought it from some a third party vender, they will likely just swap it without any in depth checks.
Beefheart said:
Did you buy it direct from Google? If so that could be an issue, as they're likely going to try to diagnose the fault prior to sending out a replacement, and will discover it's caused by you before refusing a replacement. Where as if you bought it from some a third party vender, they will likely just swap it without any in depth checks.
Click to expand...
Click to collapse
I purchased this from Amazon when they had the $200 Amazon GC offer... they're allowing me to return the phone, but if I were to buy it again from them it would be at full price. for some reason they are not allowing exchanges/replacement. that said, I was exploring if it would be worth sending to Google for a repair... when you say they in the last sentence, are you referring to Google or the third party vendor?
dimm0k said:
I purchased this from Amazon when they had the $200 Amazon GC offer... they're allowing me to return the phone, but if I were to buy it again from them it would be at full price. for some reason they are not allowing exchanges/replacement. that said, I was exploring if it would be worth sending to Google for a repair... when you say they in the last sentence, are you referring to Google or the third party vendor?
Click to expand...
Click to collapse
That's their policy. I bought a Logitech MX Keys for £65 in a UK deal about 10 months ago. When it developed a fault, they offered me a full refund but point blank refused an exchange for a new keyboard, which annoyed me no end as it had gone up to £105 at that point. But it can work the other way around too and you can be the one with the money in your pocket. I've had that happen too.
Beefheart said:
That's their policy. I bought a Logitech MX Keys for £65 in a UK deal about 10 months ago. When it developed a fault, they offered me a full refund but point blank refused an exchange for a new keyboard, which annoyed me no end as it had gone up to £105 at that point. But it can work the other way around too and you can be the one with the money in your pocket. I've had that happen too.
Click to expand...
Click to collapse
damn, that is rather disappointing! that said and from your response, I guess it's better to go and return to Amazon then...
dimm0k said:
damn, that is rather disappointing! that said and from your response, I guess it's better to go and return to Amazon then...
Click to expand...
Click to collapse
The question is, can you use the GC when you purchase another phone?
schmeggy929 said:
The question is, can you use the GC when you purchase another phone?
Click to expand...
Click to collapse
unfortunately Amazon thought of abuse this way and priced it so that the device was $200 less from the get-go and charging $200 for the GC
Doesn’t matter what they say, if the device is in warranty, just write them that the device is damaged. They must replace it.
Related
I want to do this. Is there a way to do so and retain data?
gunnyman said:
I want to do this. Is there a way to do so and retain data?
Click to expand...
Click to collapse
via fastboot...
fastboot oem lock
I don't recall if it factory defaults, as I rarely lock
bootloader locked now won't boot
All I want to do is run the RUU to get it back to stock
gunnyman said:
bootloader locked now won't boot
All I want to do is run the RUU to get it back to stock
Click to expand...
Click to collapse
Download appropriate RUU from https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048 place it on SD card, rename to 2PZCIMG.zip, put SD card into phone, press & hold vol down and power button to boot into download mode and confirm RUU flashing (battery should be over 30 or something %)
[Edited for better description.]
I have twrp still installed recovery won't start and it doesn't boot
gunnyman said:
I have twrp still installed recovery won't start and it doesn't boot
Click to expand...
Click to collapse
I edited my post for better description. You should do what it says there (you need to boot to download mode).
Also relocking bootloader with twrp still installed is a no no
Ok. Thanks. I'm charging phone now I got running ruu exe sorted. Thanks for the push in the right direction
gunnyman said:
Ok. Thanks. I'm charging phone now I got running ruu exe sorted. Thanks for the push in the right direction
Click to expand...
Click to collapse
Np.. Hope you get it sorted.
(the steps I described I described are for sd card method, if there is ruu exe for your variant you should just follow instructions once you start ruu exe on your computer)
I was freaking out because I was getting USB error 170 running the RUU. Got it all sorted out and am back up and running.
gunnyman said:
I was freaking out because I was getting USB error 170 running the RUU. Got it all sorted out and am back up and running.
Click to expand...
Click to collapse
Good to hear :good:
Sorry to hijack the thread but is there any way to unlock bootloader without going through the htcdev method? I believe that the warranty is voided if i unlock my bootloader and the support will not entertain any hardware damage (not caused by me) which is why i wanted to unlock without using htcdev. Any info is appreciated, thanks!
tokenbest said:
Sorry to hijack the thread but is there any way to unlock bootloader without going through the htcdev method? I believe that the warranty is voided if i unlock my bootloader and the support will not entertain any hardware damage (not caused by me) which is why i wanted to unlock without using htcdev. Any info is appreciated, thanks!
Click to expand...
Click to collapse
There isn't at least for now. And in any case until there is s-off even if there was other way it will show as relocked and modified after you lock it again.
there's no sunshine in the sky for now, but warranty is not voided in most countries/cases anyway.
velimircek said:
There isn't at least for now. And in any case until there is s-off even if there was other way it will show as relocked and modified after you lock it again.
there's no sunshine in the sky for now, but warranty is not voided in most countries/cases anyway.
Click to expand...
Click to collapse
Thanks but sadly.. the customer support for HTC Singapore said warranty would be void after unlocking bootloader and any issues would not be covered, seriously though -_- sucks to hear that and making me hesitate on purchasing a U11 currently.
tokenbest said:
Thanks but sadly.. the customer support for HTC Singapore said warranty would be void after unlocking bootloader and any issues would not be covered, seriously though -_- sucks to hear that and making me hesitate on purchasing a U11 currently.
Click to expand...
Click to collapse
I got the same response from HTC Czech Republic: unlocking the bootloader would instantly void my warranty, plus they said that warranty-keeping bootloader unlock is possible only in that one special case for US customers, the rest of the world voids their warranty by doing so :/
Rant on the side: I truly despise not being allowed to get root privileges without voiding the warranty - it is MY device, yet I can't control the system. I want to do MY own backups, control (or inspect) the data apps save to MY phone, and control the configuration of MY system. I really hate being locked out from even such basic configurations as the hosts file is - I'm effectively barred from some aspects of web development so that advertisements can be shoved down my throat
gunnyman said:
bootloader locked now won't boot
All I want to do is run the RUU to get it back to stock
Click to expand...
Click to collapse
How did you get it to relock? i keep getting a failed messaged with the command above.
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
tokenbest said:
Sorry to hijack the thread but is there any way to unlock bootloader without going through the htcdev method? I believe that the warranty is voided if i unlock my bootloader and the support will not entertain any hardware damage (not caused by me) which is why i wanted to unlock without using htcdev. Any info is appreciated, thanks!
Click to expand...
Click to collapse
Right now it's only with the 175 USD XTC2Clip with all the attachments including the power adapter - and as of my last look, it cannot factory lock the bootloader thanks to temporary S-OFF so it will show up as relocked which will void the warranty anyway. In other words, we are all out of luck for now.
And it remains to be seen if HTC actually lets us keep our warranty in the US... The warranty in the box says otherwise.
EtherealRemnant said:
Right now it's only with the 175 USD XTC2Clip with all the attachments including the power adapter - and as of my last look, it cannot factory lock the bootloader thanks to temporary S-OFF so it will show up as relocked which will void the warranty anyway. In other words, we are all out of luck for now.
And it remains to be seen if HTC actually lets us keep our warranty in the US... The warranty in the box says otherwise.
Click to expand...
Click to collapse
175.00, S-off is not that important. Like you said a relocked bootloader voids your warranty. Why are people bothering to relock bootloader especially the OP to run the RUU, it is not needed. You do mention XTC2Clip a lot in these threads. You holding stock in the company? lol
schmeggy929 said:
175.00, S-off is not that important. Like you said a relocked bootloader voids your warranty. Why are people bothering to relock bootloader especially the OP to run the RUU, it is not needed. You do mention XTC2Clip a lot in these threads. You holding stock in the company? lol
Click to expand...
Click to collapse
Hell no, I have no interest in dropping another 175 bucks, I think it's ridiculous but it is currently the only way to do a number of things with the device. I'd consider it if being able to unlock and relock the phone without HTC ever having a clue was a big deal or there was a Google edition and I needed to change the CID and MID or other things but honestly, I still have my 10 if I really need to get at something that was on that phone but not on this one (for example my Battle.net authenticator). I suppose I could always try Helium though with my desktop but I imagine that's a protected app like Google Authenticator which required root to backup and why I switched to Authy.
I mentioned the XTC2Clip because it is the only way to get S-OFF of any kind right now and to point out that even with its temp S-OFF, it still can't restore the bootloader to factory locked status. It's an important thing to point out, not everyone knows that HTC has two different locked statuses, one that proves the phone has been tampered with, and one that is factory locked. A lot of people ask to go back to stock so they can send it in for a warranty claim or a refund to go buy another device. The relocked bootloader obviously kills one or both options depending on the situation.
EtherealRemnant said:
Right now it's only with the 175 USD XTC2Clip with all the attachments including the power adapter - and as of my last look, it cannot factory lock the bootloader thanks to temporary S-OFF so it will show up as relocked which will void the warranty anyway. In other words, we are all out of luck for now.
And it remains to be seen if HTC actually lets us keep our warranty in the US... The warranty in the box says otherwise.
Click to expand...
Click to collapse
schmeggy929 said:
175.00, S-off is not that important. Like you said a relocked bootloader voids your warranty. Why are people bothering to relock bootloader especially the OP to run the RUU, it is not needed. You do mention XTC2Clip a lot in these threads. You holding stock in the company? lol
Click to expand...
Click to collapse
Does it void warranty? I returned my bootloader relocked U11 to HTC due to a scratch on the display. Was offered a refund or exchange. I had to go the refund route to swap colours ( I went from Black to Blue). Was accepted without any fuss.
Galactus said:
Does it void warranty? I returned my bootloader relocked U11 to HTC due to a scratch on the display. Was offered a refund or exchange. I had to go the refund route to swap colours ( I went from Black to Blue). Was accepted without any fuss.
Click to expand...
Click to collapse
Yeah, a lot of people are claiming unlocked bootloader voids warranty now, however US is more relaxed. Every single HTC phone I had was returned with Unlocked Bootloader and S-off, never had a problem. Other countries are more strict I guess. I can understand not knowing the return policy and people relock for that reason(for returns) but I see many relocking for flashing RUU or firmware. This is not needed or even should be done. I'm a RUU flasher with each update, so I know no problems arise. This has been the case for the last 8,9 or 10 phones lol.
I lock bootloader on Verizon Google Pixel when my device have TWRP and i have brick! Device Loading up to logo Google on 1 sec and reboot. Fastboot work, but i don't unlock bootloader. In recovery is don't enter. Please help me!
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
kkjb said:
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
Click to expand...
Click to collapse
There is still no solution to this problem? ((
Unlock again.
lafester said:
Unlock again.
Click to expand...
Click to collapse
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
Put the phone in fastboot mode, then run `fastboot flashing unlock` from a PC. If it says unlocking not allowed, you're out of luck, it's a brick now. Never lock your phone without being 100% stock on both slots
Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
lafester said:
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
Click to expand...
Click to collapse
In this topic https://forum.xda-developers.com/pi...bootloader-t3540772/post77016940#post77016940 man has unbrick Pixel XL, but i think that method will work on Pixel.
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.
So, I have a Moto G9 Power, and I unlocked the bootloader to fool around with root access. Then I realised, that root access wasn't all that powerful as it was on older Android versions.
You simply do not have access to the root partition on Android 10, it is mounted read-only, and it ignores all commands to remount it as read-write.
Also, the location of the Boot animation zip of this phone is wierd, it is in /product/media, not /system/media, which effectively renders all Boot animation Magisk modules or apps useless.
Plus, the battery drain once unlocked and rooted was so much more than when on stock. And other stupid idiosyncrasies made being root not all that powerful.
So I decided to un-root and relock the bootloader.
The thing is, when it was stock, in fastboot mode, it showed
Code:
oem_locked
Now after relocking it by
Code:
fastboot oem lock
it shows
Code:
flashing_locked
I'm pretty sure the difference between the two is enough for the service center to deny my warranty (which I voided by unlocking it in the first place, I know, I know. But reverting back to stock should make the service guys not notice) if something happened to the phone.
Is there any way I can get the original message back? Am I permanently screwed? Please respond, anyone.
mistersmee said:
So, I have a Moto G9 Power, and I unlocked the bootloader to fool around with root access. Then I realised, that root access wasn't all that powerful as it was on older Android versions.
You simply do not have access to the root partition on Android 10, it is mounted read-only, and it ignores all commands to remount it as read-write.
Also, the location of the Boot animation zip of this phone is wierd, it is in /product/media, not /system/media, which effectively renders all Boot animation Magisk modules or apps useless.
Plus, the battery drain once unlocked and rooted was so much more than when on stock. And other stupid idiosyncrasies made being root not all that powerful.
So I decided to un-root and relock the bootloader.
The thing is, when it was stock, in fastboot mode, it showed
Code:
oem_locked
Now after relocking it by
Code:
fastboot oem lock
it shows
Code:
flashing_locked
I'm pretty sure the difference between the two is enough for the service center to deny my warranty (which I voided by unlocking it in the first place, I know, I know. But reverting back to stock should make the service guys not notice) if something happened to the phone.
Is there any way I can get the original message back? Am I permanently screwed? Please respond, anyone.
Click to expand...
Click to collapse
As far as I know anything with custom unlocks voids warranties the thing is that message likely changes to keep people from changing it back, I'm not sure what type of checks they do or how much your providers know about the device you have but considering they don't care as long as its relocked when you turn it in you may be alright. Its not like it couldn't be unlocked by them for various other reasons like flashing stock fw if it need to be fixed in that form unless they have someway of restoring that message themselves someone on our end would have to replicate it and that would take some dedicated development to do so.
Mr.Conkel said:
As far as I know anything with custom unlocks voids warranties the thing is that message likely changes to keep people from changing it back, I'm not sure what type of checks they do or how much your providers know about the device you have but considering they don't care as long as its relocked when you turn it in you may be alright. Its not like it couldn't be unlocked by them for various other reasons like flashing stock fw if it need to be fixed in that form unless they have someway of restoring that message themselves someone on our end would have to replicate it and that would take some dedicated development to do so.
Click to expand...
Click to collapse
Oh. Ok, cool. Cheers, mate, thanks!
mistersmee said:
Oh. Ok, cool. Cheers, mate, thanks!
Click to expand...
Click to collapse
I mean Motorola G Power devices are fairly popular here, wait around and keep an eye on your devices thread considering it can be unlocked with enough time you should be given a custom rom like LOS or Crdroid. The G7 power has tons of custom access as well as other G series device from Motorola so it is very likely to get something, which would very likely enable the custom access your looking for with modifications as it will be built normally.
Cheers!
Many Android devices set a "tampered" flag - which is responsible for voiding warranty of the devices - within the bootloader what can get queried by service centers.
jwoegerbauer said:
Many Android devices set a "tampered" flag - which is responsible for voiding warranty of the devices - within the bootloader what can get queried by service centers.
Click to expand...
Click to collapse
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?
Mr.Conkel said:
I mean Motorola G Power devices are fairly popular here, wait around and keep an eye on your devices thread considering it can be unlocked with enough time you should be given a custom rom like LOS or Crdroid. The G7 power has tons of custom access as well as other G series device from Motorola so it is very likely to get something, which would very likely enable the custom access your looking for with modifications as it will be built normally.
Cheers!
Click to expand...
Click to collapse
Will do.
mistersmee said:
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?
Click to expand...
Click to collapse
IDK.
jwoegerbauer said:
IDK.
Click to expand...
Click to collapse
Ok, cool. I'll search around.
mistersmee said:
That makes sense, hence why the message changed. Is there a way to remove that tampered flag? I know that older Samsung devices had a flash counter, which could be reset back to zero. Maybe something similar?
Click to expand...
Click to collapse
No nothing like that for Moto devices.
Generally, Motorola doesn't enforce the voided warranty issue.
If the device has a factory flaw and still would be under warranty, they will cover it.
At least this is based on posts on the forum.
sd_shadow said:
No nothing like that for Moto devices.
Generally, Motorola doesn't enforce the voided warranty issue.
If the device has a factory flaw and still would be under warranty, they will cover it.
At least this is based on posts on the forum.
Click to expand...
Click to collapse
Oh. Ok, that's a relief.
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.