It's finally official for AT&T Htc one m8 read the details of the ota here http://www.droid-life.com/2014/08/2...eed&utm_campaign=Feed:+DroidLife+(Droid+Life)
Sent from my custom M8
Yeah got the update just now. Digging around for changes.
Thanks man just got the update. Waiting for reboot now so I can re-root.
They added a file manager.
Before folks start diving into the OTA pool without thinking, remember a couple things:
1) OTA won't install with custom recovery. You need to return to stock recovery or else the OTA will send you into a bootloop trying find a stock recovery that isn't there.
2) Root is usually okay, as is unlocked bootloader (OTA will install) however, if any system files were frozen or removed, they will need to be returned to their "stock" condition otherwise the OTA will not install. Flashing the stock rooted ROM or RUU might be the fastest way to do this.
3) It won't be known whether sunshine and/or firewater s-off methods will work (firewater was already squashed, so its very unlikely to work) unless somebody actually tries it. If sunshine doesn't work, this means you will be stuck s-on until a new exploit is found. So s-off before you OTA if you want to be sure you can get s-off (until folks report this OTA is sunshine-friendly).
4) Back it up before you OTA. Personal data, pics whatever. If its important to you, and you will be sad to lose it, than back it up. Copy to your computer, cloud, whatever, your choice. OTA is not "supposed" to delete any personal data. But you know . . . Murphy's Law. This goes for any major system change, ROM flash, etc.
redpoint73 said:
Before folks start diving into the OTA pool without thinking, remember a couple things:
1) OTA won't install with custom recovery. You need to return to stock recovery or else the OTA will send you into a bootloop trying find a stock recovery that isn't there.
2) Root is usually okay, as is unlocked bootloader (OTA will install) however, if any system files were frozen or removed, they will need to be returned to their "stock" condition otherwise the OTA will not install. Flashing the stock rooted ROM or RUU might be the fastest way to do this.
3) It won't be known whether sunshine and/or firewater s-off methods will work (firewater was already squashed, so its very unlikely to work) unless somebody actually tries it. If sunshine doesn't work, this means you will be stuck s-on until a new exploit is found. So s-off before you OTA if you want to be sure you can get s-off (until folks report this OTA is sunshine-friendly).
4) Back it up before you OTA. Personal data, pics whatever. If its important to you, and you will be sad to lose it, than back it up. Copy to your computer, cloud, whatever, your choice. OTA is not "supposed" to delete any personal data. But you know . . . Murphy's Law. This goes for any major system change, ROM flash, etc.
Click to expand...
Click to collapse
Good write up and reminder to the folks who aren't experienced [emoji2]
Sent from my custom M8
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Anyone have the ota they can post?
Sent from my custom M8
THizzle7XU said:
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Click to expand...
Click to collapse
Always best to do a FDR after an ota it's actually recommend to do that by the manufacturer I know that's a best bet in possibly fixing the issue. Please give that a try and post an update so everyone else can know and thanks for your post
Sent from my custom M8
Sent from my custom M8
The standard root tools work on the 4.4.3 update. To update-
1. Flashed stock recovery
2. Did the OTA Update
3. Flashed TWRP
4. Rooted
I did S-Off a while ago, so I can't say whether this breaks the tools for that. All in all, easy peasy
THizzle7XU said:
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Click to expand...
Click to collapse
YES! Plummeting like a rock in a swimming pool. Can't even get it to stay level whislt plugged in to a USB port.
Dan
Buddhake said:
YES! It's plummeting like a rock in a swimming pool, I can't even get it to stay level while plugged into a USB port.
Dan
Click to expand...
Click to collapse
Mine is charging fine, as for the drain though I'll have to report back.
My battery is also crap now.
Sent from my HTC One_M8 using XDA Free mobile app
Harshpatil said:
Yeah got the update just now. Digging around for changes.
Click to expand...
Click to collapse
For what it's worth, here's the Changelog-
Android 4.4.3
Security fixes
Wi-Fi fixes
Bluetooth fixes
Mobile network fixes
Camera app update
Gallery (Image Match)
Settings (Power History)
HTC Sync Manager
Boomsound optimization
Extreme Power Saving Mode optimization
Motion Launch optimization
Quick Setting optimization
californiarailroader said:
Mine is charging fine, as for the drain though I'll have to report back.
Click to expand...
Click to collapse
To clarify, I get the charing error when plugged into a PC, which used to charge the phone just fine, even when not in power saver mode. It's still charging with an outlet, albeit probably not as fast as before. I'll try the factory reset even though the message when you are about to update basically says it's an in-place update that won't affect you files.
I'm now having other issues too. Apps won't update. Texts are sending but the apps are saying they are failing to send. The update really hosed this thing.
THizzle7XU said:
To clarify, I get the charing error when plugged into a PC, which used to charge the phone just fine, even when not in power saver mode. It's still charging with an outlet, albeit probably not as fast as before. I'll try the factory reset even though the message when you are about to update basically says it's an in-place update that won't affect you files.
I'm now having other issues too. Apps won't update. Texts are sending but the apps are saying they are failing to send. The update really hosed this thing.
Click to expand...
Click to collapse
Oh, okay, I have mine plugged into a charger. I'm not having any issues with apps not updating or apps saying messages aren't sending, see if the factory reset clears the errors.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
If all else fails, the RUU is up on HTC's web site-
http://www.htc.com/us/support/htc-one-m8-att/news/
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
That will wipe everything though.
Anyone get the ota or ruu downloaded and can upload somewhere?... Would be appreciated...
californiarailroader said:
Oh, okay, I have mine plugged into a charger. I'm not having any issues with apps not updating or apps saying messages aren't sending, see if the factory reset clears the errors.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
If all else fails, the RUU is up on HTC's web site-
http://www.htc.com/us/support/htc-one-m8-att/news/
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
That will wipe everything though.
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Anyone get the ota or ruu downloaded and can upload somewhere?... Would be appreciated...
Click to expand...
Click to collapse
Can't you download it from the link in my post?
Itll take 8+ hrs to download from that link...was asking if anyone had it already and could upload it elsewhere so it wouldnt take so long to start working on it.:silly::silly:
californiarailroader said:
Can't you download it from the link in my post?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Itll take 8+ hrs to download from that link...was asking if anyone had it already and could upload it elsewhere so it wouldnt take so long to start working on it.:silly::silly:
Click to expand...
Click to collapse
I have it, do you have a preference for sites to download from? I have Mediafire, Drive, Box, Dropbox and One Drive.
I'm uploading it to Google Drive and Microsoft One Drive. It might take just a bit, I have a 120 Mbps download with Comcast, but only 12 Mpbs on the upload.
Edit-What's your email? I can also share it through WeTransfer.
Related
Hi, I'm new to the HTC Evo 4G LTE, but I've been flashing roms through TWRP on multiple android devices and have had experience with it all. I've run into a problem though that I can't find a work around and have searched everywhere I know before posting here. I don't ever post so I can't post the URL link, but its the recommended guide through using HTC's unlocking method.
All seemed dandy till I got to the TWRP part. I flashed it over using the command prompt and the file. Then I selected Recovery. TWRP loads completely and everything looks like it works, except the touch screen. Obviously with this version of TWRP, touch is the only way to get the thing to function, so I'm stuck and can't flash superuser over. Can anyone help me out here?
Few Facts:
First time this phone has had the bootloader unlocked
When rebooting into the stock rom, the touch screen works just fine, so it isn't a hardware issue
I've taken the MicroSD card out so it is purely just the phone itself
Tried flashing over (seems older) clockworkmod recovery to see if it works, but I believe its outdated, considering this phone has 4.1.1 on it and the last update was back in August. It didn't work.
Any help would be much appreciated!
Did you try using volume buttons to move between the items, press home to select?
Sent from my lair.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
volk9029 said:
Did you try using volume buttons to move between the items, press home to select?
Sent from my lair.
Click to expand...
Click to collapse
Edit. You also did not mention what version of recovery you use. Did you try to downgrade to different version?
Sent from my lair.
Yes I tried using the volume buttons and they didn't work. The only thing that functions is the power button, but that locks TWRP, which is no use. For the versions, I tried the newest 2.4.0.0 and 2.1.8 and both had the same problem.
One thing to note also: I received the phone yesterday and while I was contemplating about rooting or not, I decided to update since it was still back at 4.0.4 ICS. Apparently, there was an update for the phone literally today, which I may have received since I'm not seeing the version of the RUU uploaded anywhere. My software version is 3.16.651.3 710RD.
Also, I'm on HBOOT 2.09 if that helps at all.
U flashed the new firmwear zip?
Sent from my EVO using Tapatalk 2
If you mean installed the new firmware via OTA, yes. After updating everything OTA, I started the rooting process.
I have same issue. Have stock/rooted/S-ON and have had no issues keeping root over the last few OTAs. The last OTA broke Voodoo Rootkeeper so I should have known this one was gonna be REALLY toxic. I rolled back to stock recovery to accept OTA and when I went to flash TWRP the touchscreen is non-responsive. TWRP is running because the clock progresses and the battery shows as charging. Power button, as OP describes, does nothing but lock TWRP. I know I take the risk of losing root with OTA acceptance but I depend on all you guys who are much smarter than I to figure those things out. Its why I try to lob donations at the most helpful devs out there...
Thanks in advance for figuring this out gents (and ladies?)...
~ScottWo
Wolosyks said:
I have same issue. Have stock/rooted/S-ON and have had no issues keeping root over the last few OTAs. The last OTA broke Voodoo Rootkeeper so I should have known this one was gonna be REALLY toxic. I rolled back to stock recovery to accept OTA and when I went to flash TWRP the touchscreen is non-responsive. TWRP is running because the clock progresses and the battery shows as charging. Power button, as OP describes, does nothing but lock TWRP. I know I take the risk of losing root with OTA acceptance but I depend on all you guys who are much smarter than I to figure those things out. Its why I try to lob donations at the most helpful devs out there...
Thanks in advance for figuring this out gents (and ladies?)...
~ScottWo
Click to expand...
Click to collapse
And THIS is why we recommend S-OFF to people, and tell people NEVER to take OTAs. At this point, I think you're stuck, unfortunately. You won't be able to access TWRP until someone figures out what the new touch panel image broke. You'll be able to use your ROM fine, but it seems this was something that was done intentionally by HTC to prevent custom firmware (or even software) from working properly.
I could be way off base, though, I guess . . . .
Inconceivable! HTC just pledged to continue supporting developers....wait they don't really support developers
Root
mr_krunchi said:
Hi, I'm new to the HTC Evo 4G LTE, but I've been flashing roms through TWRP on multiple android devices and have had experience with it all. I've run into a problem though that I can't find a work around and have searched everywhere I know before posting here. I don't ever post so I can't post the URL link, but its the recommended guide through using HTC's unlocking method.
All seemed dandy till I got to the TWRP part. I flashed it over using the command prompt and the file. Then I selected Recovery. TWRP loads completely and everything looks like it works, except the touch screen. Obviously with this version of TWRP, touch is the only way to get the thing to function, so I'm stuck and can't flash superuser over. Can anyone help me out here?
Few Facts:
First time this phone has had the bootloader unlocked
When rebooting into the stock rom, the touch screen works just fine, so it isn't a hardware issue
I've taken the MicroSD card out so it is purely just the phone itself
Tried flashing over (seems older) clockworkmod recovery to see if it works, but I believe its outdated, considering this phone has 4.1.1 on it and the last update was back in August. It didn't work.
Any help would be much appreciated!
Click to expand...
Click to collapse
Sorta the same problem, i dont flash roms but i like having my phone rooted. I had to redo the whole process because i lost my root access and i heard they were doing an update, so i did the 3.15 ruu and went back to complete stock, did the 3.16 update, unlocked the phone and it worked great up until i installed twrp 2.4.0.0, same problem touch screen not working. So i figured i would just run the 3.15 ruu again and just keep it there, unfortunately, the 3.16 version hboot which is 2.09 as well, will not let the 3.15 ruu run, says incompatible hboot, but it just restarts the phone, it did overwrite twrp somehow during the process of trying 3.15 the second time and removed it from the phone. From talking to some people, just have to wait until someone figures out how to fix that to get back up and running. I am pretty new to root but i like having those options to screw with the phone. Anxiously awaiting a fix though. Need to flash some roms soon, but never could get them to work, worked great on my Evo 4g...just not having the same luck with 4G LTE.
Same issue here
I never rooted my phone before and kept it updated up to the most recent 3.16.651.3 and it used to say "Locked" under Bootloader. I followed the instructions to the T from http://forum.xda-developers.com/showthread.php?t=2026938 with 2.09 Hboot files etc. All this and the problem I had is that when I got to the step where you load up TWRP, the touch screen didn't respond, nor did the volume rocker allow selection. Single pressing the power button, for some reason, showed "Slide to unlock" but I couldn't slide/unlock. Holding power still rebooted the phone.
Relocked and reloaded the original stock ROM, followed the procedure again, and it worked perfectly.
yeah I just got my phone back from RMA today ( parts of the screen were non responsive loose pin or something). when I sent it off I relocked it and Re S-ONed ( on H boot 1.19)it. as I read some places where they wont fix any hardware if the software has been S-OFFed.
when it came back it had the 3.16 stock firmware(Hboot 2.09) and now I cant S-OFF it ( dirty racoon gives errors about 3.16) cant downgrade it ( 3.15 RUU wont load) cant get roms on it( clockwork cant mount SD cards, and TWRP wont respond to touch)
needless to say I'm rather upset with HTC right now
Agreed
Totally agree, this kinda blows because if i could at least go back to 3.15 ruu it wouldn't be so bad, but i cant even do that. Hopefully someone way smarter at this will figure it out soon and get a fix going.
tonyevo52 said:
Totally agree, this kinda blows because if i could at least go back to 3.15 ruu it wouldn't be so bad, but i cant even do that. Hopefully someone way smarter at this will figure it out soon and get a fix going.
Click to expand...
Click to collapse
It's conceivably possible to change the main version on the /misc partition to match the previous OTA version (3.15.651.13), and then you should be able to flash the 3.15 RUU/PJ75IMG, since the HBOOT version didn't change.
But I'm S-OFF, so I don't have to worry about testing that theory.
I wish i was S-Off, i was rooted under 3.15 and everything was good, like a dumbass i updated my prl a couple weeks ago and totally forgot it would cause me to lose root, so i just never rerooted due to time, so when i saw the new 3.16 was out i figured i would relock, update, unlock and install twrp, worked good up to the twrp part where it would not respond to touch, and i tried to go back to the 3.15 ruu but wont let me. At least the phone still works, but a regular phone at this point and i just started rooting at the beginning of January so im still learing alot, actually don't mind screwing it up and learning from my mistakes, but my saving grace was always that i would go back to 3.15 if needed, not anymore, so now i will wait until someone figures it out, in the meantime though, learning alot more by reading on here. The only problem i seem to find is i understand most of the language here, but sometimes i see people trying to help people with step by step instructions and they miss a step or they explain it way technical and it puts people into panic mode, my eyes have glazed over a couple wonder what people are saying to do...but totally worth it and appreciate the help definitely.
Tony, updating your prl shouldn't take away your root.
Taking the ota could.
Sent from my EVO using xda app-developers app
I didn't even think about it taking away the root, but i lost root the same day i updated the prl a couple weeks ago. Never accepted any ota's while the phone was rooted, i just want root back...still learning though, fun messing with it!
Good news!
TWRP has been updated to version 2.4.1.0 that fixes the touchscreen issue in recovery. Please thank Dees_Troy for the fix at your earliest convenience .
Captain_Throwback said:
Good news!
TWRP has been updated to version 2.4.1.0 that fixes the touchscreen issue in recovery. Please thank Dees_Troy for the fix at your earliest convenience .
Click to expand...
Click to collapse
;
Link on the TWRP website is broken for the FastBoot version of 2.4.1.0 it takes you to an HTC page. The links goes to: htcDOTcom/www/help/htc-evo-3d/#download
Sorry, can't post URLs yet so I edited the link for viewing...
Anyone have a working link, or a way to advise the correct person of the misdirected link?
Thanks!!!!
sdax2 said:
;
Link on the TWRP website is broken for the FastBoot version of 2.4.1.0 it takes you to an HTC page. The links goes to: htcDOTcom/www/help/htc-evo-3d/#download
Sorry, can't post URLs yet so I edited the link for viewing...
Anyone have a working link, or a way to advise the correct person of the misdirected link?
Thanks!!!!
Click to expand...
Click to collapse
I don't know where you're looking, but this link is right there on the page:
http://techerrata.com/browse/twrp2/jewel
You seem to be looking at an EVO 3D version?
Captain_Throwback said:
I don't know where you're looking, but this link is right there on the page:
You seem to be looking at an EVO 3D version?
Click to expand...
Click to collapse
Victim of browsing because I've downloaded so many times before...
But in the "Download - Fastboot Method:" section there is a link that points to the drivers needed from HTC. Without reading carefully I just clicked on the link labeled HERE.
It does however point to an incorrect page for the HTC drivers. Sorry for the confusion, and thanks for the clarification Captain...
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
please delete
Tips & Suggestions, Common Fixes & Questions
please delete
Cant get PC to read watch in step 10 of flashing
I have an Omate 1/8 which arrived yesterday. I factory reset it. I got through steps 1-9 of the recent Rom update. When I tried 10, to connect my watch to my PC, it recognized a "removable disc G:" and told me to insert a disk, but it didn't/couldn't read the watch contents.
(The setup file in step 2 did properly set up according to my pc.)
Anyone able to suggest what I do?
Tom19146 said:
I have an Omate 1/8 which arrived yesterday. I factory reset it. I got through steps 1-9 of the recent Rom update. When I tried 10, to connect my watch to my PC, it recognized a "removable disc G:" and told me to insert a disk, but it didn't/couldn't read the watch contents.
(The setup file in step 2 did properly set up according to my pc.)
Anyone able to suggest what I do?
Click to expand...
Click to collapse
Are you trying to flash the ROM or trying to run the patch? They are two different things. This thread is for the Patch.
No root
Thanks for all your work so far on the x201! Having an issue of no root on the watch...
1. x201 Omate Truesmart
2. Omate_Truesmart_20140120.154604_v2.0
3. Not root after flashing 1.0.2 patch
4. Reverted back to stock, reflashed. Attempted the 1.0.1 version. Security Settings and SU say no root ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!")
urmcgwy said:
Thanks for all your work so far on the x201! Having an issue of no root on the watch...
1. x201 Omate Truesmart
2. Omate_Truesmart_20140120.154604_v2.0
3. Not root after flashing 1.0.2 patch
4. Reverted back to stock, reflashed. Attempted the 1.0.1 version. Security Settings and SU say no root ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!")
Click to expand...
Click to collapse
What OS?
EDIT;
What model?
Lokifish Marz said:
What OS?
Click to expand...
Click to collapse
Sorry Win7 x64
---------- Post added at 09:18 PM ---------- Previous post was at 08:46 PM ----------
urmcgwy said:
Sorry Win7 x64
Click to expand...
Click to collapse
And I have no idea why I wrote Win7.... its Win8.1 x64 =P
---------- Post added at 09:25 PM ---------- Previous post was at 09:18 PM ----------
urmcgwy said:
Sorry Win7 x64
---------- Post added at 09:18 PM ---------- Previous post was at 08:46 PM ----------
And I have no idea why I wrote Win7.... its Win8.1 x64 =P
Click to expand...
Click to collapse
Omate "Developer Edition" 1/8
urmcgwy said:
Sorry Win7 x64
And I have no idea why I wrote Win7.... its Win8.1 x64
Omate "Developer Edition" 1/8
Click to expand...
Click to collapse
Is ADB installed?
Did you disable Quickboot?
Did you enable USB Debugging?
Did the Patch give any errors when you ran it?
Just hard wiped my dev unit, flashed stock Jan20 and ran the Patch v1.0.2. The only thing I had happen was SuperSU tell me the su binary needed to be updated. I am curious as you mention trying to install SuperSU, it's preinstalled by the Patch and should not have to be installed by the user.
Lokifish Marz said:
Is ADB installed?
Did you disable Quickboot?
Did you enable USB Debugging?
Did the Patch give any errors when you ran it?
Just hard wiped my dev unit, flashed stock Jan20 and ran the Patch v1.0.2. The only thing I had happen was SuperSU tell me the su binary needed to be updated. I am curious as you mention trying to install SuperSU, it's preinstalled by the Patch and should not have to be installed by the user.
Click to expand...
Click to collapse
I did all of that according to your instructions and didn't get any errors. Decided to wipe and return to stock, but got an error during flashing (status bar went to 100% really quick and an error popped up around 13 seconds). Watch won't respond to anything including plugging it into a wall charger. Will try with another computer to see if that helps, and then try pulling the battery if that doesn't work. Any advice to unbrick?
urmcgwy said:
I did all of that according to your instructions and didn't get any errors. Decided to wipe and return to stock, but got an error during flashing (status bar went to 100% really quick and an error popped up around 13 seconds). Watch won't respond to anything including plugging it into a wall charger. Will try with another computer to see if that helps, and then try pulling the battery if that doesn't work. Any advice to unbrick?
Click to expand...
Click to collapse
Those errors are really important. Knowing what the error and what color the was was tells me a lot of things. As far as the watch being unresponsive, battery pull or wait a few hours for the battery to die. If you don't want ot void the warranty I suggest waiting for the battery to die.
Something is not right then because if SuperSU (or any file file that matter) was not installed, the script would have given an error.
EDIT:
I don't want to seem like I'm not trying to help but I run the script 20-30 times before a release and use it about 10-15 times a day on a regular basis. In fact I use a slightly modified version to cut down on dev time.
Lokifish Marz said:
Those errors are really important. Knowing what the error and what color the was was tells me a lot of things. As far as the watch being unresponsive, battery pull or wait a few hours for the battery to die. If you don't want ot void the warranty I suggest waiting for the battery to die.
Something is not right then because if SuperSU (or any file file that matter) was not installed, the script would have given an error.
EDIT:
I don't want to seem like I'm not trying to help but I run the script 20-30 times before a release and use it about 10-15 times a day on a regular basis. In fact I use a slightly modified version to cut down on dev time.
Click to expand...
Click to collapse
Sounds good! SuperSU was installed, it just said the binaries weren't installed. I took off the screw covers for the waterproofing warranty, but one of the screws was stripped, so I think I'm out of luck...the watch is off so I don't think the battery will even drain. I guess it is time to see what Omate customer service is made of.
urmcgwy said:
Sounds good! SuperSU was installed, it just said the binaries weren't installed. I took off the screw covers for the waterproofing warranty, but one of the screws was stripped, so I think I'm out of luck...the watch is off so I don't think the battery will even drain. I guess it is time to see what Omate customer service is made of.
Click to expand...
Click to collapse
Unless you pull the battery, the watch may appear to be off but stuck on bootloader mode. It's happened to me a couple times as well.
If yours is anything like mine, the placement screws are better than the ones in the TS.
Lokifish Marz said:
Unless you pull the battery, the watch may appear to be off but stuck on bootloader mode. It's happened to me a couple times as well.
If yours is anything like mine, the placement screws are better than the ones in the TS.
Click to expand...
Click to collapse
Thanks for all the help! I'll just wait until tomorrow to see if the watch dies on me and see what Omate has to say. Really appreciate the quick responses!
I just flashed back to stock, what next is needed?
Following Lokifish's very helpful video, I have finally succeeded in flashing back to stock. Do I need now to do a security patch, or was that included in the stock file I'd have used? Also, how might I obtain some of the useful additions that Loki installed in Imperium, working from stock?
Thanks for all your help!
Tom
Tom19146 said:
Following Lokifish's very helpful video, I have finally succeeded in flashing back to stock. Do I need now to do a security patch, or was that included in the stock file I'd have used? Also, how might I obtain some of the useful additions that Loki installed in Imperium, working from stock?
Thanks for all your help!
Tom
Click to expand...
Click to collapse
If you flashed back to stock then none of the improvements listed in the OP will be found on your device. Stock is exactly that, stock with no changes at all.
Except for some build.prop edits, removing preinstalled apps like FB and a different launcher, there is no difference between the patch and the ROM. I in fact use a slightly modified version of the Patch myself to build the test builds of the ROM.
Lokifish Marz said:
If you flashed back to stock then none of the improvements listed in the OP will be found on your device. Stock is exactly that, stock with no changes at all.
Except for some build.prop edits, removing preinstalled apps like FB and a different launcher, there is no difference between the patch and the ROM. I in fact use a slightly modified version of the Patch myself to build the test builds of the ROM.
Click to expand...
Click to collapse
I am not sure if I understood. Weren't there some security issues you helped address,( before Imperium), that were recommended to add to the stock rom?
Are you saying if I do this patch, I will basically have the Rom plus some adjustments? Are these security related or just improvements, tweaks and some helpful programs? Either way, I think I will prefer this to the basic stock. (I took your reply to suggest there might be no need to do the patch, that it is useful to you but not so necessary...)
Tom
Oh, by the way, for us true newbies, it might be helpful to offer some advice how best to negotiate the downloads at host-dev... I found myself in a hellish loop of websites offering that I join for free but then never giving a way to get past the "upgrade to premium" offers. In the end, I downloaded iLivid download manager and got it to work.
Tom19146 said:
I am not sure if I understood. Weren't there some security issues you helped address,( before Imperium), that were recommended to add to the stock rom?
Are you saying if I do this patch, I will basically have the Rom plus some adjustments? Are these security related or just improvements, tweaks and some helpful programs? Either way, I think I will prefer this to the basic stock. (I took your reply to suggest there might be no need to do the patch, that it is useful to you but not so necessary...)
Tom
Oh, by the way, for us true newbies, it might be helpful to offer some advice how best to negotiate the downloads at host-dev... I found myself in a hellish loop of websites offering that I join for free but then never giving a way to get past the "upgrade to premium" offers. In the end, I downloaded iLivid download manager and got it to work.
Click to expand...
Click to collapse
Fixes have not made it to official firmware yet.
Rom = Patch + extras
Use an adblocker and only the actual download button will be seen.
Thanks. All working with the patch now.
---------- Post added at 07:38 PM ---------- Previous post was at 06:40 PM ----------
I successfully downloaded the patch. I was downloading apps and after downloading cal from the Omate store, it froze. I cannot shut the phone off. Neither button. Touch screen unresponsive. Is there any other way to reboot things than to take the battery out? Any reset pin hole or such?
Tom19146 said:
Thanks. All working with the patch now.
---------- Post added at 07:38 PM ---------- Previous post was at 06:40 PM ----------
I successfully downloaded the patch. I was downloading apps and after downloading cal from the Omate store, it froze. I cannot shut the phone off. Neither button. Touch screen unresponsive. Is there any other way to reboot things than to take the battery out? Any reset pin hole or such?
Click to expand...
Click to collapse
Iv'e had that happen to me a couple of times even when on stock w no patch. Short of pulling the battery you have to wait for the battery to die.
Omate TS slow and built-in memory full
Hi all, hopefully this time I am posting in the right place. After flashing the patch my TS seems to be slower and seems to ignore storing things on the sd card. The TS memory now has only 228mb free and the SD card is all free (this is set up as the default storage). Has anybody come across a similar situation (TS slow and memory full) and how could I overcome that? Many thanks in advance (please be patient, I am not an expert)!
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
JayRolla said:
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
Click to expand...
Click to collapse
Thanks for the advice, but others are getting the update OTA, without root or downloading Android Rev.
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
redpoint73 said:
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
Click to expand...
Click to collapse
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
Click to expand...
Click to collapse
How did it not work? As long as you are completely stock with cid cws__001 it should work.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
sassij said:
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Click to expand...
Click to collapse
download ota package from here http://www.androidfilehost.com/?fid=23487008491963146
put it on your micro sd card
boot to recovery "vol up and power 10 sec, vol down and power until boot loader comes up and navigate to recovery"
once in recovery its either vol up and power or vol down and power for a few seconds for advanced options
choose install update from external sd.
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Click to expand...
Click to collapse
No, the phone does not need to be modded to run the RUU. Its a "official" update/recovery tool provided by HTC. If you phone is stock, it should work, as the above response also indicated.
If it "wouldn't work" it would be more helpful to give details, if you want proper help. Not just say it didn't work. What step did it fail at , any error message, etc. Also, the current state of your phone (root, unlocked bootloader, etc.), as we can only assume based on your comment about root, etc.
RUU failing on a stock device is usually a USB connectivity issue on the part of your computer (not a problem on the phone's side). Install or re-install the HTC drives, try a different USB port, or a different computer (if available). If on Windows 8.1, that version is a known issue and will not work with the HTC drivers. You can also try re-downloading the RUU to make sure it wasn't damaged/corrupted during download.
I'm new here and I need help.
Please if anyone can guide me on how to downgrade my phone from Kitkat 4.4.2 to Jellybean.
My nephew upgraded it for me and few days after I noticed my mobile data was not working anymore. Second I noticed was Bluetooth, it wasn't working either. I ignored it because I coud still use wifi, but a week ago it also gave up. My phone also restarts on its own.
I asked some tech and I was told it was because of the upgrade that is why I want to downgrade. Anyone who can assist me please? Or any solution that you know. I am not sure myself if the problem was caused by the upgrade. I tried checking videos on youtube on how to downgrade but I;m scared to brick my phone. I am not sure about the correct files to download and that sort of stuff.
PLEASE help.
I just want my phone working.
I tried to root my phone
by following a video on
YouTube and I think it's
already rooted.
Ynayashi said:
I'm new here and I need help.
Please if anyone can guide me on how to downgrade my phone from Kitkat 4.4.2 to Jellybean.
My nephew upgraded it for me and few days after I noticed my mobile data was not working anymore. Second I noticed was Bluetooth, it wasn't working either. I ignored it because I coud still use wifi, but a week ago it also gave up. My phone also restarts on its own.
I asked some tech and I was told it was because of the upgrade that is why I want to downgrade. Anyone who can assist me please? Or any solution that you know. I am not sure myself if the problem was caused by the upgrade. I tried checking videos on youtube on how to downgrade but I;m scared to brick my phone. I am not sure about the correct files to download and that sort of stuff.
PLEASE help.
I just want my phone working.
I tried to root my phone
by following a video on
YouTube and I think it's
already rooted.
Click to expand...
Click to collapse
Well, nope I don't think now you can downgrade your device from KitKat to JellyBean not possible at all because the boot loader may have been upgraded and if you even try downgrading the device by rooting your device it may results in bricking up. I would say rather than moving forward with the downgrading better would be to stay with the KitKat and keep your fingers crossed for the next update to fix most of your problems.
promo87 said:
Well, nope I don't think now you can downgrade your device from KitKat to JellyBean not possible at all because the boot loader may have been upgraded and if you even try downgrading the device by rooting your device it may results in bricking up. I would say rather than moving forward with the downgrading better would be to stay with the KitKat and keep your fingers crossed for the next update to fix most of your problems.
Click to expand...
Click to collapse
Thank you.
Ynayashi said:
Thank you.
Click to expand...
Click to collapse
Depends on which variant of the S4 that you have. Some versions have ways to do a modded downgrade (not official via Odin like the good ole days...), but in general it's more trouble and risk than it is worth.
Thank you for your time and suggestions. I'd just want to add that my phone overheats even when it's off. And it also doesn't turn on anymore unless I connect the charger. I think its dying.
Ynayashi said:
Thank you for your time and suggestions. I'd just want to add that my phone overheats even when it's off. And it also doesn't turn on anymore unless I connect the charger. I think its dying.
Click to expand...
Click to collapse
Did he update the phone officially or custom rom? By OTA or from the computer? I would reset the device and reinstall the latest firmware via Odin on the PC. If it was done via OTA, that can cause some odd issues, especially if the download was not 100% or reset during the process. It's always a good idea to reset when updating major versions, despite what the manufacturers tell you. I see it all the time at my shop and during my many many hours here on XDA researching and helping others.
es0tericcha0s said:
Did he update the phone officially or custom rom? By OTA or from the computer? I would reset the device and reinstall the latest firmware via Odin on the PC. If it was done via OTA, that can cause some odd issues, especially if the download was not 100% or reset during the process. It's always a good idea to reset when updating major versions, despite what the manufacturers tell you. I see it all the time at my shop and during my many many hours here on XDA researching and helping others.
Click to expand...
Click to collapse
Thank you! All I know is that he upgraded my phone using my laptop and using Odin.
Maybe I can upgrade it again?
Ynayashi said:
Thank you! All I know is that he upgraded my phone using my laptop and using Odin.
Maybe I can upgrade it again?
Click to expand...
Click to collapse
Since you don't know exactly what or how it was done, it might be a good idea to post a screenshot of the About Phone section for us so we can see which update, if it's official, and all that.
es0tericcha0s said:
Since you don't know exactly what or how it was done, it might be a good idea to post a screenshot of the About Phone section for us so we can see which update, if it's official, and all that.
Click to expand...
Click to collapse
Thank you so much
My nephew was here lat night and tried different things to no avail. I am just sad I only use my phone now to play songs and take photos.
Here's the screenshot. I really appreciate your time guys.
raselo8o3 said:
Thank you so much
My nephew was here lat night and tried different things to no avail. I am just sad I only use my phone now to play songs and take photos.
Here's the screenshot. I really appreciate your time guys.
Click to expand...
Click to collapse
What region are you using the phone in? It looks like the firmware is from Romania. Not that it couldn't work other places, but sometimes it works best to use a firmware and modem meant for the area you are using the phone in... Stranger things have happened.
es0tericcha0s said:
What region are you using the phone in? It looks like the firmware is from Romania. Not that it couldn't work other places, but sometimes it works best to use a firmware and modem meant for the area you are using the phone in... Stranger things have happened.
Click to expand...
Click to collapse
Thank you again.
I am in the Philippines and I don't know what firmware my nephew used.
I found video on youtube and did the same to my phone but nothing happened. I flashed my modem, it says on youtube, modem wifi fix, did it twice but didn't work. I also tried custom kernel but was getting error.
I don't know what to do anymore. It's just really very sad for a very expensive smartphone to not work. Bluetooth, mobile data and wifi are all not working. It doesn't turn on as well if you remove the battery unless you connect a charger.
: (
---------- Post added at 05:02 PM ---------- Previous post was at 04:56 PM ----------
es0tericcha0s said:
What region are you using the phone in? It looks like the firmware is from Romania. Not that it couldn't work other places, but sometimes it works best to use a firmware and modem meant for the area you are using the phone in... Stranger things have happened.
Click to expand...
Click to collapse
Thank you again.
I am in the Phillipines. I don't really know what firmware he used.
I flashed my modem twice tonight, found a video on youtbe about modem wifi fix and it didn't work too. Custom kernel didn't work as well as I was getting an error.
It's getting depressing, I don't know what to do anymore. It's just that, it's an expensive smartphone without mobile data, bluetooth and wifi. It doesn't turn on as well if you remove the battery unless you connect a charger.
raselo8o3 said:
Thank you again.
I am in the Philippines and I don't know what firmware my nephew used.
I found video on youtube and did the same to my phone but nothing happened. I flashed my modem, it says on youtube, modem wifi fix, did it twice but didn't work. I also tried custom kernel but was getting error.
I don't know what to do anymore. It's just really very sad for a very expensive smartphone to not work. Bluetooth, mobile data and wifi are all not working. It doesn't turn on as well if you remove the battery unless you connect a charger.
: (
---------- Post added at 05:02 PM ---------- Previous post was at 04:56 PM ----------
Thank you again.
I am in the Phillipines. I don't really know what firmware he used.
I flashed my modem twice tonight, found a video on youtbe about modem wifi fix and it didn't work too. Custom kernel didn't work as well as I was getting an error.
It's getting depressing, I don't know what to do anymore. It's just that, it's an expensive smartphone without mobile data, bluetooth and wifi. It doesn't turn on as well if you remove the battery unless you connect a charger.
Click to expand...
Click to collapse
What happens when you try to toggle data? Does it turn on and right back off or does the switch to move to on not slide over or is greyed out?
I might try using Odin to install the Phillipines firmware, which you can find here:
http://www.ibtimes.co.uk/update-gal...xxufnbe-android-4-4-2-kitkat-firmware-1439096
It won't make it worse anyway...