So I'm trying to root my friends hero and install a 2.2 rom since her stock 2.1 is really slow and freezes a lot. But the whole process is so different from when rooting my Epic 4g and I'm completely lost! Is there anyone who can simplify the instructions for a dummy like myself please! Lol
I'm pretty new to this and just went through rooting and installing the new Gingerbread (2.3) ROM this last weekend. Very happy with it and it's been stable and fast. If you still want to go 2.2, the backup and rooting should still be the same. Here's what I did while it's still fresh in my memory.
Step 1
Before doing anything make sure to back up data from the SD card like pictures and music. Also back up the call log and SMS.
http://android.riteshsahu.com/apps/sms-backup-restore
http://android.riteshsahu.com/apps/call-logs-backup-restore
You will also need to install HTC Sync, the Android SDK, and USB drivers to your computer, because you may need to fall back on it for several steps, or fix any mistakes.
http://developer.android.com/sdk/index.html
http://www.htc.com/us/support/hero-sprint/downloads/
Step 2
Rooting - the Z4 method is supposed to be easier,
http://forum.xda-developers.com/showthread.php?t=833953
but this is the one that worked for me.
http://forum.xda-developers.com/showthread.php?t=804296
Step 3
Once you do have root, install a recovery and Nandroid your current settings to have a working install you can return to if need be. I used ClockworkMod and updated to version 3 for Gingerbread, the regular 2.5 version should work for Eclair (2.2) ROMs.
ClockworkMOD, start with ROM Manager from the Android Market. You can flash CWM right from the ROM Manager and then tell it to reboot into Recovery so you can do the backup and flash the new radio and ROM.
Taking ClockworkMOD to 3.0.0.5 for GB
http://forum.xda-developers.com/showthread.php?t=929628 (Method II worked for me)
http://romrepo.info/wiki/index.php?title=Flash_the_ClockworkMod_Recovery
Step 4
Flash your Radio
http://forum.xda-developers.com/showthread.php?t=853868
Step5
Next you can install the ROM you've chosen. You'll have to download and copy into the root of your SD card so the Recovery softward will find them.
Eclair 2.2, find the ROM you like. I chose 2.3 so I can't really help you here. You may want to try out the Cyanogen Froyo.
http://forum.xda-developers.com/showthread.php?t=755795
Here's some Froyo install instructions.
http://forum.xda-developers.com/showpost.php?p=7564841&postcount=34
ASOP Gingerbread 2.3
http://forum.xda-developers.com/showthread.php?t=864403
Step by step 2.3
http://romrepo.info/wiki/index.php?title=Main_Page
Also, don't forget the Google Apps
http://romrepo.info/wiki/index.php?title=GApps_Info
and Sprint Visual Voicemail (VVM)
http://romrepo.info/wiki/index.php?title=Install_Sprint_Visual_Voicemail
From there, you can do other mods like themes, play with CPU speed, download all the apps you use, and restore the SMS and call logs you backed up earlier.
I can't stress this part enough. Read the instructions that are posted with every step, several times. I spent a couple days familiarizing myself with each step and making sure I downloaded and copied everything I would need to the SD card.
Hope this helped, good luck!
Very concise set of instructions. Thanks.
I used z4root to initially root my phone, then I used clockwork to recover with cyanogenmod 6.1 stable. Also make sure you get the google/android Apps (like market and voicemail). z4root was fast and I rooted about 2 weeks ago, so it should theoretically still be up and running.
Sent from my HERO200 using XDA App
Hey all so I currently have an unlocked bootloader, rooted Nexus One still running the Stock Froyo 2.2.2. and I decided to finally upgrade to the OTA Gingerbread update but have a problem.
The OTA update restarts my phone with a triangle with an "!" inside it and an Android next to it, so I decided to try a manual update as described here.
Everything went well until the installation itself, during the install I kept getting some sort of error stating Twitter.apk in the system directory could not be authenticated.
So here's the problem, with Titanium Backup I made the stupid mistake of uninstalling it and not backing it up when I first rooted a while ago. I thought I could just reinstall it from the market but I get the same error. The only solution I can think of is if someone running a Nexus One Stock Froyo could possibly send me the Titanium Backup files of Twitter, hopefully this would make it work, otherwise I don't think I could ever update.
Since your bootloader is unlocked, you can use fastboot to install a custom recovery and then flash whatever you want (including a stock image)...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Since your bootloader is unlocked, you can use fastboot to install a custom recovery and then flash whatever you want (including a stock image)...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Thanks for the response, but I'm having trouble figuring some of this stuff, after spending some time with the search option here in XDA:
1. I don't the difference between custom recovery and flashing an image.
2. I can't find a simple stock Gingerbread image (thought its called ROM?) Details in posts tend to be vague for people that are learning this stuff, like me.
3. Many people have written to use Amron_ra 2.2.1 but I don't know the specifics of each ROM are (ex. if its Froyo based, Gingerbread based, etc.)
4. Would using ROM Manager be a good method to use any ROM or is it limited?
I'm essentially looking for an effective method to upgrading to a clean Gingerbread, since doing it the normal way won't work on my phone (as stated in my first post).
1 - Recovery, bootloader, and 'ROM' are two different partitions on you phone. Once you break security on one, you can use it to break the security on the other. In your case, the security on your bootloader is broken (unlocked), so you can use it to install new software on the other partitions.
2 - See bullet 4 on the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=1005591
3 - For recovery you have 2 choices, Amon Ra or Clockwork, If you go with Clockwork, I recommend you stay away from 3.x versions. Unless the ROM you want to install says otherwise, either of these recoveries will work.
4 - ROM Manger will work. It's an easy way to achieve results, but unless you know what you are doing, it's also an easy way to screw things up.
I suggest you take it a step at at a time, and really understand what you are doing. Reading the wiki is always a good start, then ask specific questions...
http://forum.xda-developers.com/wiki/index.php?title=File:Nexus_One.png
Thanks Danger, I made the jump to Cyanogen 7, RC-4 via ROM Manager and couldn't be happier! Only problem is the known audio bug for Nexus One (person on other end of a call hears a lot of static sometimes, and have to recall them). The forced apps2sd is by far my most favourite feature, especially since the N1 internal space is pretty horrible, I've moved most of my apps2sd and haven't had any problems thus far.
Thanks for recommending CM7, I just wish their website listed the full features for newbies like me.
Thanks danger-rat http://www.nexusoneforum.net/forum/...lick-doesnt-work-gingerbread-2.html#post93952
I downgraded my gingerbread to froyo
Was pulling my hair out with a lame guide in the general section
Congrats!!
Sent from my Nexus One using XDA Premium App
Okay ... I have the Samsung Droid Charge and I'm quite comfortable flashing ROMS/Kernels/CWM Odin etc.
My wife has my old original Verizon Moto Droid (stock) and it is starting to act up a little. I'm thinking of flashing a ROM onto it to update things and see if it acts any better.
Like I said; I am comfortable using Odin and CWM on my Charge. What's different with the Droid? What will I need to accomplish the tasks? Is there an Original stock ROM available I can revert back to if things don't work out or she doesn't like it?
It looks like there's a Windows based app instead of Odin? I am running Win7-64 bit on my desktop.
Any pointers getting me headed in the right direction would be greatly appreciated.
MERRY CHRISTMAS !!
Steve
Edit: Understand this is my wife's phone. I need to know what I am doing before I attempt it .... I screw up her phone and it ain't gonna be a Merry Christmas around the Chopstix household ... ~;-p
You could use superoneclick v 1.7 to root it, you can install cwm recovery on it and flash a rom, I would reccomend project elite for its great stability. If anything ever goes wrong you can sbf back to stock
I just Flashed Cyanogen Mod 7.1.0 on my stock OG droid and it rocks. Some pointers that I couldn't find in the rest of the forums:
Like mentioned above, you have to use superoneclick 1.7 (or revert back to 1.6 if the frk76 -the latest update- has put it self on the phone)
I used "mybackup root" (free in the market) to back up my apps and data (messages, call logs, pictures, and music). Worked great.
I logged into my google account to back up contacts, calendar, etc. Also worked great.
Here is the part that everyone has a problem with: Rom Manager.
The stock ClockworkMod Recovery (2.5.0.1) in Rom Manager does not work for the OG Droid. I was able to get it to work though by going to "All ClockworkMod Recoveries" at the bottom on the Rom Manager screen and flash ClockworkMod Recovery (3.1.0.2).
After that it was smooth sailing. Remember to perform a Nandroid Back up, do a factory reset/wipe data, and what ever else the ROM you are installing suggests you do. I had to do a recovery a couple of times figuring out that SPRecovery won't work for Flashing new ROMS.
Hope it works and Merry Christmas!!!
taptaptouch said:
You could use superoneclick v 1.7 to root it, you can install cwm recovery on it and flash a rom, I would reccomend project elite for its great stability. If anything ever goes wrong you can sbf back to stock
Click to expand...
Click to collapse
sbf back to stock ... could you expand on that? I don't know what it is. The Motorolas are obviously quite different than the samsungs when doing this stuff ...
Edit: I am having trouble finding the links for downloading the superoneclick, CWM and the ROM. Odin isn't used on this phone? What will I use to install CWM? Project Elite sounds like the one I would want. Stability is key above advanced tools and eye candy. It's for my wife and it will be used as a phone and messaging only pretty much. Maybe a few pictures. I would want the market and all apps she might want to be still accessible.
sbf back to stock= making a Nandroid backup and recovering it in case there is a problem with your ROM install. Did you do that when you flashed Odin onto your Charge? As long as you have your stock ROM backed up, you can go back to it at any time. This can all be accomplished with CWM.
As far as I can tell, Odin is for Samsung devices only. If this is incorrect, someone please set me straight.
CWM is a utility inside the "ROM Manager" app, which is available in the Market.
Here is the Superoneclick Thread.
http://forum.xda-developers.com/showthread.php?t=803682
I'm just getting started in the custom romming thing, so I couldn't recommend a good bare bones ROM. Good luck in your research!
jgoose said:
sbf back to stock= making a Nandroid backup and recovering it in case there is a problem with your ROM install. Did you do that when you flashed Odin onto your Charge? As long as you have your stock ROM backed up, you can go back to it at any time. This can all be accomplished with CWM.
As far as I can tell, Odin is for Samsung devices only. If this is incorrect, someone please set me straight.
CWM is a utility inside the "ROM Manager" app, which is available in the Market.
Here is the Superoneclick Thread.
http://forum.xda-developers.com/showthread.php?t=803682
I'm just getting started in the custom romming thing, so I couldn't recommend a good bare bones ROM. Good luck in your research!
Click to expand...
Click to collapse
No I haven't used nandroid even though some on Charges do. Odin isn't something you install on your phone. It is a computer based program that you use as an interface between the computer and phone to flash 'tar' files to your phone. ROMS will come in a file format with a .tar.md5 file extension and you use Odin to flash them. There are complete stock 'Odin' ROMS out there that you can use to flash your phone back to stock. This is the fail-safe route I have used when learning to flash that saved me from a few bricked phones. I am leery of flashing her Droid without having the same abilities available to me. A nandroid backup isn't going to do any good if the phone pukes half way through a flash and gets bricked. Or am I incorrect in that statement?
I've seen mention of a windows based app here that I assumed was something akin to Odin. Is there a fail-safe fall back to a stock rom for this phone should you need to recover from a bricked state? I'd hate to flash the wife's phone without knowing going in that I have the ability to recover from a bad flash.
CWM is stand alone on the Charge. You can install it with Odin or other methods such as adb (which I am not familiar with). But getting it through an app is fine too. I would assume there are then zip files available for updating to a more recent version of cwm after a version is on the phone. CWM is also embedded into many ROMs available so that when you flash a ROM via Odin, CWM is on the phone when you boot.
What is the button sequence for entering recovery on the Droid?
Power Key + X on the keyboard.
I assume you have a physical keyboard on this droid.
Don't let these guys scare you off. If you can flash your charge then you should have no problem with an og Droid . I just fixed my sister inlaws the other day . it took me 20 min. Here's a guide anyone could follow . Root Droid 1 - regardless of OS version (driod forums . net ) (I'm not allowed to post the link for some reason) And also I would recommend project elite or cyan 7, both work great.
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
So I've got me an Atrix HD, to use as a PMP, and I've rooted it.
I've spent the better part of the day looking up custom roms, but I'm still not sure what to do.
Basically, what I want to do is have a barebones device, without 100+ services running on startup, no bloatware apps and ****, and etc.
I figure I should be using a custom ROM, yes? Is Cyanogenmod the name of a rom, because it seems to be the most popular, but there's quite a few I see on the XDA forums and I'm not sure what to do.
I have RSDlite on my computer and the Atrix HD stock firmware image, so if I screw up I should be alright since I can use that to put me back at square one, I don't think I need any recovery images on the phone then, but Can anyone give me some steps to achieve a barebones experience on for the device (want to remove all the bloatware, unnecessary background services, etc that come stock on the phone)
Any help is appreciated thanks
If you can find a ROM .img file, you can flash via adb, but it's just easier to use a custom recovery. Try Philz recovery (in dev section). I know some other devices have special ROMS without phone apps, but I haven't seen one for the AHD. Go with the most vanilla AOSP ROM you can find and install a root tool like ROM Toolbox that lets you uninstall system apps. You can freeze the phone app and any other app you don't want. If freezing doesn't mess up the device, go ahead and uninstall (at your own risk, obviously. I nor anyone else on this forum will be responsible if you mess it up). ROM Toolbox also lets you select what processes you want to run at startup. Hope this helps.
Sent From Here