Related
Hi everyone, in order to use all of my favorits xposed modules, i want to go back to android 6. I found lot of guides for rollback but my problem is Im on twrp, root and with a unlock bootloader. So i don't know how to proceed.
Can i flash an older Rom directly with twrp?
EVA L09 C33B363
Android 7.0
Emui 5.0.1
TWRP
ROOT
STOCK ROM
BOOTLOADER UNLOCK
Thanks
Thom--as07 said:
Hi everyone, in order to use all of my favorits xposed modules, i want to go back to android 6. I found lot of guides for rollback but my problem is Im on twrp, root and with a unlock bootloader. So i don't know how to proceed.
Can i flash an older Rom directly with twrp?
EVA L09 C33B363
Android 7.0
Emui 5.0.1
TWRP
ROOT
STOCK ROM
BOOTLOADER UNLOCK
Thanks
Click to expand...
Click to collapse
First you must flash stock recovery. You can extract from another full rom 7.0
Second you must have downgrade pack for your region and mobile operator.
Next you must have full rom 6.0 for your region.
You must have all file because you don't want debrand your firmware
Thanks, actually if i want debrand my phone whats the diference? Because I think I don't care...
Also, where can i find all of these files you write about?
I'm really lost with all firmware versions ... Does it matter if my version is EVA L09 C33B363 and i flash stock recovery from another version??
Also, my bootloader is locked, do I have to relock it? Does it even possible??
Thom--as07 said:
Thanks, actually if i want debrand my phone whats the diference? Because I think I don't care...
Also, where can i find all of these files you write about?
I'm really lost with all firmware versions ... Does it matter if my version is EVA L09 C33B363 and i flash stock recovery from another version??
Also, my bootloader is locked, do I have to relock it? Does it even possible??
Click to expand...
Click to collapse
If you have locked you must unlock again. All file you can take from forum. Debrand it's unlock warranty and sometime you loose your guarantee. But what region you from
chudy_85 said:
If you have locked you must unlock again. All file you can take from forum. Debrand it's unlock warranty and sometime you loose your guarantee. But what region you from
Click to expand...
Click to collapse
My bad, i wanted to write "Also, my bootloader is unlocked"
No need my phone isn't under guarantee anymore, I'm from France
So what's the steps to follow? and how??
thanks
Thom--as07 said:
My bad, i wanted to write "Also, my bootloader is unlocked"
No need my phone isn't under guarantee anymore, I'm from France
So what's the steps to follow? and how??
thanks
Click to expand...
Click to collapse
Here you have how debrand
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
If you debrand you can then flash stock recovery flash b300 and then b136 and do it wipe in stock recovery.
When you want debrand first you see your cust be c900 and then you must flash stock recovery do it wipe system/data and cache
If you do it your cust change to c432 and then must check your region using dial pad
*#*#2846579#*#* then push 3 and 4
If you see your vendor: hw and country: Europe
You can downgrade to b300 and then to b182
You lose your theme and you see ugly icon then do it wipe system/data and cache in stock recovery
After this you have update to b383 then b386 next to b391 and final to b393 or b394
I have b393
chudy_85 said:
Here you have how debrand
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
If you debrand you can then flash stock recovery flash b300 and then b136 and do it wipe in stock recovery.
When you want debrand first you see your cust be c900 and then you must flash stock recovery do it wipe system/data and cache
If you do it your cust change to c432 and then must check your region using dial pad
*#*#2846579#*#* then push 3 and 4
If you see your vendor: hw and country: Europe
You can downgrade to b300 and then to b182
You lose your theme and you see ugly icon then do it wipe system/data and cache in stock recovery
After this you have update to b383 then b386 next to b391 and final to b393 or b394
I have b393
Click to expand...
Click to collapse
Ok.... So I think there is something i done wrong...
I have flash OEM info OEM info from this thread with TWRP...
Now my phone is stuck on huawei erecovery with the EMUI logo and each time I reboot it reboot on that recovery. I can't access to TWRP...
Bootloader and FRD are still unlocked, how can i restore my phone?
thanks
Hi Guys,
I am on moonlight rom and I want to go back completely to stock (no root, relock bootloader and format everything) with cust C02 (Vodafone). I am now on cust C432, how can I do that? Could you link all the files I need please?
Thanks in advance,
Carlo
carlese said:
Hi Guys,
I am on moonlight rom and I want to go back completely to stock (no root, relock bootloader and format everything) with cust C02 (Vodafone). I am now on cust C432, how can I do that? Could you link all the files I need please?
Thanks in advance,
Carlo
Click to expand...
Click to collapse
With HWOTA you can go back to stock Nougat ROM you had before installing Moonlight:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you then need to rebrand to Vodafone, you can do it via Rollback - but you will need MM oeminfo for Vodafone cust:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Thanks but the second part shows how to get C432 not C02.. Can I use srk tool to do this after the hwota part? I have already downloaded the latest Vodafone rom (3 zips)..
carlese said:
Thanks but the second part shows how to get C432 not C02.. Can I use srk tool to do this after the hwota part? I have already downloaded the latest Vodafone rom (3 zips)..
Click to expand...
Click to collapse
As I wrote above, 2nd link points to the rebranding method but for rebranding you would need oeminfo for Vodafone cust, for Android 6 (at the point where the method points to c432 oeminfo).
The same method but to use different oeminfo with the corresponding Android 6 ZIPs for Vodafone.
AFAIK, you can't rebrand just with ZIPs, without flashing oeminfo - but I don't know where you can find oeminfo for Vodafone cust.
Btw, when rebranding from Vodafone to c432 you also had to flash c432 oeminfo, didn't you?
To see what you really have, you can check with the following commands in the Fastboot
Code:
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION
Hey everyone,
So, a couple months back I rebranded my EVA-L09 to a VIE-AL10 through the rebrand tool.
A couple weeks back I wanted to revert back to EVA-L09 to go back to Magic Rainbow v4 or v3.
I failed in trying to rebrand it back and ended up where I am now, I have TWRP installed, I can do the dload methods to install whatever, but I can't for the life of me get any ROM or firmware to boot. It either doesn't go past the "Your device is not trusted" screen or it hangs at the boot animation.
Extra notes: Yes I was on Oreo when I tried to revert, I am currently not on Oreo as I tried to flash a Nougat VIE-AL10 firmware to attempt to get the phone to at least boot to a usable state for the time being, however now it's stuck on a boot animation.
Would appreciate any help,
Cheers.
Update:
I tried to follow this: https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2
But as mentioned above the phone hangs on "Your device is booting now..." after HWOTA copies the Nougat firmware files.
gamr13 said:
Hey everyone,
So, a couple months back I rebranded my EVA-L09 to a VIE-AL10 through the rebrand tool.
A couple weeks back I wanted to revert back to EVA-L09 to go back to Magic Rainbow v4 or v3.
I failed in trying to rebrand it back and ended up where I am now, I have TWRP installed, I can do the dload methods to install whatever, but I can't for the life of me get any ROM or firmware to boot. It either doesn't go past the "Your device is not trusted" screen or it hangs at the boot animation.
Extra notes: Yes I was on Oreo when I tried to revert, I am currently not on Oreo as I tried to flash a Nougat VIE-AL10 firmware to attempt to get the phone to at least boot to a usable state for the time being, however now it's stuck on a boot animation.
Would appreciate any help,
Cheers.
Click to expand...
Click to collapse
EVA is P9, VIE is P9 Plus
Don't mix firmwares, you wll (no wonder if you really mixed), brick the phone
One procedure is for P9 = EVA (and this is P9 portal here):
rebranding from EVA L09/L19 to EVA AL00c00b535 and back
https://forum.xda-developers.com/p9-plus/development/rebrand-update-tool-hwota7-p9-plus-vie-t3843930
The other is for P9 Plus = VIE (different phone, eg bigger display)
rebranding from VIE L09/L29 to VIE AL00c00b535 and back
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
zgfg said:
EVA is P9, VIE is P9 Plus
Don't mix firmwares, you wll (no wonder if you really mixed), brick the phone
One procedure is for P9 = EVA (and this is P9 portal here):
rebranding from EVA L09/L19 to EVA AL00c00b535 and back
https://forum.xda-developers.com/p9-plus/development/rebrand-update-tool-hwota7-p9-plus-vie-t3843930
The other is for P9 Plus = VIE (different phone, eg bigger display)
rebranding from VIE L09/L29 to VIE AL00c00b535 and back
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Click to expand...
Click to collapse
I was reading through the first link there, as mentioned in the second post I made in here. After following the steps one-by-one the device is stuck at "Your device is booting now..."
gamr13 said:
I was reading through the first link there, as mentioned in the second post I made in here. After following the steps one-by-one the device is stuck at "Your device is booting now..."
Click to expand...
Click to collapse
Be more specific, confirm
- Your phone is P9 or P9 Plus?
If P9, was it L09 (single SIM) or L19 (dual SIM)
- On exactly which Chinese Oreo have you been (cannot be VIE, you must well know what you exactly had and what you were flashing), was it EVA -AL00c00 or what and which build number bXX it was
- Did you go to some Open Kirin/AOSP custom ROM or stayed on that stock Chinese ROM?
You first had to come back to Chinese stock Oreo, not downgrading to Nougat directly from Open Kirin / AOSP
- Downgrading consists of several steps, HiSuite to go to Chinese Nougat and then HWOTA7 to rebrand to eg c432 Nougat.
Up to each step did you exactly do when you got stuck in Booting?
-More precisely, if you downgraded by HiSuite to AL10c00 Nougat, did it boot successfully (or were you here stuck at booting)?
If that step was successful, which (full build name and number) you were flashing by HWOTA7 to rebrand to from the Chinese Nougat?
-Have you tried to switch off and boot again?
Have you tried booting to Recovery and do Factory reset and Wipe Cache and Internal mem and then tried to teboot?
zgfg said:
Be more specific, confirm
- Your phone is P9 or P9 Plus?
If P9, was it L09 (single SIM) or L19 (dual SIM)
- On exactly which Chinese Oreo have you been (cannot be VIE, you must well know what you exactly had and what you were flashing), was it EVA -AL00c00 or what and which build number bXX it was
- Did you go to some Open Kirin/AOSP custom ROM or stayed on that stock Chinese ROM?
You first had to come back to Chinese stock Oreo, not downgrading to Nougat directly from Open Kirin / AOSP
- Downgrading consists of several steps, HiSuite to go to Chinese Nougat and then HWOTA7 to rebrand to eg c432 Nougat.
Up to each step did you exactly do when you got stuck in Booting?
-More precisely, if you downgraded by HiSuite to AL10c00 Nougat, did it boot successfully (or were you here stuck at booting)?
If that step was successful, which (full build name and number) you were flashing by HWOTA7 to rebrand to from the Chinese Nougat?
-Have you tried to switch off and boot again?
Have you tried booting to Recovery and do Factory reset and Wipe Cache and Internal mem and then tried to teboot?
Click to expand...
Click to collapse
Sure,
EVA-L09 is a regular P9. Not a P9 Plus.
I never honestly checked which Oreo firmware I was on. I downloaded the VIE-AL10C00B535 (8.0.0.535) firmware and used that.
Yes, at one point I did go to the OpenKirin AOSP ROMs. However, I was able to do the volume + & - + Power to return to Nougat and then re-flash Oreo. After this I stayed on the EMUI 8.0 firmware.
I did not use HiSuite as it never worked for me. It would always just tell me to go to a service center.
I did not use HiSuite. When I returned to EMUI 5.0.1 from eRecovery (?) Restoring over WiFi on the actual phone it booted fine and I then upgraded again to the Oreo firmware.
Yes, I have tried rebooting.
Yes, I have tried a factory reset.
When I tried to revert from a VIE-AL10 rebrand, my phone ended up getting stuck between an AL10 and an EVA-L09. Meaning that I can use the EVA-L09 TWRP but not an EVA-L09 compatible firmware or ROM. I can only boot AL10 firmwares or ROMs however they hang at the boot animation.
gamr13 said:
Sure,
EVA-L09 is a regular P9. Not a P9 Plus.
I never honestly checked which Oreo firmware I was on. I downloaded the VIE-AL10C00B535 (8.0.0.535) firmware and used that.
Yes, at one point I did go to the OpenKirin AOSP ROMs. However, I was able to do the volume + & - + Power to return to Nougat and then re-flash Oreo. After this I stayed on the EMUI 8.0 firmware.
I did not use HiSuite as it never worked for me. It would always just tell me to go to a service center.
I did not use HiSuite. When I returned to EMUI 5.0.1 from eRecovery (?) Restoring over WiFi on the actual phone it booted fine and I then upgraded again to the Oreo firmware.
Yes, I have tried rebooting.
Yes, I have tried a factory reset.
When I tried to revert from a VIE-AL10 rebrand, my phone ended up getting stuck between an AL10 and an EVA-L09. Meaning that I can use the EVA-L09 TWRP but not an EVA-L09 compatible firmware or ROM. I can only boot AL10 firmwares or ROMs however they hang at the boot animation.
Click to expand...
Click to collapse
>> I downloaded the VIE-AL10C00B535 (8.0.0.535) firmware and used that.
In yout previous post:
>> I tried to follow this: https://forum.xda-developers.com/sho...13&postcount=2
Guide you cited is for rebranding European P9 EVA to Chinese P9 EVA-AL10c00b535 - see attached screenshots from the guide, observe it is everywhere EVA-AL10, not VIE-AL10
Once again, it must be EVA before rebranding and EVA after rebranding.
VIE is different phone (different hardware - bigger display), P9 Plus.
If you didn't care about difference between EVA and VIE, maybe you really downloaded and flashed AL10c00b535 for VIE (P9 Plus) to your EVA (P9)
----
>> Yes, at one point I did go to the OpenKirin AOSP ROMs. However, I was able to do the volume + & - + Power to return to Nougat
This is procedure to boot to Recovery (eRecovery if charging by USB), not to Nougat
----
Details are important, not just when writing posts but really when reading guides and flashing, otherwise bad things can happen ;(
So please, consider again, did you really flash VIE AL10 to your P9 (5,2 inch display)?
(Maybe it worked somehow for AL10b535 because packages for Chinese P9 = EVA and P9 Plus = VIE are similar, but now when returning to Nougat it stays on VIE and doesn't boot)
zgfg said:
>> I downloaded the VIE-AL10C00B535 (8.0.0.535) firmware and used that.
In yout previous post:
>> I tried to follow this: https://forum.xda-developers.com/sho...13&postcount=2
Guide you cited is for rebranding European P9 EVA to Chinese P9 EVA-AL10c00b535 - see attached screenshots from the guide, observe it is everywhere EVA-AL10, not VIE-AL10
Once again, it must be EVA before rebranding and EVA after rebranding.
VIE is different phone (different hardware - bigger display), P9 Plus.
If you didn't care about difference between EVA and VIE, maybe you really downloaded and flashed AL10c00b535 for VIE (P9 Plus) to your EVA (P9)
----
>> Yes, at one point I did go to the OpenKirin AOSP ROMs. However, I was able to do the volume + & - + Power to return to Nougat
This is procedure to boot to Recovery (eRecovery if charging by USB), not to Nougat
----
Details are important, not just when writing posts but really when reading guides and flashing, otherwise bad things can happen ;(
So please, consider again, did you really flash VIE AL10 to your P9 (5,2 inch display)?
(Maybe it worked somehow for AL10b535 because packages for Chinese P9 = EVA and P9 Plus = VIE are similar, but now when returning to Nougat it stays on VIE and doesn't boot)
Click to expand...
Click to collapse
I honestly can't remember how I did it now, it's been a while, but it did go through successfully, and it was working fine after applying the patch.
But yeah, as of now all I can use is fastboot and TWRP. That's all. I've tried flashing EVA-L09 firmware, it doesn't boot. I've flashed AL10 firmware and it gets to a boot animation, but no further than that.
gamr13 said:
I honestly can't remember how I did it now, it's been a while, but it did go through successfully, and it was working fine after applying the patch.
But yeah, as of now all I can use is fastboot and TWRP. That's all. I've tried flashing EVA-L09 firmware, it doesn't boot. I've flashed AL10 firmware and it gets to a boot animation, but no further than that.
Click to expand...
Click to collapse
Boot to Fastboot:
- connect by USB to PC and boot by: press and keep pressing Vol-, then Pow
Ececute from the PC side and copy/paste back your results (is Bootloader still unlocked, what the phone thinks it is current model, cust, build number)
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
@gamr13 Please enter the shown commands by @zgfg in Fastboot mode and tell us the result.
There is not much hope to restore your device after all that you have done wrong → but if you try, what we recommend, we may can recover it.
I can confirm: EVA-L09 is not the same device as VIE-L09 → you can not rebrand EVA-L09 to VIE-AL10, and it is not possible to rebrand VIE-L09 to EVA-AL10 - That causes a lot of problems and you should not be surprised if your device does not boot again.
If your original device was an EVA-L09 you can rebrand to all EVA models, but not to VIE models - That's why there are two threads - one for P9 and the other for P9 Plus.
If you flash oeminfos and related Firmware → it must match with your device!
But if you think, you can flash whatever you like, then your device get "bricked". And here we are now.
BTW: Rebranding back to your originally model can not be done with HWOTA7 - as long the device is on Android 8 ! First a downgrade from Chinese Brand Oreo to Chinese Brand Nougat is required → after this step it is possible to use hwota7 again to rebrand. I have written all the steps in separate Posts after the main Thread.
First we need this Fastboot mode information, then we can see in which status, on which firmware and which oeminfo your device is currently.
Then it's time to flash exactly this firmware with the correct method → for this step, wait for instructions from us.
Only when the device works again, it is possible to downgrade with the correct method and return to the original model, or whatever.
As long as the device is in a "brick", nothing works, since the "brick" must first be resolved.
If it is a "semi brick", a "hard brick" can happen as well, after that the device will be dead and without any function → It teaches you to be careful with flashing and get all the information before you flash anything.
We've also had other issues caused by users doing wrong actions - not knowing what they're actually doing. But both cases were solved successfully - which was not easy:https://forum.xda-developers.com/p9/help/huawei-p9-potentally-bricked-t3841197/
Hey guys,
I've attached a screenshot below which contains all the commands and what I got from them below.
Note about the get-build-number, that was the most recent firmware I tried to flash out of literally 10 other firmwares I tried.
I appreciate everything you guys are trying to do to help me fix this problem. I'm currently trying to survive with a Galaxy S3 Mini, and it's not going well in the slightest.
Cheers.
EDIT: Just as a note, which may be obvious from the screenshots to you or not, the partitions are like Nougat, meaning I do not flash the recovery to ramdisk.
gamr13 said:
Hey guys,
I've attached a screenshot below which contains all the commands and what I got from them below.
Note about the get-build-number, that was the most recent firmware I tried to flash out of literally 10 other firmwares I tried.
I appreciate everything you guys are trying to do to help me fix this problem. I'm currently trying to survive with a Galaxy S3 Mini, and it's not going well in the slightest.
Cheers.
EDIT: Just as a note, which may be obvious from the screenshots to you or not, the partitions are like Nougat, meaning I do not flash the recovery to ramdisk.
Click to expand...
Click to collapse
Looks promissing
It says EVA, not VIE - ok
Somehow you are on c900b182 which means MM (not Nougat) - did you rollback to MM?
In Fastboot screen, does it show in red, at the bottom, both Phone (=Bootloader) and FRP Unlocked?
zgfg said:
Looks promissing
It says EVA, not VIE - ok
Somehow you are on c900b182 which means MM (not Nougat) - did you rollback to MM?
In Fastboot screen, does it show in red, at the bottom, both Phone (=Bootloader) and FRP Unlocked?
Click to expand...
Click to collapse
Yes, I tried to flash MM as well.
In fastboot mode it only shows PHONE Unlocked.
gamr13 said:
Yes, I tried to flash MM as well.
In fastboot mode it only shows PHONE Unlocked.
Click to expand...
Click to collapse
Why didn't you wait, you attempted to rollback?
Now Bootloader is unlocked but FRP is locked (and you cannot boot to System to unlock OEM=FRP)
It can block you fir further flashing ;-(
Do you want to go to c432, is it L09 (Single SIM) or L19 (Dual SIM)?
zgfg said:
Why didn't you wait, you attempted to rollback?
Now Bootloader is unlocked but FRP is locked (and you cannot boot to System to unlock OEM=FRP)
It can block you fir further flashing ;-(
Do you want to go to c432, is it L09 (Single SIM) or L19 (Dual SIM)?
Click to expand...
Click to collapse
This was around a week ago, and the FRP lock thing went away when I did the rebrand - as it's supposed to
But yeah, I can't boot the system.
It's the single SIM EVA-L09.
gamr13 said:
This was around a week ago, and the FRP lock thing went away when I did the rebrand - as it's supposed to
But yeah, I can't boot the system.
It's the single SIM EVA-L09.
Click to expand...
Click to collapse
Procedure for rebranding from c900b182 to c432 is here:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Once on c432b182 you should receive OTAs to get back to Nougat.
However, procedure requires flashing OEMIFO, which most likely will be forbidden to you because your FRP is locked and you cannot boot to Systen to unlock OEM.
Which means serious brick
In that case you can try with DC Unlock (sorry, I don't know a better method), it will cost you 15 EUR (probably) and you must ask them for on-line help if needed
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
zgfg said:
Procedure for rebranding from c900b182 to c432 is here:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
Once on c432b182 you should receive OTAs to get back to Nougat.
However, procedure requires flashing OEMIFO, which most likely will be forbidden to you because your FRP is locked and you cannot boot to Systen to unlock OEM.
Which means serious brick
In that case you can try with DC Unlock (sorry, I don't know a better method), it will cost you 15 EUR (probably) and you must ask them for on-line help if needed
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
I'll follow the first link carefully and report back, thanks!
gamr13 said:
I'll follow the first link carefully and report back, thanks!
Click to expand...
Click to collapse
Try but you most likely you will need second link
Here was another user who also had to use DC Unlocker, take a look into the thread (posts #6-#11), in the last post he described how it was resolved for him by DC Unlocker
https://forum.xda-developers.com/p9/help/bought-phone-ebay-registration-wizard-t3840803
zgfg said:
Try but you most likely you will need second link
Here was another user who also had to use DC Unlocker, take a look into the thread (posts #6-#11), in the last post he described how it was resolved for him by DC Unlocker
https://forum.xda-developers.com/p9/help/bought-phone-ebay-registration-wizard-t3840803
Click to expand...
Click to collapse
I used DC Unlocker before to get my bootloader unlock key.
gamr13 said:
I used DC Unlocker before to get my bootloader unlock key.
Click to expand...
Click to collapse
I was not writing you about getting the code but to use DC Unlocker to unlock FRP ( carefully read the story, posts #6 till #11, I gave you in the previous post)
Because their tool can unlock both FRP and Bootloader, but it costs more than just getting the Bootloader code
Personally I didn't use their tool (never bricked the phone or so to need it), and cannot help you about the tool further
Hey guys, i didn't find any info about that.
So my story starts from that when i tryed to down my firmware version from 9 to 8 using Rebrander by instruction from 4pda. It worked. But i forget to backup my OEMinfo and now have chinese region and model name "COR". (It's gonna be COR-L29), and can't use HiSuite to system recovery and can't get official firmware updates. Also can't use google pay.
So question is: can i use OEMinfo backup from another person's phone to restore normal region. Or how can i edit OEMinfo manualy.
And sorry for my bad english (⁄ ⁄•⁄ω⁄•⁄ ⁄)
_Cyrax_ said:
Hey guys, i didn't find any info about that.
So my story starts from that when i tryed to down my firmware version from 9 to 8 using Rebrander by instruction from 4pda. It worked. But i forget to backup my OEMinfo and now have chinese region and model name "COR". (It's gonna be COR-L29), and can't use HiSuite to system recovery and can't get official firmware updates. Also can't use google pay.
So question is: can i use OEMinfo backup from another person's phone to restore normal region. Or how can i edit OEMinfo manualy.
And sorry for my bad english (⁄ ⁄•⁄ω⁄•⁄ ⁄)
Click to expand...
Click to collapse
Is your device rooted ?
miststudent2011 said:
Is your device rooted ?
Click to expand...
Click to collapse
Sure, but only if i using EMUI 8 (132). Using Magisk, root works perfectly!
_Cyrax_ said:
Sure, but only if i using EMUI 8 (132). Using Magisk, root works perfectly!
Click to expand...
Click to collapse
Check what results it's giving for this commands.
Commands for fastboot :
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot getvar rescue_enter_recovery
fastboot oem oeminforead-SYSTEM VERSION
I used this guide
https://forum.xda-developers.com/honor-play/how-to/guide-debranding-fixing-honor-play-to-t3916999
and returned everything. Google pay working, i can get updates.
Shortly speaking, i got full stock
Hi guys
I have rebrand my eva-l09 by chinese oreo firmware, using HWOTA7, and after starting up, all google service are missing, abd cannot intall it correctly, i trying all GMSInSTALL apk but nothing happen.
I tried to unlock bootloader via fastboot, a message showing up on adb command (unlock frp necessary...), can't enable OEM UNLOCK, always stay on grey.
Nothing is fine for me on this chinese firmware
Model : EVA-L09
BUILD NUMBER : System 8.0.0.046(0cs6)
EMUI VERSION : 8.0.0
ANDROID VERSION : 8.0.0
ANY SOLUTION TO INSTALL C432B504?
rowland.phoen1x said:
Hi guys
I have rebrand my eva-l09 by chinese oreo firmware, using HWOTA7, and after starting up, all google service are missing, abd cannot intall it correctly, i trying all GMSInSTALL apk but nothing happen.
I tried to unlock bootloader via fastboot, a message showing up on adb command (unlock frp necessary...), can't enable OEM UNLOCK, always stay on grey.
Nothing is fine for me on this chinese firmware
Model : EVA-L09
BUILD NUMBER : System 8.0.0.046(0cs6)
EMUI VERSION : 8.0.0
ANDROID VERSION : 8.0.0
ANY SOLUTION TO INSTALL C432B504?
Click to expand...
Click to collapse
You say that you followed HWOTA7 instructions - did you really
1) Your screenshot shows model L09.
OP post #2 requores that you must rebrand (change location) from L09 (or L19, L29) to AL10.
You didn't rebrand, or it failed (how, why)?!
2) Your screenshot shows build number 8.0.0.046(OCS6).
Never seen any firmware like that.
HWOTA7, post #2, clearly describes that you must flash (after rebranding to AL10 c00), first b399sp17, and after b540.
Your build number is completely different?!
What you have is not result by following HWOTA7 instructions.
If you followed HWOTA7, you would have:
1) AL10 c00 b540 (not L09 b046 or what)
2) OEM/FRM would be permanently unlocked, with no OEM Loxk/Unlock option in Developers menu (not just grayed out)
3) You would have Playstore services preinstalled, you would just need to install Playstore apk
HWOTA7 OP post #3 describes how to rollback from (properly installed!!) AL10 c00 b540 Chinese Oreo back to Nougat (eg to L08 c432 b504)
But you don't have AL10 c00 b540, but instead something totally strange/wrong - I doubt that given eRecovery procedure will work for you.
You can try with HuRupdater (sorry, I never used and needed to use HuRupdater)
https://forum.xda-developers.com/ho...ash-official-firmware-recovery-t3769279/page1
Or, you can ask for a paid help from DC-Phoenix or Ministry of solutions:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
zgfg said:
You say that you followed HWOTA7 instructions - did you really
1) Your screenshot shows model L09.
OP post #2 requores that you must rebrand (change location) from L09 (or L19, L29) to AL10.
You didn't rebrand, or it failed (how, why)?!
2) Your screenshot shows build number 8.0.0.046(OCS6).
Never seen any firmware like that.
HWOTA7, post #2, clearly describes that you must flash (after rebranding to AL10 c00), first b399sp17, and after b540.
Your build number is completely different?!
What you have is not result by following HWOTA7 instructions.
If you followed HWOTA7, you would have:
1) AL10 c00 b540 (not L09 b046 or what)
2) OEM/FRM would be permanently unlocked, with no OEM Loxk/Unlock option in Developers menu (not just grayed out)
3) You would have Playstore services preinstalled, you would just need to install Playstore apk
HWOTA7 OP post #3 describes how to rollback from (properly installed!!) AL10 c00 b540 Chinese Oreo back to Nougat (eg to L08 c432 b504)
But you don't have AL10 c00 b540, but instead something totally strange/wrong - I doubt that given eRecovery procedure will work for you.
You can try with HuRupdater (sorry, I never used and needed to use HuRupdater)
https://forum.xda-developers.com/ho...ash-official-firmware-recovery-t3769279/page1
Or, you can ask for a paid help from DC-Phoenix or Ministry of solutions:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
https://ministryofsolutions.com/paid-services
Click to expand...
Click to collapse
Im using HWOTA7, but i change update files by anothore one i have downloaded from web, i work for give you the link of firmware used.
Any solution for my big issue please SIR
rowland.phoen1x said:
Im using HWOTA7, but i change update files by anothore one i have downloaded from web, i work for give you the link of firmware used.
Any solution for my big issue please SIR
Click to expand...
Click to collapse
Sorry, really cannot help you then.
Unfortunately, since you didn't follow the guide but flashed some other firmware instead (you thought 'better' or what), you are in a specific situation, on your own, and only you should know or find how to deal with the phone and that Oreo firmware
As suggested in the previous answer, you may try with HuRupdater, but IMO, instead of further improvising (HuRupdater is very powerful but you can brick the phone), consider paying 15-20 Euros for DC-Phoenix or Ministry of solutions to safely downgrade to Nougat
After that, if you want Oreo, please follow the HWOTA7 guide carefully and in every detail (like others who now happily use the Oreo) - you will have stable Oreo AL10 c00 b540, debloated, fully working and with less battery consumption than Nougat
Also, rooted, passing SafetyNet, with fully working GApps, and ready for Open Kirin Treble custom ROMs (maybe they will work with your Oreo, too, but cannot tell you)
And if you would ever want to go back to Nougat, you would have a proven roll-back guide as in the OP post #3
zgfg said:
Sorry, really cannot help you then.
Unfortunately, since you didn't follow the guide but flashed some other firmware instead (you thought 'better' or what), you are in a specific situation, on your own, and only you should know or find how to deal with the phone and that Oreo firmware
As suggested in the previous answer, you may try with HuRupdater, but IMO, instead of further improvising (HuRupdater is very powerful but you can brick the phone), consider paying 15-20 Euros for DC-Phoenix or Ministry of solutions to safely downgrade to Nougat
After that, if you want Oreo, please follow the HWOTA7 guide carefully and in every detail (like others who now happily use the Oreo) - you will have stable Oreo AL10 c00 b540, debloated, fully working and with less battery consumption than Nougat
Also, rooted, passing SafetyNet, with fully working GApps, and ready for Open Kirin Treble custom ROMs (maybe they will work with your Oreo, too, but cannot tell you)
And if you would ever want to go back to Nougat, you would have a proven roll-back guide as in the OP post #3
Click to expand...
Click to collapse
Foud me a solution plz sir
rowland.phoen1x
Use HCU for FRP unlock
Unlock bootloader , flash twrp to erecovery and change oeminfo (better to EVA-DL)
Tnen flash via HuRupdater B540 chinese firmware
Thats do if you know how )
rambik33 said:
rowland.phoen1x
Use HCU for FRP unlock
Unlock bootloader , flash twrp to erecovery and change oeminfo (better to EVA-DL)
Tnen flash via HuRupdater B540 chinese firmware
Thats do if you know how )
Click to expand...
Click to collapse
any method without a Box ?
I have the same issue, this is how i fix it...
rowland.phoen1x said:
Hi guys
I have rebrand my eva-l09 by chinese oreo firmware, using HWOTA7, and after starting up, all google service are missing, abd cannot intall it correctly, i trying all GMSInSTALL apk but nothing happen.
I tried to unlock bootloader via fastboot, a message showing up on adb command (unlock frp necessary...), can't enable OEM UNLOCK, always stay on grey.
Nothing is fine for me on this chinese firmware
Model : EVA-L09
BUILD NUMBER : System 8.0.0.046(0cs6)
EMUI VERSION : 8.0.0
ANDROID VERSION : 8.0.0
ANY SOLUTION TO INSTALL C432B504?
Click to expand...
Click to collapse
Maybe I can help you...
I had the same issue just like you, even I read this post before I fix my phone.
First of all, the bootloader says the FRP-Locked, OEM Lock(or whatever says, i can't remember)-Unlocked.
On the Developer Settings the Oem Unlock option was greyed out.
Just like you.
So, reading this post [GUIDE] Debranding to C432 and updating to B361 (Nougat) for EVA-L09 i had a hunch...
What did I do to have my phone back?
1. My phone had the C432 oeminfo, so, I downloaded the dload-huawei-p9-eval09-eva-b136.zip (L09C432B136) in this post. Stock ROM dload file - P9 EVA-L09 B136
2. Copy the extracted dload folder to the external microSD card.
3. Now open the dialer app and enter *#*#2846579#*#* to open the project menu
4. Go to Software Upgrade > SDCard upgrade and confirm the update installation.
5. After the update, maybe shows an error at the final, let it be.
6. The phone restarts and boots with the L09C432B136, Android 6.0, and if you check the Developer options, the OEM unlock option is enabled. You can now lock or unlock your bootloader.
7. I need to update to the latest build and if i tried to check for an update, it says there is none.
8. I downloaded this firmware Download Huawei P9 B182 Marshmallow Update [Europe] I repeat steps 2-5, lock the bootloader, and search for an update... and update after update, I'm on L09C432B504 (Nougat)
Hope to help you...
Sorry for my bad english, I have no one to practice with...