Related
During the past 3 days I did mess up my device. I tried several Lagfix and Custom Rom. Then I decided to flash my device back to the stock one. Because I did try Voodoo lagfix but don't like the way these lagfix modify kernel. So, I backup my data >> Factory Reset >> Flash
I use exactly same method I successfully did with my device month ago. I flash with
1. Odin 3 v1.0 , Repartition
2. PIT 512
3. CODE_I9000DXJG4
4. MODEM_I9000DXJG4
5. CSC_I9000DXJG4
After odin finish what it does, I got an "Error in /cache/recovery/csc_sec.zip (Status 7)"
Then stuck at Boot Screen. I tried to wipe cache by Recovery Mode. But, It didn't work out.
Any clues? Thx in advance
Update
It works now.
Problem? Wrong PIT file, need to use 513 instead. <<<< WHAT A STUPID MISTAKE
Guess I should return my Com-Sci bachalor degree.
Sorry for wasting forum thread.
I tried to flash a stock rom but it was on bootloop.
So i went to odin on my pc and selected stock rom for PDA and clicked on start.
Now when i turn my phone on it says:
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again
Retry the odin flashing of the same stock rom. Next time if you get bootloops then go to recovery and just clear the cache and then reboot.
Make sure your downloaded zip is not corrupted.
Hello all,
I recieved a Galaxy Note for repair from a friend of mine. She says that the phone was working normally until it rebooted and then didnt get past the first Samsung Galaxy Note Logo.....she took it to samsung who said it was a faulty motherboard (hint: possible eMMC brick, though in India, thats their go-to response). The phone now shows a firmware upgrade failed sign (PHONE----------!-----------PC) telling me to plug it into Kies, which doesnt recognize it. It doesnt go into recovery mode at all but goes into download mode. I opened odin and flashed a stock gb rom with pit file(repartition ticked). The phone gets stuck at Set Partition. Have tried different Odins, different USB Cables, ticking diff. options in odin and god knows what else. How do i get this phone up and running? Is it the emmc brick bug? I think it is...
did you kill kies processes before using odin?
Yup. Done already....no change
if it gets stuck at repartition process, then its more than an eMMC brickbug. How its the phone right now?, can you go to recovery?. The best you can do: flash a safe kernel and then a cyannogenmod (or AOSP) rom, if it boots (probably you will get a lot of force closes), try to flash a jelly bean stock rom (without repartition) and then repartition it.
If still not work, the last option its jTag (riff box), it will repartition the whole phone.
Sorry my bad english
Hmmm, I'm not sure about that last part, but if I do it without repartition, it gets stuck at nand write of cache. Right now, it either goes into upgrade failed connect to kies sign or into download mode, both of which I'm guessing are the same
try uninstall and reInstall you samsung usb driver...
http://forum.xda-developers.com/showthread.php?t=961956
and try use other pc odin version..
try flash without repartition.
Checked. Same issue
xyancompgeek said:
Checked. Same issue
Click to expand...
Click to collapse
Odin stuck on?..
lets try flash kernel using pc odin
http://forum.xda-developers.com/showthread.php?t=1901191
Odin is stuck on this screen. Phone is in download mode. Cannot go into recovery.
You might need a usb jtag thing.maybe that will help in getting ur phone 8dentifiedby odin
Sent from my GT-N7000 using xda app-developers app
It is recognized by Odin, it just cant flash anything. One thing though, odin 3.07 atleast has the courtesy to tell me that it failed on set partition, odin 1.85 gets stuck at set partition.
what are you trying to do? you are only selecting the PIT file and nothing else in Odin. use the Original PIT not modified one with the rom file in PDA .
Nothing more is supposed to happen if only PIT file is added to odin. Donot use a custom PIT file till its confirmed a EMMC corruption.. use the original PIT file from Dr Ketans Guide in Original Dev Section
I fear i may have bricked my phone...
I was trying to create a custom ROM, set the ROM to wipe data. After i installed the ROM via CWM i got stuck in a boot loop.
I am able to boot into CWM as well as download mode.
Things I've tried:
1) Flashing stock ROM - still boot loop after doing this. It also asks to install an un-trusted package after flashing, not sure what this is.
2) Flash PARAM_I8190.tar.md5 - Still boot loop
3) Restore from backup - Gives me an error "Error while restoring /data!"
I've wiped data, cache, everything... but the boot loop persists.
Any assistance would be greatly appreciated.
have you tried installing pit file with odin
david32*2010 said:
have you tried installing pit file with odin
Click to expand...
Click to collapse
Hey, no i haven't tried that. I remember saving a pit file a while back but can't find it at the moment.
Is there any other way to get one?
Are they device specific?
Thanks,
scabs
there is one on here somewhere
david32*2010 said:
there is one on here somewhere
Click to expand...
Click to collapse
Yeah i found it thanks, do i have to flash the pit file along with the stock ROM?
with stock rom or kernal
Hmmm, okay I've flashed the PIT file at the same time as stock ROM, and still it's stuck in a loop
Okay this is sorted, i flashed stock recovery then re-flashed firmware.
Thanks David for you assistance.
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Its hard to tell what version it was on previously since recovery wont even boot, but from how its acting i'd say it was on LP and bricked for a KK flash, so you flashing NCE(Kitkat) is doing zilch. Seeing as there is no option for you to root, and im assuming you arent interested in that anyway, i would just take it to bestbuy or the att store and get them to reflash it, just say you got it off ebay and it was like that.
Sent from my Tw5ted SM-G900A using Tapatalk
I took the phone to BestBuy and the guy there flashed it with 5.0.1 with the same results. Boots to the Recovery Booting. . . . screen for about 30 seconds and then reboots. My daughter is taking it to an AT&T repair center to see if they have any better luck.
Have you tried flashing the boot image?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Boot image. Not sure which file you are talking about.
Could you give me a little more information or a link to the file?
Re: Softbricked AT&amp;amp;amp;amp;T Galaxy S5
If you have the oc4 update zip, in the zip should be a boot image, create an md5 tar file from it then flash in AP. If that doesn't work, you flashed a bad kernel and may have to use jtag to fully recover. Or bring it to a repair facility to have them do it.
My daughter took the phone to an AT&T repair center and they also could not successfully flash the phone. The only OC4 update i have found is the G900AUCU3BOC4_OneClick..exe update and I do not believe I can extract the boot image from that update. Is there another source of the OC4 update available where I could obtain the boot image.
Thanks for the help everyone.
I'll look for the DL link. But if they tried flashing it, and it didn't work. You may be SOL.
Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!
jebep said:
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!
Click to expand...
Click to collapse
How did you recover yours?