Can anyone share boot.img and recovery.img of b388?
I need to unroot the phone and need the image files to do that.
You should state the version of honor 8. Also, you should have them already if you're on 388. Unrooting is a single click whether it's with magisk or SuperSU. Not sure where you got your information but you do NOT need those files to unroot.
Related
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root
Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.
Hello!
I want to make my phone completely stock again. (Or as close as possible if completely stock isn't possible)
I unlocked, installed TWRP, and then rooted my phone yesterday (thanks to shashank1320's guide which made it very simple), but quickly found out that safetynet will prevent me from downloading and playing certain games on the Google Play Store.
After poking around online, it seems that even switching over to Magisk instead of using SuperSU will leave intermittent gaps in time where the app will be inaccessible due to the new workaround eventually being blocked.
So I want to go back. But like a derp, I forgot to create a backup beforehand.
So far I've unrooted through the SuperSU app itself, and flashed the BOOT.img and RECOVERY.img from Dazed No More's links in the Honor 6x Repository here.
After this is where I'm not sure what to do.
I think I need to find a factory system image to flash (and the vendor.img)?
I've seen a few threads saying that putting the UPDATE.APP in a dload folder into the phone and have the phone run the update worked (This did not work for me, although I'm not sure I have the right files; I downloaded it through a tech guide site here). I extracted the system.img and vendor.img from the update.app off that website using the Huawei Update Extractor, but I am afraid of flashing them in case they are the incorrect ones. But what if they are correct? Would I be able to recover if they are not?
Also, should I download and use unSU?
I know there is this guide on the front page right now. I've downloaded the Huawei Firmware Finder, but I... don't know how to use it. I narrow it down to the model number and that is where I get stuck. How... do I use it?
Some other basic questions I have in addition to this are:
Would I just have to flash the system.img and vendor.img through adb and then it will be stock again?
Would there still be leftover SuperSU files in my phone? I want to remove every trace of it. Would flashing be enough?
Am I even on the right track? And if not, where should I go from here?
Is the term "ROM" here firmware? Are the two terms interchangeable?
Ultimately, I would want to flash stock and then lock the bootloader again.
Thank you very much in advance. I appreciate it.
Edit: Wow I forgot to put any information, sorry about that.
Honor 6x
Model Number: BLN-L24
Build Number: BLN-L24C567B360
EMUI version: 5.0
Android version: 7.0
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
shashank1320 said:
If you have unrooted, foashed stock boot and stock recovery rhen you are stock completely. For safer side, you can just dload the current firmware whch will lock your bootloader also and remove those device unlocked and cant be trusted message on boot.
Click to expand...
Click to collapse
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Faifie said:
Thank you! Currently it's still tripping safetynet, but that may just be due to the phone still being unlocked.
Would it be fine to just lock the bootloader through adb now?
And are all traces of SuperSU gone like this?
Click to expand...
Click to collapse
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
shashank1320 said:
Nope. Locking the bootloader will just do it and reset but wont change the boot.img which root modified.
You need to unroot, flash stock recovery and stock boot.img to get rid of it.
Click to expand...
Click to collapse
Okay, since those have been flashed with stock, that means I'm set to re-lock the phone! Will get around to it sometime tomorrow c:
Thank you so, so much ^^
How do I manually update through OTA my honor 8 after rooting?I dont want to flash full rom.Where does the downloaded update will be saved?
Ragesh77 said:
How do I manually update through OTA my honor 8 after rooting?I dont want to flash full rom.Where does the downloaded update will be saved?
Click to expand...
Click to collapse
You can't really "manually" update your Honor 8 the way you mean it. You can't just flash the downloaded content from TWRP.
Anyway I'll guide you on how to update without full ROM reflash. You WILL need recovery image and you can try without stock boot image. Installing update with rooted device(modified boot image) is reported to not work for some people but for me it does work with no issues. If you make a full backup you also won't run into any problems.
So to update your device find stock recovery img of your current ROM version. I recommend extracting it from UPDATE.zip which you can download with Huawei extractor. You flash the stock recovery from fastboot. I will assume you know how to get to fastboot since you already are rooted and have unlocked bootloader which is OK and won't give us problems.
After flashing stock recovery proceed with OTA normally as if you did not modify your device in any way.
BUT YOU have to select full system image download. Not partial small 200-300 mb update. You have to select full 2GB system image.
If you run into an error and it refuses to update you will need to find stock boot image from the previously mentioned UPDATE.zip. So flash both stock recovery and stock boot, then proceed with normal OTA update same as said above with full system image.
By doing the above you will not lose your DATA partition. You will not lose your apps. You WILL lose root access. All you need to do to regain root access it is to first reflash TWRP via fastboot and then reflash Magisk/SuperSU/(your root alternative). Before reflashing TWRP I recommend making stock recovery backup so you won't need to extract it again from UPDATE.zip for the future OTA updates.
If you have any questions or I was not clear on something please ask for further guidance. Do not forget to make a full backup before the process. You can not hard brick your device with anything I wrote here but you can lose your data if you have no backup.
Can't I just flash the 300mb file rhrough twrp?
Ragesh77 said:
Can't I just flash the 300mb file rhrough twrp?
Click to expand...
Click to collapse
Of course You can't. I wrote that at the beginning of the post. If that was possible nobody would ever have issues with updating their rooted device lol.
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
https://forum.xda-developers.com/showpost.php?p=79548858&postcount=6
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
ozfive said:
I am looking to learn how to extract a boot image to patch. The last source for patched boot images has not updated since 9.5.10. I would like to be less dependent and be able to do it on my own.
Can someone put together a quick tutorial on how to extract a boot.img so I can run it though Magisk and create a patched one?
Click to expand...
Click to collapse
1)Download payload dumper.
2)Extract payload file from rom zip.
3)Put payload file in payload_input folder.
4)Run exe file.
5)After process complete check payload_output folder. All extracted there.
Download payload dumper from here :- https://forum.xda-developers.com/attachment.php?attachmentid=4760222&d=1558078935
Patched boot images are irrelevant and only necessary for devices without a working TWRP recovery. If you want to root, either boot TWRP once or boot and install TWRP (recommended) and then install the magisk zip from there.
larsdennert said:
I have the current rooted AA boot image in the guide in my signature. I extract them directly from the phone.
Click to expand...
Click to collapse
How do you extract the boot.img from the phone? I have the tmo version and would like to say on the stock room with root.
Sent from my GM1915 using Tapatalk
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
larsdennert said:
You need root to extract a partition, but if you have root then you have no need for it except to share it so someone else can get root.
In other words are you rooted already? If not, you'll need to use the other instructions or get a rooted or non rooted image from someone with a T-Mobile phone.
I'm going to guess you could fastboot boot boot.img to any rooted boot image for the one plus 7 pro, have root and then install magisk.
Click to expand...
Click to collapse
Not rooted yet, but everything I have read so far is that you need a patched boot.img to root, or you can create one from the boot.img in an oos package with magisk manager. The problem is, there isn't a tmo oos package out there yet, so it looks like rooting the tmo software isn't possible at the moment. Is this correct?
Sent from my SM-T550 using Tapatalk
Is your bootloader unlocked? That would be step one. Read up on the thread for that.
Not yet, but will be....trying to get my research done before I go for it... don't want to mess it up, been a few years since I rooted a phone.
Sent from my GM1915 using Tapatalk
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
SilverZero said:
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
Click to expand...
Click to collapse
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
stompysan said:
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
Click to expand...
Click to collapse
Works great. Thanks!
BostonDan said:
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
Click to expand...
Click to collapse
Post below yours worked for me but I appreciate the advice on backups and what to watch for. I haven't installed TWRP yet, just booted it and installed.
SilverZero said:
Works great. Thanks!
Click to expand...
Click to collapse
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
stompysan said:
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
Click to expand...
Click to collapse
Following up on this just in case you know anything new. My IN2017 just updated to A11 without any action on my part, and I lost root. Is there a TWRP or patched boot img that you know of for us on TMo now?
There is no working twrp for us on Android 11. I also haven't seen a patched boot image of 11.0.1.3.IN55CB around yet. I have that firmware extracted on my laptop so I could grab the boot image and patch it for you, but I won't be able to do that until later tomorrow. If no one else has it out or if you don't find it before I can get to it, I'll post it up.
Edit: Here's the patched boot image: Magisk Patched Boot IMG TMO 11.0.1.3