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!
Related
Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden
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.
Hello Everyone,
I did some foolish things to my TF300 and I'm hoping somebody can help me out.
I unlocked it and installed CM10 and life was good ! then I upgraded to CM11, and finally CM12.
I had a lot of problems with CM12, most of which revolved around constant messages that various google apps stopped working (Play, calendar, gmail, etc).
So, I decided to roll back to CM11 and that's when the problems started. I ended up formatting and wiping and doing all kinds of things that I can't remember (yup, foolish).
So now I can boot into twrp 2.8xxx but there are no .zip files visible to install. If I reboot w/o going to twrp Android starts to load (I guess it's CM12) but I can't even select the language because of constant messages about google apps that stopped. I downloaded CM10 and gaaps 4.2 to my computer, and then to a flash drive. I have a tablet keyboard so I booted to twrp with the keyboard attached and hoped to install from the flash drive, but it doesn't seem to be recognized.
So, any suggestions as to what I should do to get my tablet working ?
Thanks for any help !!
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
Hi,
i wanted to install pixel. But i got bootlooped, so i went back to the Stock Firmware and Stock rom "miui_HMNote6ProGlobal_V10.3.3.0.PEKMIXM_2f80798173_9.0" when i dont recover my apps from google the camera is working, when i do recover my apps the cam is not working anymore.
So i wanted to install the google camera
But 2 problems occur: 1st i have to reflash the recovery to get into twrp each time i want to go into recovery
2nd When i m in recovery i have to "decrypt" the phone by wiping the data partion, which i dont want to, i just want to install the lets call it "googlecamera".zip
So is there a way to a) get twrp as standard recovery for volume up and powerbutton? mine is always the useless Xiaomi 3.0 recovery
b) have the data always encrypted
c) get the bloody camera working again
EDIT: Camera is working again, its been the launcher, deinstalled evie, reinstalled it all fine. But still got question 1 and 2