Database Develop

[Q] Got CWR on Streak & made backup, stuck on next step

Hello again
I'd asked for info on how to root my Streak last week and was able to get started on the process, and have gotten as far as putting clockworkmod recovery on the streak and making the nandroid backup, but am now stuck. I'm including as much information of what I've done below to try and help make it easier to find the error, if possible. I have been trying to look up stuff for myself as much as I can, but I haven't been able to find a solution to this problem as of yet.
I've been working from the instructions at http://www.streaksmart.com/2011/03/how-to-get-rooted-android-222-update-on-your-dell-streak-7.html
For the last step, it says:
Now let's get to flashing your chosen .zip from ClockworkMod.
Turn off your Streak 7.
Turn it back on by holding down the volume up (+) button and the power button at the same time until the stock recovery menu is shown.
Select option 2, "Software update via update.pkg on SD card," from the menu to go to ClockworkMod.
In ClockworkMod, use the volume buttons to navigate and the power button to select the following options: install zip from sdcard > choose zip from sdcard > choose .zip file from wherever it is on your card >Yes - install [name].zip > wait for installation to complete > reboot system now.
Click to expand...
Click to collapse
I downloaded the DJ Steve zip from this link: http://www.streaksmart.com/2011/03/mirror2.streakdroid.com/djsteve336.zip
When I first tried to install the zip, I couldn't find it on the sdcard. I found an ADB tutorial at: http://www.xda-developers.com/android/adb-easy-tutorial/ which had the following example of how to move a file from your desktop to the Streak: "adb push something.txt /sdcard/something.txt" so I used that structure to move djsteve336.zip to the Streak.
Once I had it on the sdcard and tried to install it again, it aborted and gave me an error that the file was bad, so I deleted the file from the Streak.
Since it was giving me an error on the file itself, I didn't want to try to run it a second time. Is there another source for the file or an updated version of the file that I need to find, or another option for the .zip?
If the file itself is not the problem, can you tell from the info above what I'm doing wrong?
Thanks!

I trully think is a bad dl! Try dlding again!
Sent from my HTC Glacier using XDA App

I second what KenpoAP said; your download mught have been corrupted. Also, no need to ADB push files to your Streak. When you plug the USB in, you'll have the option to mount your Streak as a data drive on your PC/Mac (you'll have the option in the pull-down, notification panel). Do that and simply drag/drop the file where you want it. It's very handy for organising folders, music, etc. as well.
If you don't have a file manager on your Streak 7, I recommend getting ES File Explorer. It's free, and it can explore and r/w everything if you're rooted.
Market Link
Good luck!

Customizing Your Bootanimation w/ A QUIETER Bootsound!

COMPREHENSIVE GUIDE​
I finally managed to get a BOOTSOUND working on my custom BOOTANIMATION last night, but then the real frustration came. IT WAS SO FREAKING LOUD!!! I spent all night and today researching on the net about this & even trying to implement my own code in the mix in an effort to thwart/bypass the issue, but to no avail. Android seemed to insist on blasting the mother & from what I read, it seemed like this was a real problem for a great MANY, most of whom eventually gave up. Who would've thought that the solution would be much easier than I'd imagined.
I know this issue has been solved for many phones out there in many different ways, but not all and for those of us, like me, who are running stubborn versions of Android that insist on running at MAX VOLUME every time you fire them up, then this is for you!
This Bootanimation With Sound Was Made With This Tutorial!
WHAT TO KNOW FIRST:
1) BEFORE DOING ANYTHING YOU NEED TO BACK UP YOUR NAND FIRST!!! It can be done with Clockwork Mod Recovery or EXT-4 Recovery. In case you mess up you will need this to recover your rom. I am not responsible if you brick your phone!!!
2) You will need "ROOT EXPLORER" from the Android Market to do this.
3) This tutorial is for ADVANCED USERS and is assuming that you have already successfully installed your bootanimation, which is usually called "bootanimation.zip". In my case, however, it was "htc_bootanimation.zip". It will be whatever your current bootanimation is called. Just rename the original to something like "bootanimation1.zip", in case you want to go back and use it again later. Then, copy your new .zip file with the proper bootanimation name into the proper folder. Mine was in "/data/local", but different versions of Android will keep them in different places. I think, for instance, Cyanogen Mod keeps it in "/system/media". You'll just have to do some research & if you don't have a bootanimation.zip file for your phone, just search XDA for bootanimations. There are tons on here.
4) I tested this on "dansta34's" Team Blue Droid V3.7 Sensation XL Gen3 EU & Tmobile SonyXloud rom, which is ANDROID v2.3.5 w/ SENSE 3.5..
http://forum.xda-developers.com/showthread.php?t=1275119
Alright! Once you've made sure your "bootanimation.zip" is in place & you've rebooted to see that it works, you are ready to go!
INSTALLING A QUIETER BOOTSOUND ON ANDROID:
1) Make sure you have already read & done everything above.
2) Download the "bootsnd.sh" file from the internet. There are lots of sources for this, so I'll just throw out a random link.
http://dl.dropbox.com/u/30200380/bootsnd.sh
Once you've downloaded it copy the file to the root of your sd card.(ie. "/sdcard")
3) Download or dig out the MP3 or WAV file that you would like to be the sound for your animation. Make sure it's not longer than like 30 seconds to a minute. Mine's about 1 minute, but that's only because that's how long my animation is & how long my rom generally takes to start up. Once you've downloaded it rename it to "android_audio.mp3" & then copy it to the root of your sd card as well.
4) Now, open the Root Explorer app from the Android Market. You may have to agree to allowing it SuperUser functions if you haven't opened it before. just click "ok" if that screen pops up. Make sure it says "Mounted as r/w" at the top. If not, click the "Mount R/W" button.
5) If you already know where your "android_audio.mp3" file is supposed to go, then go ahead and move it now, but if not, then we'll start with executing the "bootsnd.sh" file as the audio file location can be a bit complicated.
6) Everyone says to run "bootsnd.sh" through commands in "Terminal Emulator", but I think it is much easier to just execute it manually in Root Explorer. NOTE: If you want to do this, then skip to Step 7 now. If you must install it with "Terminal Emulator", however, then just run these commands in it and skip to Step 8:
su (then hit enter)
cd /sdcard (hit enter)
sh bootsnd.sh (hit enter)
If you get a "No Such User" error doing that last command, just ignore it. Don't run it again. The script has been written. We just need to fix some permissions later.
7) If you haven't executed "bootsnd.sh" yet, let's do it manually! Again, make sure it says "Mounted as r/w" at the top & scroll down to the "sdcard" folder in Root Explorer and click on it. Then, scroll down to the "bootsnd.sh" file. Press & hold on the file until a popup menu comes up. Select the option "Permissions" & click on all the boxes, except the "Special Permissions" ones, in the popup & click "OK". If it does not allow you to do this, then don't worry about it. We'll take care of this later. After that, just click(rather than press & hold) on the "bootsnd.sh" file to open it. The Script File menu should popup this time(3 buttons). Click on the Execute button. This is the same as running the "Terminal Emulator" commands above.
8) Now, lets just make sure we have the proper permissions. Move up a level from "/sdcard" to just "/" & navigate to "/system/etc". Look for the file "init.local.rc". Press and hold on this file & click "Permissions" on the popup menu. Again click all of the boxes except the "Special Permissions" ones if they're not already & click "OK". Then move up a level again to the "/system" folder & click on the "bin" folder. You should now be in "/system/bin". Look for the file called "bootsound". Press and hold on it and do the same. Click "Permissions" & check all the boxes except "Special Permissions" boxes & click "OK". Permissions are done. NOTE: If you already know which file your bootsound MP3 or WAV needs to be copied to then move to step 9 now. If not, you will need to do steps 9 & 10 later. Skip to step 11 for now.
9) EDITING THE "BOOTSOUND" FILE IN "/system/bin" TO POINT TO YOUR MP3 or WAV: Press and hold on the "bootsound" file. Scroll down in the popup Options menu & select "Open in Text Editor". You'll see a bunch of code. Don't worry about what it means. Just look for the part that says something like "/system/media/android_audio.mp3". If your file belongs in this folder, then you don't have to change anything. If not you will have to edit this part. I had to change mine to "/system/customize/resource/android_audio.mp3", for instance, as that's where my sound file is supposed to go. Once you have made your changes. Save the file by hitting "menu" button and selecting "Save Changes". This will put you back to "/system/bin".
10) Now let's move our audio file to the right place! Back out to just "/" again & then open the "sdcard" folder. Scroll down to your "android_audio.mp3" file. Press & hold on the file until the popup menu comes up. Select the option "Move" to move the file. Then, navigate to the proper folder for your sound file according to your rom or Android version and click "Paste". NOTE: Copy the file to the same folder you designated in step 9 & move on to step 12.
11) Now, where to move this file is tricky! I had to try many different folders...one by one...rebooting each time to see if the sound would play...to figure out which one was correct for my rom. It is usually the same folder as your "bootanimation.zip". In my rom I had 2 copies of "bootanimation.zip". One in "/data/local" & one in "/system/customize/resource". However, my bootsound only worked when placed in "/system/customize/resource". I did not have to change the bootanimation in this folder though, only the one in "/data/local", as the resource folder one is more of a backup. Anyhow, I think in Cyanogen Mod, it goes in "/system/media" & still others require that it be in "/data/local" and so on. You will have to do a search on bootsounds for your rom or Android version...or just post a question in your rom thread. Don't try to be smart like I did & put a copy in all of these folders. When I restarted it, it played multiple files at the same time, which made it LOUDER THAN EVER!!! If you don't know where it goes, you will have to try the different folders one by one and reboot each time to see if it plays. Make sure before you reboot that your phone is not on MUTE, as it may make a difference, depending upon which folder your "android_audio.mp3" is supposed to go in. For instance, the fact that mine goes in "/system/customize/resource" means that the bootsound is directly linked to my ringer volume in Android. ie. If I put the phone on mute before rebooting, the bootsound will not play. It's not like that for all roms, but it is for mine. NOTE: Once you think you've figured out which folder the bootsound is supposed to be in, you will need to go back and do steps 9 & 10 before proceeding to step 12.
12) Now that you've got your bootsound to play on your bootanimation, all the hard stuff is done. Now you just have to ask yourself one question. Was it too loud? Unfortunately, many Android versions & roms default the bootsound to MAX VOLUME & like I said earlier I tried tweaking the code for it in so many different ways, but it just kept on blasting.
SO, I CAME UP WITH TWO POSSIBLE SOLUTIONS FOR THOSE WHO HAVE BOOTSOUND VOLUME PROBLEMS.
As I mentioned briefly in step 11, due to my "android_audio.mp3" file being in the "/system/customize/resource" folder, the volume of my bootsound depends partly upon my ringer volume(same as system volume) level in Android. So, if I put my phone on low volume or mute & then reboot, it actually makes my bootsound at low volume or mute. I've also read that sometimes the notifications volume can affect bootsound files that are placed in "/system/media" as well. I don't think that this is very common, but you can try playing around with different volume levels to see if it makes a difference. If you find that this doesn't apply to you then I have another suggestion below.
After messing around with all that, however, I still thought my bootsound was really loud at times so I came up with another solution which was simple, but actually worked quite well. I used a sound editing program that I had on my computer. It had an option on there called "FADE", which allowed me to load a sound file and then lower its volume manually within the file. The program was called "Cyberlink Wave Editor", but I think it only comes bundled with other software. If you want to try this method though there are tons of programs at sites like DOWNLOAD.CNET.COM. Some are free. Some are trials. Just took a quick glance & saw that there's an awesome one on there called "WavePad Sound Editor", which is just like mine. It's just a trial program, but you only need it once really & then you can delete it. You can always just search GOOGLE too by typing in something like "sound editing software decrease volume" or something, but I know CNET is virus free stuff, so that's what I use.
Anyhow, I hope this wasn't too confusing & that it helped some of you!!! If so, please click the "Thanks" Button if you can!

Razr I XT890 bloat apps safe to remove from JB?

Hi,
Just wondering if anyone has tried and tested the removal of bloatware apps from their Razr I XT890 running 4.12?
I'd be interested in cleaning the phone up a bit just to make it less crowded, I like to use real calc instead of stock calculator, go sms instead of stock messaging, zeam launcher instead of stock launcher etc etc.
I'm quite a novice when it comes to the technical side of things so would be too afraid to start deleting system apps incase they messed something up.
If anyone has seen a list compiled and could share, that would be great. Also, would it be Razr I specific, or would a general 4.12 safe removal list be safe to follow?
Any feedback appreciated

Here you can find answers.: http://forum.xda-developers.com/showthread.php?t=2223482
Read the forum.
Sent from my XT890.

Thanks a lot, have you any idea what to do with them zip files and how can I keep some of the google apps in the list? I'm not sure where to put the #?

cormie said:
Thanks a lot, have you any idea what to do with them zip files and how can I keep some of the google apps in the list? I'm not sure where to put the #?
Click to expand...
Click to collapse
I think that for you would be easier use Titanium Backup or SystemAppRemover (need root acces) to remove apps.
If you want use the zip file you have to unlock bootloader and flash CWM. In CWM you can install zip files. # you must put in front of the line where is written desired app. Updater-script you can fing in the zip file /META-INF/com/google/android/

Thanks again, I actually have my phone rooted and was able to apply the debloater, however I don't want to remove everything so will restore the backup I took before trying it, I tried install the zip file with the edited script (with the # in front of the ones I wanted to keep) but it failed to install via recovery so I must be doing it wrong
I extracted the script file, opened with wordpad, edited, closed and saved, put it uncompressed back into the zip and tried it.
that failed, so I tried open directly from the zip, edit, close and save and flash that too but that failed too the original unedited one doesn't fail.
The error I get is something referring to error in zip file.

cormie said:
I extracted the script file, opened with wordpad, edited
Click to expand...
Click to collapse
Do not use WordPad. Edify scripts require line endings to be linux style (LF only). Wordpad converts them to windows style (CR LF). Use another editor; I recommend notepad2-mod (set syntax highlighting, F12, to shell script)

See I edited and saved in wordpad and wasn't prompted to save in any other format, do you think it still saved in CR LF?
In the same script and another edit, I think I pasted something from somewhere else and went to save, but then it prompted me to save in the wordpad format itself (rtf I think it was) which I didn't, when I simply added a # or two, it just prompted to save without asking for format so it appeared to save as it was and not change anything? So you reckon it still changed it to the non-readable CRLF?
Would basic windows notepad be ok to edit it instead of having to download notepad 2?
Thanks for tyour help so far!

Maybe I'd be better just doing this via root explorer, of which I have some experience of. Is it just a case of locating each of the files listed in the script and deleting them or is there other hidden crap elsewhere that the script gets rid of which a simple root explorer delete won't?

cormie said:
See I edited and saved in wordpad and wasn't prompted to save in any other format, do you think it still saved in CR LF?
In the same script and another edit, I think I pasted something from somewhere else and went to save, but then it prompted me to save in the wordpad format itself (rtf I think it was) which I didn't, when I simply added a # or two, it just prompted to save without asking for format so it appeared to save as it was and not change anything? So you reckon it still changed it to the non-readable CRLF?
Would basic windows notepad be ok to edit it instead of having to download notepad 2?
Thanks for tyour help so far!
Click to expand...
Click to collapse
Try notepad++

Verizon Security Update for VS980 pushed out today 11/2/15

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.

Non existant file transfers only to "Download" folder. other folders are fine.

Non existant file transfers only to "Download" folder. other folders are fine.
Background: I used TWRP to completely wipe my Nexus 6. Through Windows I made a folder called "Download" and put my ROM and SuperSU in there which transferred fine. Installed ElementalX 3.0.
Now when I transfer files from my PC to the Download directory, I just get a moving bar and the files never actually transfer. I have only waited about 5 minutes then gave up. Once I cancel the transfer, Windows loses connection with the phone and I have to re-plug the USB cable in. The problem only occurs when I try to transfer to the Download directory. I can transfer files from my computer to any other folder of the phone with no problems. I also cannot delete the Download directory using Windows Explorer, and two file manager programs on the phone called File Manager, and ES Explorer. The Download directory also has two files, SuperSU and ElementalX, which cannot be deleted. It's not a major issue, but it's bugging me.
Oh, my Android skill level is novice wannabe so be gentle with the big fancy words. However, after a few short hours of owning the phone I did figure out how to ROOT and install a custom ROM, so I ain't totally stupid - just mostly.

check the file permissions on those files and the folder, ES Explorer can likely do that I don't use ES but I know its well featured. Its the only thing I could think of off the top of my head.

Bigwaverider said:
Background: I used TWRP to completely wipe my Nexus 6. Through Windows I made a folder called "Download" and put my ROM and SuperSU in there which transferred fine. Installed ElementalX 3.0.
Now when I transfer files from my PC to the Download directory, I just get a moving bar and the files never actually transfer. I have only waited about 5 minutes then gave up. Once I cancel the transfer, Windows loses connection with the phone and I have to re-plug the USB cable in. The problem only occurs when I try to transfer to the Download directory. I can transfer files from my computer to any other folder of the phone with no problems. I also cannot delete the Download directory using Windows Explorer, and two file manager programs on the phone called File Manager, and ES Explorer. The Download directory also has two files, SuperSU and ElementalX, which cannot be deleted. It's not a major issue, but it's bugging me.
Oh, my Android skill level is novice wannabe so be gentle with the big fancy words. However, after a few short hours of owning the phone I did figure out how to ROOT and install a custom ROM, so I ain't totally stupid - just mostly.
Click to expand...
Click to collapse
Reboot into recovery. Go to advanced, file manager. Browse to that Downloads folder, hit select, then choose delete.
Should get rid of it for you.
I'm assuming that you made the Downloads folder originally through TWRP while it was connected as an MTP device? If so, sometimes it can do weird things while in recovery. While the MTP driver works in TWRP, it's not extremely mature and is really just there as a convenience for folks that aren't comfortable with the standard command line stuff.

StykerB said:
check the file permissions on those files and the folder, ES Explorer can likely do that I don't use ES but I know its well featured. Its the only thing I could think of off the top of my head.
Click to expand...
Click to collapse
Thanks man. That sorta worked. There was a section in ES where I could change all permissions to RW. I don't know if that effected things but after I did that I renamed the Download folder to Downloads with an 's'. I was able to recreate another Download directory and now I can download stuff from the net as I wasn't able to with the old Download directory. This seemed like a patch but at least things were better. However, I then read Yoinx's post and it worked and complete got rid of the bad folder.
Yoinx said:
Reboot into recovery. Go to advanced, file manager. Browse to that Downloads folder, hit select, then choose delete.
Should get rid of it for you.
I'm assuming that you made the Downloads folder originally through TWRP while it was connected as an MTP device? If so, sometimes it can do weird things while in recovery. While the MTP driver works in TWRP, it's not extremely mature and is really just there as a convenience for folks that aren't comfortable with the standard command line stuff.
Click to expand...
Click to collapse
You sir are a bloody genius. Worked like a charm.
I am going to explain this as well as I can. When I wiped everything with TWRP (I didn't mean to. It was just a noob mistake) I was no longer able to see my phone's files on my computer. If I am not mistaken, it did show the phone hooked up, but no files, or even "internal storage" were showing - I could be wrong. I needed to copy SuperSU and the ElementalX ROM from my computer to my phone but I was screwed. I fiddled about in TWRP, and I believe it was under "Mount" where I was able to check/tick all the folders that were unchecked. I am assuming since they were unchecked, Windows could not see the files on my phone. After checking/ticking the folders, I hooked the phone up to the PC and the N6 showed up. I made the Download directory in Windows and copied the ROM and SuperSU that way.
Also, I don't even know what an MTP device is. Maybe I did what you said as I was sort of clicking here and there to see if this or that would work. I was in semi panic mode so I don't remember every single thing I did. Anyways brother thank you so much for your help. Here's some nice delicious Hawaiian pineapple for ya. E lauhoe mai na wa’a i ke ka i ka hoe i ka hoe i ke ka pae aku i ka ‘aina
**Oops I can't post pics yet. Insert pineapple.jpg here.