ROMS tested by me:
***************************************
These are the following KitKat based roms that worked really well with this approach:
1. CM 11 Nightly
2. PAC-MAN
3. Slimkat Weekly
I tried with both AT&T and T-Mobile variants, and didn't have to load Sprint specific kernel, the stock kernel came with those worked just fine. But if you get bootloops, go ahead and flash KToonz Sprint AOSP kernel.
IMPORTANT: The listed roms above have ability to detect device type and it will set appropriate settings meaning your default network mode with be CDMA, which you don't want to do that since u r running on unlocked GSM to begin with. So I learned that you can force GSM mode upon starting up by putting these two lines into build.prop:
telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
*******************************************
So thanks to OP on this thread http://forum.xda-developers.com/showthread.php?t=2530610 for the instructions on how to get the SIM unlocking work.
I personally wanted to run pure AOSP on my GS4, but the problem is when I go AOSP, switching over to GSM works but I can't receive any phone calls. If I run stock, I can configure it to turn off roaming guard and whatnot, this is not the case for AOSP.
Therefore, here's how I get around it. WARNING: a little lengthy but it worked.
0. Backup your current Sprint AOSP now you'll need it later.
1. Download TMOBILE AOSP rom of your choice. I chose Gummy 4.4
2. Download Sprint AOSP of your choice (I'm on sprint). I chose Gummy 4.4
3. Once download completed, open the TMO zip and delete the boot.img because it contains the kernel for TMO which we don't want. Keep this window open.
I recommend NOT extracting it because you will have to reassemble later, just use a zip software that allows you to edit in place.
4. Open the Sprint AOSP, copy the boot.img over to TMO. Basically, we are replacing JUST the kernel for Sprint into TMO to make the phone boots.
5. Now we need to get rid of the assertion check for device type in the updater-script.
6. WIth TMO zip window still open, edit the file /META-INF/com/google/android/updater-script, and replace anything that said jfltetmo with jfltespr. UPDATE 3: If you see no "assert" lines described below in your updater-script, simply ignore this step.
From:
Code:
assert(getprop("ro.product.device") == "jfltetmo" || getprop("ro.build.product") == "jfltetmo" || abort("This package is for \"jfltetmo\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
To:
Code:
assert(getprop("ro.product.device") == "jfltespr" || getprop("ro.build.product") == "jfltespr" || abort("This package is for \"jfltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
7. Save the changes, and upload the TMO to phone and flash. Now you are running completely under TMO settings and calls can be received.
8. Setup everything you need and NANDROID backup.
9. So with this approach, I tested switching back to CDMA, and the EXACT problem happens (can't receive calls). So move on to next step.
10.To switch back and forth, you just need to boot into recovery and wipe system and replace it with the targeted system you want to be on. For instance, if I am on TMO and want to switch to SPR, I reboot into recovery, wipe current TMO /system and restore SPR /system and reboot. This whole process should take about 3 minutes.
If anyone has any better approach, please share.
UPDATE: This approach also will solve my problem of using AOSP dialer. If I run Sprint ROM (CDMA), and switch over to GSM via Mobile Network (in Settings), then upon placing a call and hanging up will NOT hang up. The dialer on Sprint ROM will say the call has ended by it never did if you put it on speaker phone. So with this system switching, it also solves this problem.
UPDATE 2:
If you are in Asia using GS4, flashing Sprint S4 stock kernel will fix issues reported below:
Gummi (Won't mount my external SD card)
Omni (Won't mount my external SD card)
Cyanogenmod (Crashes, can't install apps, bunch of other problems)
AOKP (No wifi, crashes, etc.)
Go to Page 3 to find more info. >> http://forum.xda-developers.com/showpost.php?p=49724403&postcount=21
Ahh been looking everywhere for this so that's all it just change over the boot.img
Going to give it a try when I get home and in front of my lappy how's that gummy? 4.4
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
Okay see I unlocked my spr gs4 and am running T-Mobile.. Gsm soo I'm going to give this a go anyway
Sent from my SPH-L720 using xda app-developers app
wow this work like a charm. thank you very much
vboyz103 said:
So thanks to OP on this thread http://forum.xda-developers.com/showthread.php?t=2530610 for the instructions on how to get the SIM unlocking work.
I personally wanted to run pure AOSP on my GS4, but the problem is when I go AOSP, switching over to GSM works but I can't receive any phone calls. If I run stock, I can configure it to turn off roaming guard and whatnot, this is not the case for AOSP.
Therefore, here's how I get around it. WARNING: a little lengthy but it worked.
0. Backup your current Sprint AOSP now you'll need it later.
1. Download TMOBILE AOSP rom of your choice. I chose Gummy 4.4
2. Download Sprint AOSP of your choice (I'm on sprint). I chose Gummy 4.4
3. Once download completed, open the TMO zip and delete the boot.img because it contains the kernel for TMO which we don't want. Keep this window open.
I recommend NOT extracting it because you will have to reassemble later, just use a zip software that allows you to edit in place.
4. Open the Sprint AOSP, copy the boot.img over to TMO. Basically, we are replacing JUST the kernel for Sprint into TMO to make the phone boots.
5. Now we need to get rid of the assertion check for device type in the updater-script.
6. WIth TMO zip window still open, edit the file /META-INF/com/google/android/updater-script, and replace anything that said jfltetmo with jfltespr.
Code:
assert(getprop("ro.product.device") == "jfltespr" || getprop("ro.build.product") == "jfltespr" || abort("This package is for \"jfltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
7. Save the changes, and upload the TMO to phone and flash. Now you are running completely under TMO settings and calls can be received.
8. Setup everything you need and NANDROID backup.
9. So with this approach, I tested switching back to CDMA, and the EXACT problem happens (can't receive calls). So move on to next step.
10.To switch back and forth, you just need to boot into recovery and wipe system and replace it with the targeted system you want to be on. For instance, if I am on TMO and want to switch to SPR, I reboot into recovery, wipe current TMO /system and restore SPR /system and reboot. This whole process should take about 3 minutes.
If anyone has any better approach, please share.
Click to expand...
Click to collapse
where are the links to the t-mobile and sprint roms you used?
i am rooted with a custom recovery installed
do we need to be on any specific firmware to start the process?
i been going exactly through the same pain you have been
i been having to manually edit phone settings with *#0011# each time and it still isnt perfect
i mean it works ok but not like i want really.
your method is prob the most stable but is really just a work around for the real problem.
why dont our phones just read the sim cards correctly like a regular unlocked phone?
>>>>what happens if the firmware auto updates after it is installed?<<<<
en11gma said:
where are the links to the t-mobile and sprint roms you used?
i am rooted with a custom recovery installed
do we need to be on any specific firmware to start the process?
i been going exactly through the same pain you have been
i been having to manually edit phone settings with *#0011# each time and it still isnt perfect
i mean it works ok but not like i want really.
your method is prob the most stable but is really just a work around for the real problem.
why dont our phones just read the sim cards correctly like a regular unlocked phone?
>>>>what happens if the firmware auto updates after it is installed?<<<<
Click to expand...
Click to collapse
You can choose any ROM of your choice here over at TMOBILE forum http://forum.xda-developers.com/galaxy-s4-tmobile.
This is that kind of hoops we have to jump through because what we are doing is considered NON-STANDARD and therefore, UNSUPPORTED by carrier. That is the main reason why the carrier locked down the SIM card at first.
So for a little trouble of flashing back and forth, I think I can hang and to have an unlocked SIM like this save us $$. I'm thinking of ditching Sprint and go no-contract from here on on. This is the future of cell phones as it should be many places already done this.
vboyz103 said:
You can choose any ROM of your choice here over at TMOBILE forum http://forum.xda-developers.com/galaxy-s4-tmobile.
This is that kind of hoops we have to jump through because what we are doing is considered NON-STANDARD and therefore, UNSUPPORTED by carrier. That is the main reason why the carrier locked down the SIM card at first.
So for a little trouble of flashing back and forth, I think I can hang and to have an unlocked SIM like this save us $$. I'm thinking of ditching Sprint and go no-contract from here on on. This is the future of cell phones as it should be many places already done this.
Click to expand...
Click to collapse
you are acting like this phone the "cdma galaxy s4" is unique for wanting it to be an unlocked gsm phone.
not no more.
this is the standard
should be a distro for each phone just for this or an apk just for this
this is gonna be pretty regular to have all these radios built-in to a single chip or just a couple chips on the c/b in the phone.
hopefully some crews are working on this
i think they are in the roms that have HiAPN and MNE or MNC (i forget what it stands for) but basically it can read the iccid on the sim and read the apn and dload the prl automatically
some....alot of the roms dont have this but some do.
vboyz103 said:
So thanks to OP on this thread http://forum.xda-developers.com/showthread.php?t=2530610 for the instructions on how to get the SIM unlocking work.
I personally wanted to run pure AOSP on my GS4, but the problem is when I go AOSP, switching over to GSM works but I can't receive any phone calls. If I run stock, I can configure it to turn off roaming guard and whatnot, this is not the case for AOSP.
Therefore, here's how I get around it. WARNING: a little lengthy but it worked.
0. Backup your current Sprint AOSP now you'll need it later.
1. Download TMOBILE AOSP rom of your choice. I chose Gummy 4.4
2. Download Sprint AOSP of your choice (I'm on sprint). I chose Gummy 4.4
3. Once download completed, open the TMO zip and delete the boot.img because it contains the kernel for TMO which we don't want. Keep this window open.
I recommend NOT extracting it because you will have to reassemble later, just use a zip software that allows you to edit in place.
4. Open the Sprint AOSP, copy the boot.img over to TMO. Basically, we are replacing JUST the kernel for Sprint into TMO to make the phone boots.
5. Now we need to get rid of the assertion check for device type in the updater-script.
6. WIth TMO zip window still open, edit the file /META-INF/com/google/android/updater-script, and replace anything that said jfltetmo with jfltespr.
Code:
assert(getprop("ro.product.device") == "jfltespr" || getprop("ro.build.product") == "jfltespr" || abort("This package is for \"jfltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
7. Save the changes, and upload the TMO to phone and flash. Now you are running completely under TMO settings and calls can be received.
8. Setup everything you need and NANDROID backup.
9. So with this approach, I tested switching back to CDMA, and the EXACT problem happens (can't receive calls). So move on to next step.
10.To switch back and forth, you just need to boot into recovery and wipe system and replace it with the targeted system you want to be on. For instance, if I am on TMO and want to switch to SPR, I reboot into recovery, wipe current TMO /system and restore SPR /system and reboot. This whole process should take about 3 minutes.
If anyone has any better approach, please share.
Click to expand...
Click to collapse
vboyz103
you know what
this is probably one of the most important pieces of info i have come across on the boards
yes i look the root, recovery and rom sections but this is a coool tip
i have been doing this for a few years and have never tried doing this before
can i basically try any rom i want (for tbe GS4) as long as i use the kernel made for my specific phone?
are there any dos and donts we should be aware of?
so far i have only done it with CM11nightlies for jfltespr and jfltetmo and also same for gummy as you suggested
but those are basically identical roms....can we do this with any rom for the gs4?
1 more thing. it neworing defailts to LTE and if you go look at the APN's and there are the username "none" and password has a " * " and another setting has a " * * "
all the APN's are like this for that network
do we need to fix them or is that somehow correct?
i am super confused as to whats happening here.
you say do the *#0011# and hit numbers. heres the thing. i dont get any options. just a service menu with a bunch of stuff on it. nothing about debug screen or anything. ive unlocked many s3's and know what im looking for but its not there. on MJA or MK2. people are saying yea just flash the TMO CM and go, others are saying the sim unlock program works on MJA, others saying not to do it on that version because it doesnt work, others saying it only works on MF9...WTF CAN WE PLEASE GET A VIDEO TUT OR SOMETHING. ive been pulling my hair out for days with this thing. ive followed loads of instructions but none of it works. please give precise step by step what version you should be on, root or not, bootloader version, everything thanks
dragonhart6505 said:
i am super confused as to whats happening here.
you say do the *#0011# and hit numbers. heres the thing. i dont get any options. just a service menu with a bunch of stuff on it. nothing about debug screen or anything. ive unlocked many s3's and know what im looking for but its not there. on MJA or MK2. people are saying yea just flash the TMO CM and go, others are saying the sim unlock program works on MJA, others saying not to do it on that version because it doesnt work, others saying it only works on MF9...WTF CAN WE PLEASE GET A VIDEO TUT OR SOMETHING. ive been pulling my hair out for days with this thing. ive followed loads of instructions but none of it works. please give precise step by step what version you should be on, root or not, bootloader version, everything thanks
Click to expand...
Click to collapse
how about you just read the freaking first post
you can clearly tell you havent read crap
POST #1
tells you about the exact problem you are having trying to see the correct info in *#0011#
everyone who reads what you wrote about *#0011# is gonna laugh at you for demanding info and tuts when you havent even read the 1st freaking post!!!!
not in this thread but DOMESTIC UNLOCK
its always at the top in the threads in the forums....it might even be a sticky
en11gma said:
how about you just read the freaking first post
you can clearly tell you havent read crap
POST #1
tells you about the exact problem you are having trying to see the correct info in *#0011#
everyone who reads what you wrote about *#0011# is gonna laugh at you for demanding info and tuts when you havent even read the 1st freaking post!!!!
not in this thread but DOMESTIC UNLOCK
its always at the top in the threads in the forums....it might even be a sticky
Click to expand...
Click to collapse
Edit: NVM, got it working, cept i kept it on stock. thanks for the tut, its better when its clearer.
dragonhart6505 said:
Edit: NVM, got it working, cept i kept it on stock. thanks for the tut, its better when its clearer.
Click to expand...
Click to collapse
i started out thinking the thread i was in was that domestic sim unlock
there are 3 threads you really want
1st
sim unlock international (that has the unlock.exe)
2nd
domestic sim unlock (that one tells you what to do with *#0011#
3rd
this one
i have those 3 tabs open quite a bit
on a side note
when we install those tmobile romz they are doing something (correct) to the *#0011# area and maybe something else
we should just be able to flip flop with some simple script
shouldnt have to restore romz
but hey at least we got something
Yknow, i think thats the very first useful thought towards dual booting ive seen yet.
dragonhart6505 said:
Yknow, i think thats the very first useful thought towards dual booting ive seen yet.
Click to expand...
Click to collapse
lol
yep it is dual booting
do it on my linux / windows pc all the time
but the thing is...these settings are in *#9090# and a little simple script should be able to do this on the fly
en11gma said:
lol
yep it is dual booting
do it on my linux / windows pc all the time
but the thing is...these settings are in *#9090# and a little simple script should be able to do this on the fly
Click to expand...
Click to collapse
Oh trust me I do as well. Can't go without my Linux lovin' ^_^ as this was a pain in the arse but now super easy, I can't wait to do it again.
<3 bein a nerd lmao
Also, OP, since I havent found one yet (and making tuts is kinda my thing) mind if I make one? With all credits where due of course
dragonhart6505 said:
Oh trust me I do as well. Can't go without my Linux lovin' ^_^ as this was a pain in the arse but now super easy, I can't wait to do it again.
<3 bein a nerd lmao
Also, OP, since I havent found one yet (and making tuts is kinda my thing) mind if I make one? With all credits where due of course
Click to expand...
Click to collapse
Have at it man..I'm not so good it making tuts.
Nice. Ty. Will link when its done of course
would it be the same steps if i wanted to a use a touchwiz rom?
nemofbaby2010 said:
would it be the same steps if i wanted to a use a touchwiz rom?
Click to expand...
Click to collapse
From my previous testing, TW rom dialer is better in handling GSM technologies. Therefore, you don't need to do these steps. The link to the original Unlock thread will give you more information in terms of what to do with TW.
vboyz103 said:
From my previous testing, TW rom dialer is better in handling GSM technologies. Therefore, you don't need to do these steps. The link to the original Unlock thread will give you more information in terms of what to do with TW.
Click to expand...
Click to collapse
Also while using slim ROM I got a persistent notification about call fowarding
Sent from my SGH-M919 using Tapatalk
ROMs
Hi everyone,
I live in Asia, and this post was a lifesaver for me because I was pulling my hair out over why I wasn't receiving calls.
In terms of ROMs, however, I've had some issues that I wanted to ask about (I've followed the instructions above to the dot).
Here are ROMs that work (for the most part):
Cyanfox (some freezing, halo issues)
Here are ROMs that have issues:
Gummi (Won't mount my external SD card)
Omni (Won't mount my external SD card)
Cyanogenmod (Crashes, can't install apps, bunch of other problems)
AOKP (No wifi, crashes, etc.)
I currently have MJA baseband. Any thoughts? Thanks!
Related
***This will work on the T-Mobile US branded Vibrant and generic Galaxy S models***
***IMPORTANT: YOU PERFORM THIS AT YOUR OWN RISK, THIS MAY VOID YOUR WARRANTY, I NOR ANYONE ELSE IS RESPONSIBLE IF YOU BRICK YOUR DEVICE.***
***UPDATE: Now you can do this without ADB installed!
The following method should be relatively care-free but there is always a risk with activities like rooting a device or flashing a new firmware.
1. Download the attached zip and rename to: update.zip
2. On your device, navigate to Settings > Applications > USB settings and select Mass storage
3. Plug your device into your computer, select mount USB from your device's pull-down window
4. Copy the update.zip to the INTERNAL SD memory (~14gb on this drive, not the one w/ Avatar if you've still got the 2gb SD card in)
5. Turn your phone off.
6. Hold down volume up and volume down while powering on the phone, this should get you to a recovery menu, you may have to try this a few times.
7. In Recovery menu select 'Reinstall Packages' (use vol_down then power to select)
Phone will reboot
and you have
1. su+Superuser
2. busybox (/system/xbin/busybox)
Original credit goes to LeshaK at Samdroid, I modified the script within update.zip to work on the Vibrant.
Other credits to the fine folks in this thread that noted the vol up+down recovery menu.
I would link to the Samdroid forum but I can't...but check Samdroid > i9000 Development forum for the original post.
Intriguing may try this on Thursday
How easy is it to put back to stock for warranty purposes?
Thank you to the OP for posting this. Does it make sense to append the post with a quick guide to installing and getting ADB to work with Vibrant for those who have never done that? This would make it a truly complete guide to rooting Vibrant.
Thanks for this. I'm planning on getting an AT&T Captivate when it comes out. What would I have to change in your script to have it work on the Captivate? Would it just be a matter of changing the model names in the file updater-script? That seems to be the only file with an updated file date. TIA.
So with this root, will the normal Galaxy S custom rom (modaco) work on the vibrant? or does the rom need adjusting?
Thanks for this . Can't wait until Thursday!!
quickex99 said:
How easy is it to put back to stock for warranty purposes?
Click to expand...
Click to collapse
Not sure exactly, though you could easily delete the super user APK, that's the only real visible sign that this is installed. Doubt they'd check much further. The Samdroid forum post may have info on reverting to stock.
If anyone wants to take this and modify, it should work on the Captivate/Fascinate/Epic with a simple modification, add the model name for each device to this part of updater-script in the zip file:
Code:
assert(getprop("ro.product.device") == "GT-I5800" ||
getprop("ro.build.product") == "GT-I5800" ||
getprop("ro.product.device") == "GT-I9000" ||
getprop("ro.build.product") == "GT-I9000" ||
getprop("ro.product.device") == "SGH-T959" ||
getprop("ro.build.product") == "SGH-T959"
);
Does it make sense to append the post with a quick guide to installing and getting ADB to work with Vibrant for those who have never done that?
Click to expand...
Click to collapse
I'll leave that to someone else, I personally feel that if folks are in this 'development' section then they should be capable of installing and getting ADB running before they do something that could possibly harm their phone if they screw it up.
So with this root, will the normal Galaxy S custom rom (modaco) work on the vibrant? or does the rom need adjusting?
Click to expand...
Click to collapse
Honestly, no idea on this. I'm not willing to risk my Vibrant to this, I'll let someone else be a guinea pig. But I am interested to hear if the wireless hotspot feature can be added back, this is the only item I miss from the Vibrant.
I'm glad it's that easy, now what about wireless tether? It's something that I and others root for almost exclusively.
Has anyone successfully tried this yet?
Considering that the phone doesn't release until Thursday, I highly doubt it.
BigWorldJust said:
Considering that the phone doesn't release until Thursday, I highly doubt it.
Click to expand...
Click to collapse
Considering I have one sitting here in my hands, some people have access so a valid question
lp1527 said:
Considering I have one sitting here in my hands, some people have access so a valid question
Click to expand...
Click to collapse
So. Care to share the results with the people? How about some more info on speed, lag, firmware etc.
Sent from my Htcclay's SuperBad G1 using XDA App
Lag is still there, it's the reason I went for root in the first place, had to perform Paul's lag fix w/ the shipped software. With the lag fix and Launcher Pro this device is quite a joy.
Ship ROM is T959UVJFD.
once i installed the galaxy s drivers, it was REALLY painless and easy. i did it just for the wireless tethering.. and whatever other goodies I can find for this so far... really excited!
justadude said:
Lag is still there, it's the reason I went for root in the first place, had to perform Paul's lag fix w/ the shipped software. With the lag fix and Launcher Pro this device is quite a joy.
Ship ROM is T959UVJFD.
Click to expand...
Click to collapse
Can you elaborate? Do you still have the original shipped OS (Touchwiz and all pre-loaded apps, etc.)? Also, any kind of step-by-step you could provide?
Much appreciated and THANK you!
disturkis4u said:
once i installed the galaxy s drivers, it was REALLY painless and easy. i did it just for the wireless tethering.. and whatever other goodies I can find for this so far... really excited!
Click to expand...
Click to collapse
The wireless tethering is my main reason for rooting so I am very interested which tethering application you are using and which version. Also, where did you get the proper drivers for adb connection? The directions in the first post assume that everybody knows how to use adb which sadly is not the case with me. Any additional information will be greatly appreciated. Thank you in advance.
basataom said:
So with this root, will the normal Galaxy S custom rom (modaco) work on the vibrant? or does the rom need adjusting?
Click to expand...
Click to collapse
It would probably need some tweaking since the hardware is a bit different. (ei. the button layout)
Lmao, that's why I said highly unlikely, NOT impossible. SMH.
marsupial99 said:
The wireless tethering is my main reason for rooting so I am very interested which tethering application you are using and which version. Also, where did you get the proper drivers for adb connection? The directions in the first post assume that everybody knows how to use adb which sadly is not the case with me. Any additional information will be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
I searched for "galaxy s usb driver" in xda and the first link was USB Driver for Galaxy S and Misc Info - xda-developers. There's a rapidshare and multiupload link for download also in that thread. (3rd post or something).
once you extract the usb drivers folders, go to the extracted folder, double click on "setup" and it will install the drivers for you. when you enable usb debugging on your vibrant and plug it in, windows should successfully install the usb drivers. then, go to command, and follow the instructions in the first post
edit: i'm using the app called Wireless Tether version 2.0.1 website is http://android-wifi-tether.googlecode.com
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.
Hey guys,
I finally got 3G data working in Hashcode's port of ICS to the Droid 3/XT860. I'm currently using the isuacell (Mexico) revision on a Bell XT860; I wasn't able to get ICS to boot up on the current Bell update, although I'm sure it's something simple I've overlooked. I'm fairly certain it'll work on other software updates such as the ones from Argentina/Brazil, and possibly the ME863 but I don't have the time to test it myself, let me know if it works for you if you're running any of these updates.
Nevertheless, I got it working pretty easily. I don't have time to do a full writeup right now but it was exactly what I suspected earlier, a minor issue in the Android framework causing an exception that would disconnect 3G data a few seconds after a connection to the APN was successfully made. That, combined with Motorola's RIL library from the isuacell firmware and a few build.prop tweaks were all it took, and so far it is running pretty good.
Only major thing I've noticed so far is that the cell status indicator only seems to indicate either perfect reception or none, no in between, but for now I'm pretty stoked this is working as I can finally use ICS on a daily basis instead of switching back and forth a dozen times a day.
Here's a link to a .zip to be installed via Safestrap. Be sure to perform a factory reset and to be safe, mount system and format it in the "mounts and storage" area before installing the zip to ensure a clean install. Also, as Hashcode had mentioned in his release thread, don't let it restore your old settings when you run through the Setup Wizard on the first boot. Enjoy, and be sure to thank Hashcode for all the effort he's put into making our phones even better!
http://dl.dropbox.com/u/22632665/CM9_XT860.zip
md5=6302b1733777ad5d7e3d5483d9291591
176820984 bytes
---------------------------------------
EDIT: I was lazy earlier and just posted the link to the full update, I finally got around to releasing a significantly smaller, more sensible patch:
http://db.tt/HEbusNM3
xt860_ics_patch_01_30_2012-safe_system-signed.zip
md5=60dc2db347c7310d0f5e51b0e02b9952
4231015 bytes
I recommend flashing Hashcode's Alpha 5 release, then doing a factory reset before installing this update in Safestrap. I can make one for the non-safe system users out there too, just didn't bother but it'd take two seconds.
Also, check out my github repos for the changes I made to get 3G data working. (You'll probably laugh when you see the change to android_frameworks_base):
http://github.com/buddyrich
I've kind of mimicked Hashcode to keep things simple; my changes are in the branch "ics-xt860". The easiest way to compile it all from scratch is like this: (Assuming you're in your working directory)
1) repo init -u git://github.com/CyanogenMod/android.git -b ics
2) cd .repo
3) git clone git://github.com/buddyrich/android_local_solana.git
4) cd android_local_solana
5) git checkout ics-xt860
5) cp local_manifest.xml ../
6) rm -f -r android_local_solana
7) repo sync -j24
8) Place this file in the root of your working directory, eg: ~/android/system/ : http://db.tt/1HpM2m6r
9) vendor/cm/get-prebuilts
10) . build/envsetup.sh
11) brunch solana
nice, it works!
Rick#2 said:
Also, as Hashcode had mentioned in his release thread, don't let it restore your old settings when you run through the Setup Wizard on the first boot.
Click to expand...
Click to collapse
I see this mentioned everywhere, and now I just have to ask. What happens if you do let it restore your old settings?
funny....i got 3G, but i cant make a call nor receive a call......
is that my problem or known problem?
That is strange, I can make and receive calls without any issues. What software/baseband are you using?
albatorsk said:
I see this mentioned everywhere, and now I just have to ask. What happens if you do let it restore your old settings?
Click to expand...
Click to collapse
The world will explode.
No, to be honest I have never tried. I think the idea is that you don't want any settings from a completely different Android release (ie: Gingerbread vs. ICS) being restored. It will still sync up your contacts and everything, just not any wifi connections, system settings, etc.
Rick#2 said:
That is strange, I can make and receive calls without any issues. What software/baseband are you using?
Click to expand...
Click to collapse
kinda strange, i wipe and try now, sometimes clean install but got phone.apk freeze, my latest try is ok....
emprize said:
kinda strange, i wipe and try now, sometimes clean install but got phone.apk freeze, my latest try is ok....
Click to expand...
Click to collapse
Very nice man!! I was actually talking to this with Hashcode a while ago and we figured that the best way to get things working for xt860/me863 might be to release small patches to enable data etc. Is it possible to pop your modified files in a smaller patch that can be applied against the current and future cm9 builds? (With a list of what's modded I think most people can do this pretty easily and the patch should be easier to update than the ~175 meg cm9 zip as well when carriers release newer firmwares with updated libs etc).
I have this running against my bell 2.3.6 cwm rom that I flashed non-safe, only problem I have is that I have to boot the phone plugged into the computer with ICS, Hash has fixed and broke that a few times I think, not the most important thing. I notice with your build I don't need to have my phone plugged in to the computer to boot ics.
Edit: For some reason I have data and "Sim card not detected" in the status bar, everything is populated correctly in phone info, phone works for calling and data. Switching out the included libmoto_ril.so with the one from bell 2.3.6 took care of the "Sim card not detected" up top(srsly, maybe it was just the reboot) but when I try to make a call phone fc's lol.
nice ill try later
Enviado desde mi XT860 usando Tapatalk
goalando said:
nice ill try later
Enviado desde mi XT860 usando Tapatalk
Click to expand...
Click to collapse
It's worth trying now, with libertys dl site going down last night I flashed this knowing I wouldn't have data only to wake up and find that it's my every day rom now. Any hacking etc from this point might as well be done while using/on this (although I would still really like to see data working on cm7 as well personally, perhaps if Rick#2 makes this into a smaller patch we can test it on that as well). Only a few things that are holding us back now like camera/some codec/module issues.
So far so good. Thanks a lot
I'm using the stock Bell 2.3.4 rom and I installed this zip on my safe system enabled mode however it doesnt work. I wish someone could show me how to provide more meaningful logs but this is what I get from dmesg:
http://pastebin.com/jHhTiCC3
a longer dmesg:
http://pastebin.com/k5PMF3r4
and finally heres /proc/kmsg
http://pastebin.com/ygW2Fb4Y
if anyone could look through it and tell me why my xt860 is not booting this build of cm9 that'd be great thanks
Hey Congrats on setting this up Rick#2!
Get me a patch of just the changed files and I'll host it under the builds so that people can download both files at the same time as new updates happen.
You've single-handedly brought ICS to the XT860!
works awesome! i had to add some stuff to the ATT apn for data to work
and camera isnt working, but everything else is AWESOME.
THANK YOU to everyone who helped make this possible
From my xt860
Is anyone else finding that touch events take longer to register?
Sent from my XT862 using xda premium
Very nice man. Thanks
Has anyone tried to send an MMS picture message (on Rogers?) I double checked my apn's. It didn't seem to send. But data is nice!
Sent from my XT860
Edited the first post with a much smaller patch and some more info on what's going on.
Hi!
I put this patch up on the blog as well:
http://hash-of-codes.blogspot.com/p/android-downloads.html
(See XT860 sub-patch)
Rick#2: I can get that frameworks change into my build via a build.prop setting..
ro.ril.ignore.linkiperror=true
(add this to your build.prop and I'll get it in for the next release)
That you don't need to patch frameworks.jar each release.
And I might build in a prop check for disabling the GlobalNWStats trigger which causes a looping FC for non-VZW Droid 3 users. Not sure what to use tho.
Also in your update-script the mount command references:
mount("ext3", "EMMC", "/dev/block/mmcblk1p23", "/system");
That will only work for Safestrap users.
Let's change it to:
mount("ext3", "EMMC", "/dev/block/system", "/system");
Yeah, I was wondering what to do about that. Didn't think I could just use /dev/block/system, nice for compatibility!
Pretty funny how I spent countless hours sifting the radio logs, trying a billion permutations and combinations of proprietary binaries, libraries and build.prop settings when all that needed to be done was to comment out *one* line of code. I had an itch to try getting rid of that bit regarding the exception a few weeks ago but thought it couldn't possibly be that simple...
Rick#2 said:
Yeah, I was wondering what to do about that. Didn't think I could just use /dev/block/system, nice for compatibility!
Pretty funny how I spent countless hours sifting the radio logs, trying a billion permutations and combinations of proprietary binaries, libraries and build.prop settings when all that needed to be done was to comment out *one* line of code. I had an itch to try getting rid of that bit regarding the exception a few weeks ago but thought it couldn't possibly be that simple...
Click to expand...
Click to collapse
I sometimes get asked why development takes so long when they take a look at the commit changes and the code hasn't been edited much at all.
*cough* This is a fine example of just such a case.
I'm sure the entire XT860 community appreciates the hard work.
Info:
This is a custom stock rom that is only for sprint devices (Sprint/Vm/Boost). It was made using SuperR's Kitchen. It is rooted and I tried to removed as much as I could. This is just a work in progress so there will probably be more that I will remove and will replace some of the apps with updated and better versions based on user input. Also included for those that wish to make their own rom is an decrypted rooted stock. I have tested these extensively, but as always make a full backup before flashing and do a full wipe just in case. I am not responsible for any damages or loss of data that may occur from flashing these roms.
Apps that have been removed:
system/app/appmanager*
system/app/BasicDream*
system/app/CalculatorWidget*
system/app/Drive*
system/app/DriveActivator*
system/app/Exchange3Google*
system/app/facebook*
system/app/FaceLock*
system/app/FMRadioService*
system/app/Font_Helvetica*
system/app/Font_XinGothic*
system/app/Font_Yuen*
system/app/Gmail2*
system/app/GoogleTTS*
system/app/Hangouts*
system/app/HoloSpiralWallpaper*
system/app/HtcAutoRotateWidget*
system/app/HtcBackgroundDataWidget*
system/app/HTCBackup*
system/app/HtcBackupReset*
system/app/HtcCarGps*
system/app/HTC_Connect*
system/app/HtcGpsWidget*
system/app/HtcHotspotWidget*
system/app/HtcLogLevel*
system/app/HtcMessageProvider*
system/app/HtcPowerStripWidget*
system/app/HtcRingtoneWidget*
system/app/HtcScreenBrightnessWidget*
system/app/HtcScreenTimeoutWidget*
system/app/HtcSyncWidget*
system/app/IMEHWRPenPower*
system/app/IMEMurasuIndic*
system/app/IMEMurasuViet*
system/app/IME_TP_ValueAdd*
system/app/instagram*
system/app/KidMode-google*
system/app/Maps*
system/app/messenger*
system/app/Music2*
system/app/MyHTC*
system/app/News_Republic*
system/app/NewsWeather*
system/app/NoiseField*
system/app/pagesmanager*
system/app/PhaseBeam*
system/app/talkback*
system/app/Videos*
system/app/YouTube*
system/priv-app/DemoFLOPackageInstaller*
system/priv-app/Facebook*
system/priv-app/Frisbee*
system/priv-app/GooglePlusPlugin*
system/priv-app/GSD*
system/priv-app/HTCAdvantage*
system/priv-app/HtcBtWidget*
system/priv-app/HtcCalendarWidgets*
system/priv-app/HtcContactWidgets*
system/priv-app/HtcDataRoamingWidget*
system/priv-app/HtcDataStripWidget*
system/priv-app/HtcDLNAMiddleLayer*
system/priv-app/HtcDMS*
system/priv-app/HtcDotMatrix*
system/priv-app/HtcFileManager*
system/priv-app/HtcHotspotWidget*
system/priv-app/HtcMobileNetworkWidget*
system/priv-app/HtcMusicWidget*
system/priv-app/HtcRingtoneTrimmer*
system/priv-app/HtcSoundRecorder*
system/priv-app/HTCSpeakCyberon*
system/priv-app/HtcWeatherClockWidget*
system/priv-app/HtcWiFiWidget*
system/priv-app/HTCZero*
system/priv-app/iCloudTransfer*
system/priv-app/ID*
system/priv-app/installer*
system/priv-app/Instagram_SN_Plugin*
system/priv-app/LinkedIn_Fsplugin*
system/priv-app/LocationPicker*
system/priv-app/Lookout*
system/priv-app/Lucy*
system/priv-app/Mail*
system/priv-app/MirrorLink_MirrorLinkService*
system/priv-app/Photos*
system/priv-app/PolarisOffice*
system/priv-app/Sprint_Installer*
system/priv-app/Sprint_Sprint_VVM*
system/priv-app/Sprint_Sprint_Zone*
system/priv-app/TetheringGuard*
system/priv-app/Twitter*
system/priv-app/Velvet*
system/priv-app/WallpaperCropper*
system/priv-app/Weather*
De-Bloated MM (Updated: 9-2-16):
https://www.androidfilehost.com/?fid=24588232905724314, https://basketbuild.com/filedl/devs?dev=Nightbreed&dl=Nightbreed/HTC%20626s/Sprint_Stock_MMDB_2.27.651.6.zip (BB down)
Standard Stock MM (Updated: 6-23-16): https://www.androidfilehost.com/?fid=24686679545611466, https://basketbuild.com/filedl/devs?dev=Nightbreed&dl=Nightbreed/HTC%20626s/Sprint_Stock_MM_2.27.651.6.zip (BB down)
Debloated LP(Updated 1/23/16): https://drive.google.com/open?id=0BzHOZHL6ZwXhRWxZNG4zc3lDSWc
Standard Stock LP: https://drive.google.com/open?id=0BzHOZHL6ZwXhX0RoYnpxTUsyZnc
Let me know if there are any problems/request you have I'll try to do my best to fix them as quickly as possible.
I would like to thank @Captain_Throwback for all of his help in making this rom.
*updated links 9-2-16
Nice! I'm downloading now. Thanks for putting in the time. Can't wait to check it out.
thefuryofZ3US said:
Nice! I'm downloading now. Thanks for putting in the time. Can't wait to check it out.
Click to expand...
Click to collapse
Let me know how it goes. I still have some work to do on it. Wasn't really sure what some of the files were. I'll be running more test to see what else I can remove and still have it boot. Wan't to get this as small as possible. If I removed anything that breaks something important let me know. As I said I'm not a dev and this is my first attempt.
No doubt. I have no problem putting it through the wringer. I'll let you know if I find anything, as well as any fixes that may work. I'm stoked to get back to my 626 and get to flashing!
I'll keep an eye on this. Just got the phone in the mail and noticed the extreme amounts of bloatware. Can't wait to root Dx.
Everything seems to be functioning correctly so far. Nice, lite and responsive. Flashed well, maybe 3 minutes total to complete. Boot up took even less. As of this post, no FC's or hangups found.
Solid rom! Thanks again!
Finally a rom for the sprint variants! I'll be giving this a try, downloading now. I hope it solves the low memory problems....
Sinister Drake said:
Finally a rom for the sprint variants! I'll be giving this a try, downloading now. I hope it solves the low memory problems....
Click to expand...
Click to collapse
Removed most of the apps that were causing problems. Have another version that I am currently working on that will have the updates included and a few more apps removed. Only problem is this phone is very hard to make flashable roms for. Most attempts end with a boot loop. Still not giving up though.
A few things I have noticed: first is the HTC Account apk was missing so I couldn't sign in to install themes. I fixed that by downloading it from Google Play and making it a system app using rom toolbox pro.
Secondly I'm not sure if our phone has a magnetometer (compass) I would think it would have one. But it's not working.
Other than those 2 issues, this is a solid rom. Good job man. Keep up the good work.
I'm trying to get viper4Android to work but it keeps telling me my busybox installation is broken which it isn't.
Might wanna see if you can include busybox in future updates. Just a suggestion.
Oops, sorry noob here, got the 626s desire but connected to the bell network. if this is a sprint rom i guess i got to go back to rooted stock? The rom boots but hangs at activation. am i correct?
Unfortunately until someone comes up with a rom for your variant, you'll have to go back to your original rom. I hope you made a backup before you installed this rom.
I have the boost mobile variant and I still can't get twrp to work only Cyan recovery anyone know anything about getting two to work I used captainthrowback
Maybe I should learn how to read better. Is new so started off the bat with nothing on it so no backup I did with it. Worst case is I'm screwed lol.
kindlefire39 said:
Maybe I should learn how to read better. Is new so started off the bat with nothing on it so no backup I did with it. Worst case is I'm screwed lol.
Click to expand...
Click to collapse
You might not be screwed. Try searching the HTC website for an Ruu for your carrier. Once you find it lock your bootloader, then let it run its magic. Should return you back to stock.
@Sinister Drake I removed a lot of HTC stuff as I didn't think most people use it. If I do remove something you really need and can't find let me know and I'll re-add it.
As for busybox it does come pre-installed. Why some apps find it and others do not I can't really say. Doing a busybox check does show it's there.
Now as for the compass that is a issue that worries me. All my research says this phone has one, but it doesn't work even on my recovery. I need to know if it was something that worked on stock or if it was just false reporting by HTC, so I can narrow down the problem. It shouldn't be a problem with my rom as it is taken directly from the RUU, but I cannot be for certain until I get more feedback.
You know I screwed myself and went to quick because I had it rooted with twrp and oh look debloated firmware without paying attention to the Carrier, Doh! You know what silly, I called HTC Canada because bell is a Canadian outfit and they apparently don't supply ruu's like the states does. Oh well my bad 200 smackers later and a new phone. I guess on the bright side I can root it lol. Maybe one of the excellent developers will somehow create a bell version.
New version = https://drive.google.com/open?id=0BzHOZHL6ZwXhRWxZNG4zc3lDSWc Removed an extra 200mb now total over 600mb freed. Also, updated the OP with the list of apps that have been remove. As always if I removed something you want and can't find let me know I will add it back in. Been using this version for a few days and found no errors, but make a backup just in case. Report any error you find I'll do my best to fix them.
Working on updating the apps to free up even more space. After that I'll be replacing some apps with lighter versions. Once I get any significant build I'll post it.
@kindlefire39 hopefully you can find someone else that has this phone in your region to make a backup for you. Once you get that you can easily use suprr kitchen to make a debloated version.
Is it possible to backup my new phone and use super kitchen? Or am I out in left field? I could be the first one with a bell mobility variant.
kindlefire39 said:
Is it possible to backup my new phone and use super kitchen? Or am I out in left field? I could be the first one with a bell mobility variant.
Click to expand...
Click to collapse
Once you flash a rom it overwrites the one you currently have installed. That is why it is good to make a backup before you flash. Out of curiosity have you tried to flash Captain_Throwback's rom? Its for metropcs but if you can get your phone to boot you can call your phone company tell them your phone is on a different carrier and you need the codes for the phone to work on their network. If you do get it to boot some things might not work, like the wifi, but it can get you through until you can get a proper rom/backup. Try posting in the help section asking for someone to make a backup of their phone. Heck even try asking anyone you know that has the same phone if you can borrow it for a bit to fix yours.
nightbreed813 said:
You might not be screwed. Try searching the HTC website for an Ruu for your carrier. Once you find it lock your bootloader, then let it run its magic. Should return you back to stock.
@Sinister Drake I removed a lot of HTC stuff as I didn't think most people use it. If I do remove something you really need and can't find let me know and I'll re-add it.
As for busybox it does come pre-installed. Why some apps find it and others do not I can't really say. Doing a busybox check does show it's there.
Now as for the compass that is a issue that worries me. All my research says this phone has one, but it doesn't work even on my recovery. I need to know if it was something that worked on stock or if it was just false reporting by HTC, so I can narrow down the problem. It shouldn't be a problem with my rom as it is taken directly from the RUU, but I cannot be for certain until I get more feedback.
Click to expand...
Click to collapse
When I installed the rom I did not see Busybox, I installed it from google play. I'm still trying to figure out how to get viper4android to work to no avail. Maybe you can add it as a system app with the rom. With that being said, I've learned that another thing you have to do to get it to work is to use the selinux changer. with a quick google search you can find it elsewhere to download since it is not availble on google play anymore.
I do have to give you props though man, you're doing a fantastic job developing this rom whilst not being a developer. Kudos to you brother.
---------- Post added at 10:15 PM ---------- Previous post was at 10:10 PM ----------
Is it possible that you could provide the apk for the HTC clock widget? I really dig the flip clock style. I can install it myself, I just dont have the apk for it
Sorry what I meant is I got a second phone because HTC Canada couldn't help. I just bit the bullet. So with the new phone can I make a stock backup or through twrp than backup? If I have a stock backup, than I could custom it and delete apps that you did for yours in your list.