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
I have an earlier thread here http://forum.xda-developers.com/showthread.php?t=2107600 but that is now buried on page 2 and might be missed by new readers. After a disastrous time trying to root my Galaxy Tab 5100 I did manage with the help of people here to flash the recommended stock ROM - however while the tablet goes through its boot sequenece with the aminated Samsung sign - it sticks when it gets to the plain Samsung logo and wont go further.
Odin reported that it installed OK and the tab rebooted as it should but only this far - not sure what I should try next to get my stock Samsung image back and working. One thing I didn't do was to tick repartition because the instructions only said to do this when a certain type of file was included in the package, and it wasn't. Should I have ticked this after all, if so I can try the same thing again if I can force it back into download mode again. (though as the yellow pane still shows in odin when connected I wonder if I can just go ahead anyway)
I have also been looking for rooting software and came across this
http://root-android.org/?version=Tablet&country=Samsung&ios=Galaxy+Tab+2&submit.x=63&submit.y=104
I am wondering if next time (assuming I ever get it working!) I would be better shelling out $30 and getting software to do it all for me - is this any good? has anyone used it or had reports about it? I wish I had seen this before I read "that it was almost impossible to brick the tab 2"
Also I would like to have root access on my S3 as well but wouldn't dream of risking this I don't think now
gbswales said:
I have an earlier thread here http://forum.xda-developers.com/showthread.php?t=2107600 but that is now buried on page 2 and might be missed by new readers. After a disastrous time trying to root my Galaxy Tab 5100 I did manage with the help of people here to flash the recommended stock ROM - however while the tablet goes through its boot sequenece with the aminated Samsung sign - it sticks when it gets to the plain Samsung logo and wont go further.
Odin reported that it installed OK and the tab rebooted as it should but only this far - not sure what I should try next to get my stock Samsung image back and working. One thing I didn't do was to tick repartition because the instructions only said to do this when a certain type of file was included in the package, and it wasn't. Should I have ticked this after all, if so I can try the same thing again if I can force it back into download mode again. (though as the yellow pane still shows in odin when connected I wonder if I can just go ahead anyway)
Click to expand...
Click to collapse
Have you tried a factory reset from recovery? If you've restored the stock ROM, then all you need to do is the factory reset to get things working again. Don't repartition unless you really need to.
gbswales said:
I have also been looking for rooting software and came across this
http://root-android.org/?version=Tablet&country=Samsung&ios=Galaxy+Tab+2&submit.x=63&submit.y=104
I am wondering if next time (assuming I ever get it working!) I would be better shelling out $30 and getting software to do it all for me - is this any good? has anyone used it or had reports about it? Also I would like to have root access on my S3 as well but wouldn't dream of risking this I don't think now
Click to expand...
Click to collapse
I can't see any reason you should spend that kind of money given how easy the CF-AutoRoot is. In fact, that product looks very shady to me. "Root Any Android Device"? Well, there's lots of devices out there that nobody's been able to root, or devices that take a lot of work. I can't believe there's a single app that'll work across every Android device with a single click.
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
CWM ?
DigitalMD said:
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
Click to expand...
Click to collapse
Well I followed one of the posted routes on this forum, downloading from a list of recommended files for each version, and it mentioned nothing about CWM which I know nothing about. I have to say that everyone's definition of "easy" on here - I find complicated and difficult - I know my way around windows but android seems much more complex. The only reason I wanted to have root in the first place was to be able to make a complete image back up that would make it easy to restore my device without having to re-download all my software and set up. I do it with windows all the time. To me "easy" is, download and install something - click go - done! Even getting the device to go into download mode in the first place is a very hit and miss affair (as others say on here too) clearly Samsung don't want you to do this.
The other problem is that while the tablet is in this state it wont turn off, just reboots itself when you do and the screen stays on - so unless you leave it plugged in 24/7 - I start each time with a flat battery that I have to recharge before I can try something else
This is the route I followed
DigitalMD said:
Be careful, which stock ROM have you flashed? I would use this sequence
flash the stock ROM
then immediately
flash CWM recovery, use CWM recovery to wipe the data (wipe data/factory reset).
Then reboot
Click to expand...
Click to collapse
I got this through earlier posts - the only thing I didn't do was to go into recovery and reset in step 2 because this simply wasn't possible - the device was stuck on the error message and no amount of button pressing did anything other than restart to the same screen. By this stage I couldn't even go back to check what version of android I was running - it would have been the latest jelly bean distributed to UK.
I also didn't check re-partition as in 6. because there was no pit file in the download
E. Restore to stock
THIS WILL WIPE YOUR DATA!
4.0.3 for p5100: https://hotfile.com/dl/155804946/76b...XALD9.rar.html
4.0.3 for p5110: http://www.hotfile.com/dl/159635395/...3_PEO.zip.html
4.0.4 for p5100: http://www.hotfile.com/dl/165065733/...1_SER.zip.html
4.0.4 for p5113: http://www.hotfile.com/dl/164415704/...5_XAR.zip.html
4.0.? for p5113: http://69.46.67.99/GT-P3113_XAR_1_20...ldcgx9tzmx.zip
4.0.4 for p3100: http://samsung-updates.com/fw/Samsun...3kdo3qe503.zip (PIT files: 16Gb p3100, 8GB p3100
Note: for more language options for stock ROM's for the tab 10, go here.
1. Unzip the downloaded ROM. If there is a file ending in .pit, skip to step 3
2. Reboot into recovery and select wipe data/factory reset.
3. Reboot into Download Mode.
4. Unzip/unrar the stock firmware
5. click PDA and find the stock file (PDA/PLATFORM file, the largest one).
6. Click PIT and open the .pit file you downloaded if one was included with your ROM. Check Re-Partition in ODIN
7. OPTIONAL: if you want to flash the bootloader and/or csc, you can select them as well. If you don't know what that means, you don't need to do it.
8. Click Start.
9. Enjoy!
Help please - this is where I am at the moment - some SIMPLE help needed please
I tried to install what I thought was the stock ROM - it appeared to install but wouldnt boot past the samsung screen. I now realise (a) that I may not have followed the full correct procedure and (b) may have downloaded the 5110 rom instead of the 5100 rom - silly mistake I know.
However reading all the guides I can find there doesnt seem to be a simple way I can find of restoring the standard un-rooted rom so that I can go back and try again. All of the things I can find seem to included downloading something onto the external card but cant do that as I cannot access it and don't have an external card reader.
What I can do now is
boot into download mode
connect to ODIN and see the yellow block
It will not boot normally past the samsung splash screen
and cannot connect to KIES in any mode (I do have the drivers installed and have connected before)
I also have no idea now what is installed on it because I cant get to the system to see!
Is there an easy way to install a stock samsung rom from this point? I don't mind if data is lost, I have nothing important on there and wouldnt mind re-installing apps as I had accumulated far too many anway - really I just want to get my tablet back the way it was from the factory but with the 4.2 jelly bean installed (though if it went back to an earlier version and I could update in Kies that would be ok too)
Can anyone give me simple instructions for doing this using just ODIN and my computer without involving the external card - please.
After that I will be looking for an equally easy way to root it again
I will credit you with a good answer if you can help -as well as appreciating it.
gbswales said:
I tried to install what I thought was the stock ROM - it appeared to install but wouldnt boot past the samsung screen. I now realise (a) that I may not have followed the full correct procedure and (b) may have downloaded the 5110 rom instead of the 5100 rom - silly mistake I know.
However reading all the guides I can find there doesnt seem to be a simple way I can find of restoring the standard un-rooted rom so that I can go back and try again. All of the things I can find seem to included downloading something onto the external card but cant do that as I cannot access it and don't have an external card reader.
What I can do now is
boot into download mode
connect to ODIN and see the yellow block
It will not boot normally past the samsung splash screen
and cannot connect to KIES in any mode (I do have the drivers installed and have connected before)
I also have no idea now what is installed on it because I cant get to the system to see!
Is there an easy way to install a stock samsung rom from this point? I don't mind if data is lost, I have nothing important on there and wouldnt mind re-installing apps as I had accumulated far too many anway - really I just want to get my tablet back the way it was from the factory but with the 4.2 jelly bean installed (though if it went back to an earlier version and I could update in Kies that would be ok too)
Can anyone give me simple instructions for doing this using just ODIN and my computer without involving the external card - please.
After that I will be looking for an equally easy way to root it again
I will credit you with a good answer if you can help -as well as appreciating it.
Click to expand...
Click to collapse
What you need to do is to download the stock ROM for your 5100.
Go to www.samfirmware.com and put "GT-5100" into the search box. You'll see a list of the stock firmware for your device. Pick the appropriate firmware for your country and click "download".
Start up ODIN. Click on the "PDA" button and open the firmware file you downloaded above.
Restart in downloader mode (power and volume up), and connect the tablet to your PC. ODIN should now show the device.
Make sure repartition is not checked, and click on "Start". When it finishes, you now have stock firmware installed.
Power off, then restart in recovery mode. (Hold power and volume down.)
Choose "wipe data/factory reset" by using the volume keys to move the highlight, then pressing the power button to select an entry.
Once it's finished booting, you should be back to normal.
Thanks K1MU for this information which at least looks clear - the only problem I have is when I put in the model etc when I get to country it offers me only 3 choices
UK (BTU) GB (O2) or GB (vodafaone)
My phone was purchased from Amazon and is unlocked so I am worried if these might lock me to a carrier which I wouldn't want
I wonder if BTU is the unlocked one as it doesn't sound like any provider I know - but I am not sure
will post on their forum as well
I think I am getting more and more muddled by the minute (sign of old age I fear) I realise now that I have a p5110 - wifi only and not p5100 3g and wifi.
This means in all probablilty I downloaded the correct rom in the first place. As I had not done the factory reset afterwards so tried that - it appeared to work ok but when I restarted it just played the samsung tune and moving image - then went to "Samsung" and stuck there as it was before.
I am downloading the p5110 wifi only rom from Sam's site - awful download programme they use which doesn't accept paypal even to sign up for faster downloading - I will then try following exactly what you have suggested and keep my fingers crossed
thank you
k1mu said:
What you need to do is to download the stock ROM for your 5100.
Go to www.samfirmware.com and put "GT-5100" into the search box. You'll see a list of the stock firmware for your device. Pick the appropriate firmware for your country and click "download".
Start up ODIN. Click on the "PDA" button and open the firmware file you downloaded above.
Restart in downloader mode (power and volume up), and connect the tablet to your PC. ODIN should now show the device.
Make sure repartition is not checked, and click on "Start". When it finishes, you now have stock firmware installed.
Power off, then restart in recovery mode. (Hold power and volume down.)
Choose "wipe data/factory reset" by using the volume keys to move the highlight, then pressing the power button to select an entry.
Once it's finished booting, you should be back to normal.
Click to expand...
Click to collapse
Although I thought it had got nowhere after wipe restore - when I turned it back the next day I arrived at the start up guide - admitedly it was 4.0.3 and in Portugese but after exploring settings and working out what to click i got it back to uk english - it has now connected to kies ok and is currently downloading the latest firmware - thanks partcularly to the last poster and to all others who helped - I will go through and thank you others too,
Point is now - once I have jelly bean can I get root access easily -without installing another custom rom - ahh well tomorrows problem
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Unfortuently there is no clear tutorial to root this phone but you car read here: [GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
Snypie said:
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Click to expand...
Click to collapse
1. Do i need custom rom?
no
2. Do i need custom kernel?
no
3. Will the android self update as now?
if you flashed TWRP, no
1. Do i need custom rom? No
2. Do i need custom kernel? No
3. Will the android self update as now? depend on your settings
1-to root it the first thing is to have OEM Unlock available and enabled in Dev Options
if not keep the device fully on and with data on dont restart, power off or reset for at least 7 days continuously (or a bit more) and you should have it
if it's not shown dot bother with the rest
2-to have Dev Menu available go to settings >> about phone >> software information >> on build number tape multiple times 10 times i guess, you will have a pop up confirmation
once back at settings menu you will find a new choice at the very bottom "Develper Options"
3-next step with to plug ur phone with PC with usb cable
after installing SAMSUNG DRIVERS & ODIN and downloading TWRP (custom recovery)
in ODIN 2nd tab, untick "AUTO REBOOT" VERY VERY IMPORTANT
chose the TWRP file using AP button/option in ODIN
put your phone in download MOD power off completely >> power back on while holding vol+ and vol- at the same time
flash the file using ODIN to your phone
4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so, after flashing TWRP, press vol- + power button to reboot the phone
AT THE VERY PRECISE MOMENT WHEN PHONE TURN OFF BEFORE POWERING BACK ON WHEN IT BLINK
RELEAS POWER BUTTON AND VOL+ and PRESS POWER BUTTON + VOL+ AGAIN VERY VERY QUICKLY
if successful you should boot into TWRP directly
5-once you are in TWRP wipe everything then format the device (ALL DATA WILL BE LOST)
of course you need to have the needed files already copied in the SD CARD
from twrp after the wipe and formatiing
go to install and flash in that order RMM_Bypass_v3_corsicanu or RMM-State_Bypass_Mesa_v2
then no-verity-opt-encrypt-6.0
then at the end flash Magisk-v19.3
once its done reboot the phone normally, you will have your phone working as normal
once you are in, install Magisk APK MagiskManager-v7.3.2
reboot again
and voilaaa, you should have root and everything shoul be functional for you
allthow of course I will not be responsible for any kind of software or hardware damage, and certainly not ressponsible for any data loss
as it is completely you responsibility
I would like to attach all the files mentioned above, to help better but dnt sems to find how
so you will have to download and gather them from previous posts
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Snypie said:
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Click to expand...
Click to collapse
its virtually impossible to brick samsung devices these days. Well, perma-brick that is. I have spent entire evenings after work bricking phones just so i could figure out what caused the brick and then fix it. the worst thing that would happen if the FRP lock gets enabled again is that youd have to go re-disable it.
i guess i didnt really explain that clearly after re-reading it. So, when he says "stuck" he means with TWRP installed and no method of rooting. The phone will boot normally in the situation described in point #4