Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] GPE 4.4.3 Update Problems

OP critterhart

5th June 2014, 12:12 AM   |  #11  
Junior Member
Thanks Meter: 0
 
5 posts
Join Date:Joined: Dec 2013
Unhappy
Hey, i also updatet while having twrp, but my phone gut stuck,
so i followed instruction in these thread.

Okay, so I flashed google recoery from the link, but now i'm stuck.

How can i transfer the 4.4.3 update to my htc m7 phone storage, so I can apply it.

I managed to get to the a"pply from phone storage" menu.
Can you add some hints on how to transfer the zip file to the phone and where exactle to put it so the update wents through smoothly?

Seems I don't see my phone, while doing "adb devices".
I'm on windows 8, maybe that's the cause. Any Ideas?

Kind regards
Last edited by TomFader; 5th June 2014 at 12:19 AM. Reason: added some details
5th June 2014, 12:35 AM   |  #12  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Jun 2014
Thank you for the instructions, I have tried this, without any luck.

I can get to 4.4.3, but always with corrupted display.

I've tried;

Install 4.4.2 RUU via fastboot. (RUU from Link
Boot into Android.
Reboot to fastboot
Install recovery.img as listed in your post.
Reboot into Android.
Install OTA through Android.

This stuck me with the graphical errors (although the install went smoothly).

I then download the OTA file, placed it in downloads and ran it manually from the recovery menu.

I feel like I might be missing something obvious, but the process seems quite simple, and I've been on stock recovery for quite some time now (was able to OTA the 4.4.2 when it came out).

Anyways, thanks for your time and effort all the same, I think I'll just keep with 4.4.2 for now.



Quote:
Originally Posted by ericiidx

Thanks in advance! I'm in the same boat (M7 converted to GPE 4.4.2 with TWRP) and my screen has been on but blank for the past 5 minutes. I'll give it another 10, and if that fails, opt for the stock recovery.

As I was typing this, the launcher came up finally. I also had about 1/3 of my apps removed, and am getting graphical glitches. So, time for that stock recovery!

Oh, also, my power button won't turn the screen off.

---------- Post added at 04:24 PM ---------- Previous post was at 03:56 PM ----------



For this to work, you need S-OFF and an unlocked bootloader. It also stands that you are running GPE 4.4.2 (or have just updated to 4.4.3 and are having this problem.) This does not apply to any other ROM/RUU.

Download the latest GPE recovery from the first link; http://d-h.st/2F9. For ease of use, rename this file to recovery.img.

Also download the 4.4.3 OTA update from the second link. Put this on your phone's storage whenever you can.

Plug your phone into your computer via USB, open a command prompt, and type adb reboot bootloader

Once your phone reboots and you get your bootloader menu, type fastboot flash recovery recovery.img (it's the stock GPE recovery file you downloaded before.)

Reboot your phone.

Let the phone boot up, then type adb reboot bootloader again. Now, choose recovery to enter recovery. If you get any error (such as a KO'ed Android with a warning symbol above his head) hold VOL-UP and press the power button. You may need to do this multiple times. Your end goal is getting a menu, and you need to choose "apply from phone storage"

Find the 4.4.3 OTA file you downloaded before (the large ZIP file) and select it to install.

You should be done and good to go at this point.

I'd also like to add that TWRP was indeed to blame, as can be the case when OTAs come around. Using the GPE stock recovery got rid of the graphical glitches and slowdown. Now to just redownload the apps it decided to remove :P

5th June 2014, 03:49 AM   |  #13  
Member
Thanks Meter: 29
 
54 posts
Join Date:Joined: Dec 2012
Quote:
Originally Posted by brassm22

Thank you for the instructions, I have tried this, without any luck.

I can get to 4.4.3, but always with corrupted display.

I've tried;

Install 4.4.2 RUU via fastboot. (RUU from Link
Boot into Android.
Reboot to fastboot
Install recovery.img as listed in your post.
Reboot into Android.
Install OTA through Android.

This stuck me with the graphical errors (although the install went smoothly).

I then download the OTA file, placed it in downloads and ran it manually from the recovery menu.

I feel like I might be missing something obvious, but the process seems quite simple, and I've been on stock recovery for quite some time now (was able to OTA the 4.4.2 when it came out).

Anyways, thanks for your time and effort all the same, I think I'll just keep with 4.4.2 for now.

Sounds like you got it. I had to install the OTA via recovery because I had already updated the OS to 4.4.3, and wasn't interested in formatting/flashing down to 4.4.2 to redo the process. If you are still on 4.4.2, you could just install it via the natural OTA process in Android. I would just recommend being on stock recovery to avoid any glitches.

Quote:
Originally Posted by TomFader

Hey, i also updatet while having twrp, but my phone gut stuck,
so i followed instruction in these thread.

Okay, so I flashed google recoery from the link, but now i'm stuck.

How can i transfer the 4.4.3 update to my htc m7 phone storage, so I can apply it.

I managed to get to the a"pply from phone storage" menu.
Can you add some hints on how to transfer the zip file to the phone and where exactle to put it so the update wents through smoothly?

Seems I don't see my phone, while doing "adb devices".
I'm on windows 8, maybe that's the cause. Any Ideas?

Kind regards

Sure! While you are in the bootloader menu, your phone is in "fastboot mode" I suppose you could call it. It hasn't initiated the Windows driver at this point, so you are only connected to your phone as a dumb terminal. It will respond to fastboot commands only.

There is the command fastboot update <filename>, but I'm not sure if it would be appropriate for an OTA update. It sounds like it would be appropriate, but I'm not sure. I won't recommend it right now because I don't want you to possibly harm your device!
Last edited by ericiidx; 5th June 2014 at 03:57 AM.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes