Related
I just receveid an OTA update, but the installation stuck because the system is rooted.
I found the update.zip file on my Handy, but it contains some directory (Meta-inf, patch and system) and a big file update.app that I believe contais all the update file.
Is it possible to extract the file from update.app and then create an update that can I launche from TWRP? And if so how could I do it?
Thanks
You can't.
flash back a stock recovery.
After ulocking bootloader and root the OTA didn't work with original recovery that's why I wanto to create an update that works with TWRP
did you try?
ItalianWolf said:
did you try?
Click to expand...
Click to collapse
Yes I reinstalled the original recovery that you can find in t he root package and I completely unroot the phone using the unroot command in SuperSu.
Then I launch the update but after reboot it stuck at 11%, so I create the dload folder in my handy memory and copied there the content of update.zip and then forced the update. In this case, after reboot, it load until 99% that it reboot, but the installed version is still the 170 and not the 188.
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
ItalianWolf said:
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
Click to expand...
Click to collapse
What does here mean?
Which thread?
Thanks
Harlock1978 said:
What does here mean?
Which thread?
Thanks
Click to expand...
Click to collapse
Sorry, forgot link: http://forum.xda-developers.com/p8l...-lite-android-6-0-marshmallow-t3305550/page40
You need the Huawei Update Extractor Tool, and do the following:
Load the UPDATE.APP file inside the HUET
Extract boot.img, system.img, and cust.img, from UPDATE.APP inside the HUET
Flash the respective files via Fastboot
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
AmINoS007 said:
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
Click to expand...
Click to collapse
If you have to, flash the B052 recovery... you can always flash the Marshmallow recovery if it doesn't let you update.
I only flashed boot.img, cust.img, and system.img, when I upgraded; didn't flash Marshmallow's recovery at all.
Don't think you can even get OTA updates on the Marshmallow beta anyway (even via a normal bootloader-locked device).
Sorry for my late answer but I was travelling only with a Mac and I couldn't use Huaweu Update extractor.
This are the file that you can find in UpdateApp 188:
00.SHA256rsa.img
01.crc.img
02.curver.img
03.verlist.img
04.efi.img
05.fastboot1.img
06.boot.img
07.recovery.img
08.recovery2.img
11.cache.img
13.dtimage.img
14.dsp.img
15.fastboot.img
16.hifi.img
17.mcuimage.img
18.modemimage.img
19.modemnvm1.img
20.teeos.img
21.trustfirmware.img
And also the following directory:
META-INF
patch
system
Which file should I install, I didn't find a system.img and there are two different recovery
Thanks
You should not install any OTA with TWRP...
Flash back the stock recovery, update, then flash the twrp again, it's way easier and more secure, than doing a flashable zip from an OTA update without knowing what to do with the file within.
The OTA updates usually doesn't contain the SYSTEM.IMG file you are looking for, it contains individual files and scripts to patch up the current system partition to work with the new update.
From the two recoveries you should use the RECOVERY.IMG (the one without the 2 in it).
But again, I do recommend to flash the original recovery(not the one in the update), do the update, and put twrp back.
Where can I find the original recovery from ALE-L21C432B170, so that I can flash the original recovery again?
TIA
I found the original recovery and flashed it then I did a complete unroot and tried again to do the OTA update but it stopped at 11%.
Is there a different way to update?
THIS GUIDE IS FOR ALL MIUI BASED ROMS WHETHER IT IS OFFICIAL, UNOFFICIAL(Xiaomi.eu,sphinx) OR MODDED(smiui).This is for the people who unlocked bootloader through the unofficial way.
http://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-waiting-permission-t3349886
People with officially unlocked bootloader can also try just to be on safer side...nothing to lose right?
Many people after unlocking their bootloaders flashed miui recovery/fastboot roms through twrp/miflash and got their device hardbricked with locked bootloader, which is a pretty messed up situtation, (follow this guide if you are a victim
http://en.miui.com/thread-245347-1-1.html
) and the only way to unbrick from that state is test-point method which voids warranty of course. Others who flashed fastboot roms with default recovery using miflash ends up with locked bootloader too, so I'm gonna share steps by which you can flash full recovery/fastboot roms and not get harbricked/locked bootloader:-
1) First let me tell you why it happens, every recovery rom zip file has a firmware-update folder containing a emmc_appsboot.mbn file, that file relocks bootloader everytime a full rom recovery rom is flashed, fastboot roms also have the same emmc_appsboot.mbn file.
2) To flash recovery roms through twrp, delete the emmc_appsboot.mbn file from the firmware_update folder inside the rom zip file, and then flash rom. Winrar works best, open the recovery zip file with winrar and open firmware-update folder and right click on the emmc_appsboot file and select delete, wait for it to complete(takes some time). For fastboot roms extract the download fastboot file and delete the file emmc_appsboot.mbn file from the images folder. Also in order to keep your desired recovery like TWRP intact, delete the recovery.img file. Edit :- Tested it on my Redmi note 3 pro, deleting only the emmc_appsboot.mbn file works, no need of deleting entire firmware-update folder.
3) To update roms, first download OTA through updater app (or download it from pc) and then open the OTA zip file (located inside downloaded roms folder) and delete emmc_appsboot.mbn file inside the firmware-update folder and then flash through twrp. OTA's can relock bootloader and hardbrick(as it happened in Mi4c).Can't flash OTA due to build fingerprint error? Follow this guide
http://en.miui.com/thread-262947-1-1.html
4) After flashing rom through twrp, flash modified boot.img specific for that miui version, or else you will get bootloop. Guide to make modified boot.img http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
Original Boot.img is located inside recovery rom zip.For those who dont want to do it manually, link for downloading modified boot.img
http://miuidroid.com/rn3/boot_images/
(credits to magdag)
It is required to flash modified boot.img even if you updated through OTA.
P.S:- I've tested all this using my Redmi note 3 pro, should work on other devices too. Any suggestions for improving the guide is welcome.
If I helped pressing thanks won't cost you a thing.:good:
Can you update or post the modded boot image for latest SD 7.2.3.0 Stable global rom?
I have 7.1.8. global rom with officially unloced botloader and TWRP. If I want to install the update I just download the OTA from the updater app in my phone, then remove the emmc_appsboot.mbn and flash. Do I need to flash a modified boot image after that?
anshude1 said:
Can you update or post the modded boot image for latest SD 7.2.3.0 Stable global rom?
Click to expand...
Click to collapse
okay give me sometime, I'll upload on gdrive
Rajdip said:
okay give me sometime, I'll upload on gdrive
Click to expand...
Click to collapse
here you go
https://drive.google.com/open?id=0B5bSNUUrjm6JSk1lZWx5VlRqbkU
Can you please make a modified boot.img for China Stable?
sanuj.bhatia said:
Can you please make a modified boot.img for China Stable?
Click to expand...
Click to collapse
will do
Edit:- https://drive.google.com/open?id=0B5bSNUUrjm6JQTZscE5YZUhuNlE this for china stable 7.2.2.0
Rajdip, you wrote to first flashing rom through twrp and after that flash modified boot.img. How can I flash file boot.img through twrp?
Maby can I copy midified boot.img into rom zip file and after flashing rom?
KrzysiekGP said:
Rajdip, you wrote to first flashing rom through twrp and after that flash modified boot.img. How can I flash file boot.img through twrp?
Maby can I copy midified boot.img into rom zip file and after flashing rom?
Click to expand...
Click to collapse
img file can flashed via TWRP, when you select install option on TWRP , look for "install image" option on right bottom part of screen, now select the modified img and then select boot and then flash.
Rajdip said:
will do
Edit:- https://drive.google.com/open?id=0B5bSNUUrjm6JQTZscE5YZUhuNlE this for china stable 7.2.2.0
Click to expand...
Click to collapse
Can you make one for the latest 7.2.3?
sanuj.bhatia said:
Can you make one for the latest 7.2.3?
Click to expand...
Click to collapse
Look at post # 5... The link is already there for 7.2.3
i've succes flash official rom v stable cn 7.2.3.0...but i 've problem cannot turn on wifi....any idea how to fix it?
Rajdip said:
THIS GUIDE IS FOR ALL MIUI BASED ROMS WHETHER IT IS OFFICIAL, UNOFFICIAL(Xiaomi.eu,sphinx) OR MODDED(smiui).This is for the people who unlocked bootloader through the unofficial way.
http://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-waiting-permission-t3349886
People with officially unlocked bootloader can also try just to be on safer side...nothing to lose right?
Many people after unlocking their bootloaders flashed miui recovery/fastboot roms through twrp/miflash and got their device hardbricked with locked bootloader, which is a pretty messed up situtation, (follow this guide if you are a victim
http://en.miui.com/thread-245347-1-1.html
) and the only way to unbrick from that state is test-point method which voids warranty of course. Others who flashed fastboot roms with default recovery using miflash ends up with locked bootloader too, so I'm gonna share steps by which you can flash full recovery/fastboot roms and not get harbricked/locked bootloader:-
1) First let me tell you why it happens, every recovery rom zip file has a firmware-update folder containing a emmc_appsboot.mbn file, that file relocks bootloader everytime a full rom recovery rom is flashed, fastboot roms also have the same emmc_appsboot.mbn file.
2) To flash recovery roms through twrp, delete the emmc_appsboot.mbn file from the firmware_update folder inside the rom zip file, and then flash rom. Winrar works best, open the recovery zip file with winrar and open firmware-update folder and right click on the emmc_appsboot file and select delete, wait for it to complete(takes some time). For fastboot roms extract the download fastboot file and delete the file emmc_appsboot.mbn file from the images folder. Also in order to keep your desired recovery like TWRP intact, delete the recovery.img file. Edit :- Tested it on my Redmi note 3 pro, deleting only the emmc_appsboot.mbn file works, no need of deleting entire firmware-update folder.
3) To update roms, first download OTA through updater app (or download it from pc) and then open the OTA zip file (located inside downloaded roms folder) and delete emmc_appsboot.mbn file inside the firmware-update folder and then flash through twrp. OTA's can relock bootloader and hardbrick(as it happened in Mi4c).Can't flash OTA due to build fingerprint error? Follow this guide
http://en.miui.com/thread-262947-1-1.html
4) After flashing rom through twrp, flash modified boot.img specific for that miui version, or else you will get bootloop. Guide to make modified boot.img http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
Original Boot.img is located inside recovery rom zip.For those who dont want to do it manually, link for downloading modified boot.img
http://miuidroid.com/rn3/boot_images/
(credits to magdag)
It is required to flash modified boot.img even if you updated through OTA.
P.S:- I've tested all this using my Redmi note 3 pro, should work on other devices too. Any suggestions for improving the guide is welcome.
If I helped pressing thanks won't cost you a thing.:good:
Click to expand...
Click to collapse
Currently I'm on 6.4.14 (CHINA LATEST DEV ROM) ,Can i use 6.4.14 Fastboot ROM in place of 7.1.8 Global stable rom to unlock using unofficial method . After unlocking bootloader , i want to directly upgrade to latest global stable rom 7.2.3.0 with TWRP and root. I have recovry ROM (OTA) of 7.2.3.0 .
What would be the appropriate steps to do that without any problems ?
Please tell me step by step as i will follow exactly that steps and don't want to risk even a bit by using my half knowledge . I know i have to read the guide but i get lost in between , would appreciate if you could tell me exact steps .
akhil17kr said:
Currently I'm on 6.4.14 (CHINA LATEST DEV ROM) ,Can i use 6.4.14 Fastboot ROM in place of 7.1.8 Global stable rom to unlock using unofficial method . After unlocking bootloader , i want to directly upgrade to latest global stable rom 7.2.3.0 with TWRP and root. I have recovry ROM (OTA) of 7.2.3.0 .
What would be the appropriate steps to do that without any problems ?
Please tell me step by step as i will follow exactly that steps and don't want to risk even a bit by using my half knowledge . I know i have to read the guide but i get lost in between , would appreciate if you could tell me exact steps .
Click to expand...
Click to collapse
Yeah you can use china dev rom for unlocking bootloader, and after that to upgrade to global 7.2.3.0 you need a full recovery rom, OTA wont work, also WHENEVER YOU DOWNLOAD A OTA/ROM OPEN IT WITH WINRAR, OPEN THE FIRMWARE-UPDATE FOLDER AND DELETE THE emmc_appsboot.mbn file or else you will hardbrick your device and the only wasy from recovering from it is by opening your phone
Mayoz said:
i've succes flash official rom v stable cn 7.2.3.0...but i 've problem cannot turn on wifi....any idea how to fix it?
Click to expand...
Click to collapse
Did you flash the modified boot.img of 7.2.3.0?
Rajdip said:
Yeah you can use china dev rom for unlocking bootloader, and after that to upgrade to global 7.2.3.0 you need a full recovery rom, OTA wont work, also WHENEVER YOU DOWNLOAD A OTA/ROM OPEN IT WITH WINRAR, OPEN THE FIRMWARE-UPDATE FOLDER AND DELETE THE emmc_appsboot.mbn file or else you will hardbrick your device and the only wasy from recovering from it is by opening your phone
Click to expand...
Click to collapse
Hi , can you make sure again that China dev ROM will work in place of stable 7.1.8.0 without any problem ?
Also 7.2.3.0 which I've is full ROM i think it's "miui_HMNote3ProGlobal_V7.2.3.0.LHOMIDA_74136dde89_5.1.zip" and it is 0.99 GB in size.
So after unlocking bootloader , i can normally boot into current china dev ROM and directly upgrade to 7.2.3.0 through updater app with just emmc_appsboot.mbn deleted from it ?
I guess there is no need to delete boot.img as i still haven't flashed the twrp and root yet and will flash both of files after upgrading to 7.2.3.0 .
Plz tell if my steps are correct or not ?
akhil17kr said:
Hi , can you make sure again that China dev ROM will work in place of stable 7.1.8.0 without any problem ?
Also 7.2.3.0 which I've is full ROM i think it's "miui_HMNote3ProGlobal_V7.2.3.0.LHOMIDA_74136dde89_5.1.zip" and it is 0.99 GB in size.
So after unlocking bootloader , i can normally boot into current china dev ROM and directly upgrade to 7.2.3.0 through updater app with just emmc_appsboot.mbn deleted from it ?
I guess there is no need to delete boot.img as i still haven't flashed the twrp and root yet and will flash both of files after upgrading to 7.2.3.0 .
Plz tell if my steps are correct or not ?
Click to expand...
Click to collapse
What about you use the miui global 7.2.3.0 directly for unlocking bootloader the unofficial way? after that you can flash TWRP if you want, and you cant update using updater app, you have to update directly from TWRP.
anshude1 said:
Look at post # 5... The link is already there for 7.2.3
Click to expand...
Click to collapse
I guess that boot.img is for Global Stable 7.2.3!?
Rajdip said:
What about you use the miui global 7.2.3.0 directly for unlocking bootloader the unofficial way? after that you can flash TWRP if you want, and you cant update using updater app, you have to update directly from TWRP.
Click to expand...
Click to collapse
Well to do that i have to download again the GB of flashboot rom of miui global 7.2.3.0 and i really have painful slow internet so thought of first unlocking bootloader and then later upgrade through Recovery zip file.
What do you suggest for best way as i just don't want to f**k up my device..
So if updater app can't flash the Official MIUI roms even with unlocked bootloader then what's the point of recovery ROM of different types such as global stable,beta china stable beta if you want to switch ROM's ?
Why in redmi note 3 there are so hurdles to switch /downgrade/upgrade ROM after unlocking bootloader ? I have done all flashing stuff on some other android phones too but there was never a risk for relock of bootloader and overwrite of custom recovery while flashing ROMS ..so why all this hurdles in Redmi Note 3 as it doesn't make sense to unlock bootloader after each and every upgrade /downgrade of ROM's or it is only due to the fact that it has been unlocked through unofficial way ?
akhil17kr said:
Well to do that i have to download again the GB of flashboot rom of miui global 7.2.3.0 and i really have painful slow internet so thought of first unlocking bootloader and then later upgrade through Recovery zip file.
What do you suggest for best way as i just don't want to f**k up my device..
So if updater app can't flash the Official MIUI roms even with unlocked bootloader then what's the point of recovery ROM of different types such as global stable,beta china stable beta if you want to switch ROM's ?
Why in redmi note 3 there are so hurdles to switch /downgrade/upgrade ROM after unlocking bootloader ? I have done all flashing stuff on some other android phones too but there was never a risk for relock of bootloader and overwrite of custom recovery while flashing ROMS ..so why all this hurdles in Redmi Note 3 as it doesn't make sense to unlock bootloader after each and every upgrade /downgrade of ROM's or it is only due to the fact that it has been unlocked through unofficial way ?
Click to expand...
Click to collapse
This is what xiaomi made of themselves, every move is f*****g hassle right now. I understand the problem of slow internet. You have unlocked bootloader right? why dont you just leave MIUI and install the AOSP rom. no more hassle no bricks.
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:
Since those generic system images are image files, can I flash them using Odin instead of custom recovery?
Answering my own question
I have tested it yesterday with Heimdall and it worked!
This was the command line I used:
Code:
$ heimdall flash --pit file.pit --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img
Being boot.img patched by Magisk, recovery.img -> TWRP and system.img a generic System Image of Android Q pure, type AB.
cizordj said:
Answering my own question
I have tested it yesterday with Heimdall and it worked!
This was the command line I used:
Code:
$ heimdall flash --pit file.pit --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img
Being boot.img patched by Magisk, recovery.img -> TWRP and system.img a generic System Image of Android Q pure, type AB.
Click to expand...
Click to collapse
so you flashed recovery.img
Can't you now boot into recovery and flash GSIs from there?
physwizz said:
so you flashed recovery.img
Can't you now boot into recovery and flash GSIs from there?
Click to expand...
Click to collapse
No, I installed the first release of TWRP taken from here
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
and it simply doesn't flash system images, only small boot images.
Now I'm going to the latest version to see if it has been fixed.
cizordj said:
No, I installed the first release of TWRP taken from here
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
and it simply doesn't flash system images, only small boot images.
Now I'm going to the latest version to see if it has been fixed.
Click to expand...
Click to collapse
What is your firmware date.
cizordj said:
No, I installed the first release of TWRP taken from here
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
and it simply doesn't flash system images, only small boot images.
Now I'm going to the latest version to see if it has been fixed.
Click to expand...
Click to collapse
Dude I just want to say lol.
physwizz said:
What is your firmware date.
Click to expand...
Click to collapse
If I am not mistaken I was running november 2019 released firmware, I know... I read somewhere that this firmware would not work well with TWRP - yet - but I installed it anyway.
I flashed the android 10 GSI with Heimdall, I don't know how but it's working. I'm using it right now haha
cizordj said:
If I am not mistaken I was running november 2019 released firmware, I know... I read somewhere that this firmware would not work well with TWRP - yet - but I installed it anyway.
I flashed the android 10 GSI with Heimdall, I don't know how but it's working. I'm using it right now haha
Click to expand...
Click to collapse
The TWRP you are using is correct for your firmware.
I've not read of any issues with it.
Most problems work out to be some other cause.
Hi, Can anyone tell me where to get the pit.img?
Moreover, Is it alright to use boot.img extracted from Stock ROM?
Also would like to know about pit file. Trying to install google GSI at a Galaxy A7 2018 (1750G/DS). Without any luck so far...
Please show me how you did it via windows?
DISCLAIMER
I have only tested this on my OnePlus8T Indian model - KB2001
Huge thanks to @topjohnwu for his magic.
YOU NEED TO UNLOCK YOUR BOOTLOADER!
In case you brick your device, use this unbrick guide
If you get into a boot-loop by flashing problematic magisk modules, consider using the patched recoveries from my post HERE to remove the modules.
Manual ROOT procedureSkip to step #6 and then #10 if you do not want to use the payload dumper tool and want to directly patch and flash the stock images for your variant and Build version!
If you haven't updated OxygenOS yet, download it via the system updater. It will be stored in /sdcard/.Ota folder in your internal storage ( /sdcard/.Ota/OnePlus8TOxygen_15.I.16_OTA_0160_all_2010150110_84be0c.zip )
The size should be >2GB. If it is not, it's probably an incremental OTA, not a full one. This guide will NOT work on incremental OTA Zips.
DO NOT Reboot or else you will lose the file
Copy the ZIP file over to your PC
Download the Payload Dumper
Alt dumper for windows only:
https://androidfilehost.com/?fid=818070582850510260
1.Put payload.bin to "payload_input" folder
2.Run payload_dumper.exe
3.Successfully extracted img files are in "payload_output" folder
Extract the zip in the folder where you downloaded the payload dumper.
Follow the instructions in the readme of payload dumper, and extract the OTA images:
Code:
python payload_dumper.py payload.bin
You will get a boot.img file in the output folder.
Proceed with installing the OxygenOS update and reboot the phone.
Download and install the latest magisk canary release to your phone : https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
Copy over the boot.img file created by payload_dumper to your internal storage
Open Magisk Manager > Select Install > "Select and patch a file"
Browse and select the boot.img file.
Magisk will create a patched boot.img file in /sdcard/Downloads/magisk_patched.img . Copy this file over to your PC.
Reboot to fastboot mode
Code:
adb reboot bootloader
Either flash the patched magisk_patched.img in the active slot or temporarily boot into it if you are skeptical.
I recommend to BOOT first and then perform a direct install via magisk as it is more reliable to patch the active slot.
To flash:
Code:
fastboot flash boot magisk_patched.img
To Temporarily boot into a rooted system (RECOMMENDED!!):
Code:
fastboot boot magisk_patched.img
If you used the fastboot BOOT method, next you'll have to open magisk manager again, and this time, perform a "Direct Install".
This will install magisk on the active boot slot and the next reboot will give you root.
How to update OTA and KEEP ROOT
It is advised to disable all magisk modules to be safe!
epr said:
- Go to System-Update
- Tap OK when the message that you are rooted appears
- Tap "Download and install"
- Wait until you are prompted to reboot - DO NOT REBOOT NOW!
- Open Magisk Manager, select install -> Install to inactive slot and start installation
- When Magisk has finished to install, reboot and you stay rooted with newest OTA.
Click to expand...
Click to collapse
For the curious / impatient, Here are the OTAs / boot images for the different 8T Versions
All patched images are removed to ensure users perform the steps 6 - 11 of the guide and also not trust images patched by others.
To find your model and build to download the right file:
Bash:
adb shell getprop ro.product.model
KB2001
adb shell getprop ro.build.version.ota
OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
adb shell getprop ro.build.display.id
KB2001_15_201015
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK boot.img
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK boot.img (md5sum 3202f74ea45b906e9f0ea7cfcd81a014 )
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK boot.img
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK boot.img
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK boot.img
11.0.5.6 - OnePlus8TOxygen_15.I.20_OTA_0200_all_2011132215_feb8ca02ab.zip
KB05DA_11.0.5.6_BOOT_STOCK.img
11.0.6.8 - 11.0.10.10
KB05DA - India Folder on AFH
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK boot.img (md5sum af4bb15254d38ab17167583eba23d5bd )
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK boot.img
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
Thanks @GraveDigger176 for the OTA zip
STOCK boot.img
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK boot.img
11.0.5.6 - OnePlus8TOxygen_15.E.21_OTA_0210_all_2011132216_d2e1e993.zip
KB05BA_11.0.5.6_BOOT_STOCK.img
11.0.6.9 - 11.0.11.11
KB05BA - EU Folder on AFH
KB2005 / KB05AA - International Variant
Credit @northmendo @SAKO4444GODZ and @g96818
UPDATE:
For this variant please refer to this guide first! The OTA updates on this variant are partial and hence the rooting method isn't straightforward.
https://forum.xda-developers.com/showpost.php?p=83791723&postcount=95
Stock KB2005_15_201015 boot image SHA-1 D59C74767F74F4D7876BDCA930DEF23CCAA3FD2E
Patched KB2005_15_201015 boot image SHA-1 C1126E8057EF9FB25D80645B850374BBDDE983C5
OOS 11.0.3.4.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83893183&postcount=151
OOS 11.0.4.5.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83940123&postcount=210
OOS 11.0.5.6.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=84003695&postcount=258
OOS 11.0.6.8 - 11.0.11.11 : https://androidfilehost.com/user/?w=settings-dev-files&flid=329462
KB2007 / KB05CB - T-Mobile Variant
¯\_(ツ)_/¯
It's also a good practice to backup a few important partitions once you're rooted.
I used ADB shell, but you can use any terminal emulator from the play store (Termux)
adb shell
[email protected]:/ $ su
[email protected]:/ #
Now run:
Bash:
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemst2 of=/sdcard/modemst2.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/modemdump of=/sdcard/modemdump.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/persist of=/sdcard/persist.img
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/persist_bkp of=/sdcard/persist_bkp.img
Other Misc Stuff for my reference!
If after flashing a custom kernel, you see Sim cards not working:
FullOfHell said:
Be sure NOT to have a magisk patched image on both boot slots. That causes this behavior
Click to expand...
Click to collapse
Recovering lost app data after a failed boot:
Download and flash one of my adb-patched recoveries from my post here
Reboot to recovery, enter the password, open adb shell
Create a tar bundle of the app via tar -czvf MiXBackup.tgz data/data/com.mixplorer/silver and adb pull it to your system
*Or* the entire /data partition via tar --exclude /data/media/0 -czvf /data/media/0/data.tgz data/ (You CANNOT restore all of /data like this due to encryption stuff! but you can extract one app at a time and test)
Reinstall the app , reboot to recovery, adb push, and extract via tar xf MiXBackup.tar
Repo of Oxygen OS Builds
OOS Unbrick tool
ADB Enabled OOS Recovery
Re-locking the bootloader on the OnePlus 8t with a self-signed build of LOS
Widevine discussions
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2000_Magisk_15.H.16_OTA_0160_all_2010150101_4101.img
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK boot.img (md5sum 3202f74ea45b906e9f0ea7cfcd81a014 )
MAGISK patched boot.img which you can flash/boot directly - KB2001_magisk_patched_11.0.1.2.KB05DA.img
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2001_magisk_patched_11.0.2.3.img
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.3.4_BOOT_MAGISK.img
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.4.5_BOOT_MAGISK.img
11.0.5.6 - OnePlus8TOxygen_15.I.20_OTA_0200_all_2011132215_feb8ca02ab.zip
KB05DA_11.0.5.6_BOOT_STOCK.img
MAGISK patched boot.img which you can flash/boot directly - KB05DA_11.0.5.6_BOOT_MAGISK.img
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK boot.img (md5sum af4bb15254d38ab17167583eba23d5bd )
MAGISK patched boot.img which you can flash/boot directly - boot_magisk_patched_11.0.1.2_EU.img
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly - KB2003_magisk_patched_11.0.2.3.img
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
Thanks @GraveDigger176 for the OTA zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly (thanks @rage302) - magisk_patched_11.0.3.4_KB05BA.img
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK boot.img
MAGISK patched boot.img which you can flash/boot directly (thank @rage302) - magisk_patched_11.0.4.5_KB05BA.img
11.0.5.6 - OnePlus8TOxygen_15.E.21_OTA_0210_all_2011132216_d2e1e993.zip
KB05BA_11.0.5.6_BOOT_STOCK.img
MAGISK patched boot.img which you can flash/boot directly - magisk_patched_11.0.5.6_KB05BA.img
KB2005 / KB05AA - International Variant
Credit @northmendo @SAKO4444GODZ and @g96818
UPDATE:
For this variant please refer to this guide first! The OTA updates on this variant are partial and hence the rooting method isn't straightforward.
https://forum.xda-developers.com/showpost.php?p=83791723&postcount=95
Stock KB2005_15_201015 boot image SHA-1 D59C74767F74F4D7876BDCA930DEF23CCAA3FD2E
Patched KB2005_15_201015 boot image SHA-1 C1126E8057EF9FB25D80645B850374BBDDE983C5
OOS 11.0.3.4.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83893183&postcount=151
OOS 11.0.4.5.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=83940123&postcount=210
OOS 11.0.5.6.KB05AA : Refer to https://forum.xda-developers.com/showpost.php?p=84003695&postcount=258
I wonder if this same process would work for the KB2005 model? Unfortunately I was too quick to pull the trigger on the system update ??*
guess I'll be waiting a little longer
JWhetstone02 said:
I wonder if this same process would work for the KB2005 model? Unfortunately I was too quick to pull the trigger on the system update ??*
guess I'll be waiting a little longer
Click to expand...
Click to collapse
Yep, the procedure will stay the same. I would recommend waiting for someone to upload the OOS OTA zip or Oneplus to provide a direct download link.
However, if you are on the same build version, you try to patch the KB2001 boot.img and just use the fastboot boot method instead of flashing the patched image.
If it boots, you're in luck. If it doesn't, force reboot back into stock OOS.
Would be nice if someone can do this with the european version too. Maybe I can do it tomorrow but only if the dumper tool works on windows. Any idea on that?
5nickers said:
Would be nice if someone can do this with the european version too. Maybe I can do it tomorrow but only if the dumper tool works on windows. Any idea on that?
Click to expand...
Click to collapse
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
DroidFreak32 said:
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
Click to expand...
Click to collapse
Cool, guess I'll be doing that tomorrow after I get my phone. If it works I'm gonna upload the modified boot image here for everyone else
5nickers said:
Cool, guess I'll be doing that tomorrow after I get my phone. If it works I'm gonna upload the modified boot image here for everyone else
Click to expand...
Click to collapse
Also share the OTA zip too, please
If anyone can provide the OTA or patched img for the KB2005 that would've great, I was too quick to update [emoji2363]
Oh well, I guess I'll need to wait a little longer
Sent from my KB2005 using Tapatalk
DroidFreak32 said:
Yes it should work. All you need is to have python and the dependencies installed. It's listed in the readme of the dumper.
You can also use this one I found from the OnePlus NORD thread
https://androidfilehost.com/?fid=818070582850510260
Click to expand...
Click to collapse
After rooting and making the safetynet pass, does the widevine remains L1 like OP8 and OP8Pro? Or it becomes L3 like older OP devices?
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
epr said:
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
Click to expand...
Click to collapse
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
What model is this for? ... Or would it matter?
Yeah please clearly state which version all these OTAs are from.
5nickers said:
Yeah please clearly state which version all these OTAs are from.
Click to expand...
Click to collapse
Just wanted to give Wykillin a little help...
Payload.properties from his OTA says: ota_target_version=OnePlus8TOxygen_15.O.16_GLO_0160_2010150057
Hope this makes it a little bit clearer...
Wykillin said:
I captured the OTA yesterday. But I'm having a hard time getting the payload extracted.
Here is the link to the OTA:
https://r5---sn-vgqs7ney.gvt1.com/p.../c552fbf9fb85a74c246c1265a2f10b2382015e82.zip
If I understand correctly, we need to use python payload_dumber.py --diff payload.bin
But we don't have the original boot.img?
Click to expand...
Click to collapse
Yes, you'll need to have the original boot.img as this is just an incremental OTA, not a full one.
I will add a note in the OP as well to not use incremental OTA files.
epr said:
Here is the boot.img extracted from your OTA:
https://drive.google.com/file/d/1jxf6EBSU6-8TuIUV_vN5ABiy-bUA38L1/view?usp=sharing
Click to expand...
Click to collapse
I wouldn't use this image. It cannot be just 4.4 MB in size. I believe it is a partial extract as the OTA zip is just incremental, not a full ~2GB OTA
DroidFreak32 said:
Yes, you'll need to have the original boot.img as this is just an incremental OTA, not a full one.
I will add a note in the OP as well to not use incremental OTA files.
I wouldn't use this image. It cannot be just 4.4 MB in size. I believe it is a partial extract as the OTA zip is just incremental, not a full ~2GB OTA
Click to expand...
Click to collapse
Hi. Could you please answer my earlier question? Thank you
theincognito said:
Hi. Could you please answer my earlier question? Thank you
Click to expand...
Click to collapse
It's l3 unfortunately.
I didn't know op8 could keep it at l1! I would've bought that otherwise!
DroidFreak32 said:
It's l3 unfortunately.
I didn't know op8 could keep it at l1! I would've bought that otherwise!
Click to expand...
Click to collapse
Yeah. Both OP8 and OP8 Pro can retain L1
DroidFreak32 said:
PS: For the curious / impatient, I have uploaded the OTA ZIP here (md5sum d1a944205b91898a84b082c57ebac5a8 ):
https://drive.google.com/file/d/18kTOttFEfQN04JHt_7bkoHN3MWa4ZKo4/view
Click to expand...
Click to collapse
I am about to receive my China version of OnePlus 8T. Since the Global ROM is not yet released by OnePlus, if I flash this full OTA will it work? I want to replace the stock HydrogenOS with OxygenOS.
zellleonhart said:
I am about to receive my China version of OnePlus 8T. Since the Global ROM is not yet released by OnePlus, if I flash this full OTA will it work? I want to replace the stock HydrogenOS with OxygenOS.
Click to expand...
Click to collapse
It will. Though I suggest that you flash the EU variant over the Indian variant (cleanest OOS variant).
---------- Post added at 09:07 PM ---------- Previous post was at 08:49 PM ----------
@DroidFreak32
Magisk patched boot image for OOS 11.0.1.2 EU variant (from the full OTA zip - OnePlus8TOxygen_15.E.17_OTA_0170_all_2010150108_77edc51b51680.zip)
https://androidfilehost.com/?fid=10763459528675567936