Related
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
awnorwood said:
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
awnorwood said:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Just an added note, as far as I know, you can't switch back to S-ON on this
device, at least, not at the moment.. If they get S-ON to work on these phones,
good, but if not, I'm not overly concerned.
http://forum.xda-developers.com/showthread.php?t=759955
and
http://unrevoked.com/rootwiki/doku.php/public/forever
for details..
Asadullah said:
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
Click to expand...
Click to collapse
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
mercado79 said:
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
Click to expand...
Click to collapse
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Asadullah said:
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Click to expand...
Click to collapse
Good information to know. Thanks Asadullah.
This thread is an attempt to help out the Tiamat Developers by answering the frequently asked questions in one consolidated thread. This thread should also be helpful to those who either cannot use the search feature or are having a hard time figuring out the correct search terms to find what they are looking for. If you have suggestions or added questions/answers feel free to reply and I will update the OP.
NOTE: I am not a developer. All of the information in this thread is from other members who have helped me out or information I found in the XDA forums. I do not take credit for any of the great work that has been done on this ROM and I will point back to the original answer when possible. I am only trying to help lessen the burden on the developers so they can spend more time getting us the best features. Hopefully you find this helpful as well.
I've flashed this ROM and now I get update notifications. Should I accept the update? How do I stop these notifications?
No, you should never accept an OTA upgrade when using any custom ROM/Kernel. This could result in severe problems. Your best bet is to be patient and give the developers time to react. If the update is worthwhile I am sure they will roll it out pretty quickly.
To get rid of the notifications flash Mod pack 3 as noted here.
OK I made the mistake of accepting the OTA update and now my Xoom won't boot. What can I do?
okantomi said:
Can you make it reboot by pressing volume up and power at the same time and holding? If it reboots, wait about 3 seconds once you see the dual core logo and then tap volume down you shoud see android recovery, then tap up to choose it. I hope you did a nandroid backup. If not, you can try and get fastboot by tapping volume down sooner after it reboots.
Click to expand...
Click to collapse
From this thread.
With this ROM certain websites don't load correctly or I can't get to the mobile version of a site.
This ROM by default sets the User Agent String to "desktop". If you want to revert to the stock settings flash either Mod pack 1 or 2 depending which version of Moray you are running. Look here.
I flashed this ROM and now when I click links in email or my file explorer the screen just dims and nothing happens.
This is a bug in Android 3.2 and not specific to this ROM. To solve this, simply ensure auto-rotate is enabled and rotate the device from landscape to portrait and back to landscape. The app chooser window should appear allowing you to choose which app to open the selected file.
I just flashed this ROM and the speed is amazing, so I OC'd it to 1.7GHz cuz I want more and I am now stuck in a boot loop. This worked for others why not me?
The Xoom was only specified to run at 1.0 GHz, anything beyond that is a gift. Due to part-to-part variation not everyone's Xoom will be stable at the same speed. Yes some people are able to run at 1.7 GHz, but many cannot. For your specific Xoom try out the various speeds, but do NOT click "Set on Boot". This way if it crashes it will revert back to stock speed and you will be able to boot. Once you are satisfied with a speed then feel free to enable "Set on Boot". Before you do so I would suggest making a nandroid backup so you can restore just in case.
How do you get out of this boot-loop? The only way I know of is to boot into recovery and restore a nandroid backup if you have one or perform a full wipe if you do not.
I updated to the latest CWM and I cannot find the zip card or I get "get error: E:failed to mount /sdcard (No such file or directory)."
Latest is not always the best, for the Xoom you need to either use ClockworkMod 3.2.0.0 (R4C) or CMW Rogue Recovery v1.1.1
After flashing this ROM the Motorola icon gets distorted during boot up, is that a problem?
Basically it is not a problem. This kernel has a patch provided by NVidia which causes the distortion during boot. It does not cause any problems after it boots.
Is there a way to get the stock WiFi and Battery icons?
Yes
How do I boot into recovery without ADB or my PC attached?
There are a couple methods.
1) The latest Tiamat ROM includes this if you press and hold the power button. Just pick what you want and hit OK.
2) Download and install "Quick Boot" from the market. It gives you the above options as well as others when you run the app.
3) Turn the Xoom on, wait ~2 seconds after your see the Dual Core logo, then press the volume down key. In the upper left corner it should say "Android Recovery", then press the volume up key to select it.
How do I get started? Any good guides?
There are several guides that are pretty good. The best one I have found and personally used is here.
The Xoom Heaven thread found here is also a good place to start for all sorts of information.
If you have another question please feel free to post to this thread. If you are having a problem or have a question it is likely that someone else along the lines will have the same problem or question. I will continue to update this OP with the list of F.A.Q.s.
Additional Q&As
After installing this ROM I am having issues with the market not finding all of my apps or apps are giving errors when trying to install them.
See this post for one possible solution.
One more for good measure...
HuckFinn, I think you have covered most of the hot issues. Great job!
Stickied. Thanks for posting this, and Solarnz for giving me the heads up to do so.
Sorry for the newb question, but what's "root"?
Psychokitty said:
Sorry for the newb question, but what's "root"?
Click to expand...
Click to collapse
oh kitty, you funny!
Psychokitty said:
Sorry for the newb question, but what's "root"?
Click to expand...
Click to collapse
It's what you pull your hair out by when something is not working properly!!
darn you... I earned 1/2 my posts responding to the "why does my screen dim" question... now I'll have nothing to say!
i performed a factory reset from the os-> settings and once again performed a wipe/factory reset from the cwm recovery but still can't get back to the initial setup screen (where you enter your google a/c, etc)
any idea?
Thanks!!
Here is one..
Why does Market show up in USD even though my locale is set to UK, my language is English British along with my keyboard layout?
Ive had boot loops twice. Both times i could get into recovery but could not get backup to restore . kept getting cant read /sdcard. also cant reinstall update .zip becuase the sd card wont mount. I have only gotten back in by letting it sit powered off for a bit.
any ideas?
should i adb a stock image and start again?
should i flash a different recovery?
madamimadam said:
Ive had boot loops twice. Both times i could get into recovery but could not get backup to restore . kept getting cant read /sdcard. also cant reinstall update .zip becuase the sd card wont mount. I have only gotten back in by letting it sit powered off for a bit.
any ideas?
should i adb a stock image and start again?
should i flash a different recovery?
Click to expand...
Click to collapse
What version of recovery is installed now? If you have the version that doesn't recognize your external sdcard you should certainly flash a compatible recovery version through fastboot.
okantomi said:
What version of recovery is installed now? If you have the version that doesn't recognize your external sdcard you should certainly flash a compatible recovery version through fastboot.
Click to expand...
Click to collapse
Is there a way to check version without booting into recovery? Which version would you suggest?
And thank you
madamimadam said:
Is there a way to check version without booting into recovery? Which version would you suggest?
And thank you
Click to expand...
Click to collapse
There are only two recoveries compatible..
you will find them in the Xoom Android Developmet Board in the sticky threads
LPHS said:
There are only two recoveries compatible..
you will find them in the Xoom Android Developmet Board in the sticky threads
Click to expand...
Click to collapse
OR here:http://forum.xda-developers.com/showthread.php?t=1209341
Links to both of these recoveries are also in the first post of this thread.
HuckFinn said:
Links to both of these recoveries are also in the first post of this thread.
Click to expand...
Click to collapse
Guess I should have read the thread before posting here, sorry for being a troll.
I tried this ROM on my 4G Xoom, but it left me without 4G or 3G (wifi only). Any way to get this working, or do I have to wait for an update?
I did try activating the network in settings, but it never connected even half an hour.
Thanks to steps mentioned by user 'LordDeath' in another thread and a bit of experimenting with a rooted 4G Xoom and a friends 3G Xoom running Moray, there seems to be a remedy for those who are having issues with the market compatibility issues as well as missing apps. I did not activate until attempting to sign in to the market and had missing apps and compatibility issues. I simply did a full wipe & reset and made sure the full activation went through in set up then let it automatically start restoring. I took a peek in the market after a a minute and all my apps were back with no compatibility issues. Here is a copy of his original post and mine but the last step was not needed for me.
Originally Posted by LordDeath
Something more about the market:
After I restored my backup of the official 3.1 ROM I still had some issues. On http://market.android.com I still saw that my Xoom is not compatible with some apps. The market app on the device did show these apps but upon installing I got the error message: "Fehler beim Verarbeiten des Kaufs". Translated into English it means "Error while processing the purchase". It was a free app, btw.
To solve this issue I did the following:
1. Wipe data/factory reset
2. Active the device during the wizard on the first boot with my Google account
3. Restore the nandroid backup of the official 3.1 ROM
Therefore it seems that the market servers check your device-compatibility only during the activation process at the first startup.
----------------------------------------------------------------------------
"This fixed everything for my friend running Moray and even corrected the issues on my 4G Xoom..."
I should add that though this fixes the issue, if you change your pixel density you may run into similar issues but can correct it by setting it back to 160 before going into the market.
Guys,
I rooted my Samsung Galaxy Tab 2 10.1 GT-P5113, and forgot to freeze the updater with Titanium Backup. I have since done that, do not want any updates to take my root away. I will ask you guys about updates, like is this a bad one, should I allow it to install or remove the downloaded update from my system? Where is the downloaded update so that I can remove it with ES File Explorer?
Click here for a shot of my About Device page.
I have frozen "Software update 1.0" but not "Software update v3_1205_3_2". How do I make these Install Update messages go away"? They now "remind me" every 3 hours and this sucks.
Also, by looking at my version link screenshot above, what is the new update, is it good, should I take it, and will it make me lose root?
Side note, Clockworkmod fails to make a backup every time and I really want to backup this system just in case. Here is the log if anybody knows about what to do, if not, I will make a new post for this issue. Thanks guys!
This "upgrade reminder every 3 hours" is driving me nuts, someone please answer quickly.
Clockworkmod Backup Fail Log
NOTE: I have a great relationship at droidxroums and the developers have gone FAR out of their way to get me root and help with any questions. 1KDS and Goose306 are top developers and 1KDS even built 6 CD iso files to boot into Linux and root my Droid Razr Maxx. But they do not do tablets. I need a new home for this. You guys are terrific and with your help, I got my tab 2 rooted. Thanks!
Ohmster said:
Guys,
I rooted my Samsung Galaxy Tab 2 10.1 GT-P5113, and forgot to freeze the updater with Titanium Backup. I have since done that, do not want any updates to take my root away. I will ask you guys about updates, like is this a bad one, should I allow it to install or remove the downloaded update from my system? Where is the downloaded update so that I can remove it with ES File Explorer?
Click here for a shot of my About Device page.
I have frozen "Software update 1.0" but not "Software update v3_1205_3_2". How do I make these Install Update messages go away"? They now "remind me" every 3 hours and this sucks.
Also, by looking at my version link screenshot above, what is the new update, is it good, should I take it, and will it make me lose root?
Side note, Clockworkmod fails to make a backup every time and I really want to backup this system just in case. Here is the log if anybody knows about what to do, if not, I will make a new post for this issue. Thanks guys!
This "upgrade reminder every 3 hours" is driving me nuts, someone please answer quickly.
Clockworkmod Backup Fail Log
NOTE: I have a great relationship at droidxroums and the developers have gone FAR out of their way to get me root and help with any questions. 1KDS and Goose306 are top developers and 1KDS even built 6 CD iso files to boot into Linux and root my Droid Razr Maxx. But they do not do tablets. I need a new home for this. You guys are terrific and with your help, I got my tab 2 rooted. Thanks!
Click to expand...
Click to collapse
I think I found my answer on another board, will show it here for others that need the help. Still need help with clockwork mod if anyone has an answer.
Post here with answer
Screenshot of frozen app in Titanium Backup
Thanks if anyone had an answer. I really need a new home for my Samsung Galaxy Tab 2 10.1. If you make me fell welcome here, I have much to share. Goodnight.
~Ohmster:good:
Questions should be asked in Q&A forums, not Development forums.
Thread moved.
Archer said:
Questions should be asked in Q&A forums, not Development forums.
Thread moved.
Click to expand...
Click to collapse
Agreed. Thanks for the heads up.:good:
i recently used rsd to flash back to stock after a failed rooting/unlocking attempt. i believe the flash was successful, and the phone seems to be preforming just fine. the problem comes up when i try to check for the kit kat update. the phone says that it needs me to set up a motorola account. when i press setup it says connecting to servers please wait. i dont believe it will ever actually connect to the server though since ive waited upwards of ten minutes with no results. if there is anything to fix this? any help would be greatly appreciated, and my apologies in advance if this is a stupid question. im currently on 9.30.1.xt926.verizon.en.us
I left my experience getting to kitkat with my post here helping someone. http://forum.xda-developers.com/showpost.php?p=52696764&postcount=5
Since you already have 9.30.1 firmware, you skip to the KIt ota zip download and follow the directions from the post I left if you want to sideload the OTA. Otherwise it should notify you of an update. I got a update notification but already had the OTA on my sd card so went ahead and did that way instead.
pmccarthy7745 said:
i recently used rsd to flash back to stock after a failed rooting/unlocking attempt. i believe the flash was successful, and the phone seems to be preforming just fine. the problem comes up when i try to check for the kit kat update. the phone says that it needs me to set up a motorola account. when i press setup it says connecting to servers please wait. i dont believe it will ever actually connect to the server though since ive waited upwards of ten minutes with no results. if there is anything to fix this? any help would be greatly appreciated, and my apologies in advance if this is a stupid question. im currently on 9.30.1.xt926.verizon.en.us
Click to expand...
Click to collapse
UOTE=yujikaido79;52720878]I left my experience getting to kitkat with my post here helping someone. http://forum.xda-developers.com/showpost.php?p=52696764&postcount=5
Since you already have 9.30.1 firmware, you skip to the KIt ota zip download and follow the directions from the post I left if you want to sideload the OTA. Otherwise it should notify you of an update. I got a update notification but already had the OTA on my sd card so went ahead and did that way instead.[/QUOTE]
Thanks man, I think I'm just gonna wait until the update is sent to my phone, I'm a little gun shy after my last experience flashing anything
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.