Database Develop

[Beta Rom][10/5] Bare-Bonez v0.1

[BETA] Bare-Bonez v0.1​
DON'T GO ANY FURTHER UNTIL YOU READ THE FOLLOWING MESSAGE BELOW!​
This rom is based off the stock cricket 2.2.1 rom for the Zio M600. This rom will not contain all of the bloatware and unnecessary elements that come with your everyday stock rom. This rom contains the bare essentials to operate. If you were looking for the cricket applications that came with the rom they are not there anymore, but feel free to go to their website here for anything cricket related. I am not responsible for you lack of knowledge on how to take this bare-boned rom and customize it into what fits your liking or for any thing that happens to your phone because of what you did to it. I will be available to answer any questions you may have but that is all. This rom is just to provide users with only the elements they actually need while also providing performance tweaks to make your Zio M600 move like it is supposed to.
IF AND ONLY IF YOU'VE READ THE ABOVE CONTINUE​
>>>>CLICK HERE TO DOWNLOAD BARE-BONEZ v0.1<<<<<<<​
Features:
Adrynalyne's Beta Kernel included in Spz0's OpenZio 2.1.2 Rom
Stripped of all unnessacary applications
Busybox
ADW Launcher
Video Hardware Acceleration Enabled
Mobile Data Speeds Slightly Increased
Universal Androot's Latest Beta App
Tweaked Internal Task Manager (WIP)
Tweaked Kernel Settings (WIP)
Instructions:
Flashing
Boot into clockworkmod recovery via USB
Wipe User Data & Cache in the home options
Go into advanced options and wipe dalvik
Go into the mounts/storage and wipe system, data, cache
Go flash Bare-Bonez v0.1.zip via the menu and wait for success
Reboot
After reboot complete the google sign-in
Go to the app drawer choose "Universal Androot" and choose root in it's optoins
Dial *228 and let your phone complete its data programming
After reboot completes enjoy
If you enjoy this rom and would like to support my further work I put into this rom in the future, please click below and donate to me as a form of your appreciation and thankfulness
​
>>>>CLICK HERE TO DONATE<<<<​
Comments and questions are accepted and welcomed here on this thread.
Credits​
Code:
- [URL="http://forum.xda-developers.com/member.php?u=1415579"]Adrynalyne[/URL]: The Custom Kernel
- [URL="http://forums.whirlpool.net.au/archive/1340479"]montalbert[/URL]: For the network additions that I am currently experimenting with to see if they work for our Zio M600 Mobile Data
- [URL="http://forum.xda-developers.com/member.php?u=2992811"]Mattix724[/URL]: For providing me with the Cricket 2.2.1 Stock Rom
- [URL="http://forum.xda-developers.com/member.php?u=2984496"]Spz0[/URL]: For the updater-script I was too lazy to re-create and also busybox.
- The Viewers: For the support
-

Can you upload the zip to xda?
Sent from my Zio using xda premium

I can not since it is to large of a file to upload to xda's .zip attachment system.

It won't let me download, can you dropbox it?
Sent from my Zio using xda premium

Not at the moment but tomorrow I might be able to do so.

Can anyone else download and upload to dropbox so end users can download straight to their Zio?
Sent from my Zio using xda premium

Believe it or not, I just had someone offer me (sum too much to speak of) for my Zio, so I just sold it tonight.
Ironic, eh?
But, the good thing is that I can go get another one since Cricket is still selling them for only ~$50 but I have to wait a few weeks till I actually have enough to get the first month of service (wish I could just buy the phone but, whatever).
Anyway, so while I won't be participating at this precise moment, here's my contribution - the first ROM uploaded to Dropbox as requested. I haven't used my Dropbox account since I created it, so I have no idea how the hell it works to be honest (signed up so a friend got more space or whatever, no idea). I believe this link will get the download for anyone, but I'm not sure about the bandwidth potential and it getting throttled or capped or whatever.
Regardless, here ya go:
http://dl.dropbox.com/u/19019338/v0.1.zip
Hope to be testing this thing soon but, it'll be a while.

So I've flashed the rom and it has plenty of extra memory, I'm not seeing much difference in ram. Also the cricket mobile web app is not needed since it is only a shortcut to the browser, and since there is no browser you can get rid of it and some of the other cricket stuff.
Sent from my Zio using xda premium

Mattix724 said:
So I've flashed the rom and it has plenty of extra memory, I'm not seeing much difference in ram. Also the cricket mobile web app is not needed since it is only a shortcut to the browser, and since there is no browser you can get rid of it and some of the other cricket stuff.
Sent from my Zio using xda premium
Click to expand...
Click to collapse
The cricket's apps appear for you? O.O
On my phone they are not there......
Which one's are still auto-installing themselves onto our phones?
I have a script that can remove those applications from our phones if they are still appearing for some of you.
The ram difference isn't available yet due to my init.d script not working either because of the kernel or my permissions or something else.
This is no where near finished yet

-x]Trunks[x- said:
The cricket's apps appear for you? O.O
On my phone they are not there......
Which one's are still auto-installing themselves onto our phones?
I have a script that can remove those applications from our phones if they are still appearing for some of you.
The ram difference isn't available yet due to my init.d script not working either because of the kernel or my permissions or something else.
This is no where near finished yet
Click to expand...
Click to collapse
So far my experience with this phone is that the wiping dies not erase anything. So the stock apps will not be gone unless the end user removes them. I installed a custom boot screen over the cricket one and it has never been removed. Even after I restored the stock image it was still there.

I will be installing vbox on my laptop's windows 7 OS later and unpacking the kernel stickied on the forum and the one in open zio to see why init.d scripts aren't working and what are the differences I'll maybe have an updated release of the rom next week....
Sent from my Zio using XDA Premium App

jlmancuso said:
So far my experience with this phone is that the wiping dies not erase anything. So the stock apps will not be gone unless the end user removes them. I installed a custom boot screen over the cricket one and it has never been removed. Even after I restored the stock image it was still there.
Click to expand...
Click to collapse
I noticed that myself, as I can't get the cricket stock apps to re-appear but I have a script for you all to run if you want those apps gone. It wont work though until I figure out this init.d startup script problem. As for your "boot screen" do you mean splash image or boot animation?
Sent from my Zio using XDA Premium App

-x]Trunks[x- said:
I noticed that myself, as I can't get the cricket stock apps to re-appear but I have a script for you all to run if you want those apps gone. It wont work though until I figure out this init.d startup script problem. As for your "boot screen" do you mean splash image or boot animation?
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
the boot animation. before spaz created his rom the only way i could install a different boot animation was to overwrite the stock images with alternate ones for a custom boot experience. I removed all the cricket apps right after I got the phone plus half of the google junk that i dont use.
edit...
hey i just installed your rom. only one small issue you should include some kind of file browser so we wont have to push one onto the system to access our data. also it would be nice if you could add the reboot option like spaz did.

It's because I didn't do a wipe of the data partition. I figured the updater script would do the wiping.
Sent from my Zio using xda premium

jlmancuso said:
the boot animation. before spaz created his rom the only way i could install a different boot animation was to overwrite the stock images with alternate ones for a custom boot experience. I removed all the cricket apps right after I got the phone plus half of the google junk that i dont use.
edit...
hey i just installed your rom. only one small issue you should include some kind of file browser so we wont have to push one onto the system to access our data. also it would be nice if you could add the reboot option like spaz did.
Click to expand...
Click to collapse
Mattix nope it doesn't wipe the data partition that's why I instructed to do so
As for jlmancuso I have never added a reboot option to the end button long-press options. But I can add a file browser Is ES File Explorer okay? Or would a different one be better?

I use ES file explorer myself. Though any browser of your choosing would be perfectly acceptable. I like the stripped down style. Keep up the good work.

I'd say root explorer but it's a paid app... I can also make a backup of gapps and upload a zip.
Sent from my Zio using xda premium

Mattix724 said:
I'd say root explorer but it's a paid app... I can also make a backup of gapps and upload a zip.
Sent from my Zio using xda premium
Click to expand...
Click to collapse
I use root explorer myself
As for gapps I already have that ready for the next release but thanks for the offer. My main focus is the init.d script problem which i can't really examine until next week/this weekend maybe. But I'm working on it.

Is anyone else getting force closes on the Google search app, and force closes in acore while attempting to save contacts?
I think there was a few too many pulled off the system that are necessary for everyday use...
Sent from my Zio using xda premium

Mattix724 said:
Is anyone else getting force closes on the Google search app, and force closes in acore while attempting to save contacts?
I think there was a few too many pulled off the system that are necessary for everyday use...
Sent from my Zio using xda premium
Click to expand...
Click to collapse
were the force closes due to not having a browser at first boot of the rom? or when you have a browser downloaded from the market does it still force close?
if so in both situations i may have pulled to many apps. i'm still working on them rom atm

Nexus 5 Auto-Updater 4.4.4 with Root Restore

Introduction
This kit is designed to update Stock rooted Nexus 5 devices to Android 4.4.4 while retaining all user data as well as root permissions. This will also work on non-rooted devices with an unlocked Bootloader.
Before you Start
# This kit is designed to update without wipe but anything is possible, so I strongly urge you
to back up all data. Also I am not liable for any lost information.
# Please configure all ADB drivers
# Place phone in Fastboot mode. Power down the device; (Press and hold Power + Volume Down)
until the device boots into Fastboot.
# Extract all files, open the Unfathomable EXE file in the provided folder and follow the prompts Carefully.
Instructions
Run the EXE. After your device reboots, boot your Nexus into recovery. TWRP recovery should boot. Select the reboot option and reboot system.
You will be prompted "Swipe to flash SuperSU". This will restore all Root permissions.
*Also in the event that your device is stuck in a bootloop, just wipe the cache and you should be good to go!
Downloads
Nexus 5 Auto Updater 4.4.4 by Unfathomable.zip
The Kit can also be downloaded at this Dev Host URL
http://d-h.st/mRY
[Nexus 5 Auto Updater 4.4.4 By Unfathomable.zip - 451.78 MB]
Other Information
The Nexus 7 Wi-Fi Auto-Updater 4.4.4 can be found at this URL
http://forum.xda-developers.com/showthread.php?t=2791773
XDA:DevDB Information
Nexus 5 Auto-Updater, Tool/Utility for the Google Nexus 5
Contributors
Unfathomable
Version Information
Status: Beta
Created 2014-06-29
Last Updated 2014-06-29

Got to be one of the slowest downloads for such a small file in the history of man.
Painful to say the least.

For me, almost half a gig is something other than small.

TiltedAz said:
For me, almost half a gig is something other than small.
Click to expand...
Click to collapse
Still slow to download. Had faster larger files.
Sent from my SM-G900F using XDA Premium 4 mobile app

@home said:
Still slow to download. Had faster larger files.
Sent from my SM-G900F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And you're complaining in the OP's thread, why? Blame Dev-Host not them. Lol.

Not complaining, just stating a fact.
Sent from my SM-G900F using XDA Premium 4 mobile app

With all do respect to opinions I would greatly appreciate if this thread is used for and remains a hub for questions and support. With that being said I have taken the liberty of uploading the file into XDA's server for downloading. Please respect my wishes as I have taken my own personal time to provide the community with this tool and many more to come. Thank you all! If you have any concerns, feedback or need support please feel free to contact me at [email protected].
Sent from my Nexus 5 using XDA Premium 4 mobile app

Thanks for do us a easy way to update to v4.4.4 with stock rom! :good:

Just want to thank the op for making it so easy

It's a good idea but a little long winded when you can just flash a rooted stock ROM.zip via recovery.
Sent from my Nexus 5 using Tapatalk

Hello guys,
I am a newbie in this. I have Nexus 5 with Stock rooted 4.4.2. Will this method work for me to update to 4.4.4?
Thank you!

miserableboy said:
Hello guys,
I am a newbie in this. I have Nexus 5 with Stock rooted 4.4.2. Will this method work for me to update to 4.4.4?
Thank you!
Click to expand...
Click to collapse
Yes, it is not a requirement to be running 4.4.3. Let me know if you have any difficulties.

Out of Memory
I'm getting "error: out of memory" shortly after the update starts. It sends and writes the bootloader then reboots into the bootloader and gives me the error. What am I doing wrong?

ddukatz said:
I'm getting "error: out of memory" shortly after the update starts. It sends and writes the bootloader then reboots into the bootloader and gives me the error. What am I doing wrong?
Click to expand...
Click to collapse
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Unfathomable said:
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same thing here. Already wiped cache but no memory message appears.

Unfathomable said:
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Click to expand...
Click to collapse
Not sure which one but one of these things fixed it for me.
Thanks!

ddukatz said:
Not sure which one but one of these things fixed it for me.
Thanks!
Click to expand...
Click to collapse
Thank you for bringing the issue to my attention, and no problem I'm glad I was able to help.

I also don't want to offend the developer as he did spend a lot of time on this. I do respect him, but I wanted to share my opinion. The last couple of OTA's I just downloaded the update straight from the OTA thread to my phone, I then flashed them in TWRP. I didn't loose TWRP and it even gives an option to install SuperSU binaries if it doesn't see them.
However, I do want to stay on topic. I'm curious, for people who use xposed, would this tool allow an update without needing to uninstall modules? I'm just trying to see the differences between your method and flashing an OTA. Also, would people with custom kernels be able to update as well? If they can, then this would prove useful for those with custom kernels.
Again, I don't mean to offend the OP. I'm just curious about the differences/benefits.

PsychDrummer said:
I also don't want to offend the developer as he did spend a lot of time on this. I do respect him, but I wanted to share my opinion. The last couple of OTA's I just downloaded the update straight from the OTA thread to my phone, I then flashed them in TWRP. I didn't loose TWRP and it even gives an option to install SuperSU binaries if it doesn't see them.
However, I do want to stay on topic. I'm curious, for people who use xposed, would this tool allow an update without needing to uninstall modules? I'm just trying to see the differences between your method and flashing an OTA. Also, would people with custom kernels be able to update as well? If they can, then this would prove useful for those with custom kernels.
Again, I don't mean to offend the OP. I'm just curious about the differences/benefits.
Click to expand...
Click to collapse
It flashes the image not an OTA
Sent from my Nexus 5 using Tapatalk

rootSU said:
It flashes the image not an OTA
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh ok. That would make sense why the file is so big. So then, isn't this basically deleting the -w from the batch file and flashing normally? Well and retaining root.

NEXUS 6 OTA Question

Hello XDA, I recently rooted / unlocked my N6. I used WugFresh NRT to do so. However, I did not like the process of rooting so I (using NRT) flashed stock + unrooted and then factory reset followed by an OEM lock. Reading about lollipops new way of OTA, can I perform OTAs? Or is it too late?
Sent from my Nexus 6 using XDA Free mobile app

Hi,
As long as you are now stock, no system partition changes and Stock recovery, you should get and be able to install an OTA.
But, I don't own the device, so I'll have your thread moved to your device section in case there's something I don't know about the N6 in particular.
Good luck!

Thanks! I'm a newb to this whole technology stuff. My first nexus device as well. I soft bricked it too while attempting to remove a ROM.
Sent from my Nexus 6 using XDA Free mobile app

TheSkillfulTroll said:
Thanks! I'm a newb to this whole technology stuff. My first nexus device as well. I soft bricked it too while attempting to remove a ROM.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure if this is of any value to you but considering the device apps are similar it may be used.
http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865

Oh to be honest I'm done with rooting for now. Ill wait till 5.0.2 comes out if I OTA good then great but if it fails (hopefully ill still be able to access phone if it does) I'll then flash and root. Hopefully its not the latter
Sent from my Nexus 6 using XDA Free mobile app

TheSkillfulTroll said:
Oh to be honest I'm done with rooting for now. Ill wait till 5.0.2 comes out if I OTA good then great but if it fails (hopefully ill still be able to access phone if it does) I'll then flash and root. Hopefully its not the latter
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
If your completely stock and unrooted their is nothing to worry about. You will indeed get updates.

Even with lollipops new way of checking?
They check blocks
Sent from my Nexus 6 using XDA Free mobile app

if you are rooted and on TWRP. Just download the 5.0.1 image. Extract it till you see the system.img and boot.img. Also download twrp and run
fastboot flash system system.img
fastboot flash boot boot.img
I then reboot and then run
fastboot flash recovery whateverthefilefortwrpis.img
after that restart to system and twrp will ask if you want to install supersu. I let it install and now i'm on 5.0.1. Everything is intact and no wipe is required.

I don't think you quite understand what I am asking... I had 5.0.1 , I rooted and unlocked using NRT. I installed a ROM, didn't like it and attempted to remove. At the attempt to remove it, I screwed up and the setup wizard wouldn't start, so I FORCE FLASHED USING NRT Stock and unrooted. This allowed me to start the phone and use it, I factory reset then relocked the OEM. I do not want to root nor unlock, I am asking if that, after these events, and lollipops new way of OTA, will I be able to update via OTAs?
Sent from my Nexus 6 using XDA Free mobile app

What is the new way lollipop handles OTA's?
Sent from my Nexus 6 using Tapatalk 4

Back then, it used to check file by file which was easily avoidable. Now, it checks a whole block of a partition, if it sees something as small a byte changed, it aborts. You can read more NY just googling Nexus 6 OTA root.
Sent from my Nexus 6 using XDA Free mobile app

TheSkillfulTroll said:
Back then, it used to check file by file which was easily avoidable. Now, it checks a whole block of a partition, if it sees something as small a byte changed, it aborts. You can read more NY just googling Nexus 6 OTA root.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It's not hard to understand, actually quite simple. If you have flashed the stock image then there is nothing to worry about and there is no need for assumptions. Yes, you will receive OTAs. No need for the "what if" and "how about," if you aren't willing to accept an answer, don't ask a question.

If you're 100% stock then you will get ota.

Oh okay, thanks for the help! Once 5.0.2 rolls out, if it does not work, I'll just have to do it within NRT
Sent from my Nexus 6 using XDA Free mobile app

Updating to 5.1 from 5.0.1

Hey guys I have a Moto bought Nexus 6, running on T-Mobile network Sim card and all. Currently the 6 is on 5.0.1 and has been asking me to bump up to 5.1. My phone is stock and rooted. As we all know I can't use the OTA as a result.
I'm here bugging you all because I know there are different builds for the Nexus 6, and they seem carrier specific. So I went and hunted down an M build which supposedly is for Tmo, as we have some specific tweaking.
I downloaded the LMY47M build and I am currently on the LRX22C 5.0.1 build. What I would like to know is it okay for me to go into TWRP and flash the download? Like the way a person would flash a nightly of CM? Is it the same process? If not what do I gotta do?
(On a bus ride so would be nice to have it update while I'm still riding)
Sent from my Nexus 6 using XDA Free mobile app

If the "download" is an OTA, it cannot be flashed from a custom recovery. ...and it will still fail because you're rooted.

Nope I downloaded online and it's sitting in a download folder now
Sent from my Nexus 6 using XDA Free mobile app

dynamo147 said:
Nope I downloaded online and it's sitting in a download folder now
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Let me rephrase, if the file you have downloaded is the same file you would get as an ota, then what i said before.

Very likely it's the same but I can't say for sure.,. So where does that leave me in terms of options?
Sent from my Nexus 6 using XDA Free mobile app

dynamo147 said:
Very likely it's the same but I can't say for sure.,. So where does that leave me in terms of options?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know much about this "M" build and what version it is supposed to flash from. What I do know is there is no full factory image available.
Of everything else is stock on your phone (Including radio) I think the best action would be:
- download the factory image for the version you are on now.
- extract it and fastboot flash the stock recovery and system.img
- do NOT lock your bootloader
Then you should be able to accept the ota or side load it from stock recovery.

Mmm will try this when I get home thanks! Will be back to update Folks!
Also, will flashing the stock image and recovery wipe any of my data?
Sent from my Nexus 6 using XDA Free mobile app

dynamo147 said:
Mmm will try this when I get home thanks! Will be back to update Folks!
Also, will flashing the stock image and recovery wipe any of my data?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Not if you extract it an flash only the system.img
Its flashing the userdata image that wipes data

Yes. I would like to know how to do this also. Is there a difference in flashing the D or E version of 5.1 and then flashing a custom ROM that is built from T-Mobile's update?
Or is there carrier specifics in the different Factory Images?

downloading the img right now, when i get back I will make a little step by step for anyone else curious

dynamo147 said:
downloading the img right now, when i get back I will make a little step by step for anyone else curious
Click to expand...
Click to collapse
Its only 3 steps and I already Gave them earlier in the thread

BossJ said:
Yes. I would like to know how to do this also. Is there a difference in flashing the D or E version of 5.1 and then flashing a custom ROM that is built from T-Mobile's update?
Or is there carrier specifics in the different Factory Images?
Click to expand...
Click to collapse
In my mind in its the radio. you want the radio that comes with the T Mobile version. (if you are on t-mobile obviously) what you flash on top of it for system doesn't matter as long as it supports the radio and is version 5 .1. And as long as what you're flashing doesn't include the radio you are good to go.
So for me as long as I keep the E radio for Verizon I can flash D through M it kind of doesn't matter.
Sent from my Google N6 on VZ

rootSU said:
Its only 3 steps and I already Gave them earlier in the thread
Click to expand...
Click to collapse
Thanks for your replies here. I'm in the same boat as the OP, and have one follow-up question to this thread, if you or anyone could answer --
After doing the steps you mentioned previously -- specifically sideloading/accepting the OTA update, will the bootloader remain unlocked? I'd like to re-root afterwards and keep the user data, though I was under the impression it would actually re-lock the bootloader.
Thanks for any info!

vormund said:
Thanks for your replies here. I'm in the same boat as the OP, and have one follow-up question to this thread, if you or anyone could answer --
After doing the steps you mentioned previously -- specifically sideloading/accepting the OTA update, will the bootloader remain unlocked? I'd like to re-root afterwards and keep the user data, though I was under the impression it would actually re-lock the bootloader.
Thanks for any info!
Click to expand...
Click to collapse
Yes, your bootloader will remain unlocked.

dynamo147 said:
Hey guys I have a Moto bought Nexus 6, running on T-Mobile network Sim card and all. Currently the 6 is on 5.0.1 and has been asking me to bump up to 5.1. My phone is stock and rooted. As we all know I can't use the OTA as a result.
Click to expand...
Click to collapse
Did you ever get this going? I know I procrastinated a bit due to the "unknowns", but finally made it happen (bug off, TMo "5.1 Available" notification!). I ran into a lot of oddities between my phone and computer (running Windows 7) like the phone being an unrecognized device when working with adb sideloads... I ultimately opened the Device Manager and forced the composite ADB driver through for each instance. For me, the rough flow was, starting out with stock but unlocked and rooted,
* flashed stock LRX22C system and recovery images
* used adb to sideload the T-Mobile LMY47M official update
* flashed TWRP
* used adb to sideload SuperSU
* and of course, cleared the dalvik/cache and rebooted
All data in-tact, and my LEDs are still functional (the LEDs are actually the key reason I have it rooted right now... it's insanely stupid that Google blocks these built-in LEDs from being used by those that want them!).
Anyways, if you run into any of those issues, happy to help!
Evolution_Freak said:
Yes, your bootloader will remain unlocked.
Click to expand...
Click to collapse
Thank you...exactly what I needed to know!

Ah yeah I did actually, and I like you, had problems getting the phone recognized with the ADB, also windows 7, which prevented me from slide loading like I wanted to, but nevertheless got all the updates pushed through thnx though!
Sent from my Nexus 6 using XDA Free mobile app

Came back from M and now cm12.1 won't boot

Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app

Try a factory image?

sookieball said:
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
advice, thought, or a suggestion.. dont use toolkits until you know what you are actually doing. do things the right way, until you learn how to do it properly. then use all the toolkits you want. the problem is that toolkits dont teach you a single thing, and doing things right on any nexus is very easy.
my suggestion would be to wipe data/system then reflaah cm again.

sookieball said:
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Junk ROM anyway.. Lol

simms22 said:
advice, thought, or a suggestion.. dont use toolkits until you know what you are actually doing. do things the right way, until you learn how to do it properly. then use all the toolkits you want. the problem is that toolkits dont teach you a single thing, and doing things right on any nexus is very easy.
my suggestion would be to wipe data/system then reflaah cm again.
Click to expand...
Click to collapse
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Oh and thank you for the wipe/advice.
I did :-/ go fig
Reflashed before I restored backup but no go.
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Did you downgrade the bootloader back to 5.1.1?

Evolution_Tech said:
Did you downgrade the bootloader back to 5.1.1?
Click to expand...
Click to collapse
Yes, manually first and when it wouldnt* boot past animation, last resort was NRT
So I'm assuming NRT flashed boot loader associated to LMZ28E
Edit: maybe if I downgrade down to 5.0.1? Then reroot and recovery?
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
Yes, manually first and when it would boot past animation, last resort was NRT
So I'm assuming NRT flashed boot loader associated to LMZ28E
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do we know for a fact the that we can downgrade the bootloader from m? We learned we couldn't downgrade from 5.1 bootloader.

rootSU said:
Do we know for a fact the that we can downgrade the bootloader from m? We learned we couldn't downgrade from 5.1 bootloader.
Click to expand...
Click to collapse
I reread the thread like 3x.
And it was mentioned that another user used NRT to downgrade successfully.
I thought the same thing, but didn't try it till I read that thread till 4am. This morning decided to take the plunge.
I was thinking also, if I just reflash bootloader and radio and put M back on, then just try manually flashing 5.1?
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Oh and thank you for the wipe/advice.
I did :-/ go fig
Reflashed before I restored backup but no go.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
i did flash the new bootloader, but i went back and forth from M to terminus(rom) about 5 times yesterday. flaah the new bootloader again, and keep it. you trying to downgrade it might be the issue. btw, i flashed m, and the bootloader, via twrp recovery, its much easier and faster that way. after, i made a backup in recovery. so now all i do to go back and forth is restore the backups.
oh, and i meant you no disrespect. while it doesnt include everyone, most people using toolkits around here are noobs. and they are the ones that usually get stuck. so, i apologize

simms22 said:
i did flaah the new bootloader, but i went back and forth from M to terminus(rom) about 5 times yesterday. flaah the new bootloader again, and keep it. you trying to downgrade it might be the issue. btw, i flashed m, and the bootloader, via twrp recovery, its much easier and faster that way. after, i made a backup in recovery. so now all i do to go back and forth is restore the backups.
Click to expand...
Click to collapse
I think that's where I messed up from the beginning when I flashed M.
I didn't notice the modified boorloader that doesn't force encryption and it was all downhill from there.
That being said,
Should I flash modified boorloader to not force encrypt, and blah blah blah?
Sent from my Nexus 6 using XDA Free mobile app

Disregard

sookieball said:
I think that's where I messed up from the beginning when I flashed M.
I didn't notice the modified boorloader that doesn't force encryption and it was all downhill from there.
That being said,
Should I flash modified boorloader to not force encrypt, and blah blah blah?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
moddified bootloader? huh? there is a modified kernel thats not supposed to force encryption. i did flash it, even though i am encrypted(by choice).

http://forum.xda-developers.com/showthread.php?p=61027468
I'm assuming that's what this is.
Lol I never tried or even downloaded it so not 100% but yeah
Lol **** my bad. Lol its boot.IMG not boorloader hahaha! #nooberror for reals lol
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
http://forum.xda-developers.com/showthread.php?p=61027468
I'm assuming that's what this is.
Lol I never tried or even downloaded it so not 100% but yeah
Lol **** my bad. Lol its boot.IMG not boorloader hahaha! #nooberror for reals lol
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
thats probably the same one i flashed. btw, in the op he has a twrp flashable version of the bootloader, the kernel, the radio, and the rom.. http://4ndr01d.com/repos/shamu/jdx/

simms22 said:
thats probably the same one i flashed. btw, in the op he has a twrp flashable version of the bootloader, the kernel, the radio, and the rom.. http://4ndr01d.com/repos/shamu/jdx/
Click to expand...
Click to collapse
God I wish it was a faster download link -_- lol
BTW, when I first downloaded and flashed boorloader via twrp (radio also) rebooted twrp to flash ROM, and sdcard was wiped
It shouldn't do that right?
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
God I wish it was a faster download link -_- lol
BTW, when I first downloaded and flashed boorloader via twrp (radio also) rebooted twrp to flash ROM, and sdcard was wiped
It shouldn't do that right?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
no, it shouldnt unless you accidentally did it yourself. ive seen people do that too often. if you go into the wipe menu, be sure to go into advanced options, where you can pick what you want wiped.or itll wipe everything.

K so everything's downloaded....
Going to flash in a sec all via twrp.
Report back .
Wish me luck lol
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
K so everything's downloaded....
Going to flash in a sec all via twrp.
Report back .
Wish me luck lol
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
fingers crossed

What cracks me up the most is people that posses limited knowledge about fastboot flashing partition images are just seemingly willy nilly flashing images not really fully understanding what they are doing/flashing. We all have to learn somehow but I wouldn't do it at the expense of flashing a boot loader. If anything went wrong during a boatloader flash you would definitely have an unrecoverable hard brick.
Moral of the story.... People, read the how to's and SLOW down... Think about what you are doing. After reading the above replies its clear to me that people are getting a bit confused with a boot.img and a bootloader.img. its OK guys. Just be careful