yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] ericgl:
Better solution

First I should note that I'm using the LG G2 D802 32GB model, I have the 4.4.2 KitKat stock ROM, I have root, but I haven't installed a custom recovery.

I accidentally changed the permissions on the build.prop file in the system folder, and after reboot, my phone was stuck in a boot loop.

I searched a lot online for a good fix that wouldn't involve losing the information and apps that I have installed on it. And I managed to do it :).

I believe this is a better solution than what the OP suggests, and is more user-friendly.

So, in case your LG G2 is stuck in a boot loop with LED flashing green-cyan:

=========================================================

1. Enter Download mode:

A. Turn off your LG G2 completely, if possible. If not, try to time yourself by pressing & holding the power button on the back and then immediately after it turns off and back on again:

B. Hold Volume Up + Insert a microUSB cable in to your phone (the other end should already be attached to your PC).

You should see a blue rectangle, and then the phone will display that it's waiting for a FW update with 0% on the bar.

2. Download & Install the official "LG Mobile Support Tool". The actual filename is B2CAppSetup.exe (256KB).

Run it (there should be a shortcut on the desktop) but give it time, as this app is very slow to load even on a fast machine.

3. Click Options -> Upgrade Recovery. Wait after pressing the button, app is very slow!!!

4. Sit back and relax until it's done (around 10-15 minutes).

In this step, it downloads the latest official KDZ file directly from LG (around 2GB), and re-installs it on your phone.

5. Phone should boot normally with all your settings intact.

6. Note: Closing the "LG Mobile Support Tool" also takes a bit of time, and might even give an error that "the application has stopped working".

This is normal and you can safely ignore it. Simply close the error window and be done with it.

7. You will need to root your phone again using ioRoot (latest version dated 2014-06-17).
[G2 Q&A, Help & Troubleshooting] TheCelestial:
Hi! Thank you for such a detailed walkthrough. However, my AT&T LG G2 D800 doesn't go past the LG Logo, though, I'm able to enter Recovery Mode and Download Mode. I just want to ask, is there any way to know my mobile's accurate Serial Number and Model Number without entering into Settings Mode since I cannot turn on my device? Upgrade Recovery option needs it. Thank you!
[G2 Q&A, Help & Troubleshooting] ericgl:
Not sure what you mean by "Upgrade Recovery option needs it", but if you have the original retail box, there's a sticker on it with the IMEI and exact model number. There might be an option to get this info from the phone itself in one of the recovery/download/whatever modes, but I haven't tried.
[G2 Q&A, Help & Troubleshooting] TheCelestial:
@ericgl: Thank you for the response! LG Support Tool requires you to enter either Model Number and Serial Number of your device or the IMEI Number. And since I bought a used phone (without box), I couldn't find the IMEI Number anywhere. Anyways, I opened up the phone's back cover and it was there. I ended up fixing my device using OP's tutorial since LG Support Tool keeps on crashing on Windows 7 32-bit. Still, huge thanks for the method!:)
[G2 Q&A, Help & Troubleshooting] ndiri:
any help will be much appreciated

my problem is i cannot go into recovery mode, i guess i flashed a wrong custom recovery before and the phone just boots and says verizon but never goes pass this point. i am not using a verizon version though, i am using lg g2 802, my other problem is i do not know which firmwares to use because they are from different countries and all that, some be it 802a 802b and all that, so how can i tell which one is for my phone? i have the imei number and i bought the phone second hand still broken and trying to fix it myself. is there any universal firmware for lg g2 802? working on all phones?

---------- Post added at 07:04 AM ---------- Previous post was at 07:02 AM ----------

and i cannot download the dll file on the OP's post, when i click download nothing happens, please my facebook name is Lawrence Handly, anyone who knows much about this and willing to help can inbox me anytime, please
[G2 Q&A, Help & Troubleshooting] SapoPT:
Did this and worked, It took 40 minutes the complete process but got my device back. Thanks
[8125, K-JAM, P4300, MDA Vario General] GerooTech:
when i was using magician i was able to select to synchronize active tasks only or all tasks, but after i have upgraded to the wizard i can not find this option can anybody help me doing this.
[One (M7) Q&A, Help & Troubleshooting] rm83855:
Ok so has anyone experienced the keyboard overlapping the text input field when using the browser so that you can't see what your typing? It also doesn't let you scroll the screen either... I have found a few things on other forums which require you to edit manifest files etc but surely this issue still isn't a widespread android issue, please correct me if I'm wrong?
[Galaxy S III Q&A, Help & Troubleshooting] 9anas:
hi guys;

i'm new in this forum, i came here to get some help please,

i need to flash my galaxy s III i9300 with the [ROM] Amestris BlackDiamond V5.0 |ODEX, but i can't find it in the net, the web site where it was is now down so anyone have it please upload it for me and thankyou so much.
[Galaxy S III Q&A, Help & Troubleshooting] MIKEMON:
http://xdaforums.com/galaxy-s3/development/rom-amestris-blackdiamond-v5-0-odex-t2162618

thread here, but writing in a different section
[Galaxy S III Q&A, Help & Troubleshooting] 9anas:
thanks

thanks for your answer, i'm sorry i can't write any thing on that thread that's why i wrote it here if anyone can help me please i need it.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] lnkGO:
Hello, sorry if I'm in the wrong forum, I'm new to XDA and rooting android devices in general.

I have a Samsung Galaxy Tab GT-P7500 (has both Wi-Fi and 3G on the back) and I tried to root it using this tutorial (http://xdaforums.com/showthread.php?t=1239185). I followed it exactly except for a part where you're supposed to launch odin 3 1.85. Trying to run that program would just give me some korean letters and it would exit after closing the korean letters. I downloaded Odin 3 v3.04 thinking that the version doesn't matter. Ran all things fine, finished the tutorial and the ClockWord mod or w/e said root finished. After that I couldn't access the system root folder to change some permissions. I downloaded an app to check if my device is rooted and it says that it's not. Now when I try to access those two options (holding power button + volume down button) they don't even come up and I just keep seeing the galaxy tab logo when holding that combination. Other than that, the tablet works fine.

What do I do now? How do I get the recovery and download modes back? Help would be greatly appreciated, plz!!! :angel:

EDIT: I also have some kind of Superuser app that the process installed for me.

EDIT2: Apparently I can access recovery and download mode! What do I do now? (I have ClockworkMod Recovery v4.0.0.4)

Final Edit ( I hope): I fixed it!. I installed (flashed) Superuser from the ClockworkMod Recovery and now it says that I am rooted. :D
[Security Discussion] kbntk:
Hello,

I think about rooting my device.

However I also think about how secure the custom roms builds or rooting apps are.

E.g.

In the modaco forum there is a tool called Superboot r2 to root the motorola moto g device.

How can I know/trust that this tool doesn't contain any spyware/malware or other malicous code?

How do you guys look at the security of custom roms and other apps which root your device?
[Security Discussion] Elzbach:
Customizing and rooting one's phone can be done very securely. Even more now than a few years ago. I would be wary about apps that can root your phone with a buttoon press. Unless, of course, there is a really long thread about it on xda. The same with apps not from the Google store. You should run a virus scan on any apks you get in general. They can contain malicious code that can mess up your device and steal your information.

Once you root your device, it's a good idea to look into the XPrivacy app. You can use it to control the individual permissions of all of your installed app. There are a lot of other security measure you can take too. Do research on what would be relevant to your device.
[Security Discussion] jcase:
Rooting a device greatly decreased the overall security of the device. You are breaking the basic security design of Android, you are incorporating new code (mods etc) from developers who may not be properly trained, many who jsut copy past code from elsewhere without understanding what exactly is going on. Potentially (almost certainly with most custom roms) introducing new vulnerabilities.

I'm going to have to flat out disagree. Once you have rooted your device, security has greatly been decreased. What would be a minor vulnerability in a normal app, can become a huge vulnerability in an application that has been granted permission to use root. Same goes for the Superuser control application.
[Security Discussion] kbntk:
Thank you for your replies guys.

I agree rooding the device decreases the overall secruity of the device.

On the other hand, rooting the device gives access to the apps that give you control over the system and data on it. For example as Elzbach wrote, with the app XPrivacy I can control what apps have access to my personal information.

Now - without root - when I instal a new keyboard or launcher with widgets, I'm warned that these apps can have access to my personal information and can use them malicously. For me that means, that even without root using normal apps I can get big security risk when using some apps from play store.

Do you build the custom android version by yourself from the source or use builds provided on this forum or modaco or use another way?
[Security Discussion] jcase:
XPrivacy, and apps like them introduce additional security concerns of their own. Android is not designed to work the way they force it too, introducing many new unknowns.

New keyboard, launchers introduce an infinitely smaller risk than any root app, and unlike with root apps you are warned and privileges are handled by an established well tested permission system. Comparing the two is completely silly.

Any developer, in a matter of minutes, put together a root app requesting 0 permissions, that can gain permissions or otherwise use APIs requiring permissions at runtime without declaring them, and disable or work around any "security" any XPrivacy type app claims to provide. Once rooted, apps like XPrivacy provide a complete false sense of security. Given you need root to use them... they provide no real security at all.

A completely valid scenario (one we have seen in the wild): An app with 0 permissions, but the ability to use su could download and dynamically execute new code to perform the malicious activities. IE Google bouncer, and any anti virus software would be @#$@ out of luck on that one. All because a user decided to completely break the basic security model, by installing su.

The only customized version of Android I use, is a customized emulator I use for analysis, and that only used when I suspect something could damage an actual test device.

I do not mess with customized versions of Android on real hardware, I only build when testing patches I plan to push to the AOSP gerrit for review.
[Security Discussion] Elzbach:
Well I stand corrected.
[Security Discussion] Kayak83:
Apologize if I'm resurrecting an oldie but this is a topic I've been contemplating for a while now. I used to root, looking back to my old OG Droid days. But I find newer devices sufficient as to not root anymore (mostly). I'm currently debating rooting a Samsung Tab S 8.4 to remove Touchwiz and hopefully speed some things up and maybe further control the CPU.

If the user is rooted and they only install apps from the marketplace that are known to be safe (I assume)- i.e.- not downloaded from some misc internet site and from "non-trusted sources," would this still be able to happen?

- "Any developer, in a matter of minutes, put together a root app requesting 0 permissions, that can gain permissions or otherwise use APIs requiring permissions at runtime without declaring them, and disable or work around any "security" any XPrivacy type app claims to provide. Once rooted, apps like XPrivacy provide a complete false sense of security. Given you need root to use them... they provide no real security at all."

I guess I'm just not sure how google approved apps, or if they even do. And what's the process of showing app permissions in the Play Store these days, since permissions are front and center when you download an app. Do dev's just flag permissions on their own will or is it built into the Android code? I would ASSUME the android code when posting to Play Store decides permissions for the dev. I would be horrified if Android relied on good will for people to post permissions solely from the dev's input.
[Security Discussion] nutpants:
I could be completely wrong

But as I understand dev a pick the permissions they need for the app to work correctly. They declare the permissions they need to the Android system. And then they can only use those permissions and no others. However they don't need to use all of the permissions but they can if they want to.

Btw apps from google play are in no way safe.it has no bearing if you do or don't have apps from unknown sources on your device. fact is google in no way checks the source code of apps on the play store.now maybe the run a virus checks but honestly that means nothing as moron could code in malicious code that would not trigger a scanner (and Trojans are far more prevalent for Android than viruses). If the source code is not available then no one knows what an app could be doing.

90% of my apps come from fdroid, who builds everything from source.

In the discussion above I should also note (but could be wrong about this completely) that system apps (the ones that come with your phone) all have root(administrator) permissions by virtue of being system components.

So rooting may decrease your security but personally I think factory roms are far too unsecure to start with and will never have a device that is not rooted. The benefits far out weight the risks for the careful user. Until such time as the source code is released.

Unless you trust google, face book, Samsung, Twitter, and a host of other baked in developers who get to put apps on your phone at the factory.

Or Apple who has their own way of making money off your every move, or microsoft with win 10 that also sells your habits.
[Security Discussion] Semseddin:
This alone is enough for me to stay away from root and its capability to make things worse in my end. Thank you for the professional input on this. :cowboy:
[Security Discussion] nutpants:
Without root you can't add any security to Android. Which has very little security to start with. Permissions are vague and can't be denied on a per app basis short of not installing the app.

System apps have no way of being removed without root unless you do it before flashing, and without root you can't do a complete backup of your system.

Even if you don't root a device yourself Trojans can gain root with many of the same exploits, root themselves and cause whatever havoc they desire.

An app only gets root if you allow it even after rooting your device. It will pop up and ask you if you want to allow or deny or always allow or deny. a Trojan that can create root will do can do it regardless if you root your device yourself, I have no idea if such a Trojan tried to get root if supersu, or superuser will pop up and ask.

A firewall requires root and that alone is worth rooting for me.

But then I have very few apps that I allow online.

Can root cause serious damage to your device? Yes

Can you administrator your device without root? No

Every Linux has root capabilities,

if you own it you should be able to administer it to the best of your abilities and to do that you need root.

Custom Roms are updated far more often that oem roms and as such generally have the newest fixes and updates for security.come that to factory roms that may update once or twice in their expected lifetime, regardless of how many security holes are found in the rom.older devices(read older as a synonym for 2 years old) may never get another update and the only way to protect yourself with out a custom Rom is to buy a new device.

For example Android 5.01 has a major memory leak.and even with that and other bugs and security issues Samsung had not updated the north American galaxy s5 (just over a year old,) above 5.01 yet and may not until marshmallow comes out (Which will mean almost a year after the security and memory leak were found). And until then you walk around using a device with major security issues and a major memory leak.
[Security Discussion] Primokorn:
XPrivacy is not about Security. "Security" is never linked to Xprivacy on Github. "XPrivacy can prevent applications from leaking privacy-sensitive data". Saying the opposite is a lie.

Whether you have root access or not you can almost do nothing against serious attacks BUT having root access allows you to control some things like Internet connection, restricted access,...

Finally do not confuse Custom ROMs and Root. You can run a custom rom without root and vice versa. As explained above custom ROMs are more updated so you can enjoy more patches and new security features like SElinux.

Go to F-Droid or fossdroid instead of Google Play to avoid crappy apps and unwanted connections. Apps on F-Droid are safer. Google has an automatic system to scan apks when they are uploaded but it doesn't detect everything... Be sure that if you didn't update the version number of your apk you will be blocked though lol

Permissions are stored in the AndroidManifest.xml. If the developer doesn't want to state the permissions he needs then nothing will be shown into the Manifest. That's why it's important to use 3rd party apps to control what apps really do.
[Security Discussion] Andy1767:
Would never use my phone without a firewall installed. I want to have control over what apps can access the net and which cannot.

So rooting is a must for me.

Have no gapps installed and privacy is important to me.
[Security Discussion] optimumpro:
And you'll be 100% wrong. You are getting a bad advice from someone who sounds like he works for Google. He is wrong and he knows it...

Your system apps have root whether you like it or not. So, they can do whatever Google wants them to do. And they can do it silently. So, the question is are you going to have control over your device or google? Without root you can't; with root you can if you know what you are doing. Your main security threat comes from Gapps and the infamous google services framework, which spies on you and regularly transmits home (google servers) your every activity. That has to go and for that you need root. Custom rom vs stock. Custom roms don't have Gapps and gsf, so that puts them on pedestal, as compared to stock. Stock rom is android plus manufacturer's bloat which also spies on you and wastes battery. Custom roms don't have gapps and they are open source (like Linux). Have you ever heard about viruses on Linux? Maybe 2 or 3, but thousands in other OSs. As another user noted, linux (on which android is based) has root. So is any major OS. Root is just a key to control your device. It can be set up to restrict everything, even system apps, so the point that having root reduces security is invalid except for one situation, when you don't know what you are doing. Do you want incompetent and malicious evil Google to own your phone? If you do, stay away from root.
[Security Discussion] Semseddin:
Thank you for your detailed answer but if i am not mistaken, are you suggesting that a custom rom made by a 3rd party hobbiest developer is more secure than oem's firmware ? If so, i will continue to be mistaken.
[Security Discussion] optimumpro:
Most of the time the answer is yes. Also, you could be a developer yourself meaning you can compile your rom from sources with your own modifications. OEMs have user's security on the back burner. Their goal is to monetize the user and in case of mobile devices, there is no way to monetize the user without compromising security. The beauty of a published source code is that anyone could examine it and they do (even if it is not you yourself). Look at businesses: the majority of them use neither windows nor apple. They use Linux, because linux does not monetize the user and it is open sources and by the way, it is maintained by "hobbiest" developers. And naturally, because of this Linux has a vastly superior security and virtually no viruses.

Google is malicious and incompetent, but luckily, Android is based on linux and most of the code there is from linux.

This is of course a separate from root issue, which remains simply an issue of control: whether you want to be in control of your device or not. You can't name any OS that does not provide root to the user out of the box... Just because some (or most) smart phone dumb users don't know what they are doing does not mean that everyone should be denied root on their devices... And by the way, most Google engineers also don't know what they are doing and had it not been for Linux and the community at large, google wouldn't be able to produce anything that moves...
[Android Q&A, Help & Troubleshooting] ibo46:
Hardware : MT6572

Model : GT-I9500

Build number : ALPS.JB3.MP.V1.2

Build date UTC : 20130925-054250

Android v : 4.2.2

Baseband v: MOLY.WR8.W1315.MD.WG.MP.V2, 2013/06/13 16:08

Kernel v : 3.4.5 (soft02@cc-desktop) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Wed Sep 25 13:40:00 CST 2013

Uboot build v : -----

LCD Driver IC : 1-otm9601a_qhd_vdo_dsi2

PLEASE VOLCONE BOX FLASH HEP ME
[Android Q&A, Help & Troubleshooting] DarkFrenzy:
hahahaha its time to bury....:crying:

man u should always have a backup ready before doing anything.

How it Died ?
[Android Q&A, Help & Troubleshooting] hmprincehenry:
i got my backup but it does not work what must i do?

Hardware : MT6572

Model : GT-I9600

Build number : ALPS.JB3.MP.V1.2

Build date UTC : 20140603-061117

Android v : 4.2.2

Baseband v: MOLY.WR8.W1315.MD.WG.MP.V2, 2013/06/13 16:08

Kernel v : 3.4.5 (linux@XzServer) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Tue Jun 3 14:09:16 CST 2014

Uboot build v : -----

LCD Driver IC : 1-ili9806e_fwvga_vdo_dsi

can boot into recovery but cannot mount the system and data cannot charge too.I connect the charger i only see the image of the battery 24/7does not turn off.the red light doesnt come up and i connect it in recovery iget this
[Sony Xperia Miro, Tipo (Dual), J, E] Yash98:
Nothing much to say, what this does is adds the ability to use a custom kernel with any ROM.

Usually with ROMs like zNxT and Paradox the ROMs won't boot with custom kernels because of init.d scripts.

This fixes such bootloops.

Simply, flash it with recovery after installing ROM.

Download: http://tusfiles.co.nz/d/1BpUo
[Sony Xperia Miro, Tipo (Dual), J, E] kreatonn:
To late yash, ive extracted the zip already:(

Good job btw :thumbup::thumbup:
[Sony Xperia Miro, Tipo (Dual), J, E] kidkree1:
Could you mirror the upload, for some weird reason it doesn't let me download it.
[Sony Xperia T, TL, TX, V] arturiu:
FYI, I just got an official OTA update for Walkman.

I now have Walkman 8.1.A.0.3 on my Xperia V using 4.3 (fw: stock 9.2.A.0.295, non rooted, no BL unlock) .

You may find some info about this release here.

Although some custom ROMs are including it already, this OTA is an offical update to stock.

Working/Sounding fine so far.
[Sony Xperia T, TL, TX, V] jose78987:
Where are you from? Waiting for Walkman update... :/
[Sony Xperia T, TL, TX, V] DrizztDWX:
I also recived this update at Xperia T with CE1 soft.
[Sony Xperia T, TL, TX, V] nlooooo:
Here you have it even newer:

http://xdaforums.com/showthread.php?t=2423361

Just install as normal app.