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.
Related
Everytime I flash I go back to stock unless its a same rom.
Ex. I was on darky 7.2 I just downloaded the rom on my phone via dolphin. Just used rom manager to get 8.0.
But can I do this for all roms? I'm kinda confused cause some say you can and some say you can't..
Sent from my phone
You do not have to. You should disable lag fix, clear cache and davlik cache, prior. Flashing back to stock is cleaner, especially if you are going from a rom with one base to one with another. You can always try without going to stock and flash stock if something goes wrong.
I never do. I just boot to recovery and flash. If I'm using a different kernel I'll reboot to recovery then check my lagfix options and then reboot.
No need to flash back to stock. If the ROM is a 'no-wipe ROM', install like you normally would through CWM/Recovery. If you have problems, or if the ROM is a 'wipe' ROM, clear cache and data in CWM and install. If you still have problems and nothing else seems to be helping, try reverting to stock and starting fresh.
Reverting to stock between ROM's is an unnecessary extra step that generally adds the risk of Odin failure/incompatibility (which can result in a soft-bricked or hard-bricked phone).
Simple question. If answered in another thread, please give me a pointer. I searched, but couldnt find an answer. Here is the question.
Why do we have to revert to Stock 2.1 before flashing a custom ROM? Why can't we flash a 2.2 custom ROM over another 2.2 Custom ROM? And finally, is there a CWM flashable version of stock 2.1 with root and cwm pre-installed?
Thanks.
before a lagfix was adopted as "standard" by the dev community this was necessary to reset the phone file system to n unmodified state. Now that all the devs are using the same type of awesome lagfix, reflashing to stock isn't really necessary anymore, IMHO. I never do it anymore. I just do a wipe user data from my recovery menu and everything seems to work fine.
The answer is not simple.
You do not have to flash stock. It used to be more needed. Devs still say so, but I believe that is largely to problem shoot issues from the get go. Threads are cluttered with comments like omg my phone is possessed. Well what were you running prior, and what was your setup? If stock well we know what was what. If ulk kernel with ext 2 loop, then yes there could be issues
Flashing stock at this point is just as risky, if not more risky then flashing directly over. If something feels wrong and you can't fix it, flash stock\master clear start over
So in essence, we can flash fine over an existing ROM and if there are issues, better go to stock and flash from there. Am I right? Can you list the steps you take to flash a new ROM without going to stock? Will there be issues if lets say I flash a 2.2 ROM over a 2.2.1 ROM?
I.do this but it may be redundant
Backup apps
Dl rom
Boot recovery
delete cache
delete davlik cache
Flash rom
delete davlik cache
Boot
I never did flash back to stock. I failed. Odin would not connect.
But for you guys out there - there is a way to bring recovery menu, that's what saved me.
Remove SIM and SD card.
Power+VolumeUp = reboot from any locked state
Power+VolumeDown=reboot into recovery
Power+both Volumes=download mode, never worked for connecting Odin, I could go there from Recovery
So my sequence:
remove old backups
create new backups
download ROM
boot into recovery
flash rom
clear cache partition and dalvik cache (probably the same)
run fix permissions
reboot
I think for most new ROMs that take advantage of the updated 2.2.1 filesystems you don't need voodoo or any lagfix. Can't even remember the last time I used ext4 when using speedmod kernel and JS3/JS5 Rom. Makes it easier to flash new roms when you don't have to worry about corruption.
But flash back to stock clears out any unnecessary gunk that could cause 90% of Force Closes and random vibrates on boot
I always thought of it as installing a new operating system or a different version of. It. Cming from the same roots of the ROM or OS, you can just install a different, major update over it (Different ROM) and be on your way.
However if sonething is built differently from the start (Windows and OSX), you cant just install right over the other because there are problems.
I always start back at the beginning because it onky takes a few minutes extra and it makes the phone a whole lot faster; you clean out alk the gunk and unused folders and whatnot.
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
mengbo said:
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
Click to expand...
Click to collapse
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Enhanced said:
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Click to expand...
Click to collapse
I use the oneclick odin to do master clear. The master clear works on i896 too.
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
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
First off, let me make this clear very clear(prerequisite) I do not want to hear the word "safestrap", or any variation. I apologize for sounding arrogant , but I am not interesting in wasting my disk space(no offense against the quality work of Hashcode) or dual booting a ROM. I noticed some interesting issues with CWM recovery both the default that comes with Bionic Bootstrapper(4.x.x.x), and ROM Manager(5.x.x.x) in regards to any ICS leaks. So here is the situation, after installing the .232 leak using the "stock recovery option" it went smoothly without any issues, as well as rooting with motofail for ICS. The problems start when I first attempt to install any ROM(AOKP, CM, liquidsmooth etc etc) using 4.x.x.x CWM it appears to install correctly(even booting the ROM up and everything) but when I reboot the phone will continue to boot directly into CWM, and using the reboot option only to boot loop.(I have done the standard Wipe System/Factory reset, Wipe Cache, Wipe Dalvik Cache prior to installing any ROM). Finally, when I attempt to install an updated CWM 5.x.x.x via ROM Manager, it appears to install, but forcing the device to reboot in to recovery does not work, even the two button solute(PWR+VOL UP) as used in the second stage to force CWM to boot into the menu(worked in 4.x.x.x) it is as if it is not corretly installed.. Both CWM installs are clean, and no previous 1st/2nd stage boot loaders are installed, I would like to rule out me being a dumbf*** and it being a case of error on my part. Like I said before please do not mention "SAFESTRAP" as an option, unless it can flash over current baseline install's, having the safe option(noob proof) is not an option. If anyone can assist me with the installation or even a solution to getting CWM recovery to work after installing the ICS leaks it would be greatly appreciated. Thanks again!!! Also I have tested CWM 5.x.x.x install from .905 based roms and it works flawlessly.