Hi all, my Tab S 10.5 (T800) was running stock MM with no root. I tried using the Adoptive storage enabler patch from this site. After installing the TWRP using Odin and flashing the adoptable storage patch, I am stuck in that stupid reboot loop. I did selected "Allow modification to system partition..." in TWRP. I managed to apply the batch and after a number of attempts boot successfully, changed to internal storage etc but still getting random reboots all the time now. Read more on the site; then did cache clear, factory reset via recovery and then also flashed back stock MM firmware - everything successful but still getting random reboots.
Just to mention, the tablet has recently had a brand new original battery so that is not the problem. It was working fine before I attempted the TWRP/Adoptive storage patch or stock firmware flash and now getting random reboots (sometimes right at startup logos and sometimes soon after booting up).
This appears to be a very common one on these Samsung tablets so no clear reason anywhere why it happens. Any suggestion for a quick fix for this please. I am getting random reboots at the moment all the time since I tried flashing the recovery/patch/stock firmware. Any help would be appreciated please...
update
Just to provide quick update and info:
Purely by hit and trial, I have found that if I keep hold of the power button (pressing it constantly since power up), it goes past the initial boot loop consistently and boots the device up. But then, once it hits the limit for holding the power button (think 30 secs), it vibrates and turns itself off (which I think is normal behaviour). So I thought this is interesting to share as not something I have read anywhere else. Not sure what difference it makes to the startup by holding down on the power button but that does not appear make it loop. Of course, this is not a solution as the tablet eventually shuts down after 30 secs of holding the power button.
The power button itself seems fine and not broken/damage or anything - clicks fine and solid and works fine every time. Also the random restarts does not happen in recovery/download mode so I take it the power button is not faulty as else, it should be happening for everything.
Again, requesting everyone for some help please as I am a bit stuck what to try next.... thanks in advance!
anyone pls...?
Bump again... in the hope one of the experts will jump in to help!!
Thanks in advance
I'm experiencing the same exact issue, The tablet will power up to the setup screen and I can almost finish the setup process but then it vibrates and powers down. PLEASE... someone, chime in and help with this problem.
Thanks In Advance
Related
Hi guys:
I have this phone from about 10 months ago. I have always it rooted and with CyanogenMod, actually with CM7.
Today I was using my browser, and then it closed, the phone begin giving me a lot of errors, any application worked and I decided to reset it, because sometimes that work.
For my surprise, when I reseted it, It was bootlooping, It start booting (cyanogen logo doing circles), then freezes and then reset.
I know how to work with this problems and I reseted it on recovery and when I entered to the recovery everything seems to be fine, but I only see the menu, when I try to install zip from sd card, go to mount & stored, go to clear cache, or enable USB the screen just get empty but its ON.
Im very frustrated, I don't know how to proceed in this situation, I have looked in the Troubleshooting thread but have not found anything that worked for me with boot looping.
I hope someone can help me, sorry for my english, it's not my main language.
what button are you pressing to select the menus? Power?
Yes Im using power button.
Before I used the power button but now tried using the middle button and it worked.
Lets see if it recover correctly.
Yes because power button turns off the screen.
So I'm running CM 10.2 android version 4.3 and I started to notice that when I pressed the power button, it brought up the reboot menu instead putting my screen to sleep so I downloaded the newest nightly and figured it was probably just a bug and went to flash the latest nightly. Upon reboot, my phone got in an infinite bootloop so I pulled the battery, let it sit for a minute and then held the power, volume up and menu button to enter recovery. I got the blue words in corner that you will normally see when booting into recovery, then saw the S3 screen that you'll see right before entering recovery, however, my phone started rebooting again constantly vibrating etc. So then I decided to try and get into download and flash back to stock with Odin. So I entered download mode, pressed volume up on the confirm screen and then it entered download mode and then immediately rebooted and wouldn't stop. Is my phone bricked? I'm wondering if the power button is broken since when in download mode, it reboots which normally occurs when you hold the power button in download mode. Sorry for the long description but just wanted you guys to know what I've done so far and am experiencing. Any help is appreciated. I've been rooting phones from all manufacturers for years now and I'm out of ideas at this point. Thanks!
Definition of a bricked phone: A completely unresponsive device which doesn't turn on at all. Doesn't vibrate upon start up and doesn't have any signs of life.
You most likely have a jammed power button as that has been the issue with the GS3. Not a brick.
Clearly not bricked as the first reply explained. And for the love of god, please use some white space (paragraphs) next time.
If you think that a button is jammed, see if you can physically unjam it without causing damage. If you believe that the flash may be messed up, the mskip's Samsung Toolkit may be able to reflash a known good ROM even with a stuck button. And look into some of the button remapping apps like the aptly titled Fix Broken Power Button app.
Good luck.
Firstly, yes, I am sure that the info that I need is on here somewhere, but I have spent the last hour reading threads and I am not a developer and I cannot tell the difference from a soft brick or a hard brick or a boot loop.
Also almost all of the tutorials to root / unbrick involve enabling USB debugging on the phone first, but I can't boot my phone to do this anyway....
So, I got 2.19 OTA update and installed it normally. Phone is not rooted, totally stock 550ML WW model.
But in the last update I got a few bugs so I wiped the cache from recovery mode by following a tutorial, no problems and the bugs went away. So I decided to do the same this time....
I got to the boot menu OK and selected Recovery Mode, then got the Error / sleeping droid screen, so I tried to hold power / vol up to get into the recovery mode and the phone turned off. It was at about 35% battery and plugged into the charger so I'm pretty sure it wasn't a battery issue.
Now I can't get it to turn on / boot at all. If I hold the power button down it just vibrates once and does nothing else, same for vol up and power.... Is this some kind of brick?
Problem is I am going travelling for a month tomorrow and I can't be without my phone so I have to fix it in less than 24 hrs.
Can anyone help me without using terms like "flash image" or "sideload" unless you explain exactly what they mean?
Thanks in advance. :silly:
Can you press vol down and power and see if it turns on?
Sent from my ASUS_Z008D using Tapatalk
Vol down and power has done something!!
The phone vibrated twice and the led has lit up showing that it is charging!! Also I have the battery graphic on the screen.
Should I just now turn it on normally?
Sorry to sound so dumb but I really don't want to screw this up...
Thanks for answering by the way.
You can try to boot like normal but my guess it would still be stuck with the android logo. Happened to me when I rebooted my phone while wiping cache.
Anyway go to the link and follow his instructions. Let me know if there's any problems. Cheers!
http://forum.xda-developers.com/showthread.php?t=3101556
Sent from my ASUS_Z008D using Tapatalk
i experienced shutting down during wipe cache.bad times then.i resolved with this : forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
remember for bootloader press power+volume up.when it vibrates release power and keep pushing volume up.you should be in booloader.scrolling with volume up volume down you can choose recovery..may will be wrote installing update and then an error message.just press power and immediately after volume up for a bit.you should be in recovery.if you reached recovery do a wipe cache.REMEMBER IT CAN TAKE 15-20 MIN TOO ! check if it power on.
if you still cat access bootloader...for me you have to use warranty.say to asus you just did an ota and then phone bricked.dont use the word brick say just it won't power on.approach is the key in this cases.approach to them like a total noob.call them,don't email them.if you are young,let someone older to talk,a relative or someone like this and give to him a text to follow.is difficult to think a noob thinks to do some difficult moves as root,unlocking bootloader....they think "this is a noob.he never thinked to root or modify phone" .so they can think your seller sold to you a rooted device (updating with root takes to brick,bootloop etc.) and so they will give to you a new phone.if it not power on they cant see if it is rooted or not
good luck bro
Many thanks to all of you that contributed, it seems that I was pretty lucky.
After the "reanimation" as per Aceazzay's suggestion, I left it charging for about an hour or so (just in case it was battery related) then booted it normally and it worked (upon booting the battery was over 90%, so it was certainly not a shutdown due to battery).
I have now been able to do a Cache partition wipe correctly and all is good.
I don't know why it shut down in my first attempt, perhaps clumsy fingers, or something more sinister? I guess I'll never know, but this site has certainly saved me some grief!!
Overandout said:
Many thanks to all of you that contributed, it seems that I was pretty lucky.
After the "reanimation" as per Aceazzay's suggestion, I left it charging for about an hour or so (just in case it was battery related) then booted it normally and it worked (upon booting the battery was over 90%, so it was certainly not a shutdown due to battery).
I have now been able to do a Cache partition wipe correctly and all is good.
I don't know why it shut down in my first attempt, perhaps clumsy fingers, or something more sinister? I guess I'll never know, but this site has certainly saved me some grief!!
Click to expand...
Click to collapse
happy for you :good:
I've got one of those 10.5 models (SM-T807R4, the US Cellular version) that suffers from the screen freezing problem which requires either pushing the power button twice or closing an opening the case. In an effort to fix the problem, I rooted it and installed TWRP 2.8.5.0 and was able to successfully boot into TWRP. I backed up the boot loader and the system using TWRP and the entire tablet with Titanium Backup.
I just booted into TWRP and was ready to wipe everything and install a new ROM when the screen froze. I can't unfreeze it with the power button or by closing and opening the case. When I pushed the power button, it locked TWRP but since the screen is frozen, I can't swipe to unlock it. I tried the power+home+vol down sequence and that didn't work. I have held the power button down for a minute or two (until my fingers gave out) and that didn't work either. I hooked it to the PC but the PC doesn't see it so Odin or ADB or Fastboot don't do anything. The only upside to this is that now I'm pretty sure the screen freezing problem is hardware rather than software so flashing a new ROM probably won't help.
At any rate, I need suggestions to shut it down, given that nothing I have tried has worked. Then I'll see if I can sell it as a boat anchor!
================
Well, I got finally got it to boot with the power+home+vol down sequence. Will try TWRP again later.
Good evening All, It's been a long time since I last posted but want to start at custom roms again and I'm hoping someone can help me as I am now considering giving up on this device.
My sister-in-law gave me her old Galaxy A50 after it stopped working, gives the circle with lightning icon but not the normal charge notification. If it boots I just get the Samsung A50 start screen but no boot and no boot animation.
I have cleared cache, factory reset and tried flashing stock roms via Odin as the bootloader is currently locked so no custom ROM's for me to play with yet. I have tried a couple of stock roms but no joy.
The questions I have are below:
1, could a faulty battery cause the phone to not boot?
2, Is there a way to unlock the bootloader via ADB or some other alternative?
3, is there anything I've missed that I could try to get it to boot thus allowing me to perform number 2 from within Android?
Thanks all in advance. :good:
Maybe
No
Try flashing through ordin and see if it gives an error or completes, failing that - try flashing TWRP and see if you can boot into that maybe formatting data or wiping the system somewhere else might help?
Have you tried more than one charger / plug? - same thing? maybe bad wire / plug
I had this issue today and last week. there's a bug w the latest firmwares. havent had this issue on april/may builds.
Anyway my solution is.....
Once plugged in (lightning circle shows up and nothing happens)
press volume down + power till it reboots
once it reboots, boot into recovery by quickly holding vol up + power then release it 2 sec after u see galaxy logo
once in recovery. let it charge for about an hour so it should have enough juice to power on
The thing I notice is the phone does not like to have it's battery drained it this happens most of the time, but this started happening on the last few updates only.
So I will rolllback or install the one ui rom with custom kernel to stop it from happening ever again. it's annoying
hope it helps. it works for my end with the similar locked BL and stuff as u have
InFam0us-1985 said:
Maybe
No
Try flashing through ordin and see if it gives an error or completes, failing that - try flashing TWRP and see if you can boot into that maybe formatting data or wiping the system somewhere else might help?
Have you tried more than one charger / plug? - same thing? maybe bad wire / plug
Click to expand...
Click to collapse
Thanks for the reply, I have tried a few different images via Odin but non of them work and I get stuck at the same place. I can't flash TWRP because the bootloader is locked, unless you know a way I can do it with a locked bootloader?
Abaddon said:
I had this issue today and last week. there's a bug w the latest firmwares. havent had this issue on april/may builds.
Anyway my solution is.....
Once plugged in (lightning circle shows up and nothing happens)
press volume down + power till it reboots
once it reboots, boot into recovery by quickly holding vol up + power then release it 2 sec after u see galaxy logo
once in recovery. let it charge for about an hour so it should have enough juice to power on
The thing I notice is the phone does not like to have it's battery drained it this happens most of the time, but this started happening on the last few updates only.
So I will rolllback or install the one ui rom with custom kernel to stop it from happening ever again. it's annoying
hope it helps. it works for my end with the similar locked BL and stuff as u have
Click to expand...
Click to collapse
Thanks for your reply, unfortunately it still wont boot. It has charge as unplugged and currently sot on the android recovery screen. If you can think of anything else I could try I would be very grateful
You could try again with recovery mode, as it charges with that mode. I had to repeat the steps I took for a couple of times for it to boot. Or use another cable perhaps? that's what I did too. It's really frustrating.
Abaddon said:
I had this issue today and last week. there's a bug w the latest firmwares. havent had this issue on april/may builds.
Anyway my solution is.....
Once plugged in (lightning circle shows up and nothing happens)
press volume down + power till it reboots
once it reboots, boot into recovery by quickly holding vol up + power then release it 2 sec after u see galaxy logo
once in recovery. let it charge for about an hour so it should have enough juice to power on
The thing I notice is the phone does not like to have it's battery drained it this happens most of the time, but this started happening on the last few updates only.
So I will rolllback or install the one ui rom with custom kernel to stop it from happening ever again. it's annoying
hope it helps. it works for my end with the similar locked BL and stuff as u have
Click to expand...
Click to collapse
works for me! great tip!! tnx
Same problem for me, when trying volume down + power till to reboot but this is not working
any idea please ?