[Q] Tablet doesn't turn on - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hi,
I have successfully rooted my GT P7500 and installed ClockWork Recovery. When I tried to create a backup in it, the backup process got stuck. Probably because lack of free space during the backup process as there was a lot of data. So I tried to reboot the device - first time it booted up and got stuck on homescreen. So I had to reset it. After reset the device does not start at all - display is off (no reaction), battery is fine (was around 50%), even putting on charger does not do anything to show up on display.
Is there a way to do something about it? A special "reset" or anything?
Thank you for any advice.

Related

[Q] note stuck on Samsung + model screen. details inside.

Hey. Been lurking this forum since before i got my NOTE.
ran it stock for a bit noticed issues.
Rooted thru Odin3 V1.85 (DA_G + zaptor99 's methods)
things worked ok cept for streaming video online (not youtube)
in an attempt to freeze my social hub and answering machine notification (its disabled on bell's side but i still have a notification that won't go away)
I assume i button mashed or did something wrong went i went to freeze those apps.
the note acted like it crashed, slowed the hell down and froze.
upon restart, i get past the first samsung screen, into the second that also has the model number in is (in my case SGH-i717M)
this is where the phone get stuck up on now.
Useful info:??
I can get into Download mode. I can get into TeamWin Recovery.
But the phone doesn't seem to get recognized by Odin3 anymore (v1.85 or v3.04 )
So would there be a way to restore thru Teamwin's recovery by using my SD card and loading it with the required files?
or do i have a brick on my hands?
thanks in advance for any help whatsoever!
It sounds as if you have frozen your launcher, and of course this means the device wont boot past the splash screen.
If you have a nandroid backup of the rom prior to the freeze, you can push that image back to the device using recovery. (wipe first)
You can also push the exact same rom image you are currently using, (rom image only) to the device via recovery, and correct the issue as well. (full wipe)
Either way, fully wiping the device before a nandroid restore, or fresh rom install is always a good idea.
You are very far from bricked...
Good luck....g

[Q] Flashing issues

Hi, got some difficulty flashing.
Just trying to flash liquid smooth onto my old s3, but having some difficulty.
Previously loaded with a temasek rom and with devil recovery, pretty sure that the partitions had been reformatted to f2fs to boot. Well, I tried to reformat the partitions to ext4, complete wipe, install rom, gapps and then wiped cache and dalvik. Tried many times to boot, got it to load once but resulted in an unresponsive touchscreen (still works in recovery though). I didn't do anything specific to get it to boot this time, it just hung on the Samsung screen for over 10 minutes, saw a liquid smooth writing (which I thought was a boot loop) for about 20 minutes and then the intostart screen but unresponsive. Needless to say something isn't right, and it can't take half an hour just to reboot the phone!
I would go through odin, and start from scratch, but it's no longer my phone and the phone is no longer recognised by my pc (I guess the connector has been damaged, I had to get the volume buttons repaired this morning just to access recovery!). It can charge, just not specified under device manager on the pc... therefore can't seem to use odin at the moment.
Question is does anyone have a solution? Is there a specific recovery (do you have to use TWRP)? or am I doing something wrong? I've loaded lollipop onto my xperia z2, and a friends galaxy s4 but I'm facing issues with the s3... I have no idea why it just won't boot but if anyone could give me a hand it would be greatly appreciated! I've been banging my head against the wall for hours now! The only way I can get the phone to work again is to restore from my backup... something is definitely wrong here but for the life of me I can't figure out what!

Galaxy S2 Crash

Hi all,
I've managed to royally mess up my Galaxy S2, and I could really do with a bit of help! It was running a rooted stock rom.
The problem started when I attempted to install the Orange Signal Booster using instructions from this thread. I think the killer was replacing default.prop in system.
At this point the phone would crash a couple of seconds after the unlock screen appeared. I could get as far as dragging down and clicking settings before the entire thing hangs. I got similar results in safe mode. I also tried wiping cache etc in CWM but to no avail. I'm backed up, so I tried a factory reset, but I'm having a similar issue. The language selection screen appears, I press start and the phone freezes again.
I'd really appreciate some help!
BTW, my phone's USB port doesn't work so I'm looking for a solution that can be done within recovery. This is a separate issue and I believe it is unrelated as I have managed fine for over a year.
With a dead usb port you're pretty much screwed. The best and fail proof solution is to reflash stock rom using odin because it will wipe and reflash all partitions that were used before.

Retrieving data from soft-bricked S3

Hello all,
I have a soft-bricked Galaxy S3. I have no idea why it soft-bricked. I was using Google Maps to find a place and put it in my pocket. When I got there and took the phone out, I was greeted with a black screen with the white Galaxy S3 I-9300 logo that wouldn't go away. Tried taking the battery out then putting it back in and powering on: no dice.
I cannot access Recovery Mode with the Volume Up shortcut; the device bootloops. I can only access Download Mode with Volume Down shortcut. Even stranger, plugging the phone into the charger causes the battery icon to appear, then freeze.
Now, most advice I've searched for says to flash firmware or a custom ROM or do a factory reset to get the phone working again. I'm worried about doing this because it will probably delete the data on the phone. I don't really care about the phone anymore having bought a new one; I just want to get the data. Please let me know what I can do to recover it. Again, the phone doesn't matter. If your method requires me to break the phone in half, so be it as long as the data remains intact and I can retrieve it.
Thanks very much for reading!

Galaxy Tab A (SM-T350) won't boot after ODIN Flash

Recently, I flashed a TWRP and rooted my Tablet (Galaxy Tab A SM-T350). Yesterday, I made the mistake of installing crdroid (https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t3912517) and wiping the recommended partitions (In that post). After confirming that the custom ROM worked, I went back into TWRP to install the Google Apps and SuperSU. That's when I screwed up.
After installing those .zips I went back into crdroid, and the "Weather Pro" or something like that, which appeared to be the launcher, kept crashing.
Regretting my choices and wanting to go back to stock, I flashed this ROM with ODIN: https://androidfilehost.com/?w=files&flid=154234
That didn't seem to work, as when it booted into the setup, it would crash and reboot. I thought I had flashed the wrong version of Android on it, and downloaded this ROM: https://www.sammobile.com/firmwares/galaxy-tab-a/SM-T350/XAC/download/T350XXU1CQJ5/194035/
That also didn't seem to work, as the device would do the same thing. Boot to setup and crash. I tried to boot into ASR and wipe it from there, which is what landed me where I am now:
The device booted, went into setup and immediately shut down. The device does not boot at all, and when plugged in, simply shows the circle with the bolt inside, never showing the green circle and the battery percentage.
Quick FYI: I backed up everything with ADB to my PC way before this happened. Don't know if that will help.
What I mean: https://1drv.ms/v/s!AnXXk5PX0LXn3gd4nJiaPXYOKhFv
Anyone know where to begin in terms of resurrecting my tablet?
Thanks in advance
UPDATE: I don't know what happened, but the device is not charging. Still refuses to boot without crashing but I feel like this could help
Update 2: Ok so it turns out I was stupid and the battery was just dead (I thought it was charged after a night-long charging, but I guess not)

Categories

Resources