So I'm on cm7, and noticed that my build is 4.5.1 198_6 instead of 198_7. If I'm not going to be running a stock ROM anytime soon, is there a reason to sbf to 198_7? I have the latest radio according to Lokifish's Photon Compendium.
If I should update, what's the safest way to do so? My partitions are updated to ext4 I believe, and I get the debug screen instead of the red Motorola label.
Sent from my MB855 using Tapatalk
CharFalco said:
So I'm on cm7, and noticed that my build is 4.5.1 198_6 instead of 198_7. If I'm not going to be running a stock ROM anytime soon, is there a reason to sbf to 198_7? I have the latest radio according to Lokifish's Photon Compendium.
If I should update, what's the safest way to do so? My partitions are updated to ext4 I believe, and I get the debug screen instead of the red Motorola label.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
I dunno, what were you on prior to CM7 and did you make a backup of that? Then you could restore back to that and SBF if you want...I dunno, but that seems reasonable to me.
So I watched QBking's video on upgrading your photon system version - and he says NOT to SBF if you have an unlocked bootloader. If I'm -not- on a stock rom, and don't plan to be, and have the latest PRL, webtop, and radio version (198_6), do I need to bother updating at all?
If I -should- upgrade, what should I do? Will I need to relock, SBF to 197_6, then unlock again?
CharFalco said:
So I watched QBking's video on upgrading your photon system version - and he says NOT to SBF if you have an unlocked bootloader. If I'm -not- on a stock rom, and don't plan to be, and have the latest PRL, webtop, and radio version (198_6), do I need to bother updating at all?
If I -should- upgrade, what should I do? Will I need to relock, SBF to 197_6, then unlock again?
Click to expand...
Click to collapse
I think might have mis read your original post there. If you don't plan on going back to stock at all, forget it about it updating the phone, once you flash that custom ROM it'll mess with all that stuff. so enjoy cm7! I remember with the constant updates back in September, I was on Alien Rom and had to flash back to stock to receive updates, but once that went through, couldn't go back to Alien ROM because it was based off of old builds.
Well in that case, I'll leave well enough alone for now.
Just to satisfy my curiosity though, if I -did- want to go from CM7, 198_6 to SkinnyJoker (198_7), what would I need to do?
Can I just flash Skinny? Is there something more complicated I need to do?
CharFalco said:
Well in that case, I'll leave well enough alone for now.
Just to satisfy my curiosity though, if I -did- want to go from CM7, 198_6 to SkinnyJoker (198_7), what would I need to do?
Can I just flash Skinny? Is there something more complicated I need to do?
Click to expand...
Click to collapse
Skinny roms are great...if you want to go back..
- charge your phone all the way
- back up apps with Ti
- nandroid back up
- wipe data/factory reset
- wipe cache for good measure
- reboot into rsd
- flash 154-5 sbf
- flash 198-7 sbf
- flash derpunlock.sbf
- moto-fastboot install cwm
- reboot into cwm
- wipe caches
- flash skinny rom
- reboot
- reboot
- root and get superuser
- get ti and restore apps only
- calibrate battery
- enjoy and take a breather
Sent from my MB855 using xda premium
This is the way I would do it to ensure a clean install...its a long process and I think you could essentially just factory reset/wipe data/cache and flash skinny but I like to start with a clean slate and do it properly to make sure everything is there.
Sent from my MB855 using xda premium
Thank you. I really appreciate your sharing that knowledge with me.
Related
Okay, so I see there are many people that have the same questions I had yesterday trying to apply this update with a custom ROM already on my phone. Here is what you'll need and how to get your phone updated. This isn't the only way to do it, but it's what I did and it was pretty easy. It was harder finding out how to do all of this, and in what order than actually doing the process.
It will take a little while to do this, roughly 30-45 minutes.
Here are the steps I had to use being on 1.5.7 with GingerBlur:
Here is what you'll need after backing up your apps/files to the SD Card, in this order:
Download RSD Lite 5.0
Download 1.8.3 sbf
Gingerbreak
GladEnable
Tenwar's System Recovery
GreyBlur 2.X (Or insert custom ROM here)
1: Flash the 1.8.3 update on to your phone using RSD Lite, this will reset your phone completely to stock.
2: Run GingerBreak to root the device.
3: At this point I was unable to install Tenwar's, so I used GladEnable to sideload it.
4: Installed Tenwar's and loaded up my custom ROM.
5: Restore your backup.
This should get you all updated and with your custom ROM installed.
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Thanks a lot for this....
spitefulcheerio said:
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Click to expand...
Click to collapse
Yes, use Titanium Backup to backup your User Apps and Data, not the system apps or data. And make sure to backup to your SD Card as the flash with wipe your internal memory and your backup will be lost. I had that issue and had to reinstall all of my apps. It's minor, but still a pain in the ass.
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
IrateCustomer said:
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
Click to expand...
Click to collapse
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Swiftks said:
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Click to expand...
Click to collapse
Maybe because I was on 1.5.7, and flashed 1.8.3 instead of going back and OTAing the phone. That would make sense because the OTA process probably does a backup/restore during the process. As mentioned in the OP, it's only one way to do it, but there are other options.
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Datblkbro said:
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Click to expand...
Click to collapse
I've updated the link in the OP so you can download the correct file. My apologies.
Regarding 1.8.3 sbf, which of the sfb files from the link you provided is it? They vary in size. Thanks.
You want the one with the most hits and the ridiculously long filename.
It actually has 1.8.3 buried in the name of the file. It's a few from the top.
THANK YOU this has been a big question mark for me ever since 1.83 came out. Fantastic guide.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
Did the GingerBlur 3.1 get fixed when it comes to the Webtop mod? Cuz I read something about it having a problem with actually working on this Rom? Maybe that was on the 3.0, so I figure 3.1 fixed it?
PLease just a simple "yes it works" or "No, it doesn't" will suffice
Thanks
Just wanted to post my initial experience with using RSDlite to update afterting and gingerblurring it.
I followed your how to as much as I could (You should provide a link to RSDlite instructions, I had to search for it because I didn't know how to do it exactly... not a big deal but it would make it easier/idiot proof)
When I first updated via RSDlite, something must hve went wrong. At first, A triangle and lil android was haunting me on my screen... so I went to reboot.. **** [I thought I bricked it]... Then I restarted it again... DOUBLE ****... Couldn't load into recovery... I restarted a third time and it loaded up(**** YES). But for some odd reason, it said I still had to update (even though it said the firmware was @ 1.8.3.)
Everything seemed to work fine, and was able too root and ginger blur it. About a few hours later, wifi seemed wonky (kept randomly disconnecting and the update dialog came up every 15 minutes).
I ended up reflashing to 1.2.8 and OTA's all the way up to 1.8.3 and then re-rooted and blurred it. No problems since the full refresh
Hopefully everybody elses experience goes better than mine!
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
winky! said:
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
Click to expand...
Click to collapse
You can use Uninstaller for Root (I found it on the Market), and you can uninstall from there if you wish. Personally I see no real reason to remove it, but you can if you need to with the above referenced Uninstaller. There are a few others that can do it, but UfR is free, which is clearly a win.
564mb for the sfb??? Thats freaking huge
GreyBlur on 1.8.3
After following the steps I still show
"System Version 4.1.57MB860.ATT.us"
rooted and sideloading enabled by gladroot then flashed greyblur 2.1....little help for the n00b?
So I rooted my phone about a month ago and didn't bother to do an OTA update. So I didn't think this one through all the way and I am not sure if I actually flashed 1.8.3 onto the phone.
When I look at the phone information the System Version says:
Version.4.1.83.MB860.ATT.en.US
GingerBlur appears to work just fine...how ever I can't reboot into clockwork recovery mode any more...
I've had good luck with my Captivate but this atrix is proving to be a challenge.
Is their any way that I can flash back and start over? Or am I **** out of luck on this one?
Just found an answer to my problem
http://forum.xda-developers.com/showthread.php?t=991072
I still am not understanding. So did you end up just reflashing? or did you figure a way to turn it off ( I am having the same issue, but can boot into recovery)
winky! said:
I still am not understanding. So did you end up just reflashing? or did you figure a way to turn it off ( I am having the same issue, but can boot into recovery)
Click to expand...
Click to collapse
Yea I just ended up reflashing all together. Backed up all of my pictures, contacts, etc... and then reflashed the phone to 1.2.6 and OTA updated all the way to 1.8.3
Now to root and flash to gingerblur
Alternatively, you can use TiBU to freeze "updater".
warmwaffles said:
Yea I just ended up reflashing all together. Backed up all of my pictures, contacts, etc... and then reflashed the phone to 1.2.6 and OTA updated all the way to 1.8.3
Now to root and flash to gingerblur
Click to expand...
Click to collapse
Why not just directly flash to 1.8.3? (Im an android n00b, so dont hate)
winky! said:
Why not just directly flash to 1.8.3? (Im an android n00b, so dont hate)
Click to expand...
Click to collapse
Because I didn't think about that and I figured it was safer to go all the way back.
Well, I ended up doing what you did and just flashed to 1.28 and OTA'd up and now it works fine. So you may have done the better thing anyways... its not like the OTA's take that long.
I'm sorry if somebody already posted that, i swear I had a look
I have a SIM unlocked AT&T MB860 Atrix with gingerblur 4.5, and I would like to try some real gingerbread goods, which means bootloader unlock and 2.3.4 HKTW.
Do I have to flash back to 1.8.3 stock sbf before actually unlocking and installing gingerbread? I heard people saying is not safe to flash sbf for SIM-Unlocked Atrix because it can cause Wi-Fi problems, is it still the case?
Second problem: I had my phone rooted, but now I don't have an external micro SD card, so I wouldn't be able to root with gingerbreak-similar methods, is this a deal breaker or there is another way to complete the process all the way through?
Thanks a lot
As a general rule, it's best to flash back to stock before flashing anything else. Because Gingerblur requires Tenfar's recovery to run, I believe this will be the best way to do this. If someone else could chime in about the SIM-unlock/wifi issue, that would be great.
As for the rooting method on 2.3.4 HKTW, it works by installing a ZIP through recovery. In my own experience, it only seems to read external SD cards. If you can make it read the internal somehow, then you should be able to root.
i was on GingerBlur 3.1 (rooted via GladRoot), and did the following over the weekend
- flashed the unlocker SBF (still on 1.8.3)
- flashed the new CWM onto the phone via fastboot
- flashed GingerBlur 4.5 using that CWM, just for a few days
- flashed the 2.3.4 IMG using the Windows x64 guide in the general forum.
ran into no problems, and the GB build was already rooted when it booted up.
dLo GSR said:
i was on GingerBlur 3.1 (rooted via GladRoot), and did the following over the weekend
- flashed the unlocker SBF (still on 1.8.3)
- flashed the new CWM onto the phone via fastboot
- flashed GingerBlur 4.5 using that CWM, just for a few days
- flashed the 2.3.4 IMG using the Windows x64 guide in the general forum.
ran into no problems, and the GB build was already rooted when it booted up.
Click to expand...
Click to collapse
Good to know, thanks!
Did you clear data or anything like that after flashing?
jwhited said:
Good to know, thanks!
Did you clear data or anything like that after flashing?
Click to expand...
Click to collapse
oh, right, forgot. i did do the fastboot -w beforehand.
i have simunlocked atrix as well, it makes no difference.
I went from Greyblur straight to GB with no issues.
Thanks guys
This is worth a try
If I wanted to return to the stock ROM after flashing 2.3.4, all I have to do is RSDLite flash 1.8.3 back correct and then restore using CWM?
kshiuan said:
If I wanted to return to the stock ROM after flashing 2.3.4, all I have to do is RSDLite flash 1.8.3 back correct and then restore using CWM?
Click to expand...
Click to collapse
I just did this tonight, and for some reason, I had some problems flashing the 1.8.3 SBF directly. So I downloaded the 1.2.6 (shipping) firmware and just did the updates.
I was trying about 10 days to install any 2.3.4 based rom on my AT&T atrix!
Everytime i trying to flash some rom (mostly i've tried Alien's and Cherry) i see bootloop: red circle with "M" >at&t logo >"M">"M">"M"... I have an unlocked bootloader, can see the sign "Unlocked" ot top of the screen, Rooted And CWM Recovery by tefnar installed, BUT EVERY TIME i flashing some rom i stucking on that bootloop. I was trying to search on xda a lot of time, still cannot find the answer. That makes me real sick of it, i'm not sleeping at nights, pleeeaseeee heeeelp!!!
How long are you waiting for your phone to boot. It can take a while. 10+ minutes.
I waited until yesterday to update to 2.3.4 because I was on call.
Things I did.
1) Made sure that I had the lastest CWM.
2) Made sure I had the latest pudding.
3) I installed 2.3.4 pudding first. Note: I had to re-install CWM after this. Not a huge deal since it installed from fast boot.
4) Followed the ROM install steps here
5) Installed the recommended radio.
6) After that it should work. I had to install the webtop and the ad block but have had no problems since.
I am now trying to decide what Kernel to mess with.
First install rom racers recovery. Two. Make sure youre wiping everything before and after you flash, unless youre upgrading the same rom, you dont have to but still recommended. Three, be patient on initial boot of a fresh flash. Sometimes it can take awhile and might reboot still.
I voided my warranty.
lemortede said:
How long are you waiting for your phone to boot. It can take a while. 10+ minutes.
I waited until yesterday to update to 2.3.4 because I was on call.
Things I did.
1) Made sure that I had the lastest CWM.
2) Made sure I had the latest pudding.
3) I installed 2.3.4 pudding first. Note: I had to re-install CWM after this. Not a huge deal since it installed from fast boot.
4) Followed the ROM install steps here
5) Installed the recommended radio.
6) After that it should work. I had to install the webtop and the ad block but have had no problems since.
I am now trying to decide what Kernel to mess with.
Click to expand...
Click to collapse
I was waiting approx. 5 minutes, but is that suppose to be like that? I mean flashing screen on a bootloop? Because fading screen, when reboot looks like if i take battery out everytime. Besides, i've installed any of gingerblur or greyblur easily, but when trying to install 2.3.4, see that crap again.
I'm using all latest (CWM, Divers, RSD...)
Are you wiping both the system cache and dalvik cache before you flash the rom?
Sent from my MB860 using XDA App
iRobby said:
Are you wiping both the system cache and dalvik cache before you flash the rom?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I Do. Maybe here some thing i've missed before. Now I have 4.1.83 on board, and can install any of 2.2.x, but NOT 2.3.4 Why?
Is the OTA update only wayout??
thread still actual. UP
I'm relatively new to the rooting community, but I think I'm doing pretty good. I have my DX2 running Eclipse 2.0.1 and am about to install Speedy v7. I am supposed to flash the .zip using BSR, which is no problem. My question is, what all does flashing involve? Should I automatically know to wipe cache when flashing? Just curious
Another questions while I'm here. I'm running Eclipse 2.0.1, let's say I wanted to try out another rom (such as Liberty), do I just flash (like above) the new rom? Or do I have to do something special for flashing roms as opposed to mod scripts (such as speedy v7)? And if I nandroid Eclipse before flashing a new rom, can I easily restore my nandroid?
Big big big thanks!
"Flashing" is just a term that means to overwrite something to make changes. Thats as much as I can tell you about that. lol
If you are wanting to flash other ROMs over your eclipse rom, you need to be on the same kernel. Since you are using Eclipse 2.0.1, I think its safe to say you are running Android 2.3.5. If you have another ROM that is built off of Android 2.3.5 then you should be safe to wipe cache, dalvik cache and flash right over it. Some might require you to do a factory reset but its not always necessary. But if you want to use a ROM based off of 2.3.4, like I think Liberty is (I'm not sure if its been updated), then you have to first be on stock 2.3.4. Which means going through the process of downgrading your OS first.
And about wiping cache and all, I would say just do it before flashing anything. It doesnt hurt and doesnt take long. Before you use any scripts though, make sure it has been updated for 2.3.5 ROMs. Otherwise you will get a bootloop and be stuck.
I hope that sheds some light on your question and didnt confuse you more. lol
No that definitely clears some things up for me, thanks
As far as downgrading the OS. Does that require the RSD/SBF process? If so, I'm familiar with that.
wesf90 said:
No that definitely clears some things up for me, thanks
As far as downgrading the OS. Does that require the RSD/SBF process? If so, I'm familiar with that.
Click to expand...
Click to collapse
Yes. Thats all you need. Just use the right SBF file. Ive been told you can SBF to a lower Android OS but I havent done it yet.
jsgraphicart said:
Yes. Thats all you need. Just use the right SBF file. Ive been told you can SBF to a lower Android OS but I havent done it yet.
Click to expand...
Click to collapse
You can SBF to the original 2.2 froyo the X2 had and either stay there or ride the two OTA updates back to 2.3.4
Thanks to both of you. I feel pretty confident now. Hopefully this topic will help someone else along the way with the same questions
wesf90 said:
Thanks to both of you. I feel pretty confident now. Hopefully this topic will help someone else along the way with the same questions
Click to expand...
Click to collapse
No problem. Hey since its solved put (Solved) in the OP subject line in front of the orginial subject so people will know
Good call. Done
jsgraphicart said:
"Flashing" is just a term that means to overwrite something to make changes. Thats as much as I can tell you about that. lol
If you are wanting to flash other ROMs over your eclipse rom, you need to be on the same kernel. Since you are using Eclipse 2.0.1, I think its safe to say you are running Android 2.3.5. If you have another ROM that is built off of Android 2.3.5 then you should be safe to wipe cache, dalvik cache and flash right over it. Some might require you to do a factory reset but its not always necessary. But if you want to use a ROM based off of 2.3.4, like I think Liberty is (I'm not sure if its been updated), then you have to first be on stock 2.3.4. Which means going through the process of downgrading your OS first.
And about wiping cache and all, I would say just do it before flashing anything. It doesnt hurt and doesnt take long. Before you use any scripts though, make sure it has been updated for 2.3.5 ROMs. Otherwise you will get a bootloop and be stuck.
I
I hope that sheds some light on your question and didnt confuse you more. lol
Click to expand...
Click to collapse
In reference to your comment about bootloop.
If u make a nandroid before flashing something (and u don't wipe data before rebooting) and you get stuck in boutloop,
Just pull battery and plug in.
BSR will come up an you can restore your nandroid and will be up and running again no problem.