Related
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
I know this is an older post but I've been unable to find the instructions for re-locking the bootloader. Any help would be appreciated.
I had the electrify m, the RAZR m for us cellular, and I unlocked it through Motorola. I was giving it to someone else and wanted to relock it and never found any instructions to do so. I contacted Motorola and they said once it was unlocked the was no way to relock. I would guess it's the same with the moto x.
Sent from my XT1055 using Tapatalk
fastboot oem lock doesn't work?
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Sent from my XT1058 using xda app-developers app
I tried it with my electrify m and it wouldn't work.
Sent from my XT1055 using Tapatalk
https://plus.google.com/110773150384694258853/posts/XUF8UP9iVfi
Here's how from p3droid
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
mschumacher69 said:
Has anyone tried re-locking a non-dev Moto X? If so, does it get rid of the "bootloader unlocked, warranty void" message that you get every time u boot ur phone?
Click to expand...
Click to collapse
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Sent on my Moto X
flashallthetime said:
Makes no difference, even when you flash the sbf firmware the logo warning still pops up, so you're best just flashing a new logo.bin file . you'll find them in the themes section, fastboot flash logo (name).bin and your done. If you need to rsdlite at any time in the future, just remove the line flash logo bin from the XML file
Click to expand...
Click to collapse
Even if u re-lock the bootloader?
bootloopz said:
Wondering if it's possible to re-lock the bootloader. Would it be the same as a Nexus device?
Click to expand...
Click to collapse
tw1tch175 said:
Yes however it will leave the tamper flag and if you used the dev site it will still be logged.
Click to expand...
Click to collapse
planktoid said:
It does. Fastboot OEM lock. Just go back to signed software before, m Kay ? Else you won't boot
Click to expand...
Click to collapse
Has anyone tried re-locking the bootloader of their Moto X??
mschumacher69 said:
Has anyone tried re-locking the bootloader of their Moto X??
Click to expand...
Click to collapse
Does not work for me. I get:
No valid PIV block in SP for system
chaoslimits said:
Does not work for me. I get:
No valid PIV block in SP for system
Click to expand...
Click to collapse
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
mschumacher69 said:
Did u try re-locking on your model/carrier stock rom, a stock rom from another model/carrier or a custom rom?
Thanks
Click to expand...
Click to collapse
Went back to stock 4.4 via RSD Lite then tried to relock.
chaoslimits said:
Went back to stock 4.4 via RSD Lite then tried to relock.
Click to expand...
Click to collapse
Which model/carrier do u have?
mschumacher69 said:
Which model/carrier do u have?
Click to expand...
Click to collapse
Vzw Dev Edition
chaoslimits said:
Vzw Dev Edition
Click to expand...
Click to collapse
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
mschumacher69 said:
Have u tried this?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
chaoslimits said:
Yes. That (minus userdata removal) is what RSD Lite does. I tried with fastboot and mfastboot as well.
Click to expand...
Click to collapse
Weird. So is ur phone bricked now or it just did not lock?
Hey guys,
I am currently trying to get my Moto X back to stock and relock the bootloader. Not because I need to, but just because I want to. I have a retDe XT1092 which I have converted to a XT1095. Is there any way to get the phone back to software status official and relock the bootloader? It doesn't matter to me that Motorola does know that I was unlocked before, I just want to relock it. I hope you guys can help me.
May I ask why you want to relock it? There really is no benefit to relocking it. :/
Anyway the command is:
fastboot oem lock
Sent from my XT1095
I know, but want to keep myself from flashing on this phone. I am trying to get away from rooting on non-nexus phones.
Yeah I've tried that multiple times, but as long as your software status isn't official the oem lock will fail. I'd guess this happens because most images you can download are not signed images.
Is your phone still converted to 1095? If so that is why lock wont work.
You would have to flash back the 1092 de image to be unmodified.
Sent from my XT1095
Okay good to know. I thought this wouldnt matter. But are there even any existing official images for the 1092?
Moto x firmwares:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25
Sent from my XT1095
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Bl4ckX said:
These aren't official. I've already tried them. If you flash those you won't be able to relock the bootloader. This is the reason why I opened this thread because I don't know any way of accomplishing my goal.
Click to expand...
Click to collapse
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
juliospinoza said:
One thing is official and other thing is carrier, and I think you need the firmware of your carrier, the one who came with your phone before the flashing. Maybe if you tell us we can find it for you.
Click to expand...
Click to collapse
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
AGISCI said:
His is retde. And these are official, they are leaks from motorola.
Sent from my XT1095
Click to expand...
Click to collapse
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
strafer69 said:
I was able to get the signed firmware from motorola, You have to start with fastboot oem lock begin and then flash. After flashing you use the fastboot oem lock and the bootloader will relock, however, you will still get the unlocked warning message. You will have to flash the modified logo.bin to make it go away.
Click to expand...
Click to collapse
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Bl4ckX said:
If you are so convinced that these are official I am willing to try them out but I am pretty sure they aren't
This doesn't sound right. Using oem unlock begin the phone will check if each and every image is signed. You shouldn't be able to flash a modified logo.bin and the message should actually go away by itself. Are you sure your relock attempt didn't fail?
Click to expand...
Click to collapse
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
AGISCI said:
I am 100% sure they are official because they are signed by motorola. If they were not official they wouldn't have motorola's signature.
Sent from my XT1095
Click to expand...
Click to collapse
I am currently downloading the XT1092 retDe image. I will report back in 6hours when I am back from work and this damn free download is finished. It takes forever..
The bootloader unlocked message would be a signed Motorola image since it is shipped with the phone. The bootloader essentially has a toggle that would switch between the normal and the unlocked message. I assume the toggle just doesn't get switched back when you OEM lock. It's not like he flashed a different custom logo or anything.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Correct. You will notice the status message when you enter the bootloader there is a status code. 1=LOCKED 2=RELOCKED and 3=UNLOCKED. Once you unlock the bootloader, you can never go back to status 1 again and you will always get the bootloader unlocked message. If you read the message it states that the bootloader HAS been unlocked. There is a counter trigger in the phone telling it how many times it has been unlocked. When I had my old Galaxy S2 Skyrocket I remembered a program that would "RESET" this counter, but I do not believe one exists for Motorola. Once you unlock your bootloader there is no going back.
http://i5.androidxda.com/main/Motorola_Bootloader_Warning.png
Yeah I know about this relocked state, but it doesn't matter as I don't want to RMA the phone. I just want it locked but I wasn't able to accomplish a successful oem lock and I am now searching for a way to do so.
Edit: So this morning after the download had finished I brought my X to fastboot mode. And for whichever reason the software status was set to official even on the XT1095 image. I would have sworn that this wasn't the case when I flashed it and I have no idea why it changed. And a big thanks to you @AGISCI after typing "fastboot oem lock begin" I could flash the Image you linked here and software status stayed official and I was even able to relock the bootloader. So I simply must have had wrong images in the past, because I did entirely the same process I did now, 3 times already and it didn't work out at all.
So thanks again guys. The only annoyance is that I can't get rid of the bootloader unlocked message. This one seems to stay.
Man, I've really done research until my eyes are ready to pop out lol. Can someone please help me.
I'm using this guide to try and unlock my bootloader: https://www.youtube.com/watch?v=cfpehEkhfyg
Problem is, it's for a verizon version, mine's a note 4 T-mobile sm-n910t3
I'm just a noob and never had to do this unlock bootloader crap on my note 2. I need help.
I just want to unlock the bootloader, and flash recovery, supersu, and a cool rom like res. remix or CM remix.
On the video, the part I'm stuck on is he's using a file: "samsung_unlock_n4-2" with no file extension (.xxx)
I'm assuming this is a bootloader file?? I found a bootloader for my version which is a folder with contents:
FOLDER: BL_N910T3_DOK2 CONTENTS: aboot.mbn / NON-HLOS.bin / rpn.mbn / sbl1.mbn / sdi.mbn / tz.mbn
He goes on to use a CMD and fastboot to temporarily root the phone to install TWRP recovery,
but when he pushes this command: "adb push samsung_unlock_n4-fix /data/local/tmp/"
I don't think I can do that with a folder and I don't know which file to use.
QUESTION:
-DOES ANYONE KNOW WHICH FILE I NEED
-OR-
IS THERE A BETTER WAY TO FLASH A CUSTOM KERNEL THAT UNLOCKS THE BOOTLOADER, THEN ROOT, FLASH ROM AND EVERYTHING A LOT EASIER.
Side note, I didn't know I had to unlock FRP and tried to flash recovery. I also tried CFautoroot.
Both are blocked from working so I'm just assuming the bootloader is locked, otherwise it would say "mode developer" on the stock recovery. Off topic, I started reading about CyanogenMod Installer.... wtf ever happened with this program?!?!?! It sounds awesome!! It said it even would unlock bootloaders and everything. It was only after reading that it was put out of service that I stopped doing my happy dance. why in the fudge brownie cheesecake would you delete something so awesome? Anyway, can you guys plesaea help before I commit android suicide. That would be great.
I CAN'T BOOT INTO CUSTOM RECOVERY. IF I COULD DO THAT I COULD DO ANYTHING. UGGGGG
Anything, whatever...
I'm at a loss here......
It's been days and I'm frustrated.
910T3 versions are locked down for good after 6.0.1MM update but you could DO2 it and then just be stuck without wireless and NFC. Lol, its just so dumb isnt it lol. Pretty soon in the future maybe they'll jusf give us an option to have our devices custom made by your own specs??
djscottallen said:
Man, I've really done research until my eyes are ready to pop out lol. Can someone please help me.
I'm using this guide to try and unlock my bootloader: https://www.youtube.com/watch?v=cfpehEkhfyg
Problem is, it's for a verizon version, mine's a note 4 T-mobile sm-n910t3
I'm just a noob and never had to do this unlock bootloader crap on my note 2. I need help.
I just want to unlock the bootloader, and flash recovery, supersu, and a cool rom like res. remix or CM remix.
On the video, the part I'm stuck on is he's using a file: "samsung_unlock_n4-2" with no file extension (.xxx)
I'm assuming this is a bootloader file?? I found a bootloader for my version which is a folder with contents:
FOLDER: BL_N910T3_DOK2 CONTENTS: aboot.mbn / NON-HLOS.bin / rpn.mbn / sbl1.mbn / sdi.mbn / tz.mbn
He goes on to use a CMD and fastboot to temporarily root the phone to install TWRP recovery,
but when he pushes this command: "adb push samsung_unlock_n4-fix /data/local/tmp/"
I don't think I can do that with a folder and I don't know which file to use.
QUESTION:
-DOES ANYONE KNOW WHICH FILE I NEED
-OR-
IS THERE A BETTER WAY TO FLASH A CUSTOM KERNEL THAT UNLOCKS THE BOOTLOADER, THEN ROOT, FLASH ROM AND EVERYTHING A LOT EASIER.
Side note, I didn't know I had to unlock FRP and tried to flash recovery. I also tried CFautoroot.
Both are blocked from working so I'm just assuming the bootloader is locked, otherwise it would say "mode developer" on the stock recovery. Off topic, I started reading about CyanogenMod Installer.... wtf ever happened with this program?!?!?! It sounds awesome!! It said it even would unlock bootloaders and everything. It was only after reading that it was put out of service that I stopped doing my happy dance. why in the fudge brownie cheesecake would you delete something so awesome? Anyway, can you guys plesaea help before I commit android suicide. That would be great.
I CAN'T BOOT INTO CUSTOM RECOVERY. IF I COULD DO THAT I COULD DO ANYTHING. UGGGGG
Anything, whatever...
I'm at a loss here......
It's been days and I'm frustrated.
Click to expand...
Click to collapse
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Trex888 said:
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Click to expand...
Click to collapse
Did this work, as in actually unlocking the bootloader right then, just by checking that box? I thought that option only got the phone ready for unlocking or something like that. I'm trying to root a T3 and don't want to flash over an unlocked bootloader, of course.
Trex888 said:
So far i know is N910T3 bootloader is not locked unlike verizon or at&t .
All you have to do is go to settings/about device and hit on build number 7 times .
You will see in settings "developer options" go to OEM UNLOCK and just turn it on this will unlock your bootloader and make sure reactivation lock is turned off in settings/security.
Thats it now you can go to download mode and flash twrp recovery and flash any rom from twrp compatible for your model.
Click to expand...
Click to collapse
Has anyone tried this? I have an 910T3 running a custom ROM on lollipop 5.1.1. I wish to try and upgrade to marshmallow 6.0.1, and eventually a new custom ROM, but I am hesitant to do so as I have read that the 910T3 cannot be downgraded, should I like to return back to lollipop.
After setting OEM unlock , don't you need to use a procedure with adb fastboot through a terminal interface to unlock the bootloader?
I would love to know more about this before I attempt and irreversible upgrade.
Any help or advice would be greatly appreciated.
580guy said:
Has anyone tried this? I have an 910T3 running a custom ROM on lollipop 5.1.1. I wish to try and upgrade to marshmallow 6.0.1, and eventually a new custom ROM, but I am hesitant to do so as I have read that the 910T3 cannot be downgraded, should I like to return back to lollipop.
After setting OEM unlock , don't you need to use a procedure with adb fastboot through a terminal interface to unlock the bootloader?
I would love to know more about this before I attempt and irreversible upgrade.
Any help or advice would be greatly appreciated.
Click to expand...
Click to collapse
Once you upgrade to marshmallow you cannot downgrade to lollipop forget it.
To unlock bootloader you just have to turn on oem unlock thats it no need adb.
If you are already running custom rom as you mentioned your bootloader should be already unlocked.
Trex888 said:
Once you upgrade to marshmallow you cannot downgrade to lollipop forget it.
To unlock bootloader you just have to turn on oem unlock thats it no need adb.
If you are already running custom rom as you mentioned your bootloader should be already unlocked.
Click to expand...
Click to collapse
So, trying to clarify, what you are saying is once you upgrade to marshmallow bootloader is permanently locked? From what I understand, locked bootloaders are what prevent you from changing ROMs, so I assume you are saying that OEM unlock will not work under marshmallow?
So no way I could reflash DOK2 Bootloader and return to Lollipop again? Or just flash a stock Lollipop ROM with ODIN?
580guy said:
So, trying to clarify, what you are saying is once you upgrade to marshmallow bootloader is permanently locked? From what I understand, locked bootloaders are what prevent you from changing ROMs, so I assume you are saying that OEM unlock will not work under marshmallow?
So no way I could reflash DOK2 Bootloader and return to Lollipop again? Or just flash a stock Lollipop ROM with ODIN?
Click to expand...
Click to collapse
Oem unlock will work no problem on marshmallow and you can root & flash roms easily same as lollipop.
But you can only flash marshmallow roms once you upgrade.
I was saying only you cannot downgrade from marshmallow to lollipop.
odin will fail if you try to downgrade
Trex888 said:
Oem unlock will work no problem on marshmallow and you can root & flash roms easily same as lollipop.
But you can only flash marshmallow roms once you upgrade.
I was saying only you cannot downgrade from marshmallow to lollipop.
odin will fail if you try to downgrade
Click to expand...
Click to collapse
Thanks for the reply. In doing more searching around I found one of your older posts from 2016 and it sounds to me like it is a idiosyncrasy of the 910t3. I believe you stated you sold the T3 and ended up getting a 910T for that reason, so you could downgrade if you wished. Looks like I will be sticking with lollipop, unless I get another motherboard or phone. Thanks again for the response.
so I was trying to update to EMUI 9 using Beta Flashy and I forgot to reflash stock recovery after flashing root via TWRP to get Flashy to work, so after the update, it couldn't reset, and when I checked bootloader, FRP was locked and now its stuck in bootloop. can anyone provide me with a method to fixing this issue without requiring me to pay the absurd amount that FunkyHuawei and DC Unlocker charge for restoring?
thank you
edit: solution here
Try Dload method and go back to EMUI8
majidamiri15300 said:
So I was trying to update to EMUI 9 using Beta Flashy and I forgot to reflash stock recovery after flashing root via TWRP to get Flashy to work, so after the update, it couldn't reset, and when I checked bootloader, FRP was locked and now its stuck in bootloop. I read this guide https://forum.xda-developers.com/showpost.php?p=73556776&postcount=24 saying that restoring the oeminfo partition should get it to work (don't worry, I still have my bootloader unlock code), but I can't find any images for the Mate 10 (ALP-L29).
Can anyone provide me with one? If not, can you provide me with a method to fixing this issue without requiring me to pay the absurd amount that FunkyHuawei and DC Unlocker charge for restoring?
Thank you
Click to expand...
Click to collapse
Have you tried factory reset from stock recovery?
Flashing someone elses oeminfo will not help you. All it will do is lock bootloader and change your unlock code. (that thread is for Mate 9 on Nougat where oeminfo can be flashed without breaking anything. On Oreo and higher it uses oeminfo to calculate unlock code. But it also uses the imei that's embedded in oeminfo to calculate it. If you flash someone elses oeminfo your imei in oeminfo will not be the same and unlock code will change)
You most likely didn't do anything wrong. Updating stock firmware will replace your recovery with stock recovery. If it got that far in installation that is?
FH should work but it cost a lot. DC does not work since June so don't bother with it.
Else you can try service firmware from androidhost.ru.
ante0 said:
Have you tried factory reset from stock recovery?
Flashing someone elses oeminfo will not help you. All it will do is lock bootloader and change your unlock code. (that thread is for Mate 9 on Nougat where oeminfo can be flashed without breaking anything. On Oreo and higher it uses oeminfo to calculate unlock code. But it also uses the imei that's embedded in oeminfo to calculate it. If you flash someone elses oeminfo your imei in oeminfo will not be the same and unlock code will change)
You most likely didn't do anything wrong. Updating stock firmware will replace your recovery with stock recovery. If it got that far in installation that is?
FH should work but it cost a lot. DC does not work since June so don't bother with it.
Else you can try service firmware from androidhost.ru.
Click to expand...
Click to collapse
It supposedly went fine, but its still as is so. im downloading the Oreo update i was on, hopefully it works. of course the download speed isnt of much help
ante0 said:
Have you tried factory reset from stock recovery?
Flashing someone elses oeminfo will not help you. All it will do is lock bootloader and change your unlock code. (that thread is for Mate 9 on Nougat where oeminfo can be flashed without breaking anything. On Oreo and higher it uses oeminfo to calculate unlock code. But it also uses the imei that's embedded in oeminfo to calculate it. If you flash someone elses oeminfo your imei in oeminfo will not be the same and unlock code will change)
You most likely didn't do anything wrong. Updating stock firmware will replace your recovery with stock recovery. If it got that far in installation that is?
FH should work but it cost a lot. DC does not work since June so don't bother with it.
Else you can try service firmware from androidhost.ru.
Click to expand...
Click to collapse
i tried but got an "Software install failed" error.
majidamiri15300 said:
i tried but got an "Software install failed" error.
Click to expand...
Click to collapse
Which build and cust are you trying to install?
ante0 said:
Which build and cust are you trying to install?
Click to expand...
Click to collapse
128, C185
majidamiri15300 said:
128, C185
Click to expand...
Click to collapse
Wait, you were on B128?!
That's from December 2017/January 2018. And that's the reason why it won't downgrade. It has old bootloader, and you are now on new bootloader. (Since Pie has new bootloader and it flashed).
Try a more recent build, like B139 or B140
You can also try downloading from androidhost.ru using JDownloader, it seem to ignore the limit.
ante0 said:
Wait, you were on B128?!
That's from December 2017/January 2018. And that's the reason why it won't downgrade. It has old bootloader, and you are now on new bootloader. (Since Pie has new bootloader and it flashed).
Try a more recent build, like B139 or B140
You can also try downloading from androidhost.ru using JDownloader, it seem to ignore the limit.
Click to expand...
Click to collapse
does it matter though? because i cant even flash Pie. it's like its not accepting anything.
majidamiri15300 said:
does it matter though? because i cant even flash Pie. it's like its not accepting anything.
Click to expand...
Click to collapse
But it did update before bootlooping, no?
ante0 said:
But it did update before bootlooping, no?
Click to expand...
Click to collapse
i think so, yes. im downloading and trying anyway cuz what do i have to lose here.
edit: B135 didn't work, B139 still downloading...
majidamiri15300 said:
i think so, yes. im downloading and trying anyway cuz what do i have to lose here
Click to expand...
Click to collapse
It's just that B128 has old bootloader, and Pie (Including Oreo firmware from June and forward) has new bootloader. You can not downgrade from new bootloader to old bootloader.
So that's most likely why it fails to flash B128.
And you would only be able to update Pie using NoCheck recovery/TWRP, which is impossible to flash as you are FRP locked.
ante0 said:
It's just that B128 has old bootloader, and Pie (Including Oreo firmware from June and forward) has new bootloader. You can not downgrade from new bootloader to old bootloader.
So that's most likely why it fails to flash B128.
And you would only be able to update Pie using NoCheck recovery/TWRP, which is impossible to flash as you are FRP locked.
Click to expand...
Click to collapse
yeah i get that. ugh why does Huawei have to make everything so hard?
majidamiri15300 said:
i think so, yes. im downloading and trying anyway cuz what do i have to lose here.
edit: B135 didn't work, B139 still downloading...
Click to expand...
Click to collapse
majidamiri15300 said:
yeah i get that. ugh why does Huawei have to make everything so hard?
Click to expand...
Click to collapse
B135 should be able to install. It's new bootloader.
Check the instruction pdf that's included in the firmware, it will show you the directory path to use. And if you need to use microsd or USB OTG to SD adapter or something.
ante0 said:
B135 should be able to install. It's new bootloader.
Check the instruction pdf that's included in the firmware, it will show you the directory path to use. And if you need to use microsd or USB OTG to SD adapter or something.
Click to expand...
Click to collapse
i tried B139 and it didnt work. what the hell is going on???
edit: nevermind, nevermind, im just a giant idiot. ive been extracting the UPDATE.APP and using that instead of the full image. its flashing now.
majidamiri15300 said:
i tried B139 and it didnt work. what the hell is going on???
edit: nevermind, nevermind, im just a giant idiot. ive been extracting the UPDATE.APP and using that instead of the full image. its flashing now.
Click to expand...
Click to collapse
Hi. Have you solved the problem? I'm stuck on Android pie beta too and I can't rollback to Oreo. I'm frp locked too.
Todesdoktor said:
Hi. Have you solved the problem? I'm stuck on Android pie beta too and I can't rollback to Oreo. I'm frp locked too.
Click to expand...
Click to collapse
Which model and cust are you on? (ex. BLA-L29 C432)
Pretoriano80 said:
Which model and cust are you on? (ex. BLA-L29 C432)
Click to expand...
Click to collapse
ALP-L29 C636 But my build says ALP-LGRP2-OVS
Todesdoktor said:
Hi. Have you solved the problem? I'm stuck on Android pie beta too and I can't rollback to Oreo. I'm frp locked too.
Click to expand...
Click to collapse
yeah i did, it was relatively easy. just go to https://androidhost.ru, download the version for your phone, and when you unzip, you'll find a folder with instructions on how to flash. easy process, although keep in mind, this process will relock your bootloader (if you already unlocked it).
if you did unlock and it relocked, firstly, check your email if you still have the unlock code buried somewhere in your deleted emails, and if not, then check out this guide, should help you find your unlock code. it worked for me, and only cost $5 or so.
majidamiri15300 said:
yeah i did, it was relatively easy. just go to https://androidhost.ru, download the version for your phone, and when you unzip, you'll find a folder with instructions on how to flash. easy process, although keep in mind, this process will relock your bootloader (if you already unlocked it).
if you did unlock and it relocked, firstly, check your email if you still have the unlock code buried somewhere in your deleted emails, and if not, then check out this guide, should help you find your unlock code. it worked for me, and only cost $5 or so.
Click to expand...
Click to collapse
Thank you. So, for confirm, this works on frp locked? And yes, I'm unlocked and I have my code and my OEM file backup.
With the Moto Z, after I returned the phone to stock (flashed stock firmware and locked the bootloader), I'd be able to flash stock firmware with the flashing locked.
Not so with the Motorola One Zoom. In other words, flashing stock and re-locking didn't return the phone to its pristine state. Even when flashing stock firmware over stock firmware, I have to unlock the bootloader.
Differences I observed: on the bootloader screen, when re-locked the Z would show "oem_locked" again. On the One Zoom, it shows "flashing_locked" instead. I'm pretty sure it showed "oem_locked" before unlocking.
WIth the Z, every time I wanted to unlock the bootloader, I had to issue "fastboot oem unlock" followed by the unlock code. The code isn't necessary with the re-locked One Zoom.
In other words, maybe it was a one-way trip. It seems that the phone won't return to its original state, it looks it's modified for good. And I'm afraid this means bye-bye to automatic updates.
Am I missing something here?
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
rafikowy said:
My bootloader is also unlocked and I dont have any problems with receiving and installing OTAs I also have Magisk and EdExposed installed - no problems at all.
Click to expand...
Click to collapse
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Whammamoosha said:
Phew! I'm glad I'll be able to install OTAs. Have you tried flashing it manually or via RSD Lite? Here it won't flash.
Click to expand...
Click to collapse
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
rafikowy said:
Hey, yes, flashing manually. I will provide you flashing scripts tomorrow.
Click to expand...
Click to collapse
Don't bother, I have mine. Thanks.
I would like the flash script if someone would share it
Help with unlocking bootloader
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Bodeman12345 said:
I tried to unlock the bootloader and i am now in a menu with an android with his chest open. In the cmd on my pc i try to type fastboot flashing unlock but it just gives me an error.
I dont know if this is the correct place to post this but i have no idea where to post it and i dont want my phone get bricked.
Click to expand...
Click to collapse
In the settings for developers you gave permission for Factory Unlock?
ilia3367 said:
In the settings for developers you gave permission for Factory Unlock?
Click to expand...
Click to collapse
I enabled the setting to unlock oem bootloader is that the same?
Bodeman12345 said:
I enabled the setting to unlock oem bootloader is that the same?
Click to expand...
Click to collapse
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
Code:
fastboot devices
If the device is detected, enter the command:
Code:
fastboot getvar all
And copy the result here.
ilia3367 said:
yes.
Click to expand...
Click to collapse
Yes I did that
Bodeman12345 said:
Yes I did that
Click to expand...
Click to collapse
Answer the other questions, please!
diculpe por que mi pc no ve el fastboot de mi one zoom?
ilia3367 said:
yes.
What instruction did you use to unlock the bootloader?
What region is your device manufactured for?
Does your PC see your device connected to the fastboot mod?
What does this command give you:
If the device is detected, enter the command:
And copy the result here.
Click to expand...
Click to collapse
I used this youtube video
I dont know where it is manifactured but I live in the netherlands.
I dont get the 3th question
I will do the commands in a couple minutes
Hey all,
I have the Moto One Zoom running on Android 9.
Also, It's Rooted with Magisk and have Riru EdXposed installed, can I install my OTA updates without bootloop or do I have to Uninstall Magisk, relock bootloader and factory reset/flash stock firmware to get latest OTA updates?
Any feedback is appreciated.
Thanks