Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop
jiv101 said:
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop
Click to expand...
Click to collapse
There are two separete issues. One is what you're describing, and one is the device just completely dying - "you can't even get to fastboot". The first one has thread here, as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no cause :/
JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app
Tasssadar said:
as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no no cause :/
Click to expand...
Click to collapse
Are they sure of what bootloader versions they had?
I know this is a Nexus device but it has a Motorola bootloader. It is safest not to downgrade the bootloader OR the partition table from my experience with the Moto X. I know there were some exceptions and that is how jcase was able to get root on at least one bootloader version, but the general rule was don't try to downgrade the bootloader or the partition table to stay out of trouble.
I was thinking of making a post on General with this advice in it for people to help them stay out of trouble:
1) know your bootloader and partition table versions before you flash anything and if you aren't sure what will happen, do not attempt to downgrade either the bootloader or the partition table; and
2) make sure OEM unlock and USB debugging are enabled before you flash anything.
I understand that the advice above may be overkill for those who know what they are doing, but clearly people who don't know what they are doing are bricking their devices. I feel bad for them and don't want to see more people in that situation.
I was bricked by CM. Last nexus I had with cm was galaxy nexus so I don't know how cm is done on nexus 5 but why do they reflash bootloader and radios on each update. It wasn't that way before. Thats what bricked my device. I just got confirmation that I'm getting my replacement device.
akellar said:
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Still a Motorola bootloader
rootSU said:
Still a Motorola bootloader
Click to expand...
Click to collapse
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Fair enough
Related
I am an Android Developer, but so far I've avoided rooting my phone or trying custom kernels, but lately I get the feeling I could learn so much more by really getting behind the curtain so to speak. I keep reading that if you root the phone you may void your warranty and no longer get over the air updates.
I'm on AT&T an paid full price for my Nexus One. I also got the phone engraved so I'm wondering what value if any the warranty actually has. Is it worth mucking around with custom kernels on the Nexus one, or should I get a cheaper dev phone like the G1 ?
Looking forward to hearing advice from other developers and what you've learned versus the risks involved.
Oh, Do you still get OTA updates as well?
I'm interested in hearing from people who decided the warranty was or was not work the risk. Looks pretty easy from what I can see.
Thanks all.
Just root it without unlocking the bootloader and you're good to go
J.L.C. said:
Just root it without unlocking the bootloader and you're good to go
Click to expand...
Click to collapse
^this
root is fun and even better you can keep your warranty
Does using the technique of not unlocking the bootloader also mean you can run custom ROMs and/or recoveries? Or just gain root access to the stock ROM?
flybyme said:
^this
root is fun and even better you can keep your warranty
Click to expand...
Click to collapse
You CAN root your Nexus One without losing your warrenty.
I had my bootloader Unlocked, then i got a issue with mounting SD cards.
I sent the phone to HTC Repair center and just got it back today with the issues gone and Bootloader locked
Unlocking your Nexus One bootloader does void your warrenty with HTC, but if you experience hardware issues, they dont care if you unlocked your bootloader !!
By unlocking your Bootloader you can put whatever ROM on your phone you like, doesn't have to be stock
About the OTA's.
Yes you will get them if you run Stock ROM's.
You will not be able to install them however since you are not using a stock recovery image.
Wow, didn't know they didn't care about unlocked bootloader as long as your problem is in hardware. My GPS doesn't work at all and I'd like to send in my phone for repairs but the bootloader is unlocked.How long did it take for you to get your phone back?
Sent from my Nexus One using XDA App
WebghostDK said:
You CAN root your Nexus One without losing your warrenty.
I had my bootloader Unlocked, then i got a issue with mounting SD cards.
I sent the phone to HTC Repair center and just got it back today with the issues gone and Bootloader locked
Unlocking your Nexus One bootloader does void your warrenty with HTC, but if you experience hardware issues, they dont care if you unlocked your bootloader !!
By unlocking your Bootloader you can put whatever ROM on your phone you like, doesn't have to be stock
About the OTA's.
Yes you will get them if you run Stock ROM's.
You will not be able to install them however since you are not using a stock recovery image.
Click to expand...
Click to collapse
See this: http://forum.xda-developers.com/showthread.php?t=718141
they arent always so nice haha
cmcm said:
Wow, didn't know they didn't care about unlocked bootloader as long as your problem is in hardware. My GPS doesn't work at all and I'd like to send in my phone for repairs but the bootloader is unlocked.How long did it take for you to get your phone back?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I sent my phone from Denmark to UK, it took 1½ week quite fast
Can you point me to a link with instructions on how to do this?
I've found a few videos and articles that say this can be done, but reading to the end they all say seem to be closed or say not to do it.
Is it still possible to root the phone without unlocking the bootloader? I've searched google, but keep coming up with dead ends.
http://forum.xda-developers.com/showthread.php?t=710842
Title says it all. Will I get the new radio/bootloader when CM12 gets updated? The update includes the ability to use the 700Mhz TMobile freq as well as VoLTE.
They normally do, yes.
Custom ROMs do not provide bootloaders
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
I didn't think so. I went ahead and restored back to stock and updated to 5.1 from the google factory images. I'll probably go back to CM when they update to 5.1.
Thanks!
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
Cm does
Sent from my Nexus 6 using XDA Free mobile app
rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
CM does. What they're currently doing is they are checking your bootloader version, and the ZIP refuses to flash if you're not on 5.1 bootloader (because downgrading the bootloader might be reason of all these bricks). If you are, then the ZIP flashes and writes bootloader (the version you already have) and radio again.
http://review.cyanogenmod.org/#/c/91181/
Tasssadar said:
CM does. What they're currently doing is they are checking your bootloader version, and the ZIP refuses to flash if you're not on 5.1 bootloader (because downgrading the bootloader might be reason of all these bricks). If you are, then the ZIP flashes and writes bootloader (the version you already have) and radio again.
http://review.cyanogenmod.org/#/c/91181/
Click to expand...
Click to collapse
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
The issue with cm specifically is that the zip attempted to downgrade the bootloader which isn't possible. Bad things followed.
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
The issue with cm specifically is that the zip attempted to downgrade the bootloader which isn't possible. Bad things followed.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah OK. I don't tend to read threads that have "cm" in the title so I've missed that.
rootSU said:
Ah OK. I don't tend to read threads that have "cm" in the title so I've missed that.
Click to expand...
Click to collapse
(looks at this thread title) Hmm...
Sent from my Nexus 6 using XDA Free mobile app
akellar said:
(looks at this thread title) Hmm...
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. "Tend" . This one piqued my interest as it was asking about the bootloaders though.
rootSU said:
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
Click to expand...
Click to collapse
No, we haven't locked our bootloaders. They have moved all nightlies except one left there. I think that explains sth. Thats how it happens to most of us i think. I never locked my BL, and that happens too. Maybe too soon to judge . Now all i got is a hard bricked phone.
randy6644 said:
No, we haven't locked our bootloaders. They have moved all nightlies except one left there. I think that explains sth. Thats how it happens to most of us i think. I never locked my BL, and that happens too. Maybe too soon to judge . Now all i got is a hard bricked phone.
Click to expand...
Click to collapse
To be hoinest I haven't been following CM specific bricks. That may indeed be what is happening to CM users. I was talking seemingly out of context about all the other threads where peiople had upgraded using fastboot then relocked their BL's
rootSU said:
To be hoinest I haven't been following CM specific bricks. That may indeed be what is happening to CM users. I was talking seemingly out of context about all the other threads where peiople had upgraded using fastboot then relocked their BL's
Click to expand...
Click to collapse
relocking bootloader leads to a bootloop , and it's nothing like a real hard brick like mine. So sad~
rootSU said:
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
Click to expand...
Click to collapse
but they will upgrade the bootloader to 5.1, which means those running 5.0.2 will upgrade.
Most bricks are happening because CM includes the bootloader and you cannot downgrade bootlodaers, if you tried in fastboot it will stop you from doing this. CM uses an old way of accomplishing this which force downgrades the bootloader and messes up the partitioning, resulting in a brick.
I have seen 3 or 4 cases in person from this, and those users never relocked their boot loader like you described.
Circaflex said:
but they will upgrade the bootloader to 5.1, which means those running 5.0.2 will upgrade.
Click to expand...
Click to collapse
Great. Got it. At some point in the future, cm "will" upgrade the bootloader but right now they will refuse to flash.
I'm safe. Haven't used cm since cm6.
I looked on Cyanogenmod's website below:
https://download.cyanogenmod.org/?device=shamu
and it just has 1 ROM for Nexus 6. I have Nexus 6 for Sprint. Is there only 1 version of the ROM that works for all carriers ?
My old Galaxy S4 has many different builds for Sprint, ATT, Verizon, etc.... wasn't sure if Nexus has the same set up.
Yes, applies to all N6 variants.
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
simms22 said:
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
Click to expand...
Click to collapse
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
mikeprius said:
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
Click to expand...
Click to collapse
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
simms22 said:
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
Click to expand...
Click to collapse
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
mikeprius said:
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
Click to expand...
Click to collapse
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
simms22 said:
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
Click to expand...
Click to collapse
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
mikeprius said:
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
Click to expand...
Click to collapse
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
simms22 said:
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
Click to expand...
Click to collapse
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
mikeprius said:
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
Click to expand...
Click to collapse
you cant, thats why i said that you should keep it unlocked.
simms22 said:
you cant, thats why i said that you should keep it unlocked.
Click to expand...
Click to collapse
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
mikeprius said:
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
Click to expand...
Click to collapse
Security.
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
scryan said:
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
Click to expand...
Click to collapse
It does nothing to secure data from remote access, but it will protect data (if set with a password) from physical access, providing they do not know the password. The bootloader being unlocked, with no password on encryption would allow them to flash a custom recovery and pull the data off. This will be decrypted on the fly. So it works in conjunction with Encryption. To secure data from physical access, you need both.
IF your bootloader is unlocked and you have no password, you may aswell not be encrypted
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
Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....
madkapitolist said:
Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....
Click to expand...
Click to collapse
Sorry, there is nothing you can do to fix a hard brick.
Sent from my XT1095 using Tapatalk
madkapitolist said:
Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....
Click to expand...
Click to collapse
Was your bootloader unlocked? Can you boot to the bootloader?
rsa 329 said:
Was your bootloader unlocked? Can you boot to the bootloader?
Click to expand...
Click to collapse
Yes bootloader was unlocked, seems like the consensus is that its dead until moto releases the blankflash files for this phone. Oh well live and learn. I cannot boot into fastboot and adb does not detect the device.
madkapitolist said:
Yes bootloader was unlocked, seems like the consensus is that its dead until moto releases the blankflash files for this phone. Oh well live and learn. I cannot boot into fastboot and adb does not detect the device.
Click to expand...
Click to collapse
I also have a pure edition XT1095 with an unlocked bootloader and reflashed to stock to take the Marshmallow OTA and bricked my phone. I used the Multi Tool V4.1 which flashed my phone from 5.1 to 4.2.2. It booted fine and started the OTA of either 5.0 or 5.1 which was when everything went to hell. I can't get to recovery mode and I'm pretty pissed. I've ordered a Nexus 6P and have put Motorola on my short list of companies I will no longer do business with as they have the drivers and utilities to fix the phone but do not release them. Yeah, I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that. The point is that it is a non-subsidized pure edition phone and an OTA should not be able to hard brick the phone.
RobbieDowie said:
I also have a pure edition XT1095 with an unlocked bootloader and reflashed to stock to take the Marshmallow OTA and bricked my phone. I used the Multi Tool V4.1 which flashed my phone from 5.1 to 4.2.2. It booted fine and started the OTA of either 5.0 or 5.1 which was when everything went to hell. I can't get to recovery mode and I'm pretty pissed. I've ordered a Nexus 6P and have put Motorola on my short list of companies I will no longer do business with as they have the drivers and utilities to fix the phone but do not release them. Yeah, I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that. The point is that it is a non-subsidized pure edition phone and an OTA should not be able to hard brick the phone.
Click to expand...
Click to collapse
The xt1095 has a warranty, you can send it in for repair. As far as as downgrading, in the upgrade descriptions it clearly states you cannot downgrade to an earlier version. You ignored that message or didn't read it and flashed 4.4.4. That isn't motorola's fault. However the pure xt1095 does not lose it's warranty when you unlock the bootloader, so they will fix it if you contact them and send it in. They just don't give us the tools to fix it ourselves, but that does not mean you have no options.
Sent from my XT1095 using Tapatalk
AGISCI said:
The xt1095 has a warranty, you can send it in for repair. As far as as downgrading, in the upgrade descriptions it clearly states you cannot downgrade to an earlier version. You ignored that message or didn't read it and flashed 4.4.4. That isn't motorola's fault. However the pure xt1095 does not lose it's warranty when you unlock the bootloader, so they will fix it if you contact them and send it in. They just don't give us the tools to fix it ourselves, but that does not mean you have no options.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Seriously? First off, the phone is out of warranty. Secondly, I don't know what upgrade descriptions you're talking about. I didn't ignore anything. I used a tool I got from these forums that had no warning. This is an honest mistake I'll guarantee others will make and to suggest they are stupid is just rude. After it happened I guessed it was due to downgrading to 4.4.4 but by then it was too late. For the phone to be so fragile that you can brick it this way is ridiculous and unacceptable that there is a tool Motorola has that would fix it but they do not make available.
Thanks for the helpful feedback. I was trying to share but now see I was wasting my time.
You might want to join the conversation going on at reddit over here I think you can go back to 5.1 by flashing the whole 5.1 image via the bootloader (including erasing userdate and cache) - I say so because that is what I did but some people say it will not work and to be honest now I'm losing confidence in my memory.... Hope we could get more insight, or at least get the official 6.0 bootloader image from moto soon.
RobbieDowie said:
Seriously? First off, the phone is out of warranty. Secondly, I don't know what upgrade descriptions you're talking about. I didn't ignore anything. I used a tool I got from these forums that had no warning. This is an honest mistake I'll guarantee others will make and to suggest they are stupid is just rude. After it happened I guessed it was due to downgrading to 4.4.4 but by then it was too late. For the phone to be so fragile that you can brick it this way is ridiculous and unacceptable that there is a tool Motorola has that would fix it but they do not make available.
Thanks for the helpful feedback. I was trying to share but now see I was wasting my time.
Click to expand...
Click to collapse
Well....apparently you haven't read much more in this forum, this downgrading brick is common and its often asked by the other. You cant downgrade from lollipop to kitkat. So, if you had read more deeper in this forum, you could prevent this hard brick. And many member forget that this is not nexus device, and yes flashing or upgrading will have risk of hard brick.
Sent from my XT1095 using Tapatalk
bimasakti85 said:
Well....apparently you haven't read much more in this forum, this downgrading brick is common and its often asked by the other. You cant downgrade from lollipop to kitkat. So, if you had read more deeper in this forum, you could prevent this hard brick. And many member forget that this is not nexus device, and yes flashing or upgrading will have risk of hard brick.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I actually knew downgrading was a bad idea and didn't intend on doing it. I used the MOTO_X_2014_PURE_MULTI_TOOLV4.1 which I had used in the past but didn't remember it was going to flash back to 4.2.2. The instructions on the page just say FLASH BACK TO TOTAL STOCK UNRROOTED ROM AND RECOVER-FULL-WIPE. It doesn't say anything about going to 4.2.2. When it said it was downgrading when I ran it I thought "oh, oh" but it was too late. I was trying to provide information in this thread because I hoped it would be helpful, e.g. DON'T USE THE MULTI_TOOLV4.1!. I specifically said "I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that" and what do I get? "...You ignored that message or didn't read it..." I'm already pretty grumpy about my mistake and bricking my phone and to get this kind of lashing isn't appreciated.