Just went through the entire 4 hour long process of SBFing to 2.3.3, doing the 2.3.4 OTA, rooting, updating to custom rom, then restoring all my sms/mms etc etc but not system data. I just flipped through the apps and noticed the new icons.
Its smooth as butter except (Edit: It Was... now its laggier then 2.2.2 stock), I just went into About Phone to see If I turned off the upgrader 2.3.4. Their I noticed It said I was still on 2.3.3.
As you can see the kernel is 2.3.4, the build is 2.3.3 and it's telling me to upgrade to 2.3.4. All my system apps says 2.3.4, and I'm on a custom rom (Moto-Ginger-Funk). I doubt I'd be able to install that with no errors if I wasn't. So would just like to ask, what the hell is going on here? I have no problems, a couple force closes after first restore of stuff but a reboot fixed that.
Had to Flash some stuff to the phone and just went into About Phone again and now it says 2.3.4 . Looks like I found another bug, even if it's not that big but it is weird.
It might have just been reading from old data and finally caught up. I am assuming this was after initial startup?
i think you might be using a kernel and system from seperate levels of gingerbread. like one is on 2.3.3 and one form 2.3.4. remember we cant really use a custom rom due to no unlocked bootloader so the rom your using could have system files from both.
AtLemacks said:
It might have just been reading from old data and finally caught up. I am assuming this was after initial startup?
Click to expand...
Click to collapse
No this was after rebooting about 4 times adding stuff into recovery.
^I kinda hope not since everything now says 2.3.4.
You know when I did the sbf it only took 15-20mins and I still had everything that I had when I was on eclipse 0.2.2 except for root. It had all my settings and txt messages. The only thing I had to do was root and *228. I thought sbf was supposed to get rid of everything.
Sent from my DROID X2 using XDA App
(aq) said:
i think you might be using a kernel and system from seperate levels of gingerbread. like one is on 2.3.3 and one form 2.3.4. remember we cant really use a custom rom due to no unlocked bootloader so the rom your using could have system files from both.
Click to expand...
Click to collapse
What? Dude, we have custom roms, just not custom kernels. We have root, we have everything except an unlocked BL. He didn't flash the 2.3.4 rom based on the 2.3.3 kernel, he took the OTA update. You are not very savvy in this are you?
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
densetsu86 said:
You know when I did the sbf it only took 15-20mins and I still had everything that I had when I was on eclipse 0.2.2 except for root. It had all my settings and txt messages. The only thing I had to do was root and *228. I thought sbf was supposed to get rid of everything.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
You still need to do a full data/system wipe if you plan on going back to complete stock. This is why a lot of people get stuck in boot loops because they don't wipe cache/davlik, or do a full wipe.
I did the sbf a couple of days ago and I had no problems. Hell my phone is running the best it has ever have. I used to hate this phone but after 2.3.4 I love it.
Sent from my DROID X2 using XDA App
Yea re-did it this time SBF not OTA and its running great. Before it was awful.
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 thinking about SBFing my rooted x2 back to 2.3.3 from 2.3.4 because of the terrible battery indicator, and was just wondering if I would be able to update straight to 2.3.5 (or possibly ICS) when the update comes. I don't know why this wouldn't be possible, but I just wanted to make sure before I actually SBFed the phone.
I also was wondering if my phone would still be rooted after the SBF because of the maintain-root-through-any-update mod. Any thoughts?
On a different note, if I had the x2 bootstrap, the maintain-root-through-any-update mod, and MyBackup Root, could I just backup all my apps and the system (using MyBackup Root and the bootstrap, respectively), SBF, then restore the phone by downloading the bootstrap and MyBackup Root and restoring my apps/system? Would this get my back to where I was before, or would I have to manually download each one of my apps and lose all previous data that I had on them? I'm just wondering what's the easiest way to restore my phone back to the layout that I had before I SBFed.
Thanks for your answers to any of these 3 questions!!! I definitely appreciate it.
germmeetsworld said:
I'm thinking about SBFing my rooted x2 back to 2.3.3 from 2.3.4 because of the terrible battery indicator, and was just wondering if I would be able to update straight to 2.3.5 (or possibly ICS) when the update comes. I don't know why this wouldn't be possible, but I just wanted to make sure before I actually SBFed the phone.
Click to expand...
Click to collapse
Perhaps someone elses experience proves different however, I kept 2.2.2 on my DX2 for quite some time because of similar reasons. When I decided to take the plunge from 2.2.2 and upgraded to 2.3.4 OTA, my phone needed to first upgrade to 2.3.3 before it would upgrade to 2.3.4. Thus, I had to perform two separate OTA updates.
If you're going to SBF you can SBF directly from your current version to the desired version.
germmeetsworld said:
I also was wondering if my phone would still be rooted after the SBF because of the maintain-root-through-any-update mod. Any thoughts?
Click to expand...
Click to collapse
To be honest, I'm not sure. I personally prefer to SBF to a clean DX2, wiping all settings and cache. To me I treat it like formatting my computer with a clean install of it's OS.
Perhaps someone else will have more insight with the maintain root through updates mod.
germmeetsworld said:
On a different note, if I had the x2 bootstrap, the maintain-root-through-any-update mod, and MyBackup Root, could I just backup all my apps and the system (using MyBackup Root and the bootstrap, respectively), SBF, then restore the phone by downloading the bootstrap and MyBackup Root and restoring my apps/system? Would this get my back to where I was before, or would I have to manually download each one of my apps and lose all previous data that I had on them? I'm just wondering what's the easiest way to restore my phone back to the layout that I had before I SBFed.
Thanks for your answers to any of these 3 questions!!! I definitely appreciate it.
Click to expand...
Click to collapse
What I typically do is using the X2 Bootstrap, I make a Nandroid backup and restore directly from that. Performing an SBF is only going to be necessary if the backup was on a different kernel, otherwise if you may run into boot looping.
What exactly happened and what are you trying to do? Are you trying to restore your phone to an earlier point via SBF? As in you enjoyed the phone on 2.3.3, made a backup and now you're unhappy on 2.3.4 and wish to go back?
It sounds like if you were to SBF back to your desired version (the version you made the backups on) you would then be able to apply your backups and should be back to your desired phone state.
I'm slightly confused to the details due to the way it's worded. I know it's somewhat difficult to describe but that's the basic idea I'm getting. Please feel free to correct me if I'm wrong or fill in the blanks.
Is 2.3.5 much better?
Sent from my DROID X2 using XDA App
Okay so what I did was SBF back to 2.3.3 (I did this two nights ago) and before I did that, I:
1. Renamed the bloatware back to .apk (I had the suffix's ".bak" as an alternate "freezing" method).
2. Used MyBackup Root to make a backup of all my apps+their data.
3. Made a backup of the phone using the bootstrap.
4. SBFed
5. Rooted
6. Downloaded MyBackup Root
7. Restored all my apps and data and it worked!!!
8. Celebrated! I had no faith in it working but all my apps are back! I was so impressed, I was expecting to have to redo all my games and everything. MyBackup Root is such a sweet app, or I'm just a loser.
I hoped this helped other people, I had no idea what was gonna happen, no one's ever told me how to specifically get my phone back to the layout that I wanted.
and related to reaktor's post, what I was doing was SBFing back to my desired state of 2.3.3, just because I hate the battery glitch on 2.3.4. It had nothing to do with any apps I had, sorry for the confusion.
Your last reply was a little off but that was my fault, I'm sorry for my wording haha. I just have never known how to NOT have to redownload all my apps and start over on my games' data once I restore/SBF a phone. Now I know.
BTW my phone didn't maintain its root, just for reference for others. I had to reroot.
Well... You might want to do that again. There's now a battery fix for 2.3.4 and 2.3.5 in the dev forum.
Pepperm1nt's battery fix thread @ http://forum.xda-developers.com/showthread.php?t=1350336
It works great
Greatttttt haha all that fer nuthin. I may update again, or I just might wait til I get bored with the phone again to install this. Thanks a bunch for the link though!
Sent from my DROID X2 using XDA Premium App
The battery fix works great. Just flash it over stock or any custom rom. It works perfect!
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
Are you rooted? And why update to 2.3.6 uckk6? Its got a few really bad bugs.
Sent from my SGH-I777 using XDA App
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
If*
Sent from my SGH-I777 using XDA App
Thank you for your helpful information.
Sent from my SAMSUNG-SGH-I777 using XDA
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
jcracken said:
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
Click to expand...
Click to collapse
Might give it a try. Trouble is, not having a rooted phone and going back to stock means I lose all applications and data with them. Eh. Thanks
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Phalanx7621 said:
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I already did this except for rooting about 3 weeks ago. From what you're saying, if I root my phone from its current state I should be able to receive OTA updates? I'm willing to root just to see but I don't see how that would fix the "communication failed" errors for updates.
Sent from my SAMSUNG-SGH-I777 using XDA
FYI I have a rooted stock ROM, and I'm having difficulty doing an OTA update also. Different error (mine is "interrupted" after reboot). I posted it here because it seemed more related to that thread and I had other Q's about the process.
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
LiLChris06 said:
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
Click to expand...
Click to collapse
I don't think you understand. First of all, in no way am I in panic mode. Secondly, my phone is a few updates behind since I just recently brought it back to stock from CM7. All I am trying to do is bring it up to date.
Sent from my SAMSUNG-SGH-I777 using XDA
ota issue
You might want to check the (Guide)How to flash custom binaries.....on this forum. Creepycrawly has posted a reply towards the end of the thread that might be helpful. Believe its on one of the last two pages.
As has been said many times in other threads, even on a stock ROM if you have rooted and removed even one item of bloatware or made any other mods you will not be able to download an OTA update.
I have not rooted my phone. And as I said earlier, I restored my phone to complete stock meaning no bloatware has been removed. I'm still at a loss for what to do
Sent from my SAMSUNG-SGH-I777 using XDA
You were on CM9 (in a later post you say CM7), but you went back to stock UCKH7. Now you are unable to update over the air to UCKK6. You are mainly interested in having the phone ready to receive the update over the air to ICS, whenever that occurs. You have not rooted the phone since you returned to stock but you are willing to try root if it will help the update happen. You were also concerned about loosing apps and their data since you are not rooted. I recapped all this because on stock you should be able to run the update. To help you solve the problem, need to know all the facts.
I've done the following, although it has been several months ago, about a week or two after UCKK6 first released. From running a custom rom, I did a wipe data/factory reset, flashed stock UCKH7 plus root, and ran the over the air update to UCKK6 successfully, retaining root on UCKK6. I just did this to test it out, so after completing the test, I used my nandroid backup to return to the custom rom I was on.
I would assume that you did a wipe data/factory reset either before or after you flashed back to stock? If not, there could be traces left over that could interfere with the update process. I'm not sure if there could be traces left even after a wipe data/factory reset, but the Cyanogen Mod file structure is so very different than stock that it wouldn't be inconceivable.
Next, I would wonder how soon after flashing back to stock you tried to run the update, and if not immediately, what action could have possibly placed or removed files that would intefere with the process.
I'm pretty certain that if you were to wipe data/factory reset with a format and then flash stock again, and then try to run the update immediately, it would succeed. So there has to be something in the file system preventing it. You may not find it easy to correct that something manually. You may just have to do a wipe data/factory reset, and maybe a format, and then start all over with a fresh install.
Of course, that is the reason for rooting first. Root, then back up everything with titanium backup, SMS backup, export contacts, etc. and save all that to your computer. Then you can restore stuff after.
Thanks creepy,
I'm in the process of doing what you said. I rooted my phone, backed up everything I thought needs to be backed up and flashed the stock rom (2.3.4 kernel version 2.6.35.7 baseband version I777UCKH7). I still need to do a factory format in order to see if that will fix the update problem.
Question. Is the firmware version(s) above the latest AT&T software? According to Kies, it is. But I am reading other places that the latest software is android 2.3.6.
Did exactly as creepy stated. Brought the phone back to stock software and did a factory reset. Without ANY customization and as soon as the phone booted up, I did the software update and had the same thing, "Communication failed" (says there is an update available but servers are busy).
I give up.
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
creepyncrawly said:
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
Click to expand...
Click to collapse
From what I've been reading on AT&T forums (http://forums.att.com/t5/Samsung/Sa...2-3-6-OTA-update-now-live/td-p/2996495/page/3) I don't think so. I've been trying every combination I can think of to make this thing work but I honestly have no idea. I was extremely surprised when I brought the phone back to complete stock and no root and still couldn't get the update.
If ICS ever comes to AT&T GS2, I'll wait a month or so to keep trying then I might resort to going to an AT&T store to get a replacement. Who knows
So I am running liberty rom, and every time i boot up my phone rom toolbox force closes, I would love to get the full version if it the x2 was supported, but since I am running liberty rom can I uninstall this app with no ill effects?
You shouldnt use Rom Toolbox with the DX2. Even if it is made to work with Liberty. The reason being is that with our phones, the bootloader is locked. Rom Toolbox allows you to do stuff that our phone doesnt support due to the locked bootloader. Trying to use it for certain stuff can mess up your phone.
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
I think I misunderstood the question. You should be able to remove it. The ROM doesnt depend on it to run. If it is installed as a system app (I dont remember if it is) you might have to take certain steps to remove it.
jsgraphicart said:
You shouldnt use Rom Toolbox with the DX2. Even if it is made to work with Liberty. The reason being is that with our phones, the bootloader is locked. Rom Toolbox allows you to do stuff that our phone doesnt support due to the locked bootloader. Trying to use it for certain stuff can mess up your phone.
---------- Post added at 09:48 AM ---------- Previous post was at 09:44 AM ----------
I think I misunderstood the question. You should be able to remove it. The ROM doesnt depend on it to run. If it is installed as a system app (I dont remember if it is) you might have to take certain steps to remove it.
Click to expand...
Click to collapse
Got it, I was thinking since the rom and toolbox were developed by the same person the ROM actually needed the toolbox to run. I will be un-installing it now. Now that I have finally rooted and flashed a new rom I am starting to see how much of a ***** it is to have a locked bootloader. I will be so glad in 6 months when I can dump this POS!!!! Thankfully Liberty was out for dx2, otherwise I may have already smashed this paperweight.
ziggityz said:
Got it, I was thinking since the rom and toolbox were developed by the same person the ROM actually needed the toolbox to run. I will be un-installing it now. Now that I have finally rooted and flashed a new rom I am starting to see how much of a ***** it is to have a locked bootloader. I will be so glad in 6 months when I can dump this POS!!!! Thankfully Liberty was out for dx2, otherwise I may have already smashed this paperweight.
Click to expand...
Click to collapse
Have you tried the other ROMS available? No offense to the developer but Liberty isnt one of the best ROMS for our phone.
jsgraphicart said:
Have you tried the other ROMS available? No offense to the developer but Liberty isnt one of the best ROMS for our phone.
Click to expand...
Click to collapse
I've tried the cyanogenmod port, just too buggy for me, the sd flip was a major turn off, in order to try eclipse I'd have to sbf, reroot with pete's update to the ota and spend another 2 weeks getting my phone back to where it is now on a new rom. Other than that I have not tried any other x2 roms, I'm running 2.3.4
ziggityz said:
I've tried the cyanogenmod port, just too buggy for me, the sd flip was a major turn off, in order to try eclipse I'd have to sbf, reroot with pete's update to the ota and spend another 2 weeks getting my phone back to where it is now on a new rom. Other than that I have not tried any other x2 roms, I'm running 2.3.4
Click to expand...
Click to collapse
I'm running the latest CM7 ROM and I dont find it buggy. If you think about it, stock 2.3.4 itself is buggy. lol. And if you dont like the flip flop mod, you can always reverse it back. I don't know, to me, CM7 has been the least buggy. And I have never liked that Eclipse was moving onto 2.3.5 either. I tried it and it is nice. I just ended up going back to CM7.
I also found the wifi turned itself off periodically, so i can rename the internal sd back to sdcard and the sd card back to sdcard-ext??
I also had trouble restoring apps via titanium backup, they would say restoring and just hang and hang.
ziggityz said:
I also found the wifi turned itself off periodically, so i can rename the internal sd back to sdcard and the sd card back to sdcard-ext??
I also had trouble restoring apps via titanium backup, they would say restoring and just hang and hang.
Click to expand...
Click to collapse
Did you use the last update to CM7? I think some of that stuff is fixed. But I use llama profiles which allows me to connect to my wifi automatically when I'm in the location. And stay connected until I leave the area. I think this has caused me to not ever have wifi problems. I have had problems with Titanium Backup before. But I think it was when I was playing with the superSU app that came out a while ago. I cant really remember having problems when I flashed the new version of CM7. And with the sd card flip flop, I think you can install CM7 which will have the flip flop mod, then use the file located in this thread here to flip it back:
http://forum.xda-developers.com/showthread.php?t=1229294
jsgraphicart said:
Did you use the last update to CM7? I think some of that stuff is fixed. But I use llama profiles which allows me to connect to my wifi automatically when I'm in the location. And stay connected until I leave the area. I think this has caused me to not ever have wifi problems. I have had problems with Titanium Backup before. But I think it was when I was playing with the superSU app that came out a while ago. I cant really remember having problems when I flashed the new version of CM7. And with the sd card flip flop, I think you can install CM7 which will have the flip flop mod, then use the file located in this thread here to flip it back:
http://forum.xda-developers.com/showthread.php?t=1229294
Click to expand...
Click to collapse
thanks! I think Ill backup and try to flash the updated cm7 and give it a spin!