Database Info

Every Restart, System not Responding?

So i'm using the AOKP Milestone 6 ROM and I recently installed a version of ClockworkMod Recovery and now every time I reboot, the background is black. Once I unlock the screen, a message pops up and says "System is not responding" and it asks to Wait, Report or OK. Once I hit OK, it proceeds to close System (I assume) and restores my phone normally. It seems to freeze every now and then in Settings once I select any of the menus every now and then, but other than that it's fine.
Also, I updated ClockworkMod Recovery from one of Sk8er's threads and it still seems to do the exact same. I've Fixed Permissions from the ROM Manager app and inside of Recovery mode. I really do not want to re-install this mod as i've spent hours and hours customizing it to my liking.
Any help would be greatly appreciated!

Serfma said:
So i'm using the AOKP Milestone 6 ROM and I recently installed a version of ClockworkMod Recovery and now every time I reboot, the background is black. Once I unlock the screen, a message pops up and says "System is not responding" and it asks to Wait, Report or OK. Once I hit OK, it proceeds to close System (I assume) and restores my phone normally. It seems to freeze every now and then in Settings once I select any of the menus every now and then, but other than that it's fine.
Also, I updated ClockworkMod Recovery from one of Sk8er's threads and it still seems to do the exact same. I've Fixed Permissions from the ROM Manager app and inside of Recovery mode. I really do not want to re-install this mod as i've spent hours and hours customizing it to my liking.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
you have no choice but to wipe/reset then install backup or reflash rom

Not too sure what I've done, but it's back to normal now!
Sent from my SGH-I727

I finally made it, Soft-Brick in another Way... -.-

Yeah, i finally made it. I bought a TMO-DE One S (With S4 Processor) 5 Days ago, unlocked the Bootloader (HBoot 1.09), rooted and SuperCID´d it, installed CWM Touch and installed TrickDriod V8.0 incl. its Tweak Package. After that i installed another Radio and everything was fine. It could have been SO easy, but i just HAD to do more, and now its soft-bricked.
At all TrickDroid is a really good ROM, but i hated the thingy that it shows G symbol instead of H when getting HSPA speeds. So i decided to dump it and go for a 4.0.4 / Sense 4.1 Stock Rom without branding instead until a JB / Sense Rom comes out. And thats were the trouble started. i flashed the stock rom with CWM, installed the boot.img that came shipped with it and booted it up. I did a full wipe before flashing. It booted up, Sense Stock Background Image came on and it showed "Unfortunately Wiper App is closed" at the "Preparing phone storage" stage. After OK´ing that another Screen came up about some system service wouldnt respond (dont know the exact Text anymore) wich i could close or wait for it. No matter what i do, or if i do nothing, after ~20 seconds the phone crashes and restarts. After the first restart the phone only boots into a black screen but with the Android bar at the top is working with time, battery-charging and a warning smybol. But the Phone wont react to anything i do except for lockscreen button. When its "online" i can push files via adb to the internal SDCard so i thought it wouldnt be a big problem. i pushed ONE MaximuS V2.5 ROM to the SD Card, booted into CWM and installed it. then flashed the boot.img of it via fastboot and booted it up. but nothing happens. still black screen with bar on top and not reacting phone that reboots every 20 seconds. i allready tried full wipe, cache wipe, dalvik cache wipe and i dont really know what to do now.
A broken SD Partion cant be since i can push files via ADB to it and install them with CWM. But whatever i try to install every ROM boots only in this blackscreen. its clearly not hanging in bootloader, but in android itself. I dont really know what to do, and returning to my dealer is no option since Rooting, SuperCID´ing and flashing another ROM. You maybe have a Idea what to do now?
Peace
TK
PS: Sorry for my bad english, hope you can understand it
Edit: Okey, i got something. i formatted everything i could in CWM, and now (as its now supposed) it hangs in bootloader since no system is there for booting. The good thing is in CWM i get ADB Connection so i can still push files to the SDCard. Im now trying installing a ROM again. So at least i have a starting Point if it fails again
Edit 2: Okey, found it. The "Stock" ROM is broken, not my Phones Fault. and MaximuS just doesnt install right so nothing was changed. Installed TrickDroid again for testing and everything is fine again. Close this one...

Stuck in a loop, need help

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

[Q] Stuck in bootloop after Cyanogenmod install error

Hi folks,
This evening I decided to install Cyanogenmod on my Moto G. All seemed to go fine until I started getting "Unfortunately, System UI has stopped" errors that meant I couldn't even get into any of the phone's menus. I tried to reset the phone to reinstall the ROM, but got stuck in a boot-loop where the phone won't boot to allow my PC to see it, so I can't copy the necessary files to it to re-flash the ROM. I also can't push them with ADB for the same reason.
I am stuck! Please offer any advice. Thanks!

evh5150ni said:
Hi folks,
This evening I decided to install Cyanogenmod on my Moto G. All seemed to go fine until I started getting "Unfortunately, System UI has stopped" errors that meant I couldn't even get into any of the phone's menus. I tried to reset the phone to reinstall the ROM, but got stuck in a boot-loop where the phone won't boot to allow my PC to see it, so I can't copy the necessary files to it to re-flash the ROM. I also can't push them with ADB for the same reason.
I am stuck! Please offer any advice. Thanks!
Click to expand...
Click to collapse
did you install a custom theme? does your computer recognize your phone when in recovery?

Just a failed installation of Cyanogenmod. Windows can recognise the phone but gives an error when installing the driver, meaning I can't copy anything to it to re-flash.
On the phone itself, I can get into TWRP in recovery mode, but I don't know how to get files onto it to re-flash.

evh5150ni said:
Just a failed installation of Cyanogenmod. Windows can recognise the phone but gives an error when installing the driver, meaning I can't copy anything to it to re-flash.
On the phone itself, I can get into TWRP in recovery mode, but I don't know how to get files onto it to re-flash.
Click to expand...
Click to collapse
Go to my profile, and I started a thread about this. Go to "started by".
My work: SmoothGKernel for the Moto G, and remember always hit the thanks button if anyone helped.

Lost WiFi and other features after switching from Slot B to Slot A

I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working

One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.

shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.

MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...

You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.

We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.

I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.

shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.

shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask

What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.

shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6

Helium is a great alternative to titanium.