Database Users

[Q] Updating via OTA works with TWRP?

I was wondering if it will be safe if you update via OTA with a custom Open script Recovery such has TWRP would be safe, I do not want to get any issues while updating to Android 4.3 when it is available like soft bricking.

andyabc said:
I was wondering if it will be safe if you update via OTA with a custom Open script Recovery such has TWRP would be safe, I do not want to get any issues while updating to Android 4.3 when it is available like soft bricking.
Click to expand...
Click to collapse
You have to be stock to get the google updates. No custom recovery at all.

zelendel said:
You have to be stock to get the google updates. No custom recovery at all.
Click to expand...
Click to collapse
Have you tested it?, I am not sure if it could be possible since TWRP is OpenScriptRecovery so the system should be able to just get the OTA update to flash like nothing is wrong or anything.
I can restore the stock recovery using the Nexus Toolkit.
Sent from my Nexus 4 using xda app-developers app

andyabc said:
Have you tested it?, I am not sure if it could be possible since TWRP is OpenScriptRecovery so the system should be able to just get the OTA update to flash like nothing is wrong or anything.
I can restore the stock recovery using the Nexus Toolkit.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It is well known that it will not work on none official recoveries. It will also not work if you are rooted. There are threads around about this.

zelendel said:
It is well known that it will not work on none official recoveries. It will also not work if you are rooted. There are threads around about this.
Click to expand...
Click to collapse
What do you mean that it will not work if your rooted?, will it give you some error or something on the stock recovery?
Sent from my Nexus 4 using xda app-developers app

andyabc said:
What do you mean that it will not work if your rooted?, will it give you some error or something on the stock recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ok it seems it will flash but you will lose root.
http://forum.xda-developers.com/showthread.php?t=2145848

zelendel said:
Ok it seems it will flash but you will lose root.
http://forum.xda-developers.com/showthread.php?t=2145848
Click to expand...
Click to collapse
Will OTA Rootkeeper help?, I have that installed just in case there is an update has I am fully aware that the update will replace the system partition.
Sent from my Nexus 4 using xda app-developers app

andyabc said:
Will OTA Rootkeeper help?, I have that installed just in case there is an update has I am fully aware that the update will replace the system partition.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
To be honest I have no idea as I never do OTA updates. No real point.

zelendel said:
To be honest I have no idea as I never do OTA updates. No real point.
Click to expand...
Click to collapse
Ok, I found a really useful thread though: http://forums.androidcentral.com/htc-one/282447-install-ota-update-twrp-recovery.html
Looks like that stock recovery is the first thing to do.
Sent from my Nexus 4 using xda app-developers app

andyabc said:
Ok, I found a really useful thread though: http://forums.androidcentral.com/htc-one/282447-install-ota-update-twrp-recovery.html
Looks like that stock recovery is the first thing to do.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Even though that is for a different device and a completely different OTA set up. Being fully stock is always the best bet. Like I said I never do OTA and on a nexus it is almost completely pointless as the 4.3 update will be available in a flashable zip file with in a matter of hours in not less.

zelendel said:
Even though that is for a different device and a completely different OTA set up. Being fully stock is always the best bet. Like I said I never do OTA and on a nexus it is almost completely pointless as the 4.3 update will be available in a flashable zip file with in a matter of hours in not less.
Click to expand...
Click to collapse
So you can just flash the zip 100% on a custom recovery?
Sent from my Nexus 4 using xda app-developers app

andyabc said:
So you can just flash the zip 100% on a custom recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. Once the devs have gotten their hands on it there will be a rooted zip in a matter of hours of release that can be flashed like a normal custom rom

zelendel said:
Yeah. Once the devs have gotten their hands on it there will be a rooted zip in a matter of hours of release that can be flashed like a normal custom rom
Click to expand...
Click to collapse
Awesome, I am just going to flash the stock recovery so when the update is available the data will not get wiped.
Sent from my Nexus 4 using xda app-developers app

If your using twrp v2.5.0.0 when we get the ota update you can use it to update and it will flash it fine it will also detect that you don't have root and will ask you if you want it restored
From my BLACKED OUT N4

spaceman860 said:
If your using twrp v2.5.0.0 when we get the ota update you can use it to update and it will flash it fine it will also detect that you don't have root and will ask you if you want it restored
From my BLACKED OUT N4
Click to expand...
Click to collapse
So the OTA update would just work?, all well I have the stock recovery flashed at the moment anyway so when the OTA updates stop I will flash the recovery back and then install a custom rom with 4G and USB Host supported also having all the good tweaks like the camera tweak.
Sent from my Nexus 4 using xda app-developers app

I had CWM on my rooted Nexus 4, and the OTA for android 4.3 came along, and worked fine! Android asked to reboot to install the update, so I agreed, and the reboot loaded CWM which flashed the update. I lost root however, but it was easy to put back.
Has anyone done the OTA to 4.3 while having TWRP recovery? I wonder which of the two recoveries is better at handling OTA updates ... some folks say never attempt OTA with a custom recovery, but CWM has always handled it fine on my Nexus 4 (I've done different over-the-air updates around 3 times now).

sordna said:
Has anyone done the OTA to 4.3 while having TWRP recovery? I wonder which of the two recoveries is better at handling OTA updates ... some folks say never attempt OTA with a custom recovery, but CWM has always handled it fine on my Nexus 4 (I've done different over-the-air updates around 3 times now).
Click to expand...
Click to collapse
I am also interested about doing an update to 4.3 with everything stock except for TWRP, and am waiting to hear other people experiences before I try it. I see that the following shows one recommended method (Scenario #2), although I am not sure exactly how to do it. I am curious as to why this is any different than doing it OTA:
http://forum.xda-developers.com/show....php?t=2145848

pjc123 said:
I am also interested about doing an update to 4.3 with everything stock except for TWRP, and am waiting to hear other people experiences before I try it. I see that the following shows one recommended method (Scenario #2), although I am not sure exactly how to do it. I am curious as to why this is any different than doing it OTA:
http://forum.xda-developers.com/show....php?t=2145848
Click to expand...
Click to collapse
From what I am reading now, it's going to work. You will loose root and might loose TWRP, but if you have unlocked bootloader you can flash them both again. I'd say go ahead and let us know if you lost both root and TWRP or just root.

sordna said:
From what I am reading now, it's going to work. You will loose root and might loose TWRP, but if you have unlocked bootloader you can flash them both again. I'd say go ahead and let us know if you lost both root and TWRP or just root.
Click to expand...
Click to collapse
Actually, what I am reading now from a lot of people is that it is not necessary to download the file, and just do the OTA, as there is no difference. If I were to lose TWRP it is an easy enough process to get it back. As far as rooting, I am waiting for Koush to upgrade his superuser app, as I switched from SuperSU a while back (Both developers are having a tough time with 4.3). I am also waiting for things to settle down with all the 4.3 bugs and app upgrades. Maybe in a few weeks; there is just way too many issues.

pjc123 said:
Actually, what I am reading now from a lot of people is that it is not necessary to download the file, and just do the OTA, as there is no difference. If I were to lose TWRP it is an easy enough process to get it back. As far as rooting, I am waiting for Koush to upgrade his superuser app, as I switched from SuperSU a while back (Both developers are having a tough time with 4.3). I am also waiting for things to settle down with all the 4.3 bugs and app upgrades. Maybe in a few weeks; there is just way too many issues.
Click to expand...
Click to collapse
No need to wait, you can switch back to SuperSU, the latest version (1.51) has been working perfectly with 4.3 for me.
BTW I just installed BootUnlocker for nexus devices, a great app that can lock/unlock your boot loader from within android without wiping your data!

Latest OTA

Just receive message of OTA. It is a small update and file size is 3.4MB. Since I have flashed the latest TWRP that support the OTA update.
I can not see any different version change.

taitony said:
Just receive message of OTA. It is a small update and file size is 3.4MB. Since I have flashed the latest TWRP that support the OTA update.
I can not see any different version change.
Click to expand...
Click to collapse
i just recieved it myself on my Android 4.4, it says "fixes bugs" which i haven't felt there was, but i guess it's not everyone that finds the bugs they fix, and maybe the performance will go up a little more, i will bench a little later, depending on how much i have to do at work

Yeah it's mostly under the hood bug fixes. There's no change log but one new 'feature' they found is that it will remind you to set up a backup account if you have multiple Google accounts on the device.
Sent from my Nexus 7 using XDA Premium 4 mobile app

puma99dk| said:
i just recieved it myself on my Android 4.4, it says "fixes bugs" which i haven't felt there was, but i guess it's not everyone that finds the bugs they fix, and maybe the performance will go up a little more, i will bench a little later, depending on how much i have to do at work
Click to expand...
Click to collapse
Great to see your investgation what will be updated. But my Nexus 4 has no such update, so it is not for all KitKat devices.

Yeah I checked if it was also up for Nexus 4, sadly its just the N7 up for grabs, Just got the OTA notification, 3MB file.
Also there's this, new build, KRT16S

Sorry is this a jelly bean update or kit kat?
Sent from my SM-N9005 using XDA Premium HD app

protoism said:
Sorry is this a jelly bean update or kit kat?
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
we talk about "Kitty kat"
but so far Benchmarks haven't improved to me, but it don't get as hot as with JB rom around the cam when it's in use so that's fine with me

puma99dk| said:
we talk about "Kitty kat"
but so far Benchmarks haven't improved to me, but it don't get as hot as with JB rom around the cam when it's in use so that's fine with me
Click to expand...
Click to collapse
Maybe I have missed something, but are people receiving a small kitty kat bug fix OTA, even though 4.4 has not actually gone out over the air, but is just being sideloaded?
Sent from my SM-N9005 using XDA Premium HD app

protoism said:
Maybe I have missed something, but are people receiving a small kitty kat bug fix OTA, even though 4.4 has not actually gone out over the air, but is just being sideloaded?
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
i read some has gotten OTA but not everyone, i used adb yesterday at work to "sideload" 4.4 on to my Nexus 7 2013 16gb tablet and it just is nice running smooth, no heat around my cam anymore in use.
i normally game a little and use it for Teamviewer. I brought my tablet bcs i was tired of dragging a laptop with me around, bcs i drag it to work everyday.
I basicly when at family, or friends house use my tablet for surfing, teamviewer and all what i used the laptop for it's nice

puma99dk| said:
i read some has gotten OTA but not everyone, i used adb yesterday at work to "sideload" 4.4 on to my Nexus 7 2013 16gb tablet and it just is nice running smooth, no heat around my cam anymore in use.
i normally game a little and use it for Teamviewer. I brought my tablet bcs i was tired of dragging a laptop with me around, bcs i drag it to work everyday.
I basicly when at family, or friends house use my tablet for surfing, teamviewer and all what i used the laptop for it's nice
Click to expand...
Click to collapse
Nice, just in this forum only one person claims to have received 4.4 OTA. It does seem they are sending out a patch for something that is only available as a factory image that is being sideloaded. Curious.
Sent from my SM-N9005 using XDA Premium HD app

protoism said:
Nice, just in this forum only one person claims to have received 4.4 OTA. It does seem they are sending out a patch for something that is only available as a factory image that is being sideloaded. Curious.
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
the factory image and the one that comes on OTA should be the same as far as i know.
but it was pretty easy to flash my tablet, it took a little bcs i had a problem but when i fixed that one it went smoothly and no issues at all.

anyone else's touchscreen get ridiculous after this small OTA? I never had issues, then we got that jellybean OTA to "fix" touch screen issues for certain people, which then proceeded to break my touch screen. then I got kitkat, and it's perfect again, no touch issues anymore.. now I got this OTA and this morning I had to press everything 5 times before it registered! I did a reboot and it went away, but seriously, if they broke touch again, I'm giving up on this tablet.
Sent from my Verizon LG G2 using Tapatalk Pro

Where is the update located once it is downloaded, I'm trying to install it with TWRP.

Just got it via OTA (had side loaded KitKat before that). Made me lose root but that should be easily fixed.

I had side loaded 4.4, unlocked and rooted. I got the OTA notification and there was an error installing and now I'm stuck in a bootloop. When it comes up it has dead android with red exclamation point and says "No command."

embhorn said:
I had side loaded 4.4, unlocked and rooted. I got the OTA notification and there was an error installing and now I'm stuck in a bootloop. When it comes up it has dead android with red exclamation point and says "No command."
Click to expand...
Click to collapse
Same thing happened to me. I got the OTA notification but stoopidly I had SuperSU in OTA survival mode. The update failed and I ended up at the 'No Command' recovery thing you are talking about.
I was able to fix it by manually flashing the /boot, /recovery, and /system partitions (NOT /userdata ) in fastboot using the KRT16S system image that can be found here (https://developers.google.com/android/nexus/images#razorkrt16s). Everything was okay after that - all of my user data was intact and I was updated to KRT16S :good:

paddycr said:
Same thing happened to me. I got the OTA notification but stoopidly I had SuperSU in OTA survival mode. The update failed and I ended up at the 'No Command' recovery thing you are talking about.
I was able to fix it by manually flashing the /boot, /recovery, and /system partitions (NOT /userdata ) in fastboot using the KRT16S system image that can be found here (https://developers.google.com/android/nexus/images#razorkrt16s). Everything was okay after that - all of my user data was intact and I was updated to KRT16S :good:
Click to expand...
Click to collapse
Ah well. I win the noob award. I panicked and re-flashed stock. But my saving grace is that I have a backup from not too long ago.

airmaxx23 said:
Where is the update located once it is downloaded, I'm trying to install it with TWRP.
Click to expand...
Click to collapse
I was on stock, unlocked, rooted with TWRP. I ran the KRT16S OTA normally. TWRP installed it. I lost root and TWRP. Easy enough fix.
Sent from my Nexus 7 using Tapatalk 4

Lost root, tried reflashing the SU 1.43 binary in TWRP and still don't have root. Any advice?

nchopp said:
Lost root, tried reflashing the SU 1.43 binary in TWRP and still don't have root. Any advice?
Click to expand...
Click to collapse
This: http://autoroot.chainfire.eu/
You need to do this in fastboot. The instructions are at the bottom of the page

[Q]Anyone update VZW LG g2?

I'm rooted and was wondering if the new
VS98012B update was worth it and plus if it would get my phone to boot loop by getting this update since I'm rooted.
Sent from my VS980 4G using xda app-developers app

I used the LG Mobile Support tool while rooted because the update failed otherwise. After getting the update I no longer have root. I'm happy with this update, it added a few small things and corrected an issue with the touch screen behaving erratically. I haven't tried to re-root it and I haven't bothered with any custom recoveries since this update.

EnsoniqHT said:
I used the LG Mobile Support tool while rooted because the update failed otherwise. After getting the update I no longer have root. I'm happy with this update, it added a few small things and corrected an issue with the touch screen behaving erratically. I haven't tried to re-root it and I haven't bothered with any custom recoveries since this update.
Click to expand...
Click to collapse
So you just updated like that without your phone bootlooping or any malfunction?
Sent from my VS980 4G using xda app-developers app

It will fully update wiped. Like an out of the box device.

Steamer86 said:
It will fully update wiped. Like an out of the box device.
Click to expand...
Click to collapse
What do you mean?
Sent from my VS980 4G using xda app-developers app

wadamean said:
What do you mean?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
I was rooted - stock recovery took the B OTA and didn't loose root mine also didn't wipe. Ive checked and my Verizon g2 does indeed say it has the new B update on it.

12b and no custom recovery
if you are still on 11a, use ioroot to root your phone and then install a recovery afterwards.
if you update to 12b you can still root it, but for now you wont get a custom recovery to install.
that should change today or shortly i would guess, but if your gonna flash roms your better off doing it now in 11a and skipping 12b.
just a heads up and info share. enjoy

EnsoniqHT said:
I used the LG Mobile Support tool while rooted because the update failed otherwise. After getting the update I no longer have root. I'm happy with this update, it added a few small things and corrected an issue with the touch screen behaving erratically. I haven't tried to re-root it and I haven't bothered with any custom recoveries since this update.
Click to expand...
Click to collapse
Are their instructions on how to do this? I'm rooted and the update just keeps failing. Also, I have read that VooDoo does allow you to keep root.

Ferret1978 said:
I was rooted - stock recovery took the B OTA and didn't loose root mine also didn't wipe. Ive checked and my Verizon g2 does indeed say it has the new B update on it.
Click to expand...
Click to collapse
So your phone didn't get into any sort of boot loop or anything?
Sent from my VS980 4G using xda app-developers app

Ferret1978 said:
I was rooted - stock recovery took the B OTA and didn't loose root mine also didn't wipe. Ive checked and my Verizon g2 does indeed say it has the new B update on it.
Click to expand...
Click to collapse
Oh you had stock recovery? I have cwm
Sent from my VS980 4G using xda app-developers app

wyrdtrtle said:
if you are still on 11a, use ioroot to root your phone and then install a recovery afterwards.
if you update to 12b you can still root it, but for now you wont get a custom recovery to install.
that should change today or shortly i would guess, but if your gonna flash roms your better off doing it now in 11a and skipping 12b.
just a heads up and info share. enjoy
Click to expand...
Click to collapse
Well I don't flash roms at all. I just have my phone rooted to hack the games and get unlimited money. But I do have cwm and if I were to get the update I don't want to risk it getting my phone into any sort of glitch or boot loop
Sent from my VS980 4G using xda app-developers app

new update didnt mess with root?
EnsoniqHT said:
I used the LG Mobile Support tool while rooted because the update failed otherwise. After getting the update I no longer have root. I'm happy with this update, it added a few small things and corrected an issue with the touch screen behaving erratically. I haven't tried to re-root it and I haven't bothered with any custom recoveries since this update.
Click to expand...
Click to collapse
I've been wondering if i should accept the new update, thought i heard somewhere that it included a patch to relock the bootloader or something, & I'm planning on rooting mine (vs98011a). Sounds like its a worthwhile upgrade tho..my screen gets just a tiny bit glitchy sometimes. Guess I'll go ahead & take it then, thanx for the heads up. As long as i can root it still after I'm good...?

Boatloader had always been locked. There is just currently no working recovery/loki with the current update. If you plan on flashing/heavy modding, don't take it. You can still root.
Edit: Apparently, Freegee now works to flash recovery on 12B.

update/effect on bootloader vs980
Steamer86 said:
Boatloader had always been locked. There is just currently no working recovery/loki with the current update. If you plan on flashing/heavy modding, don't take it. You can still root.
Edit: Apparently, Freegee now works to flash recovery on 12B.
Click to expand...
Click to collapse
10-4, well thanx for the heads up bro. I ended taking the update & I'm glad i did cuz it fixed the screen glitch. I'm gonna root as soon as i can get to a decent computer. Idk anything about freegee....I'll have to look into it. Well hey, i appreciate the info man looks like i have some research to keep me busy for a min. Thanx again! Btw...I'm lovin this phone, its a totally underestimated beast. Any tips on a good rom aosp/stock would both be good to know about. Heard OSE had one for this phone maybe & i loved ose on my s3.

[Q] SD Card issue after OTA kitkat update

Hey everyone,
I've been having issue where I cant download anything directly to my SD card. It occured after the 4.4 update. I get messages of insufficient space or download failed. I cant download pic, pdfs or videos. The only way I can save to SD is downloading to the device then moving it with the file manager. Any ideas?
Ive formatting the card a few times already.
Thanks
Brian

brmagic said:
Hey everyone,
I've been having issue where I cant download anything directly to my SD card. It occured after the 4.4 update. I get messages of insufficient space or download failed. I cant download pic, pdfs or videos. The only way I can save to SD is downloading to the device then moving it with the file manager. Any ideas?
Ive formatting the card a few times already.
Thanks
Brian
Click to expand...
Click to collapse
Hey Brian! This is a known issue. A quick search in this 4.4 update discussion thread of the in the Q&A section of the forum should've given you the answer. There's also a flashable fix in the development forum.
*Remember to search first before asking :good:

Thank you Kevin,
I did search the forums beforehand. Unfortunately all I could find were fixes for Rooted S4's. I received the official OTA two days ago. Would you happen to know where I could find a solution for my unrooted device?
Any help would be great.
Thanks!

piss on sammys KK...lol.. wait till one of these devs hooks us up with a rom fixed....
im running negalite v6 myself.. like i have room to talk, however if your rooted id go to stockish v6 untill something is updated...
Sent from my SPH-L720 using xda app-developers app

brmagic said:
Thank you Kevin,
I did search the forums beforehand. Unfortunately all I could find were fixes for Rooted S4's. I received the official OTA two days ago. Would you happen to know where I could find a solution for my unrooted device?
Any help would be great.
Thanks!
Click to expand...
Click to collapse
Oh you're not rooted..well currently, I don't think there's any until Samsung realizes and pushes out a small update for the users not rooted.
You should root your device! Super simple process and a whole lot of benefits

brmagic said:
Thank you Kevin,
I did search the forums beforehand. Unfortunately all I could find were fixes for Rooted S4's. I received the official OTA two days ago. Would you happen to know where I could find a solution for my unrooted device?
Any help would be great.
Thanks!
Click to expand...
Click to collapse
It's not an issue, it is by design. Google wants you to use the cloud and not an sdcard to store data so they removed functionality of the sdcard with kit kat. Kind of like when they removed the ability to move apps to the sdcard after gingerbread. Hopefully Samsung will defy Google again and add functionality of the sdcard back in a future update like they did when they added the ability to move apps to the sdcard with mf9. But if you want to have it now you will need to root your phone.

Yeah that's tough not being rooted. I would be pissed a throwing a fit with Sprint. They've disabled a function of the phone. Seems like it could become a legal issue if the right people got involved.
All the more reason to root and live free.
Sent from my SPH-L720 using Tapatalk

Guys it's not a Smasung issue... It's GOOGLE that did it purposely. They are slowly trying to get rid of external SD cards for whatever reasons -__-

Joe0113 said:
Guys it's not a Smasung issue... It's GOOGLE that did it purposely. They are slowly trying to get rid of external SD cards for whatever reasons -__-
Click to expand...
Click to collapse
Reality is whoever is "at fault" ... you might as well sell me a 5 inch screen but only let me use 4 inches of it ... I purchased this phone because it has the sd card function. I might just call and complain to Sprint myself.
Sent from my SPH-L720 using Tapatalk

cmonsterf50 said:
Reality is whoever is "at fault" ... you might as well sell me a 5 inch screen but only let me use 4 inches of it ... I purchased this phone because it has the sd card function. I might just call and complain to Sprint myself.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Sprint has nothing to do with it. IT IS GOOGLE!!!!!!!!! How many times does it have to be spelled out for you. GOOGLE wants you to use the cloud not the device. They want you to pay high data rates to use your content. Calling Sprint will do nothing, if you want to complain, flood Google with complaints about eliminating sdcard writing with Kit Kat! Or root you damn phone and fix it yourself.

4.4.3 GPE update DO NOT UPDATE (edit:Fixed)

The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Edit:
To get the OTA to work properly and flash the correct kernal, your CID must be changed to GOOGL001. If you have the GPE device, you don't need to do anything, but if you have a converted GPE then you must change your CID if you want OTA's. This was not made clear in the RUU thread, it was mentioned that changing your CID was optional if you had one of the listed CID's, but it is not optional, but a requirement if you want the OTA's to work.
Everyone that has changed there CID's reflashed the OTA and everything flashed fine, whereas anybody that had not modified there CID had the problem with the kernal.

Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
maybe you had a bad download?

HRodMusic said:
maybe you had a bad download?
Click to expand...
Click to collapse
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.

Same results with OTA.
Sent from space.

Psosmith82 said:
I used the download linked from the discussion thread. Put on phone storage, rebooted into recovery and applied the update from phone storage.
Click to expand...
Click to collapse
Checked the MD5 before?

Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
Used the OTA provided by graffixnyc

Extremer2903 said:
Checked the MD5 before?
Click to expand...
Click to collapse
The signature verification wouldn't apply the update if it saw mismatches.

Archon810 said:
The signature verification wouldn't apply the update if it saw mismatches.
Click to expand...
Click to collapse
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?

graffixnyc said:
Odd.. I had no problems using the OTA zip.. Did you guys try wiping data?
Click to expand...
Click to collapse
I tried wiping data, still had the same problem. I am reflashing the RUU and will try the ota again. If it doesn't work after the 2nd try, i will just wait for google to send the OTA to me. Wiping data sucks, have to redo everything

Psosmith82 said:
The camera won't connect anymore, Wi-Fi won't turn on and the SD card wont mount. How did this get approved by google??
Click to expand...
Click to collapse
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?

willverduzco said:
I wonder if this is also being experienced by any other users or if this is specific to your software config and/or some glitch while writing the firmware. I assume you haven't yet tried wiping your /data partition, right?
Click to expand...
Click to collapse
I wiped data and still had problems. I'm working on starting over right now

Then problem should be wiped/not wiped, I think. Anyway, trying with this error stuff is always an excited challenge with me, try to deal with it like that to reduce percentage of throwing your devices away .

Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK

graffixnyc said:
Also you need to be FULLY stock.. that includes the stock kernel. If you are running a custom kernel some kernels flash libs and modules. EVERYTHING NEEDS TO BE STOCK
Click to expand...
Click to collapse
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID

Psosmith82 said:
Mine is fully stock. I have an unlocked HTC one, and i flashed the GPE conversion RUU. Does the CID need to be changed to the Google CID
Click to expand...
Click to collapse
that's a really good question Psosmith

Only thing I can think of on my example is I had 'CF.lumen' installed... Other than that, I had (your) completely stock GPE conversion.
Troubleshooting...
Sent from space.

Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured out the problem. I flashed the new RUU that graffix posted with 4.4.3. The Kernal in the OTA is not updating like it should, it stays on the kernal that was made in March. The new Kernal has a date of Thursday May 22nd. So for whatever reason, the OTA is not flashing the new Kernal, which is why all those things were broken. If you use the RUU update, it will flash the new kernal, and everything works as it should.
You'll know right off the bat at first boot. With the OTA, the boot animation hangs and it hangs on the home screen. With the RUU flash, everything is buttery smooth.

Something tells me this problem is occurring for people who actually have a retail M8 that they dirty-flashed using a GPE RUU.
Does anyone with an honest-to-God GPE that was purchased from Google have this problem? If so, this is huge.

Android The Greek said:
Is the problem from the update zip or ota+
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The update worked fine on my device and I used it for the conversion RUU. odd.. I used that very same OTA file. very odd...