Develop Bugs

[Q] After CWM upgrade cannot start or restore phone

I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks

northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app

northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message

Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"

I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium

I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse

stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?

In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.

Same here, stay away from that update! Bad things!

This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?

Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...

I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP

I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium

xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!

xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.

J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.

[Q] CM bootloop after rooting

I will try to keep this brief and clear; hopefully someone will be able to help.
I was following this xda guide to gain root access through Odin3, using CF-Auto-Root. Originally, I thought the process had failed, because KNOX showed me an alert that SuperSU was being blocked. However, I updated SuperSU through the play store and it managed to start up. It also asked me if I wanted to disable KNOX, which I said yes to. I downloaded another app called Root Checker which told me that I had root.
I then went on to install Rom Manager and download CWM Recovery. Rom Manager told me it was successful in flashing CWM, so I went ahead and downloaded the latest stable CyanogenMod along with Google Apps. Once it was done, I opted to install and restart. The CM logo with the two rotating circles managed to come up. However, these circles never disappear and after 20 minutes of waiting for it to load I'm pretty sure something is amiss.
Anyway, I figured I would restart to CWM recovery and simply install CM manually, following CM's own online guide. However, when I start up, I cannot enter CWM and ODIN MODE starts up. I have tried to flash CWM manually through Odin3 v3.07 as well as TWRP, but neither works. Odin3 says the transfer/installation is successful, then restarts the phone, but I am put right back into Odin Mode when I try to use the Power+Volume Down+Home button method.
Any ideas? To be clear, the phone will not boot into CM and I have (apparently) not been successful in replacing stock recovery. I am on international N7100 bought from Amazon.

rsanek said:
Odin3 says the transfer/installation is successful, then restarts the phone, but I am put right back into Odin Mode when I try to use the Power+Volume Down+Home button method.
Any ideas? To be clear, the phone will not boot into CM and I have (apparently) not been successful in replacing stock recovery. I am on international N7100 bought from Amazon.
Click to expand...
Click to collapse
You always get back to download mod if you use power+volume DOWN+home button, try power+volume UP+home button instead to get into recovery :good:

Androidwizzard said:
You always get back to download mod if you use power+volume DOWN+home button, try power+volume UP+home button instead to get into recovery :good:
Click to expand...
Click to collapse
Wow I am an idiot. I can't believe I didn't try this sooner. This got me to TWRP, I will update if I am successful in installing CM. Thanks!:good::good:
EDIT: I was indeed successful in installing CM after re-flashing with the newest CWM and entering CWM restore with Volume UP+Power+Home. I am now on ThdDude's CM11 build with Gapps via TKruzze and it is working like a charm. No problems that I could find except for minor audio issues.

Custom ROM for OH1 bootloader SIII

Is the OH1 bootloader compatible with custom roms that require nd8?
I want to put Wicked S5 Xperience on my SIII but it says must have nd8 bootloader and I did the ota to OH1 and rerooted w/ twrp and supersu.

OH1 compatible with custom roms
aschubart said:
Is the OH1 bootloader compatible with custom roms that require nd8?
I want to put Wicked S5 Xperience on my SIII but it says must have nd8 bootloader and I did the ota to OH1 and rerooted w/ twrp and supersu.
Click to expand...
Click to collapse
Hey all,
Answered my own question. Successfully installed wicked s5 xperience 2.2 (wih requires nd8) without a hitch. basically I followed the step by step with exception to. I used twrp... wich they dont support. I did a dirty flash... worked fine but all my old settings were still there, So I did a Proper clean flash and all is good. Way better modem.... than OH1. I have signal and data in places I used to not get.
Hope this helps anyone else.

I have a question, how did you go about installing a custom ROM with OH1.
I can't seem to use Odin to install TWRP. It says success but when I try to 'adb reboot recovery', it just goes to the stock recovery. Any idea on how to install a custom recovery?

TheFatDemon said:
I have a question, how did you go about installing a custom ROM with OH1.
I can't seem to use Odin to install TWRP. It says success but when I try to 'adb reboot recovery', it just goes to the stock recovery. Any idea on how to install a custom recovery?
Click to expand...
Click to collapse
Did you
Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery.
I got from http://forum.xda-developers.com/showthread.php?t=2787771
If odin says success it should boot to twrp.
Once I was in twrp I just installed my downloaded ROM. You probably will want to do a wipe first to have a clean flash.

aschubart said:
Did you
Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery.
I got from http://forum.xda-developers.com/showthread.php?t=2787771
If odin says success it should boot to twrp.
Once I was in twrp I just installed my downloaded ROM. You probably will want to do a wipe first to have a clean flash.
Click to expand...
Click to collapse
I ended up having to do that. For some reason Odin wasn't kicking me into recovery so I had to boot into recovery myself. Another issue that I noticed was that TWRP couldn't root stock firmware. It would install SuperSU but wouldn't install the su binary. I ended up just installing AICP.
Thanks for the help.

TheFatDemon said:
I ended up having to do that. For some reason Odin wasn't kicking me into recovery so I had to boot into recovery myself. Another issue that I noticed was that TWRP couldn't root stock firmware. It would install SuperSU but wouldn't install the su binary. I ended up just installing AICP.
Thanks for the help.
Click to expand...
Click to collapse
Glad you got it going.. I haven't tried Ice Cold looks like a solid ROM though.

Roms
Is there any rom for the l710vpudoh1?

Hi...Please can you get an OH1 modem for me? My phone has no service and im running android 6.0.1

Samsung Galaxy Tab S (10.5 Wifi) - "Semi-Rooted" Device Crashes on Reboot

Recently tried to root my Samsung Galaxy Tab S (I am not allowed to post links yet so I'll just say the site is techbeasts)
I believe I went through these instructions and followed them all precisely.
This method also installs SuperSU on my device..
However, I tried checking the root status with Root Checker, and it says "verification failed"
I then checked SuperSU, and it said something along the lines of "binary needs updating". I tried the "normal" method for doing this twice, but it didn't seem to work. There is an option presented in SuperSU to do this through TWRM or CWM, so I tried that option. ( NOTE I do NOT have TWRM or CWM installed)
**Then when I started the tablet, a whole bunch of messages came up saying "unfortunately, ____ stopped" [/B]and a whole bunch of these are there. I'm sure this is a crash.... **
I managed to get the tablet back to semi-working state by using the factory reset from the recovery partition (it's the stock recovery partition). However, the crash-on-reboot problem still persists.
Any help on getting back to working state? I can use the tablet but I cannot restart it as it will crash again (have had to do the factory reset from recovery twice now...)
I should mention that i am trying to:
1) have a rooted tablet
2) Not have these crash-on-reboot issues...
Bharat

Best would be to flash your firmware again with Odin. You can download your firmware on sammobile (see link below).
You will need Odin for this, the correct drivers on your pc and to have USB Debugging on (under Developer options in Settings).
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
Download supersu.zip as well (see link below, you can download 2.46 or 2.49 beta) and put it on the tablet or external sd card.
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
http://www.sammobile.com/firmwares/database/SM-T800/
http://forum.xda-developers.com/showthread.php?t=1538053
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Good luck!

Wow, how to massively over complicate something.
Just install the stock firmware, then look for my build of cf_autoroot in the dev section, flash in ODIN. Done.
If you want to upgrade twrp to the latest version you will find it in the dev section too. This version fixes some of the issues with the official version and has more options.

Hi guys,
TThanks so much for your replies! Complicated or not, anything helps...
I had previously used Odin to flash the rooted firmware to the tablet, so I amn faniline with the software.
Alta1r: looked at the links and it looks like sprue stock firmware. A couple of questions about this procedure:
1) Is it normal that the stock firmware file (as downloaded) is larger than firmware images used to root the tablet?
2) Would using TWRP to flash Supersu onto the tablet root the tablet, even if the stock firmware is installed?
Thanks again guys!!

Not sure what you mean with firmware images to root the tablet. Do you mean a custom rom? Those should be smaller in size yes, as the are usually de bloated.
Maybe you flashed a wrong version if a custom rom for your tablet before, that would give you problems when flashed.
Both my or ashyx's method can be applied on a stock rom. I'm running just stock with root.
@Asynx: I flashed the latest firmware on my T800 this week and twrp didn't stick after the first boot. Tried many versions, also the one you mention in the dev section, but to no avail. Even replaced the recovery in the samsung's tar file and flashed it like that: twrp screen showed up right after the flash, but on next boit it was stock again. Only way to make it stick was to reboot into recovery right after flashing it.
Never had that problem before though on the Tab S (did have it already once on Galaxy S6).
Edit: forgot to mention I hadn't seen there was cf-auto root available for our current firmware. If I knew it would have saved me some time. Could have flashed the recovery with Flashify afterwards.

Apologies I am still getting used to the lingo with this stuff
Have done some stuff with Linux and some tweaking in Windows as well, so figured this shouldn't be too bad...
@Alta1r: so the process you describe is what you said, flashing the stock ROM and then root it afterwards...
Will try this process and report results here
(aside: I think the tablet was working fine after flashing with CF autoroot ROM -- is that the right word? -- what I think ruined it was when I told Supersu to try updating its binary through TWRP or CWM....which isn't yet on my tablet)

Alta1r said:
Only way to make it stick was to reboot into recovery right after flashing it.
Click to expand...
Click to collapse
It seems since lollipop this has to be done if flashing over stock recovery or it will be replaced at boot with stock.
Twrp will patch the recovery install script at first boot.

Sooooo...
First off, thanks for the "luck wishing"
I decided to try the method of @Alta1r.
@ashyx - I tried the CF-autoroot thing before (this was first attempt at getting a rooted tablet), and this didn't work for me. So I wanted something a bit more "hands on".
This is procedure I followed and worked for me (as of this post):
1) Before I began, I accidentally went into recovery mode instead of download mode. So I had to restart the tablet *gulp*
....yet I was able to restart just fine (no crashed as mentioned in my first post). I think this ~might~ have something to do with the fact that I downgraded the version of supersu that was "updated" through Google Play, but I'm not really sure...
2) Downloaded all relevant files.
3) Flashed firmware for tablet as instructed:
Alta1r said:
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Click to expand...
Click to collapse
Result was that tablet booted just fine!
Made sure that a few apps worked OK, and also rebooted the tablet a few times to make sure it was stable
(this is a linux based system, not Windows, but I still like reboot tests for stability checking...)
4) Next I did the TWRP flash through Odin:
Alta1r said:
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Click to expand...
Click to collapse
TWRP flashed fine. But then....
5) Tried to boot into TWRP recovery:
Alta1r said:
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Click to expand...
Click to collapse
As predicted, Alta1r, the TWRP didn't flash properly. I got an error on the stock recovery saying:
"Error message is "E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)"
So I tried your odin + reboot trick as above, and this booted into TWRP recovery.
6) Then I flashed supersu.zip (had kept on microSD card that is in tablet).
Andddddd.....
Root checkers says all good
Thanks so much for the help guys. I wrote the procedure above for anyone else who attempt this method!

bsquared938 said:
Root checkers says all good
Thanks so much for the help guys. I wrote the procedure above for anyone else who attempt this method!
Click to expand...
Click to collapse
Glad to hear all went well, and by the looks of it had fun doing it.

Although computer/device problems can get me agitated, I still have fun in the end
Not sure if I can ask this here, but two other slight issues after the rooting:
1) Upon rebooting the tablet, I always get the message "android is upgrading", even if I didn't touch any apps through Titanium Backup or other root-only apps that are meant to remove pre-installed applications.
Is this an issue? And if so, is there a way to get rid of this?
2) I am able to uninstall/remove apps with Titanium Backup (freezing them isn't possible without the paid version of the app), but I am not able to restore them. I made a full backup before I started to uninstall stuff. I put on USB debugging mode in developer options, but still I cannot put apps back. Any thoughts on this?
Thanks again!
Bharat

I wouldn't worry about the upgrading message, most get that.
AFAIK TB requires a kernel that can be set permissive to fully function.
If you want the ability to remove and restore apps use system app remover (root)

ashyx said:
I wouldn't worry about the upgrading message, most get that.
Click to expand...
Click to collapse
Okay thanks, I will not worry about that upgrading message for now...
ashyx said:
AFAIK TB requires a kernel that can be set permissive to fully function.
If you want the ability to remove and restore apps use system app remover (root)
Click to expand...
Click to collapse
Is there a way to set this up? Even System App Remover does not let me reinstall stuff...
(I don't plan to ever use any of the apps I am removing, but I would like this feature for "sanity" purposes...)

bsquared938 said:
Okay thanks, I will not worry about that upgrading message for now...
Is there a way to set this up? Even System App Remover does not let me reinstall stuff...
(I don't plan to ever use any of the apps I am removing, but I would like this feature for "sanity" purposes...)
Click to expand...
Click to collapse
Are you sure you have full root?

ashyx said:
Are you sure you have full root?
Click to expand...
Click to collapse
Yes I am sure I have full root.
I used root checker to check if I have full root access and it comes back green (to say root access is good).
(Just checked again now before posting this...)
Using either Titanium Backup and Root App Deleter, I am unable to restore deleted apps...
I have enabled USB debugging in the developer tools, as instructed to by Titanium Backup....
I read something about the "mount namespace separation" in supersu, I might try to toggle that option to see if it helps this situation.

Root app deleter? Is that system app remover?
Also what is the error when you try to restore with it?

ashyx said:
Root app deleter? Is that system app remover?
Also what is the error when you try to restore with it?
Click to expand...
Click to collapse
App is called System App Remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
It tries to restore the app, and after about half a second it just says "try again if it fails" with a "yes" button to be selected...

bsquared938 said:
App is called System App Remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
It tries to restore the app, and after about half a second it just says "try again if it fails" with a "yes" button to be selected...
Click to expand...
Click to collapse
That doesn't mean it doesnt restore. It says that every time iirc. Check in system apps to see if it restores.

ashyx said:
That doesn't mean it doesnt restore. It says that every time iirc. Check in system apps to see if it restores.
Click to expand...
Click to collapse
Okay I'm just going to say exact issue...
I deleted calendar storage, thinking that it's part of Samsung's calendar app (when in fact it is used by all calendar apps).
So now Google Calendar doesn't show me my calendar....and I'm trying to restore calendar storage, but it's not restoring
(had previously deleted through System App Remover, but now can't get it back)
Edit: I uninstalled and reinstalled Google Calendar, and that seemed to bring back my calendar.....
Sorry to cause you this trouble, I guess I panicked too early...
But will still be careful of what I remove...

Alta1r said:
Best would be to flash your firmware again with Odin. You can download your firmware on sammobile (see link below).
You will need Odin for this, the correct drivers on your pc and to have USB Debugging on (under Developer options in Settings).
Unzip the firmware you downloaded and put it in PDA or AP in Odin, connect your tablet in download mode (power + home + volume down , afterwards volume up to 'continue') and click start.
Go to TWRP website, search for Tab S 10.5 and download the latest TWRP (tar-file).
Download supersu.zip as well (see link below, you can download 2.46 or 2.49 beta) and put it on the tablet or external sd card.
When this is done and your tablet rebooted (can take a while), reboot in download mode, open Odin again and add the twrp-tar you downloaded before (same PDA or AP).
Tablet should reboot as well after that. To enter recovery mode press home button + power button + volume up. This should bring you in TWRP recover. Flash the supersu.zip you downloaded before, reboot and you should have root.
http://www.sammobile.com/firmwares/database/SM-T800/
http://forum.xda-developers.com/showthread.php?t=1538053
Note: should the tablet reboot in stock recovery after you flashed the TWRP-recovery. Go to download mode again, fire up Odin but uncheck 'Auto Reboot' and flash TWRP-tar again. Once it's done, hold power + home + volume down, you will get to the screen again where it says volume up to continue volume down to cancel and reboot. Choose volume down but quickly press power + home + volume up until the screen turns on again. That should take you straight to TWRP recovery. You can flash supersu.zip and TWRP recovery should stick now.
Good luck!
Click to expand...
Click to collapse
worked for me thx :good:

rooted galaxy s9 exynos stuck in download mode, vol down + Power doesnt work.

Hey
Im new to rooting and yesterday I decided to root my galaxy s9. I used Odin to flash twrp and flash ' Disable_Dm-Verity_ForceEncrypt_03.04.2020 ' and Magisk v20.4. All went well.
Used Magisk hide to bypass banking apps. but I encountered a few social apps like Instagram that kept on crashing. So I searched up what the problem could be and came to an article where it said the TWRP app may cause interference and delete it and wipe cache partition from recovery mode.
I didn't delete the TWRP app yet and decided to boot into recovery via magisk. But then my phone booted into download mode. that's where the issue started.
Its the downloading do not turn off target screen but strangely enough doesn't have the small system writings the top left side of the screen. All it says is Vol down + Power to cancel but when I do that,my phone boot into this download mode again. I panicked and flashed twrp, Disable_Dm-Verity_ForceEncrypt_03.04.2020, and magisk again and I did get into the Teamwin recovery. formatted and installed all the necessary things. But when I reboot from there it rebooted to download mode again. As of now its still in download mode and im waiting for the battery to run out and the turn on my phone normally. Please help

Have you try to flash the stock firmware? The latest one would be nice

B1nz said:
Have you try to flash the stock firmware? The latest one would be nice
Click to expand...
Click to collapse
I will try that and let you know soon

b1nz said:
have you try to flash the stock firmware? The latest one would be nice
Click to expand...
Click to collapse
thank you so much mannn it worked!

HaadiM2000 said:
thank you so much mannn it worked!
Click to expand...
Click to collapse
glad to hear that

Hello
I have Samsung Galaxy S9 exynos. I rooted it and flash android 12 beta GSI and it booted fine. I however could not boot TWRP as the phone is stack up at TWRP recovery animation. It is not even allowing me to boot download mode to go back to stock.
I really need help