Hi, this is my first post here so Hello everyone!
I tried to root P9 lite using below steps:
1. Get unlock code from DC-unlocker.
2. "fastboot oem unlock XXXXXXX..."
3. Phone was reset to factory default sow raw Android 7 was installed.
4. "fastboot boot twrp-3.1.1-0-eva.img" was not working (unknown or forbidden command, don't remember exact message)
5. fastboot flash recovery twrp-3.1.1-0-eva.img
6. After restart with recovery mode still Marshmallow recovery was running so I assumed flash failed.
7. I tried several time put other versions (twrp-3.0.2-0-eva and twrp-3.1.0-0-eva) but if I remember well last one was again installing twrp-3.1.1-0-eva again.
8. As that didn't helped I decided to give up and restore phone to previous state so locked bootloader using SRKToolHuawei-STABLE-V1.3-20160619
9. System restarted and restored to factory default and after running I saw message informing that password is needed to unlock mass storage (or mass memory). There was no onscreen keyboard so no possibility to type anything.
10. Restarted in recovery mode (volume up + power) and tried to recover system from Marshmallow recovery option (using WiFi) but it didn't helped.
11. During next restart I accidentally hold both volume up, down with power so phone tried probably to install system from SSD, but as there was no UPDATE.APP it just stopped at 5%. I left it as it is and after some time (around 5min) phone restarted.
12. Now after restart I see only info that "Your device is booting now...". All key combinations are causing phone restart and same message.
Please advise if there is anything what I can do now.
Will appreciate any help.
After discharging the battery phone started responding properly.
With connected USB cable, volume down and power buttons fastboot&rescue mode is working.
Phone unlocked
FRP unlocked
There is still EMUI recovery in place.
So looks like recovery partition was not replaced and bootloader was not locked again.
I can't tell what is in bootloader now.
System is cleared and can't reinstall it using Marshmallow recovery as it is probably end of maintenance.
My goal is to recover system now and I don't want to root it anymore.
How should I proceed?
JimiLincoln said:
After discharging the battery phone started responding properly.
With connected USB cable, volume down and power buttons fastboot&rescue mode is working.
Phone unlocked
FRP unlocked
There is still EMUI recovery in place.
So looks like recovery partition was not replaced and bootloader was not locked again.
I can't tell what is in bootloader now.
System is cleared and can't reinstall it using Marshmallow recovery as it is probably end of maintenance.
My goal is to recover system now and I don't want to root it anymore.
How should I proceed?
Click to expand...
Click to collapse
Hello,
it seemed that android 7 was your latest working OS.
Can you confirm it ?
If yes what was you complete firmware ?
(example: VNS-L31C432B418/VNS-L21C185B392, etc...)
note: 'EVA' stuff is for P9 variant, not P9 lite..
that's why you f***ed your phone...
Thank you Dadditz for your reply.
Dadditz said:
Hello,
it seemed that android 7 was your latest working OS.
Can you confirm it ?
If yes what was you complete firmware ?
(example: VNS-L31C432B418/VNS-L21C185B392, etc...)
Click to expand...
Click to collapse
It was 7 installed there for sure. And this is VNZ-L21.
Probably latest possible firmware version but can't be sure about this.
Can it be somehow checked now (guess not but not losing hope )?
Dadditz said:
Hello,
note: 'EVA' stuff is for P9 variant, not P9 lite..
that's why you f***ed your phone...
Click to expand...
Click to collapse
I took TWRP from here: twrp.me/huawei/huaweip9.html
When I look at devices list there is not P9 lite here: twrp.me/Devices/Huawei/
Which one should I use then?
P.S. sorry for no links or pictures but as new here I can't add them for now.
EDIT: I found TWRP in SRKToolHuawei-STABLE-V1.3-20160619\recovery\p9\p9.zip\twrpp9mm.img.
Guess I should load this one.
What do you think?
JimiLincoln said:
Thank you Dadditz for your reply.
It was 7 installed there for sure. And this is VNZ-L21.
Probably latest possible firmware version but can't be sure about this.
Can it be somehow checked now (guess not but not losing hope )?
I took TWRP from here: twrp.me/huawei/huaweip9.html
When I look at devices list there is not P9 lite here: twrp.me/Devices/Huawei/
Which one should I use then?
P.S. sorry for no links or pictures but as new here I can't add them for now.
EDIT: I found TWRP in SRKToolHuawei-STABLE-V1.3-20160619\recovery\p9\p9.zip\twrpp9mm.img.
Guess I should load this one.
What do you think?
Click to expand...
Click to collapse
I don't think firmware can be checked now...
Firmware may depend on where you live...
If you live in Europe it can be a branded one
(ex. vodafone: VNS-L21C02B345/6) or unbranded one(VNS-L21C432B505/6).
You cannot flash one of them if you have the other one.
You have to flash an OEMinfo file...
Anyhow you may try a factory reset first and let's hope it will restore the device.
Boot your phone with vol+and power till the e-recovery appear,
do the reset and report back how it went.
P.S.: P9 lite doesn't have an OFFICIAL TWRP.
Available unofficial versions can be founded searching into P9 lite XDA threads.
P.S.2 : A LITTLE SARCASM...
When you tinker with the phone you're not cooking
a plate of spaghetti with tomato sauce.
As you can see bricks are beyond the corner... and not always they can be solved...
Generally it is always better to ask before do, specially
if you don't know what you're doing ... but ... yes,
phone is yours and you can do anything you want...
Dadditz said:
Firmware may depend on where you live...
If you live in Europe it can be a branded one
(ex. vodafone: VNS-L21C02B345/6) or unbranded one(VNS-L21C432B505/6).
You cannot flash one of them if you have the other one.
You have to flash an OEMinfo file...
Click to expand...
Click to collapse
VNS-L21C22B383
Dadditz said:
Anyhow you may try a factory reset first and let's hope it will restore the device.
Click to expand...
Click to collapse
I don't have such option in Huawei eRecovery, only 3 below:
Download latest version and recovery
Reboot
Shutdown
When I used first option and connected trough WiFi I got error "Getting package info failed".
I tried that several times previous days but today this phone again surprised me.
After over 24 hours with discharged battery it became even more responsive (or maybe I just treated it different today).
Today I tried Huawei eRecovery again, it tried to download latest version trough WiFi and "Getting package info failed".
After restart I saw recovery wizard.
Went trough it and I got 7.0 working.
There was no screen keyboard but after recovering backup from HiSuite keyboard is was installed.
I'm also missing some other default android applications like file explorer, mirror, voice recorder, calc.
I'm wondering if it wasn't corrupted during my activities (eg "fastboot flash recovery twrp-3.1.1-0-eva.img").
Dadditz said:
P.S.: P9 lite doesn't have an OFFICIAL TWRP.
Available unofficial versions can be founded searching into P9 lite XDA threads.
Click to expand...
Click to collapse
When I mentioned about SRKToolHuawei-STABLE-V1.3-20160619.zip in my previous post it was one from:
forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Would you recommend it?
Dadditz said:
P.S.2 : A LITTLE SARCASM...
When you tinker with the phone you're not cooking
a plate of spaghetti with tomato sauce.
As you can see bricks are beyond the corner... and not always they can be solved...
Generally it is always better to ask before do, specially
if you don't know what you're doing ... but ... yes,
phone is yours and you can do anything you want...
Click to expand...
Click to collapse
I fully agree with you.
I was searching for many instruction how to do it properly and my mistake was that I stopped fallowing them at point where I tried to installed manually TWRP.
My general conclusion is that even if system was recovered I'm not sure if everything will be ok.
I was totally surprised how my phone reacted during last days so still everything may happen.
I see also some corruption in restored system as some apps are missing.
Any advise how this could be cleaned?
Maybe I should install this system again from some trusted package like from below topic?
forum.xda-developers.com/huawei-p9lite/development/huawei-p9-lite-firmware-compilations-t3517124
What about unlocked bootloader? Should I leave it with annoying screen during phone startup or lock again?
JimiLincoln said:
VNS-L21C22B383
Click to expand...
Click to collapse
This is a good new !!
JimiLincoln said:
I don't have such option in Huawei eRecovery, only 3 below:
Download latest version and recovery
Reboot
Shutdown
When I used first option and connected trough WiFi I got error "Getting package info failed".
I tried that several times previous days but today this phone again surprised me.
After over 24 hours with discharged battery it became even more responsive (or maybe I just treated it different today).
Today I tried Huawei eRecovery again, it tried to download latest version trough WiFi and "Getting package info failed".
After restart I saw recovery wizard.
Went trough it and I got 7.0 working.
There was no screen keyboard but after recovering backup from HiSuite keyboard is was installed.
Click to expand...
Click to collapse
Also a good new !!
JimiLincoln said:
I'm also missing some other default android applications like file explorer, mirror, voice recorder, calc.
I'm wondering if it wasn't corrupted during my activities (eg "fastboot flash recovery twrp-3.1.1-0-eva.img").
Click to expand...
Click to collapse
Yes, surely.
JimiLincoln said:
When I mentioned about SRKToolHuawei-STABLE-V1.3-20160619.zip in my previous post it was one from:
forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Would you recommend it?
Click to expand...
Click to collapse
No, this recovery isn't for nougat (android 7) version.
If you want, you can flash the one you find into HassanMirza01 TWRP thread.
Do not use 3.2.1, instead choose the 3.1.1-1 version, it's the most stable one.
JimiLincoln said:
I fully agree with you.
I was searching for many instruction how to do it properly and my mistake was that I stopped fallowing them at point where I tried to installed manually TWRP.
Click to expand...
Click to collapse
I agree too, it happen when process aren't properly followed...
JimiLincoln said:
My general conclusion is that even if system was recovered I'm not sure if everything will be ok.
I was totally surprised how my phone reacted during last days so still everything may happen.
I see also some corruption in restored system as some apps are missing.
Any advise how this could be cleaned?
Maybe I should install this system again from some trusted package like from below topic?
forum.xda-developers.com/huawei-p9lite/development/huawei-p9-lite-firmware-compilations-t3517124
What about unlocked bootloader? Should I leave it with annoying screen during phone startup or lock again?
Click to expand...
Click to collapse
Dude,
system can be fully recovered, especially now you're sure about
your latest firmware...
There was a thread with a list of stock apps, but it's been closed
because links are dead...
First thing, eliminate all safeties (fingerprints/pattern/pin)(you can add at the end of process)
You should try to reinstall your current firmware using Firmware Finder app,
download it from the big G store. Use dns/vpn method
and choose VNS-L21C22B383 FULLOTA-MF.
Also all info are inside the app. Using this method
the bootloader will be relocked.
If you wont succeed then i can tell you how to use twrp recovery
providing your stock full firmware.
Cheers
Dadditz said:
No, this recovery isn't for nougat (android 7) version.
If you want, you can flash the one you find into HassanMirza01 TWRP thread.
Do not use 3.2.1, instead choose the 3.1.1-1 version, it's the most stable one.
Click to expand...
Click to collapse
Thanks for that info. I will try it in a while when my wife will have new phone.
Dadditz said:
First thing, eliminate all safeties (fingerprints/pattern/pin)(you can add at the end of process)
Click to expand...
Click to collapse
Done
Dadditz said:
You should try to reinstall your current firmware using Firmware Finder app,
download it from the big G store. Use dns/vpn method
and choose VNS-L21C22B383 FULLOTA-MF.
Also all info are inside the app. Using this method
Click to expand...
Click to collapse
I fallowed instructions and choose first VNS-L21C22B383 FULLOTA-MF from the top (each version appear 2 times on this list).
Tried downloading trough DNS but got below message.
"Due to changes in the data exchange protocol between the Huawei server and the device, this function stopped its correct operation, but still works on older software that allows you to upgrade to one of the latest software if it has not already been done."
I tried with all FullOTA-MF versions on the list and same situation for all.
Because no other option I choose Download from last section (Other) and now I have 3 files on my phone:
update.zip
public/update_data_full_public.zip
VNS-L21_polkomtel_pl/update_full_VNS-L21_polkomtel_pl.zip
Should I install them manually?
If yes then how?
Vol+Vol-Power with those files on SD card or by TWRP?
Dadditz said:
the bootloader will be relocked.
If you wont succeed then i can tell you how to use twrp recovery
providing your stock full firmware.
Cheers
Click to expand...
Click to collapse
Many thanks for your help so far! Really appreciate that.
JimiLincoln said:
I fallowed instructions and choose first VNS-L21C22B383 FULLOTA-MF from the top
(each version appear 2 times on this list).
Tried downloading trough DNS but got below message.
"Due to changes in the data exchange protocol between the Huawei server and the device, this function stopped its correct operation, but still works on older software that allows you to upgrade to one of the latest software if it has not already been done."
I tried with all FullOTA-MF versions on the list and same situation for all.
Because no other option I choose Download from last section (Other) and now I have 3 files on my phone:
update.zip
public/update_data_full_public.zip
VNS-L21_polkomtel_pl/update_full_VNS-L21_polkomtel_pl.zip
Should I install them manually?
If yes then how?
Vol+Vol-Power with those files on SD card or by TWRP?
Many thanks for your help so far! Really appreciate that.
Click to expand...
Click to collapse
Dude, sorry if i wrote this.
I'm pretty sure you done everything correct,
but before attempt using the TWRP it's better if you
try again using Firmware Finder this way...
1 - connect to the internet, open the app, accept the disclaimer;
2 - add your complete firmware (add model) - VNS-L21C22B383;
3 - tap on your firmware;
4 - select the one with fullota-mf;
5 - tap check firmware access;
6 - tap check availability, accept disclaimer;
7 - you should have an 'availability of firmware' popup, tap ok;
8 - go back and tap 'get update through dns';
9 - a popup 'alert' you already faced will apper, tap ok;
10 - a new popup 'select dns method' will appear, tap 'auto',
then tap run vpn service and 'accept' the new connection request popup;
11 - you should now have the running vpn service in the notification panel...;
12 - minimize Firmware Finder;
13 - open settings > tap system updater,
you should find the VNS-L21C22B383 update (check multiple times);
14 - tap on it do download and apply the update;
15 - when the download reach 5%, stop the vpn service and continue doing the process...
It's something like THIS VIDEO.
Let me know...
Hi, your directions as well as movie you provided is giving much more details than application itself.
(In below description I had to use links without https as still I don't have enough posts to make them working.)
Dadditz said:
1 - connect to the internet, open the app, accept the disclaimer;
2 - add your complete firmware (add model) - VNS-L21C22B383;
3 - tap on your firmware;
4 - select the one with fullota-mf
5 - tap check firmware access;
6 - tap check availability, accept disclaimer;
7 - you should have an 'availability of firmware' popup, tap ok;
8 - go back and tap 'get update through dns';
9 - a popup 'alert' you already faced will apper, tap ok;
10 - a new popup 'select dns method' will appear, tap 'auto',
then tap run vpn service and 'accept' the new connection request popup;
11 - you should now have the running vpn service in the notification panel...;
12 - minimize Firmware Finder;
Click to expand...
Click to collapse
Done
Dadditz said:
13 - open settings > tap system updater,
you should find the VNS-L21C22B383 update (check multiple times);
Click to expand...
Click to collapse
No such option in my Phone. It looks like this
{
"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"
}
ibb.co/Zf4k0fX
when it should look like this
ibb.co/C0NfpJd
I found it using search menu
ibb.co/SDSYdjR
but when I tap it nothing is happening
Dadditz said:
14 - tap on it do download and apply the update;
15 - when the download reach 5%, stop the vpn service and continue doing the process...
It's something like THIS VIDEO.
Let me know...
Click to expand...
Click to collapse
I wish I could do that
JimiLincoln said:
Hi, your directions as well as movie you provided is giving much more details than application itself.
(In below description I had to use links without https as still I don't have enough posts to make them working.)
Done
No such option in my firmware finder
ibb.co/DYkBGVH
ibb.co/rsNTvdb
so i tried to proceed without checking.
Done
No such option in my Phone. It looks like this
ibb.co/Zf4k0fX
when it should look like this
ibb.co/C0NfpJd
I found it using search menu
ibb.co/SDSYdjR
but when I tap it nothing is happening
I wish I could do that :
Click to expand...
Click to collapse
Thank you for all your feedbacks dude.
Yep, it's clear the firmware is completely f***ed...
Tomorrow i will tell you how to use TWRP
and completely restore the device.
@JimiLincoln
You can restore the exact same rom you had on your smartphone ...
(I'm not sure, it seems it's a sort of firmware branded by vodafone)
but if I can afford, if it were you
i would install the European non-brand version (C432),
without bloatware and should also have the most updated security patch.
Is the phone single or dual sim?
Also, let me know if you want to have all stocks or
have the bootloader unlocked for future manipulations ...
Hello @Dadditz,
Dadditz said:
You can restore the exact same rom you had on your smartphone ...
(I'm not sure, it seems it's a sort of firmware branded by vodafone)
Click to expand...
Click to collapse
It is branded by Polkomtel (plus.pl).
Dadditz said:
but if I can afford, if it were you
i would install the European non-brand version (C432),
Click to expand...
Click to collapse
European non-brand version would be the best.
Dadditz said:
Is the phone single or dual sim?
Click to expand...
Click to collapse
Dual (hybrid)
Dadditz said:
Also, let me know if you want to have all stocks or
have the bootloader unlocked for future manipulations ...
Click to expand...
Click to collapse
I have bootloader unlocked and if future modifications will not erase phone data then we could start with minimal version.
Thanks
JimiLincoln said:
Hello @Dadditz,
It is branded by Polkomtel (plus.pl).
European non-brand version would be the best.
Dual (hybrid)
I have bootloader unlocked and if future modifications will not erase phone data then we could start with minimal version.
Thanks
Click to expand...
Click to collapse
You must use a twrp to rebrand your phone.
Download and flash the one i suggested you (3.1.1-1 by HassanMirza01)
When you done, come back for the files and the guide...
TWRP 3.1.1-1 For P9 Lite by HassanMirza01 installed.
I can enter it only by holding Power + Vol Up without USB connected.
When I hold Power + Vol Up with USB connected Huawei eRecovery is launched.
Is it normal?
JimiLincoln said:
TWRP 3.1.1-1 For P9 Lite by HassanMirza01 installed.
I can enter it only by holding Power + Vol Up without USB connected.
When I hold Power + Vol Up with USB connected Huawei eRecovery is launched.
Is it normal?
Click to expand...
Click to collapse
Yes, normal, you have both
stock and custom recovery now...
Ok, i will post a list of file you have to download:
1 - HuRUpdater04.zip file (will do the job);
2 - L21C432OEMinfo.zip file (dual sim);
THE FIRMWARE:
3 - update.zip ;
4 - update_data_full_public.zip ;
5 - update_full_VNS-L21_hw_eu.zip ;
Let file 3 the same name, rename file 4 from
update_data_full_public TO update_data_public,
rename file 5 from update_full_VNS-L21_hw_eu TO update_all_hw.
Names must mandatory match the ones I wrote to you, otherwise it won't work.
This is the procedure:
Use your PC, make a folder and rename it L21C432B506.
Copy files 3-4-5 (renamed) and HuRUpdater04.zip file into that folder.
(if you want you can keep the TWRP copying the .img file into that folder too).
Copy the folder into the SD.
Copy the OEMinfo file wherever you want into the SD.
Put the SD into the device...
Reboot into recovery and format DATA
(wipe>advanced wipe>tick data and tap format in the bottom right> type 'yes').
Reboot again recovery and wipe everything except SD
(wipe>advanced wipe>tick everything except sd).
Go in main menu, tap install, find and select OEMinfo file, let it flash...
When finished go in main menu and select REBOOT then Bootloader.
Once booted, connect the phone to your PC and
unlock again the bootloader. (quickly disconnect it from PC)
Device should automatically reboot into the recovery otherwise you can do
holding vol + and power button.
Now tap install, find your L21C432B506 folder,
select (only) HuRUpdater04.zip file and let it flash...
Your device should reboot into the system correctly,
if not (if passes over 15 mins) reboot into the e-recovery and
do a factory reset + wipe cache.
Done !!
Hello Dadditz,
Everything installed and working fine
Only bothering thing is message that device was unlocked and can't be trusted.
I will keep this for now as it may be useful at some point.
Many thanks Dadditz for your great help!!!
I will probably come back to this topic when my wife will have new phone, so I will play more with this P9 lite, customize system and learn more.
JimiLincoln said:
Hello Dadditz,
Everything installed and working fine
Only bothering thing is message that device was unlocked and can't be trusted.
I will keep this for now as it may be useful at some point.
Many thanks Dadditz for your great help!!!
I will probably come back to this topic when my wife will have new phone, so I will play more with this P9 lite, customize system and learn more.
Click to expand...
Click to collapse
Amazing polite guy,
i was very pleased to be able to help you, obviously, for what I know ...
It's not a big deal to have that 'annoying' message at boot.
Re-lock the bootloader is the only way to remove it.
You have more than one method:
Flash a previous version of your current firmware
and use Firmware Finder to update to the latest;
or wait untill a new version of your current firmware comes out
and use Firmware Finder to update to;
or use fastboot commands but it's seriously risky;
Keep it as is..
Cheers dude. :highfive:
help
i have a similar problem BUT i can't restart my p9 lite in recovery mode. I tried vol+ & power; vol - & power; vol +, vol - & pwer; only power. The result is always the same: "your device as been unlocked and can't be trusted....... Your device is booting now....". I try also to wait to descharge battery. After descharging, when i connect usb cable to recharge, the smartphone wake on with the same message..... Someone can help me?
Dadditz said:
Amazing polite guy,
i was very pleased to be able to help you, obviously, for what I know ...
It's not a big deal to have that 'annoying' message at boot.
Re-lock the bootloader is the only way to remove it.
You have more than one method:
Flash a previous version of your current firmware
and use Firmware Finder to update to the latest;
or wait untill a new version of your current firmware comes out
and use Firmware Finder to update to;
or use fastboot commands but it's seriously risky;
Keep it as is..
Cheers dude. :highfive:
Click to expand...
Click to collapse
Hello Dadditz,
thank you for your warm words.
I can only comment that still being polite is much easier than spending your private time on helping stranger
Also thanks for warning about locking bootloader by fastboot.
Related
You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!
Thanks for that muchly dude, hadn't checked that for a while.
Update seems to be stability improvements, power efficiency improvements and some yotamirror and panel improvements and features.
Its not 5.1, but it's an update, I'll take it.
And yeah, super glad moved to the RU ROM. Backing up now, will OTA flash update once that's done. SuperSU has been flashable everytime after an update so far so fingers crossed.
All up and running .
I was rooted, running RU 1.87 with TWRP - phone handled it all just fine - downloaded OTA, pressed install - it went to TWRP > flashed stock recovery back over itself > rebooted and installed.
Phone booted up, all working fine. Lost root - simple reboot and flash the SU.zip had sitting there from the last update. Cache and Dalvik wiped for good measure.
Reboot and all is well and back to normal but with a few improvements, lovely.
About as easy as it's even been done really.
Hope everyone else gets to enjoy the update through similarly smooth procedures .
Yeah, I ended up doing a fresh installation plus rooting, everything smooth. I'm never too sure what an update leaves behind.
It's really a great device, hopefully they'll keep updating things for a while. Of course version 6.0 would be welcomed... Apparently, by the numbering they use, next step would be either 1.2.xx with Android 5.1 or 2.x.xx with 6.0. Let's see.
Fair play, I toyed with idea of it, but was fresh from last install and honestly don't have the time to set everything up again.
My hope is they take all their good ideas from this and can at least join someone else in making a great device.
Saw a working bendy phone the other day, lets you turn pages on reading app by bending corner as you would a book etc. I thought if that could be combined with yota tech, then you have damn near the perfect tablet.
Honestly I don't think we'll get 5.1, let alone 6.0. They're refining their ideas in prep for Yotaphone 3, that and the possible tablet are their main focus right now.
Interestingly, the update flashed it's stock recovery over twrp - someone prepared for the possibility of root owners this time around. So they are still paying attention .
So any idea what's the difference between the EU and the RU rom? I mean there has to be some reason they are two separate roms.
To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.
Jeopardy said:
To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.
Click to expand...
Click to collapse
FYI the difference is essentially the product package configuration (app bundles that are pre-loaded) but there are also some differences between the resources used for the stock apps. One in particular (my personal fav ) is the dialler - the RU variant includes cyrillic characters regardless of language/locale setting (feature). The EU will give you a regular english-only dialler if you're using english locale settings
Vuche said:
You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!
Click to expand...
Click to collapse
Ho to flash the update zip file? I m stuck on 4.4.3...
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Does the new update solve the keyboard sensitivity issue??
zute333 said:
numerous guides and how to's in this forum and across XDA, as well as google.
download fastboot + adb > boot to download mode > flash twrp via fastboot commands > boot into twrp > flash zip.
There's obviously more to it than that, up to you to do the research.
Click to expand...
Click to collapse
i'm using this post as a minimalistic guide for myself (so i keep it up with my "discoveries" )
and ofc for been helped by everyone who wants to help me because i am completely new to android world cause this is my first android phone ever!
so.. let's get started!
i downloaded [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
version 1.4.3 doesnt works for me so i downloaded the 1.3 as suggested and worked.
then i enabled the download mode following the procedure:
Turn off the phone, then press and hold the volume down key + the power key at the same time. This should boot you into download mode.
Click to expand...
Click to collapse
note: phone MUST be disconnected form pc to be turned off.
now..
*does install twrp invalidate warranty?
EDIT: answer is YES cause of
TWRP 2.8.5.0 YotaPhone 2 recovery image said:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem
Click to expand...
Click to collapse
*is installing TWRP a mandatory step?
EDIT: the answer is NO. it seems that the mandatory part is to unlock the bootloader (the bad part for the warranty.. and that can erase ur data..) and this can be done following this guide How to Install TWRP Recovery on YotaPhone 2 untill point 6 included - which i am reporting here for easy of use.
How to Install TWRP Recovery on YotaPhone 2 said:
How to Flash TWRP Recovery on YotaPhone 2
1 - Setup ADB and Fastboot on your Windows PC.
2 - Enable USB debugging from developer options on your YotaPhone 2.
3 - Connect it to PC with a USB cable, if it asks for debugging authorization, permit it.
4 - Go to the folder where you downloaded the TWRP recovery image from the download link above on your PC and open a command window inside that folder by doing “Shift + Right click” on any empty white space inside the folder, then select “Open command window here”.
5 - (Skip this if your bootloader is already unlocked) Now to unlock the bootloader, type in the following command:
└ Beware that unlocking the bootloader may wipe your phone’s data. Make sure to backup first before proceeding.
adb reboot bootloader
Click to expand...
Click to collapse
└ This will reboot your phone to bootloader mode
fastboot oem unlock
Click to expand...
Click to collapse
└ This will unlock bootloader on your device.
6 - Now if your phone has rebooted and is no longer in the bootloader mode, then boot it back into bootloader mode with the “adb reboot bootloader” command.
Click to expand...
Click to collapse
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
error: cannot open 'firmware/emnc_appsboot.mbn'
error: cannot open 'firmware/boot.img'
error: cannot open 'firmware/system.img'
error: cannot open 'firmware/recovery.img'
error: cannot open 'firmware/cache.img'
error: cannot open 'firmware/radio/NON-HLOS.bin'
error: cannot open 'firmware/radio/sbli.mbn'
error: cannot open 'firmware/radio/rpm.mbn'
error: cannot open 'firmware/radio/tz.mbn'
error: cannot open 'firmware/enmc_appsboots.mbn'
Would you like to flash userdata[Y/N]:
Click to expand...
Click to collapse
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx
Hello guys, I downloaded Lollipop from the ftp but installation fails: no MD5 file found!
I downloaded all russian versions and also the 1.6 EU version... but no way I always get this error.
I'm using TWRP 2.8.5, I guess the last one, and in the tutorials I see this version...
Does anyone know how to solve? :crying:
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
The info is described in various posts across the yotaphone forum. Are you rooted? If not then there also many many guides across the internet for that.
Not walking you through the whole process, sorry. We all had to learn, once you do it's all much easier.
It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status
in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.
Melting Blaze said:
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx
Click to expand...
Click to collapse
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167
TKPL said:
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167
Click to expand...
Click to collapse
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
JAMMANDROID said:
It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.
Click to expand...
Click to collapse
yeah. is exactly what i did, but super panicing like a chicken without head
Melting Blaze said:
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
yeah. is exactly what i did, but super panicing like a chicken without head
Click to expand...
Click to collapse
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
Hi, download YotaFlasher, it permits you to download and flash firmwares in an easy way, and you don't need to know any shell command
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
TKPL said:
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening
Click to expand...
Click to collapse
Hello! I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB :laugh:
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.
Click to expand...
Click to collapse
seems that is the same for a lot of people if not everyone..
cause of this problem i am using this app gravity screen on/off.
it halves the problem cause now i have no problem for the amoled. and for problem i mean use the pwer button instead of simply swipe.
for the e-ink panel i still have to use the power button, only way it works.
HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks
masterpointer said:
HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks
Click to expand...
Click to collapse
Hi masterpointer,
You can almost always un-brick S3 with MTK SP Flash tool, but then, you need a firmware (with scatter file) to flash, and, you need to decide to flash KK or LP. If previously you ran KK and go LP (or, for some reason, other way around), you must use "upgrade firmware" instead of just "download" in tool. That's because KK and LP partition layout differ. You can find S3 firmwares and MTK SP Flash tool instructions in various places. Personally, I would perhaps recommend RC5 jiayu.de until a much anticipated MM upgrade arrives.
Just curious: what firmware did you run that would allow/suggest to upgrade/install resulting in getting stuck? Of course, some upgrade/install procedures may expect stock, not custom, recovery.
TWRP should give you adb, and you can always restore stock recovery put on SD card from there with 'dd'.
Dior DNA said:
Hi masterpointer,
You can almost always un-brick S3 with MTK SP Flash tool, but then, you need a firmware (with scatter file) to flash, and, you need to decide to flash KK or LP. If previously you ran KK and go LP (or, for some reason, other way around), you must use "upgrade firmware" instead of just "download" in tool. That's because KK and LP partition layout differ. You can find S3 firmwares and MTK SP Flash tool instructions in various places. Personally, I would perhaps recommend RC5 jiayu.de until a much anticipated MM upgrade arrives.
Just curious: what firmware did you run that would allow/suggest to upgrade/install resulting in getting stuck? Of course, some upgrade/install procedures may expect stock, not custom, recovery.
TWRP should give you adb, and you can always restore stock recovery put on SD card from there with 'dd'.
Click to expand...
Click to collapse
Thanks for trying to help.
However, I'm no expert so, for a start, I don't know what "KK" and "LP" refer to.
I do have a firmware (20150205-141543 (unzipped)) complete with a scatter file and I also have the MTK SP Flash Tool. I can copy the firmware to the external SD card (unzipped or zipped?) but how do I proceed from there? Please
masterpointer said:
Thanks for trying to help.
However, I'm no expert so, for a start, I don't know what "KK" and "LP" refer to.
I do have a firmware (20150205-141543 (unzipped)) complete with a scatter file and I also have the MTK SP Flash Tool. I can copy the firmware to the external SD card (unzipped or zipped?) but how do I proceed from there? Please
Click to expand...
Click to collapse
KK=KitKat aka Android 4.4.4
LP=Lollipop aka Android 5.1.1
20150205-141543 for sure will be KitKat.
Where did you get firmware?, it seems very old, older than anything I can find on needrom.
Are you sure you do not want to flash something newer? I suggest Lollipop RC5 from Jiayu.DE (to be found there).
You need to have unpacked files on PC for MTK SP Flash Tool to load the scatter file.
If you upgrade KK->LP then use "upgrade firmware" instead of "download".
Good luck!
I managed to flash my S3 Plus using Flash Tools in order to replace the useless rom published on Feb this year.
Having downloaded TWRP 3.0.0.0 on my pc I'm trying to install it on my phone using Flash Tools but I don't know how to open the .img file.
Can anyone help me please?
I tried many times following the process for TWRP but I got the answer
FAILED (remote: download the partition "recovery" is not allowed)
What is wrong?
Please HELP ...
masterpointer said:
HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks
Click to expand...
Click to collapse
Apparently you tried to perform an OTA update (over the air). Unfortunately, this will only work with Stock revovery. So - flash the original recovery.img with Sp flash Tool. Power on the phone again. Perform the OTA again.
Gesendet von meinem Telekom Puls mit Tapatalk
Blackcrown said:
Apparently you tried to perform an OTA update (over the air). Unfortunately, this will only work with Stock revovery. So - flash the original recovery.img with Sp flash Tool. Power on the phone again. Perform the OTA again.
Gesendet von meinem Telekom Puls mit Tapatalk
Click to expand...
Click to collapse
Sorry for the delay with my response. I have been away the last 2 or 3 weeks.
I'm afraid no luck.
I copied the raw zip files (JY-S3-2 and JiayuS2-5.1_20160121-212346_PC)) both from NeedRom. In TWRP I click on Install, select ext. card and click on one of the zip files and then when I swipe to "flash the screen" it starts processing, then shows some error messages and finally a red "Failed" message appears. The same thing happens when I click on other rom.
I have also tried to copy all the unzipped files from an old rom i had (20150205-141543) to the external card, but that doesn't seem to do anything.
I'm obviously doing something wrong. Is it possible to get a step-by-step instructions of how to flash a rom via TWRP? I'm fairly certain that the phone is ok if I can only get the system reinstalled.
Hoping you can help
@masterpointer: Ok, so I got it wrong. You don't try OTA but want to flash a zip from recovery. The steps you've taken seem fine to me, except: do not unzip the files because TWRP will take care of that.
I suspect that you use the wrong version of TWRP recovery. I will get back to you later in the evening (Central European time), when I can access my home PC, and tell you the name of the TWRP recovery file I used.
Blackcrown said:
@masterpointer: Ok, so I got it wrong. You don't try OTA but want to flash a zip from recovery. The steps you've taken seem fine to me, except: do not unzip the files because TWRP will take care of that.
I suspect that you use the wrong version of TWRP recovery. I will get back to you later in the evening (Central European time), when I can access my home PC, and tell you the name of the TWRP recovery file I used.
Click to expand...
Click to collapse
Thanks, looking forward to hearing from you. I really would like to fix it. I loved that phone...!
Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
masterpointer said:
I copied the raw zip files (JY-S3-2 and JiayuS2-5.1_20160121-212346_PC)) both from NeedRom. In TWRP I click on Install, select ext. card and click on one of the zip files and then when I swipe to "flash the screen" it starts processing, then shows some error messages and finally a red "Failed" message appears. The same thing happens when I click on other rom.
Click to expand...
Click to collapse
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.
Many thanks for the explicit explanation. That should keep me busy for a while! I'll have a go and let you know how I fare...
Once again, thank you!
Blackcrown said:
Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.
Click to expand...
Click to collapse
Ok, here's what I've done:
1. downloaded and installed the drivers (as per the Windows site) and the Rom you recommended (Jiayu_S3_5.1.1_rc5_flashtool.rar. Please note the ".RAR" extension!!! - No problems
2. I also downloaded the latest flashtools file. However, that needed a password (which was shown) to unzip it, but the shown password does not work! However, I have Flashtools_v5.1452.00 already installed so I used that.
3. opened flash-tool.exe, clicked on Scatter-loading and then on the MTK6752_Android_scatter.txt
4. opened the Download only box and selected "Firmware upgrade"
5. clicked on Options/Download and ticked "DA and DL with checksum.
6. clicked on Download...
...and this is where the story ends! The screen simply greys out and stays like that until I click on Stop. No yellow progress line appears. Nothing happens.
Am I doing something wrong?
masterpointer said:
Many thanks for the explicit explanation. That should keep me busy for a while! I'll have a go and let you know how I fare...
Once again, thank you!
Click to expand...
Click to collapse
Blackcrown said:
Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.
Click to expand...
Click to collapse
Hi again.
Just realised that the following screen appears in the tutorial (after the "Options/Download/check DA and DL"). The items on my screen stay the same
Preloader
MBR
EBR1
UBOOT
Those items (apart from the "Preloader") do not appear on my screen at any stage. I assume that has got something to do with the lack of further progress?
masterpointer said:
6. clicked on Download...
...and this is where the story ends!
Click to expand...
Click to collapse
This is, where the flashing begins! AFTER clicking download, connect the phone to your computer. Phone must be switched OFF. As soon as you connect it, Windows will recognize the switched-off phone (provided that you successfully installed the preloader VCOM driver) and start the flashing indicated by the yellow bar. If the phone is not recognized, start Windows again, then use another USB port and/or try another USB cable.
masterpointer said:
Hi again.
Just realised that the following screen appears in the tutorial (after the "Options/Download/check DA and DL"). The items on my screen stay the same
Preloader
MBR
EBR1
UBOOT
Those items (apart from the "Preloader") do not appear on my screen at any stage. I assume that has got something to do with the lack of further progress?
Click to expand...
Click to collapse
No. The person who made the tutorial used some screenshots from another phone. That's all. However, you should untick the "Preloader" image in SP Flashtool before hitting Download. The preloader is working (that's why you can connect to the phone) and should not be flashed again for safety reasons.
Blackcrown said:
This is, where the flashing begins! AFTER clicking download, connect the phone to your computer. Phone must be switched OFF. As soon as you connect it, Windows will recognize the switched-off phone (provided that you successfully installed the preloader VCOM driver) and start the flashing indicated by the yellow bar. If the phone is not recognized, start Windows again, then use another USB port and/or try another USB cable.
No. The person who made the tutorial used some screenshots from another phone. That's all. However, you should untick the "Preloader" image in SP Flashtool before hitting Download. The preloader is working (that's why you can connect to the phone) and should not be flashed again for safety reasons.
Click to expand...
Click to collapse
No luck, I un-ticked the preloader but as soon as I hit the download button, everything simply greys out. I have attached a screenshot for your perusal. I'm stuck!
{
"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"
}
masterpointer said:
No luck, I un-ticked the preloader but as soon as I hit the download button, everything simply greys out. I have attached a screenshot for your perusal. I'm stuck!
Click to expand...
Click to collapse
more info: Initially I had set the "download only" box to "firmware upgrade", but when I unticked the "preloader" as you suggested, the "firmware upgrade" automatically reverted to "download only" (I hadn't noticed). Same end result, though.
masterpointer said:
more info: Initially I had set the "download only" box to "firmware upgrade", but when I unticked the "preloader" as you suggested, the "firmware upgrade" automatically reverted to "download only" (I hadn't noticed). Same end result, though.
Click to expand...
Click to collapse
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.
1testi said:
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.
Click to expand...
Click to collapse
It works!!!!!!!
I thought I had to wait until being told by SP-FT to connect the phone. You last message made me think that maybe it should be connected BEFORE hitting the download button. So I did that and...Bob's-your-uncle.
I can't thank you enough for all your help. Wish I would get the opportunity to reciprocate. Many, many thanks.
1testi said:
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.
Click to expand...
Click to collapse
It works!!!!!!!
I thought I had to wait until being told by SP-FT to connect the phone. You last message made me think that maybe it should be connected BEFORE hitting the download button. So I did that and...Bob's-your-uncle.
I can't thank you enough for all your help. Wish I would get the opportunity to reciprocate. Many, many thanks.
Hello all,
I needed to root my phone (P8) in order to install some applications for file recovery. I did the following:
1) I unlocked bootloader (by obtaining the key on huawei pages, going to Settings, Developer options, USB debugging, HiSuite installed to get drivers, ADB Fastboot v.1.4 installed, volume- and power on. I got to the fastboot&rescue screen where after using the command in ADB Fastboot I gained "Phone unlocked" message)
2) I installed the TWRP in the phone (thru the Spanish console)
3) I copied UPDATE-SuperSU-v2.79.zip to internal memory
4) Volume+- Power on and got to the TWRP console where I chose install the UPDATE-SuperSU-v2.79.zip
5) everything looked fine, so I rebooted. Now I have looping logo and I am unable to unbrick the phone.
Any help please?
Thank you
Are you able to start your phone into TWRP?
Sometimes it is a little bit tricky! (hold Volumen-Up + Power, if the phone vibrates release the power button, keep holding the Volumen up button and release it if the Huawei logo disappears)
I have the same problem, and I can't get into TWRP
Paloik said:
Are you able to start your phone into TWRP?
Sometimes it is a little bit tricky! (hold Volumen-Up + Power, if the phone vibrates release the power button, keep holding the Volumen up button and release it if the Huawei logo disappears)
Click to expand...
Click to collapse
Hello,
Thanks for your answer. Yes, I am able to get to TWRP
Ok, what build version is on your P8 ?
Also what TWRP version did you flash ?
These answers are important.
Ps:-
If using B398 you MUST use the latest versions of TWRP and SU.
Just follow the instructions in post #1,
https://forum.xda-developers.com/huawei-p8/how-to/rooting-huawei-p8-marshmallow-emui4-0-1-t3431249
TO THE LETTER, using these linked to files (TWRP and SuperSU) and, hey presto, a fully rooted P8.
https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img.html
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
Sparkrite said:
Ok, what build version is on your P8 ?
Also what TWRP version did you flash ?
These answers are important.
Ps:-
If using B398 you MUST use the latest versions of TWRP and SU.
Just follow the instructions in post #1,
https://forum.xda-developers.com/huawei-p8/how-to/rooting-huawei-p8-marshmallow-emui4-0-1-t3431249
TO THE LETTER, using these linked to files (TWRP and SuperSU) and, hey presto, a fully rooted P8.
https://eu.dl.twrp.me/grace/twrp-3.1.1-0-grace.img.html
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
Click to expand...
Click to collapse
Hello Sparkrite,
the version I guess (I am not 100 % sure but I remember that I upgraded over the air about two months ago) is B397 and I installed TWRP version 3.0.2-0
Before I progress any further, tell me if the combination is wrong or I can follow the link you posted.
Thank you
You have absolutely nothing to lose by downloading and flashing the versions I have linked to.
Do so and let me know how you get on.
Sparkrite said:
You have absolutely nothing to lose by downloading and flashing the versions I have linked to.
Do so and let me know how you get on.
Click to expand...
Click to collapse
Hello,
I followed the points in the abovementioned post;
a) I was able to see phone unlocked,
b) I installed newer TWRP version (3.1.1.0)
c) I chose the "B" option for rooting and flashed kernel for root (version which is mentioned in the post) and
d) I flashed the SuperSU downloaded from your post
e) I rebooted and ended up with the following error message
Error!
error func No : 10 (boot image)
error No : 2 (load failded!)
I tried the steps c and d but still the same result.
Can you please give me further help?
Thank you
nameh said:
Hello,
I followed the points in the abovementioned post;
a) I was able to see phone unlocked,
b) I installed newer TWRP version (3.1.1.0)
c) I chose the "B" option for rooting and flashed kernel for root (version which is mentioned in the post) and
d) I flashed the SuperSU downloaded from your post
e) I rebooted and ended up with the following error message
Error!
error func No : 10 (boot image)
error No : 2 (load failded!)
I tried the steps c and d but still the same result.
Can you please give me further help?
Thank you
Click to expand...
Click to collapse
Start again and use option "A", Rooting in systemless Mode (by maintaining the original Stock-Kernel.
Thais is the method I used on B398.
Less chance of anything going wrong............
BTW, I can't see an option "D".
Sparkrite said:
Start again and use option "A", Rooting in systemless Mode (by maintaining the original Stock-Kernel.
Thais is the method I used on B398.
Less chance of anything going wrong............
BTW, I can't see an option "D".
Click to expand...
Click to collapse
I tried with the A option and still the same message
Rescue mode
Attention!
Please update system again
...
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed)
The c and d I mentioned in my previous post was related to the step-list (what I did)
nameh said:
I tried with the A option and still the same message
Rescue mode
Attention!
Please update system again
...
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed)
The c and d I mentioned in my previous post was related to the step-list (what I did)
Click to expand...
Click to collapse
Not to worry, have you done a stock update to B398 ?
And if so does the phone boot up correctly ?
This is what I meant by "Start again".
Sparkrite said:
Not to worry, have you done a stock update to B398 ?
And if so does the phone boot up correctly ?
This is what I meant by "Start again".
Click to expand...
Click to collapse
No, I just flashed the SU and twrp. Can you give me a hint where to search for the European version. All I found was a newer version than B398 or other regions.
Thank you
nameh said:
No, I just flashed the SU and twrp. Can you give me a hint where to search for the European version. All I found was a newer version than B398 or other regions.
Thank you
Click to expand...
Click to collapse
Well that explains why you are getting the same error.
First page that came up on Google search :-
http://www.stechguide.com/huawei-p8-b398-marshmallow-update/
Please follow the instructions EXACTLY.
Sparkrite said:
Well that explains why you are getting the same error.
First page that came up on Google search :-
http://www.stechguide.com/huawei-p8-b398-marshmallow-update/
Please follow the instructions EXACTLY.
Click to expand...
Click to collapse
You are the HERO! I am in! Although still the phone is not rooted at least it is working (which means "great to see it up and running again") :victory: :highfive:
I do not know why but Google never showed me the page you posted in its search results (maybe it is the new way of "personalizing" results) or any similar. It was always something from other regions or something which was full of ads and not really trustful.
Thank you again!!!
nameh said:
You are the HERO! I am in! Although still the phone is not rooted at least it is working (which means "great to see it up and running again") :victory: :highfive:
I do not know why but Google never showed me the page you posted in its search results (maybe it is the new way of "personalizing" results) or any similar. It was always something from other regions or something which was full of ads and not really trustful.
Thank you again!!!
Click to expand...
Click to collapse
Excellent !!
Its always good to "resurrect" a bricked phone.
Now, if you use the TWRP and SU I previously linked to and Method A you WILL have a working and most importantly a ROOTED phone.
https://forum.xda-developers.com/huawei-p8/how-to/rooting-huawei-p8-marshmallow-emui4-0-1-t3431249
Cheers.
Sparkrite said:
Excellent !!
Its always good to "resurrect" a bricked phone.
Now, if you use the TWRP and SU I previously linked to and Method A you WILL have a working and most importantly a ROOTED phone.
https://forum.xda-developers.com/huawei-p8/how-to/rooting-huawei-p8-marshmallow-emui4-0-1-t3431249
Cheers.
Click to expand...
Click to collapse
Thank you a lot... I mean A LOT!!! It works! I have literally no words. Thank you again
[Update as of May 23, 2020] - Thread no longer active and all download links are invalid
A brief history - A few weeks ago, i got fed up of EMUI and all the bloat. EMUI has a bunch of very useful features but i did miss the AOSP look and feel, root advantages. So, i tried magisk and couldn't get it to work with EMUI(pre 15.4 version). So i switched to Open krin 8.1 AOSP. Used it for a few days but it was too much of a sacrifice (VOLTE and Camera) and occasional buggyness for me to live with.
During this adventure, i found myself (multiple times) with a bricked device (A critical brick with FRP on aswell!).
After a lot of struggle(Specially to find working download links), i'm making this thread, to help fellow users like me.
Before we get started,
This is tested on my device but may not necessarily work with yours! I'm not responsible for any loss/damage/whatever caused because of the information in this thread.
Note 0 : Do not Quote the entire post!!
Note 1 : This guide will be updated as and when necessary.
Note 2 : These methods are only tested on Honor 8 Pro - Indian Variant(DUK-L09-C675)
Note 3 : This guide assumes the bootloader is unlocked.
Note 4 : Do text if you need any clarification on any step!
Thanks to @nanortemis (https://forum.xda-developers.com/honor-8-pro/how-to/restoring-dukfullotaromflasher-t3741223) for the ROM flasher
Download links for every file needed - Download links are now removed.
Let's get started.
Reboot your device into bootloader mode.
How? Method 11. Shut down the phone.
2. Hold the volume down button and connect the usb cable connected to your PC.Method 2 (If device is boot looping)1. Press and hold power button untill phone reboots.
2. Hold volume up key to boot to e-recovery.
3. Click shutdown.
4. Now follow Method 1.
Now that you are in bootloader mode,
You may find yourself in one of these three conditions
Condition 1. You read Phone unlock , FRP unlock ( Hurray !! This is the easiest to recover from.)
Condition 2. You read Phone unlock , FRP Lock AND you have TWRP flashed and working. ( Phew , there is still hope!)
Condition 3. You read Phone unlock , FRP Lock AND you have STOCK recovery! (Not sure how you got here, but this method is not tested by me.) (Please text if someone is stuck in this situation. I Will think of something if needed)(Guide is not yet updated with instructions on how to do this yet!)
Steps to recover from condition 1
1. Download stock rom files and stock rom flasher(from here) ( I have updated files for indian version.
Please get the version appropriate to your location.)
2. Extract files into a folder and transfer them to an exteral SD or USB OTG(If you can get it to work. I
Couldn't get my OTG to be detected) and insert it into your phone.
3. Reboot to recovery.
How? 1. Shutdown the deive(Look above for instructions, if needed.)
2. Hold volume up and then simultaniously press the power key. 4. In TWRP, erase everything except micro-sd/otg.
5. Reboot the device into recovery.
6. Flash the zip with the file name "FlashThisZip-DUK_FullOTA_ROM_flasher".
7. Done ! You should now be on Stock Indian oreo rom 8.0.0.323
8. (Optional) Relock bootloader (Check other guids please.)
Steps to recover from condition 2
1. Download and extract the twrp recovery files i made. ( You may use any stock emui (all partition)
backups you have made!
2. Transer the TWRP folder to External SD / OTG and insert it into the phone.
3. Reboot to recovery.
How? 1. Shutdown the deive(Look above for instructions, if needed.)
2. Hold volume up and then simultaniously press the power key. 4. In TWRP, erase everything except micro-sd/otg.
5. Restore the backup.
6. Done !!! To flash full stock fresh rom, read on.
7. (Optional) Boot up the phone, head into settings, enable developer options and enable OEM unlock.
8. (Optional) Now, simply follow steps from Condition 1(which is above!)
Guide is still under construction. I got this out as soon as i can to help anyone who is stuck. Please ignore any typos(They will be fixed when i find time to make this guide better).
All the best :good: :fingers-crossed:
---------------------------------------
Guide created on : 10 June, 2018
Last modification : None
Anirudh A said:
A brief history - A few weeks ago, i got fed up of EMUI and all the bloat. EMUI has a bunch of very useful features but i did miss the AOSP look and feel, root advantages. So, i tried magisk and couldn't get it to work with EMUI(pre 15.4 version). So i switched to Open krin 8.1 AOSP. Used it for a few days but it was too much of a sacrifice (VOLTE and Camera) and occasional buggyness for me to live with.
During this adventure, i found myself (multiple times) with a bricked device (A critical brick with FRP on aswell!).
After a lot of struggle(Specially to find working download links), i'm making this thread, to help fellow users like me.
Before we get started,
This is tested on my device but may not necessarily work with yours! I'm not responsible for any loss/damage/whatever caused because of the information in this thread.
Note 0 : Do not Quote the entire post!!
Note 1 : This guide will be updated as and when necessary.
Note 2 : These methods are only tested on Honor 8 Pro - Indian Variant(DUK-L09-C675)
Note 3 : This guide assumes the bootloader is unlocked.
Note 4 : Do text if you need any clarification on any step!
Thanks to @nanortemis (https://forum.xda-developers.com/honor-8-pro/how-to/restoring-dukfullotaromflasher-t3741223) for the ROM flasher
Download links for every file needed - https://drive.google.com/open?id=1qkFa9uMWWVWwnF3GS75Pzw6vDQ9GKx6J
Let's get started.
Reboot your device into bootloader mode.
How? Method 11. Shut down the phone.
2. Hold the volume down button and connect the usb cable connected to your PC.Method 2 (If device is boot looping)1. Press and hold power button untill phone reboots.
2. Hold volume up key to boot to e-recovery.
3. Click shutdown.
4. Now follow Method 1.
Now that you are in bootloader mode,
You may find yourself in one of these three conditions
Condition 1. You read Phone unlock , FRP unlock ( Hurray !! This is the easiest to recover from.)
Condition 2. You read Phone unlock , FRP Lock AND you have TWRP flashed and working. ( Phew , there is still hope!)
Condition 3. You read Phone unlock , FRP Lock AND you have STOCK recovery! (Not sure how you got here, but this method is not tested by me.) (Please text if someone is stuck in this situation. I Will think of something if needed)(Guide is not yet updated with instructions on how to do this yet!)
Steps to recover from condition 1
1. Download stock rom files and stock rom flasher(from here) ( I have updated files for indian version.
Please get the version appropriate to your location.)
2. Extract files into a folder and transfer them to an exteral SD or USB OTG(If you can get it to work. I
Couldn't get my OTG to be detected) and insert it into your phone.
3. Reboot to recovery.
How?1. Shutdown the deive(Look above for instructions, if needed.)
2. Hold volume up and then simultaniously press the power key.4. In TWRP, erase everything except micro-sd/otg.
5. Reboot the device into recovery.
6. Flash the zip with the file name "FlashThisZip-DUK_FullOTA_ROM_flasher".
7. Done ! You should now be on Stock Indian oreo rom 8.0.0.323
8. (Optional) Relock bootloader (Check other guids please.)
Steps to recover from condition 2
1. Download and extract the twrp recovery files i made. ( You may use any stock emui (all partition)
backups you have made!
2. Transer the TWRP folder to External SD / OTG and insert it into the phone.
3. Reboot to recovery.
How?1. Shutdown the deive(Look above for instructions, if needed.)
2. Hold volume up and then simultaniously press the power key.4. In TWRP, erase everything except micro-sd/otg.
5. Restore the backup.
6. Done !!! To flash full stock fresh rom, read on.
7. (Optional) Boot up the phone, head into settings, enable developer options and enable OEM unlock.
8. (Optional) Now, simply follow steps from Condition 1(which is above!)
Guide is still under construction. I got this out as soon as i can to help anyone who is stuck. Please ignore any typos(They will be fixed when i find time to make this guide better).
All the best :good: :fingers-crossed:
---------------------------------------
Guide created on : 10 June, 2018
Last modification : None
Click to expand...
Click to collapse
woaw.. is very well created! it might be handy in any case! thank you
Sent from my DUK-L09 using Tapatalk
Hi, Thanks for the guide.
However, I'm in deep shi*. I'm currently stuck in bootloop, I'm even unable to get to e-recovery. I'm able to get to fastboot though. Even though, I read PHONE Locked and FRP Unlock. What options do I have? I got my bootloader unlock code from EMUI but when I try to unlock bootloader, it says that the password is incorrect..
Check your password
tuniekonematei said:
Hi, Thanks for the guide.
However, I'm in deep shi*. I'm currently stuck in bootloop, I'm even unable to get to e-recovery. I'm able to get to fastboot though. Even though, I read PHONE Locked and FRP Unlock. What options do I have? I got my bootloader unlock code from EMUI but when I try to unlock bootloader, it says that the password is incorrect..
Click to expand...
Click to collapse
Hey,
While i was messing around with my H8P bootloader, i noticed an additional 's' in my password ! Probably while saving it would have got added.
I recommend cross checking if you're actually using the right password. (To the extent that you go through the request process again! Recommend doing this and taking screenshots as after a few days, you will no longer be able to request codes anymore!).
Also, post the error you get while trying to unlock the bootloader.
Anirudh A said:
Hey,
While i was messing around with my H8P bootloader, i noticed an additional 's' in my password ! Probably while saving it would have got added.
I recommend cross checking if you're actually using the right password. (To the extent that you go through the request process again! Recommend doing this and taking screenshots as after a few days, you will no longer be able to request codes anymore!).
Also, post the error you get while trying to unlock the bootloader.
Click to expand...
Click to collapse
Hi Anirudh,
I've gone through the same process several times and every single time I get the same Bootloader Password with the same error when trying to unlock:
{
"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"
}
That's the password Huawei gives me:
(I'm using H8 NON-pro version btw, sorry)
tuniekonematei said:
Hi Anirudh,
I've gone through the same process several times and every single time I get the same Bootloader Password with the same error when trying to unlock:
That's the password Huawei gives me:
(I'm using H8 NON-pro version btw, sorry)
Click to expand...
Click to collapse
Hey. Sorry for the late reply. Before investigating further, any progress?
Anirudh A said:
Hey. Sorry for the late reply. Before investigating further, any progress?
Click to expand...
Click to collapse
Hi,
Eventually I had to pay 15€ for DC Phoenix to be able to flash my Honor. Absolutely nothing helped and none of C434 firmwares worked on C900B131 rollback package, therefore I had to flash C636B130. I received an update to B360 which worked just fine. Then B380 update came which is a nightmare that bricks our phones and the reason I bricked my Honor 8 the first time (back in October of 2017). I had to reflash it through DC Phoenix once again. Later on I tried to move from B360 to B389 which bricked my phone AGAIN. So I am staying on B360 which, I think, works just fine. It is sad that I am unable to get the latest firmware updates but it is what it is. Although I really hate the notification on my Settings icon which informs to update the phone. I disabled all the Updater notifications and so on but it is still there.
I like Honor 8 and I've been always recomending it to everyone but as of now I doubt I'll ever buy Huawei phone again.
tuniekonematei said:
Hi,
Eventually I had to pay 15€ for DC Phoenix to be able to flash my Honor. Absolutely nothing helped and none of C434 firmwares worked on C900B131 rollback package, therefore I had to flash C636B130. I received an update to B360 which worked just fine. Then B380 update came which is a nightmare that bricks our phones and the reason I bricked my Honor 8 the first time (back in October of 2017). I had to reflash it through DC Phoenix once again. Later on I tried to move from B360 to B389 which bricked my phone AGAIN. So I am staying on B360 which, I think, works just fine. It is sad that I am unable to get the latest firmware updates but it is what it is. Although I really hate the notification on my Settings icon which informs to update the phone. I disabled all the Updater notifications and so on but it is still there.
I like Honor 8 and I've been always recomending it to everyone but as of now I doubt I'll ever buy Huawei phone again.
Click to expand...
Click to collapse
DC Phoenix always to the rescue. Unfortunately , this is the sad state of Huawei/Honor . Your device should be fixed free , because of Honors fault. Now that they're also not giving out unlock codes after a month , it's a direct screw you to all the advanced users. There's no predicting how this gamble will play out for them. I'm also not going to recommend Huawei /Honor to any advanced users . One plus has my money. However , Huaweis midrangers and just about OK for regular use.
i just restore your backup now stuck with bootloop frp lock phone lock
jazzy ╰_╯ said:
i just restore your backup now stuck with bootloop frp lock phone lock
Click to expand...
Click to collapse
Ensure your phone varient is what is specified in this thread. Phone lock is impossible. Please mention condition before, steps taken.
jazzy ╰_╯ said:
i just restore your backup now stuck with bootloop frp lock phone lock
Click to expand...
Click to collapse
Also, try factory reset, with data erase
Anirudh A said:
Ensure your phone varient is what is specified in this thread. Phone lock is impossible. Please mention condition before, steps taken.
Click to expand...
Click to collapse
i was on condition 2 i formated the phone as you said and downloaded twrp back up when i restored the back the first boot took me to erecovery then i try to go to twrp but it was gone i booted into fastboot and saw that phone is locked frp is lock stuck with bootloop ( which boots up my device to erecovery again and again) i do have an indian varient and was already on mm it was just that i had rooted device with magisk where i was not able to pass safenet so i thought to unroot it to stock and reroot again
---------- Post added at 01:52 AM ---------- Previous post was at 01:51 AM ----------
Anirudh A said:
Also, try factory reset, with data erase
Click to expand...
Click to collapse
already tried nothing happen
Anirudh A said:
Also, try factory reset, with data erase
Click to expand...
Click to collapse
are you going to help me out
jazzy ╰_╯ said:
i was on condition 2 i formated the phone as you said and downloaded twrp back up when i restored the back the first boot took me to erecovery then i try to go to twrp but it was gone i booted into fastboot and saw that phone is locked frp is lock stuck with bootloop ( which boots up my device to erecovery again and again) i do have an indian varient and was already on mm it was just that i had rooted device with magisk where i was not able to pass safenet so i thought to unroot it to stock and reroot again
---------- Post added at 01:52 AM ---------- Previous post was at 01:51 AM ----------
already tried nothing happen
Click to expand...
Click to collapse
Got it repaired by service center even though I want to do it by myself
jazzy ╰_╯ said:
Got it repaired by service center even though I want to do it by myself
Click to expand...
Click to collapse
Yikes. Is yours an Indian Honor 8 pro ?
jazzy ╰_╯ said:
Got it repaired by service center even though I want to do it by myself
Click to expand...
Click to collapse
Yikes. Is yours an Indian Honor 8 pro ?
I am stuck with condition 3. I have flashed project treble, but i wanted to revert back to stock so flashed stock ramdisk.img and my phone is showing phone unlock and frp lock. i can boot into the treble rr rom, but i want to revert back to stock emui. what should i do?
rhijuloves said:
I am stuck with condition 3. I have flashed project treble, but i wanted to revert back to stock so flashed stock ramdisk.img and my phone is showing phone unlock and frp lock. i can boot into the treble rr rom, but i want to revert back to stock emui. what should i do?
Click to expand...
Click to collapse
First thing, go to developer options and enable oem unlocking.. DO NOT FLASH/ DO ANYTHING BEFORE THIS STEP. Then you'll be on condition 1 so you can follow those steps.
Anirudh A said:
First thing, go to developer options and enable oem unlocking.. DO NOT FLASH/ DO ANYTHING BEFORE THIS STEP. Then you'll be on condition 1 so you can follow those steps.
Click to expand...
Click to collapse
can't change oem unlocking, it says bootloader unlocked. Kindly help me.
rhijuloves said:
can't change oem unlocking, it says bootloader unlocked. Kindly help me.
Click to expand...
Click to collapse
Bootloader and frp unlock are different and are independent of each other.Turn on your internet/connect to one and then try oem unlocking. Also, share the screenshot of the oem unlock screen.
Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...
fr4nk32 said:
Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...
Click to expand...
Click to collapse
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck
Dadditz said:
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck
Click to expand...
Click to collapse
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.
fr4nk32 said:
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.
Click to expand...
Click to collapse
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery
(name.of.recovery).img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added
Dadditz said:
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery.img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added
Click to expand...
Click to collapse
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.
fr4nk32 said:
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.
Click to expand...
Click to collapse
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...
Dadditz said:
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...
Click to expand...
Click to collapse
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!
fr4nk32 said:
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!
Click to expand...
Click to collapse
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.
Dadditz said:
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.
Click to expand...
Click to collapse
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.
fr4nk32 said:
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.
Click to expand...
Click to collapse
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards
Dadditz said:
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards
Click to expand...
Click to collapse
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....
fr4nk32 said:
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....
Click to expand...
Click to collapse
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )
Dadditz said:
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )
Click to expand...
Click to collapse
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:
fr4nk32 said:
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:
Click to expand...
Click to collapse
Ok i'm glad to see that worked..
I wish to thank in a special way Firmware Finder TEAM that with their
programs gave us the chance to solve many problems, THX guys. :good:
See you