Related
I've been an Android user for a while (Nexus One, and now Galaxy Nexus), but am quite tired of Samsung's tyrannical rule over that little version number in "About Phone".
So, I've got my Samsung Galaxy Nexus (on 4.0.1, ERGH!), and I'm on Bell Canada (Alberta, specifically), and I don't believe I have LTE capability (I do have HSPA+...). As for computer, I run Windows 7 x64.
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
These are the questions (and confirmations) I have, as I haven't been able to find any FAQ or thread that covers them...
1. Is this the ROM I should be downloading?
2. Is this the tool I should be using to unlock the BootLoader safely and properly?
3. Is a relocked BootLoader traceable by the carrier/manufacturer, in the event that I need to return it?
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Any help is appreciated... I'm a bit of a tech geek but I've never even tampered with a phone before, so this is all new to me. Thanks to anyone brave enough to help me! ^^
PS: Sorry if this is in the wrong section; this was the most fitting, I thought.
I used that toolkit and that update and I can confirm that they both work
That is NOT the ROM for you, you have a GSM device. H+ is not LTE.
The GSM and CDMA devices are markedly different.
Try to read in this thread... as well as efrant posts, you will get your answer !
N.B. most important thing is read and read and read... before doing anything..
http://forum.xda-developers.com/showthread.php?t=1391881
Zackster said:
I've been an Android user for a while (Nexus One, and now Galaxy Nexus), but am quite tired of Samsung's tyrannical rule over that little version number in "About Phone".
So, I've got my Samsung Galaxy Nexus (on 4.0.1, ERGH!), and I'm on Bell Canada (Alberta, specifically), and I don't believe I have LTE capability (I do have HSPA+...). As for computer, I run Windows 7 x64.
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
These are the questions (and confirmations) I have, as I haven't been able to find any FAQ or thread that covers them...
1. Is this the ROM I should be downloading?
2. Is this the tool I should be using to unlock the BootLoader safely and properly?
3. Is a relocked BootLoader traceable by the carrier/manufacturer, in the event that I need to return it?
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Any help is appreciated... I'm a bit of a tech geek but I've never even tampered with a phone before, so this is all new to me. Thanks to anyone brave enough to help me! ^^
PS: Sorry if this is in the wrong section; this was the most fitting, I thought.
Click to expand...
Click to collapse
Argh! Didn't realize CMDA was the LTE version.
Thanks to everyone! Will read through that thread tonight and hopefully all is well.
Zackster said:
[snip]
On that note, I'd like to unlock the BootLoader and flash 4.0.4 (no root, if possible), or at least be able to receive updates directly from Google.
Click to expand...
Click to collapse
There is no official 4.0.4 ROM for the GSM version.The latest is 4.0.2.
By the way, you can still update your version (yakjuux) to 4.0.2 without flashing yakju, by following the instructions here.
Zackster said:
4. What is the best way to back up all of the App data on my phone? (High scores, calendar settings, user/password combinations, etc.) Or is this even possible? (I think things like contacts, phone settings, calendar events, and Apps will sync from the cloud... right?)
Click to expand...
Click to collapse
Best way is to root your device by following the instructions here, and then install Titanium Backup from the market. TB will do what you are asking.
efrant said:
There is no official 4.0.4 ROM for the GSM version.The latest is 4.0.2.
Click to expand...
Click to collapse
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
efrant said:
By the way, you can still update your version (yakjuux) to 4.0.2 without flashing yakju, by following the instructions here.
Click to expand...
Click to collapse
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
efrant said:
Best way is to root your device by following the instructions here, and then install Titanium Backup from the market. TB will do what you are asking.
Click to expand...
Click to collapse
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.
http://forum.xda-developers.com/showthread.php?t=1454314 That there is a little something-something I happened upon when I was growing entirely to impatient waiting for the 4.0.2 update.
It'll give you instructions on what you need to do for everything. Just make sure you select GSM/HSPA+ first.
My gift, from one Alberta boy to another!
Zackster said:
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.
Click to expand...
Click to collapse
There is no 4.0.4 source. There is a rumored leak of the 4.0.4 LTE version (no idea of the condition of the version), but the only source that is available is 4.0.3 (it's in the AOSP). The latest version on any GN is 4.0.2 (GSM or LTE/CDMA).
It's kind of disappointing to see the GN taking so long to update, but the Nexus S is apparently taking ages to get onto ICS. I doubt we get another update until the Nexus S gets 100% updated to ICS.
Zackster said:
Hmm... does this mean that no 4.0.4 version will work on the GSM version? Or would it be ridden full of bugs, or what?
Click to expand...
Click to collapse
There are custom ROMs available based on 4.0.3. There are NO 4.0.4 ROMs for GSM.
Zackster said:
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Click to expand...
Click to collapse
I don't use tool kits, but yes, you need to install the drivers. You do not need to unlock the bootloader.
Zackster said:
Doesn't rooting require wiping the device, though? I'm interested in backing it up pre-4.0.4.
Click to expand...
Click to collapse
If you would have looked at the link I posted , you would have answered your question. No, rooting does not require wiping. Unlocking the bootloader wipes.
Sent from my Galaxy Nexus using Tapatalk
Zackster said:
[snip]
Still requires setting up the toolkit to get the drivers and bootloader unlocked, and to get fastboot working though, it seems, yes?
Click to expand...
Click to collapse
I've found that these drivers work the best.
krblake13 said:
http://forum.xda-developers.com/showthread.php?t=1454314 That there is a little something-something I happened upon when I was growing entirely to impatient waiting for the 4.0.2 update.
It'll give you instructions on what you need to do for everything. Just make sure you select GSM/HSPA+ first.
My gift, from one Alberta boy to another!
Click to expand...
Click to collapse
Great! I'll look into this! Good to know it's worked for someone else in this situation.
descendency said:
There is no 4.0.4 source. There is a rumored leak of the 4.0.4 LTE version (no idea of the condition of the version), but the only source that is available is 4.0.3 (it's in the AOSP). The latest version on any GN is 4.0.2 (GSM or LTE/CDMA).
It's kind of disappointing to see the GN taking so long to update, but the Nexus S is apparently taking ages to get onto ICS. I doubt we get another update until the Nexus S gets 100% updated to ICS.
Click to expand...
Click to collapse
Hmm... disappointing, for sure. I had found this MoDaCo ROM, which is why I asked.
efrant said:
There are custom ROMs available based on 4.0.3. There are NO 4.0.4 ROMs for GSM.
I don't use tool kits, but yes, you need to install the drivers. You do not need to unlock the bootloader.
If you would have looked at the link I posted , you would have answered your question. No, rooting does not require wiping. Unlocking the bootloader wipes.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Argh, I keep getting rooting and the bootloader confused. Sorry about that.
efrant said:
I've found that these drivers work the best.
Click to expand...
Click to collapse
Excellent, I'll give these a try.
Hi, I have yakjuxw and I want to replace it with yakju. I have Ubuntu, so i found this toolkit but I don't know what I need to do for doing that. I've already installed the toolkit. In the first i choose my device
G. GSM Galaxy Nexus [maguro], but then? I have to follow ALL this five points for have a yakju or I need only the last (n 5)?
1. Unlock the Bootloader
2. Flash ClockworkMod Recovery
3. Root the Device
4. Lock the Bootloader
5. Flash Google Factory Image
0. Exit
Thanks
TheSignal said:
Hi, I have yakjuxw and I want to replace it with yakju. I have Ubuntu, so i found this toolkit but I don't know what I need to do for doing that. I've already installed the toolkit. In the first i choose my device
G. GSM Galaxy Nexus [maguro], but then? I have to follow ALL this five points for have a yakju or I need only the last (n 5)?
1. Unlock the Bootloader
2. Flash ClockworkMod Recovery
3. Root the Device
4. Lock the Bootloader
5. Flash Google Factory Image
0. Exit
Thanks
Click to expand...
Click to collapse
If you use a toolkit, you won't learn anything. Use this method, just skip the part about drivers.
This makes me sick. I'm sorry.
Sent from my i9250
Jesus Christ man... you're running Linux and you want a toolkit to root your Android phone? What the hell has this world come to.
efrant said:
If you use a toolkit, you won't learn anything. Use this method, just skip the part about drivers.
Click to expand...
Click to collapse
Do this, please.
martonikaj said:
Jesus Christ man... you're running Linux and you want a toolkit to root your Android phone? What the hell has this world come to.
Do this, please.
Click to expand...
Click to collapse
I've never had an Android phone until yesterday, I don't know how do they work. Get off your high horse man
TheSignal said:
I've never had an Android phone until yesterday, I don't know how do they work. Get off your high horse man
Click to expand...
Click to collapse
In that case, read and learn. Otherwise, you'll just be back here in a panic posting a thread asking for help with your soft brick. Too many of the "my phone's broken, what do I do?" threads start with "so, I used this toolkit". That's why so many people are anti-toolkit at this point.
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
jahames said:
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
Click to expand...
Click to collapse
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
StuMcBill said:
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
Click to expand...
Click to collapse
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
jahames said:
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
Click to expand...
Click to collapse
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
StuMcBill said:
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
Click to expand...
Click to collapse
Was working with the 4.4.2 image. Going to give the 4.4 a shot now
Same thing with 4.4...still stuck with the flo bootloader
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
jahames said:
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
Click to expand...
Click to collapse
You flashed a recovery for flo. Flash one for deb.
Edit:
http://techerrata.com/browse/twrp2/deb
Reasonably sure I had a deb recovery, but apparently redownloading and reflashing the CWM image did the trick. Thanks!
if you ever have problems try nexus root toolkit. It works wonders if you ever severely mess up any nexus device.
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
same issue
Richieboy67 said:
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
It is here
http://www.wugfresh.com/
It is a toolkit that makes these things very easy. I have used this many times and have never had any issues with it.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
LinearEquation said:
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Richieboy67 said:
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Click to expand...
Click to collapse
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
LinearEquation said:
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
Click to expand...
Click to collapse
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Richieboy67 said:
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Click to expand...
Click to collapse
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
LinearEquation said:
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
Click to expand...
Click to collapse
While not disastrous, I kind of know what you mean, I started with Wug's (and it is a great toolkit), but once I flashed my own kernel (I used francos app to autoflash so did not have to use recovery or fastboot), I did not realize that by using Wug's a week later that it would flash over that kernel to run those commands and NOT replace francos (I found I was back on stock), lucky by then I had learned enough to recover and no damage was done, but it does point out that my reliance had caused me more work and a bit of worry in the long run.
Still Wug's NRT is a great toolkit...but it should be used as a tool, not a replacement for knowing what to do without it.
Hey guys,I was wondering if theres any development blogs ,sites, that may get us an indication about what's going on with the custom recovery?
I'm looking for it now and then but all I get is antique topics about how the phone is just out to market and we should give it a month to see custom roms/recoveries .
subwoffer13 said:
Hey guys,I was wondering if theres any development blogs ,sites, that may get us an indication about what's going on with the custom recovery?
I'm looking for it now and then but all I get is antique topics about how the phone is just out to market and we should give it a month to see custom roms/recoveries .
Click to expand...
Click to collapse
T-Mobile is the only one with the bootloader unlocked so they have full access to using recovery and roms, I don't know if other variants are using a recovery yet since I am a vs985 (verizon) user I don't watch them closely
For vs985 we can't get into fastboot mode because verizon decided to remove or disable it, so we can't use tethered recovery (temporarily booting the recovery from adb shell)
I can tell you that Recovery's aren't hard to make at all. its just we don't have a way to use them right now &
Roms will quickly follow after Recovery's are able to be flashed
bunchies said:
T-Mobile is the only one with the bootloader unlocked so they have full access to using recovery and roms, I don't know if other variants are using a recovery yet since I am a vs985 (verizon) user I don't watch them closely
For vs985 we can't get into fastboot mode because verizon decided to remove or disable it, so we can't use tethered recovery (temporarily booting the recovery from adb shell)
I can tell you that Recovery's aren't hard to make at all. its just we don't have a way to use them right now &
Roms will quickly follow after Recovery's are able to be flashed
Click to expand...
Click to collapse
Any personal thoughts /guesses about how long will it take?
I'm really excited about it , because when I bought my g3 I left my note 2 for experiments, and hell isn't the name for what my oldie note went through.
My point is that I finally learned how to install custom EVERYTHING. from kernel to build.prop,and my hands are itchy to do the same on my g3
Unfortunately and until the bootloader is unlocked, we have to patiently wait for our great devs to unlock this retarded bootloader. It may take a couple of days, it may take a month, it may never happen. We just have to wait. Oh, and friendly advice: never ask for an ETA on xda
Ferindel said:
Unfortunately and until the bootloader is unlocked, we have to patiently wait for ou great devs to unlock this retarded bootloader. It may take a couple of days, it may take a month, it may never happen. We just have to wait. Oh, and friendly advice: never ask for an ETA on xda
Click to expand...
Click to collapse
Very true , I'm going to get a nexus as I'm not completely convinced an unlock will come and even if it may be awhile.
dabug123 said:
Very true , I'm going to get a nexus as I'm not completely convinced an unlock will come and even if it may be awhile.
Click to expand...
Click to collapse
jcase already found a Loki-like exploit but won't release it till he is sure a complete unlock is impossible. So, we will have an unlock and if not, then we will 100% have the exploit.
Sent from my LG-D852 using Tapatalk
I hope that it wont take long till they find a way to unlock the bootloader. The stock rom is loaded with a lot of bloatware and lg apps that i never intend to use. I want to see how fast the g3 is on a cm 11!
Helloworld294 said:
jcase already found a Loki-like exploit but won't release it till he is sure a complete unlock is impossible. So, we will have an unlock and if not, then we will 100% have the exploit.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Where did you find this out at? If true it's the best news I've heard in months!
katsika said:
I hope that it wont take long till they find a way to unlock the bootloader. The stock rom is loaded with a lot of bloatware and lg apps that i never intend to use. I want to see how fast the g3 is on a cm 11!
Click to expand...
Click to collapse
i just installed some mod ( forgot the name , something liquid 4.4.4 ) on note 2 , and i didnt think that a phone , especially an old one, could be that quick and smooth .
i dying to do the same with my lg
subwoffer13 said:
i just installed some mod ( forgot the name , something liquid 4.4.4 ) on note 2 , and i didnt think that a phone , especially an old one, could be that quick and smooth .
i dying to do the same with my lg
Click to expand...
Click to collapse
Abit old maybe. But its not ainchent...2 MB ram and quad core cpu.. Its pretty good specs still.
Helloworld294 said:
jcase already found a Loki-like exploit but won't release it till he is sure a complete unlock is impossible. So, we will have an unlock and if not, then we will 100% have the exploit.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Please link us to where this was talked about great news, cheers.
skeamznz said:
Please link us to where this was talked about great news, cheers.
Click to expand...
Click to collapse
no news, this are older "news". you can find them in at&t lg3 forum section with forum search.
be patient, the devs don't like to get stressed and the whole xda drama about unlock.
jcase already said he is able to run custom images but time is the problem to release it. when everyone is stressing them, they will lose interest to unlock under pressure.
when it's ready you will know it. until release be quiet please. thanks.
There's the "news"
http://forum.xda-developers.com/showthread.php?p=55238605
Cheers
Sent from my LG-D852 using Tapatalk
Hi all,
First at all, sorry for my bad English. I'm trying to install Android M's factory image on my Nexus 7, but I'm very lost. Someone could explain me the process step by step? My device isn't root.
Thank you very much.
Use Wug's Toolkit.
^Pretty dangerous recommending a toolkit to someone who has no idea what they're doing.
It'll likely work fine considering it's pretty much a fastboot gui BUT if something goes wrong hes ****ed since he doesn't really know how it works.
OP learn how to use fastboot and flash the factory images there are many guides all over the forums it's very easy. Or wait for the ota.
dangerous recommending NRT ? It's instructions could not be clearer If someone can't properly use it then they can't read simple instructions or understand English
yosmokinman said:
^Pretty dangerous recommending a toolkit to someone who has no idea what they're doing.
It'll likely work fine considering it's pretty much a fastboot gui BUT if something goes wrong hes ****ed since he doesn't really know how it works.
OP learn how to use fastboot and flash the factory images there are many guides all over the forums it's very easy. Or wait for the ota.
Click to expand...
Click to collapse
There is nothing as simply as Wug's toolkit for newcomers so..
might be better off instructing the guy to research the whole entire Android scene before you tell him to toolkit up lol. Google , some research would probably be his best bet
Sent from my Nexus 7 using Tapatalk
Was able!to flsh 6.0. So far so good.
Sent from my Nexus 7 using XDA Premium HD app
Shouldn't N7 2013 running 5.1.1 update to 6.0 with/by OTA? Asking because mine didn't... even with manual check for updates it's reporting no updates available.
flashed! Works great!
strumf666 said:
Shouldn't N7 2013 running 5.1.1 update to 6.0 with/by OTA? Asking because mine didn't... even with manual check for updates it's reporting no updates available.
Click to expand...
Click to collapse
Not yet. I had a OTA update to LMY48T last week. The OTA to 6.0 (from LMY48T) has not appeared yet. Therefore patience - it should happen soon.
Trev
Besides the derp, any issues with video freezing? I reverted back to 5.1.1 as no one seemed to have a clue as to what was causing this.
aiiee said:
Besides the derp, any issues with video freezing? I reverted back to 5.1.1 as no one seemed to have a clue as to what was causing this.
Click to expand...
Click to collapse
Was this on stock kernel or elemental? Video works great for me on stock kernel.
Sent from my Nexus 5 using Tapatalk
tegodwin said:
Not yet. I had a OTA update to LMY48T last week. The OTA to 6.0 (from LMY48T) has not appeared yet. Therefore patience - it should happen soon.
Trev
Click to expand...
Click to collapse
Finally got the OTA upgrade yday