Hey guys me and Hyperrunner are working on an update for our rom but we need some codes so we could fix a problem in aroma. So could someone please Factory Reset, clear Cache, dalvik cache, and battery stats and make a logcat for each (adb logcat or adb shell then logcat). If ur up to this please do it then post the pictures or codes. Thank You
Id be more than willing
Can you point me to a decent logcat guide? id hate to provide useless info.
edit: nvm, found one. pulling a backup and getting started.
mattdubuc said:
Can you point me to a decent logcat guide? id hate to provide useless info.
edit: nvm, found one. pulling a backup and getting started.
Click to expand...
Click to collapse
thanks my drivers are a bit iffy on my computer
http://forum.xda-developers.com/showthread.php?t=1726238
There's a how-to for ppl that aren't sure how to use logcat.
@Jeff is there something in particular your looking for?
Sent from my R800x using xda premium
We need to fix the factory reset option in aroma to clear cache, dalvik cache, battery stats, and to factory reset the device but we need the codes for each
Sent from my Xperia Play using Tapatalk 2
Couldn't you disable them and have the user wipe them themselves? Most regular flashers are used to it and most other intros to flashing roms say it's a safer way to flash newer roms. just imo
my pc's being nit-picky with adb so I might have to re-install the sdk.
It would be easier and we still need to update aroma
Sent from my Xperia Play using Tapatalk 2
How does one acquire a logcat in cwm? I know how to get one when the phone is booted but I didn't know you could pull one in cwm.
tempest918 said:
How does one acquire a logcat in cwm? I know how to get one when the phone is booted but I didn't know you could pull one in cwm.
Click to expand...
Click to collapse
It should be the same
Sent from my R800i using Tapatalk 2
jeffbud98 said:
It should be the same
Sent from my R800i using Tapatalk 2
Click to expand...
Click to collapse
Ok, I tried pulling it last night in the new cwm v6.0.0.2 and logcat showed nothing, could be something to do with the fact that I was up late trying to do it. :silly: I will again tonight and see what happens. Has anyone else sent you a logcat?
unlocked bootloader?
Do you have to have an unlocked boot loader to do this?
tempest918 said:
Ok, I tried pulling it last night in the new cwm v6.0.0.2 and logcat showed nothing, could be something to do with the fact that I was up late trying to do it. :silly: I will again tonight and see what happens. Has anyone else sent you a logcat?
Click to expand...
Click to collapse
No I need those recovery codes soon and every test rom I'm doing isn't booting. I'll try as hard as I can to get this update out before I leave for vacation on saturday
Sent from my R800i using Tapatalk 2
jeffbud98 said:
No I need those recovery codes soon and every test rom I'm doing isn't booting. I'll try as hard as I can to get this update out before I leave for vacation on saturday
Sent from my R800i using Tapatalk 2
Click to expand...
Click to collapse
I didn't realize cwm makes a log of what you do while your in recovery. lol here's mine from wipeing and restoring glazed ics
Related
I apologize if this circumvents any rule and/or policy on this forum.
I just want to give people a heads up regarding Chainfire 3D Pro 3.3.
If you have JB, don't install it, I made the mistake of doing so and my P5100 ended up stuck on the boot screen.
Solution: Re-flashing.
Well the author does say " Now available for Honeycomb- but still a big risk there!!" So if you're running Honeycomb, that was a possibility.
Another solution, which I just did to my SGS2 with the new JB (and already had the CF-3D pro app installed so didn't see the market warnings) was to boot to (stock!) recovery, (home+volup+press power till get logo while still holding other keys for a bit longer) plug in USB to PC, run adb shell, then su, then
cd /system/lib
./cf3d_uninstall.sh
throws some errors but phone reboots and bingo.
You might try clearing cache and dalvik in recovery too. Its no guarantee, but it can help with boot loop issues depending on the cause.
Sent from my GT-P5110 using xda app-developers app
For normal non root apps, yes, but won't help in this case, since Chainfire 3D isn't putting anything much in data or cache, all the main modifications are /system/lib which clearing cache won't help at all...
Sent from my GT-N7105 using Tapatalk 2
tonymy01 said:
For normal non root apps, yes, but won't help in this case, since Chainfire 3D isn't putting anything much in data or cache, all the main modifications are /system/lib which clearing cache won't help at all...
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Unless its conflicting with something else. Then it could help. Still less likely, but its free, easy, and won't hurt so its worth trying. Something could have gotten botched on the install too. It could be a Google play cache issue. (Its probably not)
I've fixed plenty of stuff in my life by doing things that shouldn't work.
Sent from my GT-P5110 using xda app-developers app
Installing the app isn't causing the non boot, it is going into the app and pressing the option to get it to, via root, modify the system to put new surface flinger drivers in. It is these drivers, which are in system, which causes the non (full) boot on JB. No amount of any cache or even factory reset will fix up /system modifications. Just good thing it has a driver uninstaller which can be run from adb shell.
Sent from my GT-N7105 using Tapatalk 2
tonymy01 said:
Installing the app isn't causing the non boot, it is going into the app and pressing the option to get it to, via root, modify the system to put new surface flinger drivers in. It is these drivers, which are in system, which causes the non (full) boot on JB. No amount of any cache or even factory reset will fix up /system modifications. Just good thing it has a driver uninstaller which can be run from adb shell.
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Ooooohhh!! Yeah thats different. I read the op as if he just installed it and got bootloops. I didnt realize it wasnt until after he used it.
My bad!
In that case this is a lesson in why you should always make a nandroid before messing with system files.
Sent from my HTC Sensation using xda app-developers app
Meyby next udpate fix that problem ;/
help solution
dosbalbin said:
I apologize if this circumvents any rule and/or policy on this forum.
I just want to give people a heads up regarding Chainfire 3D Pro 3.3.
If you have JB, don't install it, I made the mistake of doing so and my P5100 ended up stuck on the boot screen.
Solution: Re-flashing.
Click to expand...
Click to collapse
think that u didn't have a clean flash after u installed ur app which uses ur root permisssion
dosbalbin said:
I apologize if this circumvents any rule and/or policy on this forum.
I just want to give people a heads up regarding Chainfire 3D Pro 3.3.
If you have JB, don't install it, I made the mistake of doing so and my P5100 ended up stuck on the boot screen.
Solution: Re-flashing.
Click to expand...
Click to collapse
Apps have descriptions which are often useful if read ^_~
Sent from my SGH-T769 using xda premium
Any Wanna help me fix mine?
I am stuck in bootloop now, And :WipeData: Didn't work neither did Using the reset externally Tried flashing stock but RCK Just Loads a dead droid. Any tips Msg me On skype at slade228
Ohno!i installed it and my phone bricked.how can i unbrick it?
Sent from my LG-P715
Flash a new rom. And why you have used ist? I mean chainfire wright it in the description that only gingerbread should install this.
There is a driver uninstaller you can run from adb shell from recovery, if you don't want to flash a new system partition or full rom again.
Sent from my GT-N7105 using Tapatalk 2
it is such a pitty that CF 3D doesnt work on any 4.1+ rom :/
I was using it on my phone on ICS,but its devs are obviously not making it compatible with 4.1 and 4.2
Can some make Chainfire change the thing in the play store so it appears as "imcompatable"?
Luigi2012SM64DS said:
Can some make Chainfire change the thing in the play store so it appears as "imcompatable"?
Click to expand...
Click to collapse
It's in the description, the user's must only read.
Dexxmor said:
It's in the description, the users must only read.
Click to expand...
Click to collapse
Sadly, you are asking a lot.
Sent from your phone. You should be careful where you leave that thing.
That's true, 90 percent of the people can not read......
A few months back I rooted my girlfriend's Impulse 4G and installed a custom ROM. I don't know the exact ROM but at the very least the boot screen says "Kalo 'Perfection'". EDIT: I believe it was this rom: http://forum.xda-developers.com/showthread.php?t=1553705
Anyway, a few days ago apps started to crash randomly on her phone. When I reboot the phone, apps begin to crash after a minute or two of use and continue to crash more frequently until it's unusable.
I've tried: factory resetting it, uninstalling apps with adb, installing titanium backup pro with adb and uninstalling apps, clearing cache from recovery, factory resetting from recovery, restoring a backup with roadkil's, flashing a new rom, flashing a new recovery, updating to stock with the dload folder on my sdcard, and ...
no matter what I do, when I reboot the phone it always returns to the same state, unchanged.
And, long-time lurker here who registered to beg for help, of course. Any help will be greatly appreciated. Thanks.
Are you able to provide logcat?
I turned on the phone and let it boot for a minute, then ran logcat. Never used it before, so let me know if you need something more specific.
h t t p : / / pastebin.com/eMTJmvLZ
EDIT:
And, if it helps, when I try a factory reset from recovery I get "E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2". I'm using CWMR Touch v6.0.1.0.
Dexdro said:
I turned on the phone and let it boot for a minute, then ran logcat. Never used it before, so let me know if you need something more specific.
h t t p : / / pastebin.com/eMTJmvLZ
EDIT:
And, if it helps, when I try a factory reset from recovery I get "E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2". I'm using CWMR Touch v6.0.1.0.
Click to expand...
Click to collapse
There is no such block as /dev/block/mmcblk1p2 in the phone. But I guess your phone is different to the normal one.
The only thing I can think is that you have probably flashed the wrong android for your phone. What Custom ROM did you flash? Can you give me a link to both the recovery and the ROM (link for where you downloaded them from).
http://forum.xda-developers.com/showthread.php?t=1553705 I believe this was the ROM. I can't find the recovery at the moment but it's CWMR touch v6.0.1.0. Based on the instructions given with the ROM I'm using the wrong recovery
I am not familiar with your phone, but this might help:
http://forum.xda-developers.com/showthread.php?t=1889305
Meanwhile, I will try to get someone who is familiar.
Unfortunately I've tried everything I can from that thread, I think. Whenever I replace the recovery.img it doesn't stick when I reboot. Same for the roadkil's image. I tried to recover the image I made before I rooted the phone but it never sticks.
I think your partitions for data and cache is incorrect or missing.
What pink screen are you trying to restore(2.2,2.3,4.0,4.1,4.2?)
Sent from my u8800-51
Somcom3X said:
I think your partitions for data and cache is incorrect or missing.
What pink screen are you trying to restore(2.2,2.3,4.0,4.1,4.2?)
Sent from my u8800-51
Click to expand...
Click to collapse
I have pink screen access currently. I was going to try to restore it with the instructions found here http://forum.xda-developers.com/showthread.php?t=1457490 but I wasn't sure that the bootloader.bin they provide is compatible with the u8800-51.
Anyone figured anything out?
Dexdro said:
I have pink screen access currently. I was going to try to restore it with the instructions found here http://forum.xda-developers.com/showthread.php?t=1457490 but I wasn't sure that the bootloader.bin they provide is compatible with the u8800-51.
Click to expand...
Click to collapse
I asked the creater of that thread, but he doesn't know if it would work on yours. He is recommending you to use the bootloader from u8800pro.
Dexdro said:
I have pink screen access currently. I was going to try to restore it with the instructions found here http://forum.xda-developers.com/showthread.php?t=1457490 but I wasn't sure that the bootloader.bin they provide is compatible with the u8800-51.
Click to expand...
Click to collapse
I never saw your post.
Anyhow, you can upgrade to 2.3 but cannot go back to 2.2 unfortunately
Tell me how this results.
http://forum.xda-developers.com/showthread.php?t=1844442&highlight=am+labs
rqmok said:
I asked the creater of that thread, but he doesn't know if it would work on yours. He is recommending you to use the bootloader from u8800pro.
Click to expand...
Click to collapse
Where could I find that?
Somcom3X said:
I never saw your post.
Anyhow, you can upgrade to 2.3 but cannot go back to 2.2 unfortunately
Tell me how this results.
http://forum.xda-developers.com/showthread.php?t=1844442&highlight=am+labs
Click to expand...
Click to collapse
Gonna follow the instructions now.
Somcom3X said:
I never saw your post.
Anyhow, you can upgrade to 2.3 but cannot go back to 2.2 unfortunately
Tell me how this results.
http://forum.xda-developers.com/showthread.php?t=1844442&highlight=am+labs
Click to expand...
Click to collapse
The link in that thread is dead.
Dexdro said:
The link in that thread is dead.
Click to expand...
Click to collapse
You can download official 2.3 from huawei website, or from the thread, in Android Development section, that has the index of all ROMs.
Dexdro said:
The link in that thread is dead.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1844442
Sent from my U8800-51 using Tapatalk 2
Somcom3X said:
http://forum.xda-developers.com/showthread.php?t=1844442
Sent from my U8800-51 using Tapatalk 2
Click to expand...
Click to collapse
It resulted like the other things I tried: no change. At all. What would make the phone unable to write changes? Something amiss with the partitioning?
Dexdro said:
It resulted like the other things I tried: no change. At all. What would make the phone unable to write changes? Something amiss with the partitioning?
Click to expand...
Click to collapse
Thought it would work tbh. I will give you my gtalk in pm
Sent from my SGH-T769 using Tapatalk 4 Beta
Can you try posting the logcat again? I could not open the one you sent before.
h t t p : / / pastebin.com/j50wr7i2
Okay, so I was listening to a YouTube video via Popup Browser BETA. When the song finished, I tried closing the window, but it wouldn't let me interact with the window. Not sure why. I just figured since the app was in beta it was just confused, so I went to the settings->running applications->I force closed the app. But for some reason, the little window still wouldn't go away. So I decided to reboot my device. Bad idea, apparently...
Now whenever I boot up my phone it'll vibrate, display the Google logo for a few seconds, and then... it goes to a blank black screen. Not a clue why. I've tried:
- Leaving it to charge and rebooting
- Leaving it in the blank black screen
- Booting into recovery, then trying to reboot the device from there
- Clearing cache partition
Nothing works. I still can't boot up my phone again.
I'm running Slimbean 4.2.1 (not the latest version). There really isn't anything that might have triggered this. I can still charge my phone (the charging animation still occurs) and I can still go into CWM Recovery. I'd really rather not have to install a new ROM or anything... but if I have to, is there a way to extract the data I have on my phone now while in recovery or something?
Any suggestions?
EDIT: This has been FIXED. Moderators, if you see this, you can close this thread. If anyone else has this problem, try reflashing your current version of your ROM, that's how I fixed mine. I'm not responsible for damage to your device.
Why haven't you tried reflashing your rom without wiping data?
Sent from my iPad 4
mitchdickson said:
Why haven't you tried reflashing your rom without wiping data?
Sent from my iPad 4
Click to expand...
Click to collapse
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Surpass said:
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Click to expand...
Click to collapse
It's not going to hurt anything. Make a CWM backup of your data if you want.
Sent from my iPad 4
Surpass said:
I could try that.. but isn't there a chance it'll corrupt the data for certain apps or no? I'd just really rather not loose all of that.
Click to expand...
Click to collapse
No way of corrupting your data, as long as you don't select to wipe data partition or data is already corrupted. But this is strange that your phone gone crazy like this. Try to reflash your rom without wiping data and see if your phone will boot up
Sent from my Nexus 4 using xda app-developers app
mitchdickson said:
It's not going to hurt anything. Make a CWM backup of your data if you want.
Sent from my iPad 4
Click to expand...
Click to collapse
I've not got enough free space on my phone I don't think (it's only 16GB, I got about 2GB free).
Unless I'm mistaken the backup will take more than that, yes? Considering I've got a few games apps that probably equate to about 4GB.
gallardo5 said:
No way of corrupting your data, as long as you don't select to wipe data partition or data is already corrupted. But this is strange that your phone gone crazy like this. Try to reflash your rom without wiping data and see if your phone will boot up
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Should I reflash with a newer version of the ROM or should I reflash the old one that I'm running?
EDIT: Woops sorry about double post.
Surpass said:
Should I reflash with a newer version of the ROM or should I reflash the old one that I'm running?
EDIT: Woops sorry about double post.
Click to expand...
Click to collapse
Reflash the same version you were running before this accident, as the newest version requires clean flash. If you want to run the latest version and have your data back, reflash the same version you were running before, then backup your data, wipe phone, flash the latest version and restore your data
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Reflash the same version you were running before this accident, as the newest version requires clean flash. If you want to run the latest version and have your data back, reflash the same version you were running before, then backup your data, wipe phone, flash the latest version and restore your data
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Okay I'll give that a go, thanks for the help and I'll report back my results. :good:
EDIT: Tried downloading the Zip from their site and now it's saying I've got to log in, but no place to register... grr. I might be a bit longer..
Surpass said:
Okay I'll give that a go, thanks for the help and I'll report back my results. :good:
Click to expand...
Click to collapse
Good luck then and if you will have any problem, just write here and don't forget to quote my post so I will get an email notification
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Good luck then and if you will have any problem, just write here and don't forget to quote my post so I will get an email notification
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
WOO! Thanks a lot! Booted up perfectly, and no loss of data or anything like that. Only odd things is it seems to have changed my DPI... but I can change that easily so it's not really a bother. It also made me have to update the Virus Definitions on Avast!, not sure why either.
I shall now proceed to thank all of your posts.
Surpass said:
WOO! Thanks a lot! Booted up perfectly, and no loss of data or anything like that. Only odd things is it seems to have changed my DPI... but I can change that easily so it's not really a bother. It also made me have to update the Virus Definitions on Avast!, not sure why either.
I shall now proceed to thank all of your posts.
Click to expand...
Click to collapse
Great to hear it worked for you now comes the best part, flashing the latest rom
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
Great to hear it worked for you now comes the best part, flashing the latest rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes either that or perhaps switch to a new one, I've been with semi-stock Android for quite a while now I'm really liking the port of MIUI V5...
Hey guys,
So went ahead and flashed TWRP (using flashify) and it worked just fine. The only problem is that now any reboot just takes me back to TWRP. What did I do wrong? Thanks!
Mike
TWRP>Reboot>System?
Sent from my LG-D800 using Tapatalk 4
lastdeadmouse said:
TWRP>Reboot>System?
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, tried that. No matter what option I use to reboot, I just reboot into TWRP. Kind of starting to panic
dankasfuk said:
Yeah, tried that. No matter what option I use to reboot, I just reboot into TWRP. Kind of starting to panic
Click to expand...
Click to collapse
Have you tried fixing permissions, clearing caches, repushing Loki/twrp via adb?
Not sure beyond that.
Sent from my LG-D800 using Tapatalk 4
lastdeadmouse said:
Have you tried fixing permissions, clearing caches, repushing Loki/twrp via adb?
Not sure beyond that.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, thanks for the suggestions. I don't think I can even get to adb since I can't boot at all. If anyone here has any idea what else might have happened, please let me know.
dankasfuk said:
Yeah, thanks for the suggestions. I don't think I can even get to adb since I can't boot at all. If anyone here has any idea what else might have happened, please let me know.
Click to expand...
Click to collapse
You may be able to access adb from d/l mode if not twrp.
Sent from my LG-D800 using Tapatalk 4
---------- Post added at 09:26 PM ---------- Previous post was at 09:21 PM ----------
http://forum.xda-developers.com/showthread.php?p=45690006
Factory reset method might help.
Sent from my LG-D800 using Tapatalk 4
yup factory reset is your friend.
lastdeadmouse said:
You may be able to access adb from d/l mode if not twrp.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
Tried that too - my fear is that I may have somehow replaced that bootloader with TWRP, therefore there seems to be no way to load System. Man, I hope there is a solution to this. No way I can try and return it in this state.
dankasfuk said:
Yeah, thanks for the suggestions. I don't think I can even get to adb since I can't boot at all. If anyone here has any idea what else might have happened, please let me know.
Click to expand...
Click to collapse
Head on over to http://webchat.freenode.net/ and join #lg-g2
You may find help there.
UPDATE: So the issue was a misset flag in misc, meaning that the phone can only boot into recovery. This happened when you used the hardware keys to boot into recovery. Usually you could fix this with adb, but adb in the current G2 build of TWRP wasn't working.
So, until ADB works in recovery again, don't try to flash it!
dankasfuk said:
Tried that too - my fear is that I may have somehow replaced that bootloader with TWRP, therefore there seems to be no way to load System. Man, I hope there is a solution to this. No way I can try and return it in this state.
Click to expand...
Click to collapse
I don't see you making it to twrp without a boot loader, but did you possibly check anything besides recovery in flashify?
Sent from my LG-D800 using Tapatalk 4
That's is what happens if you format system. Did you make a back up in TWRP? If system had not been formatted then perhaps factory reset us a good option.
First I would force a hard reboot by holding power button until it turns off.
Sent from my LG-D800 using XDA Premium 4 mobile app
djkinetic said:
yup factory reset is your friend.
Click to expand...
Click to collapse
Thanks djkinetic. So following http://forum.xda-developers.com/showthread.php?t=2432476 would potentially work?
stuck on TWRP. Damn!
used flashily, now am stuck on twrp. it wont reboot on system nothing. did factory reset, still on the same page.
I need your help guys
jnclocker said:
used flashily, now am stuck on twrp. it wont reboot on system nothing. did factory reset, still on the same page.
I need your help guys
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=45293512
That should work.
Sent from my LG-D800 using Tapatalk 4
lastdeadmouse said:
http://forum.xda-developers.com/showthread.php?p=45293512
That should work.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
no i have tried all that and it hasnt worked.
jnclocker said:
no i have tried all that and it hasnt worked.
Click to expand...
Click to collapse
http://webchat.freenode.net
Join #lg-g2
Devs are working on diagnosing and repairing the issue. The only other viable solution is the flash back to stock, which you said didn't work for you.
Similar predicament
im also stuck at TWRP but i do have access to adb and adb sideload
i was wondering if it would be possible to sideload an TWRP from someone who had a working G2
Let me start off by saying I apologize if this is posted somewhere already.
Here's my situation. A couple days ago I lgflashed back to stock. All went well. I then rooted and installed TWRP. No issues at all. I didn't take an update, modify the stock ROM or even flash another ROM. Just ran stock rooted. Today, I pick my phone up, go to turn it on and I'm in recovery. No big deal, right? Well I can't get out of TWRP. My backups are still showing, but when I restore it and reboot the phone I'm right back in recovery.
I can't get into download mode either. Not sure what happened and everything was fine earlier in the day. Any thoughts?
Sent from my Nexus 5 using Tapatalk
I should also say that adb doesn't recognize my phone.
Sent from my Nexus 5 using Tapatalk
droidiac13 said:
I should also say that adb doesn't recognize my phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm in your same boat right now, working on a buddy's phone cept when i formatted phone to stick a rom on it the nandroid i made got file 13'd
dcillusions77 said:
I'm in your same boat right now, working on a buddy's phone cept when i formatted phone to stick a rom on it the nandroid i made got file 13'd
Click to expand...
Click to collapse
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
droidiac13 said:
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
Click to expand...
Click to collapse
Tried it but it didn't work :\.....
Mine is stuck in fastboot mode whenever I try to reboot it into recovery what files are missing? Anyone know why whenever I reboot it into recovery it boots fastboot instead? Any help would be much appreciated
If you stuck in fastboot mode. Just push
laf file through fastboot to your phone.
Sent from my LG-F320L using xda app-developers app
droidiac13 said:
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
Click to expand...
Click to collapse
I'm so glad your back up and running again. I've been following your thread. And thanks for sharing the fix.
Does that mean that without your knowledge, your phone may have probably automatically updated itself (OTA) when you left your phone overnight? That's why you were stucked in recovery? Because it seems so odd that you didn't do anything wrong and it suddenly behaved that way. And I have read somewhere here that OTA just installed itself automatically without user intervention. So confusing if that did happen. How is that even possible?
Sent from my LG-D802 using Tapatalk
cccho said:
If you stuck in fastboot mode. Just push
laf file through fastboot to your phone.
Sent from my LG-F320L using xda app-developers app
Click to expand...
Click to collapse
Got it up and running by downloading the FreeGee app from play store and installing TWRp that way. I had tried it before just didnt stick the first time
mrm43 said:
I'm so glad your back up and running again. I've been following your thread. And thanks for sharing the fix.
Does that mean that without your knowledge, your phone may have probably automatically updated itself (OTA) when you left your phone overnight? That's why you were stucked in recovery? Because it seems so odd that you didn't do anything wrong and it suddenly behaved that way. And I have read somewhere here that OTA just installed itself automatically without user intervention. So confusing if that did happen. How is that even possible?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I can only guess that it updated by itself. I really don't know what else it could be.
Sent from my LG-D800 using Tapatalk
droidiac13 said:
I can only guess that it updated by itself. I really don't know what else it could be.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Yes it might seem that way. Thanks
Sent from my LG-D802 using Tapatalk