yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
I think people are bricking b/c they are attempting to downgrade the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done in the past, but those are few and far between.

The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.

Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.

So based on what has helped avoid bricks on the Moto X:

1) ensure your bootloader is unlocked before you flash anything to your phone;

2) do not attempt to downgrade the bootloader or partition table*;

3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table*;

4) make sure OEM unlock and USB debugging are enabled each time you flash;

5) never take an OTA unless you have reverted back to stock completely;

6) never upgrade the bootloader w/o also upgrading the partition table* and vice-versa; and

7) use mfastboot for flashing**.

* there is apparently no partition table on a Nexus

** this may or may not be necessary on the Nexus 6

Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.

As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.

---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------

Did you flash the 5.1 partition table when you flashed the 5.1 bootloader? I would never have a mismatch of versions b/t the bootloader and the partition table.

Once you upgraded the bootloader to 5.1, do you know if any of the subsequent flashes you did included earlier versions of the bootloader or the partition table?
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
I personally.

I'm not on 5.1 yet so I cant say if the "Enable OEM lock" is controlled by the bootloader at boot or the Kernel / OS..
[Nexus 6 Q&A, Help & Troubleshooting] pallefar:
Better be safe then sorry

Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above
[Nexus 6 Q&A, Help & Troubleshooting] cmh714:
i believe it would be controlled by the kernel/OS...and thats how it gets disabled upon boot of 5.1
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
I think I would add to that not to do anything to cause a version mismatch b/t the bootloader and the partition table. And since you shouldn't be downgrading those, what that means is never upgrade the bootloader w/o also upgrading the partition table and vice-versa.

Again, maybe you can get away with upgrading the bootloader w/o upgrading the partition table but I can't think of any reason not to have those both be on the same version.

One more thing - use mfastboot not fastboot to flash. mfastboot may only be needed for the larger files like system.img but I just use mfastboot all of the time and then I don't have to worry about it.
[Nexus 6 Q&A, Help & Troubleshooting] pallefar:
benefit of mfastboot

What is the benefit of mfastboot compared to normal fastboot flashing? just want to make sure everyhitng is covered

thanks in advance
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
http://mark.cdmaforums.com/MotoX-mFastboot.htm
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
The issue with bricking is that after updating to 5.1 people flashed CM which for some reason includes a bootloader. (no rom should include a BL and radio) When they flashed CM it tried to load an older bootloader which caused bricks. This will be seen by any roms that pretty much is just a renamed CM rom. My advise would be to know what your flashing by always inspecting the zip file before you flash it.
[Nexus 6 Q&A, Help & Troubleshooting] kenbrownstone:
Is the nexus locking its bootloader itself now...I unlocked mine and never have knowing locked it back....So on every flash or after every reboot always turn OEM unlock on?
[Nexus 6 Q&A, Help & Troubleshooting] pallefar:
safe side

So basicly to be on the safe side, stay away or evestigate any Rom which is using the CM 12 source.

I guess AOSP is a safer bet at the moment? like Chroma rom
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
Pretty much. Many claim to be based off of AOSP but most are just using CM sources. I know Slim and DU are based off of AOSP. DU uses the theme engine from CM but thats about it. Slim doesnt use anything from CM last I knew. Many are moving away from using anything CM related so there may be more.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Yep. I think [MENTION=1978554]zephiK[/MENTION] chroma is aosp no-cm.
[Nexus 6 Q&A, Help & Troubleshooting] pallefar:
awesome thanks guys, I think this thread will guide people to not brick thier phones
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
No it doesn't relock itself but lots of people who are on these forums don't really understand what they are doing/flashing and so to be extra safe, I put that in there for people always to double check that OEM unlock is enabled.

People may think they have unlocked when they haven't or may not realize they relocked. I know that seems hard to do but I have never seen so many bricked nexi in my life before.

Just trying to help the less experienced from bricking. If you know what you are doing you don't need to take advice from me.

---------- Post added at 10:37 PM ---------- Previous post was at 10:32 PM ----------

Yep, that will do it - downgrading the bootloader is a no-no on a motorola phone except in rare cases when it was possible.

Always!
[Nexus 6 Q&A, Help & Troubleshooting] jackpollard:
Great write up! Saved my a$$ for sure. I updated my bootloader and radio the day it was available and I'm running a 5.0.1 CM12 based ROM. Here's where sometimes you get lucky, I was on v8.7 of this ROM, after I did the 5.1 bootloader and radio flash, an update came out to 8.8, I'm usually flash happy, but I figured why bother if I can wait for the 5.1 integration! I did unzip the update and no bootloader.img to be found, so I suppose the dev was wise enough not to put it in, but still.

I was curious about why most are moving away from CM? Because of these types of oversights? Their"interesting" business model?
[Nexus 6 Q&A, Help & Troubleshooting] randy6644:
Does nexus have a partition table to flash? I've never heard of that from a nexus forum. I just flashed the 5.1 BL and went back to 5.0 stock rom ,then flashed euphoria. I believe that you flash via Fastboot if your bootloade is mismatched, that you can't acutally flash it. Not unless you use dd command. I'm not sure about this, though. I'm no way a dev or someone with knowledge in this field. But for nexus devices i owned, i never saw any nexus could be bricked this easy. Yes, they're made by motorola, but it's still a nexus . LG makes nexus 4 and 5, doesn't mean LG locked their bootloader as well. I don't think it's a fault of Motorola or has anything to do with its manufacturer. It's a nexus.
[Nexus 6 Q&A, Help & Troubleshooting] Sentinel196:
Here's the updater script from the 11/03/15 CM12 ROM which is bricking phones already updated to 5.1.

As you can see, it's brute force flashing the bootloader and radio, with absolutely no checks. CM have obviously recognised the issue and removed the ROM from their site entirely while they implement the necessary changes.

It should also be noted that user compiled CM ROMs do not contain the bootloader and radio, so they will soft brick at worst.

By comparison, Euroskank's CM compiled ROM checks the bootloader for compatibility before flashing the system parittion to avoid soft bricks, but does not contain a bootloader.

Here's their updater script. As you can see, it checks for a compatible bootloader before flashing anything (the way it should be done).

CM have done the right thing by removing the ROM entirely for the time being.

EDIT:

CM team have removed the brute force flash from their code.

Discussion here:

http://review.cyanogenmod.org/#/c/91181/
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
OK, if there is no partition table in a Nexus then there is no issue with a BL PT version mismatch. I haven't upgraded to 5.1 yet so I haven't looked at the files I need to flash.

Maybe you don't need mfastboot either, but mfastboot does everything fastboot does but doesn't have the smaller file size limitation that fastboot has so that is why I use it.

That was true on RSD Lite on the Moto X, but you could use fastboot or mfastboot to try to downgrade the bootloader. That is how Jcase got root on the Moto X at one point (Slap My Moto)- by downgrading the bootloader. But that is the only example I am aware of that you can downgrade a Motorola BL safely, and it was only after an experienced dev was willing to test it that people felt comfortable doing it.

However, using fastboot instead of RSD Lite was also how a lot of people bricked their Moto X's by attempting to downgrade the bootloader. All of these bricked Nexi are reminding me of all of the bricked Moto X's and it was mostly due to people flashing lower version bootloaders.
[Nexus 6 Q&A, Help & Troubleshooting] Konfuzion:
Yeah every reboot the OEM Unlock gets switched off.
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
I am not a dev either, but I do have experience with Motorola devices and have seen/helped a lot of people avoid bricking their Motorola devices before. Rule #1 with Motorola devices is DO NOT DOWNGRADE THE BOOTLOADER. Seeing all these bricked Nexi made me think that is what is going on here maybe.

I don't see the harm in pointing out to people not to do it unless they know what they are doing.

But why so many bricked Nexi? All I can think of is bootloader downgrades. As long as you can get into bootloader mode, have an unlocked bootloader and have the factory images, you shouldn't be able to brick a Nexus.

---------- Post added at 03:55 AM ---------- Previous post was at 03:54 AM ----------

But you stay unlocked don't you unless you relock right?
[Nexus 6 Q&A, Help & Troubleshooting] Konfuzion:
Correct. But having OEM Unlock unchecked leads to some potentially scary accidental bricks in my opinion.
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
OK, but you should be able to flash a lower version radio w/o bricking. Your phone may not work as a phone if you do it (depends on the version) but if you didn't try to flash a lower version bootloader, you should still be able to get into bootloader mode and flash the higher version radio if your bootloader is unlocked.
[Nexus 6 Q&A, Help & Troubleshooting] Sentinel196:
The reason thre are so many bricked nexus 6 devices is because CM roms (and I presume others cooking CM's zip) brute force flash the 5.01 bootloader, and if the user has already upgraded to 5.1 bootloader, this bricks their phone.

Basically it comes down to a perfect storm of ingredients:

1. Nexus 6 bootloader not being downgradable

2. CyanogenMod's nightlies brute force flashing bootloader and radio without checking compatibility (It's now confirmed this will be fixed in future nightlies).

3. Users flashing zips without checking their contents.
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
I agree, there are threads on here where people "accidentally" relocked their BL. Clearly people who don't understand what they are doing are flashing so best to just warn everyone to check that OEM unlock is enabled before they flash anything. More experienced people can do what they want but for those who are flashing w/o understanding what they are doing, they need to check each time IMO.

---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------

Yeah, that is what I suspected was going on since afterall, this is a Motorola phone.

It may be a Nexus, but it is still a Motorola phone. And you should not attempt to downgrade a Motorola bootloader.

I really don't think the radios are the problem. It's the bootloader that is the problem.
[Nexus 6 Q&A, Help & Troubleshooting] zelendel:
Alot of things like this yes. They have a habit of merging untested code which leads to things just like this.

Also the fact that they want to start removing Google from Android which will cause issues with all the other roms that will not.
[Nexus 6 Q&A, Help & Troubleshooting] Sentinel196:
Correct. I was just pointing out that CM was brute force flashing both.
[Nexus 6 Q&A, Help & Troubleshooting] JulesJam:
OK well someone needs to post on General a Warning Not to Attempt to Downgrade the Bootloader and in the post explain what is going on with the CM-based ROMs. I think that would help a lot of people. I nominate you, lol!
[Nexus 6 Q&A, Help & Troubleshooting] randy6644:
I do think it somehow has sth to do with the 5.1 bootloader that might have some sort of security function. I'm not so sure .
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
Most users bricked their phone because they didn`t enable/check the boot unlock feature in developer options so they couldn`t flash a stock firmware in fastboot after wiping their current OS. Don`t think downloading the bootloader causes on the N6 casuses issues, its still possible to downgrade afaik.
[Nexus 6 Q&A, Help & Troubleshooting] ChristianJay:
Great post and apparently much needed.

"Cyanogen - Building a brand new mobile operating system, one brick at a time."
[Nexus 6 Q&A, Help & Troubleshooting] randy6644:
I'm not talking about the bootloop, thats soft bricked. Imo I don't think soft brick is a problem. What i was talking about is the hard brick. Then we didn't get any Fastboot or recovery , All we can see is qshusb-bulk when the device is connected to a PC. And yet, there's no fix. And thats what downgrading the bootloader causes, And we didn't even know CM 12 contains BL and Modem until we hard bricked our devices.

---------- Post added at 11:32 AM ---------- Previous post was at 11:29 AM ----------

Your one brick at a time sarcasm makes me laugh even though my phone is screwed, LMAO!
[Nexus 6 Q&A, Help & Troubleshooting] nEUTRon666:
One Question, because i don't understand it. If i have checked the oem unlock flag in developer settings and this flag does not survive a reboot, how can this flag be used at all? If i boot into fastboot mode that's a "reboot" or? Or does it reset only when doing a complete reboot, ie. not going to recovery or fastboot mode ?!

Oh, and second question, if you have a unlocked bootloader (because you never relocked it again) you can still brick the device with a possibly downgraded bootloader? I mean, if i'm unlocked i could also flash the 5.1 BL again, or not ?!
[Nexus 6 Q&A, Help & Troubleshooting] Konfuzion:
Booting into bootloader or recovery isn't an issue, the flag gets reset when the Rom in loaded.

Afaik you cannot downgrade bootloaders (don't quote me on that) and that is where people were running into issues.
[Nexus 6 Q&A, Help & Troubleshooting] ChristianJay:
What can you do but laugh, right. :)
[Xperia Z3 Q&A, Help & Troubleshooting] zombiej79:
Any way to keep the battery not charging dialog box? When on mhl it pops up and is annoying
[T-Mobile LG G3] rob_z11:
I am using ATT network, and was wondering if I can use unlock T-Mobile LG G3 for wife who left her phone on the hood of the car, and it is gone.
[T-Mobile LG G3] xdiimez:
Any unlocked sim phone will work for any other Sim carrier so yes. Companies unlock phones so that should not be an issue only thing usually unlocked phones will not get LTE on another carrier
[T-Mobile LG G3] Sher The Love:
Just got a T-Mobile G3 yesterday and using it on AT&T. No issues. LTE works. Just make sure you put in the right APN

Edit: I don't know how the wrong quote got in there....
[T-Mobile LG G3] cesarlulito:
Yes, just make sure after you activate the simcard you head over to Settings\ Tethering & networks\Mobile networks\Access point names

and use the correct settings for your network.
[T-Mobile LG G3] urtruelove78:
I'm using t-mobile version on att and lte works. make sure to enable proper apn and you are golden.
[T-Mobile LG G3] shaxs:
Does the Tmobile version have wireless QI charging available?
[T-Mobile LG G3] HinotoriBR:
As long as you use a QI compatible back cover or a QI compatible Circle Case cover, yes, it does not come with the QI compatible back cover (U.S. carriers crap, unfortunately). You can use any backcover that is compatible with the 855 Model (International LG G3) and that has QI coil and it works fine (I'm using the original LG Circle Case like this one and it works just fine: http://www.expansys.com/lg-quickcircle-cover-for-lg-g3-titan-black-262284/ )
[T-Mobile LG G3] bigdaddyrobb:
What APN setting do you use? I just unlocked a G3 today and on ATT 4g I am getting less than 1 Mbps, on my 55 I am getting 14.

This is what I have.

Name	ATT Phone

APN	phone

Proxy	Not set

Port	Not set

Username Not set

Password Not set

Server	Not set

MMSC	http://mmsc.mobile.att.net

MMS proxy proxy.mobile.att.net

MMS port 80

MCC 310

MNC 410

Authentication Type	None

APN type	default,mms,supl,hipri

APN protocol	IPv4

Bearer	Unspecified
[T-Mobile LG G3] Dresden:
LG G3 Wireless Charging Battery Sticker Attachment, NFC Antennae, Qi Charging Recieve

Try this.

http://www.amazon.com/dp/B00MMRWS5E...TF8&colid=2SQVGTFG71SNV&coliid=I3DLQNOT2XSNF7
[Galaxy Note II Q&A, Help & Troubleshooting] Smokes68:
Can anyone Please tell me what would the best rom I could choose to install? I understand I can't downgrade from 4.4.2 to 4.1.2 what choices (if any) do I have? I have googled and tried my best to take in some of the vast info on XDA most confusing on what to exactly choose or look for Im not computer savy like many on here

Note 2 t0lexx LTE Kitkat 4.4.2 (drains battery quickly) despite stopping some apps with Titanium still feel as though the rom has a lot of bloatware, network works along with wifi and bluetooth

SuperSU, network unlocked, Clockworkmod recovery 6.0.4.1

knox0x1

FIRMWARE INFO

Bootloader N7105XXUFNI2

Baseband N7105BVUFNE1

PDA N7105XXUFN12

CSC N7105EVRNG1

Kernal N7105 3.0.31-2682814 dpi@SWDD 3912 #1

Would Ditto note 3 or 4 work or would I be better with Dimond Rom V8.0L or Nameless 5.0 (think I read somewhere of problems with Bluetooth and Wifi, Im not 100% sure)

Thank you for any help
[Galaxy Note II Q&A, Help & Troubleshooting] 1eyedmonster:
Miui v5 4.1 works on the kit kat bootloader
[Galaxy Note II Q&A, Help & Troubleshooting] Smokes68:
Would this give better battery life?

The link i clicked on earlier http://xdaforums.com/galaxy-s2/development/rom-miui-v5-v4-4-18-t2520363

Is there a link for this rom which will work for my phone, the ones I have seen say stock 4.2.1 or for other phones im not sure about international , just looking for something better that will replace kitkat 4.4.2

Thanks
[Android Apps and Games] gdstudiogame:
Escape Ghost Villa - Can You Escape In One Hour?

It is a point and click adventure game with a scary experience that take place inside a haunted house. Your goal is to destroy this wicked house and all the evil that is inside. The game has a lost of puzzles that will give you hours of gameplay until you beat it.

It was a dark and snowy night. Perfect time for a little breaking and entering, right? Deal with monsters and more in this creepy-cool point-and-click adventure that'll take you a surprisingly long time to finish and has piles of potential despite its design missteps.

Are you ready? We’ll see it!. Good luck and have fun!

Google Play:

https://play.google.com/store/apps/details?id=air.com.hbx.escape.escapeGhostVilla
[Android Apps and Games] gdstudiogame:
Anyone Pass this escape without walkthrough?
[HTC Desire 500] romanpesta:
Hello how to get s-off on dual sim version ? Please help!
[HTC Desire 500] micko9854:
Here's how

Find my quote on ultimate thread i wanna only say that you need to use rumrunner 0.71 proto,your device has to be on 1.26.401.2 and have ultimate kernel boot6 or boot8_no_oc with stock recovery flash firmware.zip first from RUU mode with relocked BL and then flash kernel and has to be rooted and busyboxed.You have to use windows 7 sp1 x64 or earlier and make sure every antivirus,antispyware is turned off and

htc sync,samsung kies,sony pc companion,itunes and other stuff to be closed completly..Use usb 2.0 port only no hub no usb 3.0..Device has also not to have lock screen pattern.. https://www.dropbox.com/s/3j5qnhto6709ujw/rumrunner_proto_0.7.1.zip?dl=0
[Networking] D_Maharaj:
Hi everyone,

I Recently purchased a t-mobile mda from ebay. The phone was locked to the t-mobile network, but i did manage to unlock it as im using the phone in Canada on the Fido network. Im having a problem sending and receiving MMS messages. When I try to send one, it says can not connect. And when i checked the servers, the only one available is the T-mobile mms server and it won't let me create a new one. Is there anything I can do so I can use MMS here in canada?
[Networking] spastico:
I don't have an answer.

But I know how frustrating it can be trying to find a solution.

Here is something one of the mods setup to help us find answers.

http://xdaforums.com/showthread.php?t=298893
[Networking] melbarr:
Your phone is probably "Application Locked". SIM unlocking allows you to use a sim from another provider but the data side is still locked down... try to get the application unlocker I had to do that for my t-mobile dash... also you could try changing the rom to an original HTC rom, provided you can find one

Cheers

melbarr
[Networking] D_Maharaj:
Do you know where i can get the application unlock program?
[Networking] luiggi:
"Application Locked"

Where did you learn the existense of such "Application Locked"? I haven´t heard about it untill now while I was reading your post. I have an 8525 that works at very low data connection speed, same phone flys when I use it with another service provider SIM, the funny part here is that my 8125 works great with both operators. So please redirect me to where you read or heard about "Application Locked" or tell us where one can get the application unlock program?

Thanks
[Sony Xperia T3] XperiaT3:
I think i'm not the only one who wants to root the T3. There are many guides which are very complicated for people who are no software developers...
[Sony Xperia T3] Ditarius:
http://xdaforums.com/xperia-t3/general/root-firmware-18-1-1-21-t2889847

If this is too complicated then probably you shouldnt even consider rooting - procedure cant be any easier. There isnt also any other way to root T3 ATM.

And yes, this works also with .25 (4.4.4 KK). And for different ver. of T3 (5102 for example) use software for your model as base.
[Sony Xperia T3] XperiaT3:
I think I know what to do. Can i use the sony Emma thing as the flash tool?
[Sony Xperia T3] avayrocks:
what to do now

I've installed adb drivers fastboot drivers and successfully flashed the .14 kernel then switched on the phone and trying to root using Xperia rootkit is not detecting my device and stuck like this(as shown in the screen shot) what to so and PC companion is also not detecting my t3 (but while am on .32kernel it works fine)

I've flashed the .32kernel (cause am on 4.4.4) again and repeated everything but same problem,, redownloaded the kernels but same problem,,

Why rootkit is not detecting my phone ??? Plz help