Got the phone today and I'm considering installing a Svc7 based on leak#2 as the only system. Not a fan of GB Motoblur so I'd rather not have it take up internal memory.
I still have some reading to do but here's what I'm aiming at:
Install leak#1
Allow OTA to proceed
Root
Install scv7 leak #2 as only systen in boot menu manager
Keep an eye out for leak#2/final based ICS and CM10 roms to add as 2nd system
Can you see anything obviously bad about the process outlined?
You may want to stay on leak #1 for the time being. As of right now there's no way back to GB from leak #2 if you have problems with your phone.
Sent from my MB865 running SCV7
r_scotter said:
You may want to stay on leak #1 for the time being. As of right now there's no way back to GB from leak #2 if you have problems with your phone.
Sent from my MB865 running SCV7
Click to expand...
Click to collapse
This is stated in many stickies so why don't you tell me about a specific scenario that would require GB?
RoadToNever said:
This is stated in many stickies so why don't you tell me about a specific scenario that would require GB?
Click to expand...
Click to collapse
If you screw something up and need to FXZ back to stock, if you get into a bootloop on leak 2 you're done.
JDogg1329 said:
If you screw something up and need to FXZ back to stock, if you get into a bootloop on leak 2 you're done.
Click to expand...
Click to collapse
I see your A2 is softbricked. Was it related to ICS updating and did you figure out what caused it?
RoadToNever said:
I see your A2 is softbricked. Was it related to ICS updating and did you figure out what caused it?
Click to expand...
Click to collapse
I was fxzing back to GB from ICS because ICS kept crashing and rebooting, the fxz ran successfully but didn't work (bootloop), which apparently is normal, but my battery is also dying so I couldn't use RSD to try again. I'm having even more problems now with my phone not recognizing that a usb cable has been plugged in but that's another story. SCV7 says leak2 in the title but it's based on leak1, basically it's all the good stuff from leak2 but the bootloader is from leak1 so you CAN fxz back from it. There are NO custom roms for Leak2(OTA) and everyone is saying to stay away from it for now, there's really no reason to install the OTA.
Ok, I suppose I could run a leak#2 ROM as a second system for now and reconsider only when CM10 becomes boot menu compatible. Also I suppose the amount of Gingerbread left over after installing leak #1 minimal. Thanks all!
Road, please read the following thread and threads within it.
http://forum.xda-developers.com/showthread.php?t=1897042
Because the atrix 2's bootloader is locked we rely on the fxz to get us out of binds. We only have a gingerbread fxz right now. This is why we're recommending everyone to stay on leak one.
It's just not safe to be on the official. Plus leak two has been baked into scv7.
Almost everyone has fxz'd at least once. If not more.
The choice is yours.
Sent from my SAMSUNG-SGH-I727 using xda premium
RoadToNever said:
Ok, I suppose I could run a leak#2 ROM as a second system for now and reconsider only when CM10 becomes boot menu compatible. Also I suppose the amount of Gingerbread left over after installing leak #1 minimal. Thanks all!
Click to expand...
Click to collapse
Try timmytim's Team Shogun ROM. Its awesome.
Sent from my MB865 using xda premium
I've gotten to having SCv7 as the first system. Maybe I'll test Shogun as second system when I have more time, right now I'm enjoying the AOSP-ish experience in SCv7. Smooth sailing so far.
JDogg1329 said:
I was fxzing back to GB from ICS because ICS kept crashing and rebooting, the fxz ran successfully but didn't work (bootloop), which apparently is normal, but my battery is also dying so I couldn't use RSD to try again. I'm having even more problems now with my phone not recognizing that a usb cable has been plugged in but that's another story. SCV7 says leak2 in the title but it's based on leak1, basically it's all the good stuff from leak2 but the bootloader is from leak1 so you CAN fxz back from it. There are NO custom roms for Leak2(OTA) and everyone is saying to stay away from it for now, there's really no reason to install the OTA.
Click to expand...
Click to collapse
Very sorry for Off-Topic, but the ROM here is ICS leak #1, isn't it?
http://forum.xda-developers.com/showthread.php?t=1683893
From what I've gathered it's Leak#2 with the leak#1 bootloader(allowing for fxz to Gingerbrad)
RoadToNever said:
From what I've gathered it's Leak#2 with the leak#1 bootloader(allowing for fxz to Gingerbrad)
Click to expand...
Click to collapse
Alright!
This is the one I needed, so that I can FXZ back to GB anytime.
Wait! Checked the link again, it's pure leak#1! I'd recommend Shogun or SCv7 which are leak#2/official OTA-based AND will let you go back to Gingerbread if necessary.
Related
NOTE: this is from 2.3.6 to stock 2.3.5. NOTHING RELATED TO ICS DOWNGRADE.
I hope my experience on reverting back to stock 2.3.5/2.3.6 can help other people with similar problem.
I was running Romulus V2.0 (Android 2.3.6). I wanted to update to Leaked ICS or prepare for future ICS official update. So I need to revert back to stock 2.3.6.
The method Jim suggested is (1) FXZ to 2.3.5. (2) OTA to 2.3.6. But when I use RSD to flash 2.3.5 FXZ (precisely following the beginner's guide, download InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip and replace files in "replace.zip"), I get "Invalid CG version". My next try is to follow the guide in http://forum.xda-developers.com/showthread.php?t=1493386, and my phone is alive again. However, I cannot do a factory reset, so I still cannot go back to stock 2.3.6.
After a lot of searching, I was able to find another "replacement package". Its linke is http://www.mediafire.com/?3bs8ovqteawab02, named "replaceFilesInFXZ.zip". I replaced files in InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip with files in this package. My phone boots without problem and is on stock 2.3.5. I also have OTAed to 2.3.6.
I think this could be helpful for those that want to revert back to stock 2.3.5/2.3.6, and be able to update to ICS. If you are on 2.3.6, I think it is safe to take a try, since there is no hard brick problem as long as you do not flash ICS leak.
---------------------------
I was thinking why some people can FXZ 2.3.5 following the beginner's guide but some people cannot. One possible case could be (please correct me if I am wrong):
I was on stock 2.3.5, but has never OTAed to 2.3.6. I was always using bootstrap recovery to flash other's customized 2.3.6 rom. Therefore, some files such as CDT.bin, boot.img, recovery.img, device_tree.bin and lbl was never updated to 2.3.6 version.
When I follow the beginner's guide, I think this guide assumes that everyone has ever OTAed to 2.3.6 before. So some inconsistency happens.
jerrycrystal said:
I hope my experience on reverting back to stock 2.3.5/2.3.6 can help other people with similar problem.
I was running Romulus V2.0 (Android 2.3.6). I wanted to update to Leaked ICS or prepare for future ICS official update. So I need to revert back to stock 2.3.6.
The method Jim suggested is (1) FXZ to 2.3.5. (2) OTA to 2.3.6. But when I use RSD to flash 2.3.5 FXZ (precisely following the beginner's guide, download InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip and replace files in "replace.zip"), I get "Invalid CG version". My next try is to follow the guide in http://forum.xda-developers.com/showthread.php?t=1493386, and my phone is alive again. However, I cannot do a factory reset, so I still cannot go back to stock 2.3.6.
After a lot of searching, I was able to find another "replacement package". Its linke is http://www.mediafire.com/?3bs8ovqteawab02, named "replaceFilesInFXZ.zip". I replaced files in InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip with files in this package. My phone boots without problem and is on stock 2.3.5. I also have OTAed to 2.3.6.
I think this could be helpful for those that want to revert back to stock 2.3.5/2.3.6, and be able to update to ICS. If you are on 2.3.6, I think it is safe to take a try, since there is no hard brick problem as long as you do not flash ICS leak.
---------------------------
I was thinking why some people can FXZ 2.3.5 following the beginner's guide but some people cannot. One possible case could be (please correct me if I am wrong):
I was on stock 2.3.5, but has never OTAed to 2.3.6. I was always using bootstrap recovery to flash other's customized 2.3.6 rom. Therefore, some files such as CDT.bin, boot.img, recovery.img, device_tree.bin and lbl was never updated to 2.3.6 version.
When I follow the beginner's guide, I think this guide assumes that everyone has ever OTAed to 2.3.6 before. So some inconsistency happens.
Click to expand...
Click to collapse
Did you update to ICS or not? That does not appear to mentioned at all in your post... It just says that you are on 2.3.6 and not ICS... that really does not help all here if that is the case... those bricking have ALL installed the AT&T ICS leak, and tried to fxz back to 2.3.5...
So.... I am sure that what you mention does not really do any good since you appear to NEVER have installed the OTA ICS leak for AT&T, this really does not help...
jimbridgman said:
Did you update to ICS or not? That does not appear to mentioned at all in your post... It just says that you are on 2.3.6 and not ICS... that really does not help all here if that is the case... those bricking have ALL installed the AT&T ICS leak, and tried to fxz back to 2.3.5...
So.... I am sure that what you mention does not really do any good since you appear to NEVER have installed the OTA ICS leak for AT&T, this really does not help...
Click to expand...
Click to collapse
+1
Sent from my MB865 using xda's premium carrier pigeon service
It is from 2.3.6 to 2.3.5, not from ICS
jimbridgman said:
Did you update to ICS or not? That does not appear to mentioned at all in your post... It just says that you are on 2.3.6 and not ICS... that really does not help all here if that is the case... those bricking have ALL installed the AT&T ICS leak, and tried to fxz back to 2.3.5...
So.... I am sure that what you mention does not really do any good since you appear to NEVER have installed the OTA ICS leak for AT&T, this really does not help...
Click to expand...
Click to collapse
No, I was just to help people that running 2.3.6 to go back to stock 2.3.5 (There are people that have the same issue as mine). Nothing related to currently leaked ICS.
jerrycrystal said:
No, I was just to help people that running 2.3.6 to go back to stock 2.3.5 (There are people that have the same issue as mine). Nothing related to currently leaked ICS.
Click to expand...
Click to collapse
There is already a sticky on this... please search next time...
UGGGGGGHHHHHHH!!!!!
I am getting so tired of repeating myself:
http://forum.xda-developers.com/showthread.php?t=1778853
jerrycrystal said:
...After a lot of searching, I was able to find another "replacement package". Its linke is http://www.mediafire.com/?3bs8ovqteawab02, named "replaceFilesInFXZ.zip". I replaced files in InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip with files in this package.
Click to expand...
Click to collapse
^^^This guy even shot himself in the foot right here^^^
Seriously, what do you consider "a lot of searching"?
Sent from my MB865 using xda's premium carrier pigeon service
jimbridgman said:
There is already a sticky on this... please search next time...
UGGGGGGHHHHHHH!!!!!
I am getting so tired of repeating myself:
http://forum.xda-developers.com/showthread.php?t=1778853
Click to expand...
Click to collapse
In fact, this is REALLY not the same thing as the sticky one!!!!! Especially the beginner's guide.
People have problem reverting back, that's why there is a post also sticked "2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX"
But these people will want to go back to full stock 2.3.5 with the ability to do OTA and recovery.
That's the reason I post this.
jerrycrystal said:
In fact, this is REALLY not the same thing as the sticky one!!!!! Especially the beginner's guide.
People have problem reverting back, that's why there is a post also sticked "2.3.6 from modified 2.3.5 Flashboot: "Invalid CG Version" FIX"
But these people will want to go back to full stock 2.3.5 with the ability to do OTA and recovery.
That's the reason I post this.
Click to expand...
Click to collapse
Dude, The invalid cg fix is the sticky, and it works perfect for this issue. Again this phone has been out over 10 months now, and we have seen it all. Please just sit back and watch things around here for a while before you jump in and just muddy the waters... it is already hard enough to keep people from doing stupid things, that we are expected to fix.
Apex_Strider said:
^^^This guy even shot himself in the foot right here^^^
Seriously, what do you consider "a lot of searching"?
Sent from my MB865 using xda's premium carrier pigeon service
Click to expand...
Click to collapse
I read all posts in this forum related to atrix2 about from 2.3.6 to 2.3.5. And the attachment I give is NOT the "replace.zip" in the beginner's guide, I found it in another forum.
jimbridgman said:
Dude, The invalid cg fix is the sticky, and it works perfect for this issue. Again this phone has been out over 10 months now, and we have seen it all. Please just sit back and watch things around here for a while before you jump in and just muddy the waters... it is already hard enough to keep people from doing stupid things, that we are expected to fix.
Click to expand...
Click to collapse
Sorry if I muddy the waters... and I appreciate what you have done for us, really.
But the method in sticky posts really does not help me to revert back to stock 2.3.5, I INDEED have read all posts/replies one by one. The method I posted actually worked for me to go back to stock 2.3.5, so I wanted to share it.
I was updating from Supercharged v5 update 2 to v7 yesterday, and I think I may have bricked my phone in the process.
I updated properly from v5 to v6, but from v6 to v7, I did not follow the step using bootmode, but instead I accidentally used CWM.
Now, it's stuck on the dual core screen, the phone can only be turned off by pulling the battery. It is still able to go into bootmode though, by pressing the volume up + down at the same time, and repeatedly pressing the power button. Let me know if it can be fixed, as the guide for the fxz hasn't been updated in two months, and this phone is important to me. Thanks.
Supercharged link: http://forum.xda-developers.com/showthread.php?t=1648421
I just used the fxp and it worked fine.
RoadToNever said:
I just used the fxp and it worked fine.
Click to expand...
Click to collapse
Did you brick it or do it from scv7? And are you referring to the fxp from two months ago, in that thread that says "last updated 7/22/12"?
So you went back to 2.3.5?
I made the misstake of installing CWM on top of CM10 resulting in a stuck boot. I used the 2.3.6 fxp from here: http://forum.xda-developers.com/showthread.php?t=1805975
CM9onmyMoPho said:
I was updating from Supercharged v5 update 2 to v7 yesterday, and I think I may have bricked my phone in the process.
I updated properly from v5 to v6, but from v6 to v7, I did not follow the step using bootmode, but instead I accidentally used CWM.
Now, it's stuck on the dual core screen, the phone can only be turned off by pulling the battery. It is still able to go into bootmode though, by pressing the volume up + down at the same time, and repeatedly pressing the power button. Let me know if it can be fixed, as the guide for the fxz hasn't been updated in two months, and this phone is important to me. Thanks.
Supercharged link: http://forum.xda-developers.com/showthread.php?t=1648421
Click to expand...
Click to collapse
Scv7 is ICS based only. If i'm not mistaken, you HAVE to be on ICS to use that ROM.
However, like RoadToNever said, a simple FXZ can be done to solve the problem. You're not hardbricked, only softbricked.
EDIT: This should be in Q&A, ↓↓ bootloop and softbricking are one in the same.
You didn't bricked you phone. You're into a bootloop.
Try installing ICS Leak again.
Axis is right sc5 & 6 are both GB based. You HAVE to be on the ICS leak before you install sc7. As it is an ICS ROM. Follow the instructions in this thread on how to fxz back to gingerbread. http://forum.xda-developers.com/showthread.php?t=1779968
However, some people who have done this have borked the system image before. So I wish you the best of luck. Always read carefully before installing anything, as I know rdavisct explained the procedure thoroughly in his thread for v7.
Sent from my SAMSUNG-SGH-I727 using xda premium
So am I supposed to use the fxp for ICS or for GB? I'm not completely sure and I don't want to actually brick it this time.
CM9onmyMoPho said:
So am I supposed to use the fxp for ICS or for GB? I'm not completely sure and I don't want to actually brick it this time.
Click to expand...
Click to collapse
If you was on GB, use the fxz for GB.
If you was already on ICS, then use Jim's script.
Sent from my MB865 using xda premium
Axis_Drummer said:
If you was on GB, use the fxz for GB.
If you was already on ICS, then use Jim's script.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Well, I'm not completely sure.
I was on v6, then I improperly updated to v7 with CWM, causing my phone to be stuck in a bootloop.
I also did a data wipe when I went into bootmode after the phone was bootlooping for a while.
Not sure what it actually is now.
CM9onmyMoPho said:
Well, I'm not completely sure.
I was on v6, then I improperly updated to v7 with CWM, causing my phone to be stuck in a bootloop.
I also did a data wipe when I went into bootmode after the phone was bootlooping for a while.
Not sure what it actually is now.
Click to expand...
Click to collapse
Dang, son. Ain't that a mopho'er! :laugh:
You flashed an ICS ROM from GB, that's not good. You're going to have to FXZ back to stock GB. Can you get into AP Fastboot by holding down the power button>volume up>volume down AT THE SAME TIME to boot into FB? Now that you have flashed improperly from GB to ICS, you have no system image to boot, that's why you're soft bricked.
Make sure you have the latest Mofo, erm... I mean, Moto drivers installed on your computer, then download RSD Lite (if you haven't already) and find the FXZ file to run search the forum for that thread, I'm too busy to find them for you. Then, assuming RSD gets you back to GB, do not flash from one system version to another (GB to ICS) unless you flash the ICS leak or wait for the official OTA to be able to flash ICS ROMs based off ICS or GB ROMs based on GB -whichever you choose to stay with...
EDIT: I see from the OP you can boot into AP Fastboot, which is a good sign.
Well I'm not 100% sure, but i'd say you need to use the GB fxz.
If you was on gb before trying the scv7 ROM, that would definitely put you into a loop. But if you had been on ICS leak, which is in the link FallofEnosis posted above, I wouldn't see why there would have been a problem.
And Apex just told you steps above on how to fxz once you get the proper one.
Sent from my MB865 using xda premium
Axis_Drummer said:
Well I'm not 100% sure, but i'd say you need to use the GB fxz.
If you was on gb before trying the scv7 ROM, that would definitely put you into a loop. But if you had been on ICS leak, which is in the link FallofEnosis posted above, I wouldn't see why there would have been a problem.
And Apex just told you steps above on how to fxz once you get the proper one.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You are 100% correct, since he never applied one of the leaks or an ota, which would change the bootloader, flashing the 2.3.6 fxz is the correct solution.
Thanks to everybody who helped, I've got scv7 running properly now.
CM9onmyMoPho said:
Thanks to everybody who helped, I've got scv7 running properly now.
Click to expand...
Click to collapse
Glad to hear that, mate. Just going forward, make sure you read the OP's instructions and requirements before attempting any flash, and you should have a pleasant experience with this device. Enjoy...
Totally agree with Apex. Always read! And if unsure, there's always the Q&A forum. We're here to help!
Sent from my SAMSUNG-SGH-I727 using xda premium
Well, i recently installed the MIUI rom to see if the battery bug was fixed, but its not.
So, i was triyng to go back to the ics leak, as always.
But now, i don't know why, when i'm in the step 14/21 the program doesn't move.
I mean, the '>>' is still moving, but i left it about an hour and it's still there.
Any ideas?
brianmoyano said:
Well, i recently installed the MIUI rom to see if the battery bug was fixed, but its not.
So, i was triyng to go back to the ics leak, as always.
But now, i don't know why, when i'm in the step 14/21 the program doesn't move.
I mean, the '>>' is still moving, but i left it about an hour and it's still there.
Any ideas?
Click to expand...
Click to collapse
Wait, you installed MIUI and now you're trying to use RSDLite to flash the ICS leak? That won't work. Which leak are you trying to flash? You're teetering on the verge of a soft brick if you go down this road. Not good...
Apex_Strider said:
Wait, you installed MIUI and now you're trying to use RSDLite to flash the ICS leak? That won't work. Which leak are you trying to flash? You're teetering on the verge of a soft brick if you go down this road. Not good...
Click to expand...
Click to collapse
Oh crap ^^
Firts i flash the '5.5.1-EDEM-27-MEARET_cfc.xml' with RSD lite. Then, when i'm on 2.3.6 i uptadte something via OTA. And then, i flash via recovery 'Blur_Version.55.28.37.MB865.MERetail.en.06.zip'
So, what should i do now?
brianmoyano said:
Oh crap ^^
Firts i flash the '5.5.1-EDEM-27-MEARET_cfc.xml' with RSD lite. Then, when i'm on 2.3.6 i uptadte something via OTA. And then, i flash via recovery 'Blur_Version.55.28.37.MB865.MERetail.en.06.zip'
So, what should i do now?
Click to expand...
Click to collapse
Uh oh... you installed an OTA from 2.3.6? Do you know what the update was for? If it was for the OTA to ICS, and you tried to flash a GB .xml or something lower than the official OTA to ICS, you likely have yourself one of those fancy non-FXA'able soft bricked devices...
Edit: If you were on MEARET you may stand a chance to FXZ back to GB, and try to re-OTA to ICS, as some users have noted success with. But, I'm not making any promises in your case...
@Apex, i tried the back to GB from ICS utility and I'm stuck at the dual core screen. I can access AP fastboot however. I was on the stock ICS leak, and i deleted safestrap, and logwrapper and logwrapper.bin files, and upon rebooting i was stuck at boot screen, now after trying the utility I am still in the same position... any help??
No, no. I doesn't installed anything yet. That was the steps that i do to go into ICS Leak, but now, y cant pass throught the first the step. When i flash the .xml it freeze at 14/21.
But, my other problem is that i don't have enough battery, and i think i'm going to the warrancy service.
Enzopreme said:
@Apex, i tried the back to GB from ICS utility and I'm stuck at the dual core screen. I can access AP fastboot however. I was on the stock ICS leak, and i deleted safestrap, and logwrapper and logwrapper.bin files, and upon rebooting i was stuck at boot screen, now after trying the utility I am still in the same position... any help??
Click to expand...
Click to collapse
If you were on the first leak, and tried to FXZ back to GB, you still have a fighting chance. It's only when on the 2nd leak (as was my case) that's there's no known way out of that soft brick. I'm sure Jim or alteredlikeness will see this and figure out how to bring you back out. Sorry, I'm not much help without my knowledge of FXZ'ing back from ICS leak #1. You shouldn't worry too much, I think you're situation is 'fixable'...
Sent from my rooted Mayan Calendar
Apex_Strider said:
If you were on the first leak, and tried to FXZ back to GB, you still have a fighting chance. It's only when on the 2nd leak (as was my case) that's there's no known way out of that soft brick. I'm sure Jim or alteredlikeness will see this and figure out how to bring you back out. Sorry, I'm not much help without my knowledge of FXZ'ing back from ICS leak #1. You shouldn't worry too much, I think you're situation is 'fixable'...
Sent from my rooted Mayan Calendar
Click to expand...
Click to collapse
how can i be sure whether i was on the first or second leak? i used the Blur_Version.55.13.25.MB865.ATT.en.US to get ICS, is that the 1st leak?
Can you give us a link to a thread where you downloaded it from? It did you ota to it?
Sent from my SAMSUNG-SGH-I727 using xda premium
http://www.grupoandroid.com/topic/52205-ics-filtrado-version-no-att/
This is the tutorial that i use. Is in spanish, but i guess that was extracted from here.
And, i use this MIUI.
http://forum.xda-developers.com/showthread.php?t=1914096&page=11
Made it to ICS without looking at this thread
I ran into the same issue freezing at 14/21 and failing at 16/21. Being stubborn I continued installing updates.
When an update is ready to install and my phone restart and say flash failure, I would hold both volume buttons and press the power button, once to exit and again to reenter. Next I would scroll to recovery and the installation would continue.
First update 2.3.6 then ICS. During ICS update I had flash failure a couple time but I just redo the button combination the scroll to recovery, thinking everything would be wonderful.
Well I now have ICS installed but my ringtones and notifications won't stick. When I shut down my phone is goes back to the flash failure screen and will not charge automatically while off. These are the only issues I've noticed, I'm sure there is more...
Please help!
I have a rooted A2 (AT&T Branded RUNNING on Straight Talk)
Baseband Version LUD_EDISON_R1D7_PATCH_36_111116_2336
Webtop Version WT-1.3.0-176
Kernel Version 2.6.35.7-g98a0a06 [email protected]#1
Build Number 5.5.1-175_EDMR1.25
So, I got this phone a long time ago after breaking (physical damage) my old Samsung Infuse. I had the Infuse (and a Captivate before that) on custom ROMs and enjoyed it.
This phone is only rooted and I deleted some of the bloat-ware from ATT and Moto.
I got a pop-up yesterday to update (67.21.125.en.US - 299MB). However when I downloaded it, and tried to install, it just rebooted, and said install failed. I wen't on Moto's website and downloaded a "fix" (55.13.26.en.US - 57MB) and put it on the SD card. It also failed. From the reading I've been doing, i've found its probably because of deleting the Moto/ATT bloat-ware.
I want ICS (Or Jelly Bean if its available?) but I've read some threads here that it can be a bad idea... I have been looking at some ROMs but I'm still a little nervous because of the locked bootloader.
Should I reflash stock GB and upgrade to OTA ICS or should I just bite the bullet and ROM it with an ICS ROM? (If ICS ROM, which one do you recommend?)
S2005x said:
I have a rooted A2 (AT&T Branded RUNNING on Straight Talk)
Baseband Version LUD_EDISON_R1D7_PATCH_36_111116_2336
Webtop Version WT-1.3.0-176
Kernel Version 2.6.35.7-g98a0a06 [email protected]#1
Build Number 5.5.1-175_EDMR1.25
So, I got this phone a long time ago after breaking (physical damage) my old Samsung Infuse. I had the Infuse (and a Captivate before that) on custom ROMs and enjoyed it.
This phone is only rooted and I deleted some of the bloat-ware from ATT and Moto.
I got a pop-up yesterday to update (299MB). However when I downloaded it, and tried to install, it just rebooted, and said install failed. I wen't on Moto's website and downloaded a "fix" (55.13.26.en.US - 57MB) and put it on the SD card. It also failed. From the reading I've been doing, i've found its probably because of deleting the Moto/ATT bloat-ware.
I want ICS (Or Jelly Bean if its available?) but I've read some threads here that it can be a bad idea... I have been looking at some ROMs but I'm still a little nervous because of the locked bootloader.
Should I reflash stock GB and upgrade to OTA ICS or should I just bite the bullet and ROM it with an ICS ROM? (If ICS ROM, which one do you recommend?)
Click to expand...
Click to collapse
You have to be on ICS to flash ICS or Jelly Bean ROMs. You either have the option of flashing back to stock gingerbread and applying the leak if you want to return to gingerbread at some point, or you can ota and be stuck on ICS permanently.
Sent from my MB865 using xda premium
Scottyfer said:
You have to be on ICS to flash ICS or Jelly Bean ROMs. You either have the option of flashing back to stock gingerbread and applying the leak if you want to return to gingerbread at some point, or you can ota and be stuck on ICS permanently.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Thank you very much for the reply!
So no matter what, I have to reflash back to GB. I gotta go find out how to do that now... : \
Is this the HOW TO guild for the leak you'd recommend I use to get to ICS?
Found this in the Noob Thread. However, the 2 links to the FXZ files are no longer available/broken links...
*Ninja Edit* Found this thread, downloading now to try it out.
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
Here is the Motorola Driver site
http://www.motorola.com/consumers/v/...D&pubid=987654
2) Download RSD Lite & install on your PC.
Here is the latest version to download (RSD Lite 5.6)
http://forum.xda-developers.com/atta...7&d=1321414457
3) Choose the FXZ file to download
Android 2.3.5 ---- Blur_Version.55.11.16.MB865.ATT.en.US
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip
4) Make sure you alternatively boot into AP Fastboot mode by powering down (or pulling battery), then press and hold the volume up and down button while powering on.
5) Plug your phone into a back USB port on your computer.
Front USB ports are often unreliable when it comes to power levels. They should not be used for flashing.
6)Run “RSD Lite” on your computer
7)Press the “. . .” button next to the box labeled “Filename”
8)Browse and open the FXZ file or just just drag the FXZ file onto the file path bar in RSD Lite
9)Wait for the program to read the file, then choose “START”
10) Now, the device will slowly flash the FXZ file. BE PATIENT AS THIS MAY TAKE A WHILE!
11) Congratulations! You’ve restored your ATRIX 2!!
S2005x said:
Thank you very much for the reply!
So no matter what, I have to reflash back to GB. I gotta go find out how to do that now... : \
Is this the HOW TO guild for the leak you'd recommend I use to get to ICS?
Click to expand...
Click to collapse
That's the correct ICS leak.
The fxz script is much easier to use, just don't use it after you've upgraded. You WILL end up with a hard brick. There's a different fxz here: http://forum.xda-developers.com/showthread.php?t=1805975
Sent from my MB865 using xda premium
Scottyfer said:
That's the correct ICS leak.
The fxz script is much easier to use, just don't use it after you've upgraded. You WILL end up with a hard brick. There's a different fxz here: http://forum.xda-developers.com/showthread.php?t=1805975
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Cool. Downloading now. Thanks again for your help Scott!
Scottyfer said:
That's the correct ICS leak.
The fxz script is much easier to use, just don't use it after you've upgraded. You WILL end up with a hard brick. There's a different fxz here: http://forum.xda-developers.com/showthread.php?t=1805975
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
That FXZ script is from ICS back to 2.3.5... I'm not on ICS yet...
I need one that gets me from 2.3.6 to 2.3.5...
Updating to ICS now
Already picked a ROM, and as soon as this finishes, gonna install that too
S2005x said:
That FXZ script is from ICS back to 2.3.5... I'm not on ICS yet...
I need one that gets me from 2.3.6 to 2.3.5...
Click to expand...
Click to collapse
Here you can grab the GB to GB 2.3.6 fxz.
Sent from my MB865 running a beastly CM10
Awesome.
Thanks guys!!! Got it working.
Running this ROM because its really close to stock, and it reminds me of my Nexus 7. Now I just gotta play with it, and set up my apps/widgets etc.
I really appreciate the help directing me to threads etc
I have installed the 4.2.2 CM 10.1 ROM on my Atrix 2 and need to return it to stock 4.04, I bought an S4
I can't for the life of me find anything concrete about flashing back to stock on the Atrix 2. A bunch of mumbo jumbo about "fxz" and "rsd" and "sbf"
Can someone please clear the air so I can get this phone safely back to stock??
EDIT: All I found is this video. . .
Read this:
http://forum.xda-developers.com/showthread.php?t=1396650
Use this:
http://forum.xda-developers.com/showthread.php?t=1961310
You do not need to patch the fxz, just load it into RSD and go. Just read the first link, it has all the need to know about flashing an fxz in it.
I Keep getting a Flash failure on MBM, MBMLOADER, lbl or System. After trying to revert back to Stock 4.0.4
Biom4st3r said:
I Keep getting a Flash failure on MBM, MBMLOADER, lbl or System. After trying to revert back to Stock 4.0.4
Click to expand...
Click to collapse
Darn, the same thing happened to me 2 days ago, a flash failure that is. If you're able to get into ap fastboot still then you can try again to achieve a successful flash. That's how you generally overcome flash failures which worked for me.
Sent from the Ace's MB865 using xda app-developers app
Biom4st3r said:
I Keep getting a Flash failure on MBM, MBMLOADER, lbl or System. After trying to revert back to Stock 4.0.4
Click to expand...
Click to collapse
That almost definitely means you are using the wrong files. make sure you have the proper ones for your version of the A2. it must be the ICS one too, no way to get to GB if it is an ATT phone.
Problem is fixed. This issue was the battery was dying I had to MAcGyver style charge my battery
Biom4st3r said:
Problem is fixed. This issue was the battery was dying I had to MAcGyver style charge my battery
Click to expand...
Click to collapse
Yup, that's a classic! Glad it all works, and inn the future, never start something that could brick you without a full battery. This has screwed us all at some point.
Haha i will keep that in mind. Thanks