Related
I have a VZW 16GB Moto X currently rooted and safestrap installed, I keep defering the update since I don't want to lose root and am pretty sure it will fail since stock recovery is gone.
What are my options to either get the OTA with root or disabling the update notification?
I am not 100% sure i want to dive into an SS ROM nor is there really anything out there.
Just trying to figure out what I should do / what everyone else is doing.
DiGi91 said:
I have a VZW 16GB Moto X currently rooted and safestrap installed, I keep defering the update since I don't want to lose root and am pretty sure it will fail since stock recovery is gone.
What are my options to either get the OTA with root or disabling the update notification?
I am not 100% sure i want to dive into an SS ROM nor is there really anything out there.
Just trying to figure out what I should do / what everyone else is doing.
Click to expand...
Click to collapse
I would get the OTA with root. The camera and phone call difference really do show in my opinion.
To keep your root I would rsd back to stock. Download pwnmymoto and install it BUT don't run it. Just have it installed. Then update. After the update you can run pwnmymoto and you'll have root with the OTA. Jcase said this is the correct way to do it.
Sent from my XT1060 using XDA Premium 4 mobile app
ruben8448 said:
I would get the OTA with root. The camera and phone call difference really do show in my opinion.
To keep your root I would rsd back to stock. Download pwnmymoto and install it BUT don't run it. Just have it installed. Then update. After the update you can run pwnmymoto and you'll have root with the OTA. Jcase said this is the correct way to do it.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will consider doing that, it's just a giant PITA since I will have start from scratch.. Coming from the S III and flashing a new ROM every day this is so different to me lol. There is nothing wrong with the stock ROM just regretting not waiting for the dev edition to be honest.. I still use my S III as a media player and lately have been thinking of switching back, just hoping we get 4.4 soon or something to make it a bit better.
I know safe strap is another option but haven't heard great things about it and back in the droid 3 days remembered using it.
Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app
pyro6128 said:
Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Can you use the new FXZ to return to OTA'd stock if necessary down the road?
pyro6128 said:
Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I might do that, I just don't have the time right now. I heard the OTA is a big improvement though. I wish I could be rooted with write access and no need for workarounds lol wishful thinking..
EDIT: Besides using safestrap
anotherfiz said:
Can you use the new FXZ to return to OTA'd stock if necessary down the road?
Click to expand...
Click to collapse
Yup, stock OTA, but you can't go back to a previous version
DiGi91 said:
Yeah I might do that, I just don't have the time right now. I heard the OTA is a big improvement though. I wish I could be rooted with write access and no need for workarounds lol wishful thinking..
EDIT: Besides using safestrap
Click to expand...
Click to collapse
fyi. if you are on vzw then SS is an easy fix for you. The "not great things" you heard were just posts from when SS was having some problems. I have SS up and running with the new rom for vzw in a rom slot and flashed the new radios and everything is working perfectly. No problems for me at all. Also, tibu is really easy to use and will restore system data, your launcher and anything you want. Very minor things that you will need to screw with after using it. Takes about an hour and a half if you need to do things to your system after you start using the new rom. If you don't need to make any of those edits then it really only takes about 30 mins from installing SS to having the new rom running with all your settings and apps.
jayboyyyy said:
fyi. if you are on vzw then SS is an easy fix for you. The "not great things" you heard were just posts from when SS was having some problems. I have SS up and running with the new rom for vzw in a rom slot and flashed the new radios and everything is working perfectly. No problems for me at all. Also, tibu is really easy to use and will restore system data, your launcher and anything you want. Very minor things that you will need to screw with after using it. Takes about an hour and a half if you need to do things to your system after you start using the new rom. If you don't need to make any of those edits then it really only takes about 30 mins from installing SS to having the new rom running with all your settings and apps.
Click to expand...
Click to collapse
What about the limited space that is available when using SS?
Also idk If I want to RSD back to get the OTA seeing as "eventually" we will get 4.4 not sure what to do right now lol
I was thinking of trying out the SS OTA ROM but I really don't know also how did you flash the radios.. RSD?
http://www.droidrzr.com/index.php/t...-x-ss-rom-139151-update-10-31-13/#entry370601
Ota stock ROM never take ota's
DiGi91 said:
What about the limited space that is available when using SS?
Also idk If I want to RSD back to get the OTA seeing as "eventually" we will get 4.4 not sure what to do right now lol
I was thinking of trying out the SS OTA ROM but I really don't know also how did you flash the radios.. RSD?
Click to expand...
Click to collapse
if you are worried about space then just flash it to the stock rom. I have plenty of space. with 500 photos on it. I don't use music though. You don't have to rsd to get the ota. You can just flash the recovery.img if you didn't touch the system or flash the system.img as well if you need to using fastboot. Take some time to learn what fastboot and adb are and how to use them and you will be happy you did. Doesn't take much time at all. They are kind of the same thing, how they work at least.
Use fastboot when in fastboot mode. Use adb when the phone is just on normally. Then run appropriate commands. "adb reboot" "fastboot reboot"
here is a link on how to use adb and if you go through it and understand everything then you will also understand fastboot and fastboot will already be installed as well). Then you can take the ota without losing data and having to use RSD.
http://forum.xda-developers.com/showthread.php?t=872128
As for the new radios, you will need to use fastboot. you flash the non-hlos.bin then erase modemst1 and modemst2 then flash the fsg.mbn. if you want help with it just send me a pm
shane1 said:
http://www.droidrzr.com/index.php/t...-x-ss-rom-139151-update-10-31-13/#entry370601
Ota stock ROM never take ota's
Click to expand...
Click to collapse
Looks like WiFi isn't working on that ROM!?
Also could I restore my stock ROM to a ROM Slot on SS and then flash the OTA ROM over it?
This would not require TiBu or anything like that..
Just trying to figure the best and easiest way to do this.
Not sure bit if your on a slot it shouldn't hurt to try. I'd make a backup and put it on PC or the cloud to be safe.
shane1 said:
Not sure bit if your on a slot it shouldn't hurt to try. I'd make a backup and put it on PC or the cloud to be safe.
Click to expand...
Click to collapse
So boot into SS, backup my stock ROM - save on my pc, then make a ROM slot in SS and restore the backup to the slot? Can you even do that lol
Then if all is well flash the SS OTA ROM on top and I SHOULD be okay..
Might give it a shot likely need to update SS idk what the latest version is
DiGi91 said:
Looks like WiFi isn't working on that ROM!?
Also could I restore my stock ROM to a ROM Slot on SS and then flash the OTA ROM over it?
This would not require TiBu or anything like that..
Just trying to figure the best and easiest way to do this.
Click to expand...
Click to collapse
I just flashed it over my stock backup and it worked but doesn't fix wifi
shane1 said:
I just flashed it over my stock backup and it worked but doesn't fix wifi
Click to expand...
Click to collapse
That is a big issue, I need WiFi working...
I finally got around to messing with SS and the OTA ROM and did a backup of my stock slot and flashed the ROM to it. everything was working but no WiFi and I can't deal with that =/
Ended up restoring my stock slot backup.
I did however manage to update the baseband, super easy!
EDIT: Flashed the ROM on XDA and now I have working WiFi, looks like the one on droidrzr didn't work for me.
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
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
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
So I still have not received Android 6.0 on my Completely stock Nexus 6.
I'm on LMY48T...about a week ago I received a random update but nothing
changed.
It was bought from Motorola and is now activated on VZW as a Non-VZW Nexus 6
(even though that shouldnt matter)
Any Ideas?
(I don't want to flash the image files because i really do not want to go through the set
up process again. I plan on selling it as soon as i get my Nexus 6p anyways.)
Verizon has not yet released an OTA over their network to take their special N6 lollipop build to the unified Marshmallow, and has not even given a date yet for that release. I think if you have your Verizon SIM in place, the OTA will need to come from them.
I know that when I switched from my Verizon SIM to my Cricket prepaid SIM a couple of weeks ago, the Marshmallow unified OTA was immediately offered. Since then, I have used both the Verizon and my T-Mobile SIM and no OTA has been offered, my N6 is "currently up to date" on the international lollipop build it shipped with.
Sent from my VS985 4G using Tapatalk
Do you recommend taking it out and using WiFi? What other options do I have?
Sent from my Nexus 6 using XDA Free mobile app
collinjm01 said:
Do you recommend taking it out and using WiFi? What other options do I have?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I recommend installing a Cricket/AIO prepaid SIM and getting the OTA that way, if you don't want to sideload.
I know it's not so practical, sorry, but it's the only way I know for a fact works.
What is so strange about Verizon not sending 6.0 out OTA is that it's all the same exact build. No need for them to withhold it, they are just being assholes as usual.
Sent from my VS985 4G using Tapatalk
I'm on project fi, still on 5.1.1 waiting patiently. My Nexus 9 got the update a few days ago...
trent999 said:
I recommend installing a Cricket/AIO prepaid SIM and getting the OTA that way, if you don't want to sideload.
I know it's not so practical, sorry, but it's the only way I know for a fact works.
What is so strange about Verizon not sending 6.0 out OTA is that it's all the same exact build. No need for them to withhold it, they are just being assholes as usual.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
That actually works?
Sent from my Nexus 6 using Tapatalk
It did once. I refused the update, switched in my Verizon sim and then my T-Mobile sim, no updates, then I put back in my Cricket sim and now no update.
So, might have just been lucky that one time. I am in a different part of the country now than when it offered the update...
Sent from my Nexus 6 using Tapatalk
Is there a way to Sideload and not wipe data? or a safe way? (I mean that's technically how OTA does it anyways, i would assume) I would sideload if i knew it wouldn't wipe data.
I might just say screw it and install a 6.0 ROM and sell on Swappa as that (or per request a different ROM).
collinjm01 said:
Is there a way to Sideload and not wipe data? or a safe way? (I mean that's technically how OTA does it anyways, i would assume) I would sideload if i knew it wouldn't wipe data.
I might just say screw it and install a 6.0 ROM and sell on Swappa as that (or per request a different ROM).
Click to expand...
Click to collapse
Sideloading doesn't wipe data. If you flash a factory image it will wipe data by default, but sideloading the OTA is just like getting the update normally. I would look into the WugFresh tool, as it greatly simplifies the process.
[edit] If you're planning to sell it on Swappa wouldn't you need to wipe data anyway? A factory data reset is definitely recommended before selling a device.
unbesorgt said:
Sideloading doesn't wipe data. If you flash a factory image it will wipe data by default, but sideloading the OTA is just like getting the update normally. I would look into the WugFresh tool, as it greatly simplifies the process.
[edit] If you're planning to sell it on Swappa wouldn't you need to wipe data anyway? A factory data reset is definitely recommended before selling a device.
Click to expand...
Click to collapse
If you have unlocked the bootloader, you can flash the factory images, if you want to keep your data just don't flash the userdata image but flash all the rest.... there are instructions all over the place for this.
OTA zip
If you don't want to wait and don't want to flash the factory image, you can sideload the ota zip through ADB.
klharalson said:
If you don't want to wait and don't want to flash the factory image, you can sideload the ota zip through ADB.
Click to expand...
Click to collapse
unbesorgt said:
Sideloading doesn't wipe data. If you flash a factory image it will wipe data by default, but sideloading the OTA is just like getting the update normally. I would look into the WugFresh tool, as it greatly simplifies the process.
[edit] If you're planning to sell it on Swappa wouldn't you need to wipe data anyway? A factory data reset is definitely recommended before selling a device.
Click to expand...
Click to collapse
Gage_Hero said:
If you have unlocked the bootloader, you can flash the factory images, if you want to keep your data just don't flash the userdata image but flash all the rest.... there are instructions all over the place for this.
Click to expand...
Click to collapse
I appreciate the response guys. I ended up using WugFresh and just flashing the whole system image. I got tired of waiting and my battery life was terrible on 5.1.1. Now that i am on 6.0 it's like night and day difference. At this point im usually plugged into the wall at like 15% and im now on like 71%.
Once again thanks