Database Users

Display is Reversed!

After several unsuccessful attempts to mount 3.1 on my Xoom, something seems to have caused the display to reverse. That is, the display is a mirror image of what it should be! This starts with the boot-up image of the Motorola Icon and carries all the way through till it's up. Several restarts have failed to resolve it, and it has me in a bit of a panic.
Have I just bricked my Xoom? Has this happened to others? Ideas? Suggestions? There's nothing on it that I have to save, so I could re-flash it, but I am not sure if/how to do this.
Many thanks in advance for any suggestions/fixes!
Phillip

Its not bricked if it boots...
That is strange though. May have to reflash stock images.

Try bringing everything back to stock?

Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.

Gr3yghost said:
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Click to expand...
Click to collapse
No push the images using adb

I figured it could be done. Could you please point me to a thread explaining how to push images using adb?

Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942

djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
That's great, thanks for the info. I'll have to do this later today when I am at a PC (now at a Mac).
Any ideas about why this would happen in the first place? I've looked through the forums but haven't seen any other threads about this issue. It may be fixable with a reflash, but it sure was 'easy' to 'break' today without even knowing why...:^(

djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
I have the 3G model. Looking at the instructions in that post, I have to admit I am not sure about a few (like most!) of the steps. It may become more apparent when I am doing it, but right now I am not clear as to where these steps take place.
[edit] Ok, I have just done some more reading and it appears I have quite a bit of work ahead of me, and that's just to get back to square one. Dang this was too easy to mess up!

I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.

djsaad1 said:
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
Click to expand...
Click to collapse
Sorry for the confusion, but I haven't been using adb. I was trying to install the update manually with a usb data stick and the microsd cord that came with my Xoom. That's how I got myself into this pickle...way too easy it was!

Sent it back
Thanks to all who helped here. I ended up taking it back to Verizon and asking for a replacement. This they did, and even shipped it overnight at no charge (though I had to ask them to do that--they were going to charge me). The fellow at the counter was as perplexed as me. Apparently this is not a common problem.

Touchwiz Update bricked my non-rooted Tab (static lines across screen)!

I decided to go ahead with the TW firmware upgrade. Everything seemed to be going fine until I tried to install it and it told me there was an error and I needed to hook it up to Kies first. I had already been using Kies with it on my Macbook for a couple weeks now so I went ahead and plugged it in. Kies recognized it as usual and all the information came up.
So I went on and tried to install again and it said it needed to reboot.
It reboots and comes to the Samsung Galaxy Tab 10.1 screen like normal (right before it starts the galaxy animation). Next thing I know it comes to a screen that looks like the attached images! I immediately unplugged it from Kies and shut it down. Every time I start it back up it does the same thing. I honestly have NO idea what to do. I can't even return it as it's past the 14 day period and I (stupidly) didn't buy Staples' bogus $160 insurance.
I was not rooted before. This was a stock tab that I bought at staples. It had the firmware 4.24 when I bought it, I think.
Please, any help is appreciated. I tried doing firmware recovery in Kies but the pop up comes up in Korean and I have no idea what it says...
Edit: More info. I'm not the only one with this problem. Two other people have posted on AndroidPolice about this. http://www.androidpolice.com/2011/08/04/samsung-galaxy-tab-10-1-wifi-touchwiz-ux-update-is-now-live/
The software is definitely running underneath all that mess but it's literally impossible to see what is going or to touch anything.

I guess this thread is about the same issue
http://forum.xda-developers.com/showthread.php?t=1203610

Thanks, I'm checking the thread out now. I probably should have searched more than just Google before posting but I freaked out when it happened.

No need to freak out . we have xda and dev to solve all our problems

i have exactly the same problem as you... what should i do now?

I get the same screen but after rebooting! pfft it's making me really sad :\

I'm sorry but I tried reading this http://forum.xda-developers.com/showthread.php?t=1171089 and couldnt understanding what should I do!
What CWM + my device is not rooted, all I could understand is that the thread contains instructions on how to root your device..
I just want my normal screen back!
Please tell me what to do in simple english :\

And now I did a wipe and the stripes are gone, but the screen is black instead :\ still not working. Please help me!

Are you sure you didnt sit on it?

Amal Kadi said:
I'm sorry but I tried reading this http://forum.xda-developers.com/showthread.php?t=1171089 and couldnt understanding what should I do!
What CWM + my device is not rooted, all I could understand is that the thread contains instructions on how to root your device..
I just want my normal screen back!
Please tell me what to do in simple english :\
Click to expand...
Click to collapse
haha i had the same problem go look at my threat that was posted above. in thier someone posted instructions on what to do the link you posted contains the download to the things needed heres a basic rundown of what you need to do
install clockwork recovery mod "CWM" to replace your bootloader.
download and install stock 3.1 and you should have your tab back to normal.
my help thread has the instructions to instal CWM

tonyurquiza said:
haha i had the same problem go look at my threat that was posted above. in thier someone posted instructions on what to do the link you posted contains the download to the things needed heres a basic rundown of what you need to do
install clockwork recovery mod "CWM" to replace your bootloader.
download and install stock 3.1 and you should have your tab back to normal.
my help thread has the instructions to instal CWM
Click to expand...
Click to collapse
So I need to follow all the steps for rooting except the last one which is the actual rooting? Great thanx! Do I need to use Kies? My current computer is Mac but I guess I need to download those things to a Windows machine to make it work, right?
Thank you very much

I had the same problem. I upgraded the update on my non-rooted tablet and got the funked up video mess. Per instructions from Samsung support, I hard booted to the recovery menu (power+vol down, then power up, down on download screen) and did the factory wipe. After that I ended up with the black screen. I could tell things were working in the back but couldnt see a thing. I figured I would throw it on the Kies and it saw that there was a factory upgrade so I let the Kies run through it and it works fine now.
Dont know if this will help w/other but it worked for me.

[Q] Viper4Android and Bricking

Figured I would be a lurker forever, but I guess my hand was forced.
Well, I was annoyed by the sound on my Note 3 and some applications with no equalizer, so I tried a couple out with very limited success. Lots of people suggested Viper4Android as working better than the random ones you could find on Google Play. So I tried going to what looks to be the official thread. The installation seemed simple, aside from modifying a build.prop file(still simple but possible to mess up).
Long story short, I restarted the phone when the application told me to and was greeted with a permanent white 'Samsung Note 3' text-logo. I never get to see the Samsung or Sprint carrier video-logo. Holding down power merely reboots the phone after a few seconds. Seemingly the Power/VolDn/Home combo still works for download mode... but at the moment I don't know what to do with that access.
I would try posting on the official thread, but being a lurker, I don't have the required 10 posts.
Searching the Viper4Android thread, I only see happy Note3 people... and no one at all having the extremely bad luck that I have had. I don't even see any particular warnings about this being possible. The only thing I can think of is the driver that it installs and the build.prop file. If something seriously went wrong there with the audio, it could possibly prevent the videos from playing and the boot process wouldn't continue.
I'm at a temporary loss and thought I would post somewhere to get my options rolling as I think. Primarily, given that Viper4Android was the last thing that I did before this happened... is there something different I should be looking for rather than a generic method of undoing a soft-brick?

jljtgr said:
Figured I would be a lurker forever, but I guess my hand was forced.
Well, I was annoyed by the sound on my Note 3 and some applications with no equalizer, so I tried a couple out with very limited success. Lots of people suggested Viper4Android as working better than the random ones you could find on Google Play. So I tried going to what looks to be the official thread. The installation seemed simple, aside from modifying a build.prop file(still simple but possible to mess up).
Long story short, I restarted the phone when the application told me to and was greeted with a permanent white 'Samsung Note 3' text-logo. I never get to see the Samsung or Sprint carrier video-logo. Holding down power merely reboots the phone after a few seconds. Seemingly the Power/VolDn/Home combo still works for download mode... but at the moment I don't know what to do with that access.
I would try posting on the official thread, but being a lurker, I don't have the required 10 posts.
Searching the Viper4Android thread, I only see happy Note3 people... and no one at all having the extremely bad luck that I have had. I don't even see any particular warnings about this being possible. The only thing I can think of is the driver that it installs and the build.prop file. If something seriously went wrong there with the audio, it could possibly prevent the videos from playing and the boot process wouldn't continue.
I'm at a temporary loss and thought I would post somewhere to get my options rolling as I think. Primarily, given that Viper4Android was the last thing that I did before this happened... is there something different I should be looking for rather than a generic method of undoing a soft-brick?
Click to expand...
Click to collapse
looks like a factory reset ,volume up, power home, factory reset

Did you choose the correct driver to install?

jaythenut said:
looks like a factory reset ,volume up, power home, factory reset
Click to expand...
Click to collapse
Even losing absolutely everything doesn't really bother me. Only hard-bricking does.
munnarg said:
Did you choose the correct driver to install?
Click to expand...
Click to collapse
I had very few choices. I used the ViPER4Android_4.x_2313.apk since I have Android 4.3; a no brainer. Once installed and open, the changelog popped up, SuperSU asked to authorize, then V4A asked to install the driver. By this point I had already done the build.prop modification so I clicked Yes. It told me that it would automatically detect my CPU type which matches what the official thread says. It then prompted me to select the driver profile(?) with the options of Battery Saving, High Quality Mode and Super Audio Quality. Since the thread didn't give any suggestions, I went with the middle-ground of High Quality Mode. After the selection was made, it told me to reboot. I closed the application, held the Power button and selected Restart(then OK). And was stuck there.
Looking at some other various threads, it seems that improper modification of build.prop can indeed cause the type of bricking that I am seeing. I'll have to try V4A without that one step since it looks like it was added in after the fact... and in some cases optional if the lines to modify don't exist.

Don't think you had to mess with the build.prop at all. I sure didn't do it.
SwiftKey Flowed from my tiny Galaxy Note 3

munnarg said:
Don't think you had to mess with the build.prop at all. I sure didn't do it.
SwiftKey Flowed from my tiny Galaxy Note 3
Click to expand...
Click to collapse
I would have not done so if it had not asked me to.
http://forum.xda-developers.com/showpost.php?p=39156718&postcount=2
1. ROOT your device.
2. Install busybox if doesn’t come with root.
3. Modify build.prop (Thanks [email protected])
a. Open up /system/build.prop in text editor using any file explorer with root access.
b. Change the line (If you can’t find these lines, skip this step.)
Ipa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Click to expand...
Click to collapse
As a side note, factory resetting doesn't seem to affect this. Doing so says that it's wiping out /data and /cache. Where as what I modified was in /system. Some of my other reading proposed that re-rooting will undo those sorts of changes. Looks like I'll have to go down that research path.

I guess it should be unsurprising to me, but I never encounter only small problems.
Factory resetting in recovery mode and re-rooting in download mode, while successful, do not allow the device to boot past the first screen.

jljtgr said:
I guess it should be unsurprising to me, but I never encounter only small problems.
Factory resetting in recovery mode and re-rooting in download mode, while successful, do not allow the device to boot past the first screen.
Click to expand...
Click to collapse
if its still not working download your firmware from www.sammobile.com and flash with odin

jaythenut said:
if its still not working download your firmware from ----sammobile---- and flash with odin
Click to expand...
Click to collapse
I'm willing to try... but will that really replace more than what the CF-Auto-Root image has? Nevermind... just looked at the file size. That certainly changes a lot more than the CF-Auto-Root image. It'll take me a while to get it off of their free file hosting, probably.

Well, I have a blank but working device now... and that's what really matters.
Reading around... if I were to make a wager that I can't collect on, I would say that I ran into a bug with ES File Explorer. I read someone else bricking their device in the same way editing the same file. ES-FE makes a backup by renaming the file, then fails to save the new file. I swear I saw it do this once before on a less critical file and I was annoyed to have to do the cp through terminal. I didn't hit refresh to make sure it did it correctly... I just assumed when it said it saved, it saved.
Thanks for the responses. Back to lurking!

Just for info, V4A is running flawlessly on my N3. All I did was install the APK, open it, install driver as prompted and restart!

Samsung GalaxyNote 2 AT&T - Always Stuck On Galaxy Note II Screen

Hey all,
I have read all over the place but I honestly get more confused the more I read. I wanted to switch to another OS since my phone was starting to become bogged down (too many pictures, videos, old files, etc etc etc; My phone is my work tool since I'm a field sales engineer)
So I went ahead and rooted it with ODIN 3 v1.85 and I317-UCUBMK6.tar.md5. I also installed TWRP although I have no clue which version it is. I suppose it's the latest one. My bootloader is 4.3 (I think; I go to About Device and I see the android version 4.3)
I always do the full swipe and a NANDROID back up. However, when I flash a custom ROM, I always end up stuck on the Samsung Galaxy Note II screen. It won't go.
I have tried to install the following ROM's:
DN3 - Always says "Failed" when I try to flash, even when following instructions of reboot recovery and flash again.
JEDI X 20 - Go through the entire aroma installer - it installs - asks for reboot - when rebooting, stuck as Samsung Galaxy Note 2 screen
and it pretty much happens with all of them. I have decided to back to stock (because I was a retard and accidentally deleted my NANDROID backup) and now I find my WIFI is broken.
I pretty sure this has all been discussed in various threads but I rather bring it all into one so that all that are having the same issue as me (I read a lot of people complaining about this issue with very scattered replies) can have a single thread that addresses how to fix this.
Any help will be greatly appreciated.

Wrong Section for your Note II

McLaren__F1 said:
Wrong Section for your Note II
Click to expand...
Click to collapse
Thanks for letting me know. Where should I post it?

You'd get more replies here
http://forum.xda-developers.com/galaxy-note-2-att

LGSmartcard Service Error

Hi,
I have an LG V20 H910-10c (Nougat 7.0) and I am having an issue that I am praying someone can help me out with. I have already tried a Factory Wipe/Reset and Wipe Dalvik/ART & Cache and have Formatted Data to remove Encryption, etc..
Timeline: The phone worked fine in all aspects before Rooting it.
After Rooting it, I had this issue.
I then tried a Factory Reset and got stuck in a TWRP Bootloop.
I fixed the Bootloop issue with a Reset (Yes then Yes).
The issue is still there.
ISSUE: When I boot into Android, I get the following message;
"LGSmartcardService has stopped"
.....and I cannot use my External SD Card (TWRP sees it fine, I Flashed SuperSU from it).
I have Googled my brains out and simply cannot find any suggestions, except to perform a Factory Reset, which I did and that's what put me into the Bootloop and I reset the way you said and now it boots up okay, except that error message is still there.
I have not put any apps on the phone or anything. It's factory fresh (except for Rooting it).
I hope I'm not violating any rules by posting this, but the page I used to Root it has a REAL SMALL downloadable file called "V20-Root.zip" that contains everything, including the Batch files with the steps that they perform in them. I did NOT use the ROM, as that's ONLY for Sprint users and my phone is an AT&T model (Unlocked and my Carrier is MetroPCS). But I put it here, just in case someone wishes to bless me by taking a look and seeing if there's something to note. I am not a coder by any means. I do understand some basics, but I couldn't see anything that would cause this sort of problem. I did NOT install the ROM listed, because it's for Sprint users ONLY and I have an AT&T (Unlocked, using MetroPCS) H910. Here's the link to the page:
https://tinyurl.com/yacdendm
I really need my Ext SD Card to be seen! I use it extensively and it would be a real hindrance not to have it! Plus this is my ONLY phone (no landline) and I am disabled and must run everything, including my home network and laptop, etc. from it and I need its space for things I have to have available on my phone to do things that I need to do, so any help would be appreciated GREATLY!
Please Help Me and Thank You!
Dave

If I see this post one more time I think I'm going to puke, ugh
Sent from my LG-H910 using XDA Labs

cnjax said:
If I see this post one more time I think I'm going to puke, ugh
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
This is my fault. There were 3 main sections to choose from and none of them fit exactly and I wasn't sure where to post it so I did all 3.
I guess I got anxious, as this phone (my only one) is my lifeline! I am disabled and everything runs from it (I'm stuck in bed), including all of my network and its computers, as well as home type stuff and I process videos, etc (needs lots of free space) and so I absolutely need my Ext SD Card working for some of the stuff I need to do. So yea, I guess I have been getting a bit anxious.
I am genuinely sorry for any etiquette that I may have broken. My apologies, please.
Mod, please remove them from where they shouldn't be and leave only the 1 that is where it should be.
Sorry Again and Thank You Again,
Dave

Instead of searching google. You should check out the forums. Just a quick search and I found useful info:
Code:
[url]https://forum.xda-developers.com/v20/how-to/stock-att-h910-stock-recovery-boot-image-t3528060[/url]
[url]https://forum.xda-developers.com/v20/how-to/h910-att-lg-v20-root-talk-t3523515[/url]
I would suggest to search for updated TWRP of your model. Also to use Magisk instead of SuperSu.
Hope you get your device working :fingers-crossed: :good: