Okay so I accidentally soft-bricked my phone. To flash the stock ROM(system, recovery,boot) I need my phone's build number. I have the box and on the side I can see it saying VTR-L09, but when downloading the firmware there are literally tons of VTR-L09 models. So where can I get my exact model number.
Any fastboot commands?
Also, does it even matter? Tried to flash the stock rom for VTR-L09C432 and nothing would happen.
my phone is in FASTBOOT & RESCUE MODE
Other info:
Acces to IMEI, Product ID, Unlocking password
ROM: 64GB
RAM: 4GB
Color: graphite black
Bought in Slovenia - telemach
EDIT: saved the phone with:
https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
(thanks to hamburg)
With this fastboot commands you should get all information you need:
Code:
fastboot oem get-product-model
fastboot oem get-build-number
When you have a carrier branded phone than you can't update with the international (C432) version.
But what you can do is to flash your firmware with HWOTA.
With this you can change your phone to C432 and even to dual SIM L29 if you need it.
Here, in the P10 forums is a good tutorial, but I don't have a link yet, sorry.
Jannomag said:
With this fastboot commands you should get all information you need:
Code:
fastboot oem get-product-model
fastboot oem get-build-number
When you have a carrier branded phone than you can't update with the international (C432) version.
But what you can do is to flash your firmware with HWOTA.
With this you can change your phone to C432 and even to dual SIM L29 if you need it.
Here, in the P10 forums is a good tutorial, but I don't have a link yet, sorry.
Click to expand...
Click to collapse
Okay, so my model is VTR-L09C432B171
Does that mean I am hard-bricked?, I flashed for sure the right:
system.img, recovery.img, recovery2.img, boot.img and cust. img
And after flashing these images everything succeeded, but literally nothing happened?
Is flashing with HWOTA any different? If so, could you please provide the link when you get it.
Thank you!
Hi,
Bought a used P10. Now some apps mention that the phone is rooted.
So after a quick look I saw that the about page tells EMUI V 3.1 and Android V 5.1. Also size of internal storage shows 16 GB.
So for sure there is no official firmware on it. I tried to update to stock with the dload & erecovery method but I had no luck.
Can someone tell me how I can get back to stock? Do I have to unlock the bootloader to be able to do so? (In fastboot phone tells me bootloader is locked) Or did I miss something?
thanks for helping me out
Are you sure it's a P10? Because those firmware versions suggest P8.
Search "huawei p10 codes" on youtube and check the ones that can provide phone information (like project menu) where you could see if yoh were scammed.
majaczos said:
Are you sure it's a P10? Because those firmware versions suggest P8.
Search "huawei p10 codes" on youtube and check the ones that can provide phone information (like project menu) where you could see if yoh were scammed.
Click to expand...
Click to collapse
pretty sure that it's an p10.
fastboot oem get-bootinfo
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION
locked
VTR-L09
hw/eu
NRD90M test-keys
VTR-L09C652B101
also in settings (or using 3rd party filemanager) it shows that it has 32 GB of storage and 4 GB of RAM
https://imgur.com/eQ2VxIr
https://imgur.com/zuIVh0t
https://imgur.com/95a9xwN
https://imgur.com/EHrKyaG
Test Keys indicate failed flashing.
Who knows what was flashed - you cannot judge is this P10 or P8 based on what that failed firmware reports about Internal memory size.
However, there are differences between P10 and e.g. P8 in processor type, sensors, etc (screenshot attached):
https://www.gsmarena.com/compare.php3?idPhone1=8514&idPhone2=7006
Use an app like DevCheck to find about your hardware, and does it fit to P8 or P10 specifications
Btw, I shortly googled about onyx d188 (as from your screenshots) and found this - very similar to yours (Test keys, EMUI 3.1, Onyx, d188):
https://forum.xda-developers.com/showpost.php?p=73838247&postcount=81
https://forum.xda-developers.com/showpost.php?p=74253118&postcount=194
where some people report same issues when they flashed custom fROMFuture to P10 - btw, it means that seller must have had the Bootloader code for your phone
thanks for your reply,
i trying to get in contact with the shop and try to clear up whats wrong. That was a phone which was buyed "refurbished"
from the looks (and the 4GB RAM) it is a P10
Hello i bought used huawei mobile phone . the seller told me that its huawei p9 plus on the back of cover i found this info (model EVA-L19 FCC ID : QISEVA-L19 IC: 6369A-EVAL19) which mean its p9 .. but when look to info about phone i found this (VIE-C900B150) VIE -- when connect to my pc via HiSuite the model number shown was VIENNA ; VIENNA is p9 plus ? so help me to know
There is only "Huawei" on the front and back, no model.
They are visibly different in dimensions and weight - Plus, as the name says is bigger:
https://www.gsmarena.com/compare.php3?idPhone1=7745&idPhone2=7972
i measured the screen size and it was 13.4 cm = 5.2 inch .. that mean its p9 .... but is it possible to run p9 plus software on p9 ??
other question the camera and wifi no working ... android 6 and emui 4.1.1 ?
It's strange that VIE firmware runs on EVA, that it was not bricked (not just camera and wifi).
They have same chipset, so maybe.
EMUI 4 is ancient, and c900 cust was used for rollback in some cases - who knows what happened with your phone in the past and which idiot flashed a wrong firmware and then sold the phone
You would need Bootloader code to properly brand it back to EVA.
If you are not familiar with methods for flashing Huawei phones, you better sell it further or buy DC Phoenix credits and ask for instructions to use their tools (they will also provide you BL code and instruct how to use them):
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
zgfg said:
It's strange that VIE firmware runs on EVA, that it was not bricked (not just camera and wifi).
They have same chipset, so maybe.
EMUI 4 is ancient, and c900 cust was used for rollback in some cases - who knows what happened with the phone and which idiot flashed a wrong firmware and then sold the phone
/QUOTE]
thank you ... Also battery info shown from CPU X (which give system and hardware info) is 3320 mAh and that capacity similar to p9 plus ?
Click to expand...
Click to collapse
this screen shots from phone
befine said:
thank you ... Also battery info shown from CPU X (which give system and hardware info) is 3320 mAh and that capacity similar to p9 plus ?
Click to expand...
Click to collapse
P9 Plus means bigger display, yours isn't
Who knows what that app thinks
Battery can be replaced with not original but higher capacity
zgfg said:
befine said:
P9 Plus means bigger display, yours isn't
Who knows what that app thinks
Battery can be replaced with not original but higher capacity
Click to expand...
Click to collapse
I need your advise to install suitable software to solve camera and wifi issue as i wrote before the current is android 6 and emui 4.1.1 VIE-C900B150
Click to expand...
Click to collapse
befine said:
I need your advise to install suitable software to solve camera and wifi issue as i wrote before the current is android 6 and emui 4.1.1 VIE-C900B150
Click to expand...
Click to collapse
Post #4, gave you link for DC Phoenix
You need anyway to buy Bootloader code / unlock Bootloader, you cannot rebrand back to EVA without - but you need it to get things working
zgfg said:
befine said:
Post #4, gave you link for DC Phoenix
You need anyway to buy Bootloader code / unlock Bootloader, you cannot rebrand back to EVA without - but you need to to get things working
Click to expand...
Click to collapse
unfortunately i cant buy bootloader code or buy any thing online hence i live in sudan :crying: is there other way ?
Click to expand...
Click to collapse
befine said:
unfortunately i cant buy bootloader code or buy any thing online hence i live in sudan :crying: is there other way ?
Click to expand...
Click to collapse
No, there are only more expensive providers than DC Phoenix
Huawei stopped providing BL codes (they did for free) a year ago.
Actually, for their new models (DC Phoenix does not support them) it's more and more complicated and expensive:
You have to open the phone, short the Testpoints pins, provide TeamViewer on-line acces to your PC and pay almost 40 bucks just to obtain the BL code - on the other side, for the old P9, for half of that price and without opening the phone, you get BL code and unbrick P9 with DC Phoenix.
If you wanted to flash for free, you had to buy Xiaomi or so, Huawei is trying to bacome 'closed' like Apple ;-(
can upgrade or downgrade from EMUI 4.1.1 C900B170 or EMUI 4.1.1 C900B130 Firmware For Huawei P9 Plus VIE-L09 to mine (VIE-C900B150 model EVA-L19) directly by dload ... is l09 and l19 has same soft
befine said:
can upgrade or downgrade from EMUI 4.1.1 C900B170 or EMUI 4.1.1 C900B130 Firmware For Huawei P9 Plus VIE-L09 to mine (VIE-C900B150 model EVA-L19) directly by dload ... is l09 and l19 has same soft
Click to expand...
Click to collapse
VIE is P9 Plus
EVA is P9
L09 is single SIM
L19 is dual SIM
c900 is some kind of test/rollback cust, there are no Nougat/EMUI 5 firmwares with c900, only OLD MarshMallow/EMUI 4
To rebrand from c900 to c432 (European) or c185 (Middle East) or to any other cust, you will NEED UNLOCKED BOOTLOADER
Also to rebrand from L09 to L19 or vise versa.
However, P9 L09 and L19 are little diff in hardware, L09 does have NFC but not dual SiM reader
L19 has no NFC but it has dual SIM reader
Believe me, three of us experimented for weeks, trying MM and Nougat firmwares - we did rebrand software from L09 to L19, but never got it recognzed the second SIM
(P9 Lite, P10, Mate 9 can be rebranded from L09 to L19, to really work as dual SIM, but P9 single SIM cannot become dual SIM)
Finally, people never rebrand from P9 to P9 Plus, or from P9 Lite to P9, etc - it makes no sense because of different hardware.
Generally, it would brick the phone
But, P9 and P9 Plus have the same chipsets, and similar hardware, and dome of their firmwares were cross-compared and found to have the ame kernel, ramdisk, recovery
So probably, previous owner of your P9 phone flashed P9 Plus firmware without bricking the phone- your phone boots but Camera and WiFi do not work
---
Anyway, I think that you need to rebrand from VIE-L09c900 to EVAL09c432, because your phone, by dimensions is P9, not P9 Plus.
So only with EVA things will really work, and with c432bor c636nor so, you will have latest available Nougat/EMUI 5
Proper "rebranding" means:
- with TWRP, (on your phone) to restore OEMInfo from e.g. EVA-L09c432 (backed up on such a phone)
- for that, you first have to flash TWRP
- to be able to flash TWRP, you need to have unlocked Bootloader and FRP
- to unlock Bootloadet, you must have Bootloader code
For anything else you want to do, like DLOAD flashing firmwares (it doesn't require unlocked Bootloader) you can do on your own - I will not 'assist' you because Im pretty sure that only by DLOAD, without proper rebranding, you cannot make it back to EVA.
You can only make things worse - full brick, bootloop
In that case, please spend your own time to search and learn about DLOAD, models, custs, FullOTA-MF-PV, FirmwareFinder, etc
---
You can just do the following test:
Boot to Fastboot, does it show green Phone and FRP locked, or red Phone and FRP unlocked?
In Fastboot, execute commands and provide back their results, to see on the 'low' level what the phone knows about his current software
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
@befine You should also test following (before doing anything else):
In settings - "About phone" click 7 times on the "Build-Number" until the message appears: "You have successful enabled Developer Options".
Then go back to settings - "Developer Options" and check, if you have there:
- Oem Unlock.
Try to enable OEM Unlock. If it is possible, then you could unlock the Bootloader - which is the main important thing to change the wrong Firmware to the right one, exactly how @zgfg explained it in the previous postings.
If Oem Unlock is greyd out and you cannot enable Oem Unlock with the switch-button - then there is no chance to correct the device!
Without Oem Unlock enabled it is even not possible to unlock the Bootloader (even if you already would have the code).
But if you can enable "OEM Unlock" - then enable also
1) ADB Debugging in charging mode
2) USB Debugging (in this order, otherwise ADB Debugging will not stay enabled)
In case, this three options are enabled - I could send you a personal message with a User Name and password. With this information (it would be a gift for you) you could use HCU Client (which is the Best Software by DC Unlocker/DC Pheonix) to read the Bootloader Code from the phone.
But first you have to check, what I told you. In case, it is possible, you will also get a detailed guide how to do the steps to change your phone from the wrong VIE Firmware to the right EVA Firmware.
Without all those steps, there is no chance. You could flash what you want with dload, but without any effect (you cant get camera etc. to work on a wrong oeminfo, which does not match the real phone) In the worst case you would brick your phone completely.
The seller of your phone flashed a wrong "oeminfo" to the phone (VIE instead of EVA). This should be corrected after opening the boot loader (and I would tell you how to do).
The other possibility is, just give the phone back to the seller and get your money back. Because in this state it is useless.
Best regards
Tecalote
zgfg said:
VIE is P9 Plu
---
You can just do the following test:
Boot to Fastboot, does it show green Phone and FRP locked, or red Phone and FRP unlocked?
In Fastboot, execute commands and provide back their results, to see on the 'low' level what the phone knows about his current software
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Click to expand...
Click to collapse
this is log below
befine said:
...this is log below
Click to expand...
Click to collapse
All are VIE, from meafnaf you were probably on c185
Bootloader says locked (unfortunately as expected) - can you ask the seller if he can give Bootlloader code to you (somebody in the previous life flashed that phone and he must have had BL code, at that time it was easy and free to obtain)
Still two questions:
1) Please click 7 times to Build number in Settings/System/About as @Tecalote explained, then open Developer Options menu.
Do you see there Enable OEM unlock option, can you enable it - or option is missing or greyed out?
If you can enable it, then when you boot to Fastboot you will see on the bottom of the phone screen, FRP unlocked in red.
If FRP cannot be unlocked, then it requires HCU Client
2) You measured display size. To double-check, measure also phone length and height, do they correspond to the dimensions of P9 or P9 Plus (check post #2, gsmarena comparison sheet)
3) Btw, do you have two cameras on the back, printed Leica - check device photos on gsmarena.
And in the Settings, can you enable/disable NFC?
And btw, in Settings/Storage, what does it say for Internal memory size, 32 or 64 GB?
Tecalote said:
@befine You should also test following (before doing anything else):
In settings - "About phone" click 7 times on the "Build-Number" until the message appears: "You have successful enabled Developer Options".
Then go back to settings - "Developer Options" and check, if you have there:
- Oem Unlock.
Try to enable OEM Unlock. If it is possible, then you could unlock the Bootloader - which is the main important thing to change the wrong Firmware to the right one, exactly how @zgfg explained it in the previous postings.
If Oem Unlock is greyd out and you cannot enable Oem Unlock with the switch-button - then there is no chance to correct the device!
Without Oem Unlock enabled it is even not possible to unlock the Bootloader (even if you already would have the code).
But if you can enable "OEM Unlock" - then enable also
1) ADB Debugging in charging mode
2) USB Debugging (in this order, otherwise ADB Debugging will not stay enabled)
In case, this three options are enabled - I could send you a personal message with a User Name and password. With this information (it would be a gift for you) you could use HCU Client (which is the Best Software by DC Unlocker/DC Pheonix) to read the Bootloader Code from the phone.
But first you have to check, what I told you. In case, it is possible, you will also get a detailed guide how to do the steps to change your phone from the wrong VIE Firmware to the right EVA Firmware.
Click to expand...
Click to collapse
yes OEM Unlock was enabled also adb debugging and usb debugging .. could you send user name and pass of dc unlocker and i will try unlock boot loader and thank you man
befine said:
yes OEM Unlock was enabled also adb debugging and usb debugging .. could you send user name and pass of dc unlocker and i will try unlock boot loader and thank you man
Click to expand...
Click to collapse
Ok, FRP enabled, pls check the other questions in my previous post, you will need to know is it really P9, and which OEMInfo L09, L19 or L29 to take for rebranding, as Santa Claus will give you dc ac****
zgfg said:
All are VIE, from meafnaf you were probably on c185
Bootloader says locked (unfortunately as expected) - can you ask the seller if he can give Bootlloader code to you (somebody in the previous life flashed that phone and he must have had BL code, at that time it was easy and free to obtain)
Still two questions:
1) Please click 7 times to Build number in Settings/System/About as @Tecalote explained, then open Developer Options menu.
Do you see there Enable OEM unlock option, can you enable it - or option is missing or greyed out?
If you can enable it, then when you boot to Fastboot you will see on the bottom of the phone screen, FRP unlocked in red.
If FRP cannot be unlocked, then it requires HCU Client
2) You measured display size. To double-check, measure also phone length and height, do they correspond to the dimensions of P9 or P9 Plus (check post #2, gsmarena comparison sheet)
3) Btw, do you have two cameras on the back, printed Leica - check device photos on gsmarena.
And in the Settings, can you enable/disable NFC?
And btw, in Settings/Storage, what does it say for Internal memory size, 32 or 64 GB?
Click to expand...
Click to collapse
1/no the seller doesn't no any thing about phones and iwas enabed developer optin and Enable OEM unlock option was enabled and fast boot mode showing FRP unlocked in red and phone locked in green
2/ screen size was 5.2 inch... phone dimension height 5.6 inch width 2.7 inch
3/ yes two camera in the back printed Leica
4/ no NFC option found
5/ storage is 32 GB
befine said:
1/no the seller doesn't no any thing about phones and iwas enabed developer optin and Enable OEM unlock option was enabled and fast boot mode showing FRP unlocked in red and phone locked in green
2/ screen size was 5.2 inch... phone dimension height 5.6 inch width 2.7 inch
3/ yes two camera in the back printed Leica
4/ no NFC option found
5/ storage is 32 GB
Click to expand...
Click to collapse
So if dimensions are 5.71 x 2.79 mm, then must be P9.
For P9 Plus and for P9 L09, NFC should be there and work, maybe you don't have due to inappropriate firmware flashed.
That means, you will need OEMInfo for EVA L09 c185 or c432
If you see two IMEIs in Settings/About, then L19 (dual SIM, no NFC)
So a few days ago I picked up my X4 on Amazon to replace my dying old Samsung, (XT1900-7, 4/64) for 125€ which is a steal for the specs you get. After playing with it for a while I decided to unlock the Bootloader so I can root it. When I tried the fastboot oem get_unlock_data in fastboot mode It only says "Invalid Command" then I realised I have the Amazon Prime version (which had Alexa installed), which allegedly cannot be unlocked, and was stuck in Android 8. So after a lot of googling I tried Sideloading Pie in fastboot, which didn´t work. Applying update from SD Card also didn´t work (couldn´t mount /sdcard). So I followed this method here: https://forum.xda-developers.com/moto-x4/how-to/rom-upgrade-directly-to-pie-8-0-locked-t3876127 (thanks to TeamRainless). I downloaded the factory signed Image from the MEGA Link: https://mega.nz/#!QQ1mgKpS!ce2kysojSUv9pzA-V4YE4kv5jg0S7X5X1lNrIWn6su0. I put the zip file (DO NOT RENAME THE FILE!) in the root folder of my internal storage, then checked the update manually in the Settings, and voila! It applies the Pie update in the 30 Minutes and now I have the retail version of the ROM without Amazon apps on it.
I applied all patches until September 2019 (PPWS29.69-37-5). I rebooted into fastboot mode and ran the fastboot oem get_unlock_data as usual and now I get the 5 lines of code I could use to unlock the device. I logged into Motorola website and pasted the code, accepted all the T&Cs, got the unlock code in my Email and now my phone is unlockable. I ran this in fastboot fastboot oem unlock *code given in email* and the phone was unlocked. When I rebooted the phone all my data was deleted so if you want to do this back up your data first! I hope this gives hope to all of you who bought the Amazon version without knowing. Good luck trying and stay healthy guys!
https://postimg.cc/gallery/XXVR3H3
wow thnx for information
Hey, bumping this with a few general questions:
Has anyone with the US Amazon XT1900-1 been able to unlock their bootloader this way?
Is there any way to get this working if I'm already at the most recent patch?
I know that attempting a downgrade with a locked bootloader causes a bootloop. Is it possible to recover from that state? Exactly how bad of an idea would it be to try to downgrade to Oreo (triggering the bootloop) then apply the stock (non-Amazon) Pie image?
gatesps said:
Hey, bumping this with a few general questions:
Has anyone with the US Amazon XT1900-1 been able to unlock their bootloader this way?
Is there any way to get this working if I'm already at the most recent patch?
I know that attempting a downgrade with a locked bootloader causes a bootloop. Is it possible to recover from that state? Exactly how bad of an idea would it be to try to downgrade to Oreo (triggering the bootloop) then apply the stock (non-Amazon) Pie image?
Click to expand...
Click to collapse
I have Moto X4 Amazon XT1900-1. I'm not sure that I have US version and I don't know how to check this.
I can check you method on this phone.
I have Android 9(Version PPWS29.69-39-6-4 with security patch from January 2020) on my phone.
So update application doesn't see factory signed image.
Is there any way to downgrade to Android 8?
Or is there any other way how to install mentioned image?
maks_kyiv said:
I have Moto X4 Amazon XT1900-1. I'm not sure that I have US version and I don't know how to check this.
Click to expand...
Click to collapse
Device Model #, Codename, and Software Channel.
maks_kyiv said:
I can check you method on this phone.
I have Android 9(Version PPWS29.69-39-6-4 with security patch from January 2020) on my phone.
So update application doesn't see factory signed image.
Is there any way to downgrade to Android 8?
Click to expand...
Click to collapse
Only if the bootloader is already unlocked
maks_kyiv said:
Or is there any other way how to install mentioned image?
Click to expand...
Click to collapse
sd_shadow said:
Device Model #, Codename, and Software Channel.
Only if the bootloader is already unlocked
Click to expand...
Click to collapse
I got error when trying to get fastboot variables:
$fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
sd_shadow said:
Only if the bootloader is already unlocked
Click to expand...
Click to collapse
Bad, I will wait for any working bootloader unlocking method for Amazon phones.
maks_kyiv said:
I got error when trying to get fastboot variables:
$fastboot getvar all
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) allt-suffixes: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
Click to expand...
Click to collapse
Tried on another PC. Got all fastboot variables successfully.
So my phone is from US.
I also have an XT1900-1 already upgraded to Pie with a locked bootloader. I had a thought - would it be possible to trick the update service into thinking that this image is an upgrade? How does the update service know that the image is a newer version anyway?