Database Users

[Q] /system/etc/gps.conf

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

[Q] TWRP/Rooted Nexus 10 w/Super SU in bootloop after OTA

My rooted/TWRP Nexus 10 w/ Super SU is stuck in a bootloop after receiving the OTA update.
I've tried the following:
Running Wug's and sideload the 4.4 update
Errors:
I was unable to get to the android with red exclamation point, even with Wug's.
I've looked around XDA and unfortunately either my searching capabilities are limited or I cannot find this exact problem that someone else had and fixed.
Does anyone have a suggestion on how I can fix this?
I have access to Wug's and the device has the TWRP 2.6.0.0 recovery.
What my screen looks like now after trying to sideload for 20 minutes:
{
"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"
}

Skullpuck said:
My rooted/TWRP Nexus 10 w/ Super SU is stuck in a bootloop after receiving the OTA update.
I've tried the following:
Running Wug's and sideload the 4.4 update
Errors:
I was unable to get to the android with red exclamation point, even with Wug's.
I've looked around XDA and unfortunately either my searching capabilities are limited or I cannot find this exact problem that someone else had and fixed.
Does anyone have a suggestion on how I can fix this?
I have access to Wug's and the device has the TWRP 2.6.0.0 recovery.
Click to expand...
Click to collapse
In order to sideload you will need to use factory recovery.img
There are several open threads iin this subforum already open that spell out in exact detail the process.
In a nutshell you will replace your recovery with 4.3 factory.img, boot to bootloader and go to new factory recovery and the dead droid and then sideload from there the OTA package

planet_x69 said:
In order to sideload you will need to use factory recovery.img
There are several open threads iin this subforum already open that spell out in exact detail the process.
In a nutshell you will replace your recovery with 4.3 factory.img, boot to bootloader and go to new factory recovery and the dead droid and then sideload from there the OTA package
Click to expand...
Click to collapse
I found the problem with files not transferring, I was using my phone USB cable instead of the Nexus 10 one. Unfortunately, I had to use Wug's and flash + unroot to get my device back. Although I can almost guarantee there was another way without losing the data partition. Anyway, I've now rooted my device and backup is restoring. The only thing I lost was my pictures, movies, themes, tones, saved pinball high scores, etc. It's quite a big loss so I think I will read up before applying the OTA next time and do some data backups.

OnePlus One July OTA Update Android 4.4.4

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

Why don't changes to /system have any effect?

I unlocked my P8 Lite's bootloader today with the intention of moving from its current Asiapac ROM to the European ROM (both devices have no hardware differences, anyhow it shouldn't affect the issue I'm having).
I downloaded a complete C432B170 ROM, and used the Huawei Update Extractor Tool to extract the various system images from the update:
{
"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 then proceeded to flash the system.img and boot.img, and both appeared to flash properly, but however upon rebooting the device I have the exact same ROM!
Having flashed other devices previously in the same fashion with positive results, I downloaded a few other complete (aka, complete ROM) packages, with every one experiencing the same issue (one of them however did manage to downgrade the device from 5.0.1 to 5.0, so it must be doing something to it [this was after wiping the userdata and cache partitions]).
Further tries to flash the ROM have had the same result.
What am I doing wrong here?
How is the P8 Lite different to other Android devices (in respect of firmware flashing)?
Do I need to flash something else?
I thought that it could be that it's not actually letting me modify the partitions, but I am able to wipe /system in TWRP (yes, it did let me install a custom recovery, so that's working).

you need to flash cust.img and recovery.img too
PS:you will get balong error so you need to flash the B052 rom in the first place then flash the custom folder ( dload2 or step2 ) that comes with it to fix it, you may loose your IMEI but updating to B170 VIA OTA will fix it

AmINoS007 said:
you need to flash cust.img and recovery.img too
PS:you will get balong error so you need to flash the B052 rom in the first place then flash the custom folder ( dload2 or step2 ) that comes with it to fix it, you may loose your IMEI but updating to B170 VIA OTA will fix it
Click to expand...
Click to collapse
Did it, and upgraded to Marshmallow, cheers .
Yeah, I got the Balong build-number error, but the updater allowed me to upgrade to B188 and then to Marshmallow (it's only a build number so I'm not that bothered). Only bug I've found so far is with the settings panel, otherwise its great.
Only thing is, I now only have 2.5GB of storage on /system rather than ~10GB I had before; how can I fix this? This issue occurred after I flashed B170.
Looks like to me that the /system partition is only 2.56GB (perhaps the B170 ROM was from an 8GB variant of the device?).
Another issue that I've found is that I can't seem to root the device (flashing the SuperSu zip always causes a boot-loop, regardless of the version of SuperSu I use).
Will probably re-flash this weekend fixing the Balong build-number error and (hopefully) the /system partition's size).

Galaxy A700FD bootloop after updating SuperSU

Hi there, I've been having problems with the Titanium Backup recently and tried some troubleshooting method such as unticking Mount namespace separation in SuperSU. They didn't work until i get to the point on updating the SuperSU from Play store. Then asked me to update the binary which i selected TWRP and it rebooted. After the installation from TWRP, it only boots to recovery. Tried turning off the phone and it still go to recovery even if i select reboot system.
Now i tried re-flashing the 'CF-Auto-Root-a7lte-a7ltexx-sma700fd.tar' via Odin3. It completed but then it's only boot looping. Sure i know it would reset multiple times but it has been more than 30mins doing like that over and over again. Tried to flash the TWRP again via Odin and wiped data/system/cache. And tried installing the Ressurection rom but it fails it gives me error "E:Error executing updater binary in zip '/external_sd/A7 Root and all/Roms/RessurectionRemix........"
Error flashing zip........
Then tried rebooting system. It said no OS installed proceed to reboot then saying device does not appeared to be rooted and asked me to install SuperSU which I did and it just restarted and still on boot loop....
Any help, please? TIA

{
"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 is what happen when i try to flash the firmware that i downloaded from sammobile... please help.
On the recovery, whenever i try to reboot, it says No OS installed. Then SuperSU installation. Whenever i try to install a custom rom, it fails. Giving me error: error executing updater binary in zip...

gsmtec said:
flash latest version for you model, should work
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
which one? CF auto root? firmware? thanks for replying..
btw im flashing the latest ones. except the SuperSU which I will try later. But the No OS installe would be the problem i think?

gsmtec said:
flash latest 6.0.1 version for your region or for the one that phone came
Click to expand...
Click to collapse
not sure but when i clicked earlier it was all china versions. and on first click on something it selects other something like samsung camera. but now i was able to see the firmwares. guess the site have some bugs. imma try it.
there's no 6.0.1 on my region. only 5.0.2 and lower versions.. i take the 5.0.2?