Need Help to Return to the Stock OS - Honor 8 Lite Questions & Answers

Hi. Recently, I did all it was necessary to install CyanogenMod 14.1 on my Honor 8 Lite PRA-LA1 including unlocking the bootloader, installing TWRP and others. Now, I want to revert to the stock OS. The problem is even by searching on and on, I wasn't successful. For the sake of one time clarity for me and other people that may need to do the same things as I want to do, please guide me on how to revert to the stock OS (Android 7 or the new EMUI 8) of my particular device as I already feel hopeless to get to that point. I came across many broken download links, incomplete and ambiguous guides and others.
Thanks a lot.

Hi, you can use HURUpdater to return to stock. Please see the link below:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
I have used it with success.
Good luck.

I used Huawei erecovery and it automatically does everything. Wait 20 minutes after installing and it will do several bootloop

Related

I can't install any ROM and i have no backup (or OS)

Hey! First thing you need to know: i'm stupid af
So yesterday i tried to root my Huawei P9 Lite VNS L31, and everything was doing great: bootloader unlocked and everything.
Because the root didn't seem to work on EMUI, i tried to install another ROM (i'm stupid) with TWRP: so I wipe cache, system and data in order to do it good, i flash the ROM but now when i tried to reboot it didn't boot.
So i figured that i was trying to install a MM Rom on an Nougat (at least it was) device. I then tried another ROM and i didn't work either. After hours of trying to make it work, now it boots on Huawei eRecovery, but i already tried to use it since i made no backup (i'm an idiot), and it seems to fail every time? idk it only show a big red ! mark
Right now i'm still looking for a fix but i would be soooooooooooooooooooo freaking relieved if someone could help me please :crying:
(i'm an idiot)
I DID IT!!!!
So i followed a tutorial made by the website androidmtk (i can't link it it's my first post), and is used the official stock firmware for my phone which you can find on cusumer huawei dot com
DONT FORGET TO BACKUP!!!!!!!!!!!!!!

Stuck on Huawei eRecovery after phone failed OTA Oreo update

Hi,
Big trouble time with my Huawei P8 Lite 2017 (PRA-LX1) after it tried to OTA upgrade to Oreo.
I had not tried anything before - no rooting, no unlock, nothing - and it measerably failed on its own, well done Huawei.
I tried to create a "dload" folder on extSD + adding update.app file etc. it goes up to 5% upgrade then fails..
I found previous methods and posts here on how to unbrick the phone but it requires to unlock the phone and install TWRP etc.
I will bring it back to the store next week and see what they can do, for the moment I bought another phone..
If someone encounters the same problems feel free to post here.
Edit: for the record the attempted methods (thanks Gigi)
- https://forum.xda-developers.com/p8...on/guide-unbrick-huawei-p8-lite-2017-t3766678
- https://forum.xda-developers.com/p8...uide-brick-huawei-p8-lite-2017-maybe-t3816694
Well,I was before on Nougat and had some battery issues so I decided,maybe going to Oreo would solve my issues,so I go ahead and unlock the bootloader and install TWRP,and then it seems I flashed Oreo No Check recovery on Nougat and it displayed the BOOT error.
The only way I fixed my phone was to buy a three day license of DC Phoenix for 20 euros.
I flashed the first version of Nougat on it and then it installed a new version of Nougat through eRecovery,and after a few weeks the Oreo update came,installed it with no issues.
Overall,DC Phoenix might be the only thing that will work,but at least it is guaranteed to work.

Bricked OnePlus 5

Hi everyone,
I had issues with the update of my OnePlus 5 as stated on this thread : https://forum.xda-developers.com/oneplus-5/help/oneplus-5-update-fails-t3866533
I tried the solutions that were given to me but it wouldn't work, since TWRP kept returning ERROR 7.
I finally managed to install OnePlus5Oxygen_23_OTA_040_all_1811051816_c6670cf.zip thanks to twrp-3.2.1-1-cheeseburger.img without getting any error but my phone got stuck at the "Dots turning" logo when I boot.
I looked around a lot trying to find a solution and as far as I understood, it may be due to the addition of Treble to OnePlus. I tried to wipe everything thanks to TWRP and flash my phone back to OxygenOS 5.1.3: OnePlus5Oxygen_23_OTA_036_all_1806131715_b5381c0ef26d9e.zip but it's still stuck.
Could anyone help me ?
Thanks a lot
This guide will help you: https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
A HUGE thank you ! It worked perfectly.
Note for people who might see this thread : it locked my bootloader, I had to unlock it back (and wipe all data). Flashed TWRP and Magisk, everything works perfectly

Flashed roms stuck on bootscreen (logo screen)

Hi guys,
I need an advice. It will be appreciated!
I am with TRWP 3.1.0-1 alice.Flashed an image through official TRWP app.
I flashed "ressurection remix" , "stock 8.0" , "lineage OS". They all just get stuck on logo screen after install.I waited for 25 mins and nothing happens; only once the phone restarted & then froze again.
If i turn it off, after 4 secs. it turns on by itself.
(but if i go quickly with combo buttons, i am able to get into TRWP and go back to backed up system...)
I'm currently running Android 5.0.1 / EMUI 3.1 ;
I have rooted the phone with Kingoroot
(without pc)
***
If you can give some advice, i'll be very gratefull...
Thank you!
The best is you update your stockrom to emui 8 first, after this it should work with customs.
I see there are emui 8 updates, but they all seem to be for 2017 version.
I bought my phone in 2015.
Not sure if it is safe to flash something , that is for the later version.
What do you think?
crystalsun111 said:
I see there are emui 8 updates, but they all seem to be for the 2017 version.
I bought my phone in 2015.
Not sure if it is safe to flash something, that is for the later version.
What do you think?
Click to expand...
Click to collapse
As far as I know, Resurrection Remix, LineageOS, and all other Custom ROMs only work on B896 Version (this is meant for Vodafone). First, you need to have this ROM and only then you can successfully flash Custom ROMS, unless, you're searching for in P8Lite (2017)...
Do read the main part before installing... They should have mentioned it there...

Comprehensive guide and resources for migrating to a custom ROM from stock OREO?

Okay, so I've been trying to get some answers regarding custom ROMs for the past few days but I haven't even got one...and it seems I'm not the only one looking for them. So...lay it in this thread maybe we can start something up.
I am on stock OREO B04, phone's software has never been tampered with anything, TWRP, BL unlock and so on.
This is the premise of the thread, not only for me but for other users who find themselves in the same situation.
Oreo seems to be a bit of a hassle right now for migrating to custom ROMs, and this is not helped by the fact guides in the A7 section are all over the place as well, some may be outdated and there's no clear "Don't use this on x.x version" warning.
I am not even going to attempt to unlock the BL until I clear answer on wether it's possible or not. So let's start with this:
-Is it possible to unlock the BL on OREO?
-If not, what stock official ROM should we install in order to successfuly attempt to unlock the bl?
-Which guide or method is the best for doing so? I've found 2, one from 2016 on MM ROMs and one provided by TurkDevs that seems to work on some Nougat ROMs.
Then comes the recovery section:
-What TWRP should we install on a freshly unlocked device, the official releases, or the Nfound custom ones?
-Also, what are the prerequisites for installing TWRP...I hear that fastboot commands are gone since Nougat and that some flashing methods don't work, then I hear somehow you can do it by bringing back fastboot. How? There's only replies saying "type that command in fastboot" but nobody says if they had it or reinstalled it somehow.
Then comes the ROMs section:
-All custom ROMs seem to require a vendor partition as most if not all of them are Treble based. How do we get that to work?
- I am aware of the fact that the ROM threads have a prerequisites section, but none of them redirect you to a guide on how to get those prerequisites working. I understand that it's not the dev's responsability, I am not bashing anyone here, but a little bit of info cleaning and structuring should be in order in this section.
What I want for me and others in my situation is a clear answer on how to proceed, not a "flash this flash that". There's no secret that the A7 still has life in it especially with the new PIE ROMs.
I've recently seen a reply in one of the threads, encouraging the dev of one of this ROMs to not be disappointed by the seemingly low interest in PIE ROMs. I don't think there's a low interest in them, I think there are users that don't want to risk a bricked phone because of outdated guides and unlcear steps.
There's a lot of confusion going around here so I hope this thread will become a source of updated info on what's possible and what not. Thanks in advance!
Hi, I'm not the best person to help you with this since i've unlocked my Axon 7 a long time ago and I can't remember everything but I will try to help you based on my experience and on what I can remember.
Let's go
Starting with the bootloader, I unlocked mine on stock Nougat B09 using EDL Tool (Oreo wasn't even out when I unlocked my bootloader so I don't know if you can do it while running Oreo but just to be safe you should downgrade to Nougat)
It should be quite easy to unlock the bootloader, here's a simple step by step (please anyone correct me if I'm wrong)
- Download the EDL tool from the link above
- Downgrade your phone to Nougat (Using the updater on the phone itself or an EDL Package with EDL Tool or MiFlash - you can find the stock ROMs on @raystef66 's Download Center
- Once running Stock Nougat, turn on USB Debugging and Allow OEM Unlocking on Developer Settings
- Plug the phone to your computer and open EDL Tool (that should reboot the phone into EDL mode automatically)
- Navigate through the EDL Tool using the number keys on the keyboard, and it should be easy to find the Unlock Bootloader option. Unlock it and you should be done.
Once again that's the way I did it, I don't know if this is the easiest one available. You have more methods available like this one
Now onto the recovery situation, I think each developer recommends a specific TWRP version for their ROM's, like for example
@raystef66 likes NFound's TWRP 3.2.1-8 as you can see on his ROM's posts (check the first line in the installation guide)
@OrdenKrieger likes the official TWRP as you can see on Lineage OS 16.0 post
Generally, official TWRP should work just fine with any ROM.
On a recently unlocked Nougat Stock ROM, I recommend maybe an older version of TWRP, like 3.2.1 for example and you can flash it also using EDL Tool.
But when moving to Pie I recommend you use the latest TWRP version or the version that the ROM developer recommends. You probably know this but you can update your TWRP version by flashing it over the current version you have.
Now about the ROM's, the new ones have a Vendor partition so you have to create it when you're coming from Stock (because our Axon 7 doesn't support Project Treble) and to do that you can use @Oki 's PARTY Tool and after that you can flash the ROM normally, using the proper Bootstack and Modem files.
You could also try GSI's but I can't help you with that because I never tried them.
And this should be all.
I tried to keep it simple for now but i can help you further
I'm not the best person to guide you but at least I tried Feel free to ask me something and good luck!
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
TorqueSsS said:
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
Click to expand...
Click to collapse
I'm glad I could help
Since you're not the only person with questions on how to migrate from stock to custom, I'm thinking about writing a full post so more people can see it.
Btw what method did you use to downgrade to nougat?
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
TorqueSsS said:
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
Click to expand...
Click to collapse
Thanks! That will help me a lot to write a full guide. You'll be credited, don't worry
And yeah, when you migrate to custom roms you'll have to sacrifice camera quality and functionality and also a bit of speakers sound quality (all dolby atmos ports I tried are quite buggy and don't work well ; i only use atmos with the speakers). Headphones sound quality is great though.
If you don't use camera that much (not my case) and you're okay with the speakers sound quality then custom roms are probably the best option out there.
@joaocandeias
I was fully aware of the camera issues I might encounter, this has been the case with my old Mediatek devices when going to custom as well, same camera issues, but at least...it works here. Yeah, I lost some functionality, but to me it's a good trade-off. It can still take snaps and film properly so it's enough for me.
I am kind of going to miss Dolby on speakers (never liked it on headphones though), as it did a really good job for podcast style videos on YT, but it still sounds way better than a lot of phones without it so it's fine. I just need to crank the volume up a little more than usual.
I've heard that treble Pie Roms require a oreo bootloader, is this true? I am still confused how to install on my A2017G. In which order would I install bootloader and vendor partition?

Categories

Resources