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.
Hi there,
I have a rooted 3G Nexus 7. I ran the notification to run an OTA update for 4.3 Jellybean, it rebooted into TWRP, and I blindly said yes. Eventually I confirmed TWRP to allow it to fix root permission. I tried rebooting, but I ended up getting stuck at the X screen. Tried a few resets, but that didn't work. I Googled a bit, cleared the cache and the dalvik cache on TWRP, and came across this.
I got lazy, and probably shouldn't have done most of what I had done, so I'd like to know if there is a way to fix this without having to reflash the ROM.
Fix
I got impatient waiting for a response, so I just flashed Cyanogen on it, thinking this would be the most opportune time to try it out hehe. To anyone else who runs into the issue and sees this, I'm 99% sure that you could just flash stock on too, but I wanted to try out a custom ROM.
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?
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
Just so everyone's aware, I got this boot loop too today with the following scenario:
Completely stock 6p, upto date with latest MM, never been rooted, flashed, whatever.
Signed up for beta N programme today
Immediately got the N OTA update
Installed it - it rebooted post install but back into MM not N.
Rebooted - it got stuck on the Google logo for 30 minutes
Rebooted - permanent boot loop
I can get into the recovery menu and bootloader, and have tried sideloading the latest 7 OTA but still have the bootloop. Reset/cache clearing all tried.
Annoyingly my bootloader is locked - I've never tried doing anything other than installing standard OTA updates from Google so was unaware that unlocking it might save my bacon until it was too late.
I guess it's a phone call to Google tomorrow....
Update - sideloading this installed OK but I still have the boot loop:
6.0.1 (MTC20F) Link 5a1e93e9974908a0683a4ac8a732b81023f4b01182fd3ead3f091f54300de5ce
So all is not lost. I have an unlocked bootloader, but everything else the same as you. Doesn't really matter as I'm unable to flash anything....even updated my android SDK.
Anyway, I too signed up for Android beta program this morning, and instantly got the N update. Boom bootloop. Non stop. Most I could get it was 20 minutes after a factory reset.
What has worked for me (since 12pm today) was a factory reset and upon signing in to setup. I didn't. I set it up like it was brand new and didn't take ANY restore of apps or data from Google. I added my Gmail after and it's up and running with no reboots for 8 hours now.
It really sucks. The only thing I was able to salvage were my ringtones and notification sounds. It's like starting with a brand new phone ( froyo days without titanium backup). Google has a list of all your apps in the store but reinstalling all of them and logging in is a real pia. Been at it all day. But I do have a functioning stable Android 7.