Related
Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.
Hi Guys, Just to let everyone know the command for unlocking the bootloader is now "fastboot flashing unlock" oem unlock will return an error and no longer functions.
Isn't the command just "fastboot oem unlock"?
overlord727 said:
Isn't the command just "fastboot oem unlock"?
Click to expand...
Click to collapse
Not anymore it would seem.... fastboot oem unlock returns an error
according to the android developer FAQ, "flashing" is the correct command, but I can't figure out why.
https://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
God, I thought I was going crazy. Unknown command error returning had me confused as ****. Good to know I'm not the only one.
it made me start to wonder if OEM would somehow trigger the fuse, whereas FLASHING is specifically designed not to. anyone know why there's a "unlock bootloader" switch in the developer options within Android?
Is it confirmed that 'fastboot flashing unlock' is the new command now then?
Kitch16 said:
God, I thought I was going crazy. Unknown command error returning had me confused as ****. Good to know I'm not the only one.
Click to expand...
Click to collapse
I know, I spent ages trying to get it to work on my Laptop and Desktop before I discovered about the new command. It was really getting annoying as I was desperate to setup the device but didn't want to do it before the bootloader unlocking wipe.
Kitch16 said:
Is it confirmed that 'fastboot flashing unlock' is the new command now then?
Click to expand...
Click to collapse
Yes, Confirmed on my 6P.
Cheers bud, saved me spending more than the 30 mins I have already done pulling my hair out.
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
Tung_meister said:
I know, I spent ages trying to get it to work on my Laptop and Desktop before I discovered about the new command. It was really getting annoying as I was desperate to setup the device but didn't want to do it before the bootloader unlocking wipe.
Yes, Confirmed on my 6P.
Click to expand...
Click to collapse
Did it trip your eFuse?
Kitch16 said:
Did it trip your eFuse?
Click to expand...
Click to collapse
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
What happens if you flash TWRP AFTER unlocking bootloader?
I came across a cautionary note that you may bootloop.
fron 5X forum
"So I fastboot unlocked my bootloader and flashed TWRP straight after. Now stuck in bootloop between "your device software cant be checked for corruption" orange screen and TWRP first install Failing."
.
Before I try anything trying to sort out how Marshmallow alters unlock, root, flash game.
.
Born<ICs said:
What happens if you flash TWRP AFTER unlocking bootloader?
I came across a cautionary note that you may bootloop.
fron 5X forum
"So I fastboot unlocked my bootloader and flashed TWRP straight after. Now stuck in bootloop between "your device software cant be checked for corruption" orange screen and TWRP first install Failing."
.
Before I try anything trying to sort out how Marshmallow alters unlock, root, flash game.
.
Click to expand...
Click to collapse
TWRP isn't available for the Nexus 6P yet!
But when it is available, we'll have to cross that bridge when we come to it.
Also if I'm not mistaken buttons to get to Fastboot are now Vol Up+Vol Dn+Pwr vs old Pwr+Vol Dn
Born<ICs said:
Also if I'm not mistaken buttons to get to Fastboot are now Vol Up+Vol Dn+Pwr vs old Pwr+Vol Dn
Click to expand...
Click to collapse
I got in to Fastboot by holding volume down and powering on the phone as normal.
JustinTrouble said:
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
Click to expand...
Click to collapse
So what causes the Qfuse to blow?
Being a Nexus device shouldn't command be fastboot oem unlock. Curious
On the official Google Developers Factory Images page it’s still “fastboot oem unlock”.
http://forum.xda-developers.com/nexus-6p/general/fastboot-unlocking-command-t3233722/page2
To add to this also make sure your Android SDK is fully up to date
JustinTrouble said:
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
Click to expand...
Click to collapse
how are you checking qfuse status? i thought the process of unlocking the bootloader trips it?
indianajonze said:
how are you checking qfuse status? i thought the process of unlocking the bootloader trips it?
Click to expand...
Click to collapse
Does qfuse trip if you relock bootloader?
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
GCbard said:
Does qfuse trip if you relocation bootloader?
Click to expand...
Click to collapse
Does qfuse trip if one flashes a rom?
Jose-MXL said:
CAN ANYONE IN THIS THREAD AND WITH THE INTENTIONS OF UNLOCKING THE BOOTLOADER PLEASE CAPTURE THE OTA PER THE POST BELOW:
http://forum.xda-developers.com/axon-7/how-to/to-unlock-bootloader-hold-help-t3437617
Sorry the harsh capitals, we need more visibility on this.
In case someone with the intentions of unlocking the bootloader reads this, there is an OTA being pushed to devices when they request the bootloader unlock, it is very important for development to capture these OTAs.
Click to expand...
Click to collapse
OK guys this seems to be great NEWS , yeahhh....
Here is the link for the step provided by [email protected] Community.
https://community.zteusa.com/docs/DOC-1193?et=watches.email.document
And I'll add as attachment the PDF file for the steps..so far seems like is super easy.
I'll be writing the steps here later today , I'm using my phone as we speak and is not easy getting all that info here hehehe.
P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS WILL WIPE INTERNAL STORAGE AND DATA .....
P.S.S. Looks like one of the Steps for Unlocking is a FOTA (Forcce OTA) without it the steps above are useless
Copy-Paste from the other thread:
If you read the document looks like unlocking the bootloader boils down to "fastboot oem unlock", like you'd do on any Nexus
If this is the case, it's pretty good, because it means that the procedure isn't tied to the phone's IMEI.
Btw, I've tried doing it, and it didn't work, so I guess there'll be another OTA soon to actually activate the unlocking, and that must be the OTA that it's been referred to in the instructions
AlesG87 said:
Copy-Paste from the other thread:
If you read the document looks like unlocking the bootloader boils down to "fastboot oem unlock", like you'd do on any Nexus
If this is the case, it's pretty good, because it means that the procedure isn't tied to the phone's IMEI.
Btw, I've tried doing it, and it didn't work, so I guess there'll be another OTA soon to actually activate the unlocking, and that must be the OTA that it's been referred to in the instructions
Click to expand...
Click to collapse
Did you enable "OEM Unlocking" under Developer Options?
yep, it was enabled
I think they push out an OTA update specific to your device to let this happen. We need someone to capture it.
Actually. It sounds like they will send you a specific file for your device that you will install per instructions.
AlesG87 said:
yep, it was enabled
Click to expand...
Click to collapse
dennis96411 said:
I think they push out an OTA update specific to your device to let this happen. We need someone to capture it.
Click to expand...
Click to collapse
mmmm, i'm doing a Device Backup (Data/Apps , MMS,Text and internal storage) and give it a try...report back as soon i get something.
AlesG87 said:
yep, it was enabled
Click to expand...
Click to collapse
At which point in the process did you notice it not working for you? You do have the B20 update installed, correct?
Well, I skipped all the useless stuff about the SDK since I'm on linux, just made sure adb debug and unlock switches were on and did
adb reboot bootloader
fastboot oem unlock
Got "FAILED (remote: unknown command)" response in the terminal
AlesG87 said:
Well, I skipped all the useless stuff about the SDK since I'm on linux, just made sure adb debug and unlock switches were on and did
adb reboot bootloader
fastboot oem unlock
Got "FAILED (remote: unknown command)" response in the terminal
Click to expand...
Click to collapse
What about "fastboot devices"?
swehes said:
Actually. It sounds like they will send you a specific file for your device that you will install per instructions.
Click to expand...
Click to collapse
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Wait, try to save the OTA for research purposes before you install!
charlie.s said:
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Click to expand...
Click to collapse
Same here, I was pushed an update.
charlie.s said:
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Click to expand...
Click to collapse
were you able to capture it?
and yeah Doesn't work without the OTA for unlocking :'( .....
I hope someone can save it and upload it here so the developers can have a look.
Worked for me. I updated the phone via settings. The file was about 50MB...I think. When connected to the PC, you have to choose "install driver" instead of MTP/PTP.
"P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS MAY or WILL WIPE INTERNAL STORAGE AND DATA ....."
There's no MAY, I just did it and it WILL erase your data.
Rats -- I hit the trigger too quickly, so I can't capture the file. For future reference, how can I do that?
CandyFoxJ said:
"P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS MAY or WILL WIPE INTERNAL STORAGE AND DATA ....."
There's no MAY, I just did it and it WILL erase your data.
Click to expand...
Click to collapse
Unlocking/locking the bootloader will always format the userdata partition.
charlie.s said:
Rats -- I hit the trigger too quickly, so I can't capture the file. For future reference, how can I do that?
Click to expand...
Click to collapse
Does the update install as soon as it finishes downloading?
Made a bit of a boob here. I was upgrading my firmware version 10v to the new January firmware using LGUP. Unfortunately i forgot to click Upgrade, and so by accident ran the refurbish command.
The 'upgrade' ran through OK, and it boots, but I lost root/twrp (im on H930).
When I tried to bung TWRP back on, I cant get the fastboot boot twrp.img command to work (sorry if syntax is wrong while typijg this message) - that command just reboots the phone but it sits of the LG v30 loading screen.
Ive noticed that the fastboot screen tells me to make sure I flip the OEM Unlock switch in Dev options (a blue message). However, that setting is greyed out. Running the getvar command says I am unlocked though, as does re-running the unlock command.
So im confused. Im guessing i cant install TWRP as fastboot mode thinks im locked?
Any ideas??
Sent from my LG-H930 using Tapatalk
It may say you are unlocked, but you are not. Once you are rooted, you should never flash a KDZ -- especially if you are unlocked via the unlock.bin method. If you want to upgrade, flash the firmware via TWRP.
But you are in this situation now.... so, have you tried flashing unlock.bin again?
-- Brian
runningnak3d said:
It may say you are unlocked, but you are not. Once you are rooted, you should never flash a KDZ -- especially if you are unlocked via the unlock.bin method. If you want to upgrade, flash the firmware via TWRP.
But you are in this situation now.... so, have you tried flashing unlock.bin again?
-- Brian
Click to expand...
Click to collapse
Hi Brian
Yeah, if i try flash the unlock.bin file again i get an error telling me im already unlocked (or words to that affect...im away from my PC so can't see the exact message)
Sent from my LG-H930 using Tapatalk
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
runningnak3d said:
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
Click to expand...
Click to collapse
Awesome Brian, thanks loads for the help. I'll PM you the Zip as soon as ive done it
Sent from my LG-H930 using Tapatalk
runningnak3d said:
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
Click to expand...
Click to collapse
Brian, quick question. Would i need to be rooted to create the dumps....?
Sent from my LG-H930 using Tapatalk
Nope.
-- Brian
thenoble06 said:
Any ideas??
Click to expand...
Click to collapse
Since you flashed a fully stock rom, can you try to do 'fastboot oem lock' and then check developer settings if OEM unlocking became active so you can flip it to ON again?
padmanek said:
Since you flashed a fully stock rom, can you try to do 'fastboot oem lock' and then check developer settings if OEM unlocking became active so you can flip it to ON again?
Click to expand...
Click to collapse
Ahhh cool, that did it. Re-locked, flashed latest KDZ with LG UP and then relocked, installed Recovery and re-rooted.
Jobs a good un!
I'll stay away from KDZ files now and just update/upgrade via TWRP (that's right yeah)?
Thanks both for your help!!
Sent from my LG-H930 using Tapatalk
Hello,
After receiving my new Motorola x40 I realized that I wasn't able to use my GooglePay nor did it have other language support. So I decided to unlock my x40 bootloader via https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your- device-a
It all worked. I managed to install a global rom with all the google apps and extra language support.
However, Global rom didn't allow my GooglePlay to use my cards or backup via googleOne since the flashing was unlocked. So I went to fastboot to " fastboot flashing lock". After which my cards were able to work.
After few days of using global rom I decided to go back to chinese one since I found it a bit easier to navigate.
So when I decided to go back to my old chinese rom, in "Developer Options" OEM unlocking says "Connect to the internet or contact your operator" and it is greyed out.
I tried using " fastboot flashing/oem unlock" in fastboot however it tells me that i need to unlock it in " developer options " first.
My phone has already been connected to wifi for around 90 hours on a Global rom And around a week before I transitioned from Chinese room over to global rom.
How long do I need to be connected to the internet or what operator do I need to contact to unlock my OEM again? Or maybe there is another way to unlock OEM without waiting?
Things I tried and failed:
1) Factory reset
2) Wipe/Cache reset via recovery3) "fastboot flashing/oem unlock" via bootloader
Global rom used: https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETGB/
Have same problem.
cryptm said:
Have same problem.
Click to expand...
Click to collapse
How many days are you in this state? maybe you are closer to 7 days than I am
The toggle to unlock the bootloader is now enabled for me after 8 days. I have the Edge 40 Pro.
mine too, didn't look before, i own mine since 14 april
Ok so the theory is that once you get a global rom and "fastboot oem lock", it will act like new phone and will only unlock after 7-8 days. Guess will have to wait to test this theory out.
zeakey said:
Ok so the theory is that once you get a global rom and "fastboot oem lock", it will act like new phone and will only unlock after 7-8 days. Guess will have to wait to test this theory out.
Click to expand...
Click to collapse
Any update whether you can toggle OEM Unlocking?
Also, as someone who have been using Moto phones from China for years, CN ROM is way way way better the Global ROM when it comes to features and software updates. One useful feature is the built in Motorola Wallet app where I can use my phone as keycard and transpo card.
ijuanp03 said:
Any update whether you can toggle OEM Unlocking?
Also, as someone who have been using Moto phones from China for years, CN ROM is way way way better the Global ROM when it comes to features and software updates. One useful feature is the built in Motorola Wallet app where I can use my phone as keycard and transpo card.
Click to expand...
Click to collapse
Nope. Still not unlocked. Waiting for new firmware updates. So far EU region didn't get any.
zeakey said:
Nope. Still not unlocked. Waiting for new firmware updates. So far EU region didn't get any.
Click to expand...
Click to collapse
Supposedly OTA updates are being released, some can update successfully, others can't. Keep us updated if you're able to successfully update.
JustHereForNow said:
Supposedly OTA updates are being released, some can update successfully, others can't. Keep us updated if you're able to successfully update.
Click to expand...
Click to collapse
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
zeakey said:
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
Click to expand...
Click to collapse
I'm assuming it's a Motorola issue. I'm assuming maybe even real Edge 40 Pro devices can't unlock yet? Honestly if OTA works and so do all features (banking, 5g, etc) then I have no problem doing the conversion.
zeakey said:
I did update from from 20-15 to 20-28 version. OEM still didn't get unlocked
Click to expand...
Click to collapse
Does this mean you were able to update to 20-28 even with the locked bootloader (and locked OEM)?
Zechosenjuan said:
Does this mean you were able to update to 20-28 even with the locked bootloader (and locked OEM)?
Click to expand...
Click to collapse
I also updated without problem with bootloader closed and oem blocked and everything fine in the same way I solved the vpn and everything at 100 on the computer
ziggmax said:
I also updated without problem with bootloader closed and oem blocked and everything fine in the same way I solved the vpn and everything at 100 on the computer
Click to expand...
Click to collapse
What tools\steps did you take to update while bootloader and OEM are locked?
Zechosenjuan said:
What tools\steps did you take to update while bootloader and OEM are locked?
Click to expand...
Click to collapse
Using TinyFastbootScript flashing the reteu rom But when I installed it I blocked the bootloader thinking that it could be opened again to my surprise I could no longer activate the box so I have to wait and see if with any update I can go back To activate that option To activate that option
ziggmax said:
Using TinyFastbootScript flashing the reteu rom But when I installed it I blocked the bootloader thinking that it could be opened again to my surprise I could no longer activate the box so I have to wait and see if with any update I can go back To activate that option To activate that option
Click to expand...
Click to collapse
You won't be able to unlock the bootloader twice, impossible it's done by design by motorola.
You can only unlock your bootloader once
jody2k said:
You won't be able to unlock the bootloader twice, impossible it's done by design by motorola.
You can only unlock your bootloader once
Click to expand...
Click to collapse
does this mean the phone that went through unlock\lock of the BL will never get a firmware update (whether OTA or manual)?
Zechosenjuan said:
does this mean the phone that went through unlock\lock of the BL will never get a firmware update (whether OTA or manual)?
Click to expand...
Click to collapse
It's possible that we won't get OTA, only will know for sure in the future, i'm in the same situation.
But you can always manually update your firmware with rescue tool or through ADB as long it's the official firmware. You don't need a unlocked bootloader for that
jody2k said:
It's possible that we won't get OTA, only will know for sure in the future, i'm in the same situation.
But you can always manually update your firmware with rescue tool or through ADB as long it's the official firmware. You don't need a unlocked bootloader for that
Click to expand...
Click to collapse
This gives hope. Can you link me to flashing through adb? So far have only seen fastboot and magisk.
Zechosenjuan said:
This gives hope. Can you link me to flashing through adb? So far have only seen fastboot and magisk.
Click to expand...
Click to collapse
I think this method would work:
I screwed up...moto X40 bricked / Any EDL mode available?
Hi guys sadly I completely softbricked my motorola X40 phone i'm a idiot. I flashed to a wrong firmware file (edge 30 pro) and re-locked bootloader then found it phone doesn't properly boot anymore. I can boot it in fastboot mode but flashing in...
forum.xda-developers.com
But I think this will erase all your data so it's not a real "upgrade firmware" method
I also found out there is an "software update" in the lenovo rescue tool
Maybe it's worth the shot to try this out too, but for me it's says I have the latest firmware already (which is correct) so I can't test it out right now.