Database Info

[Q] Clockwork Recovery Stuck in "Recieved Files" while restoring a backup

Alright, so here's the issue. I searched and could not find anything close to this...
I have stock JH7 installed. Installed Clockwork (via Rom Manager,) backed up my ROM, Metamorphed a theme, didn't like the theme, tried to use Clockwork to restore from my backup. Clockwork would go through all of the files, but when it gets to "ReceivedFiles," it just hangs. I let it run through the night, approximately 5 hours, and in the morning it was still in the restore process at this same step. I knew something was wrong, so I unplugged, removed battery, and booted it up. My phone just sat at the Galaxy 'S' screen and would not start up.
After several more attempts with 2 different backups (always hanging at the same place) I finally wiped data, cache, & dalvik cach, then booted it up. All was well and working stock. Then I shut down, booted into recovery, opened Clockwork, and attempted to restore again. My phone is currently sitting at the same step as before.
Any clues? I've attached a picture of its screen.

Did you pull the battery out? Mine is stuck as well....was updating to Serendipity 5.1.
Finding update package...
Opening update package...
installing update....
And it's been there for over half hour
I pulled it and can get back in the phone just fine. It seems to still get stuck there though.

[Q] Boot Loop after Cyanogen Mod install. Help me please.

Hey folks,
I could desperately use some help here...
I rooted my Droid Incredible using UnRevoked, which was painless and easy. After that, I downloaded Rom Manager, then backed up my current Rom.
Then I downloaded Titanium, and backed up all apps and system data.
Using Rom Manager, I downloaded Cyanogen mod 7.0.2, checked google apps, DID NOT check wipe data or cache, and then clicked OK to let it work it's magic.
The system turned on and off a bit, and then the CyanogenMod boot screen came on, ran the arrow around the droidbot a few times, then the droidbot dissapeared, came back across the screen, and the arrow resumed circling. This happened about 20 times, before I gave up and powered off by removing the battery.
Then I loaded Hboot, and attempted to access items in Clockworkmod, but even though I could click on an item, it would show the top hat with no change in status for many minutes. I eventually tried almost all options.
My Hboot screen shows:
HBOOT - 0.92.0000
Radio- 2.15.00.07.28
I am unable to click on Fastboot, Recovery leads me to busted Clockwork menu, Clear Storage causes restart into looped Cyanogen Mod screen, haven't tried Simlock, and Factory Reset also goes to broken Clockwork Menu.
I downloaded the RUU file from Doug, changed the title as directed, and put it on the SD Card. It gave me the option to Update, which when restarted afterwards continued to loop in Cyanogen Mod screen. Or, if I went to Clockwork Mod screen, the font was now Green instead of Orange. Also, when I click an item in the Clockwork Mod menu, it simply goes to a black screen until I hit the power button to bring me back to the menu,
I'd love to just get the phone to a factory state, so I can possibly use it for it's purpose of calling and sexting (just kidding.)
Please help, any advice would be greatly appreciated.

Oftentimes, ClockworkMod Recovery has an error at the bottom stating:
E:Invalid command argument
I have to go to bed for a bit, but will be back on around 10:30am EST. Thanks for any and all help!

In ClockworkMod, I can now access and start an operation by selecting it with the volume buttons, and then hitting the joystick button. This wasn't working previously. So, I've tried some of the obvious options such as Factory Reset but it's not doing anything. I've tried multiple solutions, which means I've probably messed it up on many levels. Is there any way I can just start from scratch or get a system restore done?

After utilizing that update from Doug, and then going into Clockwork Mod, clearing all caches and system data, and then trying to restore to a previous flash for the 7th time... I think it might be working!
Thanks to anyone who looked at this.

Need Help ASAP

On my phone I was running CM10. I recently downloaded the nightly for CM10.1. So I went into CWM, flashed the new 10.1, Gapps, then wiped Data and Factory Reset. When I was done and rebooted my phone, It gets stuck in a loop of "Unfortunately Setup Wizard has stopped. I try to turn the phone off but the power button seems useless. Is there a way for me to fix this. Any help will be greatly appreciated!
To make things worse my PC crashed a few days ago and I had to purchase new Hardware and is back up and running, but with a fresh install.

FinalTrigger said:
On my phone I was running CM10. I recently downloaded the nightly for CM10.1. So I went into CWM, flashed the new 10.1, Gapps, then wiped Data and Factory Reset. When I was done and rebooted my phone, It gets stuck in a loop of "Unfortunately Setup Wizard has stopped. I try to turn the phone off but the power button seems useless. Is there a way for me to fix this. Any help will be greatly appreciated!
To make things worse my PC crashed a few days ago and I had to purchase new Hardware and is back up and running, but with a fresh install.
Click to expand...
Click to collapse
If you can't turn the phone off then pull the battery.

So I am able to get back into CWM. New Problem...When i go to chose zip from internal SD card, i get 3 options:
-0/
-legacy/
-obb/
When i go into the first one I see my downloads folder, when i go to it says "No Files Found". Ok.....so i go to my external SD and select a different zip I get the dead Andy and it says
"E:Cant open/external_sd/(Rom Zip)
(bad)
Installation Aborted

FinalTrigger said:
So I am able to get back into CWM. New Problem...When i go to chose zip from internal SD card, i get 3 options:
-0/
-legacy/
-obb/
When i go into the first one I see my downloads folder, when i go to it says "No Files Found". Ok.....so i go to my external SD and select a different zip I get the dead Andy and it says
"E:Cant open/external_sd/(Rom Zip)
(bad)
Installation Aborted
Click to expand...
Click to collapse
You should have choose O. It also helps to remember where you put the flashable zip of the ROM.

"Unfortunately Setup Wizard has stopped." is because you flashed the wrong gapps. make sure you have the latest for CM10.1 which i believe is 20121212.

[Q] Any tips on how to unbrick my phone?

Somehow my phone is bricked, although I still am not sure if it's because I actually did something wrong or it just decided to brick itself out of spite. Here's the rundown of events:
This past August I rooted my phone and installed cm-10.2. I made a backup of the stock rom beforehand (which for some reason is dated from 1970). Since then there have been a bunch of bugs, but nothing super major.
Today I decided to upgrade to cm-11, so I backed up everything important to my PC and used the auto-updater. I got a Status 7 error and the installation didn't complete, and I got stuck in a reboot loop that kept returning me only to the bootloader. I read on another forum that the problem was probably my CWM version (6.0.1.2 instead of 6.0.1.3). Anyway, I tried restoring one of my backups, but the bootloader said the folder was empty and no backups were found. I ended up reinstalling cm-10.2 and gapps from the same zip files I used months ago. This let me properly boot up my phone, but for some reason the google play store still wasn't working. I did a simple reboot and it started working again, so I downloaded rom manager and updated cwm. Rebooted into bootloader, made another rom backup, and tried again to install cm-11. Same error, install aborted. This time, however, my backups magically reappeared (along with an extra mystery backup that had today's timestamp but was ~10 hours in the future), so I restored the original (1970, stock rom). Things boot up fine.
I decide to try installing cm-11 one more time because at this point I assume that if it fails again I can safely restore a backup or at the very least reinstall cm-10.2. It fails again, but this time, when I try restoring any of my cm-10.2 backups I get a DM5 mismatch error and it immediately stops. Restoring 1970 is different, it starts recovering but then halfway through says "error restoring /system" or something like that. So now I'm left with no choice but to reinstall cm-10.2 from the same zip file again. Only this time, booting up only shows the cyanogenmod logo forever. I go back into bootloader and my backups are once again suddenly not recognized. I make a new backup of my broken phone to see if it will make the folder show up. I reboot, and now that new backup is the only one that does show up. Trying to restore gives me a DM5 error. I've now tried reinstalling cm-10.2 several times, but my phone will never get past the cyanogenmod logo. I'm out of ideas for how to get my phone to work.
My questions:
1. Any idea how to unbrick my phone? I have not done any factory resetting because I was worried it would erase my backups and also I don't really see how it would help.
2. Does anyone have a backup image I could use? I don't have mine stored anywhere but on my phone's internal SD, but I could maybe try loading one from my external SD if I had one.
3. What did I do wrong here? From my viewpoint it seems I basically tried the same thing twice and got different results. Is there something I'm missing?
4. If I get a new photon q, how the hell should I go about installing cm-11? I know people have gotten it to work before. Which version are you using?
Thanks for any and all help

I'm guessing you don't have a backup of stock?
Have you tried restoring stock everything using RSD Lite?
Also, how long have you let the phone sit? If the phone requires a 'fsck' (file system check) on you /data partition, you could be waiting for an hour or more at the boot animation.

I do not have any backups stored externally. I'm not familiar with RSD lite, could you explain and/or link? I have only left my phone for about half an hour at the most before hard rebooting it. I'll let it sit for a couple hours and see if it does anything different.

DRH48 said:
I do not have any backups stored externally. I'm not familiar with RSD lite, could you explain and/or link? I have only left my phone for about half an hour at the most before hard rebooting it. I'll let it sit for a couple hours and see if it does anything different.
Click to expand...
Click to collapse
See this thread for information on how to restore stock... always a good idea to know how to reset the phone back to a complete stock configuration

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.