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.
Related
Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
rootSU said:
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
Click to expand...
Click to collapse
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
kenbrownstone said:
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It depends what you're expecting in future. If you want OTA, you'll need everything to be 100% stock and the right version. If you don't care about that, minimum is system.img and boot.img.
i tried to downgrade my bootloader through fastboot from 5.1's bootloader to 5.0.1 and fastboot throws an error from moto saying it cant be downgraded.
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
freebee269 said:
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
Click to expand...
Click to collapse
I had been running Chroma 5.02 with the 5.1 bl and radio. I reverted the radio because of issues with TMo, but the bl seemed fine. FWIW, I made all my changes via fastboot.
kenbrownstone said:
Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It resets on boot. Check it boots before relocking
rootSU said:
It resets on boot. Check it boots before relocking
Click to expand...
Click to collapse
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
naresh2990 said:
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
Click to expand...
Click to collapse
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
naresh2990 said:
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
Click to expand...
Click to collapse
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
pwned3 said:
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Konfuzion said:
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
rootSU said:
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
Click to expand...
Click to collapse
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
the_rooter said:
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
Click to expand...
Click to collapse
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
the_rooter said:
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
Click to expand...
Click to collapse
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said after a reboot it goes unchecked so if i check it and then reboot to recovery wouldnt that uncheck it again?
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.
I unrooted and relocked my nexus 6, but my mobile iron still says it is OS comprismised. I did uninstall supersu, doesn't look to be installed. What else does MDM or mobile iron flag for? I am the admin to our MI box, so I can see what's going on, and can retire/readd at whim. I just don't see what else it's flagging for, it just says OS compromised, like when I was rooted, and unlocked.
vivithemage said:
I unrooted and relocked my nexus 6, but my mobile iron still says it is OS comprismised. I did uninstall supersu, doesn't look to be installed. What else does MDM or mobile iron flag for? I am the admin to our MI box, so I can see what's going on, and can retire/readd at whim. I just don't see what else it's flagging for, it just says OS compromised, like when I was rooted, and unlocked.
Click to expand...
Click to collapse
Not sure but probably same as Google update. Just removing the SU app doesn't remove all the SU system files. Have to reflash back to stock.
It is a stock OS. Do I have to unlock wipe, flash, lock ,wipe?
vivithemage said:
It is a stock OS. Do I have to unlock wipe, flash, lock ,wipe?
Click to expand...
Click to collapse
no. you want to unlock your bootloader, flash a factory image, make sure that it boots fine, only then you want to relock your bootloader.
vivithemage said:
It is a stock OS. Do I have to unlock wipe, flash, lock ,wipe?
Click to expand...
Click to collapse
If you just removed SU app will have to unlock and reflash system to actually remove root. Do not relock till you sure it will boot and reset the unlock switch in developer options.
OK, doing that now. What's the correct way to relock once in the OS unlocked bootloader and fresh install?
I booted into the OS, went back to recovery, ran this: fastboot oem lock
Should be good, will set it up again, hopefully mobile iron thinks I am an compromised OS now.
vivithemage said:
OK, doing that now. What's the correct way to relock once in the OS unlocked bootloader and fresh install?
I booted into the OS, went back to recovery, ran this: fastboot oem lock
Should be good, will set it up again, hopefully mobile iron thinks I am an compromised OS now.
Click to expand...
Click to collapse
fastboot oem lock is the only way to lock the bootloader
ahhh man, after all that, it still says OS compromised. Is there another flag somewhere? It is not rooted, or unlocked!
vivithemage said:
ahhh man, after all that, it still says OS compromised. Is there another flag somewhere? It is not rooted, or unlocked!
Click to expand...
Click to collapse
You did fastboot flash the system.img and boot.img before locking your bootloader, right?
cam30era said:
You did fastboot flash the system.img and boot.img before locking your bootloader, right?
Click to expand...
Click to collapse
yeah, and everything else in the gz file, cache, system data, radio, boot, etc.
I am going to open a ticket with mobile iron, they have a root ident app that they can install, to tell me what is still flagging it.
vivithemage said:
yeah, and everything else in the gz file, cache, system data, radio, boot, etc.
I am going to open a ticket with mobile iron, they have a root ident app that they can install, to tell me what is still flagging it.
Click to expand...
Click to collapse
Let us know what you find out.
https://help.mobileiron.com/articles/MI_Article/Android-Compromised-Rooted-devices
Apparently they have a root checker app. I removed all of my root required applications and I am good. So greenify (flagged), root browser (flagged), total commander (not flagged), betterbattary stats, .
I also uploaded their root status tool if anyone wants to use it:
http://vivithemage.com/extra/RootCode.apk
If anyone else is having problems, but doesn't have support with MI. this should help you discover what's causing it to be listed as comprismised. I am sure some of the savvier folks will use it as a way to stay rooted, but find ways around MI MDM .
vivithemage said:
If anyone else is having problems, but doesn't have support with MI. this should help you discover what's causing it to be listed as comprismised. I am sure some of the savvier folks will use it as a way to stay rooted, but find ways around MI MDM .
Click to expand...
Click to collapse
Any chance you could re-upload the tool? I'm running into the exact same problem but don't have MI support available
Sorry, they asked me to remove it
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.
H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.
-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.
Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.
Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.
Hi guys, so here is the story. My brother bought a Nexus 6, it came with 5.1 and he tried to update it via OTA today, it boot up, reboot and when powering on, it was stuck in a bootloop.
I tried first just clearing cache and data on the stock recovery, but had the same results when trying to boot up. I started to get worry but hey its a Nexus, he couldn't brick it just taking an OTA.
Well, I booted to fastboot which does fine, my computer recognozed it, i tried to faatboot flash a custom recovery but, happens the bootloader is locked, i thought I am just a command away to unlock it, but it fails telling me that the option was not thicked in settings.
I now, have no idea what else to do. Any ideas? Is there anything I can flash on the bootloader if it is not unlocked?
Sent from my C6906 using Tapatalk
Hello,
please try to Flash with this:
[Toolkit] Wug's Nexus Root Toolkit v2.0.5 [Updated 03/27/15]: Nexus 6 Thread
There should be laws against soliciting.
Sent from my Nexus 6 running cyosp using Tapatalk
Trafalgar Square said:
Hello,
please try to Flash with this:
[Toolkit] Wug's Nexus Root Toolkit v2.0.5 [Updated 03/27/15]: Nexus 6 Thread
Click to expand...
Click to collapse
Will do in the AM
istperson said:
There should be laws against soliciting.
Sent from my Nexus 6 running cyosp using Tapatalk
Click to expand...
Click to collapse
Not sure if understand what do you mean
Sent from my C6906 using Tapatalk
istperson said:
There should be laws against soliciting.
Sent from my Nexus 6 running cyosp using Tapatalk
Click to expand...
Click to collapse
shall i ask a lawyer for you?
JakeOcn said:
Not sure if understand what do you mean
Sent from my C6906 using Tapatalk
Click to expand...
Click to collapse
Offering "solutions" that are proved not to work, by promoting methods that are not recommended. These are the homeopathic solutions for the real diseases.
If your phone's bootloader is not unlocked, and the Enable OEM unlocking is not ticked then you can't do anything. And if you can't do anything, you can't do anything with tollkits either, because they are not magic pixies that solve problems, but only frontends for adb and fastboot.
---------- Post added at 08:44 AM ---------- Previous post was at 08:36 AM ----------
Droidphilev said:
shall i ask a lawyer for you?
Click to expand...
Click to collapse
istperson said:
Offering "solutions" that are proved not to work, by promoting methods that are not recommended. These are the homeopathic solutions for the real diseases.
If your phone's bootloader is not unlocked, and the Enable OEM unlocking is not ticked then you can't do anything. And if you can't do anything, you can't do anything with tollkits either, because they are not magic pixies that solve problems, but only frontends for adb and fastboot.
---------- Post added at 08:44 AM ---------- Previous post was at 08:36 AM ----------
Click to expand...
Click to collapse
Thanks for clarifying. So, I guess the phone is basically bricked with no known solutions, correct?
To be clear:
You seem to know your way around fastboot, so the tip to use a toolkit is a bit useless (and not recommended by a large part of xda).
And about your problem: Your brothers N6 is a brick, sorry. With a locked bootloader and no custom recovery there is no way to recover from a bootloop if the "allow OEM unlocking" isn't ticked (found in the developer options in settings).
Since Lollipop it is quite possible to brick your Nexus by just taking an OTA. First thing I always do with my phones, even before Lollipop, is to unlock the bootloader. That way you always have a way back.
I'm afraid, you have to send it for repairs. But they'll replace it, because it's their fault.
But when you get your replacement, you really should start with unlocking the bootloader. That won't affect anything else, but if Google botches another OTA, the phone will be fixable.
Didgeridoohan said:
To be clear:
You seem to know your way around fastboot, so the tip to use a toolkit is a bit useless (and not recommended by a large part of xda).
And about your problem: Your brothers N6 is a brick, sorry. With a locked bootloader and no custom recovery there is no way to recover from a bootloop if the "allow OEM unlocking" isn't ticked (found in the developer options in settings).
Since Lollipop it is quite possible to brick your Nexus by just taking an OTA. First thing I always do with my phones, even before Lollipop, is to unlock the bootloader. That way you always have a way back.
Click to expand...
Click to collapse
istperson said:
I'm afraid, you have to send it for repairs. But they'll replace it, because it's their fault.
But when you get your replacement, you really should start with unlocking the bootloader. That won't affect anything else, but if Google botches another OTA, the phone will be fixable.
Click to expand...
Click to collapse
Thank you both, I will in that case send it back to google and make sure my brother unlocks the bootloader as soon as he gets it.
Sent from my C6906 using Tapatalk