Did you do a hard reset after you were finished?
Sent from my LGLS740 using XDA Free mobile app
Sent from my LGLS740 using XDA Free mobile app
Nop, but I remember that happened when I started messing with gravity box. So I cleared the app data and took my time on selecting the only things I need. Everything is back to normal, just don't know what I enable inside the app to make the LG apps not usable.
But thanks for trying to help,
now what's the benefit of getting the costume recovery? If I brick my device can I unbrick it since we have costume recovery?Nop, but I remember that happened when I started messing with gravity box. So I cleared the app data and took my time on selecting the only things I need. Everything is back to normal, just don't know what I enable inside the app to make the LG apps not usable.
But thanks for trying to help,
Yeah, that is why you would want a custom recovery. However, having a custom recovery does not guarantee 100% brick protection. I'll explain what usually happens in your average "brick" event.
To understand this, you need to understand how Android works, which, this is the same with Linux and most other operating systems. When Android boots, the system immediately goes to the boot rom which immediately starts running the scripts and whatever else to begin the boot loader. The boot-loader then decides where it is you want to boot. If you're just starting your phone, it'll go to start the kernel, then the initializing scripts to run the system. If this is not where it goes, it'll go to run the scripts to run your recovery, or whatever other things it can run.
When we flash something, we're over-writing memory that is already on the phone forcibly. As you should well know, Android has a few partitions, /boot /system /recovery /data /cache and /misc. Boot, system, and recovery are considered Read-Only because they're the 3 most critical to making sure your phone works. /boot stores how the phone boots, loads the boot-loader, kernel, eventually leading us to go either into /system (your actual usable interface for SMS, phone calls, and facebook), or /recovery, where we can do maintenance. /data is where your apps and user data is stored. /cache is where a lot of system temporary files are stored and /misc is where a lot of system settings like region ID and what not is stored.
So. When we have a custom recovery, we are able to make images of most of these partitions. The recovery allows us to be able to flash these images onto the phone if for whatever reason one of them gets corrupted. From how I explained, you should be able to tell that /boot and /recovery then are two partitions that absolutely critical because /boot allows the phone to turn on and /recovery allows us to do maintenance if we mess something up by giving us the power to flash these images.
Now largely, if /boot or /recovery get messed up and if we take improper steps, we'll end up with a completely unusable phone. When flashing anything to /boot, which, usually you shouldn't have to, make sure that a new /boot image is actually on the phone (to the best of your ability) before you restart, otherwise, you aren't going to be able to fix this. If a bad recovery goes on, and prevents you from getting to recovery, depending on the phone, there may be some ways to get a recovery back on without needing to be in recovery. (You can't usually flash a recovery on while in recovery, so this one is fixable as well.)
So, learning from this, a very hard brick is when we have no /boot. At that point, we're pretty well ****ed and the phone is dead. Otherwise, with a custom recovery, it turns just about anything else that can happen into a soft brick.
Getting to the point: A custom recovery, as I said, is not a 100% protection against bricking your phone. However, it does allow us to fix just about anything that goes wrong with the phone via modding use. Root allows people to make changes to areas of the phone that we would otherwise not want changes to happen in. Some of these changes, depending on what you do, can result in a brick. This is because if a change was made in /system, and you try to factory reset using the standard recovery to fix it, android will delete the /data and /cache partitions and remake them based off /system. Which, at this point, you should understand that if /system is corrupt, that'll result in a non-workable phone. BUT, because we have our handy-dandy custom recovery, we can fix that. Because instead of just deleting the /data and /cache partitions, we'll just flash back on the old /system pre-changes. Which will result in a happy working android again.
That's why we want a custom recovery. Anyone who took the time to read this, please correct me where I'm wrong and clarify it.
I would say to read the thread, since I wrote a long post on the current state of the LG Volt. But to explain again, there has been progress made but we're kind of at a skill plateau.
User, danhalen1 I believe was the one who managed to crack the boot-loader and make it semi-usable. However, we have one big issue where the boot-loader isn't 100% open right now so we can't flash a recovery without getting a catastrophic error. We are able to run a live custom recovery (The same way you would run a live linux off a flash drive or CD), from what I've heard, that is capable of making images, I'm not sure about flashing images. You could call it half of a custom recovery, by all regards.
So, the problem we're facing is, there is just something in the code for the boot-loader that is not letting us do anything and no one is quite sure what it is. danhalen1, if I remember right, did say he was hoping someone more experienced would jump onto the LG Volt. This is honestly something we were all hoping for, but so far, I believe anyone more experienced is probably playing with higher end phones than the LG Volt. Even now, Virgin has the HTC Desire 816. HTC is very easy to mod, even having their own website to get a boot-loader unlock code from them. Considering the HTC Desire 816 also has better specifications than the Volt, it seems that more people are probably working on that. The Volt is nice, would be better with a custom rom, but unfortunantly, I don't think anyone with a lot of experience has any interest in the phone. We're kind of on our own over here.
Is there a working method to remove or bypass the Virgin Mobile data throttle? This sllllooooowwww speed is killing me!!! Im rooted, and not running the update.
The throttle is most likely server-side
---------- Post added at 03:38 PM ---------- Previous post was at 03:38 PM ----------
Very informative, thank you for your time
Not sure, have you tried much googling? Things that work on other devices should work on this
I downloaded the wrong app (autorun manager) i opened autostart manager and it forces close pffttt
Use this app to fix the issue https://play.google.com/store/apps/...store&pcampaignid=APPU_Gt0uVMuqMbOUsQTC-oDYAw
Well since this requires root how would you recommend rooting, I got the update that came a few days ago.
Also, what does the spinning sun on the status bar mean?
Last edited:
Similar threads
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
4Thanks, I tried renameing Zone-Sprint.apk to bak, it but it still comes up
Hands Free Activation
Waiting for Repy
If you are not already working with a representative, select activate now
tries 5 times each boot
---------- Post added at 02:55 AM ---------- Previous post was at 02:09 AM ----------
I went through 1 by one until I found it.
To disable the Hands Free Activation on the Boost Mobile LG Volt740 - rename the LGDMSClient.apk to .bak in the system/ app folder4Nop, but I remember that happened when I started messing with gravity box. So I cleared the app data and took my time on selecting the only things I need. Everything is back to normal, just don't know what I enable inside the app to make the LG apps not usable.
But thanks for trying to help, now what's the benefit of getting the costume recovery? If I brick my device can I unbrick it since we have costume recovery?
Yeah, that is why you would want a custom recovery. However, having a custom recovery does not guarantee 100% brick protection. I'll explain what usually happens in your average "brick" event.
To understand this, you need to understand how Android works, which, this is the same with Linux and most other operating systems. When Android boots, the system immediately goes to the boot rom which immediately starts running the scripts and whatever else to begin the boot loader. The boot-loader then decides where it is you want to boot. If you're just starting your phone, it'll go to start the kernel, then the initializing scripts to run the system. If this is not where it goes, it'll go to run the scripts to run your recovery, or whatever other things it can run.
When we flash something, we're over-writing memory that is already on the phone forcibly. As you should well know, Android has a few partitions, /boot /system /recovery /data /cache and /misc. Boot, system, and recovery are considered Read-Only because they're the 3 most critical to making sure your phone works. /boot stores how the phone boots, loads the boot-loader, kernel, eventually leading us to go either into /system (your actual usable interface for SMS, phone calls, and facebook), or /recovery, where we can do maintenance. /data is where your apps and user data is stored. /cache is where a lot of system temporary files are stored and /misc is where a lot of system settings like region ID and what not is stored.
So. When we have a custom recovery, we are able to make images of most of these partitions. The recovery allows us to be able to flash these images onto the phone if for whatever reason one of them gets corrupted. From how I explained, you should be able to tell that /boot and /recovery then are two partitions that absolutely critical because /boot allows the phone to turn on and /recovery allows us to do maintenance if we mess something up by giving us the power to flash these images.
Now largely, if /boot or /recovery get messed up and if we take improper steps, we'll end up with a completely unusable phone. When flashing anything to /boot, which, usually you shouldn't have to, make sure that a new /boot image is actually on the phone (to the best of your ability) before you restart, otherwise, you aren't going to be able to fix this. If a bad recovery goes on, and prevents you from getting to recovery, depending on the phone, there may be some ways to get a recovery back on without needing to be in recovery. (You can't usually flash a recovery on while in recovery, so this one is fixable as well.)
So, learning from this, a very hard brick is when we have no /boot. At that point, we're pretty well ****ed and the phone is dead. Otherwise, with a custom recovery, it turns just about anything else that can happen into a soft brick.
Getting to the point: A custom recovery, as I said, is not a 100% protection against bricking your phone. However, it does allow us to fix just about anything that goes wrong with the phone via modding use. Root allows people to make changes to areas of the phone that we would otherwise not want changes to happen in. Some of these changes, depending on what you do, can result in a brick. This is because if a change was made in /system, and you try to factory reset using the standard recovery to fix it, android will delete the /data and /cache partitions and remake them based off /system. Which, at this point, you should understand that if /system is corrupt, that'll result in a non-workable phone. BUT, because we have our handy-dandy custom recovery, we can fix that. Because instead of just deleting the /data and /cache partitions, we'll just flash back on the old /system pre-changes. Which will result in a happy working android again.
That's why we want a custom recovery. Anyone who took the time to read this, please correct me where I'm wrong and clarify it.2
I would say to read the thread, since I wrote a long post on the current state of the LG Volt. But to explain again, there has been progress made but we're kind of at a skill plateau.
User, danhalen1 I believe was the one who managed to crack the boot-loader and make it semi-usable. However, we have one big issue where the boot-loader isn't 100% open right now so we can't flash a recovery without getting a catastrophic error. We are able to run a live custom recovery (The same way you would run a live linux off a flash drive or CD), from what I've heard, that is capable of making images, I'm not sure about flashing images. You could call it half of a custom recovery, by all regards.
So, the problem we're facing is, there is just something in the code for the boot-loader that is not letting us do anything and no one is quite sure what it is. danhalen1, if I remember right, did say he was hoping someone more experienced would jump onto the LG Volt. This is honestly something we were all hoping for, but so far, I believe anyone more experienced is probably playing with higher end phones than the LG Volt. Even now, Virgin has the HTC Desire 816. HTC is very easy to mod, even having their own website to get a boot-loader unlock code from them. Considering the HTC Desire 816 also has better specifications than the Volt, it seems that more people are probably working on that. The Volt is nice, would be better with a custom rom, but unfortunantly, I don't think anyone with a lot of experience has any interest in the phone. We're kind of on our own over here.2gonna try the new kk_root.zip file from the ioroot25 and try to use that instead of the update.zip file. just waiting on my sd card.
