Database Users

Bricked my Bell Galaxy S. help needed badly PLEASE PLEASE PLEASE!!

Hi guys,
I had darky's rom on my phone and then i had to factory reset it. It was working fine after the factory reset. I wanted to go back to stock firmware since i was planning on taking my phone to the Bell store tomorrow but in doing so i bricked my phone. Now all it does is show the boot screen and then the screen turns black and it keeps on vibrating randomly.
Can anyone PLEASE help me with this? I wanna go back to stock firmware if possible, or any firmware really i just wanna get my phone working. please help

superstrongboy said:
Hi guys,
I had darky's rom on my phone and then i had to factory reset it. It was working fine after the factory reset. I wanted to go back to stock firmware since i was planning on taking my phone to the Bell store tomorrow but in doing so i bricked my phone. Now all it does is show the boot screen and then the screen turns black and it keeps on vibrating randomly.
Can anyone PLEASE help me with this? I wanna go back to stock firmware if possible, or any firmware really i just wanna get my phone working. please help
Click to expand...
Click to collapse
What version of darky's rom were you using and which stock firmware version did you want to go back to?
It could be that you were using a version of darky's rom that is gingerbread and you flashed back to the froyo stock rom.

superstrongboy said:
Hi guys,
I had darky's rom on my phone and then i had to factory reset it. It was working fine after the factory reset. I wanted to go back to stock firmware since i was planning on taking my phone to the Bell store tomorrow but in doing so i bricked my phone. Now all it does is show the boot screen and then the screen turns black and it keeps on vibrating randomly.
Can anyone PLEASE help me with this? I wanna go back to stock firmware if possible, or any firmware really i just wanna get my phone working. please help
Click to expand...
Click to collapse
Ok, try to turn on the phone pressing VOLUME DOWN+HOME+POWER and see if the phone goes in Download Mode.
Then, follow the guides that you can find in the forum and flash with ODIN a new ROM (I suggest JS8 if you're in EUROPE, Froyo 2.2.1)

Download Mode work ? 3 buttons holding Vol down+home+power

bobloblawsum said:
What version of darky's rom were you using and which stock firmware version did you want to go back to?
It could be that you were using a version of darky's rom that is gingerbread and you flashed back to the froyo stock rom.
Click to expand...
Click to collapse
I had darky's ressurection edition rom and i had it on froyo.
i want to go back to any firmware version that will get my phone working

olivercervera said:
Ok, try to turn on the phone pressing VOLUME DOWN+HOME+POWER and see if the phone goes in Download Mode.
Then, follow the guides that you can find in the forum and flash with ODIN a new ROM (I suggest JS8 if you're in EUROPE, Froyo 2.2.1)
Click to expand...
Click to collapse
yeah it goes into download mode
. I live in canada.
can you please link me to the proper firmware for Canada's bell SGS? and possibly if there's a guide on how to go back because i m a total noob.

superstrongboy said:
yeah it goes into download mode
. I live in canada.
can you please link me to the proper firmware for Canada's bell SGS? and possibly if there's a guide on how to go back because i m a total noob.
Click to expand...
Click to collapse
Here is a link to the official stock Bell JL2 firmware, there is a slightly newer one but i can't find the link and this should work fine.
You will need to use Odin to flash the file
*edit; forgot the link. http://www.multiupload.com/UTFJCCIP5H

download a stock Eclair or Froyo Rom from samfirmware.com with (512.pit,PDA,MODEM,CSC) get in download mode (vol up+power+menu all at the same time) flash via ODIN DO NOT UNPLUG wait till full flash make shure you have at least 60% battery left before flashing
if it dosen't work search around you'll find some methods its not bricked its just in a continuous loop

i tried flashing with that link you gave, but ODIN doesnt do anything after this
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..

superstrongboy said:
i tried flashing with that link you gave, but ODIN doesnt do anything after this
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
Click to expand...
Click to collapse
Did you add the tar file to the PDA section of Odin? That should be all that's needed in odin, no repartition, no pit file and the Tar file that was extracted from the Zip file placed in the PDA section of odin.
I forgot to add, did you run Odin as an administrator?

bobloblawsum said:
Did you add the tar file to the PDA section of Odin? That should be all that's needed in odin, no repartition, no pit file and the Tar file that was extracted from the Zip file placed in the PDA section of odin.
Click to expand...
Click to collapse
yeah i did that it wasnt moving forward.
then i disconnected and now when i press HOME+VOL. UP+POWER or only power button, i get the [Phone -- ! -- PC] symbol. i can still go into download mode idk what to do im so screwed.
yeah i m running odin as admin

i flashed that firmware onto my phone.
now all it does is freeze at the Galaxy S screen and vibrates randomly. what do?

superstrongboy said:
i flashed that firmware onto my phone.
now all it does is freeze at the Galaxy S screen and vibrates randomly. what do?
Click to expand...
Click to collapse
Here is the thread where i got the link to the Rom from, i'm reading through it now to see if there are any similar problems http://forum.xda-developers.com/showthread.php?t=883568

According to post #45 on that thread you should flash the rom with the 'Phone Bootloader Update' option checked.
I'm not 100% certain on that and don't want to give you some wrong advice but if i remember right, it was the new bootloader in JL2 that fixed the SD card problems that the Bell vibrants had. It's up to you if you want to try flashing the file with that option checked. Unless you get some better advice.

superstrongboy said:
i flashed that firmware onto my phone.
now all it does is freeze at the Galaxy S screen and vibrates randomly. what do?
Click to expand...
Click to collapse
had u ever upgrade to 2.3.3 ?
try those roms
UGJL2/BMCJL2/UGJL2 (North America for I9000M only)
UGKC1/BMCKC1/UGKC1 (North America for I9000M only)
i dont have any link atm , i will search about that and i will edit my post

NCSoft said:
had u ever upgrade to 2.3.3 ?
try those roms
UGJL2/BMCJL2/UGJL2 (North America for I9000M only)
UGKC1/BMCKC1/UGKC1 (North America for I9000M only)
i dont have any link atm , i will search about that and i will edit my post
Click to expand...
Click to collapse
nope i havent ever upgraded to 2.3.3
and if i take my bricked phone to the store, will they replace it? I still am under the warranty period

superstrongboy said:
nope i havent ever upgraded to 2.3.3
and if i take my bricked phone to the store, will they replace it? I still am under the warranty period
Click to expand...
Click to collapse
They'll send it off to the repair centre and try to determine and fix the problem. If they think the problem was caused by you then they might try to charge you a fee for fixing it.
Have you installed Kies on your laptop before (just to know if you have the samsung drivers that come with it installed)
If it has come to the point where you're thinking of bringing it to the store then, personally, i would try flashing the JL2 rom with the update bootloader option checked. That's just what i'd do personally though.
It could also be something simple like trying to flash it from a different usb port.

bobloblawsum said:
According to post #45 on that thread you should flash the rom with the 'Phone Bootloader Update' option checked.
I'm not 100% certain on that and don't want to give you some wrong advice but if i remember right, it was the new bootloader in JL2 that fixed the SD card problems that the Bell vibrants had. It's up to you if you want to try flashing the file with that option checked. Unless you get some better advice.
Click to expand...
Click to collapse
THANK YOU SO MUCHHHH!!!!! I DID IT AND ITS WORKING NOW!!! YAYAAAAYAAAAAAAAY CANT TElL YOU HOW HAPPY I AM LOL you're a life saver mate.

superstrongboy said:
THANK YOU SO MUCHHHH!!!!! I DID IT AND ITS WORKING NOW!!! YAYAAAAYAAAAAAAAY CANT TElL YOU HOW HAPPY I AM LOL you're a life saver mate.
Click to expand...
Click to collapse
Yea, that was the problem; now I remember! Some months ago, I had your same problem (an apparent brick, vibrating on the big S at the startup). A user suggested me to simply flash a FW with a Bootloader (at the time, the JPU), ad it worked ^^

superstrongboy said:
THANK YOU SO MUCHHHH!!!!! I DID IT AND ITS WORKING NOW!!! YAYAAAAYAAAAAAAAY CANT TElL YOU HOW HAPPY I AM LOL you're a life saver mate.
Click to expand...
Click to collapse
Haha, no problem! glad to help
i was in the same position a few months ago and the JL2 rom helped me out. I keep a copy of it on my harddrive to use if things go tits up again.

[Q] MF3 via ODIN or Kies, yet?

My SGH-I337 bricked with the MF3 OTA update. Kies recovery and emergency recovery fails. ODIN with MDL fails, too. I'm guessing they all fail due to either my device being officially dorked, or my device has enough of MF3 that it won't let Kies or ODIN "download" to an older firmware. Does anyone know for sure whether or not Kies has access to the MF3 firmware? Is MF3 out there in the wild, yet, that I can flash with ODIN? I've searched and haven't found anything so far.

runbuh said:
My SGH-I337 bricked with the MF3 OTA update. Kies recovery and emergency recovery fails. ODIN with MDL fails, too. I'm guessing they all fail due to either my device being officially dorked, or my device has enough of MF3 that it won't let Kies or ODIN "download" to an older firmware. Does anyone know for sure whether or not Kies has access to the MF3 firmware? Is MF3 out there in the wild, yet, that I can flash with ODIN? I've searched and haven't found anything so far.
Click to expand...
Click to collapse
Yea, i have same issue. My phone is actually working but my root has been cleared out and ODIN fails with every single firmware version i have. It appears that i upgraded through air update to the latest one. MF3 which i was unable to find yet online.

I know this doesn't help your situation at all, but can you tell me: at what point does Odin fail? Can you post a log somehow?
I'm curious which part is causing it to reject Odin. The OTA included a new sbl2, sbl3, aboot, and something called "tz" (has something to do with security).

Aou said:
I know this doesn't help your situation at all, but can you tell me: at what point does Odin fail? Can you post a log somehow?
I'm curious which part is causing it to reject Odin. The OTA included a new sbl2, sbl3, aboot, and something called "tz" (has something to do with security).
Click to expand...
Click to collapse
Here is where mine fialed:
<ID:0/004> Initialzation...
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL (Auth)
<OSM> All Threads Completed. 9 succeed 0 / failed 1)
But it might be cause because i tried to load earlier version of firmware the one before MF3

Aou said:
I know this doesn't help your situation at all, but can you tell me: at what point does Odin fail? Can you post a log somehow?
I'm curious which part is causing it to reject Odin. The OTA included a new sbl2, sbl3, aboot, and something called "tz" (has something to do with security).
Click to expand...
Click to collapse
I'm pretty sure mine failed in ODIN exactly where the other poster showed failure. Essentially, it occurs when ODIN starts actually trying to write to the device. It's quick.
Just tried it again with a Kies Emergency Recovery. I poked around in my temp files and found the MDL bootloader, so I'm reasonably certain the Kies firmware is MDL (and I have forced a delete of all temp files each time I run it).
When using Kies, the error shown in the tiny tiny tiny text in the upper left corner of the S4 screen is:
START [224,1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1

Slavisha said:
Here is where mine fialed:
<ID:0/004> Initialzation...
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL (Auth)
<OSM> All Threads Completed. 9 succeed 0 / failed 1)
But it might be cause because i tried to load earlier version of firmware the one before MF3
Click to expand...
Click to collapse
I see. I'm considering attempting to update some of the other parts of my phone (sbl2, sbl3) while not touching my recovery or my aboot. ... I'll see if I can collect more information.
Thank you for providing this info. Much appreciated. I sincerely hope that Samsung will release a new Odin/Kies for you guys.
---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------
runbuh said:
I'm pretty sure mine failed in ODIN exactly where the other poster showed failure. Essentially, it occurs when ODIN starts actually trying to write to the device. It's quick.
Just tried it again with a Kies Emergency Recovery. I poked around in my temp files and found the MDL bootloader, so I'm reasonably certain the Kies firmware is MDL (and I have forced a delete of all temp files each time I run it).
When using Kies, the error shown in the tiny tiny tiny text in the upper left corner of the S4 screen is:
START [224,1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
Click to expand...
Click to collapse
I don't like that word, "fused".

runbuh said:
I'm pretty sure mine failed in ODIN exactly where the other poster showed failure. Essentially, it occurs when ODIN starts actually trying to write to the device. It's quick.
Just tried it again with a Kies Emergency Recovery. I poked around in my temp files and found the MDL bootloader, so I'm reasonably certain the Kies firmware is MDL (and I have forced a delete of all temp files each time I run it).
When using Kies, the error shown in the tiny tiny tiny text in the upper left corner of the S4 screen is:
START [224,1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
Click to expand...
Click to collapse
Any luck? I'm stuck at the same point.

InstigatorX said:
Any luck? I'm stuck at the same point.
Click to expand...
Click to collapse
I'm stuck at the same thing too...except mine wont reboot

I ended up returning the phone and getting a new one. Was 1 day past 14 day return policy but was able to return... Whew!
Sent from my SGH-I337 using XDA Premium 4 mobile app

You guys are all hosed until if and when mf3 comes out for kies. You can try returning your device and may get lucky.

At&t S4 Stuck in Download Mode
I am having the same issues as the others have talked about; I have tried multiple stock firmware files but all fail. The same happens when I try to use Keis. Is there any file that could flash to completely start fresh? I would appreciate any help.

HunterTJones said:
I am having the same issues as the others have talked about; I have tried multiple stock firmware files but all fail. The same happens when I try to use Keis. Is there any file that could flash to completely start fresh? I would appreciate any help.
Click to expand...
Click to collapse
From what I have seen here you can take your device up to Best Buy & they can reflash mf3 for you.
Sent from my SGH-I337 using Forum Runner

If someone could confirm this, they will make the happiest person alive.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Mortorojo said:
If someone could confirm this, they will make the happiest person alive.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Confirm what? Best Buy flashing MF3? If that is what you are talking about confirming I suggest you take some time to read through posts on the forum(s). It has been mentioned (confirmed) dozens of times in several different threads.

Not the best buy in my area . Oklahoma City
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

You have to go to Bestbuy that has Samsung experience and most of the people that went said their Best Buy Associate had no idea how to do this.
Sent from my GT-I9505G using Tapatalk 4

I'm stuck as well... I went to Our local Best Buy and they weren't able to do anything either. Their Samsung "Specialist" knew nothing... especially considering the misuse of terminology. I was honest and told her I had rooted the phone (when asked) but that I hadn't installed any custom ROMs... She said she would have to call Samsung tech support, but eventually said there was nothing she could do because it said "Custom" on my phone.
I asked if I could sign a waiver or something saying i assume liability, and she said they had nothing. I said I understood, but asked if she would at least plug it in to the laptop to see if the phone was recognized. She did, and it was recognized (surprise)... I was hoping that would have convinced her it was ok... No luck, I dejectedly left. If you can find someone that doesn't look closely or just doesn't care, you may be in luck.

*sigh* add me to the brick list.
Will have to wait for the weekend to see if I can get to an ATT store and pull the "you ****ed up my phone with your useless update" card..
Partially my fault for seeing the popup, and not thinking at the time due to being busy and just hitting accept without researching the update.
I managed to get the encrypted mdl version and extract it, I can still flash a pit file, but after that its a no go.

Does anyone know if Samsung brings the Kies servers down when updating/adding new firmwares? I know i'm probably being too hopeful in thinking that, but I didn't know if someone else may have noticed a pattern with it or if they just have regular maintenance when they bring the servers down for a bit.
I just too the attached screenshot a few minutes ago.

[Q] Galaxy S5 Bootloop

Before marking this as a duplicate, please note that I've gone through almost every thread on this and different possibilities, but nothing had worked.
This morning, I rooted my AT&T Samsung Galaxy S5 (US) using towelroot. The root was successful. Next I downloaded Superuser from the Play Store (not the Chainfire one). It said it needed to update something using recovery mode, but it failed with an error. So, I ignored it and continued using the phone. Next, I downloaded the Google Now Launcher from Android L, to get Material Design. I installed Sliding Explorer from the Play Store to access root files. I also got a simple text edit app. To get Material Design, I needed to change ro.build.version.codename=REL to =L in build.prop. When I did and tried to save, it said access denied, so I changed permissions (oops!) to allow the file to be saved. Still didn't work for some reason so I saved the file as build.prop somewhere else and cut and pasted it in. Then, I rebooted my device and it got stuck on the boot screen with the Samsung Galaxy S5 logo with powered by Android beneath it.
What I've tried:
- I have wiped data, the cached, but there is no advanced option for me to wipe dalvik in the stock recovery for the Galaxy S5.
- When I try to use ADB, my device shows up as sideload and sideloading a ROM goes to 100% but ends up in an error. I cannot run ADB Shell, which ends in error:close.
- Using Odinv3 Build 3.09, I think, gets stuck on connecting to the phone, while Odinv3 Build 1.85, I think, gets fails at Complete(Write) error after something to do with NAND write.
My device drivers are all updated, and I've tried different USB ports, even different PC's. Nothing works. How can I fix this? Thanks!

I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.

fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.

tforkan99 said:
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
Click to expand...
Click to collapse
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.

fffft said:
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
Click to expand...
Click to collapse
Odin3 v3.09: Stuck on "SetupConnection"
Odin3 v1.85:
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, originally ATT
Regular model
Don't know about re-activation lock
I think the firmware version is the problem. The last update was the one from ATT that added Yellowpages and Lookout in May. Don't know version. I've been download an April build so maybe that's why there is an error. My phone says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1" which apparently occurs when downgrading. Maybe if I can get an updated ROM, I can use Odin? And I've seen suggestions to use Odin3 v3.04, but same error with the April build. I can't find the May build anywhere.
Maybe this will work?:http://forum.xda-developers.com/showthread.php?t=2737257 But it's .zip and I can't flash it with Odin.
I have a Kies backup, that's it. This always happens to me . I'm always too lazy to back up my devices.....
Yes recovery mode works and I can get into ADB Sideload.
Nope, never used Odin before. never tried.

I may have something here!
http://forum.xda-developers.com/showthread.php?t=2785185
My firmware is G900AUCU2AND3.
I will update after following the guide.

It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.

tforkan99 said:
Device successfully restored to functionality.
Click to expand...
Click to collapse
Great to hear.
As I commented at the outset, all you needed to do was restore a full, stock firmware image to recover. Ideally one that matches your existing baseband. Which is essentially what that thread did. Collected all of the pieces to do a 100% reversion to stock.
I've written similar posts for Verizon and TMobile. Was in fact just rewriting the Verizon one for you when you updated the thread. Anyway, good work. Give yourself a pat on that back and promise to make more backups this time.
.

Ego?
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
I'm allergic to egocentric attitudes when it comes to answers in a Q & A thread.

tforkan99 said:
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
Click to expand...
Click to collapse
Happy to hear it that worked out for you!

[Q] Bricked Galaxy S4, pls help (everything tried)

Hi all ! Hope sb help me with this...
I updated my S4 i9500 to android 5.0.1 lollipop (XXUHOAA ) about 8 months ago. No problem untill 2 days ago my phone turned off itself then went to bootloop.
Now it just shows the s4 logo then restarts again all the time. SOMETIMES it turns on but after 4 or 5 seconds again turns off (not able to do anything during 4 seconds)
I CAN NOT access recovery mode. The recovery mode became a black screen and not able to wipe/factory reset.
Before I bring it to serviceman I want to see if u can help me with this(It's warranty is voided now)
WHAT I HAVE TRIED RECENTLY:
I tried to flash 4 different Roms using 3 different odin versions but no success
[flashing roms get the error "complete(write) operation failed" and by using the suitable PIT file I get the error "repartition operation failed"]
Also tried flashing 5-files-firmware (with pit file) but again "repartition operation failed"
I used 3 usb cables including the original one
I did all of those steps using 2 different laptops and also different ports
I'm sure the samsung drivers are installed[odin port comes blue or yellow]
I used SkipSoft ToolKit and one click unsoftbrick softwares but no success
Also used adb to factory reset phone but it doesn't detect my phone[ seems it needs to be turned on]
I removed simcard, format extra sd card, remove battery for a long time and.....
Is there anything I haven't tried yet?? Can somone help ? I appreciate any suggestion,Thanks
[[Sorry my English]]

Try flashing a custom recovery and then factory reset?

KennethHau said:
Try flashing a custom recovery and then factory reset?
Click to expand...
Click to collapse
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused

Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Sent from my unknown using Tapatalk
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
alimtale said:
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused
Click to expand...
Click to collapse
Is the Odin version the proper one for your phone?
Sent from my unknown using Tapatalk

Jchef said:
Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Is the Odin version the proper one for your phone?
Click to expand...
Click to collapse
Of course I did. I even downloaded different android versions (5.0.1,4.4.2,4.2.2) But non of them flashed
I remember I used Odin 3.0.9 to upgrade my S4 to 5.0.1 months ago but I tried different Odin versions (1.85,3.0.7,3.0.9) for in case.
Unfortunately,I face an error all the time that is related to Nand write corruption .

If you have flashed 4.2.2 it's a brick ,for sure.

ludoke said:
If you have flashed 4.2.2 it's a brick ,for sure.
Click to expand...
Click to collapse
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.

alimtale said:
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.
Click to expand...
Click to collapse
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work

ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
My phone turned off itself. I tried flashing firmware after the problem occurred. I don't think the problem is because of flashing 4.2.2

Deleted

Maybe it's the battery

ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
This is incorrect. You don't brick your phone when you try to flash 4.2.2. That's simply not possible.

dorian2kx said:
Maybe it's the battery
Click to expand...
Click to collapse
I have 2 batteries...both of them same result (bootloop)

alimtale said:
I have 2 batteries...both of them same result (bootloop)
Click to expand...
Click to collapse
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.

Lennyz1988 said:
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.
Click to expand...
Click to collapse
No it doesn't reboot while download mode.Maybe hardware damage but it sometimes turns on and I can access applications and settings for a short time (about 5 seconds)
I have rooted my device when upgraded to 5.0.1. And recently I unchecked "enable superuser" in the superuser app.( I have done this before many times without problem)
I guess there is a problem related to that because when my phone turned on I tried to check the enable option in the superuser but as soon as I touch the check box my phone turns off instantly

If your phone goes into download mode. I don't think it is bricked.
Sent from my unknown using Tapatalk

You cannot fix your phone by Odin because of the Secure Download enabled bootloader.
You will have to pay a JTAG repair service.
Android 5.0.1 is a crap, which replaces your bootloader with a secure-download featured one,
so you won't ever be able to have the control of your phone again!

@Killnolife: A little melodramatic? It's not a locked bootloader so he still has total control over the device. Come back with an AT&T or Verizon S4 and then complain about having no control.
OP, Lennyz1988's advice is sound. Follow it.

Well I got tired of trying to flash my device with Odin. Always error... The Only choice I have is to take the phone to the service center and see what they can do...I'll share the result...

I took my phone to service centers for repair, they said the hard is damaged and it takes about 100$ to replace that:crying: if I pay that much I'm not sure it wont damage again
So my phone is dead now on my table and I gonna buy a new phone (maybe s5 or z3). Hope no one experience this situation

phone with split personality

I have a sm-n910t3 phone I recently got. It was already flashed with some rom, twistd i think . I got an su binary is occupied error so i thought I would just reload stock, and downloaded the \N910T3UVS3EQE2_N910T3TMB3EQE2_N910T3UVS3EQE2_HOME .tar.md5 since that what the phone says it is in the battery compartment. HOWEVER,
if i look at the about device, settings, model number ,it says the model is sm-g935t, baseband version says N910T3UVS3EQE2
when i run odin it checks the md5, adds it to the ap block and click start I get
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
Twrp 3.2.1-0 is installed and accessable
all i wanted was to put on stock 6.0.1, twrp, root and magisk but now it seems i have a very basic os with little else.
any help will be greatly appreciated

stock bootloader n910t3
SO i HAVE MANAGED TO PRETTY MUCH ALMOST BRICK MY 910T3. after screwing around with it for way too long it now will not boot at all keeps returning to twrp. odin will not download due to the device error mentioned above. I still have hope but it is dwindling every day may have a $200 brick.

cmccarter said:
SO i HAVE MANAGED TO PRETTY MUCH ALMOST BRICK MY 910T3. after screwing around with it for way too long it now will not boot at all keeps returning to twrp. odin will not download due to the device error mentioned above. I still have hope but it is dwindling every day may have a $200 brick.
Click to expand...
Click to collapse
Hey... I want to try and help you out if I can. My note 4 although a different version was also almost bricked. When you just hold the power button only, does it just go straight to twrp or does nothing happen? Does it vibrate or go to the Samsung Logo or anything?

If I just do power on it goes to the Galaxy note 4 logo then twrp, I can also get to the download screen and the twrp screen using the roll up/down home pwr keys.
Sent from my SHIELD Tablet using XDA Free mobile app

cmccarter said:
If I just do power on it goes to the Galaxy note 4 logo then twrp, I can also get to the download screen and the twrp screen using the roll up/down home pwr keys.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
A long shot but, if you were willing to try this, there's a rom on this website https://forum.xda-developers.com/no...eo-8-1-0-unofficial-lineage-15-1-rom-t3760969 It's a small file size in comparision to others, install it via twrp (Follow the instructions in the link...) It's supposed to support your phone. I use it and it works fine.
So what you'd be doing is installing the rom, then Open GApps, then Magisk one after another without exiting twrp, then when done, go to the main menu of twrp, then pull out your battery, and take the Micro SD card out of the phone and keep it out, then try booting up the phone and give it about 10-20 minutes and give the results?
I'm aware you might want stock etc, but I just want to see if this works.

Hi
I 100% agree with the post above :good:
Juste dont forget to flash the latest BL and CP: https://basketbuild.com/filedl/devs?dev=ripee&dl=ripee/BL_CP/N910T3UVU3EQI2_N910T3UVU3EQI2.tar
From the OP pointed...
Sent from my SM-N910F using XDA Labs
---------- Post added at 10:07 AM ---------- Previous post was at 10:02 AM ----------
cmccarter said:
if i look at the about device, settings, model number ,it says the model is sm-g935t, baseband version says N910T3UVS3EQE2
Click to expand...
Click to collapse
My guess is that it was a ported ROM
Sent from my SM-N910F using XDA Labs

THANK YOU
lightbright001 said:
Hey... I want to try and help you out if I can. My note 4 although a different version was also almost bricked. When you just hold the power button only, does it just go straight to twrp or does nothing happen? Does it vibrate or go to the Samsung Logo or anything?
Click to expand...
Click to collapse
Ok tried a few things the files mentioned are, I think, for a note 8 but they did get my phone back to where it thinks it is a 910t3 instead of something else. not sure I like the lineage os but it worked for me gonna try now to get back to stock os 6.0.1 since odin will work again. will post as to how it goes
again a huge thank you to those who helped
:good:

maybe worse
finally ended on lineage for now, really did not want v8 but will take what works for now.

Gonna work today on an older ROM close as I can get to 6:0.1. Any suggestions seem like stock ROMs are hard to come by.

cmccarter said:
Gonna work today on an older ROM close as I can get to 6:0.1. Any suggestions seem like stock ROMs are hard to come by.
Click to expand...
Click to collapse
Just my 2c - did you try the Samsung Smart Switch ? It helped me when I had it bricked (910C) to get back to the latest official firmware.
You need to get the serial number, which is located under the battery.

w41ru5 said:
Just my 2c - did you try the Samsung Smart Switch ? It helped me when I had it bricked (910C) to get back to the latest official firmware.
You need to get the serial number, which is located under the battery.
Click to expand...
Click to collapse
I'm not able to use SmartSwitch on LOS 15.1 maybe OP could...
Before messing around, please backup (at least EFS)
My 2c
Sent from my SM-N910F using XDA Labs

barlu said:
I'm not able to use SmartSwitch on LOS 15.1 maybe OP could...
Before messing around, please backup (at least EFS)
My 2c
Sent from my SM-N910F using XDA Labs
Click to expand...
Click to collapse
Samsung Smart Switch as a PC (windows) program and not as an android app.
https://www.youtube.com/watch?v=9QhJngOuLQ4&t=337s

w41ru5 said:
Samsung Smart Switch as a PC (windows) program and not as an android app.
&t=337s
Click to expand...
Click to collapse
I forgot this one... I don't use that much my (too) old PC.
Thanks for remind me.
Sent from my SM-N910F using XDA Labs