hi.
Unfortunateley i bricked my lg l'fino d290n.
Is there a way of booting from sdcard?
my lg cant be seen by my computer using usb-connection any more.
Behavior:
powered off connected to usb: loadscreen appears, but freeze
normal start: lives good screen appears, but freeze
download start (volume up + usb-connection): lives good screen appers, but freeze (no downloadmode any more)
hard-reset start (volume down + poweron, pause,volume down+poweron): Hard-reset screen appers. you can answer both questions (with volume up/down and powerbutton), but the reset screen freeze (checked several times and waited up to an hour), no boot after that.
to get shure, i tested the usb-connection with a new cable on another pc using win10 ( installed new qualcomm driver). No connect.
system of my support-computer is win xpsp3.
this is what happened:
the handset was succesfully rooted 2 years ago.
10 days ago i tried to restore a backup with twrp, ignored the errors and decided to reboot (didnt add supersu).
lfino was not able to boot after this. I then didnt do a hard reset (and dont ask me why), but decided to flash
the device with flashtool2014, since the downloadmode was working.
apparently i missed to install the right .netc++distributable. An error popped up, but it was not readable. The downloadscreen - a loadbar- of lfino freeze at 2% while downloading . after some minutes i cut the usb-connection.
After this, the handset behaves like described above.:crying:
Well. later I found out, that the sd card (where the backupd files of twrp were saved) couldnt be saved by Win32Diskimager (2tb size????) . Having a look inside the files, i found out, that something was wrong with the backup-file system.ext4.win. (explorer chrashed trying to copy, terracopy showed an error too).
Looks like, the restore failed because of this.
Then the flashing failed because of the wrong c++distributable, or i just had to wait longer (as stated in one of the describtions found here).
any Ideas, e.g. a reset thru a reset point of the motherboard?
Related
Ok this might seem strange, and just bare with me if I'm being thick...
I have had a nose around the forums and done a search but I couldn't find a solution to my problem.
I installed CM6 (by bumblebee) on my vega via CWM and instantly got BSOD - I didn't really think this was a problem because I knew the risk that it might happen and I had already done a backup etc.
However, all the parts for my new computer arrived the next day so I forget about my BSOD vega for a week as I started building my new computer and setting it up etc etc
I just got round to sorting my vega out when I realised I had completely wiped my old laptop with all the adb drivers on it etc (because I was going to sell it). Therefore, I cant get into recovery or flash anything to it because I cant use any adb commands :s (I cant reinstall the drivers - windows wont recognise the device as adb, only as a mobile device...).
Any suggestions? Am I being thick? Thank you for taking time to read through my rambling post anyway
You should be able to get into recovery and re-flash a stock rom. Make sure the device is plugged into the power and usb. Open device manager in win 7. Then hold down the back button for 2 secs then while still holding back hold power for 2 secs then release power but keep back button down for 2 more secs under universal serial bus controllers a new device should pop up. Point that at the usb drivers from the advent website. When the drivers have installed the screen on the vega will still be black but you should be able to flash the stock rom and start again.
Hope that helps
I will give that a try thanks for your help
Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.
willk22 said:
Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.
Click to expand...
Click to collapse
Keep trying to put it into recovery mode. At times it gets picky and you have to time it just right. Took me several attempts before it worked correctly again, so keep at it
Also, be sure to keep the USB plugged in while you are attempting to get it into recovery-mode and your sound turned up so you hear the infamous hardware-connected sound. Once you hear it, immediately plug in the power and start the recovery-flash. Do not wait too long or you'll have to start from scratch again
Keep at it, you're almost there.
Got there in the end thanks for your help!
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
Hello there!
I have already used the search function, but I wasn't able to find my exact problem in any other post.
Yesterday I flashed the rom Carbon (4.4.2 maded by coderzs) on my p705, and today It appeared with the LG logo a little buggy, then I take out the battery and it never turns on again (no matter what key combination I used) and another surprise is that my 32gb micro sd was corrupted too, I can't even format it with HP disk storage format tool, neither I can use Recuva to get the files.
Plus, when I connect the phone to USB withouth battery it gets really hot.
Do anyone have an Idea of what to do? Actually I'm more concerned in recovering the SD card info or at least use it again in the future.
Thanks in advance.
New Info:
Now I can make it boot LG logo sometimes, but it still buggy and there is no key method to enter bootload emergency is working. =S
try this
nehuy said:
1 Actually I'm more concerned in recovering the SD card info or at least use it again in the future.
2 Now I can make it boot LG logo sometimes, but it still buggy and there is no key method to enter bootload emergency is working. =S
Click to expand...
Click to collapse
1 try putting it in a blackberry while its on (old bb are the best) and it will prompt its corrupted say yes to format and then try plugging into recuva (worked for me numerous times)
2 did you try vol+ and vol- and power hold and release power after vibration and then use KDZ_FW_UPD_EN.7z
try link2sd it does same but on a different level
IGGYVIP said:
1 try putting it in a blackberry while its on (old bb are the best) and it will prompt its corrupted say yes to format and then try plugging into recuva (worked for me numerous times)
2 did you try vol+ and vol- and power hold and release power after vibration and then use KDZ_FW_UPD_EN.7z
try link2sd it does same but on a different level
Click to expand...
Click to collapse
I will have to try to put the sd in another phone, but I don't know anyone with bb =S
Also, the only way to make the phone "boot" is holding vol+ (and any other key) and then it vibrates and sow a buggy LG logo, then it continously restart over and over again showing different buggy logos (LG ones).
THanks for the reply.
Other than trying kdz flash you can use LG official update tool to do an emergency update. You will in that process need to enter both imei&serial. Basically this also flash kdz but in addition it check and repair your partitions.
Hope it might help you :beer:
I will try that last advice, thanks
The SD card seems dead =S
It is recognized by the computer and devices, it shows 1gb instead of 32 and it needs to be formated, but no program let me do it.
I already have this problem with my girlfriend's phone last week-end and solve it!
I use a modified stock rom (root + cwm in KDZ) avaiable here http://forum.xda-developers.com/showthread.php?t=2214717. ROM KDZ V20A_00 ROOT
Put the phone in emergency mode (power off the phone, plug it on usb to your pc, wait for the battery logo then press vol+ and power)
Start KDZ updater then flash the rom. After install, start cwm (vol+ vol- power home at same time) and do a wipe data factory reset and wipe dalvik and cache.
Reboot and it work! :victory:
Yes, I already did it too in the past, I bricked my phone twice, but this time is a hard brick, and wont let me get to emergency mode (there is no way, really I test it). It seems that I can't make it boot =S
Maybe all this is because I was using ART instead of davlink, and something may explode inside the phone.
Thanks anyway for the reply, I'l keep searching for some solution (the SD have more chances to keep alive I guess)
hmmm
nehuy said:
Yes, I already did it too in the past, I bricked my phone twice, but this time is a hard brick, and wont let me get to emergency mode (there is no way, really I test it). It seems that I can't make it boot =S
Maybe all this is because I was using ART instead of davlink, and something may explode inside the phone.
Thanks anyway for the reply, I'l keep searching for some solution (the SD have more chances to keep alive I guess)
Click to expand...
Click to collapse
does your phone come-up with blank (black but backlit) screen ?
if it does then you will be able to use kdz updater in attachment LG-RDTT_1.0.5.4 (needs included windows enabler for this version)
use THIS GUIDE to flash just skip the hosts file editing steps
and let us know
Okey, I'll try it in a moment
well, it didn't work =S
Computer don't recognize the phone, I tried with ubuntu, 3 windows and 2 mac.
When you say buggy logo do you mean there is visual distortion to screen?
if so it most likely will be hw damage
you got ubuntu can you see it in adb ?
Push/pull ?
IGGYVIP said:
When you say buggy logo do you mean there is visual distortion to screen?
if so it most likely will be hw damage
you got ubuntu can you see it in adb ?
Push/pull ?
Click to expand...
Click to collapse
No, and I'm not able to mount it neither.
The logo is as you say, but it reboots constantly and make some little color bars blur the image, then restart again and make some other kind of buggy image :x all with LG logo.
--------------------------------------------------------------
Well, I finally choose to go for LG service, I'm going to call them tomorrow.
Thanks for the help and trying to solve my problem, I guess they will make my phone boot, but my SD will never come back, or that is what is seems =(
It keeps saying that it is read only, and that's why I can format it.
hello
i reinstalled my ROM after installing FREEDOM and the google play wasn't working
i installed it about a month ago and it worked out fine, i rooted the phone again but didn't do anything with it
today after using the phone for a couple of hours i plagged the charger in and then i saw that the screen is all black
and all that says is :
fastboot mode started
udc start
i tried everything with the power + vol down and it keeps getting into the same screen
the phone just stuck in this and i can't recover it
i have read the other questions that people wrote here about this problem and couldn't find an answer
PLEASE HELP ME SOLVE THIS!!!
nir3011 said:
hello
i reinstalled my ROM after installing FREEDOM and the google play wasn't working
i installed it about a month ago and it worked out fine, i rooted the phone again but didn't do anything with it
today after using the phone for a couple of hours i plagged the charger in and then i saw that the screen is all black
and all that says is :
fastboot mode started
udc start
i tried everything with the power + vol down and it keeps getting into the same screen
the phone just stuck in this and i can't recover it
i have read the other questions that people wrote here about this problem and couldn't find an answer
PLEASE HELP ME SOLVE THIS!!!
Click to expand...
Click to collapse
I was in the same situation tonight. I have the AT&T variant. I found the answer on droidforum(dot)net by member HARVESTERX:
"OK, so you're booting into fastboot and trying to ADB from there? Have you tied booting into recovery (since you said that you were able to successfully flash one)? I'm on the Verizon G2 so not too familiar if it's the same on your model, but to get into recovery I power on the phone by pressing and bring the power and volume - buttons at the same time. After seeing the LG logo I have to release both buttons and press and hold power and volume - once more which takes me into the factory reset mode. From here press the power button a few times as if I'm doing a factory reset and it loads up TWRP from there.
This has saved my ass once already because I wiped my internal storage mount by accident and deleted all my backups and ROMs, so I used a Windows XP computer (can't get any other version of Windows to recognize my device...well I know how but it involves more time than I have at the computer as it's not mine) and pushed a ROM over using ADB that way. It's been a few days so hopefully you've fixed the issue... "
This method put me into TWRP and I was able to RESTORE my phone to the backup I had done earlier this evening.
I hope this helps!
JACE759
Hi there!
So I rooted my LG G2 (D802, 4.4.2, Stock, used ioroot) yesterday.
I intend(ed) to flash the Optimus G3 Rom, in the start post they recommended to flash cmw/twrp via "Simple Tool 3.2" (http://forum.xda-developers.com/showthread.php?t=2633941). After doing so (I used the automated version, not the manual one) I got STUCK ON THE BOOTSCREEN. There is a notification popping up for a few seconds in the left upper corner which lists several errors occurring:
BOOT CERTIFICATION VERIFY
SECURE BOOTING ERROR;
CAUSE: BOOTCERTIFICATION VERIFY
along with the following numbers listed from top to bottom: 710, 760, 810, 860, 910, 960 (I just noticed, the numbers can vary, but always follow the same pattern...)
after this message, the screen fades to black, I think it it is still running though, since it takes more than 10 seconds to reboot the phone by pressing the power button. I still have access to the button down/power button combo which leads to a factory reset setting, but it doesnt do anything for me since I still get stuck at the lg boot screen.
I
Atm I dont what to do! Enter download mode and flash something? I'm seriously kind lost here. So, thank you for your help!
Cheers
You flashed a custom recovery version thad doesin't match you phone ( example you flashed D801 recovery on D802 phone )
Just search in Q/A and you find the solution to fix it. Be calm , if you phone is booting - you can fix it
If you are lazy , i searched it for you. http://forum.xda-developers.com/showthread.php?t=2694530
harkis123 said:
You flashed a custom recovery version thad doesin't match you phone ( example you flashed D801 recovery on D802 phone )
Just search in Q/A and you find the solution to fix it. Be calm , if you phone is booting - you can fix it
If you are lazy , i searched it for you. http://forum.xda-developers.com/showthread.php?t=2694530
Click to expand...
Click to collapse
Thanks a ton!! Finally I can put a name on the problem (bricking...)- Ironically I never mangaged to get there in 3years of samsung flashing but got there within 15mins of flashing on the LG G2. I guess it's true what they say about samsung devices, as hard to brick as a brick...
I'll report back if it worked...
Weeell, as it turns out my phone isn't recognized by my pc (Win 7) anymore...I literally can't do anything. Any hints?
I can use the Tool, but it's always trying to connect to my phone without success. But when I connect my phone to the computer it opens a dropbox window (import photos) and several windows partitions, which it tells me to format...
thechillerdewd said:
Weeell, as it turns out my phone isn't recognized by my pc (Win 7) anymore...I literally can't do anything. Any hints?
I can use the Tool, but it's always trying to connect to my phone without success. But when I connect my phone to the computer it opens a dropbox window (import photos) and several windows partitions, which it tells me to format...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2687768