What chance is there of me bricking my phone by doing sbfing, rooting, installing custom recovery, and then applying p3's custom update? Have there been reports of people irreversibly bricking their phones by doing any of this? I am trying to assess the risk of doing this.
Just sbf and factory reset and don't install anything but system recovery and you will be fine
Sent from my DROID X2 using XDA Premium App
There should be little risk but one thing you should know is that you take a risk anytime you modify your phone from it's factory condition. With that said, make sure your have Gingerbreak.apk and MOTODX2_Bootstrap_signed.apk in the root of your SDCard (external card). SBF to factory so that you have a clean plate to start with... think of it as going to a buffet... you must use a clean plate each trip Once you root and install the bootstrap you'll want to boot into recovery then do a data wipe to make sure you don't run into trouble. Then simply install the zip. It will take about 5 minutes or less.
P.S. Make sure to put the update in the same place you put the other two files.
redwingfaninnc said:
What chance is there of me bricking my phone by doing sbfing, rooting, installing custom recovery, and then applying p3's custom update? Have there been reports of people irreversibly bricking their phones by doing any of this? I am trying to assess the risk of doing this.
Click to expand...
Click to collapse
Pretty much every dev has in their sig something about putting your phone at risk any time you modify the system, that being said i am a total noob at this stuff and i got it right first try, even having to sbf back from 2.3.3. As long as you are careful and follow all directions you shouldnt have a problem. i suggest doing an android factory reset after SBFing to 2.2.2 and before rooting it, then root, bootstrap, upgrade and do ANOTHER factory reset through recovery. after doing all that mine is BEAUTIFUL
Well I sucked it up and finally did it. No more than an hour from start to finish, excluding sbf download time, including time to read, reread, and read again the instructions.
Could not have gone smoother.
Somehow my apps just started downloading. Does that make sense? Is it because I had moved the apps to the media area?
Did you back up your apps to google? That could explain your apps being restored.
Sent from my DROID X2 using XDA Premium App
Related
Sorry again for initially posting this I the wrong forum!
Hey all!
I was thinking of rooting my eris, but after reading the forum some, I still have a couple questions about Eris rooting and rooting in general.
First off, if I use the one click root app, I will not have to install a new rom, correct? Also, how likely is it to brick my phone? If bricked, is there a method of restoring it?
Secondly, if I install the FroYo rom, would I be able to go back to the factory build of OTA 2.1? Or would I be stuck with custom roms then?
The only reason I am concerned with restoring the factory rom is that if something happens to the phone, I'd like my warranty to still be able to cover it (I'm 99% sure that they won't cover a rooted froyo thats overclocked).
Also, sorry if these have been asked before, I just wasn't able to find them on my own.
Sent from my Eris using XDA App
birel44 said:
First off, if I use the one click root app, I will not have to install a new rom, correct?
Click to expand...
Click to collapse
It doesn't force you to do anything; it only installs a custom recovery - from which, anything is possible. One of the options is to overlay two different flashes - engtools3.zip and the "OC Kernel" - this gives you root capabilities and overclocking, but leaves you with exactly the same Apps and settings. Or, you can replace everything with a brand new ROM, after you have made a Nandroid backup.
birel44 said:
Also, how likely is it to brick my phone?
Click to expand...
Click to collapse
There is about a 0.0000000001% chance it will brick your phone.
What the risks are after that depend on your ability to read and follow directions, but are generally pretty low.
birel44 said:
If bricked, is there a method of restoring it?
Click to expand...
Click to collapse
A brick is defined as "unable to be restored by any means"; so, no, a brick can not be recovered. There are ways you could make the phone unbootable, but not "bricked". Those can generally be recovered from.
birel44 said:
Secondly, if I install the FroYo rom, would I be able to go back to the factory build of OTA 2.1? Or would I be stuck with custom roms then?
Click to expand...
Click to collapse
If you make a Nandroid backup, you can go back to EXACTLY what you had before.
cheers
bftb0
I had pretty much the same questions the other day; I went ahead and installed one-click root, flashed rootme.zip, encountered no problems. Then I simply followed the directions in the sticky in the development subforum (can't remember the name) for flashing a custom rom.
It started off by saying to create a nandroid backup, and it's a darn good thing I did, since my first rom flash was a failure. Luckily I just restored from the backup and my phone was exactly the sane as it was before the custom rom install. Still rooted, and all apps, contacts, and settings were the same.
Sent from my nonsensikal Froyo using XDA App
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?
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!
There is probably some ridiculous, overwhelmingly simple reason for the answer to this question, but take into account that its coming from the guy who has been trying install a ROM for a week unsuccessfully, Anyway, enough personal degradation for the moment, and on to business. It seems to me that every time I have to .spf it gets easier and faster(imagine that). RSDlite is such a perfect format flashing, so why has no one thought of a way to flash ROMS via RSDlite? I understand that getting your proverbial elbows greasy is the fun of this, but for the helpless and hopeless, such as myself, there should be a super simple segue into cool techy stuff for us too!! I'm kidding, I'm not that buried.....I think.
Why would you sbf a rom when it only only takes a couple of minutes to flash a rom?
1, are you rooted?
2, do you have tenfar bar installed?
3, is the rom of choice on SD card?
Where are you having your trouble what rom? How are you trying it? It is pretty simple.
MathiasKnight said:
There is probably some ridiculous, overwhelmingly simple reason for the answer to this question, but take into account that its coming from the guy who has been trying install a ROM for a week unsuccessfully, Anyway, enough personal degradation for the moment, and on to business. It seems to me that every time I have to .spf it gets easier and faster(imagine that). RSDlite is such a perfect format flashing, so why has no one thought of a way to flash ROMS via RSDlite? I understand that getting your proverbial elbows greasy is the fun of this, but for the helpless and hopeless, such as myself, there should be a super simple segue into cool techy stuff for us too!! I'm kidding, I'm not that buried.....I think.
Click to expand...
Click to collapse
Okay, looks like you created a new thread about the same issue...but moving on.
RSD Lite is a Motorola tool, that was initially just supposed to be used by retailers (like VZW and Radioshack) so that they could reset people's phones rather than having to ship the to Moto and send them back to the customer, or for VZW and others to wipe devices and resell them as "refurbished" units. The reason we can't use RSD to create ROM's is the SBF files are signed by Motorola. So if we were to modify them in anyway or try to make our own, it would refuse the files and not flash the device.
Now, from your other thread you posted this:
MathiasKnight said:
Sorry about that, I must have been excited. Unfortunately I spoke too soon. Either that or I'm not meant for this, which I hope is not the case seeing that I'm getting my degree in IT. I finally get bootloader, with ROM and GAPPS placed accordingly(I opted for Eclipse). When the zip is finished uploading and I see confirmation that all was installed correctly, I begin the reboot......and it takes new to an unactivated Droid X2. I've created nandroid after nandroid, with different methods and different ROMS, and I either land there or with a signature error, even in bootstrap. I'm gonna try one more time before I hang up my guns. Maybe.....
Click to expand...
Click to collapse
Could you please outline everything you do, step by step? After you SBF you should have to activate your phone anyway, so that after you root, install bootstrap and then boot into that and apply the ROM and GAPPs the phone should already be activated.
Travisdroidx2 said:
Why would you sbf a rom when it only only takes a couple of minutes to flash a rom?
1, are you rooted?
2, do you have tenfar bar installed?
3, is the rom of choice on SD card?
Where are you having your trouble what rom? How are you trying it? It is pretty simple.
Click to expand...
Click to collapse
The only time I have gotten any response that remotely resembled success was the first time I used System Recovery, but the status bar was incredibly slow, like not moving basically, so I figured after about 25 minutes something was amiss...again. Yes I'm rooted, don't know what a tenfar bar is yet but I'm on it now, and I've got a variety of .zip's that are supposed to be compatible with 2.3.4, and I'm sure they are. I was really kind of joking about the .sbf, but I still think it would be a viable alternative.
MathiasKnight said:
The only time I have gotten any response that remotely resembled success was the first time I used System Recovery, but the status bar was incredibly slow, like not moving basically, so I figured after about 25 minutes something was amiss...again. Yes I'm rooted, don't know what a tenfar bar is yet but I'm on it now, and I've got a variety of .zip's that are supposed to be compatible with 2.3.4, and I'm sure they are. I was really kind of joking about the .sbf, but I still think it would be a viable alternative.
Click to expand...
Click to collapse
Okay, so you've SBF'd to 2.3.4. Rooted using whatever method, and you have the BootStrap recovery installed yes? Then you boot into recovery, wiped data, wiped cache and wiped dalvik cache, then tried installing a zipped ROM from you sd card, and upon restarting you get stuck at the moto M screen?
A couple things. First, when you wipe the dalvik cache (for roms or any mods) the phone has to rebuild that before it can actually boot into Android. This can take anywhere from a few minutes to 5 minutes or upwards. If you've gone 10 minutes and still nothing, all you need to do is pull the battery (so the phone powers off), reinstall the battery, DONT TURN THE PHONE ON, and then plug your phone into your wallcharger. After you plug in your phone, it'll turn itself on, go to the M screen and then go back into the BootStrapRecovery. From there you can redo the steps, wipe everything and then reinstall. However, IF you boot into the stock Android Recovery and wipe cache and data from there, you mucked it up and you'll have to SBF and restart the process.
ALSO, from your previous thread you said you were trying to install Eclipse. What version are you trying? 1.xx eclipse will work on 2.3.4, but Eclipse 2.xx will only work on 2.3.5, which could be another reason you are having issues.
Ok, so I readily admit that I'm the jackass the n00b video was aimed at. I thought I understood what I was doing, and clearly didn't. Now I can't get my phone to do ****.
I was attempting to flash the new CM9 beta. First time I've attempted to flash anything.
was on 2.3.5.
rooted using the 2.3.5 root method.
SBF-ed to 2.3.4. (prob didn't need to root on 2.3.5 if I was going to sbf to 2.3.4, but I'm an idiot)
SBF went fine. then I messed up good.
at the end of Moon Shadow's SBF tutorial he said he recommends the full factory reset, so I did it.
so now...I have no phone service. looking at settings/about phone it doesn't know my phone # and I have no idea how to fix this. not sure what other problems will present themselves after that, but that's the big issue. I'm connected to my home network, so at least I have some data connectivity.
before starting...
I made a backup with Clockwork Recovery, but that backup seems to be gone.
I made a backup with Go Backup, and that seems to still be there, but it was a 2.3.5 backup...how can I get to that and will it fix my problem?
ideally right now I'd just like to go back to the Go Backup backup I made before starting any of this and then I can reconsider where to go next.
additionally, I thought about just going forward, but I cannot for the life of my figure out how to flash this CM9 ROM, despite having read the directions 15 times. I tried to use Clockwork to install it from SD, but when I try that I can't see the .zip, despite having copied it over.
Can anyone take pity on a n00blet, or point me to a thread with information on how to solve this (I searched and had trouble finding anything useful)?
Very appreciative of all help.
Croda said:
Ok, so I readily admit that I'm the jackass the n00b video was aimed at. I thought I understood what I was doing, and clearly didn't. Now I can't get my phone to do ****.
I was attempting to flash the new CM9 beta. First time I've attempted to flash anything.
was on 2.3.5.
rooted using the 2.3.5 root method.
SBF-ed to 2.3.4. (prob didn't need to root on 2.3.5 if I was going to sbf to 2.3.4, but I'm an idiot)
SBF went fine. then I messed up good.
at the end of Moon Shadow's SBF tutorial he said he recommends the full factory reset, so I did it.
so now...I have no phone service. looking at settings/about phone it doesn't know my phone # and I have no idea how to fix this. not sure what other problems will present themselves after that, but that's the big issue. I'm connected to my home network, so at least I have some data connectivity.
before starting...
I made a backup with Clockwork Recovery, but that backup seems to be gone.
I made a backup with Go Backup, and that seems to still be there, but it was a 2.3.5 backup...how can I get to that and will it fix my problem?
ideally right now I'd just like to go back to the Go Backup backup I made before starting any of this and then I can reconsider where to go next.
additionally, I thought about just going forward, but I cannot for the life of my figure out how to flash this CM9 ROM, despite having read the directions 15 times. I tried to use Clockwork to install it from SD, but when I try that I can't see the .zip, despite having copied it over.
Can anyone take pity on a n00blet, or point me to a thread with information on how to solve this (I searched and had trouble finding anything useful)?
Very appreciative of all help.
Click to expand...
Click to collapse
ok, noob found thread about activation and fixed that part.
now I'm hoping I can just go back to 2.3.5 and apply my backup.
Lol, first take a deep breath. Your phone is not hosed, it's actually working like it's supposed too.
After you sbf, you phone is back to it's factory state right? So remember when you got your phone for the first time you had to have it activated/programmed. If you're on Verizon then dial *228 and follow the directions, takes about 5 minutes. This will give you back service and your phone number.
Second, the droid x2 is unique and requires a few different steps than most phones to flash things because it has whats called a locked, encrypted bootloader. So with the X2 you will NEVER want to use Rom Manager (Clockwork Mod Recovery) or Rom Toolbox. They just do not work with our phone yet.
Your going to want to read this link: http://www.droidxforums.com/forum/droid-x2-support/41785-common-x2-questions-answers.html
It gives a good overview of how the X2 works and explains a lot of things.
Then go here: http://forum.xda-developers.com/showthread.php?t=1318083
This explains how to install and get into the X2's special Bootstrap Recovery. This is where you will make backups, restore backups, and flash new roms. The thread explains in great detail how to make and restore backups in Bootstrap Recovery.
oh man, thanks a bunch lead off.
that whole deal with the boot strap is something that I never saw in all the reading I did and probably solves a lot of my problems. I'll do what you said (starting with the deep breath) and begin again.
thanks again for the help.
Yea no problem