I have the metropcs lg optimus f6 and used the y4pie app to expand my drive space but noticed it completely bogged the phone down. I thought i removed it via the uninstall within it but to no avail. When i do an lg hard reset the y4pie android logo still comes up when rebooting the phone. During the bootup/setup phase the phone randomly reboots and after getting to home screen still continues to randonly reset/reboot sometimes going back to the start of the setup of the phone. Im on the metro rom no custom rom but was rooted at one time. 4.4.2 kitkat and no outside apps only preinstalled ones on device. I think i have the lg rom to loadvon the phone if there is a way to conpletely wipe the phone 100% clean.
XDA Visitor said:
I have the metropcs lg optimus f6 and used the y4pie app to expand my drive space but noticed it completely bogged the phone down. I thought i removed it via the uninstall within it but to no avail. When i do an lg hard reset the y4pie android logo still comes up when rebooting the phone. During the bootup/setup phase the phone randomly reboots and after getting to home screen still continues to randonly reset/reboot sometimes going back to the start of the setup of the phone. Im on the metro rom no custom rom but was rooted at one time. 4.4.2 kitkat and no outside apps only preinstalled ones on device. I think i have the lg rom to loadvon the phone if there is a way to conpletely wipe the phone 100% clean.
Click to expand...
Click to collapse
Hello, and welcome to XDA!
I see where the hack is mentioned:
> General discussion > Upgrading, Modifying and Unlocking > [Root/Recovery] LG Optimus F6 safest and easiest way
It sounds like a ramdisk hack (packaged with the kernel). I done something like this before, for the F3Q.
So, you will need either a different stock kernel or (if you have files) restore from KDZ. The former is the better option, while the latter is easier to acquire but will leave you with a device that thinks it's from T-Mobile.
You might get in luck with the former option if you ask in the above thread for a copy of the unadulterated boot.img (or any other stock-based kernel that does not have the pressy4pie hack).
Hope this helps, and good luck!
Related
I am a noob at this whole rooting, flashing mods, etc. But when i got my first smartphone the LG VORTEX in the begining of May, 2011 and started downloading apps i noticed a lot of ROOT apps. Ever since then and finding out what root was..I just couldn't keep my hands off anything "ROOT" ever since.
Anyways my problem is:
I downloaded the app Root Toolbox. My phone is ROOTED, although i have been to chicken to actually flash a custom ROM. Obviously I should have. because after changing almost every option i could in the app Root Toolbox, i chose to reboot after changing the options. Well i chose just "reboot" and now my LG Vortex will not boot up. It stays stuck at the black screen that says LG in the middle.
PLEASE HELP I THINK I NEED TO FLASH A CUSTOM ROM. BUT I DO NOT KNOW HOW TO DO THAT UNLESS I CAN ACTUALLY GET INTO MY PHONE!!
i have a samsung captivate i897.
i bought it sim free and unlocked from the states but i'm in the UK.
i recieved it already rooted running cyanogen mod and miui and have had it for 8 months. its worked perfectly the whole time.
until the past month i'd say its been radomly forcing closs on nearly everything.
i havent installed any new software or roms or anything or even dl any new apps so i cant figure out what would be causing the problem.
i tried checking for updateds on the muiu and it runs android 2.3.7
i'm not a tech person at all so i spoke to one of the tech guys at my local phone shop and he said i should try a factory reset.
so i guess i'm asking a few questions here:
1) does anyone have any idea what might be up with my phone?
2) can someone elplain to me the easiest/safest way to fix it?
please bear it mind i am a total noob at this tech stuff. i'll try to understand and cooperate as much as i can with those so kind to help me, but i'd really appreciate if people would help/point me in the right direction instead of giving me a short blunt answer which assumes i know all this tech stuff then locking my thread.
If it's already rooted & running a custom ROM, then you probably already have a custom recovery installed (probably clockworkmod). 1st thing would be to boot into recovery & do a backup. Then, you can try flashing any ROMs you want / factory reset / whatever, and restore your backup if you don't like the results.
-- Sent from my TouchPad using Communities
how do i know if i have clockwork mod installed (i've never seen it before, but then again if its on the boot menu where i've not been before)
for booting into recovery i just long press the power button (at least it works like this on my phone) > reboot > recovery > ok
then what should happen after i press "ok" ?
also just to state (if it helps) the options i get for rebooting are: normal, hot boot, bootloader & recovery.
i dont really feel confident to be flashing roms (mainly because i dont really know how/which are stable etc) on the other hand i do need to fix it. guess i'd like to try the factory reset first though..... under the assumption its slightly easier.
i thought factory reset would restore the phone back to stock settings? but the guy in the phone shop said it wouldnt? (not sure how reliable he is ;] )
found this thread here which seems kinda similar
http://forum.xda-developers.com/showthread.php?t=1264177&page=3
have tried uninstalling some apps to see if it helps.
the thing is with the problem is seems to occur randomly. the phone will work like perfect again for a few days then boom starts forcing close yet again.
only time will tell.
Hi everyone,
I am new to rooting stuff and this forum. I have a lg g2 at&t D800. I wanted to flash rom because of its dark camera issue. I rooted my phone first using ioroot based on instructions from this forum and some other source. I checked my phone I have root access now.
Then, I changed my mind. One thing it is my of control. There are too many stuff to learn. Also, the current os is not too bad.
Anyway, I did not go any further. All the software stays the same as before. I did not flash anything. I even did factory reset afterwards. The only thing changed is that I have root access now.
Can I get still official update and update my phone? Will it mass up my phone?
Thanks in advance!
Ok guys,
I'm gonna post this knowing that there is probably NO SOLUTION to my issue. Let me attempt to explain EXACTLY my issue and what I did. I found a potential solution here > http://forum.xda-developers.com/showthread.php?t=2582142 however my issues don't exactly match the description in that thread.
So, long story short - I've ended up back on the G2 for now (until I upgrade) - I got the G2 on Amazon brand new. When I got it the other day - I discovered when I attempted to boot into download/fastboot or recovery using ADB - the phone would just reboot. The G2 came with KK 4.4.2. I had it rooted but still couldn't get into recovery or download modes. So, for the hell of it - I decided to take the OTA (after reading the G2 can still be rooted on LP). Halfway thru the OTA update (after it reboots into stock recovery) the device reboots. Did it multiple times. So, I went to LG's website and downloaded the LG Mobile Support tool. Plugged the G2 in - it said there was no update available. So, I tried one of the options I found to update the recovery. So, it starts updating.... and then I realized it flashed Lollipop instead of updating the recovery. So, no I'm on stock Lollipop 5.0.2 and I still can't boot into recovery/download/fastboot to flash a stock KitKat image so I can root, ROM, etc.
Anyone heard of this issue or even possibly know how to fix it WITHOUT using a bootable Linux drive or a virtual machine (I have a Windows 8,1 laptop - 8.1 doesn't support Hyper-V out of the box)? If you know anything related to this - please post. I have no clue what else to do except accept the fact that I have a stock G2 that I will NEVER be able to root. I was going to send it back to Amazon and get another one but I don't feel like going thru all that for a phone I'm probably not gonna end up using too much longer.
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!