I bought a Moto Z Play off of Swappa and it's arriving on Tuesday. I wanted to double check that the bootloader's locked to make sure that it wasn't loaded with any kind of keylogging software. The seller had photos of it still in the original packaging, but I'm paranoid, so I just wanted to make sure. If I do the volume down + power button method to go into fastboot, how will I know if the bootloader's unlocked? I've seen a few photos of the fastboot screen, and none of them seemed like they had that info.
If the bootloader ist unlocked you should see a warning screen for 5 seconds immediatly after starting the phone.
Edit: i found this in the OnePlus Forum:
"You can also type this command : fastboot oem device-info
if you see the word : true instead o false near the result, that means you're phone is or have been unlocked"
the easyest way is to see if you getting 5 second warning on boot
Anyone else know where the info would be on the fastboot screen?
Xecu said:
If the bootloader ist unlocked you should see a warning screen for 5 seconds immediatly after starting the phone.
Edit: i found this in the OnePlus Forum:
"You can also type this command : fastboot oem device-info
if you see the word : true instead o false near the result, that means you're phone is or have been unlocked"
Click to expand...
Click to collapse
Where do I use that command? On the fastboot screen? I know there's a dial code I can use to check the bootloader, but I was hoping to see it before I logged into the phone.
defilip69 said:
the easyest way is to see if you getting 5 second warning on boot
Click to expand...
Click to collapse
Any idea what that warning looks like? Is it just the little unlocked lock icon?
You cant miss it. It shows up as the first screen your device displays immediatly after starting it. It will say something like "The bootloader has been unlocked. This device can not be trusted" for 5 seconds and then proceed the normal startup procedure. If you miss it then your bootloader is locked.
Xecu said:
You cant miss it. It shows up as the first screen your device displays immediatly after starting it. It will say something like "The bootloader has been unlocked. This device can not be trusted" for 5 seconds and then proceed the normal startup procedure. If you miss it then your bootloader is locked.
Click to expand...
Click to collapse
So, if the bootloader's locked, then phone should be safe for use, right? Or is there anything else the seller might've done to tamper with it?
Even if the bootloader is unlocked it could be safe.
Jimi Mack said:
Even if the bootloader is unlocked it could be safe.
Click to expand...
Click to collapse
But if the bootloader is locked, does that mean it's definitely safe? Anything else I could do to protect myself?
Bantersaurus said:
Anyone else know where the info would be on the fastboot screen?
Where do I use that command? On the fastboot screen? I know there's a dial code I can use to check the bootloader, but I was hoping to see it before I logged into the phone.
Any idea what that warning looks like? Is it just the little unlocked lock icon?
Click to expand...
Click to collapse
before boot animation u have boot logo which have moto logo. if you have message like ... warning ... bla bla bla ... your phone is unlocked ... bla bla bla ... ( yellow triangle thing ) bla bla bla then is unlocked
Bantersaurus said:
But if the bootloader is locked, does that mean it's definitely safe? Anything else I could do to protect myself?
Click to expand...
Click to collapse
Basically what separates a locked bootloader and an unlocked bootloader is the ability to alter the partitions of the phone. A phone with an unlocked bootloader could probably be reflashed in a way to skip the Google sign in lock after a "reset" and be sold off if it were stolen. If you have a locked bootloader and a password on the device, all that could be done is a wipe through stock recovery and be prompt by Google to sign in with the previous account. In terms of OS security patches, your basically helpless until the device manufacturer feels like maintaining the device. Apparently Android O is supposed to fix that with project treble where Google adds an extra API layer on the kernel level.
DroneDoom said:
Basically what separates a locked bootloader and an unlocked bootloader is the ability to alter the partitions of the phone. A phone with an unlocked bootloader could probably be reflashed in a way to skip the Google sign in lock after a "reset" and be sold off if it were stolen. If you have a locked bootloader and a password on the device, all that could be done is a wipe through stock recovery and be prompt by Google to sign in with the previous account. In terms of OS security patches, your basically helpless until the device manufacturer feels like maintaining the device. Apparently Android O is supposed to fix that with project treble where Google adds an extra API layer on the kernel level.
Click to expand...
Click to collapse
Did you miss my opening post? I said I'm buying a new phone from an independent seller. I wanted to know if there's any way to check if they installed malware of any kind that might keylog me.
Bantersaurus said:
Did you miss my opening post? I said I'm buying a new phone from an independent seller. I wanted to know if there's any way to check if they installed malware of any kind that might keylog me.
Click to expand...
Click to collapse
I'd check the indication of an unlocked bootloader as others previously mentioned, look at what's prompted upon booting up the phone. If it was unlocked, the message is as clear as day that tells you it's unlocked. If they tried to cover that up you'd still see part of the message like "N/A" or "bad key" within the logo. That indication right there alone is suspicious. Should you contact the seller or reflash the stock firmware yourself, you should be wary about what's already installed on the device.
If you don't see any indication of an unlocked bootloader, then I'd still wipe it through stock recovery and run an app that checks signature verifications and heuristics of malicious apps (Malwarebytes or some other antivirus app).
I forgot to mention the logos that are SUPPOSED to show on the device depending on what Android version it's on.
For marshmallow, you should see the white logo I've posted in attachments along with the indication I marked where you'll see text from the bootloader telling you that's unlocked if the seller tried to cover it up.
For nougat, the one with the aqua colored background and the indication I marked where the cover up text should be.
If there's nothing and the logo is "natural" looking and you don't see a message before the logo then your bootloader is probably locked.
Edit: sorry the indication for the nougat is slightly lower than where it needs to be. Should be on the same level as the marshmallow one.
DroneDoom said:
Should you contact the seller or reflash the stock firmware yourself, you should be wary about what's already installed on the device..
Click to expand...
Click to collapse
I don't think there'll be anything installed (besides the possibility of malware). It's supposed to be a brand new, unopened phone that's still in the original packaging. It'd be too suspicious if there are apps already installed (besides bloatware that's on most phones).
Related
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, everything but I am still unable to take OTA updates like a new phone would be able to. I think this is because they banned my device from OTAs which I believe they do if you have messed with the device. I need to RMA my device so my question is would it be better to say that I didn't tamper with the device and run the risk of them finding out I did, which is pretty likely seeing as how my device has been banned from OTA updates, or tell them that I did unlock it and all of that but that I have relocked it and I am back to stock? If any of you have had a similar issue how did ASUS handle that? Thanks!
E3AANG11E3 said:
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, and all of that but that I have relocked it.
Click to expand...
Click to collapse
How to you relock bootloader?
mr_gourav2000 said:
How to you relock bootloader?
Click to expand...
Click to collapse
Since I am a new user I cannot post links. But Google "Zenfone 2 bootloader unlock" and I followed the instructions of Grekky's Blog.
there is no such thing as relocking the bootloader. only thing you can do it flash the stock image to make it look stock (since an unlocked bootloader has a white splash screen) but im sure asus knows of this and will still check and see that the bootloader is indeed unlocked and not warranty it.
This is just something we all accepted as a consequence of unlocking our bootloaders. hell i have a screen thats getting worse and worse with a yellow/brownish line coming from the top of the phone, but alas i have an unlocked phone too.
You can replace the white splash screen by flashing a black splash screen image to try and cover up unlocking your bootloader. http://forum.xda-developers.com/zenfone2/themes-apps/551-black-white-splashscreen-twrp-flash-t3141945 . If the reseller has no clue about custom recoveries and trying to flash a rom you'll be safe.
They fixed it, no questions asked. And yes, I was able to relock the bootloader.
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
I believe you're not able to relock the bootloader until Motorola release a signed bootloader. I had the page once before I'll see if I can find it again and add an edit if I do.
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
Don't relock your bootloader unless you want a brick. Technically you can relock it, but everything has to be legit. You've already voided the warranty, relocking won't reinstate that, all that will happen is you'll be bricked with nothing to do about it because you've locked the bootloader.
Why do you want to relock it?
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
jeffritz1 said:
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
Click to expand...
Click to collapse
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Uzephi said:
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Click to expand...
Click to collapse
So, I did a "fastboot oem lock" and it re locked the bootloader. Restart bootloader, shows locked. Restart phone and still getting a splash screen similar to the one when your unlocked but this time it says "Device has loaded a different Operating System". Continues to boot normally into the system without issues. This was odd so I unlocked again did a Flashall w/ "XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and "fastboot oem lock". Both times said the lock was successful. But I'm still getting this boot splash screen with test reading "Device has loaded a different Operating System". System boots but still fails SafetyNet.
What gives? What am I missing?
From what I can muster up on XDA I can see that "you need a signed boot.img". Does this mean something and how can I find this?
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
jeffritz1 said:
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
Click to expand...
Click to collapse
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
jeffritz1 said:
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
Click to expand...
Click to collapse
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Marcowe said:
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Click to expand...
Click to collapse
Yeah, I was trying to find out if the phone could be reverted back to an out of back state. Another words, no splash screen saying "HEY! I HAVE BEEN MESSED WITH!" like you can on any other phone I have ever owned.
Thanks!
Yes you can
thomas.raines said:
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Click to expand...
Click to collapse
Yes you can , I already had this issue with my moto z2 force in Morocco , so what I did is I connected the phone to internet via bluetooth and when I added my google accounte the unlocking oem in dev option was normal , so I was able to flash roms again . Hope this will help you
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
EddiePR said:
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
Click to expand...
Click to collapse
If you do that OTAs will fail
Marcowe said:
If you do that OTAs will fail
Click to expand...
Click to collapse
Yes, you are rigth
So, which of the methods to re-lock did finally work? I was running on Android 8 before, OTA failes for at least 10 times, but suddenly it worked to upgrade to Android 9. Now I am weirdly not passing SafetyNet-check anymore (was working fine on Android 8, GooglePay etc).
Any recommendations? I just need the stupid GPay thing working
I recently got a 7x from ebay.co.uk. I noticed the opened box states the model is BND-AL10 (Chinese) but in the phone settings it's a BND-L21 (International). S/N and IMEI match.
Out of curiosity I tried Huawei Firmware Finder for Oreo. I used DNS method, picked the top one as seen here (verified): hxxp://pro-teammt.ru/firmware-database/?firmware_model=BND-L21C432&firmware_page=0
It downloaded like 20 patches totalling around 8+GB and then asked to reboot...and failed.
My phone still works but I now get this during boot:
"your device has failed verification and may not work properly.
1) Press power key to continue.
2) Press volume up key up to 3 seconds to enter erecovery to restore your device.
3) your device will stop,start if there is not operation.
I tried Huawei eRecovery: 'Getting package info failed'
What should I do? Noob.
Brent.M said:
I recently got a 7x from ebay.co.uk. I noticed the opened box states the model is BND-AL10 (Chinese) but in the phone settings it's a BND-L21 (International). S/N and IMEI match.
Out of curiosity I tried Huawei Firmware Finder for Oreo. I used DNS method, picked the top one as seen here (verified): hxxp://pro-teammt.ru/firmware-database/?firmware_model=BND-L21C432&firmware_page=0
It downloaded like 20 patches totalling around 8+GB and then asked to reboot...and failed.
My phone still works but I now get this during boot:
"your device has failed verification and may not work properly.
1) Press power key to continue.
2) Press volume up key up to 3 seconds to enter erecovery to restore your device.
3) your device will stop,start if there is not operation.
I tried Huawei eRecovery: 'Getting package info failed'
What should I do? Noob.
Click to expand...
Click to collapse
erecovey fails for everybody. dont know why.
the message you see is normal if bootloader is unlocked. You should have had that same message first time you turned it on too.
Attempting to use firmware finder to apply updates , is not possible to unlock bootloader, so it had to have already been that way.
mrmazak said:
erecovey fails for everybody. dont know why.
the message you see is normal if bootloader is unlocked. You should have had that same message first time you turned it on too.
Attempting to use firmware finder to apply updates , is not possible to unlock bootloader, so it had to have already been that way.
Click to expand...
Click to collapse
Thanks for the reply. I definitely did not have this message before trying Firmware Finder. I have not done anything else to the phone.
Brent.M said:
Thanks for the reply. I definitely did not have this message before trying Firmware Finder. I have not done anything else to the phone.
Click to expand...
Click to collapse
This is known message resulting from of having boooader unlocked. Few people have been trying to make it not show , but no one has made it public if they have been successful at hiding it.
Now you got that phone (used, I assume ).From eBay. Perhaps the previous owner found some way. And attempting to update made his "hack" undo. Don't really know.
You can check if bootloader lock status to be sure if it is unlocked or not.
mrmazak said:
This is known message resulting from of having boooader unlocked. Few people have been trying to make it not show , but no one has made it public if they have been successful at hiding it.
Now you got that phone (used, I assume ).From eBay. Perhaps the previous owner found some way. And attempting to update made his "hack" undo. Don't really know.
You can check if bootloader lock status to be sure if it is unlocked or not.
Click to expand...
Click to collapse
In FASTBOOT&RESCUE MODE:
PHONE Unlocked
FRP Lock
This phone is sold as brand new boxed. However, like I said it was opened. I wasn't expecting to get a Chinese version that has been flashed. I should have just paid a bit more from Amazon. Though, I'm not fussed as long as I get updates and it's stable.
https://www.ebay.co.uk/itm/Huawei-H...var=541715986486&_trksid=p2057872.m2749.l2649
The 'your device has failed verification and may not work properly.' screen also says:
To learn more,visit:
http://zh.ui.vmail.com/emotiondownload.php?mod=restore
Brent.M said:
In FASTBOOT&RESCUE MODE:
PHONE Unlocked
FRP Lock
This phone is sold as brand new boxed. However, like I said it was opened. I wasn't expecting to get a Chinese version that has been flashed. I should have just paid a bit more from Amazon. Though, I'm not fussed as long as I get updates and it's stable.
ebayDOTcoDOTuk/itm/Huawei-Honor-7X-5-93-Octa-Core-16-0MP-32-64-128g-Android-7-0-OTA-Smartphone/332608261102?ssPageName=STRK%3AMEBIDX%3AIT&var=541715986486&_trksid=p2057872.m2749.l2649
The 'your device has failed verification and may not work properly.' screen also says:
To learn more,visit:
http://zh.ui.vmail.com/emotiondownload.php?mod=restore
Click to expand...
Click to collapse
that status is very bad.
that combination of unlocked bootloader and locked frp is often hard if not impossible to get past.
unless you can access developer options menu and enable "enable oem unlock" menu option.
mrmazak said:
that status is very bad.
that combination of unlocked bootloader and locked frp is often hard if not impossible to get past.
unless you can access developer options menu and enable "enable oem unlock" menu option.
Click to expand...
Click to collapse
PHONE Unlocked
FRP Unlocked
I read that "Huawei is no longer offering bootloader unlock code in 60 days." I tried to request a unlock but I get just get
"If you have any questions about the unlock code application, please contact us."
Nothing happens. I contacted them.
Will I ever need that unlock code given that it is already unlocked? Should I return/refund the phone and buy from Amazon UK or am I wasting my time, since I'll likely be requesting a unlock code and possibly be playing with roms in a few years. I keep phones as long as possible and a basic user which is why I have little knowledge with them.
Brent.M said:
PHONE Unlocked
FRP Unlocked
I read that "Huawei is no longer offering bootloader unlock code in 60 days." I tried to request a unlock but I get just get
"If you have any questions about the unlock code application, please contact us."
Nothing happens. I contacted them.
Will I ever need that unlock code given that it is already unlocked? Should I return/refund the phone and buy from Amazon UK or am I wasting my time, since I'll likely be requesting a unlock code and possibly be playing with roms in a few years. I keep phones as long as possible and a basic user which is why I have little knowledge with them.
Click to expand...
Click to collapse
I would try and get a refund (if you bought via PayPal I think you may get some kind of support).
You can get the 7x from UK retailers for as low as £210. But the current Amazon price of £228 is not bad.
Do you browse HotUKDeals? Always check there before buying anything in the UK or from China.
Cracking deal for a China sourced redmi note 5 from tomorrow:
https://www.hotukdeals.com/deals/sa...900mah-aliexpress-xiaomi-online-store-2948784
Search for 7x deals.
Cheers
Sent from my BND-L21 using Tapatalk
sipart said:
I would try and get a refund (if you bought via PayPal I think you may get some kind of support).
You can get the 7x from UK retailers for as low as £210. But the current Amazon price of £228 is not bad.
Do you browse HotUKDeals? Always check there before buying anything in the UK or from China.
Cracking deal for a China sourced redmi note 5 from tomorrow:
https://www.hotukdeals.com/deals/sa...900mah-aliexpress-xiaomi-online-store-2948784
Search for 7x deals.
Cheers
Sent from my BND-L21 using Tapatalk
Click to expand...
Click to collapse
Yes, PayPal. I contacted the seller on the matter. Will see what they say. After using Firmware Finder correctly I updated to 8.0 Oero. The message during boot also went away... I'll certainly check out hotdeals. But if the phone works should I bother?
Brent.M said:
Yes, PayPal. I contacted the seller on the matter. Will see what they say. After using Firmware Finder correctly I updated to 8.0 Oero. The message during boot also went away... I'll certainly check out hotdeals. But if the phone works should I bother?
Click to expand...
Click to collapse
i think it is a little suspicious on the bootloader getting unlocked like that, but if its working , and you flashed full ota, then maybe give it a try.
¯\_(ツ)_/¯
¯\_('.')_/¯
`
mrmazak said:
i think it is a little suspicious on the bootloader getting unlocked like that, but if its working , and you flashed full ota, then maybe give it a try.
¯\_(ツ)_/¯
¯\_('.')_/¯
`
Click to expand...
Click to collapse
"Dear buyer,
Sorry for bring you any inconvenience and disappointment, the reason we have opened the package is because we need to download a multiplied language system to the phone before sent it out, they it can be use normal in this country. And for the model no, that's a normal phenomenon after rooting the phone.
Anyway, is it affect your use? what can us do for you now?"
Brent.M said:
Yes, PayPal. I contacted the seller on the matter. Will see what they say. After using Firmware Finder correctly I updated to 8.0 Oero. The message during boot also went away... I'll certainly check out hotdeals. But if the phone works should I bother?
Click to expand...
Click to collapse
Oh yes if you got it working no point. Enjoy the 7x
Sent from my BND-L21 using Tapatalk
Since the bootloader is unlocked I won't need to request a unlock code or ever need that code? As I did read Huawei is no longer offering bootloader soon.
Bootloader unlock and relock
deleted, posted on a new thread
Hi. I'm having an issue with this new phone. It's Wowi Ultra SQ766. On start up interface the 'Red State' notice comes up, goes off for 5 seconds and comes back on. The full message states:
'Red State
Your device has failed verification and may not work properly.
Please download boot image with correct signature or disable verified boot.
Your device will reboot in 5 seconds'.
Could you please help me out with a solution or fix for this.
I'd be happy if you would help.
Awaiting your reply.
Noob
Earlier today I installed Magisk, but then found that some apps I frequently use (Samsung Pay being one of them) were no longer working so I decided to revert back to Android O, remove Magisk etc. and basically go back to stock. I flashed the factory images using fastboot, then sent the command to lock the bootloader. Strangely when I tried "fastboot flashing lock_critical" it told me the bootloader was locked, but when I entered "fastboot flashing lock" it went through and restarted.
This is where I get stuck, when the phone boots it shows a message about the device being corrupt. If I press the power button, it just then goes to the white screen with Google in the middle and does nothing else.
What should I do to get my phone back to factory specs?
naiku said:
Earlier today I installed Magisk, but then found that some apps I frequently use (Samsung Pay being one of them) were no longer working so I decided to revert back to Android O, remove Magisk etc. and basically go back to stock. I flashed the factory images using fastboot, then sent the command to lock the bootloader. Strangely when I tried "fastboot flashing lock_critical" it told me the bootloader was locked, but when I entered "fastboot flashing lock" it went through and restarted.
This is where I get stuck, when the phone boots it shows a message about the device being corrupt. If I press the power button, it just then goes to the white screen with Google in the middle and does nothing else.
What should I do to get my phone back to factory specs?
Click to expand...
Click to collapse
Why on earth did you lock the bootloader? But oh well. Try unlocking it again, then fastboot 8.1 again. No need to worry about data anymore since you've been wiped! ?
I locked it again as Samsung Pay kept crashing saying I had a modified system, since I had already flashed back to factory 8.1 I assumed that was the reason why, hence locking the bootloader. I was actually in the middle of flashing 8.1 again when you replied, did exactly that, unlocked bootloader, flash-all in fastboot and I am back to setting it up again.
Going to leave the bootloader unlocked for now, but I do want to be able to use Samsung Pay so if that means locking it will likely go through the whole ordeal again at some point!!
naiku said:
I locked it again as Samsung Pay kept crashing saying I had a modified system, since I had already flashed back to factory 8.1 I assumed that was the reason why, hence locking the bootloader. I was actually in the middle of flashing 8.1 again when you replied, did exactly that, unlocked bootloader, flash-all in fastboot and I am back to setting it up again.
Going to leave the bootloader unlocked for now, but I do want to be able to use Samsung Pay so if that means locking it will likely go through the whole ordeal again at some point!!
Click to expand...
Click to collapse
Well glad your up and running. Outa curiosity, did you run the fastboot flashing unlock_critical when you first unlocked the bootloader? ?
Yep, in fact I think I only ran the unlock critical. Did both this time, oddly though unlock critical did nothing initially, so did just unlock, then tried unlock critical again and it reported being unlocked.
In the middle of setting everything up now, Samsung Pay working with the unlocked bootloader. Must have been something with root, even after removing it, that screwed it up previously.
naiku said:
Yep, in fact I think I only ran the unlock critical. Did both this time, oddly though unlock critical did nothing initially, so did just unlock, then tried unlock critical again and it reported being unlocked.
In the middle of setting everything up now, Samsung Pay working with the unlocked bootloader. Must have been something with root, even after removing it, that screwed it up previously.
Click to expand...
Click to collapse
Yep, root is usually always the culprit with pay type apps if magisk hide isn't working properly. But hey, at least your happy now ?
Yup, I had tried magisk hide and it did not work, so (wrongly) assumed the bootloader unlocked was the problem.
Thankfully all good now, was definitely a little worried earlier this evening!
naiku said:
Yep, in fact I think I only ran the unlock critical. Did both this time, oddly though unlock critical did nothing initially, so did just unlock, then tried unlock critical again and it reported being unlocked.
In the middle of setting everything up now, Samsung Pay working with the unlocked bootloader. Must have been something with root, even after removing it, that screwed it up previously.
Click to expand...
Click to collapse
How did you get SP to work on a non Samsung phone? Does MST work or does that take special hardware?
Sent from my SM-T820 using Tapatalk
dew.man said:
How did you get SP to work on a non Samsung phone? Does MST work or does that take special hardware?
Sent from my SM-T820 using Tapatalk
Click to expand...
Click to collapse
Pay works fine with no issues, I did nothing other than install the app while on O, then it still works on P DP3.
Not sure what MST is, so can't help there.
Are you sure you're talking about SAMSUNG pay, and not Android Pay? As far as I know (and just checked again), it' s not available from google, only from the galaxy store.
MST is the (supposedly) proprietary Samsung technology that allows you to pay with your phone at older terminals that do not have NFC. From what I understand, they have a way to communicate with magnetic card readers enabling their solution to work pretty much everywhere.
dew.man said:
Are you sure you're talking about SAMSUNG pay, and not Android Pay? As far as I know (and just checked again), it' s not available from google, only from the galaxy store.
MST is the (supposedly) proprietary Samsung technology that allows you to pay with your phone at older terminals that do not have NFC. From what I understand, they have a way to communicate with magnetic card readers enabling their solution to work pretty much everywhere.
Click to expand...
Click to collapse
100% sure it's Samsung Pay. I will say though that I use it on my watch, not the phone itself. Had to double check though, looks like we are both right. I don't have Samsung Pay on my phone as its own app, but it is used as part of the Gear app in order to set it up on my watch. During set up with the phone rooted, the watch Samsung Pay setup, on the phone, was crashing. Sorry for any confusion.
Gotta say I am glad the watch works with it. I would not have been happy if I had lost that functionality switching from the S7 Edge to the Pixel.
What should I / could I do?
I have the update.zip in my root, but still I keep getting unsupported device.
Any advice would be appreciated!
(I've already factory reset, also the attached image is one I found online, I have a Z2 and not a G5 Plus.)
fastboot work right if so get flash all , the model number bottom of phone by charging port they have a lot of threads lol
ericerk said:
What should I / could I do?
I have the update.zip in my root, but still I keep getting unsupported device.
Any advice would be appreciated!
(I've already factory reset, also the attached image is one I found online, I have a Z2 and not a G5 Plus.)
Click to expand...
Click to collapse
Please, provide real screen. Who ever need random picture from Google on XDA ) Can you also show fastboot.exe interact process? Locked, unlocked, was it tempered? Come on, more information!
s5610 said:
Please, provide real screen. Who ever need random picture from Google on XDA ) Can you also show fastboot.exe interact process? Locked, unlocked, was it tempered? Come on, more information!
Click to expand...
Click to collapse
The unlock company who I went through apparently changed the Model number to a Moto G4, but the unlock seems to have stuck, but the model number is different. At this point, I've gotten ATT to give me an official sim unlock code. So I'm really not sure what to do.
ericerk said:
The unlock company who I went through apparently changed the Model number to a Moto G4, but the unlock seems to have stuck, but the model number is different. At this point, I've gotten ATT to give me an official sim unlock code. So I'm really not sure what to do.
Click to expand...
Click to collapse
Write me PM, I know the solution to unlock even hard locked device.