Related
ok i know, another attempt to learn something from seniors:
Just downloaded the 'GT-P1000-CSC-MULTI-OXXJK2.tar.md5 *' from samfirmware.com attempt to flash asian multicsc and after unzipping, see the tar.md5 extension and feel something have to do with the 'signed' thingy every one now fear of.
This tar.md5 contains 3 files: cache.rfs, dbdata.rfs & moveinand.mst
May i know will i face problem if i flash this csc with Roto's JME firmware?
I just try flashed my tab to the newest asian rom == ZHKA1 with the CSC u mentioned .....
After reboot.......
Do u think I being signed?
HA...HA....HA....
It still unsigned and can flash any rom I like..
I just test it with SGT bootloader check..!!!
So, just go on, without this CSC, the tab even can't boot!!!!!
MY FIRST FLASH in Galaxy TAB...
the mentioned CSC didnt work with Roto's JME flash which i applied to my SGT. Odin1.7 reported checksum not right or something like that and halt the flash. so i am using CPW from JME multiCSC that came with Roto's.
I will try when gingerbread 2.3 is ready for SGT. btw, you're from HK/China to use that ZHKA1?
I from Hong Kong, haven't flash Roto JPE before as it have protected bootloader issue.
Just follow the guide of Chainfire to asure the ROM is safe before flash. I think your tab have be protected as the post stated by Chainfire.
Sent from my GT-P1000 using XDA App
rainbow ng said:
I just try flashed my tab to the newest asian rom == ZHKA1 with the CSC u mentioned .....
After reboot.......
Do u think I being signed?
HA...HA....HA....
It still unsigned and can flash any rom I like..
I just test it with SGT bootloader check..!!!
So, just go on, without this CSC, the tab even can't boot!!!!!
MY FIRST FLASH in Galaxy TAB...
Click to expand...
Click to collapse
Check Fus also notified me of KA1 version available, but could you kindly explain step by step how you upgraded your FW please?
smaragdhk said:
Check Fus also notified me of KA1 version available, but could you kindly explain step by step how you upgraded your FW please?
Click to expand...
Click to collapse
he....he.... "Fus" mean what??
I am not expert, just share my experience to see if it helpful.
When I 1st flash I9000, I lost much thing, like APN (can't use 3G), CSC code( no Samsung Apps to download, market link, can't use KIES to update offical rom, IMEI no), and some app which need password and username as I forgot that anyway. So try to backup everything is the must before you flash, as mentioned by Rotohammer and Chainfire.
Go to your APN setting and write down everything for u to get your 3G connection.
Use Z4Root to root your device and make a full backup with "Titianium Backup".
Use SGS tools to backup ur product code, something like nv_data.bin etc.
Use root explorer to copy the /efs
Use Chainfire root if u can to make a nandroid backup of your current ROM, it is highly recommended in case your TAB being bricked can easily recover to the current stage without pain.
after everything backuped, copy all the file to your computer or external SD card and remember to unmount it.
Flash is simple , backup is painful but MUST do if u don't want to post "my TAB is bricked, help me pls" in the forum. (In actual case , it is really difficult for u to brick your TAB or I9000 permenant if u are not a developer like Chainfire as they always try to make something experimental on the phone that why they are so respective!
Flash procedure:
1. stop the KIES running in your computer, (front or background running is not allowed), terminate it by task manager of window if u don't know how.
2. start the Odin v1.7
click the re-partition box, click the pit and choose p1.pit, click the PDA and choose the ROM file u want to flash,in me case is KA1, which should with .tar as extension, click the CSC and choose the CSC u want to use.
3. power off you TAB , remove SIM and SDcard, press the volume down and the power buttons together for a few seconds, a nice yellow android robot appear on the skin, release the buttons and connect to the computer asap.
4. the Odin window will appear a yellow box if it detect the phone, then click the start button.
5. everything will go on automatically , no need to do anything and pls don't, be patient . The whole process of flashing about 3 to 7 minutes, then the TAB reboot to fresh new ROM.
p.s. if any thing go wrong or missing berfore u connect the phone to computer, just close all restart again, do not click any thing not mentioned. If the phone hv any problem long press the power button for 8 second will reboot. if u failed (odin will tell u), and see "phone-!-computer" ,just re- start the odin again and plug in the phone, u will see the yellow box and click start , the flashing process wil restart once again.
hope helpful. ;-)
Sent from my GT-P1000 using XDA App
rainbow ng said:
Flash procedure:
1. stop the KIES running in your computer, (front or background running is not allowed), terminate it by task manager of window if u don't know how.
2. start the Odin v1.7
click the re-partition box, click the pit and choose p1.pit, click the PDA and choose the ROM file u want to flash,in me case is KA1, which should with .tar as extension, click the CSC and choose the CSC u want to use.
3. power off you TAB , remove SIM and SDcard, press the volume down and the power buttons together for a few seconds, a nice yellow android robot appear on the skin, release the buttons and connect to the computer asap.
4. the Odin window will appear a yellow box if it detect the phone, then click the start button.
5. everything will go on automatically , no need to do anything and pls don't, be patient . The whole process of flashing about 3 to 7 minutes, then the TAB reboot to fresh new ROM.
Click to expand...
Click to collapse
Are you able to root this? I did the same as you before, but error is not enough space for superuser.apk sigh, if you have any info, perhaps enlightening me
EDIT: Nevermind Put in su, busybox, and superuser.apk into /system/app through linux mount, in the process I removed usual stuffs that I dont need Cool!
fastcx said:
EDIT: Nevermind Put in su, busybox, and superuser.apk into /system/app through linux mount, in the process I removed usual stuffs that I dont need Cool!
Click to expand...
Click to collapse
use adb shell
rootsh
mount /system
cd app
ls ~~ to see what is inside and choose some unwanted app
rm
exit
exit
and now u gain space in /system and can install su
Sent from my GT-P1000 using XDA App
rainbow ng said:
use adb shell
rootsh
mount /system
cd app
ls ~~ to see what is inside and choose some unwanted app
rm
exit
exit
and now u gain space in /system and can install su
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Already rooted it yesterday but thanks anyway, i just edit the factory.rfs in linux b4 I flash it into my tab instead now I dont need to remove anything after flash
fastcx said:
i just edit the factory.rfs in linux b4 I flash it into my tab instead now I dont need to remove anything after flash
Click to expand...
Click to collapse
Out of interest, do you use this Linux shell command ?
#mount -o loop factoryfs.rfs /mnt/rfs
On Mac OS X terminal I normally use the following commands, but I don't think modifications can be written back to the RFS archive:
#sudo mkdir /Volumes/rfs
#sudo hdiutil attach -imagekey diskimage-class=CRawDiskImage -nomount factory.rfs
#sudo mount_msdos /dev/disk{n} /Volumes/rfs
I use Ubuntu for most of my Android hacking, so I guess I will also start using Linux to look inside RFS archives, and to modify them directly
[GUIDE] How to upgrade, root & flash Samsung Galaxy Ace S5830 [DOWNLOAD LINKS | CWM5]
Hey guys,
in this tutorial I will show you how to upgrade and root your Samsung Galaxy Ace S5830. This method is the simplest way to do it.
Shall not be liable for any resulting damage to your phone! Everything you do at your own risk!
If you want to upgrade to newer version then Gingerbread I suggest you to make full procedure, not only flash recovery.
WARNING
If you don't understand what is root, ROM, phone, flash, CMD etc. watch this movie
You will need these files:
Brain
PC with Windows XP SP2 or later
Samsung Galaxy Ace GT-S5830
USB to Micro-USB cable
.Net Framework 2.0 or later
Android Software Development Kit (SDK)
Samsung Kies or Samsung Android USB Drivers
ODIN 4.38 + OPS
SuperOneClick (for 2.2> firmwares) or Universal Gingerbread Root or Unroot (for 2.3< firmwares)
ClockworkMod Recovery 5.0.2.6 (Fixed!)
New firmware
*Optional Custom ROM
Newest firmware:
Release name: S5830DXKT7
Release date: November 2012
Country: Vietnam
CSC: S5830OLBKT3
Android Version: Gingerbread 2.3.6
DOWNLOADS
Dropbox
Google Drive
YouTube Tutorial
Thanks to GadgetCheck!
A. Preparing your PC:
Install .Net Framework 2.0
Install Android SDK
Download SDK Tools & Platform-tools in Android SDK
Right click on Computer and select Properties
Select Advanced System Settings then Advanced and Click the Environment Variables button.
Click on the variable called 'Path' and then click on Edit. Now add the target directory to the value of the variable, using a semi-colon as a separator.
Add system path to Android SDK and Android SDK Tools folders
x86
Code:
C:\Program Files\Android\android-sdk
C:\Program Files\Android\android-sdk\platform-tools
x64
Code:
C:\Program Files (x86)\Android\android-sdk
C:\Program Files (x86)\Android\android-sdk\platform-tools
Now your PC is ready!
B. Preparing your phone (only for 2.2.x users! If you only want to root your phone, go to step D, if your phone don't have root skip this steps):
Install Samsung Kies
Turn on your phone
Enable Debugging at Apliccations>Programming
Connect your phone into PC via cable
Launch SuperOneClick
Click "Unroot"
Wait
When the process is complete turn off SOC and unplug your phone
Reboot to apply changes
Now you have unrooted phone!
C. Flashing the newest firmware:
Turn off your phone
Remove your SIM Card and SD Card
Extract previously downloaded firmware
Open ODIN 4.38 on your PC and change OPS file name to
Code:
Cooper_v1.0.ops
Select from extracted archive: OPS-OPS, Boot-APBOOT, Phone-MODEM, PDA-CODE, CSC-CSC (leave EFS and One Package empty)
If archive contains only <filename>.tar.md5 select it as PDA and OPS as OPS, leave other fields EMPTY
Connect your phone via USB into PC
When the screen is turned on hold POWER+VOLUME DOWN+HOME and wait until the phone enters the Download Mode
If ODIN detected and recognized your phone should light up the first square to the left side
Press "Start" button and wait, the process should take ~5 minutes
If all goes well your phone should reboot automatically
Square should change the color to blue and display "PASS" it means that flashing process was successful and we have the newest firmware
Disconnect your phone
Turn off your phone
Insert your SIM Card and SD Card again
Turn on your phone
Now you have the newest firmware!
Da. Rooting for 2.2.1:
Turn on your phone
Enable Debugging at Apliccations>Programming
Connect your phone into PC via cable
Launch Super One Click 2.3.3
Click "Root"
Wait until the program will root your phone
When the process is complete turn off SOC and unplug your phone
Reboot
Now you have root!
Db. Rooting for 2.3.x (NEW METHOD!):
Download file called universal_gb_root_v25.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file universal_gb_root_v25.zip
After the update completed - reboot
Now you have rooted S5830
OPTIONAL Unrooting for 2.3.x:
Download file called universal_gb_unroot_v9.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file universal_gb_unroot_v9.zip
After the update completed - reboot
Now you have unrooted S5830[/QUOTE]
OLD ROOTING METHOD FOR 2.3.x
Rooting for 2.3.x (Thanks to russian forum-user with nickname may213) (if it doesn't work try D method):
Code:
upd_1.zip [URL="https://hotfile.com/dl/193725879/700f6be/upd_1.zip.html"]HotFile[/URL]
Download file called upd_1.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file upd_1.zip
After the update completed - reboot
Now you have rooted S5830
Unrooting for 2.3.x (Thanks to ingbrzy) (if it doesn't work try D method):
Code:
unroot.zip [URL="https://hotfile.com/dl/193725835/d31c709/unroot.zip.html"]HotFile[/URL]
Download file called unroot.zip and copy it to your sdcard
Turn off your phone
Press POWER+HOME BUTTON
Select update from sdcard, select the file unroot.zip
After the update completed - reboot
Now you have unrooted S5830
Click to expand...
Click to collapse
E. Flash Custom Recovery:
Put recovery-clockwork-5.0.2.6-galaxyace.zip into SD Card
Turn off your phone
Press POWER+HOME BUTTON
Select Update Zip From SD-Card option. [If you are on previous version of CWM recovery then you might need to select Install Zip From SD Card and then Choose Zip From SD Card Option simultaneously. ]
Select recovery-clockwork-5.0.2.6-galaxyace.zip and flash it
Reboot your device
F*. Flash Custom ROM:
Select Custom ROM
Put Custom ROM .zip into SD Card
Turn off your phone
Press POWER+HOME BUTTON
Wipe All
Select "Install zip from sd card"
Select "Choose zip"
Select .zip with your Custom ROM
Select "Yes"
Reboot into system
That's ALL!!!
Now you have the newest firmware and root and probably Custom ROM!
Please don't send me messages on IM because i don't have much time to read it and reply. I've maded special thread for problems and issues: http://forum.xda-developers.com/showthread.php?p=22230605#post22230605
If I helped you, click "Thanks" also you can vote it into main page, rate this thread or donate me
If you have problems with one of this steps post it in this thread I will try help you!
about to root mine.will let u know wat happens.
jnrphil said:
about to root mine.will let u know wat happens.
Click to expand...
Click to collapse
What do you mean?
it worked!!!thanx
You're welcome
Sent from my GT-S5830 using XDA App
hubix said:
You're welcome
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Why I cannot find the DXKC1 firmware?
Hello, i need FW DXKC1. Can you help me? I don't find it on samfirmware . Please!!!
P/S: Sorry for my bad english ~.~
Where are you from? I need to know this to tell you the newest available ROM for your phone.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
i'm from Vietnam, my FW is XXKC1 but i need DXKC1
I have found the problem, sometime my ACE freeze
when the phone freezes,and i have to take the battery out to get it work.
hi hubix, do you know where to find this galaxy rom: S5830DXKA9 if you know please post a link. or do you know how to extract a rom from galaxy ace because i want to share my S5830DXKB1 firmware which i currently have now.
If you can't find it at samfirmware it doesnt exist. Link: http://www.samfirmware.com/WEBPROTECT-S5830.htm
The newest Asia firmware is S5830ZCKA7
I've related names of the newest ROM for any continent in the 1st post.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
hubix said:
If you can't find it at samfirmware it doesnt exist. Link: http://www.samfirmware.com/WEBPROTECT-S5830.htm
The newest Asia firmware is S5830ZCKA7
I've related names of the newest ROM for any continent in the 1st post.
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
Click to expand...
Click to collapse
Actually, i'm from the philippines and when i connec to Kies its prompting me to upgrade my firmware from xxxxDKA9 to xxxxDKC1, so i assume it is an asian firmware, but when i check in samfirmware.com this xxxDKC1 is under the European firmware. Nonetheless, i have upgraded my firmware via kies and now it is xxxDKC1, and i dont see any issue/s on it so far.
It fixes wifi disconnecting bug, LED Flashlight + stock camera program bug and it's more stable for me
Sent from my Samsung Galaxy Ace GT-S5830 using XDA App
Congratulations body, very good explained , very good tutorial!
Thank you very much
can't open downloaded attachments
i can't open downloaded attachments, another mirror please...
I've edited 1st post. Now you have official mirrors there
hubix, thank you...
tomdotnet said:
hubix, thank you...
Click to expand...
Click to collapse
No problem
i've followed all the steps and Odin detects the device, but when i start the process the phone never reboots - keeps the "Downloading..." text in the screen - and i'm "stuck" at the first step, "mibib download..". any ideas?
this is the debug message..
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
UPDATES STOPPED: MORE IN-DEPTH THREAD POSTED OVER IN DEVELOPMENT FORUM WITH UPDATED INFORMATION.
http://forum.xda-developers.com/showthread.php?t=1275031
There have been a number of threads regarding working with the Sprint tablet. Due to the lack of support for it, I've complied various items from all across the information tubes to help your get the full use of your Sprint tablet.
I've compiled the instructions from various sources across the internet. If I've failed to reference an item, let me know and I'll correct it.
Something to keep in mind - Heimdall and Odin use different drivers. You WILL NEED to swap between them each time you swap programs. It's unfortunate, but it's necessary.
Flash back to stock (EA24) with Odin
1) Download the files from here
2) Open Odin, and select PDA
3) Choose the appropriate .tar file.
4) Make sure repartition is UNCHECKED!
5) Press start.
6) When the process is finished, the Odin program will say Pass, then Reset.
Install Gingerbread on your Tab
1) Download this file
2) Rename it to update
3) Place it on the root of your SD Card (not in a folder)
4) Boot into recovery and choose "apply update.zip"
Install Rooted Gingerbread on your Tab
1) Download the rooted GB file.
2) Open Odin, and select PDA
3) Choose the appropriate .tar file.
4) Make sure repartition is UNCHECKED!
5) Press start.
6) When the process is finished, the Odin program will say Pass, then Reset.
Root your Sprint Galaxy Tab on FROYO
1) Download SuperOneClick
2) Enable USB Debugging
3) Connect your Tab to the PC
4) Run SuperOneClick
5) Select Root
6) You're rooted!
If you're on Gingerbread, see this thread
Heimdall (needed to flash kernel with CWM)
1) Download Heimdall and unzip
2) Download Microsoft C++ 2010 Redistributable Package
3) Put the Tab in download mode (Vol Down + Power)
4) Connect it to your PC
5) Navigate to your Heimdall folder and run zadig.exe
6) Choose Options>List all devices>Samsung USB Composite Device
7) You'll receive a prompt about the driver, accept to install.
Kernel with CWM Recovery for FROYO
1) Download the zip file here
2) Unzip the file. You will need the file named zimage only.
3) Open Heimdall Frontend
4) Select Browse under Kernel and navigate to the file you downloaded in step 1 and select it
5) Press Start
6) The Tab will reboot, but will freeze on the Samsung logo. Turn it off and boot into recovery (Vol Up + Power)
7) CWM Recovery will attempt to back your tab up, but will fail. Don't fret.
8) Do a factory reset in CWM Recovery and reboot
9) You'll freeze on the Samsung logo again Turn it off and boot into recovery.
10) CWM Recovery will back your Tab up successfully.
11) You now have a CWM backup. Reboot.
12) Your auto rotate is broken.
13) Download the rotation file
14) Put it in /system/lib/hw and change the permissions to match the other items.
Heimdall/CWM instructions compiled and cleaned up from here
Flashing ROMs
1) Keep in mind that the dev may suggest a specific kernel. See kernel instructions (step 1-5 above)
2) Put the ROM .zip file on the root of your SD Card
3) Choose install .zip from SD Card in CWM Recovery
4) Select the ROM .zip file
ROMs for the Sprint Galaxy Tab
1) Honeycomb - in early stages (Dev - spacemoose)
2) Better than Life - FROYO (Dev - oldmacnut)
3) Future Echoes - GB - (Dev - oldmacnut)
4) MIUI Port - (Dev - oldmacnut)
Finally, each of these steps involves the potential of rendering your device useless. Take care with each step. If you're not 100% comfortable with the process, post your questions. Hopefully, other Sprint owners will take note of the thread and use it.
I rooted a couple weeks ago and finally flashed cwm the other day, i wish this had been posted then! Nice job.
question, when i install cwm when i turn on usb mode it shows up as a cd rom on my pc, is that normal?
cmlucht said:
question, when i install cwm when i turn on usb mode it shows up as a cd rom on my pc, is that normal?
Click to expand...
Click to collapse
From what i've read, that is a known side effect, it happened to me too. Also my camera and screen auto rotation are broken. I know there's a solution to the screen rotation issue, but still looking for the solutions for the other two issues.
l8agin said:
From what i've read, that is a known side effect, it happened to me too. Also my camera and screen auto rotation are broken. I know there's a solution to the screen rotation issue, but still looking for the solutions for the other two issues.
Click to expand...
Click to collapse
I have the rotation sensor file. Ill post it when I get home tonight.
Sent from my SPH-P100 using XDA App
^ Thanks, do you have any ideas about the camera and cd rom issue? Would a custom rom or kernal fix those issues?
l8agin said:
^ Thanks, do you have any ideas about the camera and cd rom issue? Would a custom rom or kernal fix those issues?
Click to expand...
Click to collapse
I don't know about the camera, because I never use mine. Ill try to do some research on it.
If I remember correctly, it seems that spacemoose1 had a fix for the cd rom issue. Might wanna try posting in that thread. If you get an answer, bring it back over here and ill include it in the first post.
Sent from my DROID Pro using XDA App
Rotation file
http://www.megaupload.com/?d=CMZV7A9Y
Put it in /system/lib/hw and change the permissions to match the other items.
Sent from my SPH-P100 using XDA App
mounting the sd card
Yes I can confirm that spacemoose had a fix for the mounting of the sd card instead of showing up as a cdrom. I use it. I'll post it. Thanks spacemoose1!!!
Perform the following while tab is connected to pc via usb
1) open cmd prompt
2) cd to "adb.exe" directory (usually the android sdk tools directory)
3) adb shell
4) mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard
5) echo /dev/block/mmcblkp1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
Thanks, I gotta figure out how to do this.
I'm from Vietnam and I cant download the KhasMek rom via the host gunsforgeeks.com.
Could you guys please re-upload for me these rom [link belowed] on another hosts such as megaupload, duckload, mediafire ...
Thank you very much
Code:
1. KleanMod
http://gunsforgeeks.com/Tab/roms/KhasMek.DJ11.KleanMod.v3.zip
2.Voodoo plus
Hemidall
http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.plus.CDMA.Tab.v4.OC.zImage
http://www.gunsforgeeks.com/Tab/addons/VoltageControl-gt.apk
Odin
http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.plus.CDMA.Tab.v4.OC.tar
http://www.gunsforgeeks.com/Tab/addons/VoltageControl-gt.zip
gsu_golfer said:
Rotation file
http://www.megaupload.com/?d=CMZV7A9Y
Put it in /system/lib/hw and change the permissions to match the other items.
Sent from my SPH-P100 using XDA App
Click to expand...
Click to collapse
I finally fixed the rotation issue, now working on the cd rom issue. Thanks
USB connection appears in CD-rom
same problem with me
my camera also ran out of work
How do I revert to the stock recovery and get rid of this CWM?
prezmater said:
How do I revert to the stock recovery and get rid of this CWM?
Click to expand...
Click to collapse
Just out of curiosity, why do you want to do it?
Reflash the stock kernel.
Thanks so much for this topic. A lot of Sprint-centric instructions have been scattered around the forums and consolidating it in one place is enormously helpful.
Thanks!
gsu_golfer said:
Just out of curiosity, why do you want to do it?
Reflash the stock kernel.
Click to expand...
Click to collapse
I have no idea where to find the stock kernel. I need to do this because ever since I flashed CWM my auto rotate does not work.
prezmater said:
I have no idea where to find the stock kernel. I need to do this because ever since I flashed CWM my auto rotate does not work.
Click to expand...
Click to collapse
Have you tried the posted instructions on fixing rotation?
EDIT: I just added them to the OP.
Perform the following while tab is connected to pc via usb
1) open cmd prompt
2) cd to "adb.exe" directory (usually the android sdk tools directory)
3) adb shell
4) mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard
5) echo /dev/block/mmcblkp1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
what do i start up the command prompt on my computer and what do i type in there come on can any body help me please i am still stuck on the Samsung logo i put the sd card back in my tab an it shows up cd drive..
gsu_golfer said:
Have you tried the posted instructions on fixing rotation?
EDIT: I just added them to the OP.
Click to expand...
Click to collapse
I was finally able to revert to stock with Odin.
I've gotten into the habit of running all kinds of ROMs and sometimes they just blow up. Usually a reboot suffices but the last crash caused my phone to only bootloop and I couldn't get into recovery anymore, thankfully download mode still worked. This will focus on how to get your phone back to life, provided you can access download mode.
Steps this guide will walk you through:
Calm down a bit
Get everything you need to fix your phone
Do the magic
Boot your phone
Rejoice
Step 0: Backup
I can't stress this enough. Once you've really bricked your phone there's a chance you might not be able to access the data that's on there anymore. So, if there's stuff on your phone you care about, just backup it from time to time.
Step 1: Calm down
There's a myriad of exercises you can do to calm down, meditate, go for a walk/swim/jog, go to the gym, whatever works for you. Just chill out for a second because being in a completely panicked state is not going to help you to recover your phone.
Step 2: Get the tools in place
We need a few tools to fix your phone:
Heimdall version 1.3.1. DO NOT download 1.3.2 it has issues with uploading large files
Windows: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.1-win32.zip
Mac: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-1.3.1-mac.dmg
Debian AMD64: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_amd64.deb
Debian i386: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_i386.deb
Heimdall package of 2.3.6/XWJVZ: http://www.mediafire.com/?3v35chw9a8a2wmw
CFRoot for 2.3.6/XWJVZ: http://download.chainfire.eu/130/CF-Root/SGS/CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip
Once you've downloaded everything:
Install Heimdall (run the installer)
On Windows the link I provided also includes the GUI
For Mac and Linux the link I provided only includes the command line binary, we don't want to use the GUI for this
Extract the Heimdall package of 2.3.6.tar.gz to a directory, you should end up with the following files:
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
firmware.xml << delete it, we're not going to need it
modem.bin
params.lfs
Sbl.bin
s1_odin_20100512.pit << delete it, we're not going to need it
zImage << delete it, we're not going to need it
Extract the CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip, this contains only one file: zImage, put it next to Sbl.bin
If the Heimdall installer asked you to reboot your machine but you didn't, do it now. That will make sure the drivers are loaded.
What we've done right now is set up your machine so that it's ready to flash your i9000 back to a Samsung release of Gingerbread. The astute reader might notice I'm telling you to delete the zImage (kernel) from the Heimdall package. This is true but we're replacing it with the one from CFRoot so you can flash a rooted stock instead of first flashing stock and then flashing CFRoot on top. Some people advice against this approach but it has never caused me issues.
Step 3: Do the magic
Now we're actually going to flash your phone. We're going to do this from the command line because the Heimdall GUI is a bit twitchy when it comes to flashing without a PIT-file. The command line has no such issue and will just download the PIT from your device and use that.
Windows:
Find out where Heimdall was installed (probaly %PROGRAMFILES%\Heimdall)
Copy all the files (zImage, Sbl.bin and so forth) into the directory where the heimdall executable is located
Go to the location of cmd.exe, right-click on it and select: Run as Administrator
Now cd to the directory Heimdall was installed
Issue a dir on the commandline to verify all the files (heimdall.exe and the rest) are there
Mac / Linux:
Heimdall was probably installed into /usr/bin so all you need to do is open a Terminal of your choice and see if running the heimdall command results in heimdall output or a command not found.
Open a Terminal
cd to the location of zImage, Sbl.bin and the other files from Step 2
Flashing:
Use the 3-button combo to put your phone into Download mode: Volume Down + Home + Power and connect your phone over USB to your computer.
Windows, issue the following command:
Code:
heimdall.exe flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --dbdata dbdata.rfs --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage
Mac / Linux, issue the following command:
Code:
sudo heimdall flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --dbdata dbdata.rfs --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage
If all went well you should get output similar to this:
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
IBL+PBL upload successful
Uploading SBL
100%
SBL upload successful
Uploading PARAM
100%
PARAM upload successful
Ending session...
Rebooting device...
Your device will now reboot. If it doesn't and stays at a black screen, just pull the battery, put it back in and turn it on.
Step 4: Boot your device
Just let the phone boot but don't unlock your SIM-card / use it. Once it's is done booting for the first time just shut it down and now boot into Recovery Mode: Volume Up + Home + Power.
From here you can go into the Mounts and Storage section and then into the Mount USB menu. Now your phone will make it's storage available over USB so you can recover files you've lost or upload a zip-file to flash a new ROM.
Step 5: Rejoice
Your phone is now back into a workable state with a fully functional Recovery so you can now start flashing your fancy ROMs again.
A few pieces of advice:
Before you flash anything else: data/factory reset and wipe your cache
Before you flash anything else: flash CM 9.1.0, twice. The first time will upgrade your Recovery to 6.x but will then bootloop so you need to flash it again.
If you want to flash a JellyBean ROM, flash CM 9.1.0 first. If you don't and try to upgrade from Gingerbread (2.3.6) to JellyBean in one go you'll probably end up with an invalid IMEI (no idea why this happens, it just does)
Good luck!
Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got:
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
ERROR: Failed to confirm end of file transfer sequence!
IBL+PBL upload failed!
Ending session...
Rebooting device...
Click to expand...
Click to collapse
Please HELP me
What do I do from here??
battznz said:
Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got:
Please HELP me
What do I do from here??
Click to expand...
Click to collapse
That one is in my experience either caused because you supplied a PIT-file or because you've got a funky version of Heimdall.
how about when the phone can't get to download mode :/
usb jig?
microMXL said:
how about when the phone can't get to download mode :/
usb jig?
Click to expand...
Click to collapse
try solutions in My Android Solutions
Use only ROM and solution for your model and Wipe x3
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)
The link for Heimdall version 1.3.1. (Windows) you posted has no Installer inside.
I desparetely need to unbrick my Gaaxy S. Any solutions?
SpartanWarrior said:
The link for Heimdall version 1.3.1. (Windows) you posted has no Installer inside.
I desparetely need to unbrick my Gaaxy S. Any solutions?
Click to expand...
Click to collapse
try download from My Android Collections
Phone stuck in bootloop, possible corrupt internal memory?
HI,
Thanks for your post, as a noob I find posts like yours great as they are easy to follow, and have all the info in one spot.
I have followed everything that you said to do, however, when my phone reboots after cmd successfully finishes, it boots into recovery, and says the following:
[QUOTE]--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
--Deleting files...
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
--Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished
Succesfully updated filesystem.
--Wiping cache...
Formatting /cache...
Cache wipe failed.
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.[/QUOTE]
If I hit "reboot system now" it comes up with the Galaxy S logo, then switches off, then repeats itself, the only way to stop it is to take the battery out. I can still access both recovery and download mode at this stage.
I bought this phone cheap off someone who had installed a custom ROM which had messed the phone. I am trying to get it working again, but I think I may only have made it worse . The phone is not recognizing any SDcard, or its own internal memory. When the phone was working, if you went into settings under memory it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"
Any help would be much appreciated.
Thanks
mars777jd said:
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
Click to expand...
Click to collapse
try to flash a Ezbase Rescue or Darky resurrection Kit from My Android Collections
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
xsenman said:
try to flash a Ezbase Rescue or Darky resurrection Kit from My Android Collections
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Hi,
I tried EzBase Rescue, with the following result:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
-- Wiping data...
Formatting /data...
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
I will try the resurrection kit...
mars777jd said:
Hi,
I tried EzBase Rescue, with the following result:
I will try the resurrection kit...
Click to expand...
Click to collapse
Couldn't seem to find a link to the resurrection kit that worked properly. All other rescue packages either result with bootloop or the above error messages in recovery mode.
mars777jd said:
Couldn't seem to find a link to the resurrection kit that worked properly. All other rescue packages either result with bootloop or the above error messages in recovery mode.
Click to expand...
Click to collapse
you can try http://depositfiles.com/files/ro6fnlr38 or http://depositfiles.com/files/zay0if5x7 for Darky and a solution from My Android Solutions for
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
well just for the record, mine didn't work neither with usb jig, now I have a pretty nice paperweight. *sighs*
microMXL said:
well just for the record, mine didn't work neither with usb jig, now I have a pretty nice paperweight. *sighs*
Click to expand...
Click to collapse
usb jig can only work when USB slot is not damaged or misaligned , check usb connection problems in My Android Solutions or read this thread
mars777jd said:
HI,
Thanks for your post, as a noob I find posts like yours great as they are easy to follow, and have all the info in one spot.
I have followed everything that you said to do, however, when my phone reboots after cmd successfully finishes, it boots into recovery, and says the following:
[QUOTE]--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
--Deleting files...
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
--Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished
Succesfully updated filesystem.
--Wiping cache...
Formatting /cache...
Cache wipe failed.
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
If I hit "reboot system now" it comes up with the Galaxy S logo, then switches off, then repeats itself, the only way to stop it is to take the battery out. I can still access both recovery and download mode at this stage.
I bought this phone cheap off someone who had installed a custom ROM which had messed the phone. I am trying to get it working again, but I think I may only have made it worse . The phone is not recognizing any SDcard, or its own internal memory. When the phone was working, if you went into settings under memory it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"
Any help would be much appreciated.
Thanks[/QUOTE]
Same happens to me. Any idea on what's going on?
vindikleuk said:
it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"?
Click to expand...
Click to collapse
explain what is your phone model, if you had lag fix applied before and what you had done and what is the exact message you are getting when you try to boot .
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
xsenman said:
explain what is your phone model, if you had lag fix applied before and what you had done and what is the exact message you are getting when you try to boot .
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Well what happened is this:
I saw this phone going cheap on eBay by someone who said that they "had tried flashing a custom ROM, and now the camera won't work due to a memory error." I had successfully flashed CM7 to a Nexus One, so I wanted to see if I could fix it.
I don't know what ROM he tried to install, but at that point the phone still booted. I could use the phone and all functions that didn't need free memory (ie camera). I went into settings, and, like I mentioned, although there was a micro-SD card the phone reported "0.00B free of 0.00B Internal" and "Please insert an SD card" for external. I thought it may have been a problem with the SD card, so I formatted it on the computer. Same result.
I then proceeded to flash a known trusted stable ROM to the phone. I opted for CM9 with CWM for I9000. This is where I first ran into problems. I was using fastboot at the time, and always, after flashing anything I would get these results (see pics.) So I downloaded Odin, and after trying several different things from various wiki's and guides on xda and other sites, I believe I have successfully wiped any existing OS, and any custom recoveries.
The phone's model is GT-I9000. The SSN is I9000GSMH. I also have the IMEI and S/N. From my understanding, it was originally locked to Vodafone, and was unlocked by the previous owner.
So far I have tried flashing:
CM9
DarkyRom_10.2 Resurrection
ezbase gb
SGS_Rescue_kit-13-1-2012
plus a few different individual pda, csc, bootloader files.
I am again going to try DarkyRom_10.2 Resurrection, once I can get Odin to recognize my phone.
Is there any thing else I can try? Or should I try to sell my phone for parts?
I really appreciate everyone's help
Thank you so much
mars777jd said:
Is there any thing else I can try? Or should I try to sell my phone for parts? I really appreciate everyone's help
Thank you so much
Click to expand...
Click to collapse
you may need to repeat flash at least 3 times, first with 512 PIt and repartition, second with 803 Pit NO REPARTITIONING and finally a normal flash without PIT, use JVU or JVZ ROM
xsenman said:
you may need to repeat flash at least 3 times, first with 512 PIt and repartition, second with 803 Pit NO REPARTITIONING and finally a normal flash without PIT, use JVU or JVZ ROM
Click to expand...
Click to collapse
OK, I will try that, do you know where to find those?
mars777jd said:
OK, I will try that, do you know where to find those?
Click to expand...
Click to collapse
in My Android Collections
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Thank you guy, your tuto saved my device
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
help please
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
sms473 said:
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
Click to expand...
Click to collapse
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
santatralalaina said:
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
Click to expand...
Click to collapse
Hi..thanks for the reply....My phone is G2 F320L..Korean version with removable battery and SD card....I tried to install a non compatible ROM..got bricked with only fastboot...Then I try to flash aboot.bin..boot.bin..laf.bin..etc files (which I have extracted from the kdz) through fastboot...during flashing my phone was disconnecting and connecting back again...thats where all the problem started I guess. Now I dont have fastboot also. If i connect my phone to PC.. LG logo comes on the phone screen...on PC it try to detect as LGE android MTP devices and try to install the driver of the same. But the driver installation fails eventually.... At windows device manager it show as LGE Android MTP devices with error code 10...and showing connected to port:COM3....If I try to get in to the download mode..it get stuck at the (.............) download page...it is not going to the page with big USB picture...
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
sms473 said:
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
Click to expand...
Click to collapse
Hello,
It was easy to unbrick the fastboot but now... ok, you are stuck in LG LOGO but after no black screen? can you charge you battery? And if you try to go to RecoveryMode, what's happen? do you have multiple partitions and QHSUSB_DLOAD trying to be instaled? It's also easy to unbrick the QHSUSB and if it is the case, don't use send_command to flash manualy your device.
Maybe, you can force flash. You have to find a solution to push all .img files to your device. If you cannot use ADB, try to put the img files to sdcard.
you can found send_command.exe and ports.bat in this zip file, it's an utilities for having root on LG G2 :
LG_Root.zip
you can use all root command with it!
Added to index thread
[INDEX][LG G2] ROMs, Kernels, Guides and more
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Well, I need help. how do i copy these files to my device? my device is not located in adb. cant i just flash the files from there place in my pc?
hi - I have t mobile d801 .it has boot loop - show lg logo and then the android robot and then lg logo again.
it does enter download mode(but with the 4 blue dots - but in the device manager cant install the drivers.
when the phone is plugged in to computer normally without download mode' it shows lge phone and drivers in device manager.
I tried to flash kdz bit stuck on 60%. it shows on phone download mode - but not show the firmware update logo.
what should I do?? when I d.mode not the regular d.mode - device isn't detected in pc. so I think this is my main problem.
try with srk tools no luck. its says waiting for device..is there any solution? thanks!
foxyfoxyblah said:
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Click to expand...
Click to collapse
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
santatralalaina said:
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
Click to expand...
Click to collapse
I don't have ADB, so most of these i cant do.
im scared of touching the motherboard....
so im not shorting test point.
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
i have flashed wrong firmware ..now my phone have same symptoms like urs with partial download mode and no recovery....but i m unable to push files via adb bcz adb debugging is not active and i m getting error that phone not found.....now what can i dooo...plz plz plzzzz help me
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
santatralalaina said:
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
Click to expand...
Click to collapse
and how to do that?
Thank you your topic was helped me to find a solution for my phone lg g3