Related
Okay, I'm really on the fence here. I've got ADB working, I've read the warnings, I've flashed my previous WinMo phones about a hundred times. I am also getting annoyed at the missing market apps and the incredibly awful 3G uplink speed of the 2.2 test build in my area. My phone looks in no way shape or form likely to crap out, needing the warranty. So the round is in the chamber, hammer is cocked, finger is on the trigger.
Only thing holding me back is the idea of the official 2.2 update coming out tomorrow (or really any point in the first half of the week), and having to reverse everything I did (unlocking aside, I get that it's permanent, for now at least). Which all revolves around extra work. I'm not looking to flash other ROM's at the moment, just get access to tweak a few things.
So...3 questions
1) Since I'm just going to root the stock ROM, and edit a few things in build.prop, do I need to disable the online app and info backup? I'm 99% sure I read somewhere that unlocking the bootloader wipes the phone, but that's not a concern as I could just let the thing boot after unlocking it and pull my info from the cloud. This is for AFTER I root (though if you're responding, you probably already know that).
2) Any way to backup a complete system image, so that I can revert to that when the official 2.2 comes out?
3) Which SU/Rooting method do you, the knowledgable and expert [insert additional groveling] reader, suggest for FRF50? I've seen Cyanogen's and the one on Modaco ( http://android.modaco.com/content/g...-erd79-frf50-superboot-rooting-the-nexus-one/ ) I'm guessing this is a "doesn't matter," but I figure why not ask.
Was this the wrong section for this kind of thing?
I'm no expert, just have had my n1 for a couple of weeks but:
1. Can't help you there, no idea, sorry.
2. nandroid backup.
3. I've read a lot about this and I'd go with Cyan's method and amon_ra's recovery. It seems like they do the job well. Plus if you search around, you'll see instructions on going back to stock recovery from amon_ra's, but I'm not sure about the other recovery image (or whether it would be the exact same procedure)
1. I really don't understand the struggle here. Why you would want to disable app backup in the first place? It's not like Google is persecuting people who unlock bootloaders that they might cut you off if they see you're rooted. Just leave it running so you don't have to install everything manually. Unlocking does wipe everything, so it'll be convenient.
2. Well yeah... Make a nandroid the way your phone is now and go back to it whenever you like. And if you like, you can restore just the system.img from fastboot.
3. I prefer the cyan method with .34 kernel. There were some people complaining that Froyo was really slow for them, but I haven't noticed that at all.
^
1) Was because of things I've read, that if you do X, you should turn off backup syncing to keep from screwing things up. I certainly have no desire to turn it off. I love it.
2)Thanks.
3) Thanks
EDIT: Done. That was stupid-fast. From installing the fastboot drivers to installing SU was 90 seconds. Add 20 more for AmonRa's recovery.
Titanium backup installed.
build.prop edited to allow protected apps and fixes to the missing ril info.
Glad it turned out okay!
I'm so glad to be rid of Twitter!
Thanks you for your input.
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
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
i've searched for days on trying to understand how to root the Vivid and still not sure if i've done it correctly.
devices i've rooted or think i've rooted b/c i installed custom ROMs:
- htc aria
- htc inspire
this is something completely different.
none of the threads seem to be clear and concise giving step by step instructions for installing custom ROMs. many abbreviations and skipped steps. i will attempt to be very detailed in what i've done thus far. i understand even the slightest detail is important when having inquiries on forums.
when attempting to root, used Vivid_All-In-One_Kit_v1.2
this assisted in unlocking boothloader (this term is still hazey to me)
now i'm thinking... because the bootloader is unlocked, i can get into recovery, which i can. for some reason, had a problem with completing step 6, so i dont know if i'm 'permanently' rooted or not.
with aria and inspire, i used this recovery section to install (note: is install and flash used interchangeably?) custom ROMs. however, i didnt manipulate any 'kernels' to do so (unless it was autoManipulated in the installation of the ROM. now this kernel thing is the reason why i'm writing this post.
i'm attempting to install holiraider_final_4g.zip (hasnt finished downloading yet).
this thread: [ROM][03/06/2012] HoliRaider FINAL - Sense 3.5 /APM/Beats/DSPAudio/Amaze/Bravia, gives files, but no instructs.
so my questions are
- if the bootloader is unlocked, and i can access recovery menu, am i rooted?
- is install and flash used interchangeably?
- to use the holiRaider ROM, must i install/flash the kernel shown in thread?
- if kernel is needed, when is it installed/flashed (in reference to the steps in installing/flashing ROM, ie: install ROM first, then kernel or vice-versa)?
- in lamens (noob, for dummies, etc) terms, what is CRT on/off?
- when is 'RestoreCRT_Animationfor_final.zip' installed/flashed (step by step)?
if more info is needed i'll be glad to give it.
also, i've read the 'everyone needs to read this' thread. dont know what happened, but i have no intention of disrespecting anyone who's assisting me.
thanks for any help.
I imagine someone will help more but to answer some of your questions:
You have to flash the kernel for the rom to run correctly or else you will boot loop.
The kernel is flashed first using a command prompt with your phone hooked up to the computer.
To check if you have root you should use titanium backup or another app that requires root. Just getting into cwm is not enough I don't believe.
I believe crt is an animation, either way not crucial for the rom.
Also, read this post for help with flashing the kernel/rom. Slapshot did a great guide.
Hope I helped somewhat.
i've installed titanium backup, it states i'm not rooted.
so now... that's the first thing i need to do before installing anything.
i've unlocked the bootloader and can access recovery menu. how do i go about permanently rooting vivid. the Vivid_All-In-One_Kit_v1.2 doesnt root my phone when using the 'permRoot' button.
any assistance is greatly appreciated.
is there a link to that thread of installing/flashing kernel by slapshot. i will need the information prior to installing/flashing the holiRaid ROM.
also, i remember going to chat room or something of the sort (mIRC i think) and got assistance w/ rooting my htc inspire by attn1. this guy was fantastic. is there anything like that for the htc vivid? he remotely took over my computer and rooted my inspire. it was beautiful.
basically i want bloatware gone. i also want to be able to move every app that has the option to move to SD to move to the SD (adobe flash player, nfs shift, adobe reader, etc...).
http://forum.xda-developers.com/showthread.php?t=1416836
Sorry, forgot to post the thread.
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