Yesterday, I tried to unlock using lineage16, using twrp3.31 version. . In the first system version of emui9, flashing lineage. Failure, error7 is prompted. . I carried out several system updates, (the latest emui9) installed twrp, flashing lineage16. Still failed.
Finally, I carried out the wrong operation, recovery cleared the data, and now rec and erac can not enter I think I should go to the sale to solve this problem.
My device is a Chinese version, the model is al20 (as far as I know, the hardware is no different from the US version, except for the baseband)
This is my system version, and various parameters. . I hope you can get your help I have unlocked the device protection lock. The only problem is error7. This phone does not have the rom I like in China. . . . I have checked some information, it may be that the rom and the phone model are wrong, or the underlying firmware is wrong (I used the official recovery tool to restore to emui9) Now, I can only guess. . . . The problem with rom, may not be considered by the developers, and it is not known that the Chinese version can be unlocked.
My friend told me to delete the rom model verification, I do n’t know if it is useful (after I am modified, use twrp to flash, error7)
He asked me to delete the first four columns
Don’t know if u r still using this device or not, the official 3.3.1 twrp will get error of unable to mount partitions on too new firmware version such as emui 9.1.337, downgradeing the firmware version may help, and lineage 16 will not work on Chinese's specific device such as al00 and al20, it would only work for some US specific model, in this case you can use other rom like aosip, i just flashed this rom and it is booting normally, but my al20 was sucked in installing magisk, after flashing the patched recovery the device will not boot or boot into the system without magisk......too many time were wasted on this device, and i don't want to play with it anymore..
Related
Okay so here's the info to the best of my knowledge,
Phone Model : Moto G 3rd Gen (XT1550, dual sim, 2gb RAM, 16gb ROM, India)
Bootloader Status : Unlocked
Root Status : Rooted
Recovery : Stock
ROM : Stock ROM 5.1.1
I've been running the stock Recovery & ROM with high hopes of getting an official OTA Marshamallow update.
To truly customize the device to my liking I flashed the xposed framework (the arm version) , it worked fine and all the modules I installed worked perfectly.
I also had Device Control, Xposed Gels, and some other apps to bring my Stock ROM experience close to that of Cyanogen MOD.
When the OTA Marshmallow update started rolling in , I was unable to install the update even after successfully downloading the file numerous times. But i was so comfortable with my device and all the customization I had on my device that I decided to keep using my customized Stock ROM.
4 months later (now) the lack of a gyro in this device and my eagerness to get into VR headsets has left me with no choice but to sell it and get another phone. So i needed it in a sale worthy condition, without the customization and with the Marshmallow update installed.
I uninstalled the xposed framework and all the modules but was still unable to install the OTA update.
So i figured i'd install CyanogenMOD with TWRP custom recovery.
I have done this for quiet a lot of my friends and am fairly used to the steps involved. I use the " minimalADB fastboot " kit and my device on fastboot to flash recovery. For some reason i was not able to flash the lastest TWRP image (twrp-osprey-3.0.0-r2.img ) for the device nor was i able to boot from it :crying:. The fastboot command prompt on my PC would show success but the devices would not restart into the custom recovery like it is supposed to, but the device would stay at the fastboot mode and kept restarting everytime i selected the recovery mode option.
I had an older image (twrp-osprey-2.8.7-r3.img ) which i couldn't flash either but i was able to boot into TWRP with this image. From here i tried installing the latest CM12.1 nightly available (cm-12.1-20160227-NIGHTLY-osprey.zip) as soon as i swiped the device would just reboot, i tried this numerous times and with other nightly builds as well.
In haste and frustration i wiped the cache/dalvik , internal storage and system through TWRP , thinking that changes made in the quest of customizing my device were causing this hindrance. I had no OS now. I went over trying to flash TWRP and CM12.1 many times again with the same issues.
I came about a thread on How to " Fastboot Flash Moto G (3rd Gen) Factory Firmware Images " (http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750) & used this firmware image " Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7 ". Still no progress.
The bootloader unlocked warning has come back (i flashed a stock MOTO logo there earlier) which keeps flashing on my screen again and again , no booting into OS or anything else. Not even an error. As if there is no OS installed.
I have gone about the procedure in the above thread a couple of times, with no success and the same problem.
Is there any reason why i'm unable to flash a custom recovery or ROM ??? What am i missing???
Please help i'm stuck, pulling my hair out with no phone and completely frustrated.
Thanks in advance.
Did you check your build no for stock ROM?
samirza692 said:
Did you check your build no for stock ROM?
Click to expand...
Click to collapse
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
ashrith.s said:
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
Click to expand...
Click to collapse
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
samirza692 said:
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
Click to expand...
Click to collapse
the link provided is the exact same link from where I flashed a stock rom before.
build number for stock rom??? am i missing something???
all i see is the model variant (xt1550 is my phone)
RAM specification (mine is 2gb)
and the region (mine is retails asia | india )
so i went with the following firmware
Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7
where does the build number come into the equation???
Please lemme know if im doing something wrong. Thanks for the replies.
So I've successfully flashed twrp-osprey-2.8.7-r3.img to my device and I've been able to boot into twrp. The touchscreen doesn't seem to respond though. It asks to swipe to begin and I'm stuck again.
I had the screen replaced a couple of days ago.
Could it be a faulty screen or a software issue?
P.S. I have not been able to flash any version of twrp after the above mentioned version (v 3.0.0 is the latest stable version) but the ones prior are flashable.
Hey, contact me via PM and il do my best to help you in this.
therealduff1 said:
Hey, contact me via PM and il do my best to help you in this.
Click to expand...
Click to collapse
Is not big issue
Is it still possible to boot back into the OS? If it is, check if you have OEM unlocking enabled, since you're on stock ROM, it might be gotten unchecked after unlocking your bootloader because that's what happened with me. If you do t wether or not that was checked, you're at a dead end and there's nothing you can do. You can try paying someone to fix it, i.e., Motorola.
Hello everybody, I hope to find help here.
My phone is the HTC One A9, Europe Version ("hiaeuhl"). Recovery is TWRP 3.0.2-0.
The background story is that I already managed to install Cyanogenmod after downgrading the original ROM to Version 1.10 and unlocked the bootloader with the HTC Unlock tool. I also managed to decrypt the device.
I'd like to update my system regularly, but unfortunately the last running version is the cm-13.0-20160904-NIGHTLY-hiaeuhl.zip from September 4th.
If I try to install the latest versions of Cyanogenmod (for example from September 9th) I always get the error
hiae.veryfy.trustzone() failed to read current TZ version: -2
Updater process ended with ERROR 7
I already tried to remove the lines that check this in the file updater_script inside the ROM's zip, then I could install the update, but afterwards I was stuck in a boot loop.
The error has nothing to do with the encryption, it apears with and without device encryption, and it has nothing to do which system (original or custom) is installed before flashing. It is also indifferent if I try the update via the system's update function or directly in TWRP. It's the fact that the Cyanogenmod version from September 4th is the last working for me. I definetly chose the right one for hiaeuhl, but it seems the developers have added a feature that makey my device incompatible to this ROM.
If there is anything I can do to update my system again, please let me know.
Have the same issue.
We need to update it, but I don't know how
jira.cyanogenmod.org/browse/NIGHTLIES-3351
Here is how I could solve the issue:
- flashing the latest stock firmware (and let it possibly completely update)
- install TWRP via fastboot
- from TWRP a factory reset
- install new version of the Cyanogenmod from TWRP
It worked for me, now I can use my beloved custom Rom
The Same Problem
I have exactly the same Problem, last working CM-Update was the 3rd September
Did you try my solution? With the older CM Rom versions for the HTC A9 you had to downgrade the stock rom, otherwise the CM wouldn't have started after the installation. Now it seems that the stock rom has to be the latest one (for me the 1.56) that you are able to flash the latest CM versions.
I do not have the latest stock Rom, my os is 1.27.161.6, seems actually cm needs 1.57, i am unlocked and s-off
You should probably find the right version for your phone here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
You should take the one with the right cid for your phone (which you can find with "fastboot getvar all" in the fastboot mode)
Thanks, i will try it and report
The last build i found for my version is 1.27. this is what i have
Hmmm... then I guess you have to wait until the new version appears in the forum. Seems that you have a device with vodafone branding. Since you already set S-off you also have the possibility to change your cid to one of the existing newer firmwares.
Is there a solution without going back to stock?
I'm not an expert, but I don't think so. It seems that the version number of the stock rom is stored somewhere even after changing the system to Cyanogenmod, and this version has to be the latest one. So unfortunately, as far as I know, you'll have to do the flashing procedure again...
thanks Silberhase, now i am on CM 13 again. Thats what i did: wrote Supdercid, searched a ruu-version for my build, found a 1.56.401.70 version, flashed this, then flashed twrp 3.0.2.0 again, factory reset - without factory reset i was not able to install cm, format data, recovery, latest cm update, flash gapps, restore my other data with titanium, done....
I'm glad to hear it worked for you!
Yes, but next Problem or better i actually do not know what problems will raise. After updating today successfully to last cm build phone is encrypted... TWRP requires password for decryption. Problem all over forums. Today i habe no fun to Format data again and restore all.
That's also what I experienced. Other users reported that the current TWRP version 3.0.2.0 can't handle the encryption of the HTC One A9. And every update will encrypt the device again. As a workaround you can do this:
- copy the downloaded update from /sdcard/cmupdater to the external memory card
- boot to the recovery (when asked for password push the cancel button) and install both the update and the gapps again (without wiping anything) from the memory card.
Its a pity, all worked perfectly. Installed last cm.. Which encrypted phone. Restored my backup. All Working. Updated apps, want backup again.... .... Error opening /system/addon.d (not a directory)..error in generating tarlist......Create tarfork()
Process Ended with error 255
I'm trying to help as much as I can even though I have no experience with all this. I never did a backup
Maybe you find the answer here:
http://forum.xda-developers.com/nexus-6/help/e-createtarfork-process-error255-t3302462
Maybe it helps to mount "system" in TWRP and then delete /system/addon.d. But it seems that this step has to be repeated before every backup.
Any news to this theme? Is Twrp able to handle A9 again in new Version?
The recent version 3.0.2.0 of TWRP is available for the A9 but can't handle it's encryption. It works anyway if you are willing to use some workarounds.
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, guys. I bought two of these phones. BLN-AL30 VERSION is the one that I was using for a while. I tried to unlock its bootloader and it was a complete success. I remember that my phone said BLL-L22 in its about device section and not BLN-AL30 though. I proceeded to install TWRP and rooted it, I also backed up all the partitions so I decided to go for the elite version (TWRP, for I wanted to install their room). Everything was ok. I installed the elite rom which I thought was cool and I used it for a while. Then I decided to switch into slim ROM. I had made the proper back up also and still have them files. I backed up everything because I realized the elite ROM asked for a complete wiping. The next thing I realized was that my phone wouldn't be able to install the slim rom because I had this error:
Unable to wipe vendor /vendor command not allowed.
It also happened with product and version partition. And sometimes it said unable to mount /vendor. (The same for product, version)...
Now, I can't install any other room because of that. And I have downloaded many update.app files to recover and heal my phone as stock but it seems impossible. I have bought another honor 6x and it's coming the next month because I loved this phone but also because if bricked but unrecoverable I'd like to have its parts in case of some repair needed. Is there anyway to recover it? it's so sad. I never thought elite rom would do that to my phone. I assure I followed every single step from its thread. Thanks in advance. Hope you can help.
try to formate data then go to main main screen reboot to recovery now wipe everything. if it is not working then try previous version of elite TWRP or Berlin TWRP. if nothing works then u need to do dload. but u r saying dload is also not working still u have two solutions. download oem info of another region and flash it via TWRP u can try oem info for bln-l22c675b340 https://forum.xda-developers.com/honor-6x/how-to/guide-debranding-to-india-variant-bln-t3679402 now Google for bln-l22c675b340 firmware download it then unzip update app file. now Flash oem info file in TWRP then using sd card flash update app by pressing 3 buttons. this time it will install for sure. if oem file failed to install then extract the oem file then download srk tool put both files in restore folder connect your phone in fastboot restore oem info will work for sure. there is no way to brick honor 6x lot of rescue methods available if this fails still you can use hwota8 method to upgrade oreo.
Thank I'm going to try that
Where can I find the Oreo update thing?. Thanks
evjgl said:
Where can I find the Oreo update thing?. Thanks
Click to expand...
Click to collapse
once it is ready for your model. its in beta phase in China and not released for public yet.
I've somehow bricked my 6X.
I have an EU version successfully debranded to India variant BLN-L22 and upgraded to EMUI 8.0, unencrypted and rooted with Magisk.
Something went wrong during the flash of AEX for hi6250 devices (which is reported to be 6X compatible ): I was mainly stuck in a bootloop except for two times when the phone booted, but internal storage wasn't recognized properly (in settings I was able to see the correct percentage of available space but in default file manager I wasn't able to access it and also downloading files to internal storage was impossible, as if my it was full - which isn't true since I was able to move file there through TWRP file manager).
At that point I was pretty pissed, I've forced fastboot and used update.bat to flash stock Oreo again and here things screwed up.
I took a full TWRP backup before experimenting with AEX and copied it to my pc; I'm able to push it to internal storage through adb, but then TWRP isn't able to restore it, dunno why.
My phone is in these condition now:
fastboot is available, commands from pc are working here
bootloader is unlocked
FRP is unlocked
I have a working TWRP recovery (askuccio 3.2.3) which I can access and use; I'm able to replace it with Elemental 3.2.1, with the one provided in the "update.bat" thread (which is another 3.2.1 version) or with stock recovery
if I replace TWRP with stock recovery and boot into it, it shows the update screen and it freeze at 5%, then reboot; no factory reset option there
when I'm into TWRP I can push files from pc to internal memory through adb
pretty sure my phone is still decrypted, dunno if it's still rooted tho
eRecovery is gone
I have no idea how eRecovery gone missing since I never touched that partition; trying to flash ERECOVERY_RAMDISK.img through fastboot using "fastboot flash erecovery_ramdisk erecovery_ramdisk.img" which fails (remote: command not allowed) and "fastboot flash recovery2 erecovery_ramdisk.img" which fails (remote: partition length get error) as well as through Multi Tool (the size or path does not match the file system markup); if I try to boot into eRecovery I get error mode screen: Func NO : 11 (recovery image) Error No : 2 (load failed) and I have no idea how to try to restore it in another way (pretty sure all I need is to factory reset through it and then reflash the firmware for unbrick my phone).
Atm I've tried only Multi Tool: I can successfully flash everything in the unbrick section but it doesn't solve my problem (guess it's due to my missing eRecovery).
I still need to try Image Download method (which I would like to keep it as last resource since it requires to disassemble my device and since I have a working fastboot and TWRP), HuRu and dload (I don't have a micro SD big enough atm, only 2GB - dunno if it can can work from internal storage the same).
Thank you for any help.
@player615 @shashank1320 @vovan1982 @RedSkull23
I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.
shashank1320 said:
I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.
Click to expand...
Click to collapse
How do I do that?
I mean, flash OEMINFO and Custom Bin and then dload method as per debranding guide or HWOTA7, since I'm on Oreo/Emui8 now?
You already debrnaded to Indian version and then updated to Oreo right?
shashank1320 said:
You already debrnaded to Indian version and then updated to Oreo right?
Click to expand...
Click to collapse
Exactly. I was on BLN-L21 Nougat (EU), debranded to BLN-L22 (Indian) through fast method (flash oem and cust bin, dload, update through system update) and then upgraded to Oreo through HWOTA8_BLN - script method.
Multi Tool list my device as BLN-L22 8.0.0.510(C675).
Just dload b340 indian variant. You should be fine
I restored my device countless times with HuRUpdater, the best tool I used on Huawei devices. It always go fine, but a microSD of at least 3GB is required (files to flash are usually 2,70GB). Probably the device won't boot with stock recovery because as you pointed out, it needs to format first before booting since that you was decrypted. HuRUpdater needs to be executed from microSD because it flashes files from there to internal storage, so flashing from there isn't allowed due obvious reasons.
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)
shashank1320 said:
Just dload b340 indian variant. You should be fine
Click to expand...
Click to collapse
RedSkull23 said:
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)
Click to expand...
Click to collapse
dload doesn't work, I guess it's because I miss eRecovery.
If I hold vol+ vol- and power my phone boot into TWRP; I've tried replacing it with stock recovery but it freeze at 5%.
Any way to flash eRecovery from fastboot or as a zip from TWRP?
Gonna get a SD and for HuRu if I won't be able to solve it differently.
Edit: managed to boot into dload screen, but it states "software install failed".
AleNonsense said:
Edit: managed to boot into dload screen, but it states "software install failed".
Click to expand...
Click to collapse
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)
RedSkull23 said:
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)
Click to expand...
Click to collapse
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!
AleNonsense said:
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!
Click to expand...
Click to collapse
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.
player615 said:
Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.
Click to expand...
Click to collapse
Wait: wiping /data with TWRP makes it visible through custom recoveries since that it removes encryption, but when you flash whole EMUI 8 on system stock recovery_ramdisk is reflashed on the recovery partition too, and it forces to reformat /data before booting because if not it'll say that OS is seriously corrupted bla bla bla... EMUI 8 doesn't have to run encrypted?
By the way HuRU is faster, easier and leaves bootloader unlocked.
RedSkull23 said:
If you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Click to expand...
Click to collapse
Nope: don't get me wrong, but I'm here since 2012 and I'm pretty used to this kind of stuff.
I can assure you I haven't picked wrong packages nor any other noobish error: in fact I wouldn't even had to post here if I had encountered just some standard problem lol... my device wasn't fixable through usual ways, or else I would have been able to
RedSkull23 said:
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse
Just heard back from assistance and they are waiting for a new motherboard since there was nothing to do, good to me I was still covered by warranty.
Now it would be nice to know what screwed up my device so bad, since I hadn't any problem till the flash of AEX for hi6250 devices (so 6X compatible) and even in the case it wasn't flashing a wrong rom has never fked up a motherboard in my experience, but whatever.
My only trouble is I'm pretty sure I won't be able to unlock bootloader when my phone will be back, now
Also, thank you to everyone who tried to help!
try this
i had issues also until i found this step by step, i named everything just as he has pictured and made sure to just add the .zips all 3 needed, got correct FW from FW finder and also be sure to put the actual HuRuUpdater.zip in the same folder with the FW files and name the parent folder just like the pic on post shows...poof working stock FW and did not relock my BL....Honor 8 FRD-L04 reverted from no OS to stock 7.0 on EMUI 5 https://www.getdroidtips.com/hurupdater-tool/#comment-109621
RedSkull23 said:
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse