This seems to be the most elusive resolution ever. Perhaps you guys can help me out.
Was on rooted stock JB. Toggled safesystem ON. Flashed AOKP 10/22. Booted but buggy. Went back to Safe System to Toggle OFF and continue to get "Error while restoring /data" and unable to disable safe system. Now I'm stuck with a boot loop on the AOKP logo.
I'm sure that if I wipe and re-flash AOKP 10/22 zip I'd be able to boot again BUT that doesn't resolve the inability to toggle safe system back off. At this point I think I need to restore everything back to factory, lose root and then reroot, reflash from there. I can't find current info on restoring to factory, unroot for the Droid 4 on JB.
Help me fix the safe system toggle issue or other suggestions to "sbf" and start over.
So, it appears that I was running an old version of Safe Strap. v 2.x. I uninstalled it and updated to 3.x from hash of codes. Now it looks totally different and I don't even think that safe mode/unsafe mode is relevant. Perhaps that is why I couldn't find anything current on the issue. Thanks!
If you have anything other than the stock rom activated, then you are in safe mode
Sent from my XT894 using xda premium
Related
Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard
Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)
No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?
I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.
I will try the wipe version
What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App
I was still on stock (froyo 2.2). Actually still on it today
You were right. The wipe version worked fine. I have now to decide to keep it or not...lol
ROM is awasome was worth well the trouble.
Glad it worked out for you - have fun with the rom
Sent from my Desire Z
Basically the title.
I removed the Tweaked Bootstrap.apk and just downloaded and installed Safe Strap. Rebooted and performed my first backup in Safe Strap. Tried to boot into primary and got black screen.
My current ROM is the latest (11-16) version of CM7.
I don't really need Safe Strap, I kinda just want to be able to boot again. Any help is greatly appreciated.
EDIT: Formatted /system and reflashed CM7 and GApps in SAFE MODE. Can boot now, going to try booting in NON-SAFE MODE.
EDIT2: Still can't boot into non-safe mode. My whole reason for switching was to test out ICS, so I guess I can just flash it and if I need to go back, I'll just reflash CM7.
Regardless, if anyone can tell em what I'm doing wrong, I'd be appreciative.
Did you wipe everything including dalvik? and its best if you start from a stock system. No custom ROMs. then install CWM and install whatever rom you want. uninstall CWM and install safestrap. now boot into safestrap and wipe cache and all taht. Now install ICS/CM9. I found tahts the best way to do it recieve none of the errors many people are having.
Well, since safestrap can't flash nonsafe (yet) its obvious you still can't boot nonsafe if you couldn't before. What you need to do is reflash cm7 using the old bootstrap, install safestrap, make backup, then switch to safe system and flash ics.
I rooted and got stupid with removing certain apps while safe mode was disabled. I tried restoring the restore posted in development somewhere and an MD5 mismatch error kept coming up... I tried downloading again after clearing the browser cache and that didn't work. Right now I'm just running the pre rooted stock ROM in safe mode.... but not sure if that's a good thing or not.
If you're trying to flash something over your non-safe system you won't be able to do it through safestrap. Clockworkmod recovery is the first thing that pops into my mind. If you're still able to use your non-safe system, switch back to that, completely remove safestrap, and use CWM recovery to flash a stock ROM. Just be sure the ROM isn't specifically designed for safestrap's /preinstall system.
Sent from my DROID4 using Carrier Pigeons
So I just got this phone, and I've been trying to get it up to ICS. I've gone through and was able to complete the ICS update the first time completely, installed Safestrap, etc. Now this is where the issues came in. I did a backup, and then I started restoring some apps from titanium, from an old phone. This is where I started getting constant force closes. Tried fix permissions, went through again, same issue. So I wiped the phone, and went to restore with safestrap - it failed. Now on bootup, it refuses to even boot into safestrap anymore. All I can get is either a blank screen, or motorola recovery menu. By the fact that I can get into the motorola recovery menu, I presume it's not fully bricked, but I know there can be issues with installing on top of Safestrap.
Long story short, my question: In this condition, will flashing the same file I did during the ICS leak installation through Moto Recovery allow the phone to boot? Or will that cause a brick like downgrading from ICS does?
So, just to be sure, you installed one of the ICS leaks correct? Then you installed safestrap 2.0?
Sent from my Droid 4
Yes, that's exactly what I did. Was able to boot up into Safestrap (2.0) and restore through Safestrap, but after wiping /data I got errors with restoring a backup, and after rebooting to attempt it again, Safestrap splash screen no longer appears for me. It has the initial splash, and where the Safestrap splash should be, it just stays blank screen.
Not sure what would have caused this. I don't think you'll be able to flash the zip again since it looks for a .219 system build. Might be worth a shot though. You could also try booting into recovery and doing a factory reset. If neither of those work, try following the instructions for upgrading from one leak build to another.
Sent from my Droid 4
Tried Factory reset already, and attempted just flashing the update anyways - got an error saying build.prop file was invalid/missing?
Now I'm going through the tool steps to swap between ICS builds. At least I'll hopefully get something working.
Though I did do a step I forgot to mention, if that explains why it happened. After the Safestrap restore failed, I tried to do a partial restore of /system and /data. /system restored fine, when I went to do /data it said it was restoring /system in the log - could that have been an issue? A possible mistake in safestrap that overwrote the wrong folder? Or just an issue with the menu?
Doing the ICS switch got it working for me. Now to attempt round 2 and see if I can get into CM9, and Safestrap works right.
More research, root cause : Forgot to install busy box when doing the initial root.
Glad you got it working!
Sent from my Droid 4
Hello, guys. I have ICS leak on my device, installed safestrap successfully, but after first time boot (boot recovery or system), when I can choose what system I wanna boot, the phone shows only black screen with led backlight. Tried to wait about 15 minutes, but no luck. Busybox was updated, safestrap works, but safe system doesn't want to boot. Any advice? I tried to wipe all and install safestrap in clean system, still no go.
Can you boot into unsafe system, recovery? If you can get into recovery, I'd try a factory reset.
If all else fails, I'd reflash 219 --> ICS 213 and start over.
Did you install a ROM on your safe system?
Sent from my Droid 4
kwyrt said:
Did you install a ROM on your safe system?
Sent from my Droid 4
Click to expand...
Click to collapse
yes
I was having the exact same issue. You can't enable safe system and boot in to a non-safe system ROM. If you enable safe system, you have to install a custom rom. If you haven't yet wiped or made any changes in CWM/Recovery, then you can just disable safe system and you should boot in to stock, which is what I did. Although I did later on install the AOKP ICS leak. I'm currently waiting for there to be a release of the .213 Moto ICS rom.