Database Info

CWM: A thread of its own

OK, it goes without saying that to do rooting and flashing you need to have at least a basic understanding of the English language, a decent IQ and the ability to follow basic instructions.
However, with the CWM mod that's out there for this phone, there are dangers in trying to use for anything other than flashing. IMO, the problem is that those discussions are getting buried in long threads that were originally meant for other Subjects. I feel that CWM needs to have a thread of its on to benefit EVERYONE, especially the newbies. So I am starting it off with this simple instruction:
DO NOT TRY TO USE A ROM MANAGER AT THIS TIME! THE DEVS WILL LET YOU KNOW WHEN YOU CAN USE IT
ALSO; DO NOT USE CWM TO RESTORE AT THIS TIME YOU WILL BE BRICKED
#2 IF YOU WANT TO GET INTO CWM FROM START-UP TO FLASH A ROM - HOLD DOWN THE VOL UP BUTTON + HOME BUTTON + POWER BUTTON, WHEN YOU SEE THE SAMSUNG LOGO, RELEASE THE POWER BUTTON.
TO END THE CONSTANT QUESTIONS ABOUT THE "GO BACK" MENU OPTION: SCROLL COMPLETELY THROUGH ALL MENU OPTIONS TWICE, THE GO BACK OPEN WILL THEN APPEAR
I ask the devs to post info. here even if it has been posted in one of the threads.
Forum Management FTW!

If one of the devs could throw up the file to flash CWM and the instructions, that might be helfpful as well.

Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.

boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?

kejar31 said:
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
Click to expand...
Click to collapse
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.

hoppermi said:
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
Click to expand...
Click to collapse
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?

kejar31 said:
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
Click to expand...
Click to collapse
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...

boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
I have found pressing the vol up and vol down at the same time enables the "go back" option. It will state that it is enabled.
It will pop up when you select another option first.
Sent from my voodoo Droid Charge ED2

On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
And ShotgunSam you might as well add don't restore w/ CWM in your big red warning.

boostedjti said:
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
Click to expand...
Click to collapse
Well, I'm already stuck there, if your idea isn't too complex, I can try it out

I have one that was bricked for this reason. If anyone has any ideas I will test them out. I am good with adb shell and have been trying to figure out how to change the bootmode=7 which I think is the sdcard to 6 which I think is the nand. Can't find where the file is in the system because I can't boot. Or a signed update zip that boots Android of the sdcard like the hd2 might work.

stranula said:
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
Click to expand...
Click to collapse
Go to the epic 4g forums and in development you'll find a thread that contains an update.zip that will use cwm 3.0.2.x. adb push that update to your sd card or just transfer it. Flash jts cwm compatible kernel through odin then try applying the update.zip.
Just a theory. If cwm boots, you can then flash a rom and that may work.
hoppermi said:
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
Click to expand...
Click to collapse
That was something I mentioned on irc the other day lol great minds think alike.

Has anyone with bricked phones tried to reach out to Koush?
Sent from my ADR6400L using Tapatalk

kejar31 said:
Has anyone with bricked phones tried to reach out to Koush?
Click to expand...
Click to collapse
Koush has been worse than useless for the Galaxy S.

Well he does have the Charge listed as a supported device on his website.. if its bricking he might help.. so if my phone were bricked I would at least try and start with him
Sent from my ADR6400L using Tapatalk

I tweeted at him and said the problem. No response yet. Ill keep posted. Everyone should tell him
Sent from my SCH-I510 using XDA Premium App

Koush is looking into it.
Sent from my SCH-I510 using XDA Premium App

Thanks OP for this tread. I agree 100%.
1) I think some "bootloopers" have had success entering download mode when their SD card was pulled.
2) Have any brickers/bootloopers tried the JIG method to force download mode?
Google JIG:
http://forum.xda-developers.com/showthread.php?t=819551
http://www.youtube.com/watch?v=iSaeaAcJHqw
http://www.youtube.com/watch?v=GjDkShT-65Y
http://samsungjigs.blogspot.com/
http://shop.ebay.com/skisky1/m.html
3) Also, I *think* someone who had bootloops was able to clear his data/cache folder somehow/someway. And I *think* he was either able to stop the bootloops or at least get into download mode. But maybe I am thinking of something else here.

Would empty cache/dbdata/movinand.bin files be helpful for Odin? We could rip them out of one of the Fascinate Odin packages to be included with a "Restore to stock" Odin package. Based on the error I've seen of someone that tried to restore, it looks like /data is getting FUBARd and that's causing the problem, but it's not something I want to personally test since my phone is working.

Anyone having issues after a restore, please see if you have adb shell access. If so, please grab a logcat and post it here.
Sent from my SCH-I500 using XDA App

[Q] Double Recovery Install - Arg (stupid mistake)

I goofed up. :cyclops:
I was on a nice custom 2.3.6 ROM, and now I'm just on needles.
I was ...um, let's just say,.. barely conscious. So, anyhow I'm not 100% positive what I did -- but this is my best guess.
I am fairly sure I was fiddling with system settings (just looking around, no changes), and probably because of the apps I had installed, things became unstable.
What's strange now, is that I don't recall pausing on CWM recovery, which is VERY odd indeed, because I WAS really happy to have installed JW Daddy's CWM on every boot installed, and I've still got several full CWM backups that should work fine.
This much is 100% certain, after several failed attempts to stabilize (even long enough to uninstall the most recent apps), I decided to just restore a CWM backup. But I had forgotten that I had the CWM on every boot mod installed (because it wasn't working anymore, for some reason), and still didn't remember, even after I failed to find the Bootstrap app (which I had uninstalled, just after installing the CWM on every boot mod).
I must have just figured it was probably some ROM or backup of a ROM that I had put on that was clean I guess. Of course, on the next cycle up, it stayed up just long enough, so that I finally got the BootStrap installed again, but before I could hit the button to reboot into CWM, the phone crashed back down into a loop again, and this time, never came back up at all, not even for a second. Factory reset, & clearing Dalvik cache didn't help either.
The problem is that I didn't have a chance to reboot into CWM Recovery after installing the bootstrap and now that it won't boot at all, I'm just stuck looping without an easy way to get into CWM recovery. I am able to get into the useless stock recovery and/or fastboot, but I'm not sure what to do, now that I've got (I think) 2 additional goof-ball mods potentially in there --- one for the old faithful A2 Bootstrap, that is used to reboot into CWM recovery, and of course, the CWM on every boot mod, which was for whatever reason, broken by some other cause (possibly the apps I was fiddling with?) even before I 'worsened' things up.
I'd rather not go all the way back to stock 2.3.5 via RSD but I may have to? What say thee?
===================================================
SPECS PRIOR TO SCREW-UP:
AT&T Best Buy
Model Number: MB8656
Android version : 2.3.6
Display : SuperCharged_V_5_Update_2

Yeah, it sounds like a goof up to me.
You're probably going to have to FXZ the 2.3.5 and then upgrade to the 2.3.6 and use the FXZ fix to get your phone back to where it was. The problem that probably occurred was that you had both the bootstrap and the cwm on boot at the same time. You shouldn't use both of them, only 1 or the other.
If you read the posts, it tells you to un-allow the bootstrap app after installing the cwm on every boot. In fact, the roms that come with the cwm on boot on them don't even have the bootstrap app.

DusThis said:
If you read the posts, it tells you to un-allow the bootstrap app after installing the cwm on every boot. In fact, the roms that come with the cwm on boot on them don't even have the bootstrap app.
Click to expand...
Click to collapse
Oh well. I was hoping to at least only FXZ to 2.3.6 and maybe skip a step, since I was already there. ugh.
Thanks DusThis (hitting the Thanks Button now ;-)
Is there a single criteria that defines when we can FXZ back to 2.3.6 versus 2.3.5?

Yeah I would FXZ back to 2.3.5 and do the OTA, then restore your CWM backup using the bootstrap.
There is not currently a way to FXZ back to 2.3.6. Our 2.3.5 was something a very nice XDA member went and got off of a moto server for us. Since this phone ships with 2.3.5, and not 2.3.6 I am sure we will not see a 2.3.6 FXZ unless we make our own which is totally possible, but more work that it may be worth.

jimbridgman said:
Since this phone ships with 2.3.5, and not 2.3.6 I am sure we will not see a 2.3.6 FXZ unless we make our own which is totally possible, but more work that it may be worth.
Click to expand...
Click to collapse
<-- ahh, this makes sense now. There is more to an FXZ than just what comes OTA (I had forgotten that ;-)

Once you FXZ back to 2.3.5 you can just simply reroot, install A2 bootstrap and then perform a backup. I have done this several times and have never had any ill effects. Just make sure your backup is GOOD

To get rid of your errors now you must have to restore FXZ then update to 2.3.6 and restore CWM backup after that
To restore FXZ follow:
http://forum.xda-developers.com/showthread.php?t=1721218

jimbridgman said:
Yeah I would FXZ back to 2.3.5 and do the OTA, then restore your CWM backup using the bootstrap.
There is not currently a way to FXZ back to 2.3.6. Our 2.3.5 was something a very nice XDA member went and got off of a moto server for us. Since this phone ships with 2.3.5, and not 2.3.6 I am sure we will not see a 2.3.6 FXZ unless we make our own which is totally possible, but more work that it may be worth.
Click to expand...
Click to collapse
people seem to want it though. I will make it. I just have to pull all the images from the updated phone then write the XML with the same format right.
Sent from my MB865 using xda premium

lkrasner said:
people seem to want it though. I will make it. I just have to pull all the images from the updated phone then write the XML with the same format right.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yes, but getting the boot image will be a challenge, I think. Let me know if you run into an issue and I might be able to point you in the right direction.
The rest are east but, you HAVE to cat the device for each image, you can't dd it.
I would use the SAME xml file, just update the md5 sums.
The rest of the changes you already know.

I'm no expert at that kind of stuff by any means, but wouldn't it be easier to do if you FXZ your phone to 2.3.5 and then download the OTA. Don't install it right away and pull the update.zip and use that to make the 2.3.6 FXZ??

DusThis said:
I'm no expert at that kind of stuff by any means, but wouldn't it be easier to do if you FXZ your phone to 2.3.5 and then download the OTA. Don't install it right away and pull the update.zip and use that to make the 2.3.6 FXZ??
Click to expand...
Click to collapse
Nope, an ota is just basically linux patch files that are then applied to the apks and kernel and os files on your phone, it is not a whole new firmware that writes over the one on your phone.
Linux/UNIX patch:
http://en.m.wikipedia.org/wiki/Patch_(Unix)

Oh ok. That makes sense. I'm pretty much self teaching myself on this kind of stuff and I know that for instance the cheesecake stuff can be looked at and checked so I didn't know if an OTA update could be done the same way. Thanks for the link Jim.

DusThis said:
Oh ok. That makes sense. I'm pretty much self teaching myself on this kind of stuff and I know that for instance the cheesecake stuff can be looked at and checked so I didn't know if an OTA update could be done the same way. Thanks for the link Jim.
Click to expand...
Click to collapse
the cheesecake stuff and otas are the same thing. you can tell some stuff by looking inside the zips. for example they often contain a build.prop, which lets us see if it is ics, or what has changed.

Need help pushing gapps with odin ASAP!

I installed paranandroid and gapps but it was the wrong gapps which caused it to error out during install. so now I have the correct gapps on my SD card but do not know how to access it through my phone since I have no recovery. How do I get gapps back on phone so I can get into recovery?

damn....

PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...

1Android said:
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
Click to expand...
Click to collapse
OK, don't panic yet! Basic questions first:
Did you flash a recovery like CWM (Clockworkmod) before trying to flash the rom?
Are you able to get into recovery mode via volume up+power+home?

Why dont you reflash the ROM and then do the right Gapps? That way you wont have any screwed up files at all. If you really screwed it up just Odin back to stock and start again.

just flash the rom over the top then flash the right gapps

I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.

1Android said:
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
Click to expand...
Click to collapse
Good, now when that's done, lets get you up and running with paranoid. It is alot easier, and generally safer to flash through CWM on the phone itself then through odin on your desktop or even the odin app. What method were you using? And more importantly did you do a IMEI backup?

Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app

1Android said:
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The IMEI is very easy to do, especially if your running Synergy. There are 3 methods in the link I'll attach. The first uses any terminal emulator app (free in play store) and simply typing in a code: su (enter) then: reboot nvbackup (enter)...done! Then there is the next way to create a second easier to install if something were to happen way using a Synergy recovery zip. You must do the first method first or the zip way will backup the wrong IMEI. On the link there is another link to the Synergy Key zip file (its right in the directions with HERE in bold as the link). Download zip, run it in recovery ONCE to create the backup, thats it! The synergy backup can then be used on other roms. Overall its super easy, I spent 2hrs researching and 5 min creating the backup. IT really is as simple as that, just do it in order. As far as paranoid goes, I don't have hands on with it, too many bugs for me to bother with it yet, but yes it generally should use less battery due to JB's unmatched efficiency.
Here's the link: (only need to read the first page for making the backups, read further to restore which hopefully won't be needed!)
http://forum.xda-developers.com/showthread.php?t=1852255

I will look into it tomorrow. Thank you so much for your help!! Very much appreciated.
I need/want a fully functional Rom without a bunch of bugs. Might stay with synergy till some bugs can be worked out.
Sent from my SCH-I535 using xda app-developers app

Atrix 2 BootStrap Recovery[CWM 6] for MIUI v5[OTA UPDATE NOW WORKS]

This is the bootstrap recovery for atrix 2 based on clockworkmod recovery 6 [CWM 6] to be used with MIUI v5
Steps to use bootstrap cwm6:
1. Install the Atrix2Bootstrap.apk in the rooted leaked jellybean #3
2. Select "Bootstrap Recovery"
3. Superuser will prompt for permissions. Give access to it
4. Select "Reboot Recovery"
5. Then flash latest MIUI v5
6. With this recovery ie CWM6, Direct OTA update will work, the phone will flash the OTA and automatically reboot. Earlier Bootstrap based on CWM5 threw an error if we tried to auto update from system updates. This is the recommended recovery to be used with MIUI v5. Now you wont get any error messages while OTA update.
If you find the post useful...plz hit thanks.

arnab said:
This is the bootstrap recovery for atrix 2 based on clockworkmod recovery 6 [CWM 6]
Steps to use bootstrap cwm6:
1. Install the Atrix2Bootstrap.apk in a rooted stock rom
2. Select "Bootstrap Recovery"
3. Superuser will prompt for permissions. Give access to it
4. Select "Reboot Recovery"
If you find the post useful...plz hit thanks.
Click to expand...
Click to collapse
Is this useful since 98-99% of our latest ROM's are based on BMM? No disrespect just stating the facts. I'd personally like to try it out since Multi-booting is not my thing really anymore... Nice find either way. Thanks for the share. I'll give a thanks when I try it out
Sent from my MB865 using XDA Premium 4 mobile app

A2Trip said:
Is this useful since 98-99% of our latest ROM's are based on BMM? No disrespect just stating the facts. I'd personally like to try it out since Multi-booting is not my thing really anymore... Nice find either way. Thanks for the share. I'll give a thanks when I try it out
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm wondering the same thing since I don't care much about multi-booting. My guess would be that you would have to flash the ROM first, then uninstall BMM, then install this but don't take my word for it yet. I'm going to play around with it once I get home and charge up my A2.
@arnab, thanks for this.:thumbup:
If I had a dollar for every time I said that, I'd be making money in a very weird way.

It works perfectly...U don't have to worry a thing...Personally I like non kexec based custom ROMs...But be sure to remove BMM before installing it.

Are we able to cwm at boot?

No

atrix2man said:
Are we able to cwm at boot?
Click to expand...
Click to collapse
Good point out that IS one thing I like with BMM. Forgot CWM doesn't really work that way without an extra mod probably.
Sent from my MB865 using XDA Premium 4 mobile app

Wish we could boot kexec with this

seems like alot of extra work required to get a recovery that you cant boot directly into, and that no still worked on ROM actually support this anymore.
So from a BMM ROM, must remove BMM recovery by using the BMM application, then remove the app, then install this and then use it to install the recovery that we cant get into at boot.
Is that correct?
Not purposely coming off as an ass, can just see alot of problems coming from it.

You will not be able to boot any kexec/2nd init based roms using this.. @OP, I recommend you to take a look at the cmdefy recovery in altered's github or wang's.. If you want to get them working..
In short your recovery must start on every boot (look into Cwm on every boot) and then run a script that loads kexec or 2nd init..
Sent from my MB865 using Tapatalk 2

Yea i checked it out and will only use this if i want to stay on ics. Pretty kool tho! :good:

I am not sure of how relevant this is but out of my personal experience, if you have already installed BMM make sure to search for the logwrapper.bin file being altered (or was it deleted, don't recall) issue in the forum before uninstalling BMM, else it may cause you grief.
EDIT
Just looked it up, the issue was :
Quote
DO NOT INSTALL BMM IF YOU USED A2 BOOTSTRAPPER BEFORE. THAT WILL MESS THINGS UP WITH YOUR LOGWRAPPER.BIN. THERE IS A GOOD CHANCE YOU WILL BOOT LOOP AFTER REBOOT. NOW IF FOR SOME REASON YOU DID NOT READ THIS, AND GET A MESSAGE ABOUT BMM ASKING YOU TO GET HELP, BEST THING FOR YOU TO DO IS RECHARGE YOUR BATTERY FULLY AND FXZ BACK. OR THERE IS A GOOD CHANCE YOU WILL HAVE TO USE MCGRUVYER METHOD OR ANOTHER A2 BATTERY. USER RAD7 RECENTLY HAD QUITE A LOT OF TROUBLE WITH HIS BATTERY DYING AFTER BMM MESSED WITH LOGWRAPPER. YOU HAVE BEEN INFORMED.

I want to thank all those who replied. As you all gave me a clear & concise understanding of the issue being discussed. And I will be staying with BMM for all the reasons that were very easy to understand.

RAD7 said:
I am not sure of how relevant this is but out of my personal experience, if you have already installed BMM make sure to search for the logwrapper.bin file being altered (or was it deleted, don't recall) issue in the forum before uninstalling BMM, else it may cause you grief.
EDIT
Just looked it up, the issue was :
Quote
DO NOT INSTALL BMM IF YOU USED A2 BOOTSTRAPPER BEFORE. THAT WILL MESS THINGS UP WITH YOUR LOGWRAPPER.BIN. THERE IS A GOOD CHANCE YOU WILL BOOT LOOP AFTER REBOOT. NOW IF FOR SOME REASON YOU DID NOT READ THIS, AND GET A MESSAGE ABOUT BMM ASKING YOU TO GET HELP, BEST THING FOR YOU TO DO IS RECHARGE YOUR BATTERY FULLY AND FXZ BACK. OR THERE IS A GOOD CHANCE YOU WILL HAVE TO USE MCGRUVYER METHOD OR ANOTHER A2 BATTERY. USER RAD7 RECENTLY HAD QUITE A LOT OF TROUBLE WITH HIS BATTERY DYING AFTER BMM MESSED WITH LOGWRAPPER. YOU HAVE BEEN INFORMED.
Click to expand...
Click to collapse
If I am not mistaken you can uninstall BMM from within the app itself and it will automatically clean all of that up for you. It's been a while since I've had the time to experiment with my A2, but I'm almost positive of that at least.
If I had a dollar for every time I said that, I'd be making money in a very weird way.

1BadWolf said:
If I am not mistaken you can uninstall BMM from within the app itself and it will automatically clean all of that up for you. It's been a while since I've had the time to experiment with my A2, but I'm almost positive of that at least.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Click to expand...
Click to collapse
Yeah you are right in what you have stated but what I wanted the guys to be wary was installing BMM after previously having installed and uninstalled A2 bootstrap in which case the logwrapper.bin issue crops up causing boot loop and battery cannot be charged until fresh fxz via rsd is done. Even I have not been experimenting for long but strongly contemplating getting aboard jbx :fingers-crossed:

I updated the thread. Its made for MIUI v5 enthusiasts (santajin)

arnab said:
I updated the thread. Its made for MIUI v5 enthusiasts (santajin)
Click to expand...
Click to collapse
with this recovery you can apply any OTA update of the miui rom?

Yup...earlier it used to crash giving sm sd card error...nw it will work like a charm...actually this is the official recovery for santajin's miui v5 at miui.com

guys atleast press the thanx button

MIUI is not for ATT .... right ?? :silly: :silly:

[q] please respond fast waiting...

OK so i installed pac man rom from this site ok :http://true-android.blogspot.com/2013/11/android-431-jelly-bean-pac-man-rom-for_998.html
and now i'm stuck in bootloop... i get the moto logo and blackscreen and it just reboots after that..... can someone help me fix this or give me a guide to get back to ICS or another rom. I really don't like ICS cause its slow but if i have to get back to it i will.
i made a back up of ICS but since i can't boot back into recovery i can't go back otherwise this post would not exitst

Antonoram said:
OK so i installed pac man rom from this site ok :http://true-android.blogspot.com/2013/11/android-431-jelly-bean-pac-man-rom-for_998.html
and now i'm stuck in bootloop... i get the moto logo and blackscreen and it just reboots after that..... can someone help me fix this or give me a guide to get back to ICS or another rom. I really don't like ICS cause its slow but if i have to get back to it i will.
i made a back up of ICS but since i can't boot back into recovery i can't go back otherwise this post would not exitst
Click to expand...
Click to collapse
You should either ask for support from the developer on the website you downloaded the ROM from, or just flash the FXZ for your phone and start over. If you don't know how to flash an FXZ then you've got some reading to do. There is a great and comprehensive guide to flashing FXZs by alteredlikeness in this forum so I'm not going to try to explain it here. Besides, alteredlikeness did it better than I could anyway. Just read and make sure you understand what you're doing before getting started to avoid any further complications. Good luck!:thumbup:
If I had a dollar for every time I said that, I'd be making money in a very weird way.

1BadWolf said:
You should either ask for support from the developer on the website you downloaded the ROM from, or just flash the FXZ for your phone and start over. If you don't know how to flash an FXZ then you've got some reading to do. There is a great and comprehensive guide to flashing FXZs by alteredlikeness in this forum so I'm not going to try to explain it here. Besides, alteredlikeness did it better than I could anyway. Just read and make sure you understand what you're doing before getting started to avoid any further complications. Good luck!:thumbup:
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Click to expand...
Click to collapse
I already installed ICS on my phone .... I'm not that big of a noob but i wanna know... i used bootstrap to install the rom and i wanna know if its safe to use BMM. I've been reading posts that says its dangerous to use BMM after using bootstrap but i flashed ICS using RSD Lite so shouldn't any files from bootstrap be gone?

Antonoram said:
I already installed ICS on my phone .... I'm not that big of a noob but i wanna know... i used bootstrap to install the rom and i wanna know if its safe to use BMM. I've been reading posts that says its dangerous to use BMM after using bootstrap but i flashed ICS using RSD Lite so shouldn't any files from bootstrap be gone?
Click to expand...
Click to collapse
Delete bootstrap and use BMM. Bootstrap is old and does not support kexec. I don't know who said this, but BMM is pretty safe to use. Flash rom on system 3,4,5,6.

nishant203 said:
Delete bootstrap and use BMM. Bootstrap is old and does not support kexec. I don't know who said this, but BMM is pretty safe to use. Flash rom on system 3,4,5,6.
Click to expand...
Click to collapse
instructions or video would be nice if its not to much.:fingers-crossed:

nishant203 said:
Delete bootstrap and use BMM. Bootstrap is old and does not support kexec. I don't know who said this, but BMM is pretty safe to use. Flash rom on system 3,4,5,6.
Click to expand...
Click to collapse
OK i followed instructions from this video https://www.youtube.com/watch?v=gT3zevmZg8s the one thing i did see was when i went in backup/restore i saw no bootstrap i then installed root explorer and looked for the logwrapper.bin but i didn't see it there was only logwrapper no .BIN so can i just install BMM safely from here?