To Flash****UPDATED******
- Boot into safestrap
-Select safe system
-toggle safe system on
(It seems we have an issue wiping the safe strap /data and /cache so these additional steps are needed for now)
-quick toggle safe system off *****MUST BE A QUICK TOGGLE*****
-wipe data/factory reset
(To be safe wipe the following)
-Wipe Cache partition
-format /system
-wipe dalvik cache (Found a bug in safestrap that prevents us from wiping dalvik cache see thread)
-quick toggle safe system on *****MUST BE A QUICK TOGGLE*****
Now, flash the rom. (Selecting external Sdcard)
Safestrap works alot like a dual boot, so you can always return to your stock system by simply disabling safestrap in the safe boot menu.
http://forum.xda-developers.com/showthread.php?t=1425026
This is ics for the droid 3 by hashcode, same guy that gave us permission to unofficially port and support safestrap. It does boot and work on our phones.
This is what i know for sure right now
-Wifi works
-Most tasks and apps work
-market is broken
-calling/texting is broken, looks like its stuck on cdma?
-accelerometer is broken
What I'd like to see from here is some one willing to take over my project on this rom. I have a few of my own flash able zips complied with various tweaks to hopefully be able to make and receive calls, no success yet. I will keep trying but this is a project better suited for some one who is not so new to the linux environment. (I just got my first linux box 2 weeks ago)
Please enjoy and the thanks button is below the download link
http://forum.xda-developers.com/showthread.php?t=1425026
Proof It works! http://youtu.be/B_J3fs80dV0
**************-Edit*************************************************************************
I have decided to take on this project. I will post a more "ported" version as I progress on it, These things take time so please be patient. The information contained above should only be used as a "prof of concept" sort of thing. Anyone willing to help may do so here: http://forum.xda-developers.com/showthread.php?t=1428117
Great work !!! Thank you very much!!! Waiting the update!!
Don't we need the source code for the Atrix 2 to make this work?
I've followed all the steps in safestrap, got it working, except mounting SD (is that expected?), but after I flash the CM9 zip while in safe mode, I reboot and get stuck with a black screen. Anyone else get this working? It seems to flash rather fast which seems abnormal to me.
I agree that this Alpha 4 is stuck on CDMA. If anyone has gotten 3g to work, please let me know how you did it. I tried entering their little trick *#*#4636#*#*, rebooted, wiped cache and dalvik like they said and still nothing.
lfaber06 said:
Flash this using safestrap only.
To Flash
Boot into safestrap
Select safe system
toggle safe system on
wipe data/factory reset
(To be safe wipe the following)
Wipe Cache partition
format /system
wipe dalvik cache
Now, flash the rom. (Selecting external Sdcard)
Safestrap works alot like a dual boot, so you can always return to your stock system by simply disabling safestrap in the safe boot menu.
http://forum.xda-developers.com/showthread.php?t=1425026
This is ics for the droid 3 by hashcode, same guy that gave us permission to unofficially port and support safestrap. It does boot and work on our phones.
This is what i know for sure right now
-Wifi works
-Most areas of the phone work
-phone is broken, looks like its stuck on cdma?
What I'd like to see from here is some one willing to take over my project on this rom. I have a few of my own flash able zips complied with various tweaks to hopefully be able to make and receive calls, no success yet. I will keep trying but this is a project better suited for some one who is not so new to the linux environment. (I just got my first linux box 2 weeks ago)
Please enjoy and the thanks button is below the download link
http://forum.xda-developers.com/showthread.php?t=1425026
Click to expand...
Click to collapse
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Why can't I get this to boot? I go into safestrap, put it on safemode, wipe all the necessary things, flash the zip, reboot, and I get a black screen. If I take it off safe mode it goes back to my stock ROM successfully.
Calundle said:
Why can't I get this to boot? I go into safestrap, put it on safemode, wipe all the necessary things, flash the zip, reboot, and I get a black screen. If I take it off safe mode it goes back to my stock ROM successfully.
Click to expand...
Click to collapse
Try this. Using safestrap, make a Full backup Including webtop to be safe. then disable safe mode and factory reset, then wipe dalvik cache, then format /system, then wipe /data, enable safe mode, flash it, and let me know.
lfaber06 said:
Try this. Using safestrap, make a Full backup Including webtop to be safe. then disable safe mode and factory reset, then wipe dalvik cache, then format /system, then wipe /data, enable safe mode, flash it, and let me know.
Click to expand...
Click to collapse
Alright I'm trying it as we speak. So is the SD card currently unmountable in safestrap? If I do a backup while in safemode, won't that backup the safemode ROM, which is the CM9 one I can't get to work? I don't really understand how the safemode/no safemode works. I was under the impression that my stock ROM is under no safemode so anything I do with safemode off will effect that (meaning when I do the format and wipes you're talking about it would do that to my stock ROM), then when I turn safemode on everything I do effects the other ROM. Can you clarify for me?
Calundle said:
Alright I'm trying it as we speak. So is the SD card currently unmountable in safestrap? If I do a backup while in safemode, won't that backup the safemode ROM, which is the CM9 one I can't get to work? I don't really understand how the safemode/no safemode works. I was under the impression that my stock ROM is under no safemode so anything I do with safemode off will effect that (meaning when I do the format and wipes you're talking about it would do that to my stock ROM), then when I turn safemode on everything I do effects the other ROM. Can you clarify for me?
Click to expand...
Click to collapse
Not exactly..... safestrap knows which ROM is your stock system, and which one is the "safestrap". It calls your stock rom /systemorig or something similar, and then when in safe mode, it will mount the stock system to /systemorig and back that up as well as /system, which will be the CM9 rom, that is why you had to partition your card a certain way, to make this work right.
jimbridgman said:
Not exactly..... safestrap knows which ROM is your stock system, and which one is the "safestrap". It calls your stock rom /systemorig or something similar, and then when in safe mode, it will mount the stock system to /systemorig and back that up as well as /system, which will be the CM9 rom, that is why you had to partition your card a certain way, to make this work right.
Click to expand...
Click to collapse
Ah thanks for the explanation. So, when you backup it does a backup of both system and systemorig, both roms, how do you go about wiping one rom and not the other? Am I correct in saying if you have safemode off and do wipes/restores it will do that to your stock rom, but if it's on it will do it to the systemorig one, then backing up with it off does a backup of stock rom, and when it's on it backs up both?
Calundle said:
Ah thanks for the explanation. So, when you backup it does a backup of both system and systemorig, both roms, how do you go about wiping one rom and not the other?
Click to expand...
Click to collapse
Safestrap will only allow you to wipe your non safe data. it will not let you wipe your safe system aka "stock rom".
lfaber06 said:
Safestrap will only allow you to wipe your non safe data. it will not let you wipe your safe system aka "stock rom".
Click to expand...
Click to collapse
Awesome. Sorry for all of the questions, I'm familiar with CWM, but this is new territory for me. I really appreciate it. I'm doing the steps you provided. Am I basically doing a complete backup, complete wipe of both ROMs, then trying to install CM9 on the safe partition?
EDIT: I don't want to clutter this thread with questions about safestrap so I'll take any further questions to it's thread. Thanks again.
Calundle said:
Awesome. Sorry for all of the questions, I'm familiar with CWM, but this is new territory for me. I really appreciate it. I'm doing the steps you provided. Am I basically doing a complete backup, complete wipe of both ROMs, then trying to install CM9 on the safe partition?
Click to expand...
Click to collapse
No, you will only be making changes to the safestrap ROM, not the system ROM.... The backup will currently only be the stock ROM. now if when you enable safestrap do a backup, then disable safestrap, while in safestrap and taking a backup, you can backup the "safetrap" ROM, not the system ROM....
Now if you follow the directions in the original post, you will end up with two bootable ROMs on your phone. you really are only interested in the safestrap one right now, so doing the backup before flashing will ONLY backup the stock ROM. and you will not wipe the stock ROM either so to speak, because you can "dual" boot both ROMs by enabling and disabling the safestrap.
jimbridgman said:
No, you will only be making changes to the safestrap ROM, not the system ROM.... The backup will currently only be the stock ROM. now if when you enable safestrap do a backup, then disable safestrap, while in safestrap and taking a backup, you can backup the "safetrap" ROM, not the system ROM....
Now if you follow the directions in the original post, you will end up with two bootable ROMs on your phone. you really are only interested in the safestrap one right now, so doing the backup before flashing will ONLY backup the stock ROM. and you will not wipe the stock ROM either so to speak, because you can "dual" boot both ROMs by enabling and disabling the safestrap.
Click to expand...
Click to collapse
Ah okay okay, I think I understand how it works now. I've tried the steps in the OP and the ones faber mentioned and I'm still getting a blank black screen after reboot. How long should it take to flash the CM9 zip? It takes like 6-10 seconds for me and from my experience that's rather short for a ROM. Could the zip have gotten corrupted?
jimbridgman said:
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Click to expand...
Click to collapse
Yup just tried it, I get "Unfortunately, phone has stopped" over and over so i guess its force closing.
So, without phone or 3g capabilities, this port is basically just pretty window dressing for our Atrix 2 right?
jimbridgman said:
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Click to expand...
Click to collapse
Has anyone tried this yet? If not I will mess with it and let you know what happens.
lfaber06 said:
Yup just tried it, I get "Unfortunately, phone has stopped" over and over so i guess its force closing.
Click to expand...
Click to collapse
duke8804 said:
Has anyone tried this yet? If not I will mess with it and let you know what happens.
Click to expand...
Click to collapse
Yep lfaber06 tried it, and if you read his reply noted in the top quote here in my reply it keeps force closing..... To bad, I am guessing because it is ICS and not GB, like out phone is currently.
jimbridgman said:
Yep lfaber06 tried it, and if you read his reply noted in the top quote here in my reply it keeps force closing..... To bad, I am guessing because it is ICS and not GB, like out phone is currently.
Click to expand...
Click to collapse
Sorry about that, I guess i overlooked that one.
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
famac! said:
Flashed several ROMS in my life and have not always wiped all data. Mainly i do dalvik and cache. My phones have always work. Now i have a Razr HD with an unlocked BL with TWRP loaded. I cant seem to get past the initial bootup screen no matter what ROM i flash. What am i missing here guys? Do i need to check the "factory reset" in TWRP along with Dalvik, system and cache?
Click to expand...
Click to collapse
answered here http://forum.xda-developers.com/showthread.php?t=2465695
bweN diorD said:
answered here http://forum.xda-developers.com/showthread.php?t=2465695
Click to expand...
Click to collapse
Not really. The majority of ROMS in question have been 4.2.2 based....
famac! said:
Not really. The majority of ROMS in question have been 4.2.2 based....
Click to expand...
Click to collapse
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
bweN diorD said:
quote from post 11
"By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot"
Click to expand...
Click to collapse
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
famac! said:
Please explain this further to me. My problem is with 4.2.2 ROMS. The fix above is for folks having issues with 4.3 ROMS. Are you suggesting that doing this will also fix my 4.2.2 problems? This is also CWM while i run TWRP. I did a quick look and the two are setup a little difference. I played around with those highlighted instructions and almost accidentally wiped my only backup of my previous state. I actually thought i was toast but somehow i reloaded and went back to my old backup state.
Click to expand...
Click to collapse
i could be wrong, but in my opinion having the exact same issue even though its a different version, one of the 2 fixes in that thread should work.
the first fix likely doesn't directly apply although i suggest you ensure you have the latest version of your recovery of choice found here http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
second fix (backup ALL data you don't want to loose first as noted above), then do a full wipe as listed above, not just a fdr that doesn't wipe everything on the internal card.
the problem at this point is, you are assuming it wont work because of version differences, i am assuming it will. until you try it, i don't see any point in exploring other options, if there are any.
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
RikRong said:
Dirty flashing when you go to different ROMs is generally not a good idea. Even on 4.2.2, it leaves residual data behind. There's a reason that the devs talk about doing complete wipes in their ROM threads, and there's a reason that they tell you not to talk about bugs unless you use their install directions.
Click to expand...
Click to collapse
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
famac! said:
Yeah, i am straight now. Did a full wipe and sailed right past the startup animation. Thanks all.
Click to expand...
Click to collapse
Nice! Glad to see you got it working.
Hi! I just installed a new Custom ROM for my phone. After 5 minutes I wanted to create a backup. So I started ROM Manager. I entered the name, and hit OK. The phone booted into a crashed recovery mode. So I took the battery out and rebooted the phone. It didn't boot into my Custom ROM. It booted into recovery. So I am stuck inside the recovery mode and can't boot normally.
Phone: Samsung Galaxy Mini (GT-S5570)
Recovery: CWM Recovery
Custom ROM: CyanogenMod
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
It still puts me into recovery
HashyCode said:
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
Click to expand...
Click to collapse
I tried it. I wiped /system, /data, /cache and I did a factory reset. Flashed it back but it still puts me into recovery.
xdcsaba said:
I tried it. I wiped /system, /data, /cache and I did a factory reset. Flashed it back but it still puts me into recovery.
Click to expand...
Click to collapse
Flash the original firmware back. And try from the start
HashyCode
It still doesn't work
HashyCode said:
Flash the original firmware back. And try from the start
HashyCode
Click to expand...
Click to collapse
Tried it. Does not work.
xdcsaba said:
Tried it. Does not work.
Click to expand...
Click to collapse
Visit here and try one of them
HashyCode.
Hi, i would like help you with this problem as I myself have experienced it. The things that you should have done are:
1. Always make the backup early on before installing the Custom ROM.
2. When installing a Custom ROM, make sure you have not replaced core system apps
3. Make sure your there are complete symlinks in your ROM otherwise it be hard bricked. Ouch.
4. Before installing a Custom ROM, make sure they are from experts, like CyanogenMOD, and sure your device is supported for updates.
5.[Most Important] The only things to wipe when installing a ROM are : 1. Cache 2. Dalvik Cache 3. User Data, never ever ever ever WIPE your system folder with root access on it. This will always ensure that you will reboot into recovery, and it will be annoying to root your device w/o ADB USB Debugging on.
6. Make sure that there are no system apps missing on your Custom ROM, check for the legibility of the Custom apps installed. Are they pirated perhaps?
7.[Very Important]Always watch a video tutorial for it's errors, and search how to Unbrick your device first before proceeding with an installation.
So that if any problem arises, you will be sure to restore it to it's Stock experience.
8.[Absolutely Important]Make sure that your software counterparts on the PC are compatible and functioning well first before you proceed.
Now tell, me which of the following did you not do?
And if this really helped you a lot, please like. For the sake of those who did their research.
HashyCode said:
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
Click to expand...
Click to collapse
ive already done factory reset like 5 times i still am not able to flash it to custom rom stock condition im going to try using a laptop with windows 7 to see if i can do that way because its not working on the latest windows 8
Kinnngzzzz
Try fastboot?
Hi,
No one seems to have suggested using a program called fastboot. It involves just installing some essential software on a PC, then running the program "Fastboot" along with the desired options.
I strongly suggest trying this: http://forum.xda-developers.com/showthread.php?t=2277112
I am always flashing ROMs and then trying to tweak them and end up messing up the bootloaders, or somehow breaking the system. And then i try using CWM or TWRP and still there remain issues. However, fastboot has always done the job for me.
Hope this helps.
Someone help me with my problem please ??
Use Fastboot!!!
kinnngzzzz said:
Someone help me with my problem please ??
Click to expand...
Click to collapse
kinnngzzzz, you too should use Fastboot! See my post right before yours...
So again, see this link: http://forum.xda-developers.com/showthread.php?t=2277112
I say if fastboot can't get it fixed, nothing will. :victory:
kinnngzzzz said:
Someone help me with my problem please ??
Click to expand...
Click to collapse
As you said that you're going to try with windows 7. Did you tried it? And please! Visit the link which youniqueg33k provided.
HashyCode.
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Nope it does not.
Stoney60 said:
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Click to expand...
Click to collapse
Factory reset only Clears out use added content apps and Personal Settings. To get back to stop you will ..
1 Download the Correct Latest Version Of Android From Sam-mobile or Samsung For your Device.
2. Download odin for your device
3. Make sure you can access your device from windows or os your using.
4. Follow instructions for getting into download mode and flashing the samsung firmware with odin from your computer.
5 . Reboot the device and Leave it be..
Never flash anything on any Device until you know how to get back.
There are many Threads with step by step details on the above. even many youtube videos..
Good Luck
Hey,
I don't think you have to flash back to a stock ROM in order to upgrade to a different ROM. I was able to upgrade my tab with 4.1.2 (I can't remember what ROM it was) right to GNABO then a few hours later to Carbon, and a few hours later to Hyperdive and I'ts running fine with no issues besides the Aroma freezing, but what else is new...
You shouldn't have to flash back to a stock ROM to flash to a modified ROM, reason being is the modified ROM Flashes over the current ROM on the device, so the original ROM will be deleted anyways. The new ROM contains the updates for you, that's the advantage of androids. I recommend trying a few OS's before you pick the one for you stick with it. If you want to go stock there is a thread somewhere in the DEV section with the stock ROM just do some searching.
Make sure when you install a ROM to ;
Backup your device and make sure to keep a copy of the backup to your pc!
Boot into CWM Recovery or TWRP
Wipe data / factory reset
Wipe cache
Wipe dalvik cache
Install ROM from SD
Good Luck