I'm currently running SR Remix KitKat and I'm tired of the bugs so I want to go back to 4.3. I've tried simply doing a full wipe and factory reset then installing SR 4.3 v3.1 but it just loops the boot animation endlessly. I've tried using both TWRP and Philz Touch recovery. After restoring my 4.4.2 backup all is working but I'm back to square one. Before I set about using Odin to flash back to 4.1.2 I would like to make sure I'm not wasting my time
UPDATE:
So I decided to try odining back to 4.1.2 and after unlocking with casual everything was working until I tried updating to SR Remix 3.1. This doesn't make sense because that's where I was when first updating to SR Remix. I have one last thought. When first updating to MJ9 I started with the "Beans Official" release. Maybe I'll try that before giving up.
UPDATE 2:
Well that's very strange, I used the Beanstown official stock release then installed SR and got it working. I wonder what's missing from Sophisticated ROM that is keeping it from working.
Related
Ok, I have a what i think is a rooted droid razr. I was on jelly-wizz rom and i went back to my stock rom with safestrap 3.11. My phone told me there was an OTA update that i did successfully and brought me to 98.72.16.XT912.Verizon.en.US (4.1.2). I had already manually updates the xmas leak so I was on 4.1.2 before the OTA. I erased the jelly-wizz rom slot and wanted to use the new Eclipse Razr JB v1.1 so I went threw all the steps and that and installed and activated the new rom. That put me into a boot loop. I then activated the stock rom and figured that I would start from scratch and unroot then root and start all over. The problem is i uninstalled Safestrap and didn't remove the recovery. I tried to reinstall safestrap and it takes but when i try to launch it it says safestrap has stopped and wont let me in. When i reboot, I get the safestrap menu saying it is disabled and can get into safestrap but any rom i install just puts me in a boot loop but I can boot to stock fine.
I just want to unroot and start from scratch and deleting all rom slots and factory reset does nothing. Any Ideas????
Use this to get you unrooted. It will take you back as if you never rooted, it will also delete your apps so back them up.
http://www.droidrzr.com/index.php/topic/12777-droid-razr-utility-xt912-jellybean-windows-mac-linux-all-in-one/page__pid__227369#entry227369
That was actually my next plan of attack. Worked like a charm. Made me unrooted and just had to start over from scratch which is fine. Nice that Matt has a root process built right into the app. I found out that the Eclipse JB Rom v1.1 can only be used on the xmas leak and if you do the official OTA then it just boot loops. That was the other half of my problem. Will just have to look for a new rom for the time being. Thanks!!
I think Jelly-Wiz has the same problem as the Eclipse. It just puts me in a boot loop as well. Guess I'll stay with stock for the time being
I had the same exact problem with the bootloop after updating to the Verizon OTA. I guess the kernel had some minor changes or something because any ROM built for the Xmas leak caused the same issue. I've been very happy using one of the CM 10.1 nightlies. Works like a charm even with the OTA update. I also heard of a ROM called FlyingJelly that works with the OTA update but I haven't tried it myself.
How do you do the cm10 mods. I've heard about them but haven't yet. Are they any different or better. I'd assume you use cm for them instead of bootstrap?
[Edit] I found out on droidrzr.com that there are actually 6 roms that work with the .16 kernel.
Aviator
Cyclone
Black Widow HDish***
Flying Jelly***
Rage ROM
Breakneck Blur***
*** These three have the circle widget from the Razr M (I'm guessing) I'm using the Breakneck Blur one and its really nice. Just over one page of installed apps and everything works great on it so far. I hate all the bloat that Verizon and moto put on these phones that you never use and cant uninstall.
My current configuration:
STOCK JB 4.1.2
AT&T
Screen Rotation selected
Things I have tried:
Gyroscope calibration (result: ball stuck in the middle)
Leveling Applications from Play Store (result: looks like it calibrated but did nothing ultimately)
Used *#0*# - Sensors (result: All sensors passed except image test)
I view my phone horizontal and the screen rotates to landscape as expected. I rotate my phone to normal position and the screen is still displaying landscape. It should be portrait. HELP!!!!!!!
Redownload and reinstall the firmware to insure it was not a corrupted download or bad write.
I forgot to mention that prior to updating to official JB, I installed CM10 JB 4.2.2 and screen rotation didn't work at all. So I restored to stock and it still was broken. It was working prior to installing CM10 JB 4.2.2. I came to the conclusion that it had to be CM10's version that messed up my settings with screen rotation. I restored to stock 2.3.6 and tried everything possible. I restored CWM backup image of working image prior to install of CM10. Still having the same issue. Last night, I updated to official JB 4.1.2 via Kies and thought that they may fix it. I was wrong....
studacris said:
Redownload and reinstall the firmware to insure it was not a corrupted download or bad write.
Click to expand...
Click to collapse
You've flashed several kernels at this point
Pretty much ruling out software issues (unless you've restored an app that's getting funky or something weird)
Kinda sounds like a hardware malfunction to me
jtrinh said:
I forgot to mention that prior to updating to official JB, I installed CM10 JB 4.2.2 and screen rotation didn't work at all. So I restored to stock and it still was broken. It was working prior to installing CM10 JB 4.2.2. I came to the conclusion that it had to be CM10's version that messed up my settings with screen rotation. I restored to stock 2.3.6 and tried everything possible. I restored CWM backup image of working image prior to install of CM10. Still having the same issue. Last night, I updated to official JB 4.1.2 via Kies and thought that they may fix it. I was wrong....
Click to expand...
Click to collapse
You are NOT alone. CM 10.1 broke auto-rotate on a LOT of phones. I'm currently flashing CM 10.1 from 4/22/13, since that version worked correctly, to see if that will help.
I read about another phone having the same problem a while back, and they had some weird, contorted way of fixing the problem that, of course, could not be done to the Note.
P.S. I have also tried installing CM 10.1 from 5/02/13. No joy.
I hope installing the new Stock 4.1.2 between CM versions didn't yak the phone forever.
I give up. Hopefully, someone will come up with a flashable .ZIP file that can fix this mess.
I had android 4.4 Omnirom on my phone earlier today and yesterday. Today there was an update for the nightly. I decided to download it and updated through the recovery as a normal update would've. However, after waiting for almost an hour for the android is upgrading prompt to go away, I figured it was stuck in a boot loop. Well it turns out it more than likely was so don't say I'm impatient :d. So I forced it to shut down and it rebooted, but it didn't get past the Omni logo for almost an hour as well. So I decided to downgrade to the previous nightly. That didn't fix anything. After that, I tried to restore to cm 10.2 but it wouldn't let me for some reason. So I figured I was screwed. I downloaded Odin and attempted to restore to the stock rom. Well, Odin failed. So I was literally desperate and out of nowhere decided to try to downgrade the kernel. I attempted a downgrade to AJK 4.9 mic swap and it worked. So I installed MIUI after that (I'm too lazy to try adb) and it loaded up fine. I was so happy that at least something worked. After that I noticed the back and search buttons were not functioning. I decided to restore to cm 10.2 and it worked. Everything SEEMS fine but I'm not too sure if everything is. Can anyone tell me if my process is correct? Or if I messed up everything
Thanks!
I had to wipe the caches after i flashed the nightly to get it to boot.
The CM nightlies didnt work for me either. Something about the build.prop in Omni calling my phone both the ATT and ST version of the phone. I did what you did. Flashed AJ 4.7 i had, rebooted the Recovery, and Nandroid restored.
I liked Omni and ill be back but that battery life right now Ugh. Good luck Entropy and Co!
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
Hello all...
First of all, I'm not very experienced at flashing roms.. HOWEVER, I've flashed several roms across multiple phones over the years and have yet to brick a phone.. so I am fairly familiar with recoveries, etc... But I've run into a "wall" and don't know what to do.... hopefully someone can shine some light to my issue.
My TMobile S5 is currently running Twisted Lollipop (v7?).. but I want to switch now to a CM based rom. I had PREVIOUSLY used a CM based rom (a nightly) dated back from June before I switched to Twisted. My phone is rooted.. and I am using TWRP recovery. However, NOW if I do a full on wipe... and try to flash a rom (so far only the latest nightlies).. it seems to do some partitioning stuff.. and then stops saying COMPLETE... I never get the typical "install" text you see when installing a rom in recovery.. If when it's finished.. when I click REBOOT.. TWRP asks me if I want to.. and warns NO OS is installed..
I was able to load a backup of a CM 12.1 based build from a June nightly I had.... but I get the same thing if I go thru the CM updater. I honestly haven't tried to flash anything else..
Am I missing or overlooking something.. I'm on the DOB1 firmware.
Thanks
aenielida