Need boot img from 10.0.27 - OnePlus 7T Pro 5G McLaren Questions & Answers

Updated to 10.0.27 then used 10.0.25 magisk boot img to root and lost wifi, I believe it's cause of the using the .25 boot so if anyone backed up their .27 boot img and can post it I would appreciate it.

Nevermind delete the thread I just msm back, there were other issues as well.

nexendz said:
Nevermind delete the thread I just msm back, there were other issues as well.
Click to expand...
Click to collapse
THREAD CLOSED on behalf of OP, and moved from Guides forum to Q&A.

Related

no force encrypt on nexus 6p running mhc19i

Hi, can some one give me a guide on the nexus 6 p running mhc19i for no force encrypt, with either a system root that will allow me to remove apps, or a systemless root that I have to go through recovery, and is there a recovery for this version at this time other then the stock one
gigawatt said:
Hi, can some one give me a guide on the nexus 6 p running mhc19i for no force encrypt, with either a system root that will allow me to remove apps, or a systemless root that I have to go through recovery, and is there a recovery for this version at this time other then the stock one
Click to expand...
Click to collapse
To decrypt you need to format the userdata partition:
Code:
fastboot format userdata
This will obviously wipe your storage so back it up to your PC first. You will also need to flash a custom kernel that doesn't force encryption first otherwise the stock kernel will just encrypt again when you boot after formatting. You need to use TWRP recovery to flash SuperSU to get root. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
yeh, is there a custom kernel for mhc19i
gigawatt said:
yeh, is there a custom kernel for mhc19i
Click to expand...
Click to collapse
Of course, there are many. Have you actually looked?
yes, I have looked, but most of them have an aroma installer, I am totally blind so I need one I can flash through fastboot as there is no talkback in aroma or recovery mode. Even the stock no force encrypt would be helpful thanks.
gigawatt said:
yes, I have looked, but most of them have an aroma installer, I am totally blind so I need one I can flash through fastboot as there is no talkback in aroma or recovery mode. Even the stock no force encrypt would be helpful thanks.
Click to expand...
Click to collapse
You can flash any of them via fastboot. Extract the boot.img from the zip and flash it:
Code:
fastboot flash boot boot.img
You'll just end up with the default settings. Why don't you just flash TWRP? Then you can install it the intended way.
I can flash twrp through fastboot, but I am totally blind and use a screen reader, so I would have to have some one around to use the twrp interface, since there is no speech there, so I need a kernel or modified no force encrypt boot.img I can flash through fastboot
gigawatt said:
I can flash twrp through fastboot, but I am totally blind and use a screen reader, so I would have to have some one around to use the twrp interface, since there is no speech there, so I need a kernel or modified no force encrypt boot.img I can flash through fastboot
Click to expand...
Click to collapse
Ahh, I see, that is definitely a difficult situation. So basically as I said, I believe any of them can be flashed via fastboot, but it isn't without its own work. You'd need to download the kernel zip, extract it, place the boot.img into your working directory (your fastboot folder), and use the "fastboot flash boot boot.img" command to flash it to the device. This will give you a kernel that doesn't force encryption, and you could then go on to use an app like Kernel Auditor to tweak the settings once you've booted into Android. How possible is this for you?
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
gigawatt said:
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
Click to expand...
Click to collapse
Apologies for the late reply, been a bit busy with my family. It looks like Franco is one of the kernels that doesn't have the boot.img directly inside the zip. There's probably a way to extract it but it's beyond my expertise. I'm in the process of extracting the boot.img from some other popular kernels for you now though, I'll update here once I have some uploaded. It might take a while because my upload speed is woefully slow.
gigawatt said:
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
Click to expand...
Click to collapse
Actually, it turns out none of the kernels have an easily accessible boot.img inside the zip. Things have changed since I last unpacked a kernel. I'll see what I can find out for you.
Here my friend use this thread. From @Tigerstown
https://tapatalk.com/shareLink?url=...share_tid=3306684&share_fid=3793&share_type=t
[UPDATED 3-10-16][Stock modified boot.img for regular root/Android N decrypted boot
It contains a stock modified boot image allowing system root and no force encryption. He updates thread for every build. Flash right from fastboot. If you need anything else feel free to PM me.
Sent from my Nexus 6P using Tapatalk
toknitup420 said:
Here my friend use this thread. From @Tigerstown
https://tapatalk.com/shareLink?url=...share_tid=3306684&share_fid=3793&share_type=t
[UPDATED 3-10-16][Stock modified boot.img for regular root/Android N decrypted boot
It contains a stock modified boot image allowing system root and no force encryption. He updates thread for every build. Flash right from fastboot. If you need anything else feel free to PM me.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Heisenberg said:
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Click to expand...
Click to collapse
Yes that's the correct link. I shared it from Tapatalk instead of web browser. Thank you for grabbing the correct one.
Sent from my Nexus 6P using Tapatalk
Heisenberg said:
Apologies for the late reply, been a bit busy with my family. It looks like Franco is one of the kernels that doesn't have the boot.img directly inside the zip. There's probably a way to extract it but it's beyond my expertise. I'm in the process of extracting the boot.img from some other popular kernels for you now though, I'll update here once I have some uploaded. It might take a while because my upload speed is woefully slow.
Click to expand...
Click to collapse
If they are using anykernel zip there is no boot.img.
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
Heisenberg said:
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Click to expand...
Click to collapse
I posted that thread in General. I should have posted in dev threads but less traffic the better for me answering the same questions over and over ??

TWRP

Hello,
I've flashwed twrp-3.0.1-0 onto my phone successfully, however, when I go into recovery, there is only folders and no files. How do I fix this?
U will need to delete data as in the twrp thread if u have just rooted and installed this.
Edge of insanity
auskingdom said:
Hello,
I've flashwed twrp-3.0.1-0 onto my phone successfully, however, when I go into recovery, there is only folders and no files. How do I fix this?
Click to expand...
Click to collapse
All the questions and answers are posted in the twrp thread.
Sent from my Blackberry Torch 3000

When Android Keep Booting Into TWRP Recovery

Thousands of android users having this problem, when you install custom ROM and then you try to reset your phone; it keep rebooting into TWRP recovery (not system), even after you flash your ROM again.
So here's the solution: https://www.youtube.com/watch?v=vSWC5MAB5cE
Mod edit:
Thread closed. Link is dead.
link is dead...
I'm already rooted and I tried to install twrp and it keeps doing the same. Even after flashjng boot.img to both slots before hand.and rerooting after installing twrp
Sent from my Pixel using XDA-Developers Legacy app
Somebody please repost the answer.
I dont know if it has changed but whenever this happened to me I just fastboot flashed the boot.img and then it booted up fine
oneders65 said:
Somebody please repost the answer.
Click to expand...
Click to collapse
oneders65 said:
Somebody please repost the answer.
Click to expand...
Click to collapse
The answer for me when I had this happen in September was to simply flash the Magisk zip file from the TWRP recovery after one of the many loops that it had done
(and I had tried everything else - reflashed TWRP from both fastboot and recovery many times, re-flashed the Google Pixel full image via the flash-all.bat file a few times, etc).

10.3.0 bootloader unlock + root

I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
stovo06 said:
I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
Click to expand...
Click to collapse
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Click to expand...
Click to collapse
I thought this was for 9.x.x
stovo06 said:
I thought this was for 9.x.x
Click to expand...
Click to collapse
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Nothing has changed but the versions of TWRP and Magisk
Click to expand...
Click to collapse
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
clsA said:
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
flyoffacliff said:
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
Click to expand...
Click to collapse
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Striatum_bdr said:
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Click to expand...
Click to collapse
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
stovo06 said:
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Striatum_bdr said:
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Click to expand...
Click to collapse
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash boot TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
clsA said:
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash recovery TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
Click to expand...
Click to collapse
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Striatum_bdr said:
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Click to expand...
Click to collapse
That's what I've read as well. And there are many solutions but I find them scattered all over the forms.
And I don't trust YouTube videos lol
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
stovo06 said:
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
Click to expand...
Click to collapse
I don't think there is the need of another thread. Many are already talking about rooting and flashing twrp.
What makes people confuse is that perhaps some of them think things have changed... And that methods are bound to an Android version.
Nothing has changed.
Fastbooting TWRP and then flashing it, is the way we do it since years. Patching boot img as an alternative is also a classical way to root.
People are blinded by tiny differences and don't see that the frame hasn't changed. You unlock the bootloader, then boot to twrp and then either you flash only Magisk either you flash twrp then Magisk. Very simple. Always with latest versions.
It's because xda threads are not moderated except for offenses, etc that many users post their 'own' recipe every 2 pages without anybody cleaning and organizing things to make them understandable. And the fact that threads are not well maintained in time, with titles and first posts instructions that can seem obsolete.... Especially on old phones like our when devs are quitting the scene without designating a maintainer
clsA said:
Nice instructions, But I'm curious why you think he needs them ?
Click to expand...
Click to collapse
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
aaron74 said:
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
Click to expand...
Click to collapse
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Striatum_bdr said:
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Click to expand...
Click to collapse
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
stovo06 said:
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
Click to expand...
Click to collapse
Wait for render zenith
stovo06 said:
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
Click to expand...
Click to collapse
Yeah, this is an awesome device. Only device I've been happy with since my old Samsung note 4. Biggest thing I miss, it'd be nice to have an SD card slot!
Patching a boot image is what Magisk does when you install it. But you just would manually do this.
Last question, I've been reading too install Magisk 19.4.
Does that still apply?
Apologies for all the questions (and great appreciation for the help), but the information here is scattered and at times contradicting when all I need now is a simple magisk manager and mod ?.
Thank you all for your help.

patched the wrong boot.img file while rooting, now stuck

i patched the wrong image in magisk and flashed it, phone was stuck on fastboot mode. i made a mistake again due to lack of knowledge or roms and flashed another boot.img stock again, now im stuck on the screen where it says “the bootloader is unlocked and its integrity cannot be guranteed” my computer wont register the device on adb so im stuck.
Flash the stock boot image (boot.img) in fastboot for whatever version of OOS you are running.
starcms said:
Flash the stock boot image (boot.img) in fastboot for whatever version of OOS you are running.
Click to expand...
Click to collapse
i cant seem to find one for 11.0.1.4
Raahim.v said:
i cant seem to find one for 11.0.1.4
Click to expand...
Click to collapse
It's in the thread about fixing reserve.img
..
boot_11.0.1.4.img | by StarCMS for OnePlus 7T Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
starcms said:
It's in the thread about fixing reserve.img
Click to expand...
Click to collapse
could you link it?
Raahim.v said:
could you link it?
Click to expand...
Click to collapse
I already did in the post immediately above this post by you...you can't search and can't even read all the posts in your own thread?
and the thread on fixing reserve is at the very top and you shouldn't be doing anything, including unlocking the bootloader, without first reading the threads about how to root properly (and how to unroot properly b4 trying to take the next OTA so it doesn't fail), how to backup your persist.img (which is probably the most important step by far), and how to restore reserve.img after first unlocking the bootloader so you'll still get future OTA updates (info on all of which are in the top 5 threads or so of the subforums) and you'd have a much easier time and make less mistakes on what is possibly the most fickle device ever made
starcms said:
I already did in the post immediately above this post by you...you can't search and can't even read all the posts in your own thread?
and the thread on fixing reserve is at the very top and you shouldn't be doing anything, including unlocking the bootloader, without first reading the threads about how to root properly (and how to unroot properly b4 trying to take the next OTA so it doesn't fail), how to backup your persist.img (which is probably the most important step by far), and how to restore reserve.img after first unlocking the bootloader so you'll still get future OTA updates (info on all of which are in the top 5 threads or so of the subforums) and you'd have a much easier time and make less mistakes on what is possibly the most fickle device ever made
Click to expand...
Click to collapse
im sorry, i am new to everything. Also, i flashed the boot.img file and my phone is in bootloops
Thanks for the files, it was a partition issue

Categories

Resources