Is there then an easy way to relock the bootloader and wipe any trace of it ever being unlocked?
I know I sound a bit paranoid, but what if I need to send it in for a warranty-related problem?
I got my phone today and was actually a tad disappointed over it being "Samsung-branded" with the yakjuxw-build. One would think it would be entirely managed by Google with it being a Google phone and all.
use the gnex toolkit to flash to google version, then use it to relock bootloader. 10 min thing
Sent from my Galaxy Nexus using XDA Premium HD app
If you care about voiding the warranty, then I would recommend that you do the following BEFORE unlocking your bootloader:
Plug it into USB, reboot into bootloader.
Type "fastboot getvar all".
You'll probably see a variable called "unlocked" which would be set to "no" or "0". See if there are any variables listed there that talk about warranty. If there are, then I wouldn't recommend unlocking because even if you re-lock the bootloader, they'll know it was unlocked at some point.
I know that this was not an issue on the Nexus S (also made by Samsung). You could re-lock the bootloader and nobody would be any the wiser.
The reason I suggested you try it was because of the Motorola Xoom (which of course is another Google Experience device with an unlockable bootloader). On all Xoom bootloaders, there's the standard "unlocked" bootloader variable, but also an additional one called "IsWarrantyVoid". From the factory, both bootloader variables are set to "no". As soon as you unlock the bootloader for the first time, both variables are set to "yes". If you then go and lock it again, "Unlocked" gets set to "no", but "IsWarrantyVoid" remains "yes" and there's nothing you can do to change it.
So I think you're OK because this is a Samsung device, but just double check it before you unlock the bootloader. If you don't see any kind of bootloader variable pertaining to warranty, I say go for it. I did a quick check of bootloader variables on my LTE Gnex and didn't see anything suspicious, but it sounds like you have a GSM version, so you should check yourself just to be absolutely sure.
< waiting for device >
(bootloader) product: tuna
(bootloader) variant: maguro 16GB
(bootloader) serialno: -x-
(bootloader) version-hardware: 9
(bootloader) version-baseband: I9250UGLC1
(bootloader) version-bootloader: PRIMELA03
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
(bootloader) signing: production
all:
finished. total time: 0.006s
I dared to unlock the bootloader and flash yakju 4.0.2. I mainly flashed 4.0.2 too see if OTA's work and they seem to. Got a small 8mb update but no .3 or .4 as of yet. Gonna check tomorrow morning, though. It's 10.40 pm here.
When on 4.0.4, I'll root.
I couldn't even stay from tampering with my 7 hours old phone, lol. Let's just hope I won't need any repairs. ^^
Sent from my Galaxy Nexus using Tapatalk 2
JaiaV said:
< waiting for device >
(bootloader) product: tuna
(bootloader) variant: maguro 16GB
(bootloader) serialno: -x-
(bootloader) version-hardware: 9
(bootloader) version-baseband: I9250UGLC1
(bootloader) version-bootloader: PRIMELA03
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
(bootloader) signing: production
all:
finished. total time: 0.006s
Click to expand...
Click to collapse
Hmm..."secure" worries me. I'm sure this is a stupid question to ask at a place like XDA, but does anyone have a GSM Gnex that has NOT been unlocked yet? Can you tell us the value of "secure"? I went back and checked on my LTE Gnex and it's there and also set to "no". I missed that one the first time around.
(bootloader) product: tuna
(bootloader) variant: maguro 16GB
(bootloader) serialno: -x-
(bootloader) version-hardware: 9
(bootloader) version-baseband: I9250UGLC1
(bootloader) version-bootloader: PRIMELA03
(bootloader) secure: no
(bootloader) unlocked: no
(bootloader) off-mode-charge: 1
(bootloader) signing: production
all:
finished. total time: 0.007s
Secure flag doesn't reset when re-locked.
Theshawty said:
Is there then an easy way to relock the bootloader and wipe any trace of it ever being unlocked?
I know I sound a bit paranoid, but what if I need to send it in for a warranty-related problem?
I got my phone today and was actually a tad disappointed over it being "Samsung-branded" with the yakjuxw-build. One would think it would be entirely managed by Google with it being a Google phone and all.
Click to expand...
Click to collapse
Unlock, flash temp Clockwork, make backup, done.
Just restore that backup and you'll be back to yakjuxw. Reboot after restore to remove temp Clockwork, then relock bootloader. Good as new.
P.S. might be a good idea to note the radio your phone came with, in case you flash a different one. Clockwork does not backup radio, so you'll just need to flash the radio before restoring to stock.
Sent from my Galaxy Nexus
JaiaV said:
(bootloader) product: tuna
(bootloader) variant: maguro 16GB
(bootloader) serialno: -x-
(bootloader) version-hardware: 9
(bootloader) version-baseband: I9250UGLC1
(bootloader) version-bootloader: PRIMELA03
(bootloader) secure: no
(bootloader) unlocked: no
(bootloader) off-mode-charge: 1
(bootloader) signing: production
all:
finished. total time: 0.007s
Secure flag doesn't reset when re-locked.
Click to expand...
Click to collapse
Yes, which makes me wonder if it's set to "yes" out of the factory, then set to no upon first unlock. "Secure" reeks of being Samsung's version of Motorola's "IsWarrantyVoid".
I'm sure most of us here at XDA unlocked our bootloader the day we got the phone even if we ended up re-locking it a day later. I'm hoping that someone has a girlfriend or parents or somebody that has a Galaxy Nexus that's never been unlocked in order to check the value of that "secure" variable.
secure is basically another way of telling if the bootloader is secure, it's nothing to get scared over
So does it come from the factory set to no?
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
Yes, which makes me wonder if it's set to "yes" out of the factory, then set to no upon first unlock. "Secure" reeks of being Samsung's version of Motorola's "IsWarrantyVoid".
Click to expand...
Click to collapse
On HTC devices, the secu_flag (or secure flag) is what dictates if the bootloader is re-lockable. If the flag is set to 1, you cannot re-lock the bootloader; if it is set to 0, you can. I'm just speculating here, but it may be similar on a Samsung device. Confirmation would be needed of course.
That's great info to know. Thanks!
Sent from my Galaxy Nexus using Tapatalk 2
Related
I'll start with a little background, then I'll get to the point. I got a "Verizon" HTC One M7 from ebay. It had a cracked screen, but it was in pretty fine working condition. I took it to a shop to have the screen replaced because it looked a little too complicated for me. Got it back and noticed it didn't have any reception when I charged it back up. Flashed a new ROM and radios, but still no reception.
My problems multiplied once I attempted to downgrade to see if that would revive the reception. I ended up sending it to jtag because I bricked it in the process. Fast-forward to today where I have my phone back, in working condition, somewhat, but no reception. I'm told that it has a GSM board, not CDMA. It was advertised as a Verizon phone and had a signal when I got it. Possibly switched at shop...I don't know.
Now, all I want to do is get a working phone. How do I proceed to get it working so that I can, at the very least, sell a working phone to get one that I can flash to PagePlus?
Go to about phone and check the software information. Post a screenshot of that.
Ok...here's what I have...
Go into fastboot mode and use the fastboot get-var all command and post that as well. That might be able to tell for sure if it is gsm or not. If it is you won't be able to get a signal at all with Verizon. On the plus side you should be able to flash the correct firmware for that board and sell that phone to someone else as a gsm phone. It should work just fine on gsm as long as the correct firmware is flashed.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**********
(bootloader) imei: 99000**********
(bootloader) meid: 9900**********
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 22222222
(bootloader) battery-status: good
(bootloader) battery-voltage: 4094mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
C:\adb>
Fastboot flash this firmware and you might be good to go again. http://www.androidfilehost.com/?fid=23329332407570630
disconnecktie said:
Fastboot flash this firmware and you might be good to go again. http://www.androidfilehost.com/?fid=23329332407570630
Click to expand...
Click to collapse
Are these the commands i need?
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
Just want to make sure I don't flub this up...
Yes and you can find those instructions in the stock Rom radio thread of santods for future reference.
disconnecktie said:
Yes and you can find those instructions in the stock Rom radio thread of santods for future reference.
Click to expand...
Click to collapse
Ok...still no signal. I used an active PagePlus sim card and there is no change. I'd like to try a gsm rom to see if it works...again, I don't want to mess this phone up again...
trojanbrutha said:
Ok...still no signal. I used an active PagePlus sim card and there is no change. I'd like to try a gsm rom to see if it works...again, I don't want to mess this phone up again...
Click to expand...
Click to collapse
Try ViperOne 7.0.1 it has all the apns you would need.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Can a cdma ROM be flashed onto a gsm board?
Sent from my DROID BIONIC using Tapatalk
Question...I noticed the problem that I have started after I had my screen replaced...could this be an issue with the lack of cell reception?
Sent from my HTC6500LVW using Tapatalk
repair shop may have not connected the antenna cables.
So, after thinking about this whole thing for a while, I decided to call Verizon to find out if the cell shop pulled a switch-a-roo on me with the motherboard. The guy tells me that my IMEI is not compatible with the vzw network. Now I want to know what HTC has to say about it. I call them and I'm told it's a vzw phone...and IT'S STILL UNDER WARRANTY!:highfive: Of course, he walks me through a factory reset and questions me about htcdev account. I'm mostly truthful about it and explain about the replacement screen...he's undeterred about that...asks if I can relock my bootloader...I say yes :good: So, now I'm thinking faux bootloader, but I think I should just ruu down...
trojanbrutha said:
So, after thinking about this whole thing for a while, I decided to call Verizon to find out if the cell shop pulled a switch-a-roo on me with the motherboard. The guy tells me that my IMEI is not compatible with the vzw network. Now I want to know what HTC has to say about it. I call them and I'm told it's a vzw phone...and IT'S STILL UNDER WARRANTY!:highfive: Of course, he walks me through a factory reset and questions me about htcdev account. I'm mostly truthful about it and explain about the replacement screen...he's undeterred about that...asks if I can relock my bootloader...I say yes :good: So, now I'm thinking faux bootloader, but I think I should just ruu down...
Click to expand...
Click to collapse
Don't forget to fastboot oem writecid VZW__001 (two underscores). Your cid is all 2s.
Sent from my One using XDA Free mobile app
Uzephi said:
Don't forget to fastboot oem writecid VZW__001 (two underscores). Your cid is all 2s.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Done...do I need to go S-On or does it matter much?
trojanbrutha said:
Done...do I need to go S-On or does it matter much?
Click to expand...
Click to collapse
I did when I did my screen replacement. Be sure you are completely stock and **locked** not **relocked**.
Sent from my One using XDA Free mobile app
Uzephi said:
I did when I did my screen replacement. Be sure you are completely stock and **locked** not **relocked**.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
I'm in the process of going back to stock and while I was running the ruu that was somewhat successful, the following is what I saw that failed...
(bootloader) start image[sbl1-1] unzipping & flushing..
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing..
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing..
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-4] unzipping & flushing..
(bootloader) [RUU]UZ,sbl1-4,0
(bootloader) [RUU]UZ,sbl1-4,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[cir] unzipping & flushing...
(bootloader) [RUU]UZ,cir,0
(bootloader) [RUU]UZ,cir,100
(bootloader) ...... Successful
Click to expand...
Click to collapse
Now it's just stuck trying to activate. All I need to do now is a factory reset and lock the bootloader and s-on. I was just curious about what didn't work or what failed in the ruu...
trojanbrutha said:
I'm in the process of going back to stock and while I was running the ruu that was somewhat successful, the following is what I saw that failed...
Now it's just stuck trying to activate. All I need to do now is a factory reset and lock the bootloader and s-on. I was just curious about what didn't work or what failed in the ruu...
Click to expand...
Click to collapse
Normal for secondary bootloaders to not update. Especially when s-off.
I have tried to install a new custom ROM on my HTC One M8.
It has a unlocked bootloader, it's unlocked, rooted, and i've had InsertCoin and Paranoid Android, and CyanogenMod on it.
My device is S-ON.
However, lately I have not been able to update to any of the newer roms.
The ROMs that I have tried to install are:
HTC_One_(M8)_-_MaximusHD_11.0.0
insertcoin-m8_5.0.3_ART
ViperOneM8_4.2.0_v2
And none of them work except for
pa_m8-4.45-20140729
which is always my go-to ROM right now when the others fail so I don't soft brick it.
I do have a Nandroid in case everything goes to hell.
But my question is, what is wrong with my device and why can't I update to another ROM? It gets stuck at the HTC White Logo screen every single time with every ROM that fails.
Thanks!
technocrat7 said:
But my question is, what is wrong with my device and why can't I update to another ROM? It gets stuck at the HTC White Logo screen every single time with every ROM that fails.
Thanks!
Click to expand...
Click to collapse
You have old hboot and firmware version.
All the newer Sense based ROM require hboot no less than 3.19.0000
What's your fastboot getvar all - post here minus serial no. & imei no.
Maybe lollipop OTA already available for your device region.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Here is my information on my phone, so it would seem that I am outdated. How would I get back up to date?
Here is the RUU for your device version : http://forum.xda-developers.com/showpost.php?p=58771521&postcount=4593
This will update your device to the latest lollipop 4.20.531.4
1. put your device in bootloader/fastboot mode and connect to PC
2. run command to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
Then if you want to install custom ROM again, re-unlock bootloader & install any custom recovery that you like.
Thanks! I did what you said, then this happened:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.127s
Is this supposed to happen?
it says RELOCKED at the top though
technocrat7 said:
Is this supposed to happen?
it says RELOCKED at the top though
Click to expand...
Click to collapse
Yep ... just proceed to install RUU (step 3)
Okay thank you, Also I wanted to ask you, how exactly did you find my RUU?
I saw the cidnum was TMOBO010 or whatever it was, but how exactly did you use that to find my RUU?
Thanks again for the help, much appreciated
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
These are the 3 items that important to check what you need.
I don't really need to search for it because I'm always around in this thread : http://forum.xda-developers.com/showthread.php?t=2701376
and it happens that I just helped other person there with more or less same problem as yours.
BTW ... please remove those sensitive data (serial no. & imei no.) from your post above.
I did what you asked.
And okay I will keep that in mind
**EDIT**
Also, do I need to "re unlock" my phone? Or can I just do "fastboot oem unlock" because I have once before unlocked it?
This IS a relock right?
technocrat7 said:
Also, do I need to "re unlock" my phone? Or can I just do "fastboot oem unlock" because I have once before unlocked it?
This IS a relock right?
Click to expand...
Click to collapse
No .. you need to unlock it with the unlock_code.bin that you received from HTCDev when you first unlock your device.
If you don't have it, reapply a new one.
I see, okay I unlocked it again.
While I'm at it, I wanted to ask one final question that's been bugging me for a while now.
When I got to my Philz recovery and do "factory wipe" why doesn't it actually wipe my data?
I want ALL of my data, ROM, apps, everything to be gone, but it doesn't do that.
Is there an alternative?
Is there no way to remove all user data/apps?
I don't use Philz recovery so not sure how to help you. Maybe try an older version 6.26.6
I use only TWRP and now your device already updated to 5.0.1; you need to use TWRP 2.8.4.0 or the latest 2.8.5.0
Okay I am on TWRP, how do I do a factory reset on TWRP?
and what exactly will it do?
I just hope it'll actually wipe everything when I factory reset it. Or else I don't see a point of even having a factory reset option
It's all depends on what you want to do.
Factory reset - to prepare your device to install next ROM, it wipes user data, cache, dalvik cache
I always prefer - wipe menu - advance - select data, cache, dalvik, system - this wipe everything except internal storage.
To wipe data and internal storage - wipe menu - advance - format data - yes
I got to go now ... bed time
Thank you that's all I needed to know.
I appreciate the help, goodnight!
technocrat7 said:
Thank you that's all I needed to know.
I appreciate the help, goodnight!
Click to expand...
Click to collapse
No problem ... and it's already good day here
Haha I see.
Do you know any information on the OnePlus?
I made a post there, however it's not a very active forum.
Sent from my HTC One_M8 using XDA Free mobile app
No idea about any other brand phone ... I use only HTC since 2008 when I first registered with XDA with my first HTC Elf
Haha interesting, I started with the Droid DNA being my first HTC device, and that thing was so bad it almost never make me want to go HTC again. But I got my M7
And staying on topic... If you have a different kernel on your device, would you still be able to RUU it? Or would you have to revert the kernel back?
Sent from my HTC One_M8 using XDA Free mobile app
RUU - no need
OTA - need to revert to stock kernel/modules if modules are changed. If modules are stock, then no need
Has anyone successfully rooted and put recovery on this device?
I guess we have to wait for a while before someone find a way to root. If zte allows easy way to unlock bootloader. Also depends how popular this phone is between the community. (Apparently not popular at all)
it's problably time to abandon all hope for ever getting this phone rooted. It's such a shame because it actually is a pretty nice phone.
Should have checked earlier whether there is root already.
Actually it should not be that difficult to compile a twrp image since the phone has a pretty common setup (Snapdragen 435 (non-Pro) and Snapdragon 635 (Pro).
hstop said:
Should have checked earlier whether there is root already.
Actually it should not be that difficult to compile a twrp image since the phone has a pretty common setup (Snapdragen 435 (non-Pro) and Snapdragon 635 (Pro).
Click to expand...
Click to collapse
Pretty much
From what I know they simply dont allow to unlock the bootloader.
https://forum.xda-developers.com/bl...er-bootloader-mode-t3558410#postcount73838994
hstop said:
it's problably time to abandon all hope for ever getting this phone rooted. It's such a shame because it actually is a pretty nice phone.
Should have checked earlier whether there is root already.
Actually it should not be that difficult to compile a twrp image since the phone has a pretty common setup (Snapdragen 435 (non-Pro) and Snapdragon 635 (Pro).
Click to expand...
Click to collapse
I'm actually thinking of picking up this phone since my current one doesn't have all the Att bands. Seems to be a great phone for $120 new.
Sent from my XT1635-01 using Tapatalk
NesteaZen said:
Pretty much
From what I know they simply dont allow to unlock the bootloader.
Click to expand...
Click to collapse
Jup. Tried it myself. It seems they have modified fastboot. Apart from
Code:
fastboot getvar all
the bootloader is responding with
Code:
FAILED: (remote: unknown command)
or not at all to any other command.
So unlocking and flashing is not possible unless they give us a different bootloader or reveal how to do it.
This is what the bootloader of my Blade V8 (nonPro) presents
Code:
C:\Program Files\ZTE_Handset_USB_Driver>fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4114000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x8000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5efbfbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x110000000
(bootloader) serialno:16b2c461
(bootloader) kernel:lk
(bootloader) product:QC_REFERENCE_PHONE
all:
finished. total time: 0.029s
Yea I wanted to get a ZTE too but I did what you didn't (look up if it can be rooted) and that's why I snubbed ZTE and went for a lenovo zuk z2 for example.
Unfortunately there are no black Zuk Z2 Pro available anymore. White one are no option for me.
I want emojis
maria123 said:
I want emojis
Click to expand...
Click to collapse
there you go
Don't forget to update us in case you find a way to root it
As of today the ZTE Blade V8 can't be rooted and i'm SICK, SICK , CRAZY SICK of the bloatware my local carrier put in it... i need to remove all that s**t
There is an option under settings developer option for OEM unlocking which it says allows the bootloader to be unlocked... if that means anything.
Can any be rooted I have a zte a blade max pro
ENCOMcorp said:
Has anyone successfully rooted and put recovery on this device?
Click to expand...
Click to collapse
It is definitely possible. I know the axon 7 has a very similar bootloader situation. They were able to bypass it with a custom flashable image. unfortunately it is not compatible with the blade. I have been investigating it though. I am not the most qualified to do this, but this phone has so much potential, but it is stuck on old software. I don't want to see that happen.
I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid
vibraniumdroid said:
I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid
Click to expand...
Click to collapse
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei
41rw4lk said:
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224CQPCT
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 5786D2FB
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed for privacy)
(bootloader) meid:
(bootloader) date: 08-05-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4385
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.01R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g2c64ab8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Apr 20 09:21:37 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.242s
wtf xda turned some of it into emojis
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
I have the oem unlock enabled in Dev options
41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
Also can u link the thread u were talking about.
vibraniumdroid said:
I have the oem unlock enabled in Dev options
Click to expand...
Click to collapse
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
Click to expand...
Click to collapse
thnx a lot I really appreciate the help
41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Will let u know if I make any progress
41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Did not work
vibraniumdroid said:
Did not work
Click to expand...
Click to collapse
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.
41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
I will try to flash twrp also I have the oem unlock switch checked in Dev options
vibraniumdroid said:
I will try to flash twrp also I have the oem unlock switch checked in Dev options
Click to expand...
Click to collapse
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Sent from my Moto Z2 Force using XDA Labs
vibraniumdroid said:
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.
Click to expand...
Click to collapse
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.
fast69mopar said:
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Click to expand...
Click to collapse
I know. As I mentioned earlier this is my second z2
41rw4lk said:
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.
Click to expand...
Click to collapse
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.
vibraniumdroid said:
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.
Click to expand...
Click to collapse
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.
41rw4lk said:
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.
Click to expand...
Click to collapse
Okay I will try tomorrow
If you want to unlock bootloader, just follow the motorola guide.
For trouble shooting or more info about how to get your "cid" and see if it's unlockable , have a look here.
If you want to relock it:
Code:
fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.080s]
finished. total time: 0.080s
Code:
fastboot oem lock
...
(bootloader) warranty bit blown
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.943s]
finished. total time: 0.944s
So, um, is it unlockable? (Given the article linked is generic across all Moto phones, and the list of unlockable phones does not actually list the Moto One Vision.) Apparently you can run
Code:
fastboot getvar all
with the phone in bootloader mode to get the cid, and if it is one of: 0x0000, 0x0003, 0x0007, 0x0009, 0x000B, 0x000C, 0x000D, 0x000E, 0x0014, 0x00DE or 0x0032; but no others, its bootloader can be unlocked.
Asking because there's an Amazon UK Prime Day deal on today and tomorrow for this phone where it's 25% off its regular price, and I'd rather only buy it if, once its warranty runs out as do the Android One security updates, there's a chance for me to unlock the bootloader and put on, say, Lineage OS. My LG G5 is on its last legs and I do need a new phone, and it'll be a long while before this phone regularly sells used for £199.99 here in the UK. Especially with Brexit, and therefore an impending Sterling devaluation, closing fast.
(I gather the "Amazon Prime phones" mentioned as non-unlockable in the article are US Amazon Prime exclusive phones such as the Moto G6 and X4 that were for a time offered only to Amazon Prime customers in the US.)
obs3rv said:
So, um, is it unlockable?
(I gather the "Amazon Prime phones" mentioned as non-unlockable in the article are US Amazon Prime exclusive phones such as the Moto G6 and X4 that were for a time offered only to Amazon Prime customers in the US.)
Click to expand...
Click to collapse
Yes. Developer Mode has an option to unlock the bootloader.
£199 quid is a hell of a deal ; considering I shelled out £269 last month for mine.
Would you (or anyone with an EU version of this handset really) be kind enough to get the cid in bootloader mode using fastboot per my earlier post? I gather that the cid is the ultimate arbiter of whether the bootloader is unlockable, and that even permanently-locked bootloader handsets have similar firmware that has the Enable OEM unlock option in Developer Mode. (I'm happy to be corrected on this point.)
Answering my own question, the cid of a Motorola One Vision bought off Amazon Italy turned out to be 0x0032, indicating that its bootloader may be unlockable:
Code:
(bootloader) cid: 0x0032
You can boot into the bootloader from a powered-off, cable disconnected state by:
holding down the volume-down key
plugging in the USB cable whose other end is already connected to a computer with the Motorola Device Manager drivers installed
Then fastboot works.
(Why did I buy it from Amazon Italy rather than Amazon UK, taking advantage of the Prime Day deal? Despite the fact that Amazon UK showed the Prime Day deal was meant to run for 48 hours, at midnight, Amazon UK pulled its own merchant listing, leaving only third-party sellers, and so the Prime Day deal became unavailable. Amazon Italy had a lightning deal the following day on the phone for €249.99, which was a better price than I could find anywhere else. So I bought it, having missed out on the Prime Day deal the previous day. Thanks, Amazon. Thamazon.)
Almost full fastboot getvar all output for those who are curious (with serial number, IMEI and battery serial number redacted):
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190605
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 000003D60F1C577A0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 05-20-2019
(bootloader) sku: XT1970-3
(bootloader) carrier_sku: XT1970-3
(bootloader) battid: [redacted]
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jul 23 6:59: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/kane_reteu/kane_sprout:9/
(bootloader) ro.build.fingerprint[1]: PSA29.137-17/6875e:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.18.kane_reteu.
(bootloader) ro.build.version.full[1]: retail.en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld66) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Wed Jun 5 08:01:45 CDT 2019
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190605
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.611s
FYI Amazon Spain seem to have had this handset at a decent price since Prime Day, and the price hasn't gone back up yet -- the price is down €40 from its usual €299.99 price to €259.99 since last week. Not quite as good as the €249.99 Lightning Deal on Amazon Italy from a week ago, and nowhere near as good as the £199.99 Amazon UK Prime Day deal, but still a good deal. (On Amazon Italy it's €269.99 starting today, but on the other Amazon Eurozone websites it's still €299.99, and in the UK the Amazon usual offer of £269.99 is back.)
obs3rv said:
Answering my own question, the cid of a Motorola One Vision bought off Amazon Italy turned out to be 0x0032, indicating that its bootloader may be unlockable:
Code:
(bootloader) cid: 0x0032
You can boot into the bootloader from a powered-off, cable disconnected state by:
holding down the volume-down key
plugging in the USB cable whose other end is already connected to a computer with the Motorola Device Manager drivers installed
Then fastboot works.
(Why did I buy it from Amazon Italy rather than Amazon UK, taking advantage of the Prime Day deal? Despite the fact that Amazon UK showed the Prime Day deal was meant to run for 48 hours, at midnight, Amazon UK pulled its own merchant listing, leaving only third-party sellers, and so the Prime Day deal became unavailable. Amazon Italy had a lightning deal the following day on the phone for €249.99, which was a better price than I could find anywhere else. So I bought it, having missed out on the Prime Day deal the previous day. Thanks, Amazon. Thamazon.)
Almost full fastboot getvar all output for those who are curious (with serial number, IMEI and battery serial number redacted):
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.2-kane_retail-523afc7-190605
(bootloader) product: kane
(bootloader) board: kane
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 128GB SAMSUNG KLUDG4U1EA-B0C1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=01 M8=12
(bootloader) cpu: Exynos9609
(bootloader) serialno: [redacted]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 000003D60F1C577A0000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: [redacted]
(bootloader) meid:
(bootloader) date: 05-20-2019
(bootloader) sku: XT1970-3
(bootloader) carrier_sku: XT1970-3
(bootloader) battid: [redacted]
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jul 23 6:59: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/kane_reteu/kane_sprout:9/
(bootloader) ro.build.fingerprint[1]: PSA29.137-17/6875e:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.18.kane_reteu.
(bootloader) ro.build.version.full[1]: retail.en.US
(bootloader) ro.build.version.samsung: 20190510
(bootloader) version-baseband: S337AP_KANE_SGCS_QB2190425
(bootloader) kernel.version[0]: Linux version 4.14.56-g1007313 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld66) (Android (4691093 based on r
(bootloader) kernel.version[2]: 316199) clang version 6.0.2 (https://and
(bootloader) kernel.version[3]: roid.googlesource.com/toolchain/clang 18
(bootloader) kernel.version[4]: 3abd29fc496f55536e7d904e0abae47888fc7f)
(bootloader) kernel.version[5]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[6]: ain/llvm 34361f192e41ed6e4e8f9aca80a4ea7
(bootloader) kernel.version[7]: e9856f327) (based on LLVM 6.0.2svn)) #1
(bootloader) kernel.version[8]: SMP PREEMPT Wed Jun 5 08:01:45 CDT 2019
(bootloader) bootloader.git: MBM-2.2-kane_retail-523afc7-190605
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.611s
FYI Amazon Spain seem to have had this handset at a decent price since Prime Day, and the price hasn't gone back up yet -- the price is down €40 from its usual €299.99 price to €259.99 since last week. Not quite as good as the €249.99 Lightning Deal on Amazon Italy from a week ago, and nowhere near as good as the £199.99 Amazon UK Prime Day deal, but still a good deal. (On Amazon Italy it's €269.99 starting today, but on the other Amazon Eurozone websites it's still €299.99, and in the UK the Amazon usual offer of £269.99 is back.)
Click to expand...
Click to collapse
Yea it's sold by amazon.it at 299 euro, I was near to gets an galaxy a70 but seems they have troubles to run gsi roms. I'll order Moto's phone pretty soon, but I'd like to compile his kernel first so if done well I'll get it.
My phone is a RETBR with cid: 0x0032. Motorola sent me an unlock code that seemingly works, however I'm unable to activate OEM unlock under developer options, as it's greyed out. Any ideas?
Activate internet, switch back and open developer again
Karanso said:
Activate internet, switch back and open developer again
Click to expand...
Click to collapse
I've tried even factory resetting with LTE and WiFi during the setup process.
edit: something random happened and I've succeeded, lol.
Impossible to relock the bootloader
Good afternoon,
I am trying to Relock the bootloader again, but it does not work.
I have followed the instructions of the first post.
The command screen when I try to unlock it is as follows:
Then I turn on the smartphone and the following screen appears:
I'm going to "Settings / Developer options", and I can't activate "OEM unlocking", it's gray
I have followed the clarification of post # 8 and nothing changes..
I am doing something wrong? Is there any solution?
Regards
gonzo1963 said:
Good afternoon,
I am trying to Relock the bootloader again, but it does not work.
I have followed the instructions of the first post.
The command screen when I try to unlock it is as follows:
Then I turn on the smartphone and the following screen appears:
I'm going to "Settings / Developer options", and I can't activate "OEM unlocking", it's gray
I have followed the clarification of post # 8 and nothing changes..
I am doing something wrong? Is there any solution?
Regards
Click to expand...
Click to collapse
Hi. I have relocked my bootloader twice but never seen anything like that.
A quick google suggests that a factory reset before relock should work. Other says that rooting with magisk made the oem toggle usable again so that they could relock. You'll have to reflash firmware before ofc, cause you don't wanna get it locked with non signed code flashed to it
Let me know if you get it solved.
tys0n said:
Hi. I have relocked my bootloader twice but never seen anything like that.
A quick google suggests that a factory reset before relock should work. Other says that rooting with magisk made the oem toggle usable again so that they could relock. You'll have to reflash firmware before ofc, cause you don't wanna get it locked with non signed code flashed to it
Let me know if you get it solved.
Click to expand...
Click to collapse
Good Morning,
I don't know if I understood you well, I'm sorry, my English is not perfect.
First inform you, it is not essential to relock the bootloader. I just want to do it, to update via OTA.
If I can update it manually with the bootloader unlocked, I would not need to relock it.
Can I do it as you indicate in this post: https://forum.xda-developers.com/showpost.php?p=80903809&postcount=23?
I have not rooted the smartphone yet, I will do so soon as explained in this thread: TWRP 3.3.1 & Root for Moto 1 Vision
It occurs to me...
Do you think it would be fixed by reflashing the latest firmware again manually as you explain in this thread: [XT1970-X] Stock firmware share thread. [TOOL] fastboot flash / info
Regards
gonzo1963 said:
It occurs to me...
Do you think it would be fixed by reflashing the latest firmware again manually as you explain in this thread: [XT1970-X] Stock firmware share thread. [TOOL] fastboot flash / info
Regards
Click to expand...
Click to collapse
Good again
I've tried it, but it's still the same.
The same problem, still locked.
Regards
gonzo1963 said:
Good again
I've tried it, but it's still the same.
The same problem, still locked.
Regards
Click to expand...
Click to collapse
I really don't know as I don't have this problem.
View attachment 4907879
Have you tried full reflash with wipe, and then boot it and go through the setup so that it connects online?
Have you tried with root to see if the toggle gets enabled?
tys0n said:
I really don't know as I don't have this problem.
View attachment 4907879
Have you tried full reflash with wipe, and then boot it and go through the setup so that it connects online?
Have you tried with root to see if the toggle gets enabled?
Click to expand...
Click to collapse
Good morning,
I've only done a "factory setting", I don't know how to do a wipe and everything you tell me.
I hope to root the smartphone in the next few days! Another challenge!, hehe.
I hope I don't keep a brick.
I'll tell you how it goes
Regards and thanks
Enviado desde mi unknown mediante Tapatalk
Good afternoon,
I don't know how to do it: "full reflash with wipe, and then boot it and go through the setup so that it connects online?", maybe I've done it without knowing it.
Anyway something strange is happening, it is updated via OTA (PSAS29.160-55-7-1) although it has the bootloader locked.
Rooting is delayed due to a doubt: https://forum.xda-developers.com/showthread.php?p=81281003 until I solve it, I will not do it for fear of the brick.
Regards
Enviado desde mi unknown mediante Tapatalk
Good afternoon,
After rooting it, it seems that everything has been fixed.
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good afternoon,
I am trying to Relock the bootloader again, but it does not work.
I have followed the instructions of the first post.
The command screen when I try to unlock it is as follows:
Then I turn on the smartphone and the following screen appears:
I'm going to "Settings / Developer options", and I can't activate "OEM unlocking", it's gray
I have followed the clarification of post # 8 and nothing changes..
I am doing something wrong? Is there any solution?
Regards
Click to expand...
Click to collapse
Did anyone find the solution to this problem?
I've tried everything, completely reflashing retail rom, retbr rom, installed magisk on an encrypted phone, on an unencrypted phone, erased the phone data, unerased... Every f*CK*NG thing and the switch is still grayed out...
I want to relock my bootloader but I just can't.... I don't know what to do anymore...
Can anyone help me?
Thanks a lot
Preceptor said:
Did anyone find the solution to this problem?
I've tried everything, completely reflashing retail rom, retbr rom, installed magisk on an encrypted phone, on an unencrypted phone, erased the phone data, unerased... Every f*CK*NG thing and the switch is still grayed out...
I want to relock my bootloader but I just can't.... I don't know what to do anymore...
Can anyone help me?
Thanks a lot
Click to expand...
Click to collapse
No idea why that is.
While rooted, I have no problems with the oem unlock toggle.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my moto one vision.
tys0n said:
No idea why that is.
While rooted, I have no problems with the oem unlock toggle.View attachment 5047225
Sent from my moto one vision.
Click to expand...
Click to collapse
Not only that, I've rooted using different methods. Encrypted phone, not encrypted, old magisk, new magisk, and the list goes on. The oem unlock Is always grey...