Database Info

Poking at latest OTA update for fun and profit

I am poking around the latest official OTA update (get it here).
I am trying to see if there is anything useful for aftermarket roms. I will post
here my findings, if any, and all the questions that pop to my mind. Hopefully
someone in the community will have answers.
The updating script does the following:
1) several checks on bootloader/recovery/cid/device version
2) copy fotaBoot to /data/system/fotaBoot to trigger some changes at reboot
3) checks on files to be patched
4) delete several files from /data (notably adio_checksum, DxDr,
SuplRootCert_injected)
5) delete lots of files form /system
6) apply patches
7) copy files into /system
8) set permissions
9) flash firmware.zip via
Code:
write_firmware_image("PACKAGE:firmware.zip", "zip");
Among the files being modified there are a couple of firmwares (yamato_pfp.fw
yamato_pm4.fw). I do not have them on my system (I run CM7) and I have no idea
which piece of hardware they refer to. There is also an app whose purpose I
ignore (HTC-DPM-GB-2.3-48637-11.1.apk) and a mysterious recovery.img in /system
(more on this later).
Does anyone know the exact procedure by which firmware.zip is flashed? Will any
check be performed on it? Its content is the following:
* android-info.txt: ASCII file with some version numbers.
* boot.img: should be the new kernel+ramdisk; I tried booting it with few
expectations and indeed it wont boot with a non-sense /system
* hboot_8x60_DOT_1.45.0013_20111121_signedbyaa.nb0: the new bootloader; I see no
reason to flash this unless it provides some new features.
* radio.img: fat image with radio files (should be safe to flash)
* rcdata.img: ???
* recovery.img: this won't boot; may it require the above mentioned recovery.img?
Anyway this is completely useless
* rpm.img: ???
* sbl1.img: ???
* sbl2.img: ???
* sbl3.img: ???
* tz.img: ???
Anyone has ideas on what the other files are? I assume that if we avoid flashing
hboot we will always have fastboot available to us and S-OFF to flash anything
we would like to, correct? Revolutionary team can you please explain how you
make the phone S-OFF once your exploit gives you the right privileges? Will any
of those files affect it? Has anyone here any idea of which partitions should
they be flashed to?
As I said I tried to boot both recovery.img and boot.img to get a config.gz and
kernel version with scarce success. I'd like to see whether they made some modifications to the
kernel which improved battery life. I think I will repack the new kernel with
CWM recovery and get the info from there.
Ideas of things to poke at? Comments? Helpful insights?

Related info: here .
sbl*.img might be the boot loader. (secured/secondary boot loader???) but why in 3 separate chunks?

More info: here
rcdata.img is text; it should be the configuration of the radio but if I check the content of the corresponding partition (mmcblk0p18) on my phone there is a lot of binary junk together with the small amount of text. The options are the same except for one (AGPSNVSetting) that is missing in the updated rcdata.img
Code:
# cat /dev/block/mmcblk0p18 | strings | tail -n 9
QCT_UMTS_RADIO_VER=1
DisH=2
AGPSNVSetting=1
EnDTM=0
MSCMode=10
HSDPACat=10
HSUPACat=6
GEA3=0
QCT_UMTS_RADIO_END=1

I know probably the biggest request from the community is to figure out how to root the update; it seems that the Rev. team has been notified that the exploit they used before seems to have been patched in this update.
Also very profitable would probably be zips for the new kernel and radio, if possible. Early reports have indeed been of better battery life, and also higher quadrant scores.
Anyway, many thanks for this thread, and for looking at the update

Etn40ff said:
Among the files being modified there are a couple of firmwares (yamato_pfp.fw
yamato_pm4.fw).
Click to expand...
Click to collapse
Just a shot in the dark, but Yamato is refered to here:
http://code.google.com/p/synergy-ki.../system/etc/adreno_config.txt?spec=svn41&r=41
It seems to have something to do with the adreno chipset...

There's a Pre Rooted Version of the OTA Update on Rootzwiki. I would imagine those on XDA would be rooted all ready. I understand trying to find a way to Root the OTA Update for those who had it before they could root. But wouldn't a simple Temp Root, then Downgrade work? That's what I had to do with my G2 and G1.
Sent from my MyTouch_4G_Slide using xda premium

Litesorrows said:
There's a Pre Rooted Version of the OTA Update on Rootzwiki. I would imagine those on XDA would be rooted all ready. I understand trying to find a way to Root the OTA Update for those who had it before they could root. But wouldn't a simple Temp Root, then Downgrade work? That's what I had to do with my G2 and G1.
Sent from my MyTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
the version on Rootzwiki isn't the newest update, the one that just came out 3 days ago. and the newest update has proven impervious even to temp-root so far. the only way to downgrade is if you were S-OFF before updating. there is a thread on this in the general section.....

If you updated, please view this thread.
http://forum.xda-developers.com/showthread.php?t=1405859

I had pulled the new google talk app and made it flashable on request, here's the link:
Gtalk update
There are a couple others if anyone wants them - deskclock, wifi calling, t-mo mall and carbon backup, netflix, and two logging utilities.
The rest is all small updates to a lot - what I wanted to look into first were the GPS updates to make sure my patch stays as current as possible.
You can either pull apart the package directly, or flash the update and do an adb pull to grab new stuff - backup guide in my sig tells you all about using the adb pull command.
Now that we know you can rewind the changes and get root back after the update, either should be fine. I've been going through the download zip, but haven't had much time at my workstation.
I have a couple emergency shifts to work, kept me offline yesterday & today, I'll check back on a break later and see if I have anything else to add.
Sent from my Bulletproof_Doubleshot using xda premium

Blue6IX said:
I had pulled the new google talk app and made it flashable on request, here's the link:
Gtalk update
There are a couple others if anyone wants them - deskclock, wifi calling, t-mo mall and carbon backup, netflix, and two logging utilities.
The rest is all small updates to a lot - what I wanted to look into first were the GPS updates to make sure my patch stays as current as possible.
You can either pull apart the package directly, or flash the update and do an adb pull to grab new stuff - backup guide in my sig tells you all about using the adb pull command.
Now that we know you can rewind the changes and get root back after the update, either should be fine. I've been going through the download zip, but haven't had much time at my workstation.
I have a couple emergency shifts to work, kept me offline yesterday & today, I'll check back on a break later and see if I have anything else to add.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
could i get deskclock, wifi calling, and netflix

Yamato is gpu proprietary files. U would use them in a compile against source code for the improvements. I would say kernel fixes would be the main thing if reports are better quadrant and battery life
Sent from my MB525 using XDA App

I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.

Where did you get the stock/signed T-Mo PP59IMG.zip? Can't find it anywhere here. Thanks.

monakh said:
Where did you get the stock/signed T-Mo PP59IMG.zip? Can't find it anywhere here. Thanks.
Click to expand...
Click to collapse
Link in quote below:
yogi2010 said:
sure Blue, it is pretty much the usual...
To undo the update/restore the stock firmware that came with the phone:
(Note: this will only work if you are still S-OFF even tho you have the new HBOOT version. If you are S-ON with the new HBOOT, then at this time there is no known way to revert... hopefully we can get the devs. of Revolutionary, etc, to update the root methods. Also, if you want to update just to check it out, make sure to turn S-OFF first if you'd like to give yourself the option to revert later.)
1. Download the stock firmware package from here: http://forum.xda-developers.com/showthread.php?t=1178082
2. Rename it PG59IMG.zip and put it on the root of your sdcard.
3. Boot into the bootloader('adb reboot bootloader' or power down the phone then hold volume down + power), let it read the update package, and press 'volume up' to update when prompted.
4. At the end it will prompt you to press Power to reboot. It scared me because when i pressed Power, the screen went off and seemed to not come back on, so i pressed power once again, and it booted into the system.
That's it! Just remember that if you do this, it will of course erase all your data... your phone will be like it was out of the box.
Click to expand...
Click to collapse

I'm not sure if this helps anyone, but here is the boot.img taken from my nandroid of the newest OTA ROM:
http://db.tt/GHfzWNIj
come to think of it, looks like you might already have this in the OTA zip... although this one is a bigger file...

Two questions:
1. How do you flash this update? When I click the HTC Update, it gave me the ~5MB update, however not the ~40MB one. So is there a way to manually flash it?
2. Is there a way to doing so without loosing the recovery and root?

Sinfamy said:
Two questions:
1. How do you flash this update? When I click the HTC Update, it gave me the ~5MB update, however not the ~40MB one. So is there a way to manually flash it?
2. Is there a way to doing so without loosing the recovery and root?
Click to expand...
Click to collapse
You can download the update and run it manually. I can't remember if I renamed it update.zip and flashed it through stock recovery or used the bootloader.
If it was the bootloader, rename the downloaded zip to PG59IMG.zip, put it on the root of your sdcard and boot into the bootloader. The device's screen should prompt you with install instructions.
As for keeping root and recovery, no. As long as you are S-OFF *before* doing this, however, you can re-flash a custom recovery and re-root using these instructions: http://forum.xda-developers.com/showthread.php?t=1433805

Yeah, the update flashed nicely thru the stock recovery. I learned once you get to the recovery screen, you press volume up + power to get the options to show up.

[TMOUS] Updating your rooted device to 1.84.531.2 using OTA

Hello everyone,
rhcp did some work with the One S and even bricked a device over it regarding this update. Great news though, he was able to locate the CORRECT method that HTC uses to update via OTA for those who want to flash this.
Before we get to the goods, please understand that I am not responsible for any bricks or other issues. I'm just passing along information from someone who has done great work for the Android community and has already risked his device to locate this method.
Please help him by donating if this was able to help you, this method definitely cost him some money in the end .
Click Here for Instructions
Thanks guys, I really hope this helps!
-h8

This is for TMO user only right?
Sent from my HTC One S using XDA

We'll all I did was flash the nandroid and then the radio from CWR. It updated appropriately and I have -zero- issues.
What does the update package on the linked site do for the phone exactly? I see if flashes the following:
adsp.img
boot.img
radio.img
wcnss.img
So I'm assuming it does quite a bit...
(I have CWR recovery installed, not TWRP, and see that this is required for this package... so that furthers my hesitation as well as I don't want to flash a new recovery either, as my previous nand's were done with CWR as well)
I don't really want to do anything as my device is currently working beautifully.
Thoughts? Input? Your outcomes?

Sorry to disappoint but the method did not work for me.
I was able to flash the stock recovery like mentioned and my phone has the original stock firmware.
I was able to keep the OTA downloaded by the phone and used it.
Followed to the letter the instructions, but once it boots in recovery, i see the red exclamation point, then nothing happens, then it reboot and no update was applied.
Phone is not bricked though so that's good.

How to update rooted phone v1.53

I tried to ask the question before but had no luck getting the answer.
I have rooted tmobile one s, version 1.53 (every one else seems to have 1.78).
I need to update my software.
I downloaded ota update but installation failed.
I have removed couple originals mobile software.
No new rom is installed.
I am sure the question was asked before but I do not seem to find it.
I appreciate if someone post a link or have some guidance on this as to what steps are needed.

dell4320 said:
I tried to ask the question before but had no luck getting the answer.
I have rooted tmobile one s, version 1.53 (every one else seems to have 1.78).
I need to update my software.
I downloaded ota update but installation failed.
I have removed couple originals mobile software.
No new rom is installed.
I am sure the question was asked before but I do not seem to find it.
I appreciate if someone post a link or have some guidance on this as to what steps are needed.
Click to expand...
Click to collapse
Version 1.53 means you are on RomBase 1.53 ??

dell4320 said:
I tried to ask the question before but had no luck getting the answer.
I have rooted tmobile one s, version 1.53 (every one else seems to have 1.78).
I need to update my software.
I downloaded ota update but installation failed.
I have removed couple originals mobile software.
No new rom is installed.
I am sure the question was asked before but I do not seem to find it.
I appreciate if someone post a link or have some guidance on this as to what steps are needed.
Click to expand...
Click to collapse
The OTA update would bring you to version 1.84, the other versions are not for TMOUS. It would seem to help if you gave more details as to how the OTA failed like error messages and such, as well as what "couple originals mobile software" it was you removed, was that some swinging app?

Thank you, here is more info to clarify the question:
Android version 4.0.3
Htc sense version 4.0
Software number 1.53.531.1671 ORD
Htc sdc API level 4.11kernel version 3.0.8-01053-g5dc1dc4
Base version 0.16.31501s.02_10.18
Build number 1.53.531.16CL47441 release keys
The software I removed wifi manager , where is my water, twitter and another one do not remember the name.
The error I am getting when I try to install the downloaded OTA is
[I]Certifying current system....assert failed: apply _patch_check("/system/apphtcTwitterWidget_30.
E:Error in / internal_sdcard/download/OTA_ville_U_TMOUS_1.84.531.16_release2651973.....zip
Status 7
Installation aborted[/I]
I was up for two nights trying to figure how to install the update with no luck. Any assistance is appreciated.

Ok. Easy fix. Download the t mobile nandroid and install the zip in cwm recovery and you'll be on 1.84 . It's in dev section. Make sure you get the t mobile one.
Sent from my HTC VLE_U using xda premium

dell4320 said:
Thank you, here is more info to clarify the question:
Android version 4.0.3
Htc sense version 4.0
Software number 1.53.531.1671 ORD
Htc sdc API level 4.11kernel version 3.0.8-01053-g5dc1dc4
Base version 0.16.31501s.02_10.18
Build number 1.53.531.16CL47441 release keys
The software I removed wifi manager , where is my water, twitter and another one do not remember the name.
The error I am getting when I try to install the downloaded OTA is
[I]Certifying current system....assert failed: apply _patch_check("/system/apphtcTwitterWidget_30.
E:Error in / internal_sdcard/download/OTA_ville_U_TMOUS_1.84.531.16_release2651973.....zip
Status 7
Installation aborted[/I]
I was up for two nights trying to figure how to install the update with no luck. Any assistance is appreciated.
Click to expand...
Click to collapse
Have never had any issues myself but read that OTAs and possibly RUU (?) sometimes require all original apps to be present. You could try to find that TwitterWidget .apk somehow like in /system/app that nandroid Mike talked about, copy it to your SDcard and install it then try the OTA again. Or just install the whole Nandroid in CWM, make sure you backup your stuff first if you mess it up

http://forum.xda-developers.com/showthread.php?t=1698861
Sent from my HTC VLE_U using xda premium

Thank you Mike, can I push my luck and get an answer on how to unzip the update file and how to create cwm step by step link. Thank you again all. It is a rough journey.

dell4320 said:
Thank you Mike, can I push my luck and get an answer on how to unzip the update file and how to create cwm step by step link. Thank you again all. It is a rough journey.
Click to expand...
Click to collapse
you dont unzip any update file, you have a few way to fix this:
1: Restore the apps that the OTA update is complaining about. To do this you download the Nandroid file Mike linked to and use winzip, 7zip or whatever to open it in Windows and find the twitterwidget file in it. Then you copy it to your phones SDCard and click it on your phone. You might have to check the setting to allow apps from other sources than the Play Store in phone settings. Hopefully this works, if not you have to bootloader unlock your phone and root it. There are good guides stickied around here.
2: Unlock your bootloader so you can install CWM recovery, then download the Nandroid file to your SDCard, boot into CWM recovery, and restore the Nandroid. A Nandroid is a complete backup of someones phone software and settings. This might wipe all your data.
3: Easiest way might be to run a RUU for T-Mobile USA with version 1.84. This might wipe all your data. A RUU is a program you run in Windows with your phone connected via USB, it'll factory reset your phone with the version of software in the specific RUU file, you can find a TMOUS one in development section, the thread is called Ville/VilleC2 shipped ROMs.
4: Send it in to TMOUS and they'll probably run a RUU for you.

Thank you frdd:
1: I tried to do number one, but the unzipped files still does not have a breakdown for the specific twitterwidget, somehow it will have to be within a system file that has different name. My phone is unlocked and rooted.
2- eventhough my phone is unlocked, i still can not install cwm, i guess it has something to do with previous postings where others have a problem entering the recovery on htc one s
4- I will do as last resort.
3- I am trying to do now, Do I have to relock the bootloader? is there a step by step guide on how to run RUU.
Thank you again.

Has anyone gotten the OTA URL or file for the Stagefright patch?

Hey I was wondering if anyone has managed to get their hands on the download URL for the patch. It'd be a small patch that you would be able to flash in the stock recovery since it's signed by Alcatel. It'd be much easier for people to put this on their sd cards and flash rather than reimaging their phones.

Someone had a link to the bin... maybe @famewolf

FBis251 said:
Hey I was wondering if anyone has managed to get their hands on the download URL for the patch. It'd be a small patch that you would be able to flash in the stock recovery since it's signed by Alcatel. It'd be much easier for people to put this on their sd cards and flash rather than reimaging their phones.
Click to expand...
Click to collapse
What exactly are you trying to do with it? The patch was specific to each different model of idol 3 (6045i, 6045Y, 6045K, 6039Y, 6039K, 6039i) and was generated at the time the system checker polled their server...it looked at what firmware level the user was already at and added all patches they didn't yet have installed..the urls last for a limited time so yes I did intercept it via a transparent squid proxy but I doubt the url will do you much good as it's probably expired by now...if you want the FILE this is not a patch that will sideload to well I don't believe since one of the things it does is check the checksum of recovery and if it doesn't match the system default recovery it overwrites it. If you try to install it on a device that has any of the previous patches applied that were not applied to MY device at the time of download the update will fail as patch will not apply to an already updated file. The update will then error out.
So to sum all of that up, what exactly are you trying to do with the file? Oh and the update is 302mb....not exactly "small".
..and no it's not "easier" as if you are rooted and don't fully unroot you risk putting yourself into boot loops that currently cannot be resolved since it wipes out your recovery at the same time. Factory recovery for 6045i and 6045Y does not have reboot to bootloader as an option so you basically have a paperweight. It's easier to deal with an image that is already updated and then just flash the supersu zip right after.

The neat thing is that since the updates are signed by alcatel they're basically the only type of file that will flash with the stock recovery.
It's a shame that they got generated on the fly but it makes sense since it'll be a single download every time for each phone, but that means that as you said it's not reusable.
I haven't messed with Android phones in a bit but I read that as of lollipop that patching mechanism changed to some sort of binary diff patcher instead unlike in the KitKat and older days that an OTA zip would contain the full file to be replaced.
Thanks for the information

FBis251 said:
The neat thing is that since the updates are signed by alcatel they're basically the only type of file that will flash with the stock recovery.
It's a shame that they got generated on the fly but it makes sense since it'll be a single download every time for each phone, but that means that as you said it's not reusable.
I haven't messed with Android phones in a bit but I read that as of lollipop that patching mechanism changed to some sort of binary diff patcher instead unlike in the KitKat and older days that an OTA zip would contain the full file to be replaced.
Thanks for the information
Click to expand...
Click to collapse
Add me to the list that can send you pm's and I'll drop you a link to look at.

6045i usa latest 5.0.2-01001

hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.

OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.

Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..

lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.

famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?

tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.

famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:

tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.

famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.

tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.

famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao

tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.

famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.