Database Info

GB Sd card fix

according to Tom Gray, who's leaked fixed files I'll post later, to fix the sd card issue, remove autorun.iso from the /system/etc/ folder asap. it embeds itself in the sdcard and does some strange things.
just passing it along. will post newest gb leaked fixed files in the am when they are released on fb, unless someone beats me to it.

Am I first?
Sent from my SCH-I500 using XDA App

Autorun.iso is a CD image file that executes in Windows. When the phone is connected to your PC and it shows up as a CD drive in Windows Explorer, this file is responsible for that. As I understand, Verizon purposely designed their stock (bloatware/Bing) ROM so that your phone would show up as a CD drive when connected to your PC, unless you install a special program they provide for file transfer. If I'm right, this means that the stock EC09 leak would come with this file, and anyone building a custom ROM based on this leak would have to remove this file from the stock ROM.
Another Fascinating post by my XDA app...

Ima kinda a noob at this so um how do i get there and remove it? Do i use like astro file manager to get there? cause i tried finding it yesterday and couldnt find it.

Actually based on the other thread in fascinate development the sd issue may be associated with the rooting meathod. You may wanna check that thread out before deleting anything. Not saying that isn't the issue but seems more has developed since this was first brought up for discussion.
Tap-a-Talked from my Mesmerize

[Q] what is the new update??

sorry for posting new thread but I don't know where to ask...can anybody please tell me tge new update 4.5.269 and someting3..is it the new version of gingerbread,is it safe to update..please tell me...

The new update is 4.5.629. It goes from Gingerbread 2.3.3 to Gingerbread 2.3.4, so a slight update. There are a few bug fixes, but it has a number of undesirable things.
1) 4.5.629 is currently not rootable
2) You cannot simply return to an earlier version via SBF.
You can overcome the first by using Voodoo Rootkeeper or similar to root on your current version, back up root with Rootkeeper and then update.
Recently, a method was found for this release to unbrick phones damaged by attempts to SBF or from bad ROMs: http://rootzwiki.com/topic/23207-how-to-sbf-unbricking-root-d2g-629 This also allows users who did upgrade to 4.5.629 to return to the previous version, root there and then upgrade again.
So it is sort of safe, but not ideal. The changelog is here, decide if the bug fixes are important enough for the added inconvenience
http://support.verizonwireless.com/pdf/system_update/droid_2_global.pdf

ok...thank u very much +1..I prefer not to update for now,and by mistake ,i select yes button in the update prompt,and its in the pull down bar,stucked and is ready to start downloading as soon as I connect to wi-fi,how will I cancel the download

You can block the update by renaming these files (e.g., append ".bak" to each filename):
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
Since these are in /system, renaming them requires root privileges and a root-enabled file manager (such as Root Browser Lite, available in the Google Play store).

ok..thanks,will do that,but after doing that,will I be able ro manually update it,or all the updates have been blocked???

Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.

jabberwockish said:
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
Click to expand...
Click to collapse
okok..thanks man +1
edit : i got this 'failed to rename file' error ..what should I do??

What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)

jabberwockish said:
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
Click to expand...
Click to collapse
the app that u suggested me,root browser lite and my phone was rooted and also have been granted superuser's permissions..

You didn't remount /system in Read/Write mode.

Gasai Yuno said:
You didn't remount /system in Read/Write mode.
Click to expand...
Click to collapse
please tell me how to do that

Root Explorer has a button for that.
“adb remount” when connected to a PC with USB debugging enabled will do that as well.
It's also possible to do from the terminal emulator, however I don't remember the exact command.

i can't find that button,by long pressing the file/folder or what?

It looks like this app defaults to RW once it gets superuser permission (GY was referring to Root Explorer, a different app). How about copying a system file, does that work?

[solved] crashing accessibility app

To the Admins, I'm not entirely sure where you guys would want this thread...troubleshooting seemed to be the most sensible.
all right everyone, I'll explain here how I fixed this, but keep in mind I have the ATT LG G2 running KitKat with TWRP 2.7.0.0 and I'm rooted. I only recommend this for advanced users. If you aren't an advanced user, well, make sure you have a backup. I'm sure there was a faster way to fix this, but my goal wasn't to find the fastest way initially, it was to find a working way. For example, you could just ADB everything. You could also, assuming you know how to use your OS to search that deep into the device files, done a rename, copy/paste etc. etc. Not all devices are made equal, so be CAREFUL! BTW, I was in debugging mode + charge only.
WARNING: I AM ONLY OFFERING THIS FOR INSIGHT TO ADVANCED USERS THAT KNOW WHAT THEY ARE DOING - I DON'T OFFICIALLY RECOMMEND THAT ANYONE DO THIS. I AM NOT RESPONSIBLE FOR ANY TRANSMUTATION FROM LG G2 TO BRICK.
Here's what I did:
1) I opened accessibility while hooked up to the debugger in Android Studio to see that it was producing a Null Pointer Exception.
2) I have a slightly modified version of the TOT file so that I can run TWRP and still be rooted in KitKat.
3) I am rooted, so I used Root Explorer to search for accessibility and found that the file is called "LGSettingsAccessibility.apk" and .odex - it's under (WITH ROOT ONLY) /system/priv-app/
4) I searched for a system dump copy online...I found this site: http://hunterspad.com/Domains/StorageCow/Xda/Users/garyd9/Extracted System/priv-app/
I found that by typing "LGSettingsAccessibility.apk" and initially found a Google Drive version but it was posted in September of 2013 - unlikely to be the odex and apk from KitKat hahaha. I used a Google Search that searched custom range between Feb 1st and today. I found 2 links, one of which is the above.
NOTE: I don't recommend anyone do the following unless you KNOW what you are doing and definitely have a backup to restore to if things go wrong
5) I sent the link for each file to myself on Google Hangouts. I used Hangouts to download the March 14th upload of the LGAccessibilitySettings.apk and LGAcessibility.odex
5.5) I copied each of the original files (.apk and .odex) from /system/priv-app/ to my /sdcard/LGBackup folder I created using the Root Explorer app.
6) I went into the app "Root Explorer" again after downloading both files (DID NOT INSTALL IT, though it probably won't let you anyway). I checked both files and copied them.
7) I went back to /system/priv-app/ and renamed the existing files to be replaced with the extension ".bak" so that the system no longer points to those files (NOTE: Root Explorer asked me to remount as R/W (read and write vs. read-only) a good feature of root explorer to be in read-only by default; dangerous territory.
8) Bottom right corner of Root Explorer it was waiting for me to "Copy Here" when arriving at the location where I wanted to copy the files: /system/priv-app/ and after copying them I decided to be a fool and install the apk and it told me something like "app not found" or something.
9) FINALLY went into Settings and touched Accessibility and VOILA! It worked! A lot of luck involved - the odexed and apk files may not have been the proper version. I could have checked with relative ease (though likely time-consuming) by using some of my android dev skills/utilities.
WARNING: I AM ONLY RECOMMENDING THIS FOR ADVANCED USERS THAT KNOW WHAT THEY ARE DOING.
Thanks to garyd9 on XDA - without your uploaded files on storage cow, I couldn't have fixed this problem!

i have deleted xbin folder in system/xbin path

Please Help I have deleted xbin folder in system/xbin in my samsung gts5303 and now i want to again root my samsung gts5303 but it is not rooting now.Firstly i have rooted it with Root Master android app but now when i m trying to reroot it with Root Master app it shows Sucessfully Rooted and also installs supersu app but not installs binary becouse binary is installed in system/xbin folder and i have deleted it.
and an unknown folder sbin is added in /sbin. and it is empty i have no root acess but when i m deleting it it is sucessfully deleted but when i comeback to / path it is added again
Now i m requesting you to please solve this problem and give me any app by which i can add xbin folder again in system/ with out root.and with out pc because i have not any pc...
thanks in advnce...

I hope you have a nandroid back up, otherwise it is going to be really hard to do with out a PC handy.

You will not be able to add File or folder in system even 3rd party app will not be able to write on system folder without root permission so try to full unroot the phone then again try to root so there is a chance of reinstalling binary again anyway don't you have nandroid backup?

how can i do nandroid backup
justmpm said:
I hope you have a nandroid back up, otherwise it is going to be really hard to do with out a PC handy.
Click to expand...
Click to collapse
what is nandroid backup how can i do this.

CWM for gts5303
please give me any CWM for my samsung gts5303 by which i can flash a .zip file to install binary again. thanks

i have also deleted all files in /sbin folder
And i have deleted all files in/sbin folder can it be a cause for not rooting .or deleting system/xbin folder.

I Have find out the solution of this Problem
Good News for all who are suffering from this problem.If you want to get rid from this problem by simply installing an .apk file then contact me on My Whatsapp
919622506468
EMail: [email protected]
Or If You want a simple .apk file to root your device (for all phones) then contact me now. hurry!

you need reup rom for your device

I Have Findout The Solution Of This Problem (MySELF)
I Have Foundout It's Solution By My Self. I Haven't got any Best solution for this problrm in Xda Or Google. But I Myself Had Fixed this problem. So I Only want the Users who Have This problem in their phone would Get rid from this problem they have to done nothing. They Only have to install a simple android app of about 2mb (No Need of Pc Or Anything etc) So, Contact Me To Get its Simple (OIS) OneInstallSollution By HackerRM
Whatsapp/Phone : +919622506468
EMail : [email protected]
Thanks...
[Any Problem On Any Device]
Get Simple (OneClick) Solution.
[ONLY WITH HackerRM]

Looking for dir of ota files

Does anyone know what dir the ota files are downloaded too? I would like to capture the ota and see whats in there.

TheJokah said:
Does anyone know what dir the ota files are downloaded too? I would like to capture the ota and see whats in there.
Click to expand...
Click to collapse
I did it earlier, have to be rooted to see the file that's downloaded. If you're using a root explorer search for "dlpkgfile" that's the name of the newest OTA at least, I made a copy on my SD card so I could keep putting it in the right dir and avoid downloading it all over again. Since I tried all my options i'm back to unrooted, still can't upgrade from g to o.
I don't remember the exact directory, somewhere in /etc/ if I recall.

ajent said:
I did it earlier, have to be rooted to see the file that's downloaded. If you're using a root explorer search for "dlpkgfile" that's the name of the newest OTA at least, I made a copy on my SD card so I could keep putting it in the right dir and avoid downloading it all over again. Since I tried all my options i'm back to unrooted, still can't upgrade from g to o.
I don't remember the exact directory, somewhere in /etc/ if I recall.
Click to expand...
Click to collapse
I'm having the same issue with upgrading 10G. maybe there is a way in the ota Package
EDIT:
I found this link http://forum.xda-developers.com/showthread.php?t=2699123 to force an update using the dlpkgfile from ota. I wonder if it could work for G4 also??

@TheJokah @ajent. Don't need to be rooted. Root Browser will be able to view the directory without root permissions. (I use it all the time to browse system partitions and files on unrooted devices). You can do a lot with Root Browser without root. You just can't make changes.
When the fota is available you will find it in /cache/fota
I have captured several OTAs for various devices this way...
EDIT: Make sure to copy the file after it downloads and before restart, otherwise the file will be deleted before you get it.

That is good info, thanks.
I'm pretty convinced flashfire installing the xposed zip does something that isn't reverted when flashing the unrooted system image. I used my limited knowledge to look at that xposed zip and it seems like only modifications are made to /system so it should be removed when flashing back unrooted image. I really don't know, but hope somebody can figure it out lol.