Related
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/
My nexus is stuck on the google boot loop since this morning, i am on stock firmware no root or no nothing, can someone suggest me how can i fix this issue. i have mac and does not have access to any windows machine so i will be greatful if the suggestions will be accordingly for mac
switch off your phone . if you cant switch off the phone then take the battery out and put it back in. Press the volume up and down key along with the power key . this will take you into the bootloader. press the volume down button and navigate to the recovery section. press the power button . this will take you to the default recovery on your phone.
At that time you will see an android robot with an exclamation mark. press the volume up and down key along with the power once again. you should now see the option to update your phone , wipe/reset options. wipe the phone and reboot it . you should be ok after that.
I had the same problem with my gsm gnexus.
Hopefully factory reset using recovery works as krunal1981 suggested. If it doesn't then you will have to use Odin or Heimdall for Mac and preform a full restore. If you have a warranty and the first doesn't work, take it back to Verizon and tell them that your phone isn't booting anymore and they'll replace it.
krunal1981 said:
switch off your phone . if you cant switch off the phone then take the battery out and put it back in. Press the volume up and down key along with the power key . this will take you into the bootloader. press the volume down button and navigate to the recovery section. press the power button . this will take you to the default recovery on your phone.
At that time you will see an android robot with an exclamation mark. press the volume up and down key along with the power once again. you should now see the option to update your phone , wipe/reset options. wipe the phone and reboot it . you should be ok after that.
I had the same problem with my gsm gnexus.
Click to expand...
Click to collapse
Thanks Much this solved all my problems with the phone as of now, wonder what caused the phone to go in that ever ending loop
Question: Did wiping from stock recovery also erase your internal storage (/sdcard) or not?
Anyway - I have had this problem too, and all I can say is: A full wipe fixes it but only temporarily. It will happen again most likely. I believe it is a hardware problem with the internal memory. Next time it happens you should seek a warranty replacement.
when i do this all i get is the droid robot with an exclamation mark. my phone seems to go crazy at moments just keeps power cycling and gets soooooo hot and verizon just keeps trying to give my refurbed ones doing the same thing
galaxy nexus stock
Yes.. resetting the phone from the stock recovery erases everything
---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------
when you get the android with an exclamation mark , press all the hardware buttons on your phone i.e volume up , volume down and the power button. this will take you to the stock recovery .
Phone just did this last night, it was on my desk and I saw it reboot to the google logo after which it would continually random reboot.
Did a factory wipe/reset, fixed temporarily, but within minutes, begins to do it again. No sim card in, etc.
Curious if there's been any more progress on this.
sphish said:
Phone just did this last night, it was on my desk and I saw it reboot to the google logo after which it would continually random reboot.
Did a factory wipe/reset, fixed temporarily, but within minutes, begins to do it again. No sim card in, etc.
Curious if there's been any more progress on this.
Click to expand...
Click to collapse
It's a hardware defect. The only permanent fix is a warranty replacement.
Fortunately the units with this defect seem to manifest it within the first few months so that the owner can figure it out and get a swap.
So, a bit more information here. I'll get to the result at the end.
I did the factory reset from recovery, that would allow the phone to boot and stay on for a few minutes, I found, after which it would go into boot loops again.
Once the phone was on, I had USB debugging on, and was looking at the phone files when I noticed that folders that were originally on the phone from before the wipe @ recovery would begin to appear, one by one. Complete with all the original files that I had before the factory reset. Once I noticed this, I performed a full wipe from the phone OS (Settings -> Backup & Reset -> Factory Data Reset).
This actually wiped everything, 100%. Made sure not to restore all apps from my google account, either, and guess what, more than 24 hours of not a single reboot. Heavy use for those 24 hours, as well. Been stressing the phone HARD.
Near as I can tell, there was some file or app that for whatever reason probably went rogue and was causing the phone to encounter something which I can only relate as being similar to a core dump/BSOD if you were on linux/windows. I don't study phone OS culture enough (I'm an auto service technician by trade) and haven't compiled a Linux box in over 10 years, so I'm a bit rusty on it, but it honestly doesn't surprise me that this is a definite possibility given all the different hardware configurations and all the different apps that are out there that are expected to work on everything.
So, there you have it, my experience, my fix, and what worked for me (so far). I'll keep everyone posted if I notice any random reboots or any future reboot loops.
I believe it's a hardware level defect with the eMMC. It keeps working fine again until it attempts to write some important file to that exact sector of the internal memory. Then it corrupts again and back to the boot loop.
When I had a defective unit, the longest it'd last before looping again was 20 days. Sometimes as few as five hours. If it spontaneously starts looping again - it's a hardware problem and there's no fix. You need a replacement.
Sent from my Galaxy Nexus using Tapatalk 2
So, here's an update on the situation with my phone.
The update, is that there is no situation. The phone is operating perfectly fine. Had it's OTA update to Jelly Bean a couple/few weeks back now, and is still running smoothly. Moderate to heavy data/wifi usage (past 10 days has seen 700mb wifi traffic, 1.2gb 3G/HSPA traffic) and phone hasn't been rebooted in over 300 hours.
I'll give periodic updates every month or so.
I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
....
FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.
I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.
I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.
Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.
So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.
That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.
I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....
I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]
Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.
I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?
after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone
I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.
I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!
I run a rooted SG S3 on stock 4.1.1 with an old 3.0.56 kt747 kernel
Until recently, I've been running this set up for years without any problems.
I've also updated fairly recent CWM along with the latest SU.
As the title states, my phone has been turning off automatically. After weeks of troubleshooting, I noticed a pattern.
When I press the power button, there are three different scenarios that happen.
The phone goes to sleep normally
The phone goes to sleep and immediately wakes up to the lock screen
The phone displays the shut off menu
If scenario 1 occurs, everything is fine and runs perfectly for an indefinite amount of time until i attempt to put the phone to sleep again.
but, if scenario 2 or 3 occurs, the phone automatically shuts down abruptly, within 1-5 seconds.
This problem still occurs even when I boot into safe mode, and I have eliminated the SD card as a suspect. Furthermore, booting the phone up has become extremely difficult. The boot would sometimes crash after the samsung logo, after the splash screen, or during the boot animation. It takes somewhere around 3-5 tries to fully boot up the phone.
Booting into CWM recovery is still possible, but even that sometimes crashes mid-way. I've also noticed that at certain times, when I click the power button to select an action in CWM, it actually double clicks (thankfully CWM is tolerant to that) and cancels the action I was trying to do. I've done some googling and found that an over sensitive power button is a common occurrence in this model, and while that may explain why the 3 different power button scenarios occur, it still doesn't explain the crash.
Finally, I seemed to have remedied the automatic shut off problem several times by wiping cache from CWM. When I first started having these problems and began troubleshooting, wiping the cache eliminated the problem for about a week before the problem came back. When it did, I uninstalled some apps and re-wiped the cache which eliminated the problem again for several days. However, these periods become shorter and shorter, and now wiping cache does not seem to help at all. I've also tried wiping the delvik cache, but it didn't help.
I'm stumped right now. Any suggestions would be appreciated before I try some more large-scale attempts such as resetting my phone or taking it apart. Thanks everyone!
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
jason2678 said:
This definitely fits more in your large-scale attempts category, but it is what I'd try.
I'd grab the stock 4.1.1 firmware from sammobile.com and Odin back to stock. You're fortunate to be on the old firmware, so you can Odin back to stock. When Odin completes successfully, pull battery don't let the phone reboot normally (untick auto reboot in Odin). Boot straight into the stock recovery and do a full wipe. Then reboot your phone normally.
Doing this will correct any problems that exist with your internal storage to the extent possible. If you've still got problems after doing this, it is probably a hardware issue.
Click to expand...
Click to collapse
Yeah, that's part of the reason why i didn't want to upgrade the bootloader for the newer firmwares. I messed around with my phone this morning and its been avoiding the problem ever since. Not exactly sure what I did though lol. Thanks for the reply, I'll try it if the problem comes back over the next few days.
Your phone isn't "crashing," your power button is malfunctioning. The fix is pretty easy. You will need to open your phone up and scrape it off (the phone can be turned on without it). There are youtube videos that show how to remove it.
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
AussieMouse said:
After recovering from a previous bootloop issue with my Tab S, I'm in the same situation after flashing the official Samsung stock ROM for KitKat 4.4.2 via Odin.
When the ROM was first flashed, the tablet began working as per normal with the exception of it taking 10+ minutes to fully reboot and the device somehow restarting itself and loading the display within a second. However, after a few days, I kept receiving pop-up windows on the tablet stating that different applications (most of them I didn't have opened or running in the background at the time) weren't responding. A couple of days after that, more of said pop-up windows kept appearing on the screen, sometimes freezing the whole device until a push notification appeared in the background or the device force-rebooted itself.
I flashed the ROM again once or twice and cleared the cache partition to see if that made any difference, which it unfortunately didn't. I also removed the microSD card and SIM card, force-rebooting the device without them, and then with them when that test failed.
Now, for roughly about a week, the tablet has been stuck in a bootloop (the splash screen animation) where I have left it to drain the battery, leave it for about a day or so, and recharged it to 100%. So far there hasn't been any success.
Today I finally factory reset it to see if that may help, and the only thing that has changed is that the sound of the device rebooting is now playing when it does transition to the loading screen, which I had turned off previously when the tablet was still working.
Is there anything else that I may have missed that could help it work again? It's not rooted (and I would very much prefer to keep it that way) and has not had a custom ROM installed or flashed onto it. It can still enter Download Mode and Recovery Mode, but other than that and being about to use the Power-Volume Down technique, there's not much else I can do with it so far.
Click to expand...
Click to collapse
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
It worked! Thank you so very much!
And I'm not a huge fan of updating my Android devices due to past experiences, but if this happens again, I might just update it to Marshmallow.
ashyx said:
Factory reset, install stock firmware, wait ten minutes and you should be good.
But why kitkat? MM is available and working well.
Click to expand...
Click to collapse
@ashyx
i love you man...this worked for me too...thank you...now i need to reinstall TWRP again and see what's cooking......
I had this problem recently too, with the added complexity that the "Factory Reset" option in recovery wasn't working -- it would say something like "MDM does not allow factory reset" and then just reboot.
Fixed it by directly flashing TWRP with heimdall, then booting into the new TWRP recovery, performing a factory reset, and then rebooting the OS. This time it got pass the bootloop.
i flashed new twrp for T700 it's bootloop cannot enter the twrp menu keep bootlooping ...what's the solution for this?please help
Help ME!
What are "stock firmware" and "MM"? and where to get it?
I've replaced the power button thinking it was a hardware issue but now I'm not sure. I've also installed a few different stock roms but still have the same problem. Does anyone have any insight as to what could be going wrong and what I can try to get it fixed? Thanks for any help you can give. The device is a Samsung SM T-800