Database Info

Message from AT&T to update Rom! rooted, unlocked bootloader

Ok people, Here is a couple of Questions for you. My AT&T One X is rooted with an unlocked bootloader however, I am running a stock Rom. I just started getting this AT&T message that is giving me the option to update my software. But! It gives me a choice of 1, 2, 3, 5, and 8 hours to remind me if I do not do it now. If I let the update happen, will it crash my phone? Will it take out my root? Permanently ?? I am afraid to update because I have been reading that AT&T has been trying to fix their back door.
Also, How can I stop the reminder from coming back???

Flash a custom rom cleanrom 2.5 se is nice. Its really the best way. It blocks ota.
Sent from my HTC One X using xda premium

kleeman7 said:
Flash a custom rom cleanrom 2.5 se is nice. Its really the best way. It blocks ota.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks however, can you direct me to a thread that includes the ROM, Kernal, Exc.? I have Fastboot and all. Is this Rom compatable with my stock IMG?
Thanks again, Gary

kelnhofer said:
Thanks however, can you direct me to a thread that includes the ROM, Kernal, Exc.? I have Fastboot and all. Is this Rom compatable with my stock IMG?
Thanks again, Gary
Click to expand...
Click to collapse
If you haven't installed an custom recovery you would need to with this tool.
http://forum.xda-developers.com/showthread.php?p=26528640
Getting links.
Then CleanROM 2.5 SE (stock debloat performance and battery mods)
http://forum.xda-developers.com/showthread.php?p=26119274
Or CleanROM Lite (very slim speedy rom mostly everything stripped out install own apps from market)
http://forum.xda-developers.com/showthread.php?p=27048708
And then kernal from (general consensus is 1.82 is the best for performance and battery.
http://forum.xda-developers.com/showthread.php?p=26933428
And finally a radio from (will have to try them and find out which works best for you with data speed and signal)
http://forum.xda-developers.com/showthread.php?p=27022095
I made this from mobile app. Had to edit to add links, lol.
Sent from my HTC One X using xda premium

Very nice!!!
THANK YOU SOOO Much, Gary

No problem. Let us know if you have any issues. But you shouldn't its pretty easy to do.
Sent from my HTC One X using xda premium

kleeman7 said:
No problem. Let us know if you have any issues. But you shouldn't its pretty easy to do.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I will do that. I have to get up early for work so I will be back on tomorrow night. One last thing though, you said to flash the Rom then the Kernal? I thought the Kernal came first.
Oh and what if I flash the Kernal without updating to the new Rom? The reason I'm asking is that My wife has the same phone However hers is Rooted but not BL un-locked. so if I flash just the Kernal would it work? Then, would it solve the AT&T reminders to upload their Rom?
Sorry for all the Questions, Gary

These kernals are recovery flashable. Meaning from CWM so ordet doesn't matter, technically the Rom will flash a kernel, but some users say one is better than another so just throwing out options. I don think there is a way to get rid.of.the notification unless you could.freeze the updater app with something like titanium backup, or go custom Rom route.
Sent from my HTC One X using xda premium

Ok Thanks I'll let you know how it goes, Gary

kleeman7 said:
No problem. Let us know if you have any issues. But you shouldn't its pretty easy to do.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I want to thank you for the recomending this Rom it all went in beutifully! I ended up flashing my wifes phone also.
Today AT&T sent us messages that stated that there would be no more reminders and that if we did not choose to update they would update anyway. So I shut down the phones until I got off work and took out our access cards then turned off Wi-Fi. Finnally when I could this afternoon I started flashing.

Nice, I'm glad it worked out for you. CleanROM lite is nice too, if you want a leaner Rom.
Sent from my HTC One X using xda premium

I have flashed two custom ROMs now and both have been glitchy and slow. (stuttering, freezes, FCs, etc)
I found my original nandroid from just barely post unlock/root, and restored it. I'm on 1.7x and would like to stay that way if at all possible.
Does anyone know what to freeze in TiBa in order to get this to stop? I just want to stay on stock/rooted for right now.

xeper said:
I have flashed two custom ROMs now and both have been glitchy and slow. (stuttering, freezes, FCs, etc)
I found my original nandroid from just barely post unlock/root, and restored it. I'm on 1.7x and would like to stay that way if at all possible.
Does anyone know what to freeze in TiBa in order to get this to stop? I just want to stay on stock/rooted for right now.
Click to expand...
Click to collapse
Try cleanrom now, you need to give it a day to build up caches, but it was rebuilt on a more stable Rom.
Sent from my HTC One X using xda premium

kleeman7 said:
Try cleanrom now, you need to give it a day to build up caches, but it was rebuilt on a more stable Rom.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Since what version? I was having issues with 2.5.

xeper said:
I have flashed two custom ROMs now and both have been glitchy and slow. (stuttering, freezes, FCs, etc)
I found my original nandroid from just barely post unlock/root, and restored it. I'm on 1.7x and would like to stay that way if at all possible.
Does anyone know what to freeze in TiBa in order to get this to stop? I just want to stay on stock/rooted for right now.
Click to expand...
Click to collapse
Or use Rootkeeper from the market and update to 1.85 and keep root.
Edit* I responded to the wrong post
Sent from my HTC One X using xda premium

xeper said:
Since what version? I was having issues with 2.5.
Click to expand...
Click to collapse
The newest version 2.6, or lite 1.1
Sent from my HTC One X using xda premium

azturbomini said:
Or use Rootkeeper from the market and update to 1.85 and keep root.
Edit* I responded to the wrong post
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Is there any reason I'd want to keep my 1.7x and NOT update (if I can help it)?
Every time I flash something on this phone, it seems to slow way way down. I just want it to stay where it is.

Trust me, It's worth the trouble of doing it.
Sent from my HTC One X using xda premium

Been running CleanRom 1.1 lite for about 12 hours and its WAY better than stock by far! Flashed the battery percentage and dim 3 led's and dual core mod. Couldnt ask for anything more

thanks!
So if I have 1.73 rooted with bootloader unlocked. Can i just install clean rom to update to 1.85? or do i first have to update? If i have to update first is it better to use the Peter's guide post or can i just use bootkeeper and to the ota update?
Thanks!

Brick Bug

Are there any rom /kernals still out there that have the emmc bug in them? I want to flash an ics rom, but with all the stuff floating around I'm a little nervous. Sorry if this has been asked before, I did a quick thread search on the phone and didn't find anything.
Sent from my SAMSUNG-SGH-I727 using XDA

All of them
Sent from my SGH-I727 using Tapatalk 2

Ive run every leak that's came out ucalc4 ucld2 and now ucle2 and I've had absolutely no problems. I've flashed cwm touch and rooted all 3. I've did factory data resets inside the UI and in cwm. I've wiped cache dalvick cache and battery stats several times on all 3 leaks. I've flashed different modems and kernels and yes I've even formatted the SD both inside the UI and in cwm and I've had no problems. And yes chainfires brickbug app says my phone is at risk for being bricked. But I had already done all this stuff mentioned before I found out there was even a problem. So if your worried about the brickbug then maybe you should just stay on stock gingerbread. If your scared to take a risk and push things to the very edge then maybe xda isn't for you... we are a group of devs and tech savy people who test and push things to the edge to learn new things and make android phones better. Anytime you flash a rom or recovery image or modem or even root a phone you run the risk of a brick. I know people who have bricked phones with Samsung kies doing a official update. So if bricking scares you that much then just stay stock
Sent from my SAMSUNG-SGH-I727 using xda premium

The brickbug happens on ics kernels.
So.. wiping all that stuff from cwm (which seems to be based on gb kernel) is fine.
Do not format from within ics rom!
You may not corrupt your emmc, but its not worth the risk.
sent from my I727 TROLLING DEVICE using XDA premium.

treo750ii said:
Are there any rom /kernals still out there that have the emmc bug in them? I want to flash an ics rom, but with all the stuff floating around I'm a little nervous. Sorry if this has been asked before, I did a quick thread search on the phone and didn't find anything.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
read this on what not todo http://forum.xda-developers.com/showthread.php?t=1621679

vincom said:
read this on what not todo http://forum.xda-developers.com/showthread.php?t=1621679
Click to expand...
Click to collapse
Thanks!!!! Really appreciate the info!
Sent from my SAMSUNG-SGH-I727 using XDA

Can't flash Beatmode v4, any suggestions?

I've tried flashing v4 probably 4 or 5 times now. I've even tried v3 a couple times. Neither stuck... Ove contemplated just factory reset then going through the whole process again..
What am I doing wrong/not doing?
All caches get wiped before flash.
EDIT: I was just able to flash over the ElementalX kernel just fine. I'm still confused on why Beastmode isn't flashing. When I go to install from TWRP, the .zip install time is no less than 2-3 seconds long and then it says finished.
Sent from my HTC One XL using xda app-developers app

Really... 151 views and not one person has a suggestion?
Sent from my HTC One XL using xda app-developers app

The kernel didn't stick or the CPU settings?
I went into setcpu and it said min 384 max 384 after flashing the kernel.. so I sent min to 384 and max to 1809 and applied set on boot. That worked for.me, but I notice a few bugs. Like the lockscreen won't unlock so I have to hard reboot
Sent from my HTC One XL using xda app-developers app

The kernel...
Sent from my HTC One XL using xda app-developers app

Myrder said:
I've tried flashing v4 probably 4 or 5 times now. I've even tried v3 a couple times. Neither stuck... Ove contemplated just factory reset then going through the whole process again..
What am I doing wrong/not doing?
All caches get wiped before flash.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Don't post threads unless you've tried full wipe. No one knows what's wrong if you're doing a dirty flash.

Myrder said:
The kernel...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Works for me and I use SetCPU..

Might just do a factory reset and see if that won't solve my problem.
Sent from my HTC One XL using xda app-developers app

work yet? I have the same problem and i am on stock .....wiped dalvik,cache, before i flashed it....it just says sucessfully installed...it flashes very quickly for some reason when I know it should not...did a recovery before i flashed, recovered....still nothing..

Literally just did the factory reset and didn't do a thing. So I just rebooted my backup and am now going on about my business. I'm almost to the point of giving up unless something else pops in my head besides running my RUU and then trying to flash again... too dang lazy for that right now. been trying to think all day and now I have quite a few beers in me, it wouldn't be safe.

Myrder said:
Literally just did the factory reset and didn't do a thing. So I just rebooted my backup and am now going on about my business. I'm almost to the point of giving up unless something else pops in my head besides running my RUU and then trying to flash again... too dang lazy for that right now. been trying to think all day and now I have quite a few beers in me, it wouldn't be safe.
Click to expand...
Click to collapse
Don't do it! IceColdJelly isn't worth it!

absolutelygrim said:
Don't do it! IceColdJelly isn't worth it!
Click to expand...
Click to collapse
Lol, I should say that it would only be a test.. There is no way I am getting rid of ViperXL 2.1.2. Love this ROM.
You think I may have done something with my phone to where it wouldn't install v4 when I tried to flash over the ViperX ROM do you? I keep thinking about that, I don't know if that would have any effect on anything considering I was able to RUU back to stock and flash my current ROM.

Myrder said:
Lol, I should say that it would only be a test.. There is no way I am getting rid of ViperXL 2.1.2. Love this ROM.
You think I may have done something with my phone to where it wouldn't install v4 when I tried to flash over the ViperX ROM do you? I keep thinking about that, I don't know if that would have any effect on anything considering I was able to RUU back to stock and flash my current ROM.
Click to expand...
Click to collapse
That brings up a good point.. but since your RUU'ed it should have gotten rid of any corruption applied by the international ROM..
edit: btw, IceColdJelly is an international ROM that will brick your phone,, currently there is no fix (for 2.20).. don't even try it buddy

absolutelygrim said:
That brings up a good point.. but since your RUU'ed it should have gotten rid of any corruption applied by the international ROM..
edit: btw, IceColdJelly is an international ROM that will brick your phone,, currently there is no fix (for 2.20).. don't even try it buddy
Click to expand...
Click to collapse
This I know, I saw that when I found ViperX 2.6 in the international thread... Going to try the stabilizer from the v4 thread and see if that will work. read a post about page 14 +/- a page said to try the stabilzer and see if that would work.
Edit: Speaking of no fix for bricked 2.20, how's that coming? Jtag looking like the only method so far? Haven't read your WIP thread in awhile.
Edit2: Stabilizer didn't do a thing. I really want to be able to flash this kernel... :crying: Seems like it does a really nice job for everyone that has it working... Might end up with going back to RUU again, when I feel I am competent in flashing everything correctly, in the next day or so.

So I've tried another option..
Trying to pull the boot.img from the kernel using "adb pull /tmp/abootimg". Since that looks like where it makes the boot.img in Aroma. Didn't work.
Just flashed ElementalX v1.14 and that works just fine.

Problems with nexus s 4g

Every time I put my phone to sleep it freezes and reboots. Sometimes it'll reboot fine, others it'll freeze on the google boot screen until I pull the battery. I've tired 4 different ROMs from locked stock to unlocked Cm9 to baked and slimbean. I've tired dirty flashing. I'm out of ideas now. If anyone could help out I would greatly appreciate it.
Sent from my Nexus S 4G using xda app-developers app

Flash stock? Try a different kernel then ROM specific. Factory reset.
Sent from my vangogh using xda premium

My knowledge ends at locking/unlocking and flashing ROMs. How do I change kernals and how would I know which one to change to?
Sent from my Nexus S 4G using xda app-developers app

aquag said:
My knowledge ends at locking/unlocking and flashing ROMs. How do I change kernals and how would I know which one to change to?
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Changing kernels is exactly like changing ROMs. You flash them, although, you have to wipe cache and dalvik cache every time you change a kernel. Look in the developer section for our phone, there are 3 kernel choices: Matr1x, Marmite, and Air Kernel. Test each out on different ROMs, find your favorite. Be sure though, if you're going to be hopping between Android versions (4.0.4 (ICS), 2.3.7 (GB), and 4.1.1/4.1.2 (JB)) You find the version of the kernel that corresponds with whatever version of Android the ROM you're using is running. As far as I know, Marmite is only available for JB, Matr1x has kernels for all versions of Android (GB-JB), and I think Air only has ICS and JB versions. Hope this helps!
Sent from my Nexus S 4G using Tapatalk 2

aquag said:
Every time I put my phone to sleep it freezes and reboots. Sometimes it'll reboot fine, others it'll freeze on the google boot screen until I pull the battery. I've tired 4 different ROMs from locked stock to unlocked Cm9 to baked and slimbean. I've tired dirty flashing. I'm out of ideas now. If anyone could help out I would greatly appreciate it.
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Hi..
It either some junk files u have floating around ur SD card..
Or
Are u tweaking the CPU when u install the ROMs?
Or
Are u using titanium backup to restore any of ur apps?
Try to do the entire factor reset/ wipe both cache & dalvik but also flash a zip file call "wipe all" ( it formats everything under storage and mounts except the SD card stuff)
Then flash the newest slim bean 3.0 it comes with a good kernel
Flash it and do not add anything. Check if the sleep reboot issues still occur.
If not then make a backup b4 adding ur apps and restores since one of those can be causing it.
I hope it works... good luck
Vs Nexus S4G using tapatalk2

[Q] Will HTC__044 (WWE_Asia) work on HTC__038 (India)

Can someone please tell me if I can your this RUU for my HOS CID:HTC__038 (India make). I want to go to stock in order to update to 4.0.4 but dont have a back up. Please help!

I have a nandroid backup you can restore it on your device if you want but only problem which I.am.facing is WiFi and data won't work after restoring the Rom back to stock...
Sent from my HTC One S using xda premium

torque2584 said:
I have a nandroid backup you can restore it on your device if you want but only problem which I.am.facing is WiFi and data won't work after restoring the Rom back to stock...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Well if you can provide me with a link to download it I will give it a shot and try to fix from there on. Do you know why is that happening? Is it to do with the nandroid you have or a issue with porting from one phone to another?

Sorry buddy... It won't be possible for me to upload the Rom, as I am out of town....It will be only possible after a week.... And the problem its causing may be because of boot.IMG if you can get the boot.IMG which is compatible it will surely work
Sent from my HTC One S using xda premium

You can download a HTC__044 OEM ROM here in my Thread...
http://forum.xda-developers.com/showthread.php?t=2011598
Sorry, oder CID´s won´t work on HTC__044

I guess not
I don't think the HTC__44 will work on the HTC__038. I have got the second model and I have tried to load an European RUU but I didn't get it because it said the Customer Id (CID) was wrong.
I guess the same will happen with the Asian RUU.

Why cant we change CID inside the RUU?
torque2584 said:
Sorry buddy... It won't be possible for me to upload the Rom, as I am out of town....It will be only possible after a week.... And the problem its causing may be because of boot.IMG if you can get the boot.IMG which is compatible it will surely work
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Thats ok. Once I get the nandroid I will be able to play along with it i guess. I tries installed the CID__044 but it got stuck in the middle as it always does for the wrong version ones. I dont see why it has not been possible to tweak the RUU to be fooled into feeling it is a different CID and not the other way round. Like change the CID code for the RUU. Just a random thought.
javism1 said:
I don't think the HTC__44 will work on the HTC__038. I have got the second model and I have tried to load an European RUU but I didn't get it because it said the Customer Id (CID) was wrong.
I guess the same will happen with the Asian RUU.
Click to expand...
Click to collapse
Somewhere I had read that the asian WWE ones can be cross installed. So was just giving it a shot. Anyways tried and it failed so I may be quoted for the same.
mr.trader said:
You can download a HTC__044 OEM ROM here in my Thread...
http://forum.xda-developers.com/showthread.php?t=2011598
Sorry, oder CID´s won´t work on HTC__044
Click to expand...
Click to collapse
Ya I have the HTC__038. It is so annoying that HTC is damn specific. Samsung lets you flash any country using ODIN. If HTC is being so uptight they could at least release the country specific RUUs on the respective Dev sites.

Any idea why we don't have even 4.0.4 yet?
Update : downloading 4.0.4 update right now
Sent from my HTC One S using xda app-developers app

'AL' said:
Any idea why we don't have even 4.0.4 yet?
Update : downloading 4.0.4 update right now
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hey are you on HTC__038 ????

Yes... Didn't you get it yet?
Sent from my HTC One S using xda app-developers app

'AL' said:
Yes... Didn't you get it yet?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am a super dumbass who lost his stock backup while on Trickdroid. Need to get back to stock to update. Hence running amok trying to score a RUU..
any suggestions??

Try at your service centre... Sweet talk the guy there into flashing the RUU .. they are bound to have the RUU... Its worth a try
Sent from my HTC One S using xda app-developers app

'AL' said:
Try at your service centre... Sweet talk the guy there into flashing the RUU .. they are bound to have the RUU... Its worth a try
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yup going today to do it. Hope he is not a bone head like the last one. Had forgotten to lock OEM when I took it to them. Said that they need to send it to Bangalore for retesting. Anything else you suggest I should do before taking to the repair guys??
(Apart from the backups and OEM relock bit)

Well the idiots at HTC could not fix it. Back to square 1. boo hoo!!

The issue that your having, is it because you did not take nandroid backup? I want to install trick droid but want to make sure i will be able to get back to stock..
Sent from my HTC One S using xda app-developers app

'AL' said:
The issue that your having, is it because you did not take nandroid backup? I want to install trick droid but want to make sure i will be able to get back to stock..
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Well If you wanna install TD its simple. Make a backup of your present system. But SAVE A COPY OF IT ON YOU PC, it will in you TWRP folder. This is where I went wrong. After upgrading ROM I got bootloop. Just restarted the phone to recovery and the SD card got locked. In order to unblock the SD card had to reformat and kaput!! I know there are ways to fix the issue I told earlier but chances of hard-bricking becomes high. This will be simpler! remember to back up the entire phone on PC before messing with ROMS. :silly:
So ya, TD is safe and stable. If you already on 4.0.4 go for TD v4. else you will have to start from v2 and move your way up!. if you need more help just post back.
Happy to help.
PS: Do you have a backup of you older version of stock. If possible can you upload whatever stock you have. I will PM you my public dropbox address if you need it!

That's the thing... since there was no India ruu i never tried to mess with the roms.... Have been on stock always.... The only reason I want trick droid is for Google now... But won't if there is a chance that I may not be able to get back to stock plus I'm fed up of restoring apps and data from my previous phone every time I change ROMs
Sent from my HTC One S using xda app-developers app

'AL' said:
That's the thing... since there was no India ruu i never tried to mess with the roms.... Have been on stock always.... The only reason I want trick droid is for Google now... But won't if there is a chance that I may not be able to get back to stock plus I'm fed up of restoring apps and data from my previous phone every time I change ROMs
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Well I have managed to screw more than once while trying to install ROMs and the TWRP backups have always delivered. Not once have I had a problem. So if you follow the steps the way I mentioned I believe you wont be sorry. Just keep a backup outside the phone. Something people dont mention while installing ROMs!!
Plus google now is completely pathetic if you ask me. havent used it once and had to revert back to normal google as it kept popping things without need!! Guess its more guess for people always on the move.

I think I'll wait for official jb ... Have no real problems with the current rom and I'm too lazy for new rom setup... Is there any way to only root while remaining on stock and keeping the ability to get ota updates intact?
Sent from my HTC One S using xda app-developers app

'AL' said:
I think I'll wait for official jb ... Have no real problems with the current rom and I'm too lazy for new rom setup... Is there any way to only root while remaining on stock and keeping the ability to get ota updates intact?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Well you are on stock as long as you don't install a custom ROM! Using a custom recovery will not kill your OTAs so just Unlock bootloader using HASOON's Method. I think it is the easiest. you could try adb if you are comfortable with it. Use goomanager to get TWRP. any other method will be a lot more complex. then have all the rooted privileges without loosing stock. Just make sure to lock bootloader before getting an OTA. thats all.
PS: The above it just speculation from my own reading through the forums. I was on a rooted stock system for a while and it worked fine. Theoretically what I have mentioned should work but post it on some of the dev forums to get a proper reply!