Hi,
I flashed VT V6 on my F400K which changed the hardware and software to F400L and F400L100g respectively. Everything was working fine until I changed ART from Dalvik and now on rebooting it is giving me Unfortunately the process com.android.phone has stopped as well as process com.android.systemui has stopped. I am not able to get past them.
I have backed up my stock image in recovery, can someone please advise how do I get into it and recover to original settings..
Please help
UPDATE: I am able to see my phone on device manager but dont see the PORT under properties (see attached), also once I press volume+ and plug USB, it starts booting and ends up with the error, not sure whether I am in download mode
Related
Hey! I wanted to follow this Tutorial -> klick.
After i finished it, some of the Apps on my SD card didn't work anymore. I wanted to do a factory reset. The Problem is, i deleted some of the system apps, i even deleted the home.apk. I couldn't to anything without the home launcher, so i flashed a zip with launcher pro throu recovery. I downloaded root explorer and wanted to copy my backuped /system/app over to my phone, but i think this wasn't a good idea. The system crashed and just many many force closes came up. I closed everything, but the system still wanted to close, so i removed the battery...another bad idea. Now, if i want to turn on my Phone, the boot animation stops and the phone reboots and is doing the same.
I really hope anybody here can help me
It's called a bootloop, and from what you described caused it, it may be unfixable without flashing a fresh rom with flashtool.
Sent from my R800i using Tapatalk
Fine, but how can i do this? I've read that i habe to hold power when plugging it in while Flashtool is looking for an device, but the phone is just trying to boot normally
EDIT:
Ok, i have to push the back button... but if i want to Flash, i get this:
10/040/2012 06:40:20 - ERROR - Error flashing. Aborted
10/040/2012 06:40:20 - INFO - Now unplug the device and power it on
10/040/2012 06:40:20 - INFO - Then go to application settings
10/040/2012 06:40:20 - INFO - turn on Unknown Sources and Debugging
but i cant do this.
Found a solution! I installed the newest Firmware again with SEUS and everything is working. Thanks, XDA!
hi2all
before post this thread i cheked all xda but anyone method did not help me
my problem is "scanning media files"
one day when i serfing inet my E975 has been rebooted
after load i got a first time boot start message
all data lost and phone ask me to set all setting from beginning
now i see alltime 'scanning media files'
I have tried the following: steps:
made hard resets - no effect
flashed using KDZ updater (E97510C_00, E97510a_00 E97510f_00) - no effect
used LGtool (selected recovery..inserted my IMEI and load) - no effect
and followed this http://forum.xda-developers.com/show....php?t=2010624
but problem haven't solved
always media scanning
cant try any ways like fleshing kernel, becose need fastboot mode
cant unlock fastboot, cos cant make root... anyone way to install root not work, cos no access to phone storage
someone told me i can try to do root with adb shell... but cant find how i can use this in my sutuation
I would be very thanksfull any help
i rly dont know what should i do next....
In the past I have a problem with media scanner message, always running in the background, although I had no problems about rebooting or soft-resets, it was only a message running in the background always. The way I solve it was to go into "almacenador de medios" (dont know in english, maybe something like "media store") in app manager, and then force stop, clean data and clean cache, reboot and after a first past again, all went ok. I suppose you continue with the message after reseting maybe because cache or dalvik cache is not clean.
Hope that help.
pr0_eMoTIoN said:
hi2all
before post this thread i cheked all xda but anyone method did not help me
my problem is "scanning media files"
one day when i serfing inet my E975 has been rebooted
after load i got a first time boot start message
all data lost and phone ask me to set all setting from beginning
now i see alltime 'scanning media files'
I have tried the following: steps:
made hard resets - no effect
flashed using KDZ updater (E97510C_00, E97510a_00 E97510f_00) - no effect
used LGtool (selected recovery..inserted my IMEI and load) - no effect
and followed this http://forum.xda-developers.com/show....php?t=2010624
but problem haven't solved
always media scanning
cant try any ways like fleshing kernel, becose need fastboot mode
cant unlock fastboot, cos cant make root... anyone way to install root not work, cos no access to phone storage
someone told me i can try to do root with adb shell... but cant find how i can use this in my sutuation
I would be very thanksfull any help
i rly dont know what should i do next....
Click to expand...
Click to collapse
have you tried the lg pc suite?go to lg's site and download it and the connect your phone to pc in "pc suite" mode.then from there you can do an update or press the "emergency firmware recovery" under device menu.This will propably recover your phone.
MafiaGR said:
have you tried the lg pc suite?go to lg's site and download it and the connect your phone to pc in "pc suite" mode.then from there you can do an update or press the "emergency firmware recovery" under device menu.This will propably recover your phone.
Click to expand...
Click to collapse
already tried this
but problem havnt solved after "emergency firmware recover"
anyone knows how i can made root without access rights to sd card?
ways like "frameroot.apk" and via bat file "currentroot.bat" - not worked (all those methods need access to sd card)
or maybe there are any commands on ADB to reset or fix sd card?
i'm rly sad with my problem....
what is the model of your phone and ROM?
did You try go back to stock rom with LGMobile Support Tool?
I have same problem but it occurs when I flash to E97510D ROM (my phone is F180K):
http://forum.xda-developers.com/showthread.php?t=2246867
when I want to fix it, I make emergency firmware recovery in LGMobile Support Tool (and factory reset after this).
Maybe your motherboard is giving up
no... every time I go back to stock ROM, its working fine
bihslk said:
Maybe your motherboard is giving up
Click to expand...
Click to collapse
i think this is rly...
cos i have tried already all ways...
Hi,
I have followed the official wiki to install Cyanogenmod 12.1 nightly builds (December 25, 2015 nightly build) on my xperia M. It all worked well for the first time.
But suddenly after using it for some days happily, when I rebooted the device, the moment the device boots up, all the apps start crashing, causing the device unusable. I tried to reboot but it's still there. So I tried to repeat the process to get rid of this and tried to flash the December 30, 2015 build but somehow it is not working.
When I sideload the update zip file, it starts and gets stuck at 47% for quite long time and then suddenly finishes with (Total xfer: 1.00x ). The instant it goes 100%, the android icon showing "update" process disappears and screen keeps blinking and stays dark but still "adb devices" shows my device connected but the device screen just keeps blinking and nothing shows. I tried "adb reboot" but it throws this error
"error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
the "kill-server" command fails as well and thus, the problem persists.
I also installed open gapps after installing CM12.1 on the very first time. But in all those re-flashes, I skipped flashing it altogether and wiping cache partition, media and data & factory reset, these apps (calendar, music and gmail etc) throw the error the devices boots up. I guess the device is not getting formatted properly and its not being flashed with just the newer image. It gets stuck at 47% for way too long (almost 20 mins or more), while if I remember correctly, it didn't do so on first flashing.
Since I can't use any app when the device is ON, I can't open settings to check anything. Please help me getting rid of this, so that I can enjoy using this awesome ROM.
Thanks in advance.
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.
Hello Guys
My friend ask me for get a Lineage OS to his H815 with Nougat. I agreed as I made few successful changes from stock to Lineage OS with Samsungs and older LGs (like L3 E400). But G4 is really more complicated, more than I expected . Firstly I wanted to unlock this phone with FWUL, so I download a VirtualBox emulated image with FWUL and after it boots I opened SALT program and it detects the phone. I made a basic backup and then I choosed Unlock G4 (UsU). After that some windows pop up. Last window was a pre-checking, when the bar gets to the end window closed and nothing more was happening. So after almost hour of waiting I just turned off the phone - I thought its all. After that while phone is booting I have those messages in the left top corner:
[820]-----------------------
[870]
[920] Secure boot error!
[970] Error code : 1009
[1020[ OFFICIAL !!
[1070]
[1120]-----------------------
Its booting, but only sometimes its normal boot, most starts are with bootloop, sometimes its start after 10 restarts, sometimes after 2nd restart, sometimes after plug in/plug out USB cable it starts boot normally (connecting cable only to phone, not to PC), sometimes only thing that helps is to take out the battery. I made full wipe to be sure that its not a software problem, but only thing I achived with that is fact that phone has a Nougat and now it have a Marshmallow. It is (was?) H815, but now model name is LGLS991 (?), it gets very long until it shows software version (V20g), IMEI is unknow, even when I type *#06# I get the null response.
I can get into recovery, can put phone into download mode. But i'm not able to do anything to get LOS or a least Nougat.
I've read many, many tutorials how to get G4 working properly after unsuccessful unlock, but nothing helps. What I've tried:
1. Flashing stock Nougat for H815 with LGUP, installed USB drivers, proper DLL, set com to 41, but when I trying to flash, after a 4% i get error: KDZ file is invalid. Downloaded few KDZ firmwares, dont belive that every single one is invalid, there is something wrong with LGUP or with settings, but I cant find what
2. Flashing with LG Flash Tool 2014: tried both normal flash and cse flash and always stoping in the same moment, with "Connection to server failed. Try again in a moment". Read many tutorials about this error, none was helpful in my case.
3. Flashing with LG Flash Tool v1.8.1.1023 and a TOT file, but after select of dll and tot file and press the yellow arrow I get an error: "Failed PreviousLoad()"
Tried all this methods on second computer but without a luck.
What else can I try to get this G4 working properly? Maybe try to install some rom from stock recovery? But which rom will be ok and dont get things worst?
If you need more info dont hesitate to ask. Would be very greatful for any advices .
you definitely didn't read enough... go to read again the UsU thread and as you've read the whole tutorial, you can also read the whole FAQ and the OP, because 90% of what you pointed out in your publication (which incidentally is in the wrong section) is explained there.
A quick advice: Don't try to flash any KDZ/TOT again.