hi guys,
my op3t is bricked. now all i can access is fast boot mode. no recovery.
the problem is the bootloader is locked, so i can't install new recovery partition.
i've tried the quallcom msm tool to no avail. is there anything else i can do?
thanks
Unlock Bootloader via Fastboot, flash TWRP, and then sideload a ROM via ADB.
Perhaps No,
Your device needs to be sent to oneplus service center. they will replace your motherboard.
deleted
ersandeepkr said:
Perhaps No,
Your device needs to be sent to oneplus service center. they will replace your motherboard.
Click to expand...
Click to collapse
Why? He can unlock the bootloader, flash TWRP via Fastboot, and sideload a ROM. He doesn't need a motherboard replacement.
ersandeepkr said:
Perhaps No,
Your device needs to be sent to oneplus service center. they will replace your motherboard.
Click to expand...
Click to collapse
There are a number of things that can be tried, before getting to your suggestion (which should be considered a "last resort").
---------- Post added at 09:27 AM ---------- Previous post was at 09:10 AM ----------
zeta555 said:
no recovery.
Click to expand...
Click to collapse
Meaning what exactly? What happens when you select recovery from bootloader?
zeta555 said:
i've tried the quallcom msm tool to no avail.
Click to expand...
Click to collapse
Again, it is probably helpful to provide specifics on how far you got with the unbrick tool, what the specific results, error, or outputs were. I haven't personally had to use the unbrick tool, so I can't personally help much on this particular point. But others here may (almost certainly) be able to advise, if you provide more specific details, besides just saying "it didn't work".
You can also try the stock OOS update zip (which can be done with a locked bootloader): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_5.0.1/
Flash the stock recovery (available on the same link) if needed.
thes3usa said:
Unlock Bootloader via Fastboot, flash TWRP, and then sideload a ROM via ADB.
Click to expand...
Click to collapse
i can't, it won't let me unlock the bootloader. and it also won't let me flash any recovery.
when i choose recovery from the fastboot the phone just rebooted to the one plus logo and keep bootlooping (is that a word?) infinitely.
oh, i dont know if this will help. but the phone will only bootloop if it's connected to the charger. if not it wont even turn on.
sometime it will show low battery warning, and/or low temp warning. and no, i don't live in cold climate. i live in the tropics.
ersandeepkr said:
Perhaps No,
Your device needs to be sent to oneplus service center. they will replace your motherboard.
Click to expand...
Click to collapse
yeah, there's no service center in my country. into the shelf of shame then.
He already stated that the recovery is not flashing because you cannot flash anything if the bootloader is locked. If by any mean boot loader is unlocked, then one is good to go.
You should know that bootloader can be unlocked only if the system OS allowed to do so. But in this case system os is crashed as well as recovery.
redpoint73 said:
There are a number of things that can be tried, before getting to your suggestion (which should be considered a "last resort").
---------- Post added at 09:27 AM ---------- Previous post was at 09:10 AM ----------
Meaning what exactly? What happens when you select recovery from bootloader?
Again, it is probably helpful to provide specifics on how far you got with the unbrick tool, what the specific results, error, or outputs were. I haven't personally had to use the unbrick tool, so I can't personally help much on this particular point. But others here may (almost certainly) be able to advise, if you provide more specific details, besides just saying "it didn't work".
You can also try the stock OOS update zip (which can be done with a locked bootloader): http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_5.0.1/
Flash the stock recovery (available on the same link) if needed.
Click to expand...
Click to collapse
He already said he can't access recovery.
what errors is it giving u with the msm tool and where did u download the unbrick tool from? If the msm tool doesn't work its more than likely a hardware issues, b/c that should cure almost any type of brick
ZVNexus said:
He already said he can't access recovery.
Click to expand...
Click to collapse
I asked him to clarify what that meant, since all he said was "no recovery". Which is much too vague, and can mean a lot of different things.
I also posted the link to the stock recovery so he can try to flash it.
---------- Post added at 10:45 AM ---------- Previous post was at 10:39 AM ----------
ersandeepkr said:
He already stated that the recovery is not flashing
Click to expand...
Click to collapse
He only stated that after being prompted for more info (post #7). As I just stated, he only said "no recovery" in his first post, which can mean a lot of different things. His top post is very vague, and doesn't accurately or sufficiently describe his situation.
ersandeepkr said:
you cannot flash anything if the bootloader is locked.
Click to expand...
Click to collapse
You can flash signed files like stock OOS and stock recovery.
Bradl79 said:
what errors is it giving u with the msm tool and where did u download the unbrick tool from? If the msm tool doesn't work its more than likely a hardware issues, b/c that should cure almost any type of brick
Click to expand...
Click to collapse
no error, it's successful, but nothing changes. still bootloop and only fastboot.
redpoint73 said:
I asked him to clarify what that meant, since all he said was "no recovery". Which is much too vague, and can mean a lot of different things.
I also posted the link to the stock recovery so he can try to flash it.
---------- Post added at 10:45 AM ---------- Previous post was at 10:39 AM ----------
He only stated that after being prompted for more info (post #7). As I just stated, he only said "no recovery" in his first post, which can mean a lot of different things. His top post is very vague, and doesn't accurately or sufficiently describe his situation.
You can flash signed files like stock OOS and stock recovery.
Click to expand...
Click to collapse
i can't flash anything. even stock recovery. i'm assuming it's because my bootloader is locked, or is there other way to flash stock recovery?
zeta555 said:
i can't flash anything. even stock recovery. i'm assuming it's because my bootloader is locked, or is there other way to flash stock recovery?
Click to expand...
Click to collapse
What happens when you try to flash something? Goes fastboot return an error? If so, what does it say? This is the kind of detail I already mentioned. Don't just say "I can't flash anything". Give specific details on what exactly occurred, error messages, etc.
redpoint73 said:
What happens when you try to flash something? Goes fastboot return an error? If so, what does it say? This is the kind of detail I already mentioned. Don't just say "I can't flash anything". Give specific details on what exactly occurred, error messages, etc.
Click to expand...
Click to collapse
it said FAILED (remote: Partition flashing is not allowed)
when i try to unlock bootloader it said oem unlock is not allowed
see if this is the same unbricking tool
OnePlus3T.UnbrickTool
ersandeepkr said:
He already stated that the recovery is not flashing because you cannot flash anything if the bootloader is locked. If by any mean boot loader is unlocked, then one is good to go.
You should know that bootloader can be unlocked only if the system OS allowed to do so. But in this case system os is crashed as well as recovery.
Click to expand...
Click to collapse
What? Lol. You can unlock Bootloader even if OS is missing. You just need to type "Fastboot oem unlock" and it's unlocked. The "Allow OEM unlocking" in developer settings doesn't really do anything.
He can unlock Bootloader without any problem, and flash a ROM.
Just to clear things out, what exactly did you do before the device ended in this state?
The usual fault people seems to be doing from what I read in most of these "brick" threads is that they flash non factory recovery (TWRP or the likes) and then lock the bootloader. This resets the OEM unlock and triggers DM-Verity and also ends you with a non-working recovery as the locked bootloader doesn't allow you to boot recovery not signed by Oneplus (all other recoverys than Oneplus original).
In that case you simply shutdown your phone, hold volume up and connect the USB cable which skips fastboot and starts phone in Qualcomm restore com-port mode and from there the Qualcomm factory tool/unbrick tool should restore a phone to working state coming from the mentioned lock-out.
Bradl79 said:
see if this is the same unbricking tool
OnePlus3T.UnbrickTool
Click to expand...
Click to collapse
just tried that one, it said Download Complete. but when i rebooted the phone, still bootloop in the oneplus logo.
thes3usa said:
What? Lol. You can unlock Bootloader even if OS is missing. You just need to type "Fastboot oem unlock" and it's unlocked. The "Allow OEM unlocking" in developer settings doesn't really do anything.
He can unlock Bootloader without any problem, and flash a ROM.
Click to expand...
Click to collapse
how? when i type "Fastboot oem unlock" it said
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
pitrus- said:
Just to clear things out, what exactly did you do before the device ended in this state?
The usual fault people seems to be doing from what I read in most of these "brick" threads is that they flash non factory recovery (TWRP or the likes) and then lock the bootloader. This resets the OEM unlock and triggers DM-Verity and also ends you with a non-working recovery as the locked bootloader doesn't allow you to boot recovery not signed by Oneplus (all other recoverys than Oneplus original).
In that case you simply shutdown your phone, hold volume up and connect the USB cable which skips fastboot and starts phone in Qualcomm restore com-port mode and from there the Qualcomm factory tool/unbrick tool should restore a phone to working state coming from the mentioned lock-out.
Click to expand...
Click to collapse
i'm browsing the news on my phone and checking my whatsapp. never flash anything to this phone before. all i ever did is update the os when there's OTA notification.
zeta555 said:
just tried that one, it said Download Complete. but when i rebooted the phone, still bootloop in the oneplus logo.
how? when i type "Fastboot oem unlock" it said
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
i'm browsing the news on my phone and checking my whatsapp. never flash anything to this phone before. all i ever did is update the os when there's OTA notification.
Click to expand...
Click to collapse
oh so u never actually flashed anything? if that is the case more than likely its hardware issues, the mobo will need to be replaced, u may want to contact OnePlus, I read somewhere else that someone had a similar issue, if the msm tool does not work then its going to be hardware issues. Are u still under warranty?
Bradl79 said:
oh so u never actually flashed anything? if that is the case more than likely its hardware issues, the mobo will need to be replaced, u may want to contact OnePlus, I read somewhere else that someone had a similar issue, if the msm tool does not work then its going to be hardware issues. Are u still under warranty?
Click to expand...
Click to collapse
nope, never flash anything.
my phone is 1 year and 2 weeks old, and sadly I'm not in a country where oneplus operate so no warranty.
Related
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
OK so I assume you have a pretty descent idea of what your doing but just to be sure... Your bootloader is unlocked when trying to flash stock via vast opt right? If it's not unlocked you can't modify system. Your using the Jeter firmware not aljeter right?
Can you grab screen shots of the errors to see if maybe there's something we see that you didn't that might be relevant.
Also stick to one thread per issue. That way we know what others ha e suggested, exactly what you have done, the outcome, etc.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Right, Lets begin....
Originally i followed a guide to root my g6 play,that was by booting a patched twrp, and dm verity and another file beginning with Q, then flash the twrp........... all that was working except dm verity which gave a error (cant remember which one)
i have tried a different number of firmwares (motorola themselves said try jeter and alijeter - as some alijeter firmware are for my model xt1922-2)
now there was a OTA, as far as I can remember, there was 2 ota updates, they went smoothly, but still the BAD KEY message (brought on by the patched dm verity file i think)
after doing this ota, the oem unlocking button was no longer greyed out, so i tried fastboot oem lock but it gives errors about bootloader bad key and more, or invalid android image
whatever happens, i cannot relock the bootloader to remove the message, i cant flash any firmware for my model without one or two errors.......
the only thing that works, to show the bootloader is locked, is fastboot flashing_lock (as my bootloader screen shows flashing_unlocked) this shows, by doing fastboot getvar all and all that, that the bootloader is relocked....but I still have bad key error, and then have to oem unlock again to do anything.....help
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Again is your bootloader unlocked when flashing stock?
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
biggary said:
yes, on the bootloader screen, it says flashing_unlocked
and on the development setting its greyed out and says bootloader is already unlocked
Click to expand...
Click to collapse
Ok so let's put this out there first. I am helping you for free because I generally enjoy being a helping hand! I asked for screenshots, which we still have not gotten. I asked if bootloader was unlocked still to be sure, because I wasn't sure if you had tried to relock it. I think you did try to relock based on your post, but I had to ask twice to get that information out of you. If you truly want help, help those who want to help you help yourself.
That said, I asked for screenshots because I have never heard of a "bad key" error. The way I understood it you were seeing this error in TWRP. After a quick google search I found this image:
https://forums.lenovo.com/lnv/attachments/lnv/230/6043/1/IMG-20170528-WA0015.jpg
I assume this is the same error you see? If so, you can actually ignore it. If you don't want to ignore it, you can try going to bootloader and type this: fastboot oem fb_mode_clear
Also, you can try to see if there is a modified logo.bin for your device and flash it. You could try the G6+ logo.bin possibly:
https://forum.xda-developers.com/moto-g6/themes/bootlogo-remove-message-unlocked-t3789155
PS: I found this info with a quick google search, so I assume you didn't even bother to search?
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
I am having the same issue as you, i am trying so much that i forget about doing root and just want to lock my bootloader again ;-;
The XT1922-2 is an annoying little ****.
biggary said:
Yes, I always search several times, and read other forums to see if error is posted elsewhere.
Its hard to take a screenshot when the phone is in bootloader mode.
the screen is totally black. it shows just in the top left hand corner with the words 'bad key' and if I installed magisk (I dont install twrp, I just boot into it), I get the message 'N/A', the bad key is caused by errors when flashing the stock firmware, for some reason, thats why I cant remove the message, or relock the bootloader.
The bootloader unlocked messages that you linked to, are completely different looking than mine.
One thing confuses me, when you boot into bootloader, it says JETER, as the model name, but no JETER firmware flashes properly, my phone is a xt1922-2 which for some reason posted everywhere as ALIJETER........ god, this phone is a pain in the arse!
Click to expand...
Click to collapse
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
w4r3zgod said:
I agree it's a pain in the arse! Can't get past it at all! If I had the knowledge to work on the kernel and bootloader i'd make a custom bootloader that atleast said lenovo sucks instead.
All other moto G6 variants will haev the error that the other guy linked to, same as my Moto g5, G, E, and X did.
My E3 is worse as that has a Mediatek CPU lmao
Click to expand...
Click to collapse
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
madbat99 said:
You can't get rid of it. You likely cannot relock bootloader. Warranty is void just by requesting unlock code. @biggary same
Click to expand...
Click to collapse
Yea warranty void.
biggary said:
Hello Forum, this phone is really getting to me now.
I just want to return the phone to complete stock, box fresh with no messages about boot loader etc
as I may return the phone for another one
but in all my 11 years on xda, I have never had a problem like this phone.....
Bloody boot-loader messages, re-locking bootloader, returning to stock, firmware files...
I cant whatever i try, get rid of the N/A (if i use TWRP to install magisk) or BAD KEY if I dont use TWRP
My Phone details are as follows
its a xt1922-2 UK Generic Phone, it has had the OTA update (the June 2018 one), its a Moto G6 play JETER
Build Number is OPP 27.91.87
It doesnt matter whatever firmware I download, whether the flashing gives errors or not in FASTBOOT
I cant get rid of the error message n/a or bad key!!!
whenever I try to lock bootloader, by fastboot oem lock..... it say run the command again, I run the fastboot code again, and it gives a error, something similar to please flash a valid android image, I CAN relock it by using : fastboot flashing lock ........... but still the bootloader error is there!!! HELP!!!!
Click to expand...
Click to collapse
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
Click to expand...
Click to collapse
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
jdavidm2 said:
I finally found this last night. Didn't remove the n/a, but it replaced the boot logo image with something that mostly hides it.
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
https://www.getdroidtips.com/moto-g6-plus-unlocked-bootloader-warning
Click to expand...
Click to collapse
I found this for another g6. Use the firmware for your model and it may work.
https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292/post78432631
I'm doing some research before I commit to unlocking my bootloader, and I can't find anything definitive on whether or not it's possible to re-lock after unlocking with the official tool. I have experience unlocking and re-locking bootloaders, flashing custom recoveries/ROMs/kernels etc but only with Nexus and Samsung phones, so I just want to make sure I'm clear on how Nokia's setup differs (If at all). Would also be interested to find out if Nokia will still offer me OTA's with unlocked bootloader.
Thanks for any help, and feel free to move or close the thread if it matches another one that I've missed.
Bb
2WildFirE said:
I'm really sure you can relock bootloader. Why not?
And yes ota works fine with open bootloader if you are on stock
Click to expand...
Click to collapse
Awesome, cheers for the assist ?
2WildFirE said:
I'm really sure you can relock bootloader. Why not?
And yes ota works fine with open bootloader if you are on stock
Click to expand...
Click to collapse
Nokia says that relooking isn't possible. Is there anybody who tried the command 'fastboot oem relock'?
And why says this text please lock ? the bootloader, if it is not possible?
2WildFirE said:
And why says this text please lock ? the bootloader, if it is not possible?
Click to expand...
Click to collapse
Dude, crop out that serial number?
Go to download mode
Run adb:fastboot oem lock
Choose lock bootloader in your phone
namle98 said:
Go to download mode
Run adb:fastboot oem lock
Choose lock bootloader in your phone
Click to expand...
Click to collapse
confirmed, i did it today
Since I also unlocked critical, I ran: fastboot oem lock_critical and then fastboot oem lock
Phone will factory reset both times.
Has anyone tried the re-lock with a custom kernel/ROM?
dimitar10 said:
Has anyone tried the re-lock with a custom kernel/ROM?
Click to expand...
Click to collapse
No, and nobody should do it. It will brick your device.
The point of a locked bootloader is to prevent unofficial software from running, and the point of unlocking it is to make that possible. So relocking the bootloader with unofficial software installed will make the phone think that the software got corrupted and rightfully lock down the device.
THMSP said:
No, and nobody should do it. It will brick your device.
The point of a locked bootloader is to prevent unofficial software from running, and the point of unlocking it is to make that possible. So relocking the bootloader with unofficial software installed will make the phone think that the software got corrupted and rightfully lock down the device.
Click to expand...
Click to collapse
Basically anyone should be able to do it and it shouldn't brick your device, as per Google's bootloader recommendations. However, manufacturers decide to cripple bootloaders not to support it in the verified boot chain (where kernel verification can be explicitly made against a custom root of trust set after the device has left the factory i.e. set by the user, instead of the original root of trust). As far as I know, only Pixel devices implement this, and can be achieved by issuing the command:
Code:
fastboot flash avb_custom_key <key_blob>
I'm sure there are lots of advanced users/modders that can find this feature beneficial (if implemented by the device vendors).
dimitar10 said:
Basically anyone should be able to do it and it shouldn't brick your device, as per Google's bootloader recommendations. However, manufacturers decide to cripple bootloaders not to support it in the verified boot chain (where kernel verification can be explicitly made against a custom root of trust set after the device has left the factory i.e. set by the user, instead of the original root of trust). As far as I know, only Pixel devices implement this, and can be achieved by issuing the command:
Code:
fastboot flash avb_custom_key <key_blob>
I'm sure there are lots of advanced users/modders that can find this feature beneficial (if implemented by the device vendors).
Click to expand...
Click to collapse
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
Code:
fastboot flash avb_custom_key <key_blob>
how to use this code? any specific key_blob for nokia 8 or is it supported on this phone?
help me guys ;(
Edit:
After so many tries, I went to service centre and they fixed the phone in few mins :highfive::silly:
Crazy Tweaks said:
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
Code:
fastboot flash avb_custom_key <key_blob>
how to use this code? any specific key_blob for nokia 8 or is it supported on this phone?
help me guys ;(
Edit:
After so many tries, I went to service centre and they fixed the phone in few mins :highfive::silly:
Click to expand...
Click to collapse
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
CommieTurtle said:
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
Click to expand...
Click to collapse
Did they fix it for free since bootloader is locked? I'm going to service centre in few hours
CommieTurtle said:
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
Did they fix it for free since bootloader is locked? I'm going to service centre in few hours
Click to expand...
Click to collapse
Well it wasn't in warranty xD so just asked me this and boom it was not free after that but well yeah it doesn't matter if it's locked or unlocked lol as long as they are getting paid, they'll do it hahahha
Crazy Tweaks said:
Well it wasn't in warranty xD so just asked me this and boom it was not free after that but well yeah it doesn't matter if it's locked or unlocked lol as long as they are getting paid, they'll do it hahahha
Click to expand...
Click to collapse
lol my device was under warranty so I got it fixed for free
I can assume that, in service centers, they are able to reflash the entire firmware including the (secondary) bootloader. They would probably boot the device into EDL mode, and flash it with stock firmware, with a properly signed Qualcomm EDL programmer, and use Qualcomm's QFIL tool to do this.
CommieTurtle said:
lol my device was under warranty so I got it fixed for free
Click to expand...
Click to collapse
Glad to hear that
Hello, how do I completely unlock the bootloader?
When I try to do "fastboot erase recovery/boot/system" for example - it tells me that I am not allowed to.
I unlocked the bootloader so why did I get a partial unlock?
ThisIsRussia said:
Hello, how do I completely unlock the bootloader?
When I try to do "fastboot erase recovery/boot/system" for example - it tells me that I am not allowed to.
I unlocked the bootloader so why did I get a partial unlock?
Click to expand...
Click to collapse
Why would you want to erase any of those in fastboot? Are you trying to flash a custom ROM or something? Why not use TWRP instead? Unless you're trying to flash a GSI, in which case I've never seen anyone suggest erasing anything other than userdata, or maybe system, in fastboot.
Are you purposely trying to brick your device?
If you used an unlock code to unlock your bootloader, then it fully unlocked. However, there are still limitations. For instance, you cannot downgrade the bootloader after upgrading to Pie.
If you want another recovery, just flash another recovery. If you need to flash another boot.img, then just flash it. I can't think of any valid reason to do what you're trying to do.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
ThisIsRussia said:
Yeah, sorry I was a little upset because they are always responding with phrases like "soon it will be updated" etc.
Since February. Its May now.
I just don't use Motorola phones anymore and if someone asked me for opinion I didn't recommend Motorola/Lenovo.
They are a bunch of liars. period.
Click to expand...
Click to collapse
If you're not using Motorola phones anymore, then why are you worried about modifying one?
If you're so distraught over the experience, just get another phone and move on.
ThisIsRussia said:
Hello, how do I completely unlock the bootloader?
When I try to do "fastboot erase recovery/boot/system" for example - it tells me that I am not allowed to.
I unlocked the bootloader so why did I get a partial unlock?
Click to expand...
Click to collapse
It's either unlocked or not. There is no partial unlock. Why are you trying to erase recovery? Or boot? You simply flash over those. You're attempting things that will for sure brick that phone. Maybe that's why the bootloader doesn't allow it.
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
Hello
Hoping somebody can help getting my phone up and running again.
I wanted to unroot my phone, because i was having issues with danish "MitId". And was a bit sloppy with it.
First i tried using SuperSU to remove root. Because i didnt feel like setting everything up again. Didnt work.
Then I locked the OEM Lock in developer settings. Not thinking this would be a fatal error.
Got home from work, and said to myself. Jusk lock the bootloader and the phone will reset itself.
But this is not the case, when you have been stupid enough to lock the OEM lock.
Now I am stuck on "No valid operating system could be found. The device will not boot"
I can get in to fastboot by pushning power+vol down. But cannot flash anything since the phone thinks the OEM Lock is locked on it.
Does anyone know of a solution for me. Or is it going to the shop tommorow and say that my phone is going this. And hope they will sort it for me?
Can't you fix stuff by using https://flash.android.com/ ?
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Pearsondk said:
No, unfortuantly not. It fails:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
Click to expand...
Click to collapse
Try sideloading the full OTA. You don't need an unlocked bootloader for that.
Unfortuatly not, if I try to enter recovery mode. The phone just goes back to the screen saying "No valid operating system could be found. The device will not boot"
ADB is not available to me
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
*****I apologize I just saw it's actually still locked****"
Contact U-break I-fix if I typed that correctly. The third party warranty repair center for Google's warranty. I believe they can attempt to switch the boot slot with a locked bootloader with the equipment they use to reflash these devices. If anything it's under warranty get the RMA and if the bootloader is locked on it trade someone or sell it and use it to make buying a new cheaper..
JovialQuestion said:
Can you get into recovery at all. Even if it's the stock you can attempt a sideload of the stock OTA.zip from Google. You may also try if your on boot slot A
fastboot --set-active=b
On b use
fastboot --set-active=a
Try to see if the other boot slot has an a bootable OS.
Click to expand...
Click to collapse
No, I can get into fastboot and that is it.
But everything I try in fastboot gets rejected, since it says the phone is locked.
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
JovialQuestion said:
Does the bootloader screen on the phone have the option to boot into Rescue. This has a ADB connection but I am not sure if adb sideload works. Use the volume keys and power button to select it
Click to expand...
Click to collapse
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
Google is not responsible for phone's with locked bootloaders. They make the device with the specifications the carrier that sells it stipulates. Google themselves allows the unlock.
Lughnasadh said:
If you can't sideload the OTA, I'm afraid there is not much else you can do with a locked bootloader except try to RMA it.
Click to expand...
Click to collapse
Iam guessing the same. Phone doesnt want to do anything.
And since i cant get into the phone to oem lock i am stuck. Live in Denmark, so by law I havnt voided the warrenty by rooting.
Pixel warranty is always valid even if you unlock and root. Google doesn't void the warranty. Go to Google pixel support page. Find warranty and act as if your submitting a RMA and it will tell you after you enter the device IMEI how long your warranty is valid for
Delete
If that were true. Android flash tool https://flash.android.com/welcome
Would work as it's the same process for the browser to flash the very same file. Motorola allowed signed factory img on locked. Google had never allowed that in fastboot as far as I am aware
DroidRommer said:
All you need to do is go here Factory pixel firmwares and scroll down to pixel 7 panther assuming you're not on the pro (cheetah)
-select the latest version for your model whether that's Verizon or whatever if you have the carrier unlocked one like myself just choose the Feb firmware that doesn't have a carrier name at the end of the firmware number (you should have your phone plugged into your PC and in fastboot mode) click flash and follow the steps. These are Googles factory images so it doesn't matter if your bootloader is unlocked or not as long as you choose the latest version and the correct version for your phone. Tbh you can't really brick the pixel 7 as long as you have a PC and are able to put the phone in fastboot mode (holding the volume down and power button while powering on)
-Anytime you run into some kind of bootloop issue or wanna get rid of root flashing the stock firmware from this website will factory reset and revert your phone to the way it was the very first time it was pulled out of the box and powered on. If you have already tried this and you know forsure you did everything correctly then I must admit I have never had this happen and I'm someone who flashes custom roms and goes back to stock to get the latest security update just to turn around and flash another custom rom right after lol. If you need any help or advice feel free to pm me whenever. I have been rooting phones for a long time and have to say that the Google pixel is by far the most user friendly phone I've ever owned when it comes to custom rooms, rooting etc. You can ALWAYS go back as long as you know what steps to take. Sorry for the rant especially if you already figured it out.
Happy Customizing!
DROIDROMMER
Click to expand...
Click to collapse
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Kofa1 said:
Really mad that Google intentionally locks phones this way, turning them into completely functional, but useless piece of junk. I guess that's late stage capitalism for you xD
Click to expand...
Click to collapse
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Edit: I was not aware you couldn't flash the stock firmare using googles dev page without oem unlock. I apologize for jumping to conclusions. I thought I had every possible bad scenario happen to me by now but apparently I learned something new today.
DroidRommer said:
This wouldn't be Google, they basically encourage you too unlock the bootloader and root if you want as they give you all the tools you need and factory firmware options to go back if you make a mistake. Tbh if you are able to unlock and root the phone to start then you can go back. Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader. If we really wanna poke at some phone developers I vote Samsung as I have had multiple people ask me to root their phones and if it's a US snapdragon version it cannot be done its so frustrating lol thanks for letting me vent, have a great day if you have the the carrier unlocked dev edition of the pixel 7 and ever need any help feel free to pm me. I have been rooting and romming pixels for a long time
Click to expand...
Click to collapse
Dude. You cannot flash factory images of any kind on any Google phone with the bootloader in locked status. Please stop giving false information on here. If you want to talk up Samsung do it on a Samsung post. Let's not confuse everyone please
DroidRommer said:
Even with a locked bootloader you can always flash the latest factory image on googles dev website, you just can't downgrade firmware or install different carrier firmware without the unlocked bootloader.
Click to expand...
Click to collapse
To use Android Flash Tool, you have to have OEM Unlocking enabled in Developer Options for it to be able to unlock the bootloader.
To flash the factory image in fastboot you must have an unlocked bootloader.
Lughnasadh said:
Their bootloader is locked. You cannot flash a factory image like that with a locked bootloader. They also turned off OEM Unlocking in the developer settings. If they had left this enabled they would be able to use Android Flash Tool as that tool will unlock your bootloader if OEM Unlocking is enabled.
Click to expand...
Click to collapse
Okay my bad you are right fortunately I have never had this happen. And like someone else said if he can't get into recovery then he can't sideload a factory ota... sorry I'm at a loss on this one. Some custom roms use "fastboot update file.zip" would that do anything in this case or would that command not even work with a locked bootloader I'm assuming. I apologize for trying to act like a know it all I've just never heard of this happening