Database Users

[SOLVED] My Note 10.1 shows a fuzzy/white lined screen when booting up ??? [Video]

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:

[Q] Flashed ROM - it rebooted and died?

Hi,
Sorry if this has been covered but search is down and I am panicking! I have an i-337 ATT Galaxy S4 that was unlocked for Tmobile. I just bought it 2 days ago and tonight I rooted it via motochopper and installed TWRP.
I downloaded Liquidsmooth and Gapps and flashed them via recovery. I did a factory reset and a nandroid backup. After the flash I selected reboot, and the phone turned off like it was rebooting, but never came back on!
I did a battery pull and nothing! I also tried holding down + home + power!
I accidentally forgot to wipe cache/dalvik cache after the install.
Help! I hope this isn't a brick. I've been rooting phones for a while and haven't ran into a problem.
No response when I plug it into the computer, and no charging light (the battery probably has 95% charge)
Thanks

re: download/recovery modes
Nurmi_CEO said:
Hi,
Sorry if this has been covered but search is down and I am panicking! I have an i-337 ATT Galaxy S4 that was unlocked for Tmobile. I just bought it 2 days ago and tonight I rooted it via motochopper and installed TWRP.
I downloaded Liquidsmooth and Gapps and flashed them via recovery. I did a factory reset and a nandroid backup. After the flash I selected reboot, and the phone turned off like it was rebooting, but never came back on!
I did a battery pull and nothing! I also tried holding down + home + power!
I accidentally forgot to wipe cache/dalvik cache after the install.
Help! I hope this isn't a brick. I've been rooting phones for a while and haven't ran into a problem.
No response when I plug it into the computer, and no charging light (the battery probably has 95% charge)
Thanks
Click to expand...
Click to collapse
You were holding down the wrong buttons.
Press and hold the VOL-UP button then press and hold the POWER button until
you see tiny blue text on upper left side of screen to go into "Recovery Mode".
If you want download mode do it the same way except instead of the VOL-UP
you need to press and hold the VOL-DOWN.
Good luck with it.
Remember it;s faster to click the "THANKS" button than it takes to type "thank you"!

Misterjunky said:
You were holding down the wrong buttons.
Press and hold the VOL-UP button then press and hold the POWER button until
you see tiny blue text on upper left side of screen to go into "Recovery Mode".
If you want download mode do it the same way except instead of the VOL-UP
you need to press and hold the VOL-DOWN.
Good luck with it.
Remember it;s faster to click the "THANKS" button than it takes to type "thank you"!
Click to expand...
Click to collapse
Tried....no go still nothing

Nurmi_CEO said:
Tried....no go still nothing
Click to expand...
Click to collapse
Can you link to the specific rom you flashed. It's sounds to me like you might have flashed a bad or wrong rom.

Yes....I went to original android development and got liquidsmooth...http://goo.gl/jvdfwT. I clicked on the latest version and it's the third from the bottom . says att at the end . sorry I'm on my phone browser.

Nurmi_CEO said:
Yes....I went to original android development and got liquidsmooth...http://goo.gl/jvdfwT. I clicked on the latest version and it's the third from the bottom . says att at the end . sorry I'm on my phone browser.
Click to expand...
Click to collapse
I can't tell if the t01teatt is for your specific device. I haven't seen the t01te before. I would have expected something different. The symptoms you describe sounds like a bricked device caused by flashing a rom not for your specific device.

I assume your MDL cause you have a custom recovery.
Did you use Auto Loki recovery?
If you didn't use Auto Loki recovery did you flash the Loki doki zip ?
We need all steps you took from start to end before you rebooted your phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app

the phone was bone stock locked att i337. I unlocked it via the service hidden menu on YouTube. it worked fine.
next I rooted it with the motochopper, flashed twrp with goo manager and rebooted to recovery. my first load with twrp seemed to hang up and freeze, so I pulled the battery and rebooted into twrp.
I loaded the liquidsmooth to1att and gapps to be flashed. both seemed to flash successfully, and then I hit restart. forgot to wipe cache and dalvik, planned on rebooting back into recovery to wipe/maybe reflash and wipe cache.
the phone turned off and never turned back on.
I had a T-Mobile sim card in the entire time.
thanks and please help. sending this from my crappy evo lte

Did a little searching and I think the t01te is the note ii. Check out mobiletechvideos.com. they might be able to jtag it.

after root the phone was working fine on the stock ROM.

Nurmi_CEO said:
after root the phone was working fine on the stock ROM.
Click to expand...
Click to collapse
It's the rom you flashed after that which is causing the problem. Like I said I think it was for the note II and not the i337

Yup we only have liquidsmooth 2.10. Tolteatt is not this phone. This phone is jflteatt. Your only option is JTAG as jd1639 said
Sent from my SGH-I337 using Tapatalk

rushi.1986 said:
Yup we only have liquidsmooth 2.10. Tolteatt is not this phone. This phone is jflteatt. Your only option is JTAG as jd1639 said
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
send in for repair? only option? thanks for help

Nurmi_CEO said:
send in for repair? only option? thanks for help
Click to expand...
Click to collapse
If Odin doesn't recognize it, and I think you said it doesn't, then yea I think that's your only hope. But I'd keep trying to get it into download mode and have Odin recognize it. I haven't seen a hard brick of the i337.
Use the original usb cable, the usb ports in the back of the computer, and if that doesn't work try a different computer.

The build.prop in that ROM you flashed says it is for the SAMSUNG-SGH-I317 which is the Galaxy Note II. That's why it is bricked. Make sure you don't try to flash that one again. If you do get it to come up in download mode make sure you have the correct file before trying to flash again.
Good luck!

Nurmi_CEO said:
send in for repair? only option? thanks for help
Click to expand...
Click to collapse
Well that, or if its in warranty, send it off to samsung and play dumb! Just say something like "it turned off during firmware upgrade and never turned back on"

rushi.1986 said:
Well that, or if its in warranty, send it off to samsung and play dumb! Just say something like "it turned off during firmware upgrade and never turned back on"
Click to expand...
Click to collapse
...and end up with an MF3 phone?
It's better to send it off for Jtag like JD said. If it never had the MF3 bootloader on it, there shouldn't be a problem with them putting MDL back on it (as long as there isn't a hardware issue). To me, the cost is well worth it.

scott14719 said:
...and end up with an MF3 phone?
Click to expand...
Click to collapse
Good point! I didn't think of that..

Help: hard bricked?

I was trying to unlock my Nexus 10 with 4.4.2 through fastboot. First I booted into fastboot mode, and then issued the following command:
fastboot oem unlock
I saw on the tablet the status showed 'unlocked'. After that I just pushed the power button to try to reboot, but it keeps spinning. Even if I pushed the power button again, spinning remains. And I can't shut it down either. Is it hard bricked? What should I do now? Should I have waited for the tablet to reboot itself?

mj56gt said:
I was trying to unlock my Nexus 10 with 4.4.2 through fastboot. First I booted into fastboot mode, and then issued the following command:
fastboot oem unlock
I saw on the tablet the status showed 'unlocked'. After that I just pushed the power button to try to reboot, but it keeps spinning. Even if I pushed the power button again, spinning remains. And I can't shut it down either. Is it hard bricked? What should I do now? Should I have waited for the tablet to reboot itself?
Click to expand...
Click to collapse
You should be fine. Hold down the power button and both volume buttons until it restarts into the bootloader. Go into the Recovery Mode. Then, you'll see the little android on his back with a red exclamation mark over him. Don't panic. You need to hit power + volume down at the same time (no need to hold). It may take a few tries, but when successful, you'll see the recovery menu pop up. Do a factory data wipe. Then, after it does it's thing. Select reboot system and you're good to go.

charesa39 said:
You should be fine. Hold down the power button and both volume buttons until it restarts into the bootloader. Go into the Recovery Mode. Then, you'll see the little android on his back with a red exclamation mark over him. Don't panic. You need to hit power + volume down at the same time (no need to hold). It may take a few tries, but when successful, you'll see the recovery menu pop up. Do a factory data wipe. Then, after it does it's thing. Select reboot system and you're good to go.
Click to expand...
Click to collapse
Thanks a lot! Those steps fixed the problem... I really appreciate your help!!!

mj56gt said:
Thanks a lot! Those steps fixed the problem... I really appreciate your help!!!
Click to expand...
Click to collapse
No problem. Same thing happened to me on my N10 (and also my Nexus 5). Has something to do with it not properly wiping/formatting the data partition after unlock like it's supposed to, so you have to do it manually.

It was quite a scary experience for me! Thanks again for the kind help...
Also I just flashed TWRP 2.7.0.1, and then flashed SuperSU-v1.80 in TWRP. It said successful, but both Root Checker and Busybox indicate that it's not rooted. What did I do it wrong?

mj56gt said:
It was quite a scary experience for me! Thanks again for the kind help...
Also I just flashed TWRP 2.7.0.1, and then flashed SuperSU-v1.80 in TWRP. It said successful, but both Root Checker and Busybox indicate that it's not rooted. What did I do it wrong?
Click to expand...
Click to collapse
Hmm. That's odd. Unfortunately, I don't use TWRP, so probably couldn't help much there as I prefer Philz Recovery. I do know that SuperSU v1.80 is a pretty old version (may be some compatibility issues with 4.4.2). Have you tried downloading and flashing the latest SuperSU in TWRP? I believe it's v1.94. I would try that first.

charesa39 said:
I do know that SuperSU v1.80 is a pretty old version (may be some compatibility issues with 4.4.2). Have you tried downloading and flashing the latest SuperSU in TWRP? I believe it's v1.94. I would try that first.
Click to expand...
Click to collapse
You're absolutely right. Previously when I googled SuperSU, it came out with the version 1.80 for some reason. This time I used Google Play, sure enough it installed v1.94! And everything looks good now!
You made my day! Thanks a lot...
Sent from my Nexus 10 using xda app-developers app

mj56gt said:
You're absolutely right. Previously when I googled SuperSU, it came out with the version 1.80 for some reason. This time I used Google Play, sure enough it installed v1.94! And everything looks good now!
You made my day! Thanks a lot...
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
No problem. I, too, am familiar with that feeling you get in the pit of your stomach when you start to think you just ruined your not-so-cheap toy. Just glad I could help you get through it. Regards.
Sent from my Nexus 7 using xda app-developers app

G928V (Verizon model) menu bar/reboot issue

Every time I reboot my phone, the top menu bar does not drop down when swiped and icons placed towards the top near it I cannot press. If I turn off the screen and turn it back on, it will work, but only for a few seconds. My phone will have to sit for 2-5 minutes after reboot before the top menu bar starts to work, and then it never stops working until, yes, I reboot the phone.
I haven't seen any threads on this so I'm wondering if I have a faulty phone? It's only a few months old but I'm assuming I'm able to exchange it for the same unit considering this seems to be a functionality error. I was hoping upgrading to the latest 5.1.1 version would solve the problem but it has not.
Any advice and/or recommendations? The phone is stock and not rooted or anything.

BoostinBen82 said:
Every time I reboot my phone, the top menu bar does not drop down when swiped and icons placed towards the top near it I cannot press. If I turn off the screen and turn it back on, it will work, but only for a few seconds. My phone will have to sit for 2-5 minutes after reboot before the top menu bar starts to work, and then it never stops working until, yes, I reboot the phone.
I haven't seen any threads on this so I'm wondering if I have a faulty phone? It's only a few months old but I'm assuming I'm able to exchange it for the same unit considering this seems to be a functionality error. I was hoping upgrading to the latest 5.1.1 version would solve the problem but it has not.
Any advice and/or recommendations? The phone is stock and not rooted or anything.
Click to expand...
Click to collapse
Try factori reset and if don't work you have to install stock firm again and start fron scratch

jah2110 said:
Try factori reset and if don't work you have to install stock firm again and start fron scratch
Click to expand...
Click to collapse
Install stock firmware? I am not rooted or anything - the phone is bone stock.

BoostinBen82 said:
Install stock firmware? I am not rooted or anything - the phone is bone stock.
Click to expand...
Click to collapse
Sometimes stock firmware fail and that is the reason to install again.

jah2110 said:
Sometimes stock firmware fail and that is the reason to install again.
Click to expand...
Click to collapse
So how does someone unrooted go through the process of installing the stock firmware again?

BoostinBen82 said:
So how does someone unrooted go through the process of installing the stock firmware again?
Click to expand...
Click to collapse
Odin?
Sent from my SM-G928V using Tapatalk

thornev said:
Odin?
Sent from my SM-G928V using Tapatalk
Click to expand...
Click to collapse
Are you asking me a question or trying to be witty?

Unsure reply
Sent from my SM-G928V using Tapatalk

thornev said:
Unsure reply
Sent from my SM-G928V using Tapatalk
Click to expand...
Click to collapse
I see. Not much out there for us Verizon folks, then. I'm perfectly fine with having an unrooted phone, to be honest (though Titanium Backup would be great to have again). I may try Verizon/Samsung's default program that you can install on your PC that lets you "fix" your phone and such.

that's what Odin is.. An app with which to install firmware, rom, etcetera.
Sent from my SM-G928V using Tapatalk

Essential Phone Stuck in bootloop / soft brick?

Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Sent from my A0001 using Tapatalk

trsargent said:
Good morning all,
I am throwing this out here hoping someone can please help.
Woke up yesterday to the Essential phone logo screen powered by Android... Unresponsive. Restarted with no luck. Went into recovery mode and factory reset. Went to start up animation for an hour but nothing. Device is locked (bootloader locked) and running on the latest build from Essential (7.1.1/NMJ88C/464). I have never unlocked nor flashed anything on the phone, only OTA updates directly from Essential. Just started it up again today and says your device is corrupt. Factory reset again and now cycling between logo screen and erasing circle.
Any ideas to fix the phone? Reached out to Essential but haven't heard back yet.
Thanks all!
Click to expand...
Click to collapse
do you have an adb option in your recovery ?

nicoconepala said:
do you have an adb option in your recovery ?
Click to expand...
Click to collapse
Yes, I can get to an adb option in recovery
Sent from my A0001 using Tapatalk

trsargent said:
Yes, I can get to an adb option in recovery
Click to expand...
Click to collapse
ok then you should try to flash stock rom from essential

nicoconepala said:
ok then you should try to flash stock rom from essential
Click to expand...
Click to collapse
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Sent from my A0001 using Tapatalk

trsargent said:
Am I able to do that with the device locked? Oem unlocking is not turned on I believe. I have never flashed anything on a phone before
Click to expand...
Click to collapse
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions

Wrong section.

NaterTots said:
You don't need to be unlocked to adb sideload the Oreo beta builds from essentials website.
Just follow their instructions
Click to expand...
Click to collapse
Gave it a try, but it didn't resolve the issue. Got the your device is corrupt message. Any other ideas? Thanks!
Sent from my A0001 using Tapatalk

I'm searching for answers too! My essential is doing the dotted box to the dotted circle spin back & forth over & over ! I saw the dead robot with exclamation mark . The only thing on the essential website is to wipe phone ! Help. If the person that made this phone do this to people dies please let me know, so I can smile during this stressful time . If they r still alive I hope they are in agony over something thx!