Until i looked on here today I wasnt aware there was actually an update for the huawei p9 as i the phones 'Check up update' would always tell me there was no new version. I have the P9 EVA-L09 UK version and am currently on EMUI Ver 4.1.1 and Android version 6.0. What is the latest update i can install on this phone please and will i lose all the data on my phone?
Depends on your build number. If it's C432 you should be able to update to Nougat. If not you will need to follow the debrand guide found on this forum.
My build number is EVA-L09C432B182, which is the correct version right? I just tried updating to B386 from this guide here...
http://www.stechguide.com/download-huawei-p9-b386-nougat-update/
but i get an error message saying that the update.app is the wrong version, do i need an early version of the Nougat FW??
It's a minefield. Some work some don't. I'd try an earlier build b360 or b361 maybe. You could also try using the Huawei updater guides are on here.
hmm tried version B360 and it gets to about 39% installer and then gives me a 'Software Install Failed' message. Do i need an even older version of the Nougat FW?
That's the oldest as far as I know. Did you try with 3 button or hidden update menu method.
nah i used the phone keypad code method. I have just unlocked my bootloader and installed TWRP, can i update it via TWRP safely?
Hmm well ive updated to Nougat but something doesnt seem to be right alot of the programs are missing and now im unable to get TWRP to load and just seems to load Huawei eRecovery when i press the volume up and power button on turn the system on. How do i got about getting the phone back to stock (bootloader relocked, un rooted, twrp uninstalled and back on Android Marshmellow 6.0)?? so i can start again?
Look for the b136 rom. I believe that fixes a lot of issues for people. Most of this is on the debrand guide. Have a good read of that thread.
wards5150 said:
Look for the b136 rom. I believe that fixes a lot of issues for people. Most of this is on the debrand guide. Have a good read of that thread.
Click to expand...
Click to collapse
Ok thanks i just posted a new thread as i now seem to be stuck on a 'this system is rebooting' screen (the warning screen you get that tles you the phone is unlocked) and the phone never actually boots anymore. Will me force flashing (Volume Up+Down+Power button) the b136 rom get me out of this predicament?
I've not had to do it myself but I have read that others have. Good luck. Shouldn't be this hard to update.
Hmm i dont even seem to be able to get the phone into the force update process (Volume UP+DOWN+Power) just hangs on the Huawei logo screen
Hmm i think the phone is bricked, im unable to get into the menu to update the Update.app file from the dload folder on the SD card, i cant even get the phone to switch off it just keeps restarting itself and freezing on the 'your device has been unlocked and cant be trusted' screen....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......
and if i hold down both the volume and power buttons i get this screen....
and not the firmware update screen i should be getting.
It has been suggested that i need to use DC Phoenix program to fix the phone but thats a paid method and dont really want to go that route if there is another way!??
Sorry to hear that mate. Good luck fixing it. It should not be this hard to update. For some it's easy for others it's a right pain. I'm sure there will be a way to sort it the hard bit will be finding it.
Related
Hi! I have a Galaxy S5 G900A (AT&T), Which I wanted to change to a stock Galaxy S5 ROM, to get rid of all those AT&T apps that no-one uses. So I searched it up! Long story short, I found out that AT&T locked the bootloader and I can't do anything about it. Then I found this post to root my phone: http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299 . Then I just realized how I wanted root, so I did every thing they said, turned off reactivation lock, installed towelroot, and then flashed the file they said (G900A_ND3_Stock_Kernel) with Odin. After that, My phone just showed the Galaxy S5 logo for a minute like it's booting for the first time, and then it restarted to recovery (stock recovery). I clicked on reboot device in the recovery mode, and it just did the same. Afterwards, I tried to flash the G900A_Downgrade_to_NCE.tar file to go back to normal. Flashed it, and it said "firmware encountered an issue". I went to kies but it didn't see the device. Then I saw this video: https://www.youtube.com/watch?v=Jfgq6bYfKLg . It had a "All recover Samsung.tar" file which should be flashed with Odin. And, I flashed it in odin. Odin said fail but it went back to the state when it was rebooting to recovery. I tried downloading so many AT&T ROMs and flash it but all say "Fail(auth)!" in odin. Any help? Thanks.
Hope this helps, just ask I will help you further if I can.
I did this too. It's a noob mistake. But from what I understand there is still no way to root Galaxy S5 SM-G900A after the 5.0 Lollypop update. This has to do with the bootloader being locked and not enough dev support on these now considered too old phones to be worth their time.
It took me 3 months to fix it and basically from what I gathered, from you, using the same method. Shoot in the Dark Flashing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just keep flashing **** and hope it works. LOL. It can't get any worse, right? After three moths of trial and error Flashing and just a LITTLE wiser in these areas, I think I might be able to help you. You need to Flash something at least 5.0+. Nothing below this will work and will always get "Auth Fail!". That is your locked bootloader preventing you from downgrading and rerooting and reupgrading with an already unlock, root access, stock Rom.
This is the one I used to finally unbrick my phone:
Link it was posted at: http://forum.xda-developers.com/att-galaxy-s5/help/g900aucu4coi5-file-t3231450
Link to Download: 5.1.1 OI5 https://drive.google.com/file/d/0B11_scgy1qonMW45T0lRbXQ3ZHM/view
But any of these should work...
5.1 PA2 http://forum.xda-developers.com/att...w-to-update-to-g900aoi5-5-1-unrooted-t3235774
6.0.1 PH2 http://forum.xda-developers.com/att-galaxy-s5/general/g900a-mm-odin-package-g900aucu4dph2-t3477515
6.0.1 PH4 http://forum.xda-developers.com/att-galaxy-s5/general/galaxy-s5-android-version-6-0-1-t3419016
P.S. I was on KitKat before all the above. My biggest mistake was just Flashing random stuff. I inadvertently flashed a lollypop kernel and that is what forced me into an update I could not get out of. So no more root access for me. Lesson learned!
Oh and btw, Hello this is my first post. Never even saw a need to register an account until after be a reader for at least 5 months. The POWER of SEARCH. I did what 5 cell phone repair shops could not. Unbrick my Galaxy S5. All with the resources of this amazing forums.
Good evening folks!
I've been lurking around in this amazing forum for some time now, but now i need a little bit of help.. I have searched my ass off in here and out there in google city, but can't find squat!
So...
I have this Huawei P9 that used to be EVA-L09C432B182 until yesterday when i tried to update/upgrade to C432B360 dload style. It went great i thought, 100% and succeed message. Then it rebooted to eRecovery...
I tried to update the HW_EU the same way - 99% Fail message.
I've tried update via Huawei updater as you can see in the picture below. I also tried unbrick/refurbish via Huawei updater but all that happened on Hisuite you can also see in the picture. The circle of nothing kept going for hours.
What my EVA can do? Enter eRecovery (which helps me nothing), fastboot/rescue mode (Huawei updater kinda recognizes my device, Hisuite does not.) and force update three button method (Here i get a message when trying to flash anything from ext. sd card: "Not compatible with this version, download the right software". Or something to that matter.)
If you take a look at the picture i've tried to embed below, you'll see that Huawei updater recognizes my phone as
Hardware: EVA-L09
Firmware: EVA-L09-hw-eu-V001 (Never seen or heard of!)
C- version: C000
D- version: D000
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My question is; What can i do with this?
I'm not rooted.
[/COLOR]Phone locked.
FRP Unlock
Windows recognize as: HI3650, Huawei Android Interface.
I'll appreciate all and any links, downloads, guides, tools.. Ideas you might have!
Squirrel.
Norway
try to do "systemgjenoppretting" what happens then ?
ofcorse, swich in hisuite to "no proxy'
I have the same problem mate , i don't know what can i do . Did you try to wipe cache etc?
Arnys said:
try to do "systemgjenoppretting" what happens then ?
ofcorse, swich in hisuite to "no proxy'
Click to expand...
Click to collapse
Hisuite answers with "your device is not supported, contact local service..."
pindlosz1 said:
I have the same problem mate , i don't know what can i do . Did you try to wipe cache etc?
Click to expand...
Click to collapse
Yeah, i tried. Wipe cache - Fail. Factory reset - Fail.
Something actually happening after trying custom rom method on Huawei updater with hisuit IP/Port set manually .
Lets hope it lasts!
It helped you?
pindlosz1 said:
It helped you?
Click to expand...
Click to collapse
Don't know yet, it's going reeealy slow. I'll keep you posted!
It was going so great...
And then not so much..
I was stuck in a similar sort of place, I used a program called DC Phoenix, which I found in these forums. You have to pay a fee of 15 euros which gives you access to force flash a rom. It worked perfectly on mine after I had exhausted other options. Its part of dc unlocker. Hope that helps
Natchi said:
I was stuck in a similar sort of place, I used a program called DC Phoenix, which I found in these forums. You have to pay a fee of 15 euros which gives you access to force flash a rom. It worked perfectly on mine after I had exhausted other options. Its part of dc unlocker. Hope that helps
Click to expand...
Click to collapse
Hey!
Do you know if this Is a guaranteed succeed solution? I'll look into it. Definitely worth the 15Euros if it actually works magic!
Thanks.
Theres a forum thread somewhere on here, I cant find it at the minute, but there were numerous good reviews
Tried using SRK and update extractor. See pic.
Anyone know what i can do with this "command not allowed"?
No time for school, work or family with this **** going on..!
Natchi said:
I was stuck in a similar sort of place, I used a program called DC Phoenix, which I found in these forums. You have to pay a fee of 15 euros which gives you access to force flash a rom. It worked perfectly on mine after I had exhausted other options. Its part of dc unlocker. Hope that helps
Click to expand...
Click to collapse
I did this too , phone starts normally and it's full working but i have to write NCK code (simlock ?) . How can i repair this ?
I would try and flash a full rom using the dload method just to make sure. I flashed B136 after I reset mine to take it back to original and let it updat to b166 ota
Phoenix woke my phone up again! Thanks!! Now I'm on Nrd90m though, hoping to bring back stock.
Help
Look_Squirrel said:
Phoenix woke my phone up again! Thanks!! Now I'm on Nrd90m though, hoping to bring back stock.
Click to expand...
Click to collapse
I had the same problem, what did you do to fix it?
I downloaded DC phoenix from DC unlocker page. Bought 15 credits ≈ 15 euro
Downloaded full b361 for EVA-L09. Then followed instructions given by the program. I can explain better when I'm on my laptop if needed?
Still have no built-in camera, no BT, no NFC and no built-in flashlight..
Seems like Android Pay does not recognise the latest system update as an official ROM, after installing Android pay and giving all the permissions:
Android Pay can't be used on this device. This may be because your device is rooted, has an unlocked bootloader, or is running a custom ROM. As a result, Google can't confirm that your device meets Android Pay's security standards.
Click to expand...
Click to collapse
I inadvertently ran this update after purchasing the phone 2 days ago, didn't unlock the bootloader (though applied for it) and of course, haven't rooted.
I factory reset twice and still got the same. Looking forward to unlocking the bootloader so I can downgrade to the older ROM or even go on the global one (since I saw in another thread Android Pay's working on the latest global ROM V8.2.1.0.MAHMIDL, and the latest downloadable Chinese stable Rom V8.2.2.0.MAHCNDL)
Anyone updated and experience the same issue? And as I'm a newb in all of this, must I unlock the bootloader in order to downgrade?
Tried to get it to work, this time through using recovery flash (without need to unlock the bootloader and what not). Here's how I finally got Android Pay to work, and also got myself on Global Rom (lovin' it)
Prerequisite: Download the latest stable ROM file here to PC
1. Download the Chinese version of the Xiaomi Mi PC Suite and run it
2. Plug in your phone to PC and boot into recovery mode (push both volume up button + power button together until your phone reboots)
3. Allow driver to install, if you're in recovery mode, a prompt will come up. If not don't panic, read step 4. Otherwise go to Step 5.
4. If the PC Suite does nothing even if you push the big orange button on the right to connect (apparently they haven't upgraded the software to support Android 6.0 yet -_-"), click this button show below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and select the button with the words "Recovery" in it, it will prompt you to reboot your phone into recovery mode (push both volume up button + power button together until your phone reboots).
5. Select the ROM you pre-downloaded on your PC and let it run.
6. The PC Suite will look like it hits some error and on desktop the progress remains at 0% but somehow things are churning on your phone as you can see "MIUI update" and a progress bar below.
7. Let it run its course and allow the phone to reboot
8. Voilà, your phone is now in Global ROM
And Android Pay now works, hoorah!!!
Great guide, thanks a lot! I've got the sister phone to this one, the Xiaomi Mi Note 2... and my Android pay was not working with 8.3.2 global.. But now it is.. I will post a guide elsewhere as to how I had to fix it...
THIS is a DANGEROUS post, it may work - or like in my case it will start for just a moment then stop [causing a factory reset to occur] without updating. Make sure you have your mi account login and pass ready when it comes back up - or your locked out of the device setup.
Due to frustration caused by trying this post I ended up unlocking / rooting the device. It was easier than I thought it would be, flashed global fine from there and updated to 8.2.4.0 just fine OTA. Have gone on too work on other things I had decided not to due because I hadn't decided to root the device. So I guess there was a silver lining to this.
Hi, I have checked this thread as I experienced the same issue(If confused what I'm talking about read
www chinaphonearena com/forum/Thread-Question-LeEco-Le-S3-X626-Helio-X20-Bricked ), I was able to get past the phone buttons not working and was able to flash a new firmware. But this led to another issue considering the system.
For one, I am unable to unlock my bootloader, I just receive the error : FAILED (remote: unlock operation is not allowed), and there is no way fro me to get in my android as it always stays on the LeEco POWERED BY ANDROID screen, which then shuts down and reboots.#
As well as this, the display is now very unusual: the LeEco logo is coloured green white and yellow, the display is flipped horizontally and mirrored vertically.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image above shows this.
It's VERY annoying and I hope it can be solved.
NOTE!! I can still use locked bootloader/fastboot, can't use adb and can use SP FLASH TOOL
You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom
damtrx_ said:
You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom
Click to expand...
Click to collapse
Thanks for the reply, I fixed the issue the same day, I just fixed it using the second part to tickernel's red light unbrick tutorial, I completely missed it out. The rom I was using where everything was inverted was just to unbrick the phone, then after I'd have to flash the rom provided by tickernel to fix. It worked again and an advantage was that there was no more ORANGE state, I didn't have to patch to hide the message nor wait the 5 seconds, so now I can flash custom roms on my phone without the message. The method you provided wasn't the fix, before opening this thread I double checked and saw your method, but thanks anyway .
it was necessary to use a mirror. for example, in the bathroom
after brick and ressurect what write in (telephone settings) model?
Shekor said:
after brick and ressurect what write in (telephone settings) model?
Click to expand...
Click to collapse
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop
Kychera22 said:
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop
Click to expand...
Click to collapse
after bad ressurects i return my device le x626. to le x620 with eui 5.8.018S (stab.) it works normal. But was some bugs with 4g on (turn phone off) and google programs don's start.
But i fixed it all, now it works great, but i think is it bad?
take the stock firmware 28. and install. why use the old version? maybe get my firmware.
to use google apps. you need to download google installer, then after installation, in the settings give permissions to all Google apps.
and correctly to do so: to install firmware, then to start system and to configure it. and then only install the google gapps.
Update on unbrick
With my phone unbricked, it now works perfectly. But now the battery drains very fast. It drops by around 25% in less than half an hour with normal use such as watching videos on youtube in "360p" with all my apps closed, but still the battery drains. I have tried flashing different roms and clearing all partitions in twrp and flashing the CUOCO AND WOLFRED x.28s custom stock roms, but still the issue persists. This is very unusual as before my phone bricked, the battery would hold up for at least an hour before falling by 10 to 20 %. Does anyone have any speculations on why or any fixes? Please help.
UPDATE: I fixed by flashing the international version system.img only if you need it send me a message and I'll put up a link.
I have a camellia device, I tried to use a custom rom(pixel experience) the other day and some time later I wanted to revert back to stock rom.
I mistakenly flashed "camellian" rom instead of "camellia" rom through PE recovery.
Since then the device kept bootlooping.
So while troubleshooting, I tried to use the Sp flash tool.
For the roms I get them from "mifirm.net". I downloaded all the necessary drivers that I can find.
But the first version of SP flash tool, Sp flash tool v6,
the app asks for the "download-XML" file which I can't find ( screenshot in pic1).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I downloaded another version.
In this version though, the app doesn't recognize the xml file and gives the error
"5011; the scatter file has incorrect format! Please ask for help!"
I googled the reason why it gives me the error but the fix that people are giving didn't seem to fix this particular case. (pic 5,6,7).
.
.
.
I can't find any other fixes so I gave up on Sp flash tool.
I tried to use "mi flash tool" this time with Global rom.
Again, wrongly I flashed it with the Qualcomm settings a bunch of times and also got the bootloader locked. But the flash got successful somehow?
(I can't provide any pics because I am making this thread now after I've sent the phone to the Xiaomi service and I didn't take screenshots before sent it)
At this point I noticed that the stock recovery is back into the device.
Anyway, I used some 'shady' workarounds to get it unlocked again and when it was unlocked the phone said something like "your device is corrupt and can't be trusted".
It went away when I flash the stock rom with Mi flash tool again. ( I still used the Qualcomm settings)
When it's done it's still bootlooping but at least the "your device is corrupt and can't be trusted" message is gone.
I tried again a couple of times with different versions of roms; miui 12, 13, 14, global, china, india.
It was after that I discovered that there is "MTK" option in Mi flash tool.
I selected the "scatter, auth, and DA" files in it. But there seem to not have the "refresh" buttom to detect the device. I tried plugging into it with Fastboot mode and again while pressing volume down, up, and all buttons. Nothing showed up. (pic.8)
So what do you guys think? Do you have answers to any of the problems that I got during this journey? Please share your thoughts because there is no answers of a lot of my questions when I was trying to google it. I could not even use reddit because as you know, that site is under strike and apparently dead for the moment. I would love to know what experienced people have to say about this post. ^_^