Hello all!
I have trouble with my device. I have YP-G1CWY/XAA. I made a mistake when flash my device. I flash G1ZSKC5-REV01-PDA-low-CL976041 by Odin, but it for INTL. And after this touchscreen work not correctly and battons from the bottom do'nt work. After I try flash stock YPG1US by hemdall for full recovery, but this did not help. After this touchscreen and battons do not work. Next my step, I flash by hemdall G1ZSKC5;
IBL+PBL: boot.bin
SBL: sbl.bin
PARAM: param.lfs
CACHE: cache.rfs
DBDATA: dbdata.rfs
FACTORYFS: factoryfs.rfs
KERNEL: zImage., with YPG1US.pit and repartition.
Touchscreen work, but not correctly, battons from the bottom do not work. I don't know what me do. Help please!
Related
After an attempt to root with Odin3, which by the way ended with a Fail.
(Note: When I tried to root the phone I didn't click PDA and designated a .tar)
My phone turns on and goes to a screen with an exclamation mark in a triangle with the message of "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I haven't found a solid post on how to fix this.
any help?
-------------FIXED------------
I used the wrong PDA file for my Skyrocket. It is not a 1777. GOES TO SHOW, BE CAREFUL, the smallest and dumbest mistake can waste you a lot of time...
This happens when you flash a bad tar file. I have had it happen with a bad param.lfs in the PDA slot. I'm not really sure, but I think it depends on what you actually had in the bad tar file. My problem was solved by flashing a good param.lfs tar. So I hosed the param.lfs with a bad tar, and then fixed it by flashing a good tar.
I can't say any more about your situation without knowing exactly what you tried to flash with Odin. You say you did not put anything in the pda slot, but what exactly was the configuration? What were you flashing with odin? A kernel?
So this is what I did to get me in this situation.
I followed these instructions...
http://forum.xda-developers.com/showthread.php?t=1309293
and instead of a success, I got a red Fail!. I forgot whether I put in a .tar or not, i very well might have not. If that means anything. But now when I put in a .tar is still says fail regardless.
That tar file contains zedomax's kernel for rooting and ClockworkMod Recovery. It only contains the zImage which is the kernel.
I think you can recover by flashing Entropy512's Unbrick/Return to Stock plus root using Odin. You can find his thread in the development forum, or use the instructions and the one-click downloader in step 2c of my guide. This will also give you the root you are trying to get.
Let us know if you have success.
I get a Fail! on the Odin One Clicker.
"<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)"
The error is beyond my knowledge. At this point I am only speculating. Maybe one of the developers will help.
I'm thinking that somehow some other part of the file system was damaged during the first Odin flash. The Unbrick/Return to Stock package does not flash the secondary bootloader or the param.lfs. You could try flashing those two files one at a time, starting with param.lfs first, to see if one of them is the problem. There is always risk when flashing bootloaders or the param.lfs. And again, I am only speculating. And further, while I've learned quite a lot from reading and doing, I am not a developer.
If you want to try those options, downloads and instructions are available in the Download Repository.
Alright, if worst comes to worst I can try exchanging it. I got the phone about 2 weeks ago so I still have a 30 day return/exchange.
You really shouldn't have to exchange it. You are soft bricked, as it is called. As long as you can get into download mode, you can recover the phone.
Since you can boot into download mode, it is clear that your bootloaders are still good. You have already attempted to flash --factoryfs --kernel and --modem. That leaves the following sections of the file system that could be causing the problem. --cache --dbdata --param and the partition table.
If it was my phone, I would next try flashing the param.lfs using Odin. After that I think I would switch over to Heimdall command line and flash --factoryfs --kernel --modem and --param together.
Maybe Entropy will see this and have some suggestions.
I hate to potentially put this burdon on you, but could you link me to those files your refering to?
ashaiba said:
I hate to potentially put this burdon on you, but could you link me to those files your refering to?
Click to expand...
Click to collapse
For param.lfs, downloads and instructions are available in the Download Repository, both the tar for odin, and the file for heimdall.
For the stock rom parts, extract factoryfs.img, zImage and modem.bin from downloads available in Entropy512's UCKH7 Return/Unbrick to Stock thread in the development forum.
How to flash Entropy512's Return/Unbrick to Stock, Kernel + Non-Rooted System Package with the param.lfs and the modem from the command line using Heimdall
Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
Download Entropy512's Return/Unbrick to Stock kernel plus non-rooted system package and the modem package. Extract the PDA.tar files from this package to a directory on your hard disk drive, then extract the three component files from the tar - zImage, factoryfs.img and modem.bin.
Place zImage, factoryfs.img, modem.bin and param.lfs in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --factoryfs factoryfs.img --param param.lfs --kernel zImage --modem modem.bin
First try flashing just the param.lfs tar using Odin. Try the Heimdall flash if that doesn't work.
OHHHH DO I FEEL STUPID. i don't have the galaxy s2 1777. i have the 1727 Skyrocket. -_- sorry man.
peace.
Hi. I use Linux primarily, I have vista dual boot but it's inconvenient to reboot just to restore my Fascinate.
I have downloaded the EH03 .zip file CI500_VZW_EH03_GB_CM.tar.md5 with the sum of 89045064cf45ccd85f8ad746911b6e28. I extracted it and then ran heimdall like this:
Code:
heimdall flash --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --kernel zImage --modem modem.bin
And then it finished installing, and then it just was in a boot loop, going from the red verizon screen to the blue animation whatcha-ma-call-it. Anyway it wouldn't boot. So then I Odin'ed it and did it fine.
How do I heimdall eh03? did I miss an option or something?
mvmacd said:
Hi. I use Linux primarily, I have vista dual boot but it's inconvenient to reboot just to restore my Fascinate.
I have downloaded the EH03 .zip file CI500_VZW_EH03_GB_CM.tar.md5 with the sum of 89045064cf45ccd85f8ad746911b6e28. I extracted it and then ran heimdall like this:
Code:
heimdall flash --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --kernel zImage --modem modem.bin
And then it finished installing, and then it just was in a boot loop, going from the red verizon screen to the blue animation whatcha-ma-call-it. Anyway it wouldn't boot. So then I Odin'ed it and did it fine.
How do I heimdall eh03? did I miss an option or something?
Click to expand...
Click to collapse
You pretty much had it, the only thing missing was --recovery recovery.bin. If you were coming from an MTD ROM setup, you would also have likely needed to re-flash the bootloaders, which is honestly a job best left to ODIN, you really don't want to screw with those.
Heimdall can't use the "movinand.bin" file in the ODIN TAR that wipes/resets the DATA, PREINSTALL and FOTA partitions. To get the desired effect, you need to flash all that you can from Heimdall and then boot immediately into recovery and execute a wipe/factory reset to format the DATA partition. What most likely hung you up was the Dalvik-cache. Wiping the DATA partition removes this cache so when ODIN flashes movinand.bin it disappears.
Using ODIN for a full stock/factory reset operation is arguably the best way to go rather than using Heimdall. It's great for flashing most of the device, but the whole thing? ODIN it. On my Linux machine I use ODIN through an Oracle VirtualBox Windows XP guest OS. If you have/can find an XP product key, VirtualBox is free and works very well.
Hi,
Yesterday I bricked my SGSII when flashing Siyahkernel (see: http://forum.xda-developers.com/showthread.php?p=25204237&posted=1#post25204237)
There are many more users who bricked their device lately using Siyahkernel SiyahKernel v3.1rc6.
The problem is: returning to the stock Samsung rom is impossible because the /data cannot be written to.
I cannot flash the rom package because at the end the installation Odin hangs when the datafs is flashed, I can wait for an hour or so, and the installationproces does not proceed.
This is what Odin reports:
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> factoryfs.img
<ID:0/003> data.img
SO, when flashing data the installation stops. Same in CWM, when flashing a rom.
PIT - PHONE -BOOTLOADER -KERNEL: they all can be flashed. It is just in the last minute that /data cannot be written to. And afterwards, the SGSII is stuck on the boot logo.
Now my question: could the internal SD-card be repartioned of be formatted? Does anyone know how? That might solve the problem.
or do I just have to jtag the device? I cannot reset the counter either, because I cannot boot the rom.
I would be willing to pay for the solution, as I think many more users would be prepaired to do. I have counted at least 10 bricked devices ON XDA developers since saturday.
you need a pit file for repartition to work.
http://dl.dropbox.com/u/19319086/u1_02_20110310_emmc_EXT4.pit
Exactly the same problem for me... I tried flashing some stock roms but the phone always hangs on data.img with 3-file-fw (+ .pit file) or stays in bootloop with 1-file-fw.
The only way to enter recovery is rogue recovery (cf-root doesn't work for me) but internal storage can't be mounted.
Is there any known solution or I'll have to send my phone to Samsung?
Try it with the original USB cable
I'm trying to recover my device from a brick state by flashing the original firmware with heimdall, like this guide tells.
Because I want to bring everything back to the original state, I need these following files:
gt-p1000_mr.pit (partitioning)
modem.bin (modem)
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs (file-system or ROM?)
param.lfs
Sbl.bin
zImage (kernel)
On another guide in this same forum I found a link to this page, where it's supposed to be downloaded the firmware. However, I cannot get any of those files.
Moreover, I cannot find any place where these files can be downloaded.
Thanks in advance.
Hello,
i tryied to flash CM11 to my i9300 using one of the manual here but i ended up with phone going on boot loop when started(Shows only Samsung i9300 black/white logo in 3seconds loop). I only have an access to download mode
It says:
Product name: GT-i9300
Custom Binary download: Yes
Current Binary: Samsung Official
System Status: Custom
When i try to get the recovery mode installed again the Odin say
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> boot.img
<ID:0/028> NAND Write Start!!
And thats all. I supose i can connect through the USB while the odin shows the USB COM port and blue color.
Is my phone bricked or is there any way how to save it? Thank you for your advice
honzicek69 said:
Hello,
i tryied to flash CM11 to my i9300 using one of the manual here but i ended up with phone going on boot loop when started(Shows only Samsung i9300 black/white logo in 3seconds loop). I only have an access to download mode
It says:
Product name: GT-i9300
Custom Binary download: Yes
Current Binary: Samsung Official
System Status: Custom
When i try to get the recovery mode installed again the Odin say
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> boot.img
<ID:0/028> NAND Write Start!!
And thats all. I supose i can connect through the USB while the odin shows the USB COM port and blue color.
Is my phone bricked or is there any way how to save it? Thank you for your advice
Click to expand...
Click to collapse
If I'm not mistaken boot.img is the bootloader, not the recovery. Are you sure you can't get into recovery using the 3-button-combo? If not I would try flashing this recovery via ODIN. And then try to reboot into it using the combo. Then flash CM zip from there again.
Hi, im sure i cant get to recovery using 3 button combo. That gives me only the loop of "Samsung SIII" logo. The 3buttons combo work only for download mode.
Thats what i wrote, when im trying to flash the recovery via ODIN it gets stucked on the on the message <ID:0/028> NAND Write Start!! and nothing else happens. I tryed the 3.07 and 3.09 version of ODIN.
honzicek69 said:
Hi, im sure i cant get to recovery using 3 button combo. That gives me only the loop of "Samsung SIII" logo. The 3buttons combo work only for download mode.
Thats what i wrote, when im trying to flash the recovery via ODIN it gets stucked on the on the message <ID:0/028> NAND Write Start!! and nothing else happens. I tryed the 3.07 and 3.09 version of ODIN.
Click to expand...
Click to collapse
Ah, I'm sorry I misunderstood. I thought that was just a snippet of the log... Try flashing the recovery I provided and see if it flashes. If not, maybe you can flash stock firmware with pit file (new partition table). If nothing flashes, I have no further ideas.
Thanks, but ive already tryed to flash several recovery with the same results (got stucked on NAND write in ODIN), I downloaded stock rom but the package was without pit and other kinds of files (got stucked too on NAND write in ODIN). Its a ROM for TMZ (T-mobile Czech). Do you know where i can get the "full" package. Do i need to flash the pit and other files together with ROM?
You're seriously pottering a brick. The 'full package' contents 3 files, which you've to place in the right Odin-windows +repartition-check. These files are unofficial. Google for files and instruction.
rp158 said:
You're seriously pottering a brick. The 'full package' contents 3 files, which you've to place in the right Odin-windows +repartition-check. These files are unofficial. Google for files and instruction.
Click to expand...
Click to collapse
I could be mistaken but I believe the 3-part-roms (csc / pda / phone) is the "old style" how roms where put out by sammy. You would have to search but I would think you can also use the version you get from sammobile nowadays (one zip) and additionally just use the gt-i9300 pit file found somewhere here in the forums.
@Hawaiihemd: be shure, you're wrong.
honzicek69 said:
Thanks, but ive already tryed to flash several recovery with the same results (got stucked on NAND write in ODIN), I downloaded stock rom but the package was without pit and other kinds of files (got stucked too on NAND write in ODIN). Its a ROM for TMZ (T-mobile Czech). Do you know where i can get the "full" package. Do i need to flash the pit and other files together with ROM?
Click to expand...
Click to collapse
Try this >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << the pit file is in the 4.1.2 download and can be used on both versions.(Also try the 1.85 version of Odin) >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 <<
rp158 said:
@Hawaiihemd: be shure, you're wrong.
Click to expand...
Click to collapse
@rp158 Well, I think I only made a small error in my assumption.
Here are the details on the sammobile download. It seems to hold everything a "3-part-version" holds. I downloaded the file and a look at the .tar file inside the single .zip seems to confirm that.
This post suggests that flashing the .tar with the pit file should work.
I don't know because I haven't tried myself, maybe you have. Or I'm missing a piece of the puzzle. If so, maybe you could point me to it!?
@Hawaiihemd: If I look into the unzipped tar.md5-firmware, there are image-files. One for each partition. If I look into a 3part-zip-file, there are 3 tar.md5-files for each Odin-input-window. I tried only this soft method. The way, described in your cited post, I would only try as a last exit. The whole Odin-firmware-flashing is a black-box: noone knows, why&when during a normal flash a factory-reset is triggered or during repartition efs-data are restored. So, where the software finds the necessary repartition-data in the usual 1part-zip, is also unknown. Sorry, if I hurt you.
rp158 said:
@Hawaiihemd: If I look into the unzipped tar.md5-firmware, there are image-files. One for each partition. If I look into a 3part-zip-file, there are 3 tar.md5-files for each Odin-input-window. I tried only this soft method. The way, described in your cited post, I would only try as a last exit. The whole Odin-firmware-flashing is a black-box: noone knows, why&when during a normal flash a factory-reset is triggered or during repartition efs-data are restored. So, where the software finds the necessary repartition-data in the usual 1part-zip, is also unknown. Sorry, if I hurt you.
Click to expand...
Click to collapse
You didn't, don't worry. I was a little stumped maybe, but only because your answer was so terminal. Actually I only wanted to start a discussion about this, because you seemed to know more about said process than me and I always try to gain knowledge here to better help solving problems. I haven't been in this forum for long or into android for that matter...
That said, I have done the "3-files" version of this process with a .pit file thrice already on different gt-i9000s. Always worked flawlessly.
Looking at the ones in the post @tallman43 suggested, I found the contents of those 3 .tar.md5 files in summary(!) similar to the ones in the 1 .zip from sammobile. That's why I thought it could work in the first place.
One thing I'm sure of is that in both cases the repartition info is in the .pit file. If you choose none, the MMC should not be repartioned. If partitions are reformatted... that's another deal.
Concerning the efs partition, to/from where that info is stored/restored during repartitioning of the MMC... that's a very interesting question!
tallman43 said:
Try this >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << the pit file is in the 4.1.2 download and can be used on both versions.(Also try the 1.85 version of Odin) >> http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539 <<
Click to expand...
Click to collapse
Thank you very much for this hint. It worked well. I used the all files from KOR zip and 1.85 ODIN. Now i have the Korean version but at least i have something to start with and phone which works now.