[Q] (for me) unrecoverable softbrick - Galaxy Note 3 Q&A, Help & Troubleshooting

Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Hardware involved:
Galaxy Note 3 N9005 that was running 4.4.2 (bought unlocked)
iMac with Yosemite and Parallels with Ubuntu and Windows 10 with Heimdall and Odin 3.09 installed
What I set out to do: root & install clockworkmod recovery with the ultimate goal to install Linux on Android. I had my previous Note 2 and LG P990 rooted too, so I was not entirely new to the procedure.
What I "achieved": Heimdall would not work at all due to a problem that apparently affects all Samsung 4.4.2 devices. So I got Parallels on my Mac and installed Windows 10 Technical Preview to run Odin. After several attempts I finally managed to got Odin to say "PASS" on the CF Auto-Root procedure. However, the phone would not boot anymore and always return to it's ODIN state. But I also succeeded to get Clockworkmod installed.
With that I installed Cyanogen, thinking to be able to get around the booting problem. I wasn't. Now when booting Cyanogen, I get a message that encryption was unsuccesful and the device needs to be restored.
I would like to comply and downloaded the stock files for restoring through Odin, but now even with the device in the proper ODIN download state, the phone is no longer recognized by the Software. Tried about a hundred times now with reboot etc. and nothing seems to work. Even KIES does note recognize the phone anymore.
I can enter CWM and Odin modes just fine. I just can't boot and I can't get it recognized by my Mac anymore. My best guess is I unintentionally screwed up the partition table / PIT file and now I can't restore it anymore.
I am at the end of the rope here and getting desperate, any suggestions (preferably step by step) would be most welcome!

psearcher said:
Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Click to expand...
Click to collapse
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.

Joku1981 said:
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.
Click to expand...
Click to collapse
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?

psearcher said:
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?
Click to expand...
Click to collapse
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.

Joku1981 said:
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.
Click to expand...
Click to collapse
Hi there Joku!
Just tried the Polish Lollipop Firmware and it still keeps displaying the "Encryption failed" error. It looks like it does not matter which file I flash, it will keep showing the same error.
Like I said, I believe I somehow broke the PIT file of the phone. Any ideas how to fix this?
Regards,
Rene

Try this pit file.
https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT VFG-UK-MSM8974.zip/
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005

Question solved!
DeuXGod said:
Try this pit file.
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005
Click to expand...
Click to collapse
Thanks DeuXGod, but by now I more or less stumbled on the solution by trial and error. I'll post it here, hoping that somebody may benefit from my endeavours in the future. As a n00b I can't post links though. Sorry for that.
I do not know if all the steps are necessary or correct, but in the end they did lead me back to a working device. :fingers-crossed:
After trying a few PIT files here in the forums, the problems did not go away. Some of them would lead to a phone that just got stuck at the "Samsung" screen and would not fully boot up.
So I got the idea to flash back the "old" Dutch 4.4.2 ROM, which I downloaded from Sammobile and flashed in ODIN. After booting it showed a bit of a different error message, saying the file system was corrupted
I googled for this and stumbled on a small ZIP file that is supposed to fix "cannot mount DATA / EFS errors". I loaded this on my SDXC.
Flashed aforementioned ZIP file through the recovery from the SDXC.
After rebooting it still showed the same error, so I got back to recovery, did a factory reset and a cache wipe.
Another reboot and much to my surprise (and great relief) the phone booted up normally again!
From there I thought that if this worked, the Polish 5.0 should work too. I flashed it. Flashed CF Auto Root after that and everything seems to be working fine!
I set everything up and the phone is now restoring the apps etc. So far looking very good!

Related

4.3 downgrade -> 4.2.2 epic fal

I just did legend fail.
Been on stock MK2 (MF3 sideloaded to upgrade MK2), then i decided to go back to 4.2.2 stock since i really did not like the 4.3, did not make any research, so i odin the MF3 files and tried to flaash, but got an error in first 5 sec. Now every time i switch on the phone its saying i have to make upgrade through KIES, what sounds work w/o luck.
I know we dont have 4.3 odin files yet and not sure we will have them, but is there any way still to get this device to work ? Or its absolutely broke ?
Would appriciate any help ty
If Samsung experience at best buy has the new update, you could try to see if they could help. If not, I feel you are in for a wait.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I did the same thing on my SGH-I337M. Kies was a waste of time. I used Odin, downloaded the newest 4,3 firmware and reflashed it in update bootloader section only. Took about 8 minutes but saved my phone. Knox won't let us downgrade so we are sad at the moment.
can any1 please share this file bootloader of MK2 so i can flash it throu odin to make the device to work, would appriciate any further info or help ty. w/o phone for 3 days already
HiTideBlastoise said:
If Samsung experience at best buy has the new update, you could try to see if they could help. If not, I feel you are in for a wait.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I know you used the xda app so you probably didn't notice the OP is located in Athens, Greece. So no dice
Yeap got the phone from my bro he is leaving in Rochester, if i would know that he sent me At&T and its as block as it is now, i would spent money to buy it from Amazon Germany, internatioonal fully functional =) but my luck
Since we got the 4.3 update closing our download funtion in phone, will we be able to flash through odin the stock 4.3 MK2 to re-stock bricked sgs4 ? like you can do with MF3?
I am asking since currently i am w/o phone and waiting for someone to post the stock MK2, but will that for sure make it work normal excluding its blocked downlaod etc. ? just curious
Same thing happened to me.. I worked for hours and finally just tried flashing the I337 PIT file thru Odin in the Pit option.. It said failed but I pulled the battery and rebooted into recovery then restarted.. Google for the pit file.... I have the full zip MK2 file but you have to have the MD5 files for Odin
Sent from my GT-N8013 using xda app-developers
If i will flash PIT file i will be able to enter recovery ? since know the only option i have is download mode, and kies recovery (what is useless)
When u flash PIT with fail and enter recovery what did you do next ? the device booted normally ?
Where can i find this PIT ?
Ty for the help
So let me ask this so I do not make a similar mistake. Yesterday I used odin to go to mf3 then sideloaded mj9,. If I have the file for mk2. Can I just side load it even though im on mj9?
nomikSqash said:
If i will flash PIT file i will be able to enter recovery ? since know the only option i have is download mode, and kies recovery (what is useless)
When u flash PIT with fail and enter recovery what did you do next ? the device booted normally ?
Where can i find this PIT ?
Ty for the help
Click to expand...
Click to collapse
When I flashed the PIT file, I just took a chance and tried to boot it, and it allowed me to boot normally. It also allowed me to enter recovery
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
blackguy101 said:
So let me ask this so I do not make a similar mistake. Yesterday I used odin to go to mf3 then sideloaded mj9,. If I have the file for mk2. Can I just side load it even though im on mj9?
Click to expand...
Click to collapse
Yes, you should be able to sideload or flash the zip through recovery.. With all these fails at updates, I wish I would have stayed at what I had and not messed with it..lol.. It seems nothing is guaranteed and it's always a risky chance when you flash something..
I decided to update to 4.3 and didnt like it so i stock flash 4.2 back via odin. flash said "pass" but now i have knox on recovery. Im guessing i have the new bootloader. 4.2 flash on but with errors like wifi wont toggle on & on every reboot i get an erro "kernel seandroid is not reonforsing" or something like that...so now im stock on 4.3 :/
blackguy101 said:
So let me ask this so I do not make a similar mistake. Yesterday I used odin to go to mf3 then sideloaded mj9,. If I have the file for mk2. Can I just side load it even though im on mj9?
Click to expand...
Click to collapse
The mistake i made was to go downgrade from 4.3 to 4.2.2 do not make it since we do not have files for ODIN flash 4.3.
There is full 700 mb file witch you can easily sideload, if u get any error just go back to odin to flash stock MF3 and then sideload MK2, worked for me w/o problem but pls do not downgrade !
If i were you i would not go 4.3, TW is much more bugged for me, and phone feels way different thats why i wanted to go back to 4.2.2
nerdyblonde said:
When I flashed the PIT file, I just took a chance and tried to boot it, and it allowed me to boot normally. It also allowed me to enter recovery
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
Did not get it, i need to get the PIT file, but when can i get it to flash through ODIN if we do not have files for odin yet ?
Click to expand...
Click to collapse
I was able to downgrade... kinda..
I had my own epic fail when bell's update came out.
Flashed stock/counter reset.
Got OTA update no prob.
Rooted - Deleted too much bloat... (didnt backup) MY EPIC MISTAKE.
Thought "oh ill just start again"
Odin Back to 4.2.2 FAIL!!!
Stuck.. kinda
found someone with the international version in the same issue that odin flashed files from another carrier and was able to fix his situation...
so i went to http://www.sammobile.com/firmwares/ and downloaded the NEWEST date 4.2.2 rom for my 337m, which happened to be Dominican Republic carrier.
Flashed the DR version successfully in odin, and had no sound, no mic, no wifi.
I was then able to Odin flash 4.2.2 from bell... but still had no sound, no mic, no wifi....
the only real fix was LUCKILY within 24 hours of the OTA release, the odin file was posted to sammobile and saved my ass... all works now.
Played with the 4.3 update for a couple hours, then went back to 4.4 builds... LOL
At least i got to use my captivate again for a few calls for a day. that was nice.
Really have no idea how i an fix this w/o odin files.
umm you cant.
Problems solved, any1 who will have the same issue as me:
Had MK2 update installed and wanted to downgrade to 4.2.2 and failed to kies update, just flash the attached filed, it will fail you in download mode, but after 2-3 tried, just restart the device, and it will normally boot into 4.3 =)
Ty for all the help, and info best regards !
nomikSqash said:
Problems solved, any1 who will have the same issue as me:
Had MK2 update installed and wanted to downgrade to 4.2.2 and failed to kies update, just flash the attached filed, it will fail you in download mode, but after 2-3 tried, just restart the device, and it will normally boot into 4.3 =)
Ty for all the help, and info best regards !
Click to expand...
Click to collapse
That's the file I had used before too.. I posted it on another guys post.. Glad it worked for you
http://forum.xda-developers.com/showthread.php?p=47586777
This is the complete guide on how to flash back from 4.2.2. Even that 16 gig pit file won't even work on some peoples phone. Use this guide and it will help you get back to 4.3. First mj9 than you can sideload mk2.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
nomikSqash said:
Problems solved, any1 who will have the same issue as me:
Had MK2 update installed and wanted to downgrade to 4.2.2 and failed to kies update, just flash the attached filed, it will fail you in download mode, but after 2-3 tried, just restart the device, and it will normally boot into 4.3 =)
Ty for all the help, and info best regards !
Click to expand...
Click to collapse
That file I gave you won't help if your stuck with incomplete flashes. For people who were experiencing the problem I had use that guide posted by gtj0 and you'll get your phone back to normal.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

[Q] DOWNLOAD mode N9005 - 4.4.2 - UDC START?

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.

stuck in odin mode after failed root

Can someone please help me. I attempted to root my wifes i9505 (already done my own with no issues). It failed during flashing cf-root (CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
I had no choice but to reboot the phone and now it's stuck in odin mode - Firmware upgrade encountered an issue! Kies won't connect to the phone for the recovery either? What should I do, please help!!!
EDIT: Doesn't matter, tried a different usb lead and re-tried the process and it's working now. Very strange, could have only been the lead I was using
tim132 said:
mode - Firmware upgrade encountered an issue! Kies won't connect to the phone for the recovery either? What should I do, please help!!!
EDIT: Doesn't matter, tried a different usb lead and re-tried the process and it's working now. Very strange, could have only been the lead I was using
Click to expand...
Click to collapse
Mate, I have 3 (THREE) sammy's galaxy phones [connection cables], I had two wife and, to be honest, form all of that, only one wrks without problems
spamtrash said:
Mate, I have 3 (THREE) sammy's galaxy phones [connection cables], I had two wife and, to be honest, form all of that, only one wrks without problems
Click to expand...
Click to collapse
thanks a lot.
re: try this.
tim132 said:
Can someone please help me. I attempted to root my wifes i9505 (already done my own with no issues). It failed during flashing cf-root (CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5)
I had no choice but to reboot the phone and now it's stuck in odin mode - Firmware upgrade encountered an issue! Kies won't connect to the phone for the recovery either? What should I do, please help!!!
EDIT: Doesn't matter, tried a different usb lead and re-tried the process and it's working now. Very strange, could have only been the lead I was using
Click to expand...
Click to collapse
Download the cf-auto-root again, just in case it was a bad download.
Then power off the phone then power it back on into download mode
and close Odin, re-open odin and place the cf-auto root.tar file into
the PDA slot in Odin.
Then plug usb cable into the computer and phone and be sure that the [COM:xx] lights up & start odin.
Chances are good it will flash without errors.
Good luck!
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
error post
Yeah thanks. I've flashed my phones ever since having the s2 and never had a problem as I research properly before doing anything.
I used the same downloaded cf-root for my own phone so knew that wasn't the problem. I obviously used a different lead for flashing my own phone.
Once I used the same lead on my wifes phone it worked fine. Just had to put the phone back into download mode and run through the odin process again.
I guess if that hadn't have worked I would have to flash a new rom using odin. Wouldn't have been ideal, I hadn't backed up any data - I needed to root before I got full functionality with titanium backup.
Anyway all worked out fine in the end. Hopefully, this post will help someone the future.
Sent from my GT-I9505G using xda app-developers app

need help guys at&t s4 brick. desperately

hi xda guys this is my story
i have an at&t samsung s4 on android 4.2 i have tried to update it via wifi to 4.4
but no use. a message appear say's " your device is up to date "
i have tied "loki way" it failed
i have tried "odin tool way' it failed it won't complete the process
i have tried samsung kais it fail's too a message says no update for this device
***** i managed to root the device
and then i found the safestrap apk i have insert the TWRP recovery
i have made a backup in case something go's wrong
and i have tries to flash a clean google s4 4.4.4 rom
**** and then the the phone stuck of samsung logo and vibrate often .the TWRP is lost
**** i have tried to recover the the via samsung kias it made it wors
now it have message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
i have tried via odin using the official firmware that i have downloaded. but did not work also
i have tried the kais recovery mode but i did not get the recovery code
help my friend what should i do
nead you help desperately
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Every time I have had and issue with a ROM or forget to flash loki I have no issues just ODIN back to 4.2.2 MDL. I say try it again.
MF3
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
You are on mf3 firmware. Flashing the mdl firmware won't work. That's the problem you're having. I would recommend you upgrade and flash the nb1 tar file. Read this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
spirodave said:
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
Click to expand...
Click to collapse
yes my friend
sorry my misstake i have flashed this room : Danvdh-GE-4.4.4-07172014.zip
And it works--
rugmankc said:
And it works--
Click to expand...
Click to collapse
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
I think you missed something--
You can't run aosp roms at all
On MF3 only 4.3 afaik
As mentioned do a lot of reading in those threads before going on--saves headaches--:good:
Best would be to upgrade to NB1, those instructions are in those threads too--:good:
myounis said:
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
Click to expand...
Click to collapse
Im gonna save you a bunch of time ................You are on MF3 ...Your BootLoader is locked ... You can only flash Safe Strap Roms aka HyperDrive or GoldenEye based off stock .. You can only use safestrap to install recovery ... Anything else will render your device useless.
Check the General Section ... Send you a link isn't gonna help ... You need to read multiple threads ...CHECK THE GENERAL SECTION
LOCKED BOOTLOADER= NO AOSP ROMS = ONLY ROMS BASED OFF STOCK
LOOK FOR A THREAD IN THE GENERAL SECTION CALLED DEBRICK
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
myounis said:
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
Click to expand...
Click to collapse
:good::good::good:
Same issue but mk2 has me struggling
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
I would try to find a Windows pc and flash the nb1 tar in Odin
I'm assuming you're using this but if not it's what you want http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would try to find a Windows pc and flash the nb1 tar in Odin
Click to expand...
Click to collapse
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Epiclectic said:
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Click to expand...
Click to collapse
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Epiclectic said:
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
Click to expand...
Click to collapse
my friend
if the mk2 is the same mf3
then download this link : https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
more details here : http://forum.xda-developers.com/showthread.php?t=2502003
place the 4 files in to odin
and flash them... it worked for me
and if not the same as mf3
look for mk2 ota update build from 4 files
it will reset you phone to factory firmware
i hop it will work for you
Epiclectic said:
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Click to expand...
Click to collapse
Consider installing Win7. Licenses can be had cheaply or just install, use for couple days for Odin (before it license locks) then wipe...
Sent from my SAMSUNG-SGH-I337 using Tapatalk

S5 G900I: Soft Brick or Door Step?

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

Categories

Resources