Related
A few weeks ago I rooted my X and ran the manual deodex method posted on the site. Phone ran great, I installed clockwork recovery and made a few backups. after installing a rom and not being able to get back into the recovery, I had to flash the phone with the 2.2 full SBF. This leads to my questions
1. After I SBF'd I was able to recover my applications and my data was all on the SD card. however I have a few applications that when run will close and give me an error message stating that the "application unexpectedly quit" I can duplicate the issue most when attempting to search the a forum through the XDA application. I am sure I failed to wipe data and cache before I recovered the stock OS, could this be the cause, any ideas?
2. I have re-rooted my phone but I have a question about deodexing again. I understand that motorola is in the early stages of working on an update to fix reported issues with 2.2, I also believe that they will use this opportunity to update the bootloader version. is there a way to disable the OTA updates? I am concerned about bricking my phone if an update is release and I am deodexed, what is the worst that could happen?
Sorry for the post, I am technically inclined but am still learning the android OS, any help is very much appreciated.
If you run a rom either aosp or blur you can avoid the ota that's end only way I know to avoid it
Sent from my DROIDX using XDA App
thanks for the response, I read a few places that clockwork recovery blocks OTA updates from installing, but I am having a hard time nailing down a definitive answer.
From what I understand Droid X SBF files do not wipe data like other phones. I recently had to SBF but kept getting stuck looping at the droid eye. I booted into recovery and did a factory reset and all worked out just fine. I know it's not your exact problem but it still might be worth it to try.
As for not getting OTA updates other than doing a custom ROM I can't help you there, sorry.
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.
I rooted, bootstrapped, and flashed clockwork with rom manager. I am currently running liberty3 v2.0 and I am on .886. Is it worth updating to .901? And if so how do I do it? Step by step instruction will help. Thanks
Read around. Just to give you a hint:
There is currently a thread on the first page of the "Droid Bionic General" section of this forum (same area as this thread) that has a list of step by step instructions. To give you an even bigger hint, it has NOOB in the title.
whoops! my bad.
Edit: Just checked out post. Its for .893, but is it basically the same way? In other words, could I just run R3l3AS3DRoot in order to restore to stock, update to .901 and then reinstall liberty. Also, is it worth updating? Thanks.
901 radio is flawless for me never dropped signal phone went from 5 starts to 10 stars however I am stock plan on rooting after I learn a bit mire
Sent from my DROID BIONIC using XDA App
I have no experience with 886 since my phone came with 893 pre installed. Here's my general advice.
1) Read more.
2) Get rid of Bootstrap and install Safestrap. Especially since you're a noob, this is like an insurance policy. Again, refer back to #1.
3) If you want to get to 901, my best guess would be to FXZ back to stock, and then get the OTA (over-the-air) update to 893. I've never done that, so I can't be more help. But there's definitely instructions somewhere. Let me know how that goes.
EDIT: Maybe try this post: http://forum.xda-developers.com/showthread.php?t=1408522 Disclaimer: I haven't tried it, have no idea what I'm talking about, but it looks promising.
EDIT2: Or maybe this could help? http://www.mydroidworld.com/forums/droid-bionic-forum/10577-bionic-path-saver-1-click-method.html
How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Why this guide?
I noticed over time that my phone has become slower and more frustrating to use. For example, long pauses when trying to open a program - sometimes it takes an easy 10 or more seconds to open the dialer and dial a number.
I wanted to try a custom rom, but was concerned about the ability to get back to stock, if something goes wrong, or to be able to take advantage of a Bell update if they release a new one. Thanks to the hard work of many on this board, I have discovered how to make this possible and wanted to share with others.
Big thanks to DoomLord, HashCode, Enderoid, Rick#2, Dasilva333, Willis111 and others. Please feel free to make corrections to these instructions.
Note: This has been tested with an XT860 on Bell 2.3.6 firmware. This will probably NOT work on v2.3.4 So if you have 2.3.4, upgrade to 2.3.6 and then these instructions should work. When I first got the phone, it was at 2.3.5 and later was updated OTA (Over the air) by Bell to 2.3.6. To check which firmware you have, Home Screen / Settings / About Phone
Needed:
1. Windows pc (someone else more knowledgeable could probably tell you how to make this work on a Mac)
2. USB cable for connecting your phone.
3. Rooting tool, I highly recommend zergRush method by DoomLord found here:
http://forum.xda-developers.com/showthread.php?t=1321582
4. Safestrap by hashcode
http://hash-of-codes.blogspot.com/p/android-downloads.html
5. Custom rom of your choice.
Step 1:
Root your phone using the DoomLord tool. I used version 3. It was really easy, just follow the instructions on the link above.
Step 2:
Backup existing user programs that you might want to restore on a new system. I used Titanium Backup Pro but there are others.
Step 3:
Please read this page carefully
http://hash-of-codes.blogspot.com/p/how-to-safestrap.html to download and install safestrap v1.08. Note, you should remove any other type of bootstrap (eg. ClockworkMod, ROM Manager) before installing Safestrap.
Step 4:
Now you should be ready to download and try a custom rom. Make sure to do a backup (“Nandroid” backup) of your working system before you try a custom rom so you have something to fall back on in case something goes wrong or you want to return to stock.
Find a rom, download it and save it to a location on your sdcard or ext-sdcard. There’s lots of good candidates for you to test and a good thread with some reviews here:
http://forum.xda-developers.com/showthread.php?t=1384676
To do this, power down your phone after you have run safestrap and clicked to make recovery active. If you did it right, when you turn it on again, you should see a different splash screen that gives you a few seconds to enter the recovery menu by pressing the “menu” button on you device.
You should see “Safestrap Recovery v1.08” and below that “Safe System is: DISABLED”
on a black screen with some green menu choices.
Use the volume keys to scroll up/down and select “backup and restore” by pressing the power button.
The screen should change to show the Nandroid backup menu. You need to make a Nandroid backup of your existing (working) system, which is simply a snapshot of the exact system with all programs, settings, sms’s, call logs, etc. It’s like a snapshot in time in case you need to revert. Select “backup”, then select Internal or External SD Card for the location (I’m not sure it it matters for the location).
Safestrap will backup your system to a Nandroid backup. It takes a few minutes.
After the backup is complete, you can enable the Safe System where you will install custom roms. Scroll down and select “safe boot menu”, then “Toggle Safe System”, then on the next screen confirm your selection. It will backup the original system to a safe area where it can’t be modified (unless you are an advanced user and install a different version of Safestrap but that’s beyond the scope of these instructions).
After Safe System is: ENABLED, scroll down to “Install zip from sdcard”, select your rom, install, reboot and enjoy.
To revert back to your original system, follow these steps:
1. Turn off your phone and reboot into SafeStrap recovery menu.
2. Turn off SafeSystem. (Safe boot menu -> Toggle Safe System)
3. Restore your nandroid backup and reboot.
If you wanted to go further back to stock you could uninstall Safestrap and even unroot using DoomLord’s zergRush tool, which would put you back to stock.
I think that’s it. Hopefully this guide will be helpful to others who want to try a new rom without losing the ability to revert back to stock Bell.
ncho2233 said:
How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Why this guide?
I noticed over time that my phone has become slower and more frustrating to use. For example, long pauses when trying to open a program - sometimes it takes an easy 10 or more seconds to open the dialer and dial a number.
I wanted to try a custom rom, but was concerned about the ability to get back to stock, if something goes wrong, or to be able to take advantage of a Bell update if they release a new one. Thanks to the hard work of many on this board, I have discovered how to make this possible and wanted to share with others.
Big thanks to DoomLord, HashCode, Enderoid, Rick#2, Dasilva333, Willis111 and others. Please feel free to make corrections to these instructions.
Note: This has been tested with an XT860 on Bell 2.3.6 firmware. This will probably NOT work on v2.3.4 So if you have 2.3.4, upgrade to 2.3.6 and then these instructions should work. When I first got the phone, it was at 2.3.5 and later was updated OTA (Over the air) by Bell to 2.3.6. To check which firmware you have, Home Screen / Settings / About Phone
Needed:
1. Windows pc (someone else more knowledgeable could probably tell you how to make this work on a Mac)
2. USB cable for connecting your phone.
3. Rooting tool, I highly recommend zergRush method by DoomLord found here:
http://forum.xda-developers.com/showthread.php?t=1321582
4. Safestrap by hashcode
http://hash-of-codes.blogspot.com/p/android-downloads.html
5. Custom rom of your choice.
Step 1:
Root your phone using the DoomLord tool. I used version 3. It was really easy, just follow the instructions on the link above.
Step 2:
Backup existing user programs that you might want to restore on a new system. I used Titanium Backup Pro but there are others.
Step 3:
Please read this page carefully
http://hash-of-codes.blogspot.com/p/how-to-safestrap.html to download and install safestrap v1.08. Note, you should remove any other type of bootstrap (eg. ClockworkMod, ROM Manager) before installing Safestrap.
Step 4:
Now you should be ready to download and try a custom rom. Make sure to do a backup (“Nandroid” backup) of your working system before you try a custom rom so you have something to fall back on in case something goes wrong or you want to return to stock.
Find a rom, download it and save it to a location on your sdcard or ext-sdcard. There’s lots of good candidates for you to test and a good thread with some reviews here:
http://forum.xda-developers.com/showthread.php?t=1384676
To do this, power down your phone after you have run safestrap and clicked to make recovery active. If you did it right, when you turn it on again, you should see a different splash screen that gives you a few seconds to enter the recovery menu by pressing the “menu” button on you device.
You should see “Safestrap Recovery v1.08” and below that “Safe System is: DISABLED”
on a black screen with some green menu choices.
Use the volume keys to scroll up/down and select “backup and restore” by pressing the power button.
The screen should change to show the Nandroid backup menu. You need to make a Nandroid backup of your existing (working) system, which is simply a snapshot of the exact system with all programs, settings, sms’s, call logs, etc. It’s like a snapshot in time in case you need to revert. Select “backup”, then select Internal or External SD Card for the location (I’m not sure it it matters for the location).
Safestrap will backup your system to a Nandroid backup. It takes a few minutes.
After the backup is complete, you can enable the Safe System where you will install custom roms. Scroll down and select “safe boot menu”, then “Toggle Safe System”, then on the next screen confirm your selection. It will backup the original system to a safe area where it can’t be modified (unless you are an advanced user and install a different version of Safestrap but that’s beyond the scope of these instructions).
After Safe System is: ENABLED, scroll down to “Install zip from sdcard”, select your rom, install, reboot and enjoy.
To revert back to your original system, follow these steps:
1. Turn off your phone and reboot into SafeStrap recovery menu.
2. Turn off SafeSystem. (Safe boot menu -> Toggle Safe System)
3. Restore your nandroid backup and reboot.
If you wanted to go further back to stock you could uninstall Safestrap and even unroot using DoomLord’s zergRush tool, which would put you back to stock.
I think that’s it. Hopefully this guide will be helpful to others who want to try a new rom without losing the ability to revert back to stock Bell.
Click to expand...
Click to collapse
Good writeup. As a note when your switch back to nonsafe you don't need to restore a nandroid. Actually with safestrap you should rarely have to restore a nandroid as its next to impossible to screw up your device so bad that a restore is required. The stock bell /system stays nice and untouched
Sent from my XT860 using xda premium
Dont you just root, install safestrap and flash paritions to preinstall from stock(to avoid not being able to return to true stock) and not flash the og /system? Obviously works on 2.3.4, 2.3.6 etc any rootable rom capable of running safestrap. You should be able to even use my rom to return to stock deodexed by flashing to /system(non-safe) and removing any custom recovery. It should be very easy to convert that or the og dumps into a system.img for use with rsdlite and even the rest of the stock img files. I'll take a look at it this aft. Thanks for the write up, hope some of this info helps.
Maybe this is the wrong place to ask, but XT860 threads are few and far between in this droid 3 section. But I've got a few questions about this method.
First off, how safe is this from start to finish? I'm by no means new at the whole installing custom roms thing, but there have most definitely been times on all three of the devices I've installed roms on (Nook Color, Milestone, Transformer) where I've gotten a non-booting device that was fixed either because it was so easy to just go into CWM or RSDlite and flash a new rom or revert to stock. Doing anything (I'm not even rooted yet) on my XT860 kind of scares me, because we don't have an sbf or anything. This method seems like its the closest thing we've got, but new things are scary.
Secondly, I read somewhere that ICS uses a different kernel than GB. Would this method be able to deal with that or are we boned (i.e. stuck with the GB kernel and hackarounds) until Moto randomly decides to unlock the bootloader and we can rewrite everything?
And lastly, we can root on bell now? Last time I'd looked into it, I seem to remember flashing firmware from another country and without an easy way to get back to stock, that kind of killed it for me.
Once again, sorry that some of this is kind of off topic, its just kind of hard to know where to read while we're piggybacking on the droid 3 forum.
Tyfighter said:
Maybe this is the wrong place to ask, but XT860 threads are few and far between in this droid 3 section. But I've got a few questions about this method.
First off, how safe is this from start to finish? I'm by no means new at the whole installing custom roms thing, but there have most definitely been times on all three of the devices I've installed roms on (Nook Color, Milestone, Transformer) where I've gotten a non-booting device that was fixed either because it was so easy to just go into CWM or RSDlite and flash a new rom or revert to stock. Doing anything (I'm not even rooted yet) on my XT860 kind of scares me, because we don't have an sbf or anything. This method seems like its the closest thing we've got, but new things are scary.
Secondly, I read somewhere that ICS uses a different kernel than GB. Would this method be able to deal with that or are we boned (i.e. stuck with the GB kernel and hackarounds) until Moto randomly decides to unlock the bootloader and we can rewrite everything?
And lastly, we can root on bell now? Last time I'd looked into it, I seem to remember flashing firmware from another country and without an easy way to get back to stock, that kind of killed it for me.
Once again, sorry that some of this is kind of off topic, its just kind of hard to know where to read while we're piggybacking on the droid 3 forum.
Click to expand...
Click to collapse
Yes we can root, there is no need to flash any other countries fastboot files as long as you are on bell 2.3.6. While bell doesn't have a fastboot package yet(sbf) if you borked your device you can use motofastboot to flash just /system from the fastboot package of another country, and then restore a backup, thus everything stays bell stock.
The best advice is to use safestrap and only flash the safemode. You should always be able to get into CWR with safestrap
And yes we are stuck with the GB kernel for now, which is part of the reason developing ics roms has been so painful
Sent from my XT860 using xda premium
This process does not work for me...
When I load SafeStrap 1.08, I get Recovery State: Not Installed
I try and click the "Install Recovery" button and it goes through a process (preparing something, obtaining root, etc) but the Recovery State never changes
I have an XT860 from Bell (2.3.6) that is running on Rogers (unlocked).
Root works fine for TiBu and Root Explorer....The SuperUser entry for SafeStrap lists allowed and logs a whole bunch of "granted".
Any thoughts?
Caz666 said:
This process does not work for me...
When I load SafeStrap 1.08, I get Recovery State: Not Installed
I try and click the "Install Recovery" button and it goes through a process (preparing something, obtaining root, etc) but the Recovery State never changes
I have an XT860 from Bell (2.3.6) that is running on Rogers (unlocked).
Root works fine for TiBu and Root Explorer....The SuperUser entry for SafeStrap lists allowed and logs a whole bunch of "granted".
Any thoughts?
Click to expand...
Click to collapse
Perhaps you don't have su binary properly installed. I've had this happen with bootstrap. Check that you have su in both /system/bin and /system/xbin
Sent from my XT860 using xda premium
Close...it was busybox. It was present, but borked. Nuked and reloaded..problem fixed.
Many thanks to hashcode for the pointer to busybox being most likely.
Sent from my XT860 using xda premium
Caz666 said:
Close...it was busybox. It was present, but borked. Nuked and reloaded..problem fixed.
Many thanks to hashcode for the pointer to busybox being most likely.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Now that you say that I remember someone else having the same issue and it turned out to be busybox. I had nearly the same problem with the bootstrap and it ended up being su missing from xbin
Sent from my XT860 using xda premium
OK I tried this and it works perfectly. Thanks man. This is what I needed.
Finally got around to trying this. I'd been in the middle of a move with my pc in a box, but now I've got ICS fully up and running (save for the whole camera thing). Panicked halfway through when I got into a bootloop, but then I wiped everything (forgot the cache the first time) and then everything worked.
I got wifi tether working with the app that was included in the rom, but have any of you had any luck with doing it natively through the settings? I only ask because being able to trigger it from the status bar would be pretty sweet.
edit: did some looking around and it looks like maybe its an issue with shoehorning GSM into a CDMA rom. At least that's the feel I've been getting, I'd love to be wrong.
Thanks for this thread! I hadn't realized there had been developments for the XT-860.
I had unlocked (for use on the Fido network)/rooted my phone and it was working great, then the OTA update from Bell came and I installed that. Now, I seem to have lost root privileges (I guess, obviously).
So, I guess I'm pretty much back to square one.
I would love some advice on how to proceed! I'm thinking of following your directions, and am interested in recommendations for which ROM to install.
What is the problem with the camera with ICS? I use the camera on our phone pretty often so I want a ROM that doesn't break it. Does anyone have some links to some good ROMs to try that work with the XT-860?
twitchcity said:
Thanks for this thread! I hadn't realized there had been developments for the XT-860.
I had unlocked (for use on the Fido network)/rooted my phone and it was working great, then the OTA update from Bell came and I installed that. Now, I seem to have lost root privileges (I guess, obviously).
So, I guess I'm pretty much back to square one.
I would love some advice on how to proceed! I'm thinking of following your directions, and am interested in recommendations for which ROM to install.
What is the problem with the camera with ICS? I use the camera on our phone pretty often so I want a ROM that doesn't break it. Does anyone have some links to some good ROMs to try that work with the XT-860?
Click to expand...
Click to collapse
Use zergrush to root 2.3.6. Picture camera works in ics but you can't record or view video. There's some good gb roms. Give me a few and il shoot you some links
Sent from my XT860 using xda premium
Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.
Bell SBF available at the following URL:
http://sbf.droid-developers.org/umts_solana/list.php
ncho2233 said:
How to install a custom rom (eg. CM9, Ice Cream Sandwich, Liberty, Maverick, SteelDroid) to a Bell XT860 without losing the ability to revert to stock later.
Click to expand...
Click to collapse
If there was any interest at all I would have just made a 100% stock bell 2.3.6 that you flash with CWM and then remove the recovery to be 100% stock but the deodex version seems to be good enough, especially to get a phone with a physical problem past bell/motorola reps. I'm downloading and mirroring that bell sbf right now, very nice find pfak! I made a new thread since you didn't but just linked to your post.
twitchcity said:
Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.
Click to expand...
Click to collapse
There are many roms on this part of the sub-forum, just look around or try a search with [ROM] as your query (might not work so hot in the d3 dev subforum )
I
twitchcity said:
Starting the process now. Can someone please send me a link or two to a good ROM for the XT-860?
I would prefer ICS (I want Chrome on my phone), but if that causes to many problems, a GB recommendation would be fine.
Click to expand...
Click to collapse
Willis111 said:
If there was any interest at all I would have just made a 100% stock bell 2.3.6 that you flash with CWM and then remove the recovery to be 100% stock but the deodex version seems to be good enough, especially to get a phone with a physical problem past bell/motorola reps. I'm downloading and mirroring that bell sbf right now, very nice find pfak! I made a new thread since you didn't but just linked to your post.
There are many roms on this part of the sub-forum, just look around or try a search with [ROM] as your query (might not work so hot in the d3 dev subforum )
I
Click to expand...
Click to collapse
I have a number of xt860 adapted roms on my computer. Give me a few days to contact the devs and such and I'll see if I can get a stickied thread with xt860 ready roms to make it easy for new comers. Also willis, ignore my other post to you, I'll include that info in aforementioned thread if I can get it going
Sent from my GT-P5113 using xda premium
Endoroid said:
I have a number of xt860 adapted roms on my computer. Give me a few days to contact the devs and such and I'll see if I can get a stickied thread with xt860 ready roms to make it easy for new comers. Also willis, ignore my other post to you, I'll include that info in aforementioned thread if I can get it going
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
You can just use one of the patches (small xt860 patches) to get any rom working on our phones as far as I know.
pfak said:
Bell SBF available at the following URL:
http://sbf.droid-developers.org/umts_solana/list.php
Click to expand...
Click to collapse
thank you for this it will help a ton of peeps
It's been awhile since I did anything much with my phone and so I am a bit out of date on what is available these days, especially with the Bionic, I could use a little advice and some recommendations. I used to be into phone modding big "back in the day" with my DX but not so much anymore.
Firstly, I am not a nub and I spent a few hour's online reading before deciding to post anything so I am not trying to be spoon fed here, but I am a bit stuck here and I am not sure what to do. Anyway, I got the phone with 886 and rooted it, installed my stuff and have been using it since. Been having some issues with the phone (still do) so I decided to update it. I made backups via clockworkmod and did the forever root (where you edit with SQL editor) and ran the official update. The OTA said I would be getting 902 however after it installed I was on 893, so I assume I needed to be on 893 before I could go to 902, however when I try to go to 902 I get failed update.
I have tried two ways of updating.
1a. Updating to 902 from phone
2a. Updating from stock recovery using the 902 update file, named Blur_Version.5.5.893.XT875.Verizon.en.US.zip
1b. When updating from phone it downloads, "installs", phone reboots to "update failed".
2b. When installing update from stock recovery I get "package verification failed bla bla myverizon.apk".
So, I figured it was apps and such I either removed, froze, etc. I unfroze and restored any stock apps and still myverizon.apk failed. I read online about putting myverizon.apk in /system/apps however that did not work.
My goal is to keep my phone as is, I cannot really afford to reset it at this time. I feel what I need is the proper myverizon.apk file and someone with more knowledge than myself to tell me exactly what to do.
Any help is greatly appreciated and thank you in advance.
Go here and use Timmy10shoes files if needed...http://androidforums.com/bionic-all-things-root/480176-how-flash-5-5-893-5-9-902-rsdlite.html
Thank you but this does a full wipe, I am just trying to update to 902.
This will get you to 902 and Timmy10shoes file will prevent a wipe of the sd card.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A