HTC One boom sound after root - One (M7) Q&A, Help & Troubleshooting

Hello all...
I have a rogers htc one.. I unlocked the boot loaded n then rooted it.. However after the root I've notice that the volume on the speakers and if I were to plug in earphones (tried different ones) is not what it used to be before rooting.
If volume is set half way it is not as loud as it used to be..
I've tried the stock music play... Then I installed other players and still the same issue..
Maybe I've gotten used to the boom sound that I find it normal that it doesn't seem xtra ordinary anymore?
Has anyone had this issue?
Also doing the root.. I've notice that I don't have access to the calculator app in the app drawer.. Even though the I have access to the calculator widget...
Any help would be great and I thank you all in advance...
Regards

mobscene123 said:
Hello all...
I have a rogers htc one.. I unlocked the boot loaded n then rooted it.. However after the root I've notice that the volume on the speakers and if I were to plug in earphones (tried different ones) is not what it used to be before rooting.
If volume is set half way it is not as loud as it used to be..
I've tried the stock music play... Then I installed other players and still the same issue..
Maybe I've gotten used to the boom sound that I find it normal that it doesn't seem xtra ordinary anymore?
Has anyone had this issue?
Also doing the root.. I've notice that I don't have access to the calculator app in the app drawer.. Even though the I have access to the calculator widget...
Any help would be great and I thank you all in advance...
Regards
Click to expand...
Click to collapse
You probably updated the phone in the meantime to the latest OTA, because HTC decided to lower speakers volume in last update, to prevent them from being damaged, but they said also that tuning the right volume is still a work in progress and it will change in upcoming updates

Tabtoub said:
You probably updated the phone in the meantime to the latest OTA, because HTC decided to lower speakers volume in last update, to prevent them from being damaged, but they said also that tuning the right volume is still a work in progress and it will change in upcoming updates
Click to expand...
Click to collapse
Thanks for the reply but my question is sorta related to ur reply..
OTA update shows there's an update for my phone so I'm guessing I didn't install the update u speak of..
My next question was... How to manually install set since I'm rooted
Thanks

mobscene123 said:
Thanks for the reply but my question is sorta related to ur reply..
OTA update shows there's an update for my phone so I'm guessing I didn't install the update u speak of..
My next question was... How to manually install set since I'm rooted
Thanks
Click to expand...
Click to collapse
Install it normally if you are still on stock, even if you are rooted I think you can still install official otas (someone correct me if I'm wrong please), but I'm not sure so search before doing anything, and for the updates, I believe there was many updates since the version shipped with the device, so maybe you've already done one of those updates and now it's simply showing a new one?
what's your current software version?

Tabtoub said:
Install it normally if you are still on stock, even if you are rooted I think you can still install official otas (someone correct me if I'm wrong please), but I'm not sure so search before doing anything, and for the updates, I believe there was many updates since the version shipped with the device, so maybe you've already done one of those updates and now it's simply showing a new one?
what's your current software version?
Click to expand...
Click to collapse
the update doesnt work....if i select to update OTA..it reboots into CWM recovery and it says "aborted" and i have to select the reboot now option from the recovery...
currently i have the following sft installed
android 4.1.2
soft version 1.29.631.4
htc sdk api level 5.1.2
its asking me to update to 1.29.631.17 and it says this update is for system enhancement...im in canada btw.
i know for a fact that with custom recovery OTA doesnt work...
EDIT: ok i was right...with custom recovery OTA doesnt work...another fellow canadian is have the same issue.. http://forum.xda-developers.com/showthread.php?t=2293528
but if anyone can help with the boom sound

If you want to install an OTA you have to relock your bootloader. If it's just volume patch you are after you can easily flash a zip to fix it again. If you want the zip just let me know
Sent from my HTC One using xda app-developers app

Related

Software update from ATT

So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Bigluc said:
So I just got a notification from ATT saying that there is a software update available. Has anyone else gotten this and installed it? Is it jelly bean or a minor update? I haven't tried it myself because I am rooted.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes just got it I'm Rooted & S-OFF
it won't be jelly bean since the ONE X series doesn't have it yet haha just a minor I bet
Can someone detail this update?
*Edit* Called AT&T the Update was released October 9th it an 13mb update so yea Minor the girl
on the phone was talking to fast for me to listen what it offers
Got it last night. Android version did not change. Couldn't tell for sure if any other numbers updated. It wouldn't kill AT&T to send out an e-mail or text message telling us what the update was for.
got the same thing i have no idea what is the update
Update has my phone stuck in a darn boot loop..any idea what it is?
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
I was hoping for a new Radio/RIL. That's not what this is...
New Kernel & Recovery. If you are rooted and on a custom rom Do Not run the update. I'm sure the developer of the rom you are on will work to add anything useful to future updates.
The dates on these files is 7/27/12 so it took At$t over to months to test & release.
To delete it look in /cache/fota/OTAPkg.zip
Once gone you shouldn't be bothered by it anymore.
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
gattech said:
Have anyone successfuly downloaded and installed it?
What's new? Bluetooth bugs fixes? Usable Voice Dialer? Better battery life?
Sense 4.0?
Please comment.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
I forgot I was unlocked and rooted. Now I am really stuck. How do I get out of the dead Android loop?
I googled the update, and found this on the ATT Support website.
Beginning on October 9, 2012, AT&T and HTC have released an additional software update for the HTC Vivid that will be available via firmware over-the-air (FOTA). This 13MB software package updates the firmware version to 3.26.502.56_R23 and improves sensor performance.
NOTE: Customers must have a data SOC in order to obtain any FOTA updates. Customers who have a data opt-out SOC are not able to receive FOTA updates.
strose09 said:
Think the majority of users on here are rooted and running custom roms so they wouldnt' be installing this.
Click to expand...
Click to collapse
Hmmm....
Sent from my HTC PH39100 using Tapatalk 2
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
kos26 said:
For the users in boot loop I just recovered from it. Boot into cwm and clear the cache a couple of times and reboot.
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
This Fix works. My phone no longer boot loops
3f62011 said:
Sorry bludiamond.
Since my phone is rooted, I did not want to install this update. It's quite upsetting that AT&T forces the update unconditionally.
Anyway, I had let the download to complete, but did not let it to install. The update did prompt me, whether I want it to install now, or later. I had opted for later.
Then, after some Googling, I had deleted the download (from /sdcard/Download), and had un-installed the following services: com.htc.demoflopackageinstaller and com.smithmicro.dm.
Then, I've rebooted the phone. Afterwards, the phone still had a notification, that there's an update ready to be installed. When, selecting the notification, updater did realize that the downloaded file is gone, and had prompted me whether or not I'd like to download the update again, on which, I had responded no. The notification is gone, and AT&T did not prompt me to download and install the update again, at least not yet.
My phone seems to be OK.
Click to expand...
Click to collapse
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Apatche69 said:
This Fix works. My phone no longer boot loops
After getting my phone out of the boot loop I tried this and am no longer prompted to update. Thank you for the help
Click to expand...
Click to collapse
I had the looping issue too. I cleared the cache once and rebooted. Received a message that there was a problem with the update and to wait for the next update. Phone seems to be okay since.
I'm unlocked s/on..no custom rom..it was so early, I must have hit the wrong button, so I'm stuck in the loop and can't seem to get into recovery either..ugh
I'm stock - not rooted. I did do the download without any problems, although you do have to manually reboot after the update.
It supposedly improves the sensor. Not sure what that means, but that's what the ATT website says. Other than it changing my default ringtone, I don't see any difference.
Could not get it out of the loop. Took it to the service center and neither could they..they ended up replacing it under warranty..thank goodness. Said that another lady came in with the same issue as well.
AT&T Upgrade to Nowhere
I'm running stock on the HTC Vivid and got this upgrade pushed out by AT&T. This is the second AT&T upgrade I've done on this phone (the first was to ICS not long after I got the phone).
I ran the update yesterday, which force rebooted my phone and I watched as the upgrade downloaded and installed, then came back up.
NOTHING has changed. I don't know what AT&T supposedly upgraded, but it's certainly nothing noticeable.
I didn't even get the "3.26.502.56_R23" software designation that the AT&T help article says I was supposed to see.
It was literally an upgrade to nowhere. Not sure why I wasted time off the grid and battery power on it.
As usual-- AT&T fail.
At least no harm was done.
I was rooted, stock ROM, and got the notification yesterday. I postponed as much as I could but it finally wouldn't let me anymore and I let it try to update.
Of course, went into a boot loop. I did eventually get the boot looping to stop by reflashing the wxc recovery image and CWM-root, but then my wifi wouldn't work. I suspected some difference in the kernel version or some other borking of the update.
Long story short, I had to re-lock, go back to stock, and re-unlock and root again. Then spend the time (ongoing) to get my environment back. Thank goodness for Titanium backup pro and Dropbox. LOL.
Wish I could bill AT&T for the 18 hours I've spent. And if they push it to me again, I'll be irritated.

[Q] How to perform OTA 4.2 update to a rooted Nexus 7?

I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
hinsdale1 said:
I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Click to expand...
Click to collapse
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
volarchico said:
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
Click to expand...
Click to collapse
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
2) I would like to know more about how you avoided this issue described in this thread here with stickmount not functioning with v4.2 because of the new mulituser framework that causes it no longer to see files in the mounted folders.
Thanks for your help and to anyone else that chimes in... any help is appreciated. Again sorry for being stupid.
hinsdale1 said:
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
Click to expand...
Click to collapse
i tried with OTArootkeeper app. but it don't update.... at restart for installing, it gave a black screen with android in the middle, with a RED icon inside it...... then it restart and 4.1.2 is always there
Perhaps these questions are so rudimentary that they hardly seem worth bothering with - but for some of us, these hacks and the info being thrown around in here are pretty confusing at times. I would be very grateful to anyone with some insight willing to help out?.
i found that this could be a problem with recovery mode... infact if i tr y to restart in recovery, it gave the same error...
i rooted with toolbox, and i'm thinking that it could have removed my recovery... now i'd like to try to recover the stock recovery with the same tool... but i'm not sure about that.
We seem to have veered off topic a bit here (at least for me)... so let me re-post the questions and beg again for mercy from any kind soles who can offer some advice?
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet?
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Bueller...... Bueller...... Bueller?
Hi! Last month I did the 4.1.2 OTA update. I was rooted but on stock. It updated with no problems. I used Voodoo OTA rootkeeper, restored the root, and either renistalled super su, or just updated the binary. Can't remember.....But I did lose my custom recovery. Didn't realize it till tonite when I went to do the 4.2 update.
So to your question. I forced the OTA 4.2 update. And it downloaded. I made sure voodoo rootkeeper was set to save the root. Then let it install. It rebooted. I opened voodoo, restored root, was asked to update super su binary, accepted. Still not rooted till I rebooted.
So far I have root, and am on 4.2 JB. So my goal was to get my custom recovery back on. Install goo manager from market. Open it, go to the settings button top right, it will give you the choice to install open recovery script. TWRP- Then it will ask you twice are you sure you want to do this and reboot? Say yes. Mine did not reboot and it looked like it did nothing. So, I flipped into recovery and Teamwinn recovery was installed. I made a backup, and rebooted.
Good luck!
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
hinsdale1 said:
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
Click to expand...
Click to collapse
Hi hinsdale,
Have you tried updating to 4.2 yet? Also i heard that if you update SuperSU to version 0.98 the latest version it could cause issues and you will have to reflash the device.
Thanks,
JBIRD
Thanks,
JBIRD
4.2 OTA already loaded, lost root
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Hi hinsdale! I am not a techie- I just learn as I go and read, read, read.
So, my voodoo app has 4 checks in the boxes. I seem to remember only 3 boxes checked when I did the update, but I'm not sure. It would make sense that all are checked.
After I updated, I opened the voodoo app first, and there is a box that says restore root. Then it asked if I wanted to update the su binary. Did that, still not rooted according to Tit. BU. Rebooted, then I was rooted. Good luck with your update.
I'm sorry I can't tell you how to run the initial save root on voodoo. I did it a while ago and don't remember, but it was not hard. Very easy.. Just make sure you Read, re- read, and read again before you do any modifications to your tablet. Know the possible bad outcomes, and be prepared to trouble shoot. This site is very good about helping you out if things go wrong. That's why it's a very good idea to be aware of the possible bad outcomes. The only way to know is to READ-READ=READ!
Did I mention READ??? lol. That's how I figure stuff out. If you read about others mistakes, you can avoid them. I also wait a day or 2 to see how it goes for others before I attempt modifications. That includes new roms. You never know what goes wrong until someone is the guinea pig! I am not techie enough to be the guinea pig!
paulie7880 said:
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Click to expand...
Click to collapse
same thing here...I tried to use TWRM to flash SU but it seems that after going into recovery using TWRM I can't see any any file or folder on my SD except 3 folders???? Can someone please help us....
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
sashusmom said:
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
Click to expand...
Click to collapse
Nexus Root Toolkit
The OTA update downloaded to my cache folder, I moved it to my sdcard. Wouldn't install since I had to fix a couple of files I had edited. So once those 2 files were fixed it installed just fine. Haven't had any issues yet.
The same on here...
But I guess it is better until they fix all this bugs they are reporting.
I'll wait until then.
Sent from my Nexus 7 using xda app-developers app
Updated to 4.2
Hi have updated the nexus to 4,2 and used Voodoo OTA Rootkeeper to keep my root followed the instructions as I did when updated to 4.1.2,my Nexus appears to be rooted superSu is working also stickmount sees the usb but it will not show any files on the sd card any help here please to get it to see the files on the sd card, thanks for your time
Nick
i dont post often as i am usually here looking for help. this time i get to help
i just downloaded and installed 4.2 OTA.
if your nexus was previously unlocked and rooted, it will download and install just fine. however you will lose root, but KEEP the unlocked state.
to root it again, you must goto "about tablet" and tap your build number 7 times to become a developer, this is not a troll, i got this info from another thread on xda.
then using the nexus root toolkit 1.5.4 with modeltype set to "android *.*.* any build", just do the root procedure.
reboot and ur in business, no need to update supersu, and busybox will still be installed already.

[Q] Im rooted.. need some pointers please

Hi all.. Firstly, so sorry about the generic title.. but as you will see, i have quite a few questions and I wasn't sure what to put.. or even if this needs to be in a different section.. sorry mods..
Anyway, here we go.. (advanced warning.. im not a complete idiot.. but not far off. so go gently)
HTC one sim free from phones4u in the UK.
im on android 4.1.2
software 1.28.401.7
htc sdk api level 5.12
The story so far:
Ive rooted my HTC one as I need to have rSAP working on it for my car (Audi). Also, I found the stock bluetooth stack didn't seem to work with my car either so i installed bluetooth phonebook app v 1.1.4.. this all seems to work well. I used rSAP v2.3.2
Now, I carried out all the above myself with lots of reading and to be perfectly honest, lots of trial and error installing it all. I didn't find it easy and for the life of me, I can't remember the steps.
The issue i have:
1. I keep getting a notification for an OTA update for my phone. I have tried to run it once.. but it did not install. I'm assuming because my phone is rooted. I force stop it, but it comes back every time i reboot.
2. I've noticed any app that requires root access is failing. (not all the time, some of the time) and if I go into SU it tells me the binary files need to be updated. I have two options. Run "normal" or "TWRP/CWM" neither of them work.
If i pick normal. It says installing, then reboots and is basically the same. The other option boots me into the recovery but I can't see any update to be applied.
UPDATE: I have now resolved this. I simply downloaded the latest zip file for SU.. booted into recovery and ran the zip update from there and it worked..
Now, you super clever lot probably think this is fun to mess around with.. but us, dare i say it, older peeps just really want to be able to press a button and it works.. (i know iphone.. but give me some credibility).
What I'd like to achieve:
1. I've ordered an OTG cable and drive today (be here tomorrow) with a view of taking an off device back up of my current data / app setiings etc. I assume this is easy to do?
2. I'd like to unroot and update the phone to the latest updates via the OTA service
3. I'd really like to get the rSAP/Bluetooth working with very little fuss
4. Put all my email accounts data etc back to where it was.
How to do achieve my request:
Over to you guys... just please for my own sanity.. and anyone else that reads this in the future.. make it easy.. just remember.. I'm not R2D2...:laugh:
Thanks so much.......... i will personally thank each and every useful reply..
If you're rooted, I'm guessing you're using a custom recovery? The OTA won't install if you have a custom recovery installed.
1. Yes, no issues there, but unrooted devices can only r/rw on FAT32 devices, and if your drive is NTFS, you need an app that requires root.
2. No need to unroot for OTA
3. Not too sure about this one
4. OTA won't wipe anything unless it specifically says so.
ArmedandDangerous said:
If you're rooted, I'm guessing you're using a custom recovery? The OTA won't install if you have a custom recovery installed.
Click to expand...
Click to collapse
Yes correct, I have the TWRP, I believe.
1. Yes, no issues there, but unrooted devices can only r/rw on FAT32 devices, and if your drive is NTFS, you need an app that requires root.
Click to expand...
Click to collapse
OK.. so I should be good to go with NTFS format drive. Is this as simple as I think, i.e. plug in the OTG cable and drive and go into the recovery and backup from there?
2. No need to unroot for OTA
Click to expand...
Click to collapse
I'm a bit confused with this reply, as I don't seem to be able to complete the OTA update becasue I have custom recovery.. Do I need to remove custom recovery then apply the OTA update? If you could just expand on this please? i.e if i need to remove custom recovery, how do i do it?
Thanks
uktivo said:
Yes correct, I have the TWRP, I believe.
OK.. so I should be good to go with NTFS format drive. Is this as simple as I think, i.e. plug in the OTG cable and drive and go into the recovery and backup from there?
I'm a bit confused with this reply, as I don't seem to be able to complete the OTA update becasue I have custom recovery.. Do I need to remove custom recovery then apply the OTA update? If you could just expand on this please? i.e if i need to remove custom recovery, how do i do it?
Thanks
Click to expand...
Click to collapse
Hey,
Because you are rooted, you will not be able to install otas. They may notify you they exist, but you can't install them.
How do you get rid of them?
Well you're on a stock Rom. That Rom will receive otas from your service provider. You can install a custom Rom. It's fun! it gets rid of the notification but that's only like 2% of any advantage you can have from a custom Rom. Plus that ota that's trying to come to your phone is most likely already on a custom Rom, as the devs get leaks and port them way before regular users receive them. You could give it s try?
No idea about the first post.. loving the Audi part though haha!
Sent from my HTC One
ArmedandDangerous said:
How do you get rid of them?
Click to expand...
Click to collapse
Pull down the banner from the top of the phone. Click and hold the notification for the update, click app, then pick to force close it. It then goes away until you next re-boot.
uktivo said:
Pull down the banner from the top of the phone. Click and hold the notification for the update, click app, then pick to force close it. It then goes away until you next re-boot.
Click to expand...
Click to collapse
Think you're quoting the wrong person
As I said in my earlier post, you can still receive OTAs and apply them even if you are rooted. The part that makes it fail is the custom recovery. You should be able to find the correct stock recovery from one of the threads here on XDA, or if you have ever received an OTA before on your device, the OTA zip file should still be in your internal SD.
Flash the stock recovery over TWRP (make sure to do a nandroid/backup first) and apply the OTA. You will probably lose root, but just root it again the usual way.
Then you can flash a custom recovery, root, etc etc all over again.
About the USB OTG, I believe TWRP always saves the nandroid backups internally, but you can always transfer them off to a USB device through USB OTG if you want. I don't think it natively supports reading from USB OTG while in recovery.
Why have it so complicating?
Hi,
what I don't understand is why your Audi is not recognising your phone properly? I stream music at home via BT to an APT-X receiver plugged into my stereo, and using quite often rental cars of all makes, I simply connect it, punch the PIN into my fone and the One phonebook is available.
Now, as you are already rooted, and of course unlocked, just download and flash a Custom ROM. They are rooted, and some are based on 4.2.2 and work very well.
No need to fuss about with what you are about to do!
Don't forget to backup imortant stuff you want to keep on your SD card, simply copy it over to your computer for future reference. JB 4.2.2 is organising the SD card structure differently, so you copy stuff back to SDcard/0/
Custom ROMs are featuring the latest updates anyway very quickly, so there really is no need whatsoever to wait for an OTA (which you should never ever attempt to flash when rooted/S-off-ed)
Looking forward to see what you are telling me about the Audi BT connection trouble. I never had any!
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..If course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
uktivo said:
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..of course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk 4 Beta
uktivo said:
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..If course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah, to much Iphones stuff around! hehehe
Try maybe with the Custom ROM in my signature. It worked very well with the Ford Kuga I had last week, music as well as contacts.
Just read up a bit on the different SD card managment google implemented with the multi user stuff.
And I have to say: Audi A7 ???? Nice motor!
Yes , it's a lovely car.. Thanks.. Also; thanks for the info. I will investigate roms..
Sent from my HTC One using Tapatalk 4 Beta
Hi all, Sorry I've been away working for the last few weeks so I've not had chance to do any of the above.
I was hoping I could get some easy to follow (trust me, it has to be easy at my age) instructions on the best way to achieve what I want to do. If the step by step instructions could include links ot the downloads i need, that would be fantastic.
Re-cap on what I want to acheive:
My phone right now:
The phone was purchased from Phoes4u (UK) as a sim free unit. I currently have an O2 sim inserted
Android 4.1.2, HTC sense 5, Software 1.28.401.7
HTC SDK API level 5.12
Kernel 3.4.10-gddcfb8croot
When i boot into recovery it tells me:
M7-UL PVT SHIP S_ON RH
HBOOT-1.44.0000
I have added rSAP v2.3.3 to the phone in order for my car to have access. http://www.android-rsap.com/compatibility.html
I have one exchange email, some movies, and basically thats it.
----------------------------------------------------------------------------------------------------------------------------------
I would like to update to the latest Jelly Bean and ensure I keep rSAP for my car. If there is a way to back up all my data and movies and simply press a button to re-install it, data, settings for email etc that would be fantastic.
Please help if you can.....
thanks.

[Q] help - no su binary installed?

i have previously unlocked bootloader and rooted my device using the Hasoons all in one tool kit and then had been using ard 12.1.
I then fancied trying the latest GE 4.3 release (stock) which i downloaded and flashed and all seemed fine however when i went to check root was still there i have the icon but get a message saying that there is no su binary installed. I have tried to use the toolkit again to go back the root procedure in the hope i can re-install what ever is missing however for some reason now the tool kit comes up with an error message in the box saying waiting for device or device not recognized.
I have tried to sort the problem but now feel i am just going round and around in circles and really dont have the knowledge to put it right as im quite new to the flashing and modding side and dont fully understand all the terminology, im sure its probably something really simple to fix for those who know how so would really appreciate some advice.
My overall aim would be to be running the stock rom (or might even try the new arhd 4.3 ge) with root so that i can then use the volume + to wake mod as i find this really usefull as my power button is quite depressed and hard to use.
hpsauce37 said:
i have previously unlocked bootloader and rooted my device using the Hasoons all in one tool kit and then had been using ard 12.1.
I then fancied trying the latest GE 4.3 release (stock) which i downloaded and flashed and all seemed fine however when i went to check root was still there i have the icon but get a message saying that there is no su binary installed. I have tried to use the toolkit again to go back the root procedure in the hope i can re-install what ever is missing however for some reason now the tool kit comes up with an error message in the box saying waiting for device or device not recognized.
I have tried to sort the problem but now feel i am just going round and around in circles and really dont have the knowledge to put it right as im quite new to the flashing and modding side and dont fully understand all the terminology, im sure its probably something really simple to fix for those who know how so would really appreciate some advice.
My overall aim would be to be running the stock rom (or might even try the new arhd 4.3 ge) with root so that i can then use the volume + to wake mod as i find this really usefull as my power button is quite depressed and hard to use.
Click to expand...
Click to collapse
hello you are in need of the new 4.3 superuser.zip
http://download.clockworkmod.com/test/superuser-4.3-beta3.zip
if you are using CWM, when it asks to fix su upon reboot, select NO
Wow thank you!!!!!
You have no clue, or maybe you do, how lost I got trying to root my HTC One. This is all new to me, but this forum has helped massively. I found that the supersu zip I had was the older version when I already had 4.3 uploaded before rooting. This community rocks!
why do my gapps processes keep crashing?
NM forgot to full wipe
So I have the same issue - my only question is that I am running 4.4 now. Does this super user file still work or is there a 4.4 version?
Just use "SuperSu" if you face any root acces issues
Sent from my loved HTC One S using (most time buggy) Tapatalk
HHEELLPPP
Hi there, Im new to the rooting world, I have a htc one m7 from sprint trying to sim unlock it, as far as I know I unlocked the bootloader, tampered it, and rooted, but no access to super user so I can sim unlock it. I downloaded and installed this App that you mention, but still keeps saying no binary updated, and with this 4.3 version says there was an error installing superuser. Please help, I dont know what to do.
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
​Settings > More > Application Manager > All > SuperSU > Uninstall updates
​(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
Any updates on this? I'm trying to get root on an HTC One M7 that I just purchased and I'm running into the same error.
Thanks!

I do not want to take OTA system updates...

I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
Root solved your problem ha ha
simms22 said:
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
Click to expand...
Click to collapse
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
cam30era said:
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
Click to expand...
Click to collapse
right. any system file changes prevent install.
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Install a custom recovery. Done. OTAs require the stock recovery in order to flash files.
LaTropa64 said:
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Click to expand...
Click to collapse
itll only attemp if you let it(it needs your approval to update), otherwise itll only tell you that an update is available. if you let it, itll try, but fail. if you boot up, youll be where you were before.
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
you can always look at your android version in aboy phone, to see if it updated or not.
LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
You'll find update or not optimizing apps happens a lot especially if you clear cache etc...
Your fine otas can't install with root
Just flash twrp it will cone in handy incase you brick it one day you'll have twrp to fastboot fix or sideload a rom to recover from.
ONE NOTE: Never ever ever relock your bootloader with the toolkit you'll be screwed. Always leave bootlaoder unlocked. I just had to rma manufacturer phone replacement I relock mine with toolkit and couldn't flash stock firmware or oem unlock again.
Sent from my LGMS769 using XDA Free mobile app
simms22 said:
you can always look at your android version in aboy phone, to see if it updated or not.
Click to expand...
Click to collapse
I'll take a look the next time I get over there. It's not my phone, I just set it up for someone with accessibility issues and wanted it to stay the same as the day I set it up but apparently it's not done that.

Categories

Resources