Related
A reddit user captured his link to the DP
Here is the link
https://android.googleapis.com/pack.../f9cb176ee75399a48e927d9f1bd6aeb6a643272c.zip
Credit: https://m.reddit.com/r/Nexus6P/comments/5edfam/captured_my_ota_url/?compact=true
Flash guide: *should* work
1. Boot twrp on DP1
2. flash SU of choice
3. reboot
4. install FlashFire from play store
5. Select "Flash firmware package"
6. Select the zip
7. Flash it!
**** A FEW DISCLAIMERS
**** TWRP seems to be based on 6.0.1 and the OTA can only be flashed on 7.1.1
**** In this case twrp will NOT flash this OTA file
**** FlashFire IS REQUIRED
**** I am not google. Yes I am sorry that force encrypt wiped your data or you got stuck in
**** a boot loop because you flashed it incorrectly BUT I am NOT google, I am NOT even
**** the person who captured the link for the ota ALL I DID WAS SHARE IT
**** If your data partition got wiped, you got stuck in a boot loop, or the guide didn't work
**** chances are you did something wrong
**** if you would like support but Google up in the DMs
**** I am happy to help just know I won't troubleshoot what you screwed up
Would we get a full OTA as well?
gqukyo said:
Would we get a full OTA as well?
Click to expand...
Click to collapse
If by full OTA you mean full ROM zip, here it is.
WelcomeToTheSkye said:
A reddit user captured his link to the DP
Here is the link
https://android.googleapis.com/pack.../f9cb176ee75399a48e927d9f1bd6aeb6a643272c.zip
Credit: https://m.reddit.com/r/Nexus6P/comments/5edfam/captured_my_ota_url/?compact=true
Click to expand...
Click to collapse
Sorry for being a noob but do I flash the zip file through TWRP or is there some other way? I am rooted with custom recovery on DP1.
Thanks
marmeak7 said:
Sorry for being a noob but do I flash the zip file through TWRP or is there some other way? I am rooted with custom recovery on DP1.
Thanks
Click to expand...
Click to collapse
If you're rooted, use flash fire from play. It restores twrp and root after updating. Haven't used any other method. No problems. Best app ever.
Just updated. Sound louder, November security patch and overall smoother scrolling.
No regrets getting the 6P. Amazing phone.?
It work fined at my Nexus 6p. All the rooted apps working fine. Thank you very much for your sharing. Appreciated it.
Just curius, has anyone of you guys unencrypted?
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Can't flash it in TWRP --> error
edit: I got E3001: the build fingerprint doesn't match. How can I fix this?
I succesfully flashed using Flashfire.
First thing I noticed is the many (repeating) superuser notifications I get for apps getting root during boot.
DRD70 said:
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Click to expand...
Click to collapse
the same for me... I only have twrp and have modified system... maybe is because of that... but I tought that would not be a problem... guess I'm going the twrp way
hmm, now I get it... this is not a full ota file.
Will I be able to flash it via TWRP like I did with the full OTA file from DP1 ??
^You need the full ota not this type of ota...
So this is the update from DP1 to DP2, correct? Is there any other way to install it besides with Flashfire? I've always installed from my PC, so is there any way to sideload it or install the zip through TWRP?
DRD70 said:
I installed it with flashfire but I'm still at DP1... Am I doing something wrong?
I installed it as flash zip or ota but nothing still got the message to update.
Is it because I have installed custom kernel?
Click to expand...
Click to collapse
You must be on dp1 and select flash firmware package not flash zip
ahmd gomaa said:
You must be on dp1 and select flash firmware package not flash zip
Click to expand...
Click to collapse
I was on dp1 and my first selection was firmware package and nothing happened. So i tried the other with the same outcome.
I finally revert it to stock and got ota update the dp2 since I'm a beta tester and root it again.
Rooted with TWRP on NPF10C
So I'm rooted and have TWRP installed, how can I update to DP2 ?
aakash dabrase said:
So I'm rooted and have TWRP installed, how can I update to DP2 ?
Click to expand...
Click to collapse
Install FlashFire from the play store and select firmware
swa100 said:
Can't flash it in TWRP --> error
edit: I got E3001: the build fingerprint doesn't match. How can I fix this?
Click to expand...
Click to collapse
Noted it in the op
Twrp is based on 6.0.1 afaik just use FlashFire
WelcomeToTheSkye said:
Install FlashFire from the play store and select firmware
Click to expand...
Click to collapse
Here's what I did:
1. Downloaded the OTA (137 MB) on pc.
2. Copied it to phone.
3. Selected Flash OTA in flashfire and selected the zip.
4. Flashfire failed to do it.
Should I use flash firmware option instead of flash OTA?
Also there are further options to select like recovery etc. What about them?
aakash dabrase said:
Here's what I did:
1. Downloaded the OTA (137 MB) on pc.
2. Copied it to phone.
3. Selected Flash OTA in flashfire and selected the zip.
4. Flashfire failed to do it.
Should I use flash firmware option instead of flash OTA?
Also there are further options to select like recovery etc. What about them?
Click to expand...
Click to collapse
Yep select firmware (it says that in op) select what you would like to keep
I just received the OTA update from 7.1.1 DP2 to MNF26F.
Here is the OTA url to download:
https://android.googleapis.com/pack.../2c6f100d0f9ef8ccee10d661b7454adb7161aa0e.zip
You can sideload it into your device and you will be on the official 7.1.1 release.
Just got it too. Only 27 megabytes.
Just download it... Where the downloaded OTA file located in our file system?
deani77 said:
Just download it... Where the downloaded OTA file located in our file system?
Click to expand...
Click to collapse
/data/data/com.google.android.gms/app_download/
If rooted on dp2 I can just download and install through TWRP, no?
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
thedead69 said:
I installed this and I got a boot loop, so careful. First time ever with an issue and I didn't bring my cable
Click to expand...
Click to collapse
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
RaceFaceXC said:
If rooted on dp2 I can just download and install through TWRP, no?
Click to expand...
Click to collapse
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
RaceFaceXC said:
Any more info? What version were you on before? Rooted? Used TWRP? What version of TWRP?
Click to expand...
Click to collapse
Rooted with SuperSU on DP2. Using flashfire
I got this OTA this afternoon. Stock DP2 on Verizon.
rchtk said:
No. ota only installs on stock images.
http://forum.xda-developers.com/showthread.php?p=62924118
Points 12/ and 13/
Click to expand...
Click to collapse
Thank.
I think I knew this at some point. Wasn't sure so that's why I asked.
thedead69 said:
Rooted with SuperSU on DP2. Using flashfire
Click to expand...
Click to collapse
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
onesolo said:
Can you or someone help me??
Yesterday I received the notification. Download the file from here, as I am rooted, twrp and custome kernel.
I tried to flash this via flashfire, but after phone reboots, nothing happens... am I doing something wrong??
I open flashfire, choose Flash ZIP or OTA, choose the file, on the options I don't change anything (it only has Restore boot and recovery images ticked) and then on the main screen I press Flash. Then phone reboots and nothing happens, it enters again on android.
Someone??
Click to expand...
Click to collapse
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Link ota for NEXUS 5X PLEASE
Link ota for NEXUS 5X PLEASE
hanibioud said:
Link ota for NEXUS 5X PLEASE
Click to expand...
Click to collapse
Wrong forum. This is for the Nexus 6P.
RaceFaceXC said:
Can you enter bootloader or recovery with power/vol dn? If so, try sideloading a stock image? Or, if you can get into recovery restore with a nandroid backup?
Click to expand...
Click to collapse
I didn't even try, cause I can enter on twrp fine. As I said, I have twrp and root. My sys is obviously modified. I'm not even trying to sideloaded over bootloader cause it wont work. The same thing on TWRP. I think that sideloading on TWRP only works with full OTAs and not with this one, that is an incremental OTA file, unless I'm completely wrong (I wish).
Anyone's got a changelog for those 26 MB of 'system stability and performance' ?
onesolo said:
Can you or someone help me?? Someone??
Click to expand...
Click to collapse
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
v12xke said:
Download the full Google image- not OTA and flash that. If you can still boot the OS, use FF to flash boot, system, vendor. If you cannot boot OS, use ADB Fastboot to flash those partitions. Yes, I used the full image to go from DP2 to Public Release using FF. If more details are needed, check out the FF thread.
Click to expand...
Click to collapse
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
onesolo said:
yep, that is what I'm going to do... I guess not even FF can flash an mere incremental OTA (only full OTAs). bad luck
Click to expand...
Click to collapse
I didn't think flashing a ota over a rooted os, let alone a highly modified os/kernel/etc was a good idea with any utility.
Hi, i have new honor 9, as i open the phone , it is upgrade to B183 Version.
i need to automatic call recorder and i have found a zip.file to flash whit twrp. So i want install twrp and root...
The first time i download TWRP 3.1.1-1 and Supersu 2,82, i install all whit my zip file per automatic call recorder...
all is ok, twrp, i have root and call recorder working,,, but...
I lose navigation buttons and Camera Flash.
for navigation buttons isnt a problem... i can use only Home button ( i had a Meizu phone before but...
I need camera flash ! it have to work.
so....
for have again all working , i used the Rebrand Guide of HWOTA, whit B120 all work again.
cannot have more OTA upgraded but i think because i just had download them whit my imei.... ok i will wait new update for verifyng it.
I can use Finder Firmware Huawey for have manual upgrade.
Now i'm again in b183.
how can I do now for have a valid twrp or valid method for root phone? Because i read that same people have them..... but i think have reroll to b120 almost 50 time whithout always same results....
oh oh, i see now that i have wrong section. moderator can you move?
SOLVED!
After many time i can have all working now:
Starting to B183 firmware whit button and flash not working:
Step 1) Rollback on B120, downgrading by flashing with hwota scripts, this post . option are 2 (directory upgrade) and 1 (same brand). with this you will have working buttons
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Step 3) Unlock the bootloader.
Step 4) Install the TWRP-3.1.1.1_120_130_170.img from this thread.
Step 5) Install Supersu SR5
WARNING: you have to be carefull when go in TWRP recovery: do not modify system data at twrp's boot, then rebooted choosing not to install twrp at twrp's exit prompt. ( dont'know if it is important... but so it work
so you will have a b183 firmware whit all working: root, button and flash.
please, reply if this work for you.
Add more infos about FF .
In updater system , no update available after roolback to B120.
Need to use Firmware Finder Huawei on Playstore.
1-Choose the desired full version
2-Check Firmware access for be sure not make mistakes.
3-Get an update throught DNs , register update and change Dns .
4- Come back to updater and check update .
angelobiz said:
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Click to expand...
Click to collapse
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Zuzler said:
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Click to expand...
Click to collapse
While on stock B120 use the android application Huawei Firmware Finder to upgrade:
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/
But you could try to test to use HWOTA to upgrade from b120 to b183 and then report here?
I already tried upgrading to B182/183 with HWOTA. I was on B120 and did a B182 and B183 upgrade. I was left with no capacitive keys and no flash. Camera was working however.
Just right now downloading B183 on top of a new locked B120 with the Firmware Finder, will report back.
However, it's very inconvenient to update the system this way if you have an unlocked bootloader and are rooted. I mean, downgrade to B120, twice within HWOTA, upgrade within the system and then AGAIN re-unlock the bootloader which results in a factory reset - come on...
Does it also work with Magisk or only with SuperSu?
SuperSu already is nice, but the additional benefits like would be nice to have, especially passing SafetyNet.
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
zxz0O0 said:
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
Click to expand...
Click to collapse
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Zuzler said:
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Click to expand...
Click to collapse
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Good. This might be a breakthrough. Could you please share a step by step guide what to do? Thanks.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
angelobiz said:
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
Click to expand...
Click to collapse
It would be a good thing.
Edit : As we are all trying to make your device 100% functional with root.
Here is a link for a Su Emui , not testes yet. Work on the mosty Huawei devices
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
http://www.mediafire.com/file/pn2pv1rqih1ug81/SuperSU-v2.82-EMUI5-SELPermissive[1].zip
https://androidfilehost.com/?fid=673956719939815322
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you provide details?
I wonder if we can pull the touch_key firmware from a working B120 firmware and flash over a later version?
angelobiz said:
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Now i'm ok .
I used the good twrp and sideloaded Supersu.sr3 .
All buttons and flashlight work nice
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
So did your twrp fix touch_key once broken?
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you please share your modified TWRP recovery, so we can test on our phones?
This issue is driving me crazy.
Thanks :good:
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
t-shock said:
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
Click to expand...
Click to collapse
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Pretoriano80 said:
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Click to expand...
Click to collapse
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
t-shock said:
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
Click to expand...
Click to collapse
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
ante0 said:
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
Click to expand...
Click to collapse
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
t-shock said:
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
Click to expand...
Click to collapse
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
ante0 said:
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
Click to expand...
Click to collapse
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
t-shock said:
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
Click to expand...
Click to collapse
It shouldn't. And it works again with root. Apparently something broke in SEPolicy, but mankindtw fixed it in his pre-rooted ramdisk. Though, we can install Magisk "normally" now (as a package through recovery) so it shouldn't be a problem anyway SuperSU should install in a similar way too, if one would take the time to make it. I prefer Magisk though
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Edit: I can flash system, I did flash kernel, I can flash recovery too, but when I try to flash anything else, it gives me that error
Edit2: can someone tell me which files do I need to extract via huawei update extractor to flash? I know that system.img is one of them
konopla4 said:
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Click to expand...
Click to collapse
Check if you're still FRP unlock in Fastboot.
ante0 said:
Check if you're still FRP unlock in Fastboot.
Click to expand...
Click to collapse
Both bootloader and from are unlocked
konopla4 said:
Both bootloader and from are unlocked
Click to expand...
Click to collapse
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
You could use HWOTA for Mate 10 Lite if you can get into stock recovery, as it will flash the full update.app rather than the limited partitions fastboot can flash.
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
Click to expand...
Click to collapse
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
konopla4 said:
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
Click to expand...
Click to collapse
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
Click to expand...
Click to collapse
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
konopla4 said:
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
Click to expand...
Click to collapse
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
ante0 said:
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
Click to expand...
Click to collapse
Waaaait it, I can update from TWRP?
Or is it a specialized one?
konopla4 said:
Waaaait it, I can update from TWRP?
Or is it a specialized one?
Click to expand...
Click to collapse
It's a script, but it needs a TWRP that's compatible. The one by Catuva21 is (or so I've heard).