Telstra ROM showing update available to ICS
System upgrade to 3.44.841.3
Anyone else getting this?
My phone is on the standard Telstra ICS ROM, however is S-off and unlocked... and has recovery if I update will this bork my phone?
Download Here https://docs.google.com/open?id=0B_yipCshKsIQa3B6bHl6UnVDMGs 58.8MB
I upgraded to this about 2 days ago, admittedly on a stock Velocity....rumblings seem to say that this is a radio fix from Telstra only at this stage (and an unsuccessful one at that)
Ah righto, I attempted applying it but it just made my phone display a belly up android with a hazard sign sticking our of its belly, I'm uploading the file now for people to play with should be done soon :laugh:
I did the upgrade on stock too, any idea what it was supposed to fix? I've yet to notice any differences, not that I noticed any problems before...
Sent from my HTC Velocity 4G using xda
I do believe this article may enlighten you.
Not sure.. That's really for the nexus in US only. Maybe related...
One thing I just noticed with this update is that it finally muted the camera sounds when the phone is on silent
Leigh Kennedy said:
I do believe this article may enlighten you.
Click to expand...
Click to collapse
I'm not sure that's it. The patent in my understanding is about apps/contacts/other stuff showing up in the universal search, which mine still does after the update.
Update fails. any hints welcome
I have a Velocity with the OTA 4.0.3 ICS update. When I bought it I tried to root it using hansoon2000s 1 in all kit. I did unlock the bootloader, but attempts to gain root access failed so at that time I relocked the bootloader and just forgot about it.
When I try to install the 3.44.841.3 update, the phone shuts down then reboots to the FASTBOOT menu which gives me the option of
BOOTLOADER,
REBOOT,
REBOOT BOOTLOADER or
POWER DOWN
and it shows at the top *RELOCKED*.
If I select BOOTLOADER I go to the HBOOT menu and I can see
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
I have limited skills but I am guessing if I got to the recovery menu I would be able to choose a zip file to run and I could point it at the OTA zipfile which it downloaded, but when I go to recovery it just goes back to the FASTBOOT menu.
Any ideas which course of action I should take. Because it's not rooted I don't have a good backup of app data so I'd really prefer not to take any action which is going to set the phone back to Factory unless I am fairly certain of the outcome. I'm still not even sure that I need to apply this update because I have no issues with my phone (but just for the sake of the exercise lets presume I'm trying to load a Jellybean OTA update, which is something I definitely would want to do even if I reset the phone).
Ideas or suggestions ?
Bro use all in one to unlock bootloader from the menu your talking about select recovery then when it boots into a recovery you chose from the all in one use the volume to navigate to the zip file there's a prerooted gb one that I'm using then once you install it and phone reboots let the phone update to ics
Sent from my HTC PH39100
I've got a feeling that this may have updated the Velocity to a custom hboot version, because now I'm having all sorts of trouble with custom kernals and roms. Investigating now to make sure it's not my own derpiness that's causing this.....
Demomanca said:
I've got a feeling that this may have updated the Velocity to a custom hboot version, because now I'm having all sorts of trouble with custom kernals and roms. Investigating now to make sure it's not my own derpiness that's causing this.....
Click to expand...
Click to collapse
Yeah same thing happened to me because of using a deodexed rom, but you can get it fixed pretty easily.
Only problem is I don't know how to get the update to work with the stock rom as i doesn't keep. I assume leigh kennedy knows how to apply the update to stock rom and then deodex, as he did it the for stock. Hope he does it for this too.
does anyone know exactly what the update does or are we all in the dark about it? It looks like its just an update to a few APK's, using my
*mad grand karate master winzip skillz, yo*
Is it a radio fix or what?
davidcampbell said:
does anyone know exactly what the update does or are we all in the dark about it? It looks like its just an update to a few APK's, using my
*mad grand karate master winzip skillz, yo*
Is it a radio fix or what?
Click to expand...
Click to collapse
Google result said the update was to fix radio reception issues for some users, I think it was mentioned on whirlpool and a telstra support site.
OTA update.
Hi I also have received the notification for an OTA update with a link to HTC.com for my Velocity 4G, But I am running "nightly Build 4" since it came out and it is running like a dream. I also got the error msg with Mr android, belly open and a triangle warning sign. Not surprised tho. However I am thirsty still and ofc with Jelly Bean bouncing in I am tempted to flash the new ROM when it is avail.. Any ideas when it will be? :fingers-crossed:
How can I flash this OTA manually?
My Velocity is stock non rooted an locked.
The phone is stuck at the HTC screen so really only have access to fastboot...
Also, does anyone have the stock build.prop for the velocity 4g?
Ryyuu said:
How can I flash this OTA manually?
My Velocity is stock non rooted an locked.
The phone is stuck at the HTC screen so really only have access to fastboot...
Also, does anyone have the stock build.prop for the velocity 4g?
Click to expand...
Click to collapse
If you have access to fastboot, try running the RUU while connected in fastboot (drivers must be installed). This will put the phone back to a factory state, then you can check for and install the OTA
Any word on this coming to rogers? I would hate having to revert to stock to accept the update
Screw the update lol
Sent from my Holiday using xda app-developers app
Homeslice's PACman ROM doesn't prompt me for an update
Sent from my Holiday using Tapatalk 2
Related
Please forgive the idiotic sound of this.
I have experience rooting and flashing ROMs. Did it a lot with my Nexus One, Aria, and Inspire. I have no idea why what i am trying isn't working. I was intending to remain unrooted as long as possible on this new phone.
Stock unrooted Vivid from AT&T
purchased the day of the leaked OTA, but didn't grab it before AT&T turned off the 682 code.
I have downloaded a copy of the OTA file that was posted by another XDA member, and have a copy of it at the top level of internal memory AND a copy at the top level of my SD Card.
I made more copies of the file, and tried renaming one copy PH39IMG.zip, and the other copy update.zip and placed them also at the top levels of both memory places.
Booting into bootloader; the phone sees the PH39IMG file, loads it, checks it, and then does nothing with it. I try selecting recovery and applying update. Phone doesn't apply update and reboots to normal.
What the heck am i missing here?
Sent from my HTC PH39100 using Tapatalk
Hey I too came from the HTC Aria so this was a learning experience for me too. What rom are you trying to flash. i can try to walk you through the steps as I did it. If you are are locked you can just run the RUU to upgrade to ICS. From there I can guide you on how to flash a rom.
It appears as though the AT&T update is being officially pushed out now. I was able to take my stock, unrooted, locked bootloader Vivid and update the normal way (select software update).
No need to mess with anything...just go ahead and get ICS like you would get any software update.
anthromatt said:
It appears as though the AT&T update is being officially pushed out now. I was able to take my stock, unrooted, locked bootloader Vivid and update the normal way (select software update).
No need to mess with anything...just go ahead and get ICS like you would get any software update.
Click to expand...
Click to collapse
I can confirm this! Downloading now!
I'll be darned. now i just have to wait until i get home to wifi.
Sent from my HTC PH39100 using Tapatalk
My wife has a vivid and she went through with the update that was poping up even though I told her not too until I fixed it. It was on 4.0.3 before 1.85 I believe, and then updating to 2.2 is the attempt.
The phone is rooted and unlocked, s-on
I don't mind the update happening but when the phone restarts to do the update, it starts and then jumps to a screen with the android, with his belly open and a red danger sign and just sticks there.
What do I do now, to get this update done and back to root/unlocked?
maxpower2078 said:
My wife has a vivid and she went through with the update that was poping up even though I told her not too until I fixed it. It was on 4.0.3 before 1.85 I believe, and then updating to 2.2 is the attempt.
The phone is rooted and unlocked, s-on
I don't mind the update happening but when the phone restarts to do the update, it starts and then jumps to a screen with the android, with his belly open and a red danger sign and just sticks there.
What do I do now, to get this update done and back to root/unlocked?
Click to expand...
Click to collapse
Wrong section.....and is this the new update after ICS?
camo_flage said:
Wrong section.....and is this the new update after ICS?
Click to expand...
Click to collapse
what section should it be in and yes, this would be the most recent update, I believe it moves the android from version 4.0.3 to 4.0.4 I think
maxpower2078 said:
what section should it be in and yes, this would be the most recent update, I believe it moves the android from version 4.0.3 to 4.0.4 I think
Click to expand...
Click to collapse
This should be in the Q/A section and I don't think it does. it was just a minor update for sensor issues or something like that. Have you tried running an RUU?
camo_flage said:
This should be in the Q/A section and I don't think it does. it was just a minor update for sensor issues or something like that. Have you tried running an RUU?
Click to expand...
Click to collapse
wow, I have too much to learn about this stuff. I just switched services and was on a spring phone (CDMA) there is a lot of differences, I don't even know what RUU is so will do some reading
maxpower2078 said:
wow, I have too much to learn about this stuff. I just switched services and was on a spring phone (CDMA) there is a lot of differences, I don't even know what RUU is so will do some reading
Click to expand...
Click to collapse
Lol you are not alone everyone needs to start somewhere
Sounds like a botched install. You will likely need to re-install from RUU.
You'll need to re-lock the bootloader, and download whatever RUU you want. The RUU is basically the downloadable Windows Installer version of what the carrier pushes via OTA update. You can find one for each of the main carriers. In my experience, it doesn't matter which carrier you install (for example, my phone when purchases was Rogers, but I flashed a Bell RUU, then flashed roms based on AT&T and Telstra afterward).
Look at the Superguide sticky thread in the Dev section, and it will (hopefully) answer all your questions. It has the steps for re-locking and un-locking, links for the RUU's, and (I think) I guide for installing the RUU, though it's really straight forward. Once you have the RUU installed, and are starting fresh again, you will have to un-lock the bootloader and root again, or just flash a custom rom after re-installing a custom recovery (CWM, TWRP, etc).
Good luck, and don't be afraid to post back here if you have any issues. But make sure you read the superguide top to bottom at least twice. It will give you an idea of what steps are preformed in what order and why. Even if you don't need to do all the steps, at least you should have an understanding of what's actually going on.
DO NOT INSTALL CWM...
It corrupts partitions...
I recommend twrp
Sent from my Vivid 4G using Tapatalk 2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sent from my HTC Raider on the Rogers Wireless Network
Thank you everyone, I was able to get it back to before the update. The wife was complaining about "what does this root thing get me anyways" after this trouble so I am just going to unroot it, do the OTA update and let me have it. Is she ends up wanting something different I will step in.
Great to hear!
Sent from my HTC Raider on the Rogers Wireless Network
Hi to all
Bought a razr i in mint condition on saturday it was on 4.0.4 81.5.31002.XT890.Retail.en.GB, so hearing about all the possible update to jellybean I checked through the menu to see if one was available.Then was prompted to download 81.5.39001.en.GB (56.7MB) so I download this update over wifi ,while plugged in and charged properly.The download finishes and the phone reboots the big m shows up and it goes to the android update screen runs for a while,then the robot appears horizontally with an exclamation mark after which itreboots to normal phone screen in maybe 50 to 60 seconds.As soon as the screen shows up a system message shows up saying "update failed"?
I have done this a good few times now and am sure it isnt going to work.Does anyone have any ideas what is causing it or how to fix?As far as I know the phone has never been altered but cant be sure.Any ideas?Should I return the phone?I am fairly profiicent with phones but did not really intend to do anything to the phone that might invalidate warranty.
Any help is appreciated
Scotty I'm no expert at this can you download the update again will the phone let you?. Maybe you can try a factory reset I'm quite sure that the jb update for retail GB has not touched down yet in UK so the update is a old ICS one. you could unlock you're bootloader and flash one of Matt's homemade fast boots etc which you'll find on the forum here
Sent from my XT890 using xda app-developers app
dog121 said:
Scotty I'm no expert at this can you download the update again will the phone let you?. Maybe you can try a factory reset I'm quite sure that the jb update for retail GB has not touched down yet in UK so the update is a old ICS one. you could unlock you're bootloader and flash one of Matt's homemade fast boots etc which you'll find on the forum here
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
Yep, I can confirm that version 81.5.39001.en.GB is ICS unfortunately
Hi thanks for the input.Yeah it will let me download it again.But it never installs "system update failed" every time.Also I know this is still ICS was just saying I had checked system update because of jelly bean.
Am beginning to wonder if there is any way this can be fixed without unlocking bootloader/or rsd?Not really wanting to interfere with it given that all updates so far have failed.I have downloaded the same stock rom I am on.Am thinking I can flash this through rsd without unlocking bootloader?
scotty7910 said:
Hi thanks for the input.Yeah it will let me download it again.But it never installs "system update failed" every time.Also I know this is still ICS was just saying I had checked system update because of jelly bean.
Am beginning to wonder if there is any way this can be fixed without unlocking bootloader/or rsd?Not really wanting to interfere with it given that all updates so far have failed.I have downloaded the same stock rom I am on.Am thinking I can flash this through rsd without unlocking bootloader?
Click to expand...
Click to collapse
I think your best bet is to wait for the official jb retail update which should be quite soon now as all the carrier updates have been pushed out now
Sent from my XT890 using xda app-developers app
I see what your saying I am just worried that if the phone wont do the ota I have then it will never get to any other jelly bean or not update.
thanks for the input
It seems I cannot get my windows 8 or 7 laptop to "see" my phone in fastboot at all.Also tried rsd etc have looked at various guides etc and used fastboot before with numerous other devices but this one I cant.Very odd?So it wont ota update and not seem to enter fastboot properly ie the laptop cant see it.Is this a sign of anything?I have used this fastboot before lots.So I have lots of new up to date drivers etc
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?
Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.
well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?
AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk
If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
Hasn't this already been discussed in the update thread? Flash the stock ATT JB, then accept the update.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
devilsking said:
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
Click to expand...
Click to collapse
Same here!
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
magocop said:
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
Click to expand...
Click to collapse
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
audit13 said:
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
Click to expand...
Click to collapse
Did you have to call Bell to get that customer recovery? And where can I get one at?
skeevydude said:
Did you have to call Bell to get that customer recovery? And where can I get one at?
Click to expand...
Click to collapse
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
audit13 said:
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
Click to expand...
Click to collapse
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
skeevydude said:
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
Click to expand...
Click to collapse
No worries. Good thing you brought the error to my attention; otherwise, Bell would start receiving requests for the "customer" recovery files:laugh:
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
I probably did when i first figured out how to use custom roms i was trying a whole bunch of them but that was awhile ago and now i dont remember how to flash a stock recovery or where to get it and i did awhile ago use RSD Lite to flash a stock rom onto my phone but that is the last thing I did and know its been sooo long i dont remember how any help from anyone would be greatly appreciated and sorry i have not got back to this post in a few days been busy doing other things but once again if anyone could help me it would be appreciated
Thanks
- Bart
Try using Myth Tools to flash back to stock, take the update, install a custom recovery, and flash a KK ROM.
http://forum.xda-developers.com/showthread.php?t=2262726