I Recently tried going back to stock Honor 8 coming from RRos (Oreo) but whenever I flash the stock images extracted from the latest UPDATE.APP file, I never get past "Your device is booting now..." message on bootloader screen, any help? Willing to give more info if necessary.
What did you flashed exactly? You need to flash system.img, kernel.img, ramdisk.img, recovery_ramdis.img the after all, when prompt to you have to press vol up and go into recovery. Do a full wipe then reboot. It should work, for me worked when trying to pass from RR beta 3 to OmniPie alpha2. I had to go back stock first
Giuskiller said:
What did you flashed exactly? You need to flash system.img, kernel.img, ramdisk.img, recovery_ramdis.img the after all, when prompt to you have to press vol up and go into recovery. Do a full wipe then reboot. It should work, for me worked when trying to pass from RR beta 3 to OmniPie alpha2. I had to go back stock first
Click to expand...
Click to collapse
That's exactly what I did before it broke, now, even redoing the procedure doesn't allow me to go past Bootloader :C
I'm going to try to empty the battery and retry.
UPDATE:
I managed to get back to stock using TWRP and the latest updates, but now I faced an new problem.
My phone has now been uncertified... and my build number is System 8.0.0.046(0JSQ)
How does one fix this issue?
FIXED:
Used Hurupdater to flash latest images.
CurlyApple said:
UPDATE:
I managed to get back to stock using TWRP and the latest updates, but now I faced an new problem.
My phone has now been uncertified... and my build number is System 8.0.0.046(0JSQ)
How does one fix this issue?
FIXED:
Used Hurupdater to flash latest images.
Click to expand...
Click to collapse
Glad you were able to fix. However thw uncertified device was probably caused by twrp wich is unsupported with openkirin's roms
Related
Hi guys, I flashed the latest factory image, then flashed the latest TWRP but can access it 1 out of 10 tries.. What am I doing wrong? Is it a faulty replacement phone? Never had this issue with my other nexus 5 (same recovery file but lollipop and not marshmallow) and now I have this problem.. Tried to riflashato the factory image 5 times, boot to recovery without installing but nothing changed.. Thanks in advance!
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
beekay201 said:
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
Click to expand...
Click to collapse
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
carlese said:
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
Click to expand...
Click to collapse
do you finde fix
slavisa037 said:
do you finde fix
Click to expand...
Click to collapse
Downloaded twrp again and used flashify..
carlese said:
Downloaded twrp again and used flashify..
Click to expand...
Click to collapse
This is not really a fix, since to use Flashify one needs to be rooted already.
What I did to work around this was reflash LMY48M. After reflashing that, fastboot correctly boots/flashes twrp.
I've read that the issue arises when trying to boot and/or flash twrp with MRA56K installed, AND the device is connected to USB.
Ok, i got some of problems here, i tryied to root my Nexus 5 with other Android 6 version, it was the first one launched after development version. Now i have MRA58K version.
Problem 1 : I have no stock recovery, i first rooted original version of Marshmallow with CWM and i soft bricked, so no backup, no factory images. Installed MRA58K and there is no stock recovery, thanks god i can use bootloader. I can install TWRP, but i want to install the old recovery, Tell me how to do it.
Problem 2: Actual version of Marshmallow ask me to install a patch, but when installing i got stuck in TWRP, it cant install it (yes, android was rooted, but i installed twrp before root, and the update were before it.)
Thanks.
You can flash a stock ROM using the flash-all file in a command prompt. This will install stock ROM with stock recovery. Make sure the phone has an unlocked bootloader and you should be fine.
Official OTA updates cannot be installed with a custom recovery.
I tryied 3 times to install OS with flash-all. All the problems start after i installed CWM and try to root the phone, but after that, i used a stock rom image that was different build than actually one.
I`m not sure yet who`s fault is.
Any ideas?
I don't recommend using CWM, only TWRP.
After you flash TWRP always boot into it, and since you're flashing a custom recovery I'm going to assume you don't care about OTA's, swipe to allow system to be mounted. TWRP will automatically patch the system to survive android trying to overwrite it. Reboot into TWRP a second time to be safe. TWRP should stick from now on until you flash over it or restore stock system partition.
Yes, now i have TWRP as recovery, but i want to replace it with stock recovery.
Problem is, when i upload stock recovery and try to boot in recovery mode, i got the green dead android with red triangle.
But after TWRP uploading and booting in recovery mode, TWRP is there..
I really don`t know what`s wrong.
Flash stock recovery, select recovery from the fastboot menu, hold the power button and press volume up button.
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda
audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.
kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/
Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...
hi guys, there is several posts for upgrade to the newer firmware, but is there any guide to downgrade? I'm running L29C636b138 and it's draining my battery quickly. I was using 136 and it was super! and for now i can't upgrade to the 158 yet since it's not authorized yet.
I guess you will just have to wait on that 158 update. It will come soon enough. I've been experiencing the same updating from 126 to 138 on my eu phone. The standby drain is worse than the 126 fw. Battery is still good for me tho with 9hrs sot over 2 days off charger. Just that 126 was better.
Hi guys, I was using L29b636b158. I decided to flash to "[ROM] RomAur_b175_v1.0 [19/03]-[UB]". Some how I didn't like, I used TWRP to restore my backup. and Now the camera is not working at all. It shows an android icon. nothing happens (it tries to open but crash right away). I've tried to Format Data in TWRP. I didn't work. I tried to install "hw_data.zip". I didn't work. I tried to flash back to "[ROM] RomAur_b175_v1.0 [19/03]-[UB]" camera still not working.
Can some one help please??
aznboix said:
Hi guys, I was using L29b636b158. I decided to flash to "[ROM] RomAur_b175_v1.0 [19/03]-[UB]". Some how I didn't like, I used TWRP to restore my backup. and Now the camera is not working at all. It shows an android icon. nothing happens (it tries to open but crash right away). I've tried to Format Data in TWRP. I didn't work. I tried to install "hw_data.zip". I didn't work. I tried to flash back to "[ROM] RomAur_b175_v1.0 [19/03]-[UB]" camera still not working.
Can some one help please??
Click to expand...
Click to collapse
Did you restore your boot image?
If you didn't back it up:
Download firmware from http://hwmt.ru/hwmtsite/firmware-database
Download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Unzip update.zip
Open update.app in update extractor
Right click on boot and Extract.
Flash boot using twrp.
Note: this will encrypt your /data if you boot without applying SuperRoot or SuperSU.
ante0 said:
Did you restore your boot image?
If you didn't back it up:
Download firmware from http://hwmt.ru/hwmtsite/firmware-database
Download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Unzip update.zip
Open update.app in update extractor
Right click on boot and Extract.
Flash boot using twrp.
Note: this will encrypt your /data if you boot without applying SuperRoot or SuperSU.
Click to expand...
Click to collapse
1) which option do i choose when it prompts "boot" or "recovery" when I flash using twrp
2) Do I have to flash "superoot soverinity" again? after flashed the stock boot img?
aznboix said:
1) which option do i choose when it prompts "boot" or "recovery" when I flash using twrp
2) Do I have to flash "superoot soverinity" again? after flashed the stock boot img?
Click to expand...
Click to collapse
1. Boot
2. Yes.
Before you do, can you go to Install click Select Storage - internal, and check that /data is not encrypted again. You should see regularly named folders, not random letters/numbers. If you can mount data that is.
If it is encrypted you will bootloop if you try to boot with a decrypted boot image.
So I installed the boot.img from stock (158). Nothing changed..My phone works super well. Camera still not working ;(
u can try to find your boot here as well
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Update: I tried flashing TWRP by Askuccio through fastboot and I successfully did. Then I flashed PixyOS v2.4 and flashed it successfully then flashed Gapps and stock recovery then followed rest of the required steps and everything went smooth and right. Using PixyOs now. Great rom with great stability with Android P. ?
I was on Oreo on my 6x. I wanted to flash this pixyos rom on my Honor 6x. I unlocked the bootloader of my phone installed the Twrp successfully without any hassle. Now it was time to flash PixyOs and unfortunately I did not do any backup of any sort. The PixyOs Package showed some error when I tried to clean flash it. And here we go my phone had No Os now. I searched a lot and found this thread
https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I gave it a try step by step thinking about that it would work but after successfully following all the mentioned steps and flashing everything I got this "System failed" error when the device was booting. In other words it didn't work eventually.
I tried the dload method with the same update zip from the thread linked above but it failed too.
I tried erecovery to restore my device but it gave me "Getting package info failed".
I don't know what to do now. Please help me with this and help me restore my phone.
I had the same issue
i made something like this a month ago
only one temporary solution worked is flashing EliteRom via twrp and i got the phone working again but still can't flash a stock rom.
tanaybitw said:
I was on Oreo on my 6x. I wanted to flash this pixyos rom on my Honor 6x. I unlocked the bootloader of my phone installed the Twrp successfully without any hassle. Now it was time to flash PixyOs and unfortunately I did not do any backup of any sort. The PixyOs Package showed some error when I tried to clean flash it. A then nd here we go my phone had No Os now. I searched a lot and found this thread
https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I gave it a try step by step thinking about that it would work but after successfully following all steps and flashing everything I got this "System failed" error when the device was booting. In other words it didn5 work eventually.
I tried the dload method with the same update zip from the thread linked above but it failed too.
I tried erecovery to restore my device but it gave me "Getting package info failed".
I don't know what to do now. Please help me with this and help me restore my phone.
Click to expand...
Click to collapse
Can you boot to fastboot. What did the PC say when you ran the script. Try to flash TWRP if EMUI 5 and then press and hold Volume Up and Power to boot into it. If it works, good. If not then again boot to bootloader and try to flash TWRP of EMUI 8. Again try to boot into it. If it works, good. Anyway, once you're in TWRP don't let your phone turn off. Plug it in charging. Now go-to wipe, and format data
»FáRéS...?« said:
i made something like this a month ago
only one temporary solution worked is flashing EliteRom via twrp and i got the phone working again but still can't flash a stock rom.
Click to expand...
Click to collapse
I'd suggest you to try PixyOs (With Askuccio TWRP). It's a great and fluid ROM. Only downside is it doesn't have Stock Emui camera and I didn't even try flashing it because I read somewhere that it causes the device to get stuck in bootloop.
Mannan Qamar said:
Can you boot to fastboot. What did the PC say when you ran the script. Try to flash TWRP if EMUI 5 and then press and hold Volume Up and Power to boot into it. If it works, good. If not then again boot to bootloader and try to flash TWRP of EMUI 8. Again try to boot into it. If it works, good. Anyway, once you're in TWRP don't let your phone turn off. Plug it in charging. Now go-to wipe, and format data
Click to expand...
Click to collapse
Thank You for your reply.