I have been on the leaked 2.2 since it came out in the summer. I want to try and get on Fission but am a little perplexed on what would be the safest way to do so. Here is what I am on right now
System Version - 2.3.9
Android Version - 2.2
Baseband - 1.09.06
Kernel Version - 2.6.32.9
Bootloader - 30.01
So what I was going to try and do was to SBF to 2.3.15, then SBF to 2.3.320 then finally use the update.zips here to upgrade to the latest everything THEN finally get to Fission. How does that sound to everyone? Then once on Fission I can start the Fission Dynamite theme.
You should be able to go from 2.3.15 to the most recent just by hitting update on your phone. Altentatively go here
I would just skip the 2.3.32 sbf and force the OTA once you get to 2.3.15
Just use Bootstrap and ROM Manager. That is definitely the easiest way to install
ROMs.
It's pretty much as easy as this:
Flash into Clockwork Recovery, wiped data, install .zip from sd and you're done.
Before I tackle this upgrade I was wondering if there was a way to get back to my froyo via SBF then root then clockwork restore. Or will it brick it?
You can go back to 2.2. Just
1. sbf back to .340
2. You will bootloop, boot into stock recovery and wipe data/cache.
3. Boot into 2.2 and root.
4. Install bootstrap.
5. Restore backup/install new rom.
Sent from my DROIDX using Tapatalk
i sbf back to 2.3.340 adn i cant go in to recovery to make a data factory reset i hit sear and the recovery menu wont apear.please help
That shouldn't happen. Did you use the _full_ sbf and not the system only? Do you have the correct Motorola drivers? Have you sbf'd before using the same computer/phone?
Sent from my DROIDX using Tapatalk
vladimirtm said:
i sbf back to 2.3.340 adn i cant go in to recovery to make a data factory reset i hit sear and the recovery menu wont apear.please help
Click to expand...
Click to collapse
You have to press both volume and up button when you see the exclamation point not the search button
i did factory reset but im still stuck in moto logo
That's for the new recovery, the old recovery required you to press the search button. It sounds like the sbf didn't complete properly.
Sent from my DROIDX using Tapatalk
Did you have to press the volume up and down buttons to get into recovery? If so, you're still on the new recovery and you'll need to sbf to get back to the old one.
Sent from my DROIDX using Tapatalk
Make for certain you are using the full 2.3.340 SBF file located here
http://www.mydroidworld.com/forums/droid-x-discussion/6367-new-full-sbf-droid-x-2-3-340-a.html
Otherwise it will not boot. You can tell if you have the red M logo you still have the leaked GB bits. If you use the system only SBF file it will not work. If the full 2.3.340 SBF file worked, you will have a white M logo when you power on the phone.
This thread does not belong in Development, Moved to General. Development Questions are not Development Forum Material. Development Sections are for Development Project Threads only.
Thank you have a Nice Day.
problems getting back to froyo
I am hitting problems sbfing back to froyo 340 from gingerbread. My drivers are installed and rsdlite 4.9 is recognizing the droid x perfectly fine as well. The sbf process starts fine, but fails due to a group 31 checksum error.
ERROR: Flash failure: Interface AP-OS: Error verifying Code Group 31 checksums. File: 0x56E0, Phone: 0xB9A8 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
The strange part is that now when i reboot, it always goes back to the way my phone was before i attempted to flash it. Any apps I install just get installed. Icons that were moved get put back.
Any suggestions?
Hello everyone I was hoping I could get some help with my ATT Atrix 4G, as of right now I have my Atrix running 1.5.7 and rooted. For some reason about a week ago my Wifi just stopped working and says error. So I did a little looking around and didnt see a fix besides flashing the phone so I thought I might as well update to the latest and greatest. Now I did my phone so long ago that I have Tenfar's CWM recovery for Motorola Atrix 4G on it. I would like to flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf but Im not sure the steps I need to take. Over all this is what I would like to do.
Number 1. Put CWM Recovery Mod for Atrix 4G and take off Tenfar's CWM
Number 2. Unlock the phone Pudding
Number 3. Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
Number 4. Get wireless tether working.
One thing I don't fully understand is do you need to unlock the phone using pudding before you flash Full 2.3.4 with preinstall root and pudding bootloader unlock or can you just flash and have it unlocked?
So what I really need to know is the order of everything, CWM Recovery Mod for Atrix says you need to be unlocked to use it. So do I need to unlock the phone like in number 2 to before I do number 1 and 3 or can I flash number three and the will unlock the phone? Then do Number 1 and skip number 2 altogether? And as far as number 4 goes if some one could point me in the right direction for working wifi tether on 2.3.4 ATT that would be great.
One other thing I was wondering is it safe to flash for 1.5.7 to 2.3.4 or should I flash to 1.8.3 and then to 2.3.4?
Thanks so much and any and all help is greatly appreciated
Jay
1. You need too unlock first
http://forum.xda-developers.com/showthread.php?p=16018910#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/showthread.php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/showthread.php?t=1186537
or
http://forum.xda-developers.com/showthread.php?t=1160649 from Nav.
Both good roms.
Thanks JayRolla but do I need to flash to Full 2.3.4 with preinstall root and pudding bootloader unlock before I install the 2.3.4 roms you linked to up there?
Jay Dogg said:
Thanks JayRolla but do I need to flash to Full 2.3.4 with preinstall root and pudding bootloader unlock before I install the 2.3.4 roms you linked to up there?
Click to expand...
Click to collapse
As far as I understand, at the moment you are on 1.8.3.
In that case the very first thing you should do is flash pudding (BL unlock sbf).
After that install CWM and do a full backup.
When you have that you can install whichever room you want (don't sbf back to 1.8.3 tho - hard brick), you can install stock 2.3.4 via CWM and root it afterwords manually if you want. It's all a matter of which rom you prefer. Hell, you can try them all as CWM makes it all really easy.
Pudding needs to be flashed only at step 1 and it stays with your forever as long as you dont' SBF. Which you really don't need to do since we have CWM and fastboot.
Have a quick question, what is the difference between the automatic unlock script and the SBF that unlocks and roots via preinstall?
I am on stock 4.5.91 OTA with no modifications at all. Which method should I use? Which is safest/easiest.
I am on win7 64 bit with latest moto drivers installed.
dcarpenter85 said:
Have a quick question, what is the difference between the automatic unlock script and the SBF that unlocks and roots via preinstall?
I am on stock 4.5.91 OTA with no modifications at all. Which method should I use? Which is safest/easiest.
I am on win7 64 bit with latest moto drivers installed.
Click to expand...
Click to collapse
Automatic script is supposed to automate (duh ) some of the unlocking steps for you, but I personally wouldn't recommend it. It failed for me and for many other people too if you read their thread.
With the manual pudding unlock - you can't screw up if you follow all of the steps precisely. But you do have to do all the steps manually, which is a good learning process if you ask me.
If you are on 4.5.91, after flashing pudding and doing the fastboot unlock commands you will get failed to boot error. This is normal and all you have to do is repeat the fastboot commands for the second time and all will be fine.
Do not under the fear of death SBF back to 1.8.3 or you will brick your phone.
Here is the link to the pudding SBF -
http://forum.xda-developers.com/showthread.php?t=1136261
Here are the specific steps laid out in a very straightforward way -
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Just make sure you install the drivers before doing them. For example, you can download Windows 7 x64 drivers here -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
xploited said:
Automatic script is supposed to automate (duh ) some of the unlocking steps for you, but I personally wouldn't recommend it. It failed for me and for many other people too if you read their thread.
With the manual pudding unlock - you can't screw up if you follow all of the steps precisely.
Here are the specific steps laid out in a very straightforward way -
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Just make sure you install the drivers before doing them. For example, you can download Windows 7 x64 drivers here -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
Click to expand...
Click to collapse
Thanks for the info
One last question, should I use the small (10mb) pudding sbf or the full SBF that does unlock + root all in one?
dcarpenter85 said:
Thanks for the info
One last question, should I use the small (10mb) pudding sbf or the full SBF that does unlock + root all in one?
Click to expand...
Click to collapse
I would recommend using the smaller pudding sbf, since that's what I used. But from what I read, both SBFs work without problems.
You can root manually afterwords. It's very easy.
xploited said:
As far as I understand, at the moment you are on 1.8.3.
Click to expand...
Click to collapse
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?
Jay Dogg said:
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?
Click to expand...
Click to collapse
Nope. The process slightlt differs between 2.3.4 and prior.
But besides that you can unlock 1.5.7 just fine.
Jay Dogg said:
Im on 1.5.7 rooted right now, not sure if that makes any kind of difference, do I need to be on 1.8.3 or higher before I do pudding?
Click to expand...
Click to collapse
No you don't need to be on 1.83 but for easy I would recommend also if it helps these are the steps I took.
1. Unlock bootloader using auto script http://forum.xda-developers.com/showthread.php?t=1182871 (I was running 1.83) (**I did have an issue after doing this where it wiped my phone and wouldn't let me go past the MOTOBLUR login so I just flashed back down to 1.26 OTA back to 1.83 then reran the script just to make sure I was still unlocked now I only read about that happening to one other person on their forum so chances are slim of it happening**)
2. Using RSD (the latest one 5.x.x) I flashed the 2.34 sbf that comes prerooted/unlocked although the root doesn't actually work then you have to follow the preinstall root method they describe on that same post for the sbf.
I never installed CWM but I would suggest doing that one last
**Edit: yes I did forget to mention my circumstance where I flashed back to 1.26 was Im sure pure luck that I did not hard brick my phone. This is not recommended. Why my phone did not brick is still unknown.
From unlocked/rooted GB Atrix
I'm on 1.8.3, unlocked, rooted, with Gingerblur and webtop hacks (web2sd, without dock, full ubuntu).
So I'm confused as to why I cant just flash ATT-2.3.4_Pudding_preroot.sbf, it has 2.3.4/2.5.91, unlocked, root preinstalled.
Would this not give me unlocked 2.3.4 with root ready to set-up? Would I have to "clean" it or is that just optional?
People are saying to install pudding using the automatic script first, but then why create the above sbf file?
What about the 1.8.3, unlocked, root preinstall sbf file?
So if I cant use the unlocked 2.3.4 sbf file, I would first flash pudding on my phone then which 2.3.4/4.5.91 sbf file would I flash with since the OTA update won't work due to mods, and because I didnt think we should use OTA.
I want to do the method that will prevent any bricking, but I also dont want to waste time or do unnecessary flashing.
BE CAREFULLY .... IT SEEM HE/SHE WAS LUCKY WHEN HE/SHE FLASH BACK TO 1.26... IF YOU RUN THE SCRIPT AND PASS STEP 3 YOU HAVE PUDDING SO IF YOU FLASH BACK TO 1.26 YOU WILL END WITH A HARD BRICK... IT IS WELL DETAILED IN THE SCRIPT ONCE YOU HAVE PUDDING YOU CAN NOT RSD ANY DOWNGRADE VERSION OF MOTO SBF FOR EX 1.26 1.57 OR 1.83
drock212 said:
No you don't need to be on 1.83 but for easy I would recommend also if it helps these are the steps I took.
1. Unlock bootloader using auto script http://forum.xda-developers.com/showthread.php?t=1182871 (I was running 1.83) (**I did have an issue after doing this where it wiped my phone and wouldn't let me go past the MOTOBLUR login so I just flashed back down to 1.26 OTA back to 1.83 then reran the script just to make sure I was still unlocked now I only read about that happening to one other person on their forum so chances are slim of it happening**)
2. Using RSD (the latest one 5.x.x) I flashed the 2.34 sbf that comes prerooted/unlocked although the root doesn't actually work then you have to follow the preinstall root method they describe on that same post for the sbf.
I never installed CWM but I would suggest doing that one last
From unlocked/rooted GB Atrix
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
I flashed the full SBF of 2.3.4 with pudding and preroot already installed and I was left with a 0x1000 error which i was able to fix by simply rebooting into fastboot mode and then running 'fastboot oem unlock'. I was really scared when I saw the error but I was able to fix it. Just an fyi for anyone else that might run into that problem.
A few weeks ago when the bootloader was unlocked, and hktw craze began I was happily running GB, a couple days into it my phone started acting crazy, would constantly act if someone was touching it, and I noticed a very small portion of the touch screen quit responding, this happened out of no where, I took the phone back to at&t and they shipped a new one to me.
Now that has nothing to do with your phone but what I am trying to say is that if hardware on your phone randomly quit working more than likely having nothing to do with mods you've done to it.. take it back, get a new one, if you can.
Goodluck
Sent from my MB860 using XDA Premium App
dcarpenter85 said:
I flashed the full SBF of 2.3.4 with pudding and preroot already installed and I was left with a 0x1000 error which i was able to fix by simply rebooting into fastboot mode and then running 'fastboot oem unlock'. I was really scared when I saw the error but I was able to fix it. Just an fyi for anyone else that might run into that problem.
Click to expand...
Click to collapse
This is a known issue and you resolved it correctly by redoing fastboot commands.
Many other people weren't so luck (didn't read instructions) and opted for an SBF back, causing them to hardbrick.
Now just so make sure before I do this, should I take path a or b
PATH A
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
PATH B
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3 .Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
4. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
Jay Dogg said:
Now just so make sure before I do this, should I take path a or b
PATH A
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
PATH B
1. You need too unlock first
http://forum.xda-developers.com/show...0#post16018910
2. You need to install Tenfars (not rom managers) CWM recovery for atrix unlocked.
http://forum.xda-developers.com/show....php?t=1138541
3 .Flash to Flashable SBF: Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf
4. Install whatever ROM you feel you will like. I recommend Kenns ROMS
http://forum.xda-developers.com/show....php?t=1186537
or
http://forum.xda-developers.com/show....php?t=1160649 from Nav.
Click to expand...
Click to collapse
Path A. After flashing pudding i would avoid SBFs entirely, unless there's no other way. Any rom can be flashed via fastboot or CWM, so use that as it's much safer.
Hi guys, I was on my girlfriend's DROID x which was running liberty v3 then switched to simply Stunning 2.2.
After this, I tried to flash an sbf for stock. 605 in CWM and it froze during installation. Now it only boots to the red M and stays there. Is there anyway I can flash back to stock or just get this booting again?
Thanks in advance and I will click thanks on helpful posts when I get to a pc
Sent from my SGH-I897 using XDA
Try booting into recovery by holding down the home button while powering on. If you get in do a factory reset and reboot and you shoud be good. If you can't get into recovery then you need to sbf by either Linux boot disc or rsd.
You're definitely going to have to SBF.
Use the 1kds Linux live CD to SBF to .602.
Note: be sure not to take any OTA updates.
Sent from my DROIDX using Tapatalk
You tried to flash an sbf in CWM?! I hope you didn't actually try that.... Sure sbf files often come in a zip package but the way to use an sbf is not to install via CWM.
1) unzip the file to get the raw .sbf file.
2) install and open rsd lite
3) hook up phone to computer and make sure it's recognized by rsd lite
4) choose phone in rsd lite and then browse to find three sbf file
5) flash the sbf file and let it do its thing (it'll tell you when it's done)
This is a very rough step by step. I HIGHLY recommend you find a comprehensive guide for flashing an sbf specially for the Droid X. Things I haven't addressed are stuff like which sbf you should be using, installing drivers so your computer recognizes the Droid x, etc
You can find the required drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my Transformer TF101 using Tapatalk
Slap Yourself
First time flashing a rom so I know i've got something out of order in the process.
ATTEMPTED:
I attempted ROM manager and it kept saying that I needed to install Clockworkmod recovery and I never could really get it working.
ENDED UP DOING:
Phone is rooted and unlocked for non-market apps with Superoneclick.
Installed 2init to flash [JB] CM10 Jellybean 4.1.1 from the Quartz build (http://forum.xda-developers.com/showthread.php?t=1779324)
No problem here. Got it up and running and gapps installed.(from http://goo.im/gapps used gapps-jb-20121130-signed.zip)
When I tried installing the sbf file with RSD Lite (v5.7), I hit the red Moto logo bootloop and had to do the stock recovery.
I am wondering how to avoid this bootloop when I install the SBF file (p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf) can't remember which site I downloaded it from. I've tried this 4 times. Any suggestions?
Btw, what is included in the SBF file? I assume it has the moto and att apps. I'm just looking for the att phonebook and the motoblur for backup.
I've looked around the forum a lot so please forgive me if I am asking about something already posted. It just wasnt clear for me.
Thanks for the help.
NickKG81 said:
First time flashing a rom so I know i've got something out of order in the process.
ATTEMPTED:
I attempted ROM manager and it kept saying that I needed to install Clockworkmod recovery and I never could really get it working.
ENDED UP DOING:
Phone is rooted and unlocked for non-market apps with Superoneclick.
Installed 2init to flash [JB] CM10 Jellybean 4.1.1 from the Quartz build (http://forum.xda-developers.com/showthread.php?t=1779324)
No problem here. Got it up and running and gapps installed.(from http://goo.im/gapps used gapps-jb-20121130-signed.zip)
When I tried installing the sbf file with RSD Lite (v5.7), I hit the red Moto logo bootloop and had to do the stock recovery.
I am wondering how to avoid this bootloop when I install the SBF file (p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf) can't remember which site I downloaded it from. I've tried this 4 times. Any suggestions?
Btw, what is included in the SBF file? I assume it has the moto and att apps. I'm just looking for the att phonebook and the motoblur for backup.
I've looked around the forum a lot so please forgive me if I am asking about something already posted. It just wasnt clear for me.
Thanks for the help.
Click to expand...
Click to collapse
The SBF has factory/stock MotoBlur with the at&t bloatware included. You can't use MotoBlur with cyanogenmod that I know of. You might be able to use the at&t address book though.
You need to reboot into recovery after installing 2init. You do that by pressing volume down when the blue led light comes on at the red logo.
Then you can install cm10 and gapps.
Try sbf in linux if all else fails, skeevy420 posted a great tut on how to do it, or just look up "flash sbf linux" in google and you'll find a guide from somewhere. Sounds like you just need to start from scratch, in which case you have to flash sbf first.
Sent from my MB520 using xda app-developers app