Related
This is a post I wrote for my personal forums nTelosDroid.com, but noticing there isn't a dedicated how to for CDMA Milestones, here it is!
So I posted how to root your Milestone using z4root a few days ago, which can be found here [link]. Now, with this post, I'm going to show you how to Root, ROM, and Restore back to the normal nTelos firmware. So heres the tools you'll need to begin. NOTE: These tools are all available for free! I'll host them for you on my DropBox as well as this server.
:!: WARNING: THIS CAN BRICK YOUR DEVICE MAKING IT COMPLETELY AND UTTERLY USELESS! I, MY SITE, OR MY STAFF, CANNOT BE HELD RESPONSIBLE FOR ANYTHING YOU DO TO YOUR DEVICE! :!:
So, first thing we have to do before ANYTHING else is root or "open" your device. How we achieve this is by installing z4root or Universal Androot. Install the app, follow the directions for z4root from this thread. If you install Universal Androot, once it's installed:
Open Universal Androot
Select Superuser for Android 2.0 ~ 2.2
Don't tick Root Temporary or it'll root until next reboot
Then click Root
If you just want root, stop here. If you want to make a backup and rom your device, continue.
Once you're rooted, exit to your Home screen, check to see if SuperUser was added to your list of apps. If it hasn't try to reroot. Once you see SuperUser, go to the Marketplace and download "ROM Manager" by clockworkmod. This is the tool we need to make a backup and rom the device. Once ROM Manager is installed, run it. You'll be prompted to enable SuperUser permissions. Click Allow.
Scroll all the way down to "Flash Alternate Recovery" which should say SPRecovery 0.99.3b
It'll go through a download process and after that it'll Flash your recovery.
DO NOT PULL THE BATTERY OUT OR SHUT THE PHONE DOWN! YOU'LL BRICK YOUR DEVICE!
Scroll all the way back to the top and Flash the ClockworkMod Recovery 2.5.0.1
It'll go through a download process and after that it'll Flash your recovery.
DO NOT PULL THE BATTERY OUT OR SHUT THE PHONE DOWN! YOU'LL BRICK YOUR DEVICE!
Once everything is flashed and finished, you are now ready to perform a nandroid backup.
Scroll to Backup Current Rom
A Window will pop up and you'll be able to name your new backup.
Once it's named to your liking, click ok. Your device will reboot.
After it reboots into recovery, it'll do a backup process. This shouldn't take more than 5 minutes.
It should make a backup and reboot.
If this doesn't happen, something has failed, pull the battery, reboot into recovery.
Perform a nandroid backup. If that doesn't work, Congratulations! You'll have to sbf! (Google how to do this)
Once this process is finished, you'll have a full backup of your current OS! Now, you can completely stop here and enjoy your nTelos Milestone as "Stock" or continue on to ROM your device.
Open ROM Manager again, and scroll down to Download ROM. Now here's where you have to make a choice. If you don't want to make it a simple easy process, use the free version. You'll have to clear your cache and data in recovery by yourself. This tutorial will not get into that.
Roming is one of those things that if you do it, you will need to know EXACTLY what you're getting into. You're gonna have to setup settings that are hidden in the phone to make things like MMS and Data work. I'm merely showing how to ROM the device, another tutorial will show you how to setup things that aren't working. If you take it upon yourself to write one, please let me know, I'll link to it here.
Once you've downloaded the ROM of your choice, before you do ANYTHING make sure you have a BACKUP!!! Once you have that done, you find the ROM from the downloads section that you want, I chose Bugless Beast (but Cyanogen Mod is another ROM of choice). Once it's done downloading, it'll give you the option to backup your current rom and wipe the data/cache. Select both regardless if you have a backup. It'll go through the backup/install process. Your device will ask you to go through the basic initial setup. If it doesn't, click on the Market and sign in. Once that's done, your data, voice, and sms will be completely ready! If you want to enable MMS (Picture/Video Messages), follow these steps.
Open Voice Dial (NOT Voice Search)
Say in a clear voice "Open APN's". This may take several tries.
Once it's gives you that choice, click it.
You'll see Verizon, tab it, change the name from Verizon to nTelos first
Scroll down to MMSC and enter http://mms.ntelospcs.net
Hit the Menu button (the Four bars next to the House on your device) and click Save
Send a MMS to yourself to test the settings work!
And that's it! You have Rooted, Backed Up, and ROMed your device in under 1 hour! :lol: CONGRATS! :lol: If any thing messes up, you always have your back up. Boot into recovery by pressing and holding X then hitting the power button while keeping X pressed. Go to nandroid and recover from your SD card! Hope this helps!
z4root
Universal Androot
ROM Manager
I hope that this is a help for ANYONE on ANY Forum! Please, feel free to copy/paste this anywhere you feel necessary!
EDIT: For those with LOCKED Bootloaders, there was a post deep in the thread for unlocking them. Here's the quote:
meltwater said:
I have the same issue.
Could the OP of this sticky be updated for Milestone users which have locked bootloaders to point them to:
http://forum.xda-developers.com/showthread.php?p=17569718
Spent ages going in the wrong direction when all I needed was to use OpenRecovery instead.
Click to expand...
Click to collapse
Very Nice
Great job and all of us CDMA a854 milestones thank you. We need more CDMA stuff!
The Apns part didnt work for me. It either won't save or goes blank and reverts to Verizon on reboot. *tried APN manager as well* Also I noticed the marketplace usually says My Apps, but will switch to Verizon if you flash to say Cyanogen 6.1.2., Bugless ,or LFY.It would be great IF we could get developers to have ROM with no APN's so we can add our own.
Thanks again for the guide, nicely done.
icemanak said:
Great job and all of us CDMA a854 milestones thank you. We need more CDMA stuff!
The Apns part didnt work for me. It either won't save or goes blank and reverts to Verizon on reboot. *tried APN manager as well* Also I noticed the marketplace usually says My Apps, but will switch to Verizon if you flash to say Cyanogen 6.1.2., Bugless ,or LFY.It would be great IF we could get developers to have ROM with no APN's so we can add our own.
Thanks again for the guide, nicely done.
Click to expand...
Click to collapse
Yeah man! No problem! As far as APN Manager/APN Backup & Restore. If you just edit the MMSC, do you have the same problem?
Oh I tried APN manager and a slew of others. Still didnt work, editing the MMSC either. There is a way to drop APNs into the Rom before installing.Ipfreelytech made one for me. But if I want to run other ROms it would be nice to have a real fix.
Nice work wish I had it before I began...
icemanak said:
Oh I tried APN manager and a slew of others. Still didnt work, editing the MMSC either. There is a way to drop APNs into the Rom before installing.Ipfreelytech made one for me. But if I want to run other ROms it would be nice to have a real fix.
Click to expand...
Click to collapse
I was actually thinking of making a rom for cdma non vzw milestones
stevgunt said:
Nice work wish I had it before I began...
Click to expand...
Click to collapse
I saw that thread and someone asked for one, figured I'd make one
Tappin' and a Talkin' from my Milestone
Yay Non -verizon Rom!! please make one I'd help test it out
I'm getting the website built at the moment. Started looking at how to's today, but I'll PM you to let you know what's up. Thanks for your interest!
I would be interested in testing as well....
AWESOME
Glad I found this post. I live in Roanoke, VA & my carrier is nTelos. I have been looking for WEEKS on an Android Sense 2.2 rom. I mainly want to just have to option of saving my apps on my SD card. I love Android but WinMo has 1 up on Android with being able to install apps to the SD card.
Good luck & I can't wait to see what you come up with!
I am in Roanoke as well
Will this work for an Alltel Milestone.
As far as I know, this should work on most cdma a854's
From the Milestone
It works with Alltel. I just need to know if I can flash back to my stock 2.1 update 1 nandroid backup from CyanigenMod 6.1.2 without running into problems with the kernel not being compatible. I heard that if you flash between Froyo and Eclair you'll brick your phone because the kernels aren't compatible. Is this true?
Alltel Motorola Milestone A854 / Droid CyanogenMod 6.1.2.
Can't find the sbf for Ntelos
I need help returning my phone to the stock sbf. I rooted my phone, all was well until I started playing with Titanium Backup. I deleted Google talk, and as a result I would get this error "process Google.process.gapps has stopped unexpectedly" I tried several different things to fix it but finally decided to just flash back to the stock ROM/sbf. I used the MILER_X1-00.26.1 (I now know that my build is 00.26.0) that and-developers.com sites for use. The problem is that now I have the Verizon stock info on my phone. It changed the MIN, PRL MEID AND phone number. I get an error on start up that my phone needs to be activated, it places a call that starts off "welcome to verizon, to activate your phone......" So now I have no phone service. I can use the wifi so I have access to everything that has been backed up via Titanium Back up, but as you know that will not contain any system data from the stock sbf. Does anyone have any ideas or am I just prolonging the insurance call for replacement?
Conner85 said:
It works with Alltel. I just need to know if I can flash back to my stock 2.1 update 1 nandroid backup from CyanigenMod 6.1.2 without running into problems with the kernel not being compatible. I heard that if you flash between Froyo and Eclair you'll brick your phone because the kernels aren't compatible. Is this true?
Alltel Motorola Milestone A854 / Droid CyanogenMod 6.1.2.
Click to expand...
Click to collapse
I've flashed from Froyo to Eclair with no issues
Tappin' and a Talkin' from my Milestone
smb1966 said:
I need help returning my phone to the stock sbf. I rooted my phone, all was well until I started playing with Titanium Backup. I deleted Google talk, and as a result I would get this error "process Google.process.gapps has stopped unexpectedly" I tried several different things to fix it but finally decided to just flash back to the stock ROM/sbf. I used the MILER_X1-00.26.1 (I now know that my build is 00.26.0) that and-developers.com sites for use. The problem is that now I have the Verizon stock info on my phone. It changed the MIN, PRL MEID AND phone number. I get an error on start up that my phone needs to be activated, it places a call that starts off "welcome to verizon, to activate your phone......" So now I have no phone service. I can use the wifi so I have access to everything that has been backed up via Titanium Back up, but as you know that will not contain any system data from the stock sbf. Does anyone have any ideas or am I just prolonging the insurance call for replacement?
Click to expand...
Click to collapse
Call customer support. The EXACT same thing happened to.my first Milestone. Tell them you don't know what happened and you want it fixed.
Tappin' and a Talkin' from my Milestone
Moved and stuck.
Root+Overlock rapid method
Android by O2 :
tested today:
UniversalAndroot 1.6beta + Milestone Overlocking 1.48 from Market (free) and rulez
@ cfultz
Is there a chance you could put a brief description of the Sbf wipe / restore method, or maybe a link you know of? I've been digging for a week and all I find are droid 2 & X references. ROM manager decided to not get me back to a recovery / boot loader screen and I am really stuck.
Sent from my Droid using XDA Premium App
**Edit**
Really not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.
**Edit**
Problem fixed, sorry for the interruption.
Looks like custom roms might finally be here for the xt860 (and possibly me863, read Update4 below for more info). Thanks to Hashcode for all the work he's done for all of us building safestrap, porting cm7 and everything, daywalker04 for uploading the Brazil Retail sbf, Endroid for being the first to try it with a normal bootstrap and now I'm confirming it working with Hashcodes newest safestrap(as well as his old ones, I originally tested w/v0.92 and worked my way up to current). I Just booted cm7 off /preinstall.
As usualy, please keep in mind that neither I or anyone else will take any responsibility for anything that happens to your phone through use of these files.
IF/When you enable and disable safestrap remember to format data/cache, causes bootlooping for me if I don't.
Warning, if you do this the way things are now you will not be able to get back to your bell software!! Only do this is you are absolutely sure you know what you're doing!!!!!!!!
You may have to be on the brazillian retail rom for this to work! You can find it in This Thread. You're looking for Fastboot package for UMTS XT860 Retail Brasil. At this point in time you can't get back to bell stock so again, it's at you're own risk!!
UPDATE: Thanks Rick2 for the recovery fix that allows us to swap between safestrap on the fly. Now when I need data I can get it anywhere. Works with Hashcodes newest safestrap (1.06). Go here to thank him and get the patch!
Update2: I've attached a CWM flashable zip that I've used to successfully get 3g working on Liberty and Mavs Rom, it does not work on cm7 but will hopefully work on other verizon based roms. It pushes the stock libmoto_ril.so(from the brazil retail), a new apns-xml.conf and a slightly edited build.prop(just made it en/US). I've had it cause the phone to fc loop if I installed it on an existing rom and didn't factory reset.
Update3: Watching this thread for info about me863 I think but according to that thread a user has flashed the brazil retail to his me863 and is trying to get data working
Update4: I've reworked the data patch to make it more universal. It should work on me863 providing safestrap runs on your phone. The patch will now copy files from /systemorig so you'll be using matching kernel/libs etc rather than using generic xt860 files. It also makes backups of the original files in the same location (just adds a .bak extension). This new patch IS SAFESTRAP ONLY. Huge huge thanks to Adamogle!!! If it weren't for him I'd still be banging my head up against the wall and no one would be using this patch. You may have to format data/cache, I left it out of the patch so everyone can test (if you phone goes into a force-crash loop then reboot and clear data/cache). Once I get confirmation of this working (or not) on the me863 I'll fix the thread again. I've left the old data patch(renamed as fit) as well in case anyone runs into troubles. Still not a cm7/9 patch, if one comes about it will get it's own thread but it works on all other custom roms based on motorola firmware.
if you see this and you're like "yes, finally some progress on the xt860!! Where do I donate???!?!!" You do that on Hashcodes website, it's ALL his hard work, I just basically wrote you a little story and pooled some files together. He really deserves it, he's working around the clock right now on cm9, seriously around the clock. Of course you can feel free to click the "Thank" button on this post if you like using my data patch
1./ Flash Brazil retail sbf from this thread
2./ root with Zerg from this thread. For some reason v3 kept tossing errors, v2 worked first try.
3./ install safestrap or whatever bootstrap (safestrap from Hashcodes site http://hash-of-codes.blogspot.com/
4./ profit (follow the directions to install a safestrap rom
boot recovery
Enable safestrap in options
Factory reset (formats data & cache)
Mounts > format system
Install your rom
Install my 3gfix
Reboot and profit
)
Again, my patch doesn't work on cm7 at the moment. Sorry Hashcode and everyone but I figured we'd be better off shooting for a known working rom. I'll update the post as I and other users test more roms. Thx thing on a spring for providing the patch "template", every time I threw one together and put it on my phone it turned out to be corrupt somehow so I just removed the files from your data fix and shoved in my own.
does it work with me863?
Thanks Willis I'll try that fix tonight. I'll try some of the other custom roms too see if any work. Probably give safestrap a whirl too
Beamed by invisible waves from my rooted xt860
I gotta say after months of watching customs roms and dev for the xt862 this is pretty exciting. Does wifi data work on cm7? I would assume if the issue is just with apn. I know its not the intended purpose but I may use safestrap as a dual boot, run custom roms at home in safe mode and switch back to Brazil retail when I need 3g
Beamed by invisible waves from my rooted xt860
This is awesome.
Great work guys. As soon as this gets a little more stable I'm going to flash it onto my gf's phone, work around these bugs that came in the stock FW.
Awesome. Been looking forward to this day. Not jumping on the train just yet, but I'm sure that once the 3G bug is ironed out, I'll be flashing.
emprize said:
does it work with me863?
Click to expand...
Click to collapse
Try it out, you can always sbf back to stock if it doesn't work.
Endoroid said:
I gotta say after months of watching customs roms and dev for the xt862 this is pretty exciting. Does wifi data work on cm7? I would assume if the issue is just with apn. I know its not the intended purpose but I may use safestrap as a dual boot, run custom roms at home in safe mode and switch back to Brazil retail when I need 3g
Beamed by invisible waves from my rooted xt860
Click to expand...
Click to collapse
Wifi works, I'm pretty sure it is an apn issue. Think I need to find my old framework-res.
From the bell rom? I have that at home if you need
Beamed by invisible waves from my rooted xt860
Did you try this http://forum.xda-developers.com/showthread.php?p=19981520
Beamed by invisible waves from my rooted xt860
Endoroid said:
Did you try this http://forum.xda-developers.com/showthread.php?p=19981520
Beamed by invisible waves from my rooted xt860
Click to expand...
Click to collapse
Yeah, I tried that and the gsm data patch. I'm having trouble adding/editing apns etc, can't join networks because "Your SIM card does not allow a connection to this network" etc. This is with cm7 and liberty. I have liberty on my safestrap now, running. I can get sms, make calls etc, wifi works. I'll firgure the rest out. If I want to go back to stock for data or something I just turn safestrap off and do an advanced restore of my /data partition to my backup from after installing the brazil retail.
I can't seem to make this work willis, i adb pushed those files to /preinstall but i still get constant FC of com.android.phone the only thing that makes it not do that is removing the sim. i'm confused
Endoroid said:
I can't seem to make this work willis, i adb pushed those files to /preinstall but i still get constant FC of com.android.phone the only thing that makes it not do that is removing the sim. i'm confused
Click to expand...
Click to collapse
I was gonna put together a flashable patch earlier but had some things come up and ended up in a hospital waiting room all night(next time I'll bring my laptop >.<). I'll toss it together asap and update the first post as long as I can flash it/it works. I should have mentioned (this is the confusing part) I pushed those files before enabling safestrap so /preinstall was /system if you get what I mean.
For CM7 to work correctly on GSM, I need to edit the init.mapphone_umts.rc file to setup all of the services the right way.
TBH, I never even looked twice at that file because I thought there wasn't anyone using it.
*blush*
Glad to see the XT860 crowd finally get some fun. )
Thanks Hashcode for putting so much effort into it, it's highly appreciated.
We were feeling a little bit left out.
Well, if you can get a version of CM7 working before I start having to study for exams, would be greatly appreciated.
But, if not, I'm sure I'll just divert time from studying to testing.
Sent from my Nexus S using xda premium
Accophox said:
Well, if you can get a version of CM7 working before I start having to study for exams, would be greatly appreciated.
But, if not, I'm sure I'll just divert time from studying to testing.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Changing your phone's firmware before exams is a bad thing... Trust me, I know Mine are starting next week!
Willis, I wondered if such was the case, I had safe system enabled and tried adb push to both /preinstall and /system as I wasn't sure how adb would recognize them in safe system. I also was pushing while in recovery
Beamed by invisible waves from my rooted xt860
danifunker said:
Changing your phone's firmware before exams is a bad thing... Trust me, I know Mine are starting next week!
Click to expand...
Click to collapse
Which is why I have a trusty nexus s
Sent from my Nexus S using xda premium
Hashcode said:
For CM7 to work correctly on GSM, I need to edit the init.mapphone_umts.rc file to setup all of the services the right way.
TBH, I never even looked twice at that file because I thought there wasn't anyone using it.
*blush*
Glad to see the XT860 crowd finally get some fun. )
Click to expand...
Click to collapse
After the little bit of testing I've done over the last day or two with different custom roms it looks like we're(xt860 and me863 users I image) going to have to have (or really really want) a patch we can flash against any custom rom to get our data and sometimes maybe phone up(or to keep it from crashing). Haven't been able to get 3g up (though the 1 method I did not try was to crash the phone through the dev tools in cm7 as was mentioned in another thread) on any rom yet. Phone/text works right off the bat w/liberty, mavs etc etc.
Narrowed down why Safestrap Recovery would only boot if a USB cable was connected on the XT860; it had to do with a line in the init.rc file executed when booting into recovery:
Code:
write /dev/usb_device_mode msc_adb
As well as a line in the postbootrecovery.sh script which accomplishes essentially the same thing, except via an echo command.
Obviously, we could just comment those lines out, but then we're left without adb in recovery without messy changes each time we want it. So, I whipped up a little script that checks if there is a USB connection and if so, run the previous necessary commands to enable adb and if not, then leave them out. End result: Safestrap Recovery is working like a charm now. No more need to worry about tinkering with my phone without a computer nearby to get into the recovery...
I attached the modified recovery.zip, just replace the original one located at /system/etc/safestrap/recovery.zip with the attached one and you should be good to go.
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? I got confused with that.
Afterwards, I dl safestrap once I'm rooted? or should I just dl it and put it onto my phone all at once?
Apologies for the noobness. I'd rather be a noob asking questions than a retard who goes ahead and does things and finds out he screwed up too late.
Rooting is done to get superuser permissions within Android so you can install some advanced apps and modify system files which can all be done from within the stock ROM. Rooting then flashing an unofficial ROM is a little more advanced and something I haven't done yet so I can't help you much there. I'm waiting for something a little more stable since my Droid 3 is my main phone. You can read Hash of Codes site (the developer of ICS/JB for the Droid 3) on how to safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/
To root use Motofail. I know it says its for the Droid 4 but the original Droid 3 root exploit was patched with the latest OTA so we have to use the Droid 4 method called Motofail:
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
DróidScìon said:
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
.
Click to expand...
Click to collapse
My D3 has Maverick as non-safe for daily driver and the latest Hashcode for fun. I find that to be the best combination. Once Hash finishes the camera and JB is working reasonable well, JB will be my DD.
I also have an SGS3, TF300T, and a Spica, all of them rooted.
once rooted, make sure you use safe strap. It makes roms easy to try out before having to settle
Sent from my DROID3 using Tapatalk
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
DróidScìon said:
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
Click to expand...
Click to collapse
Safestrap 1.08 is the 'normal' ssafestrap
Safestrap 1.08e/f/g is an advanced safestrap with extra features like touch etc but not by hashcode
Safestrap 2.10 is the latest which allows the new kernel with the kexec ICS/JB to be used.
2.10 It appears to also work fine with normal roms so i'd use that
DróidScìon said:
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? .
Click to expand...
Click to collapse
If you were stock 906, there was no reason to run the 1-click.exe - that's only for people who rooted their phones and deleted bloatware to get the phone back to stock, or people whose phones are bricked somehow. Coming from stock, just running Motofail was enough to root.
I will concur with everyone here that running rooting, installing and running Safestrap, and installing a custom ROM - and leaving your rooted stock alone - is the best way to go. It will be a lot easier to unroot later on if you want to sell the phone, etc.
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It doesn't matter. Choose which has enough space.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It's asking where to backup TO, like the post above me, choose wherever has space. Backups are about 1GB. You may wish to move it to your computer after if you don't have much space on your device. You can always stick it back on your external sd via card reader if needed, but it's really hard to brick while using safestrap
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Sent from my XT860 using xda premium
I saw that, and before I rooted, I did a Factory Reset on the phone and formatted my SD card. So I have 11+gig free on Internal and 15+gigs on External.
Now, I just need to learn to Flash RoMs (probably more to it than just hitting a button that says flash .zip) and find some info on the "must-have" apps for a rooted phone.
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
DróidScìon said:
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
Click to expand...
Click to collapse
If your contacts are on your google account they will show up.
What other account info do you mean?
You should go ahead and restore contacts. just go to Settings>Accounts and Sync>Google, then turn contacts sync on.
Endoroid said:
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Click to expand...
Click to collapse
I must have made another noob mistake. Everything went well, up until my first startup with the new OS (cyanogenmod9). It has been at the startup screen for over 15minutes right now. I must say, it is one awesome startup screen, with the blue effects and all, but I would love to get to the desktop/homescreen, haha.
If you guys have any advice I would greatly appreciate it. This is a Droid 3, it was rooted a couple hours ago, I did the safestrap as described, created a backup file, etc. My only guess is I jumped the gun by trying this OS on my Droid3 and it may still be under development? FWIW to you, this is the first I've rooted or modded a smartphone in my life, from 0-full speed in a couple hours is what I was shooting for using everyone elses experience.
thanks
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Phibernaut said:
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
thanks. since my last post I used a more detailed how-to, and wiped 3 different areas for data. Now, i had only a black screen (with power, barely lit) and it never even got to the cool blue screen.
I'm currently in safestrap after pulling my battery again, just trying to figure out how to revert back to my standard OS (rooted) and try a ROM like MavRom since it's suppoedly fully capable and stable. I'd love ICS, but I just want a working phone right now
---------- Post added at 10:25 PM ---------- Previous post was at 10:14 PM ----------
good news is, I did enough steps correctly, that I was able to startup in my unsafe mode, and my normal rooted system is functioning fine. That makes me very happy.
This duel boot thing is pretty cool, reminds me of having bootable thumb drives on my old linux system with different OS's. I hope i can get a seperate OS working, however, that fits my needs for a day to day functional phone, without all of Verizon's crap on it
Once rooted use titanium backup to back up apps and data.
Only restore with the same ROM though, the following is in increasing order of risk
restore app only to exact same ROM+version
restore app+data to same ROM+ver
restore app only to update of same ROM
restore app+data to updated ROM version
play chicken with a bus on a highway
restore apps to different kernel e.g. CM7 backup => restore to CM9
check to see what a gun firing looks like down the barrel
restore app+data to different kernel
restore app+data to an older ROM or kernel
do anything at all with system apps+data if you don't know what you're doing
****ALL CREDIT FOR THIS GOES TO HASHCODE AND DHACKER****
I saw this rom on hashcode's rom page, but didn't see a thread for it here. So I decided to create one.
Discuss bugs, experiences, questions on this thread I guess.
Installation procedure should be the same as CM10.1:
"Using this ROM requires Safestrap v2.11 OR SAFESTRAP 3.X currently. As things progress we may add support for Bootstrap or others in.
In all cases moving from ICS to JB, I recommend a full wipe and Titanium Backup restore of just apps+data.
If moving from KEXEC STOCK there might be some issues where you will need to wipe and restore. Be aware.
INSTRUCTIONS FOR FLASHING:
1. Download the ROM from the above link
2. Grab Jellybean GApps
3. Place both files on your SD card
4. Reboot into Safestrap by pressing [menu] at the splash screen
5. If necessary format /system when swapping from ICS to JB to make sure that GApps and other files are reset correctly
6. Also if necessary do a wipe of data/cache (when moving between ICS and JB)
7. Flash the .zip files as normal
8. Reboot and let the phone sit for about 1 minute while it re-indexes files, etc."
Click to expand...
Click to collapse
Able to be installed on ANY slot in safestrap 3.x.
Build 6 and on is kexec, needs to be installed on romslot-2, as pointed out by Kwyrt
http://goo.im/devs/aokp/maserati
jsnweitzel's AOKP builds, among other Droid 4 goodies: https://www.dropbox.com/sh/mhmmrku5e4x8boj/hbd5BE-Nae
The rom runs same as CM10.1, but has some other awesome features added to it
If you have any questions for Hashcode about this, I think it would be best to contact him on twitter at http://twitter.com/Hashcode0f
alex94kumar said:
****ALL CREDIT FOR THIS GOES TO HASHCODE AND DHACKER****
I saw this rom on hashcode's rom page, but didn't see a thread for it here. So I decided to create one.
Discuss bugs, experiences, questions on this thread I guess.
Installation procedure should be the same as CM10:
http://rombot.org/ROMs/maserati/aokp/
The rom runs same as CM10, but has some other awesome features added to it
SCREENSHOTS
(hashcode, if you see this and anything needs to be added, PM me or post it here, ill edit this OP post accordingly)
Click to expand...
Click to collapse
Global Data and Voice calls working?
What are Things that are added apart from hashcode ROM?
Saw the screenshots, very beautiful.. Lot of features seems added.:good::good:
I have been running Stock based AOKP for about a week now and it runs well. The only issue I have with it is no flash for the camera.
I also have been building my own from hashcode and dhacker29 source. I noticed that the stock-aokp build on rombot is a couple of days old. Here is one I did yesterday that is android 4.1.2 : http://forum.xda-developers.com/showthread.php?p=31584441#post31584441
yeah, there are workarounds for most of the bugs in this rom
NEW BUILD, 10-14, updated in OP. This AOKP build has been merged with JB 4.1.2
The ota updater is fixed now too. No more prompts to update to an older rom. But no flash for the camera still.
Sent from my XT894 using Tapatalk 2
im just waiting for camera flash or mms to work... id be happy with just one of those
He's about to go beta with ssv3, I'm sure then they will focus on the kenex builds and get everything working.
Sent from my DROID4 using Tapatalk 2
I think you mean kexec?
I just updated to SS3 and followed all of the instructions, once I rebooted to the new recovery my phone bricked. I was running CM10 on the DROID 4 and now I'm stuck in a boot loop. I tried flashing RSD fastboot files but still no go. Any suggestions?
f0r71fy said:
I just updated to SS3 and followed all of the instructions, once I rebooted to the new recovery my phone bricked. I was running CM10 on the DROID 4 and now I'm stuck in a boot loop. I tried flashing RSD fastboot files but still no go. Any suggestions?
Click to expand...
Click to collapse
Just to be clear, you are actually bootlooping, not getting any error messages, yes?
Second, try wiping data in stock recovery.
Let us know if that works!
f0r71fy said:
I just updated to SS3 and followed all of the instructions, once I rebooted to the new recovery my phone bricked. I was running CM10 on the DROID 4 and now I'm stuck in a boot loop. I tried flashing RSD fastboot files but still no go. Any suggestions?
Click to expand...
Click to collapse
Not sure if I can help, but certainly interested in what happened to cause it. Did you boot back to stock and uninstall the older safestrap first? If you can still get to the recover there must be some way to get it working again.
podspi said:
Just to be clear, you are actually bootlooping, not getting any error messages, yes?
Second, try wiping data in stock recovery.
Let us know if that works!
Click to expand...
Click to collapse
I ended up doing this right after i made my post and it booted up.
I to boot looped my phone, so i wiped data and factory reset in stock recovery, which once it booted, i disabled super user than re enabled it, which then i was able to update it and get busy box installed than install SS3 and everything is back to normal
Glad to hear it all worked out for you
This latest build is awesome. I got a good battery life and smooth as butter. Love it so far and definitely my daily driver. I just found that checking global options makes gsm function. But,signal won't come out. Cdma ruim works fine.
Sent from my XT894 using Tapatalk 2
I have stock camera working on 10-14 build! it has never worked on any previous build, I've done nothing different.
however, there is still no camera flash.
I've seen this problem on other AOKP ROMs... how do I disable the AOKP Statistics notification that keeps popping up? Already ticked and unticked the report checkbox. I just cleared Settings data/cache so maybe that will change it.
Also, how about we "kang" the lockscreen options from CM10. Miss those already.
Freezing??
Has anyone experienced their D4 freezing up and then rebooting itself?
Briteyez83 said:
Has anyone experienced their D4 freezing up and then rebooting itself?
Click to expand...
Click to collapse
Yup, last night when I was trying to use the Alarm Clock, and then again today with the Camera. This one has some neat features (Status/Notificaiton Bar customizations are outstanding) however its not quite un-alpha enough to use as a daily driver for myself. I will be keeping an eye on this one though, its looking very promising.
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to flash the ruu. Full disclosure I no longer stand behind this due to lack of wifi. I went ahead and flashed with the RUU and fastboot flashed twrp back. This solution was only a temporary fix for me. As it should be for anybody if its used at all
You reckon this'll work with Boost Mobile?
TeamLiquid.koyo said:
You reckon this'll work with Boost Mobile?
Click to expand...
Click to collapse
There's already a flashable MM ROM for the boost 626s, http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
Yeah. On boost that's all you need
Genius... Simply Genius
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
i2andog said:
Genius... Simply Genius
Click to expand...
Click to collapse
Thanks man. Lol....
Did you try? If so, any issues?
IsaacGuti said:
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
Click to expand...
Click to collapse
I really don't know what causes the red letters. Personally speaking, I can still manage with or without them.
talksickisil said:
Thanks man. Lol....
Did you try? If so, any issues?
Click to expand...
Click to collapse
No I have a working PC... I just really admired your use of magiver like resources
Gotcha. . Yeah, it's not the first time. And not just phones. I Jimmy rig my way thru a lot of life haha. To be honest I'd probably still do this even if I had my PC. I'm just not a fan of fastboot and adb commands. And I don't want to lock my bootloader again
Yes.. those mother f'in boot loaders would burn in hell if I had any say ... in uh.. boot loaders souls or whatever... ... *crickets*.... hey check that out
Sent from my HTC Desire 626s using Tapatalk
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
s3llz said:
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
Click to expand...
Click to collapse
As far as which sprint ROM you flash debloated version or regular it doesn't really matter, since once you restore the twrp backup you're going to be on the standard non debloated metro official MM. As far as UI differences, there's a few things here and there. Nothing mind blowing. What was advantageous for me is the expanded internal storage. I love it.
I tried installing with the RUU and always got error 155 all the time some I am trying this method out. I would like to know will this method still work on a phone with exposed binary, and for those with MetroPCS, does the service still work as well.
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
bnawolf said:
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
Click to expand...
Click to collapse
In my instructions you don't stay on the sprint rom. You're supposed to restore the backup after installing that rom. But I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to re lock your bootloader and flash the ruu