I've literally just flashed 5.0.1, currently "Android is Upgrading".
If I see any changes, I will be sure to post! Please feel free to do the same!!
OTA or ADB flashing?
Sent from my Nexus 9 using XDA Free mobile app
team56th said:
OTA or ADB flashing?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Neither - fastboot!
Yeah, manually did it via factory image!
Seems a bit snappier so far, but that might just be a placebo, or just because I have freshly rebooted it!
I flashed the new image and then flashed twrp and SuperSU and so far everything seems fine. Stock, rooted seems as fast and stable as the previous build if not more so....
What was your previous firmware level?
Changes are relative
What's the kernel version/date?
I was on the latest version of 5.0 before this (can't remember exactly what it was. Ha ha).
Here is the about screen.
{
"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"
}
This version is 5.0.1_r1 (LRX22C).
Ok, downloaded the 501 image, unzipped all IMG files and flash then manually, individually.
system.img
recovery.img
cache.img
boot.img
vendor.img
even performed a fastboot -w to wipe
After reboot it does some more reboots, show android robot once.
But finally i get the google logo and thats it. Nothing.
edit: oops typo . used wrong commands.
I only flashed the system.img, the rest is the same as the previous build.
I have to say, boot pretty fast after I installed SuperSU again (you'll never know) wipe cache and Dalvik and then done.
Tablet worksfine
Dalvik? Lollipop changed to ART afaik. Lol.
Just restored Q factory image. Booted right away!
During setup i get a message 'your tablet needs to download an update and restart'.
17.9Mb
Will be the q-to-r i guess. < 5 minutes later > Yep, got R now.
Flashing 501 system.img... takes 3 minutes or so.
Ah, reboot. Got the flying dots. Finally. "android is upgrading".
Checking 'about' ... On LRX22C now. Thanks.
reijndert said:
C:\android-sdk\platform-tools>fastboot flash system Nexus9-501-C-factory\recovery.img
Click to expand...
Click to collapse
You flashed everything as system.
The correct way would be:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
reijndert said:
Dalvik? Lollipop changed to ART afaik. Lol.
Click to expand...
Click to collapse
Well, TWRP offers only wipe cache and dalvik, no matter whether there is only ART
I flashed it and it works fine. I dont notice any apparent changes though.
Sendt fra min Nexus 5 med Tapatalk
Finished flashing it and have found nothing new so far.
Sent from my Nexus 9 using Tapatalk
Does it still heat up like crazy when you browse with Chrome?
clubtech said:
Does it still heat up like crazy when you browse with Chrome?
Click to expand...
Click to collapse
To me it doesn't seem to, might be newer version of Chrome Beta though?
Are there instruction for updating N9? I am rooted, unlocked and have custom recovery.
GatorsUF said:
Are there instruction for updating N9? I am rooted, unlocked and have custom recovery.
Click to expand...
Click to collapse
Flash the images in fastboot
Sent from my Nexus 9 using XDA Free mobile app
The DNS bug is not fixed. Local addresses are still not resolving to internal addresses, but the external IP. Annoying. The bug is marked as fixed but apparently not a part of 5.0.1
Related
adb sideload the kitket update zip is fails with following error:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
Click to expand...
Click to collapse
{
"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"
}
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
alexroz said:
adb sideload the kitket update zip is fails with following error:
View attachment 2408712
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
Click to expand...
Click to collapse
look here:
http://forum.xda-developers.com/showthread.php?t=2525947
you MUST reflash a kind of stock/not gps moddified version :/
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
EvilAaron said:
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
Click to expand...
Click to collapse
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
eksasol said:
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
Click to expand...
Click to collapse
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
EvilAaron said:
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
Click to expand...
Click to collapse
The flashing will required an unlocked bootloader, so if its not unlocked you will lose all data when unlocking it. (Doing a factory reset in stock recovery also wipe everything.)
I don't really know what else you can do, if there were never any modifications, then the problem is due to Google having too much protections and issues for their OTA packages.
Unlocked so can do the method in your guide. But she says she wants to clean up her phone so a clean start will probably perform better and she gets the clean slate she wants, problem solved Though OTA checks annoy me now lol
thx for the feedback and guides
I flashed stock rom with Toolkit, many times wipe data - cache - factory reset - sd reset etc. But problem not solved. Tried 4.4.3 - 4.4.4 nothing boot system. Just stuck on bootloader animation or Updating system apps...
I can boot with 4.2.2. but just one time. After i reboot don't boot. Stuck on bootloader animation... If i do wipe, stuck at Starting System Apps.
Its something wrong with 4.4.3+ or baseband version idk. What can i do other than flash stock Google img?
Also sim card don't working... No imei no imei sv no baseband. 4.3+ don't boot. I really don't know what should i do.
{
"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"
}
I can flash all stock roms or custom roms but nothing boot without 4.2.2 stock. In 4.2.2 no baseband no imei etc.
Did you flash the corresponding modem too? May be your efs partition is broken...
tachno said:
Did you flash the corresponding modem too? May be your efs partition is broken...
Click to expand...
Click to collapse
Now flashed 4.2.2 (JDQ39) Google img with toolkit + TWRP 2.7.0.1 everything is Ok. Then flashed 0.48 Radio (Source: JDQ39). Nothing changed.
I also tried 0.84 radio.
And always boot takes a long time.
Maybe its hardware problem, how can fix it?
khanjui said:
Now flashed 4.2.2 (JDQ39) Google img with toolkit + TWRP 2.7.0.1 everything is Ok. Then flashed 0.48 Radio (Source: JDQ39). Nothing changed.
I also tried 0.84 radio.
And always boot takes a long time.
Maybe its hardware problem, how can fix it?
Click to expand...
Click to collapse
Try too when flashing 4.2.2 with toolkit changing your recovery to CWM. And it's not necessary to flash a radio after, the radio is included in the image.
danmen2 said:
Try too when flashing 4.2.2 with toolkit changing your recovery to CWM. And it's not necessary to flash a radio after, the radio is included in the image.
Click to expand...
Click to collapse
Which version of CWM?
khanjui said:
Which version of CWM?
Click to expand...
Click to collapse
Try with CWM 6.0.2.3
danmen2 said:
Try with CWM 6.0.2.3
Click to expand...
Click to collapse
Also i have no /efs folder + nv_data.bak nv_data.bin
I will try with CWM. Thanks.
khanjui said:
Also i have no /efs folder + nv_data.bak nv_data.bin
I will try with CWM. Thanks.
Click to expand...
Click to collapse
If all else fails, take a look at this tutorial, in theory could recover access to your imei with it.
Good luck.
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
danmen2 said:
If all else fails, take a look at this tutorial, in theory could recover access to your imei with it.
Good luck.
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Cwm don't working too.
My friend have Nexus4 too, can i use his Efs backup with my imei or something?
khanjui said:
Cwm don't working too.
My friend have Nexus4 too, can i use his Efs backup with my imei or something?
Click to expand...
Click to collapse
Don't know if it could work, but to have two mobiles with the same imei may be illegal.
Yep it's out.
For those of you in need to manually update read below.
Download: cm-bacon-d22b777afa-to-0428073396-signed.zip (KTU84P, XNPH30O)
Install: To install the update, flash a custom recovery (TWRP recommended), boot into it, then sideload using adb sideload - if you've ever updated a Nexus device before, then you'll feel right at home, as the steps are exactly the same. TWRP will ask if you want to re-root at the end.
{
"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"
}
Wtf is this thread....anyways has anyone tried a clean flash yet?
just flashed it. thanks man!
Why can you flash the zip, why do you have to sideload it ?
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
I flashed it through TWRP, NO ISSUES
doalittledanse said:
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
Click to expand...
Click to collapse
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
clipcarl said:
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
Click to expand...
Click to collapse
yep. on both the stock cm recovery and twrp i get this error:
Code:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
If you've flashed any mods or made any changes to the system. It will fail.
Exclusive Member of the OnePlus One Club
If you guys flashed my Smooth Scrolling Mod, flash the revert and then try the OTA
http://forum.xda-developers.com/one...scrolling-mod-mahdi-rom-t2840934/post54762296
Basically when you're on stock ROM and if you did any changes to your /system/ then it will not update because its been modified.
does this include removal of apps ? Mine failed to sideload as well.+
Edit 1: I did do some modding of the build.prop as well this morning.
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
doalittledanse said:
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
Click to expand...
Click to collapse
Same problem here, fails at:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
Everything is stock, except Recovery. Tried with original recovery and it still fails...
Got mine to update even though the system partition was updated with a modified updater-script.
I will upload the entire zip with the updated script. For those that know what they are doing the updater-script is attached.
Edit 1: Note you do loose root. You have to install supersu again if you did have it previously (if you modified system then you did)
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Anyone tried custom kernels with ota?
Sent from my A0001 using XDA Free mobile app
C-4Nati said:
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Click to expand...
Click to collapse
look at my post.
I guess the update.zip factory image from the official site isn't truly stock. so i went with the nuclear option and just reflashed everything via fastboot. update worked perfectly now haha.
Please go to the thread here to continue the conversation....http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689
Hello,
It seems that Motorola is rolling out an Update!
My XT1052 received it this morning.
{
"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"
}
but ??
netokee said:
Hello,
It seems that Motorola is rolling out an Update!
My XT1052 received it this morning.
but ??
Click to expand...
Click to collapse
I also received the notification, but I didn't start the update.
Xt1058 BL open ghost.eu firmware
Inviato dal mio XT1052 utilizzando Tapatalk
5.1.1. 222.27.5 retail.eu I've just finished this update. Very small around 9MB if I remember. Can't see difference yet.
osstis said:
5.1.1. 222.27.5 retail.eu I've just finished this update. Very small around 9MB if I remember. Can't see difference yet.
Click to expand...
Click to collapse
5.1.1 ??
i also received it yesterday evening.
This build fixes known stagefright bugs, although a new one (aka CVE-2015-6602) has recently been discovered by zimperium:
libutils in Android through 5.1.1 LMY48M allows remote attackers to execute arbitrary code via crafted metadata in a (1) MP3 or (2) MP4 file, as demonstrated by an attack against use of libutils by libstagefright in Android 5.x.
Click to expand...
Click to collapse
Do keep in mind the instructions given here: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
I had TWRP installed, root, custom logo etc. and just took the update (in my defence, it was early morning and I wasn't thinking). Taking the update with TWRP get you into a semi-bootloop, where the system restarts after about 1 minute to try to install the update again. Just restoring to stock recovery made the update install, but it then hangs at the boot logo.
I had to restore from a factory image to fix it. Whilst restoring it didn't allow me to downgrade gpt.bin, so keep that in mind.
505dv said:
Do keep in mind the instructions given here: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
I had TWRP installed, root, custom logo etc. and just took the update (in my defence, it was early morning and I wasn't thinking). Taking the update with TWRP get you into a semi-bootloop, where the system restarts after about 1 minute to try to install the update again.
Click to expand...
Click to collapse
Yea, the OTA is looking at the specific fingerprints of the build.prop, so your custom recovery would indeed prevent it from flashing , also there are the MD5 hash checks that prevent the partitions from patching
505dv said:
Just restoring to stock recovery made the update install, but it then hangs at the boot logo. I had to restore from a factory image to fix it. Whilst restoring it didn't allow me to downgrade gpt.bin, so keep that in mind.
Click to expand...
Click to collapse
It sounds like you may have had issues with the boot or the system partitions, you could have tried re-flashing the stock 5.1 partitions from the image hosted, then taken the OTA, but I'm glad you were able to get your device back up and running
The gpt.bin is applied (near) last in the official OTA procedure, this is the bootloader being updated, and once you update your bootloader, you cannot return to anything before that bootloader safely (there are ways to apply other partitions, but it is risky and complicates the OTA process moving forward), if you do flash without updating the gpt.bin, please remember that in order to safely take OTA's, you will have to flash the most up to date stock image otherwise you will hard brick your device
It seems that the Smart-lock NFC Tag recognition bug was corrected
I had TWRP installed and flashed 5.1's recovery.img to be able to install the OTA. The OTA was installing fine until I noticed a reboot, which left me with the "Bootloader unlocked" warning screen and then nothing. I can boot into fastboot and have cleared the cache partition; to no avail: the wanring screen stays on for minutes.
Any pointers to revive my phone without clearing user data?
Fear not, you can still save your phone and all data on it. See me post a few message above here. I had the exact same problem. Follow the link in my post, and flash the Factory image, then take the OTA. You can skip the command to erase userdata, and even all your data and programs are safe. It will fail on the command to flash gpt, but this is no problem.
505dv said:
Fair not, you can still dave your phone and all data on it. See me post a few message above here. I had the exact same problem. Follow the link in my post, and flash the Factory image, then take the OTA. You can skip the command to erase userdata, and even all your data and programs are safe.
Click to expand...
Click to collapse
I tried that already, but gpt.img failed to flash (downgrade prevention) and the system.img is too big for flashboot and I don't have an mflashboot for 64bit Linux (arch) ...
Edit: missed your edit about gpt
Edit2: installed arch32-light, chrooted into 32bit and mfastboot'ed all, except for user data clear Booting/optimizing as wel speak!!!
Edit3: installed the OTA after going back to stock/non-root and it boots too!
Conclusion: always check XDA before flashing anything!
I also tried the ota. Have Stock 5.1 but TWRP and Root. TRWP showed error after flash-try. Reboot System was OK, but self-restart booted up TWRP again and again.
Update File can be found in "CACHE" folder. Just delete it (in TRWP) and self-restart is gone.
So is this actually 5.1.1 or just an update to 5.1?
5.1 only
Hi,
Using a Note3 LTE version. 9005. Tried to update with TWRP ver 2.8.7. Did not work. Tried to flash 3.3.0 TWRP image, now phone only goes in these two modes after removing the SD card:
{
"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"
}
and this
The flash was on the SD card. Card removed now. Any ideas how to fix this?
Can you perform fastboot commands?
Wait just flash a rom with odin then go back into bootloader and flash twrp.
Keno_I said:
Can you perform fastboot commands?
Click to expand...
Click to collapse
no idea. How to do that?
Keno_I said:
Wait just flash a rom with odin then go back into bootloader and flash twrp.
Click to expand...
Click to collapse
How to do that? I'm guessing this is the way. Its been a very long time since I flashed a phone.
This should be new enough.
mystvearn said:
no idea. How to do that?
How to do that? I'm guessing this is the way. Its been a very long time since I flashed a phone.
Click to expand...
Click to collapse
Use this for help
[GUIDE][HOW TO FLASH LOLLIPOP | SM-N9005][5.0 | N9005XXUGBNL8][Easy]
Confused on how to install Android 5.0 Lollipop? Fear not. This guide have you covered :D So to start this. We need some things. Odin Lollipop Leak A Backup of your PIT File incase something goes wrong and lastly a Samsung Galaxy Note 3 THIS...
forum.xda-developers.com
Keno_I said:
Use this for help
[GUIDE][HOW TO FLASH LOLLIPOP | SM-N9005][5.0 | N9005XXUGBNL8][Easy]
Confused on how to install Android 5.0 Lollipop? Fear not. This guide have you covered :D So to start this. We need some things. Odin Lollipop Leak A Backup of your PIT File incase something goes wrong and lastly a Samsung Galaxy Note 3 THIS...
forum.xda-developers.com
Click to expand...
Click to collapse
Got it working again. Now to start installing lineageOS again
mystvearn said:
Got it working again. Now to start installing lineageOS again
Click to expand...
Click to collapse
Great news! Goodluck with your phone
please mark best answer if my answer helped.
Keno_I said:
Great news! Goodluck with your phone
please mark best answer if my answer helped.
Click to expand...
Click to collapse
How do I mark the best answer?
I've installed the LOS, got it working but no gapp apps. So tried to flash TWRP again, but it always boots to the LOS 18 recovery and not TWRP. Now going back to Note3 stock. There must be something I'm doing wrong somewhere.
mystvearn said:
How do I mark the best answer?
I've installed the LOS, got it working but no gapp apps. So tried to flash TWRP again, but it always boots to the LOS 18 recovery and not TWRP. Now going back to Note3 stock. There must be something I'm doing wrong somewhere.
Click to expand...
Click to collapse
Before you flash the recovery, untick the Auto Reboot option in ODIN. Then flash the recovery. After flashing in done, reboot your device directly to recovery mode from download mode by pressing Vol up + Power + Home button together. Now you will see the TWRP recovery is booted in your device. Now you can reboot normally and your TWRP will be installed.