I installed Nougat and EMUI 5.0 via the HiCare app on my FRD-L09. I had it running perfectly, then I decided I wanted to root. I hazzled around and finally got TWRP working, but I don't remember completely what happened, but something happened and I accidentally deleted the system partition. I have tried downloading the firmware for my phone and putting it on the sdcard in dload and then press Power + Volume Up + Volume Down. Unfortunately this failed immediately and I got something like "Install failed. Incompatible with your version." I still have access to TWRP so I tried flashing different firmwares (Marshmallow Downgrade Package, Nougat Firmware, Marshmallow Firmware) but they all failed. When I try to boot the phone now, I press the power button when it says my device can't be trused blah blah blah and it just says "Your device is booting now..." forever until it reboots and the same happens. Altough I can still access TWRP with Power + Volume Up.
So my question is, how do I get my phone back to stock firmware?
Check second post of this thread
ViCioPT said:
Check second post of this thread
Click to expand...
Click to collapse
What do you want me to do? Download the rollback package and Marshmallow firmware or try the other version of TWRP?
So I found a Nougat Beta Firmware that is supposed to be installed on phones in India, but I flashed it via TWRP and I now have a working OS on my phone. However, there is one problem. My build number is "NRD90M test-keys" and there is no update option in settings and a lot of stock apps are missing (clock, backup & restore etc.). I guess I should create a new thread on how to get on the right firmware? I'm new to XDA Forums.
FreeLineTM said:
So I found a Nougat Beta Firmware that is supposed to be installed on phones in India, but I flashed it via TWRP and I now have a working OS on my phone. However, there is one problem. My build number is "NRD90M test-keys" and there is no update option in settings and a lot of stock apps are missing (clock, backup & restore etc.). I guess I should create a new thread on how to get on the right firmware? I'm new to XDA Forums.
Click to expand...
Click to collapse
You installed a rollback firmware probably. I advise you to rollback to Android 6 and afterwards install the nougat update via the official methods.
Avoid open threads for every question, there is a search button to be used before shooting questions and opening threads.
Look for the rollback for your phone version.
ViCioPT said:
You installed a rollback firmware probably. I advise you to rollback to Android 6 and afterwards install the nougat update via the official methods.
Avoid open threads for every question, there is a search button to be used before shooting questions and opening threads.
Look for the rollback for your phone version.
Click to expand...
Click to collapse
I already found the rollback for my version and tried putting it in dload but it failed and said it was incompatible with my version.
So I just tried the rollback package again and it installed perfectly. I'm on FRD-L09C900B300. Doing the firmware itself in a moment. Thank you for bothering taking a look even though I pretty much managed myself. ? @ViCioPT
FreeLineTM said:
So I found a Nougat Beta Firmware that is supposed to be installed on phones in India, but I flashed it via TWRP and I now have a working OS on my phone. However, there is one problem. My build number is "NRD90M test-keys" and there is no update option in settings and a lot of stock apps are missing (clock, backup & restore etc.). I guess I should create a new thread on how to get on the right firmware? I'm new to XDA Forums.
Click to expand...
Click to collapse
Just as future reference, when you flash an OTA based update.zip (not a full system update) in Twrp you also have to flash the data update to install the majority of the stock apps.
So I got an honor 6x that I can't do anything with. I can't flash any ROMs or firmware here's the weird part of it.
Its on some version of EMUI that I can't have the system update menu and it has a button for app twin. It says BLN-L24C567B366 as the model number. Speakers don't work. I can't play videos on it and I can't use the camera in any app.
Here's the really weird part:. If I wipe all partitions and try to flash a room it boots to the same EMUI firmware not the custom rom I can't do anything to change what the rom is. It's like it's stuck in that weird Frankenstein EMUI firmware that I don't even know how I got. I tried restoring anback up cause I formatted my data partition on accident causing it not to boot or something and the backup I restored was not the backup that I made . The backup I made was a stock backup onto an SD card. When I restore it it's rooted and has some downloaded apps on it. And a different launcher. Not what I backed up originally.
I'm at a loss here. What do I do? Ihave full access to adb to flash with fastboot and can get into twrp or stock recovery. No ROMs I flash will work. In twrp it says it was successful. Ut when I boot it doesn't boot to that room, it boots to the weird emui os I can't get rid of.
Has anyone run into this issue or know how to fix it?
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
All my update.app files get stuck at 5% too. And I know honor/Huawei won't repair it cause the warranty is void or if they can they would charge you.
Honestly get the Moto G5s plus. Get the unlocked version at best buy if you're in the states. It's 239 for the 32gb/3gb. Ram model and 299 for 64gb and 4gb. Best budget phone you can get and dual cameras. The ROM support isn't as big as the honor but it is easy to unlock the bootloader and do things. My only ROM issue I've had with this was trying to update magisk the phone had to reboot to install and after that, I had a lock screen set up btw, when I went to enter the pin the screen would go black, the phone would buzz, and go back to the lock screen. And I tried restoring a backup I made but the phone wouldn't boot stuck at the boot logo before the animation.
But the stock firmware I acquired on XDA along with the steps to flash in adb every file in the stock firmware fixed it with no problems at all so at least there's an easy way to restore the stock firmware for my new phone. It's way better than the honor 6x
Seriously tho check out the Moto G5s plus. Out of the box it has Android 7.1.1 mostly stock without all of Google's bloatware. Front mounted fingerprint sensor that you can you for the home, recent apps and back button, and can lock the screen with it if you have fingerprint set up and activate the Google assistant. It also has a notification light that you need root to use. But it has this cool "always on display" type thing that shows a clock and notifications when you move the phone or get a notification. It isn't an AMOLED display tho. It's. 1920x1080p one. Ips good viewing angles. Honestly this is the best phone I've ever used. And it has a Motorola turbocharger in the box. It's really worth it
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
i think it could be an issue with the kernel cause the eliteRom has a custom kernel in it.. i have the update.app file for the BLN-L24C567B366 ad B365 files that i can extract and give you all the images that they have and maybe try to get the stock kernel somehow that might help?
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
Try flashing every single update version until one of them works. Once youve found one that works follow this guide: https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
xinoxkai said:
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
Click to expand...
Click to collapse
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
xSpartacusx said:
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
Click to expand...
Click to collapse
Yes, firmware finder showed me 3 zips, update.zip, update_data_full_public.zip and update_full_BLN-L24_hw_usa.zip, the later 2 are the "alternative zips". Just TWRP flash them.
Also, update_full_BLN-L24_hw_usa.zip might throw an error when flashing it, don't worry, by the stage it fails in its script it already did what it was expected to do and you will not have further problems.
do i need the stock recovery flashed in order to do dload?
well i followed the first half of your guide and it successfully "updated" but my storage is encrypted
xSpartacusx said:
do i need the stock recovery flashed in order to do dload?
Click to expand...
Click to collapse
Not really, I did it when I had TWRP installed
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
xSpartacusx said:
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
Click to expand...
Click to collapse
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
xinoxkai said:
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
RedSkull23 said:
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
xinoxkai said:
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
Click to expand...
Click to collapse
Good one dude, maybe FF proxy method could help xSpartacusx to solve his issue too!
Hey guys,
Hopefully someone can help me with my problem. So i did the following:
To get rid of the 7 day Block of oem-unlocking on my s8+ i downgraded back to Nougat. From here on I flashed TWRP + rooted my device with magisk. After That i flashed the RENOVATE_ICE_G95X-7.5 rom + the Flashable_G95xF_FD_Firmware_TWRP_AQL5_r8 Firmware. I've let my Phone start up and went back to TWRP To Update the rom to RENOVATE_ICE_G95X-10.1. To this point everything Worked fine, the Phone Boots completely fine. Now to my problem: im Sitting on the actual stable rom but with the Baseband-version of Nougat which is AQL5. When i try to Flash the actual Firmware (CRC7 or CRD7) via TWRP my Phone gets stuck on the first Samsung Logo and Shows the following red Message: "Only official released binaries are allowed to be flashed". I would be glad for any help.
If you can find a standalone modem file from the ROM you mentioned you should be able to flash it in TWRP recovery. Last time I did this was on a Note 3. I think that the process should be the same with S8.
Can't seem to find one, but i found out that the same error occurs when installing other custom-roms like the King Oreo Rom which installs the newest Bootloader and Modem via Aroma installer. Only solution after that is to Flash Nougat again via Odin.
Hi all
Currently on Batman V2.0.0 Oreo - S8+ SM-G955F
Reason for change is due to poor battery life and intermittent fingerprint scanner.
I have downloaded stock Nougat 7.0 - G955FXXU1AQF7_G955FOXM1AQF7_BTU, flashed this via Odin and everything booted up fine. The next step was to root and device and install twrp.
1. Downloaded TWRP and installed
2. Installed dm-verity and force encryption disabler
3. flashed Magisk.zip
had full access to twrp and had root.
Now i am trying to flash batman V1.50 via twrp. The installation goes fine, when rebooted it stays on the Samsung screen. it will not let me load a OS. The system states no OS installed. i have tried with 2 other Nougat roms and still no joy, i even flashed the correct bootloader and modem and still hangs on logo. is there something i am missing here? all your help would be appreciated. Oreo update is not for me.
Restored a twrp backup to go back to my working version of batman oero again, stuck with this until a solution
just a update, managed to sort it out, all working with Nougat and it is stable
luv2vexx said:
just a update, managed to sort it out, all working with Nougat and it is stable
Click to expand...
Click to collapse
hello, can you share how you solve the problem? thanks
luv2vexx said:
just a update, managed to sort it out, all working with Nougat and it is stable
Click to expand...
Click to collapse
How ?
Last year i rooted my Note 8 using the SamFail V3 method, in anticipation of the Pie & OneUI update, I am attempting to reset to stock firmware to allow my device to receive OTA updates. However, Odin is failing to flash the stock firmware onto my device, I have tried every firmware version I can get my hands on, and still Odin fails with Device info or Write Error. Has anyone encountered this, some guidance would be most appreciated.
Resources:
SamFail Root Method
Egg_Bagel said:
Last year i rooted my Note 8 using the SamFail V3 method, in anticipation of the Pie & OneUI update, I am attempting to reset to stock firmware to allow my device to receive OTA updates. However, Odin is failing to flash the stock firmware onto my device, I have tried every firmware version I can get my hands on, and still Odin fails with Device info or Write Error. Has anyone encountered this, some guidance would be most appreciated.
Resources:
SamFail Root Method
Click to expand...
Click to collapse
You're using the wrong odin.. Try the newest odin.
This works for me, but I'm assuming you have 950U version. I included CRK1 to help you, as well as the Odin that is patched and works for me every time. https://bit.ly/2DBbCTP