Database Develop

[Q] cyanogenmod 11 on z1?

any one was flashing cyanogenmod 11 on z1?
any guide (how to)?
link: http://download.cyanogenmod.org/?device=honami

I'm using cm11 on my z1
To install that you need have unlocked bootloader, root
And install recovery
sorry my bad english

bruno_sbrn said:
I'm using cm11 on my z1
To install that you need have unlocked bootloader, root
And install recovery
sorry my bad english
Click to expand...
Click to collapse
no problems whit your english, i guess your are from domican republic too, if yes please send me a private message to talk in spanish.
i have a C6906 model, with locked booloader, i think flash with C6906_14.1.G.1.534 ftf, root and install recovery..
what more I need to do?
what about the performance of cm11? worth the effort?

jcmordan said:
no problems whit your english, i guess your are from domican republic too, if yes please send me a private message to talk in spanish.
i have a C6906 model, with locked booloader, i think flash with C6906_14.1.G.1.534 ftf, root and install recovery..
what more I need to do?
what about the performance of cm11? worth the effort?
Click to expand...
Click to collapse
you cant install CM11 with a locked bootloader
i recommend you unlock bootloader and install latest DoomKernel (no need to downgrade unless you want to back-up TA which is a must. Also you must be on 4.3 stock first to avoid broken camera issue when unlocking bootloader) then download and flash rom and gapps.
Sorry if some of the stuff is a bit obvious just want to insure you don't brick your device.

RealiableCandy4 said:
you cant install CM11 with a locked bootloader
i recommend you unlock bootloader and install latest DoomKernel (no need to downgrade unless you want to back-up TA which is a must. Also you must be on 4.3 stock first to avoid broken camera issue when unlocking bootloader) then download and flash rom and gapps.
Sorry if some of the stuff is a bit obvious just want to insure you don't brick your device.
Click to expand...
Click to collapse
how can i unlock bootloader?

jcmordan said:
no problems whit your english, i guess your are from domican republic too, if yes please send me a private message to talk in spanish.
i have a C6906 model, with locked booloader, i think flash with C6906_14.1.G.1.534 ftf, root and install recovery..
what more I need to do?
what about the performance of cm11? worth the effort?
Click to expand...
Click to collapse
No, no, I'm from Brazil, my english and my spanish is bad.
Flash the 14.2.A.0.290 because this not have the camera issue when you unlock the bootloader.
http://techbeasts.com/2013/12/19/install-cwmtwrp-recovery-root-sony-xperia-z1-c6903-running-latest-14-2-0-a-290-firmware-how-to-guide/
follow this to root and instal recovey
edit -------------------
Sorry, I did not see that you have the c6906 model, mine is c6903, but in the developement threads have the process to unlock bootloader, root and instal recovey, just search

my phone say
Bootloader unlock allowed: No.
i cant ullock bootloader.

you have to follow this

stoan123 said:
you have to follow this
Click to expand...
Click to collapse
If Bootlader Unlock Allowed saying NO it cannot be unlocked so your post is useless. BTW, there is no work around, it's locked permanently.
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
But you can get Root or Install Custom Roms, NO Custom Kernels.

eclyptos said:
If Bootlader Unlock Allowed saying NO it cannot be unlocked so your post is useless. BTW, there is no work around, it's locked permanently.
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
But you can get Root or Install Custom Roms, NO Custom Kernels.
Click to expand...
Click to collapse
No CM?

Yup no cm sums it up pretty good
Gesendet von meinem C6903 mit Tapatalk

jcmordan said:
No CM?
Click to expand...
Click to collapse
No.

help getting cm11 on c6903
bruno_sbrn said:
edit -------------------
Sorry, I did not see that you have the c6906 model, mine is c6903, but in the developement threads have the process to unlock bootloader, root and instal recovey, just search
Click to expand...
Click to collapse
Any chanse you can give me a noob proof guide with download links and all that stuff to get it on my z1?
Is ur camera still working by the way? Thats a must.
I have installed stock. 136 rom with the bootloader unlocked.
Seartched for the whole rooting proces on Google but I dont understand how it works cause ive seen 1000000 different ways to do it.
Would be verry thankfull!
Send me a pm.

noodlezbeats said:
Any chanse you can give me a noob proof guide with download links and all that stuff to get it on my z1?
Is ur camera still working by the way? Thats a must.
I have installed stock. 136 rom with the bootloader unlocked.
Seartched for the whole rooting proces on Google but I dont understand how it works cause ive seen 1000000 different ways to do it.
Would be verry thankfull!
Send me a pm.
Click to expand...
Click to collapse
i searched far and wide for a noobproof guide but couldnt find one end-to-end guide. it's a matter of sourcing different stages and doing it together. after many soft bricks - i worked it out.
ill try my best to make one
1) from what you said above, the only thing you need now is recovery mode - TWRP or CWM
you can get that by flashing DoomKernel's .136 advanced stock kernel - http://forum.xda-developers.com/showthread.php?t=2448613
"v07 (changelog)
[Xperia Z1] DooMKernel v07 {MIRROR}
[ MD5HASH: c3e3beefa08889ef78c311bc3922af00 ]"
use this youtube guide to flash it using fastboot - http://www.youtube.com/watch?v=l1Mp7MojuJo
2) download the latest cyanogenmod nightly - http://download.cyanogenmod.org/?device=honami&type=nightly
transfer the .zip file onto your sd card
3) boot into recovery (by turning off your phone, turning it back on and tapping the up button) and DO A BACKUP - http://www.youtube.com/watch?v=7815OazAECQ
4) follow the video from 1:18 onwards - http://www.youtube.com/watch?v=Gvi0cbMz1V8
end.
yes, the camera issue is fixed.
MAKE SURE YOU BACKUP EVERYTHING
hope this helps.

[Q] Questions about Bootloader Unlocking, Rooting and TA Backup!!

Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Thanks..

ro xl123 said:
Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
Click to expand...
Click to collapse
Follow the NUMEROUS instructions already posted. There are some in my signature
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
Click to expand...
Click to collapse
No, that's why every guide says to downgrade
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
Click to expand...
Click to collapse
Yes, messing with the bootloader can lead to a hard brick, yes you need root to backup the TA
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Click to expand...
Click to collapse
Follow the link in my signature to get that done

ro xl123 said:
Hello XDA forums, i've recently bought a Sony Xperia Z1 (C6906) and it has android KitKat 4.4.2, i'm not sure about the exact version tough, update center says that it's the most recent version. Now I have a couple questions,
Click to expand...
Click to collapse
The answare are spread over here, why do not take some more time to read?
ro xl123 said:
1) First of all, I want to root my device and my former experiances on Android was on my Galaxy S4, which i could simply use Odin to do most stuff. From what I understood, that option is not possible, at least when my phone is just, stock. How can I root this stock phone easily?
Click to expand...
Click to collapse
To root your Z1 (C6906) you have to downgrade to .534 Firmware, Install DualRecovery, Ungrade to Pre-Rooted Kitkat by NUT.
ro xl123 said:
2) And also I've heard that I had to downgrade the device in order to be able to root it. I don't want to downgrade, especially to 4.3, can't I just root in the current firmware?
Click to expand...
Click to collapse
No way! You have to downgrade then upgrade to pre-rooted version.
ro xl123 said:
3) Is bootloader a dangerous thing to mess with? Some say if I don't take backup of TA, I may hard-brick the device. Is that true? And is it an easy thing to do? To backup TA, do I have to root?
Click to expand...
Click to collapse
Is not dangerous. You brick phones just doing mistakes. You don't have to Unlock Bootloader to gain Root. So skip this part.
ro xl123 said:
4) Also how can I install CWM to my device. I also want to install CWM on my device.
Click to expand...
Click to collapse
Download the lates DualRecovery for Z1 which have CWM, Philz and TWRP Recovery, all 3 in one. Just run the application from PC and install to phone, but you have to be on .534 FW.
Start reading here:
http://forum.xda-developers.com/showthread.php?t=2711982
---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------
@gregbradley ..LOL..

Thanks all. Thank you for your help.

eclyptos said:
The answare are spread over here, why do not take some more time to read?
To root your Z1 (C6906) you have to downgrade to .534 Firmware, Install DualRecovery, Ungrade to Pre-Rooted Kitkat by NUT.
No way! You have to downgrade then upgrade to pre-rooted version.
Is not dangerous. You brick phones just doing mistakes. You don't have to Unlock Bootloader to gain Root. So skip this part.
Download the lates DualRecovery for Z1 which have CWM, Philz and TWRP Recovery, all 3 in one. Just run the application from PC and install to phone, but you have to be on .534 FW.
Start reading here:
http://forum.xda-developers.com/showthread.php?t=2711982
---------- Post added at 08:33 PM ---------- Previous post was at 08:31 PM ----------
@gregbradley ..LOL..
Click to expand...
Click to collapse
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982

ro xl123 said:
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982
Click to expand...
Click to collapse
Nothing, because you cannot flash it as you do not have a recovery yet///
Please follow the instructions in my signature, they are correct

gregbradley said:
Nothing, because you cannot flash it as you do not have a recovery yet///
Please follow the instructions in my signature, they are correct
Click to expand...
Click to collapse
So what is usb flash mode then?

when asked to enter flashmode hold the volume down button on your (Turned off) phone and attach the usb cable

ro xl123 said:
The firmware on this link is the same version as mine. What would happen if I simply flash this on my device?
link: http://forum.xda-developers.com/showthread.php?t=2711982
Click to expand...
Click to collapse
This is why the people get confused. Downgrade to .534 first, then install DualRecovery, then follow the Instruction from that link to get to your Firmware Rooted.
I think @[NUT] should add this steps on his threads for people like you who start from not rooted .681, .757 and so on.

eclyptos said:
This is why the people get confused. Downgrade to .534 first, then install DualRecovery, then follow the Instruction from that link to get to your Firmware Rooted.
I think @[NUT] should add this steps on his threads for people like you who start from not rooted .681, .757 and so on.
Click to expand...
Click to collapse
Well, I tought Sony would be just like Samsung, after all they are both androids is what I tought. Well, it's diffrent :/ Anyways I got to make sure about the things I do, because they may end up as bad things such as brick or etc.
I got it now, it's almost done.
Back in S4, all I had to do was to take the phone into Odin mode, then flash tar.md5's via odin, and it was all over, I installed cwm and rooted without downgrading and so. I feel sad that Xperia wasn't like. Well it's a great phone tough..
thanks alot everybody!

ro xl123 said:
Well, I tought Sony would be just like Samsung, after all they are both androids is what I tought. Well, it's diffrent :/ Anyways I got to make sure about the things I do, because they may end up as bad things such as brick or etc.
I got it now, it's almost done.
Back in S4, all I had to do was to take the phone into Odin mode, then flash tar.md5's via odin, and it was all over, I installed cwm and rooted without downgrading and so. I feel sad that Xperia wasn't like. Well it's a great phone tough..
thanks alot everybody!
Click to expand...
Click to collapse
It's very easy to Root the Z1, if I will had a chance in 5 minutes all will be done and the pain gone.

eclyptos said:
It's very easy to Root the Z1, if I will had a chance in 5 minutes all will be done and the pain gone.
Click to expand...
Click to collapse
Well, yeah but the downgrading part kind of sucks. Anyways, after installung recovery, it's all easy

ro xl123 said:
Well, yeah but the downgrading part kind of sucks. Anyways, after installung recovery, it's all easy
Click to expand...
Click to collapse
Just put the .534 FW in Flashtool Folder and flash it. Then connect to PC and use the Installer to install Dual recovery...the rest you know...
BTW, wipe everything any time you flash anything (Data, Appslog, Cache) to execute a clean installation. Yes, you will lose your data, but better be safe instead have issues later.

eclyptos said:
Just put the .534 FW in Flashtool Folder and flash it. Then connect to PC and use the Installer to install Dual recovery...the rest you know...
BTW, wipe everything any time you flash anything (Data, Appslog, Cache) to execute a clean installation. Yes, you will lose your data, but better be safe instead have issues later.
Click to expand...
Click to collapse
So, having root and recovery without unlocking bootloader in version .757 OFW is not possible? The thing is, I don't really want to unlock the bootloader, but i really want to have root privilleges, recovery mod is optional tough, i tought i could root easily with using CWM. So what I want is not possible?

ro xl123 said:
So, having root and recovery without unlocking bootloader in version .757 OFW is not possible? The thing is, I don't really want to unlock the bootloader, but i really want to have root privilleges, recovery mod is optional tough, i tought i could root easily with using CWM. So what I want is not possible?
Click to expand...
Click to collapse
So you just telling me that you did not understood a single word from what we already told you, great!
Follow the 3 steps provided by @gregbradley

eclyptos said:
So you just telling me that you did not understood a single word from what we already told you, great!
Follow the 3 steps provided by @gregbradley
Click to expand...
Click to collapse
No, I understood but kinda didn't wanted to.. :/
I already downgraded, rooted and installed recovery. Then I updated to stock rom 757 back, thinking that I could simply root using recovery. Anyways, after I updated, I couldn't get in to recovery mode, because the one I installed was without unlocking bootloader, I simply installed firmware based recovery. I don't really think about unlocking bootloader, the TA codes and stuff kinda scares me.. I did took backup of my TA tough. I just need to have root in OFW Kitkat. I can do without recovery (which i can't install because of bootloader). But root is essential. :/

ro xl123 said:
No, I understood but kinda didn't wanted to.. :/
Click to expand...
Click to collapse
You did NOT.
Downgrade, install DualRecovery, upgrade with the Pre-Rooted .757 using the method for LOCKED Bootloader by NUT here: http://forum.xda-developers.com/showthread.php?t=2711982
Start from the line How to update to 14.3.A.0.757:
DONE.

eclyptos said:
You did NOT.
Downgrade, install DualRecovery, upgrade with the Pre-Rooted .757 using the method for LOCKED Bootloader by NUT here: http://forum.xda-developers.com/showthread.php?t=2711982
Start from the line How to update to 14.3.A.0.757:
DONE.
Click to expand...
Click to collapse
OHHHHHHH... I'm so sorry, really. Now I understood it. Thanks alot man.. !! I love you :laugh:

ro xl123 said:
I love you :laugh:
Click to expand...
Click to collapse
I love you too.

[Q] How to Root CM11 Snapshot in 12.1.A.1.207???

Im using Xperia SP with Stock Firmware 12.1.A.1.207
I want the complete procedure to root CM11 Snapshot which was recently released
I tried 2 figure it out Myself but there are a lot of different way to do it so Im confused with the order and methods
So PLZ Help Me by giving Me the links to all required files and tools and also the COMPLETE Procedure to install it
Im having an Unlockable Bootloader (but I didnt Unlock it yet), with no custom recovery or kernel installed and also I have not rooted My mobile yet
PLZ HELP ME

bharathulaganathan said:
Im using Xperia SP with Stock Firmware 12.1.A.1.207
I want the complete procedure to root CM11 Snapshot which was recently released
I tried 2 figure it out Myself but there are a lot of different way to do it so Im confused with the order and methods
So PLZ Help Me by giving Me the links to all required files and tools and also the COMPLETE Procedure to install it
Im having an unlocked Bootloader (but I didnt Unlock it yet), with no custom recovery or kernel installed and also I have not rooted My mobile yet
PLZ HELP ME
Click to expand...
Click to collapse
flash this stock kernel with recovery http://forum.xda-developers.com/showthread.php?t=2649923,
just wipe data, cache, dalvik cache and install the CM11 rom in cwm recovery or twrp,
flash in cwm the supersu download in this site for root http://download.chainfire.eu/supersu
hope this will help you

bharathulaganathan said:
Im using Xperia SP with Stock Firmware 12.1.A.1.207
I want the complete procedure to root CM11 Snapshot which was recently released
I tried 2 figure it out Myself but there are a lot of different way to do it so Im confused with the order and methods
So PLZ Help Me by giving Me the links to all required files and tools and also the COMPLETE Procedure to install it
Im having an Unlockable Bootloader (but I didnt Unlock it yet), with no custom recovery or kernel installed and also I have not rooted My mobile yet
PLZ HELP ME
Click to expand...
Click to collapse
to root it the easy way is this http://forum.xda-developers.com/showthread.php?t=2783885
its just an app, and only thing you need is enable unknown sources and install it...after you done it, go to play store and download supersu app and you will have the root... do you know how to unlock your bootloader???
---------- Post added at 09:34 AM ---------- Previous post was at 09:32 AM ----------
kimikim0 said:
flash this stock kernel with recovery http://forum.xda-developers.com/showthread.php?t=2649923,
just wipe data, cache, dalvik cache and install the CM11 rom in cwm recovery or twrp,
flash in cwm the supersu download in this site for root http://download.chainfire.eu/supersu
hope this will help you
Click to expand...
Click to collapse
he doesnt have a recovery man...:silly:
and he doesnt have unlocked bootloader, if he do that with locked bootloader he will end in BOOTLOOP...

Gara91 said:
to root it the easy way is this http://forum.xda-developers.com/showthread.php?t=2783885
its just an app, and only thing you need is enable unknown sources and install it...after you done it, go to play store and download supersu app and you will have the root... do you know how to unlock your bootloader???
---------- Post added at 09:34 AM ---------- Previous post was at 09:32 AM ----------
he doesnt have a recovery man...:silly:
and he doesnt have unlocked bootloader, if he do that with locked bootloader he will end in BOOTLOOP...
Click to expand...
Click to collapse
yeah i know but i give him the instruction for installing the cm11 , sorry for misunderstanding

kimikim0 said:
yeah i know but i give him the instruction for installing the cm11 , sorry for misunderstanding
Click to expand...
Click to collapse
no problem

Gara91 said:
to root it the easy way is this http://forum.xda-developers.com/showthread.php?t=2783885
its just an app, and only thing you need is enable unknown sources and install it...after you done it, go to play store and download supersu app and you will have the root... do you know how to unlock your bootloader???
---------- Post added at 09:34 AM ---------- Previous post was at 09:32 AM ----------
he doesnt have a recovery man...:silly:
and he doesnt have unlocked bootloader, if he do that with locked bootloader he will end in BOOTLOOP...
Click to expand...
Click to collapse
My kernel is v3.4.0 built on 8 july 2014... So will towelroot work (its smtin like it works only on built b4 3 june)... Will towelroot work in My device???

bharathulaganathan said:
My kernel is v3.4.0 built on 8 july 2014... So will towelroot work (its smtin like it works only on built b4 3 june)... Will towelroot work in My device???
Click to expand...
Click to collapse
i think it will...give it a try...

Every One thanx a Lot for Ur replies...

bharathulaganathan said:
Im using Xperia SP with Stock Firmware 12.1.A.1.207
I want the complete procedure to root CM11 Snapshot which was recently released
I tried 2 figure it out Myself but there are a lot of different way to do it so Im confused with the order and methods
So PLZ Help Me by giving Me the links to all required files and tools and also the COMPLETE Procedure to install it
Im having an Unlockable Bootloader (but I didnt Unlock it yet), with no custom recovery or kernel installed and also I have not rooted My mobile yet
PLZ HELP ME
Click to expand...
Click to collapse
It's basically "flash", not "root" Cyanogenmod ROM. Cyanogenmod is already rooted.
If you really wish to do so, go to this link for an in-depth guide.

TechnoSparks said:
It's basically "flash", not "root" Cyanogenmod ROM. Cyanogenmod is already rooted.
If you really wish to do so, go to this link for an in-depth guide.
Click to expand...
Click to collapse
Thanx a lot 4 Ur help... I flashed PAC-man ROM... Its for LBL n totally OSM...

bharathulaganathan said:
Thanx a lot 4 Ur help... I flashed PAC-man ROM... Its for LBL n totally OSM...
Click to expand...
Click to collapse
Well congratulation to you!

[Q] How to not Brick my Nexus 6 Android 5.1

Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance

Flashed 5.1 BL and Modem on euphoria 5.0.2, then flashed back to stock 5.0.1, then flashed euphoria again, the same build upon which i flashed the 5.1 BL and Modem.
I didn't flash CM, still bricked my phone . And i don't know why. Coz after flashing it worked for a while and next morning it was bricked.

pallefar said:
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Click to expand...
Click to collapse
Most of the others relocked their bootloader after flashing the full 5.1 image and ended up in a bootloop. Not the end of the world but now the "enable OEM unlock" unsets every time you boot so if you lock the bootloader and end up in a bootloop, you cannot unlock the bootloader which means you cannot flash anything to recover.

Dont relock your bootloader?
So would you say that if you have unlocked the bottloader then dont relock it untill a fix for the brick has been found?
Also if you update to 5.1, the stay with 5.1 Roms to be on the safe side?
Thanks in advance, just want to help pthers with same questions

pallefar said:
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Click to expand...
Click to collapse
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 ----------
randy6644 said:
Flashed 5.1 BL and Modem on euphoria 5.0.2, then flashed back to stock 5.0.1, then flashed euphoria again, the same build upon which i flashed the 5.1 BL and Modem.
I didn't flash CM, still bricked my phone . And i don't know why. Coz after flashing it worked for a while and next morning it was bricked.
Click to expand...
Click to collapse
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?

pallefar said:
So would you say that if you have unlocked the bottloader then dont relock it untill a fix for the brick has been found?
Click to expand...
Click to collapse
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..

Better be safe then sorry
JulesJam said:
I think people are bricking b/c they are downgrading 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, 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:
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; and
5) never take an OTA unless you have reverted back to stock completely.
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.
Click to expand...
Click to collapse
Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above

i believe it would be controlled by the kernel/OS...and thats how it gets disabled upon boot of 5.1

pallefar said:
Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above
Click to expand...
Click to collapse
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.

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

pallefar said:
What is the benefit of mfastboot compared to normal fastboot flashing? just want to make sure everyhitng is covered
thanks in advance
Click to expand...
Click to collapse
http://mark.cdmaforums.com/MotoX-mFastboot.htm

pallefar said:
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Click to expand...
Click to collapse
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.

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?
Sent from my Nexus 6 using Tapatalk

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

pallefar said:
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
Click to expand...
Click to collapse
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.

zelendel said:
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.
Click to expand...
Click to collapse
Yep. I think @zephiK chroma is aosp no-cm.

awesome thanks guys, I think this thread will guide people to not brick thier phones

kenbrownstone said:
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?
Click to expand...
Click to collapse
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 ----------
zelendel said:
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.
Click to expand...
Click to collapse
Yep, that will do it - downgrading the bootloader is a no-no on a motorola phone except in rare cases when it was possible.
zelendel said:
My advise would be to know what your flashing by always inspecting the zip file before you flash it.
Click to expand...
Click to collapse
Always!

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?

JulesJam said:
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:
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.
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?
Click to expand...
Click to collapse
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.

Do i have to unroot before rolling back to marshmallow?

i'm trying to rollback to marshmallow using the official package, i found this in the precautions before installation
"2. Make sure your phone system version has not been unlocked or rooted."
1. why is that. is it because their policy against root or is it actually going to cause problems during the rollback process?
2. if yes i should unroot: do i simply click unroot from kingroot app or are there more comprehensive way to unroot?
thanks

09009494 said:
i'm trying to rollback to marshmallow using the official package, i found this in the precautions before installation
"2. Make sure your phone system version has not been unlocked or rooted."
1. why is that. is it because their policy against root or is it actually going to cause problems during the rollback process?
2. if yes i should unroot: do i simply click unroot from kingroot app or are there more comprehensive way to unroot?
thanks
Click to expand...
Click to collapse
Just relock the bootloader and your phone shall be unrooted.

jonezie said:
Just relock the bootloader and your phone shall be unrooted.
Click to expand...
Click to collapse
not sure how to do that because i used kingroot with a single click

Just install stock recovery then flash the roll back package.
After that, flash stock MM rom for your device.

swedenboy said:
Just install stock recovery then flash the roll back package.
After that, flash stock MM rom for your device.
Click to expand...
Click to collapse
what about the bootloader that jonezie is talking about?

i flashed rooted c432b836 with rolback package first small one then i got c900b300, after that i flashed c432b136, and successfully got back to marshmalow. so, realy dont know why i need unroot or flash stock recovery, if its working anyway

09009494 said:
what about the bootloader that jonezie is talking about?
Click to expand...
Click to collapse
For me, the only way to relock bootloader is flashing stock firmware.
Last time, I tried relock bootloader by SRK Tool and it costed me 2 days to get my device back to normal, since it encountered serious error.
---------- Post added at 12:23 AM ---------- Previous post was at 12:21 AM ----------
Arnys said:
i flashed rooted c432b836 with rolback package first small one then i got c900b300, after that i flashed c432b136, and successfully got back to marshmalow. so, realy dont know why i need unroot or flash stock recovery, if its working anyway
Click to expand...
Click to collapse
I always flash stock recovery before flashing stock rom, and I didn't try flashing stock rom over twrp. Next time I'll try ?