Just got a security patch update today (11/2/15) from Verizon. About 24 MB. Froze the update as I'm stock rooted on 5.0.2 I may pull the trigger to see if I lose root. But before I do I wanted to see if anyone else received this update and can confirm if it may be the stagefright patch?
Doh! This should be in the VERIZON LG G2 forum. Apologies.
P.S. Thanks mods for moving this to the correct forum.
I'm also stock rooted and tried to get the OTA yesterday but failed (saw an error message "0x1111004" during install and nothing was modified.) Please let me know how it works with you. I'm not sure if this one is a stagefright patch but I found some discussions -- google "verizon lg g2 3aa".
Got the same error message. Can't seem to get the Software Upgrade Assistant to work either. Not in any rush. I may try a factory reset, try a clean update, and see if I can re-root this weekend if I have time.
tedyun said:
I'm also stock rooted and tried to get the OTA yesterday but failed (saw an error message "0x1111004" during install and nothing was modified.) Please let me know how it works with you. I'm not sure if this one is a stagefright patch but I found some discussions -- google "verizon lg g2 3aa".
Click to expand...
Click to collapse
It is the stagefright patch, I was able to install it with no issues. But they didn't patch CVE-2015-6602, all else is patched and I can't wait to get another phone soon.
Got error message as my G2 is rooted.
Yes it's the 3AA update. I went back to stock to get it, now I have all those apps I don't use. I'll have to root again so I can use Titanium to freeze apps.
Got 3AA OTA update working - kept root
striker59 said:
Got error message as my G2 is rooted.
Click to expand...
Click to collapse
Being rooted doesn't block the update. The update script checks a large number of files already installed on the phone, and if they don't match what is expected to be there prior to the update, the script exits and throws the error message.
Since you're rooted, if you don't have one already you can download an install file explore than is root capable and can also mount your file system read/write (several out there).
Browse to the System folder (with Root access)
Open the cache folder
Open the fota folder within the cache folder
Open the log folder within the fota folder
Assuming you had the upgrade error, you'll find a log file there - I don't recall the exact name, and now that I had a successful update the file appears to have been deleted, but it was something to do with "fota" with a file extension of "log". Open the file (it's a readable text file) and scroll to the bottom. You'll see a number of lines that trace the script's examination of each of multiple files, verifying that the right version is in place. In my case, "install-recovery.sh" was the wrong size, causing the script to abort with an error code -- with the update failing.
I did a bit of research, and learned that installing SuperSU (which is excellent) also caused the original install-recovery script to be backed up and replaced by a modified version. If you started by installing a current version of SuperSU, I believe the backed up version of the install-recovery script is still there and an uninstall of SuperSU (via it's own internal menu) will cause the original copy of install-recovery.sh to be replaced.
In my case, I didn't want to give up root - so instead of uninstalling SuperSU, I dug around a bit (don't remember if it was in system\etc or system\bin) and found "install-recovery_original.sh" -- which is the backup that SuperSU had created for me on installation. I backed up "install-recovery.sh" from the system\bin (just renamed it, actually) and dropped in a copy of the "install-recovery_original.sh" file and renamed it to "install-recovery.sh". BTW - I noted the the OEM file was something like 649 bytes, while the SuperSU version was 629 bytes (I think -- all from memory now).
Once I had the original file back in place, the OTA update worked just fine. I also checked: it's now running:
Software version: VS9803AA (Android 5.0.2)
Build number: LRX22G
Baseband version: VS9803AA-MPSS.DI.2.0.c2-00081-M8974AAAAANAZM-1
Kernel version: 3.4.0-perf-ga038154
Using Root Checker Pro after all this, I verified that I still have root, and busybox is still happily installed. No need to re-root the phone doing it this way. The OTA apparently does NOT unroot the phone.
If you're getting an error running the OTA (I think it was 11110004), that suggests that the install script ran into a non-OEM file (size or CRC didn't match). If you have the patience to find the log file and look at the bottom 10 or 15 lines, you can likely figure out which file it's choking on, and possibly figure out how to get the original / OEM file back in its place, after which the OTA will work.
- Jon
Jonstrong I will print this out for next time, thanks. Long involved process the way I did it, now in the process of freezing apps I don't use with Titanium after I rooted again.
Any idea how to get the Verizon security update when the Verizon phone uses a secondary carrier? (Net10/tracphone).
Alternately, is the security fix build into any of the LG G2 custom ROMs (like Xdabbeb's?)
My gf is using my old phone and complaining about the nagging update. I am not sure it is rooted but I think it is. Regardless, does the update block the root process?
Is it possible to manually install this update?
Help
i keep recieving this error when rooting using aviochs one click method is there any solution
ERROR: The system was unable to find the specified registry key or value.
I know LG has been plugging the root method. My G4 and x8.3 tab require root injection to the system.img.
jonstrong said:
Being rooted doesn't block the update. The update script checks a large number of files already installed on the phone, and if they don't match what is expected to be there prior to the update, the script exits and throws the error message.
Since you're rooted, if you don't have one already you can download an install file explore than is root capable and can also mount your file system read/write (several out there).
Browse to the System folder (with Root access)
Open the cache folder
Open the fota folder within the cache folder
Open the log folder within the fota folder
Assuming you had the upgrade error, you'll find a log file there - I don't recall the exact name, and now that I had a successful update the file appears to have been deleted, but it was something to do with "fota" with a file extension of "log". Open the file (it's a readable text file) and scroll to the bottom. You'll see a number of lines that trace the script's examination of each of multiple files, verifying that the right version is in place. In my case, "install-recovery.sh" was the wrong size, causing the script to abort with an error code -- with the update failing.
I did a bit of research, and learned that installing SuperSU (which is excellent) also caused the original install-recovery script to be backed up and replaced by a modified version. If you started by installing a current version of SuperSU, I believe the backed up version of the install-recovery script is still there and an uninstall of SuperSU (via it's own internal menu) will cause the original copy of install-recovery.sh to be replaced.
In my case, I didn't want to give up root - so instead of uninstalling SuperSU, I dug around a bit (don't remember if it was in system\etc or system\bin) and found "install-recovery_original.sh" -- which is the backup that SuperSU had created for me on installation. I backed up "install-recovery.sh" from the system\bin (just renamed it, actually) and dropped in a copy of the "install-recovery_original.sh" file and renamed it to "install-recovery.sh". BTW - I noted the the OEM file was something like 649 bytes, while the SuperSU version was 629 bytes (I think -- all from memory now).
Once I had the original file back in place, the OTA update worked just fine. I also checked: it's now running:
Software version: VS9803AA (Android 5.0.2)
Build number: LRX22G
Baseband version: VS9803AA-MPSS.DI.2.0.c2-00081-M8974AAAAANAZM-1
Kernel version: 3.4.0-perf-ga038154
Using Root Checker Pro after all this, I verified that I still have root, and busybox is still happily installed. No need to re-root the phone doing it this way. The OTA apparently does NOT unroot the phone.
If you're getting an error running the OTA (I think it was 11110004), that suggests that the install script ran into a non-OEM file (size or CRC didn't match). If you have the patience to find the log file and look at the bottom 10 or 15 lines, you can likely figure out which file it's choking on, and possibly figure out how to get the original / OEM file back in its place, after which the OTA will work.
- Jon
Click to expand...
Click to collapse
Jon, your instructions worked like a charm. The backup install-recovery_original.sh is located in the same directory as the one put there by SuperSU, /system/bin/. Thanks for doing the legwork!
jonstrong said:
Being rooted doesn't block the update. The update script checks a large number of files already installed on the phone, and if they don't match what is expected to be there prior to the update, the script exits and throws the error message.
Since you're rooted, if you don't have one already you can download an install file explore than is root capable and can also mount your file system read/write (several out there).
Browse to the System folder (with Root access)
Open the cache folder
Open the fota folder within the cache folder
Open the log folder within the fota folder
Assuming you had the upgrade error, you'll find a log file there - I don't recall the exact name, and now that I had a successful update the file appears to have been deleted, but it was something to do with "fota" with a file extension of "log". Open the file (it's a readable text file) and scroll to the bottom. You'll see a number of lines that trace the script's examination of each of multiple files, verifying that the right version is in place. In my case, "install-recovery.sh" was the wrong size, causing the script to abort with an error code -- with the update failing.
I did a bit of research, and learned that installing SuperSU (which is excellent) also caused the original install-recovery script to be backed up and replaced by a modified version. If you started by installing a current version of SuperSU, I believe the backed up version of the install-recovery script is still there and an uninstall of SuperSU (via it's own internal menu) will cause the original copy of install-recovery.sh to be replaced.
In my case, I didn't want to give up root - so instead of uninstalling SuperSU, I dug around a bit (don't remember if it was in system\etc or system\bin) and found "install-recovery_original.sh" -- which is the backup that SuperSU had created for me on installation. I backed up "install-recovery.sh" from the system\bin (just renamed it, actually) and dropped in a copy of the "install-recovery_original.sh" file and renamed it to "install-recovery.sh". BTW - I noted the the OEM file was something like 649 bytes, while the SuperSU version was 629 bytes (I think -- all from memory now).
Once I had the original file back in place, the OTA update worked just fine. I also checked: it's now running:
Software version: VS9803AA (Android 5.0.2)
Build number: LRX22G
Baseband version: VS9803AA-MPSS.DI.2.0.c2-00081-M8974AAAAANAZM-1
Kernel version: 3.4.0-perf-ga038154
Using Root Checker Pro after all this, I verified that I still have root, and busybox is still happily installed. No need to re-root the phone doing it this way. The OTA apparently does NOT unroot the phone.
If you're getting an error running the OTA (I think it was 11110004), that suggests that the install script ran into a non-OEM file (size or CRC didn't match). If you have the patience to find the log file and look at the bottom 10 or 15 lines, you can likely figure out which file it's choking on, and possibly figure out how to get the original / OEM file back in its place, after which the OTA will work.
- Jon
Click to expand...
Click to collapse
Thank you JonStrong!! Worked like a charm and no more nag! Much appreciated.
Do I need to go back to the "install-recovery.sh" I originally renamed?
superchaos said:
Thank you JonStrong!! Worked like a charm and no more nag! Much appreciated.
Do I need to go back to the "install-recovery.sh" I originally renamed?
Click to expand...
Click to collapse
In my case SuperSU notified me (after update was successful and rebooted) to update its binary, and it automatically replaced install-recovery.sh during the process.
jonstrong said:
Being rooted doesn't block the update. The update script checks a large number of files already installed on the phone, and if they don't match what is expected to be there prior to the update, the script exits and throws the error message.
Since you're rooted, if you don't have one already you can download an install file explore than is root capable and can also mount your file system read/write (several out there).
Browse to the System folder (with Root access)
Open the cache folder
Open the fota folder within the cache folder
Open the log folder within the fota folder
Assuming you had the upgrade error, you'll find a log file there - I don't recall the exact name, and now that I had a successful update the file appears to have been deleted, but it was something to do with "fota" with a file extension of "log". Open the file (it's a readable text file) and scroll to the bottom. You'll see a number of lines that trace the script's examination of each of multiple files, verifying that the right version is in place. In my case, "install-recovery.sh" was the wrong size, causing the script to abort with an error code -- with the update failing.
I did a bit of research, and learned that installing SuperSU (which is excellent) also caused the original install-recovery script to be backed up and replaced by a modified version. If you started by installing a current version of SuperSU, I believe the backed up version of the install-recovery script is still there and an uninstall of SuperSU (via it's own internal menu) will cause the original copy of install-recovery.sh to be replaced.
In my case, I didn't want to give up root - so instead of uninstalling SuperSU, I dug around a bit (don't remember if it was in system\etc or system\bin) and found "install-recovery_original.sh" -- which is the backup that SuperSU had created for me on installation. I backed up "install-recovery.sh" from the system\bin (just renamed it, actually) and dropped in a copy of the "install-recovery_original.sh" file and renamed it to "install-recovery.sh". BTW - I noted the the OEM file was something like 649 bytes, while the SuperSU version was 629 bytes (I think -- all from memory now).
Once I had the original file back in place, the OTA update worked just fine. I also checked: it's now running:
Software version: VS9803AA (Android 5.0.2)
Build number: LRX22G
Baseband version: VS9803AA-MPSS.DI.2.0.c2-00081-M8974AAAAANAZM-1
Kernel version: 3.4.0-perf-ga038154
Using Root Checker Pro after all this, I verified that I still have root, and busybox is still happily installed. No need to re-root the phone doing it this way. The OTA apparently does NOT unroot the phone.
If you're getting an error running the OTA (I think it was 11110004), that suggests that the install script ran into a non-OEM file (size or CRC didn't match). If you have the patience to find the log file and look at the bottom 10 or 15 lines, you can likely figure out which file it's choking on, and possibly figure out how to get the original / OEM file back in its place, after which the OTA will work.
- Jon
Click to expand...
Click to collapse
Thanks, that worked, but I screwed up. I did the rename, but I forgot to save a copy of the 649 byte version of the file. So when SuperSU updated its binary, it wiped out the file and I can't find where it backed it up (if it did.) Is there some way to get a copy of that for next time?
Hi,
Has anyone been using the hotspot provision fix/back with the new VS9803AA update? I successfully upgraded (brand new phone) then successfully rooted (using the LG One-click method). However, I think I messed up the hotspot mod. Now when I try to turn on Mobile Hotspot, it slides to "on" but nothing really happens (I don't get the antenna icon in the upper left status bar like usual) and I can slide the switch to "off." Hotspot Settings and everything can be accessed though.
Any ideas? Did I just screw up the file replacement?
Never mind.... It somehow started working oddly.
Related
Back a year ago I rooted my nexus one phone, but the thing is I uninstalled a few stock apps. I had no idea that my updates would be a pain.
What I found out is that each new google update does a ton of asserts on files that it expects to be there. I had a problem with google books when I tried to update from 2.3.3 to 2.3.4, but someone on this forum hack a cracked version that allowed me to do so.
Now the annoying problem is back again, and this time, it's saying something about assert_failed: apply patch check ("system/app/EmailGoogle.apk...
I tried to find an EmailGoogle.apk out there, and I was able to find it, but if I was to use it, it wouldn't connect at all, then it would crash. I also placed it in system/app folder, and still same problem.
Is there a way for me to hack the update.zip so I can tell it to ignore these assertions?
AHH! I figured it out!
After much searching for updating scripts, I found out that there is indeed a file that tells your phone how to perform a patch update.
This involved me rebooting the phone 7 times (with about 5 times prior with previous experimentation)
Okay what I had were the following items
-Dropbox
-Root Explorer
-Laptop
Initially I got the error after running anon ra recovery, but I lost it when I accidently updated 2.3.4 again (I stupidly named my files as update.zip, update1.zip, update2.zip). Actually, I lost root (the phone still had the unlocked thing on it, but it was fooled). So I used this website (to root my phone again):
http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
So to get the specific error
1.you shut down your phone
2. reboot by pressing power button and down volume and hold it
3. Select recovery by navigating using the down volume, and select it by pressing power button.
4. After it reboots again, scroll down using your trackball and select Flash zip from sdcard
5. make sure you toggle signature verification to disable
6. select your update.zip
thats how you get your error
to fix:
1. So I took the signed zip file, and uploaded it to my dropbox
2. I opened the file using winrar (DO NOT UNZIP THIS FILE TO EDIT) the reason you do not want to unzip is because if you zip it up again you lose the signature, and your phone won't find the script
3. I used winrar to navigate to the following:
META-INF-->com-->google-->android
4. Open update-script using notepad
5. crtl-f on each package-name searching through the file:
emailgoogle.apk
GenieWidget.apk
Mms.apk
Talk.apk
Twitter.apk
VoiceDialer.apk
(ugh.. I forgot I uninstalled all those)
they existed twice. Once to assert to make sure the file exists, and the second to apply the patch
You have to remove both, you can keep the progress bar command there, that's just to update the progress of your update on your screen
example
;assert(apply_patch_check("/system/app/Twitter.apk", "48dcef1792760138acb1c10e2a2341dfbee69258", "e3e34aa0a72d0eaf76d80a06828bd14ea8450d34"))
apply_patch("/system/app/Twitter.apk", "-",
48dcef1792760138acb1c10e2a2341dfbee69258, 1596937,
e3e34aa0a72d0eaf76d80a06828bd14ea8450d34, package_extract_file("patch/system/app/Twitter.apk.p"));
so after repeating this over and over, it finally updated
anyways, going to sleep
Unzip the file on your phone with eStrongs file manager.
Edit the update script (eStrongs again).
Rezip (eStrongs again).
Sign with ZipSigner, or toggle signature verification in recovery.
Flash.
Note, if you use the "flash zip from SD" option, you don't need to name the file "update.zip"
thanks danger-rat, seen your posts many times before, I saved lots of your comments in my evernote
I already knew about renaming update.zip, I just got into a dumb naming habit, the last 5 tries I just kept the name as it was
my root explorer (file manager) by speed software does what eStrongs does, I can edit, zip, tar, unmount folders, set permissions etc, maybe you should check it out
but i've learned two new things about your post
never heard of zipsigner, and eStrongs
thanks for showing the quicker way of doing this, the dropbox thing was a bit of a hassle, but I love editting this on my computer rather than my phone using the trackball touchpad combo :-|
I'm wondering why a solution wasn't even there when I was looking for answers around the web? I searched for hours too. I'm also glad I didn't brick my phone!
Yeah, I use Root Explorer a lot. I prefer the interface on eStrongs and love the LAN capabilities and Dropbox interface, but Root Explorer is much better when you need root permission.
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Foxman2k said:
Hi All,
I'm relatively new to Android (had the Nexus 7 for about a year). My questions is this:
I have 4.2.2 currently loaded. When I orinally got the nexus 7, I used a toolkit to unlock the bootloader and root the device, so I could install SixAxis and a few other apps that required root.
What is the easiest way for me to now update to 4.3? Will the OTA update that is bound to show up on the device shortly work?
BTW This is the WiFi only Nexus 7, 16 GB and my main PC at home is a Mac.
Thanks.
Click to expand...
Click to collapse
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
basuraunak said:
Get it locked and unrooted to get OTA possiblt easiest way.
Otherwise flash the factory images:thumbup:
Sent using Nexus 7
Click to expand...
Click to collapse
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Foxman2k said:
Do you have a link of a guide that I could follow on how to flash the factory image?
Can I download the zip and then use the clockwork recovery i have installed to load the zip?
Click to expand...
Click to collapse
Just use wug's toolkit. Its over in the android development in the n7 section...
---------- Post added at 10:04 AM ---------- Previous post was at 10:00 AM ----------
drake90001 said:
I don't think that having the bootloader locked or unlocked will really affect the OTA..
Am I right or am I right?
Click to expand...
Click to collapse
I dont think having it unlocked will effect the ota (it hasnt in the past for me), but it sounded like he wanted to flash the factory image. I actually have a nandroid of it on my unlocked n7. Gonna flash the official and see if I can get the ota later...
I've taken OTAs no problem on an unlocked, rooted device with TWRP recovery. So you're fine.
Sent from my Nexus 7 using Tapatalk 4 Beta
Here you go for flashable zip :
http://forum.xda-developers.com/showthread.php?t=2376522
Sent from my Nexus 7 using xda premium
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Also, just tried via adb sideload and that didn't work either.
Foxman2k said:
So I downloaded what I believe to be the right file, ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07 (1).zip.
I then reboot my nexus 7 into clockworkmod revovery and select install zip, choose zip from sdcard, browse to the aboev file but then get an error:
It ends in (Status 7) Installation aborted.
What am I missing?
Click to expand...
Click to collapse
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Groid said:
Did you install the aosp browser and rename the default browser apk and odex files or modify the buildprop file? Those must be as original to take the update. Also, you should have gotten a message about what failed when you get the Status 7 error. What else did it say?
Click to expand...
Click to collapse
Foxman2k said:
No to all of the above. I don't know what odex files or buildprop file would refer to, so I defintely haven't modified them.
It says:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/debuggerd", "a whole bunch of letters and numbers", "a whole bunch of letters and numbers")
E:Error in /sdcard/0/update rom/ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi - JWR66V - from - JDFQ39.ab67ca07 (1).zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Does it make a difference that my current build number in "about tablet" shows as JDQ39 and not JDFQ39 as above?
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Groid said:
The problem file is 'debuggerd' in the /system/bin folder as it says in the error message. I had the same issue previously on the last N7 update. I had to get the original file from someone since the file had been replaced by another app (possibly Stickmount) or it can be extracted from the previous update to 4.2.2. I don't know about the JDFQ39 compared to the download file showing JDQ39, but that is the same file I downloaded. The (1).zip means you had previously downloaded the file and this is an additional d/l. That shouldn't be a problem, but you can delete the (1) if you want.
I'll try flashing through CWM and let you know if mine worked. If so, I can send you the right 'debuggerd' file.
Click to expand...
Click to collapse
Ok great. I do have stickmount installed...
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Groid said:
Well, I got the debuggerd error also. I'll try the backup debuggered file I used in the last update. Otherwise, I'll have to find the debuggerd file from 4.2.2. Any help out there?
Click to expand...
Click to collapse
Glad I'm not alone lol
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Groid said:
Still no joy. I think someone will have to get the right debuggerd file and get it to one us on a pm or email. Also, I noticed on my update try that the file was listed as JDQ39. ... and not the JDFQ39. ... that you saw.
Click to expand...
Click to collapse
once we get the file, how do I replace the file with the debuggerd that is currently on the nexus?
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Groid said:
What I will do is to copy the debuggerd file to the N7 internal storage root folder from my pc. Then I will rename /system/bin/debuggerd to debuggerd.bak (or whatever extension you want to add). Then I will copy the correct debuggerd file from sdcard to /system/bin and try the update again. I started a new thread asking for someone with an unaltered 4.2.2 debuggerd file to send it to me. If I get it I'll pass it along to you.
Click to expand...
Click to collapse
Are you using a tool like ES File Manager to do the moving and renaming of files etc?
I am running 100%, downloaded the huge ~400 MB OTA 4.2.2 update. I then postponed the installation, flashed CWM and rooted. Rebooting still gives me the prompt to install the fully downloaded update although i know it won't work. But i just wanted to backup that OTA update. It should be possible now that i'm rooted. So, where to find that OTA update? I've been looking for the past hour and haven't been able to track it down. Is the OTA file supposed to be a single zip file? Or is it extracted already in its own folder with several files? I'm using ES File Manager with root access permission.
On firmware 1.28 i noticed that the OTA was simply dumped as a single zip file in the Download folder, which is easily accessible in the Internal Memory without any need for root. However, i just cannot find the OTA file while on firmware 1.29. HTC has obviously made some changes and tried really hard to hide the OTA update. Can someone please tell me where to look? I am rooted and using ES File Manager.
electronical said:
On firmware 1.28 i noticed that the OTA was simply dumped as a single zip file in the Download folder, which is easily accessible in the Internal Memory without any need for root. However, i just cannot find the OTA file while on firmware 1.29. HTC has obviously made some changes and tried really hard to hide the OTA update. Can someone please tell me where to look? I am rooted and using ES File Manager.
Click to expand...
Click to collapse
Hey man
Not sure (again ), but can you check /cache/
Have to be root-enabled though.
nkk71 said:
Hey man
Not sure (again ), but can you check /cache/
Have to be root-enabled though.
Click to expand...
Click to collapse
Hey nkk71 :cyclops:
The device is rooted and i've enabled root access to ES File Explorer. I just checked inside /cache/ and there are only two folders: lost+found (empty) and recovery (which has 2 insignificant logs). The 2.24.401.1 OTA is 416 MB. Now, i just have to find it.
Let's hope we can crack this one! :fingers-crossed:
electronical said:
Hey nkk71 :cyclops:
The device is rooted and i've enabled root access to ES File Explorer. I just checked inside /cache/ and there are only two folders: lost+found (empty) and recovery (which has 2 insignificant logs). The 2.24.401.1 OTA is 416 MB. Now, i just have to find it.
Let's hope we can crack this one! :fingers-crossed:
Click to expand...
Click to collapse
Hmm, I thought it would be either in downloads (which you already checked) or /cache. I'm sure it's only 1 file, not several. How about a search in ES for OTA starting from /. May take a while but should find it.
nkk71 said:
Hmm, I thought it would be either in downloads (which you already checked) or /cache. I'm sure it's only 1 file, not several. How about a search in ES for OTA starting from /. May take a while but should find it.
Click to expand...
Click to collapse
Root Explorer did it with its much better and faster search engine. ES File Manager is good for a free app, but not the best.
Verdict? While in official firmware 1.29.401.12, the 2.24.401.1 OTA is downloaded at /data/data/com.android.providers.downloads/cache
And you were right, it is still a single zip file. But the download location is really well hidden this time around.
electronical said:
Root Explorer did it with its much better and faster search engine. ES File Manager is good for a free app, but not the best.
Verdict? While in official firmware 1.29.401.12, the 2.24.401.2 OTA is downloaded at /data/data/com.android.providers.downloads/cache
And you were right, it is still a single zip file. But the download location is really well hidden this time around.
Click to expand...
Click to collapse
:good:
HTC must be following the motto: why make things simple, if you can make them hard(er).... user's will spend much more time on their phone, than doing other stuff.
I'm progressively updating from all the OTA's. I'll just add the information here during the update process so it might help others as a reference, if they need to find and save all their OTAs. I've now received the 2.24.401.8 OTA update and the save location is the same as for the 2.24.401.1: /data/data/com.android.providers.downloads/cache
Edit: And that was the last OTA update available at this time, for MID: PN0710000, CID: HTC__001 (i really thought i'd be having the 4.3 with Sense 5.5 OTA update by now. oh well.)
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
aerosmike said:
Hi,
I hope this is the write location for my post.
I have a HTC ONE rooted, android 4.3
I have a problem with my GPS: it doesn't lock any satellite. Reading on forum, I found that the problem may be the setting of gps.conf file in /system/etc.
In fact, checking it, I found that the NTP_SERVER set was for north.america, while I'm in Europe.
I would like to modify or replace it, but I'm experiencing some problem. Using Root Browser it seems to be able to modify it, but after rebooting the device it is exactly the same before the editing. I tried using other editors as ES File Explorer, but when I try to modify the file, it says "read only file system".
It makes me thing that also the other editor is not able to modify the file, since after reboot it is actually un-edited.
What do you think? how can I actually write in file system and actually modify gps.conf?
Thank you in advance
Let me add another detail: I tried to create a new empty file in the same folder with Root Browser. It seems to be able to create it, but after rebooting the device it desappears..so I guess I actually can't modify/write in the file system..
Click to expand...
Click to collapse
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
alray said:
You need an unsecured kernel (/system writable) to write to /system partition of the htc one, not only root.. Otherwise, all changes will be reverted at reboot like you are experiencing.
Kernels for htc one here
And note that modifying/deleting files in /system will probably prevent you to install future ota unless you revert the change you have made. There is a md5 checksum of many files in /system before the ota installs. If the md5 cheksum doesn't match then the ota will not install. This might not apply to the .conf file you want to edit but just in case, make a backup of that file before. So if the next ota fail, you'll know why.
Click to expand...
Click to collapse
Thank you very much
Preferably the g900a 4.4.2 version of it, just to be safe?
After messing up the file, i deleted it because i thought it would automatically regenerate (i know, i know...) when i restarted, everything crashed, so i couldnt do anything with the phone... after doing a factory reset that did nothing, i tried reflashing with Odin, it did reflash, but the issue was still there (upon restart every background app crashes and crashes), I used Odin to only reflash the "AP" file... so maybe i have to update a different one? anyway...
I finally fixed it with a platform.xml file that was "reinstalled" as a .zip via recovery... I used the one in this link: http://forum.xda-developers.com/showthread.php?t=2607215
Now the only issue that im apparently having is that i cant use the Fingerprint reader (which worked flawlessly before my screw up) So im guessing it was affected by the "fix"...
Im guessing replacing the file would fix this :/ maybe
This one also has the sdcard permissions added. You could probably swap it with the other platform file in the zip and just reflash it. There are several ways to add that file to the system/etc/permissions folder, but will crash your phone again if done incorrectly. Also, the platform file that you used was for the S4, which does not have a fingerprint scanner, which would explain why yours do not work now.
shortydoggg said:
This one also has the sdcard permissions added. You could probably swap it with the other platform file in the zip and just reflash it. There are several ways to add that file to the system/etc/permissions folder, but will crash your phone again if done incorrectly. Also, the platform file that you used was for the S4, which does not have a fingerprint scanner, which would explain why yours do not work now.
Click to expand...
Click to collapse
Thanks thats what i thought about the fingerprint scanner !
I replaced the platform.xml file in the .zip and updated via recovery, but sadly the fingerprint scanner still doesnt work...
I try the *#0*# and says version: null
badillin said:
Thanks thats what i thought about the fingerprint scanner !
I replaced the platform.xml file in the .zip and updated via recovery, but sadly the fingerprint scanner still doesnt work...
I try the *#0*# and says version: null
Click to expand...
Click to collapse
Yea, the only sure way to fix that is to backup your user apps and data, call logs and messages with Titanium, along with your storage to a computer with a file explorer, and flash the downgrade to NCE file (or the AP, CSC, and maybe CP files files for the NCE downgrade). It'll wipe the phone, but it will fix everything. Or, you'll just be without a fingerprint scanner.
I made a similar error with the same platform.xml file. Seems once it's broke, it's not fixable without reflashing.