Came back from M and now cm12.1 won't boot - Nexus 6 Q&A, Help & Troubleshooting

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

Related

[q] verizon g2 with no recovery and boots to verizon screen help

Hey guys, this is my first post. I recently bought a rooted verizon G2(VS980)and i tried to flash a rom on it. Im a noob, so of course the worst happened. My phone will boot past the LG screen, but then stays at the "verizon" screen. If i try to put it in recovery(i have cwm) it just reboots. I really need a fast fix, im having to use the good ole slll until my jewl is working again. Thanks in advance
Davidmay6 said:
Hey guys, this is my first post. I recently bought a rooted verizon G2(VS980)and i tried to flash a rom on it. Im a noob, so of course the worst happened. My phone will boot past the LG screen, but then stays at the "verizon" screen. If i try to put it in recovery(i have cwm) it just reboots. I really need a fast fix, im having to use the good ole slll until my jewl is working again. Thanks in advance
Click to expand...
Click to collapse
You need to make sure your boot stack and radios are appropriate for the rom you want to flash. The G2 ROM scene is a bit fractured, since CM11 and a good chunk of derivative ROMs are still based on the 12B (4.2) OTA, but some devs are now working with the 24A (4.4) OTA.
If you can get into the bootloader/fastboot, you may be able to flash the appropriate boot stack and recovery from there, if you know what you're doing. The "cleaner" route would be to use TOT or KDZ to get back to stock, and start from scratch.
Sent from my Nexus 7 using Tapatalk
arkolbus said:
You need to make sure your boot stack and radios are appropriate for the rom you want to flash. The G2 ROM scene is a bit fractured, since CM11 and a good chunk of derivative ROMs are still based on the 12B (4.2) OTA, but some devs are now working with the 24A (4.4) OTA.
If you can get into the bootloader/fastboot, you may be able to flash the appropriate boot stack and recovery from there, if you know what you're doing. The "cleaner" route would be to use TOT or KDZ to get back to stock, and start from scratch.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i can get my phone into download mode, but nothing more. Also, i had 12B and the rom(wich i downloaded from xda) said it was specifically for 12B.
Davidmay6 said:
i can get my phone into download mode, but nothing more. Also, i had 12B and the rom(wich i downloaded from xda) said it was specifically for 12B.
Click to expand...
Click to collapse
Did you make a backup of the rom, prior to installing the new Rom?
Sent from my GT-N5110 using XDA Premium 4 mobile app
evolishesh said:
Did you make a backup of the rom, prior to installing the new Rom?
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes.
Davidmay6 said:
Yes.
Click to expand...
Click to collapse
If you can't get into recovery, and only download mode, I'd probably go ahead and return to complete stock. The nice thing about this phone is it is easily rooted and rommed again if you want to do that. Plus you'll learn a lot in the process. My two cents. :thumbup:
Edit: When you return to stock, take the Ota to 4.4.2, then root.
Sent from my VS980 4G using XDA Free mobile app

KTU84P (4.4.4) Updater

Your bootloader must be unlocked to use this. If your bootloader is not already unlocked, unlocking it will wipe your data and this method is not recommended.
This is a modified factory image that will not erase your user data or custom recovery. This can be used even if you’re rooted and with modified system files, xposed framework, or custom recovery. Once installed you will lose root, just flash supersu in your custom recovery. Xposed should still be on your device so just go into the app and re-install it. For any modified system files, you will have to re-modify those.
This is intended for those on the stock rom, rooted, and with a custom recovery. It’ll work if you have a custom rom but will put the stock system on.
I am not responsible for anything you do to your device so flash at your own risk. Always backup before doing any significant changes to your device. I would recommend off your device in case something happens
.
To use, download the modified factory image here http://d-h.st/mYI Use 7-zip or winrar to extract the files.
Supersu by chainfire can be found here, CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
Boot into the bootloader. From a cmd window opened where the flash-all file is just type flash-all. You can use shift, right click on the occam-ktu85l-Modified folder to open a command window in the correct folder. ADB/FASTBOOT must be intalled on your PC.
You can also just double click on the flash-all.bat
This is tested on a windows machine; however it should work on a Mac too, flash the flash-all.sh.
work like a charm on Mac
Man, you guys are fast! :good:
Could someone please tell me if this can be flashed through Wug toolkit?
Unleashed by my Nexus 4
Awesome! Will try now and report back ( on 4.4.3, xposed, cwm, root)
EDIT
working flawlesly. also no problems with hellscore karnel
ty alot for this OP
Aw damn, I didn't see this and I used the stock factory image...oh well :/ 4.4.4 is good for me so far....except wifi tethering. Anyone else having that issue, as well? It started with 4.4.3 for me.
hp420 said:
Aw damn, I didn't see this and I used the stock factory image...oh well :/ 4.4.4 is good for me so far....except wifi tethering. Anyone else having that issue, as well? It started with 4.4.3 for me.
Click to expand...
Click to collapse
Try factory reset, maybe it will fix your issue?
Could anybody share the extracted zip for those of us at work not near a computer??
Sent from my Nexus 4 using Tapatalk
First of all, sorry my poor English.
I have Custom Rom (Slimkat 4.4.3) with root and twrp. Can I flash this file? Do I lost my datas (download, photos, etc) ?
¿Do I have to put the 4.4.4 baseband ?.
Thank you very much and sorry by my poor english.
You have to wait for slimkat, this is the stock image
Worked perfectly on a rooted Nexus 4 with 4.4.2. All data was kept
Works! Txn bro!
Sent from mobile
sidnoit22 said:
Try factory reset, maybe it will fix your issue?
Click to expand...
Click to collapse
Thanks, that was one suggestion I've found. Unfortunately nothing has worked for me. It apparently is a bigger issue than I knew. There's already a ticket for it here: https://code.google.com/p/android/issues/detail?id=62516 Hopefully they fix it soon, because with 4.4 and 4.4.2 I got a lot of random reboots, and with 4.4.3/.4 I can't enable the wifi hotspot.
RASTAVIPER said:
Could someone please tell me if this can be flashed through Wug toolkit?
Unleashed by my Nexus 4
Click to expand...
Click to collapse
Any info on this?
Can I select Sideload from WUG and directly flash this rom??
RASTAVIPER said:
Any info on this?
Can I select Sideload from WUG and directly flash this rom??
Click to expand...
Click to collapse
No
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Care to share any more info?
What is the difference with flashing through fastboot?
Unleashed by my Nexus 4
RASTAVIPER said:
Care to share any more info?
What is the difference with flashing through fastboot?
Unleashed by my Nexus 4
Click to expand...
Click to collapse
This flashes all the images contained in the factory image except for userdata and recovery. It's just the factory image with some modifications made to it. You could flash all those same images in fastboot if you wanted to
I'm not familiar with wugs toolkit do I dint know what it does
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
This flashes all the images contained in the factory image except for userdata and recovery. It's just the factory image with some modifications made to it. You could flash all those same images in fastboot if you wanted to
I'm not familiar with wugs toolkit do I dint know what it does
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, the proper reply to my question is : "I don't know".
Anyway, I will try with Wug and report later with results.
Unleashed by my Nexus 4
So, after trying myself with Wug toolkit, I can confirm that after a few clicks at my pc and flashing only boot, bootloader and system img files, I managed to upgrade from 4.4.3 to 4.4.4 with no problems.
Unleashed by my Nexus 4
Worked flawlessly. Of course you can manually fastboot flash system, boot, and radio and not the data from the occam zip package so as not to lose your data

TWRP 2.7.1.0

Not my project but thought this might help people find it: TWRP 2.7.1.0 for KK Bootloaders by dhacker29
http://androidhosting.org/Devs/Dhacker29/msm8960/
Edit: To avoid confusion I changed the link to the one RikRong posted that will give you the M only version. File name: TWRP2710-RAZR_M-KITKAT.img.
Edit2: Looks like the links are down so here is a link to a post that @rahimali provided in this thread. Its for TWRP 2.8 and 2.7.1.0.
http://forum.xda-developers.com/showpost.php?p=56420813&postcount=28
already had it, but thanks
allen_ho said:
already had it, but thanks
Click to expand...
Click to collapse
This works on the M?
RedBullet said:
This works on the M?
Click to expand...
Click to collapse
That one does not, but you can get the correct one here: http://androidhosting.org/Devs/Dhacker29/msm8960/
Sent from my HTC6525LVW using Tapatalk
RikRong said:
That one does not, but you can get the correct one here: http://androidhosting.org/Devs/Dhacker29/msm8960/
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Which one exactly?
RedBullet said:
Which one exactly?
Click to expand...
Click to collapse
One that says M instead of HD
Sent from my XT907 using Tapatalk 2
anyone else have a problem with this not recognizing the touch commands and just basically acting like its frozen? Nothing works I left it for awhile and came back to it and tried to open the slide lock and it doesn't do anything. The battery is fully charged so what I guess I have to do is wait for the thing to die so I can get out of recovery.
UPDATE: Still not working for me but I was able to shut it down by pressing the Power + Volumes Up and Down Keys
argedion said:
anyone else have a problem with this not recognizing the touch commands and just basically acting like its frozen? Nothing works I left it for awhile and came back to it and tried to open the slide lock and it doesn't do anything. The battery is fully charged so what I guess I have to do is wait for the thing to die so I can get out of recovery.
UPDATE: Still not working for me but I was able to shut it down by pressing the Power + Volumes Up and Down Keys
Click to expand...
Click to collapse
I don't ... But which version are you on... The correct one that RikRong linked?
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
I don't ... But which version are you on... The correct one that RikRong linked?
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I downloaded the correct one from RikRong and it was the one that says:
TWRP2710-RAZR_M-KITKAT.img
I redownloaded it and tried again but still no avail. Touch just refuses to work with this for me. So I'll just have to stick to 2630
argedion said:
Yes I downloaded the correct one from RikRong and it was the one that says:
TWRP2710-RAZR_M-KITKAT.img
I redownloaded it and tried again but still no avail. Touch just refuses to work with this for me. So I'll just have to stick to 2630
Click to expand...
Click to collapse
That's strange, I haven't had that issue either. Maybe a bad DL? Try downloading and flashing again.
maybe a different means of flashing it too...
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
maybe a different means of flashing it too...
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how else should i flash it?
fastboot flash recovery "Image"
this is all I know?
It was a long shot but there is flashify and rashr...
Sent from my XT907 using XDA Premium 4 mobile app
argedion said:
anyone else have a problem with this not recognizing the touch commands and just basically acting like its frozen? Nothing works I left it for awhile and came back to it and tried to open the slide lock and it doesn't do anything. The battery is fully charged so what I guess I have to do is wait for the thing to die so I can get out of recovery.
UPDATE: Still not working for me but I was able to shut it down by pressing the Power + Volumes Up and Down Keys
Click to expand...
Click to collapse
:: ditto ::
no luck with twrp so switched back to cwm. i also flashed the same way using fastboot
well I'll give the flashy a try and see but I think its more an issue with my phone. but I got time to play so we'll give it a shot.
Ok tried doing it with flashy and still the same result just no touch at all so I just give up with this and will stick with the one that works for me
argedion said:
well I'll give the flashy a try and see but I think its more an issue with my phone. but I got time to play so we'll give it a shot.
Ok tried doing it with flashy and still the same result just no touch at all so I just give up with this and will stick with the one that works for me
Click to expand...
Click to collapse
Are you on the KK bootloader? I believe its a requirement. I used rashr to flash it myself.
danbest82 said:
Are you on the KK bootloader? I believe its a requirement. I used rashr to flash it myself.
Click to expand...
Click to collapse
Looking at my bootloader I do not think I am on the KK bootloader it gives me a date of 2013-09-25 I am assuming that is the original bootloader that it came with. Guess I'll do a search for the KK bootloader and see if I can get that flashed over.
argedion said:
Looking at my bootloader I do not think I am on the KK bootloader it gives me a date of 2013-09-25 I am assuming that is the original bootloader that it came with. Guess I'll do a search for the KK bootloader and see if I can get that flashed over.
Click to expand...
Click to collapse
To get the KK bootloader, I flashed the latest OTA through rsd lite. It should keep the boot loader unlocked but will remove root. If you plan on using a stock ROM, Q9Nap's GPE is very smooth and stable. Their thread gives links and instructions on how to flash OTA.
So the Frog has officially Croaked his Phone.
Yes you heard right I have managed to kill my phone. Only good thing is that I couldn't use it for much more than a mini wifi tablet so I didn't really loose anything.
I could not get Twrp 2710 to work was because I had the old boot loader So I decided to update the boot loader which I did but now the phone will not go out of the boot logo screen. I have successfully reinstalled my ROM and still will not go past the boot logo screen. I have tried fastbooting back to the old bootloader but no luck there either. I have spent about 2.5 hours this morning trying different things to get it to work and nothing I have found or came across will work. I have however successfully installed twrp 2710 and now have it working. Considering that is the only area of the phone That I can actually get into i guess thats something.
Some of the older Roms won't boot on the kk kernel they will not boot past the boot logo... When you upgraded did you flash the entire kk firmware via rsd? And it wouldn't boot past the boot logo...
Sent from my XT907 using XDA Premium 4 mobile app

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

Categories

Resources