Related
Hi,
I wanted to try the Roto JME firmware, and I flashed it using the instructions at the dev forum. It seemed to work nice. Now I want to get back to stock firmware, and I am having a lot of trouble doing it.
I tried downloading the stock ROM at the sticky thread in the dev forum and decrypt it. It is not possible for me, I have tried four different computers with both Win XP and Win 7. All I get is "System.Runtime.InteropServices.COMException (0x80040154)".
Anyhow, I downloaded the file already decrypted at the first post in this thread: http://forum.xda-developers.com/showthread.php?t=881952&highlight=Official+ROMs.
I extracted the zip-file and in Odin v.1.70, I selected PDA = JME.tar which I got from the zip-file. I did not select re-partition. Odin says PASS! but the galaxy tab goes to a screen with a triangle with a exclamation mark in it, and it says "E:Can't mount /dev/block/stl10
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage is not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed. "
I tried the reboot option. The screen says "SAMSUNG" and nothing happens. I don't dare try the other options.
Please help, I don't know what to do!
Sounds like the internal sd is corrupted. Try a factory reset in recovery
Sent from my GT-P1000 using XDA App
That did not work. It still just shows the Samsung logo, it waits some time and then it vibrates, and it seems it does some kind of new boot atempt.
Please help!
No one can help me?
Please.
I think you need to get a copy of dbdata.rfs.tar and flash it using odin.
You can find a link to download it in the second post in this thred.
http://forum.xda-developers.com/showthread.php?t=875557
Thanks man, it worked!
Still not back to stock FW though. I wonder why no-one has written a howto on that.
No problem
I have been using jk5 firmware which allowed my at&t tab to make calls. However, I noticed after a while, that 90% of my use of the tab was wifi and certain apps would not download because the vendor thought my app was from a different country. None the less, I thought it was best for me to just return to the stock firmware. i called Samsung, told them I wanted stock firmware back on my tab, they gave me a prepaid ups label and I just shipped it off today for a 7 day turnaround.
What?! So you're saying there is no known procedure for getting back to stock, without calling samsung? This is ridiculous... So I have a tab wich is more or less ruined in regards to future official updates, i.e. Honeycomb and such?
I feel sad and fooled..
If you know what the original firmare was, you can download it at samfirmware.com
I think the rom you downloaded has the protected bootloader :-(
Doesn't restoring your rotobackup get back to stock?
Just have have to remove the root , unlock and any other changes after restore?
Can't you point me to a description on how to do that? I would be very grateful.
If you have a signed bootloader you cant go back to stock until the new fix is ready. Read all about it here
http://forum.xda-developers.com/showthread.php?t=888071
hello everyone..i have a problem which i hope someone can find a solution.
I had a Tab with the following FW: PDA: P1000XWJJ3-PHONE: P1000XXJID-CSC: P1000OXXJJ2
I just wanted to flash it with an arabic support fw, so i used P1000JVJJ1 with PIT 816, REPARTITION ENABLED in odin 3 (no phone or CSC selected). That was it, and the tab rebooted into recovery mode error: E: Cant't mount /dev/block/stl10 (Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
so from here i tried to reboot...wipe data/factory reset, but nothing helps, it just boots till the samsung logo and then stuck with repetitive vibrations.
i also tried to flash back the P1000OXXJJ2 with no repartition enabled, but the same happened. finally i downloaded the P1000XWJJ3 from samfirmware thinking it might bring it back to original, but it was worst..Odin failed. Not to keep it in the worst condition, i reflashed it with P1000OXXJJ2, and now am back stuck at the samsung with vibrations. If anyone can help please. I dont care about P1000OXXJJ2 firmware to be installed. i just need the Tab to work again.
Thank You
If it boots at all, then it's not bricked.
Go get Rotohammers JMI firmware and flash that with the "add_hidden.pit" file as partition.
Credit to you for posting in the right section unlike most "my tab is bricked" posts which end up in the dev forum.
just to re-confirm what knightnz said, "if it boots at all, it's not bricked" ..and, i speak from the voice of experience. LOL ....and, hey, i'm not laughing at you, i'm just thinking back on the Days that i spent thinking mine was gone for sure.
just follow the directions given, and, you may/will be pleasantly surprised!
I did a similar thing, and Rotos files saved me. Just do what knightnz said to do, and you should be good to go. Besides, I am under the impression that the tab is very hard to brick. However, don't quote me on that.
deniro0311 said:
I did a similar thing, and Rotos files saved me. Just do what knightnz said to do, and you should be good to go. Besides, I am under the impression that the tab is very hard to brick. However, don't quote me on that.
Click to expand...
Click to collapse
It would be even harder, if tab has recovery partition like other android devices.. But we have no recovery partition as it is binded to kernel in Tab
thanks for your quick reply, really appreciate it. meanwhile, am downloading the Roto-JMI-Full-v2, but just a quick question, do i need to also flash the pda and modem or just the PDA is enough? note that in all my previous flashing i have not flashed the modem. Thanks again
Mission accomplished
Thanks a million guys, u were really helpful. I have flashed my tab with the JMI firmware alone and everything went fine except that the modem was not working (*#1234# Modem: Unknown), so i searched some forums and eventually i used the JME add-on modem which did the job.
so now ..for next time, if i needed to add some language support to my tab..how can i do that? Thank you all
hey
Could someone please please help me get my phone (sm-n9005) Back on. My phone has been off for the last 12 hours try to figure out how to restore back to stock. i am literrally pulling my hair out.
I keep getting this error message when restoring through odin SW REV CHECK FAIL: [ABOOT]FUSED 2 > BINARY 1
Please could someone tell me a fix for this i would really really really appreciate it.
Thank you
BUMP anyone pls
Are you trying to downgrade?
Little more info would probably help
SM-N9005 via Tapatalk 2
sewe said:
Are you trying to downgrade?
Little more info would probably help
SM-N9005 via Tapatalk 2
Click to expand...
Click to collapse
thanks for the reply
i just simply want to get the phone working
i orignally tried to flash from TGY hong kong firmware to BTU uk firmware, but that didnt work so i have tried to retry flashing the hong kong firmware
but odin gives me the [aboot] fused 2 > Binary 1 error
i tried doing emergency repair from kies too still gives me the same error
DjeMBeY said:
SW REV. CHECK FAIL : fused:2, Binary: 1 is when you try to downgrade aboot.mbn (bootloader) or try to flash incorrect system/csc etc..
If you get this message , just reboot in Download mode and flash correct package..
Click to expand...
Click to collapse
SM-N9005 via Tapatalk 2
sewe said:
SM-N9005 via Tapatalk 2
Click to expand...
Click to collapse
I am getting the same error when I try to flash back to the stock ROM and unroot my Verizon Note 3. I made the mistake of accepting the OTA update on my rooted device, did not have custom ROM or anything. The installation seemed to go okay but apparently wiped out the root. Everything was working fine but my root apps so I thought the device was essentially stock. I tried the Dela Vega Root method and it failed several attempts. So I tried flashing a stock ROM in Odin and I get the message you got. I tried downloading the stock ROM on two different occasions in case it was corrupted but still not working. Is my device bricked or is there something I can do? Any help would be appreciated.
Got my phone unbricked by following the directions in this thread. Installed pit file and my phone rebooted! Thank G-d! Was able to root with Kingo. De la vega root does not work with the firmware upgrade.
Back to life
I had same issue and restored it . Follow this : http://forum.xda-developers.com/showthread.php?t=2511880
Need Help
I need help too
Im having the same problem i have been trying for like 2 days now.
I tried to upgrade my phone to 4.4.2 but it didnt work and when i tried to flash back my old Rom im getting the same thing
"SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
need help want to fix my phone.
i tried three different roms and Odin came back with different errors. but errors the less.:crying:
Help:crying::crying::crying:
StarBoy007 said:
I need help too
Im having the same problem i have been trying for like 2 days now.
I tried to upgrade my phone to 4.4.2 but it didnt work and when i tried to flash back my old Rom im getting the same thing
"SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
need help want to fix my phone.
i tried three different roms and Odin came back with different errors. but errors the less.:crying:
Help:crying::crying::crying:
Click to expand...
Click to collapse
You cannot go back or restore an old ROM, you have upgraded to 4.4.2 with NA6 Bootloader, so you can ONLY Run NA6 Bootloader which means you are stuck on KitKat now..
Reflash Kitkat 4.4.2 Stock and you're good to go :good:
help
radicalisto said:
You cannot go back or restore an old ROM, you have upgraded to 4.4.2 with NA6 Bootloader, so you can ONLY Run NA6 Bootloader which means you are stuck on KitKat now..
Reflash Kitkat 4.4.2 Stock and you're good to go :good:
Click to expand...
Click to collapse
THanksfor the replay but the tjing is when i was installing kitkat Odin came up with an error and it failed so the upgrade didn't go through. So does it mean I'm stuck with kitkat. The thing is I tried 2 other kitkat and none of them worked. So when I tried to go back to my old ROM Odin always coming up. with errors. "FAIL (Auth)"
What does that mean..... :crying:
StarBoy007 said:
THanksfor the replay but the tjing is when i was installing kitkat Odin came up with an error and it failed so the upgrade didn't go through. So does it mean I'm stuck with kitkat. The thing is I tried 2 other kitkat and none of them worked. So when I tried to go back to my old ROM Odin always coming up. with errors. "FAIL (Auth)"
What does that mean..... :crying:
Click to expand...
Click to collapse
Yeah you'll have upgraded cause it'll have installed the Bootloader then tried the ROM before the failure. -
What model/region are you using ? Is it a HK note?
help
radicalisto said:
Yeah you'll have upgraded cause it'll have installed the Bootloader then tried the ROM before the failure. -
What model/region are you using ? Is it a HK note?
Click to expand...
Click to collapse
Ok no problem I understand
But I tried installing 4.4.2
But no luck it's not updating. Odin giving me errors every time
Do you have any idear when i can get a rom that can work for me
Plz
well i am using Hong Kong
1 Minute I will edit and give you link to fix your device :good:
Follow exactly these steps (I've fixed the second link.). Update progress.
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
Thanks to @rinuvimal posting here
I've updated working links here:
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://d-h.st/gb3
Download Sweet Rom and place it in ExtSDcard http://forum.xda-developers.com/showthread.php?t=2487425
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
rinuvimal said:
I've updated working links here:
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://d-h.st/gb3
Download Sweet Rom and place it in ExtSDcard http://forum.xda-developers.com/showthread.php?t=2487425
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
Click to expand...
Click to collapse
@StarBoy007, after you try this out, please update your handset details and whether it worked for you. Cheers. Will help someone else!
thanks
rinuvimal said:
@StarBoy007, after you try this out, please update your handset details and whether it worked for you. Cheers. Will help someone else!
Click to expand...
Click to collapse
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:
StarBoy007 said:
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Try using PIT file, then re-flashing SweetROM, JackyawayROM or FlexKAT ROM
StarBoy007 said:
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Don't worry, as long as you can get into recovery and download modes, there will be a solution, its only a matter of time before we zone in on a solution.
What CSC region phone do you have? Dial *#1234# and check what the CSC code is. Also how much storage do you have on your phone 16Gb or 32GB?
R
thanks
rinuvimal said:
Don't worry, as long as you can get into recovery and download modes, there will be a solution, its only a matter of time before we zone in on a solution.
What CSC region phone do you have? Dial *#1234# and check what the CSC code is. Also how much storage do you have on your phone 16Gb or 32GB?
R
Click to expand...
Click to collapse
well thanks..
i know that the problem is not that big anymore its just getting the right rom. well i cant dial anything so i cant check for the CSC but im wondering is there any other way to get the CSC region well the phone was bought officially in hong kong.
do you have links to the other roms you suggested earlyer that would be helpful.
thanks again.
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line
UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:
Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
How is that going to take away the udc start?
I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.
Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:
Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.
ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.
re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.
Hi guys,
I bought my wife a G900I, flashed it to CM12 5.0.1 and had it working no problem for a week. 2 days ago after watching a FB video the phone rebooted and has seen been stuck in the Boot Loop. Nothing, even the stock firmware seems to want to install.
Tried the following:
philz_touch_6.26.6-klte.tar.md5
openrecovery-twrp-2.8.4.0-klte
CF-Auto-Root-klte-kltedv-smg900i.tar.md5
CWM recovery
Even PIT: SM-G900I_16Gb.pit
Did full WIPE, CACHE, Re-Format via TWRP
Tried the following Stock Roms:
G900IDVU1ANK1_G900ITEL1ANJ1_G900IDVU1ANJ1_HOME.tar.md5
G900IDVU1AND2_G900ITEL1AND2_G900IDVU1AND2_HOME.tar.md5
G900IDVU1ANK1_G900ITEL1ANJ1_G900IDVU1ANJ1_HOME.tar.md5
G900IDVU1ANK1_G900IVAU1ANJ2_G900IDVU1ANJ1_HOME.tar.md5
After flashing via Odin (tried 2x original cables, 3x Windows PCs)
I get the following Errors (see attached). Sceenshot is from Odin 3.07, but I tried 1.85, 3.07 and 3.09 on 3 different computers with 2x different original cables plugged into USB 2.0 at the back of the motherboard - same results, no matter which Stock ROM I choose.
Whats interesting, is that after a few boot loops, you get a Samsung Logo and a sound, but only intermittently. One time it even managed booting into the new 4.2.2 Stock Setup Wizard, but within a second the phone just reboots and keeps boot-looping.
I'm running out of ideas and I thing I tried everything possible.
Any ideas?
1) have you tried Kies?
2) are your firewall and anti virus turned off on the PCs?
3) XP, Vista and 7 have a better track record with Odin than 8.
4) have you tried EVERY USB port with EVERY PC (it *can* make a difference)
5) are you running Odin as an administrator?
6) leave the .pit files well alone for now. If a pit flash goes wrong, you have a totally unrecoverable brick.
Sent from my rooted Kn0x0 SM-G900F S5
keithross39 said:
1) have you tried Kies?
2) are your firewall and anti virus turned off on the PCs?
3) XP, Vista and 7 have a better track record with Odin than 8.
4) have you tried EVERY USB port with EVERY PC (it *can* make a difference)
5) are you running Odin as an administrator?
6) leave the .pit files well alone for now. If a pit flash goes wrong, you have a totally unrecoverable brick.
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Hey keithross39,
1) Yes, I have tried Kies. Updated to latest version. It stays on "Connecting" - I can only get the phone in Download mode since I cannot successfully flash stock via Odin.
I also tried Emergency Firmware recovery in Kies, but I don't have the code. Also tried "Firmware Upgrade and Initialisation" When I put in my model (All Upper Case) and serial number I get an error: 'SM-G900I' Does not support initialising
2) All firewalls are switched off (stopped via windows services), Anti-Virus disabled.
3) All 3 computers that I tried (with 3x different ORIGINAL Samsung cables) are Windows 7 machines
4) I tried ALL USB2.0 ports, front and back of the PCs
5) I run Odin as Administrator
Basically, I can successfully flash various roots and recoveries, be it TWRP, PHILZ, CF-Auto-Root. I can even succesfully wipe and install the CM12 + GAPPS. The end result is that I get a boot loop. If you leave the phone for 20 minutes, every once in a while it actually boots, almost to the GUI, but then resets and gets stuck in boot loops again.
Another interesting observation is that when I get into TWRP and try Wipe and Format, I get all kinds of Read/Write errors.. (see screenshots)
I've been running custom roms on my Galaxy S, S2 and S4 for years now, and have been though everything, never managed to brick any phones yet. This time I am still technically in 'Soft Brick', but after trying so many different Stock Roms via Odin I am starting to suspect maybe faulty hardware? I mean when I first got it, I rooted it and flashed CM12 via PHILZ Recovery. It ran beautifully for just over a week. Then I started getting boot loops. And these "add/remove storage" errors in TWRP are making me suspect hardware..
Hmm.......sounds like you're up against it there fella......The only thing I can suggest is to persevere with what you are trying........Most folks here know that if you are having problems Odin flashing, perseverance is the only thing that works. Odin may not flash on the first X number of flashes, but the time after, it will.........
I still maintain that you should stay away from .pit flashes though......They are strictly "last chance saloon" flashes........
Sent from my rooted Kn0x0 SM-G900F S5
artem1 said:
Hey keithross39,
1) Yes, I have tried Kies. Updated to latest version. It stays on "Connecting" - I can only get the phone in Download mode since I cannot successfully flash stock via Odin.
I also tried Emergency Firmware recovery in Kies, but I don't have the code. Also tried "Firmware Upgrade and Initialisation" When I put in my model (All Upper Case) and serial number I get an error: 'SM-G900I' Does not support initialising View attachment 3116279
2) All firewalls are switched off (stopped via windows services), Anti-Virus disabled.
3) All 3 computers that I tried (with 3x different ORIGINAL Samsung cables) are Windows 7 machines
4) I tried ALL USB2.0 ports, front and back of the PCs
5) I run Odin as Administrator
Basically, I can successfully flash various roots and recoveries, be it TWRP, PHILZ, CF-Auto-Root. I can even succesfully wipe and install the CM12 + GAPPS. The end result is that I get a boot loop. If you leave the phone for 20 minutes, every once in a while it actually boots, almost to the GUI, but then resets and gets stuck in boot loops again.
Another interesting observation is that when I get into TWRP and try Wipe and Format, I get all kinds of Read/Write errors.. (see screenshots)
View attachment 3116299
View attachment 3116300
I've been running custom roms on my Galaxy S, S2 and S4 for years now, and have been though everything, never managed to brick any phones yet. This time I am still technically in 'Soft Brick', but after trying so many different Stock Roms via Odin I am starting to suspect maybe faulty hardware? I mean when I first got it, I rooted it and flashed CM12 via PHILZ Recovery. It ran beautifully for just over a week. Then I started getting boot loops. And these "add/remove storage" errors in TWRP are making me suspect hardware..
Click to expand...
Click to collapse
Usually that error in odin means that there is a problem with the partition of the memory , try to flash your original firmware including PIT file for your device.
Try to find a 3 part or test firmware for your device. These firmwares fully wipe (and I think repartition) your phone rather than simply overwriting what's already there........
Sent from my rooted Kn0x0 SM-G900F S5
Where do you find 3 part or test firmware
---------- Post added at 12:31 PM ---------- Previous post was at 11:58 AM ----------
keithross39 said:
Try to find a 3 part or test firmware for your device. These firmwares fully wipe (and I think repartition) your phone rather than simply overwriting what's already there........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Isn't all three included in the Odin Flash-able Full Stock
Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5
keithross39 said:
Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
I cant seem to find any 3 part firmware for T-Mobile anywhere
For 3 part I don't know however sometimes you need just pit file, try asking here: http://forum.xda-developers.com/showthread.php?t=2737448, there is a collection of pit for galaxy s5
Don't look for a "branded" 3 part firmware.....they're generic unbranded (but device specific)......
And *please* leave the pit flashing as a FINAL resort........
Why will a pit flash work when firmware flashes don't.......and if a pit flash fails part way through, nothing short of motherboard replacement is going to unbrick your phone........
Sent from my rooted Kn0x0 SM-G900F S5
qrono said:
For 3 part I don't know however sometimes you need just pit file, try asking here: http://forum.xda-developers.com/showthread.php?t=2737448, there is a collection of pit for galaxy s5
Click to expand...
Click to collapse
Thanks everyone for posting your suggestions. Latest developments:
- Paid for the Raipidgator Premium DL services 'cause I was getting sick of 8-9 hour long stock downloads
- Downloaded 2x more Stock Firmwares for SM-G900I from the XDA and samsung-updates (all official stock roms)
- Downloaded PIT file from the link above. Shame I could only find 1x PIT for the 900I. Anyways, my understanding of PIT is that its just an XML partition table
Tried PIT + Official ROM at the same time - same result (
My buddy recons my Internal Flash is corrupt. I think so too. Evidence is that I can install the CM12 which is 200 odd Mbs, but I can't install the official ROM via Odin and its 1.5Gb... Also I get read/write partition errors in TWRP when doing wipe+format.
What do you guys recon?
R2D2 is sick when PITTIN
R2D2 is sick when PITTIN
artem1 said:
Thanks everyone for posting your suggestions. Latest developments:
- Paid for the Raipidgator Premium DL services 'cause I was getting sick of 8-9 hour long stock downloads
- Downloaded 2x more Stock Firmwares for SM-G900I from the XDA and samsung-updates (all official stock roms)
- Downloaded PIT file from the link above. Shame I could only find 1x PIT for the 900I. Anyways, my understanding of PIT is that its just an XML partition table
Tried PIT + Official ROM at the same time - same result (
View attachment 3117831
My buddy recons my Internal Flash is corrupt. I think so too. Evidence is that I can install the CM12 which is 200 odd Mbs, but I can't install the official ROM via Odin and its 1.5Gb... Also I get read/write partition errors in TWRP when doing wipe+format.
What do you guys recon?
Click to expand...
Click to collapse
keithross39 said:
Yes......but in a "finalized" form.......
As I said in my post before, the regular "end user" firmware flashes on top of or overwrites what's already on the phone.....The 3 part test firmware wipes the old before installing the new......
And as for finding it, sammobile and samsung firmwares are extremely UNLIKELY to host it......Unfortunately they're not readily available.......You're just going to have to trust your luck to Google or sites like XDA.........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
LATEST SET OF ODIN:
Successfully flashed G900IZTU1BOA1_G900IZZT1BOA1_G900IZTU1BOA1_HOME.tar
See Picture:
Interesting that now Odin has 2x sets of COM ports, as if some how PIT flashing did something to the boot loader? Anyways, after successful Odin (finally) I have the same problem - continuous reboots. Sometimes I see the Samung logo, music plays, but it keeps on rebooting..
Any tips how I can find the "finalized" 3 part firmware for SM-G900I? All I seem to find is the .tar 1x piece firmware files (including the one that flashed successfully above..) Would these be the 3-piece firmwares?
http://www.galaxys5update.com/austr...1anc6-original-4-4-2-firmware-restore-unroot/
keithross39 said:
Don't look for a "branded" 3 part firmware.....they're generic unbranded (but device specific)......
And *please* leave the pit flashing as a FINAL resort........
Why will a pit flash work when firmware flashes don't.......and if a pit flash fails part way through, nothing short of motherboard replacement is going to unbrick your phone........
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
I flashed pit for my phone many times and my phone still stuck at the first boot screen. It still can get to download mode and flash-able.
I am starting to think it is possible for a phone to be flash able successfully in Odin, but still be hard bricked.
Hard brick = hardware issue......usually unrecoverable
Soft brick = software issue.......*possibly* recoverable.
If your device was hard bricked, it would show NO signs of life whatsoever, no matter what you did to it......
Sent from my rooted Kn0x0 SM-G900F S5
have you tried to start in recovery and wipe data/cache?
keithross39 said:
Hard brick = hardware issue......usually unrecoverable
Soft brick = software issue.......*possibly* recoverable.
If your device was hard bricked, it would show NO signs of life whatsoever, no matter what you did to it......
Sent from my rooted Kn0x0 SM-G900F S5
Click to expand...
Click to collapse
So its possible to be permanently soft brick and unfix able despite odin being able to flash with no errors?
Ok....So here's a simplification of it........
1) ABACADAE_FA
2) ABACADAEaFA
Imagine number 1 as a firmware you are trying to flash.
Imagine number 2 as a firmware already installed on your device.
Imagine the lower case 'a' in number 2 is a bit of corrupt data that is causing your phone difficulties.
When you flash a firmware with Odin, you are OVERWRITING or directly replacing the software on your device, so the data string that goes ABACADAE and FA will be replaced.......The data called 'a' will be left untouched.....and will still be an issue after the flash.
The TEST firmware is different and does things differently. It's designed to test the firmware on a 'pristine' device, one that has ABSOLUTELY NO TRACE of a previous OS remaining that might interact with it and cause issues. To make sure this happens, the test firmware will COMPLETELY erase EVERY trace of a pre-existing OS during the flash thereby removing any trace of corrupt data (the lower case 'a' in my example).
The bottom line is, if you REALLY can't recover your phone successfully with Odin, and a test firmware for your device hasn't been 'leaked', you have 2 options.....
1) get your device JTAG-ged.
2) send it to Samsung for an out of warranty repair.......
Sent from my rooted Kn0x0 SM-G900F S5
@artem1 just had a look at your firmwares link.......at a guess, without attempting to download, I'd say that these AREN'T test firmwares.....but single file, finalised, carrier branded, official firmwares......sorry fella, just going to have to 'dig deeper'........
Just bear in mind though.........A device has to have it's 'test' firmware unofficially 'leaked' and unless that's the case for your device, you may not find it.........
Sent from my rooted Kn0x0 SM-G900F S5