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..
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 big bro tried to root Galaxy SL i9003, i don't know which rooting application/software he has used, but when handset restarted after rooting completion it's stuck at screen showing "SAMSUNG Galaxy SL i9003" boot screen...
Now what i do, some of my friend told me that I have to flash mobile with its original ROM with proper version..
Where should i get original ROM of my mobile and how can i know firmware version because i am not able to boot my handset to *#1234#...
PLz HELP!!!!!
amoghs said:
My big bro tried to root Galaxy SL i9003, i don't know which rooting application/software he has used, but when handset restarted after rooting completion it's stuck at screen showing "SAMSUNG Galaxy SL i9003" boot screen...
Now what i do, some of my friend told me that I have to flash mobile with its original ROM with proper version..
Where should i get original ROM of my mobile and how can i know firmware version because i am not able to boot my handset to *#1234#...
PLz HELP!!!!!
Click to expand...
Click to collapse
just do a clean flash of gingerbread DDLF2 2.3.6 using ODIN. your problem will get solved. and always read a plenty of articles before doing such tasks..
File Selection in Odin
maxs8007 said:
just do a clean flash of gingerbread DDLF2 2.3.6 using ODIN. your problem will get solved. and always read a plenty of articles before doing such tasks..
Click to expand...
Click to collapse
Hey maxs, Thank you For your reply...as you said i have downloaded File I9003DDLF2_I9003ODDLF2_INU.zip from http://forum.xda-developers.com/showthread.php?t=1004647 and extracted to some location on machine but this zip contains only two files first one is I9003DDLF2_I9003ODDLF2_I9003DDLE1_HOME.tar.md5 and another on is SS_DL.dll.
I m using Odin v3.07 in that where i supposed to select "I9003DDLF2_I9003ODDLF2_I9003DDLE1_HOME.tar.md5" this file at bootloader/PDA/Phone/CSC..
It will be very helpful if give steps of flashing.
Still Phone is stucked at Boot Screen
amoghs said:
I m using Odin v3.07 in that where i supposed to select "I9003DDLF2_I9003ODDLF2_I9003DDLE1_HOME.tar.md5" this file at bootloader/PDA/Phone/CSC..
Click to expand...
Click to collapse
I selected "I9003DDLF2_I9003ODDLF2_I9003DDLE1_HOME.tar.md5" file in PDA and only Auto Reboot and F.Reset Time is checked and started downloading all goes OK and Pass is showed.
But Still mobile is stucked in boot screen Plz HELP!!!
Greetings;
Have you solved your problem?
If not, tell me what Android version are you running on your device?
i.e: Gingerbread; Ice Cream Sandwich; Jelly Bean or KitKat.
Assuming you are running stock firmware i believe that either your brother flashed a wrong CF-Root for your device or used an application that could not root your device properly.
Either ways don't worry since your device can enter both Download and Recovery modes, it means that you can debug it.
[Rooting]
The best way to root this device is by flashing CF-Root file.
By flashing this file (CF-Root) you will be installing:
- ClockWork Mod Recovery
- Script that will root (automatically) your device.
- ext4 application. (do some research to know what ext4 is and how it os often used)
Small note: Since you will be rooted you will be able to overclock or underclock your device as well increase your device performance and battery duration.
Just PM me or do some research if you need some info regarding these configuration and settings.
[Fixing your issue]
Download Universal CF-Root here:
http://forum.xda-developers.com/showthread.php?t=1351056
Read the instructions before proceeding.
Now boot your device under Download Mode.
To do so:
Unplug USB Cable, Power Off your device and press the following key combination:
Vol.Down + Menu/Home Button + Power Button.
Release when the device enters download mode.
Now open Odin.
Under [PDA] load the CF Root File you've downloaded.
(Do NOT change any options inside odin if you dont know what they are for. Or you may get your device useless).
Put down your device so movement is done into the USB Cable (just to prevent bad flashing when you have low quality USB Cable).
Press Start and let the operation to complete.
Odin will display a message saying: "Pass" highlighted with Green.
Check if your device restarts (it may not restart yet)
If your device boots properly backup your data and follow the next step. If it doesnt boot properly follow to the next step.
Voot your device into recovery mode.
To do so: Power off your device and make sure it is not charging or connected to USB cable.
Then press and hold the following key combination:
Vol. Up + Menu/Home Button + Power Button.
Release after the Boot Logo is shown and you will enter recovery mode.
Now you will perform a Factory Reset.
Inside CWM select by the following order:
- Wipe Dalvik Cache
- Clean Cache
- Factory Reset
Note that Dalvik Cache is not shown at the main menu.
I dont remember the location exactly but if im not mistaken you can find it under "Advanced".
After you perform these 3 options the device shall reboot properly.
(it may take a little bit longer this time. Just be patient).
Since i dont know what was done to your device, there is still a chance that your device wont boot.
Either ways please let me / us (at XDA) know if it worked for you.
It is important (at least for me as a quality standard) that you are able to repair your device.
Best Regards
Please press thank button if this helped you. Since this will keep me motivated to continue helping.
Sent from my GT-I9003 using XDA Free mobile app
Any further help
rgxHost said:
Greetings;
Have you solved your problem?
If not, tell me what Android version are you running on your device?
i.e: Gingerbread; Ice Cream Sandwich; Jelly Bean or KitKat.
Assuming you are running stock firmware i believe that either your brother flashed a wrong CF-Root for your device or used an application that could not root your device properly.
Either ways don't worry since your device can enter both Download and Recovery modes, it means that you can debug it.
[Rooting]
The best way to root this device is by flashing CF-Root file.
By flashing this file (CF-Root) you will be installing:
- ClockWork Mod Recovery
- Script that will root (automatically) your device.
- ext4 application. (do some research to know what ext4 is and how it os often used)
Small note: Since you will be rooted you will be able to overclock or underclock your device as well increase your device performance and battery duration.
Just PM me or do some research if you need some info regarding these configuration and settings.
[Fixing your issue]
Download Universal CF-Root here:
http://forum.xda-developers.com/showthread.php?t=1351056
Read the instructions before proceeding.
Now boot your device under Download Mode.
To do so:
Unplug USB Cable, Power Off your device and press the following key combination:
Vol.Down + Menu/Home Button + Power Button.
Release when the device enters download mode.
Now open Odin.
Under [PDA] load the CF Root File you've downloaded.
(Do NOT change any options inside odin if you dont know what they are for. Or you may get your device useless).
Put down your device so movement is done into the USB Cable (just to prevent bad flashing when you have low quality USB Cable).
Press Start and let the operation to complete.
Odin will display a message saying: "Pass" highlighted with Green.
Check if your device restarts (it may not restart yet)
If your device boots properly backup your data and follow the next step. If it doesnt boot properly follow to the next step.
Voot your device into recovery mode.
To do so: Power off your device and make sure it is not charging or connected to USB cable.
Then press and hold the following key combination:
Vol. Up + Menu/Home Button + Power Button.
Release after the Boot Logo is shown and you will enter recovery mode.
Now you will perform a Factory Reset.
Inside CWM select by the following order:
- Wipe Dalvik Cache
- Clean Cache
- Factory Reset
Note that Dalvik Cache is not shown at the main menu.
I dont remember the location exactly but if im not mistaken you can find it under "Advanced".
After you perform these 3 options the device shall reboot properly.
(it may take a little bit longer this time. Just be patient).
Since i dont know what was done to your device, there is still a chance that your device wont boot.
Either ways please let me / us (at XDA) know if it worked for you.
It is important (at least for me as a quality standard) that you are able to repair your device.
Best Regards
Please press thank button if this helped you. Since this will keep me motivated to continue helping.
Sent from my GT-I9003 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your reply. Frankly speaking I don't remember which Android version I was using may be Gingerbread (Is this important)
I downloaded "bagaria-09.GT-I9003_PDA.tar" from the link given by you and following procedure that you have mentioned. After odin says "Pass" I switched off my mobile and started in Recover mode it took around 15-20 mins to show recovery option. after this performed
- Wipe Dalvik Cache
- Clean Cache
- Factory Reset
and then Reboot. As you said phone is stucked on boot image for more than 15 mins then an loop on "SAMSUNG" logo after more 15 mins phone is showing "kernel panic upload mode"
Can you help me further?
amoghs said:
Thanks for your reply. Frankly speaking I don't remember which Android version I was using may be Gingerbread (Is this important)
I downloaded "bagaria-09.GT-I9003_PDA.tar" from the link given by you and following procedure that you have mentioned. After odin says "Pass" I switched off my mobile and started in Recover mode it took around 15-20 mins to show recovery option. after this performed
- Wipe Dalvik Cache
- Clean Cache
- Factory Reset
and then Reboot. As you said phone is stucked on boot image for more than 15 mins then an loop on "SAMSUNG" logo after more 15 mins phone is showing "kernel panic upload mode"
Can you help me further?
Click to expand...
Click to collapse
Hello amoghs;
Again sorry for answering after so long; I'm not so often at XDA Lately.
Yes.
1st: Try Remove the Battery, then Put it Back and Try Again.
If this doens't Work:
1) Turn your Device Off and Press:
Vol. UP + Home Button + Power (To Enter CWM / Your Recovery Mode)
2) Select: "Factory Reset"
Let me know how it worked for you.
Note:
- After Flashing a ROM it is Normal that your Device Takes a little Longer to Boot on the "1st" time.
- Phone Stuck on Boot Logo and Looping: Boot Issues (Either Requires to Remove and Place Back the Battery; or Re-Flash the ROM or Stock Rom in a Difficult Stage).
Notes:
- After a Flash Perform a Factory Reset (To Clean Up Old Stuff).
- If you Experience: "Kernel Panic":
a) Remove Battery and Place it Back - (Works on Most Cases)
b) Flash your ROM again and DO NOT Instal Custom Kernel (May be Wrong Kernel or Bad/Incompatible Kernel Programming)
c) Phone Restarts by Himself: Reflash ROM, Try MinFreeManager or Similar APK (Application). Try "Optimal" Settings. (I dont recall the Presets names - But you can Safely test them - Even if device gets stuck. You can always revert to previous state).
d) Any Hard-to-Solve Issues: Just do a "Clean Flash" of STOCK Gingerbread (Check Sammobile Website - Invalid Download Links Just send email to Support Requesting the File)
or Flash "DDLF2 2.3.6 (Also Gingerbread). But always try Stock 1st to remove most issues, and only then Flash your Desired ROM.
Also if you haven't fixed the Boot Issue already: Do note that you can recover your device Boot.
NOT Dead Yet!
Please do let me know if you solved your Boot problem.
Best Regards;
Richard
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Gombyz said:
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Click to expand...
Click to collapse
As u mentioned, I think that your phone has gone to a Soft Brick. I don't know much about the Korean build, so Google it to solve the Soft Brick. Try flashing the stock rom via odin but I don't recommend it since it may cause your phone to be hard bricked if not done properly.
So go to the service centre, you'll get more help there
Sushant Rohan said:
As u mentioned, I think that your phone has gone to a Hard Brick. I don't know much about the Korean build, so Google it to solve the Hard Brick. But it is very hard to solve
Click to expand...
Click to collapse
I thank you sir for responding to this. From what you have said, I think the best decision is to take it to Samsung service center. (For I have tried to google it but I couldn't get a solution). I would also like to know if it is repairable, and about the cost, is it worth repairing or should I think of buying a new phone?
I am stranded.
Gombyz said:
Please guys, my galaxy S2 SHW-M20K (Korean) is in trouble.
I bought it from a 2nd hand shop , and it was runing Android 4.1.2 Jelly Bean (rooted stock rom). I had no problem with it till today when I tried to install "CWM Recovery", After searching the web i found a post with two files that supposedly could do the task. These files are:
1. CWM_KT_M250K.tar
2. Tegrak-Kernel-Build-39-for-SHW-M250K-UE18.tar
Using Odin, I triedd the first file but it couldn't work, and the phone could not boot so i downloaded the "rooted factory firmware" and flashed the phone. Everything was ok. Later I tried the second file. Again the phone could not boot and stuck at the logo with a yellow triangle. After waiting for about 5 minutes I tried to shut it down by pressing the power button it did'nt respond. (Now this is a point that I regret), I removed the battery as a way of forcing to turn it off.
Now my phone cannot boot. It doesn't respond to power button, neither does it allow me to enter recovery mode nor download mode. But When i connect to the charger or pc, it start charging and keeps cutting off the charging frequently. But it only allows me to enter download mode when connected to pc. When I tried to flash the "rooted factory firmware", again, the flashing goes smoothly but when the phone starts rebooting it fails as if there is a power cut. Is my battery damaged? Can someone give me a guide on how to fix it?
I need your help gus, I am not an expert in the rootings and roms,
Pardon My English. It's a foreign language to me.
Click to expand...
Click to collapse
Download stock firmware (like xxxx.tar.md5 full Odin package) of ur device ,enter into Download mode of ur device & flash stock firmware with Odin.
Try this...
Hello guys.
My tab (GT-P3100) have been facing some problems lately.
Before this, my tab cannot be started up for some times although it is fully charged.
Last week, I managed to boot it up and then formatted the tab via "restore factory setting" while the tab is on.
Then, I intended to load custom rom into the tab. However all pc, usb, driver, and kies version cannot help me as the tab won't be recognized. It either not showing up entirely or it simply show an error.
Then, I figured that I must format the phone via recovery mode to get the usb working again.
Now is where this problem happened. While formatting, the system message is only stuck at "formatting cache".
It then took a long time until it turned off on its own. This is when the phone cannot be started.
Initially, I can still boot it up until the "samsung galaxy" screen or in download mode. This need to be done by charging it just for a short minute until the battery charging icon shows up. If the battery icon doesn't show up, the phone cannot be started by any means. Then, the boot screen cease to show up but the download mode can still be accessed. Now, the download mode cannot be accessed as well. Lastly, the batter icon won't even show up.
So this lead to my question, what is wrong with my tab. Is is because of corrupted OS, recovery mode. Or perharps faulty battery. Can it be solved by jtag?
kukuru said:
Hello guys.
My tab (GT-P3100) have been facing some problems lately.
Before this, my tab cannot be started up for some times although it is fully charged.
Last week, I managed to boot it up and then formatted the tab via "restore factory setting" while the tab is on.
Then, I intended to load custom rom into the tab. However all pc, usb, driver, and kies version cannot help me as the tab won't be recognized. It either not showing up entirely or it simply show an error.
Then, I figured that I must format the phone via recovery mode to get the usb working again.
Now is where this problem happened. While formatting, the system message is only stuck at "formatting cache".
It then took a long time until it turned off on its own. This is when the phone cannot be started.
Initially, I can still boot it up until the "samsung galaxy" screen or in download mode. This need to be done by charging it just for a short minute until the battery charging icon shows up. If the battery icon doesn't show up, the phone cannot be started by any means. Then, the boot screen cease to show up but the download mode can still be accessed. Now, the download mode cannot be accessed as well. Lastly, the batter icon won't even show up.
So this lead to my question, what is wrong with my tab. Is is because of corrupted OS, recovery mode. Or perharps faulty battery. Can it be solved by jtag?
Click to expand...
Click to collapse
So you aren't able to install any custom recovery neither being able to get your tab detected so I think you should try heidmall
Sent from my GT-P3100 using Tapatalk
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
kukuru said:
Hello guys.
My tab (GT-P3100) have been facing some problems lately.
Before this, my tab cannot be started up for some times although it is fully charged.
Last week, I managed to boot it up and then formatted the tab via "restore factory setting" while the tab is on.
Then, I intended to load custom rom into the tab. However all pc, usb, driver, and kies version cannot help me as the tab won't be recognized. It either not showing up entirely or it simply show an error.
Then, I figured that I must format the phone via recovery mode to get the usb working again.
Now is where this problem happened. While formatting, the system message is only stuck at "formatting cache".
It then took a long time until it turned off on its own. This is when the phone cannot be started.
Initially, I can still boot it up until the "samsung galaxy" screen or in download mode. This need to be done by charging it just for a short minute until the battery charging icon shows up. If the battery icon doesn't show up, the phone cannot be started by any means. Then, the boot screen cease to show up but the download mode can still be accessed. Now, the download mode cannot be accessed as well. Lastly, the batter icon won't even show up.
So this lead to my question, what is wrong with my tab. Is is because of corrupted OS, recovery mode. Or perharps faulty battery. Can it be solved by jtag?
Click to expand...
Click to collapse
Have you tried restoring to stock rom or installing cwm?
Sent from my GT-P3100 using Tapatalk
shsagnik said:
So you aren't able to install any custom recovery neither being able to get your tab detected so I think you should try heidmall
Sent from my GT-P3100 using Tapatalk
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
Have you tried restoring to stock rom or installing cwm?
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Hello
I have downloaded the heimdall zip. However, the zadig.exe cannot find any samsung devices. I have followed the instruction where I have to uninstall kies and other usb drivers. but still no luck.
My ROM is still stock rom. And I can't install cwm because my tab can never be discovered..
kukuru said:
Hello
I have downloaded the heimdall zip. However, the zadig.exe cannot find any samsung devices. I have followed the instruction where I have to uninstall kies and other usb drivers. but still no luck.
My ROM is still stock rom. And I can't install cwm because my tab can never be discovered..
Click to expand...
Click to collapse
Try sideloading Samsung USB drivers using uh what's it's called uh yeah go to my computer, right click, mange, device manager, connect your device and see if it appears and try side loading drivers, just Google it on how to do it and tell me if it works
Sent from my GT-P3100 using Tapatalk
shsagnik said:
Try sideloading Samsung USB drivers using uh what's it's called uh yeah go to my computer, right click, mange, device manager, connect your device and see if it appears and try side loading drivers, just Google it on how to do it and tell me if it works
Sent from my GT-P3100 using Tapatalk
Click to expand...
Click to collapse
Tried and failed. Thanks for your suggestion though. I'm gonna try third usb cord after this. Will report later.
it is time for taking it to the service centre
kukuru said:
Hello guys.
My tab (GT-P3100) have been facing some problems lately.
Before this, my tab cannot be started up for some times although it is fully charged.
Last week, I managed to boot it up and then formatted the tab via "restore factory setting" while the tab is on.
Then, I intended to load custom rom into the tab. However all pc, usb, driver, and kies version cannot help me as the tab won't be recognized. It either not showing up entirely or it simply show an error.
Then, I figured that I must format the phone via recovery mode to get the usb working again.
Now is where this problem happened. While formatting, the system message is only stuck at "formatting cache".
It then took a long time until it turned off on its own. This is when the phone cannot be started.
Initially, I can still boot it up until the "samsung galaxy" screen or in download mode. This need to be done by charging it just for a short minute until the battery charging icon shows up. If the battery icon doesn't show up, the phone cannot be started by any means. Then, the boot screen cease to show up but the download mode can still be accessed. Now, the download mode cannot be accessed as well. Lastly, the batter icon won't even show up.
So this lead to my question, what is wrong with my tab. Is is because of corrupted OS, recovery mode. Or perharps faulty battery. Can it be solved by jtag?
Click to expand...
Click to collapse
i think this must be the fault in the os..
if you are lucky to go to the download mode i think you can solve it using odin.
go to sam mobile site and download the firmware for your device.
then install odin app in your pc
(this is my 5th post so i cannot add links)
now while in download mode connect your device to pc.
now open odin in your pc.
make sure you dont uncheck/check anything new in the app
now select PDA and browse the firmware you downloaded and click start.
this may take some time, and your device might reboot several times.
now once you are done there are slight chances for getting stuck in the bootlogo.
in this case you can go to recovery and do a factory reset. then you are all set to go.
NOTE:Charge your device fully before doing this process.
I think this might help you. if still any problem occurs -please notice me.
Zte blade l said:
i think this must be the fault in the os..
if you are lucky to go to the download mode i think you can solve it using odin.
go to sam mobile site and download the firmware for your device.
then install odin app in your pc
(this is my 5th post so i cannot add links)
now while in download mode connect your device to pc.
now open odin in your pc.
make sure you dont uncheck/check anything new in the app
now select PDA and browse the firmware you downloaded and click start.
this may take some time, and your device might reboot several times.
now once you are done there are slight chances for getting stuck in the bootlogo.
in this case you can go to recovery and do a factory reset. then you are all set to go.
NOTE:Charge your device fully before doing this process.
I think this might help you. if still any problem occurs -please notice me.
Click to expand...
Click to collapse
Thanks for taking your time to answer this. Actually, the tab cannot be detected on every pc I have used (3 different pc up to now). Even with drivers and Kies. Do you think it's a problem on the charger port?
I finally found the problem!!
Zte blade l said:
i think this must be the fault in the os..
if you are lucky to go to the download mode i think you can solve it using odin.
go to sam mobile site and download the firmware for your device.
then install odin app in your pc
(this is my 5th post so i cannot add links)
now while in download mode connect your device to pc.
now open odin in your pc.
make sure you dont uncheck/check anything new in the app
now select PDA and browse the firmware you downloaded and click start.
this may take some time, and your device might reboot several times.
now once you are done there are slight chances for getting stuck in the bootlogo.
in this case you can go to recovery and do a factory reset. then you are all set to go.
NOTE:Charge your device fully before doing this process.
I think this might help you. if still any problem occurs -please notice me.
Click to expand...
Click to collapse
After extensive research for weeks, I finally knew the problem! Its actually an emmc brick bug!
The symptoms are all the same. My tab started to brick after I formatted in recovery. Causing no booting, and only download mode and cannot be detected by PC. The funny thing is, the emmc chip have been replaced before by the previous owner I bought the tab from. ONLY FOR THE CHIP TO BE AN INSANE CHIP AGAIN.
Remember folks, the symptoms are:
Cannot boot, sometime boot only on logo. very rare though.
Can only access download mode but cannot be detected by PC. Even if it can, the odin flash will stuck half way.
Can be charged.
How to solve:
I don't know ****