I woke up this morning to a 95mb Android system OTA update. I cant find any mention of it on the T-Mobile support site.
I am currently on H81120o the latest build according to T-Mobile.
I imagine it's probably just security updates...
Anyone have any knowledge of this update and it's contents?
TIA
What's the Software version after the Update?
Did you find anything different from 20o?
I grabbed the file.
It looks like a radio update.
https://www.androidfilehost.com/?fid=312968873555003197
mingkee said:
I grabbed the file.
It looks like a radio update.
https://www.androidfilehost.com/?fid=312968873555003197
Click to expand...
Click to collapse
I have been facing constant signal drops on 20o. So may be this update fixes it.
Thanks for sharing.
I am new to LG. Can you explain how can I flash this update?
Edit : Should I use LGUP's FOTA Upgrade option?
Flash it with Flashfire
Check the bottom two.
Root is there
It's still 20o
mingkee said:
Flash it with Flashfire
Check the bottom two.
Root is there
Click to expand...
Click to collapse
Well I used the LGUP's FOTA Upgrade option and it worked.
It's still 20o
Click to expand...
Click to collapse
That's strange. It shows 20p on my device.
But the Network issue is still there. LTE Signal drops every other minute.
arnabJ said:
Well I used the LGUP's FOTA Upgrade option and it worked.
That's strange. It shows 20p on my device.
But the Network issue is still there. LTE Signal drops every other minute.
Click to expand...
Click to collapse
Is root wiped?
mingkee said:
Is root wiped?
Click to expand...
Click to collapse
I didn't had root so I can't say but if root is present then Update won't install to the best of my knowledge.
Do you use T-Mobile connection on this device or unlocked it to use with some other carrier?
I use it here in India. 2G and 3G carriers work perfectly but LTE carrier causing issues inside home.
For some reason Band 5 (850) is failing.
Any help will be appreciated.
Flashed update with LGUP FOTA.
Android Security Patch Level
2016-09-01
Software Version
h81120p
phineous said:
Flashed update with LGUP FOTA.
Android Security Patch Level
2016-09-01
Software Version
h81120p
Click to expand...
Click to collapse
Thanks phineous!
Did you have root before flashing and do you still after?
AndroidUzer said:
Thanks phineous!
Did you have root before flashing and do you still after?
Click to expand...
Click to collapse
No, flashed over a fresh install of H81120o. I'm trying to root now.
Rooted fine flashing phh's SuperUser hidesu r266 in TWRP.
Passes SafteyNet check.
Done.
Unrooted first using 20o kdz file and flashed with LGUP, let it finished bootup and flashed again with update.zip.
You can use fastboot boot TWRP to enter TWRP and root again.
I was unable to apply the update to a rooted phone. Does anyone know how to accomplish this without unrooting the phone?
lancemoreland said:
I was unable to apply the update to a rooted phone. Does anyone know how to accomplish this without unrooting the phone?
Click to expand...
Click to collapse
Haha. I just rooted this phone for the first time yesterday. Figures. Is it recommended I take this update? Can someone explain in n00bish terms how I should go about this? Here's my very basic understanding:
Boot into TWRP. Wipe and then install 20o kdz with TWRP. Install update with TWRP (where do I get this?). Flash SuperSU with TWRP. Install ROM of my choice. Dearie me this is mildly annoying.
unrooting is very simple. its within the settings of the Supersu app. For an update to work i i believe you must be on stock recovery as well, which can be flashed in twrp.
I unrooted and used LGUP to upgrade and install the stock recovery and still could not get it to install. When I pressed the button to reboot and install it would never reboot. Looks like I would need to do a refurbish to get it to install which would wipe my phone. Maybe someone like @MicroMod777 could make a TWRP flashable zip for the update.
Got the update today. Now on H81120p. Is there a change log?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H811 using XDA-Developers mobile app
arnabJ said:
I didn't had root so I can't say but if root is present then Update won't install to the best of my knowledge.
Do you use T-Mobile connection on this device or unlocked it to use with some other carrier?
I use it here in India. 2G and 3G carriers work perfectly but LTE carrier causing issues inside home.
For some reason Band 5 (850) is failing.
Any help will be appreciated.
Click to expand...
Click to collapse
How do you use 3G metwork.. Mine only goes 4G and 2G never seen 3G i think 3G is dosabled. Am not on tmobile either. But on my previous phone G2 i had 3G.???
raptorddd said:
How do you use 3G metwork.. Mine only goes 4G and 2G never seen 3G i think 3G is dosabled. Am not on tmobile either. But on my previous phone G2 i had 3G.???
Click to expand...
Click to collapse
My carrier is 4G only. So, I face a lot of issue. Most of the time there is no network on the ground floor. And if there is its unstable.
There is no issue when I am higher levels in buildings or outside. But my room is at ground floor and I have no network there. The phone becomes useless when I am at home.
arnabJ said:
My carrier is 4G only. So, I face a lot of issue. Most of the time there is no network on the ground floor. And if there is its unstable.
There is no issue when I am higher levels in buildings or outside. But my room is at ground floor and I have no network there. The phone becomes useless when I am at home.
Click to expand...
Click to collapse
well i have 4G but sometimes signal is gone so it doesnt go into 3G. so i read we dont have 3G on our phones h811.
Related
resresize piok here is exactly what i did to make Stock rooted NAE Rom working with DATA and WIFI
(I USED ODIN 3 TO FLASH PHILZ RECOVERY TAR)
FULL WIPE
NEED TO BE ON MK2
flash MK2 STOCK ROOTED
FOR SOME REASON IT ONLY WORKS WHEN I FLASH TRI FORCE ROM...
INSTALL TRI FORCE ROM 5.4 WITH CURRENT PHILZ TOUCH RECOVERY
LET IT BOOT
AS SOON AS IT DOES REBOOT INTO RECOVERY
INSTALL NAE ROM...NO WIPE...REBOOT SYSTEM....IT SHOULD GET STUCK AT SPRINT BOOT ANIM....ALL GOOD....NOW....
REBOOT TO DOWNLOAD MODE
FLASH NAE MODEM (FIRMWARE) UNCHECK AUTO REBOOT AND F. RESET
AFTER IT SAYS PASS....REBOOT PHONE USING POWER BUTTON....
SHOULD SAY ANDROID IS UPGRADING ...OPTIMIZING APPS .....ONCE ITS DONE.. UR GOOD
POSTED SCREEN SHOT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which bootloader are you on? MF9, MJA, MK2?
Sent from my Nexus 5 using Tapatalk
MK2
optimummind said:
Which bootloader are you on? MF9, MJA, MK2?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
MK2
deeja303y said:
MK2
Click to expand...
Click to collapse
How can I tell which bootloader I have?
You can use an app like Root Checker or Phone Info from the Playstore.
does this knox void?
legasus233 said:
How can I tell which bootloader I have?
Click to expand...
Click to collapse
You can do that from terminal emulator by entering this command getprop ro.bootloader
Sent from my SPH-L720 using Tapatalk
SayWhat10 said:
does this knox void?
Click to expand...
Click to collapse
Flashing the custom recovery will trip KNOX.
This method worked for me on the MF9 bootloader.
Wifi and data (LTE at least) are working.
Only thing is that I'm constantly getting a "Sprint ID stopped working" popup notification.
Update:
Apparently factory reset/wipe data breaks wifi
That's not good
samjam keep us posted. Were you able to get wifi restored?
Data connection still holding?
samjam91 said:
This method worked for me on the MF9 bootloader.
Wifi and data (LTE at least) are working.
Only thing is that I'm constantly getting a "Sprint ID stopped working" popup notification.
Update:
Apparently factory reset/wipe data breaks wifi
Click to expand...
Click to collapse
Turns out wifi wasn't working because my router was on the fritz. I kept getting force closes using the NAE rom from Uknownforce after I restored with TiBu, so I had to flash back to MK2, at least until a newer NAE rom comes out. Still on NAE firmware with MF9 bootloader. Everything is working fine for now.
dumb question
samjam91 said:
Turns out wifi wasn't working because my router was on the fritz. I kept getting force closes using the NAE rom from Uknownforce after I restored with TiBu, so I had to flash back to MK2, at least until a newer NAE rom comes out. Still on NAE firmware with MF9 bootloader. Everything is working fine for now.
Click to expand...
Click to collapse
Anyway I can tell what my current bootloader is ? I am lost and I realize this is a dumb q just lost my wifi is not working i see all these fixes but of course lost ...
kujanme said:
Anyway I can tell what my current bootloader is ? I am lost and I realize this is a dumb q just lost my wifi is not working i see all these fixes but of course lost ...
Click to expand...
Click to collapse
Either in an adb shell or terminal emulator, type this:
Code:
getprop ro.bootloader
It should then return your current bootloader. If it's MJA/MK2/NAE you CANNOT downgrade it, because of KNOX.
Hey guys, I have an XT1064 US GSM Moto G.
I followed the tutorial here and flashed the appropriate image to restore the phone to stock: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now, my wifi no longer works no matter what I do.
I have tried deleting the wpa_supplicant.conf file, flashing a different kernel, rebooting without the sim, and wifi will not turn on no matter what. As soon as I slide it on the button snaps back to the off position
Some help would be very much appreciated!! Thanks!
EDIT: Also, every line of flashing has returned [OKAY], and I've run the phone with stock recovery, CWM, and TWRP and no difference
Is it possible I have to relock my bootloader? I don't see how that would affect it but im not an expert
I have the exact same problem... But my device is a XT1069.
Still waiting for a solution... :/
Bl00dyMurd3r said:
Hey guys, I have an XT1064 US GSM Moto G.
I followed the tutorial here and flashed the appropriate image to restore the phone to stock: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now, my wifi no longer works no matter what I do.
I have tried deleting the wpa_supplicant.conf file, flashing a different kernel, rebooting without the sim, and wifi will not turn on no matter what. As soon as I slide it on the button snaps back to the off position
Some help would be very much appreciated!! Thanks!
EDIT: Also, every line of flashing has returned [OKAY], and I've run the phone with stock recovery, CWM, and TWRP and no difference
Is it possible I have to relock my bootloader? I don't see how that would affect it but im not an expert
Click to expand...
Click to collapse
Did you download your XT1064 firmware from here:
http://sbf.droid-developers.org/phone.php?device=36
We are not supposed to install XT1069 firmware on XT1064
rafaelbrunner said:
I have the exact same problem... But my device is a XT1069.
Still waiting for a solution... :/
Click to expand...
Click to collapse
me too xt1068
Thanks for the link, but i did not flash XT1069 firmware, I followed the guide steps to flash "Blur_Version.21.11.17.titan_retuaws.retuaws.en.US" as I have the US gsm model
This will only happen if you updated the phone with latest OTA, you can't downgrade the bootloader, if you apply the latest OTA the problem should be solved.
MiguelPT said:
This will only happen if you updated the phone with latest OTA, you can't downgrade the bootloader, if you apply the latest OTA the problem should be solved.
Click to expand...
Click to collapse
I tried applying the update from this thread from the stock recovery: http://forum.xda-developers.com/moto-g-2014/general/ota-update-t2880432
The recovery starts to verify the package and then I get "Installation aborted."
It does this with both locked and unlocked bootloader
Any other help would be great, thanks!
Bl00dyMurd3r said:
I tried applying the update from this thread from the stock recovery: http://forum.xda-developers.com/moto-g-2014/general/ota-update-t2880432
The recovery starts to verify the package and then I get "Installation aborted."
It does this with both locked and unlocked bootloader
Any other help would be great, thanks!
Click to expand...
Click to collapse
According to Q18 from this page you need to select full unroot option from the Super Su:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then follow the "[Restore to Stock][XT1068][All Dual Sim Model][4.4.4][Lock Bootloader]" and use XT1064 firmware just to see if your wifi works or not.
pleomaxell said:
According to Q18 from this page you need to select full unroot option from the Super Su:
Then follow the "[Restore to Stock][XT1068][All Dual Sim Model][4.4.4][Lock Bootloader]" and use XT1064 firmware just to see if your wifi works or not.
Click to expand...
Click to collapse
Thanks, I'll give it a shot!
Well, tried that and no luck. This is my 3rd android device and I've never heard of Wifi being borked like this
Bl00dyMurd3r said:
Well, tried that and no luck. This is my 3rd android device and I've never heard of Wifi being borked like this
Click to expand...
Click to collapse
Sorry, I don't know what to suggest, it looks like another user was facing a similar problem and no one could provide a solution to him too.
Can't you return the phone and get it replaced?
pleomaxell said:
Sorry, I don't know what to suggest, it looks like another user was facing a similar problem and no one could provide a solution to him too.
Can't you return the phone and get it replaced?
Click to expand...
Click to collapse
It looks like I'll have to. Amazon customer service is top notch, but I'll have to flash over the unlocked bootloader warning and then relock it, hopefully all bases will be covered
Bl00dyMurd3r said:
It looks like I'll have to. Amazon customer service is top notch, but I'll have to flash over the unlocked bootloader warning and then relock it, hopefully all bases will be covered
Click to expand...
Click to collapse
I had no success in re-locking my device's bootloader...
Did you have any luck with that?
rafaelbrunner said:
I had no success in re-locking my device's bootloader...
Did you have any luck with that?
Click to expand...
Click to collapse
Yes, on my 1064 i issued these commands while on the bootloader:
mfastboot.exe oem lock begin
mfastboot.exe oem lock
It returned a [FAILED] in cmd, but after reboot the bootloader reported it was indeed locked. The unlocked bootloader warning still appeared however, but the logo fix could probably be applied prior to re-locking
Bl00dyMurd3r said:
Yes, on my 1064 i issued these commands while on the bootloader:
mfastboot.exe oem lock begin
mfastboot.exe oem lock
It returned a [FAILED] in cmd, but after reboot the bootloader reported it was indeed locked. The unlocked bootloader warning still appeared however, but the logo fix could probably be applied prior to re-locking
Click to expand...
Click to collapse
me the saame....i think there isnt solution.....:crying:
WIFI fix
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
linasmit said:
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
Click to expand...
Click to collapse
IT WORKS!!! Tested here on XT1069!
Thank you once is not enough... Thanks a MILLION, brother! :good:
linasmit said:
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
Click to expand...
Click to collapse
Oh my god thank you so much!! My phone is back to life!! :laugh:
I am glad that all of you found a solution to this problem.
in case anyone lands here from google...
I successfully upgraded to 5.02 and WiFi was working initially.
but then i had to change the custom recovery and superSU, and changed the logo.bin, now the WiFi is no longer working.
--- EDIT ---
after careful examination, found out it was caused by xt1064_lollipop_boot.img
in the end I flashed back to the stock boot.img from 5.02
and then flashed twrp-2.8.6.0-titan.img
now everything is great!
G920AUCU2AOE2 -> G920AUCU2AOF3 Updater
This is a modified version of the official OTA.
Upgrade from OE2 to OF3
Retains Root
Retains OE2 Bootloader
Retains OE2 Recovery
All checks removed (deleted, modified system files won't be patched, but it won't break the entire patching process)
If you unroot while on OF3 you will have to downgrade to OE2 kernel with Odin and use PingPong root.
Edited files WILL NOT be updated, they're skipped instead of breaking the entire update process like the stock OTA. If you want to update those files they need to be returned to stock OE2.
Download and unzip "OF3 Update.7z," extract G920AUCU2AOF3.zip to your sdcard.
In Flashfire select "Flash ZIP or OTA"
Select G920AUCU2AOF3.zip from your sdcard
Leave all of the settings default and flash.
After it has flashed, reboot to download mode and use Odin to flash the updated kernel and modem.
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Once the phone has rebooted you should be on OF3.
OF3 Update.7z
MD5: 2af43b437f238491ebe0aceb987de433
https://www.androidfilehost.com/?fid=24052804347773723
Is there a new baseband with this build? I flashed this in FlashFire and it still shows the old OE2 baseband.
Capt said:
Is there a new baseband with this build? I flashed this in FlashFire and it still shows the old OE2 baseband.
Click to expand...
Click to collapse
Seeing this made me go look. Same here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this update compatible with Scrosler's CleanRom?
ChristopherXDA said:
Is this update compatible with Scrosler's CleanRom?
Click to expand...
Click to collapse
Yes I used it and it worked fine
Mine says OF3
Sent from my SAMSUNG-SM-G920A using Tapatalk
I have to use Google+ to get Flashfire to flash this? Barf.
Well, I swallowed my bile and jumped through the G+ hoops to get FF. The update seems to be working well, but I was constantly getting a notification saying "Unauthorized Activity has been detected. Reboot now to undo the unauthorized changes." I disabled all Knox apps and the Security Log with Titanium Backup and it went away.
How did you get the OF3 baseband and the newest kernel? I have the old baseband/kernel.
Capt said:
How did you get the OF3 baseband and the newest kernel? I have the old baseband/kernel.
Click to expand...
Click to collapse
What Kernel version is your phone showing?
Mine is showing
3.10.31-4823236
[email protected] #1
Sun May 3 00:35:28 KST 2015
Which is the same as Cbass15 except his build date
Thu Jun 1818:20:13 KST 2015
Mine is showing 3.10.61 - 4823236. Sun May 3.
Capt said:
Mine is showing 3.10.61 - 4823236. Sun May 3.
Click to expand...
Click to collapse
I show the same, and appear to be having the same issues as you that you brought up in the other thread.
ChristopherXDA said:
Is this update compatible with Scrosler's CleanRom?
Click to expand...
Click to collapse
I know this is a stupid question, but can I flashfire this over my XtreStoLite ROM, or will I have re-flash the ROM after doing this?
Sorry! Maybe adding to the stupid questions.
Has anyone been brave enough to flashfire from OCE to this? I am unable to use a windows computer with ODIN for quite at least a week or two. Only have a access to a Mac.
What if I've already upgraded to OF3?
I wanted to check out OF3 so I flashed back to stock OE2 and updated it. After I found out that this rooted update was possible I tried flashing back to [email protected] but kept getting errors. Is that even possible or is there any way for me to get to rooted OF3? I just can't seem to flash back to OE2. Thanks for the help!
NizzleFish98 said:
I wanted to check out OF3 so I flashed back to stock OE2 and updated it. After I found out that this rooted update was possible I tried flashing back to [email protected] but kept getting errors. Is that even possible or is there any way for me to get to rooted OF3? I just can't seem to flash back to OE2. Thanks for the help!
Click to expand...
Click to collapse
No way back to OE2 if you took the OF3 OTA. The bootloaders are updated and don't allow you to roll back.
Also, I discovered you can't roll back the radio either, you just get unknown baseband.
designgears said:
No way back to OE2 if you took the OF3 OTA. The bootloaders are updated and don't allow you to roll back.
Also, I discovered you can't roll back the radio either, you just get unknown baseband.
Click to expand...
Click to collapse
Aw man that sucks Is it likely Ping Pong will be updated for this versions or no? Thanks for the response btw!
I updated the OP with new instructions. The initial release I made that was a Flashfire backup worked great for updating the modem and boot. I didn't notice that that few that used that had the proper things updated and those who used the modified OTA didn't. The new instructions and files take care of all of that.
designgears said:
I updated the OP with new instructions. The initial release I made that was a Flashfire backup worked great for updating the modem and boot. I didn't notice that that few that used that had the proper things updated and those who used the modified OTA didn't. The new instructions and files take care of all of that.
Click to expand...
Click to collapse
Worked perfect thank you sir!
I'm getting "unauthorized actions have been detected"? Anyone else?
Sent from my SAMSUNG-SM-G920A using Tapatalk
4redstars said:
I'm getting "unauthorized actions have been detected"? Anyone else?
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
Yep. freeze 4 knox app entries and one other - some security one, I forget the exact name - long press the notification and it will tell you - with TiBu and it will go away. That worked on the flash that didn't work right for me anyway, in the process of doing this new process now.
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"
Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever
PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.
BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.
Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.
gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.
Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk
Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!
tiduscrying said:
Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!
Click to expand...
Click to collapse
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.
mrmazak said:
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.
Click to expand...
Click to collapse
My phone came out of the box with version 6.1, so i was able to flash the modified stock update from here that updates the phone from 6.1 all the way to 7.4.2. I took the boot.img from the vanilla 6.1 prime update and flashed it, so that is probably what the issue is. I assume the next step would be to flash the boot.img from the 7.4.2 version, but I can't seem to find a normal version of the v.7.4.2 update that I can just take the boot.img from (unless I can take it from one of these flashable zips?). If it helps, here is a screenshot of my system info which has all the version numbers and whatnot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Okay, so I flashed the boot.img from a slightly modified zip of the 7.4.2 update (from here) and thankfully, everything is working fine now. 4G LTE is working swimmingly and I feel like a moron. Lesson learned. Kids, make your backups!
Well, now here is another weird issue. The 4G LTE data is working perfectly fine and speedy as ever, but MMS messages are not being received or sent for whatever reason now. I've already manually entered the correct APN settings and reset them as well to no avail. Any suggestions on this? I've also tried some other SMS apps (such as Pulse) and cleared Messenger's cache and data settings, but that all seems like it did nothing.
Edit: Well, I just flashed the modified 7.4.2 rom that's from the Rom's section of the Blu R1 HD board and MMS is working again. Looks like something other than the boot.img was messed up or something. I did a dirty flash so luckily my roms are in tact.
Edit 2: Sigh, I have no idea what's happening. MMS keeps getting screwey whenever I even start playing around with Xposed (more specifically, Gravity Box). I have no idea why this is happening now all of the sudden. A few days ago before I messed with Magisk, Gravity Box wasn't messing with my MMS messages (at least... I don't think it was...).