[Q] Subsystem crash - G2 Q&A, Help & Troubleshooting

I went from latest Verizon update and rooted, back to stock and early tot file before the update. It all worked fine and installed, but I keep getting the phone going to an orange screen saying Subsystem Crash. What should I do now?

Related

Update available on Mot software updater now

I had previously tried to update OTA and with the Moto sofware updater more than 20 times and either way I tried always said no software available and the phone was up to date. Today I went to the software updater and it had found the new software. I did this time connect as mass storage device, not sure if that had anything to do with it but those that had issues updating before go try it out now.
I got 4.1.83 OTA about 20 mins ago. Problem is it reboots and starts extracting and craps out.
I'm running stock, rooted and I manually uninstalled some of the bloatware...any ideas on what I need to do?

[Q] Camera issues fixed only 4.1.2 ota?

Hello,
I will try to keep this short. Was running 4.1.1 and rooted with moto2fail and installed safestrap recovery then I made a stock backup.
One day, my camera quit working (camera screen loads then a box pops up saying unfortunately, the camera has stopped) Anyways, I cleared data, rebooted same results. I didn't want to mess around with any files, so I decided to update to 4.1.2.
After the update, i get message that the update failed but everything seemed to be fine. AND the camera started working again.. Ending up losing root in the process, motochopper appears to install fine, but I get an error message when trying to update supersu. So, I reverted back to my 4.1.1 backup through the rp(?) tools in the stock recovery.
So now I'm back to 4.1.1 with full root, but no working camera. I can update to 4.1.2, but I think I'm gonna have problems with rooting again.
I did try reinstalling the stock MotCamera.apk from a stock razr m 4.1.1 rip. but it still fails. How can I fix the camera issues without having to mess around rsd lite?
Sorry about the confusion, just trying to lay out my issues and I will answer questions as I can.
i'm having the exact same issue, after failing to update to 4.1.2, i restored to 4.1.1 backup i had, but the camera just force closes. i'm on stock room.
bobross82 said:
Hello,
I will try to keep this short. Was running 4.1.1 and rooted with moto2fail and installed safestrap recovery then I made a stock backup.
One day, my camera quit working (camera screen loads then a box pops up saying unfortunately, the camera has stopped) Anyways, I cleared data, rebooted same results. I didn't want to mess around with any files, so I decided to update to 4.1.2.
After the update, i get message that the update failed but everything seemed to be fine. AND the camera started working again.. Ending up losing root in the process, motochopper appears to install fine, but I get an error message when trying to update supersu. So, I reverted back to my 4.1.1 backup through the rp(?) tools in the stock recovery.
So now I'm back to 4.1.1 with full root, but no working camera. I can update to 4.1.2, but I think I'm gonna have problems with rooting again.
I did try reinstalling the stock MotCamera.apk from a stock razr m 4.1.1 rip. but it still fails. How can I fix the camera issues without having to mess around rsd lite?
Sorry about the confusion, just trying to lay out my issues and I will answer questions as I can.
Click to expand...
Click to collapse
It could be that the Update has updated the firmware of the Camera itself, causing it to now be incompatible with the older 4.1.1 drivers baked in.
Typically when I get into these types of scenarios, I always feel best doing something along the lines of an RSDlite wipe and start fresh. Do the update straight, then customize afterwards.
I would unlock your bootloader prior to guarantee you have a back door into the phone afterwards.
I can't rsd back to 4.1.1, i get a preflash verification error, the only thing that works is matt's new utility that flashes to 4.1.2, the camera works after that, but i want the camera to work on the backup I did when i was on 4.1.1 before the update.
cybrnook said:
It could be that the Update has updated the firmware of the Camera itself, causing it to now be incompatible with the older 4.1.1 drivers baked in.
Typically when I get into these types of scenarios, I always feel best doing something along the lines of an RSDlite wipe and start fresh. Do the update straight, then customize afterwards.
I would unlock your bootloader prior to guarantee you have a back door into the phone afterwards.
Click to expand...
Click to collapse
I ended up booting in stock recovery by trying to get into fast boot, then selecting ap or rp tools(can't remember which). Truthfully, didn't even realize what it was. It loaded up what to me looked like the recovery menu with safestrap. Which I thought I uninstalled. From there, i restored the 4.1.1 backup I had. Then updated superuser and supersu from the play store. read in another thread to check and uncheck temp unroot in voodoo ota. twice.
Then I took the 4.1.2 update, was then able to install the supersu binary once it was finished and checked, and it kept root through the update. Camera works also. I still received a update fail message afterwards. But all appears to be okay, camera works, root checker says I have root, so all appears to be good.
I did make a backup of this in safestrap, and updated my backups in titanium, and froze a bunch of apps. Everything seems to be working just fine. I haven't unlocked the bootloader because I don't really feel like flashing any roms to this phone. Stock rom and rooted seems to be be good enough for me. For now.
If you still have a locked bootloader, you can't revert back without having issues. Once you've installed 4.1.2 and its boot.img, you shouldn't be able to restore a 4.1.1 ROM. If you are unlocked, then it's a different story.
For the OP, the best solution is to use Matt's Utility 1.20 and fastboot flash to 4.1.2. This utility does not require the use of RSD. After you flash, boot up the phone and just do basic setup, then use the Motochopper function in the utility to get root access. After you get root, then continue set up on the phone.

4.3 ota prompt popping up after already updated

Hey all,
I installed the 4.3 ota update back when it was first released in August, and it was rooted, lost root and rerooted. Nothing else I have changed.
Today is the 3rd time since updating back then has my phone recieved the ota prompt. First time I just went through and it restarted. 2nd time it gave a boot error and this time it just restarted the os. Like I said it doesnt come often but I just wanted to know if anyone has had this issue and Im going to assume I need to wipe the phone and a stock image?

[Q] 4.3 Update Failed? GS4 google edition

So I finally got the 4.3 update. My phone was all ready to install the update so I tapped update and install and started to reboot and install like normal. As it was installed in the stock recovery, all of the sudden it displays the message "error!". Then it reboots back into the same version of android and a few days later, it says it need to update to 4.3 and the cycle starts again. Any one know what is going on? Thanks

Problems after flashing stock rom on my galaxy s7 edge

Hey guys, I had custom rommed my phone a few months ago and got tired of its problems so I went back to stock. I had the Echo illusion ROM and apps kept crashing, Bluetooth would disconnect after a few seconds of not having any music playing, ect. So I flashed Verizon stock rom with Oden and it worked on the first try. But after going through the set up process I saw it had an update. So I updated my device and it looked like it worked just fine. But then it popped up again saying I had a software update available. After going through that process again I saw that it still is at the same software it was at before the update, and it's still saying there is an update available. Any suggestions? The only thing I can think of is getting Verizon software manager and updating it from a computer. But I don't even know if that would work

Categories

Resources