Ok, so a few months ago I had messed up my O2x while trying to NVflash a recovery, as I had described in this thread->
http://forum.xda-developers.com/showthread.php?t=1952614
The LG service centre told me it's a hardware problem and it'd cost me around 60% of the phone's price to get it fixed. I didn't get it done and put the phone away.
Now after all these months I took it out yesterday and Googled to see if I could fix it. I found this "full brick repair" tool that was really easy to use and now the phone has cm10 and cwm installed and is booting fine.
But the problem is that the touchscreen is not at all working. The display is working fine, but touches aren't getting registered. This may very well be a hardware issue. But the phone not booting up earlier was also said to be a hardware issue, which turned out to be a software problem. So, I just wanted to make sure that the touchscreen not working isn't a software problem before I hand it over to LG service executives.
I've flashed the 725 v10 baseband to see if that solves it, but it didn't. Also flashed v20l to no avail. Flashed another rom after wiping cm10 (Dovahkiin 1.2), no improvements. Any other suggestions?
Did you try flashing cwm 6 (touch)?
My first thaught was a incompatible (wrong) Kernel (I had this on my tablet).
MrKra said:
Did you try flashing cwm 6 (touch)?
My first thaught was a incompatible (wrong) Kernel (I had this on my tablet).
Click to expand...
Click to collapse
The brick repair tool installed CWM 6.0.1.5. Does that support touch? Idk cause the touchscreen isn't working in recovery either. I can navigate and select with the vol and power buttons, which work fine.
If I install a touch recovery and the touchscreen still doesn't function, I'll lose my ability to use the recovery too, so i'm a wee bit apprehensive. (or can CWM touch also be used with the volumed and power keys?)
sean8000 said:
The brick repair tool installed CWM 6.0.1.5. Does that support touch? Idk cause the touchscreen isn't working in recovery either. I can navigate and select with the vol and power buttons, which work fine.
If I install a touch recovery and the touchscreen still doesn't function, I'll lose my ability to use the recovery too, so i'm a wee bit apprehensive. (or can CWM touch also be used with the volumed and power keys?)
Click to expand...
Click to collapse
Recovery always can be controlled by volume keys.
If I were you I would Install the latest CWM via AO Tools. Than I would try to install something with aroma installer, like optithrust rom or so
MrKra said:
Recovery always can be controlled by volume keys.
If I were you I would Install the latest CWM via AO Tools. Than I would try to install something with aroma installer, like optithrust rom or so
Click to expand...
Click to collapse
Ok, I'll install the latest CWM touch. Are you sure I should install optithrust? I was using cm10, so I think i'm on old bootloader. Optithrust seems to be for the new bootloader.
Downloaded CWM 6.0.1.5 touch from this thread ->
http://forum.xda-developers.com/showthread.php?p=34286893
It flashed fine, but touch still isn't working, not even in the recovery menu.
Should I flash a different rom or something?
You dont need to flash the rom, this is only a test if the touch is working in aroma installer.
if no => this is a + for hardware problem
if yes => Ill think about new ideas
Ok then, can you tell me in a little more detail what this aroma installer is and what I have to do with it? I tried to find out myself, but i'm not sure i fully understand it and I rather not take any chances.
The Aroma Installer provides an installation via Touchscreen.
e.g. you touch "Cancel" or "Next" instead of pressing the power button during installation.
This implementation of touch is very low level and "kernel independent".
Optithrust, Django Manouche and the CIV ROM and the Dual Boot Tool areshipped with the Aroma Installler
I am not sure, but I think CWM >=6 is needed for this
Hi guys,
Did you find any solution to the screen not working. Mine stopped working yesterday.
If its a software problem, how do i verify ?
If its a hardware problem, what needs to be changed ?
Thanks for any replies ...
I don't have a solution.. but I have the same problem. No touchscreen when I install any ics roms (including lg stock). Touchscreen works fine with gingerbread e.g. CM7 so it's software not hardware... any ideas?
Sent from my LG-P990 using xda app-developers app
Related
I cant flash this it just wont work.
Its been a while since i last flashed a recovery but i disabled usb mount and enabled usb debugging i launched terminal emulator and typed
su
flash_image recovery /sdcard/recovery.img but it keeps saying it cant find it, i noticed when i used bluetooth file manager it says it mnt/sdcard so i tried that and its still the same, i even tried root toolbox pro and erased the recovery then flashed the new touch recovery and still it doesnt work i still have clockwork mod 5.2.0.
Wtf am i doing wrong this is doing my head in, it tells me the img file doesnt exist.
Are you sure you want touch CWM? You are aware of the cache-wiping bug right?
If you're not, touch CWM has a known bug when wiping cache. This bug somehow prevents CWM from rebuilding the cache after wiping it. Therfore you'll get force closes in many apps like Market.
SP1996AC said:
Are you sure you want touch CWM? You are aware of the cache-wiping bug right?
If you're not, touch CWM has a known bug when wiping cache. This bug somehow prevents CWM from rebuilding the cache after wiping it. Therfore you'll get force closes in many apps like Market.
Click to expand...
Click to collapse
I didnt know that, are they fixing it?
I don't know if they're fixing it, for now I think it's better to keep your current CWM version.
SP1996AC said:
I don't know if they're fixing it, for now I think it's better to keep your current CWM version.
Click to expand...
Click to collapse
Wanted a touch version so i can stop wearing down my buttons, hope they get it fixed quickly and that i can actually figure out how to bloody flash it.
eraldo said:
Wanted a touch version so i can stop wearing down my buttons, hope they get it fixed quickly and that i can actually figure out how to bloody flash it.
Click to expand...
Click to collapse
Hmmm... But with CWM 5.0.2.0, (from ROM Manager) you can also use the four touch-capacitive buttons to navigate through the menus. At least on my device...
The menu button: going down
The home button: going up
The back button: back (what a surprise... )
The search button: select
SP1996AC said:
Hmmm... But with CWM 5.0.2.0, (from ROM Manager) you can also use the four touch-capacitive buttons to navigate through the menus. At least on my device...
The menu button: going down
The home button: going up
The back button: back (what a surprise... )
The search button: select
Click to expand...
Click to collapse
Other than to flash recovery I don't use rom manager and I uninstalled it when I found they charged to install touch recovery there are other apps that flash recovery for you so I'll use them now.
Sent from my LG-P990 using XDA Premium App
Keep the old one, touch recovery is too buggy for a daily use.
http://forum.xda-developers.com/showthread.php?t=1098745
Hello, since new my p990 vibrates in CWM Mode, an isn´t a low vibration, it´s at maximum strength.
I don´t know why, in all my other phones never happened this.
I did bricked it once and used a wrong NVflash (p-999) and then used the wrigth one.
Is this a hardware problem?
I also tried diferent tipes of CWM, already flashed via smartool stock rom...and nothing.
Best regards
Same thing happens to me. It doesn't seem to do much. I just flash ROMs as normal
You can update to CWM 6 via ROM manager. That recovery fixes the vibrate issue.
Tehloy said:
Same thing happens to me. It doesn't seem to do much. I just flash ROMs as normal
You can update to CWM 6 via ROM manager. That recovery fixes the vibrate issue.
Click to expand...
Click to collapse
Thank you for your response.
I did not have the oportunity to try this, as i sold the 2x and went for the SIII.
install rom manager and flash the cmw....the new cmw is fixed....now it is not vibrating..... in the 6.0.1.5 this issue is fixed
Hello there,
i've rooted my GC with newest 4.1.2 Android and all went fine. Then i wanted to use the cool init.d Script, which makes it possible to set the extSdCard storeage as 'internal' and the internal as external Storeage, to get more space for a lot of Apps.
But for this init.d script i needed to use a compatible kernel. So thinking, the GalaxyCamera HW is almost the same like from the Galaxy S II Phone. i decied to use this tut: http://forum.xda-developers.com/showthread.php?t=1772234 to download the init.d script and siyah- kernel. getting this things into the Camera i should use ClockWorkMod.
And there the Problem starts: In ClockworkMod install-tool i sayed "yes" to install it for a Galaxy S III.. humm, device restarting into recovery and Screen flashes with disorientated GalaxyCamera Logo und went blank afterall... i rebootet and all went fine, but recovery was "corrupted" (with my luck i didnt make a backup in ClockWorkMod ROM Utility on Android... ( )
So i decided to start over and started to flashing (idont now why) the root- Restore file from Chainfire for the GalaxyCamera again. Recover Mode works fine again, but NOW on normal boot my Touchscreen doenst react anymore.
After trying with several Stock recoveries, even with 4.1.1 and so on an re- Routing.... issue still persists.. ( Can anyone help me, or did i just killed the Touchscreen Controller with this Action??
Do you try a hard reset, you probably can do it from recovery mode, but not sure.
Maybe he solve your issue ?
I've already tried. But thank you for your tip!
The Problem is (i guess) that ClockWorkMod or Chainfires Root, locked up some file- permissions and the Touchscreen- driver cant load into Memory. If it where possible for me to repartition the device, all locked Data gets wiped and a fresh Andoid flashed back to NAND . I tried this with Adam's Pit- File in Odin or Heimdall several Times with differen OS'es. No success.
Yesterday i Sent the camera in for repair to a Samsung Service Provider. I Hope they will fix it. Small problem: i couldnt reset the Flashcounter with an 'defective' Touchscreen! ... I hope they would not recognize my 20 custom OS restores!
I will inform you if my lovely GalaxyCamera gets fixed!
WEissbr0t said:
I've already tried. But thank you for your tip!
The Problem is (i guess) that ClockWorkMod or Chainfires Root, locked up some file- permissions and the Touchscreen- driver cant load into Memory. If it where possible for me to repartition the device, all locked Data gets wiped and a fresh Andoid flashed back to NAND . I tried this with Adam's Pit- File in Odin or Heimdall several Times with differen OS'es. No success.
Yesterday i Sent the camera in for repair to a Samsung Service Provider. I Hope they will fix it. Small problem: i couldnt reset the Flashcounter with an 'defective' Touchscreen! ... I hope they would not recognize my 20 custom OS restores!
I will inform you if my lovely GalaxyCamera gets fixed!
Click to expand...
Click to collapse
Dude, did you get your camera back?? I made he same mistake just a couple of hours ago.. I am feeling so depressed, I dont know what to do.
Did they say anything about the flash counter?
me too
I have had this problem as well. My camera has no touch on the screen after rebooting. I saw it flick and lock and then I tried to re-flash the rom etc, but it didn't help.
Sent to Samsung and they are saying that the motherboard and screen have to be replaced at a cost of $350. They are seeing if they can repair under warranty, but it doesn't sound too hopeful.... Perhaps, I will give up on my Galaxy Camera. I am not going to pay $350 to have the item repaired. I didn't know if it was a software fault or a hardware failure. I think it really should be a warranty issue....
Anyhow, I guess clockwork mod can really wreck things up..... Anyone, found a way to fix this issue? Why didn't the default Samsung ROM flash and factory reset fix the issue if it is supposedly software?
WEissbr0t said:
Hello there,
i've rooted my GC with newest 4.1.2 Android and all went fine. Then i wanted to use the cool init.d Script, which makes it possible to set the extSdCard storeage as 'internal' and the internal as external Storeage, to get more space for a lot of Apps.
But for this init.d script i needed to use a compatible kernel. So thinking, the GalaxyCamera HW is almost the same like from the Galaxy S II Phone. i decied to use this tut: http://forum.xda-developers.com/showthread.php?t=1772234 to download the init.d script and siyah- kernel. getting this things into the Camera i should use ClockWorkMod.
And there the Problem starts: In ClockworkMod install-tool i sayed "yes" to install it for a Galaxy S III.. humm, device restarting into recovery and Screen flashes with disorientated GalaxyCamera Logo und went blank afterall... i rebootet and all went fine, but recovery was "corrupted" (with my luck i didnt make a backup in ClockWorkMod ROM Utility on Android... ( )
So i decided to start over and started to flashing (idont now why) the root- Restore file from Chainfire for the GalaxyCamera again. Recover Mode works fine again, but NOW on normal boot my Touchscreen doenst react anymore.
After trying with several Stock recoveries, even with 4.1.1 and so on an re- Routing.... issue still persists.. ( Can anyone help me, or did i just killed the Touchscreen Controller with this Action??
Click to expand...
Click to collapse
I had the same problem dude, got the touchscreen replaced at the service center.
New touchscreen works totally fine.
Hi;
I'm using samsung galaxy camera. I wanted to root with odin. But I selected bootloader instead of PDA wrongly, Then I selected start. My Camera rebooted and not opened. Just showing "samsung galaxy camera" logo.
If somebody help me, I will happy.
Flash stock rom
7dervish said:
Hi;
I'm using samsung galaxy camera. I wanted to root with odin. But I selected bootloader instead of PDA wrongly, Then I selected start. My Camera rebooted and not opened. Just showing "samsung galaxy camera" logo.
If somebody help me, I will happy.
Click to expand...
Click to collapse
You should be able to flash the stock samsung standard rom. It will update everything including the bootloader. Haven't had this problem, but this solution seems logical. Download the full rom and flash with PDA option.
Good luck.
ant75 said:
You should be able to flash the stock samsung standard rom. It will update everything including the bootloader. Haven't had this problem, but this solution seems logical. Download the full rom and flash with PDA option.
Good luck.
Click to expand...
Click to collapse
Thank you,
I flashed stock rom. SGC opening but touchscreen did not work. Just otg cable with mouse.
I will send to samsung service on monday
7dervish said:
Thank you,
I flashed stock rom. SGC opening but touchscreen did not work. Just otg cable with mouse.
I will send to samsung service on monday
Click to expand...
Click to collapse
There is no solution for touchscreen problem. You just give service your camera and they change touchsreen. Cause it's a hardware problem
Jeah it definitively was an HW Problem. Got a New Touchscreen and all works fine
Gesendet von meinem GT-I9100 mit Tapatalk 2
A pity, read the solution, because I'm at the same point
This is an old unofficial version. Please go to THIS thread for the updated, official version.
All information below this line pertains to the old, unofficial version. Use the link above to get the official version.
Updated (v2) Slow recovery bootup fixed.
This is an unofficial version of CWM Advanced/PhilZ Touch recovery. Main thread located HERE. Go to the main thread to learn about all the features.
It uses the zImage and ramdisk provided by @ketut.kumajaya with a few tweaks to get it working made by myself.
Please take a moment to say thanks and/or donate to @ketut.kumajaya for helping us out.
It takes a few seconds longer for CWM based recoveries to boot than the stock recovery, so be patient.
Credits go to:
@Phil3759 for the advanced features
@ketut.kumajaya for the working zImage
and of course Koush and the CyanogenMod team
Link to kernel source https://github.com/kumajaya/android_kernel_samsung_lt02
~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the on-screen menu doesn't show, hit one of the up/down buttons at the bottom to get it to appear. This is the same issue seen with CWM recovery and is caused by booting into recovery with the key combo. I highly recommend using the Quick Boot app or another software method of booting recovery.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Instructions:
1. Download ODIN on your computer.
2. Power off the device.
3. Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
4. Hit the "Volume Up" to enter download mode.
5. Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
6. Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
7. Select "PDA" then choose the recovery file you want to flash.
8. Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
9. Wait for device to restart. Skip this step if you unchecked auto reboot.
10. Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
11. To get the Internal SDcard to be recognized properly, choose the Advanced option; then touch the "Storage set to" option. It should change from "/data/media/0" to "data/media/". Then reboot recovery using the "Power Options".
I also recommend adjusting the Menu Height to a smaller value using the PhilZ settings option.
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if the recovery doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Instructions for recovery flashable version:
Boot into your previously installed custom recovery.
Select the Install Zip option.
Find the recovery zip.
Flash.
Reboot recovery.
Enjoy your new recovery.
Main Menu
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Cant change GUI height correctly, all the time i touch GUI it increases the value only...
batman08 said:
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Click to expand...
Click to collapse
I'm not sure what you mean about the time. It is not supposed to be in the status bar on the lock screen, and that has nothing to do with this recovery.
Sent from my DROID RAZR MAXX HD
gr8nole said:
I'm not sure what you mean about the time. It is not supposed to be in the status bar on the lock screen, and that has nothing to do with this recovery.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Ok, haven't paid much attention to that to be frank.
batman08 said:
Downloaded and installed. What i found so far is that it reacts little slow and the time in the status bar is gone in lockscreen.... After unlocking clock comes back in status bar.
Cant change GUI height correctly, all the time i touch GUI it increases the value only...
Click to expand...
Click to collapse
In regards to it reacting slowly, since you complained about that with TWRP also, I believe that is a problem with your tablet. I can't imagine it working any faster on mine. Every selection is immediate.
Keep increasing the gui height until it goes to a lower value (around 100 it switches).
Sent from my DROID RAZR MAXX HD
gr8nole said:
In regards to it reacting slowly, since you complained about that with TWRP also, I believe that if a problem with your tablet. I can't imagine it working any faster on mine. Every selection is immediate.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Some other users also experienced slow reaction with latest TWRP. I used TWRP 2.5.0.0 and speed and reaction was ok, on 2.6.xx reaction is slow...
Awesome job. Like how this is all coming together slowly for this tablet...
gr8nole said:
This is an unofficial version of CWM Advanced/PhilZ Touch recovery. Main thread located HERE. Go to the main thread to learn about all the features.
Since your in the recovery mood you should check out shabbyPenguins recovery OUDHS I think
Click to expand...
Click to collapse
my phone is samsung GT-I8268 Marvell PXA988 kernel
please Compile CWM Recovery for I8268
@ketut.kumajaya
Can we have cwm flashable zip please.
Regards.
Sent from my GT-N7100 using xda premium
nitol said:
Can we have cwm flashable zip please.
Regards.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Done. Flashable zip in OP.
After flashing one of the custom ROM's, I still get Android System recovery in Recovery mode. Tried 3 different ones, not working... Anyone? In Download mode it however says Custom...
/edit: turning off auto-reboot fixed it!
OP updated with v2. Slow recovery bootup fixed.
Ive tried this with auto reboot checked and unchecked.. and im still getting android recovery. I have Kies installed.. do i need to install drivers on my pc?? I waited several minutes but all i get is leave cs...
freak69ize said:
Ive tried this with auto reboot checked and unchecked.. and im still getting android recovery. I have Kies installed.. do i need to install drivers on my pc?? I waited several minutes but all i get is leave cs...
View attachment 2418355
Click to expand...
Click to collapse
Hit START
Ohhh.. DUHHH... hahaha i should have know that seeing thats how i rooted my S3. So i take it i have root also now right?? Or do i have to flash something else?
freak69ize said:
Ohhh.. DUHHH... hahaha i should have know that seeing thats how i rooted my S3. So i take it i have root also now right?? Or do i have to flash something else?
Click to expand...
Click to collapse
Flash the root.zip from the cwm or twrp thread.
Sent from my DROID RAZR MAXX HD
Hi, i have a t217A tab 3 7.0 and it has a msm8960 cpu not the msm8930 you mentioed earlier, which shows up under cpuz as a Krait 1.73 gighz
when i boot to recovery it says encrypted and the flash fails. im guessing i need a diffrent version. is there a current build for the touch screen recovery for this version already made and in place ? if so could someone link me ?
and i had a q , you mention that this should be flashed via already flashed recovery , is this mandatory or can i flash the touch version via odin straight away ? do i need to flash the regular non touch recovery then flash the touch or can i get away with directly flashing the touch recovery without first flashing the non touch?
I have rooted already , the method on this forum worked for the t217A
thanks
spydergt said:
Hi, i have a t217A tab 3 7.0 and it has a msm8960 cpu not the msm8930 you mentioed earlier, which shows up under cpuz as a Krait 1.73 gighz
when i boot to recovery it says encrypted and the flash fails. im guessing i need a diffrent version. is there a current build for the touch screen recovery for this version already made and in place ? if so could someone link me ?
and i had a q , you mention that this should be flashed via already flashed recovery , is this mandatory or can i flash the touch version via odin straight away ? do i need to flash the regular non touch recovery then flash the touch or can i get away with directly flashing the touch recovery without first flashing the non touch?
I have rooted already , the method on this forum worked for the t217A
thanks
Click to expand...
Click to collapse
No , it has msm8930 it will still show as 8960 it's a qcom thing. Also this isn't for your device.
Hello together,
i used search and the suggested topics but i cannot see the same problem as i have.
Recently i rooted my 4x hd with success (i used Kingo Android Root, as i found here in the forums) because i want to install Cyanogen Mod, installed Rom Manager and downloaded the CWM Recovery (not the touch one, the lates it can find, 6.# or something was it) through that. Then it got installed and finished without error. Of course i gave Super SU right to Rom Manager. Its shown as installed in Rom Manager too.
So the problem starts when i want to boot into the CWM, no matter wich way (through volume down + power or in Rom Manager with the "boot into CWM" option. When i try this all i get is 2 lines in minimal red font on a black screen. I forgot was was written there but it was really hard to come out of that. Finally the phone booted normally. I tried it 2 more times, with same results. I also re-isntalled the CWM over the Rom Manager, it just stays like this.
Whats wrong?
Senchay said:
Hello together,
i used search and the suggested topics but i cannot see the same problem as i have.
Recently i rooted my 4x hd with success (i used Kingo Android Root, as i found here in the forums) because i want to install Cyanogen Mod, installed Rom Manager and downloaded the CWM Recovery (not the touch one, the lates it can find, 6.# or something was it) through that. Then it got installed and finished without error. Of course i gave Super SU right to Rom Manager. Its shown as installed in Rom Manager too.
So the problem starts when i want to boot into the CWM, no matter wich way (through volume down + power or in Rom Manager with the "boot into CWM" option. When i try this all i get is 2 lines in minimal red font on a black screen. I forgot was was written there but it was really hard to come out of that. Finally the phone booted normally. I tried it 2 more times, with same results. I also re-isntalled the CWM over the Rom Manager, it just stays like this.
Whats wrong?
Click to expand...
Click to collapse
You did unlock your bootloader, didn't you?
If not your bootloader gets screwed and you have to reflash kdz (search for tutorials).
You can't boot into cwm because if the BL is locked, you don't have the permission to change recovery/rom
(not actually permissions I think but easier to describe it that way).
So the recovery is now corrupt and there's no way beside the one I already mentioned
(you can try to unlock your BL but I don't know if it's possible in your state.
Omario-242 said:
You did unlock your bootloader, didn't you?
If not your bootloader gets screwed and you have to reflash kdz (search for tutorials).
You can't boot into cwm because if the BL is locked, you don't have the permission to change recovery/rom
(not actually permissions I think but easier to describe it that way).
So the recovery is now corrupt and there's no way beside the one I already mentioned
(you can try to unlock your BL but I don't know if it's possible in your state.
Click to expand...
Click to collapse
Thanks for the fast answer. Makes sense,
In the tutotial i followed that time was unlocking bootloader not mentioned, i didnt do this by hand, no. Honestly i thought this will be done by the root tool.
Edit: found your answer to that, sorry.
Anyway, so can i still do this now or did the bootloader got already srewed on first try when accessing CWM?
Sorry I was a bit incorrect. The bootloader should be fine (at least when you reflash kdz as the stock recovery will get flashed as well). After that you can unlock your boot loader and flash any custom ROM.
Sent from my LG-P880 using XDA Premium 4 mobile app
Omario-242 said:
Sorry I was a bit incorrect. The bootloader should be fine (at least when you reflash kdz as the stock recovery will get flashed as well). After that you can unlock your boot loader and flash any custom ROM.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks.
I did it in another way, i think it solved it too (probably its doing the same...). I downloaded the LG Support Tool from website and used the Option "Repair Upgrade-Errors/ Behebe die Update-Fehler" without to really know what happens (hehe) and it seems to reflashed some important things, without to wipe any data though. Anyway, the root is gone now but i can go into the LG Recovery at least.
What bugs me a bit is the question if this LG recovery is the standard or if theres still a problem? Because the "recovery" i mean is only a picture with an LG Logo and something like "LG Recovery Mode -- Service Center. After put out and re-insert battery use the power button to keep using the phone."
Is this the real recovery? I had a lot of phones but never saw a recovery like this...