Got ROMs? Flashable ZIPs for your Alltel MAXX!

Yeah right, let them try.

The sale isn't even finalized yet.
It will take YEARS to get everyone off if Alltel's CDMA network.
If you decide to upgrade after the takeover, yeah, you'll have to get an AT&T phone but they can't force you.


Sent from my Motorola RAZR MAXX using Tapatalk 2
 
That's what i figured but that's just what I heard. I'm on a business plan and the alltel rep came to our store today and said by mid 2013 all remaining alltel territories would transition to AT&T. We'll see what happens i guess.

Sent from my Motorola RAZR MAXX using Tapatalk 2
 
Hey Chris,

I'm looking at the Arctic HD rom. Have you got time to crank out an Arctic ntelos patch for me?

I'm also interested in trying my hand at doing a patch, but I would need an "ntelos goodies" file to do that.

I know you're busy - thanks for any help you can give!

Bob
 
Yeah right, let them try.

The sale isn't even finalized yet.
It will take YEARS to get everyone off if Alltel's CDMA network.
If you decide to upgrade after the takeover, yeah, you'll have to get an AT&T phone but they can't force you.


Sent from my Motorola RAZR MAXX using Tapatalk 2

I thought when Verizon bought parts of Alltel, AT&T and some other small operators picked up the rest of the pieces a couple years ago?

Sent from my SPH-D710 using Tapatalk 2
 
Not in all markets no, like where I live, Verizon would have been the only option.

Sent from my Motorola RAZR MAXX using Tapatalk 2
 
I appreciate the hard work, but when i did this, I think I bricked my phone. I did it with the RazrTouchBlack recovery, and now I can't boot my new rom (AOKP / PA Hybrid Build (King Kang) 12/20/2012 build) and can only get to stock recovery. Did I brick my phone?

- - - Updated - - -

I appreciate the hard work, but when i did this, I think I bricked my phone. I did it with the RazrTouchBlack recovery, and now I can't boot my new rom (AOKP / PA Hybrid Build (King Kang) 12/20/2012 build) and can only get to stock recovery. Did I brick my phone?
 
I don't know anything about that recovery. You need to be more specific about what you did and what your phone is doing now.

Sent from my dirty rainbow unicorn Nexus 7 using Tapatalk HD (HorriblyDeveloped)
 
I don't know anything about that recovery. You need to be more specific about what you did and what your phone is doing now.

Sent from my dirty rainbow unicorn Nexus 7 using Tapatalk HD (HorriblyDeveloped)
I rooted and installed the CWM Touch recovery, RazrTouchBlack.apk
Did backup
Flashed Rom, Flashed Gapps, and flashed the patch. Wiped data and cache, and reset.

On reset, only came up with the ROM's boot screen. It never got any further. When I tried to boot back into recovery, I was only able to get into the stock recovery. Tried wiping data and cache. Same problem.

Tried vzw sbf, now I'm stuck looking for an SBF just like sipthis.
 
As far as I know, there isn't anything that can be done. The reason we use Safestrap for this is that it does not touch your stock system at all, so no matter what you flash, as long as you follow the directions you can always go back to stock.

Sent from my dirty rainbow unicorn Nexus 7 using Tapatalk HD (HorriblyDeveloped)
 
Pretty cool - I got to fooling around with Chris' Ntelos file, downloaded ArcticHD, put a build.prop file into it, and sha-ZAMMMM!!! Looky here!! Arctic HD, working on Ntelos. I backed up my apps using Titanium Pro, and pulled them off the external SD into this rom. KEWELL!!!!!!

Look out world, you got a newb on the loose!!! :D
 

Attachments

  • Screenshot_2013-02-14-11-32-01.png
    Screenshot_2013-02-14-11-32-01.png
    638.5 KB · Views: 6
Nice work. Glad it's running well.

Just for the record, the problem with doing it that way (pulling an entire build.prop from another ROM) is that not only will it display incorrect version / build info, but a ROM (especially one that is stock based) will have specific tweaks in the build.prop that are lost once you overwrite them.
 
Nice work. Glad it's running well.

Just for the record, the problem with doing it that way (pulling an entire build.prop from another ROM) is that not only will it display incorrect version / build info, but a ROM (especially one that is stock based) will have specific tweaks in the build.prop that are lost once you overwrite them.

Thanks Chris. I'll have to look at the two files (Arctic and the flick file you made for me) and see what's what. Can you tell me what I need out of the Flick build prop to change in the Arctic file?
 
You'll actually want to take your build.prop from your stock system and compare it side by side with the build.prop from Arctic. Go through it line by line, changing anything that is different in regards to the radio, cellular connectivity, etc... to what is written in your stock build.prop.
 
Where do you find the stock system's build.prop?

edit: first guess would be in the nandroid backup, no?
 
I had to pull it out of then systemorig.ext3 file that....one of you guys sent me, lol. Or, you can boot into your stock side, and it is in /system/, just e-mail it to yourself or something.
 
You'll actually want to take your build.prop from your stock system and compare it side by side with the build.prop from Arctic. Go through it line by line, changing anything that is different in regards to the radio, cellular connectivity, etc... to what is written in your stock build.prop.


Ok, I attempted to make a custom build.prop file, but when I tried to run it, the phone wouldn't boot into the rom. It just gave me the Moto "M" logo and then went black. So I bailed back to Safestrap and booted back to stock. Happened 2 or 3 times. Obviously, I'm missing something here, but I'll figure it out.

I'll keep trying the build.props until I get it to work. :p
 
Last edited: