I am using safestrap with unsafe=stock905+root and safe=KINETX rom. I want to get my safe system into ICS leak and need to get the safe system back to stock 905 to make that happen.
The first question is: Is there a easy way to get my safe system back to stock905+root? My original backup for safe system has MD5 problem so that won't work. I am imagine something like "purge the current safe system and recreate it from unsafe system".
Second question: If my only way back is RSDLite, do I need to remove/uninstall safestrap before doing that? Or, the question is rather "If I do RSDLite with safe system enabled, will that bring the safe system back to stock without affecting the unsafe system". I am not sure if RSDLite will erase the entire system including safestrap.
maxion said:
I am using safestrap with unsafe=stock905+root and safe=KINETX rom. I want to get my safe system into ICS leak and need to get the safe system back to stock 905 to make that happen.
The first question is: Is there a easy way to get my safe system back to stock905+root? My original backup for safe system has MD5 problem so that won't work. I am imagine something like "purge the current safe system and recreate it from unsafe system".
Second question: If my only way back is RSDLite, do I need to remove/uninstall safestrap before doing that? Or, the question is rather "If I do RSDLite with safe system enabled, will that bring the safe system back to stock without affecting the unsafe system". I am not sure if RSDLite will erase the entire system including safestrap.
Click to expand...
Click to collapse
i would recommend going back to unsafe to RSD Lite, but I don't think it's necessary as it will erase it all anyway.
I am not sure what you mean about trying to get your safe system back to stock+root. Why not just find a Deodexed .905 ROM and install it on your safeside after doing a wipe of KINETX or just using some other ROM on the safe side?
linuxgator said:
i would recommend going back to unsafe to RSD Lite, but I don't think it's necessary as it will erase it all anyway.
I am not sure what you mean about trying to get your safe system back to stock+root. Why not just find a Deodexed .905 ROM and install it on your safeside after doing a wipe of KINETX or just using some other ROM on the safe side?
Click to expand...
Click to collapse
Thanks!
When I say "get back to stock+root", I mean returning the safe system to the status when I enabled safe system for the first time, before I flashed KINETX.
You suggestion should get me exactly what I want. How come I didn't think of that! I guess my thought was stuck on "getting back to before KINETX".
Related
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.
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
i want to install the ICS leaks but from what im reading, safestrap screws a little with the system, causing issues for the install. Other than root and safestrap, my system is stock .905. I even deleted my safe partition.
Someone was saying that flashing preinstall.img in fastboot will restore the files that ICS needs to install. But the part that was confusing was that people were saying stuff about flashing the FXZ and what not.
my question is: do I need to flash 902 FXZ to get the files I need? Or can I boot into stock recovery, select apply update from SD card and then select preinstall.img? And if the second one, will it wipe my data? or will the .902 preinstall.img file screw up everything because my system needs to be .902?
And if im completely incorrect about all of this....what is correct?
thanks guys.
hi last night (very late) i was trying out a miui rom i am trying to port, i used the wrong update-script and i seems as though its overwritten my unsafe partition even though i was in safe. i couldnt see the safeboot splash but could still get to it form tools in the bootloader menu, i now have the safeboot menu back but no touch buttons. i have done a restore but i only have 2 backups and this is making me think i haven't backed up when i got on the leak.
so dose any one have a backup they would let me try to see if this is the case, can i fastboot out of this (i dont really understand how fastboot works with this phone as its locked down), or is there anything else i can do to get it back working i would like to keep root if possible.
Are you still able to boot your phone when you try to boot your phone of you can then the best thing for you is that try to install fresh stock room of your phone repeat the whole process again that would be better.
If I or anyone else have helped you in any kind of way please press THANK YOU button.
what type of phone do you have.if you Samsung thing will go fast and smooth to go back to stock Rom
If I or anyone else have helped you in any kind of way please press THANK YOU button.
i have droid 4 this is the droid 4 sub forum, i can boot the safe rom, i used to be able to boot non-safe (had miui on it) but after trying a restore form backup its not booting. i am still new to safe boot i dont fully know how it works.
I think you should be able to use the process for going from one leak to another to to get back to a stock ICS leak system. Follow the instructions in the Droid 4 Utility Updated thread.
Sent from my Droid 4
been thinking that and hoping it to as i think there is root for ICS now, but you are ment to unfreeze apps and uninstall safeboot before you upgrade both of witch i cant do, there is no apps to unfreeze to as the partitions gone.
and safeboot is the only thing that is making this phone not bricked.
Unfreezing and uninstalling recovery shouldn't matter the way I understand it. Fastbooting .219 should wipe that stuff out allowing you to freshly install the ICS leak.
Sent from my Droid 4
Yea, I'd fastboot "back" to 219, which of course WILL brick you, but also allow you to flash the ICS leak, which should get you back to a working phone.
Luckily there are root methods for ICS now, so you don't need to have root on 219 to enjoy root on (ICS) 213 :laugh:
Don't worry man, I've done it a dozen times already.
Just flash the system.img and the preinstall.img .219 fastboot files and erase your data and cache partitions with moto-fastboot:
Code:
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot flash system system.img
moto-fastboot flash preinstall preinstall.img
moto-fastboot flash boot [boot.img for .208/.213 kernel]
(You can skip erasing your /data partition if you want but unless you really need something on there, it's usually best to just start fresh.)
You can find the moto-fastboot executables on xda here with a quick search.
Otherwise you can just do a normal fastboot flash through RSD Lite but the method above is a bit quicker since you only really need to re-flash your /system and /preinstall partitions. If you choose to use RSD Lite, then you have to delete the boot.img file in the .219 package and replace it with the .208/.213 boot.img that you can find here on xda.
Pop the corresponding leaked .208/.213 update .zip file onto your external sdcard and reboot your phone into recovery mode by pressing Vol-Up+Vol-Down+Power and choosing Recovery Menu from the screen with white text on a black background and follow the prompts to install the update from your external card and you're good to go.
thanks i will try this soon.
i have updated to 213 now and it boots in to the animated droid eye but dose nothing not even getting a logcat.
got it working just updated again then wiped catch and data then it booted thanks a lot.
Sweet, glad to hear it. Happy hacking!
Hello guys.
I lost several hours and still no success.
I want to clone ICS leak into the safe system for rebuilding some files and have non-safe system as untouched for recovery if something will happen.
But I have no luck to launch moto ics leak in the safestrap. What I tried:
1. found that safe system's partition is the preinstall, it's /dev/block/mmcbl1p22
2. installed clean ICS leak, dumped rooted system.img using dd command.
3. installed safestrap into ICS leak.
4. in the safestrap I went to console, but since preinstall partition is 608MB only (normal system partition is about 640MB), I had no chance to use dd command to restore system.img to /dev/block/mmcbl1p22 by the sector method.
5. Mounted system.img, created .tar archive for saving all permissions for folders and files, then I did format preinstall partition and unpacked .tar files. All seems to be fine and ready to boot.
6. After trying to boot safe system, I stuck on the animation logo. It's not bootloop, it's something other.
7. I decided to restore my /data from normal non-safe system and I had success on booting ICS leak as safe system.
8. BUT no sound in the boot (droid), and no main sound. When I go to settings -> sound and trying to play something, I have freezing of settings.apk.
9. If I go to phone.apk and try to dial, sound from dial numbers are ok.
10. Camera is force closing.
Any suggestion where am I wrong?
Thanks:good:
olegfusion said:
Hello guys.
I lost several hours and still no success.
I want to clone ICS leak into the safe system for rebuilding some files and have non-safe system as untouched for recovery if something will happen.
But I have no luck to launch moto ics leak in the safestrap. What I tried:
1. found that safe system's partition is the preinstall, it's /dev/block/mmcbl1p22
2. installed clean ICS leak, dumped rooted system.img using dd command.
3. installed safestrap into ICS leak.
4. in the safestrap I went to console, but since preinstall partition is 608MB only (normal system partition is about 640MB), I had no chance to use dd command to restore system.img to /dev/block/mmcbl1p22 by the sector method.
5. Mounted system.img, created .tar archive for saving all permissions for folders and files, then I did format preinstall partition and unpacked .tar files. All seems to be fine and ready to boot.
6. After trying to boot safe system, I stuck on the animation logo. It's not bootloop, it's something other.
7. I decided to restore my /data from normal non-safe system and I had success on booting ICS leak as safe system.
8. BUT no sound in the boot (droid), and no main sound. When I go to settings -> sound and trying to play something, I have freezing of settings.apk.
9. If I go to phone.apk and try to dial, sound from dial numbers are ok.
10. Camera is force closing.
Any suggestion where am I wrong?
Thanks:good:
Click to expand...
Click to collapse
Couple of questions for you and I should be able to help you out.
Which leak are you currently running?
Did you install Safestrap v1 or v2?
You would need to follow jsnweitzel's thread on installing the leak, rooting and installing safestrap v2 (this is the ics safestrap).
Then you should be able to switch from the stock leak safe rom and go into safe mode which will create your backup and then go into a nonsafe version of your leak for modding, tweaking, etc.
Let me know if this helps/is easily understood and if you have questions. You can PM me as well.
EDIT::
http://forum.xda-developers.com/showthread.php?t=1779810 ,- D4 Tool for ICS w/ leak updating, root and safestrap.
Which leak are you currently running?
Click to expand...
Click to collapse
215 latest
Did you install Safestrap v1 or v2?
Click to expand...
Click to collapse
2.00a, with console ability
You would need to follow jsnweitzel's thread on installing the leak, rooting and installing safestrap v2 (this is the ics safestrap).
Click to expand...
Click to collapse
I installed, all fine.
Then you should be able to switch from the stock leak safe rom and go into safe mode which will create your backup and then go into a nonsafe version of your leak for modding, tweaking, etc.
Click to expand...
Click to collapse
I'm able to switch from stock leak to any other safe rom like cm9.
D4 Tool for ICS w/ leak updating, root and safestrap.
Click to expand...
Click to collapse
Thanks.
But I know all this already.
I need to run stock leak ICS 215 in the safe system and in non-safe system both in same time. In other words, clone non-safe system with safe system. That's all I need.
You dont need to install another rom then. All you need to do is switch into safe mode and reboot. No need to install another rom over it.
Hashcode created a .206 stock ROM that can be flashed to your safe system in safestrap. I don't know much about what goes into creating a ROM that can be flashed to the safe side but maybe you could use that as a reference in creating a flashable .215 ROM?
Here is the .206 stock ROM thread: http://forum.xda-developers.com/showthread.php?t=1716382
kwyrt said:
Hashcode created a .206 stock ROM that can be flashed to your safe system in safestrap. I don't know much about what goes into creating a ROM that can be flashed to the safe side but maybe you could use that as a reference in creating a flashable .215 ROM?
Here is the .206 stock ROM thread: http://forum.xda-developers.com/showthread.php?t=1716382
Click to expand...
Click to collapse
Thank you, I'll definitely look at it.
update.
but link is dead and it seems that file was deleted from the site.
There aren't up, when rombot crashed they neglected to reupload the ICS leak safe system builds. What are you trying to do in safe system? I developed and tested a deodexer (read lots and lots of "softbricking") on my "unsafe system" but my phone still works. As long as you make a safestrap backup you should be fine, especially if your using the altered version of safestrap with terminal, just make a backup of the files you change and if it doesnt boot copy them back!
Sent from my DROID4 using xda premium
moah909 said:
There aren't up, when rombot crashed they neglected to reupload the ICS leak safe system builds. What are you trying to do in safe system? I developed and tested a deodexer (read lots and lots of "softbricking") on my "unsafe system" but my phone still works. As long as you make a safestrap backup you should be fine, especially if your using the altered version of safestrap with terminal, just make a backup of the files you change and if it doesnt boot copy them back!
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
I'm actually started to use safestrap with terminal for restoring my state, but I thought that I will able to create easier process for testing - using safe system. And was crazy and mad when things happened (in first post) with stock ICS and safe system
fixed a problem, I stupidly forgot about symlinks.
Could you explain, either in this thread or a guide, how you accomplished that? I agree that it would be a lot simpler in a safe system, although testing does work in unsafe I tried doing it when the rombot build was down, but to no success :-/
Sent from my DROID4 using xda premium
moah909 said:
Could you explain, either in this thread or a guide, how you accomplished that? I agree that it would be a lot simpler in a safe system, although testing does work in unsafe I tried doing it when the rombot build was down, but to no success :-/
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
After all what I did, I found Arctic ICS rom in droidforums and found all "ready to go" update-script there. You can download it and use as example for creating safe system rom.