Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
If I'm not mistaken, you would need to un-root your phone prior to installing any OTA Updates from AT&T. Also, you should only install the OTA Updates while using the stock recovery. So, you should re-flash the stock recovery and then attempt to complete the OTA Update. After that, you could re-install TeamWin, re-root and prosper.
Refer to this link on reverting back to stock... http://forum.xda-developers.com/showthread.php?t=2721435
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
Flash factory recovery, take the update, flash twrp back
or..
Titanium backup to freeze att update
an0ther said:
Flash factory recovery, take the update, flash twrp back
or..
Titanium backup to freeze att update
Click to expand...
Click to collapse
Just downloaded titanium back up. How do I freeze the update?
howyodoing said:
Just downloaded titanium back up. How do I freeze the update?
Click to expand...
Click to collapse
Try searching next time.. I see you are new here so i'll at least give you a link this time
http://forum.xda-developers.com/showthread.php?t=2752718
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
Click to expand...
Click to collapse
Good rule of thumb, do not install OTA updates on any modded Android device, without at a minimum doing thorough research on what will happen.
Depending on the device and the update in question, attempt to install an OTA on a modded device will remove root, possibly plug existing exploits (and render the phone unable to be rooted), or put you in a boot loop (as you have experienced).
In particular, OTAs require stock recovery in order to install. So if you have custom recovery installed, this is why the OTA install is failing (and why it keeps booting into TWRP).
Also, there is little (if anything) contained in the OTAs that doesn't get posted in a safe format (flashed from custom recovery) in the Development section soon after the OTAs start to roll out.
Solution for HTC OneM8 (continous restarting after update)
howyodoing said:
Hi, android noobie here, I have a rooted m8 that keeps rebooting after updating the at&t software.
I get the pop up that says AT&T software is available. If I clicked on continue it reboots to teamwin during boot up and once i reboot to system it just reboots itself every 30 secs or so.
I had to do a factory reset just to get my phone working again. But now the update screen is popping up again and I have to keep it under 35% so it doesn't auto update and keep pressing remind me later.
How do I disable this auto update? or is there an easier way to make the phone go back to stock since I really don't have any use of a rooted device besides watching MLB games...
Thanks for the help.
Click to expand...
Click to collapse
Hi, i have a HTC One M8, and when my first update popped, i was very enthuziast.
I accepted to download the update, installed it, and... the problem appeared. The phone made his restart after update... and continued to do so over and over again. (Vibrate/HTC screen on for 30 secs/screen off and so on)
I checked the HTC website for solutions, i entered live chat with a consultant, and he asked me to start the Hard reset procedure. To do that, while turned off, you have to press both volume keys, and press the power button. The phone will enter in the Bootloader menu where you have some options. But... tell me, how to do that if the phone restarts continously? you have about 1-2 seconds to do that, while the screen is off. It gave me a hardtime to do that... Finnally, i managed to enter the Bootloader menu.
There... you have 2 options: (using volume up/down to select, and power button to select) you can select to poweroff(shutdown) the phone - and the phone will shutdown,
or you can turn off the fastboot, and the phone will restart normally.
The thing is that when you restart your phone normaly, while fastboot on, the phone skips some steps, and go directly to to turn it on and show you the startscreen.
When you make a major update, like system upgrade, when the phone restarts, he needs to load all the boot setting. And here is the problem. If you have fastboot on, and make a major update, the phone will enter in this ****ty cicle of continous restarts.
Remember to deactivate this Fastboot before you update!
sergiu.dragan25 said:
I checked the HTC website for solutions, i entered live chat with a consultant, and he asked me to start the Hard reset procedure. To do that, while turned off, you have to press both volume keys, and press the power button.
Click to expand...
Click to collapse
This is not correct. To force a reboot, you hold power and vol up (not both vol buttons). Then, when its restarting (the moment the screen goes dark and before the white boot screen appears) you let go of both those buttons, and only hold vol down.
sergiu.dragan25 said:
But... tell me, how to do that if the phone restarts continously? you have about 1-2 seconds to do that, while the screen is off.
Click to expand...
Click to collapse
In the case of a bootloop (phone keeps restarting), all you need to do is hold vol down during one of the reboot cycles. The timing doesn't matter in this case. Just sit on the vol down button until the bootloader screen appears.
sergiu.dragan25 said:
There... you have 2 options: (using volume up/down to select, and power button to select) you can select to poweroff(shutdown) the phone - and the phone will shutdown,
or you can turn off the fastboot, and the phone will restart normally.
The thing is that when you restart your phone normaly, while fastboot on, the phone skips some steps, and go directly to to turn it on and show you the startscreen.
When you make a major update, like system upgrade, when the phone restarts, he needs to load all the boot setting. And here is the problem. If you have fastboot on, and make a major update, the phone will enter in this ****ty cicle of continous restarts.
Remember to deactivate this Fastboot before you update!
Click to expand...
Click to collapse
First, the FASTBOOT selection in bootloader is not the same as "Fast boot" in Settings>Power. The latter just makes the phone start faster from power OFF. The former is an adb (Android Debug Bridge) special mode that allows you to flash partitions from a computer.
Second, in bootloader, you should have the following selections:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Of course, its the FACTORY RESET option you want if you want to wipe the phone. Scroll down to (using vol keys) and select with power button.
On the bootloader screen, the active selection is the blue box with white text below the green phone info (hboot number, radio number, etc.). FASTBOOT should only be the default "active" selection if your phone is connected to a computer by USB. Otherwise the default selection in bootloader should be HBOOT.
Third, the "Fast boot" option in Settings>Power does not make a restart "faster" by skipping any steps. It just makes a start from power OFF faster. Its kind of a trick, where power OFF is not really off, but just a deeper sleep mode. A restart is always a restart, regardless of whether "Fast boot" is selected or not in Settings>Power.
Related
Phone: Motorola Droid Maxx
Rooted
Problem: After accepting 12.15.15.en.us update, phone powers down, reboots, reaches home screen from between 30 seconds to 1 minute, then reboots again in the same fashion, nonstop.
Agreed: I should have never accepted that damned update.
I can access TWRP for about 10 seconds before it reboots again.
Can't find any backup files.
Not sure if it would even have enough time to backup, before rebooting, regardless.
I have tried holding the Vol Down key to reboot into menu. It tells me that my "Device is LOCKED." So I guess I lost root (?).
From there I selected "Reboot into Recovery" but it doesn't change anything - simply reboots into Home Screen again.
Considering a Factory Reset but not sure that will do anything.
What to do?
Please help.
Edit: Tried booting into "Factory" but it just took a long time to reboot and then nothing changed.
I'm sunk!
me too having the same loop of starting problem
imagic5 said:
Phone: Motorola Droid Maxx
Rooted
Problem: After accepting 12.15.15.en.us update, phone powers down, reboots, reaches home screen from between 30 seconds to 1 minute, then reboots again in the same fashion, nonstop.
Agreed: I should have never accepted that damned update.
I can access TWRP for about 10 seconds before it reboots again.
Can't find any backup files.
Not sure if it would even have enough time to backup, before rebooting, regardless.
I have tried holding the Vol Down key to reboot into menu. It tells me that my "Device is LOCKED." So I guess I lost root (?).
From there I selected "Reboot into Recovery" but it doesn't change anything - simply reboots into Home Screen again.
Considering a Factory Reset but not sure that will do anything.
What to do?
Please help.
Edit: Tried booting into "Factory" but it just took a long time to reboot and then nothing changed.
I'm sunk!
Click to expand...
Click to collapse
hai iam also facing that stupid problem once i installed an app from a website.... waiting somebodies hand....
I was doing a backup with TWRP and everything seemed to go just fine. Then after a reboot i unlocked the phone to notice that it was leaving the lock-screen icons on the bottom of the page. I still had access to my notification bar and could clear notifications. Figuring that there had just been a mistake in the boot process, I held the power button to restart the phone. Well it never brought up my power menu to restart. Also instead of making me wait ten seconds until it flashed its lights and restarted, it just restarted in like 3 seconds. Now my phone is stuck on the HTC ONE screen and will not respond to anything including hold the power button.
My phone is rooted an s-off. I know that I have not posted at all on here, but I have been rooting and know how at least the basics on adb shell. I just have never had a phone lock up to this point. If I can at least get to recovery, I should have 2 or 3 backups to run. I just don't want to have to wait for the phone battery to die just to hope I can get to recovery.
TugboatTony said:
I was doing a backup with TWRP and everything seemed to go just fine. Then after a reboot i unlocked the phone to notice that it was leaving the lock-screen icons on the bottom of the page. I still had access to my notification bar and could clear notifications. Figuring that there had just been a mistake in the boot process, I held the power button to restart the phone. Well it never brought up my power menu to restart. Also instead of making me wait ten seconds until it flashed its lights and restarted, it just restarted in like 3 seconds. Now my phone is stuck on the HTC ONE screen and will not respond to anything including hold the power button.
My phone is rooted an s-off. I know that I have not posted at all on here, but I have been rooting and know how at least the basics on adb shell. I just have never had a phone lock up to this point. If I can at least get to recovery, I should have 2 or 3 backups to run. I just don't want to have to wait for the phone battery to die just to hope I can get to recovery.
Click to expand...
Click to collapse
Are you saying volume up + power button does not restart your phone nor does any help? Check if your phone is detected in computer and if so you can issue and adb reboot command
also since there is no removable battery HTC added a reboot function press home vol down and power that should do the trick
The phone is not detected by a computer, nor will it charge. Vol down and power is not cutting it off. Right now I am waiting for the battery to die so I can hopefully boot into recovery and do a restore.
Vol up + Power was the key. I was thinking it was volume down. Thanks for all your help
TugboatTony said:
The phone is not detected by a computer, nor will it charge. Vol down and power is not cutting it off. Right now I am waiting for the battery to die so I can hopefully boot into recovery and do a restore.
Click to expand...
Click to collapse
Its volume up mate + power not volume down
pradeepvizz said:
Its volume up mate + power not volume down
Click to expand...
Click to collapse
Hi Do you have a HTC one max stock Rom I could use??
Thanks
mini88448 said:
Hi Do you have a HTC one max stock Rom I could use??
Thanks
Click to expand...
Click to collapse
There have been lots of request for this, ill upload a stock rooted ROM soon.
pradeepvizz said:
There have been lots of request for this, ill upload a stock rooted ROM soon.
Click to expand...
Click to collapse
OMG THANK YOU SO MUCH!!!
:victory::victory::victory:
Just wanted to point out I ran into this issue also (Stuck on white HTC boot screen) after wiping my ROM and Vol UP + Power did the trick for me also (and then Vol Down + Power to get back to the bootloader).
i need help, guys
so attempting to install a new rom, i must have dont something wrong because now restarting the phone will leave me on the htc logo loop and restart. i still have access to hboot and fastboot. but when attempting to load into twrp, it shows the team win logo for half a second and then restarts the phone. then i installed cwm and it does boot into it but whatever option i pick, install zip, wipe data, ANYTHING, restarts the phone.
i have no idea what to do. i tried installing a rom using adb sideload but it stops at around 80%, ive tried installing different versions of twrp and cwm and same thing. i think it is bricked. im using the verizon htc one max. the only option i see left is the ruu toolkit but ive only been able to find the sprint version and then it says that bootloader needs to be locked and i have not idea how to do that from hboot, fastboot, or cwm
attempting to install superuser also fails
if there's anyone here that can help, please, any suggestions will be appreciated. thanks =:laugh:
Sounds like you're flashing the wrong TWRP.
Sent from my Galaxy Nexus using Tapatalk
suieitori said:
so attempting to install a new rom, i must have dont something wrong because now restarting the phone will leave me on the htc logo loop and restart. i still have access to hboot and fastboot. but when attempting to load into twrp, it shows the team win logo for half a second and then restarts the phone. then i installed cwm and it does boot into it but whatever option i pick, install zip, wipe data, ANYTHING, restarts the phone.
i have no idea what to do. i tried installing a rom using adb sideload but it stops at around 80%, ive tried installing different versions of twrp and cwm and same thing. i think it is bricked. im using the verizon htc one max. the only option i see left is the ruu toolkit but ive only been able to find the sprint version and then it says that bootloader needs to be locked and i have not idea how to do that from hboot, fastboot, or cwm
attempting to install superuser also fails
if there's anyone here that can help, please, any suggestions will be appreciated. thanks =:laugh:
Click to expand...
Click to collapse
May I suggest following these instructions?
http://forum.xda-developers.com/showpost.php?p=51753483&postcount=129
If you're able to complete those instructions outlined in that post, this should set you up with the latest HBOOT, Radio and TWRP (Recovery) for the Verizon HTC One.
Make sure you read the post fully before you start, especially this part:
fastboot flash zip firmware.zip (Be sure it finishes saying 'successful', not 'please flush again immediately'. If it says the flush again, rerun the command)
If you succeed in getting that done, see if TWRP still causes the phone to reboot and get back to us.
Hello, today I wanted to restore my previous CWM backup. So i started with cleaning partitions before restoring. I've begun with system and my phone hang. I waited about 30 minutes, then pulled out battery with hope I'll try again via CWM. The thing is - I can't boot it into recovery: Volume Up/Volume Down+Power leads to normal start up (LG screen and nothing further). So i connected it to PC and wanted to make it right via ADB. Unfortunely it seems I had USB Debugging turned off, and ADB isn't recognizing my phone now... What should I do now?
I have rooted D620r with unlocked bootloader.
silent_hunter said:
Hello, today I wanted to restore my previous CWM backup. So i started with cleaning partitions before restoring. I've begun with system and my phone hang. I waited about 30 minutes, then pulled out battery with hope I'll try again via CWM. The thing is - I can't boot it into recovery: Volume Up/Volume Down+Power leads to normal start up (LG screen and nothing further). So i connected it to PC and wanted to make it right via ADB. Unfortunely it seems I had USB Debugging turned off, and ADB isn't recognizing my phone now... What should I do now?
I have rooted D620r with unlocked bootloader.
Click to expand...
Click to collapse
You must never delete partitions before restoring a backup especially system!!
CWM will do that for you...
Boot your device in factory reset mode (which simply boots CWM) by doing the following key combination: (while your device is off - pull and plug the battery to be sure) press and hold Vol - and power, when you see the LG logo, release the power button and press it again. Hold them until you see the facory reset mode, then simply enter YES. It will reboot to CWM.
Vagelis1608 said:
You must never delete partitions before restoring a backup especially system!!
CWM will do that for you...
Click to expand...
Click to collapse
Weird, I was always doing this when I had HTC Desire S
Used this countless times and always worked!
Ok, i've done as You said, something like CWM loading screen appeared, and then went back to LG Screen. LG Screen standing still and nothing happens
The only good thing is that I can access ADB for 20 seconds when CWM is "loading", but no action can be executed - every command ends up with "waiting for device".
Thanks for Your reply, though! :highfive:
EDIT:
I solved my problem by using "Emergency software restore" mode featured in "LG User Support Tool". I got clean, unrooted system now and I need to modify it again but...
...THAT'S WHY I REGISTERED HERE!
Lock bootloader
Hello everyone.
I was just going to try out CM11, but got one question. Is it possible to lock the bootloader and revert everything to stock? There were some talks about new stock ROMs coming out and they might not work after a custom ROM.
Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J
After I updated to C.49, my phone is acting weird...
1) Power Button is not working properly
2) Random emergency Call Screen and Power Reboot/Off Screen.
3) When I tried hard rebooting to go into recovery....it shows recovery mode at bottom for 10s and the reboots again to recovery mode text at bottom. It does not go into Menu of selection of English and Chinese language. This continues infinite times...Until finally it decides to boot to main home screen. But the Power button and Emergency screen/Reboot screen issue continues..
4) I tried factory reset of system setting...Same issue remained.
5) I finally tried factory reset wiping all data..Since the Version is latest C.49, which I believe has issues, the Emergency screen and Power Reboot Screens and Power Button not functioning properly continues..
6) I downloaded CPH1861EX_11_OTA_0490_all_sWtP8RDIvyoU.ozip from realme support. Tried updating that software in the phone..
But it lead to point (3) which I stated above...Same vibrating/rebooting after every 3 to 5 secs but not going into recovery Mode..It continued for 1 full day until battery died..Then I charged the phone for sometime and it continued its same funky routine of infinite rebooting and stopping at recovery Mode text.
But, eventually, after few hours, it booted normally to main screen.....But the problem was still there.
7) Now, even if try to shut down..from Power reboot/off screen...It shuts but in few seconds reboot again to main screen. So I cannot even shut it down.
8) I may try to download C.48 version (2.16 GB) and update from SD Card somehow..I don't know if it will revert back to different Version...But gotta try.
Or if there is enhanced or latest or custom update newer than C.49 available in market. maybe I should root or install that.
Frustrating...
How to get rid of this bug? I guess have to wait for new patch or something or next update. Service Centers are not open..because of Lockdown in Mumbai.
Please help, if someone knows the solution or had to deal with similar issue.
agovind said:
After I updated to C.49, my phone is acting weird...
1) Power Button is not working properly
2) Random emergency Call Screen and Power Reboot/Off Screen.
3) When I tried hard rebooting to go into recovery....it shows recovery mode at bottom for 10s and the reboots again to recovery mode text at bottom. It does not go into Menu of selection of English and Chinese language. This continues infinite times...Until finally it decides to boot to main home screen. But the Power button and Emergency screen/Reboot screen issue continues..
4) I tried factory reset of system setting...Same issue remained.
5) I finally tried factory reset wiping all data..Since the Version is latest C.49, which I believe has issues, the Emergency screen and Power Reboot Screens and Power Button not functioning properly continues..
6) I downloaded CPH1861EX_11_OTA_0490_all_sWtP8RDIvyoU.ozip from realme support. Tried updating that software in the phone..
But it lead to point (3) which I stated above...Same vibrating/rebooting after every 3 to 5 secs but not going into recovery Mode..It continued for 1 full day until battery died..Then I charged the phone for sometime and it continued its same funky routine of infinite rebooting and stopping at recovery Mode text.
But, eventually, after few hours, it booted normally to main screen.....But the problem was still there.
7) Now, even if try to shut down..from Power reboot/off screen...It shuts but in few seconds reboot again to main screen. So I cannot even shut it down.
8) I may try to download C.48 version (2.16 GB) and update from SD Card somehow..I don't know if it will revert back to different Version...But gotta try.
Or if there is enhanced or latest or custom update newer than C.49 available in market. maybe I should root or install that.
Frustrating...
How to get rid of this bug? I guess have to wait for new patch or something or next update. Service Centers are not open..because of Lockdown in Mumbai.
Please help, if someone knows the solution or had to deal with similar issue.
Click to expand...
Click to collapse
Alright, Is Your Bootloader Unlocked?