[GUIDE] Unbricking your O3D

[GUIDE] Unbricking your O3D - LG Optimus 3D

Hi to all,
Been here for a while and every time i log here in XDA (O3D forum), I always see new people bricking their newly bought O3D (stuck on LG Screen..., rebooting only to cwm recovery.., etc..etc..). If you got into a situation just do the search thing before posting a new topic which is already been posted because our forum (O3D Community) is still small so searching wouldn’t be a problem and there’s no need for a dig yet when reading all the topics posted here. All i can say is for all the people who just bought O3D always remember this "If it aint broke then don’t fix it" you will just end up voiding your warranty,
if there’s an update don’t try to push it on your warranted device, try to check first if the update is applicable to your device (country or region) because we all know that LG only released O3D in Europe so if you are in that place and check that your devices have an update, go grab it, but when it fails always call LG Europe (because you have a warranted device and they will assist you) and explain to them that you are experiencing difficulties in updating your unit, and for everyone else who is not in Europe (like me were my unit is not warranted)be very careful if you want to forcefully push that update to your unit (v10b, v10d or even cwm 4.0.0.9) because me i already bricked my device 3 times were i end up booting only in LG and nothing follows, the other is booting only to CWM again and again, and the last one is after unbricking the device and setting everything then when rebooting the unit it will end up stuck at the LG original android recovery system <3e>menu.
Note: Do this procedure at your own risk, i repeat "AT YOUR OWN RISK", its your unit so its your responsibility, you've been warned, i myself grab that risk and now I’m happy with my unbricked O3D (v10d July, 8, 2011 with fully working CWM 4.0.0.9), all the tools we need are here at XDA so there will be no problem getting those tools.
Ok enough about nonsense(hahaha), lets go down to business. As what the Title says, here we go.
Requirements:
This method will only work in WINDOWS XP MACHINE, i have tried it in Vista and Windows 7 but it will just hung.
I assume that all the necessary drivers are already installed from your machine because without them you can’t bricked your O3D. If by any means you don’t have it, just grab it from http://www.lg.com/uk/support/mc-support/mobile-phone-support.jsp and click the download link save it then run it after installing, it will run automatically, then do the following:
1. Go to Customer Support ---> Application, Manual & USB Driver Download.
2. Enter you IMEI then click the Search button.
3. After Searching, it will list two files form the File List, double click any of those file (me, i choose the file with divX converter)
4. After downloading, it will extract its content to C:\LGP920
5. Go to this directory C:\LGP920\USB_Driver, and double click LGUnitedMobileDriver_S4981MAN33AP22_ML_WHQL_Ver_3.3
6. Let it finish then if it ask to restart your pc, do it.
7. Optionally you can install the LGPCSuite, it can be found in c:\LGP920\LGPCSuite\, just double click the LG_PCSuiteIV_Setup.exe and follow the instruction.
Now that we have installed the drivers for O3D, we can move on to the next instruction.
Make sure to follow the instruction carefully and proceed if you know what your doing.
I have edited nikhil4186 and victortangocharlie post (Original thread: http://forum.xda-developers.com/showthread.php?t=1060121)
1. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
2. [IMPORTANT] Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.).
3. Remove the Micro SD from your O3D.
4. Download the KDZ rom v10b_00 posted by Fab985 : http://forum.xda-developers.com/showthread.php?t=1155874
(v10d_00 is already available but this method is only tested with the v10b_00 rom, so if you wanna try your luck, its up to you)
5. Download the KDZ updater - http://forum.xda-developers.com/showpost.php?p=8651505&postcount=1
6. Extract it, then run the msxml.msi
7. Now the next step will be crucial because you need a full battery (for safety of course if you don’t want your unit to die while in the middle of the unbricking process) and you will put your unit in emergency mode (by pressing the power button and the volume up button), here’s how you will do it.
Case A. (This is my Case)
If your O3D can boot but only in CWM, charge it (me, i charge mine for 3hours in cwm), you wont see a charging status but you will feel your battery getting warmer.
Case B. (Never happen to me)
If your unit is just stuck at LG logo, try to charge it too and see if your battery is getting warmer, if not, better find another way to charge your battery or a friend who has O3D and borrow the battery.
Once everything is ok proceed to step 8.
8. Open Device Manager and under Modems check if you really disable the LGE Virtual Modem, if it is already disabled don’t close Device Manager, we will need it on the next step. Make sure you can see your Device Manager window and your modems devices are expanded (were you can see the disabled LGE Virtual Modem)
(THIS IS THE TRICKY PART AND YOUR O3D WILL JUST STAY BLACK SCREEN)
9. Plug your USB cable to your pc and then plug it to your phone then enter Emergency MODE (power button plus volume up button) This step is very tricky (me, i tried it several times before it detect my O3D as LG USB modem).
First when your pc detects your O3D, it will detect as OMAP4 then it will look for its drivers, just cancel it, then another device will be detected, if you successfully entered Emergency mode, your O3D will be detected as LG USB Modem, this modem should stay, if it disappear then you failed to enter the emergency mode correctly, try it again before continuing to the next step.
10. Run KDZ_FW_UPD.exe from the extracted folder.
11. Put the following settings:
Type : 3GQCT PhoneMode : DIAG
12. Under the KDZ File, choose the KDZ file you've downloaded from Fab985 post (v10b_00)
13. Press the Launch software update. (this part will take time because it will extract the kdz file into cab file, it took me 15 to 20 mins before it proceed to the updating process)
14. Once updating has started you will encounter this message:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
This message will come out from 1 to 100 counts:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
CDMA: wPrama = 2004, IParam = 2
Model Dll Msg Not Found(2004, 2)
And so on till:
CDMA: wPrama = 2004, IParam = 100
Model Dll Msg Not Found(2004, 100)
(Note: This message is case to case because i experienced diff counts then the LG USB MODEM disappear from the device manager list, first attempt count 64 then LG USB Modem disappear from the list, the kdz flasher stops from count 64, waited up to 10 minutes but nothing happens so tried it again from the enter emergency mode step, second attempt count 76 LG USB modem disappear but after a while kdz flasher still continues up to 100 counts then it stop there, waited for 5 minutes nothing happens so decided to remove my device and turn it on and viola it booted to LG original Android system recovery <3e>)
15. After you reach the 100 counts, the process is done, the LG USB modem from the Device manager will be gone, but don’t remove yet your phone to reboot it, try to wait up to 5 minutes before disconnecting your phone.
16. Turn on your O3D, if it boots in LG original android recovery, just choose the wipe data/factory reset, then reboot system now. Then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 17.
17. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition then reboot system now.
18. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 19.
19. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition, and lastly wipe nv dynamic partition then reboot system now. (this part resolve my rebooting issue)
20. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not I guess it’s the end of the line for now.
Sorry for this very long instruction. If it helps you I don’t have a beer fund because I’m not a dev. but a simple hit with thanks will do.....
TIPS NOT RELATED TO UNBRICKING:
Rooting:
Run SuperOneClick as Administrator, before clicking Root, click first the Driver Check and if no problem has been detected, no more settings is required just click the Root button then wait until it says done or finish.
ClockWorkMod:
After rooting, download rom manager from the market, after the install run it and tap Flash ClockworkMod Recovery (4.0.0.9), once successful you may now backup your current rom before you mess again with it, since I installed cwm in my O3D I never use the buttons to boot with it(power button plus volume down button), I always use the menu's with the rom manager to boot into or backup or restore or flash in CWM.
Upgrading:
For safety purposes, if you have a warranted device and then an update pops out, always do a fresh start, what I mean is if you already rooted your device and installed CWM, better removed it first before updating your O3D so when things goes wrong from your update process you can always call LG for it to be fix eliminating the needs to post something like “Help I brick my O3D and I can’t bring it to LG because I installed CWM blah blah blah etc.. etc…”, got the point so be responsible.
For the Mod: Sir if my post will violate something feel free to removed this post. more power XDA!!!!!
Many thanks to the following:
Aremcee
Renegade_Rules
Fab985
ik911
nikhil4186
victortangocharlie
and everyone here at XDA....

thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still

wuper said:
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
Click to expand...
Click to collapse
Did you follow the whole step, I know its a long process and it work with me, just follow everything and when you are in step 9 were you need to enter emergency mode,its a tricky step,make sure LG Mobile update is not running completely,open your pc device manager and expand the modems,try to remove the battery then press volume up and power button, put the usb cable then put back the battery,it will vibrate then your xp machine will detect it as omap4 device just cancel it but don't de-press the volume up and power button,then after a while it will vibrate again check if you see LG usb modem in the device manager,once you saw it and it stays,it means you successfully entered emergency mode then that will be the time you will run the kdz flasher and follow the succeeding steps.
Sent from my unbricked LG-P920 using XDA Premium App

bro I tried it with lg mobile modem disabled lg virtual modem disabled both are not disabled both are disabled but none of them make sense. Model Dll Msg Not Found(2001, 0)
is written and lg mobile driver gone but the phone does not reboot both 10d and 10b tried I restarted manually and it opens with fw update screen

I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?

wuper said:
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
Click to expand...
Click to collapse
I have bricked my phone numerous times, and in many imaginative ways. The above instructions are pretty much what I do whenever it gets stuck in some non-functional mode.

I tried this way like 30 times during the last week, I just got back from holiday and I just tried it on a Win XP machine and it's always the same it flashes and it never reboots, V10B/D doesn't matter... After flashing I manually power it on, and only get the Firmware update screen and it hangs there forever... I called LG today waiting for a replacement.

@aremcee
Sir thanks for confirming that this method really works.
@wuper @renegade_rulez
Are you doing it in xp machine, if you run it in Windows 7 the process will just fail. Only disable the LG virtual modem from your pc device manager and completely exit LG PcSuite and LG Mobile update. Make sure your xp machine detects your O3D as LG USB MODEM and not omap4 device, the detected LG usb modem should stay in your device manager under modem and it should be enable then you can now start kdz flasher. Will try to investigate what causing your O3D not to flash using the kdz flasher and if I have time will upload a video on how to properly enter emergency mode.
@all
Thanks for reading this, if you have a question just post it here and will try to answer it back as knowledgeable as I can.
Sent from my unbricked LG-P920 using XDA Premium App

if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.

wuper said:
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
Click to expand...
Click to collapse
Hi wuper,
Can you try after flashing then turn on your device to recovery by pressing volume down + power button, or remove your battery then put it back while pressing those buttons, will it go to android recovery system <3e>?, if yes try to wipe everything then reboot. let me know. thanks.

Like wuper just told, mine is the same... It's not fixable in that way. Again this morning I tried on my XP pc and it's always the same. Just called LG again they will replace it within 24h we will see
update:
You cannot get into the recovery system, holding power + volume down the phone will power on and off again, releasing power when it boots and keeping volume down pressed gets the Firmware update screen.

same for me cannot enter recovery

Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.

Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
Hi Zirowe,
Hmm thats strange, you and dnardz have the same problem, wiping the nv dynamic partition solved my rebooting issues and didnt experience this battery not charging problem, try to root your phone and install clockwork recovery 4.0.0.9 then reboot to cwm and full wipe your O3D including the battery stats, then charge your phone again and see if it is charging(maybe two hours), if it still doesn't work, download the v101d cmw rom by PUAJohn and restore it. Let me know

Thank you, I will try it.

Will try it too..thanks Johnance17.

hefonthefjords said:
try deleting batterystats.bin then rebooting.
Click to expand...
Click to collapse
I've tried, but no luck, unfortunately, everything is the same..

hi,
It's strange what happens to you.
Have you tried this?
-Turn device off
-Take out batery
-Wait 5 min
-Re-insert battery
-do a hard-reset
-boot up device completly
-Turn device off
-plug-in charger (NOT USB-PC)
-Wait 1 hour
sorry I do not see much solution

It didn't work on mine also...restoring 10d and erasing battery stats..

Related

[Q] Unable to factory reset

Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section

Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).

I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.

Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App

Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?

I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.

I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back

Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.

rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything

DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty

I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric

Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App

rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.

Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.

Samsung I9103 Galaxy R Repair Dead By USB Cable no need JTAG NO Need Disassembly Phon

Samsung I9103 Galaxy R Repair Dead By USB Cable no need JTAG NO Need Disassembly Phon
Download Links:X0X0X
Password:forum.sptbox.net
how to enter APX mode:
hold "vol up"+"home" then connect usb cable to dead phone
after repair done phone will auto in download mode
full flash it by Odin all will ok
Enjoy free dead repair soft now
=======================
---------------
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

iKevinShah said:
also for hard bricked phones :/ ???
Click to expand...
Click to collapse
If you can enter APX Mode then it's rescuablr
Herpderp Defy.

I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.

Klajnor said:
I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.
Click to expand...
Click to collapse
Do U mind sharing how to?

I'll try do it, but my english is bad. I thing will be difficult to understand what i mean.

Klajnor said:
I have use this method and custom kernel = 0.
Nice work! But instruction is now enough full. It took about 3 hours of time to make sure that the phone worked.
Click to expand...
Click to collapse
Could you tell what you did in a step by step manner, so that even the others facing the problem can use this method to solve it.

Mini step-by-step instruction:
0) Download and unpack archive to directory like c:\repair
1) Entering APX mode. Turn off phone. Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port.
Install drivers from folder drivers in archive. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. It is mean that phone in APX mode.
You may try this method to enter APX mode: remove battery and unplug phone from PC. Hold Volumel Up + Home and plug phone to PC. Phone must be in APX mode now. Put buttery in phone.
2) Before do something do do nandroid backup. Copy it to PC.
Backup /efs to safe your IMEI.
3) Enter to APX mode, install driver and start GT-I9103.bat. If you have some errors - try again without rebooting phone. Or unplug-plug USB and try again.
Phone reboot in download mode.
4) Use Odin to flash ogiginal samsung ROM. I used сhinese ZCLA1 2.3.6. You must use PIT file to repartition file system of phone. p5.pit is on archive. If you try flash without PIT process will be fault.
5) When flashing finished load phone in recovery mode. Wipe /cache and try wipe /data.
Load android and format internal memory. Reboor in recovery mode again. Wipe all.
6) Now you have 100% work phone with custom counter equal zero, without yellow triangle and etc.
Take root and restore /efs to restore IMEI.
Take CWM, custom kernel and everything what you need.
Enjoy!
PS I have about 2-3 hours to sure phone work normal. If you know in advance - can be done in 15-20 minutes.
Google translate of my instuction( russian to english):
Training
0. Set unpack, better to go somewhere in the root directory, so in a way no spaces or other characters. But this is only a recommendation based on a small knowledge of Windows, I have a normal flash and the folder e: \ - = Samsung Galaxy R = - \ - = Dead Repair = - \
APX Mode
1.1 The largest shamanism - to be APX Mode. More or less reliable way, which I was able to do it - with the phone off hold down Volume Up + Home and plug the cord into the USB port. This method is reliable if the phone is alive.
If your phone firmware is broken (and it will be so if, immediately after the flash nvflash is not a normal firmware) - will have to catch this moment, because phone might try to get recovery (as it too may not be).
If you can not do it you can do: take out the battery, hold down Volume Up + Home and insert the cord into the computer. Once the phone is switched to battery mode APX return to the place, because flashing at a certain moment the phone off the USB port (just a guess, but without the flash batteries did not work).
1.2 After that, the phone went into the mode of APX, he determined on the computer as a device driver without APX. The driver is included. No problems with installation on Win 7 Pro SP1 x64 I do not have arisen. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. If you do so - then everything is fine.
2.1 What is necessary to have to start:
Actually set to restore the phone. He is quite self-sufficient.
Any firmware. I sewed the latest version of the Chinese I9103ZCLA1 2.3.6 firmware
Of course, Odin, the phone cord, and so you need to flash.
Be sure to make backup / efs. After nvflash IMEI, I folded to form 000004999900001 (well something like that, do not remember exactly).
If the actions are performed to reset the custom kernels - can be done at the beginning of nand backup. Yes, in general nand backup is needed in any case. Theoretically, such a scheme is possible: backup - nvflash - odin - cwm - restore. We get the phone in the same form but with zeroing counter. I am due to its krivorukost could not verify. In order not to repeat my mistakes - make a copy after the backup on your computer. It was quite unpleasant to lose all the settings over the last month (but then I blame myself, accidentally formatted the card).
2.2 Connecting the phone to APX to a PC, run GT-I9103.bat. If everything went without a problem - the script is complete without error and the phone goes into download mode. If there was a mistake - you can try again to flash.
For example when I have an error like in the image - just twitched and started the lace zanogo bat. I think if the phone was left in the mode of APX. My heart skipped a beat, but the second attempt the phone flashed fine.
Firmware
We sew a 3.1 firmware odin. Most importantly - do not forget to specify the file pit. It is a complete recovery. Bit to bit the same as there, that this firmware.
Without nutrition ask you not to succeed, because file system is a mess of half-dead sections. Sewed only some parts of the firmware. Once downloaded, the phone displays a picture of a bunch of Korean characters and English phrases like "Software update failure".
3.2 After the firmware partition / data, as I understand it, is not formed. I would suggest the following algorithm:
We go in and format the built-in recovery / cache.
Ship, and through him the android usb-format the drive. I then have to format it, just in case a recovery.
I do not know what will be if you try to install the firmware as soon as CWM, try to format all of them, and make recovery backup. I just have no backup at hand (accidentally formatted the same section of CWM / emmc and it was an external card, where to store my backups).
03.03 Well, after much room for activities. CWM and restore from backup or set up from scratch - you decide.
Conclusions:
When the curve could theoretically restore the firmware. Maybe even a bit boot-loader. I got the impression that the APX - a mode of the chip, not software. If iron is not dead - should help. In general, an hour and a half I have had the phone without a flash, probably the same at the time will resize partition to pull the cord and battery.
Resets the counter custom kernels, lost the yellow triangle. In general, if you flash the original firmware - can be easily dragged into service.
The method is not the easiest, there are many pitfalls, such as in the beginning, I forgot about the PIT, could not understand why the work is already in the phone memory is not working correctly, etc.
On the other hand, this method is not much harder than flashing the phone or through the odin cwm. Just add a few points.
Phone neubivaemy. Like my last samsung i780 (where I really made a mistake and did not start flashing in the sequence. And vykovyrivanie three parts of the firmware exe file - also had a very high risk). So much suffering in the firmware, but it is still alive. In general, I would say that acting on the instructions (or at least about following it) phone can not be killed. I love samsung for it.
Click to expand...
Click to collapse

Klajnor said:
Mini step-by-step instruction:
0) Download and unpack archive to directory like c:\repair
1) Entering APX mode. Turn off phone. Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port.
Install drivers from folder drivers in archive. After installing the device driver is defined as NVIDIA USB Boot-recovery driver for Mobile devices. It is mean that phone in APX mode.
You may try this method to enter APX mode: remove battery and unplug phone from PC. Hold Volumel Up + Home and plug phone to PC. Phone must be in APX mode now. Put buttery in phone.
2) Before do something do do nandroid backup. Copy it to PC.
Backup /efs to safe your IMEI.
3) Enter to APX mode, install driver and start GT-I9103.bat. If you have some errors - try again without rebooting phone. Or unplug-plug USB and try again.
Phone reboot in download mode.
4) Use Odin to flash ogiginal samsung ROM. I used сhinese ZCLA1 2.3.6. You must use PIT file to repartition file system of phone. p5.pit is on archive. If you try flash without PIT process will be fault.
5) When flashing finished load phone in recovery mode. Wipe /cache and try wipe /data.
Load android and format internal memory. Reboor in recovery mode again. Wipe all.
6) Now you have 100% work phone with custom counter equal zero, without yellow triangle and etc.
Take root and restore /efs to restore IMEI.
Take CWM, custom kernel and everything what you need.
Enjoy!
PS I have about 2-3 hours to sure phone work normal. If you know in advance - can be done in 15-20 minutes.
Google translate of my instuction( russian to english):
Click to expand...
Click to collapse
Nice!
Now many people in this forum should be able to get their Galaxy R back to life from the dead thanks to you!
Just one suggestion brother, keep on monitoring this thread if any person has any doubts or is facing any problem while trying to solve using your instructions, you could help them better.
I am going to directly link this post in the FAQ section.
Cheers (with a bottle of super fine Russian Vodka) !

Great job Klajnor! молодец!

'cooleagle' said:
Nice!
Just one suggestion brother, keep on monitoring this thread if any person has any doubts or is facing any problem while trying to solve using your instructions, you could help them better.
Click to expand...
Click to collapse
Ок. I will monitor this theme when it possible

One suggestion: Volume Up + Home doesn't bring any effect. To enter APX mode I had to press Volume Up + Home + Power button. Interesting that this is the way to reach recovery on some Galaxy handsets.

Volume Up + Home + Power button - it is also work. I wrote Hold Volume Up + Home buttons 10-15 second and plugin phone in usb port. I thing this way is more reliable

Hi,tried the above method for I9103 but when i proceed the steps it shows the download mode initialzed and the window shuts up and the fone remain dead,no response on fone. Installed drivers for APX and Iam using XP Sp3.

What window shuts up? bat script? If you mean bat - then that normal. If you want see result of it work use cmd.exe to run script.
Turn on phone in download mode( vl_up + home + power or vl_up + home and plug phone in usb) and try flash any firmware via onid (don't remember use pit file from firmware or from repair folder).

After restoration, at me runs not into a downloading mode, and in mode NVFLASH Recovery Mode

Just to report, there is no APX mode on my SGR
Wait is it just black screen?
Yesss it is

how is that possible?

Any chance to create this for P7500 / P7510?

Guys, sorry for OT.
http://forum.xda-developers.com/showthread.php?p=25125344#post25125344
According for the thread link above, does this method helps to solve it?
Thanks for your attention

i want to reset my binary without jig can anyone guide me with proper steps & i dont want to ruin my phone

my lg o1 stuck at lg logo, need help

Hi
I tried to install cm11
on The device
And the middle of the installation I registered it was canceled
So I had to install cm7
from the Memory card
I installed it
When I run the device
He got stuck LG logo
What to do?
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
And I followed - Upgrading from another CM10.2 or Older ROM
Sorry for the english, I'm from Israel
And I used google translate

eran32 said:
Hi
I tried to install cm11
on The device
And the middle of the installation I registered it was canceled
So I had to install cm7
from the Memory card
I installed it
When I run the device
He got stuck LG logo
What to do?
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
And I followed - Upgrading from another CM10.2 or Older ROM
Sorry for the english, I'm from Israel
And I used google translate
Click to expand...
Click to collapse
Boot back in to your recovery and wipe cache and dalvik cache. Format system and then install your ROM. There are major differences between CM11 and CM7. When making big jumps like that it's always best to format system before installing a ROM.

shinobisoft said:
Boot back in to your recovery and wipe cache and dalvik cache. Format system and then install your ROM. There are major differences between CM11 and CM7. When making big jumps like that it's always best to format system before installing a ROM.
Click to expand...
Click to collapse
I just did factory reset via cwm
And still have a problem
So do just what you say and do
system format?
You mean that you are going to have a system folder in the mount and stroage given formatting?

eran32 said:
I just did factory reset via cwm
And still have a problem
So do just what you say and do
system format?
You mean that you are going to have a system folder in the mount and stroage given formatting?
Click to expand...
Click to collapse
In CWM select Wipe data/factory reset. This will wipe the cache, dalvik cache and a couple other partitions. Then go to Mounts and Storage and select Format System. That will format the system partition.
Now go back to CWM home screen and install your ROM.

shinobisoft said:
In CWM select Wipe data/factory reset. This will wipe the cache, dalvik cache and a couple other partitions. Then go to Mounts and Storage and select Format System. That will format the system partition.
Now go back to CWM home screen and install your ROM.
Click to expand...
Click to collapse
thanks man, now my lg o1 works

Glad to help
Sent from my LG-P769 using Tapatalk

Hi,
May I ask for help here (instead of creating a new thread) ? I have the same problem: The device is booting loop at the LG screen. Bricked it when I wanted to save the ROM with ROM Manager.
I have no access to recovery mode, but Emergency mode does work (With and without battery).
I've followed multiple guides, including this one:
Most of you are stuck on a yellow screen with”Emergency mode!!” or the phone is not responding at all. You guys wanted a custom rom like Optimus Prime-v2 and let me tell you, this time it will work. Optimus One P500 comes with stock android 2.2 – V10a, V10b … and android 2.2.1 – V10n. They might be done for different regions depending upon the phone release and its popularity and definitely bug fixes and enhancements. To have Prime-v2 on your handset you will require V10a or V10b on your handset. Reason, V10n stock cannot be rooted easily. Rooting the handset is must if Prime-v2 is required on the device. Steps to install V10a, V10b series. I am using Windows 7 32-bit, 3 GB RAM laptop:
1. Clean your system first; get rid of LG PC suite and other stuff shown in Uninstall Program with vendor name as LG. Remove MSXML builts from the handset. Remove Nokia and other drivers if they are on system like Ovi suite etc. I also removed a lot of Microsoft runtime environments. Not sure about the reason but it worked for me.
2. LG usb device drivers, download the application B2CAppSetup.exe http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe .
3. In the Menu Bar, click "Options & Help", and click "Country & Language". Select the appropriate Country & Language. I used India and select P500 from the list that popup after you change the country and region. It will download, install and save the drivers somewhere in C:\LGP500\USB_Driver, it will prompt to open the rar files, just click and install the exes seen in them.
4. Reboot the system.
5. Right click on Computer -> Properties -> Device Manager and see for three drivers – LG android usb modem, LGE serial usb port and LG composite USB device. Disable the modem driver and reboot once again.
6. Switch off the phone and press volume up + BACK button + POWER button. Phone should turn yellow with text “Emergency Mode!!” To switch it off you have to remove the battery (I know it hurts, but that’s the only way out here). Switch off and let’s continue with the setup.
7. To do the KDZ of system you will require the KDZ software updater, links keep going off and on internet. Try searching for “KDZ_FW_UPD_EN” or “KDZ_FW_UPD_EN.7z” in Google and download the software. It should be somewhere around 2.3 MB. To use it you will required some good version of WinZip or winrar again Google it and install the 7z archive utility.
8. Install msxml.msi as the manual or readme.txt says to do so.
9. To get the V10x Official ROM, you need to first determine the ROM of your choice. List of all firmware available for LG Optimus One P500 (list of codes) http://csmg.lgmobile.com:9002/csmg/b2c/client/ezlooks_model_list.jsp?model=LGP500 , search for your country (use IE it looks sexy in it), I looked out for IND/INDIA. Download link to the ROM is http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/XXXXX/V10a_00/V10A_00.kdz where XXXX is code from list of codes. In my case it was: AINDBK. Save the file.
10. Prepare the handset by removing the SD card and boot it to emergency mode (some are already stuck on it so reading this post…: D) using the key combination stated above.
11. Connect to the PC and it should say, installing drivers’ blah… blah … your device is ready to use now.
12. Run the KDZ updater downloaded in step 7. Select 3GQCT in Type, DIAG in PhoneMode, and browse for ROM V10a in KDZ file and hit Launch Software update. Wait for somewhere around 5-10 minutes. It should say ===FINISHED=== in the log window of updater.
13. Handset will reboot, if not wait for another 5 minutes. Unplug from USB and try to switch it on.
Click to expand...
Click to collapse
My problem is that KDZ still doesn't find my phone after all these attempts - I uninstalled the device driver, then reinstalled it succesfully (B2CAppSetup.exe). I reboot, install msxml.msi, and start KDZ.
Next, I power my phone in Emergency phone, plug it, and it is detected for the first time by the computer. I do have LGE Android Platform Composite USB Device, listed in the Device Manager, as well as LGE Android Platform USB Modem.
Using KDZ, I select the "3GQCT" type, phone mode "DIAG", with the correct KDZ file I've downloaded earlier. Once I launch the software update, phone is not found.
I've tried several times, including desactivating the LG Modem from the Device Manager; unfortunately, when I disable it I need to reboot - I do reboot, but then the LGE Android Platform Composite USB Device is absent from the device manager, and isn't detected by Windows at all, until I fully reinstall the driver (...).
I really don't know what I'm doing wrong - note that I use a laptop with Windows 7 x64; I know laptops handle USB port in a different way than desktops.
Can you help please?
I must be SO close... =(
Thanks, I really appreciate it!

GameX2 said:
Hi,
May I ask for help here (instead of creating a new thread) ? I have the same problem: The device is booting loop at the LG screen. Bricked it when I wanted to save the ROM with ROM Manager.
I have no access to recovery mode, but Emergency mode does work (With and without battery).
I've followed multiple guides, including this one:
My problem is that KDZ still doesn't find my phone after all these attempts - I uninstalled the device driver, then reinstalled it succesfully (B2CAppSetup.exe). I reboot, install msxml.msi, and start KDZ.
Next, I power my phone in Emergency phone, plug it, and it is detected for the first time by the computer. I do have LGE Android Platform Composite USB Device, listed in the Device Manager, as well as LGE Android Platform USB Modem.
Using KDZ, I select the "3GQCT" type, phone mode "DIAG", with the correct KDZ file I've downloaded earlier. Once I launch the software update, phone is not found.
I've tried several times, including desactivating the LG Modem from the Device Manager; unfortunately, when I disable it I need to reboot - I do reboot, but then the LGE Android Platform Composite USB Device is absent from the device manager, and isn't detected by Windows at all, until I fully reinstall the driver (...).
I really don't know what I'm doing wrong - note that I use a laptop with Windows 7 x64; I know laptops handle USB port in a different way than desktops.
Can you help please?
I must be SO close... =(
Thanks, I really appreciate it!
Click to expand...
Click to collapse
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
It sounds to me like you are not entering Emergency Mode correctly. Yes, the LG USB Modem must be disabled. Power off the device. Press the "Back + Volume Up + Power" buttons together until the device boots to Emergency Mode. Now connect device to you PC/laptop. This can also be done with the battery removed and the device off. Same method except no power button involved. Press the "Volume Up + Back" buttons while attaching your device to your data cable, assuming it's already attached to your PC/laptop.
The attachment I've posted is a stripped down version of the KDZ Updater. All you need to supply is the correct KDZ file for your phone. This one does not require any of LG's other crap software either.
Download to your PC. Extract to a folder of your choosing. Read the ReadMe.txt carefully and follow it's directions to the letter. I just used this to revive two ( 2 ) bricked P506's.
If you can boot to fastboot mode, there is a tool in my signature, Android Flash Recovery, that is designed to flash a recovery to a device with fastboot. So you have two options to restore, revive your device.

shinobisoft said:
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
It sounds to me like you are not entering Emergency Mode correctly. Yes, the LG USB Modem must be disabled. Power off the device. Press the "Back + Volume Up + Power" buttons together until the device boots to Emergency Mode. Now connect device to you PC/laptop. This can also be done with the battery removed and the device off. Same method except no power button involved. Press the "Volume Up + Back" buttons while attaching your device to your data cable, assuming it's already attached to your PC/laptop.
The attachment I've posted is a stripped down version of the KDZ Updater. All you need to supply is the correct KDZ file for your phone. This one does not require any of LG's other crap software either.
Download to your PC. Extract to a folder of your choosing. Read the ReadMe.txt carefully and follow it's directions to the letter. I just used this to revive two ( 2 ) bricked P506's.
If you can boot to fastboot mode, there is a tool in my signature, Android Flash Recovery, that is designed to flash a recovery to a device with fastboot. So you have two options to restore, revive your device.
Click to expand...
Click to collapse
Hey, cheers !!
That was all I needed to do with this simple version, the update got applied properly, and I saw the FINISHED message.
My phone "rebooted". Well, what I see now if the Android logo with a big " ! ", which is normal according to what I've read.
I will do more ressearch to make sure what I do if correct now: is this safe to power off/reboot at this screen? I believe it's the last step.

GameX2 said:
Hey, cheers !!
That was all I needed to do with this simple version, the update got applied properly, and I saw the FINISHED message.
My phone "rebooted". Well, what I see now if the Android logo with a big " ! ", which is normal according to what I've read.
I will do more ressearch to make sure what I do if correct now: is this safe to power off/reboot at this screen? I believe it's the last step.
Click to expand...
Click to collapse
Yep. Sounds like you're good to go

shinobisoft said:
Yep. Sounds like you're good to go
Click to expand...
Click to collapse
Thanks
Holding the power button does not shut it down - pull the battery, right (It won't screw the thing right before the end ? XD ) ?
Look.. correct:
12 - Start the phone again. If you get stuck in a screen with an Android and an exclamation mark ("!") in a triangle, just unplug the USB cable and the battery. Plug the battery again and start the phone. It will take 2 to 5 minutes to reboot for the first time and the boot animation will be the stock LG (your carrier's stock animation is lost for good), but chances are your phone is intact, with all it's apps and configurations working the same as before the incident. When the boot finishes, turn off the phone again and put back the SD Card you took off on the first step.
Click to expand...
Click to collapse
I really don't want to mess anything at this point.

GameX2 said:
Thanks
Holding the power button does not shut it down - pull the battery, right (It won't screw the thing right before the end ? XD ) ?
Look.. correct:
I really don't want to mess anything at this point.
Click to expand...
Click to collapse
If KDZ Updater says it's done and your device has rebooted to recovery, then yes you can pull the battery to shut it down. You may still need to do the key presses for a factory reset, but the key combo has slipped my mind for the moment. Old age...

shinobisoft said:
If KDZ Updater says it's done and your device has rebooted to recovery, then yes you can pull the battery to shut it down. You may still need to do the key presses for a factory reset, but the key combo has slipped my mind for the moment. Old age...
Click to expand...
Click to collapse
Really nice, I have the Android logo !!
I will wait - people says it can take up to 5-15 minutes or even more - I won't shutdown on the logo.
Letting you know as soon as it's done.
***
After a while, the device booted, and I had a few messages saying it was restoring all the settings!
No data loss! Nothing (I had backed up my contacts and apps on my SD Card already - I was unsure if I would have loose my SMSs, I didn't) is lost !
Dude, seriously, thanks A BUNCH - this is ridiculous, I screwed the phone up at like 10PM yesterday, and did not went to sleep until 2AM because I couldn't fix the thing (I had access to FastBoot at first. I did a process to restore it from Fastboot, it should have worked properly, but then I only had access to the LG logo. Man, I thought I was toasted, and had to spend 50$ for a new phone, just because of a stupid mistake. Never would I thought that SAVING the ROM of my SD card would have screwed up the ROM!)...
I spent like 6 hours today trying to fix it, reinstalling the drivers over and over again... Installing a fresh new Windows XP on a machine, just so I could install everything on a new operating system to figure out the problem...
That was just plain crazy, seriously.
****BONUS****
The first thing I've noticed when I booted my phone was the BLACK notification bar
I really love black, and I once did ressearch a while ago to see if I could turn my white bar into black (I have Android 2.2.1), but no success.
I just realised I got it updated "accidentally" to Android 2.3, and so I was on Android 2.2. since 2011 (when I bought it) !
Well, nice addition, it is sexier with black
I belive it's because of the KDZ file I've used... I had a really hard time to find one, all the links were broken, from 2010, it's a old phone. I found the KDZ from Koodo, Canadian French, exactly my own.
Guess I "accidentally" upgraded to Android 2.3 then Nice addition !
I have no experience at all with fixing Android devices / ROM stuff - I'm used with Windows/Linux and others, but Android (although Android is a version of Linux) is another thing for me.
THANKS - seriously, I wouldn't have made it without your help.
YAY

GameX2 said:
Really nice, I have the Android logo !!
I will wait - people says it can take up to 5-15 minutes or even more - I won't shutdown on the logo.
Letting you know as soon as it's done.
***
After a while, the device booted, and I had a few messages saying it was restoring all the settings!
No data loss! Nothing (I had backed up my contacts and apps on my SD Card already - I was unsure if I would have loose my SMSs, I didn't) is lost !
Dude, seriously, thanks A BUNCH - this is ridiculous, I screwed the phone up at like 10PM yesterday, and did not went to sleep until 2AM because I couldn't fix the thing (I had access to FastBoot at first. I did a process to restore it from Fastboot, it should have worked properly, but then I only had access to the LG logo. Man, I thought I was toasted, and had to spend 50$ for a new phone, just because of a stupid mistake. Never would I thought that SAVING the ROM of my SD card would have screwed up the ROM!)...
I spent like 6 hours today trying to fix it, reinstalling the drivers over and over again... Installing a fresh new Windows XP on a machine, just so I could install everything on a new operating system to figure out the problem...
That was just plain crazy, seriously.
****BONUS****
The first thing I've noticed when I booted my phone was the BLACK notification bar
I really love black, and I once did ressearch a while ago to see if I could turn my white bar into black (I have Android 2.2.1), but no success.
I just realised I got it updated "accidentally" to Android 2.3, and so I was on Android 2.2. since 2011 (when I bought it) !
Well, nice addition, it is sexier with black
I belive it's because of the KDZ file I've used... I had a really hard time to find one, all the links were broken, from 2010, it's a old phone. I found the KDZ from Koodo, Canadian French, exactly my own.
Guess I "accidentally" upgraded to Android 2.3 then Nice addition !
I have no experience at all with fixing Android devices / ROM stuff - I'm used with Windows/Linux and others, but Android (although Android is a version of Linux) is another thing for me.
THANKS - seriously, I wouldn't have made it without your help.
YAY
Click to expand...
Click to collapse
Glad things worked out for ya And helping is what I'm here for

shinobisoft
shinobisoft said:
Yep. Sounds like you're good to go
Click to expand...
Click to collapse
Thanks for helping NOOBS, i appreciate that!

[Q] Ok so my device is not quite dead but close please help

Hi Everyone,
I've come on bended knee, and I have about 30 xda windows up where Ive tried to upgrade a perfectly working LG from android 2.2. But no matter what I try I cant get beyond the LG wink icon on the screen.
I have tried fastboot omao4boot 1.22 modified etc but I cant get past MLO (x-loader) I say YES to this but NO to 'fastboot devises' as per instructions (although why I say no to this, I dont know?) anyway it just says 'waiting for device' but nothing happens even if I take the battery out and disconnect from USB and reconnect, nothing ever happens?
So having redone the fastboot procedure, I managed to into boot mode - yellow round icon on screen and then tried to flash using LG flash tool 1.2 with LGP920 30A bin & fls files which it does and completes successfully, I have also used the LG recovery tool to flash recovery and firmware but all of the above wont let me boot the devise it just sits at the LG Icon.
Tried booting into recovery with 3d + vol + key but just ignores and goes to red LG Icon with the usual boot sound, I just cant get anything else to work! Is it down to the MLO loader issue. I dont know what else to do.
Please can anyone help me recover my phone I wanted to upgrade to JellycreamR5 cause its suppose to be a good rom but nothing now works :crying:
I know its not a busy forum now days and most have moved on, but please any assistance to get this beautiful phone going again would be brilliant.
Thanks for the time to read about this dilemma!
ATB

Ok, so if it boots to the LG logo with boot sound it is probably nothing wrong with bootloaders. It is either the system or just something incompatible on the data partition. Of you can make it too recovery try factory reset

Ok I think Ive fixed it!
Did lots of things to try to get to work, but heres roughly the guide.
Used 'rebooter' for Optimus 3d which saved the phone in the 1st instance, it was the only flasher that completed the flash... but remember 1st unplug the phone but micro usb in then remove the battery, then hold the + vol key and insert into the Win XP computer usb, I had already prepared and ran the rebooter.bat file which was waiting for omao device. Once detected keep hold the + key add battery when it says wait 5 secs, dont let the key go, say NO to flash boot but yes to the rest. It will say job done or words to that effect.
Turn on phone holding just the + key to get into download mode. Change the LGE CDMA USB SERIAL PORT to com41 in control panel device manager, refresh search for new hardware to check updated port.
Then use LG Flash to flash V3.0A which worked !
Disconnect the phone remove battery and reinsert, reboot devise, it will boot in TWRP which isnt great but good enough for flash, loaded a Rom onto the sd card and installed the software, after the usual clearing everything like Delvick/Settings etc.
Job done, rebooted and worked, still got TRWP on the boot loading would prefer Clockwork but never mind, had enough of fiddling and just enjoying having my device back
Havent tried a sim in it but might have to to the IMEI fix but hoping not.
Many thanks for your input, I know tech moves on, but there is a wealth on knowledge on these devices and it just seems to be lost in the ether.
Best wishes.

[Completed] brick problem, noob here, plz help

my problem is kind of abnormal. i couldnt find solution anywhere so i came here. my device was zenfone 5(t00f)/lollipop.
so i wanted to root my phone. i followed this guide >>
HTML:
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
the tool i used is called ZenfoneToolkit_20160719, downloaded from here
HTML:
https://drive.google.com/drive/folders/0B0AFmAAcGS5xbWpTQzBQVTN3b1k
. its a bundle of .exe, .dll, .img, .bin files. but no need to work on them seperately, there is a simple cli tool from which you can choose what you want to do and it executes that file for you. below is the list what you can do.
1. Wipe Cache
2. Factory Reset
3. Flash Boot
4. Flash Recovery
5. Flash Fastboot
6. Flash Stock ROM
7. Root
8. Unroot
9. Unlock Bootloader
10. Relock Bootloader
11. Zenfone Rescue aka Debrick
12. Fixing Generic IMEI 004999010640000
13. Backup MicroSD
14. Flash Boretz Kernel Lollipop
so wiped cache[1] first then i tried to root[7]. sadly it didnt work, when i turned the phone on it took me to fastboot screen, there i had only a few options like, normal boot(doesnt happen), recovery mode, restart. when i turned it off and pressed power and volume up together it would go to recovery where none of the options works. i though that was what called brick, so followed this guide to make my life better
HTML:
http://zenfone-blog.blogspot.com/2015/06/guide-how-to-unbrick-asus-zenfone-4-5-6.html
.
my phone by default came with kitkat. so when i downloaded the firmware i wanted to get a kitkat. but i couldnt find a matching recovery img and firmware for kitkat on asus official page. so i downloaded jellybean. ASUS ZenFone 5(T00F/T00J) software Image: V1.18.40.9 ww for firmware from here
HTML:
https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
. and recovery img is 1.18.40.9_ww_recovery.img from here
HTML:
https://www.asuswebstorage.com/navigate/s/644D9E0A19714899974C75FC4B6C87EDY
. i dont know what "ww" means in those name but i saw it in my software version before so i went with it.
All the steps went smoothly, by the end of it i guessed my phone charge would be low so i put it in charge and turned it on. first time it turn on without a problem. i checked out a few things and leave it for charge. after a while i came back and battery was 0%. i thought i would be wise to plug out and in charging port again. as soon as i pull out the pin, screen instantly turned black and the phone went dead after a looooong ass vibration.
now when i try to charge the orenge light at top lights up but the animation that shows battery always show its empty. if i try to turn it on while plugged, it shows asus logo/intel logo and goes dead again. if i try to turn it on without being plugged, it shows a battery logo with a question mark, which i think means the phone cannot find battery.
i am stuck here.... plz someone be my savior.

http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
solved here

nooblett said:
http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
solved here
Click to expand...
Click to collapse
Great that the problem was solved
Thread closed

Database Info

welcome