Related
Theoretically this might work. Can you use the first backup that was made when you first rooted your phone to go back below 7.893
waffleb051 said:
Theoretically this might work. Can you use the first backup that was made when you first rooted your phone to go back below 7.893
Click to expand...
Click to collapse
You can but there are several partitions that will not be restored (cdt.bin, recovery, boot (where kernel is located), as well as the radios). As long as this is true. You cannot be complete stock or flash any updates. As of now, if you are on 5.7.893, best to stay there and wait for a compatible update maybe in the future.
open1your1eyes0 said:
You can but there are several partitions that will not be restored (cdt.bin, recovery, boot (where kernel is located), as well as the radios). As long as this is true. You cannot be complete stock or flash any updates. As of now, if you are on 5.7.893, best to stay there and wait for a compatible update maybe in the future.
Click to expand...
Click to collapse
Well i was looking around on your cheesecake leak to complete stock forum and on page 5 a person named wingrider1964 used this
http://forum.xda-developers.com/showthread.php?t=1279825
the user chose 5 and and installed cheesecake and he got the ota update to 5.8.894. I am going to pm him and see what he says. At this point i dont mind if I lose root i have a Droid Eris that i can play around with. AGAIN LOSING ROOT IS NOT A BIG DEAL lol
I just posted on another thread about 5.7.893 or any other cheesecake leaked updates. (Not to be confused with "OTA" updates as they aren't). Anyone who has a non-OTA update installed right now, is screwed for the moment. There is no way back. This is the joys of a locked bootloader. The OTA updates out there are patching known versions to the new version. So, for example, the 5.5.886->5.5.893 update patches files from 5.5.886 including the boot image. The 5.5.893->5.9.901 update then patches the 5.5.893 files including the boot image. Those updates can *ONLY* be applied to the version they are meant to update. What we need is a full update installer that doesn't care what version you're on (ideal IMO) or an update made specifically for 5.7.893 (or whatever leak you're on). That's it. Our only options.
On the plus side nothing is wrong with my phone knock on wood i just would like to be on the path for ota
I forgot i also found this http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path-3.html
I am on T-Mobile Nexus 6 with 5.0.1, rooted with NRT (used Chainfire + TWRP Recovery). I have been expecting to get a notification to update to 5.1 within the device, but haven't gotten anything, even when I manually check for updates from the device (Settings > About > Update). Do I need to do something manually since I am rooted? I also looked for the 5.1 M build on Google's repository and couldn't find it. Thanks for the help!!
Over the air will not apply with a custom recovery. you can be patient and wait for M (NRT will update < 12 hours after Google does) or you could flash a stock recovery and OTA.
If you wait and use NRT there will be an option for the M version and then you can just do a flash to that version with the retain user option
Sent from my Google N6 on VZ
theres a stock, rooted T-Mobile build in the development section. Just flash that
I too have been waiting of the factory image to show up. Is there any reason why the TMo version hasn't been posted yet by Google? I'd like to use the stock image as it seems the easiest way to retain my data. I know there are other methods but they all seem to wipe your phone.
OGMCVilleTC said:
I too have been waiting of the factory image to show up. Is there any reason why the TMo version hasn't been posted yet by Google? I'd like to use the stock image as it seems the easiest way to retain my data. I know there are other methods but they all seem to wipe your phone.
Click to expand...
Click to collapse
Except the method posted immediately before your post.
I'll look for it. Thanks for the info.
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Rachel Ambler said:
Since I first started down this Android path I've always brought my phones direct from big red which, for all the problems it created it did make life simple when it came to identify which ROM to download etc.
This week I broke tradition and dropped some money on Google's lap and picked up a Nexus 6 direct from them - no more locked down to VZW for me if I so choose.
Previously I had a Incredible, then a GS III then finally a M8 - all three rooted and unlocked\S-OFF'd so this isn't my first rodeo.
That said I'm also wanting to tread VERY VERY lightly here because time and time again I read the the biggest reason folk get bricks is because they assumed and didn't ask questions before they flashed.
So, all this aside, here I am with my now Unlocked 5.0 Non branded Nexus 6 with LNX07M with TWRP 2.8 latest as a custom recovery and, as of right now, no root (to help ease any upgrade).
I've found various Stock ROMS out there there would indicate I'd need to be however on 5.0.1 before I could sideload a 5.1.1. Is this true? If so, do I need to blow away TWRP before I do this because when I tried previously to take the update it dropped me into TWRP.
Is there any way I can avoid all this, wipe and flash a Stock 5.1.1 direct? Wiping the phone isn't an issue as there's nowt on it right now. And should I root now, while still on 5.0 or wait until 5.1.1 (because it'll require a factory reset). Would root even survive a 5.1.1 upgrade?
I'm nervous here because I keep seeing lines such as 'T-MOBILE only' and different code letters after the build name seemingly signifying the different vendors. Given that I got mine direct from Google though I'm unsure how I should proceed because I really don't want to be left with an unhappy 6 so soon after delivery.
Thanks in advance!
R
Click to expand...
Click to collapse
The main reason that some users bricked their phone is that they wiped the OS and had a locked bootloader which leaves no possibility ro recover the phone
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Unless something is special about the N6 that I'm not aware of, the OS you update FROM only matters if you're sideloading an OTA file. Flashing factory images, you could be coming from a custom ROM(I just took my old N4 from CM12.1 to stock 4.4 on Sunday).
The current build for VZW is 5.1 LMY47E. I think they are updating to 5.1.1 now(LMY47Z, which seems to be universal now except for maybe T-Mo). I flashed mine from E to Z on Saturday because I bought mine unlocked but it had the VZW build, and I'm on an AT&T MVNO.
gee2012 said:
What carrier do you use?
T-Mobile would be the LYZ28E rom and ATT/USC/International devices would be LMY47Z and Verizon is LMY47E.
Look here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 and here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
If you root, you'll.never get an OTA anyway, sonit doesn't matter which rom you flash aa you can flash any other rom.over it
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Rachel Ambler said:
Still with VZW for now, but, as I said, I didn't purchase the phone from them, I brought it from Google direct so it's carrier agnostic (well, in the US at least!) hence my confusion. The last thing I want to do is flash a ROM that's carrier specific but I don't know which one to take with this being the case.
As for the order, my M8 needed to go in two stages to jump from my old Venom build due to changes with the radio (I think) - hence my question there.
Click to expand...
Click to collapse
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
danarama said:
None of the carrier specific roms will restrict anything, or add branding, so go for whichever.
Click to expand...
Click to collapse
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Rachel Ambler said:
Really? Is there a reason why they exist then? Usually my understanding was that they contained carrier specific items including radios and bloatware.
Click to expand...
Click to collapse
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile adds a kernel fix to allow their wifi calling to work. And that's it...
gee2012 said:
Just flash the LMY47E rom and when its available you get the OTA to update or sideload the OTA from here http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 when its available.
Click to expand...
Click to collapse
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
danarama said:
There's no bloatware on these roms.
Verizon rom includes binaries that make VoLTE work properly on their network where as T-mobile addsna kernel fix to allow their wifi calling to work. And that's it...
Click to expand...
Click to collapse
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Rachel Ambler said:
So what would be the benefit of flashing a Verizon ROM is, for example I should suddenly decide to go to T-Mobile next week given that I didn't purchase the phone from them?
Sorry if these are noob questions but this whole carrier agnostic\yet not agnostic thing has me really wanting to make sure my phone stays as agnostic as it was when it left the factory, bar a VZW Sim nestled inside and a VZW APN entry.
Click to expand...
Click to collapse
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
gee2012 said:
If you want to use T-Mobile in the future you just flash the LYZ28E rom.
Click to expand...
Click to collapse
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
danarama said:
"Well all Nexus 6 used to get the same updates but tmob and red, ..."
Click to expand...
Click to collapse
Great info, very useful.
Rachel Ambler said:
Interesting. So this would leave me to believe then that, should I decide one day to jump carriers, I'd be better off flashing a ROM for that carrier at the appropriate time?
This being the case, why would the phone come with no carrier specific software on board from Google? Wouldn't this mean I might get a degraded service?
Click to expand...
Click to collapse
There were no carrier specific ROMs when Nexus 6 came out. Using any rom on any Nexus and they will all act the same, except you wont get improved volte or wifi calling on those carriers. Their changes will not prove detrimental on other carriers
danarama said:
Well all Nexus 6 used to get the same updates but tmob and red, wanted approval on theirs - and now we know why.
Since google are still sending these updates and they update onto generic builds, they can only use your sim card as the identifier.
If you leave root out of it, the only way you can avoid the vzw update is to manually update to something else (something vzw updates won't work on). Each OTA looks for a specific build to flash on and won't flash on anything else.
If you do accept the vzw update, you'll never get away from them unless you manually flash a full factory rom.
Bringing root back into it, OTA will never flash anyway, so you'll have to either manually flash factory or flash rom.zips in TWRP
Click to expand...
Click to collapse
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Rachel Ambler said:
This is already explaining a lot! So, given that, as I said, I'm not bog standard non-carrier specific 5.0 (and I've yet to even migrate my SIM over) the suggested action would be to download LMY47E 5.1 (as 5.1.1 is not yet out for VZW as they ALWAYS seem to be last to the party) and flash it via TWRP? And I can do that over my LNX07M build?
Click to expand...
Click to collapse
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on xda that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Rachel Ambler said:
Now the murky seas are de-murkyfing!
So go for the VZW build for now with the knowledge and understanding that if I ever decide to bid them a less than fond adieu, I'd be best at that point flash a factory image OR flash another carrier specific ROM once I've chosen the new carrier?
And should I root now, or post the 5.1 flash? I'm guessing post because I'd assuming flashing 5.1 would blow my root away.
I assume I can flash post VZW 5.1 because the boatloader is still all mine and the flash doesn't effect that. Right?
Click to expand...
Click to collapse
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
danarama said:
Depends how you do it.
Google factory images are flashed from a computer using fastboot.
You may be able to find a rom.zip of that version on sea that can be flashed via TWRP.
As long as you aren't flashing an incremental OTA, you can flash over anything. OTA actually patch files not replace them, so they can only be flashed on the rom they are intended for.
Click to expand...
Click to collapse
I'm sorry if that sudden flash of the light coming on in my head just blinded you, but that's what happens when things start to make sense!
OK, so, this all being the case, and that the OTA's are incremental, then in order to go 5.1 with the build from http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 then I WOULD need 5.0.1? Would that work though if I'm on a generic build since, if it's expecting to patch existing VZW files, wouldn't it fail because they're not there? Failing that I'd need to find a flashable 5.1 for VZW (if one even exists)?
endlessryan said:
Why not go with a custom rom like chroma? Get 5.1.1 now and personally it works really well.
Click to expand...
Click to collapse
But it wouldn't have the VoLTE improvements, etc, right? Besides, right now I'd like to stay as stock as possible as it's not just my phone I'm working on, both myself and my wife got one at the same time and I know she will most definitely NOT want anything other than stock.
According to this page
https://support.t-mobile.com/docs/DOC-18109#update_download
T-Mobile began rolling out 6.0 on October 5th. It states in the instructions to perform the update manually is essentially performing the android check for updates however I get no prompt to download the OTA.
Has anyone found a way to force the update? Possibly resetting the device?
Thanks!
Wait for the OTA, sideload when someone gets the link or flash the entire image (lose everything)...
Keep pressing that update button, but it does nothing ..
I'm literally going to beat a dead horse but why, are even Google's devices subjected to this ridiculous update process? If someone wants the OTA then they should be able to get it..
I am rooted on TMO and did a manual update to LYZ28K a while back. I clicked on Check for System Update just for kicks and it downloaded a 23.2 MB file. Any idea what that is?
JimSmith94 said:
I am rooted on TMO and did a manual update to LYZ28K a while back. I clicked on Check for System Update just for kicks and it downloaded a 23.2 MB file. Any idea what that is?
Click to expand...
Click to collapse
LYZ28M An update to Android 5.1.1
steve841 said:
Wait for the OTA, sideload when someone gets the link or flash the entire image (lose everything)...
Keep pressing that update button, but it does nothing ..
Click to expand...
Click to collapse
There are methods you can use when manually flashing to not lose data. (Don't flash userdata.img) be it through fastboot cmd directly, or through the use of a toolkit like Wugs.
OP, save yourself the headache and just download the update and fastboot it. It's a unified image so there is no need to wait for a "specific" version.
Peylix said:
There are methods you can use when manually flashing to not lose data. (Don't flash userdata.img) be it through fastboot cmd directly, or through the use of a toolkit like Wugs.
OP, save yourself the headache and just download the update and fastboot it. It's a unified image so there is no need to wait for a "specific" version.
Click to expand...
Click to collapse
Am I going to lose the ability to get future OTAs if I go this route? I've got an unlocked bootloader.... But not rooted and completely stock ROM.
slopokdave said:
Am I going to lose the ability to get future OTAs if I go this route? I've got an unlocked bootloader.... But not rooted and completely stock ROM.
Click to expand...
Click to collapse
You can still get OTA's as long as you're not rooted. Unlocked bootloader doesn't matter. Anyways, even if you did root, you can just manually flash the next update the same way. Takes less than 20 minutes to do.
Peylix said:
You can still get OTA's as long as you're not rooted. Unlocked bootloader doesn't matter. Anyways, even if you did root, you can just manually flash the next update the same way. Takes less than 20 minutes to do.
Click to expand...
Click to collapse
Thanks this worked perfect!
JoshRH said:
I'm literally going to beat a dead horse but why, are even Google's devices subjected to this ridiculous update process? If someone wants the OTA then they should be able to get it..
Click to expand...
Click to collapse
We do, it's called the factory images that google provides, we get the updates immediately (had 6.0 on release day), if you want to "wait" then it's only on you, the means are out there to get the updates right away, otherwise, gotta wait for the carriers. Android isn't and doesn't seem like it'll be like the iphone, independent from carriers as far as updates. Unless Google grows some nads and lays their foot down, this is how it will always be sadly.....once again, unless you just get the update and do it yourself like maybe 80% of the community here.
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Click to expand...
Click to collapse
Nope, you don't have to erase your data to sideload an update (keep in mind that sideloading an OTA isn't possible if you have root, custom recovery or custom kernel). You don't even have to erase any data (provided that you don't need to unlock your bootloader prior to flashing) if you flash a factory image (even though it's nice to clean out the old system once in a while).
This was just a tangent, my real reason for replying follows:
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse
Of course they can roll out the OTA to everybody at once, but they don't want to (and I agree). Check out this article (2 years old, yes, but the base principle still stands):
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015.
Click to expand...
Click to collapse
You don't have to wait weeks. You have to potentially wait days, sometimes it is hours. Soon someone will snag the OTA url, if they haven't already, and then you can use ADB to sideload it without needing to wipe anything.
I haven't been following too closely, but I actually haven't seen anyone that has stated they have actually received 6.0 OTA yet. Some people posting they were, but they were getting one of the security fixes. Maybe they actually haven't pushed the OTA to the Nexus 6 yet for some reason?
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse
It also has nothing with Google's ability to roll updates out to all of the Nexus owners. It is how they decide to stagger their updates out to people. They do this to make sure everything goes smoothly. If they put an update out that causes some sort of major problem, it would suck if it was in the hands of every single user, rather than just 1%.
The only update I received today was LYZ28M sadly. Not sure why they don't just have an app where people can download Nexus updates any time instead of OTA.
I got all the important stuff backed on Drive and most of the time I get all back even without backing it up
JoshRH said:
While II respect the fact that the majority of the XDA community is willing and capable to erase all data and side load 6.0 this isn't something that should be accepted in 2015. I'm not asking for Google to be like Apple, but for a Nexus device, a device designed to offer the latest and most up to date version of android, to be forced to wait for weeks for a proper OTA update is just ridiculous. I simply laugh at the android 6.0 articles that the tech blogs are releasing when 99% of the user base doesn't have access to the software.
Like I said I know that this has been discussed time and again, it's just hard to believe that a company as mature and advanced as Google, can't get an OTA rolling out to all 5 million Nexus 6 owners when Apple does in fact provide the latest software, on day one to multiple hundreds of million users. It's honestly quite gross.
Click to expand...
Click to collapse
The Razer website doesn't have factory images available STILL for the September update. I'm not interested in going back to stock, taking the update, and hoping root will still work. In the past, these firmware images seem like they were available a week after release of the OTA.
Is there another way for me to update on this device via flashing or fastboot, maintaining root and my data, or do I just keep waiting for firmware images here:
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Quantumrabbit said:
The Razer website doesn't have factory images available STILL for the September update. I'm not interested in going back to stock, taking the update, and hoping root will still work. In the past, these firmware images seem like they were available a week after release of the OTA.
Is there another way for me to update on this device via flashing or fastboot, maintaining root and my data, or do I just keep waiting for firmware images here:
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Click to expand...
Click to collapse
You may be waiting a while. If you're already rooted why not back everything up with something like Titanium backup and just flash latest firmware take the update, root, and then restore everything. I've done it so many times. This phone is so developer friendly I can't understand why there isn't more development....sad actually
JDBarlow said:
You may be waiting a while. If you're already rooted why not back everything up with something like Titanium backup and just flash latest firmware take the update, root, and then restore everything. I've done it so many times. This phone is so developer friendly I can't understand why there isn't more development....sad actually
Click to expand...
Click to collapse
The process is so much easier just to fastboot flash all the images.
I'm actually back on my Essential Phone PH-1 now because the 2+ year old phone got Answered 10 day of release and has been updated to October security updates. I don't know that I can live with the pain of manual backups and restores when basic flash updates should be available... As to that the pathetic manufacturer support from Razer... Not an attractive daily use device for me.