Been lurking on this forum for a few months, learned MUCH on the T679 phone so I purchased one and "customized" it. That phone works great - flashed CWM, Cyanogenmod 9, OC'd kernel, etc. The phone works so well my wife wanted it. So I purchased another, but this one was (is) bricked. Phone powers on fine, but no recovery mode - only download mode - normal boot errors to the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The problem is the phone won't take a boot.img download. I can build a tar file with ANY of the other partitions (modem, kernel, recovery, and so forth) and Odin will flash it just fine. But when I flash boot.img a little message pop-up on the phone screen "Cannot read boot image header".
Nothing I try with ODIN seems to solve the problem, so I looked at using different tools. As I understand ADB/Fastboot won't work because even though I've modified the Windows driver and it "recognizes" the phone - in download mode they still won't see the device so I can send commands. I tried working with Kies - that's a lost cause. I tried working with heimdall - apparently it also doesn't talk to the T679. And I can't use an older Odin (1.85) because it doesn't work with the T679 (older Odin support the PIT which would allow me to repartition).
Researching this tells me the problem is that the boot loader is finding the partition table & recognizes where the partitions are - but when it goes to read the first boot block it fails, thus the error message. So why does the reflash fail? My guess is the boot partition has be either resized, corrupted, or in the wrong spot. I hate to completely blow-away everything because I'll loose the IMEI. I need to save the current encrypted partition, then completely re-partition and restore.
Any ideas?
ptcruser said:
Been lurking on this forum for a few months, learned MUCH on the T679 phone so I purchased one and "customized" it. That phone works great - flashed CWM, Cyanogenmod 9, OC'd kernel, etc. The phone works so well my wife wanted it. So I purchased another, but this one was (is) bricked. Phone powers on fine, but no recovery mode - only download mode - normal boot errors to the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The problem is the phone won't take a boot.img download. I can build a tar file with ANY of the other partitions (modem, kernel, recovery, and so forth) and Odin will flash it just fine. But when I flash boot.img a little message pop-up on the phone screen "Cannot read boot image header".
Nothing I try with ODIN seems to solve the problem, so I looked at using different tools. As I understand ADB/Fastboot won't work because even though I've modified the Windows driver and it "recognizes" the phone - in download mode they still won't see the device so I can send commands. I tried working with Kies - that's a lost cause. I tried working with heimdall - apparently it also doesn't talk to the T679. And I can't use an older Odin (1.85) because it doesn't work with the T679 (older Odin support the PIT which would allow me to repartition).
Researching this tells me the problem is that the boot loader is finding the partition table & recognizes where the partitions are - but when it goes to read the first boot block it fails, thus the error message. So why does the reflash fail? My guess is the boot partition has be either resized, corrupted, or in the wrong spot. I hate to completely blow-away everything because I'll loose the IMEI. I need to save the current encrypted partition, then completely re-partition and restore.
Any ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Did you try this
schuylkillparanormal said:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Did you try this
Click to expand...
Click to collapse
Yes, as I said Odin can successfully flash all the modules (from it's point of view), but the phone screen shows the error after writing boot.img, thus after the flash the phone reboots and I'm right back where I started. I'm trying to determine what tools have been used to partition the sd card for this phone. I'm not having much luck finding ANYONE who's done this.
Thanks though, I'll keep looking. Thing is I don't think even a USBJig would help because right now download mode works.
have you tried flashing cwm in odin mode? version 6.0.3.5 nontouch has odin file http://forum.xda-developers.com/showthread.php?t=2031921
Yes, I've flashed the recovery.img from Odin several times with no error. Here's the log:
<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> recovery.img download..
<1> 1/1 Finished.
<1> PASS!!!
<1> Close serial port and wait until rebooting.
<0> Destroy instant..
<0> Killed timer
As I read source code I see this problem isn't exactly with the boot partition. Obviously the phone boots, and boots into download mode when I hold volume-down. It also boots into RAMDUMP when holding both volume-up/volume-down. I don't get the boot error when the phone boots, only when the download mode receives the boot.img. So then why doesn't the phone boot into recovery mode when I hold volume-up?
T679 partition table is suppose to look like this:
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
Partition mmcblk0p5 (boot loader/odin download mode) works and since it boots with the default Samsung download screen I know that's stock/correct. I don't know if mmcblk0p13 is correct, I suspect it isn't since even after Odin successful download of recovery.img the phone still can't enter recovery mode.
I suspect Odin just sends an identifier to tell the phone what partition it's sending, and download mode determines which linux partition to write it to. I need to keep reading.
ptcruser said:
Yes, I've flashed the recovery.img from Odin several times with no error. Here's the log:
<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> recovery.img download..
<1> 1/1 Finished.
<1> PASS!!!
<1> Close serial port and wait until rebooting.
<0> Destroy instant..
<0> Killed timer
As I read source code I see this problem isn't exactly with the boot partition. Obviously the phone boots, and boots into download mode when I hold volume-down. It also boots into RAMDUMP when holding both volume-up/volume-down. I don't get the boot error when the phone boots, only when the download mode receives the boot.img. So then why doesn't the phone boot into recovery mode when I hold volume-up?
T679 partition table is suppose to look like this:
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
Partition mmcblk0p5 (boot loader/odin download mode) works and since it boots with the default Samsung download screen I know that's stock/correct. I don't know if mmcblk0p13 is correct, I suspect it isn't since even after Odin successful download of recovery.img the phone still can't enter recovery mode.
I suspect Odin just sends an identifier to tell the phone what partition it's sending, and download mode determines which linux partition to write it to. I need to keep reading.
Click to expand...
Click to collapse
Did you try flashing cwm via Odin and then try going into recovery.
http://d-h.st/WeX
Yes, tried that. Odin downloads clean but upon reboot I still can't get into recovery mode. So Odin is Samsung proprietary, what about the download mode code? I've also tried flashing a complete image like XquiziT (odin version) and that doesn't change anything. Of course even this isn't a "complete" image as many of the partitions are still left unchanged, like download mode.
Found an article on EMMCBOOT (tjworld.net/wiki/Android/HTC/Vision/BootProcess). Yea, it's HTC but I expect the Galaxy boot process is similar.
Boot reads the partition map, "After some hardware initialisation the PBL reads the Device Boot Loader (DBL) from the first partition of the flash memory device (In Linux, mmcblk0p1).". Then "It then loads and executes the combined REX/AMSS from partition 5 (Linux mmcblk0p5)", so that explains how things get started.
Which leads me to get the hboot/fastboot interface working. Then I can ask for "listpartition" and "test_partition". Maybe?
recovery.img is correct at /dev/block/mmcblk0p13.
edit: I'd try another Odin version besides the one you're currently using.
I tried odin 4.44, flashing does work, but it didn't fix the problem. I don't know, maybe the boot partition is bad. Riddle me this: at what point does the kernel start? When the phone power's up I see the "SAMSUNG" screen then the failure condition. If I hold the volume down key I boot into recovery mode. Is it possible that the eMMC boot processing is detecting the volume key and starting the download mode? In which case it never tries to boot the kernel? Also, if eMMC boot is directing the startup then there should be no problem going into recovery mode - that is unless the recovery partition is corrupt. But then why can odin flash that partition without an error?
Back to kernel start, after the "SAMSUNG" screen normally you see the "Samsung Galaxy Exhibit 4G" screen, then the boot-up screen (T-mobile, Cyanogenmod, etc). This phone never reaches the "Samsung Galaxy Exhibit 4G" screen, it drops into the failure mode. Perhaps this goes back to the boot partition being corrupt.
Android boot sequence: power -> internal ROM -> bl1 -> uboot -> kernel -> ...
edit: removed stale link
jfbs said:
Android boot sequence: power -> internal ROM -> bl1 -> uboot -> kernel -> ...
Try flashing this http://d-h.st/eNw from Odin with PDA ticked.
Click to expand...
Click to collapse
Odin doesn't understand what to do with a zImage file.
Here's the odin trace:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> e - unknown file - "zImage"
<1> set download environment.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
I've tried Heimdall, but the interface protocol with download mode isn't correct. Isn't that what usually flashes zImage?
Which ROM or kernel did you pull boot.img?
edit: this http://forum.xda-developers.com/showthread.php?t=1644240 may be worth trying.
edit2: or http://forum.xda-developers.com/showthread.php?t=2281287
[Tool][[windows] Make CWM Recovery .img's into .tar.md5 odin flash-able files 1 CLICK
Again, I've learned a lot working on this, but I still don't have it solved.
First, after searching many posts I've realized that Odin flashes the phone rom based on the file names specified in the Ancora.ops file. The T679 ops file looks like this:
0,partition
1,dbl
2,osbl
3,amss
4,emmcboot
5,adsp
6,boot
7,system
8,cache
9,userdata
10,recovery
11,persist
12,preload
This means you can create a tar file with backup file names that match the above. I.e. to rewrite the partition you need a partition.img file. I don't see anyone that has done this but 4.43 odin did flash a partition.img I made from a backup from my working T679. The same thing goes for the dbl, osbl, and persist .mbn files. I created these using dd from my working phone. Thus I have flashed almost all the partitions on this phone, except userdata and emmcboot. I can't flash emmcboot.mbn because I don't have the samsung cert to sign. You can download it with odin, but an error message pops-up on the screen about the sig.
But, in the end I still cannot successfully rewrite the boot partition. Even after successfully rewriting the partition table, and reboot, I use Odin to try to flash boot.img and the "Cannot read boot image header" message still pops-up on the phone.
I am pretty sure that since the phone will not boot to the "Samsung Galaxy Exhibit 4G" screen, I can't get into recovery mode. Which I suspect is due to a problem with either the boot partition OR possibly with /dev/block/mmcblk0p4 MBR extended partition table partition. Next step is to figure out that this table entry is and how modify .ops so that odin will accept this img.
The error is occurring because the boot_image_hdr is missing or invalid in the boot.img file. I'm guessing the download mode software is checking this before it writes it to the boot partition. But this doesn't make sense as others have been downloading the "uvlg3.odin.zip" and odin installs this boot.img just fine. What's different with this phone? What am I missing?
Today I dumped mmcblk05 (emmcboot) on my working t679, then ran strings on the dump and looked at what I found. Not surprising I found the " Cannot read boot image header" string. I also found
ODIN MODE
PRODUCT NAME: %s
SGH-T679
CUSTOM BINARY DOWNLOAD: YES (%d counts)
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: CUSTOM !!
CURRENT KERNEL: SAMSUNG !!
CURRENT KERNEL: UNKNOWN !!
I looked for the kies error, but didn't find it and I suppose that's because this message is actually in some graphics pic.
There are two copies of the "Cannot read boot image header" messages, one with ERROR: before the message and one a few lines lower without. First one must be for the aboot.c kernel startup, where I think the second must be from the download mode.
how long ago did you get the phone also does it say SGH-T679 or SAM-T679 under the battery on both working and non working phones.
TripFX said:
how long ago did you get the phone also does it say SGH-T679 or SAM-T679 under the battery on both working and non working phones.
Click to expand...
Click to collapse
If you can get in Odin try 1 click unbrick or even a jig android doesnt let anything through if it sense something corrupted as part of its security protocal it needs to forced through.
TripFX said:
how long ago did you get the phone also does it say SGH-T679 or SAM-T679 under the battery on both working and non working phones.
Click to expand...
Click to collapse
Both phones say SGH-T679.
I'm sure any experienced andriod developers are laughing when they read this post. Me, I just keep learning in baby steps.
I'm not sure why recovery mode isn't working, recovery has it's own kernel/ramdisk and should alternate boot with a bad boot partition. I discovered I can enable ro.debuggable=1 in the default.prop, but I need to unpack boot.img and modify it.
Next I'll learn how to unpack boot.img. Then, just to be sure I'll unpack the dd dump i took of my working phone partition 8 (should be boot.img). If that works then I'll see if I can unpack the dump I took of the emmcboot partition from my working phone - I can review config files there. Where I'm going is if emmcboot has a default.prop config file then maybe I modify that, rebuild the emmcboot image, and possibly find some way to flash this on the broken phone.
schuylkillparanormal said:
If you can get in Odin try 1 click unbrick or even a jig android doesnt let anything through if it sense something corrupted as part of its security protocal it needs to forced through.
Click to expand...
Click to collapse
Tried 1 click unbrick a while ago, correct me if I'm wrong but I think that tool requires Odin 3 capable phones.
Related
Can anyone help me, my galaxy mini work only on downloading mode, i can't turn on my phone, i have this problem after using the DD method for unlocking the phone.
i tried with Jtag for boot resurection but it's also the same problem, the phone display samsung when he start and reboot on loop.
thanks for the help.
ChAyOTte said:
Can anyone help me, my galaxy mini work only on downloading mode, i can't turn on my phone, i have this problem after using the DD method for unlocking the phone.
i tried with Jtag for boot resurection but it's also the same problem, the phone display samsung when he start and reboot on loop.
thanks for the help.
Click to expand...
Click to collapse
if ur in download mode..then u can flash stock firmware, even after that it gets stuck??
what do you mean by stock firmware ?
i tried to use odin to flash the phone, but after reboot i have the mase problem.
thanks for your reply
I have the same problem, i tried to flash it with the original firmware, but after reboot the phone doesn't work
ChAyOTte said:
what do you mean by stock firmware ?
i tried to use odin to flash the phone, but after reboot i have the mase problem.
thanks for your reply
Click to expand...
Click to collapse
stock firm= froyo,gb. available on samfirmware.com
ya it's done using odin only....download frm samfirmware n try again
For rooting ...
And once you fix your phone, use the upd_1.zip or tass-recovery-cwm.tar to root the phone.
Please note that if you want to remove the lock put in by the carrier, it is a different game.
tha same problem when i use odin with the original frimware.
i don't know what to do to resolve my problem
the phone start, but i have screen flickers.
1 Which version of odin? (Please give full file name)
2. Which firmware version?
3. Have you chosen the appropriate files in appropriate columns - tass, modem, csc, etc? (Or used the one package option - you cannot use one package option for packages with separate files and otherway around too).
4. Are you using the correct USB drivers on the PC?
5. What exactly do you mean by screen flickering?
Can you post output of the log in ODIN?
Hello,
i am using Odin v4.38
i tried to use multiple frimware like: S5570XXKPF, S5570BGKC3_XECKC2_BGKC1, and the original frimware: S5570XXKB1
i am using the correct usb driver from samsung.
for the sreen flickering, i meam when the phone download all package from Odin and after rebooting, i have screen flickering and the phone don't boot.
this is the log from odin:
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> mibib download..
<1> 1/10 Finished.
<1> qcsbl download..
<1> 2/10 Finished.
<1> oemsbl download..
<1> 3/10 Finished.
<1> amss download..
<1> 4/10 Finished.
<1> arm11boot download..
<1> 5/10 Finished.
<1> boot.img download..
<1> 6/10 Finished.
<1> recovery.img download..
<1> 7/10 Finished.
<1> system.rfs download..
<1> 8/10 Finished.
<1> data.rfs download..
<1> 9/10 Finished.
<1> csc.rfs download..
<1> 10/10 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
thanks for your help
Per logs, everything is going right. Unless you messed up the order in files are chosen in odin. (tass.ops, csc, modem, etc).
Can you post a video of the flickering problem? You may have to use another phone, and post the video to youtube.
Also, my question remains - was the phone tied down to any particular carrier?
If you are having boot loop you should wipe data and cache in recovery.
If you are trying to flash gingerbread and don't have a carrier locked phone you can try flashing any gingerbread available at samfirmware.com. They work with any region's phone. If you need details on upgrading visit this:
http://yagyagaire.blogspot.com/2011/08/upgrade-samsung-galaxy-popmini-gts5570.html
description about screen flickering because i don't have another phone to take video: when you put on the galaxy you have displayed in the scren Samsung www.samsungmobile.com and the phone reboot in loop and you have every 3 seconde samsung, and i can't turn off the mobile, for turn off i remove the battery.
i don't have acces to recovery mode, i have only downloading mode.
i tried to install new firmware like Gingerbread, but i have the same problem.
Tried installing CWM recovery and then getting into recovery mode?
yes i tried now, and also the same problem.
Have you tried other key combinations? Like pressing the big button in middle while holding the power button?
Yes i tried and also the same problem.
ChAyOTte said:
Yes i tried and also the same problem.
Click to expand...
Click to collapse
What's your problem by the way... Are you able to see samsung logo or text?? try flashing gingerbread from start. Read this if you have problem...
http://yagyagaire.blogspot.com/2011/08/upgrade-samsung-galaxy-popmini-gts5570.html
And if it is successfull I am sure you'll be able to go to recovery so wipe data and cache there. Otherwise falsh CWM recovery then go toi recoveyr and wipe data and cache...
Remember Home + Power Button = Recovery
the same problem with Gingerbread, i tried 4 version
hi there!
i have same problem . i try to install any rom . on some rom i see big partition size error . i can't power on my phone. does exist any way to format cache or data or any wipe command to clear all data on phone?
Hello,
I've stupidly bricked my phone after following this stated "outdated and risky" SIM unlock tutorial : http://forum.xda-developers.com/showthread.php?t=1204705
OK, you can blame me , I did not take required caution. I just read quickly the procedure and thought that anyway mounting a partition as readonly could not damage anything.
I've followed strictly the procedure, and after "cat /efs/mits/perso.txt" I've involuntary exit from ADB (due to ^C pressed).
I've immediately connected back, noticed /efs was still mounted, and umounted it. All was fine until I've rebooted my phone one day later and now the phone keeps looping immediately after boot. In fact the backlight turns on, and 1 sec later it turns off for 1-2 seconds, and turns on again, off....
Nothing is displayed on the phone, just backlight going on and off.
Here is the current status:
I manage to go to download mode by pressing VOL- + HOME, but I can not go to recovery (as it restart before).
I can connect with ODIN v4;42.
I can successfully flash a stock firmware with ODIN. I've used Orange France latest ROM (S5830BVKT3_S5830FTMKT1_S5830BVKT3_HOME.tar.md5). Here is the ODIN output:
Code:
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> mibib download..
<1> 1/9 Finished.
<1> qcsbl download..
<1> 2/9 Finished.
<1> oemsbl download..
<1> 3/9 Finished.
<1> amss download..
<1> 4/9 Finished.
<1> arm11boot download..
<1> 5/9 Finished.
<1> boot.img download..
<1> 6/9 Finished.
<1> recovery.img download..
<1> 7/9 Finished.
<1> system.rfs download..
<1> 8/9 Finished.
<1> csc.rfs download..
<1> 9/9 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
However, my phone is still bricked ! After ODIN reboot, it goes back again in the infinite restart loop !
So what's wrong there ? Do you think that /efs partition is corrupted ?
I saw that with this ODIN version, I can flash the EFS partition. Of course, I have no backup of it ! I have some receent CWM backups, but no efs partition is included.
If this partition is actually corrupted, could anyone having also a S5830 provide me with a dump of its EFS partition, so I could try to restore it in my phone ?
Any other idea of what is wrong and how to fix it ?
Thanks for help / advise.
ocarles said:
Hello,
I've stupidly bricked my phone after following this stated "outdated and risky" SIM unlock tutorial : http://forum.xda-developers.com/showthread.php?t=1204705
OK, you can blame me , I did not take required caution. I just read quickly the procedure and thought that anyway mounting a partition as readonly could not damage anything.
I've followed strictly the procedure, and after "cat /efs/mits/perso.txt" I've involuntary exit from ADB (due to ^C pressed).
I've immediately connected back, noticed /efs was still mounted, and umounted it. All was fine until I've rebooted my phone one day later and now the phone keeps looping immediately after boot. In fact the backlight turns on, and 1 sec later it turns off for 1-2 seconds, and turns on again, off....
Nothing is displayed on the phone, just backlight going on and off.
Here is the current status:
I manage to go to download mode by pressing VOL- + HOME, but I can not go to recovery (as it restart before).
I can connect with ODIN v4;42.
I can successfully flash a stock firmware with ODIN. I've used Orange France latest ROM (S5830BVKT3_S5830FTMKT1_S5830BVKT3_HOME.tar.md5). Here is the ODIN output:
Code:
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> mibib download..
<1> 1/9 Finished.
<1> qcsbl download..
<1> 2/9 Finished.
<1> oemsbl download..
<1> 3/9 Finished.
<1> amss download..
<1> 4/9 Finished.
<1> arm11boot download..
<1> 5/9 Finished.
<1> boot.img download..
<1> 6/9 Finished.
<1> recovery.img download..
<1> 7/9 Finished.
<1> system.rfs download..
<1> 8/9 Finished.
<1> csc.rfs download..
<1> 9/9 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
However, my phone is still bricked ! After ODIN reboot, it goes back again in the infinite restart loop !
So what's wrong there ? Do you think that /efs partition is corrupted ?
I saw that with this ODIN version, I can flash the EFS partition. Of course, I have no backup of it ! I have some receent CWM backups, but no efs partition is included.
If this partition is actually corrupted, could anyone having also a S5830 provide me with a dump of its EFS partition, so I could try to restore it in my phone ?
Any other idea of what is wrong and how to fix it ?
Thanks for help / advise.
Click to expand...
Click to collapse
Not To worry At all just Do as i Say then the Problem Finished.
now Open the Battery and Put it again to Your Phone
now Power On your Phone into Recovery Mode.
now Wipe all data and factory reset and wipe partition cache
then press Reboot Ur Phone will Be Ok..
If I helped You Click Button Thanks
scorpion85 said:
Not To worry At all just Do as i Say then the Problem Finished.
now Open the Battery and Put it again to Your Phone
now Power On your Phone into Recovery Mode.
now Wipe all data and factory reset and wipe partition cache
then press Reboot Ur Phone will Be Ok..
If I helped You Click Button Thanks
Click to expand...
Click to collapse
Hi,
Thanks for this advice, but as said I can not go into recovery.
I've tried both with (VOL- VOL+ POWER) and (HOME POWER), same result: phone never ends to loop as described.
The only thing I can do is going into download state (with VOL- HOME).
Is there a way to wipe /data and /cache through ODIN ?
Thanks.
ocarles said:
Hi,
Thanks for this advice, but as said I can not go into recovery.
I've tried both with (VOL- VOL+ POWER) and (HOME POWER), same result: phone never ends to loop as described.
The only thing I can do is going into download state (with VOL- HOME).
Is there a way to wipe /data and /cache through ODIN ?
Thanks.
Click to expand...
Click to collapse
Use adb to go to recovery
Code:
Adb reboot recovery
Sent from my ST25i using xda app-developers app
press n hold Home+Power till in Recovery Mode....
remember...hold...it twice bootloop..but its oke
Sent from my GT-S5830 using xda app-developers app
SpaceCaker said:
Use adb to go to recovery
Code:
Adb reboot recovery
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Adb can not connect while in download mode, neither when the device is looping.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot recovery
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot recovery
error: device not found
press n hold Home+Power till in Recovery Mode....
remember...hold...it twice bootloop..but its oke
Click to expand...
Click to collapse
It does not work. I've kept HOME + POWER pressed for 10 loops, and nothing happens.
The phone loops every ~3 seconds, it is very quick. Backlight ON for 1 sec, then backlight OFF for 2 sec.
When I press VOL- HOME, it enters in download mode at next loop, every time. Hence I'm afraid only download mode is working an I need to find a way to fix what is wrong with ODIN, as it seems to be the only tool able to connect with the device.
Any other idea ? What about using ODIN to restore /efs partition ? Could someone post a backup of its /efs partition ? Ideally from a device sold by Orange FR to have the right network setting, but any other could help to validate this assumption.
Thanks
Please, clear solutions!!!
Hi!
It's my first post here! I have to thank everyone around here who share knowledge, intelligence and loads of patience with each other to help resolve problems...
The thing is I've got a Samsung Galaxy Ace S5830 I bought from ebay. I got it right I guess, the thing is I wanted to erase the Vodafone intro it had and leave it with the original ROM by Samsung.
I flashed it with ODIN v.4.38 and after some bugs due to KIES running, etc. everything was right, except for the IMEI that was 000000000000000. It seems that my net connection was not forbidden by my operator (Simyo), but some apps gave me errors related to the 0 IMEI.
As many users, I searched the way to get my IMEI back and, found on many webs the dd method. I ran it through Android Terminal Emulator as SuperUser, of course, on my phone:
# dd if=/dev/block/stl5 of=/sdcard/stl5.rfs
# dd if=/sdcard/stl5.rfs of=/dev/block/stl5
# reboot
You can guess my phone is now bricked, it can't start, got a bootloop with Samsung logo. I cannot enter the recovery mode neither RAM Dump, only can get it into Download Mode (Downloading...).
I tried as many users as well that ODIN method to try reflashing that stl5.rfs that I luckily got saved before it got bricked. But as you guess as well, ODIN fails always and cannot reflash efs folder. I also tried with ops file modifications to supposedly allow the right efs slot.
Heimdall didn't work for me so far, it does never connect the phone or even doesn't run the exe in Windows XP, depending on its version.
After reading hundreds and hundreds of posts here and everywhere, I can't get to read any real solution, apart from taking it to the Samsung Official Service.
So PLEASE: could anyone who successfully unbricked an Ace give a real solution? No more time wasters or evidence reminders, be concise and helpful, PLEASE!!
Thank you!
samsunite said:
Hi!
It's my first post here! I have to thank everyone around here who share knowledge, intelligence and loads of patience with each other to help resolve problems...
The thing is I've got a Samsung Galaxy Ace S5830 I bought from ebay. I got it right I guess, the thing is I wanted to erase the Vodafone intro it had and leave it with the original ROM by Samsung.
I flashed it with ODIN v.4.38 and after some bugs due to KIES running, etc. everything was right, except for the IMEI that was 000000000000000. It seems that my net connection was not forbidden by my operator (Simyo), but some apps gave me errors related to the 0 IMEI.
As many users, I searched the way to get my IMEI back and, found on many webs the dd method. I ran it through Android Terminal Emulator as SuperUser, of course, on my phone:
# dd if=/dev/block/stl5 of=/sdcard/stl5.rfs
# dd if=/sdcard/stl5.rfs of=/dev/block/stl5
# reboot
You can guess my phone is now bricked, it can't start, got a bootloop with Samsung logo. I cannot enter the recovery mode neither RAM Dump, only can get it into Download Mode (Downloading...).
I tried as many users as well that ODIN method to try reflashing that stl5.rfs that I luckily got saved before it got bricked. But as you guess as well, ODIN fails always and cannot reflash efs folder. I also tried with ops file modifications to supposedly allow the right efs slot.
Heimdall didn't work for me so far, it does never connect the phone or even doesn't run the exe in Windows XP, depending on its version.
After reading hundreds and hundreds of posts here and everywhere, I can't get to read any real solution, apart from taking it to the Samsung Official Service.
So PLEASE: could anyone who successfully unbricked an Ace give a real solution? No more time wasters or evidence reminders, be concise and helpful, PLEASE!!
Thank you!
Click to expand...
Click to collapse
NO WAY, Send your device to the service centre... I'm sorry
http://forum.xda-developers.com/showthread.php?t=2324070
Same problem with me after installing Mounts2SD on stock 2.2.1. I'm not sure if it caused by Mounts2SD or the power button. My phone's power button is hard to press.
Any solution for this problem?
mandayugana said:
Same problem with me after installing Mounts2SD on stock 2.2.1. I'm not sure if it caused by Mounts2SD or the power button. My phone's power button is hard to press.
Any solution for this problem?
Click to expand...
Click to collapse
Jtag can help in this problem. Search in your location for jtag service.
Hi Every Body
i cannot enter recovery mode
vol up + home + power >>>> Dumpram Mode !!
vol up + home + power >>>> Got Android Box then after few seconds Restart without see the recovery mode
after reading
i use odin FeaModRecovery_1.2.tar.md5
i got the recovery mode now i select option install from sd
but ,,, it hanging nothing happen
so try to clear cash also nothing
after 4-5 restart i lost the recovery mode again
-------------------------------------------------------------------------
now when i flash any stock rom its complete succefully but no changes its my same apps
when i use odin to flash "Boot_loader.tar"
<1> VerifyPlatform:V0, P0,R0
=======================================
echo " Reboot into Recovery mode"
adb reboot recovery
Nothing happin :|
------------------------------------------------------------------------------------------
what is the problem??????????
Hey,
Something along the way went wrong
best solution IMO:
use this:
ODIN ,I9000XXJVU_I9000OXAJVU_OXA pack
includes
:
STOCK:
s1_odin_20100512.pit
CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5
GT-I9000-CSC-MULTI-OXAJVU.tar.md5
MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5
ROOT:
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.tar
First: Install STOCK with odin select partition, and the other two
Second: Install ROOT with odin
that should fix the problem.
AhmedSaQeR said:
what is the problem??????????
Click to expand...
Click to collapse
your combo keys are wrong, follow the fuide in the i9001 wiki
you have an i9001 so follow proper flashing guide i9001 Flashing Guide
Check this out! Links to useful Guides and " Banned " Documentaries
NewstHet said:
Hey,
Something along the way went wrong
best solution IMO:
use this:
ODIN ,I9000XXJVU_I9000OXAJVU_OXA pack
includes
:
STOCK:
s1_odin_20100512.pit
CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.md5
GT-I9000-CSC-MULTI-OXAJVU.tar.md5
MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5
ROOT:
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.tar
First: Install STOCK with odin select partition, and the other two
Second: Install ROOT with odin
that should fix the problem.
Click to expand...
Click to collapse
where to get all of this ?
i want trusted links please
AhmedSaQeR said:
where to get all of this ?
i want trusted links please
Click to expand...
Click to collapse
your phone i9000 or i9001? Do not flash JVU on i9001 as suggested by NewstHet you will have more problems , he/she is talking about i9000
Check this out! Links to useful Guides and " Banned " Documentaries
xsenman said:
your combo keys are wrong, follow the fuide in the i9001 wiki
you have an i9001 so follow proper flashing guide i9001 Flashing Guide
Check this out! Links to useful Guides and " Banned " Documentaries
Click to expand...
Click to collapse
-------------------------------------------------------------------------------
what do you mean of combo keys are wrong?
==========
and i follow steps at the link 2
this what happen
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> amss.mbn download..
<1> 1/7 Finished.
<1> adsp.mbn download..
<1> 2/7 Finished.
<1> boot.img download..
<1> 3/7 Finished.
<1> system.img.ext4 download..
<1> 4/7 Finished.
<1> cache.img.ext4 download..
<1> 5/7 Finished.
<1> recovery.img download..
<1> 6/7 Finished.
<1> preload.img.ext4 download..
<1> 7/7 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
------------------------------------------------------------------------------
2 restarted
1: i see the progress bar with android logo and box
2: i got my same rom and same apps nothing happen
why and what happen ??
xsenman said:
your phone i9000 or i9001? Do not flash JVU on i9001 as suggested by NewstHet you will have more problems , he/she is talking about i9000
Check this out! Links to useful Guides and " Banned " Documentaries
Click to expand...
Click to collapse
Model : GT-I9001
???
AhmedSaQeR said:
what do you mean of combo keys are wrong?
Click to expand...
Click to collapse
your thread title is about recovery mode, and the combo keys for recovery mode is Volume Up + Power., not what you satated in the first post, so its wrong.
what you are now saying is , no matter what you flashed the phone works with your old ROM only, is this correct?
so try enter CWM , if you don't have it flash a version 6 CWM from [Toolkit][A.I.O Rescue & Recovery] My Android Collection
or from the i9001 WIKI
enter CWM recovery, format everything, do not reboot, (just pull out battery) or you can power off by CWM too, than enter download mode an flash a ROM.
if you cannot format the partitions, than your internal SD card is corrupted.
Check this out! Links to useful Guides and " Banned " Documentaries http://forum.xda-developers.com/showthread.php?t=1796807
xsenman said:
your thread title is about recovery mode, and the combo keys for recovery mode is Volume Up + Power., not what you satated in the first post, so its wrong.
what you are now saying is , no matter what you flashed the phone works with your old ROM only, is this correct?
so try enter CWM , if you don't have it flash a version 6 CWM from [Toolkit][A.I.O Rescue & Recovery] My Android Collection
or from the i9001 WIKI
enter CWM recovery, format everything, do not reboot, (just pull out battery) or you can power off by CWM too, than enter download mode an flash a ROM.
if you cannot format the partitions, than your internal SD card is corrupted.
Check this out! Links to useful Guides and " Banned " Documentaries http://forum.xda-developers.com/showthread.php?t=1796807
Click to expand...
Click to collapse
i cannot reach recovery mode to root or wipe
this is my main problem now
so i tried another ways to fix my recovery mode
Special Thanks For Every Body Help Me To Fix My Problem
Special Thanks For xda-developers
Finallu Its Done
Using Odin 4.43 + broodROM_RC5
i found some bugs , but at least Finally Its Working Again
Thanks All
Hello , I accidentally made a mistake by naming a rom "Update" and went into recovery mode and updated it . The phone bricked and stuck at the Samsung Logo . I tried Odin . It's connected to Odin but when I press start , it freezes at SetupConnection..
I tries putting the PDA MD5 file into the PDA and everything , I installed KIES for the driver and ended the program in task manager but it still doesn't let me get pass SetupConnection . I really need to fix it before my parents find out . Oh and I can only access download mode .
Flash some custom rom from recovery first it will be easier........then flash from odin the stock firmware if u want
aayushkhajuria2842 said:
Flash some custom rom from recovery first it will be easier........then flash from odin the stock firmware if u want
Click to expand...
Click to collapse
I forgot to say .... I can't access recovery . When I hold the home button and the power button , it switched on and freezes at the samsung logo . The only thing I can access is the download mode . I want to flash the stock firmware . It keep getting stuck at the setupconnection like I said ...
New update
I downloaded Odin V4.38 Multi-Downloader for GT S5830
I inserted OPS Cooper V1 and I place the Official Firmware MD5 File in the PDA section , After that I start the phone in download mode and connect to Odin and I press start .
This Happened
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> e - unknown file - "param.lfs"
<1> e - unknown file - "!Ce‡"
<1> set download environment.
<1> boot.img download..
<1> 1/1 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
After that , they restarted my phone , this time , it just show a blank screen . And the timer ran for around 3-4 Min
After that , it showed
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
But when I turned on my phone , it still stuck at the Samsung Boot screen . Help . The only place I can access is the Download mode .
Try to flash some kernel with custom recovery it would bring back your recovery
aayushkhajuria2842 said:
Try to flash some kernel with custom recovery it would bring back your recovery
Click to expand...
Click to collapse
What's custom recovery ? , I can't flash CWM either . It was CWM that made my phone bricked
Also I tried flashing CWM with Odin but it also got into blank screen at the reboot part .
Fixed , I used another firmware .
For future reference, here is the link on how to flash stock rom using odin on Samsung Galaxy Ace.
Flash stock rom on Samsung Galaxy Ace S5830 using odin
Hope I helped
Recently Flashed OS2SD-TWRP 2.8.5.0 . Flashed CyanogenMod 12.1 rom From @cars1189 . After flashin it the wrong way i believe i got a message saying "Encryption Unsucessful" and to reboot . when i rebooted it automatically tried to go into recovery mode and that when it started looping (keeps blinking) at the TWRP screen. i am able to go into download mode but my Computer reconize it as "Unknown USB Device (Device Failed Enumeration)"
Who Knows how to fix this problem?
Download mode drivers work well with xp, vista, and win7. Try this to get synced and for Odin. Follow this reference and you should get stock back.
jfbs said:
Download mode drivers work well with xp, vista, and win7. Try this to get synced and for Odin. Follow this reference and you should get stock back.
Click to expand...
Click to collapse
i installed windows 7 now ... got the drivers to recognize the phone in dowload mode but now wa is happen is Odin is now crashing when ever i try to flash the recovery -.- i get "odin is nor working properly" and now my phone is now saying (Upgrade with Kies)
Have you tried running Odin as admin since you're using win7?
help !!
Recently Flashed OS2SD-TWRP 2.8.5.0 . Flashed CyanogenMod 12.1 rom From @cars1189 . After flashin it the wrong way i believe i got a message saying "Encryption Unsucessful" and to reboot . when i rebooted it automatically tried to go into recovery mode and that when it started looping (keeps blinking) at the TWRP screen. i am able to go into download mode but when i try to flash a recovery via odin it gets stuck at setup connection.
i removed kies, installed samsung usb driver several versions, change usb cables, ports, rebooted.
please help !!
Did you ever figure out a solution? I have the same exact issue.
no more help??? i Flashed my using cwm.6051.t679 + cm-10.2-20140627-UNOFFICIAL-ancora_tmo.zip everything done fine, but when i try to Flashed cm-12.1-20160326-UNOFFICIAL-ancora_tmo.zip i got a message saying "Encryption Unsucessful" and reboot, after reboot i try (New OS2SD-TWRP 2.8.5.0) and Flashed again, reboot then TWRP blue screen never gone! try odin mode:
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> e - unknown file - "preload.img.ext4"
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> amss.mbn download..
<1> 1/4 Finished.
<1> adsp.mbn download..
<1> 2/4 Finished.
<1> boot.img download..
<1> 3/4 Finished.
<1> cache.img.ext4 download..
<1> 4/4 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
after rebooting TWRP TWRP TWRP TWRP!!!!!!! again!!
update: i try do again again again again again again again, finally i download another Ancora.ops file, now everything back to normal!!! Ancora.ops file come with uvlg3.odin.zip is WRONG!!
download Ancora.ops from here:
https://docs.google.com/file/d/0B2e_XGOiZowOdTRQYUZjQmVlX3c/view
I had to install Ubuntu on an old hard drive and install the free virtual machine version of windows 7 from Microsoft into virtualbox . Just to get the drivers to work and to be able to flash the device in download mode. Just a tip for getting it into download mode. Plug in the usb cable, get the charge screen up and power it on, and then hold down the volume button. Keep doing this and eventually it will jump into download mode. Once you do that follower other peoples instructions for Odin here. This is what I had to do because I was using Windows 10 but you can completely legally and for free setup a virtual box of windows 7 in Ubuntu to fix stuff like this. It took me a week to find that out.
So my Exhibit is now working like brand new. I just think I should learn how to swap the external drive for the internal because the storage capacity is very small.