Database Info

stuck in a rut

So I want to do the new sw update but can't because I deleted some stock apps so the checksum wouldn't match and a hard reset won't restore them I guess so I would flash a stock rom but am I right thinking there isn't one yet? So how can I get to an original rom and then update or maybe make the new update work?

D2G stock rom
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html

@evil yeah im kind of in the same boat, let me know if srensber solution works for you.
I froze a bunch of apps with Titanium Backup and renamed some stuff with Root Explorer. I recently just re-named everything i changed back to the factory stuff (bak -> apk) but it still doesnt seem to do any good.
I did create a number of back ups using Rom manager but i cant seem to find out where they are located and how to restore them. hmm. Not sure what to do.
Ah i realize what ive done wrong ... i didnt know you had to have bootstrap installed along with clockwork recoveryy in order to make a backup hmm. Going to need a rom of stock d2g lol.

clockwork recovery installs a boot hijack, which might be the culpirt

srensber said:
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
Click to expand...
Click to collapse
I cant seem to find the download link anywhere... and after you loaded this rom did you try to update to 2.4.3 ?
If anyone else has any input about this please help!

[CLOSED][ROM]Bone Stock & Stock Deodex ROM's Triumph-Now Resets Splash.img!![CLOSED]

[CLOSED][ROM]Bone Stock & Stock Deodex ROM's Triumph-Now Resets Splash.img!![CLOSED]
Thread closed because I no longer own this device. The download links no longer work. Sorry for any inconvenience.

i just installed and wifi works but when trying to go online rebuts the phone, also the screen goes black and stays like that for like 2 minutes. And yes i did all the restores available.

Which ROM did you flash? Deodexed or Complete Stock?

deoxed one.

Hmm that's odd cause the woofing works fine on mine! Ill look into it!
Sent from my OC'ed Triumph!

b_randon14 said:
Hmm that's odd cause the woofing works fine on mine! Ill look into it!
Sent from my OC'ed Triumph!
Click to expand...
Click to collapse
Same here it works... weird, this is the fix for me that got the wifi functioning again. But then again, I flashed b_randon14's stock theme zip, not this one.
If you want deodex I would recommend that one, more confirm it working at least right now.

Stupid question perhaps, but will apktool properly decompile and recompile framework-res.apk? I ran into a doozy of a problem trying to do that with somebody else's ROM.

Yeah it decompiles just fine! I have done it a thousand times!

Edited op with the zips that will reset the splash.img back to factory as well!!!

Thanks and I'm going to have to try this one out now.
Is the Android logo text hidden deeper in the system than I originally thought? I've actually seen it on my new phone a couple of times now, after reverting different things. You know, the flashing "android" text...

When there is no boot animation, it reverts to the flashing android logo. Its in the framework Res under assets/images. The boot logo(red Motorola logo) is on the same partition as the recovery image as a splash.img. to flash it I have the recovery mount that vfat partition as sd-ext and copy over the the splash.img its the same way I flash recoveries from cwm.
The bootanimations( red Motorola animated logo then cm splash animation) is locates in /hidden/data/power-on animation.
Sent from my MOTWX435KT using Tapatalk

So I installed the deodexed version and I was able to use mobile wifi tether with barnicale without having to change the MTU for the Motorola Triumph!

Once you change the MTU once on a computer, you never have to change it again... you sure it's not just a residual effect?

primetechv2 said:
Once you change the MTU once on a computer, you never have to change it again... you sure it's not just a residual effect?
Click to expand...
Click to collapse
I'm quite well aware of that. I did it on my laptop, but not my desktop. but my desktop was able to connect online with the tether. i guess i should try it on another machine to make sure.

Is there any advantage with the deodexed version over the odexed version if your goal is to restore the phone to stock after having another ROM installed?

Selling my Motorola Triumph to a friend - I've been running CM7 since the alpha days, so I need to go back to stock. I still have a nandroid of the stock ROM, but that also has a lot of installed apps, not to mention personal information/passwords. Will the complete stock ROM allow her to activate the phone?

InfamousBlade said:
Selling my Motorola Triumph to a friend - I've been running CM7 since the alpha days, so I need to go back to stock. I still have a nandroid of the stock ROM, but that also has a lot of installed apps, not to mention personal information/passwords. Will the complete stock ROM allow her to activate the phone?
Click to expand...
Click to collapse
It should.

I know this thread is about a year old, but thanks for the stock files.
I had CM7 running on my daughters Triumph. I finally decided to just put both of my kids on my VZW family plan since the Gnex dropped to $50 each and Virgin Mobile's service is a complete waste of money.
I'm selling her Triumph now and the phone has to be stock in order for the new owner to activate it, so this came in handy.
Thank you very much!

Works perfectly. My girlfriend didn't want a buggy ROM ruining her Candy Crush games so I had to bring her back to stock. Took less than ten minutes! Tanks!

[Q] Clean Rom

Hello everyone,
What exactly does Clean Rom do? How is it different from what comes with the phone stock? Will Clean Rom mess with the updates that are pushed to our phones? Any big differences between layout?
Sorry for all the questions. I'm just not familiar with modifying my phone.

Must read more. Spend as much time as you can reading in the dev section. Clean ROM removes all of the ATT bloat and adds functionality like the FM radio and remapping the 3 dot menu button that takes up screen real-estate to the recent apps softkey. The recent apps can be accessed by holding down the home button, like we're familiar with. It also has performance and battery tweaks (says so in the changelog, haven't been using it long enough to notice). I flashed it the day before yesterday and I'm liking it.
Sent from my HTC One X

Clean Rom doesn't use profane language, think of it as the Will Smith of Roms...
Sent from my HOX running WCX

Did you bother to go to the Development forum, and read the CleanROM threads? They very well describe the features of each version of CleanROM.
You don't ever want to install an OTA update once on a custom ROM. It won't be compatible. Either it won't install, or it will remove root, or it will totally bork the system. The devs typically keep their ROM updated to the newest firmware base, and often long before the OTAs go out. So there is virtually never a benefit to updating via OTA (even if it did work).

Most custom ROMs prevent you from even getting an update pushed in the first place. Kind of a non-issue there.
To the OP, if you want to flash custom, just do it. Spend a few days on Clean, try out Smokin's ROM, too. Just find something you like. Worst that can happen is you RUU back to stock.
Sent from my HTC One X using Tapatalk 2

SoberGuy said:
Most custom ROMs prevent you from even getting an update pushed in the first place. Kind of a non-issue there.
Click to expand...
Click to collapse
Depends on the device, and I believe the carrier (and maybe the custom ROM as you mentioned). I've gotten OTA notification, and even able to download OTA (didn't install it, just to see if it would actually download . . . some have said custom ROMs will prevent that too) on 2 previous HTC devices on custom ROMs. But one was a Canada Bell phone used on AT&T, and the other was the WiFi-only Flyer tablet. So it may be that AT&T somehow directly blocks OTA to rooted phones.

redpoint73 said:
Depends on the device, and I believe the carrier (and maybe the custom ROM as you mentioned). I've gotten OTA notification, and even able to download OTA (didn't install it, just to see if it would actually download . . . some have said custom ROMs will prevent that too) on 2 previous HTC devices on custom ROMs. But one was a Canada Bell phone used on AT&T, and the other was the WiFi-only Flyer tablet. So it may be that AT&T somehow directly blocks OTA to rooted phones.
Click to expand...
Click to collapse
I don't think att can see your on a custom ROM, it has to do with if the developer is able to include that ability or not.

Thank you for the replies!
I'm trying my best to understand how Clean Rom works. Is it the same thing as rooting a phone? Any disadvantages of using Clean Rom?
I'm just curious about how it works because I tried jailbreaking my iPhone and that made it very crash prone. It's a bad example but it's the reason why I never tried using custom software again but I'm interested in giving this a try. I only get about 2 hours screen time and about 12 hours of screen off time for my phone to die.
I did the HTC battery test and my phone went down to 92% so I'm pretty sure it's not the battery that's wrong with the phone.

RPTheLefty said:
I'm trying my best to understand how Clean Rom works. Is it the same thing as rooting a phone?
Click to expand...
Click to collapse
It appears you need to do more reading to get a better understanding or root, ROMs, etc.
Root is just a change of permissions on your phone. It allows the user and apps access to system files that are normally restricted. Nothing more, nothing less.
Clean ROM (or installation of any custom ROM) is a total replacement of the firmware or operating system of the phone (also called a "ROM"). Clean ROM in particular is mostly based on the latest stock firmware version, but cleaned up to remove bloat, optimizations to make it faster and smoother, and some cool added features. There are 3 different versions of CleanROM. Just read the threads for each version to learn the differences.
I don't really keep up with iPhone stuff. But my understanding is that jailbreaking adds functionality, but makes the system less stable.
Whether a custom ROM on Android makes the phone more or less stable depends on the ROM. Some are ported from other phones, to give new UI look or functions, but can be a bit buggy at first. But any good ROM will be stable once it reaches "maturity" and the bugs are worked out. They can be very stable, and even more stable and smoother than the stock ROM. Which is one of the points of running a custom ROM.
CleanROM in particular is based on stock firmware, just cleaned up. So its very stable. Just as stable as stock, a bit smoother in some places, and with some awesome added features. Any disadvantages? Not really. But you need to unlock the bootloader to install any custom ROM, which voids the warranty. nd flashing anything to the phone has the risk of damage if you don't follow the instructions properly. Thats the only downsides I can think of (for any custom ROM, not just for CleanROM).

Redpoint had an excellent summary.
If you're looking for battery life improvement, there are significant advantages to a custom ROM. Some will allow you to adjust the clock rate for the processors. So you can turn the up a bit (overclock) to get incredible performance, or you can turn them down a bit (underclock) to get better battery life.
If that's your main goal, I personally suggest Sick Sense from Smokingl337. He has incorporated this into his ROM, and the reports I've seen have been positive. I had used his ROM before, and I did like it. The day I flashed CleanROM due to a minor bug, Smokinl337 updated his ROM to fix that bug. Figures! But I'll be going back to Sick Sense pretty soon, I'm sure.
Hopefully you can find something that works for you.
Sent from my HTC One X using Tapatalk 2

Different kernel or different radio may also help battery life.
But you need to root, SuperCID, and unlock bootloader to do any of these things (including flashing custom ROMs). So head over to Development and start reading:
http://forum.xda-developers.com/showthread.php?t=1671237

There is also a clean rom developers edition that takes out most of the HTC sense... there is the cm9 alpha 4 rom that seems very stable...
Sent from my HTC One X using Tapatalk 2

OP, I was in your shoes last week. New to android/roms etc. I rooted, unlocked the bootloader and flashed Clean Rom. Just follow the instructions in the associated threads and you'll be fine.

[Q] My first attempt at installing custom rom

I have TWRP installed on my One X and fully backed up my current settings through the Backup function in TWRP as well as Titanium backup, just to be safe.
I want to install MIUI so I've downloaded the zip. Is the best method to wipe the phone and then install the zip, or is it to restore to factory settings and then install the zip?
Also, if I want to go back to my current rom (HTC Sense - that came with the phone) how would I restore the TWRP backup that was created? Also how solid is the TWRP backup? Will I have problems restoring from that with random things like market associations or settings?
Thanks for all the help everyone.

TWRP backups back up EVERYTING (I mean kernel, system, app apks) except for sdcard data. Restoring a backup will look exactly like the moment you backed up the ROM.
In order to flash a new ROM, do this:
1. Back up your apps using some application (Titanium Backup, Ultimate Backup, etc)
2. Create a new TWRP backup
3. Factory Reset
4. Install the ZIP
5. Boot into your ROM and download whatever app you downloaded in step 1
6. Restore your apps from step 1
Enjoy

im looking for a good rom as well but im new.
my att one x was on 1.85 before i rooted it and unlocked the bootloader.
now im just looking for a senseless rom like Jdroids or CM9 that will work with my situation.
id love to get jdroids exodized revoultion, does that work with att? or do i have to wait for an att version to come out?
any suggestions. thnx

veyg said:
im looking for a good rom as well but im new.
my att one x was on 1.85 before i rooted it and unlocked the bootloader.
now im just looking for a senseless rom like Jdroids or CM9 that will work with my situation.
id love to get jdroids exodized revoultion, does that work with att? or do i have to wait for an att version to come out?
any suggestions. thnx
Click to expand...
Click to collapse
Don't flash anything that isn't actually in our dev forum unless you want a buggy POS (best case), a massive bootloop (slightly worse case), a beautiful paperweight (pretty bad), or your phone exploding (yeah that's probably the worst).
I made that last one up, but who knows.
As for Sense-less roms, look for AOKP or CM9. CleamROM DE/Dev Edition is pretty much Sense-less, but it retains some backend Sense things to ensure everything still works properly. It's as close to AOSP as you're gonna get without actually being AOSP.

stnguyen09 said:
Don't flash anything that isn't actually in our dev forum unless you want a buggy POS (best case), a massive bootloop (slightly worse case), a beautiful paperweight (pretty bad), or your phone exploding (yeah that's probably the worst).
I made that last one up, but who knows.
As for Sense-less roms, look for AOKP or CM9. CleamROM DE/Dev Edition is pretty much Sense-less, but it retains some backend Sense things to ensure everything still works properly. It's as close to AOSP as you're gonna get without actually being AOSP.
Click to expand...
Click to collapse
Hello can you help me? i have a paper weight because i installed the wrong rom and i flashed it when i had 20% battery now y one x wont turn on or charge please help

mr.5106411 said:
Hello can you help me? i have a paper weight because i installed the wrong rom and i flashed it when i had 20% battery now y one x wont turn on or charge please help
Click to expand...
Click to collapse
Well there's another lesson in there. Don't flash unless you have sufficient battery (I never do it under 50%....best to do it when fully charged though)
So you're not getting the led indicator to light up when you plug it in? What rom did you flash?

Updated: JB nav issue also on 100% stock ROMs

EDIT 3/16: After more detailed testing during the day today I withdraw all of the claims below. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text below intact for context.
------------------
It would appear that the JB nav issue some of us are plagued with is exclusively due to something devs are doing with their custom ROMs. Here is why...
I am one of the unlucky ppl who could not get Nav to work with JB. I have tried multiple custom ROMs, including stock rooted, and nav always crashes within two minutes. Today I RUU-ed back to 2.20, changed CID to AT&T, took the official OTA and played with Nav without a hickup for 30 mins. I then unlocked again, Super_CID-ed and flashed CleanROM 6 R2. Nav immediately went haywire with the same symptoms as before. I then went through the RUU and OTA process once again, and Nav purrs like a kitten.
Not sure what custom ROMs are doing to mess up things...but the above suggests that something common that devs use to root is interacting incorrectly with JB on some phones. We seem to be a minority of users, as busy as our devs are we may get no love.
At this point I will stick with AT&T true stock for a while, will just flash a custom recovery and debloat it to an extent with the TWRP file manager or just slim down update.zip.

Re: JB nav issue seems to be caused by custom ROMs
Well I can't agree.
I have been using and beta testing Viper for a long time and never have trouble with nav.
I did update all my firmware to JB stock but even before that I could not replicate the issue others are having.
Just my two cents.
Sent from my HTC One XL using Tapatalk 2

Did you try one of the stock 3.18 roms? Make sure it's odexed and has an unmodified kernel.
Personally I haven't had navigation issues on two phones using firmware from 1.85 and 2.20, on 3.17 and 3.18 based jb roms.

pablo11 said:
Well I can't agree.
I have been using and beta testing Viper for a long time and never have trouble with nav.
I did update all my firmware to JB stock but even before that I could not replicate the issue others are having.
Just my two cents.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It is well documented that only some HTC phones suffer from this problem. It has been seen on the HOX, the EVO, even on some SG3s. This is what has made it so maddeningly frustrating. It affects a small fraction of the users, so the devs don't spend any time trying to address it. Not blaming the devs, they can't go after every small issue. However, for those of us unfortunate enough to have it it has been a PITA.
slippers67 said:
Did you try one of the stock 3.18 roms? Make sure it's odexed and has an unmodified kernel.
Personally I haven't had navigation issues on two phones using firmware from 1.85 and 2.20, on 3.17 and 3.18 based jb roms.
Click to expand...
Click to collapse
Yes, I tried AT&T stock rooted, no dice. The ONLY thing that has worked so far is 100% stock unrooted OTA.

Re: JB nav issue seems to be caused by custom ROMs
don't know much about it, but I have the issue and I am most puzzled why the app hasn't had an update with bug fix. It's been too long an issue for the official channels not to have been noticed. If it IS ONLY custom roms, I wouldn't be surprised of the official channels just ignored the bug.
I initially thought maybe HTC made a deal with Google too break nav so people would start paying for a subscription to the HTC nav app. But I just use waze now. It seems to find better routes anyway.
This post was created and transmitted completely in analog.

I thought we had already covered it .. isn't it some people have a little diff hardware then others I think one member suggested gyroscopes differentiations being the problem...but I've never had a problem with nav on any jb sense rom nor jb in general ... It shouldnt be caused by custom roms as that doesnt make sense

Re: JB nav issue seems to be caused by custom ROMs
It really would be nice to see a firmware upgrade pack for the hox. It seems we actually need it.
Sent from my HTC One X using xda premium

Groovy,
There are alot of variables here, so try to narrow them down. These are the steps I would try:
1. RUU back to 2.20.
2. Take the 3.18 OTA.
3. Verify that navigation works perfectly.
4. Fastboot flash a custom recovery (twrp or cwm). Reboot back into the rom.
5. Verify that navigation works perfectly.
6. In recovery, backup the boot partition.
7. Flash scott's stock 3.18 rom from http://forum.xda-developers.com/showthread.php?t=2181399
8. Verify that navigation is crashing. If navigation is crashing at this point, it can only point to the slight changes in scott's stock 3.18 rom, which include adding busybox, superuser, and /system read/write.
9. To circumvent /system read/write, go into recovery and restore *only* the boot partition that you backed up in step 6. This will put the stock kernel back on that doesn't have init.d support, and thus won't enable /system read/write.
10. Verify that navigation is working or not working. If it works, then we know it's the kernel.

slippers67 said:
Groovy,
There are alot of variables here, so try to narrow them down. These are the steps I would try:
Click to expand...
Click to collapse
I already did this and try to convey it in the OP but perhaps was not clear.
1. RUU back to 2.20.
2. Take the 3.18 OTA.
3. Verify that navigation works perfectly.
Click to expand...
Click to collapse
This was done
4. Fastboot flash a custom recovery (twrp or cwm). Reboot back into the rom.
5. Verify that navigation works perfectly.
Click to expand...
Click to collapse
This was was done. BTW, TWRP 2.2.0 no longer works with the new firmware, but 2.3.1 works.
6. In recovery, backup the boot partition.
7. Flash scott's stock 3.18 rom from http://forum.xda-developers.com/showthread.php?t=2181399
8. Verify that navigation is crashing. If navigation is crashing at this point, it can only point to the slight changes in scott's stock 3.18 rom, which include adding busybox, superuser, and /system read/write.
Click to expand...
Click to collapse
This was done. Nav starts crashing as soon as CR6 R2 is installed. I also see crashing with stock rooted and viper.
Note also that a version of busybox is present on stock.
9. To circumvent /system read/write, go into recovery and restore *only* the boot partition that you backed up in step 6. This will put the stock kernel back on that doesn't have init.d support, and thus won't enable /system read/write.
10. Verify that navigation is working or not working. If it works, then we know it's the kernel.
Click to expand...
Click to collapse
I will have to try this. Will get to it at some point today. However, there is an additional wrinkle. I debloated the AT&T ROM last night and am now seeing crashes again. Not sure if the original stability was a red herring, will have to redo the OTA and start all over again.

GroovyGeek said:
I already did this and try to convey it in the OP but perhaps was not clear.
This was done
This was was done. BTW, TWRP 2.2.0 no longer works with the new firmware, but 2.3.1 works.
This was done. Nav starts crashing as soon as CR6 R2 is installed. I also see crashing with stock rooted and viper.
Note also that a version of busybox is present on stock.
I will have to try this. Will get to it at some point today. However, there is an additional wrinkle. I debloated the AT&T ROM last night and am now seeing crashes again. Not sure if the original stability was a red herring, will have to redo the OTA and start all over again.
Click to expand...
Click to collapse
Don't use CR6.2. Use the stock 3.18 rom he released. Then restore the boot.img from the backup. At that point, the only difference will be the different recovery on your phone, as everything else will be the same as taking the OTA.

I've had the issue but only after updating to the latest ViperXL OTA.

After more detailed testing during the day today I withdraw all of the claims from the OP. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text of the OP intact for context, have added a comment at the top to indicate it is no longer relevant. I have now officially given up on JB and am going back to ICS. Google Nav is just too much of a convenience to mess around with replacements.

GroovyGeek said:
After more detailed testing during the day today I withdraw all of the claims from the OP. 100% stock via RUU 2.20 + OTA 3.18 still crashes, it just takes a lot longer on my phone. I am leaving the original text of the OP intact for context, have added a comment at the top to indicate it is no longer relevant. I have now officially given up on JB and am going back to ICS. Google Nav is just too much of a convenience to mess around with replacements.
Click to expand...
Click to collapse
Yikes! Maybe google/HTC will try to fix it now that it happens on stock.
Sent from my HTC One XL

ECEXCURSION said:
Yikes! Maybe google/HTC will try to fix it now that it happens on stock.
Sent from my HTC One XL
Click to expand...
Click to collapse
For a small subset of a nearly 2 year old phone? Good luck with that. Your best strategy may be to remove the relocked text, change the s-off text to s-on (without actually going back to s-on), change the Cid back, ruu 2.20, take the ota, then take it to an att store and insist that since the ota broke it it is their job to fix it for you. If you are lucky they will give you a refurb with 2.20. If you are not so lucky they will give you a refurb with JB and then you are stuck without root. Worst case they tell you to eff off. You then take the phone home and revert back to whatever you want (since you are in reality s-off). And before anyone claims that this is unethical, how ethical is it for att to screw a portion of their customers?

GroovyGeek said:
For a small subset of a nearly 2 year old phone? Good luck with that. Your best strategy may be to remove the relocked text, change the s-off text to s-on (without actually going back to s-on), change the Cid back, ruu 2.20, take the ota, then take it to an att store and insist that since the ota broke it it is their job to fix it for you. If you are lucky they will give you a refurb with 2.20. If you are not so lucky they will give you a refurb with JB and then you are stuck without root. Worst case they tell you to eff off. You then take the phone home and revert back to whatever you want (since you are in reality s-off). And before anyone claims that this is unethical, how ethical is it for att to screw a portion of their customers?
Click to expand...
Click to collapse
I'm confused. This phone was released 11 months ago. Announced 13 months ago.
10 months in the US, even.

Not sure why groovygeek thinks the phone was released so long ago... May 9th 2012 in the US.
Sent from my HTC One XL
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
For those with the nav crashing, are you charging the phone when this happens? Does it cash both ways?
Sent from my HTC One XL

I have two phones bought at the same time. One is stock unrooted and runs the OTA 3.18 with no google maps crashes. My phone as described in my sig has map crashes always. I haven't jumped around to many other JB roms besides Viper to this point because they all seemed to be having issues with the JB and Google Maps. Didn't have any crashes with ICS.

Just wanted to say that many one s owners are experiencing the same problem.
Sent from my HTC One XL