Related
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .
Hello.
I need a help with my Honor 8, it's been bricked and I honestly don't know if there is much to do in my current situation.
So the phone has locked bootloader and stock recovery.
Fastboot always returns 'Command not allowed'
What exactly happened:
I was running Stock ROM, rooted, TWRP Recovery with unlocked bootloader.
An official OTA update popped-up on my phone, I was in a rush and I missclicked (don't even ask lol) and the update started installing, I knew I'm screwed.
So I was about to play with fastboot, but it always returned 'Command not allowed'.
And probably the worst mistake happened a few minutes ago (6:00 am trying to fix it half a sleep), I was reading some posts about the dload method, >>FASTFORWARD I installed an official update using the dload method and locked my bootloader by doing this.
QUICK SUMMARY:
So I'm stuck on a bootloop.
The 3 button combo works.
Stock Recovery works as well.
Fastboot does NOT work. (I tried flashing, unlocking, temp-booting.. but nothing)
adb always returns error:
Code:
device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is there ANYTHING I can do in my current situation? :crying:
Thanks in advance for any help.
Have a nice day.
Hello, as long as you have an official recovery, a proper BOOT.IMG and the dload method is working there is still a chance( i hope), the only thing you need to know is that if the firmware is the wrong for your phone it will deny it. It means that is if you try to install an android 6.0 based stock ROM over a 7.0 ROM , it will say software upgrade failed or something like that.
You need to know under which Android version you were and install the same or maybe a more recent one but not to far away from your actual ROM, try the next one. You can also try to downgrade USING a rollback package that you can download on honor official site. Make sure that's the the correct file for your phone.
Hope you'll make it bro, let me know how the situation evolve
(sorry for any language mistake, english isn't my native language.)
Rayan19997 said:
Hello, as long as you have an official recovery, a proper BOOT.IMG and the dload method is working there is still a chance( i hope), the only thing you need to know is that if the firmware is the wrong for your phone it will deny it. It means that is if you try to install an android 6.0 based stock ROM over a 7.0 ROM , it will say software upgrade failed or something like that.
You need to know under which Android version you were and install the same or maybe a more recent one but not to far away from your actual ROM, try the next one. You can also try to downgrade USING a rollback package that you can download on honor official site. Make sure that's the the correct file for your phone.
Hope you'll make it bro, let me know how the situation evolve
(sorry for any language mistake, english isn't my native language.)
Click to expand...
Click to collapse
Woohoo, after a few tries & factory resets I was able to boot my phone again using the dload method :victory: The TWRP recovery has vanished and it seems like there is no sign of root(?) either, I'm gonna redo everything again, thanks so much for your help, you saved me bro <3 Have a wonderful day.
I am really glad that you get your phone back on track ! And yh the dload method bring you to stock everything, stock recovery,stock system etc etc.
Have a nice day
crepnik said:
Woohoo, after a few tries & factory resets I was able to boot my phone again using the dload method :victory: The TWRP recovery has vanished and it seems like there is no sign of root(?) either, I'm gonna redo everything again, thanks so much for your help, you saved me bro <3 Have a wonderful day.
Click to expand...
Click to collapse
Hi Crepnik,
Even I am facing the same issue. Can you please tell me which ROM did you download.
My phone was update to Nougat EMUI 5.0
Thanks
[email protected] said:
Hi Crepnik,
Even I am facing the same issue. Can you please tell me which ROM did you download.
My phone was update to Nougat EMUI 5.0
Thanks
Click to expand...
Click to collapse
Try to flash the rollback package and then an EMUI 4.x ROM. They're both available on honor official site
Rayan19997 said:
Try to flash the rollback package and then an EMUI 4.x ROM. They're both available on honor official site
Click to expand...
Click to collapse
Hi Ryan,
Thank you so much for responding.
I could see two ROM in the official site http://www.hihonor.com/in/support/
HONOR 8 Firmware (FRD-L02, C675B130CUSTC675D002, India)
HONOR 8 Firmware (FRD-L02, Android 6.0, EMUI 4.1, C675B160, India Channel)
I tried with both the ROMs but no luck
I placed the update.APP file inside sdcard but the update stops at 5% showing that it has failed.
I also tried flashing the recovery.IMG in fastboot mode.
I have lost all the hopes in my new phone
In the rescue mode it says UNLOCKED.
Please guide me with some detailed steps.
Thanks
Flash the stock recovery of the ROM that was previously installed on your phone , then with dload method flash the rollback package downloaded from honor site , and finally flash one of the two ROM, it may resolve your issue because the phone won't accept a lower firmware without flashing the rollback package first. As long as you can use dload method it should be fine.
If it doesn't work try to flash boot.img , recovery.img, cust.img, vendor.img and system.img extracted from a clean firmware downloaded on honor official site
Let us know how the situation evolve
Hello! So I tried flashing a custom ROM to my friends Honor 8 after reading around a bit and such but it ultimately failed and now we're trying to get it back to the default ROM. We found a ROM download but it was for the version FRD-l09C900B120 which was running EMUI4.0 and Android 6.0. I also read that the "C" version he has doesn't receive any further updates, I'm failing to find anything on the correct "C" version anywhere. If anyone could guide me through the installation process for the correct and latest firmware it would be great!
On another note, the build in eRecovery doesn't seem to want to install the update package. It always fails pretty early on after connecting to WiFi, any fix for that would be great. Thanks!
Thanks for any help!
On which ROM was the custom ROM based? You should try to flash the rollback package with dload method and then flash B120 or another EMUI 4.X ROM with same method
Rayan19997 said:
On which ROM was the custom ROM based? You should try to flash the rollback package with dload method and then flash B120 or another EMUI 4.X ROM with same method
Click to expand...
Click to collapse
The custom ROM was Linageos 14.1, so it wasn't anything EMUI based.
I'm gonna try and manually flash the ROM from an update.app that we downloaded from the app Firmware Finder.
ZelafAry said:
Hello! So I tried flashing a custom ROM to my friends Honor 8 after reading around a bit and such but it ultimately failed and now we're trying to get it back to the default ROM. We found a ROM download but it was for the version FRD-l09C900B120 which was running EMUI4.0 and Android 6.0. I also read that the "C" version he has doesn't receive any further updates, I'm failing to find anything on the correct "C" version anywhere. If anyone could guide me through the installation process for the correct and latest firmware it would be great!
On another note, the build in eRecovery doesn't seem to want to install the update package. It always fails pretty early on after connecting to WiFi, any fix for that would be great. Thanks!
Thanks for any help!
Click to expand...
Click to collapse
You did not make any twrp backup??
You are on twrp recovery right now??
Which firmware number you were on before going to custom??
hassanjavaid8181 said:
You did not make any twrp backup??
You are on twrp recovery right now??
Which firmware number you were on before going to custom??
Click to expand...
Click to collapse
We did not make a twrp backup (In hindsight we should've....)
We don't have twrp on it right not but can be fixed if needed.
We were on the latest update available to the phone which should be latest today as well. (OTA)
Flashing it manually made the phone enter a bootloop. It didn't even start the firmware. Any suggestions?
EDIT: We got into Fastboot. What are our options?
Right now your best option in my opinion is to flash Boot.img, recovery.img,cust.img and system.img that you will extract from the UPDATE.APP of your CURRENT Rom. Then just try the dload method again and again, it may not accept the firmware you try to flash but in this case just try another, but not a lower one because you need the rollback package to do that
Rayan19997 said:
Right now your best option is to pray for USB debugging to be enabled and then unlock the bootloader if you didn't do it earlier. After that you should try to flash TWRP
Click to expand...
Click to collapse
What should we do after we've flashed TWRP? When I tried flashing LineageOS 14 it decided to fail the installation somehow and be at an endless boot animation. So I'd like to get the phone restored to EMUI5.0.
Sorry, what I said was garbage, I just edited my comment, you're so quick lol
Rayan19997 said:
Sorry, what I said was garbage, I just edited my comment, you're so quick lol
Click to expand...
Click to collapse
Well currently there's a broken firmware on it of FRD-L09C432B943... Or something like that.
I think at this point he's looking at getting a new phone all together.
No matter if the firmware inside isn't working properly, with fastboot you can manually flash each partition that is needed as long as USB debugging is enabled and bootloader unlocked. After flashing these cleans parts you can properly use the dload method , and if you get an error using dload method can you tell me which one is it? At least the device behavior.
I have to sleep, I'll be right back on the morning hope you'll make it this night , if don't , please be more specific and accurate when you describe the errors you faced, that way we will be more efficient when answering
Sorry for language mistakes, English isn't my native language :silly:
Rayan19997 said:
No matter if the firmware inside isn't working properly, with fastboot you can manually flash each partition that is needed as long as USB debugging is enabled and bootloader unlocked. After flashing these cleans parts you can properly use the dload method , and if you get an error using dload method can you tell me which one is it? At least the device behavior.
I have to sleep, I'll be right back on the morning hope you'll make it this night , if don't , please be more specific and accurate when you describe the errors you faced, that way we will be more efficient when answering
Sorry for language mistakes, English isn't my native language :silly:
Click to expand...
Click to collapse
Currently there's no working OS on it so I'm gonna see if I can find a firmware that I can flash. Do you have any idea where I can get one?
Yeah on honor official site: Hihonor
Or with firmware finder
ZelafAry said:
Currently there's no working OS on it so I'm gonna see if I can find a firmware that I can flash. Do you have any idea where I can get one?
Click to expand...
Click to collapse
If you need a full firmware then you should visit official honor site..
If you flash LineageOS on a phone without OS it won't work just because LineageOS patch the current installed System, if there is no system there is no way it will boot
hassanjavaid8181 said:
If you need a full firmware then you should visit official honor site..
Click to expand...
Click to collapse
I can't find any Honor 8 FRD-L09 downloads anywhere on the Huawei sites or Honor sites. They must've removed the downloads just like they did with the Honor 7..
Rayan19997 said:
If you flash LineageOS on a phone without OS it won't work just because LineageOS patch the current installed System, if there is no system there is no way it will boot
Click to expand...
Click to collapse
I get that now and I know how to proceed in the future.
On another note, I got a good UPDATE.APP available but it refuses to install using the dload method because the versions are different. Does anyone know which partition the USERDATA.img file goes to?
You don't have to flash each single partition but dude in my opinion it's better to flash the whole UPDATE.APP, just use the rollback package and flash a lower EMUI.
Another thing: I'm currently on honor official site and I can download firmwares, you're searching in the wrong place.
www.hihonor.com/fr/support/search-result/index.html?keywords=honor 8
Rayan19997 said:
You don't have to flash each single partition but dude in my opinion it's better to flash the whole UPDATE.APP, just use the rollback package and flash a lower EMUI.
Another thing: I'm currently on honor official site and I can download firmwares, you're searching in the wrong place.
www.hihonor.com/fr/support/search-result/index.html?keywords=honor 8
Click to expand...
Click to collapse
Thank you for that link, I downloaded it and flashed it, I couldn't find it on any other hihonor site but this French one had it.
Again, thank you, it worked flawlessly installing and it updated instantly. You saved me from a lot of worrying and anxiety about breaking my friends phone lol.
I'm really glad to read that dude
thanks for the firmware been looking for it for very long!
btw you just saved another honor 8
So I got an honor 6x that I can't do anything with. I can't flash any ROMs or firmware here's the weird part of it.
Its on some version of EMUI that I can't have the system update menu and it has a button for app twin. It says BLN-L24C567B366 as the model number. Speakers don't work. I can't play videos on it and I can't use the camera in any app.
Here's the really weird part:. If I wipe all partitions and try to flash a room it boots to the same EMUI firmware not the custom rom I can't do anything to change what the rom is. It's like it's stuck in that weird Frankenstein EMUI firmware that I don't even know how I got. I tried restoring anback up cause I formatted my data partition on accident causing it not to boot or something and the backup I restored was not the backup that I made . The backup I made was a stock backup onto an SD card. When I restore it it's rooted and has some downloaded apps on it. And a different launcher. Not what I backed up originally.
I'm at a loss here. What do I do? Ihave full access to adb to flash with fastboot and can get into twrp or stock recovery. No ROMs I flash will work. In twrp it says it was successful. Ut when I boot it doesn't boot to that room, it boots to the weird emui os I can't get rid of.
Has anyone run into this issue or know how to fix it?
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
All my update.app files get stuck at 5% too. And I know honor/Huawei won't repair it cause the warranty is void or if they can they would charge you.
Honestly get the Moto G5s plus. Get the unlocked version at best buy if you're in the states. It's 239 for the 32gb/3gb. Ram model and 299 for 64gb and 4gb. Best budget phone you can get and dual cameras. The ROM support isn't as big as the honor but it is easy to unlock the bootloader and do things. My only ROM issue I've had with this was trying to update magisk the phone had to reboot to install and after that, I had a lock screen set up btw, when I went to enter the pin the screen would go black, the phone would buzz, and go back to the lock screen. And I tried restoring a backup I made but the phone wouldn't boot stuck at the boot logo before the animation.
But the stock firmware I acquired on XDA along with the steps to flash in adb every file in the stock firmware fixed it with no problems at all so at least there's an easy way to restore the stock firmware for my new phone. It's way better than the honor 6x
Seriously tho check out the Moto G5s plus. Out of the box it has Android 7.1.1 mostly stock without all of Google's bloatware. Front mounted fingerprint sensor that you can you for the home, recent apps and back button, and can lock the screen with it if you have fingerprint set up and activate the Google assistant. It also has a notification light that you need root to use. But it has this cool "always on display" type thing that shows a clock and notifications when you move the phone or get a notification. It isn't an AMOLED display tho. It's. 1920x1080p one. Ips good viewing angles. Honestly this is the best phone I've ever used. And it has a Motorola turbocharger in the box. It's really worth it
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
i think it could be an issue with the kernel cause the eliteRom has a custom kernel in it.. i have the update.app file for the BLN-L24C567B366 ad B365 files that i can extract and give you all the images that they have and maybe try to get the stock kernel somehow that might help?
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
Try flashing every single update version until one of them works. Once youve found one that works follow this guide: https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
xinoxkai said:
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
Click to expand...
Click to collapse
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
xSpartacusx said:
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
Click to expand...
Click to collapse
Yes, firmware finder showed me 3 zips, update.zip, update_data_full_public.zip and update_full_BLN-L24_hw_usa.zip, the later 2 are the "alternative zips". Just TWRP flash them.
Also, update_full_BLN-L24_hw_usa.zip might throw an error when flashing it, don't worry, by the stage it fails in its script it already did what it was expected to do and you will not have further problems.
do i need the stock recovery flashed in order to do dload?
well i followed the first half of your guide and it successfully "updated" but my storage is encrypted
xSpartacusx said:
do i need the stock recovery flashed in order to do dload?
Click to expand...
Click to collapse
Not really, I did it when I had TWRP installed
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
xSpartacusx said:
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
Click to expand...
Click to collapse
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
xinoxkai said:
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
RedSkull23 said:
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
xinoxkai said:
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
Click to expand...
Click to collapse
Good one dude, maybe FF proxy method could help xSpartacusx to solve his issue too!
Hey folks,
I just got the notification for a system update. TW Model, currently in Germany. However, I tried capturing the ota link for patching the boot.img, but it gives me an error. Anyone with more luck than me?
Greetings
Update:
I managed to get the OTA.zip off my phone, but the update itself fails at 24%. Restored stock boot.img before of course. Has someone already installed it?
Hong Kong variant still on 1.24.400.03, December 2017 security update [emoji23][emoji23][emoji23]
Sent from my HTC U11 plus using Tapatalk
September 2018 security on latest 1.24.709.93... Can't remember before that... And I couldn't spot any difference between the two, does anybody see anything new?
Inviato dal mio HTC_2Q4D100 utilizzando Tapatalk
I've got it too on my TW model in the Netherlands.
Besides the security patch going from June 1 to September 1 I don't see anything different yet. Then again, there weren't any bugs I'm aware of, that needed fixing. 700MB+ seems like a lot for 3 months of security patches though.
It's nice to get an update and be less behind in security patch date again.
Thanks, HTC!
U11+ from Europe...
Didn't get the june security patch, didn't get this one either...
Tw version in Malaysia. Already updated. Everything okay. Doesn't explore much because going to work. only feel different at the display color. Looked better
UK version, no update available so far and still on 1 December 2017 security patch. I'd settle for them fixing the notification issue.
Sent from my HTC U11 plus using Tapatalk
Some findings
Battery before i go to work, 75%, on airplane mode.
Come back home after 11 hours, 75%
Soooo happy.....
Hmm.... maybe I need to learn how to roll back to stock now
Received today in Belgium with TW version of the phone!
gortys said:
Received today in Belgium with TW version of the phone!
Click to expand...
Click to collapse
Very important question:
Where/in which precise folder is the OTA update saved in HTC U11+ after downloading (I cannot find it...)
Thx a lot!
marusia7 said:
Very important question:
Where/in which precise folder is the OTA update saved in HTC U11+ after downloading (I cannot find it...)
Thx a lot!
Click to expand...
Click to collapse
Ow, sorry, I don't know at all!
gortys said:
Ow, sorry, I don't know at all!
Click to expand...
Click to collapse
found it in root folder:
data/data/com.htc.updater/files/
lillypad_33 said:
Hmm.... maybe I need to learn how to roll back to stock now
Click to expand...
Click to collapse
did you manage to update?
same situation here: although I flashed back to original boot.img (included in the last OTA update end of July 2018 which was later patched by Magisk), the update stucks at 24% with red error. Luckily the phone boots normally without applied update.
Anybody any idea how to proceed? I already tried to flash back the original boot.img from the stock RUU and also to use the boot.img provided in the latest OTA: with both boot.img (although both have very same size) the phone stucks at HTC logo but does not continue to boot.
Currently the HTC U11+ boots only from the boot.img provided with 709.8 OTA, (also booting with the patched_boot.img done by Magisk derived from the same).
I am a bit stuck here: Magisk should not touch the system (so no idea why the OTA stops at 24%) and only 1 out of 3 boot images are working (although all with same size), so currently I am not able to apply the OTA update...
I have read that for OTA updates the integrity (?) of the recovery.img is important ( (although Magisk should also not touch the recovery.img (?)
Any ideas?
best regards, Marusia
Looks like htc forgot people are still buying their phones outside Taiwan, or they don't have enough money to hire a translator!! I am an old loyal customer for 8 years, but here they are doing everything to let us get another brand, it's like they stabbed themselves and slowly turning the knife to feel more pain
marusia7 said:
did you manage to update?
same situation here: although I flashed back to original boot.img (included in the last OTA update end of July 2018 which was later patched by Magisk), the update stucks at 24% with red error. Luckily the phone boots normally without applied update.
Anybody any idea how to proceed? I already tried to flash back the original boot.img from the stock RUU and also to use the boot.img provided in the latest OTA: with both boot.img (although both have very same size) the phone stucks at HTC logo but does not continue to boot.
Currently the HTC U11+ boots only from the boot.img provided with 709.8 OTA, (also booting with the patched_boot.img done by Magisk derived from the same).
I am a bit stuck here: Magisk should not touch the system (so no idea why the OTA stops at 24%) and only 1 out of 3 boot images are working (although all with same size), so currently I am not able to apply the OTA update...
I have read that for OTA updates the integrity (?) of the recovery.img is important ( (although Magisk should also not touch the recovery.img (?)
Any ideas?
best regards, Marusia
Click to expand...
Click to collapse
I also flashed the recovery.img from the latest OTA, but still the red triangle.
Is it possible to flash the whole OTA via fastboot? Maybe thats a possibility.
metaxuss said:
I also flashed the recovery.img from the latest OTA, but still the red triangle.
Is it possible to flash the whole OTA via fastboot? Maybe thats a possibility.
Click to expand...
Click to collapse
I also flashed latest OTA recovery,same result...
I guess the only way is to flash back to stock RUU (which will lead to unrooted phone), install latest OTA via WLAN, then unlock bootloader (via HTCdev website) and root again with Magisk. I never did RUU flashing, so currently backing up everything with Titanium, if I proceed I will let you know the result...
Flashing the latest OTA might brick the phone (the red triangle already indicates that something went seriously wrong, although I have no clue what it could be: never touched the system, Magisk only patches the boot.img), instructions should be in the forum.
Tried another thing: disabling the systemless Xposed (installed via Magisk), reboot, restoring boot.img via Magisk, OTA download & trying to install --> red triangle...
I cannot remember if I disabled Xposed before the last OTA update few months ago. I had there some issues too (after successful OTA install the phone stuck at boot so I had to reflash the OTA-boot.img again via fastboot), maybe this procedure broke the possibility to install current OTA.
Will maybe try to flash selectively restored stock RUU images (without applying first the whole stock RUU) on the weekend (I have been informed by PM that this procedure should be harmless), so reverting to whole stock RUU is still not the last option.
I downloaded OTA from the following link and flash "system.img" with fastboot command. I am now on 1.24.709.93
https://drive.google.com/drive/folders/1wccnIY0NaoelhZQS4uhgP8ZGIn1iXhNX
Link Credit to : nene bear
kenosis said:
I downloaded OTA from the following link and flash "system.img" with fastboot command. I am now on 1.24.709.93
https://drive.google.com/drive/folders/1wccnIY0NaoelhZQS4uhgP8ZGIn1iXhNX
Link Credit to : nene bear
Click to expand...
Click to collapse
These OTA files dont contain system.img (the system.img file should be >4Gb).
1) Did you experience also OTA update issue (red triangle) as described in this thread?
2) Just to clarify: you flashed 1st the system.img derived from the stock RUU and afterwards applied the 709.93 OTA update?