[Q] Stuck with older custom rom - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

So, around April-ish last year I rooted my At&t galaxy note 3 and installed safestrap, then alliance rom. I wanted to find a ROM I liked, then just sort of stick with that so I didn't have to monitor development updates about my phone and all that. The only problem with the ROM was that it had a memory leak so bad that I had to reboot about 3 times a day or else the memory would get all used up and the phone would freeze. For some reason, I didn't think it would bother me that much- the phone boots quickly and I was so fed up by then I didn't want to try anything else. I figured that if I ever did want to go back to stock (and I do now), that I had my stock ROM backed up to one of the extra slots that safestrap gives you. Well, I looked- turns out I don't. I checked my external hard drive and found a backup folder with "TWRP" in it, and in it a folder called stock -1970 -04- 02. I placed that folder in the corresponding TWRP folder on my phone's extsdcard, but safestrap doesn't see it in the restore screen. Does it have to be a zip? I totally forgot all this stuff; I haven't messed with my phone in half a year.
If that doesn't work, I'd really be cool with wiping everything and flashing a stock ROM build. I don't know where to find one though, and it should be mentioned that my Alliance ROM build has "MJ5" in it somewhere, if that means anything.
I've rambled a bit, but hopefully someone can point me to my best options.
Thanks!

Use Odin to flash the file with "home" in it from this thread.
http://forum.xda-developers.com/showthread.php?t=2838117
It will load the latest stock firmware. You can re-root with towelroot.com
The "home" file doesn't wipe anything so your apps will be intact. If you want a full wipe and install use the other 4 files in that thread.

Thanks
Worked like a charm, thanks!

Related

[Q] Rebuilding my replacement Captivate

I just replaced my Captivate with a refurb from AT&T. FWIW... the guys at the warranty replacement center were very nice and knowledgeable. I have everything backed up with TiBu, moved my pictures off and all that.
My old phone had existz KB1 kernal and of course voodoo file system. Should I put this phone in the same state before I copy pictures back and restore apps? I'm wondering because voodoo as I understand it converts the file system from RFS to whatever voodoo is. That would mean my backups have been converted too.
Also, exixtz kernal is KB1 and this phone came as KB2. Any problem reapplying that kernal which I was very happy with?
I did all this stuff so long ago I've forgotten all the little stuff!
No, shouldn't be a problem. The only difference in KB1AND KB2 is the kernel and modem. But, you have to root first. Here is what I'd do.
Root
Odin flash a kernel with CWM(I used a speedmod kernel)
Flash the kernel of choice from recovery
Restore your backup.
Converting to ext4is up to you. Your back up is not dependent on using rfs or ext4.
Thank you sir! Where in north GA? cold today isn't it.
Dalton area. And yes it is.
Bad start... it won't root
I've Super one click in the past but no go now... just waits for device
helps to put it in debugging mode
dumb question... I've never restored a tibu back up... I have the backup on my pc... where do I put it. Also tibu is complaining that I won't be able to restore due to "allow third party app" not being checked in applications but there is no where to check that?
Need Superoneclick to enable non market/3Rd party apps.
Put the folder labeled Titanium Backup on your internal SDcard. Open TiBu, menu/batch/restore missing apps.
I'm mostly posting these things now in case someone else is in the same boat I am and has to go through this.
Superoneclick worked. I was a little surprised I needed it as my old phone had this enabled from ATT.
Restored most everything although TiBu died 4 times. The only thing that did not restore right was Beautiful Widgets. Fought that. Still not completely right as I can't find the same widget I had for style... FWIW.. I had 93 apps... took over an hour. I now understand the paid version if I was a heavy ROM flasher.
I enabled 3e recovery with no sig required via Truesselo's method. It worked great.
Bluetooth re-paired without requiring a password... I thought that was odd.
Had to re-enter my wireless password. Expected that.
Still evaluating whether or not to reapply Plumb Bob's GPS fix.
Still haven't updated the kernal. A reply above recommended SpeedMod but that looks like an i9000 kernal.
All in all dinked around about 4 hours with it... much of it trying to remember what the heck to do and how to do it.
CWR won't work now... What to do
I've rooted and restored. Along the way I also ran Truesello's (sp?) 3e signature fix as I had done that before with no problems.
Today I was going to flash something and it booted into recovery 3e but it os blue, I thought it was orange before.
I selected reinstall packages and I get this error
E: Can't open /mnt/internal_sd/update.zip Installation aborted.
I'm just trying to get to where I can select the zip file I want to use. I know I've done it the past.
help please.
Did you name it"update" or "update.zip". The phone will actually add the.zip part for you. Try renaming it just update.
mrhaley30705 said:
Did you name it"update" or "update.zip". The phone will actually add the.zip part for you. Try renaming it just update.
Click to expand...
Click to collapse
Thanks for your replay... I was thinking I hope mrhaley replies... he seems to know his stuff! I have plumbbob's fix on the phone and was going to flash that. it is named PlumbBob-1.0-CWM-USA.zip. It is not giving me the secondary menus to get there. I don't have an update.zip on the phone. I seem to recall it was for rooting.
Like I said, the only other thing I've done is to run the fix to allow non-signed files.
When I flashed the fix and the kernal last time I was able to navigate and select them.
The old update.zip was to install cwm. On 2e recovery it worked like a charm. 3e was not the same story. You really need cwm if you are going to flash stuff. Custom kernels haves it baked in. I don't have a copy handy, or I would upload it for you. You might try using ROM manager just to install cwm.
or rename everything you flash to update, which can cause problems if you forget to change the name back to what it really is. But, you can't have more than1 thing named update on your internal sd at a time.
mrhaley30705 said:
The old update.zip was to install cwm. On 2e recovery it worked like a charm. 3e was not the same story. You really need cwm if you are going to flash stuff. Custom kernels haves it baked in. I don't have a copy handy, or I would upload it for you. You might try using ROM manager just to install cwm.
or rename everything you flash to update, which can cause problems if you forget to change the name back to what it really is. But, you can't have more than1 thing named update on your internal sd at a time.
Click to expand...
Click to collapse
Well whaddya know... I have a folder on my pc in my Android folder called CW and in it is an update.zip file and directions. Bread crumbs... gotta love'm.
Took your advice and installed it through ROM manager. Aaaand we have PlumbBob... 7/7 and 16 ft accuracy.
Still wondering about flashing the KB1 kernal over KB2 though... the phone is sluggish. I probably will in a bit though.

Some Pointers Please on Flashing Original VZW MotoDroid?

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 rom to Bell XT860 without losing ability to return to stock

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

[Q] My method of installing ROMs - unsafe for the Note?

Hello everybody,
First of all: I have rooted some devices before, often in very bad conditions (Softbricked ones, simlocked and branded ones et cetera). However, all of them were not mine.
My smartphone is the Samsung Galaxy Note w/o branding or simlock but with the original Samsung software.
There wasn't really a reason to root my phone up to the point when it broke down (ergo: Shut itself down, reinstalled everything) on one day a few months ago, since that day, my phone has got a really, really bad battery life, apps are destroyed and it is pretty slow. Built-in obsolescence, as I won that phone when it was released, so I got the earliest version.
Because of this, I want to root dat phone and install dat cyanogen-shizzle.
All the phones I rooted before were rooted with my untested and never-recommended method of rooting it with a exploit on the phone, putting up clockworkmod via rom manager and then flashing cyanogen. Sometimes the phone was going crazy, but it always worked, every phone is working way better than ever before.
However, I read some real horror-stories about hardbricks on the Note as Samsung did some really bad work as always. (My next phone will be a Nokia Lumia anyway.)
So, what I wanted to ask: Can I root my phone and then install clockworkmod via ROM manager and then install the ROM via Clockworkmod without being exposed to an enormously high risk of a hard brick? My phone is currently on Android version 4.1.2.
I checked the phone with "Got Brickbug" and yes, I'm having it.
Any help would be appreciated
Thanks in advance,
M24o (No, this name is not inspired by a weapon..)
Best, easiest and hassle free way to get root and custom recovery is to download the philz kernel (the one corresponding to your ROM):
http://forum.xda-developers.com/showthread.php?t=1901191
you can do wipe, flash any custom rom, backup, restore and many more things on this.
Edit: download the zip file, put on ext sd, go to recovery select install zip from external storage, choose philz .zip file and that is it.
treacherous_hawk said:
Best, easiest and hassle free way to get root and custom recovery is to download the philz kernel (the one corresponding to your ROM):
http://forum.xda-developers.com/showthread.php?t=1901191
you can do wipe, flash any custom rom, backup, restore and many more things on this.
Edit: download the zip file, put on ext sd, go to recovery select install zip from external storage, choose philz .zip file and that is it.
Click to expand...
Click to collapse
Thank you, I've just read the thread, what I really like about it is that I can flash it from the phone. Thanks alot for this, those threads are the ones I am always looking for hours (and then find them) to make rooting bearable for my.
Thank you!

[Q] Avatar rom (CM10.1) for Droid 3 questions

Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
apefist said:
Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
Click to expand...
Click to collapse
Do you have a sim card in the phone? This was an issue with some Jellybean/ICS roms. It happens to me as well. For some reason when placing a sim card in the phone(it doesn't need to be active) it allows your phone to get reception.
pandam00nium said:
Do you have a sim card in the phone? This was an issue with some Jellybean/ICS roms. It happens to me as well. For some reason when placing a sim card in the phone(it doesn't need to be active) it allows your phone to get reception.
Click to expand...
Click to collapse
Hey,
So this actually worked, thanks for the heads up!
step by step
apefist said:
Hello everyone,
Not quite sure where else to put this, but I can't reply in the android dev thread since I am a new member.
I flashed (using SafeStrap 3.05) the newest stable Avatar rom for D3 (using CM 10.1 and android 4.2.2 I think) and it booted ok, mostly everything seemed to work fine (except for camera but that seems to be expected) however I have absolutely no cell service. Not even just data, but the basic cell service for texts and calls isn't on. I tried doing the Verizon activation call, but it would tell me to turn airplane mode off, (which I did, but it either seemed to turn itself back on or not matter if it was on or off anyways).
Has anyone else had this problem and has a work around for it?
Thank you
Click to expand...
Click to collapse
Hey, Glad u got your issue resolved..
i am getting my first Android phone (Droid 3 XT862 Gingerbread 2.3 ) and i want to install a custom rom the same way u have..... i was wondering if you or anyone else on the forum could give me step by step guide on how to go about installing the custom rom with the ability to revert back to my original stock OS wen i need to......
i had posted a thread here http://forum.xda-developers.com/showthread.php?t=2378162 and i got some good advise so far:
you or anyone here could reply with the instructions i need or at least send me a link to a tutorial .... as i said this is my first Android so i really dont want to make any mistakes while doing this..
THANX MUCH !!!!!!!
Tha slayer said:
Hey, Glad u got your issue resolved..
i am getting my first Android phone (Droid 3 XT862 Gingerbread 2.3 ) and i want to install a custom rom the same way u have..... i was wondering if you or anyone else on the forum could give me step by step guide on how to go about installing the custom rom with the ability to revert back to my original stock OS wen i need to......
i had posted a thread here http://forum.xda-developers.com/showthread.php?t=2378162 and i got some good advise so far:
you or anyone here could reply with the instructions i need or at least send me a link to a tutorial .... as i said this is my first Android so i really dont want to make any mistakes while doing this..
THANX MUCH !!!!!!!
Click to expand...
Click to collapse
Hey, so this was my process.
First, I made sure that the stock software on the phone was up to date. I did this since that way if you have to go back to stock, you are on the latest version, and you can confirm that you are using the correct rooting application. The root tool I link to below will work on 5.7.906 which I believe is the latest.
Second, root your phone. You will need to go HERE to download the tool. Follow the instructions on the page, and it should go fine. The phone will reboot several times during the process, this is normal. Once the program says it is done, you can go check for the Superuser application in your app drawer (it might be SuperSU or something similar, I can't quite remember).
After you have root access on your phone download the safestrap application for Droid 3 HERE. Make sure you get the one that is specifically for Droid 3. Transfer that file (should be called Droid3Safestrap-3.05.apk) onto your phone.
There are a few ways to transfer files onto your phone. You will also need to do this later to transfer the .zip of whatever ROM you decide on). If you have a micro-sd card that you can put into your computer, that works. Or, you can have the phone on and plug it into the computer and transfer it that way. I believe you can transfer to either the micro SD or the internal memory. I prefer micro SD since you might want to wipe the internal memory to fix things or switch ROMs.
After the .apk is transferred find where you put it using a file manager (I personally use Root Explorer but I think Astro or stock will work), and install it. Go to the new app and run it and it should request root access, which you grant, and it should flash the recovery.
Once you have the recovery installed you can install whatever custom ROM you want, pretty easily. Safestrap is great because even if you screw up the ROM somehow, you can always just boot back into Stock.
Here is where you'll have to chose what custom ROM you want. Now as far as I know, the Droid 3 is fairly limited in its ROM selection. It does have a Cyanogen Mod 10 version, but it is not a stable version and in my experience, doesn't run super great. If you want to try Cyanogen Mod 10, I actually suggest you get the Avatar Rom variant HERE, but keep in mind that apparently you do need a SIM card inserted for the cell signal to work at all. Overall it did seem to run fairly choppy but they are still releasing newer nightly versions (July 20th was the last) so it might have gotten better. One thing to know about these ones is that the camera does not work at all, so if that matters to you just skip these.
Now those two (CM 10 and avatar) are ROMS that will bring the droid 3 up to Android 4.2 Jellybean. If you don't care about getting up to the latest version (Jellybean actually isn't the latest anymore but still pretty darn close), then there are a few other Gingerbread ROMS out there that work a bit better.
HERE is a list of a few other droid 3 ROMs, my favorite Gingerbread one that worked overall really well and stable was Steel Droid. Otherwise, you can just look around and see what's available or what other people are suggesting. Choose your ROM (or several, it's fairly easy to install them so try a few!), and download it. You should get a .zip that is approx. 150-170 MB in size. As an aside you will probably also want to download the corresponding GApps package HERE and put that on the SD card as well. I think some ROMs have that included, but if you boot into a room and it doesn't have the Play store installed, you need to go back into safestrap and install the GApps package over it. You don't have to delete and recreate the rom slot, just go back into install and install it over. When I say corresponding, the different packages go with different versions of Android so for example the one labelled 20110307 would go with Android 2.3.4 which is Gingerbread, the version that Steel Droid uses.
For whichever one you choose, the install process is mostly the same. Reboot your phone, and after the Motorola Logo comes up, you should see the Safestrap splash screen. To get into the recovery menu you have to hit the "Menu" soft-key (the one all the way on the left) within 10 seconds so keep an eye on it.
From the recovery menu go into "Boot Options" You should see 5 options, rom-slot 1-4 and Stock. When you want to switch what ROM you are booting you select on the corresponding slot, and hit activate, then you can reboot through the menu option and it will start that ROM.
To install you will go into "Boot Options" chose whichever rom slot you want (most likely #1). You will have to create that slot, which can take a few minutes. After the slot is created, back out of boot options, and go to "Install". Find the .zip of whichever ROM you chose, and select that to install, and then you can install the corresponding GApps package.
After the install is complete, you can reboot (make sure it says rom slot 1 is selected up to), and it should boot into the Setup process of the ROM. If you ever need to go back to stock, just reboot, go back into Safestrap > Boot options, activate the "Stock" one and boot into that.
A few notes, if you want to switch ROMs, or install multiple ROMs you can do that using the different rom slots with a few exceptions. The Cyanogen Mod 10 and the Avatar Rom (most Jelly bean ones I think) have to be installed in rom slot 1, so if you're doing those and another like Steel Droid, put the Jellybean one in rom slot 1 and the Gingerbread on in rom slot 2. Also if you want to install a different ROM, it's generally best to just completely erase the rom slot and recreate it, then install the different ROM in the newly created rom slot. You can always create backups with Safestrap and restore them with Safestrap. Oh and make sure your phone has a decent charge before doing a lot of the safestrap stuff (I would say at least 60%) you can also have the phone plugged in while doing this stuff, but I'm not always confident it is charging so try and get it charged up before hand.
Finally, if you ever mess up to the point where you're worried that you broke the phone, (boot loops or it is stuck on the Motorola Logo) you can download this restore tool HERE. This should completely wipe and restore the stock software on your phone. It will bring it back one version previous though, so be sure to go through the standard update process to bring it back to 5.7.906 so that the root tool will work. This tool has saved me a few times and is pretty easy to run.
Sorry, I know that is a lot of stuff and looks pretty scary. It really is just a few steps that you should research and make sure you are comfortable doing.
1: Get Root access on the stock software on the phone
2: Install safestrap and flash the custom recovery
3: Boot into recovery and install whichever custom ROM you want
If you have any questions feel free to ask!
Much appreciated !!! ..... i will try these steps as soon as i get my phone..... hope it doesnt make a difference if my D3 is an unlocked GSM phone because all service providers in my country uses GSM
Tha slayer said:
Much appreciated !!! ..... i will try these steps as soon as i get my phone..... hope it doesnt make a difference if my D3 is an unlocked GSM phone because all service providers in my country uses GSM
Click to expand...
Click to collapse
if you are using gms you may need Rom version with a modified build prop, most of the roms threads will have a modified version for GMS, in the OP or somewhere in the thread. if you can't find it just ask in the original rom thread
also some good how to videos here https://sites.google.com/site/tomsgt123/all-videos/videos-page-4

Categories

Resources