Related
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've noticed that many in this forum for the Honor 7x / Mate SE want to try a few ROMS, and then eventually go back to stock - Some just want to go back to stock. I had my own issues and thankfully there were others to help along the way. This method does not use fastboot to flash partitions, it uses TWRP, so the assumption is you have a working TWRP. Also I am not responsible for any bricks, I am just explaining what I did to get back to stock (And based on all the issues people are having, I'm staying there)
If you've tried a Treble ROM or others, the route I took to get back to stock was as follows:
1.) Download your firmware from Firmware finder or the Pro-TeamMT website:
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-l34&firmware_page=0
In this example, mine is the Mate SE..
You should have downloaded 3 files. The important one we want right now is the Update.zip - Extract this file. You should see UPDATE.APP within this folder.
2.) Download the Huawei extractor software by worstenbrood:
https://forum.xda-developers.com/showthread.php?t=2433454
3.) Use this software to extract the files from the Update.App - You may need to disable the Checksum checks under "Settings". When you select the UPDATE.APP file, you should get a list of the files that are compiled or compressed into the app. The main 4 files you want are Ramdisk, Vendor, System, and if you'd like the Stock recovery (Recovey_Ramdisk). Copy these files to your SD card.
4.) Assuming you still have the functioning TWRP, reboot into TWRP and wipe everything but the SD card.
5.) Flash the images to the appropriate partition, Ramdisk = Ramdisk, Vendor = Vendor Image, and System = System Image - Ensure you're flashing the image partitions. Ramdisk is necessary if you've ever rooted or used Magisk.
At this point you should be able to reboot and get back into stock...But you'll notice Themes do not work properly..That's because you've wiped / formatted data at some point in TWRP, and now the Data/hw_int has been wiped. You can fix this by flashing the update on top of itself by the instructions in this thread (Thanks to mrmazak):
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
See the "Flash update while on Oreo"...This has worked twice now to get me back my themes after wiping /data.
I counted on my TWRP backup to get me back to stock after trying a Treble ROM, and I ended up bricked. So hopefully this helps someone!
PS, if anyone has more to add this this, the more help the better.
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
crayonicle said:
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
Click to expand...
Click to collapse
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Corrections, please add to original post
smokinjoe2122 said:
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Click to expand...
Click to collapse
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
System image can fail too...that's why I said to flash everything in TWRP...Plus, flashing the update on-top of itself will not only give you theming back, but stock recovery.
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Adithya Krishnakumar said:
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Click to expand...
Click to collapse
Yes, I tried it. It works flawlessly.
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
crayonicle said:
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
Click to expand...
Click to collapse
What part are you stuck on?
Essentially mrmazak created a flashable file that will take the 3 firmware files you download and flash them on top of your current firmware. This is helpful for doing an update or just reloading the firmware completely (Which is what you're trying to do)...
I'd follow the exact instructions that he's put out on that thread, but the 10,000 ft overview:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
1.) Download files from link for your device
2.) Create a correctly named folder on your SD card, along with those files properly named in that folder (Ensure these files are named properly also.)
3.) Ensure you have the stock recovery on the SD card also.
4.) Copy the "xxx_Update.zip" he created onto your SD
5.) Flash the "xxx_Update.zip"...It will will flash the stock recovery, then boot into update mode and update with the 3 files you downloaded and put into that folder. This will basically "reflash" the firmware and give you back themes.
I would go step by step on his action list and follow them to a "T". I've verified it works perfectly. He also has a "Basic-Instructions" write up in the zip also.
My device build number was BND-L21C185, I bricked my device once but I managed to get it back. Since then I have strange build number which is system 8.0.0.046(063f). Does this method fix it?
This info helped me bring my phone back to life,thank you sir for the step by step instructions.
Found a way to get back to stock without all this hassle lol
So I thought this was the only way to get back to stock... turns out there is a much easier way
This method also enables themes, I checked myself.
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
Is it possible to flash all of the partitions from fastboot?
I have the BND-L34 and I am unsure as to what happened.
I have been running the RROS surdu_petru posted for about 3 weeks now and it was running fine.
2 days ago I grab my phone and it was booted into error mode. Now when I try to boot into twrp I get an error code for my recovery. When I try to boot into the system it throws a different error code for boot image.
I have a twrp backup stored on an sd card, and all 3 OTA's I saved back during the June update. I have the Pro-TeamMT app on my pc and have found/extracted every file for the brick method only get the same errors, 1 right after the other.
I am no noob, (although I am not a Senior Member with a giant banner either ) but I have been rooting android devices going on 8 years now, and have never completely bricked any of them.
My last 2 phones were Oneplus 1 and Oneplus 3, so I am familiar with flashing all the partitions using fastboot. But with those phones there were about 9 different individual flashes that needed to be done in a particular order.
Any help or advice would be greatly appreciated.
Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.
HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!
@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!
Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.
Hi everyone!
I need to edit an APK in stock ROM (system.img) of my device. I have unpacked system.img and repacked with some programs on Windows. But When I unpack and repack the system.img file and change it with original system.img file (even though I didn't change any APK or anything), I can flash it through fastboot or port 9008 successfully. BUT When I try to start my phone, It stuck on MI Logo screen.
So There is no problem with flash any rom. But I want to unpack rom and edit an APK then repack it. This is my issue. How can I do it? I think there is a problem on unpack/repack step. I'll be glad if anyone can help me about it.
Thanks in advance!
p.s. I can't flash a recovery rom because of I can't run phone.
I'm currently using Realme X RMX1901(CN)(4-64gb), i switch to different roms pretty frequently . just now, i tried OOS GSI(A only), but its stuck in a bootloop(just showing realme logo and going on-off.
this is how i flashed using latest TWPR:
1. formated all my data(including everything in the advanced option)
2. used my pc to extracted .img file from .7z file,
3. copied that .img file to phone storage and
4. flashed .img file , only the system image.
the flash completed without any error, then i rebboted it(also tried by formatting only internal data)
my question is where did i go wrong? did i miss any part or did it wrong?
please let me know, thanks in advance.