[Q] How to flash 5.1 image? - Nexus 6 Q&A, Help & Troubleshooting

Current: Unlocked, Rooted, TWRP, Custom Rom 5.0.1, Custom Kernel, Encrypted
Goal: Unlocked, Rooted, TWRP, Factory 5.1.0, Custom Kernel, Decrypted
How do I go from my current state to my goal?
Would the following steps be correct and shortest?
1) Flash factory image - Flash All
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Disable encryption - Flash kernel, disable + wipe
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
3) Install Root - SuperSU
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
4) Install TWRP
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
5) Install Custom Kernel
Is step 2 in the correct order? Do I perform the install and disable to eliminate all traces of decryption?
Step 5, do I flash the kernel via TWRP or use the kernel's app from the Google Store?

Bump

I was Stock 5.01. except rooted and decrypted.
Copied SuperSU.zip to my Nexus 6.
had all the .img files extracted and in the same folder as my fastboot.exe from the Android SDK (make sure you are at the latest).
Boot to bootloader.
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
Using a decrypted flagged 5.1 boot.img
fastboot flash boot de-cryptedboot.img
fastboot flash system system.img
fastboot flash cache cache.img
I reflashed twrp as well...couldn't remember if I had left it on or had flash to stock recovery after rooting.
fastboot flash recovery twrp-2.8.5.0.img
When that finished flashing I used the volume keys to move to "boot recovery" and pressed power.
Team Win Recovery came up and I installed SuperSU.zip
Rebooted...done. 5.1, unencrypted, rooted and kept all my data.

Where did you get the decrypted boot img from?

From this thread.
http://forum.xda-developers.com/showthread.php?t=2946715

does the ota zip file contain all the .img files.............
it looks like it does, but there not all named in the normal fashion..........
can this be clarified.......
what files are what?

They are all there. Bootloader and the radio are in the main zip file and the rest are in the zip that is inside the main zip file. Extract both zip files.

tcrews said:
They are all there. Bootloader and the radio are in the main zip file and the rest are in the zip that is inside the main zip file. Extract both zip files.
Click to expand...
Click to collapse
after seeing this post I realize your talking about the factory image (tgz) and not the OTA zip.........
I have now downloaded the image but I am sure this post was referring to the 5.1 ota zip.......

Related

need to downgrade from CM6 to Stock 2.2

I have sold my phone and I am currently using CM6 RC3
The buyer want me to install the stock 2.2
can someone please provide me with the Download to stock 2.2, and the instructions, Just flash over cm6?
Thanks
You could download the FRF91 system image (link in my signature) and flash it using fastboot...
1. reboot into bootloader
2. extract the downloaded zip
3. fastboot flash userdata userdata.img
4. fastboot flash system system.img
5. fastboot flash boot boot.img
6. fastboot flash recovery recovery.img
Your radio and hboot can remain unchanged (they are stock anyways)
thanks alot of your help:
I am not fimilar with using fastboot
is there a way to use recovery and flash from zip file, that is how I have been trying out different roms
I think ROM Manager has the stock rom available. That would be the easiest way.

Flashing 5.0.1

I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
SoCoCapricorn said:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
Click to expand...
Click to collapse
Apparently the new update OTA or zip will update blocks instead of files so from my understanding, even the slightest change from stock will cause this ZIP to fail when flashing. I'm rooted, decrypted, and changed mixer_paths.xml and as expected the flash failed in TWRP and adb sideload so I'm backing up via Titanium and flashing the 5.0.1 stock. I'll decrypt/root/restore after the flash.
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
mzimand said:
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
Click to expand...
Click to collapse
Rooting causes a change to the system partition, so no, you can't sideload the OTA anymore. (not since Lollipop)
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Worked like a CHAMP!!
:highfive:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Are you using nexus toolkit by wug?
Sent from my Nexus 6
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, just used the steps I listed.
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, he used fastboot. Be wary of toolkits. They can do damage that a novice wont be able to fix.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Jeezus! perfect!
Thats similar to what I did.
Only thing to do if you are already decrypted is to download this boot file, rename it to boot.img and flash it instead of the one included in the google zip package.
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
dunjamon said:
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
Click to expand...
Click to collapse
yeah - since 5.0, the flash-all.bat isn't working for a lot of users.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
What about the cache.img? do we not flash the cache?
mzimand said:
What about the cache.img? do we not flash the cache?
Click to expand...
Click to collapse
From what I understand, if you flash cache.img, you will go back to stock and lose all of your settings.
Awesome man, worked perfect, you sir rock!
Great!!!!
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
It works like a champ! THX man :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Excellent, works perfectly as described. Thanks
The only thing that I'd add, to avoid any confusion, is that the factory image can be downloaded from:
https://developers.google.com/android/nexus/images
Thanks again, stevetrooper :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Having an issue while flashing system.img file. I flashed radio, and flashed system.img then flashed cf-auto-root. On first start up I was having issues with my radio. LTE was not connecting to T Mobile. So I Nandroid back to stock. Then of course I noticed this didnt change my radio back to stock. Starting everything over, I reflashed radio, reboot bootloader, Flash system.img, reboot bootloader, then fash autoroot. Restart device. Radio was flashed and I had root, but stuck on 5.0 Tried to reflash system.img and I am getting error. "access denied" when flashing. I have read this is an issue with mounting the drive, I have even tried to do this in fast boot but I am coming up with nothing. Any help on this will be greatly appreciated.
theblizzard2010 said:
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Click to expand...
Click to collapse

[GUIDE] Update stock rooted/modified rom to last 6.0 Marshmallow w/o losing your data

Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip
working fine for me, all correct, thanks
Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?
Thank you, works like a charm!
Same here, cant flash system
There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry
i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.
Tnx mate. Helped a lot
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx
chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.
Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.
@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?
foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.
In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..
You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.

While upgrading from 6.01-7.0 crashed at 83% Now Stuck at Google logo image w/Unlock

Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?
touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery
Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!

Stock recovery

Hi, can anyone provide me with stock recovery for Vtr-L09c440b112.
I'm trying to update my p10 to the latest version but since I have twrp installed during the reboot process twrp loads and gives me error 9 and prevents my device from updating. So I'm hoping I can place stock recovery and the update process goes well. Then I can re root.
Up
I have the same problem with my p10 trying to install an ota and my device is rooted the only way is to remove TWRP and to relock bootloader I think but i'm struggling with it since 48 hours now ...
- Download the installed or desired firmware as a full-ota packed from hwmt.ru / Firmware Finder.
- Unzip the downloaded too file and use the tool "Huawei Update Extractor" (Google it, it's a post here on XDA) to open the unzipped update.app file.
Extract the recovery.img and recovery2.img.
- Boot your phone into fastboot and enter following commands:
"fastboot flash recovery /PATH/TO/recovery.img"
"fastboot flash recovery2 /PATH/TO/recovery2.img".
- Now the stock recovery is installed.
You have to do the same with boot.img, because you can't install updates with the official method when you unlocked your bootloader.
Hi, I've got as far "fastboot flash recovery /PATH/TO/recovery.img". I've tried typing into CMD;
fastboot flash recovery C:/Users/dange/Desktop/filefoldewr/Huawei Official Firmware/Extract app file recovery.img
but i get an error: 'fastboot' is not reconised an internal or external command, operable program or batch file.
Where did I go wrong please,
ThankS Brian

Categories

Resources