Hi all! Im not a motorola user of any sorts, but a friend of mine, who's not a great english speaker and doesn't have an xda account, bricked, or at least so it seems, his Moto X 2014 (xt1097).
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader...
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
ad astra said:
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
Click to expand...
Click to collapse
This is only true if he upgraded to 5.1, which it sounds like he did.
ad astra said:
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader.
Click to expand...
Click to collapse
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
ad astra said:
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
Click to expand...
Click to collapse
You in fact cannot flash a ROM with a locked bootloader.
ad astra said:
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
Click to expand...
Click to collapse
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
JulesJam said:
This is only true if he upgraded to 5.1, which it sounds like he did.
Click to expand...
Click to collapse
Yep, that's exactly the case.
JulesJam said:
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
Click to expand...
Click to collapse
If i'm not mistaken it was the other way around. He tried to update to 5.1 (I believe that the zip was form a different vendor).
JulesJam said:
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
Click to expand...
Click to collapse
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
JulesJam said:
You in fact cannot flash a ROM with a locked bootloader.
Click to expand...
Click to collapse
I understand what you mean, I meant that you can flash updates from sdcard with stock recovery.
JulesJam said:
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
Click to expand...
Click to collapse
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one. So.. we didn't check that. What's the difference between both? Now he managed to flash (with unlocked bootloader) the 5.1 rom and his bootloader version shows 60.16.
On the other hand, the phone's argentinian made. The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0.
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Anyway, I think this thread will be of general interest so I'll continue to provide info on the case.
ad astra said:
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
Click to expand...
Click to collapse
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
ad astra said:
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one.
Click to expand...
Click to collapse
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
ad astra said:
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Click to expand...
Click to collapse
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
ad astra said:
the 5.1 rom and his bootloader version shows 60.16.
Click to expand...
Click to collapse
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
JulesJam said:
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
Click to expand...
Click to collapse
But how? His bootloader was locked, and we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work. We even edited the .xml file and tried the nokia flashing tool, which also resulted in a failed attempt.
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
2) adb sideload.
3) vendor flash tool (like Odin, and nokias RDS or something like that).
ad astra said:
The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0. .
Click to expand...
Click to collapse
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
ad astra said:
But how?
Click to expand...
Click to collapse
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
ad astra said:
But how? His bootloader was locked,
Click to expand...
Click to collapse
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
ad astra said:
we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work.
Click to expand...
Click to collapse
You don't do it through recovery - you do it through bootloader mode.
JulesJam said:
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
You don't do it through recovery - you do it through bootloader mode.
Click to expand...
Click to collapse
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Thanks for the info! And also thanks for the tip on the motorola deivce manager upgrade thing. The LG suite does the same thing and so I keep my stock image safely stored.
ad astra said:
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
Click to expand...
Click to collapse
Yes, this works. You don't need an unlocked bootloader to do it, but you do need mfastboot if the image file you have is a single image file. If you have the system already broken down into chunks, you can use regular fastboot.
ad astra said:
3) vendor flash tool (like Odin, and nokias RDS or something like that).
Click to expand...
Click to collapse
The one you want for a Moto X is the Motorola tool - RSDLite. RSDLite has mfastboot as a part of it.
You needed mfastboot to flash a single file system.img. Regular fastboot from the SDK won't work. mfastboot is motorola's version of fastboot.
Regular fastboot can only flash chunks of system. I think they have to be 256MB or less in size.
---------- Post added at 12:44 AM ---------- Previous post was at 12:41 AM ----------
ad astra said:
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Click to expand...
Click to collapse
I was trying to help you, but you didn't post back.
JulesJam said:
I was trying to help you, but you didn't post back.
Click to expand...
Click to collapse
Dont get me wrong. You did help me (thats why i left u a thanks) :good: My friend just went and did his thing on his own. I probably live in a different time zone, and my work doesn't allow me to be online the whole day. It was really late when I posted, I wasn't expecting a reply on the fly so I went to sleep. I continued this thread just because of curiosity.
On a side note, my friend checked his phone and, it seem'd alright, closed box and all. He worked a time at Motorola so he knows what was getting into. It seems the whole mess happened because of a forum post which indicated that he was flashing a soak test rom, when it was actually a final release (or something like that). This last, ended up messing up his system.
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Steve-x said:
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Click to expand...
Click to collapse
Agreed. Very poor judgement on behalf of my friend. Lesson learnt I guess, now he's bootloader is unlocked and he managed to flash 5.1 as previously intended.
It seems that the guy who posted the soak mistakenly posted the wrong file and caused a lot of problems for a lot of people... but, nevertheless u cant trust everything to go right... so that's my friends own fault for not unlocking, backing up and investigating enough.
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Lussardi said:
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Click to expand...
Click to collapse
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
AGISCI said:
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Lussardi said:
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Click to expand...
Click to collapse
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
AGISCI said:
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I do not know ... a customer came in for repair, so do not know the reason why he stayed so.
Related
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
you can always use fastboot to go back to 5.0.1
stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.
EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.
Sweet, successful downgrade!
I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!
Disregard! Got it handled. Thanks guys!
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1
EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??
Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?
if i clicked flast stock and unroot, did that relock the bootloader and re-enable encryption?
im trying to sale the nexus
GreeleyXda said:
if i clicked flast stock and unroot, did that relock the bootloader and re-enable encryption?
im trying to sale the nexus
Click to expand...
Click to collapse
you should check, you have the phone, not me.
im not rly sure how to.
also while trying to prep, i deleted everything from twrp and now i dont have an OS it says.
any clues/help?
GreeleyXda said:
im not rly sure how to.
also while trying to prep, i deleted everything from twrp and now i dont have an OS it says.
any clues/help?
Click to expand...
Click to collapse
if you deleted your os, then you will have to flash the factory img if you want to sell the phone stock.
but you can always check your bootloader if its locked, by just booting to it. and in your security option in the main settings will tell you if you are encrypted or not.
simms22 said:
if you deleted your os, then you will have to flash the factory img if you want to sell the phone stock.
but you can always check your bootloader if its locked, by just booting to it. and in your security option in the main settings will tell you if you are encrypted or not.
Click to expand...
Click to collapse
clicked flash stock and unroot from sofy bricked/bootlooped on the tool kit
it got my phone up.
then i clicked oem unlock.
what else do i need to check?
GreeleyXda said:
clicked flash stock and unroot from sofy bricked/bootlooped on the tool kit
it got my phone up.
then i clicked oem unlock.
what else do i need to check?
Click to expand...
Click to collapse
using a toolkit, im clueless.
Well whatever you do do not re lock it. I do not know what toolkit you're using but he should be able to flash a system image.
if you relock the boot loader it doesn't matter if you were using a tool or not you may have screwed yourself .
Sent from my Benzo'd Google N6 on VZ
simms22 said:
using a toolkit, im clueless.
Click to expand...
Click to collapse
wuggfresg nexus root tool kit
DebianDog said:
Well whatever you do do not re lock it. I do not know what toolkit you're using but he should be able to flash a system image.
if you relock the boot loader it doesn't matter if you were using a tool or not you may have screwed yourself .
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
why did i screw myself?
im on 5.0.0 now btw
Can you load recovery? You are very vague in your descriptions of the status of the phone .
Sent from my Benzo'd Google N6 on VZ
---------- Post added at 06:11 PM ---------- Previous post was at 05:58 PM ----------
If you relocked your boot loader and cannot boot recovery I am not sure I can help you recover your phone
Sent from my Benzo'd Google N6 on VZ
DebianDog said:
Can you load recovery? You are very vague in your descriptions of the status of the phone .
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
no i cant theres a red triangle sign when i try.
but the device is locked, unrooted on stock 5.0.0, and encrypted. everything wiped
dont i need twrp installed to get to recovery?
im confused, did i not re add something when i reinstalled the stock os?
GreeleyXda said:
no i cant theres a red sign on the adroid when i try.
but the device is locked, unrooted on stock 5.0.0, and encrypted. everything wiped
dont i need twrp installed to get to recovery?
Click to expand...
Click to collapse
nope. that one, with the android lating down, is the stock recovery. sounds as its where you should be. did you check if the bootloader is locked?
If you did relock your bootloader and do not have an alternate recovery aka TWRP that you can boot then you have screwed yourself.
However if you can boot to bootloader
fastboot format userdata
fastboot format cache
Get into TWRP you could flash a zip or backup and be back in business
Sent from my Benzo'd Google N6 on VZ
DebianDog said:
If you did relock your bootloader and do not have an alternate recovery aka TWRP that you can boot then you have screwed yourself.
However if you can boot to bootloader
fastboot format userdata
fastboot format cache
Get into TWRP you could flash a zip or backup and be back in business
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
which one is the bootloader again?
i get go AP Flashboot Flash mode. is that it?
it says deviced locked on that screen
simms22 said:
nope. that one, with the android lating down, is the stock recovery. sounds as its where you should be. did you check if the bootloader is locked?
Click to expand...
Click to collapse
i think it is
update, i found out when the red triange is there im suppouse to hold power and click the vol + button.
i got into recovery mode. now what?
GreeleyXda said:
update, i found out when the red triange is there im suppouse to hold power and click the vol + button.
i got into recovery mode. now what?
Click to expand...
Click to collapse
yup, thats stock recovery. if your bootloader is locked, then youre good. well, after you delete whats in your storage
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
@DebianDog thank you for trying to help, even though that wasnt his issue
Toolkit + inexperienced user = expensive paperweight.
Yet we, the "traditionalists" are repeatedly scorned for being negative about toolkits.
Running command lines willy-nilly or clicking buttons on a toolkit. doesn't matter - inexperience is inexperience
Sent from my Benzo'd Google N6 on VZ
simms22 said:
yup, thats stock recovery. if your bootloader is locked, then youre good. well, after you delete whats in your storage
Click to expand...
Click to collapse
sorry haha i never got a handle on all this, im used to locked samsung devices (verizon)
wipe data/factory reset in Cust Recovery should take care of deleting everything right? (although i alrdy had wiped every option in twrp which is why my os was gone)
also on swappa it asks if its carrier unlocked and rooted (has the device been rooted)
its direct from motorolla, so idk if that counts as a yes
and im assuming they mean is the device currently rooted?
DebianDog said:
Running command lines willy-nilly or clicking buttons on a toolkit. doesn't matter - inexperience is inexperience
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
True and I regret leaving the comment I did but it had to be said.
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.
Need help badly:
I Lost OEM unlock option when I installed a custom rom. I have waited for 7 days and the option wouldnt appear in the settings. I believe if I reboot this, Id be stuck in binary blah blah and Id be back in stock rom again and be jailed for 7 days.
Im currently rooted. Ive read an article about DrKetan OEM patch. Can I be able to install that without using TWRP? Like the app Flashify or Flashfire?
Any insights please?
Thanks
I wish to restore my TWRP backup but I cant get to TWRP as I believe id be stuck in " only official binary blah blah"
I first unlocked the boot loader but didn't worked than I was unable to find the one unlock option again in developer mode even after reflashing the firmware.
In the Odin mode it is written oem lock off
Can somebody guide me how to show that option again
sangreal327 said:
Need help badly:
I Lost OEM unlock option when I installed a custom rom. I have waited for 7 days and the option wouldnt appear in the settings. I believe if I reboot this, Id be stuck in binary blah blah and Id be back in stock rom again and be jailed for 7 days.
Im currently rooted. Ive read an article about DrKetan OEM patch. Can I be able to install that without using TWRP? Like the app Flashify or Flashfire?
Any insights please?
Thanks
Click to expand...
Click to collapse
Some roms hide the OEM unlock option to avoid accidentally switching it and then locking you out ie only official binaries. Search in the thread of the rom you are using to see if that is the case.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Malikzeeshanarif said:
I first unlocked the boot loader but didn't worked than I was unable to find the one unlock option again in developer mode even after reflashing the firmware.
In the Odin mode it is written oem lock off
Can somebody guide me how to show that option again
Click to expand...
Click to collapse
Try using this great guide
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
stonedpsycho said:
Some roms hide the OEM unlock option to avoid accidentally switching it and then locking you out ie only official binaries. Search in the thread of the rom you are using to see if that is the case.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Try using this great guide
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
Does installing a new firmware Will replace the one unlock or not
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.