I have an AT&T m7. It has S-off and an unlocked bootloader. Once Android 5 came out, I flashed the phone to GPE so I could get the OTA updates. I also prefer stock Android to Sense.
The phone is able to download the latest update: LMY47O.H6 (281.3MB) but fails to install. The phone reboots and I get the Android animation with a progress bar, but hits an error when it reaches about 25%. This has happened 4-5 times over the past couple of weeks.
Epos7 said:
but hits an error when it reaches about 25%.
Click to expand...
Click to collapse
And what is the error exactly?
alray said:
And what is the error exactly?
Click to expand...
Click to collapse
I have the same issue with my M7 (s-off, root, gpe). The error is that phone stops installing update, there's green android on its back with red triangle with exclamation mark in stomach It lasts for a minute and the phone restarts itself.
PatriotPL said:
I have the same issue with my M7 (s-off, root, gpe). The error is that phone stops installing update, there's green android on its back with red triangle with exclamation mark in stomach It lasts for a minute and the phone restarts itself.
Click to expand...
Click to collapse
To see what the error is exactly, you must hold volume up and hit power when in recovery so you can see the recovery menu and the error at the bottom of the screen when it is failing.
"Red triangle" can be caused by many things:
Not using the correct recovery
Corrupted system files
Missing system files
Rom fingerprint mismatch
and more
We need to know what is the error exactly.
I've been trying other methods to get the update and I think the error is this: a message about some fingerprints that should be "htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys" or "htc/m7_google/m7:5.1/LMY470.H6/536258:user/release-keys" and mine is "htc/cm_m7/m7:4.4.2/KVT49L/3f6e6e21ab:eng/test-keys". What can I do to install the update?
PatriotPL said:
I've been trying other methods to get the update and I think the error is this: a message about some fingerprints that should be "htc/m7_google/m7:5.0.1/LRX22C.H3/434277:user/release-keys" or "htc/m7_google/m7:5.1/LMY470.H6/536258:user/release-keys" and mine is "htc/cm_m7/m7:4.4.2/KVT49L/3f6e6e21ab:eng/test-keys". What can I do to install the update?
Click to expand...
Click to collapse
looks like you don't have to correct recovery installed, try to flash 5.0.1 or the 5.1 GPE stock recovery posted here
5.11.1700.3
or
6.04.1700.6
Hm, that's strange... In Settings > Phone Info I have "Compilation Number" that says "LRX22C.H3 release-keys" (which is one of two mentioned above necessery to install update). In fastboot i have this:
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.30.3218.21
OpenDSP-v34.120.....
OS-5.11.1700.3
So it seems that I have the version you mentioned...
PatriotPL said:
Hm, that's strange... In Settings > Phone Info I have "Compilation Number" that says "LRX22C.H3 release-keys" (which is one of two mentioned above necessery to install update). In fastboot i have this:
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.30.3218.21
OpenDSP-v34.120.....
OS-5.11.1700.3
So it seems that I have the version you mentioned...
Click to expand...
Click to collapse
so flash the 5.11.1700.3 stock recovery and try again
Ok, I flashed it and tried to go to recovery - and again there's the green bot with red triangle (I used both adb "adb reboot recovery" and power+volDown). Before I flashed that recovery you sent I had TWRP and it worked just fine (besides it didn't let me update to 5.1). Maybe you have another idea?
PatriotPL said:
Ok, I flashed it and tried to go to recovery - and again there's the green bot with red triangle (I used both adb "adb reboot recovery" and power+volDown). Before I flashed that recovery you sent I had TWRP and it worked just fine (besides it didn't let me update to 5.1). Maybe you have another idea?
Click to expand...
Click to collapse
You can't update when a custom recovery is installed. You can't neither initiate the update process yourself by booting in stock recovery. Now that the stock recovery is installed just boot in the OS, search for updates and let the phone reboot to recovery itself to install the update.
Stock recovery is installed, but why I can't boot into it? Anyway, I tried to search for the update through Settings but now it says that I am up-to-date (but I'm not - I still have 5.0.1). Is there any way to install the update manually?
Ok, I tried to install update with adb sideload, but I got this error: Installing update L50QCT.00.001.001; Verifying current system ; "/system/bin/app_process32" has unexpected contents. E:Error in sideload/package.zip (Status 7) And it stops. Any idea what can I do?
PatriotPL said:
I have the same issue with my M7 (s-off, root, gpe). The error is that phone stops installing update, there's green android on its back with red triangle with exclamation mark in stomach It lasts for a minute and the phone restarts itself.
Click to expand...
Click to collapse
This is the error I have. I also can't load recovery, getting the same error.
Hello developers,
pls help me to Get ride of this
I got this while Updating automatically from settings....which i got update notification
i tried to Flash stock/factory image, due to Unallow OEM unlock, i cudnt go further
Fone is LOCKED,STOCK ROM,NOT EVEN ROOTED, DEVELOPER OPTIONS OFF
i tried to update Android N via ADB SIDELOAD..............its not even detecting the zip file
it says... " Loading ..zip file " and get stuck PC
after few min, " installation aborted" displays in fone
i donno what to do .......pls help me
any way to solve this
thanks
If you can still get into recovery, download the latest OTA zip from Google's developer page, copy it to your internal storage, and flash it using the recovery. It will wipe your device storage, but at least your device will function again.
Hey guys, My phone has been bootlooping for about a few weeks now. I gave up on it thinking it was bricked, and also since i had a spare phone. Well that spare phone is no longer functional, and I need a device for work/school.
What happened was that I put the phone on the charger, and went to check on it. It was at about 60% battery life, I unplugged it, tried to unlock the screen and it crashed, went into boot loop for a while and said something along the lines as there was a problem with the OS or something?
So I tried hard resetting it via hardware buttons, and no luck. Now it just boot loops, goes from android one logo to Nokia. Stay on Nokia logo as if it's booting normally and the screen turns of and it boot loops again.
Is there anyway I could reflash the device? It's relative new so I doubt it would be a hardware issue and it was fine before?
However, and this might not be relevant, but a couple months ago i started getting modem ram dump popping up randomly on the screen, and it would restart the modem and it would be fine. Could this be the cause of my errors?
If it is a hardware issue, I'm in CA, would I be able to take it to a shop and have it fixed?
Thanks in advance!
try factory reset in recovery menu: hold power to powerdown, hold power + volume up some sec, aftet show no command with android logo on black screen, press short power + volup to show menu
k3dar7 said:
try factory reset in recovery menu: hold power to powerdown, hold power + volume up some sec, aftet show no command with android logo on black screen, press short power + volup to show menu
Click to expand...
Click to collapse
I've factory reset multiple times through recovery mode, still bootloops. Is reflashing the best option? How would I go about doing that?
zackman558 said:
I've factory reset multiple times through recovery mode, still bootloops. Is reflashing the best option? How would I go about doing that?
Click to expand...
Click to collapse
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
cristi.blidariu said:
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
Click to expand...
Click to collapse
Oh, that seems like a really solid idea! I think I had the June security Patch when these issue arised, so I should try to install July?
And that's installing it by going into recovery mode and selecting install update from SD card, correct?
cristi.blidariu said:
hi,you can try to update using a micro sd card or by using adb sideload command,you have to update with a new security patch that was in your phone,for example if you have june security patch then update with july patch,give a try as it might work,here you can find all the update
Click to expand...
Click to collapse
Hi! So I tried updating from SD using the OTA july 2019 file, and it started installing got to step 1/2 and then rebooted back to the android robot no command screen! What does this mean?
zackman558 said:
Hi! So I tried updating from SD using the OTA july 2019 file, and it started installing got to step 1/2 and then rebooted back to the android robot no command screen! What does this mean?
Click to expand...
Click to collapse
UPDATE!
I tried using june, and it wouldn't work since it's june so that made sense.
When I tried July this most recent time, it gave me the following error code:
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode : : kDownloadStateInitializationError)
E:Error in /sideload/package.zip (status 1)
Installation aborted.
What do i do now? I'm thinking of redownloading the July update and trying again
zackman558 said:
UPDATE!
I tried using june, and it wouldn't work since it's june so that made sense.
When I tried July this most recent time, it gave me the following error code:
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode : : kDownloadStateInitializationError)
E:Error in /sideload/package.zip (status 1)
Installation aborted.
What do i do now? I'm thinking of redownloading the July update and trying again
Click to expand...
Click to collapse
Try to sideload using adb sideload command
cristi.blidariu said:
Try to sideload using adb sideload command
Click to expand...
Click to collapse
I'm downloading android studio rn, how would I go about sideloading via adb? I know how to get to the adb from recovery but on the computer end what do I do. Thanks for the help so far
zackman558 said:
I'm downloading android studio rn, how would I go about sideloading via adb? I know how to get to the adb from recovery but on the computer end what do I do. Thanks for the help so far
Click to expand...
Click to collapse
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
UPDATE!
Tried to do it via adb, got it to get going. Got to 61 and then
adb: failed to read command: No error
What does this mean?
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
UPDATE!
Tried to do it via adb, got it to get going. Got to 61% and then
adb: failed to read command: No error
What does this mean?
zackman558 said:
Okay im using powershell rn, Got the .\adb devices to recognize the device and it says sideload
How do I get the file to sideload from here? I tried copy and pasting file name but nothing is found? I have the file saved to my desktop
Click to expand...
Click to collapse
Put the update file in the same folder where you have adb,then run adb sideload name of the file.zip and hit enter
zackman558 said:
UPDATE!
Tried to do it via adb, got it to get going. Got to 61% and then
adb: failed to read command: No error
What does this mean?
Click to expand...
Click to collapse
It either does this, or it fails to verify signature at 41%. Error 21
cristi.blidariu said:
Put the update file in the same folder where you have adb,then run adb sideload name of the file.zip and hit enter
Click to expand...
Click to collapse
Yes, I figured this much out but it won't complete past 61%. Recent attempts it gets to around 47%, and says signature verification failed.
Error 21
Installation aborted.
Why does this happen? Is there something wrong with the July file found on xda?
Is there a way of reflashing or something? Im confused as why it won't complete the install, only thing that i could think of is corrupted partition somehow.
zackman558 said:
Yes, I figured this much out but it won't complete past 61%. Recent attempts it gets to around 47%, and says signature verification failed.
Error 21
Installation aborted.
Why does this happen? Is there something wrong with the July file found on xda?
Is there a way of reflashing or something? Im confused as why it won't complete the install, only thing that i could think of is corrupted partition somehow.
Click to expand...
Click to collapse
I all so think that your sistem partition is corrupted,try again with August patch and see if is working,if not,then you need to take it to a service,or if is possible to unlock bootloader
cristi.blidariu said:
I all so think that your sistem partition is corrupted,try again with August patch and see if is working,if not,then you need to take it to a service,or if is possible to unlock bootloader
Click to expand...
Click to collapse
August didn't install yesterday, said something about how it needed July i think.
How would I go about unlocking bootloader? How can i check if it is already unlocked?
zackman558 said:
August didn't install yesterday, said something about how it needed July i think.
How would I go about unlocking bootloader? How can i check if it is already unlocked?
Click to expand...
Click to collapse
hi,you can all so try to downgrade aboot(bootloader) by flash an older security patch,try with december patch from 2018,as soon as you see abort error keep the phone in recovery,now download full firmware of march and try again to flash
ps/this method i have try on nokia 5,but it might all so work on nokia 7 plus i wish you best of luck
Sideloaded June OTA successfully. Now trying to flash custom boot img in bootloader and it says "Waiting on device" in CMD after running flash command and doesnt do anything on the Bootloader screen on phone. I have tried rebooting several times and I have the latest ADB and Fastboot.
Anyone else have this issue or know what to do? Thanks
chasehammer said:
Sideloaded June OTA successfully. Now trying to flash custom boot img in bootloader and it says "Waiting on device" in CMD after running flash command and doesnt do anything on the Bootloader screen on phone. I have tried rebooting several times and I have the latest ADB and Fastboot.
Anyone else have this issue or know what to do? Thanks
Click to expand...
Click to collapse
Just the usual.....try different cord and different port.
Tried that, it actually will not allow me to flash or sideload now since the OTA installed.
Flashing does nothing, when I tried to sideload the entire image zip it fails at 0% and says error: no message.
Does your SDK need to be updated now?
Hope it's not it's related. I just got my new phone(4a5g) last week, and already did ota to June. Have not unlocked it yet.