I'll try and keep this short and to the point. If you unlocked your bootloader and flashed TWRP and SuperSU, theirs a Good chance your phone will not return to stock and take OTA updates. Many of us have tried but for some reason the updates just fail.
Well we are lucky and someone captured and posted the 3 known updates and I'm going to show you how to flash them
New ~ All in One ~ update Instructions in Post 2
We now have a new way to do this, So the information below is just for information sake So bare with me while I get the Guide updated...
Other Files you may need
H1611.TWRP.New.img <<- This is the New Twrp by yuweng I Highly recommend everyone use this Version
minimal_adb_fastboot_v1.4.1_setup.exe
Huawei_Android_phone_drivers(1).rar
I have been working on this for some time and I now have an ALL in One Flash solution
This will allow you to flash a Single Rom to Update or Downgrade your firmware and Rom
As with any firmware update or downgrade I'm not responsible to what happens to your phone you do this at your own risk
(rest assured I have tested all these files and my phone is fine)
The Flash instructions are the same as any rom flash on this phone
Step one is to Boot to the bootloader and boot H1611.TWRP.New.img
fastboot boot H1611.TWRP.New.img
Swipe to allow modifications to System
then choose Mount and check system and cust
Select Storage Micro SDcard
Next is install and choose your Bxxx_Full_Update.zip
Swipe to flash
Reboot
That's really all their is too it, Just choose the File below that you want to update or downgrade too
Note: The phone always loads the AT&T logo and reboots the first time and then loads normally
First boot will take you to the setup screen if you formatted data
Another thing i noticed while test flashing these files is that the Data partition becomes Encrypted after the flash
This means before you can restore a data backup or flash a Rom like CleanRom (it includes data) you'll need to Format Data to UN-encrypt it
Also some roms may need to have SuperSU flashed after the Rom or the phone may not boot the first time after the upgrade.
AS Always make a complete backup of your phone before you start any flashing
Downloads
~New~ B180_Full_Update.zip
Note about B180 - If you have no wifi or the phone won't boot simply extract the boot.img from the rom and flash it with TWRP (Install Image) or fastboot (fastboot flash boot boot.img) also the AT&T Logo is missing for now but everything else works
Thanks To @madvane20 Download >> B170 Stock Full Update with Firmware
B160_Full_Update.v2.zip
B150_Full_Update.zip
I had to make B140 into 2 flashes but it works the same just copy both files to your phone and Flash A then B
B140_Full_Update.A.zip
B140_Full_Update.B.zip
B130_Full_Update.zip
Huge thanks to @madvane20 for helping with the partition layouts and testing and to @worstenbrood for the Huawei Update Extractor tool
Where do I start if I have B140 rooted on my XT? Maybe some numbers or section titles would help answer that. Thanks .
divineBliss said:
Where do I start if I have B140 rooted on my XT? Maybe some numbers or section titles would help answer that. Thanks .
Click to expand...
Click to collapse
You start at the 2nd half of the updated guide B140 to B150
the process is the same no matter what version your on
So I should start with B130 stock files even though I'm in B140 rooted right now?
clsA said:
You still start at the top and substitute the B150 files where their needed
the process is the same no matter what version your on
Click to expand...
Click to collapse
divineBliss said:
So I should start with B130 stock files even though I'm in B140 rooted right now?
Click to expand...
Click to collapse
... no you would start at returning your phone to Stock B140 and continue from their
flashing the B150 firmware then the B150 stock system and /cust
We have the B150 files and the guide is updated
If I can get back to B140 stock and take the B150 OTA, which files do you need?
clsA said:
The guide is not complete ... no you would start at returning your phone to Stock B140 and continue from their
flashing the B150 firmware then the B150 stock system and /cust
We don't have the B150 files yet so it's hard to complete the guide
Click to expand...
Click to collapse
divineBliss said:
If I can get back to B140 stock and take the B150 OTA, which files do you need?
Click to expand...
Click to collapse
is that a trick question ? if you could get back to stock and take the OTA this post wouldn't be necessary now would it ?
The whole point of the thread is that no one who rooted has been able to return to stock and take an OTA
Why bother updating? Isn't someone working in Lineage for this phone?
guest_2011 said:
Why bother updating? Isn't someone working in Lineage for this phone?
Click to expand...
Click to collapse
no one has posted any threads about it
you should still try and be on the latest security patch while you phone is stock
@RN_ReFlux Thank You ! for getting the B150 backup and /cust.img
guest_2011 said:
Why bother updating? Isn't someone working in Lineage for this phone?
Click to expand...
Click to collapse
Yes, someone is working on it but it is best to have your ROM up to date. You may not see a need for it but a lot of others see a need.
clsA said:
@RN_ReFlux any luck getting the B150 backup and /cust.img ?
Click to expand...
Click to collapse
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
RN_ReFlux said:
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
Click to expand...
Click to collapse
Thanks ... I'll post the files to my AFH account if you can share them through google or dropbox ..etc
If you request developer access, it doesn't take that long to get it ........ a few hour maybe if I recall correctly .
RN_ReFlux said:
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
Click to expand...
Click to collapse
divineBliss said:
If you request developer access, it doesn't take that long to get it ........ a few hour maybe if I recall correctly .
Click to expand...
Click to collapse
Requested it about 12 hours ago
Uploading to drive now.
Sent from my SM-T530 using Tapatalk
divineBliss said:
...
Click to expand...
Click to collapse
All the files are uploaded for your B140 to B150 update...
I'll be updating the guide soon.
The steps in a nutshell are
flash your stock B140 system/boot/recovery and stock b140 /cust
force flash the dload/update.app for b150 with the dialer code
boot TWRP restore stock B150 system and dd the B150 /cust
Flash SuperSU and Factory Reset (< optional)
reboot system and it boots to a clean B150
Click to expand...
Click to collapse
Guide is updated !
Has anyone been able to follow the OP to get up to B150 from either B140 or B130? Or even B130 to B140? Thanks!
clsA said:
All the files are uploaded for your B140 to B150 update...
I'll be updating the guide soon.
The steps in a nutshell are
Guide is updated !
Click to expand...
Click to collapse
divineBliss said:
Has anyone been able to follow the OP to get up to B150 from either B140 or B130? Or even B130 to B140? Thanks!
Click to expand...
Click to collapse
Yeah me
Sent from my Nexus 6P using Tapatalk
Be careful upgrading from B130 to B140. Went from stock non-rooted B130 to B140 using the SD card update method and hidden menu. While it went through the update process without reporting an error but after auto reboot it still showed the same version but lost WIFI functionality, mac address showed mostly 00s and can't restore full backup from TWRP without errors on /data, etc.
Anyone know if there are .img equivalent of 2017-01-26-H1611.B130.stock.complete to attempt restore from either fastboot flash or dd?
Related
Hi everyone,
I've recently messed up terribly on the Canadian model of this phone. The model # is KII-L05 and the problem is that I'm stuck on the logo screen when booting.
I was unable to flash a custom ROM properly and have no backups. I have TWRP 3.1.1-0 installed and have tried flashing cm12.1, cm-13.0, lineage-13.0 and lineage-14.1 with the proper gapps to no success. I also tried eRecovery (with a lot of trouble getting to it using the Vol+/- because it loads TWRP 99% of the time) but it won't detect the dload/UPDATE.APP that I acquired from the Canadian Huawei support site nor will it update via wifi.
I've run out of ideas so I'd appreciate some assistance in finding a solution either getting back to stock ROM(firmware?) or a custom ROM that supports this model.
If there's already an answer posted, please pass along the link as I've come up with nothing searching and following most of what's been said before.
Thanks,
You just have an option to restore the backup if someone can share it.
shashank1320 said:
You just have an option to restore the backup if someone can share it.
Click to expand...
Click to collapse
I was hoping it wouldn't have to come to that...
For clarity, would that be using TWRP to restore the backup or using the eRecovery/UPDATE.APP method?
I'll try my luck in the file repository to see if anyone has it.
Dominic987 said:
I was hoping it wouldn't have to come to that...
For clarity, would that be using TWRP to restore the backup or using the eRecovery/UPDATE.APP method?
I'll try my luck in the file repository to see if anyone has it.
Click to expand...
Click to collapse
you should try both.
TWRP backup and dload method. any of them could work
Dominic987 said:
I was hoping it wouldn't have to come to that...
For clarity, would that be using TWRP to restore the backup or using the eRecovery/UPDATE.APP method?
I'll try my luck in the file repository to see if anyone has it.
Click to expand...
Click to collapse
Extract your update.app using a program like 7zip -- it should contain a boot.img file. Use the ADB method to manually flash the file.
While your at it, if there is a system.img file -- flash that as well.
bb709394 said:
Extract your update.app using a program like 7zip -- it should contain a boot.img file. Use the ADB method to manually flash the file.
While your at it, if there is a system.img file -- flash that as well.
Click to expand...
Click to collapse
It may not work and dload will be best option here.
Fastboot may not allow him anymore to flash anything
bb709394 said:
Extract your update.app using a program like 7zip -- it should contain a boot.img file. Use the ADB method to manually flash the file.
While your at it, if there is a system.img file -- flash that as well.
Click to expand...
Click to collapse
shashank1320 said:
It may not work and dload will be best option here.
Fastboot may not allow him anymore to flash anything
Click to expand...
Click to collapse
Your suggestions are noted.
I'll try my luck at waiting a while longer for someone with a backup until I go flashing more things.
Did you try flashing stock recovery then flashing via dload?
hassanjavaid8181 said:
Did you try flashing stock recovery then flashing via dload?
Click to expand...
Click to collapse
I mentioned in my original post that I have no backups. Unfortunately, that includes me not having stock recovery to start from scratch.
My current eRecovery doesn't recognize anything I put into dload nor does it update via wifi.
I'm currently outreaching to Huawei Canada (been more than a few days without a response) as well as friends/coworkers that may have the phone that can help with no success.
Dominic987 said:
I mentioned in my original post that I have no backups. Unfortunately, that includes me not having stock recovery to start from scratch.
My current eRecovery doesn't recognize anything I put into dload nor does it update via wifi.
I'm currently outreaching to Huawei Canada (been more than a few days without a response) as well as friends/coworkers that may have the phone that can help with no success.
Click to expand...
Click to collapse
do you have orignal firmware file for your phone?if not download it from huawei website acoording to you model number
hassanjavaid8181 said:
do you have orignal firmware file for your phone?if not download it from huawei website acoording to you model number
Click to expand...
Click to collapse
Dominic987 said:
... it won't detect the dload/UPDATE.APP that I acquired from the Canadian Huawei support site nor will it update via wifi. ...
Click to expand...
Click to collapse
No backups, that includes anywhere internal or external of the phone in question. Already tried the Huawei site and they have Marshmallow - I suspect I need anything older that's on Lollipop.
Dominic987 said:
No backups, that includes anywhere internal or external of the phone in question. Already tried the Huawei site and they have Marshmallow - I suspect I need anything older that's on Lollipop.
Click to expand...
Click to collapse
Unfortunately there are no official firmware yet for this mate. I tried looking for you but couldn't get any. Its just OTA and not full firmware that could help you with dload.
Dominic987 said:
No backups, that includes anywhere internal or external of the phone in question. Already tried the Huawei site and they have Marshmallow - I suspect I need anything older that's on Lollipop.
Click to expand...
Click to collapse
May be last option is to take it to Huawei service center they will fix it for you.
OTA zip (Qualcomm) retail 3.3.2018 "Blur_Version.26.11.27.owens.retail.en.US"
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
Thanks, @Chad The Pathfinder. Good to see you here.
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
shezzy83 said:
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
Click to expand...
Click to collapse
It is for the retail XT1775 only. It's an official OTA update.
---------- Post added at 06:21 PM ---------- Previous post was at 05:40 PM ----------
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
I can probably make this work to flash with TWRP, but you'll need to have your system, oem and boot.img original stock before flashing. If anyone is willing to test it for me, I will modify the ota zip when I have a chance. I have the Boost XT1766 so I can't test it myself. Let me know if anyone is willing to test it because if not, I won't waste my time modifying the ota.
Sent from my Moto E (4) Plus using XDA Labs
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Chad The Pathfinder said:
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Click to expand...
Click to collapse
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Chad The Pathfinder said:
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Click to expand...
Click to collapse
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Chad The Pathfinder said:
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Click to expand...
Click to collapse
I'm uploading the ROM now. I just got done modifying the ota zip and I'll give you links as soon as they're done uploading. I made a deodexed Sprint variant version. Was planning on deodexing the retail version also. I may as well wait for the newer version though. The trick is, you need to deodexed the oem apps and framework also or it won't boot.
Sent from my Moto E (4) Plus using XDA Labs
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Chad The Pathfinder said:
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Click to expand...
Click to collapse
Yes. It'll be a little while, uploads are going really slow and keep failing on AFH. I had it almost uploaded twice and it keeps failing.
Sent from my Moto E (4) Plus using XDA Labs
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
I have been having issues uploading to AFH too. Man, I wish they would finally get this fixed.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
Finally got it
ROM: https://www.androidfilehost.com/?fid=746010030569959248
OTA:
So, here's what I want you to do.
1. Make a backup before you do anything.
2. Flash a Magisk uninstaller.
3. Flash the ROM. (if it should fail to flash, please get a recovery log so I can see exactly what failed.)
4. Flash the OTA zip. (again, if it should fail to flash, please get a recovery log so I can see exactly what failed.)
5. If everything flashes ok, reboot recovery to make sure you don't lose twrp.
6. Make a system backup.
7. Use fastboot to pull the boot.img, modem.img, fsg.mbn, and the oem.img.
Edit: actually, if you could pull everything you see in a stock firmware package and pull them so they have the same name and file extension, that would be great.
I'll be working until about 8 tonight. (3.5.18) I'll work on it tonight and let you know what happens.
Edit: I managed to get the "Blur_Version.26.11.27.owens.retail.en.US--XT1775_TWRP_flashable" down loaded but the other was taking too long and failed a couple of times. I will try again when I can.
so glad you guys are working on this My daughter and her moms xt1775 just popped the update message and im not "allowed" to work on them too often so i cant experiment with you. So a twrp flashable update would be great if i dont have to unroot reroot stock.img etc etc it will be a painless (for me) update.
A Sort-of Related Question
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
koop1955 said:
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
Click to expand...
Click to collapse
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Of course, sent to you via PM.
I don't think that it is a quality of your zip, I think it is related to my earlier attempt at installing the OTA itself.
Just whant to share dd backup I did who are test and working for at least BND-L21.
dd rip of official OTA 8.0.0.330.
If someone have need.
Cust.img : https://mega.nz/#!q9tn2C6T!JMMSDYN5qc4BQrmKwtjifGqg26Je8SjiToPBM7wktp4
Kernel.img : https://mega.nz/#!Kg8AADgJ!PmBFU4vM1nTvcJnT-AttXBvV7IIh93xdEPgSY9kE0BE
Product.img : https://mega.nz/#!zk8glLyJ!HIKFQoEMuShRYYvm3SWeIfmpLa3LrOI_ahpJ2PDFQXc
Ramdisk.img : https://mega.nz/#!WokUmYZJ!zusLmvamHNUfEVkzn-oEg3rescsnuPG29iRUlQM3E8M
Vendor.img : https://mega.nz/#!H5VnUJxZ!rSI4rg2Hy-cNn9-I1-dMt2y0MHq45ypu2MqL_OP7SZY
Version.img : https://mega.nz/#!q0d2ASiK!20PPaQcjevG_3Hzu1qeBS3ye6FnfG9pL6htA6vy5E8c
System.img : https://mega.nz/#!ShVTHRYJ!-Ha-K9UgKahc7KkRRSRHPkpuLSC4Yr0sZ_kCzEumRs0
If you don't use BND-L21 then use this files at your own risk.
it would have been nice
if files were on some other filehost.
plz share oeminfo too
kdark said:
plz share oeminfo too
Click to expand...
Click to collapse
Wiil try and do
U think it will work on L24?
A bit of context here - my device model is BND-L34 (Mate SE) and I had tried using a method that a user posted in a Mate SE specific thread that detailed how to manually update to Oreo.
Well, that failed miserably and I ended up with a bricked device. I had tried numerous different things to try and revive it (some that I had come up with on my own) and none of them worked. Then I thought to use Multi-Tool to unbrick it with a backup I had lying around but unfortunately it was a Nougat backup.
I had almost lost hope until stumbling upon this thread. I figured I had nothing else to lose so I decided to try to restore my phone with Multi-Tool and your backup files - all except for the system image because MEGA decided to **** block me due to it being a large file (you should definitely upload them elsewhere, by the way), so what I did was use a stock system image someone uploaded in the OpenKirin RROS thread along with the rest of your backup files.
I had also gotten a stock ramdisk_recovery.img file from somewhere else (forgot where but if anyone has trouble finding a stock recovery for Oreo I can upload mine). And VOILA (hope I spelled that right)! My device is back to life on Oreo and I couldn't be more happy.
SO all in all, even if you didn't intend for L34 users to use these files, I want to thank you!
System image I used (see post #2)
[url]https://forum.xda-developers.com/honor-7x/development/rom-t3765201[/URL]
(Screenshots below in a separate post)
Had to put them in a separate post if I didn't wanna go through the trouble of moving the screenshots to my PC and uploading them there
Thanks man, it's great..:good::good::good::good::good:
XandeR180 said:
A bit of context here - my device model is BND-L34 (Mate SE) and I had tried using a method that a user posted in a Mate SE specific thread that detailed how to manually update to Oreo.
Well, that failed miserably and I ended up with a bricked device. I had tried numerous different things to try and revive it (some that I had come up with on my own) and none of them worked. Then I thought to use Multi-Tool to unbrick it with a backup I had lying around but unfortunately it was a Nougat backup.
I had almost lost hope until stumbling upon this thread. I figured I had nothing else to lose so I decided to try to restore my phone with Multi-Tool and your backup files - all except for the system image because MEGA decided to **** block me due to it being a large file (you should definitely upload them elsewhere, by the way), so what I did was use a stock system image someone uploaded in the OpenKirin RROS thread along with the rest of your backup files.
I had also gotten a stock ramdisk_recovery.img file from somewhere else (forgot where but if anyone has trouble finding a stock recovery for Oreo I can upload mine). And VOILA (hope I spelled that right)! My device is back to life on Oreo and I couldn't be more happy.
SO all in all, even if you didn't intend for L34 users to use these files, I want to thank you!
System image I used (see post #2)
[url]https://forum.xda-developers.com/honor-7x/development/rom-t3765201[/URL]
(Screenshots below in a separate post)
Click to expand...
Click to collapse
plz share your ramdisk img file i tried to find it but didn't get it
XandeR180 said:
I had also gotten a stock ramdisk_recovery.img file from somewhere else (forgot where but if anyone has trouble finding a stock recovery for Oreo I can upload mine). And VOILA (hope I spelled that right)! My device is back to life on Oreo and I couldn't be more happy.
Click to expand...
Click to collapse
I would be very interested in the stock ramdisk_recovery, could you send me the link?
Is that L21 version Indian variant?
can i please get some help with unbricking my l24 variant. i have twrp installed but it says frp is locked. twrp says i have no os
Sonny1732 said:
can i please get some help with unbricking my l24 variant. i have twrp installed but it says frp is locked. twrp says i have no os
Click to expand...
Click to collapse
If twrp works, there is a patch file that you can use to unlock frp.
MOD EDIT: LINK REMOVED
Would be helpful to understand what caused this problem though.
mrmazak said:
If twrp works, there is a patch file that you can use to unlock frp.
MOD EDIT: LINK REMOVED
Would be helpful to understand what caused this problem though.
Click to expand...
Click to collapse
ive had installed twrp and magisk the night before and had the app call lspeed downloaded, the next morning i deleted the lspeed app and restarted the device and got stuck on a bootloop so i factory reseted and now i just get the first honor screen then it reboots to the hauwei erecovery
Sonny1732 said:
ive had installed twrp and magisk the night before and had the app call lspeed downloaded, the next morning i deleted the lspeed app and restarted the device and got stuck on a bootloop so i factory reseted and now i just get the first honor screen then it reboots to the hauwei erecovery
Click to expand...
Click to collapse
Ok. Some reason twrp does not good a good job with factory resets.
I suggest flash that frp unlock.zip
Then flash stock ramdisk.img and stock kernel.img.
That will remove magisk, for now anyway.
Then try to boot. If still not, then flash stock recovery and do factory reset. But if reset again locks frp. You will be stuck.
If you dont mind resetting from fresh system maybe just reflash with hurupdater or hwota, instead of flashing stock recovery.
mrmazak said:
Ok. Some reason twrp does not good a good job with factory resets.
I suggest flash that frp unlock.zip
Then flash stock ramdisk.img and stock kernel.img.
That will remove magisk, for now anyway.
Then try to boot. If still not, then flash stock recovery and do factory reset. But if reset again locks frp. You will be stuck.
If you dont mind resetting from fresh system maybe just reflash with hurupdater or hwota, instead of flashing stock recovery.
Click to expand...
Click to collapse
i dont mind at all resetting from fresh system how do i do that
Sonny1732 said:
i dont mind at all resetting from fresh system how do i do that
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
mrmazak said:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
Click to expand...
Click to collapse
thank you, ill give it a try
---------- Post added at 09:03 AM ---------- Previous post was at 08:50 AM ----------
Sonny1732 said:
thank you, ill give it a try
Click to expand...
Click to collapse
i cant download the frp unlock.zip
Sonny1732 said:
thank you, ill give it a try
---------- Post added at 09:03 AM ---------- Previous post was at 08:50 AM ----------
i cant download the frp unlock.zip
Click to expand...
Click to collapse
Ok hold on
Should be this
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
From @KingOfMezi
mrmazak said:
Ok hold on
Click to expand...
Click to collapse
i did the HuRUpdater_0.3.zip and now i can get to the just a sec screen after i select wifi during setup but now its stuck there
My phone is an Honor View 10 model BKL-L04 (American model) build 8.1.0.133 (C567GT).
These are the steps that I used to remove the stock firmware and recovery and replace them with something more to my taste. I did < 1% of the actual work here, I'm just putting everything that I did in once place so that other people may not have to look so hard to find answers.
Requirements
View 10 - If you don't have one then you're in the wrong place. Do NOT follow these directions for any other phone as both the directions and the links are specific to the model mentioned above.
Cash/PayPal - Most of us don't have the skills to pry out the bootloader unlock code ourselves so we must pay someone who does. God knows the manufacturer isn't going to help us out here
SD Card - You can probably get this done purely on internal storage, but weren't you going to put in a nice, big SD card anyway?
SD Card Writer (optional) - You'll need a way to load files onto the card prior to flashing. IMHO getting an SD card writer is the simplest way, but to each their own.
Unlocking
This guy will get you an unlock code for your View 10 for $22 (USD). Order a Bootloader Unlock Code, select the Huawei option "with IMEI", put BOTH of your IMEI numbers in the comments field, submit it and pay via PayPal. I got a code in about an hour. Once you have the code you can follow these directions to perform the unlocking process. If you need a bit more help getting though it then try this guide.
Flash Recovery
Don't use the official TWRP images. As of Dec 8, 2018 neither 3.2.1-0 nor 3.2.1.-1 worked for me (-0 dropped to fastboot after a few seconds and -1 caused a bootloop when entering recovery). Use the latest unofficial image from this page. Directions included. More detailed directions can be found here but make sure to use the TWRP image from the first link.
Copy Zips
Now pick out a ROM (I went with LineageOS 15.1) and copy all the zips you need to your SD card. The list probably includes the ROM itself, gapps, and some type of su/root package. Put them all on your card.
Flash ROM
If you're going with LIneageOS 15.1 as I did then this guide should get you the rest of the way. It has the links for the ROM itself as well as gapps and the su package. Again, be very careful to match exactly your phone model and architecture (arm64 for the View 10) when grabbing these packages.
Extras
You can find the latest stock firmware image for the BKL-L04 here. Be damn sure your phone matches mine before you use it! If you need to pull out the stock recovery for any reason, you can use the update extractor to do this (grab recovery_ramdisk), then flash it the same way you flash TWRP.
Good luck and have fun! I'll try to help if you get stuck but the real knowledgeable people are those that wrote the articles I've linked to.
Cheers!
- E
Is "twrp_bkl_0.7.img" the latest one?
As of Dec 9 I believe it is, yes.
Eimafn said:
As of Dec 9 I believe it is, yes.
Click to expand...
Click to collapse
It installed but it keeps saying unable to unmount system so I can't backup or flash a new rom.
MikeyJay530 said:
It installed but it keeps saying unable to unmount system so I can't backup or flash a new rom.
Click to expand...
Click to collapse
I didn't have that issue when I was first flashing the ROM, but I do now. If you're having it prior to flashing your ROM would it be because you didn't wipe & format beforehand? The guide I linked in step 5 leads you through this procedure if you need it.
As far as the unmounting error, I think that's something we'll have to live with until the issue is corrected in TWRP.
- E
Eimafn said:
I didn't have that issue when I was first flashing the ROM, but I do now. If you're having it prior to flashing your ROM would it be because you didn't wipe & format beforehand? The guide I linked in step 5 leads you through this procedure if you need it.
As far as the unmounting error, I think that's something we'll have to live with until the issue is corrected in TWRP.
- E
Click to expand...
Click to collapse
Then how can I flash a custom rom?
MikeyJay530 said:
Then how can I flash a custom rom?
Click to expand...
Click to collapse
I think it works if you wipe/format first. The guide I linked walks you through this.
Eimafn said:
I think it works if you wipe/format first. The guide I linked walks you through this.
Click to expand...
Click to collapse
I did wipe/format first lol still messed up
MikeyJay530 said:
I did wipe/format first lol still messed up
Click to expand...
Click to collapse
Hmm. Well, you can either try one of the official builds (here) or wait for the guy doing our customized build to fix this issue. You might even post a note on this thread describing your issue so that he can track how many people are having it.
Sorry I couldn't be more help. The View 10 is not the easiest phone to work with by a long shot.
- E
MikeyJay530 said:
I did wipe/format first lol still messed up
Click to expand...
Click to collapse
You should do it from emui settings not from twrp .
miststudent2011 said:
You should do it from emui settings not from twrp .
Click to expand...
Click to collapse
What do you mean?
MikeyJay530 said:
What do you mean?
Click to expand...
Click to collapse
You have told that you have formatted your device, if you have formatted it from twrp it will cause issues, you should format it from emui system settings.
miststudent2011 said:
You have told that you have formatted your device, if you have formatted it from twrp it will cause issues, you should format it from emui system settings.
Click to expand...
Click to collapse
No I need to do it in TWRP if I want to install a custom rom...lol
MikeyJay530 said:
No I need to do it in TWRP if I want to install a custom rom...lol
Click to expand...
Click to collapse
Seriously you are laughing at me for trying to help you ?
I need to do it in TWRP if I want to install a custom rom --> Where did you get it ?
Currently available TWRP are buggy and are causing issues.
miststudent2011 said:
Seriously you are laughing at me for trying to help you ?
I need to do it in TWRP if I want to install a custom rom --> Where did you get it ?
Currently available TWRP are buggy and are causing issues.
Click to expand...
Click to collapse
Noooo I'm laughing because I'm confused lol I got the twrp from the link on this thread.
MikeyJay530 said:
Noooo I'm laughing because I'm confused lol I got the twrp from the link on this thread.
Click to expand...
Click to collapse
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
miststudent2011 said:
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
Click to expand...
Click to collapse
I'm wanting to flash Pixel Experience though.
---------- Post added at 08:21 AM ---------- Previous post was at 08:06 AM ----------
miststudent2011 said:
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
Click to expand...
Click to collapse
Also, how do I get TWRP off my phone so I have EMUI recovery back?
MikeyJay530 said:
I'm wanting to flash Pixel Experience though.
---------- Post added at 08:21 AM ---------- Previous post was at 08:06 AM ----------
Also, how do I get TWRP off my phone so I have EMUI recovery back?
Click to expand...
Click to collapse
Download full firmware package from firmware finder and extract recovery from update.app and flash it ,
BTW what is your current phone state ?
miststudent2011 said:
Download full firmware package from firmware finder and extract recovery from update.app and flash it ,
BTW what is your current phone state ?
Click to expand...
Click to collapse
Is there a guide for that? Sorry I'm new with this phone. My phone is unlocked.
MikeyJay530 said:
Is there a guide for that? Sorry I'm new with this phone. My phone is unlocked.
Click to expand...
Click to collapse
What is your phone current state, you have just flashed only twrp or any other changes ?
did you format your phone through emui settings before flashing twrp ?
what build are you on currently ?
Hello all, I was asking if you can help me with an issue here.
While trying to root my Nord 2, I flashed the wrong boot.img version (A.10, while I was already update at the A.11), losing my WiFi and Bluetooth. So to recover them, I flashed the Full A.07 firmware and went back up to A.11 flashing the various OTAs. After flashing the A.07 firmware though, I've lost IMEI and Cellular functionality, and was never able to recover them.
I've done a backup of my nvram, nvdata, and nvcfg partitions before flashing, but restoring them didn't solve the issue.
I've use this guide for root: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
And this guide to flash A.07 and OTAs: https://forum.xda-developers.com/t/oneplus-nord-2-oxygen-11-3-dn2103-eea-rom.4331695/
Does someone have any hints? Or should I send it back to Oneplus?
Raygen said:
Hello all, I was asking if you can help me with an issue here.
While trying to root my Nord 2, I flashed the wrong boot.img version (A.10, while I was already update at the A.11), losing my WiFi and Bluetooth. So to recover them, I flashed the Full A.07 firmware and went back up to A.11 flashing the various OTAs. After flashing the A.07 firmware though, I've lost IMEI and Cellular functionality, and was never able to recover them.
I've done a backup of my nvram, nvdata, and nvcfg partitions before flashing, but restoring them didn't solve the issue.
I've use this guide for root: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
And this guide to flash A.07 and OTAs: https://forum.xda-developers.com/t/oneplus-nord-2-oxygen-11-3-dn2103-eea-rom.4331695/
Does someone have any hints? Or should I send it back to Oneplus?
Click to expand...
Click to collapse
You done the mess even I creted simple twrp and root method you choosed the patched boot.img way and This happened.
Try to restore your full backup of nandroid using twrp. Or fist install twrp and flash non patched boot images using twrp itself
pankspoo said:
You done the mess even I creted simple twrp and root method you choosed the patched boot.img way and This happened.
Try to restore your full backup of nandroid using twrp. Or fist install twrp and flash non patched boot images using twrp itself
Click to expand...
Click to collapse
Yeah I saw there was 2 different guides, I went with the newer one but it wasn't the right choice.
Already tried flashing a stock boot image, no change. Didn't do a Nandroid backup before hand, that's my bad.
Raygen said:
Yeah I saw there was 2 different guides, I went with the newer one but it wasn't the right choice.
Already tried flashing a stock boot image, no change. Didn't do a Nandroid backup before hand, that's my bad.
Click to expand...
Click to collapse
Try all boot images and test it
File folder on MEGA
mega.nz
Must work with anyone
sakarya1980 said:
Try all boot images and test it
File folder on MEGA
mega.nz
Must work with anyone
Click to expand...
Click to collapse
Those images are the first I've tried. I've then tried with the stock boot image linked in @pankspoo post, but with still no result. My guess is that flashing V.07 on top of V.11 rewrited some others partitions that should have not be touched
Well i am not happy to tell you, but if its true that partitions containing IMEI and WiFi connections got overwritten with nonsense information then the only thing that could save your phone is full nandroid backup which you do not have. And unfortunetly dont expect anyone else to provide it as that would mean that those 2 phones would have the same IMEI and MAC address.
I would suggest that you flash stock image, lock your bootloader and send it for RMA saying that you dont know what happened. You will have like 50/50 chance that they will just replace your motherboard without much of an investigation.
Raygen said:
Those images are the first I've tried. I've then tried with the stock boot image linked in @pankspoo post, but with still no result. My guess is that flashing V.07 on top of V.11 rewrited some others partitions that should have not be touched
Click to expand...
Click to collapse
If you have europe Version of nord2, flash Version v07, then update with otas to v09, v10, v11 with twrp
@Raygen did you get through with your imei repair? i have a similar issue.
BusterCZ said:
Well i am not happy to tell you, but if its true that partitions containing IMEI and WiFi connections got overwritten with nonsense information then the only thing that could save your phone is full nandroid backup which you do not have. And unfortunetly dont expect anyone else to provide it as that would mean that those 2 phones would have the same IMEI and MAC address.
I would suggest that you flash stock image, lock your bootloader and send it for RMA saying that you dont know what happened. You will have like 50/50 chance that they will just replace your motherboard without much of an investigation.
Click to expand...
Click to collapse
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
sakarya1980 said:
If you have europe Version of nord2, flash Version v07, then update with otas to v09, v10, v11 with twrp
Click to expand...
Click to collapse
Tried two times already, no change.
Keden said:
@Raygen did you get through with your imei repair? i have a similar issue.
Click to expand...
Click to collapse
Send it back to OnePlus sadly.
Raygen said:
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
Tried two times already, no change.
Send it back to OnePlus sadly.
Click to expand...
Click to collapse
Did any way you can flash stock. Firmware using sp flash tool of mediatek just like qualcoms MSM tool used for hardbricked devices
Raygen said:
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
Click to expand...
Click to collapse
Well my guess is that if they take a look at it and the bootloader will be unlocked they will send it back to you rejacted. Atleast that was my expirience once with my old Xiaomi phone. So probably try flashing original firmware using some kind of recovery utility such as Sp flash to help get rid of this message?
pankspoo said:
Did any way you can flash stock. Firmware using sp flash tool of mediatek just like qualcoms MSM tool used for hardbricked devices
Click to expand...
Click to collapse
BusterCZ said:
Well my guess is that if they take a look at it and the bootloader will be unlocked they will send it back to you rejacted. Atleast that was my expirience once with my old Xiaomi phone. So probably try flashing original firmware using some kind of recovery utility such as Sp flash to help get rid of this message?
Click to expand...
Click to collapse
I would like to use Sp flash but I don't know where I could find the files for the Nord 2 to use with it. Like the scatter file and the firmware in Raw format
Keden said:
@Raygen did you get through with your imei repair? i have a similar issue.
Click to expand...
Click to collapse
Might help ! Check,.
U need to get UMT dongle , Ultimate Multi tool software.