Database Info

I'm trying to avoid another brick PLEASE HELP

Howdy y'all. I bricked my old G2 D800, I don't want a repeat with the new one. I tried doing all the research I could. I have a new D800, 10d, 4.4.2. I want CM11, tried reading the threads on that and custom recovery. I just need a little help to make sure I have the order of operations down pat before I crash another. I've rooted and flashed ROMs before, but not with th locked boot loader and security AT&T has.
Please just correct me if I'm wrong. Through the threads I have read I believe this is what I am to do.
1.) Flash my 4.4.2 back to 4.2.2 using LG FT
2.) Root using IO23
3.) Download Flashify & install TWRP 2.7.7 with Loki
4.) Follow steps to install CM 10.2
5.) Follow steps to install CM 11
Of course make backup once 4.2.2 plus root and TWRP is achieved before trying CM. I just want CM like I've had on previous phones. Thanks in advance.

All is good back to being ROM junkie. Anyone who does read and wishes to flash custom roms and get custom recovery on KK. Obtain root via IOroot25, then use AutoRec Recovery Installer for TWRP recovery.

Easiest way to reinstall stock rom

Hi all as title states my moto g is downloading the new 5.0 update but during install it says error and switches phone back on with no changes made. It was rooted and custom firmware was installed. Since then uts back to fully unrooted, stock recovery is reinstalled and bootloader is still unlocked. However still it errors a quarter into installing.
So i have come to the assumption that it is best for me to revert/ reinstall the stock 4.4.4 rom back on and try updating after that. However seen loads of complicated methods on how to reinstall the stock firmware onto my phone so want the easiest way if possible.
In attatchments is the info from the current stock rom that is on the phone (will state a custom rom has never been installed to the phone always been stock) and i have downloaded the following to put onto it:
XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
Ive tried using the mototools v3.1 and does abserlitly nothing non of the commants work or do anything with my phone.
So which is the easiest method?
Many Thanks

major problems!!!!!
Stock recovery installed to phone. Started update it was installing and got to 3/4 of the way through, errored, restarted and not goes in a loop saying no command!
Phone will not switch on!!!
Why has this happened?

If fastboot is too convoluted - using a custom recovery, flash one of these zips:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510​

What update were you installing when it errored?

[HELP] mobile network connections won't function after upgrading to cm12 firmware

I've used CM12.1 based ROMs for a while now, and with my talent have managed to brick my bacon (oneplus one global 64GB), and unbrick it (using this guide)
I've restored it to stock with no problem using this tool.
my problem begins when i try to update to any LP ROM - flashing such ROMs' zip files in TWRP returned "E: error executing updater binary in zip". i found two solutions to this error:
1. first one is described in this thread. i ditched this method after it got me stuck in bootloop every time after flashing a ROM
2. second one (probably the way it should be done) is to update device firmware like described in this oneplus forums thread. flashing this zip indeed allowed me to successfully install my ROM but with one big problem - the SIM card is detected for a few seconds (even then the device wont find any networks) and then drops to "no SIM card detected - emergency calls only" then it gets detected again and so on...
I've also tried flashing some different modems like described here but it didn't change anything
have anyone encountered any network related problem after upgrading to a CM12.1 based ROM or have any idea how to solve my problem (mobile network connections won't function after upgrading to cm12 firmware)?
help would be very appreciated!
edit: if it helps, i also found that OTA updating to the latest build XNPH44S also breaks the phone's ability to connect to a mobile network

Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon

yashshan said:
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
Click to expand...
Click to collapse
1. TWRP must be installed before installing OxygenOS as it comes as a flashable zip and not an OTA/Cyanodgen update...
2. installing OxygenOS was no problem without the firmware, however after it booted i noticed it broke my mobile communications in a very similar way, so no luck with that one.
3.even after installing oxygen the firmware update is required to install anything like a CM nightly or a CM based LP ROM, and my problem was that this firmware upgrade broke my network connection, so i don't see how that could help me in any way
3.1 after flashing OxygenOS not even the firmware update would allow me to install a different ROM...
4. i linked the forum thread my firmware update came from (also found a similar suggestion in a YouTube video) and couldn't find any reference to it in any of the main ROMs' threads like you suggested, they all just say to install TWRP wipe everything and flash their zip (some say to flash a nightly before)
any other ideas? I'm starting to get desperate around my suddenly not-so-functional bacon :crying:

!!SOLVED!!
steps:
1. flash the latest CM12S fastboot image
2 .delete line 2 "aassert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");" from the updater-script file in the custom ROM's ZIP installation file
3. flash the "hacked" zip file with no problem
4. enjoy your custom ROM installed bacon, WITH your mobile connection.
thanks for the help anyway!

Need help of root, recovery & ROM on D80020y

I have an AT&T D800 and current software version is official 4.4.2 D80020y. I want to install official CM12.1 or preferably CM13, but i am extremely confused on where to start given that i havent done any modifications to my device before. I tried ioroot but it seems that my firmware version is not supported. Then i am not sure on the recovery part as well. which recovery is best for installing CM12/13? i read that some recovery causes the device to be soft bricked. If someone could give me a quick walk through on how to go about rooting and installing a recovery that supports all roms, it would be extremely helpful.

Can't get MM-based roms to work (LL-based roms run fine)

So I've been trying to update my Shield LTE ROW since this Friday from the stock based rom LL (version 3.1.1) to the MM-based rom (version 4.2) and spend a dozen of hours failing to update :crying:
When I install a MM-based rom the shield boots and the nvidia logo shows a few seconds and then the screen goes black. When the tablet is attached to my pc I noticed that the tablet is not turned off but booted in APX-mode.
These are the things I've tried:
Installing the recovery image 4.2 (fails)
Installing the recovery image 4.1 (fails)
Installing the recovery image 4.0.1 (fails)
Installing the recovery image 3.1.1 (works)
Installing several full and incremental OTA updates to 4.x (fails)
Installing CM 13.0 (fails)
Installing carbon 5.1.1 (works)
Followed the guides mentioned in topics: http://forum.xda-developers.com/shield-tablet/help/unable-to-update-to-marshmallow-rom-t3444124 and http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541 (fails)
I've tried a lot of things, but now I'm out of ideas.
Has anyone a explanation why MM-based roms don't want to boot on my tablet? And has the knowledge to fix this?
All feedback is welcome and appreciated.

You are currently able to flash and boot with 3.1.1 or stuck in apx mode?

I'm able to flash and boot with 3.1.1. Only MM-based roms are stuck in apx mode when booting.

You are probably on the Lollipop boatloader still. With that bootloader MM based roms don't work. Flash the latest stock from here, root it with cf-autoroot, flash twrp and MM based roms should work.

Thanks for your advice, I'll try it this weekend.
Just a quick question, why do I need to root and flash twrp? Shouldn't it work if I only flash the latest stock?