Related
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
Thanks in advance,
Federico
Click to expand...
Click to collapse
This Should Help You.
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
can you tell me what rollback package to use? i tried "(FRD-L19&L09, from Android 7.0, EMUI 5.0 to Android 6.0 EMUI 4.1, C900B300, Western Europe)" and didn't work
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Federico Cervelli said:
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Click to expand...
Click to collapse
If you are on a regular version of MM, as I understand it, you can update normally, yes
SharxX8 said:
If you are on a regular version of MM, as I understand it, you can update normally, yes
Click to expand...
Click to collapse
but last time i did it it brang me to test keys .-.
EDIT: i tried and it's all working, Thanks!
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Click to expand...
Click to collapse
I am in a very similar situation and unable to solve this. Could some one help in this?
I had unlocked bootload, TWRP and Root. I decided to unroot and lock the bootloader. So, by following the steps mentioned in a different thread, I could successfully flash Marshmallow B130 through Force Update.
Steps followed:
1. Flash Rollback package
2. Flash Full OTA (Marshmallow on B130) from Huawei website which flashed
Now, the real problem started while trying to upgrade to Nougat.
I tried downloading B350 firmware from Firmware Finder. After slow download, it installs fine. But, after reboot I face below problems.
1. The OS is very sluggish and crashes so often
2. The build number says NRD***-test keys
3. No keyboard installed, so not able to login to Google as well.
4. At this point, Factory Reset, Wipe Cache Partition, rollback everything fails.
I had to unlock the bootloader and again force update Rollback Package and then to Marshmallow B130.
Now, I am stuck with B130. I tried downloading B340 and B361 thru Firmware Finder. Both of them installed but with the same result. I mean No keyboard, Test-keys build, Crashes
My Honor 8 model: FRD-L02
What should I do upgrade to Nougat? I have no confidence in Firmware Finder method. Any help appreciated
It's EMUI 5.0.1 not 5.1, I think.
First of all, sorry for both repeating the topic, and for my ignorance!
I have an Honor 8 which is stuck on FRD-L09C432B394 and Android security patch level: 5 August 2017. I have received at least 2 OTA updates since I purchased the device almost 2 years ago but not since September last year (2017)!
I’m in the UK, I did not do anything with the device since I purchased it, and using the latest HiSuite version (HiSuite 8.0.1.300_OVE), no updates available either!
I downloaded a ROM from // huawei - firmware com/ (Sorry, can’t post links!) which is holds the description:
Build: FRDL09C432B521 800521FRDL19C432B521 800521FRDL02C432B521 800521
Android: 8.x - Oreo
Emui: 8.0
Size: 1.38GB
When I unzip this file I only copied UPDATE.APP to dload on MicroSD card, when trying to update via *#*#2846579#*#*, it starts but then fails at 5%!
Now I did some research and it seems like there’s more files required to update, when I unzip the downloaded ROM I only get the following files though:
full_mainpkg.tag (1KB)
new_filecontext_system (27KB)
new_filecontext_vendor (49KB)
UPDATE.APP (2,920,857KB)
VERSION.mbn (1KB)
And one folder named META-INF containing a few files.
When I did some research it seems like the files required are:
1) update.zip
2) update_full_xxxx_yyyy.zip ("xxxx" and "yyyy" = depending from hardware model/region)
3) update_data_full_public.zip
Where do I get these from? Is it UPDATE.APP or update.zip?
What am I missing? And if anyone knows, why am I not getting the update via HiSuite?
Thank you in advance!
YorkiEg said:
First of all, sorry for both repeating the topic, and for my ignorance!
I have an Honor 8 which is stuck on FRD-L09C432B394 and Android security patch level: 5 August 2017. I have received at least 2 OTA updates since I purchased the device almost 2 years ago but not since September last year (2017)!
I’m in the UK, I did not do anything with the device since I purchased it, and using the latest HiSuite version (HiSuite 8.0.1.300_OVE), no updates available either!
I downloaded a ROM from // huawei - firmware com/ (Sorry, can’t post links!) which is holds the description:
Build: FRDL09C432B521 800521FRDL19C432B521 800521FRDL02C432B521 800521
Android: 8.x - Oreo
Emui: 8.0
Size: 1.38GB
When I unzip this file I only copied UPDATE.APP to dload on MicroSD card, when trying to update via *#*#2846579#*#*, it starts but then fails at 5%!
Now I did some research and it seems like there’s more files required to update, when I unzip the downloaded ROM I only get the following files though:
full_mainpkg.tag (1KB)
new_filecontext_system (27KB)
new_filecontext_vendor (49KB)
UPDATE.APP (2,920,857KB)
VERSION.mbn (1KB)
And one folder named META-INF containing a few files.
When I did some research it seems like the files required are:
1) update.zip
2) update_full_xxxx_yyyy.zip ("xxxx" and "yyyy" = depending from hardware model/region)
3) update_data_full_public.zip
Where do I get these from? Is it UPDATE.APP or update.zip?
What am I missing? And if anyone knows, why am I not getting the update via HiSuite?
Thank you in advance!
Click to expand...
Click to collapse
The only method to install Oreo without unlocking bootloader is to flash via HiSuite... Have you tried?
ScardracS said:
The only method to install Oreo without unlocking bootloader is to flash via HiSuite... Have you tried?
Click to expand...
Click to collapse
I'm not sure if you mean flash via HiSuite as in downloading the Oreo ROM then use HiSuite to install it? Or just use HiSuite to check for updates and let it install it?
I do have the latest version of HiSuite (8.0.1.300_OVE) installed. Checking for updates through the software says that I've got the latest official version
YorkiEg said:
I'm not sure if you mean flash via HiSuite as in downloading the Oreo ROM then use HiSuite to install it? Or just use HiSuite to check for updates and let it install it?
I do have the latest version of HiSuite (8.0.1.300_OVE) installed. Checking for updates through the software says that I've got the latest official version
Click to expand...
Click to collapse
Oh, I'm sorry.
You could try method posted on my signature for flashing b399 and then watch if it update to b407
ScardracS said:
Oh, I'm sorry.
You could try method posted on my signature for flashing b399 and then watch if it update to b407
Click to expand...
Click to collapse
You Sir are a genius! :good::good:
I didn’t have the time to try it last week but I just did and miraculously your 2 Update.app files have worked and flashed my device to B399!
Immediately after I got an OTA update to B404! But stuck there unfortunately! No updates available OTA nor on HiSuite after B404! Also trying to instal B407 via dload keeps failing at 5% every time! I read in your thread saying you haven’t done anything to the B399 file? Just deleted ‘Other files’ and rezipped? It worked anyway! Would be great if you could advise me on how to do it for a B407 or B521! If not, you’re still a genius!
Stuck on B404 now! An upgrade from B394, but wouldn’t mind moving up the line a bit!
YorkiEg said:
You Sir are a genius! :good::good:
I didn’t have the time to try it last week but I just did and miraculously your 2 Update.app files have worked and flashed my device to B399!
Immediately after I got an OTA update to B404! But stuck there unfortunately! No updates available OTA nor on HiSuite after B404! Also trying to instal B407 via dload keeps failing at 5% every time! I read in your thread saying you haven’t done anything to the B399 file? Just deleted ‘Other files’ and rezipped? It worked anyway! Would be great if you could advise me on how to do it for a B407 or B521! If not, you’re still a genius!
Stuck on B404 now! An upgrade from B394, but wouldn’t mind moving up the line a bit!
Click to expand...
Click to collapse
For b406 and/or b407 I think you have to expect a bit
ScardracS said:
For b406 and/or b407 I think you have to expect a bit
Click to expand...
Click to collapse
I’m not sure what do you mean? Do I need to expect a bit of patience to get B406/7? I don’t have any patience left, I've had enough with Huawei
I’ve downloaded about 6 different firmware files from B405 to B521, I always tried the FullOTA-MF files first, then OTA-MF, all keeps failing at 5% but I ALWAYS get the ‘Software install failed’ message at 5% every time I try the SD Card\dload\UPDATE.APP method Are the firmware files I’m downloading corrupt? Your files did work so I don't think it's anything to do with my phone, but your files are the only ones that worked! I can't get my head around it
YorkiEg said:
I’m not sure what do you mean? Do I need to expect a bit of patience to get B406/7? I don’t have any patience left, I've had enough with Huawei
I’ve downloaded about 6 different firmware files from B405 to B521, I always tried the FullOTA-MF files first, then OTA-MF, all keeps failing at 5% but I ALWAYS get the ‘Software install failed’ message at 5% every time I try the SD Card\dload\UPDATE.APP method Are the firmware files I’m downloading corrupt? Your files did work so I don't think it's anything to do with my phone, but your files are the only ones that worked! I can't get my head around it
Click to expand...
Click to collapse
You first have to check if installation of each firmware is approved using Firmware Finder app. If it says it's not approved, it will fail at 5%, so there is no point downloading them
For me on my L09-C432, 406 was approved but was not displayed in system update app, I had to use Firmware Finder proxy to send it to system update app. Then I got 407, and could update to Oreo using hisuite on PC.
This method will fail on newer versions, but if 406 is approved for you and not displayed in system update app you can try it.
pix106 said:
You first have to check if installation of each firmware is approved using Firmware Finder app. If it says it's not approved, it will fail at 5%, so there is no point downloading them
For me on my L09-C432, 406 was approved but was not displayed in system update app, I had to use Firmware Finder proxy to send it to system update app. Then I got 407, and could update to Oreo using hisuite on PC.
This method will fail on newer versions, but if 406 is approved for you and not displayed in system update app you can try it.
Click to expand...
Click to collapse
That’s what’s frustrating me, all the firmware files I’ve downloaded are approved for my device Or so does Firmware Finder app says! Yet they all fail to install at 5%!
Proxy method doesn’t work on B404, or at least not working for me So nothing is working now
I’ve had enough with this phone, just to avoid smashing it into a wall next time it drives me crazy, I’m looking to get another phone, Xiaomi Mi A2 might be the one. Still looking though
Successful update
Frustrated as I was I decided to try one last time and I’m running Oreo now
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK), let it preform OTA update back to Android 7 (B380 if I remember correctly) then use Firmware Finder application's in-app proxy to let the phone do the update at this stage! And it worked!
It downloaded the ROM files then when download completed it said the package has changed and requested to download again! I downloaded that and it started installation! Everything went well during installation but at the end it said it has failed because it could not find the update package I thought it failed and restarted the device only to find it running Android 8 and EMUI 8! Full reset and all working flawlessly
HiSuite acknowledges the update and offers to rollback to B407 if you’re having problems! Please note that I was stuck on B394! So even rolling back would be an upgrade
I’ve tested different apps, NFC (I never use it for contactless payments though so can’t confirm that, but I can’t see why it wouldn’t work) Also GPS and everything’s working just fine! Only issue is/was battery draining but that’s due to the auto launch in battery settings! I changed some of the application settings into manual launch and all great now!
Thank you for all those who helped :good: And hopefully this might help some of the frustrated Honor 8 users like myself! And hopefully won’t be stuck on B521 now!
YorkiEg said:
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK)
Click to expand...
Click to collapse
Sorry for the possibly stupid question, but how did you find/apply the rollback package? Was it through firmware finder or is there some other way?
Himmagery said:
Sorry for the possibly stupid question, but how did you find/apply the rollback package? Was it through firmware finder or is there some other way?
Click to expand...
Click to collapse
No such thing as stupid question! We all need to start somewhere
Finding the rollback package is via the official Honor support website for (Preferably) the country where you purchased your handset from. Or if it was EU, any EU country.
Rollback process will be executed by downloading and unzipping 2 files, the Honor 8_Rollback Package_FRD-L09_from Android 7.0 EMUI 5.0 to Android 6.0 EMUI 4.1_C900B300 (Around 75 MB in size) and the Honor 8_Firmware_FRD-L09_Android 6.0_EMUI 4.1_CXYZB131 (Around 1.75GB in size).
Next you should have a MicroSD Card installed, formatted, and create a folder on root called dload.
Then Unzip the files you downloaded, will get you 2 Update.app files, copy the first one (From C900B300) to the dload folder, switch phone off, press Volume-, Volume+ and the Power button and don’t let go till system starts updating, this one won’t take long.
When finished, format you MicroSD Card, create dload folder again, then copy the second Update.app file (From CXYZB131) into the folder, same button combination to update. This update will take longer.
When finished, try Firmware Finder app immediately if you can and use the in-app proxy method to let your phone do the update, if it didn't work, let the phone do OTA update but don’t let it update too many times because Firmware Finder doesn’t work with newer System Update apps.
Hope that helps. And good luck :good:
YorkiEg said:
Frustrated as I was I decided to try one last time and I’m running Oreo now
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK), let it preform OTA update back to Android 7 (B380 if I remember correctly) then use Firmware Finder application's in-app proxy to let the phone do the update at this stage! And it worked!
Click to expand...
Click to collapse
Thanks for the post, finally got some time where I could try this out and i'm now upgraded to 8.0 from the B394 I was previously stuck on.
I noticed a huge lag when first running 8.0 but it seems to have settled.
For me everything seems to be running just fine, all my apps works, all hardware works and, as far as I can see in 0.5 days use the phone runs it all about as good as it did on 7.0 after the initial lag that is
darklighthim said:
Thanks for the post, finally got some time where I could try this out and i'm now upgraded to 8.0 from the B394 I was previously stuck on.
I noticed a huge lag when first running 8.0 but it seems to have settled.
For me everything seems to be running just fine, all my apps works, all hardware works and, as far as I can see in 0.5 days use the phone runs it all about as good as it did on 7.0 after the initial lag that is
Click to expand...
Click to collapse
Glad it worked for you :good:
The fingerprint scanner was a bit of a hit and miss for me when I first updated but it wasn't bad enough to mention, and it has settled now! Other than that, still running smoothly
Guys! Hello again... I'm still blocked with android 8.1 on elm29 sp5c900. I understand that c900 is global, Huawei still tells me that an update will come soon, but nothing. Erecovery doesn't find nothing on server and hisuite doesn't help me at all. Now the question... Is there a problem if I download an update file from firmware finder and install it with forced update (power plus volume buttons)? Can I brick the device, since I don't have a backup file or original software
shtresatu said:
Guys! Hello again... I'm still blocked with android 8.1 on elm29 sp5c900. I understand that c900 is global, Huawei still tells me that an update will come soon, but nothing. Erecovery doesn't find nothing on server and hisuite doesn't help me at all. Now the question... Is there a problem if I download an update file from firmware finder and install it with forced update (power plus volume buttons)? Can I brick the device, since I don't have a backup file or original software
Click to expand...
Click to collapse
Firmware downloaded through Firmware finder won't install via forced update, you can use service ROM (download though androidhost dot ru) and place it on usb OTG and force it. Or you can use patched Hisuite method to update https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/page132
Yes it can brick, anything can happen but very unlikely, just backup your device through Hisuite before trying that if you want to keep your personal data(won't back up firmware, only apps, contacts etc.)
C900 hw/normal does not get any update.
Just force some updated base via dload package or via forced hisuite with dns spoofed.
Thanks for your answers! So... The steps will be... 1. Download "update full base. app"
2. Place it on root folder in dload folder
3. Update it via forced update (power button plus both volume buttons)
I've found on firmware finder update.app file. This works via dload method?
madoxx77 said:
Firmware downloaded through Firmware finder won't install via forced update, you can use service ROM (download though androidhost dot ru) and place it on usb OTG and force it. Or you can use patched Hisuite method to update https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/page132
Yes it can brick, anything can happen but very unlikely, just backup your device through Hisuite before trying that if you want to keep your personal data(won't back up firmware, only apps, contacts etc.)
Click to expand...
Click to collapse
Thanks for the link... I will try this too
shtresatu said:
Thanks for your answers! So... The steps will be... 1. Download "update full base. app"
2. Place it on root folder in dload folder
3. Update it via forced update (power button plus both volume buttons)
I've found on firmware finder update.app file. This works via dload method?
Click to expand...
Click to collapse
For dload, you ll have to use an USBOTG, exfat formatted.
On 8.1, Use a 9.0 dload's update.app .
Once on 9.0, use a 9.1 dload's update_sd.zip
Alternative is to use forced hisuite.-If so uodzte first to 9.0 then 9.1.
oslo83 said:
For dload, you ll have to use an USBOTG, exfat formatted.
On 8.1, Use a 9.0 dload's update.app .
Once on 9.0, use a 9.1 dload's update_sd.zip
Alternative is to use forced hisuite.-If so uodzte first to 9.0 then 9.1.
Click to expand...
Click to collapse
Thanks a ton. I will try with dload. Is more simple
Forced hisuite doesn't work! Gives me only update to android 8.0. Firmware finder on pc doesn't give me my version sp5c900, so I can't download any firmware. Now I don't trust FF on phone neither. What if this gives wrong firmware, since my emui version is not suported. ****
oslo83 said:
C900 hw/normal does not get any update.
Click to expand...
Click to collapse
Meaning there is no update on hicloud server available for C900.
True. Damn huawei ****ty version.
Thx a lot #oslo for advices
I've spoked (finally) with someone from Huawei on chat, and after verifying my serial number she told me that my phone is a demo version. F%$&. So, no Android 9 for me. Still, my phone works flawlessly. Since I'm stuck on 8.1 I want to root it and play a little more. Can you give me an idea how to root it? Thanks
shtresatu said:
I've spoked (finally) with someone from Huawei on chat, and after verifying my serial number she told me that my phone is a demo version. F%$&. So, no Android 9 for me. Still, my phone works flawlessly. Since I'm stuck on 8.1 I want to root it and play a little more. Can you give me an idea how to root it? Thanks
Click to expand...
Click to collapse
First, is this device is with an unlocked bootloader ? (and/or do you have the unlock code ?)
To check bootloader/phone status, boot to fastboot/bootloader mode :
Plug device to PC with Hisuite, reboot P20 and Hold volumeDown on P20 until it boot on white screen ;
What is your Phone status ?
Sorry for late response. Bootloader is locked.
"phone locked.
FRP UNLOCKED"
And I don't have bootloader code.
So you won't mind that dload packages are locking back bootloader as it is already locked...
oslo83 said:
So you won't mind that dload packages are locking back bootloader as it is already locked...
Click to expand...
Click to collapse
Nope... I just want to root it so I can use Xposed
Hi guys,
Happy new year to all of you.
So... My story :
I downgraded my ELS-NX9 via HiProxy , but i accidentally choose LGRP6 instead of LGRP4 and voila (10.1.0.136(C432E8R6P1)) - my phone was stuck on boot logo.
Then , somehow i managed to turn it on , but the side effects:
Restarting on every 30 seconds.
No IMEI
No Base software version
No Cust software version
eRecovery failed to get the package info
No sound.
What i've tried:
I've tried to put another software via OTG cable , i downloaded the software from Firmware Finder, but it's says that the update package has not been found.
Then i've downloaded another software with dload from Easy-Firmware (10.1.0.131(C432E8R6P1)). but it's says The version is incompatible with the current one.
Any ideas how can i fix this mess ?
Thanks and Regards,
Kris
If eRecovery isn't working I think you might need to visit the huawei store. To my understanding, eRecovery is the kirin version of Qualcomm download mode, aka your last line of defense.
krissko0o said:
Hi guys,
Happy new year to all of you.
So... My story :
I downgraded my ELS-NX9 via HiProxy , but i accidentally choose LGRP6 instead of LGRP4 and voila (10.1.0.136(C432E8R6P1)) - my phone was stuck on boot logo.
Then , somehow i managed to turn it on , but the side effects:
Restarting on every 30 seconds.
No IMEI
No Base software version
No Cust software version
eRecovery failed to get the package info
No sound.
What i've tried:
I've tried to put another software via OTG cable , i downloaded the software from Firmware Finder, but it's says that the update package has not been found.
Then i've downloaded another software with dload from Easy-Firmware (10.1.0.131(C432E8R6P1)). but it's says The version is incompatible with the current one.
Any ideas how can i fix this mess ?
Thanks and Regards,
Kris
Click to expand...
Click to collapse
Inside of dload folder do you have update_sd_base.zip + ELS-N29_hw_eu folder ?
dload
+ update_sd_base.zip
+ ELS-N29_hw_eu
++ update_sd_cust_ELS-N29_hw_eu.zip
++ update_sd_preload_ELS-N29_hw_eu_R6.zip
unfortunately it's not working , when i try to update via eRecovery it's saying ""
kilroystyx said:
Inside of dload folder do you have update_sd_base.zip + ELS-N29_hw_eu folder ?
dload
+ update_sd_base.zip
+ ELS-N29_hw_eu
++ update_sd_cust_ELS-N29_hw_eu.zip
++ update_sd_preload_ELS-N29_hw_eu_R6.zip
Click to expand...
Click to collapse
Yes
krissko0o said:
Yes
Click to expand...
Click to collapse
I though you downloaded firmware for C432 location (hw/eu) but according your prints was for C185 (hw/meafnaf)
Your device is C432 or C185?
kilroystyx said:
I though you downloaded firmware for C432 location (hw/eu) but according your prints was for C185 (hw/meafnaf)
Your device is C432 or C185?
Click to expand...
Click to collapse
That's the point mate , the current firmware is C432 but when i try to install C432 i'm receiving error incompatibility with the current version
Similar issue with me.Any one can help me on that
wut_tah said:
Similar issue with me.Any one can help me on that
Click to expand...
Click to collapse
I'm trying another firmware now and if it's not working i'm sending my phone for repair , it seems that's the only way, as basically my phone does not have Cust version and Base version which is the most important thing when you are updating , as the update package is checking first if the Base and Cust version are similar to the ones from the update package.
krissko0o said:
I'm trying another firmware now and if it's not working i'm sending my phone for repair , it seems that's the only way, as basically my phone does not have Cust version and Base version which is the most important thing when you are updating , as the update package is checking first if the Base and Cust version are similar to the ones from the update package.
Click to expand...
Click to collapse
Thank a lot Shock!!!!
I rushed and bought the tencent version, and apparently it is using WW firmware. Everythig seems fine since I dont really want to unlock bootloader and all, but can I update the sofware by OTA? If I can't, how to do it manually?
Download it from the Asus site, put it on the sdcard, the phone will detect it, and then follow the prompts. OTA isn't possible with the "wrong" firmware, though.
twistedumbrella said:
Download it from the Asus site, put it on the sdcard, the phone will detect it, and then follow the prompts. OTA isn't possible with the "wrong" firmware, though.
Click to expand...
Click to collapse
Any links to the asus site? Manual update is fine too, I dont think too much, only for gaming.. thanks in advance
Edit: found the site
https://rog.asus.com/phones/rog-phone-5-model/helpdesk_bios
Currently downloading, after this the phone will automatically detect the firmware even when its .zip file? Or how?
Edit 2: the device will automatically detect the firmware .zip after restarting, and I have updated successfully! Thanks
well for me he doenst detect idk why
Gokual said:
well for me he doenst detect idk why
Click to expand...
Click to collapse
You must put the file outside of the download folder
So in internal memory>
After a restart, the phone will detect the file automatically