Related
Every time I was reboot the phone goes to this menu, Odin doesn't recognize it, windows doesn't see any device attached, and no options(or combo of) have worked.
Any ideas appreciated!
Sent from my GT-I9000 using XDA Premium App
i almost bricked my phone several times but i never seen that...
dcboi said:
Every time I was reboot the phone goes to this menu, Odin doesn't recognize it, windows doesn't see any device attached, and no options(or combo of) have worked.
Any ideas appreciated!
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
If you have a tmobile vibrant, you need to flash the original JDF firmware ... if you gonna flash the KB5 firmware after make sure "re-partition "is not checked off in odin ...You are getting that error cause you are missing some data files that are only in the original firmware...
ive gotten that screen when i flashed without disabling vodoo. i always use the "froyo that does not brick" flash through odin.
as they say!
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
U can buy or make a jig I made one easy and cheap gets in download mode everytime
Oh man, everytime I odin, that screens comes by, flash froyo that doesn't brick by eugene with re-partion check, then flash a stock odin rom with unticked repartition. And there you go, a clean phone. I had to odin last night.
Sent from my SGH-T959 using Tapatalk
Chwek13 said:
U can buy or make a jig I made one easy and cheap gets in download mode everytime
Click to expand...
Click to collapse
Jig doesn't put the phone into download mode, neither does key combo+ usb+ battery insert. I think I'm screwed, unless there's a way to access a zip file from the external sdcard.
Sent from my GT-I9000 using XDA Premium App
dcboi said:
Jig doesn't put the phone into download mode, neither does key combo+ usb+ battery insert. I think I'm screwed, unless there's a way to access a zip file from the external sdcard.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Hey, I'm helping another XDA member with the same exact problem and it took me a long time, but made good progress. He's running froyo now, but can't install apps. So I'll definitely be able to help you with this.
crazy25000 said:
Hey, I'm helping another XDA member with the same exact problem and it took me a long time, but made good progress. He's running froyo now, but can't install apps. So I'll definitely be able to help you with this.
Click to expand...
Click to collapse
That would be great! I've run out of Google searches, blogs to read, and patience. I'm afraid of trying anything cause it feels like one more mistake could make me an expensive paper weight
Sent from my GT-I9000 using XDA Premium App
dcboi said:
That would be great! I've run out of Google searches, blogs to read, and patience. I'm afraid of trying anything cause it feels like one more mistake could make me an expensive paper weight
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I totally understand. Unplug the battery, take out the sim card, and sd card....leave it alone. PM me so we can set up a time to work on it and I prefer skype because of screen share, it makes it easier for me to show someone what to do.
ok, maybe not 100's of times but my bootloader showed 52 last time i flashed. Not sure what happened, but something went wrong. My phone only shows a picture of a phone, with a yellow triangle, and a picture of a computer. Under that it says firmware failed, and under that it says try recovery mode. Download mode, and recovery mode shows the the same screen described as above, and odin does not see phone. I left the battery out over night, and this morning, the same screen, and odin still don't see the phone. I know all the key combos to get into recovery or download mode, and neither works.
You have a bricked phone now. Use JIG USB to save it!
I had similar problem and resolved mine by removing the battery, reinserting it and holding down volume down and home keys while powering on (download mode). Then I connected phone to pc via usb and used odin to flash kernel. Hope that works for you.
Or you could try this
One-Click UnBrick
it seems this is the job for a USB jig (I think)
Sent from my GT-I9100 using Tapatalk
Have you tried recovery firmware option via KIES?
Bah, just take out battery and put it back in and go to download mode and flash the firmware with Odin.
Thanks God i've got my Jig..
is it related with the limitation write of the NAND flash? quite worry about it..any idea?
You only need a jig if you can't get into download mode. Though from what I've read on here might be good to have to reset the flash counter.
Sent from my GT-I9000 using XDA Premium App
hansonator said:
You only need a jig if you can't get into download mode. Though from what I've read on here might be good to have to reset the flash counter.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
and pretty sure the OP said he can't get into download mode...hence the need for a jig...
Sent from my GT-I9100 using Tapatalk
Does the number of times flashed has anything to do with the failure? Is there a limit after which the hardware gets weaker?
Believe me. Most rom chefs or developers in here flash at least 500+ times (if they tested their product) and I don't think they have issue. (I flash my X1 at least a 1000+ times when I was a rom chef and it's still working great now)
Flash memory does have a life span on number or Read/write. But I doubt anyone here can reach that limit with 3+ yrs (by that time, you will probably get another phone).
Agreed its unlikely that 50 odd our even a few hundred rom flashes should damage your nand memory. Unless it was faulty in the first place
Sent from my GT-I9100 using XDA App
This problem..
..Was notorious on the Captivate. We lovingly referred to it "Phone ! Computer" screen.
The good news.. If you see this screen the level 1 boot loader is fine and you are only soft bricked.
If you ever plug in the phone to a power source with it turned off and you see nothing then you're screwed.
Same scenario as when you plug in a JiG and nothing happens.
budco2000 said:
My phone only shows a picture of a phone, with a yellow triangle, and a picture of a computer.
Click to expand...
Click to collapse
Hold and do not release the key combo for DLM, your phone will reboot about 3 times it should then enter DLM.
I did try this before your reply and no go, I tried again today, got the same screen, however Odin and kies, both saw the phone, went back to stock then back to cognition 1.31. My captivate, inspire, and infuse ive flashed over and over and over and never bricked a phone until my S2. It's back up and going strong now. Now im afraid to flash it again. This is best phone ever and im keeping it until the S3 comes out, so im trying to not render my S2 useless yet lol
Sent from my GT-I9100 using XDA Premium App
You've developed flashphobia?
Intratech said:
You've developed flashphobia?
Click to expand...
Click to collapse
For days, odin and kies didn't see phone no matter what I did. I'm not a developer, but I'm nowhere close to a rookie either. What ever happen was a hoax, because clockwork and download mode works as it should again. Next update for cognition i'll flash, i doubt anything will happen.
budco2000 said:
For days, odin and kies didn't see phone no matter what I did. I'm not a developer, but I'm nowhere close to a rookie either. What ever happen was a hoax, because clockwork and download mode works as it should again. Next update for cognition i'll flash, i doubt anything will happen.
Click to expand...
Click to collapse
**** happens. Flashes go right 99.9% of the time when you do everything right. You just hit that 0.1% where something went wrong during the flash.
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not be able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
altae said:
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
Click to expand...
Click to collapse
I have never considered the "hex-patched" kernels to be safe...
jeriz said:
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
Click to expand...
Click to collapse
Yep. I don't think the drivers are the problem since the phone is recognized. But it does not start to flash. It simply does nothing and the phone stays in download mode forever.
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
this in itself is a huge statement
altae said:
I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash.
Click to expand...
Click to collapse
This is diferent... not even start to flash...
Sent from my GT-P3110 using Tapatalk 2
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
It seems that remaining on Gingerbread (until official JB) for the moment is the best thing for people who do not have a warranty for their Note.
Many people confuse superbrick (phone dead right away, no life even if you plug a charger) and other bricks. This is just an unfortunate other brick not related in any way to emmc described one. Good luck at RMA
Also, copying big video to your sdcard is a good way to kill it. Old i9000 thread was popular with that
Sent from my GT-I9100 using Tapatalk 2
Was running Paranoid Android
Tried to restore the Note back to the latest UK stock ICS ROM via ODIN
Forgot to wipe/davlik before hand
then got stuck in boot loop
more boot loops
Then tried flashing a rooted GB rom in ODIN
stuck now on the Samsung Note boot screen occasionally looping.
Then tried flashing an original non-rooted GB rom in Odin
got stuck on Data.img
Then tried again and it stuck on FACTORYFS wont even get passed this.
Took battery out, then back in...
Now the screen shows three images and the message
firmware upgrade encountered an issue
Now with the Samsung Repair centre in Eastbourne and they are failing to be able to do anything...they still have my NOTE:crying:
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
Sure, you can theorically miss the binary check in rare circumstances. But this is just "an other brick" without any common relation typical to described emmc brick: no wipe, no flash, and mainly no right away (or even) complete dead phone
Sent from my GT-I9100 using Tapatalk 2
@ Entropy. Even guy above Phil3759 his bricked his note starting from PA which has a "safe" kernel, and eventually superbricking just useing PC Odin (long time considered safe). No wipes involved. Anyway, is Tungstwenty's detection method flawed for stock ICS kernels? Or is there are problem changing the offending byte from a 1 to a zero
Sent from my GT-N7000 using xda app-developers app
At least this brick has made me decide to leave my note well alone, after flashing roms practically daily for the last month or so, I have become insanely addicted to changing roms...once i get the Note back from the Sammy Service place, I am sticking with stock and wait till the official JB update arrives, which looks fantastic.
As it states on all these roms flashing custom roms at your own risk, thus its my own fault, finger crossed it can be sorted.
You can brick any phone, it happens, yes. Superbrick related to emmc bug occurs under special circumstances with typical symptoms.
Binary patching kernels, in theory, if you happen to have duplicate binary code or different, you could miss it. But, as far as i know, and for all manual checks i did, it never happened...
Sent from my GT-I9100 using Tapatalk 2
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Markuzy said:
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
As i said, it is really non recommended to use your internal sdcard for regular heavy write operations like videos. It will be corrupted at a certain point. On the i9000 this used to be a way for some to get warranty. Phone stuck often after a continuous write/wipe overnight
But this is not the superbrick. And one day, all your phones will brick. That's flash storage
Sent from my GT-I9100 using Tapatalk 2
altae said:
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
Click to expand...
Click to collapse
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
If you read across HTC and other forums, you'll see so much bricks and unhappy people. Why blame Samsung, there will be always faulty devices and unhappy unfortunate people
Sent from my GT-I9100 using Tapatalk 2
Yeah, you're right. Even PC Nand causes grief. Just hoped a Company on the cutting edge of technology like Samsung would have been able to resolve such problems.
Sent from my GT-N7000 using xda app-developers app
I would better trust seagate or corsair to push it further. Samsung HDD always failed on me. Ditched them long ago
Sent from my GT-I9100 using Tapatalk 2
---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------
By the way, for people that want to know more about binary patching kernels, read here, it is worth it
http://forum.xda-developers.com/showthread.php?p=29609295
Sent from my GT-I9100 using Tapatalk 2
I flashed stock firmware via odin, but before I clicked start I left my tablet to charge for a bit. While I was gone my son had been messing with my laptop without my knowledge, but I'm not sure whether he ticked one of the boxes on ODIN or not.
Anyway, I went back later and began the flash. It finished successfully. Then I started up my note 10.1 and the splash screen was showing white lines across the screen instead of the usual "Samsung Galaxy Note 10.1" screen.
Sometime it shows the 'download mode' screen for a few seconds too.
Here is a video showing what happens...
https://www.youtube.com/watch?v=-9gFJBz0THc
How do I get it back to normal and why did this happen? Also, will this effect how my tablet runs in any way?
I've tried flashing the firmware again via ODIN and again via kies, with no luck.
Sent from my GT-N7100 using Tapatalk 2
Re: My Note 10.1 shows a fuzzy/white lined screen when booting up ??? [Video]
Nobody?
Sent from my GT-N7100 using Tapatalk 2
CuBz90 said:
Nobody?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I wouldnt be complaining about it, looks pretty cool.
Re: My Note 10.1 shows a fuzzy/white lined screen when booting up ??? [Video]
younix258 said:
I wouldnt be complaining about it, looks pretty cool.
Click to expand...
Click to collapse
How does it look cool? lol
It's extremely annoying.
Sent from my GT-N8010 using Tapatalk HD
My tablet does the same thing, it did this after I flashed with Odin as well. It does not really bother me that much though because I rarely ever shut down my tablet.
Re: My Note 10.1 shows a fuzzy/white lined screen when booting up ??? [Video]
Notex! said:
My tablet does the same thing, it did this after I flashed with Odin as well. It does not really bother me that much though because I rarely ever shut down my tablet.
Click to expand...
Click to collapse
Well its annoying when I boot up but I really want to get rid of it for future resell.
Sent from my GT-N8010 using Tapatalk HD
CuBz90 said:
How do I get it back to normal and why did this happen? Also, will this effect how my tablet runs in any way?
Click to expand...
Click to collapse
No clue as to why it happened. If you've reloaded the s/w again successfully via Odin and it's still there I'd try a hard reset from recovery. Turn it off and when it restarts hold "power/volume up" and select "wipe data/factory reset" as shown below. It might just be a coincidental h/w issue that popped up. But the fact "download mode" appears occasionally makes that improbable. You can always send it in for repair claiming ignorance. If you've only used Odin to flash stock s/w for your device's model (EG: N8010>N8010) Samsung will be none the wiser.
Re: My Note 10.1 shows a fuzzy/white lined screen when booting up ??? [Video]
BarryH_GEG said:
No clue as to why it happened. If you've reloaded the s/w again successfully via Odin and it's still there I'd try a hard reset from recovery. Turn it off and when it restarts hold "power/volume up" and select "wipe data/factory reset" as shown below. It might just be a coincidental h/w issue that popped up. But the fact "download mode" appears occasionally makes that improbable. You can always send it in for repair claiming ignorance. If you've only used Odin to flash stock s/w for your device's model (EG: N8010>N8010) Samsung will be none the wiser.
Click to expand...
Click to collapse
The strange things are that when the download mode shows at the beginning of a boot, it's always just a kind of screen shot from when I last went into download mode. Plus everything is working perfectly fine, the system runs as it usually would, same speed, etc. I can still root, flash a recovery, flash custom ROMS, etc.
I've already tried what you said, numerous times. I've flashed a few times too, completely erasing system, data and cache before flashing. I'm currently using a custom ROM and everything is working perfectly fine. The boot issue is the only thing wrong with the tablet. Surely there's a way to change it? Like flashing a boot animations?
I thought maybe it's soft bricked? I read somewhere that flashing the PIT would fix the issue I'm having, but i can't find the N8010 PIT file anywhere
Sent from my GT-N8010 using Tapatalk HD
Re: My Note 10.1 shows a fuzzy/white lined screen when booting up ??? [Video]
I've come to the conclusion that 'NAND erase all' had been ticked on Odin. What exactly does that do and can I reverse it?
Sent from my GT-N8010 using Tapatalk HD
did u flash different model rom with nand erase ticked?if u did then u must have messed up bootloader.i use to have att infuse and i flashed rom from canada infuse and was having same screen issue at boot.
Re: My Note 10.1 shows a fuzzy/white lined screen when booting up ??? [Video]
mintu123 said:
did u flash different model rom with nand erase ticked?if u did then u must have messed up bootloader.i use to have att infuse and i flashed rom from canada infuse and was having same screen issue at boot.
Click to expand...
Click to collapse
No I flashed the stock rom, the one that was on my note when I bought it
Sent from my GT-N8010 using Tapatalk HD
CuBz90 said:
I've come to the conclusion that 'NAND erase all' had been ticked on Odin. What exactly does that do and can I reverse it?
Sent from my GT-N8010 using Tapatalk HD
Click to expand...
Click to collapse
There is no "nand erase all" option in the odin version you should be using.
legion1911 said:
There is no "nand erase all" option in the odin version you should be using.
Click to expand...
Click to collapse
I had no clue I should be using a certain version of Odin, I assumed latest version was best version to use.
Does this mean there's nothing I can do?
I've also noticed that after flashing stock firmware via Odin, the phone stays stuck on the bootloader, unless I do a factory reset in recovery.
I guess for now there is nothing I can do. Nobody seems to know what the problem is.
Finally fixed it!!
I don't know exactly what did it, but I flashed the new N8010 4.1.2 firmware via Mobile Odin, and it was as good as new
Thanks to everyone that tried to help
CuBz90 said:
Finally fixed it!!
I don't know exactly what did it, but I flashed the new N8010 4.1.2 firmware via Mobile Odin, and it was as good as new
Thanks to everyone that tried to help
Click to expand...
Click to collapse
Thanks, it fixed it for me as well . I'm assuming in this firmware they fixed the exynos exploit, so they must of changed something in the bootloader or something, which happened to fix this? I do not really know.
Notex! said:
Thanks, it fixed it for me as well . I'm assuming in this firmware they fixed the exynos exploit, so they must of changed something in the bootloader or something, which happened to fix this? I do not really know.
Click to expand...
Click to collapse
I've looked and this update does update to a new bootloader, so that is what has fixed it.
Sent from my GT-N8010 using Tapatalk HD
its a recovery issue
younix258 said:
I wouldnt be complaining about it, looks pretty cool.
Click to expand...
Click to collapse
i have the same problem, the reason was cwm recovery!!! if you use twrp it will be fine !!
CuBz90 said:
I've looked and this update does update to a new bootloader, so that is what has fixed it.
Sent from my GT-N8010 using Tapatalk HD
Click to expand...
Click to collapse
gosh, i need to resell this tmr, and this situation happen to me now....... i think this is the only hope for me...
i also press tnand erase when i flash my stock rom... oh please..make it work..:crying:
Hi guys, i have a GS5 AT&T SM-G900A. My phone is rooted with towelroot. Last night it got stuck on the android bootup screen and from there nothing else. I try to flash it back with Odin but it keeps failing. Anybody has any idea how can i get this phone to work again?
..
fffft said:
Of course you'd prefer a fast answer. We all do when something happens. But it's presumptuous to label a post urgent as if your personal predicament is somehow more important than everyone else's. I know that urgent labels discourage me from helping as much as I otherwise would. Certainly I won't subscribe to your thread unless you remove the urgent label.
You also failed to provide us much information. In particular critical details like an Odin log, verbatim Odin errors, Odin version, your firmware version, et cetera.
First, boot to recovery mode and wipe your system cache. Then see if your phone will reboot normally. If not, then you need to repair it with Odin. And no one will be able to more than guess at what you did wrong unless you provide more details.
Click to expand...
Click to collapse
Thank you sir, sorry about the urgent label. i am trying to take off the urgent label but i am not able to edit that part here.
I am using Odin V3.07, i am trying to post an screen shot of it. My firmware is kitkat 4.4.2. I already did the recovery mode and wiped the system cache but nothing.
..
fffft said:
Edit /Delete > Go Advanced > Title
An Odin log or even screen shot would be invaluable. And you still haven't told us the exact file name that you are trying to write to your phone with Odin?
At a guess, it's just Odin being temperamental. But I am only guessing since we don't have much information about your configuration yet. Odin is infamous for being sensitive to USB timing just like IOS is.
Use the newer Odin 3.09. Write a pre June 6th build of stock firmware to your phone. Temporarily disable any firewall, antivirus, antimalware, et cetera software on your PC. Do not use a USB hub. Try a different USB cable and USB port. The latter is important. Odin often fails because of a noisy USB cable. Use, borrow or buy a different one that appears to be well constructed.
Also crucial. Ensure that you entered download mode by pulling your battery and then pressing and holding in sequence volume down + power.. If your Odin write fails, do not close the Odin window. Pull your phone battery again, replace it enter download mode again and then press the start (write) button on the Odin screen again. It's important that Odin screen remains open through out.
.
Click to expand...
Click to collapse
Thank you so much, all of those are great tips. I will try again tonight cause right now i am at the work computer. I will also have more info about the file i am trying to write in Odin. Thank you again for your great help and patience.
So i can't catch a break, now my laptop hard drive is making a ticking noise and i can't use it till i fix it.
Finally fix my laptop, Odin still failing like before. I changed computers and many usb ports and cables and nothing still stuck on boot.
Dra444 said:
Finally fix my laptop, Odin still failing like before. I changed computers and many usb ports and cables and nothing still stuck on boot.
Click to expand...
Click to collapse
First pull the battery, wait 30 seconds and boot in recovery mode and data factory reset. If that fails disable Kies in windows task manager. Power down, pull the battery and wait 30 seconds and then reboot in downloadmode and try again.
Thank you so much everyone, after many sleepless nights I finally figured it out. Somehow the firmware from sammobile wasn't working in Odin. I download one from here and it pass right away. Got my phone back
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
What file, link did you use. Trying to fix fiancees phone having problems after last update and wanted to back to original furmware. Odin making me mad.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
cm0818 said:
What file, link did you use. Trying to fix fiancees phone having problems after last update and wanted to back to original furmware. Odin making me mad.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2714455
This is the one I used, good luck man. It pass right away in Odin. Only thing I don't have no more is the setting to shut off the camera shutter sound but that's no big deal.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
cm0818 said:
What file, link did you use. Trying to fix fiancees phone having problems after last update and wanted to back to original furmware. Odin making me mad.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
This is the one I used, good luck man. It pass right away in Odin. Only thing I don't have no more is the setting to shut off the camera shutter sound but that's no big deal.
http://forum.xda-developers.com/showthread.php?t=2714455
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
..
cm0818 said:
What file, link did you use. Trying to fix fiancees phone having problems after last update and wanted to back to original furmware. Odin making me mad.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
This is the one I used, good luck man. It pass right away in Odin.
http://forum.xda-developers.com/showthread.php?t=2714455
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
cm0818 said:
What file, link did you use. Trying to fix fiancees phone having problems after last update and wanted to back to original furmware. Odin making me mad.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I feel your pain, this is the one I use. The one that kept failing was the one from sammobile. Feels great having my phone back. Now I need a custom recovery mode just in case.http://forum.xda-developers.com/showthread.php?t=2714455
fffft said:
@Dra444
Glad you got your phone working again. Please link me to the firmware file that wasn't working for you to, so that I can try to figure out what was wrong with it. Perhaps find a way to identify bad files in the future. Or at least build a list of known good /bad firmware builds.
.
Click to expand...
Click to collapse
Thanks man, well I would need to upload the big file here. I almost gave up and then xpa came to the rescue.
..
fffft said:
xda?
You don't need to upload any big files here. Just a link or the exact file name of the troublesome build.
.
Click to expand...
Click to collapse
Oh Ok, here is a link to the firmware from Sammobile. Anyway i could get back the setting to shut off the camera shutter sound off? My Stock firmware had it before. http://www.sammobile.com/firmwares/3/?download=28224
..
fffft said:
For the camera shutter sound, check these two files.
After editing, check that the file permissions are 0644
Edit or add this parameter.
/system/csc/feature.xml
<CscFeature_Camera_ShutterSoundMenu>true</
CscFeature_Camera_ShutterSoundMenu>
Edit or add this parameter
/data/local.prop
ro.camera.sound.forced=0
.
Click to expand...
Click to collapse
Thanks man, i am still learning here. Can you take me step by step for this, don't want to mess my phone again.