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)
Related
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
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.
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!
Hi all.
I have installed the Cyanogenmod 12.1 UNOFFICIAL on my Galaxy S II for several months, but yesterday, suddenly, the phone shutted down and kept doing this everytime I tried to turn it on, until I couldn't even go further than the "Samsung Galaxy S II" sign.
At first I could boot in recovery mode, so I tried to do a full wipe and then re-install the Cyanogenmod, but something went wrong during the installation and a dead android with a red triangle appeared in the background. I rebooted the phone, and from that moment on I couldn't even boot in recovery mode anymore.
So I followed this guide found in the forum to fix the issue (http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771) and it worked well, because the phone installed everything successfully.
Now, the bad news is that the phone keeps shutting down soon after the operative system starts (I can't even finish the initial configuration). The good news is that at least I can boot in recovery mode (in this way the phone is turned on as long as there is enough battery energy, so it is not an hardware problem, I guess).
I really don't know what else could I do.
Can you help me in any way please? Is it a known issue? How can I fix this?
If you need further informations I'll be happy to let you know them.
Very thanks in advance.
You are using an unofficial build of CM, install an official build of CM12
Fhronk said:
Hi all.
I have installed the Cyanogenmod 12.1 UNOFFICIAL on my Galaxy S II for several months, but yesterday, suddenly, the phone shutted down and kept doing this everytime I tried to turn it on, until I couldn't even go further than the "Samsung Galaxy S II" sign.
At first I could boot in recovery mode, so I tried to do a full wipe and then re-install the Cyanogenmod, but something went wrong during the installation and a dead android with a red triangle appeared in the background. I rebooted the phone, and from that moment on I couldn't even boot in recovery mode anymore.
So I followed this guide found in the forum to fix the issue (http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771) and it worked well, because the phone installed everything successfully.
Now, the bad news is that the phone keeps shutting down soon after the operative system starts (I can't even finish the initial configuration). The good news is that at least I can boot in recovery mode (in this way the phone is turned on as long as there is enough battery energy, so it is not an hardware problem, I guess).
I really don't know what else could I do.
Can you help me in any way please? Is it a known issue? How can I fix this?
If you need further informations I'll be happy to let you know them.
Very thanks in advance.
Click to expand...
Click to collapse
Is your device boots and works well on stock?
nhmanas said:
Is your device boots and works well on stock?
Click to expand...
Click to collapse
My device couldn't even boot in the end. However I solved the problem by changing battery, so it wasn't a software problem. Thank you anyway!
I'll start from the beginining.. Okay so since i bought my tab (3 months ago) i had a battery problem, but it wasnt a bad battery problem. Once it got to 95% battery it stopped charging. Anyway, about a week after that i was unhappy with the performace of touchwiz on my tab so i decided to root it and install the cyanogenmod 12 nightlies. I was happy with cm for a while but eventually i got bored of all the bugs and instabilities so i decided to switch to a touchwiz rom.. This touchwiz rom was a vast improvement from the stock touchwiz so i decided to keep it. However i still wanted to improve the performace so i researched online for apk's/zip's that could improve my tabs performace. I came across crossbreeder and people said it was really good so i decided to install crossbreeder through TWRP. Once installed i rebooted my device and i instantly found many more battery problems. For example my battery would go from 50% to 20% in 5 mins/my battery would run out and i would reboot it and it would have had 40% etc. I downloaded some battery calibrating apps and calibrated my tab. After all that, that battery wasnt so bad. It was still dodgy but no where near as bad as it was straight after installing crossbreeder. Anyway, this was about 1 month ago. Since then, no new problems had occured with the battery until last night. Last night, my battery ent don to 1% then turned off like it should. I put my tab on charge and rebooted however when it rebooted nothing would work. My touchscreen didnt work, my home button didnt work, none of the keys next to the home button didnt work. So i thought that this was no problem and i could just boot into TWRP, factory reset and install the backup that i made. When i tried this, i booted into TWRP successfully however i couldnt press any of the TWRP buttons, again, i thought that this could be solved by flashing the stock firmware through odin. I put my tab into download mode and connected it to my pc, then flashed the stock rom. Once finished it showed a 'pass' and i thought everything was sorted.. When my tab booted up, it again, didnt let me press anything and none of the buttons would work. This is when i panicked. I then went into the stock recovery to factory reset my tab to see if that would work however, when i went into stock recovery, i couldnt go up or down using the volume keys.. So my volume keys didnt work either. I next put my tab in download mode and connected it to my pc. I opened odin and checked the 'Nand erase all' box thinking this would fully reset my whole tab. I then researched the 'nand erase all' function to find that everyone said that it breakes your device and puts it in bootloop etc. After reading this i instantly disconnected the usb from my computer to my tab. I tried rebooting my tab to see if it still booted and it didnt.. (i waited 20 mins). I then ran odin with 'clear efs' box ticked on. Again it didnt boot. I went into stock recovery again to see if the volume keys would work.. they didnt.. Infact when i opened stock recovery it had 3 errors showing (which it didnt last time i opened stock recovery). They all started with 'failed to mount /data'. Now i am here.. Sorry it was such a long read, i thought it would be better if i explained in detail. Thanks to anyone that replies/helps me.