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
I have a pure edition. Im so afraid of voiding warranty then dropping and cracking the seemingly very fragile screen.
Pure Edition counts as a developer device, unlocking doesn't void warranty. Don't count on them fixing it if you brick it while flashing though.
tw1tch175 said:
Pure Edition counts as a developer device, unlocking doesn't void warranty. Don't count on them fixing it if you brick it while flashing though.
Click to expand...
Click to collapse
is there a high chance of bricking it? What about unbricking it?Im sure thats possible
10pmStalker said:
is there a high chance of bricking it? What about unbricking it?Im sure thats possible
Click to expand...
Click to collapse
In my experience, as long as you can get your phone to bootloader/adb/recovery mode, there's always a way of unbricking it, this is of course considering you are soft and not hard bricked . If you're messing around with the correct files for your device, the chances of bricking your phone are minimal.
10pmStalker said:
is there a high chance of bricking it? What about unbricking it?Im sure thats possible
Click to expand...
Click to collapse
Considering that there really isn't anything for us to flash, there's pretty much zero chance of it bricking. Unlocking the bootloader alone has zero risk, and flashing TWRP also pretty much has zero risk.
Sent from my iPhone 6 using Tapatalk
Cool, thanks guys. Off to find tutorials
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Welcome to the club!
necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
wtherrell said:
Why in the world would you relock the bootloader? Against commonsense it would seem. Also, there are threads on here dealing with the update and warning against relocking the boot loader. Those threads also describe efforts to recover from the situation.
Click to expand...
Click to collapse
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
necroside007 said:
Hi!
Today I updated my Nexus 6 to 5.1 and something is went wrong...
When i try to boot my device into android, i Can't because its shows a dead android with a red triangle
(this is the screen where i can go into the recovery menu by pressing power on+ vol up)
i tried to flash the rom again, but the bootloader is locked because i relocked it after the 5.1 rom flash..
and i cant unlock it again because i cant boot into android to check the OEM unlock box.
i also tried wipe data, factory reset option in the recovery menu... thanks a lot for any suggestions
(sorry for my english)
Click to expand...
Click to collapse
freeman_g said:
Welcome to the club!
Click to expand...
Click to collapse
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
If you want to update to the newest OTA you dont need to lock the bootloader back up. The bootloader can remained unlocked when doing this. Its been posted all over XDA about not having to do this. The only time you may want to relock the bootloader is when selling it to someone or trading it in. Thats it.
AndrewZorn said:
I haven't seen anyone warning against relocking the bootloader - in fact, I see many instruction sets where relocking the bootloader is the final step, before the first reboot. Most are for returning to stock. Go ahead and use your hindsight though, you sound so smart.
And yeah, there are plenty of efforts to recover from the situation, but I'm yet to see anyone do so successfully.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3053497.
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
wtherrell said:
http://forum.xda-developers.com/showthread.php?t=3053497.
Click to expand...
Click to collapse
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
necroside007 said:
Well...I'm not browsing the XDA every day, i only come here for solutions for my problems....
Click to expand...
Click to collapse
well not to come off rude but number one rule for xda before u post is search, and as you can tell there are multiple threads on this exact same topic.
---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------
AndrewZorn said:
Yeah, posted this morning. What a warning to everyone who did this before.
And saying not to do something that plenty of people want to do (like, returning to stock) isn't very significant.
Click to expand...
Click to collapse
returning to stock and relocking the bootloader dont go together. You can return to stock and not lock the bootloader. Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
the_rooter said:
Locking the bootloader has nothing to do with returning a device back to stock. It returns the device back to factory state if u lock it back up. Locking the device back up only should be used for selling the device, or returning the device for repairs. not for taking a ota.
Click to expand...
Click to collapse
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
AndrewZorn said:
Unless I want a secure device.
Unless I worry about warranty/resale in case my device is no longer operable (ie, broken screen, port, or buttons).
Unless I want my device to be stock - actually stock - as sold - which is LOCKED. You're telling me and others there's no downside to an unlocked bootloader. Well, that's wrong, and some people want a locked bootloader.
Click to expand...
Click to collapse
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
rootSU said:
I posted the warning because people are not being careful. They are locking the bootloader without even checking it works. I've edited the post to say that. But if you're the sort of person that will be flashiogn a lot, a locked bootloader is not a good thing to have now because if you break recovery and cannot boot your device, you are at present - completely screwed. If you want to be stock, that shouldn't be an issue. Just be careful is all we're saying. ...and I cannot help it if my warning comes after some people have made this mistake. If no one made the mistake, I wouldn't have needed to post a warning. Can of peanuts "May contain nuts"... You know, because you know someone somewhere who was allergic to nuts, ate the nuts.
Click to expand...
Click to collapse
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
the_rooter said:
There is no downside to a unlocked bootloader. If i remember correctly a locked bootloader is only for oem to protect for warranty issues nothing to do with security that your describing. A locked bootloader or unlocked bootloader tells the oem that this device was unlocked or locked and will tell the consumer (us) that the warranty was void. Number one rule when taking a device back to OEM for repair is return to stock and lock device like I stated above. Security issues has nothing to do with the bootloader. From my understanding its just for the OEM warranty purposes Only!
Edit: what u described above is the same thing I described. Only need to lock device back up for warranty purposes or reselling. Thats it.
Click to expand...
Click to collapse
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal. I don't care if there's something about the bootloader unlocked that you find valuable. I got tired of the tinkering and decided I just wanted my Nexus 6 to be back the way it was - completely.
AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
Click to expand...
Click to collapse
If guides don't say that at the moment, they definitely should now. I'll look at ours here and ask the OP's to update.
AndrewZorn said:
I have nothing against your warning - I'm glad it's there. I was replying to the other guy, saying your the existence of your warning doesn't make everyone with this problem an idiot.
Locking the bootloader without even checking it works - again - I don't often see the "reboot to make sure it works!" step before the final fastboot oem lock. Maybe I've only been reading the lousy guides.
I thought that an unlocked bootloader allowed someone without 'normal' access to the files on your phone. That's why the bootloader lock/unlock wipes the device.
You're still completely missing my point with the warranty thing. Suppose my phone's unlocked and my screen breaks. Or my USB port stops working. That big unlocked logo under the Google is going to make getting a replacement really difficult.
By saying there's NO downside to unlocking the bootloader for daily use is absurd. I wanted to go back to as-shipped state for daily use, and locked bootloader is part of that. That's a reasonable goal.
Click to expand...
Click to collapse
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
the_rooter said:
Root access is for the special files. and also i had the same issues u mentioned above and i always found a way to return a device to stock.
1) broken screen- repaired myself
2) broken usb port - repaired myself
I only take in for warranties if it has to do with something that I cant fix myself. This is a risk that all users take in this hobby.
Click to expand...
Click to collapse
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
AndrewZorn said:
Alright, so how do I return mine to stock?
Your self-repair solutions are laughable. You're completely missing the point. I'm done arguing this.
Click to expand...
Click to collapse
its not laughable. unless u buy an extended warranty the warranty is up after a year so you would have to figure the work yourself. If you are in the boat where u locked it back up and took the ota and bootlooping or whatever. your stuck till there is a solution. if u want to return to stock . Just return to stock but dont lock the bootloader back up, and flash. its that simple.
Edit: we are not arguing. Its just i have my way on repairs and you have yours. its a debate i guess
Edit: this issue has been brought up and is being researched. i was talking about the returning to stock for repairs dont try and put words in my mouth saying i know a fix.
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
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.