purchased already rooted verizon s5. developer edition. kitkat 4.4.4, cm11, twrp installed.
i loaded titanium backup which i used on my prior phone (that was a razr maxx with os 4.?, cm (cant remember version), safestrap). ran a titanium backup. assumed it wd create a fresh backup for my new device.
upon rebooting, CM blue circle appears and runs then i get screen with time/weather in top half. dialpad on bottom half with label "verizon wireless emergency call".
only new thing was running backup. didnt try to restore prior copy of backup. could this have somehow erased part of my CM?
my old phone always had the safestrap pop up as it loaded so cd go into safe mode. thought briefly about loading safestrap prior to backup....but assumed twrp wd function the same.
if i press power+vol up+vol down: get maint boot mod. can pick safe mode. get s5 screen then CM blue circle and back to emergency dialer.
any way to reload CM w/o wiping the entire device?
appreciate any help with this. im somewhat tech savvy but new at the whole rooting thing.
pamdavisus said:
purchased already rooted verizon s5. developer edition. kitkat 4.4.4, cm11, twrp installed.
i loaded titanium backup which i used on my prior phone (that was a razr maxx with os 4.?, cm (cant remember version), safestrap). ran a titanium backup. assumed it wd create a fresh backup for my new device.
upon rebooting, CM blue circle appears and runs then i get screen with time/weather in top half. dialpad on bottom half with label "verizon wireless emergency call".
only new thing was running backup. didnt try to restore prior copy of backup. could this have somehow erased part of my CM?
my old phone always had the safestrap pop up as it loaded so cd go into safe mode. thought briefly about loading safestrap prior to backup....but assumed twrp wd function the same.
if i press power+vol up+vol down: get maint boot mod. can pick safe mode. get s5 screen then CM blue circle and back to emergency dialer.
any way to reload CM w/o wiping the entire device?
appreciate any help with this. im somewhat tech savvy but new at the whole rooting thing.
Click to expand...
Click to collapse
Maybe re-flashing the ROM (non-wipe) can help.
Best is to ask in the Verizon Galaxy S 5 Q&A, Help & Troubleshooting.
Good luck !
Thread closed and thank you.
Related
I've had a great experience so far with my xoom! I had it rooted and overclocked since the first day I had it!
Its starting to get sluggish and things are beginning to go a little wonky, so I'd like to reflash to either the stock honeycomb 3.1 installation, or one of the roms that I've seen floating around.
The trouble is that the minute I saw the 'encryption' feature, I used it. I did that before ever rooting or overclocking it.
I am now unable to reset to factory defaults. Here is what I've tried:
- using the menu option from inside of the settings area to reset the tablet to factory defaults: When I do this, it reboots and gets to a screen with a little android logo and a progress indicator - however within several seconds the progress indicator goes away and is replaced by that nasty little triangle with the exclamation point saying something isn't right.
- Booting into clockwork mod and formatting everything available to be formatted from CWM: This actually broke the tablet and I had to reflash things to get it working properly. However all of my user stuff and all the settings remained intact.
Does anybody know how to reset the tablet to factory default after its been encrypted? You guys know 50x more than Verizons support team will.
My only other option is to back up all of my data, "break" the tablet, then go use my warranty at the store to get another one. I'd really like to avoid that if at all possible.
What version CWM do you have? Flash the newest recovery if you flashed the recovery from ROM manager. If that doesn't work then flash stock software.
What version Xoom do you have? This is for 3g http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/2788-how-return-stock-3g-4g-hr166.html
You don't have to do the last step of locking if you want to reroot. That should also remove encryption. If it doesn't do a factory reset from settings. And verify CWM works as well.
I rooted my SCH 1535 and installed CM Version 11-20140215-UNOFFICIAL-d2vzw. Android 4.4.2 (Baseband: l535VRBLMD3) (Kernel:3.4.80-cm
It was working OK except in order to see my WiFi I had to reboot every time WiFi was turned off.
Plus I was having trouble updating ROMs with ROM Manager.
I had both TWRP & CM installed, although the phone defaulted to TWRP in recovery.
I downloaded seveeral CM ROMs via the CM updater in Settings > About Phone & wasn't able to flash.
So, I (stupidly) WIPED with TWRP
Now, I still have the CM KitKat ROM on my phone but when I try Play Store it starts & immediately closes.
Android Keyboard stops as soon as I boot up, so i can't log even into my Google account.
I'm pretty sure I'm no longer rooted & there's no recovery - in fact the Return, Menu & Volume buttons don't seem to work.
Most of my apps are gone except for Google & Samsung, but I can't log in.
I did do a nandroid backup & have Internal & Card backups on my PC as well as Odin.
So, my question is Should I try to restore to stock and start over? (What's the best way to do that from my build?)
or do I go for a KItKat ROM? (any suggestions?)
I want to make sure I have the proper recovery, bootloader (SuperSU_Bootloader_FIXED.zip ?)
I am wide open to suggestions on the best way to proceed. I'm really hesitant to try the Factory Data Reset - since I've heard that can brick a phone completely.
Thanks!
Earlier today, I got an error upon starting up my Samsung Galaxy S5 (T-Mobile) that says "Unfortunately, System UI has stopped." My background has been turned to black and none of the buttons work properly. The phone IS rooted (and has been for about a week), but runs on stock OS (5.0 Lollipop) and stock recovery. I have never flashed a rom on this phone. I already tried restoring from a Titanium Backup I made yesterday before this error ever showed up, but it did nothing. Perhaps it's relevant that this error first happened after I booted the phone in recovery mode (to see what stock recovery looked like), then selected "reboot phone." I also already tried wiping the cache partition, wiping the System UI cache, and rebooting is Safe Mode. None of these worked. I thought unrooting the phone might help, but I accidentally uninstalled SuperSU without removing the root. With the System UI down, I can't install any apps at all, such as SuperSU again or a file explorer that would allow me to remove the "su" folder in /system/bin/. Now I have no way of unrooting, short of wiping the phone. I DO NOT want to do that. How do I get my phone back to normal?
--EDIT-- I finally gave in and did the factory reset. I rooted it again using the same method as before (in order to use Titanium Backup), and just to see what would happen I went to recovery mode. Sure enough, I was greeted with the same error as before. I had already rebooted the phone normally multiple times before trying to use recovery mode, so I have no doubt that the stock recovery mode is the cause of these issues.
Signal2Noise said:
Personally, I don't like Titanium Backup. I seem to be in the minority with that opinion, but it's given me issues in the past. Try flashing a non-stock recovery like TWRP for your S5 and either wiping your phone or wiping and flashing another ROM.
Samsung phones seem to dislike rooted users for some reason
Click to expand...
Click to collapse
Too late, I already wiped the phone. I re-rooted using Chainfire's auto-root, then flashed CWM so that stock recovery doesn't screw me over again. Before restoring from the backup, I booted into CWM recovery and restarted the phone. No error. I hope it stays that way, this whole thing is a huge hassle. There really needs to be a disclaimer with Chainfire's auto-root telling people to get rid of stock recovery!
Hi there
You'd be best served asking for help from the experts who own your device, here:
T-Mobile Galaxy S 5 Q&A, Help & Troubleshooting
Good luck
When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet
Objective: I am hoping to be able to boot my existing system to recover data such as SMS, call logs, app data, and so on - obviously it was inadvisable to start messing around without backing up my data, particular with my amateurish capabilities. But that's the situation I am in. For some reason I thought that just replacing the Recovery was not going to risk my data. Its been over 5 years since the days when I would regularly flash my new phones with cyanogenmod, and my abilities were very basic even then.
Context: G930FD with stock rom, baseband ETC? - apparently for Dubai, which does not allow VoLTE or WiFi calling, which is what I was trying to fix when I got myself into this.
the Events:
- I enabled ADB and used Heimdall on Windows 7 to flash twrp-3.3.1-0-herolte.img
- initial attempts failed to complete download. I booted back into the system and applied OEM Unlock. Flashed successfully.
- chose the 'allow modification' option or whatever it says, not the Read-only option
- I did NOT check at that point to see if the system would reboot properly. I instead right away made a full back-up to my external SD.
That's all I did. After the back-up was complete I rebooted, and arrived at "SAMSUNG Galaxy S7" endless boot loop.
best guess: this is related to samsung encryption? TWRP file manager says that DATA is 0MB.
Again, I am desperately hoping that someone can help me recover my existing system. The threads I found on this subject all lead to wiping the phone and flashing a new rom.
thanks.
digging in deepr
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
t.krug said:
I went ahead and rooted by loading SuperSU otg through TWRP.
Now I get passed the first splash screen that was previously boot looping (Galaxy S7, powered by Android), and I get to the 2nd splash screen (glowing SAMSUNG logo). It does not boot loop, just glows in and out endlessly and never loads.
Is that progress? Or maybe its worse.
Click to expand...
Click to collapse
Reflash TWRP with Odin, boot TWRP, wipe cache, reboot.
Thanks.
I think greenman at sammobile had the answer --> NEW: S7 5 file firmware options (this forum wont let me post a link).
But I botched the execution and the CSC file overwrote my data. Crushing blow. I would say lesson learned, except that I already knew better and risked my data anyway. Sad.
I have a backup I made at the first launch of TWRP - but I assume its worthless since TWRP was not reading the encryption. Its only 3.7GB.
Side note - I did achieve the original goal of replacing the Emirati rom with one that activates WiFi calling and VoLTE.
Has this issue been solved?
I never recovered my data if that's what you mean. Did you look up greenman at sammobile? It sounds like someone followed his directions and was able to flash just the system files without overwriting their data. I think you had to modify the csc_home file. It was a bit beyond my skill level.
Oh, I was just wondering if your phone was still bricked. I didn't read your last message properly before replying lol. My bad.
I'm not personally having issues with a device, I was just curious if I could help at all.