Related
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
ZeroSkylineX said:
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
Click to expand...
Click to collapse
If I am on a custom ROM and want to update I usually download the latest firmware zip from google and extract the vendor.img and Flash it thru twrp after updating the custom ROM.
ZeroSkylineX said:
Hi guys, with Google releasing updates so frequently, I was wondering how do you guys keep up with all the new builds? From my understanding, you have to flash the new factory image (through twrp if possible?) so that you get the updated bootloader, radio etc in order to flash the most recent custom roms with the most up to date stock builds.
Is there an easier way rather than constantly wiping everything with each new build flash? I know with One Plus, you can just flash a firmware img file so that you don't have to download and flash such a large file. Does the Pixel have anything similiar?
Click to expand...
Click to collapse
Super easy. I'm assuming your bootloader is unlocked and your rooted or else you wouldn't be asking. Let's assume you are running the stock OS, you have TWRP recovery installed, you're rooted with Magisk, and maybe you also have a custom kernel installed. It's the first of the month and Google releases a new security patch. You cannot just take the OTA, nor can you just sideload the smaller OTA due to the custom recovery/root/other customizations. This is what you do, and this is what I do every month:
-Download the newly released FULL factory image from Google's site (NOT the smaller OTA package, the FULL image)
-Unzip the file, open it up, and inside there are multiple files and some zips. One file is a flash-all.bat (for Windows users) along with a flash-all.sh (for Linux/Mac users). Choose the file based on the OS you are using, open it up in a text editor and delete the -w part of the final command string. Be sure to save the file after doing this. This will eliminate the data wipe or essentially dirty flash the entire factory image without wiping your data.
-Reboot into Fastboot mode.
-Run the executable based on your OS. I use Linux, so I simply open a terminal within the files location and run the command "sudo ./flash-all.sh". For Windows you need to move the file to your platform tools folder then execute the flash-all.sh from within that folder as an administrator (double click it and authorize it). On Linux you need not move anything because Linux is ****ing awesome (assuming you have Android-Tools and Android-Udev installed).
-After you flash the entire image and the phone reboots, you simply reboot back into fastboot mode, fastboot boot TWRP, and re-root by flashing Magisk. Or you can fully install TWRP by fastboot booting TWRP, flashing TWRP, then flashing Magisk. If you're running a custom kernel do the same thing, but always flash Magisk last so it repacks the boot image properly.
-Boot back into the OS, and clear data on the Google Playstore. This will reset your Safetynet which was just set back to false after the new update and allow Magisk to continue to do it's thing and keep your device as being Safetynet certified.
-Done. It takes 10 min. and is very easy to do, but yes you do need to download the full 1.7gb FULL factory image. There are ways to do it with the smaller OTA file, but I'm not going to bother because it's useless and it's open to more problems, plus it takes longer and adds several more steps.
-If you are running a custom rom, the steps are a bit different, and in this case you can simply manually flash the desired partitions and eliminate the system image part of the flash. This still requires downloading the full factory image and manually updating the individual partitions that you want update (aka, bootloader, modem, tz, dtbo, etc). You do not run the flash-all script, rather you manually fastboot each partition you want updated. I run stock, so I'll leave these details out for someone else to chime in on. Essentially you are just going to manually flash the desired partitions to be current, but be prepared for breakage if the custom rom is not configured for the new partitions - like a new radio or bootloader.
annoyingduck said:
Super easy. I'm assuming your bootloader is unlocked and your rooted or else you wouldn't be asking. Let's assume you are running the stock OS, you have TWRP recovery installed, you're rooted with Magisk, and maybe you also have a custom kernel installed. It's the first of the month and Google releases a new security patch. You cannot just take the OTA, nor can you just sideload the smaller OTA due to the custom recovery/root/other customizations. This is what you do, and this is what I do every month:
-Download the newly released FULL factory image from Google's site (NOT the smaller OTA package, the FULL image)
-Unzip the file, open it up, and inside there are multiple files and some zips. One file is a flash-all.bat (for Windows users) along with a flash-all.sh (for Linux/Mac users). Choose the file based on the OS you are using, open it up in a text editor and delete the -w part of the final command string. Be sure to save the file after doing this. This will eliminate the data wipe or essentially dirty flash the entire factory image without wiping your data.
-Reboot into Fastboot mode.
-Run the executable based on your OS. I use Linux, so I simply open a terminal within the files location and run the command "sudo ./flash-all.sh". For Windows you need to move the file to your platform tools folder then execute the flash-all.sh from within that folder as an administrator (double click it and authorize it). On Linux you need not move anything because Linux is ****ing awesome (assuming you have Android-Tools and Android-Udev installed).
-After you flash the entire image and the phone reboots, you simply reboot back into fastboot mode, fastboot boot TWRP, and re-root by flashing Magisk. Or you can fully install TWRP by fastboot booting TWRP, flashing TWRP, then flashing Magisk. If you're running a custom kernel do the same thing, but always flash Magisk last so it repacks the boot image properly.
-Boot back into the OS, and clear data on the Google Playstore. This will reset your Safetynet which was just set back to false after the new update and allow Magisk to continue to do it's thing and keep your device as being Safetynet certified.
-Done. It takes 10 min. and is very easy to do, but yes you do need to download the full 1.7gb FULL factory image. There are ways to do it with the smaller OTA file, but I'm not going to bother because it's useless and it's open to more problems, plus it takes longer and adds several more steps.
-If you are running a custom rom, the steps are a bit different, and in this case you can simply manually flash the desired partitions and eliminate the system image part of the flash. This still requires downloading the full factory image and manually updating the individual partitions that you want update (aka, bootloader, modem, tz, dtbo, etc). You do not run the flash-all script, rather you manually fastboot each partition you want updated. I run stock, so I'll leave these details out for someone else to chime in on. Essentially you are just going to manually flash the desired partitions to be current, but be prepared for breakage if the custom rom is not configured for the new partitions - like a new radio or bootloader.
Click to expand...
Click to collapse
Wow this is such a phenomenal post, thank you very much for taking your time to write this! I never smacked that thank button so hard in my life.
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.
jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working
I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"
Hey Guys
Looking to revert back to stock from RR-O-v6.0.0-20180504-taimen-Official Rom.
I have tried to install image-taimen-opm2.171019.029.zip but it fails.
I am currently trying the sideload install method of taimen-ota-opm2.171019.029-1b792f19.zip from this website https://developers.google.com/android/ota but seems to just hang at "Verifying Update Package", been this way for 30 mins.
Is there other ways to get this done?, I'm just having no luck.
Cheers
confrontation said:
Hey Guys
Looking to revert back to stock from RR-O-v6.0.0-20180504-taimen-Official Rom.
I have tried to install image-taimen-opm2.171019.029.zip but it fails.
I am currently trying the sideload install method of taimen-ota-opm2.171019.029-1b792f19.zip from this website https://developers.google.com/android/ota but seems to just hang at "Verifying Update Package", been this way for 30 mins.
Is there other ways to get this done?, I'm just having no luck.
Cheers
Click to expand...
Click to collapse
Are you trying to clean or dirty fastboot the factory image??
Are your platform-tools up to date?
Did you extract the files from the factory image and place them in your platform-tools folder?
You can't actually flash a factory image zip, you can flash an OTA.zip via twrp if you'd like.
A few more details would be helpful :good:
As Badger said, a little more would help. Also .029 is April's firmware / security patch. .006.c1 is the most current firmware to have
So what I do: I download the firmware of choice. I put it in a folder that I can easily get to, which I named Pixel2XL (so clever)
Then I extract that zip and I'm left with what you can flash. Bootloader,flash-all.bat, blah blah. NOW I use deuces flash tool because I like it. So I will extract the OTHER folder (image-taimen-006.c1. I will then copy the bootloader and radio to the newly extracted folder. You put in dueces flash file, click on it and follow the instructions. Bam, it starts flashing to BOTH slots. This phone is a picky phone, in that regard.
1) Download factory image.
2) Put into a safe folder of your choice.
3) Extract the image.
4) Go into that folder and see the files that you need.
5) Extract the image-taimen folder (again)
6) Copy the bootloader and radio into that folder.
7) Download Dueces tool and put the "deuce-flash-all-v4.4.bat into the same folder.
8) Go into the folder and see several image files. Don't be scared )
9) Put the zip image-taimen into the folder too!!
10) Double click on duece and away you go!
https://developers.google.com/android/images (Taimen c1)
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I hope I helped!
Edit: Missed a step!
Edit 2! Photo of finished folder to flash everything.
So I found my old Huawei p9 and want to put Lineage on it. Andy Yan's site give me the xz of the img but how do I get it to the correct zip for TWRP (already loaded)?
SephRobbertse said:
So I found my old Huawei p9 and want to put Lineage on it. Andy Yan's site give me the xz of the img but how do I get it to the correct zip for TWRP (already loaded)?
Click to expand...
Click to collapse
Extract using 7zip, the .img is inside the archive.
Boot to TWRP, connect via USB, and transfer the .img to your device. Then, go to Install > Install images > select /System > select the LineageOS.img and flash.
Keep in mind that if you want to flash a GApps package, you must do it right after flashing /system. You may have to resize the /system partition if you get an error about not having enough space.
V0latyle said:
Extract using 7zip, the .img is inside the archive.
Click to expand...
Click to collapse
Thanks yea I have that. But cant get it installed (ADB or Fastboot).
SephRobbertse said:
Thanks yea I have that. But cant get it installed (ADB or Fastboot).
Click to expand...
Click to collapse
See my edits to the post above.
I'm not familiar with Huawei devices, but if you're able to flash partitions directly from the bootloader, then you'd need to flash the LIneageOS to system: fastboot flash system lineageos.img. You can make this easier by just typing fastboot flash system, leave a space after "system", then just drag and drop the LineageOS .img into the command window.
V0latyle said:
See my edits to the post above.
I'm not familiar with Huawei devices, but if you're able to flash partitions directly from the bootloader, then you'd need to flash the LIneageOS to system: fastboot flash system lineageos.img. You can make this easier by just typing fastboot flash system, leave a space after "system", then just drag and drop the LineageOS .img into the command window.
Click to expand...
Click to collapse
Many thanks.