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
Related
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.
After searching hard for a solution, I have come to the conclusion that CM10 fried my tab's kernel memory.
What initially happened was just a random freeze while I was using the tablet, running the CM10 preview build. Keep in mind this was a couple weeks ago or so.
I hard reset the tablet, and it randomly boots into download mode. Okay... nothing weird. Reboot again.
Back into download mode. Inspection reveals the message "Reason: No Kernel" at the top of the command line.
I've been at work all day (thankfully a slow day) and I've tried just about everything from rebooting the tablet into recovery mode - which the device no longer has, either - to Odin, to ADB. A final google search directs me to this thread, where it appears the same thing happened to a non-rooted user and he had his mainboard replaced (assuming for free) due to hardware malfunction.
So I guess I'm just here looking for insight, perhaps closure. Is it really dead? If so, how can I make the best of this? Anything that I can salvage through a teardown? Perhaps a gadget I can build with it?
Any input at all is highly welcomed - even wanted. Please, give your thoughts on my loss of this tablet.
If your able to get into download mode, your tab is not dead. (Hopefully you can still get into download mode)
I had a similar problem recent too. I had to ODIN a couple times to fix whatever my problem was.
Download an ODIN stock ICS version for your device (assuming its US wifi only based off the model number in the title). You can get it here http://www.sammobile.com/.
nakedninja42 said:
If your able to get into download mode, your tab is not dead. (Hopefully you can still get into download mode)
I had a similar problem recent too. I had to ODIN a couple times to fix whatever my problem was.
Download an ODIN stock ICS version for your device (assuming its US wifi only based off the model number in the title). You can get it here http://www.sammobile.com/.
Click to expand...
Click to collapse
Read before you post. I clearly stated that I had tried just about everything to restore it.
Sent from my SPH-L710 using Tapatalk 2
kehlan said:
Read before you post. I clearly stated that I had tried just about everything to restore it.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I guess any input was not welcome... :what:
Sent from my SAMSUNG-SGH-I747 using xda premium
kehlan said:
Any input at all is highly welcomed - even wanted.
Click to expand...
Click to collapse
kehlan said:
Read before you post. I clearly stated that I had tried just about everything to restore it.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Take your own advice and reread your post before acting like an ungrateful douche. You never said whether you tried Odin multiple times either. Not a great way to get anyone to go out of their way to respond.
Sent from my GT-P7510 using xda premium
If you can't flash to a stock ROM with Odin, with the "Re-Partition" option checked (select the correct pit file, get it from samfirmware/flashing tools), it's pretty safe to say it's a hardware fault.
A few days back, my wife got me a shiny new nexus 10. This thing is cool for sure. However the one I'm using now isn't the one from a few days back. It is in fact, a replacement because after I hooked into my WiFi and loaded up the apps I have on my GNex off of Google backup, I got a notification for an android update. So I said "SHURE... I need that stuff" so I pushed the item in the notification and it said "push OK to restart...", so I did.... And it did restart to a DEAD ANDY ICON AND A "NO COMMAND" under him! I did a factory reset three times and never got further than the boot animation. The dude at google play support was a bit flummoxed but beyond a reset... Well... He pronounced it mostly dead. So rather than screw up the warranty, I took it back to where we bought it and got a new one.
So here I am again... I'm at JVP15P... And I've got a pending update downloaded and ready to fry my second N10! I've heard 4.2 has some kind of update issue just like this on the N10.... Is that true? What should I do? If this is true how do I get past this... I sure as s**t don't want to return anther one! Any suggestions are most appreciated.
Sent from my Nexus 10 using xda app-developers app
A short time ago, I was unable to update to 4.2.1 from 4.2, either from the automatic update, or from adb sideload. This was because I was using some older factory image (not sure what was wrong with it), but after downloading the latest factory image from Google and flashing it, I was then able to update without any issue
I finally did my updates.
Thankfully all went smooth. Although, my N10 ran as cool as ice before the updates. I could play games for a long time and it would barely get warm. Now it seems to run extremely warm. I wouldn't say hot, but it is noticeably a lot warmer and that is doing nothing but surfing the web.
Not sure what was in that first update, but it changed the way it runs. No other issues though.
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
alias_neo said:
I'm seeing the term "brick" used to lightly these days, but rest assured, the dead Android recovery is completely recoverable.
FYI for anyone reading, as it's becoming a pet peeve of mine ... "brick" means your device is TOTALLY dead, and as useful as a brick, if you get something (anything) on the screen, it's not a brick.
I think we should start lining up and shooting the people who throw that term around too lightly.
Anyway, back on topic, dead android screen with "no command" means the reboot to recovery flag is still set, but the device has no commend for recovery to perform, there are several ways out of it.
Worst comes to worst, and you want an easy way out, get the factory images from the dev site, flash them and you're golden.
Click to expand...
Click to collapse
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
Okay.... Soft-brick.... I stand corrected
I tried to do that using Wug's toolkit... But it didn't take. Did I need to unlock the boot loader first?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It's a boot-loop, technically, but now I'm just being a pedant
I'm not too sure about the toolkits because I don't use them, but yes, you have to unlock to flash stock images.
Easiest way it do download the zip from the dev site, unlock manually, then just double click the flash-all script, that will take care of the rest, then just relock after and happy days.
I know it's a bit nerve racking when it won't boot, but that will get you out of most sticky situations, in the case of boot loops, a wipe/factory reset from recovery should normally solve the issue, if it doesn't just flash the images again as above.
Pesonally, if I'm messing i'll make sure my device is up to date and working, then fastboot boot TWRP (without unlocking or modifying my device) and backup to a USB drive, then, you can restore your system as is at any stage later if things mess up.
fastboot boot is fantastic because it lets you temp boot a custom recovery, and do all your usual stuff (including rooting etc) without replacing the stock recovery, and without unlocking, soon as you reboot, it's gone, cause it just boot the reovery into RAM.
Doctor Dedroid said:
What procedure did you use to flash? When you tried the ota updates, did your update attempts brick your tablet?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
If you are talking to me, mine is stock and used regular updates that were DL and ready.
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Doctor Dedroid said:
I talk to anyone willing to listen to my drivel! I have heard of similar issues on this device ... Not many to be sure but my concern is if is an endemic issue going from the JVP15P... to JRO... 4.2 . it's good to know that this works for some if not most folks.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
alias_neo said:
It was only a particular issue that caused the update problem from 4.2 to 4.2.1, due to different filesystem formats in the factory images presented by google dev site. You *should* only have experienced it if you had flashed stock images before they updated to fix them.
I havn't seen cases of it happening otherwise. Unlocking will however boot loop you device because it doesn't do the full factory reset like it used to on the XOOM et al. Simple factory reset from stock recovery, after an unlock gets you booting again on the N10.
Click to expand...
Click to collapse
Got it! To be sure when I tried to update I was around 60% on the battery level... Hopefully my issue was a fluke or due to a low battery.
Update: all updated and good to go. Thanks one and all!
Sent from my Nexus 10 using xda app-developers app
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:
Hello All,
I am quite new to the world of Android, but have searched and read up for multiple days on this site before finally posting my issue.
I have a GS4 that had been running stock with the MF3 OTA update. I finally decided to root and install safestrap to mess with a few custom roms. Everything went well. I was able to create a Rom Slot and load a custom rom for testing whilst keeping my stock in original form. NO issues what so ever. I used the Wicked Rom.... Eventually I decided that I would delete Rom Slot 1 and go back to stock. I followed directions to the T, deleted the slot and selected to boot from Stock. NO GO. This is where the horror begins:
Now, the phone boots up but I see the Samsung Galaxy S4 logo and it stays there...does not go back. I no longer see the SafeStrap recovery screen when booting up. --- I cannot even get into recovery on the phone any longer: it says recovery booting in blue and stays there.
I am able to get into Download mode to re-flash - but naturally none of the stock firmware files are loadable via Odin due to an error I keep getting NAND Flash! (Fail).
I finally decided to drive to Best Buy and asked the guy to flash my phone to stock there. He put the phone in download mode and used their multiflash tool which did not detect the phone and thus he could not move forward. The laptop did detect the phone at best buy, but their software did not and thus flashing did not occur.
I am looking for any and all advice to get this phone running without having to return it to Samsung....please and thanks in advance.
My apologies if my search did not yield a positive result and there is something out there....
Well There is no way to flash with Odin while on MF3, so that effort is completely fruitless at this time. Did the guy try a different USB port, cord or even restarting the computer he was using?
Can you get into your recovery to do a factory reset?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Best buy should be able to do it. I remember reading somewhere that someone had to go to 3 different stores before they found someone smart enough to do it.. Lol
Sent from my SGH-I337 using XDA Premium HD app
I cannot get into recovery at all, it just says recovery booting and sits there....recovery booting is displayed at the top left of the screen in blue.
The guy did not try a different port or reboot. When he plugged the phone in, in download mode, the computer did recognize the phone but his Samsung software did not.
graydiggy said:
Well There is no way to flash with Odin while on MF3, so that effort is completely fruitless at this time. Did the guy try a different USB port, cord or even restarting the computer he was using?
Can you get into your recovery to do a factory reset?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well he is an idiot for not troubleshooting his system. I have had the same exact thing happen with multiple different computers and phones. The computer detects the device correctly, but the program I needed to use would not. More often than anything a quick changing of ports or a reboot of the computer fixed it. I have had to completely wipe out the drivers a few times and reinstall them to get it to work. 9 times out of ten, it is not the phone that is the culprit, it is something else before the phone.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
FIXED
Well it seems the guy at my best buy was a TOOL! I took the phone in again today, had the battery pulled before I arrived - put it in download mode for him. Told him that Samsung tech support said he should reboot his pc. He did. Voila, reflashed to stock. Thank goodness....thank you guys for the advice.
Apply cold water directly to burned area.
Who's awesome?
ME!
Anyways, glad you are back up.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app