Related
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
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
try deleting batterystats.bin then rebooting.
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..
I decided to try to update to GB because my G2X rebooted while on the charger, clock night mode turns off and the screen locks, and wifi is ok but resets sometimes. My phone is stock 2.2 with stock recovery but rooted.
I turned off all programs on my Windows 7 32 bit laptop, turned off anti virus and turned off Windows firewall. The updater ran ok, checked the phone environment and downloaded the update. Then at 4% when the phone is supposed to download into software update mode, it just sat there staying in Android. After the update failed and it told me to remove the cable and remove battery, etc., I just shutdown the phone, did a battery pull and turned the phone back on. I then canceled the update.
My phone booted back into Android no problem. I tried to boot into recovery using Quickboot but that just rebooted the phone back into Android. My questions are as follows:
1. Did the update change anything on the phone or did it fail before attempting to change anything?
2. Why did it fail to boot into software update mode? Do I need to try another USB port or another computer?
3. Should I use the alternate method on a Windows XP machine that people use when their phone is soft bricked?
4. Should I just install CWM recovery and use the pre-rooted zip of GB with the old baseband?
5. Or should I just forego the update for now and see if another update is released?
Try reinstalling everything, and restarting your computer. It worked just fine on Windows 7 Ultimate x86, and x64.
My update went the same way but everytime I retried it got a little further so I just retried it over and over till I hit 100 percent
Sent from my LG-P999 using XDA App
I just tried to run the LG update program on my XP machine but I got a runtime error (see attached). Anybody know what this means and how to fix it?
Does anyone know why it just sits there on 4% and never boots into the software update mode? Can I just run it and then when it fails manually boot into software update mode? Or is that risking a brick?
jboxer said:
I decided to try to update to GB because my G2X rebooted while on the charger, clock night mode turns off and the screen locks, and wifi is ok but resets sometimes. My phone is stock 2.2 with stock recovery but rooted.
I turned off all programs on my Windows 7 32 bit laptop, turned off anti virus and turned off Windows firewall. The updater ran ok, checked the phone environment and downloaded the update. Then at 4% when the phone is supposed to download into software update mode, it just sat there staying in Android. After the update failed and it told me to remove the cable and remove battery, etc., I just shutdown the phone, did a battery pull and turned the phone back on. I then canceled the update.
My phone booted back into Android no problem. I tried to boot into recovery using Quickboot but that just rebooted the phone back into Android. My questions are as follows:
1. Did the update change anything on the phone or did it fail before attempting to change anything?
2. Why did it fail to boot into software update mode? Do I need to try another USB port or another computer?
3. Should I use the alternate method on a Windows XP machine that people use when their phone is soft bricked?
4. Should I just install CWM recovery and use the pre-rooted zip of GB with the old baseband?
5. Or should I just forego the update for now and see if another update is released?
Click to expand...
Click to collapse
Follow your Item 4
Finally got it updated
Used Windows 7 32bit.
The update progressed very scarily.
I downloaded the drivers and reinstalled them directly from the update program. I then used a different USB port then my previous attempt, unplugged all other USB devices, and shutdown everything running on the computer I could including Avast andti-virus and the Windows Firewall. This time when I plugged the G2X into my computer a lot more devices installed than last time (first time only 2 devices were installed, this time about 8 to 10).
During the first download of the firmware I canceled it because I realized I left the micro sd card in the phone and the instructions on the website say to remove the card. Then I also decided to unroot the phone and remove all programs that require root access. Since the phone would be unrooted after an update I decided I didn't want superuser in the system if I couldn't use it, and after the update I would be unable to remove it since the phone would not be rooted.
Then I ran the program again and this time the phone booted into software update mode. It started pushing the update to the phone and at 5% the phone disconnects from the computer and reconnects (does this three times during the update) but the software doesn't see the phone and tells me to unplug the USB cable, remove the battery, reinsert the battery and turn the phone back on. But I heard the computer reconnect to the phone so I decided I would just remove the cable and reinsert it. This worked and the update started over again. This time it went past 5% and then reset the phone connection again at 46%. It then slowly completed the update resetting one more time at 76% and when it reconnected it went back to 75% but then progressed to 100% and rebooted the phone.
It now has an updated baseband and Gingerbread 2.3.3. I am leaving it unrooted for now and just use it stock.
jboxer said:
Does anyone know why it just sits there on 4% and never boots into the software update mode? Can I just run it and then when it fails manually boot into software update mode? Or is that risking a brick?
Click to expand...
Click to collapse
I do! It's installing one of the THREE usb drivers that it installs over the course of the upgrade. Mine got stuck at 4% for just a second (at which point I about **** my pants), but then I saw a Win7 notification pop up that it had just installed a USB driver, and then it proceeded to do the update.
So maybe the failure mode is the LG updater not being able to install a USB driver?
Maris_ said:
Follow your Item 4
Click to expand...
Click to collapse
Is there any significant reason to update to get the newest baseband and then flash CM7? Or is there no benefit from the new baseband?
brdma said:
Is there any significant reason to update to get the newest baseband and then flash CM7? Or is there no benefit from the new baseband?
Click to expand...
Click to collapse
July 15, 2011 baseband has more reliable wifi and much better GPS lock. After the scares of getting mine updated finally, my G2X has had no issues in the 30+ hours since the update. No reboots on charger, no sleep of death and everything is working as it should.
Hey guys,
I've got a Galaxy S 4G currently running the CM 9 build Release 8 (from August) and here are the problems I'm experiencing:
- random failure to reconnect to the phone network after I've been in the subway (have to reboot)
- just plain random reboots, though they're rare
The lack of reconnectivity is driving me up the wall. How likely is it that this problem is just with the OS? I don't want to have to get a new phone but maybe I've dropped this one too may times. :silly:
You might try a different modem to see if reconnecting works better or put airplane mode in you status bar toggles and toggle it off/on when you get off the subway for a fresh connection.
Thank you, lumin!
edited: I'll direct other questions to the CM9 thread.
Sorry guys, returning to this thread rather than clogging up the Heimdall thread or the CM9 thread.
I'm having a very basic problem and am feeling very stupid and very frustrated. I can't get Heimdall to recognize my phone.
Last attempt steps I took:
- Installed Win64 Samsung drivers
- Rebooted PC
- Connected phone to computer when in each of regular, recovery, and download mode.
- Ran Zadig as administrator and selected List All Devices
- Phone does not show up as Samsung anything, just as Gadget Serial
- Hit Install Driver (Note: this has never changed to "Reinstall Driver" or anything
- Ran Heimdall as admin
- Doing a test for compatible devices turns up nothing.
Use the Odin one click here http://forum.xda-developers.com/showthread.php?t=1500427
Use a different USB port and you should be fine
Sent from my SGH-T959V using xda app-developers app
Additionally, installing the official drivers will make the phone not connect if you're using one of the MTD (ICS/JB/newer-CM7) roms. Since they use the generic Google Android driver rather than the Samsung one.
Another thing is, zadig includes (for me) 3 or 4 different driver options, and only one of them actually works. For me, that's WinUSB. For you, might be something else. But try installing one, rebooting the computer, restarting the phone, and seeing if it works. Then move on to the next one. Once you figure out what works for you, write it down somewhere and use it for the future.
Thanks, I'll give that a shot.
Theraze said:
Additionally, installing the official drivers will make the phone not connect if you're using one of the MTD (ICS/JB/newer-CM7) roms. Since they use the generic Google Android driver rather than the Samsung one.
Click to expand...
Click to collapse
Can you elaborate on that for me? By connect, what do you mean? Connect to the computer?
P.S. is this the driver you're referring to? So I should be using this and not the Samsung one?
http://developer.android.com/sdk/win-usb.html
I meant that uninstalling the Kies/official drivers, rebooting, and only using the zadig drivers is likely to give you better results if you're using newer roms. Since the Kies drivers are only helpful if you're on GB and can only cause you problems otherwise.
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works. If not, run zadig, list all devices, select the phone, install libusbK driver, reboot, unplug, reboot phone into download, plug back in, check if flashing works. Repeat with libusb0 if needed.
Theraze said:
I meant that uninstalling the Kies/official drivers, rebooting, and only using the zadig drivers is likely to give you better results if you're using newer roms. Since the Kies drivers are only helpful if you're on GB and can only cause you problems otherwise.
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works. If not, run zadig, list all devices, select the phone, install libusbK driver, reboot, unplug, reboot phone into download, plug back in, check if flashing works. Repeat with libusb0 if needed.
Click to expand...
Click to collapse
Aaaaahhh. Ok, I'll try that.
Oh, and when having zadig/driver issues... always try to flash twice. And when it gives you an error, after the second failed flash, reboot the phone and flash again. Then move on to the next driver/attempt.
When this phone gets finicky, you need to get the yellow-caution flash screen to bypass its paranoia about your flashing.
Theraze said:
But uninstall Kies driver, reboot, plug in the phone while it's in download mode if it isn't currently, run zadig, list all devices, select the phone with whatever name it currently has, install WinUSB driver. Reboot computer, unplug phone, reboot phone back into download mode, plug back into computer, check if your flashing works
Click to expand...
Click to collapse
Ok, one question about this:
- you've plugged the phone in while it's in download mode
- then in the second sentence you wrote "REBOOT phone into download mode" but the phone was in download mode before, so was a reboot actually necessary?
edit: And, I haven't actually tried flashing at all in Heimdall, I've just been checking to see if it sees a compatible device. Would you suggest I just try to go ahead with the flash, with each driver? (I'm not sure if I've seen the option to select anything more than Windows USB, but at least with that?)
Specially, shut down the phone and boot into download mode again. Easiest way to do it is probably to unplug USB, pull the battery, plug in USB, put the battery back in, etc... Guarantees that you've got your full phone-reboot cycle.
And regarding alternate drivers, there's a little up-down arrow next to the driver name. Click that to override the current best-driver-guess and manually pick your choice.
Damn, there's a bunch of reboots I was missing... I really hope I haven't screwed anything up permanently.
Theraze said:
And regarding alternate drivers, there's a little up-down arrow next to the driver name. Click that to override the current best-driver-guess and manually pick your choice.
Click to expand...
Click to collapse
Yeah.......... I don't have that. I looked again, it's not there.
edit: it would appear that Heimdall 1.3.1 came with Zadig 1.0 only... I just grabbed 2.0 from github.
Personally, I'm using Heimdall 1.3.2 and that's been working fine for me. But some people have issues with that one, so... no comments/complaints about Heimdall 2.0 RC1 yet on his site.
Theraze, if you could speak more specifically about one point here: all I have been doing is changing drivers (I've just tried all three) and then I've used Heimdall's Detect Device utility to try to detect the phone. Which has failed.
You have repeatedly said "try flashing". Do you think that can work even if Detect Device isn't working? I got the impression that was dangerous.
edit: well that's obviously what you're suggesting, but - how safe is this? Perfectly? Mostly?
If it doesn't see your phone, it won't flash. If it does, it should work or at least do... something. At which point, it probably hit the half-flash yellow screen I get every time I use Heimdall to flash a new kernel.
That's basically how complicated as I see this... Regardless of how well the detection tool is working, if it actually succeeds...
The 959V is nifty in that it's ALMOST impossible to hard-brick. If you're flashing bootloaders and pull the cord there, maybe... but if you screw up the kernel or one of the other things that make normal phones into depressing paperweight reminders, it just means reboot and flash again.
Thanks, man. Going to try flashing now.
Zilch. Can't see the phone with any of the three drivers.
Starting to give up hope of fixing this, honestly.
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!
Disclamer: Okay. This is my first XDA post so, it might be a bit shabby.
I am writing this post because it caused me a day of my life in reviving my dead Lenovo A369i. I broke my galaxy S5 so had to use this old buddy. Well, it got jacked while flashing it through the SF Tool as it accidentally (or as my hand was paining and i shook the USB cable to place in on the table - accidentally though) disconnected the phone while it was in the middle of an ongoing flash.
So, there it went, whole day of blood boil and headache.
Anyway, cutting to the point, if you have the following issues:
Bricked your phone while flashing via the SF Tool or bricked it doing something else.
Lost your IMEI [INVALID IMEI] after flashing or lost it anyway.
Your phone is showing no signs of life, even when connecting to the charger.
SF Tool gives Error 4032. Failed to read DRAM.
[/LIST
...then this is the solution you can try. At least one solution, the one that worked with me.
THIS SECTION IS FOR UNBRICK-ING YOUR PHONE IN CASE ITS DEAD. TO SOLVE IMEI, SCROLL BELOW
Things you should have before proceeding:
A Lenovo a369i phone (or any MTK devices that has the described issue).
Compatible MTK drivers.
Charged phone. Charge it for at least an hour. Your don't want to mess this up. I kinda did. It isn't mandatory but why the extra risk?
The stock ROM. Now, this is the most crucial requirement. With me, i had to download a bunch of ROMs before i got the one that matched my phone. There are two variants of A369i: The 'lite' and the non-lite (i don't know how else to put it). I had the lite variant and i didn't knew that. It took me 6 hours to understand the difference. Anyway, you should check yours and proceed. This is the lite 4.2.2 stock ROM.
Once you have all the things ready, follow ahead:
Extract the ROM somewhere. Navigate to the 'flash_tool.exe'. Run it.
Select the 'Scatter-loading' option, go to target_bin folder or wherever you have extracted the firmware and select the 'MTXXXX_Android_scatter.txt'. This will load all the files for flashing.
Now, here is where it gets a li'l tricky. I prefer to format clean the phone before flashing the rom. This helps avoid any interruptions. But it also wipes the user data. This is not mandatory but you should do it in this way.
Click the 'Format' button. Turn your phone off if it isn't. Squeeze the volume UP and Volume Down keys together and connect the USB to your computer. Your phone will get detected and your will see the bar at the bottom of the flash tool turning red and then green notifying that the format is complete. If you have any issue like the phone isn't detected, then you need to reinstall the drivers. This step is mandatory. If your drivers aren't installing properly, turn off the DIGITAL SIGNATURE ENFORCEMENT (you can search google how to) and install the drivers.
Once the format is done, remove the battery. Wait for a few sec. Fidget with the power button if you like, because i do. Then put the battery right back in and repeat the same steps as before but click the 'Download' button instead.
Then squeeze volume up and down >> Connect the USB to the phone. And wait till the tool completes flashing. And do take care you don't disconnect it. If you do, you might have to come back here again. LOL
Once its complete, you will be notified by a green notification. You can go ahead, disconnect your phone, remove the battery, fidget again, put it back up and boot your phone. Luckily, it might start.
IMEI INVALID SOLUTION
If you are as lucky as me, you might get this issue. Well, do not worry. You are not alone. And this might be just the solution for you.
You need to download a bunch of files and do a few steps. Here's what you need:
You need to root your phone. Framaroot worked for me.
If this doesn't work, you can try KingRoot app for rooting.
MTK DROID Tools for replacing your IMEI back to what is was. androidmtk.com/download-mtk-droid-tool"
The steps:
BEFORE YOU START, REMOVE YOUR BATTERY AND COPY BOTH YOUR IMEI SOMEWHERE. YOU WILL NEED THEM.
Root your phone. Open Framaroot and select any from the two options. You should get a success message if rooted. If not, install KingRoot application. You will need internet connection to root with KingRoot.
Once rooted, you need to open the MTK DROID Tool. Before connecting your phone to your computer, you need to enable 'USB Debugging' from the developers option. To do that go to Settings>>About>>Status>>Click Build Number for a few time>>go back>>Developers Option>>Enable it>>USB Debugging. Now connect your phone.
At the bottom right corner, you will find a ROOT option. Click it. It allows the tool to gain root access to your phone. It will pop up to install some app like supersu, mobileuncle tools and root explorer. You should install them. Also, you can backup your phone (This is optional).
Now click the IMEI/NVRAM type both your IMEI and click 'Replace IMEI.' Restart your phone. And that's it.
You have successfully revived your dead phone/Replaced your original IMEIs/Conquered the WORLD (well, for the moment ).
Cheers. :good:
done.