I know people hate these threads, but I have done as much research as I could before posting, and just want to confirm if my understanding is right...
I have a Canadian (Bell) XT860 -- don't worry, it's fine.
We now have options to restore this phone from a bricked state by flashing (using RSDlite?) either a Brazillian 2.3.5 image, the ME863 image, or a third that was mentioned but I could never find.
My understanding of this as far as development goes is that we don't have a safestrap that works yet, which prevents truly custom android f/w from being made for our phones... but as we do have an option for recovering from a bricked state, people can be more adventurous without worrying nearly as much.
Am I missing or wrong on anything here?
Yes, RSDLite is the program you would use to flash a stock SBF to your XT860.
There is the Chinese ME863 rom, and most recently the Brazilian XT860 rom. What is this 3rd one you heard of... where is it from, which carrier?
Safestrap didn't seem to work for XT860 (I think) or ME863 rom users (this one I'm sure of, as I tried it myself), but I recall when I was on my stock Bell XT860 rom, Bootstrap worked (problem was, there weren't any ROMS to play with - and I believe there still aren't any roms yet.) Hopefully this Brasil stock rom will help move things forward.
Until we get "SBF" that can bring us back to original Bell firmware, we can't really get truly "adventurous", since there is no way to bring phone back to factory state if you have to send it for service. Let's hope such recovery will be leaked/found for us soon and we can really get adventurous.
Accophox said:
My understanding of this as far as development goes is that we don't have a safestrap that works yet, which prevents truly custom android f/w from being made for our phones... but as we do have an option for recovering from a bricked state, people can be more adventurous without worrying nearly as much.
Am I missing or wrong on anything here?
Click to expand...
Click to collapse
I've been talking to Hashcode on and off on IRC for the past few weeks and we've been messing around with my bell xt860 when he's had the time. Unfortunately with his ICS port, patching safestrap (Hashcode mentioned just last night that he believes he's traced down the problem with safestrap on the xt860) etc he's extremely busy. He's mentioned a few times that he's working on a project or two for the xt860 that should get us moving along (ie patching safestrap I think), hopefully it's enough to know that devs(Hashcode) are still looking into the issues we have on the xt860.
With that being said, I have an idea or two I'm gonna try out here. I'll post results when I'm done. There are also a lot of other bright people who are giving things a shot, a few people are recompiling modules and trying to get cm7 working etc, it's ongoing but no ones had any progress to report yet unfortunately. It is ongoing though
Edit:No love, bricked for the moment. I've tried building and flashing a few roms, some I knew wouldn't work but a few had no reason not too, like a bell xt860 rom but for some reason all end with same results, sitting at the "M", not reaching the boot animation. Some difference between the verizon and our model in terms of boot.
Okay, thanks for the clarification everybody.
So - we're just missing a way to get back to Bell XT860 from Brazil/China XT860, but the workaround seems like it's just a matter of getting recovery to work and flash backups of the original software.
And - it sounds like we're fairly close to a breakthrough in getting bootstrapping enabled, which means that we're hopefully not too far off from a de-blur'd XT860.
Accophox said:
Okay, thanks for the clarification everybody.
So - we're just missing a way to get back to Bell XT860 from Brazil/China XT860, but the workaround seems like it's just a matter of getting recovery to work and flash backups of the original software.
And - it sounds like we're fairly close to a breakthrough in getting bootstrapping enabled, which means that we're hopefully not too far off from a de-blur'd XT860.
Click to expand...
Click to collapse
One of the problems we might run into is not being able to flash back to our bell kernel without an sbf from bell.
..as well as the Radio Firmware. Those can only be restored by SBF
Just to thank willis and endoroid I succesfully installed safestrap and liberty rom
the only thing its that it gives me an error when I switch to spanish language (I'm from mexico) on com.android.settings when selecting applications menu..
And also market closes.
XT860 Liberty ROM rooted and overclocked to 1200
goalando said:
Just to thank willis and endoroid I succesfully installed safestrap and liberty rom
the only thing its that it gives me an error when I switch to spanish language (I'm from mexico) on com.android.settings when selecting applications menu..
And also market closes.
XT860 Liberty ROM rooted and overclocked to 1200
Click to expand...
Click to collapse
I saw.on the liberty thread some other ppl have had market FC issues. Apparently the.solution is to just keep reflashing until it fixes. Although you may.wish to try clearing market data.first to see.if that clears it up
Sent from my XT860 using xda premium
Clearing market data doesn't help, along with force closing.
Happens when you start trying to download an app... then just cyclic FC.
It's just reflashing and praying. (I got it on the second attempt)
Well now im using steeldroid it works perfect
Related
Hello all,
After many months of excitement, Motorola Canada released Froyo(2.2.1) for the Telus Moto Milestone. Through all of this, it seems like I've gotten the DSI and kernel errors. The 4 capacitative keys take a while to respond (3 times before they work), and my keyboard and contacts/messaging are all screwed up, color-wise.
I was looking at rooting following this guide (http://forum.xda-developers.com/showthread.php?t=983516) but do not know if the vulnerable sbf's would be able to work now that I have 2.2.1.
Also, I have been told that FroyoMod is a very stable Froyo ROM, which I was looking to customize with a Gingerbread theme that he has released (http://forum.xda-developers.com/showthread.php?t=815595). Will I be able to follow the same tutorial to revert back to stock 2.1 then apply the official Moto update (in case I need to return it for servicing)?
I've heard rumors of people bricking their phones after applying faulty radios after flashing a custom ROM. Will I need to worry about applying the proper radio? Or is fairly painless to do?
What happens if I brick my phone if I apply a wrong radio?
Sorry for all these questions, I'd like to make this entire process as easy as possible and I've never rooted a phone before!
Thanks in advance!
skadude66 said:
Hello all,
After many months of excitement, Motorola Canada released Froyo(2.2.1) for the Telus Moto Milestone. Through all of this, it seems like I've gotten the DSI and kernel errors. The 4 capacitative keys take a while to respond (3 times before they work), and my keyboard and contacts/messaging are all screwed up, color-wise.
I was looking at rooting following this guide (http://forum.xda-developers.com/showthread.php?t=983516) but do not know if the vulnerable sbf's would be able to work now that I have 2.2.1.
Also, I have been told that FroyoMod is a very stable Froyo ROM, which I was looking to customize with a Gingerbread theme that he has released (http://forum.xda-developers.com/showthread.php?t=815595). Will I be able to follow the same tutorial to revert back to stock 2.1 then apply the official Moto update (in case I need to return it for servicing)?
I've heard rumors of people bricking their phones after applying faulty radios after flashing a custom ROM. Will I need to worry about applying the proper radio? Or is fairly painless to do?
What happens if I brick my phone if I apply a wrong radio?
Sorry for all these questions, I'd like to make this entire process as easy as possible and I've never rooted a phone before!
Thanks in advance!
Click to expand...
Click to collapse
1. The sbf will still work, sbfs replace everything...so version does not matter
2. Radios are not such a big deal on milestone, they an be easily swapped from AOR ( if you mean basebands, i dont know of any radio files other than this)
3. You can usually reflash older sbfs, unless bootloader changed
Sent from my Milstone running CM7
Caz666 said:
1. The sbf will still work, sbfs replace everything...so version does not matter
2. Radios are not such a big deal on milestone, they an be easily swapped from AOR ( if you mean basebands, i dont know of any radio files other than this)
3. You can usually reflash older sbfs, unless bootloader changed
Sent from my Milstone running CM7
Click to expand...
Click to collapse
So I will be able to use the 2.1 sbf for Canada over the 2.2.1 official Moto update that I have right now?
How would I swap the basebands and I'm guessing AOR is OpenRecovery? How would I do that.
Does anybody know if the bootloader for 2.2.1 changed?
Thanks!
skadude66 said:
So I will be able to use the 2.1 sbf for Canada over the 2.2.1 official Moto update that I have right now?
How would I swap the basebands and I'm guessing AOR is OpenRecovery? How would I do that.
Does anybody know if the bootloader for 2.2.1 changed?
Thanks!
Click to expand...
Click to collapse
1. I dont know if you can resinstall 2.1 on top of 2.2, you should...but i have never tried. At wore, you could use one of the 2.1 based roms in the dev section...i wont be the official version, but it will be eclair.
2. AOR is Androidiani open recovery...it is a different version or openrecovery with a bit more options. There is a change baseband submenu that lets you install the baseband files for each country.
Sent from my Milstone running CM7
People are saying that the bootloader is different between 2.1 and 2.2.1, so I think I might wait and see what others think before I try and root it. Thanks for your help!
any luck since then to root your Milestone from 2.2.1?
UPDATE: 27/11/11
I have started a thread in the development section that contains all this information, please leave any findings or questions there, I believe members will find it more helpful there.
The thread can be found here
I have removed the file links from the OP to stop any confusion in the future. All files can be found in the other thread where it will be maintained and updated (if necessary) in the future.
Thanks for reading.
UPDATE: 27/11/11
Andrew_Low has provided a copy of his stock FROYO backup, which I tested on my tab and confirm that it is working. The kernel is rooted, other than that it is a clean ROGERS rom.
He was also able to capture the GINGERBREAD update, (which I have not tested as of yet, any testers please post your results) this is the stock update available from KIES.
Many thanks to him for this, if it helps you, hit his thank you button[/URL]. If you find this thread helpful as well, hit my thank you button.
Instructions on flashing are not provided. If you need these files it means you know how to flash your device, have flashed a custom ROM previously, and require this to return to a stock state.
Both downloads can be found in the link
downloads here
ORIGINAL POST:
I am looking for the stock firmware for a Rogers Galaxy Tab (P1000UXJJ6)
There are many posts mentioning it, even asking for it, but no firmware to be found.
If anyone has a copy of it can you please post a link here or PM me, or even if you have a backup of the original ROM (or if you can make a backup if you have the original software on your tab). Anything will do, as searching for it has not showed any results.
MODEL: P1000R
IC: 649E-SGHI987
ORIGINAL FIRMWARE:
Version: FROYO.UXJJ6
P1000UXJJ6
The SamFIT web shows
Model: P1000
Region: Rogers - Canada, (Branded: yes)
Available languages: en, fr,
October 2010 Revision: 6
Thanks in advance.
RED
Not an easy ROM to find is it?
Anybody ?
Any fresh ROGERS tabs out there???
I just picked up a used Galaxy Tab that has this firmware on it. I'm not new to hacking Android devices, but the Tab is new to me.
I haven't installed Kies yet, but will in a couple of days and can make a backup.
That would be just great, thank you very much, and I assure you that you will be glad that you made a backup for yourself as well in the future (hopefully not though, I don't expect you to have problems or anything like that but you know what I mean).
If possible, can you make the backup before you root the device, otherwise it seems to be a bit of a headache trying to get it un-rooted after the fact.
Many thanks.
EDIT: I guess i'm thinking more of a temp root than a perm root before backup
Sigh, I'm in noobville here with Kies.
Cross booted to Windows XP (I normally use Linux as my desktop) - installed Kies and sorted out USB connectivity.
I don't see where in Kies I can do a firmware backup. The backup just grabs the user data from the device.
It detects my firmware version and offers me the chance to update (which I assume would be a bad idea). Quickly looking on the net, you can 'capture' the firmware files during an update - but that doesn't help grab the version I'm running. Seems there may be a registry hack that lets you install older versions in Kies? If that's true, why can't anyone with a Rogers tab just get the old firmware easily?
Looking for a bit of hand holding.
Oh yeah, and device is bone stock. I'll likely root, unlock and install CyanogenMod - but I'm in no rush. Happy to try to help capture the stock ROM. It may help me out in the future, you never know.
Search for Roto-backup, it is a way to back it up bit by bit. It's a thread by Rotohammer, using his technique members were able to provide UN-ROOTED firmware, which are posted in the dev section. Have a little read see what you think.
The Roto-backup link was helpful, but that requires rooting.
Here's what I've done. Starting with a bone stock, factory reset device. I rooted the device using SuperOneClick 2.2. Sadly I had to run this under Windows to get it to work, mono + Ubuntu didn't seem to work out
I used the default "auto" method of rooting with SuperOneClick, and I did install busybox. In theory - if you really wanted to have an un-rooted stock, you could use the Unroot option of SuperOneClick.
Then I used the roto-backup script. This seems to have worked and I've got a 250MB zip file that I believe contains the stock firmware.
Are you brave enough to test it?
Files were zipped into a single file then split into chunks using RAR to get around upload limits. Grab them from skydrive.
Nice. I have a backup I came across but it's screwy and can't be un-rooted. The root method you used was temporary or perm?, the difference would be one disappears after a reboot.
When I originaly did my backup I used a temp root and came up with a file that I'm pretty sure was about the same size.
Brave you ask? I'm downloading the 3 RARs right now and will check it out.
Many thanks, will flash and tell you how it goes.
Well, Andrew_Low, it worked like a charm. The flash went smooth I will attempt to un-root shortly, and tell you how it went.
Glad it worked. Let me know if unroot via SuperOnClick 2.2 goes ok.
Why do you want non root? Warranty claim?
Slightly off topic, what ROM would you recommend? Seems any AT&T compatible ROM should play ok on the Rogers tab. I'm partial to CM being that's what is on my phone.
Sent from my GT-I9000 using XDA App
It is for warranty reasons, I have two tabs one was acting up. I did re stock it and sent it back but I wasn't able to un-root so I'll see if it goes through with samsung.
I HAD my stock rom that I somehow deleted (or just misplaced, cause I can't find it anywhere) Then I figured that I am not the only one who may need this, and since it is harder to find, I thought that I would try and help out the P1000R folks by getting a stock rogers rom for those who would like to revert. I was going to wait until I receive my tab back and see what they did to it and maybe have a fresh rogers rom on it to backup. I plan on posting it for members to have.
Our Rogers tabs are great for flashing anything on it really (p1000 related of course). Currently I have BOCA on mine, I had HC RC1 on it previously for a good little bit, and was going to put the ICS alpha build on it, but now since I'm left with one I use it for business purposes and require full functionality out of it. The tab that I sent back had OVERCOME KRATOS on it. Funny enough, this tab is the one that i'm always flashing different roms on and overclocking and plain old abusing it yet it was the other one that crapped out.
I recommend the OVERCOME rom as it is very stable, fast and reliable with almost no bugs. Combined with the bell modem it could also be used for phone calls if necessary. But experiment with any one you want until you find one that suits your needs, I found both my tabs hard to brick so I wouldn't worry too much if I were you. I can't wait for an ICS beta rom to stick on this one.
Cool. I'm interested in a clean stock ROM if one shows up, please post to this thread. I'll try the unroot and see if that works for me.
Open to pointers on how to soft root and capture ROM. Seems feasible, but I didn't find a way to soft root and give me enough to roto backup.
Sent from my GT-I9000 using XDA App
Looking for a clean stock ROM for Rogers as well for warranty work, thanks!
Can't folk use the 2.3 firmware from kies? I haven't tried, but if you flash the rooted UXJJ6 from this thread then use Kies to upgrade to 2.3 you'd be in an unrooted stock state.
Sent from my GT-I9000 using XDA App
theREDlegion said:
Well, Andrew_Low, it worked like a charm. The flash went smooth I will attempt to un-root shortly, and tell you how it went.
Click to expand...
Click to collapse
Hmm, very interesting. I ran the unroot on my device and it did manage to remove the superuser apk, but beyond that the device appears to still be rooted - busybox is still installed, and when I shell in over adb I get the # indicating root access.
I suspect just removing the superuser app is enough to make it appear 'as stock' - but any expert digging into the device and it's easy to see things are not stock.
If I were to try again - seems zergRush may be the local root you want to use, then from there figure out how to backup the ROM.
[edit] Ooh... reboot and adb has lost the # - I still see busybox installed in /system/xbin/busybox - I suspect this is pretty close to 'stock' if I punt the /system/xbin stuff entirely.
I'm not sure I'm that motivated to chase this further - I can't guarantee it is 100% stock, and it's the same as dl'ing the files I previously uploaded and running SuperOneClick 2.2 unroot + removing the busybox stuff as I specified above. The only mystery here is really what causes adb to have root privs when rooted.
Sweet - appears I was able to grab the ROM from Kies during the 2.3 upgrade - so I've got a copy of the clean/stock Rogers GINGERBREAD.UXKG1 firmware.
Will upload and link here in the next couple of days.
Very sweet, I will post it in the OP for reference.
pback said:
Looking for a clean stock ROM for Rogers as well for warranty work, thanks!
Click to expand...
Click to collapse
I will post the Froyo version on the first post for reference, but if you are willing to wait Andrew_Low is generously going to provide a stock rogers Gingerbread rom which I will post for you and others in the OP.
Gingerbread is here https://skydrive.live.com/redir.aspx?cid=61f79860d644cd72&resid=61F79860D644CD72!124
+1 to theREDlegion for cleaning this stuff up and making the thread useful.
Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor
Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS
First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.
I have had my Bionic for a while now and have been thinking about rooting it. I finally got the ICS update but have been using GO Launcher too much to even notice it. Anyway, like I said, I want to root my phone. I am current on all updates. For some reason it's running at a tenth of it's memory tho not much is running that I can see. This leads me to believe there's things running in the background that I can not see. I am reluctant to get rid of all my apps, but I also don't want anything that's eating all my resources either. I kinda want to start new but kinda don't. I guess I just don't like letting go of anything.
I know this is selfish of me, but I am hoping that this thread will stay clean of others chiming in asking about their issues. I just don't want the thread to lose focus since this is about what I hope to get from my phone.
Ok, so here are my questions or favors to ask:
Since my phone is fully updated, do I need to do some other updated steps for rooting my phone or is rooting always the same no matter the build or version?
When I go to root my phone, I back up everything first and then I get it back, right?
I read somewhere that it's possible to brick the phone. What precautions should I take to avoid that?
Can I get all the benefits of a rooted phone without a ROM?
Are ROMs really that awesome that I should get one, or three?
I am interested in a ROM after some posts and pages I read. I was attracted to CM at first but so is everyone else probably at first. Does CM even work on the Bionic? And if it does, does everything work like the camera and Bluetooth?
As I said earlier, I use GO Launcher. One of the things I really like about it is the folders I can make in the App Drawer. Now CM is based off of ADW Launcher, but no options to make folders in the app drawer? Is it possible in any way if I choose CM as my main ROM?
Is CM overrated? Liberty and Eclipse look nice too. I also read a little, very little, about AOKP. Any suggestions? I want to get rid of a lot of extra processes and bloatware but I don't want to lose some of the apps pre-installed like Google Maps and Navigation, etc. Unless there are other, much better replacements that anyone knows of.
I know most of this is personal preference but I am hoping to find a comprehensive way at figuring out what's best for me.
I had more questions but I will wait and ask more as the thread continues.
Oh, I don't really need answers in step by step unless I ask. A simple link would suffice unless it's not covered anywhere.
Thanks for reading this, I hope I am not frustrating anyone as I am sure similar posts have been made.
You're basically asking to have this entire forum summarized into one post...
Spend some time reading, then ask smaller, more concise questions.
Not trying to sound like a ****, but i could spend an hour answering all of that. Half of those questions could be answered with some reading of the ROM specific threads.
Sent from my DROID BIONIC using Tapatalk 2
Ok, I know that SOME of the questions are answered somewhere else. The thing is that after I read one thread only to find it unsolved, I read others that are are 50 pages long going nowhere as well. I haven't seen anything about my phone being fully updated and I am not going any further until I know for sure from someone like a DEV that I can.
Some of these questions are yes/no questions, which wouldn't take long at all to answer, maybe even less time it takes to write a complaint about my post. I certainly don't expect one person to write for an hour on every topic I asked about. I thought it would be a collective effort.
I guess I will take this slowly.
Since my Droid Bionic is updated to the current versions, do I need to do this differently than others have used in the past to root this phone?
Where is the best method to do this?
Before I start, I have to backup everything, right? If so, what's the best way to go about backing up everything?
I read somewhere that there are 3 things you should do to make sure you avoid bricking. I have since lost it. Does anybody know a surefire way to do this.
Please be gentle.
CycoPuppet said:
Ok, I know that SOME of the questions are answered somewhere else. The thing is that after I read one thread only to find it unsolved, I read others that are are 50 pages long going nowhere as well. I haven't seen anything about my phone being fully updated and I am not going any further until I know for sure from someone like a DEV that I can.
Some of these questions are yes/no questions, which wouldn't take long at all to answer, maybe even less time it takes to write a complaint about my post. I certainly don't expect one person to write for an hour on every topic I asked about. I thought it would be a collective effort.
I guess I will take this slowly.
Since my Droid Bionic is updated to the current versions, do I need to do this differently than others have used in the past to root this phone?
Where is the best method to do this?
Before I start, I have to backup everything, right? If so, what's the best way to go about backing up everything?
I read somewhere that there are 3 things you should do to make sure you avoid bricking. I have since lost it. Does anybody know a surefire way to do this.
Please be gentle.
Click to expand...
Click to collapse
1st question . No, your phone is not special since it is updated what worked for others will work for you.
2nd follow this link and the instructions to the letter http://www.droidrzr.com/index.php/topic/4026-samurihls-house-of-bionic/
3rd . Since you are stock. I would suggest using Verizon's back up services. TiBu requires root. IMHO I wouldn't bother because Google automatically backs up contacts and most roms require you to do a full data wipe.
There is no magic formula to keep from bricking your phone. Just follow directions and if you can't tolerate the risk don't do it.
From my EVOLVED bionic
Obsidian_soul said:
1st question . No, your phone is not special since it is updated what worked for others will work for you.
2nd follow this link and the instructions to the letter Can not post links
3rd . Since you are stock. I would suggest using Verizon's back up services. TiBu requires root. IMHO I wouldn't bother because Google automatically backs up contacts and most roms require you to do a full data wipe.
There is no magic formula to keep from bricking your phone. Just follow directions and if you can't tolerate the risk don't do it.
From my EVOLVED bionic
Click to expand...
Click to collapse
That link no longer works
Also I found an article named "Learn How-To Root, Custom Recovery, Backup, And De-Bloat Your DROID BIONIC" while searching around for ROM ideas and such. Anyway, after reading this, it almost seems as if I don't need to do factory reset. Is this ok?
CycoPuppet said:
That link no longer works
Also I found an article named "Learn How-To Root, Custom Recovery, Backup, And De-Bloat Your DROID BIONIC" while searching around for ROM ideas and such. Anyway, after reading this, it almost seems as if I don't need to do factory reset. Is this ok?
Click to expand...
Click to collapse
Just last week I started with a stock ICS Bionic and followed this guide to root: http://droidbionicroot.com/droid-bionic-root/how-to-root-ics-on-droid-bionic-and-motorola-android/
That went very well. I wanted to try out JB 4.2.2, so I installed SafeStrap and an official CM 10.1 nightly. The net result was that I had a very unstable phone until I did a factory reset . As of this writing, however, it's behaving extremely well. YMMV.
Ratamacue said:
Just last week I started with a stock ICS Bionic and followed this guide to root: Can not post links
That went very well. I wanted to try out JB 4.2.2, so I installed SafeStrap and an official CM 10.1 nightly. The net result was that I had a very unstable phone until I did a factory reset . As of this writing, however, it's behaving extremely well. YMMV.
Click to expand...
Click to collapse
Ok, so you flashed the ROM, didn't work so well, then you did a factory reset. Doesn't a factory reset wipe the phone? If that's the case, doesn't it wipe out the ROM?
Oh one more thing. Following this link, does this wipe the data from my phone? Anything I should back up before doing this? Should I do any updates before flashing CM 10?
CycoPuppet said:
Ok, so you flashed the ROM, didn't work so well, then you did a factory reset. Doesn't a factory reset wipe the phone? If that's the case, doesn't it wipe out the ROM?
Click to expand...
Click to collapse
No, a factory data reset doesn't wipe the ROM, but it does require running the initial setup (as if you were setting up a brand new phone).
CycoPuppet said:
...one more thing. Following this link, does this wipe the data from my phone? Anything I should back up before doing this? Should I do any updates before flashing CM 10?
Click to expand...
Click to collapse
You definitely want to back up everything you're not willing to lose. I ran a backup the very first thing after installing SafeStrap, and it was a good thing because with all my messing around I managed to bork my stock ROM to the point that it wouldn't boot. Fortunately, all I had to do was restore it from a backup.
My phone on CM 10.1 had enough issues with freezing and crashing that I decided this morning to try a different ROM. So far, I've had really good results with Icarus HD (a custom ICS ROM). I really don't know if my experience with CM 10.1 was typical.
OK, so I want to root. Now does rooting wipe any data? Regarding Safestrap, I install that first before rooting?
Rooting doesn't wipe any data. Root first, then install SafeStrap.
Okay, I will be rooting and installing safestrap when I get home for work today. I will still have more questions I am sure. I do have a few before I actually start rooting or right after.
I know safestrap makes a backup/recovory, but is it full recovery only or can I recover portions, like say my Dolphin browser with the settings and bookmarks?
I read that when making a backup of stock ROM, use sdcard, I'm sure that means external but when flashing a ROM, will that wipe data from the external card?
When setting up slots for multi booting ROMs, gernally how much storage do they need?
If I have two different ROMs, does it act like user accounts in Windows, would I have to download the same app on each ROM or do both ROMs have access?
Can one ROM have stuff I don't want the other ROM to have visible?
CycoPuppet said:
I know safestrap makes a backup/recovory, but is it full recovery only or can I recover portions, like say my Dolphin browser with the settings and bookmarks?
I read that when making a backup of stock ROM, use sdcard, I'm sure that means external but when flashing a ROM, will that wipe data from the external card?
When setting up slots for multi booting ROMs, gernally how much storage do they need?
If I have two different ROMs, does it act like user accounts in Windows, would I have to download the same app on each ROM or do both ROMs have access?
Can one ROM have stuff I don't want the other ROM to have visible?
Click to expand...
Click to collapse
1. SafeStrap is full recovery only. Use Titanium Backup for backing up apps and data.
2. Flashing a ROM won't do anything to your external SD card.
3. When you set up ROM slots, you'll be asked how much room you'd like to allocate for data. The choices are 1, 2, or 3 GB. I started off allocating 3 GB to the stock ROM slot and was never able to load more than 3 separate ROMs before I ran out of room. I'd start with just using 1 GB for data.
4. Each ROM is an island. You have to download the apps separately (unless when you go through the initial setup you tell the system to restore apps and settings from the Google servers.)
Cool. I rooted and got safestrap but it's version 3.05 and not 3.11. Some ROM I was interested in said must have 3.11, which I am assuming that's the newest one so far. I did watch a tutorial about getting the current version, so no question there.
So the ROMs are separate islands and during flashing they can be in slots allocated up to 3GB. Does that mean that's the only amount of storage I can have when running that ROM? Say I like taking lots of photos and didn't save them to my external card, could I essentially run out of space or is the storage allocation just for the ROM itself and any updates it may have?
Sorry about these series of questions, just want to make sure I am doing it correctly in case I might make a mistake for future's sake.
The storage allocation is for the ROM, apps, and data that haven't been assigned to the external SD card. You can definitely run out of space if you load several ROMs and don't save any of your data to the external SD card.
Also, keep in mind that when VZW sends the OTA update to 4.1 next week, the only way to keep root is to root in ICS and use Voodoo OTA Rootkeeper to protect root before you take the OTA. If you flash the system image, you will lose root, and there is no known working root exploit for the Bionic JB release.
Lost Root
Hey, I used Voodoo before flashing the 4.1 update, but forgot to update the binary beforehand, and therefore lost root. Anyone have any luck yet with an exploit for the OTA?
And there's no working FXZ before this now, correct? This software is now the earliest version I can FXZ to?
auglove3rd said:
Hey, I used Voodoo before flashing the 4.1 update, but forgot to update the binary beforehand, and therefore lost root. Anyone have any luck yet with an exploit for the OTA?
And there's no working FXZ before this now, correct? This software is now the earliest version I can FXZ to?
Click to expand...
Click to collapse
Not root exploit yet for bionic JB. And if you try to FXZ back to an earlier version, you will brick your phone.
OK, so I rooted, got safestrap tho still not updated to 3.11, got TBU (free), got Voodoo. I had to race the clock today cuz it was updating android, or at least downloading the update. The root process I used gave me SuperSU and didn't tell me the version for the SU binaries. I searched around and all I could find was info on SuperUser in regards to backing up root. I uninstalled SuperSU, kinda. I just told it to use a different SU cuz when I used SuperUser and updated the binaries, SuperSU wanted to update them, then I opened SuperUser and the binaries reverted back. I was worried so I just told SuperSU to use a different SU. Was that ok? I didn't update to JB yet. Has there been luck with the Bionic using voodoo and keeping root after the JB update?
All this back and forth means I'm making a full image backup, then trying various ROMs. I've tried CM10.1, too many issues (no car dock, trouble installing lots of apps, no speakerphone). Next is... Whizzed Bean?
EDIT: Seems Speakerphone issue was fixed in the 0420 nightly. Will have to try it again.
AND I copied all the backups to my PC, so I can restore them at will (provided the phone still boots, that is... )
If I can't find a JB ROM I like I guess I can do HouseofBionic reflash (which did NOT cause me to lose data, as I upgraded to ICS that way) then allow the JB OTA to go through.
*sigh*... So much bull**** in these updates.
Hope someone sees my question above. I still haven't updated to JB yet. Once I do I will be flashing ROMs. I am interested in CM, Liquid Smooth, Icarus Hd and Wizzed Bean or Synergy (executioner ) Both WB and Synergy look indentical. What is the differences.
CycoPuppet said:
Hope someone sees my question above. I still haven't updated to JB yet. Once I do I will be flashing ROMs. I am interested in CM, Liquid Smooth, Icarus Hd and Wizzed Bean or Synergy (executioner ) Both WB and Synergy look indentical. What is the differences.
Click to expand...
Click to collapse
WB is a fork of CNA (codename Android) 4.1 JB (which is itself based on AOSP)
while Synergy is a fork of the standard Moto ICS (.246).
Yes, they look identical because they both used the Samsung UI elements.
Hello,
I rooted/flashed my bionic a long time ago, and haven't fiddled with it since..I'm currently using:
ROM - KIN3TX V1.0
Kernel - 2.6.35.7-g686e6
Baseband - CDMA_N_03.1C.57R ltedc_u_05.15.01
System Version 5.8.894.XT875.Verizon.en.US
Version 2.3.4
Could somebody please lend a hand as to what I need to do to move forward with a current rom, or even properly flash back to stock? I'm asking because my 4G stopped working a while ago.. it was fine one day, then stopped. I haven't had time to mess with it, but i've changed sim cards (different phone number) and that didn't resolve the issue either..).. if anybody would be able to lend a hand getting back on the right path, or at least get my 4G working.. it'd be greatly appreciated!!
thanks,
Dennis
Curious about this one myself. A VZ tech rep told me tonight that ICS was officially released for the Bionic and that I should really check for an updated ROM.
You should be able to use the fxz file and get back to stock. There is one for the official .246 ics update.
You shouldn't need to do anything else
Note: this wipes all user data and in rare cases the entire sd card. So back up your stuff. There are a few guides in the Android development section of our forums. (If they have not updated their old .905 gb guide, do everything in their guide except use the [fxz].246 ics file {also in the android development forums})
Sent from my DROID BIONIC using Tapatalk 2
Thank you. I actually tracked down some info and ended up flashing the FXZ 904 update, so I guess that puts me a bit behind.. I'll look up the 294 today.. thanks again!