Need noobish help with donut - myTouch 3G, Magic General

Hi and thanks for reading and answering.
I've got an HTC Magic vodafone (google branded) and have yet to receive the OTA donut update (I live in Portugal). When I tried the manual install it fails saying that there's no signature blah blah blah. The phone isn't rooted and there's a CRC1 code (don't know what that means)
I've tried to search for answer but every post reffers to cooked roms and I just want to make the official update.
So if someone could please tell me (in the most noobish way possible) how to do it I would be very much gratefull.
Also please don't use letter codes (like OTA for over the air) because most of them are unknown to me.

i dont believe your going to be able to update your phone manually without having root access
root would be like... say how if your on windows you have your "administrator" which can install and change things on your computer but a normal user wouldnt be able too?
thats pretty much what it is... just on linux the admin is "root" and because your not root(the admin) on your phone (your just a user) I dont believe you can do updates even though it is a release from android without having root access other than that you might have to wait for the update

Well as I said before, I'm really noob when it comes to android, so in case of your solution, is there a really big noob guide for rooting and updating (preferably without deleting my stuff)

I updated mine manually and i havent rooted my phone. So you should be able to do it, try downloading the file from another source

Them I happily accept suggestions to where to download the update

If you want a non-rooted phone and for your carrier to supply Donut, there's something wrong with the software on your phone, though it could be as small as a failed download and next Over The Air update will work again. Try erasing all your data with Reset To Factory (it's in the settings menu somewhere) and wait for OTA again.
(Are Vodafone even pushing Donut updates out OTA yet? I didn't think they were.)
If you want to root your phone and install a Donut ROM yourself, read around the FAQs in this forum. Essentially you need to get the Android SDK, fastboot Amon_RA's Recovery, perform a nandroid backup and install a ROM. nk02's Donut is just plain Donut with root, there are other options out there.

please close and delete this thread as I already receive my OTA update. everything is fine except Voice Search (it's not even there )

Related

OTA fail help

Hello all
Have searched this forum, but im not really sure what to do.
I've used titanium backup to perm remove a few stock apps, the exchange stock app and amazon app
Now i can't recive any updates OTA, and i get this message..:
assert failed: apply_patch_check("/system/app/Stock.apk"....
E:Error in /sdcard/download/OTA_Ace_HTC_WWE_172_405_3_r2_1_32_405_6_release_1632939lowfu0y78jktpp2.zip
(status 7)
using 2.2 android version number 1.32.405.6
please help
//Cham
You can't accept OTA updates when you are rooted.
I see, but only used temp root with visionary
is that going to affect something?
Or what are my options to get a hold of updates in the future, a costum rom instead? I do kinda like the stock rom, just without stock apps
anyone?
Once again, if you are rooted, it doesnt matter how, you CANNOT accept ota update.
If you deleted something you shouldnt have, then restore the backup to that, or do a factory reset and re-root.
Ok i just figures since it was TEMProot that it didn't matter. Tnx for the reply, tried the factory default option (no luck), is there any place where I can get the Stock firmware to re-flash the phone?
Or would anyone in here recommend another rom ? Tons of custom roms, as I can tell.
Thread moved in Desire HD General.
go here and youll find your rom that you need,
you need the ones that are "RUU_Ace_HTC_WWE" in the file name, as these are what we call World Wide Editions
Thank you very much.
Just to make sure I do not **** something up, what are the steps i should follow, to install the rom?
This is what I did: http://forum.xda-developers.com/showthread.php?t=888109
Got the same problem -- some time ago I removed some "useless" apps from my /system/app folder, and when 1.72 update was released I wasn't able to install it in any way (I was trying to follow this guide). I restored the missing apps, and then everything went fine using the guide mentioned above!
Hope this helps.
sitlet said:
You can't accept OTA updates when you are rooted.
Click to expand...
Click to collapse
Sorry but that ain't correct... You *can* update your phone if you're rooted, the main problem is that root will be gone after update. The best solution is to *always* reject OTA updates provided by HTC and wait until devs here have found a safe way to update your device without losing root privileges.
Thank you
Thank you all, it gave perfectly sense since I'm quite happy with the stock firmware, i'll stick with this. The root is not so necessary for me at least for now
I'm glad it was corrected that visionary did not remove the ability for OTA, that was also what I've read before used it.

Rooting and OTA updates

I am looking into rooting my Nexus S so I can install an ICS ROM. This is my first time rooting so got a question.
How will OTA updates work for me? Will the ICS update just work or will I have to in root to get the official OTA update?
Sry if this has been asked before couldn't find a clear answer.
Sent from my Nexus S using XDA App
Don't do OTAs. Any update released by Google or your manufacturer will be released here, rooted, within hours.
If you take an OTA you will lose root and could even find your phone locked again (as unlikely as that is with the NS, better safe than sorry. Ask the EVO users who took the GB OTA )
Sent from my Nexus S 4G using Tapatalk
Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.
Alright, thanks alot for the quick responses guys.
Sent from my Nexus S using XDA App
Once the ota is downloaded.....
* Put the zip on sdcard
* Reboot into custom recovery
* Manually flash it
* Directly after that, in the same recovery session, flash latest superuser zip
* Wipe cache
* Reboot
I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
OTA's will work with CWM installed (The OTA will however remove CWM and needs to be manually applied)
OTA's will remove root access (the permissions on the binary get changed)
I have never seen an OTA on XDA that was pre-rooted. i have seen ROM packages that incorporate the OTA that are pre-rooted (installing these usually means a wipe of the device is needed)
if you replace the ROM on the phone, you will not get OTA updated. you must remain mostly stock to obtain them.
Custom kernels or custom google apps on stock roms will cause the OTA update to fail, however you will notified that the update is available.
I hope this answers your questions.
Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.
snandlal said:
Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.
Click to expand...
Click to collapse
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.
I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6
Matridom said:
I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
I hope this answers your questions.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?
onthecouchagain said:
I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6
Click to expand...
Click to collapse
OK, let's clear a few things up here.
CWM or ClockWorkMod is a custom recover that can be installed on the phones. This step is needed because the default recovery on the nexus does not allow for updates to be installed that are unsigned. CWM does, so it's a necessary step to installing the SU binary (aka root your phone) or installing custom ROMs
The bootloader is the basic system on your phone that reacts to the power on and hands over operations to Android. The equivalent in the PC world would be a BIOS.
fastboot is a utility that is provided by google that allows you to send commands to the bootloader and direct it's operations. It's needed to unlock the bootloader (so you can replace parts of it.. like recovery with CWM)
Interestingly enough, you can boot your phone to a custom recovery WITHOUT replacing your existing stock recovery by using fastboot.
Rooting your phone is simply installing and providing the proper rights to the SU binary to allow you to have full administrative rights to the phone, the superuser application is almost always bundled with it as it allows for a form of control as to what applications can use root access. Rooting your phone allows you to install some very interesting application, most popular are titanium backup (let's you back up app data and restore them after a reset) and removing advertising (adfree/adaway or it's like) Root can also be used by some applications that allow you to "cheat" at games.
rooting your phone is reversable, though not always the easiest to do. With the stock ROMS, it's fairly easy, you just re-apply the latest OTA and it will kill Root access on your device.
When it comes to custom ROMs the vast majority come pre-rooted to save you the hassel of doing it yourself.
On other phones where the bootloader remains locked, you have to use an exploit to gain root access, this then allows you to modify the OS and install custom roms and CWM while keeping the bootloader locked. Since the Nexus line can be unlocked, it's not needed.
Please note, root access is NOT required to install a custom ROM.
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
MaxCarnage said:
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?
Click to expand...
Click to collapse
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.
Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?
Matridom said:
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.
Click to expand...
Click to collapse
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The key here is that SPRINT released an OTA for a SPRINT branded device. This has zero relevance to updates provided by Google for Nexus devices.
MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The issue at heart here is that fact that the OTA for the nexus line of phones comes straight from google and are not "tweaked" in any way by the carriers. (exception nexus 4g has additional applications required for CDMA support)
One of the selling features of the nexus phones is the fact that unlocking the bootloader is officially supported.
In regards to other phones getting their bootloader locked, I've experienced first hand the pains of that, having a galaxy S and the 2.3 installing a new bootloader and really screwing things up for me. In those cases, i agree with you whole heartily and to wait for pre-cracked roms that can be installed.
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
onthecouchagain said:
Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?
Click to expand...
Click to collapse
All you would need to do is to unlock the bootloader, install CWM, then apply the .zip associated with the ROM you wish to install. I would however carefully read the installation instructions for the rom as in some cases, it might be a multi-step process (such as going from a 2.2 rom to a 2.3).
Many ROMS also do not come with the google apps and secondary zip file needs to be applied to get those running (cyanogenMod does this)
I wanted to add, that the process of unlocking your bootloader will erase EVERYTHING on the phone, including the SDcard partition. So make sure you back up anything of importance.
Matridom said:
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
Click to expand...
Click to collapse
I can't provide an example because, as I have already stated, this was a precautionary suggestion only.
I'm not going to get into a debate with you over this; I've made my point and you've made yours. Thanks.
Matridom said:
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.
Click to expand...
Click to collapse
Good point again but the trick is to put your apps in /system/framework
Along with framework-res.apk.
This will add a dex file to /data/dalvik-cache, which is needed for saving upon reboot
Does flashing another radio that's different from your original radio impact the ability to apply an OTA?
suksit said:
Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.
Click to expand...
Click to collapse
Rooting doesn't require flashing custom recovery.
iboj007 said:
Does flashing another radio that's different from your original radio impact the ability to apply an OTA?
Click to expand...
Click to collapse
No. It doesnt

[Q] 3.2.1 rooted stock rom?

I currently have stock 3.2 rooted (US 7.006.01_COM_GEN2). I got an ota notification for 7.014.01. Is there a rooted version of the ota I can flash via cwm?
From searching around, it's also looking like another ota ( 7.014.02?) Is right behind the 7.014.01. Is that true, and if so, is that available in rooted cwm-flashable form?
Neither available yet. (I'm waiting too. They were just released, so give them some time)
I wouldn't be so quick to update something, without first knowing what it is
Old saying "if it ain't broke, don't fix it"
A little more info on the update;
http://www.androidcentral.com/syste...ia-brings-market-update-and-improved-ui-speed
Yes, the 01 and 02 will break root. But, never fear, I rooted it for you. Here's the link
http://forum.xda-developers.com/showthread.php?t=1307539&page=12
Very cool
Although I don't need it, it's nice to know some people are still doing some neat things for stock 3.2.
update without wiping?
Thanks for the info. But, unless I'm reading your instructions wrong, it sounds like I have to wipe to update to your rooted 3.2.1. Is there just a rooted update.zip that can be flashed with cwm without wiping?
Or am I missing something?
There are some roms currently in the works for 3.2.1. I'd expect them to come out fairly soon, keep an eye on the development forum. A few guys working on them right now.
mpkrcl said:
Thanks for the info. But, unless I'm reading your instructions wrong, it sounds like I have to wipe to update to your rooted 3.2.1. Is there just a rooted update.zip that can be flashed with cwm without wiping?
Or am I missing something?
Click to expand...
Click to collapse
Ok, if I hear you correctly, you are already rooted and want to use CWM to run the updates and keep root? Therefore you don't wipe out everything?
Piece of cake, just grab the update.zip and change it not to wipe your permissions. Then rebuilt it.
If you don't know how to do that, then put a backdoor into your device therefore you can get back into the device as root. Updates (normally) are not evil un-rooting tools. They don't seek and destroy root and rooting tools. Updates just reset the permissions on all files in /system removing the 'sticky' bit. The 'sticky' bit is how you get root.
What is a 'sticky' bit you ask? Well, in Linux (Unix) you can set a permission on a file so that any time it is run, it runs as the user that owns the file. This would be like setting a shortcut in Windows to say always run as 'Administrator'.
So, when you apply an update, the last thing it does is resets all the permissions back to their default. Since they recursively do this on the /system directory they remove the sticky bit on your su program.
So, all you have to do is set up a root backdoor outside the /system folder. My favorite is to set the ro.kernel.qemu = 1. This makes adb run as root. Now after your OTA resets permissions, you can just adb shell and you get #(root). Now you just reset your 'sticky' bits.
TD

[Q] Second-hand N4, some questions?

Hey!
I recently bought a second hand Nexus in decent shape.
Im really a newbie when it comes to roms, rooting, bootloader etc and Im not really interested in it either!
So what I did when I got the handset was to google around for how to restore it to factory edition. (The other guy seamed to have used other Roms and such)
I found a tool by Wugfresh called Nexus root toolkit and used it to lock bootloader, restore factory image (I downloaded myself from google) and unroot the phone.
Now I have some questions! Is the tool safe? Since Im a complete noob I have no way of telling if the rom etc is legit, could there be spyware or such on my phone now?
Since Kitkat is comming OTA soon, would that be a good way to check if the phone is "original"? I mean, if i get OTA 4.4 from google, will that make sure my handset is completly as it was out of the box, and nothing hidden can be there?
This is a screenshot from my "About phone" maybe you can verify that this is correct?
https://www.dropbox.com/s/17b4i9wi1wypsgl/Screenshot_2013-11-14-13-04-53.png
Very thankful for your help!
I found a tool by Wugfresh called Nexus root toolkit
Now I have some questions! Is the tool safe?!
Click to expand...
Click to collapse
Why don't you ask him personally?
Toolkit being safe or not depends on who you ask. It could cause problems and sometimes it's better to learn to flash the device manually. For some its better to use toolkit since they can potentially cause more problems doing something wrong manually. If you want to flash the factory firmware manually, the instructions are in these steps: http://forum.xda-developers.com/showthread.php?t=2010312
Since Im a complete noob I have no way of telling if the rom etc is legit, could there be spyware or such on my phone now?
Click to expand...
Click to collapse
If you install the factory image from here https://developers.google.com/android/nexus/images, then its the official Google firmware. However, these OTA packages are original as well: http://forum.xda-developers.com/showthread.php?t=2145848. To tell if other third party custom roms are safe, I don't program myself, but reliable ones are open source and have the sources available to the public that you can use to compile yourself. You can use hash checking to make sure if a file is original, Google gives you the hash values for their downloads.
This is a screenshot from my "About phone" maybe you can verify that this is correct?
https://www.dropbox.com/s/17b4i9wi1wypsgl/Screenshot_2013-11-14-13-04-53.png
Click to expand...
Click to collapse
The screenshot shows you are running stock Android 4.3 with stock kernel. However a device need to run an "odexed version of the stock rom" and stock recovery too to receive updates. If the toolkit installed the factory firmware for you, then you have everythig stock and is good to go to receive the updates.
Since Kitkat is comming OTA soon, would that be a good way to check if the phone is "original"? I mean, if i get OTA 4.4 from google, will that make sure my handset is completly as it was out of the box, and nothing hidden can be there?
Click to expand...
Click to collapse
No, a better way would be to flash the factory firmware of 4.4 when it become available, which would wipe everything in the process. It's always possible for phones to have spywares if you know how to exploit it, no software are impenetrable. For example, the seller could have installed a virus that stay in your system that lives through factory resets and use it to tell your exact location, phone information, record audio or take pictures of you. I use this myself, see: Cerberus (Nothing as drastic compared to what Google or Apple does however.) However, if you have flashed the factory image then it would wipe out programs like Cerberus.
But before being too worried about malwares, I suggest reading this article on Android malware: http://www.androidpolice.com/2013/1...at-001-of-apps-evade-defenses-and-harm-users/. To stay safe, just make sure to download apps from the PlayStore. Android have the ability to sideload app, don't utilize it if you are concerned. Even if you do sideload, if the phone have Google services installed, the "Verify apps" feature will ask to scan it before installing.
For many technical reasons and depending on usages and scenarios I believe its much safer to root than being unroot, but this will lead to other discussions. (Root may be required to catch and prevent exploits or close security holes that affect unrooted devices. It's down to how you use it. Aside from the UAC checking, most people who use Windows computer runs it fully rooted without knowing.)
eksasol said:
Why don't you ask him personally?
Toolkit being safe or not depends on who you ask. It could cause problems and sometimes it's better to learn to flash the device manually. For some its better to use toolkit since they can potentially cause more problems doing something wrong manually. If you want to flash the factory firmware manually, the instructions are in these steps: http://forum.xda-developers.com/showthread.php?t=2010312
If you install the factory image from here https://developers.google.com/android/nexus/images, then its the official Google firmware. However, these OTA packages are original as well: http://forum.xda-developers.com/showthread.php?t=2145848. To tell if other third party custom roms are safe, I don't program myself, but reliable ones are open source and have the sources available to the public that you can use to compile yourself. You can use hash checking to make sure if a file is original, Google gives you the hash values for their downloads.
The screenshot shows you are running stock Android 4.3 with stock kernel. However a device need to run an "odexed version of the stock rom" and stock recovery too to receive updates. If the toolkit installed the factory firmware for you, then you have everythig stock and is good to go to receive the updates.
No, a better way would be to flash the factory firmware of 4.4 when it become available, which would wipe everything in the process. It's always possible for phones to have spywares if you know how to exploit it, no software are impenetrable. For example, the seller could have installed a virus that stay in your system that lives through factory resets and use it to tell your exact location, phone information, record audio or take pictures of you. I use this myself, see: Cerberus (Nothing as drastic compared to what Google or Apple does however.) However, if you have flashed the factory image then it would wipe out programs like Cerberus.
But before being too worried about malwares, I suggest reading this article on Android malware: http://www.androidpolice.com/2013/1...at-001-of-apps-evade-defenses-and-harm-users/. To stay safe, just make sure to download apps from the PlayStore. Android have the ability to sideload app, don't utilize it if you are concerned. Even if you do sideload, if the phone have Google services installed, the "Verify apps" feature will ask to scan it before installing.
For many technical reasons and depending on usages and scenarios I believe its much safer to root than being unroot, but this will lead to other discussions. (Root may be required to catch and prevent exploits or close security holes that affect unrooted devices. It's down to how you use it. Aside from the UAC checking, most people who use Windows computer runs it fulled rooted without knowing.)
Click to expand...
Click to collapse
Very much thanks for your post! Appriciated that you are taking time to reply.
When it comes to why I don't "ask him personally", well, if I myself developed a malicious software I would obviously not tell people it is?
When I write safe, by safe I mean free from harmful or hidden software, not safe as in bricking. I've already used the toolkit and flashed the factoryimage I downloaded myself from google, my concern was if the toolkit in some way could add harmful code when the firmware was flashed.
An "odexed version of the stock rom" is not enough to be sure the phone is fine if I interpret you correctly? Since you are saying that recieving OTA 4.4 is no guarantee that the rom, bootloader, recovery, etc is completly googlish? Guess I will consider to flash 4.4 manually then when it's out, ill be reading the thread. Thanks alot!
How do I tell if Im running stock recovery?
I've never installed anything from outside google play, and pretty much every app are from trusted sources with millions of downloads. Atleast if facebook and instagram are to be trusted
You need to understand this is XDA Developers, a community that share open source ideas, not a warez site, you've been a member for a while to know this. The community and moderators do their best to check uploads for harm, in the end of the day still your choice to use the toolkit or install something, and to do research on it (reading through the thread).
Since you are able to use the toolkit to install factory firmware, KitKat firmware image is already available, so I suggest you flash it instead of waiting for the OTA. Generally a clean install have less issues than OTA updates.

HTC U Ultra Update on phone already rooted...

If someone has already asked this and I missed it, please point me in the right direction.
I have the HTC U Ultra, unlocked, Rooted with TWRP and SuperSU already installed. I am being prompted to install Software Update 1.15.617.12.
Should I allow it to update, and if so will I loose root access and have to re-root the device, or is there a better way?
(sorry about repost, still learning where to properly post in the forums)
it won't allow you to update. Will download the update and give you an error after that. You can only update a non modified system
How do I stop the phone from prompting me every ten minutes to install it then?

Categories

Resources