Okay all went well with me and my galaxy tab for two days, and then I wanted to install a ZAGG invisble shield on my 10.1v.
All seemed fine until after the application the invisble shield appeared damaged and I had to take it off 12-24 hours later. Which resulted in some sort of fog under the glass so I can only assume some of the application fluid got into the tab through some sort of crack.
I've tried rice and everything and the tab was okay for the most part but I had to flash back to stock because somehow after the damage my 3g wouldn't work.
But now the worst part, the on/off switch won't work anymore! (3g does though ;P). It's completely blank, I can't start the tab anymore nor can I flash another rom trough cwm to check if that is the problem..
What can I do..?
Elaborate what steps or link for thread you folowed!
I had to flash back to stock because somehow after the damage my 3g wouldn't work.
Click to expand...
Click to collapse
1.When connected to pc and attempted switch on, any connection sound is heard from pc?
2.Get it replaced if under warranty.
3. Try going into recovery mode with power and the volume down (left button in landscape
4.try this link from Putting tablet in nvflash ADX mode and loading clockworkmod recovery,
http://forum.xda-developers.com/showthread.php?p=15608722#post15608722
Trying to locate the defect, if its the display panel(get replaced) or firmware issue(bricked). How are you sure that the 3g works if the screen is blank?
After I flashed back to stock 3.1 I was able to start the device once and confirm that the 3g was working.
no sound can be heard of a device that is connected when plugged in the computer.
It turned on after some plugging in and out of the pc by itself a few minutes ago so the screen isn't the problem..
And I can't flash through cwm because the on/off switch doesn't work so it also doesn't work when trying to select things in cwm..
Get it replaced or take to the local samsung service center! I believe putting it into rice sack was not a good idea! Remove the sim, if tab is on, try factory rest! Or adb debugging mode to run adb commands and try rebooting into recovery via commandline on computer or via mobile terminal on tab.
Related
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
itsjuztin said:
Alright, I was having problems with my CyanogenMod, and I went to restart my phone because it kept force closing all my apps (including system processes) and it got stuck on the Vibrant screen and never started up.
I went to Nandroid to restore my backup I made before CM7, and it must be corrupted, because it refused to restore, so I said to hell with it and decided to start from scratch.
Long story short, I ended up flashing the wrong ROM by accident because I got confused between the Samsung Vibrant and the Samsung Galaxy S 4G, and somehow I got my phone stuck at an AT&T World Phone logo, and it won't do anything else. I've tried entering recovery AND download mode, and neither will work. Also, when I plug my phone into the USB port, the charging indicator gets stuck at the very beginning, showing a pinwheel and a greyed out battery.
I ordered a USB jig, hoping this would help send my phone into DL mode, but I'm still open to any ideas anyone has until then. I haven't had a phone for a couple days and its killing me!
Click to expand...
Click to collapse
Here's some tips:
1. NEVER restore non-cm7 nandroid backups on a cm7 based rom.
2. Flash stock JFD with repartitioning checked to go back to stock.
3. Reflash vibrant bootloaders. You may have some captivate bootloaders or a mismatched param.lfs that's causing the AT&T bootsplash. It could be one or the other and mismatching captivate and vibrant bootloaders or params could lead to a brick so just flash the vibrant bootloaders since it contains both bootloaders and param.lfs.
4. DL mode depends on the bootloaders you run.
Froyo bootloaders-------------
1. Volume up and down with USB inserted and with battery disconnected
2. Insert battery without letting go of buttons
Gingerbread bootloaders-------
1. hold power and volume up with the battery inserted and with the phone powered off
2. connect USB to pc when booted into DL mode.
P.S. Can you take a picture of the front and the back of the phone so I can identify the kind of phone you are using at this moment?
The name you are using for the device you have is kinda confusing me.
I'm pretty sure i have attempted every solution on here (XDA) and elsewhere to troubleshoot my problem. I am hoping it is obvious, but i've put hours into this and i could really use some help!
My tablet is (or was) a Verizon 4G LTE Galaxy 10.1
I had successfully rooted it when i first got it using Odin...i flashed a ROM...can;t remember which one (obviously a wrong one) and ever since it has been rather temperamental.
Over the course of the past week i have been to APX and back... Heimdall (which i am pretty sure i am not doing correctly) to attempting to flash firmware..stock roms etc...
I don;t know whether it is a driver issue, or if i need a stock rom or to flash firmware....but here is where i am at now.
If i try to power up normally...the Samsung galaxy tab logo bootlader flashes for a sec or two...the screen then either goes black...and repeats a few times...or sometimes it flashes the logo and the backlight stays on until i turn it off.
(Seems to be a fairly common problem)
If i hold the volume up and power together...i can get to the Odin download screen with the flashing droid and the midget droid that appears to be walking away from a trash can.
HOWEVER, when i plug the tab into my laptop (windows 7 x64) (i also have access to a (windows 7 x86) and my girlfriends xp machine. I've tried on all mostly on my x64 machine.
Heres the thing.
When i power down...sometimes just pressing the power button once or twice...sometimes, while off i hold the volume down button for a few sec..and all of a sudden the comp reads the device and i can get open ODIN...get the yellow COM thing...but never seem i always get the same error message...can not open/find com/port...
so i can get into odin on my comp with a black screen on my device...or i can get to download mode on my device and my machine wont recognize it.
I seem to have inherited a little bit of everyones problems on here...
Please tell me that there is hope for my tablet...please help? I'm sure you can imagine my frustration. TY.
joshualectric said:
I'm pretty sure i have attempted every solution on here (XDA) and elsewhere to troubleshoot my problem. I am hoping it is obvious, but i've put hours into this and i could really use some help!
My tablet is (or was) a Verizon 4G LTE Galaxy 10.1
I had successfully rooted it when i first got it using Odin...i flashed a ROM...can;t remember which one (obviously a wrong one) and ever since it has been rather temperamental.
Over the course of the past week i have been to APX and back... Heimdall (which i am pretty sure i am not doing correctly) to attempting to flash firmware..stock roms etc...
I don;t know whether it is a driver issue, or if i need a stock rom or to flash firmware....but here is where i am at now.
If i try to power up normally...the Samsung galaxy tab logo bootlader flashes for a sec or two...the screen then either goes black...and repeats a few times...or sometimes it flashes the logo and the backlight stays on until i turn it off.
(Seems to be a fairly common problem)
If i hold the volume up and power together...i can get to the Odin download screen with the flashing droid and the midget droid that appears to be walking away from a trash can.
HOWEVER, when i plug the tab into my laptop (windows 7 x64) (i also have access to a (windows 7 x86) and my girlfriends xp machine. I've tried on all mostly on my x64 machine.
Heres the thing.
When i power down...sometimes just pressing the power button once or twice...sometimes, while off i hold the volume down button for a few sec..and all of a sudden the comp reads the device and i can get open ODIN...get the yellow COM thing...but never seem i always get the same error message...can not open/find com/port...
so i can get into odin on my comp with a black screen on my device...or i can get to download mode on my device and my machine wont recognize it.
I seem to have inherited a little bit of everyones problems on here...
Please tell me that there is hope for my tablet...please help? I'm sure you can imagine my frustration. TY.
Click to expand...
Click to collapse
Have you tried rhis method
http://rootzwiki.com/topic/7718-romleakodineg01-factory-stock-odin-image-vzw-lte-tab-101/
Sent from my GT-P7510 using Tapatalk
...
Thanks for the quick reply. I think i did try this at one point...the problem still stands...when i am in odin dl mode on my tab...the com tab wont turn yellow and comp wont read my device.
If i do it the other way....with a black screen...it wont be able to communicate or find the port. ...but ill try again right now.
Nope....epic fail. There has to be a solution, right?
As long as you can get into download mode you should be able to fix it. Most likely the issue is not your tab but the drivers on your computer.
I spent the better part of a day frustrated trying to go from the leaked 3.2 to official 3.2 having issues similar to you with Odin. Funny thing is for me the PC somehow ended up not recognizing the tab on the USB port I used to flash on but would on others so I simply swapped Ports and continued. Little did I realize that although things seemed okay that issue was a symptom and Odin was now flashing corrupted info onto the tablet.
A simple reboot of the PC fixed things for me. That you have tried other machines though is worrisome. Still there's a chance it still is a driver issue so I would check drivers on the PC and perhaps install kies if you don't have it to see if the drivers with kies help.
Since you're on the Verizon tab flash back to stock 3.1 and flash stock recovery. Then let all the OTA updates run. After that all you need to do is flash cwm and Pershoots kernel along with superuser to be rooted. There is no better ROM for our Verizon tab than this and all wifi ROMs are incompatible with it.
Still, no luck. When i am in download mode on my tab....my computer doesn't recognize it. When I just power up and and plus it in, the screen goes black but the computer sees the device as well as ODIN. However sometimes it is recognized as APX and sometimes it is recognized as a Samsung android device... usually with one or two driver errors.
So, it seems obvious that it would be a driver issue... i've tries kies, and as many variations of drivers i can find.,.. when in APX mode i try to flash using the nvflash method in cmd or heimdall, otherwise i try ODIN and it seems to be successful until the "setup connection" point.
Is there a way (if it is even something i should do ) to get drivers on my device in its current state?
Im at a loss...i know this thing can be resurrected...everything just seems so backwards. Any thoughts?
I know that this is a very basic question, but do you have USB Debugging enabled?
George
No way to check now, as he says the tablet doesn't boot any more.
It sounds like a driver issue for sure, and to be clear here the ONLY requirement that I know of when flashing with odin on the TABLET end is for it to be in download mode waiting for usb BEFORE being plugged in. So when I say driver issue Im talking about on the PC side here. Have kies installed just to get the drivers, fire up odin and get the tab into download mode while unplugged. Plug it in and watch odin to see if the com port status lights up. If not swap usb port and repeat. Do not use a hub and ypu may want to remove unnecessary usb devices too just to see.
Hi
I used the factory reset function on my tab a couple days ago to delete all apps and such and upon reboot it was stuck at the slowly flashing Samsung logo and would proceed no further. I left it for a good hour and a half in that state before I tried hard resetting it but no dice. I've had it do this before when I first rooted it, but unlike that time it doesn't replay the whole boot animation, just the logo part at the end of the animation. I managed to get it in clockwork mod or bootloader whatever that function is and cleared all the caches and did a reboot recovery (i believe thats what it was called) but upon reboot it did the same exact thing. So after that I gave up and went to bed, but the next day when I went back at it again it wouldn't even turn on. After messing around with the power button and volume button trying to get into recovery mode it finally turned on but went to the battery screen with no other actions. I've tried several times to get it into recovery mode but it either wont turn on or it just goes to the battery screen. I have it plugged into my pc at the moment and apparently it is in recovery mode or something because Odin recognizes it. Says [0:COM3] and the box is yellow, but the screen never turns on though when holding the power button and volume button while it's plugged into a pc, the pc recognizes something plugged into the USB slot. My pc is only recognizing it as a modem and will do nothing else with it.
I have the Starburst rom and the overclocked kernel installed and would like to either revert it to stock rom or perhaps the AOKP rom, milestone 6. Is there any way to do this if I can't boot it into a state where I can access the SD card on my pc? All the guides I've found always require I put files on the sd card to flash in clockwork recovery mod. Thanks for any assistance
Edit: Solved it myself, feel free to delete this post. Thanks!
Hi,
I've got Lenovo s650, rooted with a custom rom (MIUI). All was perfect for weeks but few days ago it started randomly going off. Then I noticed that sometimes when I listen to music it crashes (making the music freeze and repeat same note for like 10secs) and shuts down. I thought it could be related to some apps but since I was very busy I didn't do anything about it.
Now today I noticed that my phone suddenly lost network coverage (in area where I always use it). I tried airplane mode on/off but didn't help, so I powered off and thought I will do hard reset when I get back home. However since then the phone is completely dead. Can't get into recovery, if I plug into USB nothing happens, if I take out the battery the red light turns and it goes to "META" mode for few secs (as it's intended to) but I can't download anything into it as I get some DRAM error in Upgrade /flash/ tool.
Funny thing that somehow I was trying all the combinations Volume up/down/both + power and at some point I randomly managed to turn it on so I was gonna make a backup of my stuff but it froze and shut down again. Now nothing works......
Any ideas what happened? :/
Some additional info:
I've got TWRP recovery (however I am unable to re-download it again via flashtool because of DRAM error).
I tried getting into adb but I am not sure if it's possible when the phone is off (tried volume button combinations with battery in and out but nothing).
Also when my phone is with battery and I put it into USB, pc recognizes it as "MTK USB Port", but it keeps disconnecting and reconnecting every 5 seconds. Tried to replace it with adb USB driver but didn't work.
Not having a phone I'll probably give a "Format all" option a shot in flash tool... either gonna brick it forever or fix it..
Edit1: Can't even format due to DRAM error....... :/
Edit2: This is so bizarre... I managed to connect my phone a couple of times in Mediatek preloader mode so the flash tool started flashing the rom, but stopped in a few mins unable to format something because it's protected.
I also managed to turn on the phone a couple of times and tried connecting via adb, but once I grant root permissions, adb shell on my pc cannot find device anymore.
It seems like either a hardware or kernel problem but I know nothing about either of them..
Edit3: I don't know how but I fixed it. Phone seems to be fine for now
Edit4: After 1 hour of working the phone died in exactly the same way.... And so this 6-week old phone will be going to rubbish bin. End of my blog.
As title. My phone is stuck in the emergency recovery page: use the emergency recovery function in the smart switch PC software. I cannot turn the phone off, I cannot go into recovery, and I cannot go into download mode.
I attempted to root the device using kingo but it failed. It was my first time rooting a device. So my phone essentially got stuck when it restarted at the "Samsung S6 Edge: Powered by Android" black screen. I then managed to "recover" the device by using Odin and flashing a stock firmware.
So I got back into the device and tried to change the settings back to what they were before. I disabled USB debugging (Bootloader option is not available for my mode, SM-G925I).
Then...having the itchy hands I do, I checked out the security portion under settings, and I saw that there was "unauthorized changes made". The program suggested that I restart my phone so as to get rid of those changes..which I did. And since then, it has been stuck again.
I actually took a trip down to the service centre where the tech actually managed to turn the device off, and I was told that warranty was void. In any case, when I returned home I tried to flash the same stock firmware that I used earlier but ODIN failed. I redownloaded the stock firmware for 925I from a couple of places and they're all 1.5gb+; but every time I try to even load the firmware Odin just hangs and I have to end the task...
Right now, I'm attempting to use smart switch and the emergency recovery function but it has not worked the first time, at the second stage where installation actually takes place. While the phone was connected, window's kept giving the notification that the device was not recognized. I'm giving smart switch a second desperate try and this time round I'm receiving no notifications from windows (so I suppose that's a good thing..). But assuming that smartswitch does not work? What are my options considering:
1) Failed root using kingo root (one-click stuff..wish I had known better)
2) USB Debugging is not enabled
3) Unable to enter recovery mode
4) Unable to enter download mode (but a download bar appears when I attempt to use Odin at the emergency recovery page)
5) 5.1.1 android system
6) Phone is not recognized by smart switch (might be because it is in the emergency recovery mode)
Really at a loss here..I'm helpless with tech and I really should have just left well alone. Jailbreaking was so much easier...Samsung quoted me $200+ for the replacement of the motherboard of the phone, which I will probably take up if the situation is really beyond repair.
Thanks in advance..
johnlim2345 said:
As title. My phone is stuck in the emergency recovery page: use the emergency recovery function in the smart switch PC software. I cannot turn the phone off, I cannot go into recovery, and I cannot go into download mode.
Really at a loss here..I'm helpless with tech and I really should have just left well alone. Jailbreaking was so much easier...Samsung quoted me $200+ for the replacement of the motherboard of the phone, which I will probably take up if the situation is really beyond repair.
Thanks in advance..
Click to expand...
Click to collapse
Can you still charge it?
Use the original root file you downloaded to re flash the drive. Hope that helps it did for me.
Dakhandokar said:
Use the original root file you downloaded to re flash the drive. Hope that helps it did for me.
Click to expand...
Click to collapse
bit late