[Q] Droid 3 flash rom - Motorola Droid 3

recently I have attempted to flash the monster rom to my droid 3 and I havent had success it was 1.2 version and i used D3 Safestrap. I went into safe mode then installed zip from my sd card and it loaded and was successful. Then went in to reg mode to boot up ( because it is not able to in safe) and nothing changed i went into the about phone and it does not show a new rom was loaded nor does anything look different. Did i miss a step? what happened?

Sounds like it didn't work. The point of safe mode is that it's a separate system to non-safe mode, so non-safe mode should still work exactly like it did.
So your phone not booting in safe mode means that the ROM's not working or whatever. Switching to non-safe mode is like flashing back to the backup before you installed the ROM, it _should_ not look any different.

Ok so then that mean even though it says successfull it is in fact not? I am a noob, so i apologize for my ignorance.

Did you toggle back to safe mode and reboot. That should boot up the new rom.
Sent from my DROID3 using XDA App

Unfortunately MonsterROM is not Safestrap compatible in its current form. You need to unzip it, delete a folder and rezip it for use inside of Safestrap. There's a post somewhere within the Safestrap discussion of the Android Development section that indicates what to do.

Manic_Dragon said:
Did you toggle back to safe mode and reboot. That should boot up the new rom.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I did and it wont go past the multicore display it just goes blank after

SBF, reroot, then just install the other bootloader. Don't use Safestrap. I had the same problem with Monster. Someone probably should convert it.
Sent from my DROID3 using XDA App

Related

Question about Bootstrapper and Clockwork Mod

I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Lyxdeslic said:
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Click to expand...
Click to collapse
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
erismaster said:
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
I think he's saying to not use rom manager at all. You can flash roms from cwm recovery.
Edit: just to clarify I mean by booting into recovery using the bootstrapper and flashing a rom from there to avoid any issues caused from the rom manager
Sent from my rooted xt860
Lyxdeslic said:
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
Click to expand...
Click to collapse
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
erismaster said:
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Lyxdeslic said:
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Click to expand...
Click to collapse
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
erismaster said:
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info man.

Two ROMS on one device

How can I install two ROMS (MavROM and ICS) on my D3? one in SAFE MODE and one without.
what programs to use?
I already have MAVROM installed with SAFESTRAP from hashcode, but if i disable it, i get the stock rom.
thank you.
You have to use a bootstrap to flash your nonsafe before you install safestrap
Sent from my XT860 using xda premium
can you direct me to a link to that application? all I can find is safestrap from hashcode.
i have this one: "Droid3CWBootstrap"
http://www.appbrain.com/app/droid-x-recovery-bootstrap/com.koushikdutta.droidx.bootstrap
but how can I install zip with it?
I'm sorry I didn't see your last PMs
Anyway.
1) Start in stock ROM http://forum.xda-developers.com/showthread.php?t=1336980
(Or your non-safe ROM in safestrap and then remove safestrap)
2) After root, download bootstrap (I uploaded it) http://www.mediafire.com/?3u8xhmsp3lg5yfx
3) Install the APK and open the bootstrap app. Press install recovery then reboot recovery. You're now in bootstrap, not from using vol -+ etc (from your PM)
4) Flash mavrom using their CWM Recovery instructions
5) Once you got it setup, remove bootstrap app and install safestrap http://goo.gl/1pr5T
6) Reboot into safestrap and switch to safe system. Make a backup if you want before swithing. The switch will backup your current ROM (data), which is mavrom. Once in safe-system you can now flash ICS using the instructions. This will flash ICS in a different place. When you go back to non-safe system your mavrom will be restored.
Hope it's clear now
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
bogdan_wrc said:
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
Click to expand...
Click to collapse
Np aside from the fact that I'm not on XDA all day the notification is very small - most of the time I don't see it until the next day
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
zzandrewst said:
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Endoroid said:
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
zzandrewst said:
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
you can't flash nonsafe with safestrap. Gotta use a bootstrap to flash your nonsafe, then install safestrap for flash safesystem. But yes, i have liberty as my nonsafe and ics as my safe
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
what to do?
I dont have the INSTALL from zip option, just UPDATE from zip.
that why i used safestrap.
but if I want to install the boot animation from RAZR, now in which location shall I do that? it used to be in /system/media folder. still there?
thank you, i managed to install both one successfully.
bogdan_wrc said:
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
Click to expand...
Click to collapse
I think thats because you tried to flash using original recovery, you said something with -+ volume buttons?
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Really a fastboot flash isn't such a big deal. I've done it more times than I can count. Takes 10 minutes. Id rather have my fav rom in nonsafe so I can use safe to testing new roms and new ics builds
Sent from my XT860 using xda premium
Is this dual boot system possible for my phone ? I would like to switch froyo and cynaogenmod !
Sent from my Optimus Me using XDA App
DoubleYouPee said:
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
Click to expand...
Click to collapse
I think you miss a key point. When you boot safestrap it starts in the non-safe system no matter what you do. Depending on your mode it then moves you to a totally separate partition on the device, preventing you from doing any harm to the boot rom.
The non-safe is key for the entire system to work. Yes it can be any rom, but you do put yourself at risk of losing two installs, including all the data.
Easy unbrick may be as fast to get to stock, but to rebuild back to where you were is going to take a lot longer.
In the end I am just advising caution, not telling people what to do. It does go against what the system was designed for and people should be aware of that before jumping off the ledge.
I understand, but now I have to go back to bootstrap to do essentially the same thing
Not sure if I follow you..
If you are only working in Safe-mode Rom the worst you can do is blow that rom up. Fixing it is just a matter of restoring your last backup via Safestrap recovery.
The problem with working in non-safe rom is that you can blow up both and lose your recovery. From that point you have to do Fastboot, install bootstrap, restore non-safe backup, install SafeStrap, restore Safemode backup.
Unless I am not understanding you correctly.

[BOOTSTRAP] Safestrap for Droid 4 [02/28: Version 1.09]

SAFESTRAP 1.09 for Droid 4 (2nd-System Bootstrap / Recovery)
[ After installation boot into recovery and make a FULL backup while in Non-Safe mode to have a full 1st and 2nd system backup for disaster recovery. ]
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. WE DO NOT HAVE A FASTBOOT FOR THE DROID 4 YET. PLEASE USE CAUTION. **
[ Make sure you get the DROID 4 VERSION ]
Download Here
Instructions for Use
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
Koush who develops such a GREAT recovery system and the makes the source available for others to use.
The Atrix dev team who I pulled the internal/external SD card support from
The Defy dev team that originally developed the Bootmenu source which I stripped down and used for the Splashscreen.
As always, let me know what you think!
Reserved for future use
Literally just turned on another phone after brickin my first one....flashing now
reigndropz said:
Literally just turned on another phone after brickin my first one....flashing now
Click to expand...
Click to collapse
Please be careful! I will be posting a Droid 4 ROM created from our current MotoBlur .215 system. This can be flashed as the Safe ROM in Safestrap for those who like to "play" with their phones / settings / bloatware. That way if you mess something up you'll be able to get into Recovery and restore a backup /system.
Hashcode said:
Please be careful! I will be posting a Droid 4 ROM created from our current MotoBlur .215 system. This can be flashed as the Safe ROM in Safestrap for those who like to "play" with their phones / settings / bloatware. That way if you mess something up you'll be able to get into Recovery and restore a backup /system.
Click to expand...
Click to collapse
Will do, can't wait for that! Hey quick question....let's say I wanted to flash a zip for a mod in Safestrap. I cant flash it when SS is disabled so I have to enable it but that restores the old system. Is this where I want to toggle , install the zip and then toggle back afterwards?
reigndropz said:
Will do, can't wait for that! Hey quick question....let's say I wanted to flash a zip for a mod in Safestrap. I cant flash it when SS is disabled so I have to enable it but that restores the old system. Is this where I want to toggle , install the zip and then toggle back afterwards?
Click to expand...
Click to collapse
There's no flashing zips to the "Non-Safe" ROM in Safestrap. You can only flash zips to the Safe ROM (with Safe Mode enabled).
You only run your original ROM when Safe Mode is disabled.
Hashcode said:
There's no flashing zips to the "Non-Safe" ROM in Safestrap. You can only flash zips to the Safe ROM (with Safe Mode enabled).
You only run your original ROM when Safe Mode is disabled.
Click to expand...
Click to collapse
The problem I'm having is When Safe Mode is enabled , I cant start any ROM. I enabled Safe Mode and then restored a nandroid backup but it wont load. It hangs after the Moto boot screen. The only way it seems to work is if I disable Safe Mode which in turn loads the previous ROM, so I'm always at square one. I'm sure I am doing this wrong, just not sure what exactly it is.
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
papi92 said:
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I'll download arctic and see what's happening with it. Should be able to flash that one. But the stock rooted /system dump needs some files tweaked I think.
reigndropz said:
The problem I'm having is When Safe Mode is enabled , I cant start any ROM. I enabled Safe Mode and then restored a nandroid backup but it wont load. It hangs after the Moto boot screen. The only way it seems to work is if I disable Safe Mode which in turn loads the previous ROM, so I'm always at square one. I'm sure I am doing this wrong, just not sure what exactly it is.
Click to expand...
Click to collapse
I'm not sure restoring a nandroid backup works that way. I'll get a MotoBlur .215 for use w/ Safestrap available for download here in a bit.
papi92 said:
Anytime i flash something in safestrap i get a bootloop. I tried atric rom and the stock rooted rom. Same results. I would log cat but usb debugging isnt enabled
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Looks like someone over at rootzwiki figured something out on this. According to the post, when in the bootloop, if you go back into recovery for a second time, and boot again, supposedly it lets you into the second ROM.
Here's the official post on it:
http://rootzwiki.com/topic/19673-ics-on-droid-4/
This guy loaded ICS from the Droid Kang version of RAZR and claims it's working....I was going to give it a try in a bit, and see if it works.
garlick2 said:
Looks like someone over at rootzwiki figured something out on this. According to the post, when in the bootloop, if you go back into recovery for a second time, and boot again, supposedly it lets you into the second ROM.
Here's the official post on it:
http://rootzwiki.com/topic/19673-ics-on-droid-4/
This guy loaded ICS from the Droid Kang version of RAZR and claims it's working....I was going to give it a try in a bit, and see if it works.
Click to expand...
Click to collapse
I've loaded it as well last week and it does work but there are too many issues. Besides the one he mentioned, when you turn the screen, it gets stuck in the horizontal view and wont revert back. Also, the above method doesnt work, at least not for me. Flashing a ROM does work though without going through those steps, I am just not having luck with flashing zip's of other kinds.
Cool. Jeff8732 didn't have a lot to say about it besides the keyboard didn't light up.
I also am a bit more interested in a CM9 based ROM, my understanding that's the one that Hashcode is working on....so I'll just hang tight and wait for that.
The links here are down. Anyone have working links? Thanks.
mystik1 said:
The links here are down. Anyone have working links? Thanks.
Click to expand...
Click to collapse
http://blog.hash-of-codes.com/how-to-safestrap/
There is the link that I used.
Delete files
I was wondering if i could delete any of the safestrap backups from my SD card. It's using well over 3GB. Right now I have the following files in the backup folder:
Nonesafe:
cahce.ext3.tar
data.ext3.tar
nandroid.md5
osh.ext3.tar
system.ext3.tar
systemorig.ext3.tar
Orig:
data.ext3.tar
Safe:
data.ext3.tar
I was wondering, would it be safe to delete any of those?
Links fixed.
Two requests:
Add a shell option to the recovery menu. I really miss that feature (from AmonRa recovery on my G1).
Integrate kexec. We ought to be able to intercept the boot process and load any kernel we want, safely. On the XDAndroid builds we replace /init with a shell script that does a bunch of manipulation before exec'ing the real Android init. For a kexec boot you add a kernel argument to flag that it was kexec'd. If the shell script sees that argument, it knows kexec was already done and just passes the boot on thru. If it doesn't see the argument, it kexecs the kernel you want.
Follow this thread for more details. I also added a kexec option to our Powerdown menu (in addition to Shutdown and regular Reboot) to allow fast swapping between kernels.
http://lists.xdandroid.com/pipermail/xdandroid-dev/2011-May/000327.html
Come to think of it - can we partition the internal SD card? If so, we could create a new root partition as well. Could just use the external SD too if all else fails.

[Q] Droid 3 XT860 won't boot to recovery (stock rooted)

Hello everyone!
Iv recently acquired a new milestone 3, and after gettint out of the box only did the one click root service to root it up, and installed bootstrap / rom manger and so on. But when I power off the phone holding X I get into a ! triangle screen, which I cant even power down the phone via button.
Also booting with M, or both vol buttons I can get into a list of options, but recovery, bt tools or any other wont get into the recovery mode.
is there any other way? clockwork mod is already installed says the app, and the normal boot goes ok.
Iv downloaded from another post the CM7 which I wanna install, but impossible without the recovery mode.
any help appreciated, all Iv found in the forums was how to get into recovery, but none worked for me.
... never mind
If you are using cwm, make sure you are using the DROID 3 bootstrapper. There is no way to enter recovery without it.
Imo, you should use safestrap (the official version) . It's way better. Because the only way to get to recovery when you have cwm is the bootstrap app, if you bootloop your phone, the only solution is an sbf. Safestrap retains access to the custom recovery.
EDIT: I saw you installed the bootstrap. To get to recovery, open the app and click the reboot recovery option, then reboot your phone.
Sent from my DROID3 using xda premium
both options: bootstrap recovery and reboot recovery goes to normal boot into the OS.
since its a payd up app, already sent email to the devs so I can help troubleshoot whats going up on my device, but got no answer.
Odd. Make sure you hit bootstrap recovery, wait for it to say success, then hit reboot recovery.
Sent from my DROID3 using xda premium
I've had that.problem before with the bootstrap before. I could not get it to work no matter what. Rerooted, made sure I had su, busybox etc. Sbf'd and did it all again. Just use safestrap, it works. Just uninstall your bootstrap first
Sent from my XT860 using xda premium
http://db.tt/XzRiaG55
This is the modded version. Its supposed to be able to flash both safe and non safe modes but it doesn't. You can only flash in safe mode. But it does have a console included which can be handy. Its still cwm but redesigned ui. Note that if a rom isn't specifically meant for the xt860 you will need a patch for it. So far only eclipse 3.0 and mavrom 4.0 have xt860 version. I'll also find you the sbf for you. Always handy to have
Sent from my XT860 using xda premium
http://sbf.droid-developers.org/umts_solana/list.php
Choose the one for your carrier. If you are running windows you'll need rsdlite to use it. Just unzip the sbf somewhere on your comp and point rsdlite to the xml file in the unzipped folder. Make sure your battery is charged before doing this. And before flashing anything too. Just in case.
Sent from my XT860 using xda premium

[How To] CWM Recovery

With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Nice i don't know if i should try it or wait for an official one for our device. In the mean time back to my nexus 4
Sent from my MB886 using xda premium
If you really want to give it a spin you can always flash the Photon Q version otherwise I'm sure there will be an official version ported soon
Sent from my MB886 using xda premium
Dumb question...... if I uninstall ss and install cwm will I lose the current ROM im using?
Sent from my MB886 using xda app-developers app
You'll have to reinstall yes.
Sent from my JokerMATRIX HD MAXX
Dumb question part 2..... uninstall ss first and then install cwm? Also erase all ROM slots before uninstalling? Thanks!
Sent from my MB886 using xda app-developers app
Yea make sure to erase the rom slots. I forgot to and uninstalled then was missing quite a bit of space lol.
Sent from my JokerMATRIX HD MAXX
I was thinking it might be a good idea lol. Thanks!
Sent from my MB886 using xda app-developers app
it actually works. lol
freshlycutlawn said:
With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Have you flashed anything with it?
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
freshlycutlawn said:
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
So far, i have installed the cwm for the photon q like you, and made a back up through it. Im going to see if it will restore from it as well. ill keep everyone updated.:good:
:edit: I sucessfully backed up my stock JB rom, wiped everything, and restored everything back and everythings perfect... I dont know what else to try before attempting to flash using the photon CWM. any ideas?
I uses the photon q recovery to backup & restore, and haven't had any issues yet. No ROM flashing for the time being, just haven't tried it yet.
Sent from my MB886 using xda premium
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
I'm on aosp pizza but I reverted to the stock jelly bean system. Mounted system installed the aosp ROM the Mexico firmware was giving me hell except with cm 10
Sent from my Nexus 4 using xda app-developers app
DaveNavy said:
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
Click to expand...
Click to collapse
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
bconcio said:
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
Click to expand...
Click to collapse
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
jbatacan said:
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
Click to expand...
Click to collapse
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
DaveNavy said:
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
Click to expand...
Click to collapse
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
bconcio said:
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
Click to expand...
Click to collapse
Fastboot was kicking errors and was boot looping into fastboot with firmware flash fail, I found however I could start into AOSPizza in DB mode (Safe Mode) , so I did that, charged up the phone 100% then used RSDLite and Reflashed Stock current firmware, it however does not re-lock the bootloader as some have mentioned might be the case in other post's, from there I started up the phone,turned on usb debug, used "motochopper" to root it, then installed Rom Manager from the market, flashed clockwork to device with the Photo Q CWM , copied AOSPixxaV1.zip ( The ROM ) and GappizzaV1.zip to the Phones internal storage not on the external SD memory card, from there went to clockwork mod on my atrix opened up the program and selected to reboot into recovery, went to the mounts and storage then select Mount System then go back then install zip from sd card then choose zip from sd card, then scroll to your rom and select it and it will flash when its complete you will go back and go to reboot system now, it will ask you if you want to bypass stock recovery on boot select it and your phone will reboot into AOSPizza......Have Fun!

Categories

Resources