Related
I`m having problems with booting into recovery on my OnePlus2.
This started after I did an update to OxygenOS 3.0 (beta) from my previously working TWRP.
OS itself is working, but I noticed that phone must be rerooted.. and here I found that Power + VolDown is not working anymore (phone is just stucked on 1+ logo).
OKay... I decided to reflash TWRP (who knows what may happened with it after update) but nothing helped. I tried different versions, even original OP2 recovery.. but result is always the same.
How I was trying to reflash:
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (31700 KB)...
OKAY [ 0.702s]
writing 'recovery'...
OKAY [ 0.248s]
finished. total time: 0.950s
but booting is always giving DTB error:
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.713s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.781s
I saw in other posts that dtb means broken image/etc, but I tried several and all were with the same result.
What else I can try? Please note that regular booting is working with no problems. The only problem I have is booting into recovery (with buttons and with fastboot).
Posted in wrong section. Should be in Q&A.
However to answer your question.
This has the same bootloader as H2OS Marshmallow. So, please TWRP users flash the way as mentioned below. Else you won't be able to boot into old twrp.
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!
Thanks and sorry for the wrong section.
Can you please give a bit more info on step 1 ? what rom to flash and how (current recovery is not working) ?
taha198 said:
Posted in wrong section. Should be in Q&A.
However to answer your question.
This has the same bootloader as H2OS Marshmallow. So, please TWRP users flash the way as mentioned below. Else you won't be able to boot into old twrp.
DOWNLOADS :-
recovery.img :- https://www.androidfilehost.com/?fid=24459283995297945
Step 1 :- Clean flash the ROM with new boootloader.
Step 2 :- From TWRP,go to Install Menu,click on Images button.
Step 3 :- Select the recovery.img you just downloaded.Select Recovery.Swipe to flash.
Step 4 :- From TWRP Home,reboot to recovery.
Step 5 :- Clean flash ROM with new bootloader again.
Step 6 :- Reboot into system !!!
Click to expand...
Click to collapse
Follow guide this guide
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Now it is clear. you gave me an instruction to what I should do to avoid the situation where I am now. but there is also another instruction how to fix my problem.
Thanks one again!
taha198 said:
Follow guide this guide
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
It seems you are flashing the wrong version of TWRP. The version you are flashing isn't going to work on OOS 3.0 Beta. You need specifically the H2-MM TWRP 3.0.0-1 version, which, like the previous posters listed can be downloaded here:
https://www.androidfilehost.com/?fid=24459283995297945
If you are flashing a version that you downloaded direct from TWRP's website, it won't work.
I tested different versions, including 3.0.x mentioned by you. all of them gave the same result.
Btw, the recovery tool in the link above already fixed my problem.
madferretx said:
It seems you are flashing the wrong version of TWRP. The version you are flashing isn't going to work on OOS 3.0 Beta. You need specifically the H2-MM TWRP 3.0.0-1 version, which, like the previous posters listed can be downloaded here:
https://www.androidfilehost.com/?fid=24459283995297945
If you are flashing a version that you downloaded direct from TWRP's website, it won't work.
Click to expand...
Click to collapse
Delphir said:
I tested different versions, including 3.0.x mentioned by you. all of them gave the same result.
Btw, the recovery tool in the link above already fixed my problem.
Click to expand...
Click to collapse
Could you describe exactly what did you do? At the link that you mention there is 3 methods and different recovery tools.
I followed "Method 1" from the link and then flashed TWRP recovery on top of it - this way it worked with no problems. Flashing TWRP (different versions) without this recovery tool was always unsuccessful.
Well, as long as you flash the chinese HydrogenOS version of TWRP you should get a bootable recover system.
Best regards
Peter
I recently rooted my OnePlus 2.
The bootloader is unlocked.
The twrp recovery was working fine till I flashed to oxygen os 2.0.0
Now the OnePlus2 is not booting into recovery.
There is a oxygen os update (3.5.8) available which shows in the system updates section in settings.
Can I update to this without the recovery??!
Will that help to go back to twrp recovery?!
Please help
Nandish C said:
I recently rooted my OnePlus 2.
The bootloader is unlocked.
The twrp recovery was working fine till I flashed to oxygen os 2.0.0
Now the OnePlus2 is not booting into recovery.
There is a oxygen os update (3.5.8) available which shows in the system updates section in settings.
Can I update to this without the recovery??!
Will that help to go back to twrp recovery?!
Please help
Click to expand...
Click to collapse
Flashing stock firmware will overwrite twrp, so always flash OOS and twrp after it in case you want to keep it, twrp can flash the twrp.img file, not only zips, I never used OOS2 but actually you should have stock recovery back by flashing OOS, it seems that something went wrong. Just flash twrp again, like the first time you did it, if you want to go back to stock including recovery flash OOS full zip again and reboot...
Only OOS will overwrite twrp, custom roms won't
Sent from my OnePlus 2 using XDA Labs
I have a Huawei P9 lite. (VNS-L31 dual sim) . I tried to install medrom 3 and after flashing, phone didn't boot up. So I flashed b161 firmware again using 3 button method and phone booted up. Then I realized I couldn't add my google account. After searching on xda I found a method to fix that.(flashing oem info ). But after doing that, when the phone boots up after the huawei logo the error message which says "your device has been unlocked" has become red.( Usually it's yellow). And in about phone my model number has been changed to something like hi6250 or hi650.( Can't remember the exact thing). Then I tried to reflash my b161 firmware using 3 button menu and voila. It says incompatible version. I can't flash it. Then I replaced my build prop with my friend's phone's build prop. But unfortunately it has the B151 version. Though I have B161 version installed, my about phone says it has B151 version. And I can't flash stock firmware using twrp or dload method od any how. Please help
Nemeroz said:
I have a Huawei P9 lite. (VNS-L31 dual sim) . I tried to install medrom 3 and after flashing, phone didn't boot up. So I flashed b161 firmware again using 3 button method and phone booted up. Then I realized I couldn't add my google account. After searching on xda I found a method to fix that.(flashing oem info ). But after doing that, when the phone boots up after the huawei logo the error message which says "your device has been unlocked" has become red.( Usually it's yellow). And in about phone my model number has been changed to something like hi6250 or hi650.( Can't remember the exact thing). Then I tried to reflash my b161 firmware using 3 button menu and voila. It says incompatible version. I can't flash it. Then I replaced my build prop with my friend's phone's build prop. But unfortunately it has the B151 version. Though I have B161 version installed, my about phone says it has B151 version. And I can't flash stock firmware using twrp or dload method od any how. Please help
Click to expand...
Click to collapse
That's normal if the message is red, it means that the bootloader Will be relocked.
Now for the build prop, download b161 version, use huawei firmware extractor , extract boot.img system.img and cust.img
And by fastboot type :
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot reboot
And voila, b161 is installed in your phone !
Sent from my HUAWEI VNS-L31 using XDA Labs
I can ont flash the boot.img. I get this error:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\161_entpackt>Fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13998 KB)...
OKAY [ 0.300s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.322s
Schrotty35 said:
I can ont flash the boot.img. I get this error:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\161_entpackt>Fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (13998 KB)...
OKAY [ 0.300s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.322s
Click to expand...
Click to collapse
If fastboot say "FAILED (remote: Command not allowed)", its because your bootlaoder is locked, reunlock it !
In TWRP it says unable to mount Data :/
Ax3noX_ said:
If fastboot say "FAILED (remote: Command not allowed)", its because your bootlaoder is locked, reunlock it !
Click to expand...
Click to collapse
I noticed that in TWRP it says unable to mount data :/ What can i do now
I don't know what is "mount data", i cant help you with that ?
Ax3noX_ said:
I don't know what is "mount data", i cant help you with that
Click to expand...
Click to collapse
Its okay. Still looking for a help dude. Any help is highly appreciated :good:
Nemeroz said:
Its okay. Still looking for a help dude. Any help is highly appreciated :good:
Click to expand...
Click to collapse
Code:
fastboot oem unlock XXXXXX
fastboot flash recovery recovery_stock.img
Unable to read/mount data says your encryption key got changed by something, whatever. You need to Wipe Internal storage and flash twrp again ( I recomment matic`s ) Reboot to recovery again, if you got one, flash a flashable fw via twrp. I Dont know if the stock recovery Accepts a fully wiped intern storage, i guess not and it declines the update.app method.
In the best case for sure you recover an older backup to get the Same enc. Key back
WieserZ1C said:
Unable to read/mount data says your encryption key got changed by something, whatever. You need to Wipe Internal storage and flash twrp again ( I recomment matic`s ) Reboot to recovery again, if you got one, flash a flashable fw via twrp. I Dont know if the stock recovery Accepts a fully wiped intern storage, i guess not and it declines the update.app method.
In the best case for sure you recover an older backup to get the Same enc. Key back
Click to expand...
Click to collapse
Try to hold Vol+ and the power button and if you enter in Huawei recovery, select wipe data / Factory reset
Ax3noX_ said:
Try to hold Vol+ and the power button and if you enter in Huawei recovery, select wipe data / Factory reset
Click to expand...
Click to collapse
Tried that. But didnt work mate 😔
Nemeroz said:
Tried that. But didnt work mate 😔
Click to expand...
Click to collapse
Flash oeminfo (dowbload in the ultimate guide of nougat) and put the update.app of the marshmallow version in the dload folder then hold Vol+, vol- and power.
Its worked for me
Tell me if it work
(Sorry for my bad english, im french
I'd recommend using SP Flash tool. It's saved my ass multiple times.
Where you got the Scatter File for the p9 lite
Nantonix said:
I'd recommend using SP Flash tool. It's saved my ass multiple times.
Click to expand...
Click to collapse
Spflash tool is flash tool only for mtk devices... And p9 lite doesnt have a mtk soc !
---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------
hanzox5 said:
Where you got the Scatter File for the p9 lite
Click to expand...
Click to collapse
It doesn't exist !
i wanted to convert the device to dual sim, so i tried to restore the backed-up partitions using meticulus' TWRP. But it says unable to mount /data every time i try to format it.
I know i made a big mistake, but that's how i learn..
this thread has worked for me
https://translate.google.co.uk/tran...m/showthread.php?t=1261335&edit-text=&act=url
Hello I went back the MN when startups is only then the logo after screen dark
please help me !!!
sorry for my english
pinhpongk said:
Hello I went back the MN when startups is only then the logo after screen dark
please help me !!!
sorry for my english
Click to expand...
Click to collapse
do a factory reset..if doesn work reflash stock marshmallow b160
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
algnerd said:
Since I lost everything from the boot to the recovery to the system part to anything, i haven't been able to boot the phone;
I can access erecovery but when I try to recover the phone it stops at downloading and then says couldn't connect to servers so that's dead;
I can access TWRP but when I try to flash MM, it returns errors saying that it couldn't mount partitions (Vendor, cust and other...)
I can access fastboot mode. Some people suggested that I should try recovering using dload but the transfert rate to the sd card is taking forever;
Now I extracted everything from update.app using huawei firmware extractor (see http://imgur.com/MWeCCXi ) what should I flash (via fastboot) and in what order?
I would really appreciate the help.
Click to expand...
Click to collapse
Boot.img , recovery.img , cust.img , system.img.
Claleale said:
Boot.img , recovery.img , cust.img , system.img.
Click to expand...
Click to collapse
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
algnerd said:
Are those the correct commands?
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
?
Click to expand...
Click to collapse
Yes
Claleale said:
Yes
Click to expand...
Click to collapse
Flashing cust and system returned failes
For cust: (failed remote: partition error)
For syst: (failed remote: sparse flash write failure)
Since I was running nougat before messing up the phone, it had to be System and Boot extracted from the nougat update
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice... I would never flash that but okay, that's why we are here
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM / AICP?
Schlengge said:
By Nougat I assume you mean the file that has been digged out somewhere in the web and that is floating around here in the forums?
Well we all don't really know what this build exactly is, which makes it very hard to reconstruct your errors and give you advice...
Do you have a TWRP backup that you can restore (and if no, maybe somebody can upload you a clean TWRP restore file)?
Have you tried flashing CM?
Click to expand...
Click to collapse
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
algnerd said:
...
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
You have to use the report button on your own OP. In the report text box, just ask mods to close your thread. The mod who is assigned to this forum will handle your request.
algnerd said:
Indeed, the same build that was floating in here.
I was able to resurect my phone from the dead by flashing boot, system and recovery from nougat build then I downgraded to MM untill a more stable release;
Thanks for your support anyway.
(If you know how to close this thread, you're more than welcome to do it )
Click to expand...
Click to collapse
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
thomasedwardbullen1986 said:
Hi there. Earlier I spent a few painful hours in the same boat you were in. I've managed to get back to a fresh install of the Nougat build from this thread, but can't seem the downgrade to MM using the (translated from Spanish) instructions found here (linked from that first thread). How did you manage to get back to MM?
(I should add that I tried to flash boot, system and recovery via fastboot without any success).
Cheers
Click to expand...
Click to collapse
May god have mercy on your soul.
For the downgrade, I didn't use the b161 directly. I flashed some oeminfo provided in the same folder as the TWRP. Then used b150 ans the three boutons method. Worked like a charm.
Hope it will help you downgrade your phone.
I have the same problem, someone could explain it to me step by step, please
ask help
Hello
My name is EL HADJI MODOU SOW.I request your help concerning a big problem that I meet with my phone huawei P9 lite vns-l31c113b364 (these is the serial number 4TE0216B08004097) .in fact I wanted to activate the second sim then j I made a mistake handling the shot the system is corrupt and now I can not use my phone. I tried to flash it but I can not find a good frimeware. All the flash files that I find are working except the cust.img , vendor.img and product.img. what happens when I flash the cust.img (H: \ SRKToolHuawei-Lod-Chong-V2.0-20161002> fastboot flash cust CUST.img
target reported download size of 471859200 bytes
sending 'cust' (435462 KB) ...
OKAY [10.711s]
writing 'cust' ...
FAILED (remote: partition error)
finished. total time: 10.729s).
please help me I'm really teriified
this is my email:[email protected]
So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.
Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it
xXRobyXx said:
Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it
Click to expand...
Click to collapse
Hi,
you have to rebrand to the Global version (IMO) :
1. install TWRP 3.0.2.0 , Link
2. In TWRP flash C432 oeminfo.zip Link
3. Go back to TWRP's menu without reboot
4. Follow instructions (from step 3.).
-Alf- said:
Hi,
you have to rebrand to the Global version (IMO) :
1. install TWRP 3.0.2.0 , Link
2. In TWRP flash C432 oeminfo.zip Link
3. Go back to TWRP's menu without reboot
4. Follow instructions (from step 3.).
Click to expand...
Click to collapse
Thanks for your help. Is the VNS-L31C432B370 firmware compatible with single sim?
xXRobyXx said:
Is the VNS-L31C432B370 firmware compatible with single sim?
Click to expand...
Click to collapse
No, that's why I gave you the link to oeminfo dual Sim. If that's a problem for you, try looking for the B371, I didn't find one.
-Alf- said:
No, that's why I gave you the link to oeminfo dual Sim. If that's a problem for you, try looking for the B371, I didn't find one.
Click to expand...
Click to collapse
It's not a problem for me. What problems could I encounter if I use a dual sim firmware?
M
xXRobyXx said:
It's not a problem for me. What problems could I encounter if I use a dual sim firmware?
Click to expand...
Click to collapse
It has no effect on the phone's functionality.
Btw, there's B371 Link ,but it may be password protected . For Single SIM firmware use this Oeminfo.zip
-Alf- said:
M
It has no effect on the phone's functionality.
Btw, there's B371 Link ,but it may be password protected . For Single SIM firmware use this Oeminfo.zip
Click to expand...
Click to collapse
I tried to flash the C432 oeminfo, but after rebooting a black screen with red text appears and I can't unlock my phone because it's unable to decrypt the internal archive. Same thing with the singlesim oem info.
Also I can't mount the Internal Storage from TWRP because it results as 0 MB.
The only way I found to solve this issue is by restoring the original oeminfo from a previous backup.
xXRobyXx said:
tried to flash the C432 oeminfo, but after rebooting a black screen with red text appears
Click to expand...
Click to collapse
-Alf- said:
Go back to TWRP's menu without reboot
Click to expand...
Click to collapse
-Alf- said:
4. Follow instructions (from step 3.).
Click to expand...
Click to collapse
I've installed the с432b370 update correctly, but I can't flash the data package (update_data_full_VNS-L31_hw_eu.zip).
xXRobyXx said:
I've installed the с432b370 update correctly, but I can't flash the data package (update_data_full_VNS-L31_hw_eu.zip).
Click to expand...
Click to collapse
it happens sometimes...
Just to be sure - reboot to fastboot mode and run command:
fastboot oem get-build-number
and post result.
-Alf- said:
it happens sometimes...
Just to be sure - reboot to fastboot mode and run command:
fastboot oem get-build-number
and post result.
Click to expand...
Click to collapse
Now it is NRD90M test-keys, before it was VNS-L31ITAC555B160
xXRobyXx said:
Now it is NRD90M test-keys, before it was VNS-L31ITAC555B160
Click to expand...
Click to collapse
Okay, now read carefully:
1. Download TWRP for Nougat Link
2. Flash it over eRecovery (!)
using command:
fastboot flash recovery2 twrp3102.img (recovery2 , not recovery!)
3. Flash stock Recovery Nougat
Link use:
fastboot flash recovery xxxxx.img
4. Reboot, when yellow warning appears, press and hold Volume Up for 3-4 seconds, you should boot into TWRP
5. In TWRP select Wipe - Format data - yes - confirm. Go back - Reboot - System
6. And again, after yellow warning Volume Up and reboot TWRP. Now you can try install second .zip file hw_eu.
7. Reboot into Recovery and do factory reset.
Good luck!
-Alf- said:
Okay, now read carefully:
1. Download TWRP for Nougat Link
2. Flash it over eRecovery (!)
using command:
fastboot flash recovery2 twrp3102.img (recovery2 , not recovery!)
3. Flash stock Recovery Nougat
Link use:
fastboot flash recovery xxxxx.img
4. Reboot, when yellow warning appears, press and hold Volume Up for 3-4 seconds, you should boot into TWRP
5. In TWRP select Wipe - Format data - yes - confirm. Go back - Reboot - System
6. And again, after yellow warning Volume Up and reboot TWRP. Now you can try install second .zip file hw_eu.
7. Reboot into Recovery and do factory reset.
Good luck!
Click to expand...
Click to collapse
Code:
target reported max download size of 471859200 bytes
sending 'recovery2' (24462 KB)...
OKAY [ 0.713s]
writing 'recovery2'...
FAILED (remote: Command not allowed)
finished. total time: 0.713s
I'm sure that Phone and FRP are unlocked.
xXRobyXx said:
Code:
target reported max download size of 471859200 bytes
sending 'recovery2' (24462 KB)...
OKAY [ 0.713s]
writing 'recovery2'...
FAILED (remote: Command not allowed)
finished. total time: 0.713s
I'm sure that Phone and FRP are unlocked.
Click to expand...
Click to collapse
In other words, my instructions are wrong?
Okay, have a nice evening!
-Alf- said:
In other words, my instructions are wrong?
Okay, have a nice evening!
Click to expand...
Click to collapse
Hey, I'm not doubting your instructions! Hahaha.
I'm just asking, what should I do now? I can't flash TWRP to recovery2 if it doesn't allow me to commit any command.
xXRobyXx said:
doesn't allow me to commit any command.
Click to expand...
Click to collapse
And you are sure that Phone and FRP are unlocked? Hahaha.
-Alf- said:
And you are sure that Phone and FRP are unlocked? Hahaha.
Click to expand...
Click to collapse
Yeah
xXRobyXx said:
Yeah
Click to expand...
Click to collapse
Restart your phone, if the BL is really unlocked, after restart appears on screen yellow warning. Fastboot sometimes lies...
-Alf- said:
Restart your phone, if the BL is really unlocked, after restart appears on screen yellow warning. Fastboot sometimes lies...
Click to expand...
Click to collapse
Okay, finally I flashed TWRP. After restart, I pressed Volume Up key but it remains on the yellow warning screen with the text "Your device is booting now...".
Edit:
I solved this by installing Venus TWRP for P9 lite. Then, I followed all the instructions and updated to B416 through dlaod, and later to B418 through OTA. Additionally, I had to unlock the bootloader again and root.
Now I have a fully-functional P9 lite updated to Android Nougat
xXRobyXx said:
Hi everyone. I've already rooted my Huawei P9 lite and now I'd like to update it to Android Nougat.
I tried to install different versions of firmware through OTA, but none of them worked out well. I'm starting to think that this is due to the firmware which are not compatible with my device, and considering that my build number is quite uncommon, that could also be the case. I read from some threads that I have to unroot and lock the bootloader again in order to perform the update, but honestly I'm too lazy right now and I'd prefer to keep my device rooted if it's possible.
Does anybody know what could I do in this case?
OEM Build Number: VNS-L31ITAC555B160
OEM Product Model: HUAWEI VNS-L31
Vendor Country: h3g/it
Click to expand...
Click to collapse
Which process did you follow for the root?