Related
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Click to expand...
Click to collapse
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
UPDATE: Confirmed, this method does work to update to DP5 from DP4.
Reserved
I'm going to try this.
Really want root on my sh**t.
But, theoretically, when DP5 is out, you'll have to do everything again, but with the Vendor image from DP5?
asj0422 said:
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
Click to expand...
Click to collapse
By how some people roll around these forums, I'd remove the lines from the copy/paste box-thingy you did... haha.
Edit: fell on my a**. Reminder for me to be more helpful
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Edit: fell from my pedestal, note to self: be more helpful.
asj0422 said:
I've been meaning to write this guide for a little while now, but I've only just gotten around to it. Basically, I had wanted to try the N preview, but TWRP didn't play nice with it, so until now, it has been impossible to run N with encryption, root, and without wiping your data. In the interest of full disclosure, I found the basis for this solution while down a Reddit rabbit hole in a very short post at the end of some thread that I've been unable to find again, so I can't take full credit. Many thanks to this random Redditor.
I originally posted this solution in another thread, but the tl;dr version is this: you have to wait to flash the vendor image from N until you're all done with twrp, but other than that, it's just like you're updating with a monthly security patch. This doesn't require any sort of toolkits or anything else either, so that's always a plus. I'm assuming this would work on the N5X as well, but I don't have one to test this on.
1. Download the factory image of DP4 from here.
2. We're basically going to be following step 9 of @Heisenberg 's guide. So unzip the download as you normally would to update your security patch, and put it in the directory you normally would.
3. Now flash everything EXCEPT the recovery and vendor image. I've copied the code from Heisenberg's guide here for your convenience so you don't have to keep switching pages. If you're going to copy and paste that into your command prompt, don't forget to take out the images I listed.
4. Now that that's done, we're going to go to your phone. Use the fastboot menu to boot into twrp. At this point, you should be able to enter your lock pattern/pin/whatever, and then flash SuperSu as you normally would. IIRC, you'll need v2.74 or higher, which you can download from here.
5. Now using twrp, reboot back into your bootloader. Fastboot flash the DP4 vendor image that we left out earlier, otherwise your phone won't boot.
That's it! You can now boot into system, and you'll be running Nougat DP4! The first boot took a while, and looped a couple timed for me, but it worked, and I've been running DP4 without wiping my data, without decrypting, and with root for a couple weeks. Remember, twrp won't work with the N vendor image installed, so if you want to use twrp again, you'll have to reflash the M vendor image, and then reflash the N one after you're all done. I haven't tried this yet, but that's what I intend to do when it comes time to update to DP5, whenever Google releases that. Happy flashing!
Click to expand...
Click to collapse
Kudos. Always good to have a write up with steps for folks. Thanks for contributing. [emoji6]
Thanks for this post; I think it really helps having a quick reference for something like this. I can confirm that if you need to re-access TWRP, you can just flash the marshmallow vendor.img over adb, boot to TWRP, do what you have to do, return to bootloader, flash the nougat vendor.img in adb, and continue using your device. I had to use TWRP to flash the Adaway systemless support zip and doing that sequence I listed above worked as expected. It's not as ideal as having TWRP function with an encrypted device as it does on marshmallow, but at least it works.
superchilpil said:
Quite honestly if someone needs a guide they don't need to be flashing.
They need to do the proper research and understand what each image is. Just my opinion
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
benleonheart said:
I agree on this, but you know how it is, people just come in, ask, find, copy/paste and that's it.
1day old accounts with 2/3 posts.
Click to expand...
Click to collapse
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
SyCoREAPER said:
I hope you guys don't fall off your pedestal way up there above everyone else.
Everyone has to learn somewhere and the guide above is a nice start for the noobiez on the forum.
Click to expand...
Click to collapse
Worry not, dear friend as I was also a noob back in '08/'09.
We all learn new things every day. I'm just saying that there are dedicated threads to help with newcomers and guide them step by step.
Edit: You're right. Thanks.
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Sweet! This was easy peasy and didn't lose my data. No serious issues, either. Thanks for sharing this info.
Cheers
Sent from my Nexus 6P using XDA-Developers mobile app
crossen0 said:
When booting into twrp, will it prompt you for a pin/password? I never set one and I'm afraid it will make me have to completely wipe my phone.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
To be honest, I'm not sure. I've never had to deal with twrp and no password. I wouldn't think it would reset anything; I assume you just won't have to enter a password..?
What do you normally do for twrp?
thanks for the guide. Do you think if I'm already on DP4 I could flash the vendor image from an M build and continue from there?
edit: it worked!
Thank you this worked like a charm! Switched from a rooted+busybox stock build to rooted DP4. Now waiting for DP5
No problem! Glad it worked for you!
asj0422 said:
No problem! Glad it worked for you!
Click to expand...
Click to collapse
Just upgraded from my stock M + rooted + busy boxed + xposed build to DP5. TWRP and SU both working. Thanks for the guide.
Just updated to DP5 using this method (all flashes but vendor and recovery, flash M vendor, boot into TWRP, root, reboot to bootloader, flash DP5 vendor). Works perfect.
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
mtw4991 said:
Works on un-encrypted as well. Flashed bootloader, radio, boot, cache and system, reboot TWRP to allow modification-back to bootloader and flashed modified boot.img. Then boot to TWRP, adb sideload SuperSU-2.76, reboot bootloader and flash vendor.img then reboot system. Profit! Still unencrypted with no loss of data and root retained.
Click to expand...
Click to collapse
Thanks for the extra info!
Question: doesn't twrp work with N as it did with M if you're not encrypted? I thought the issue with twrp and N was due to twrp's code not being able to decrypt - and that was the whole reason people were using the modified boot.img and decrypting was so twrp would work.
I can also confirm that this works with DP5. Will be updating OP shortly.
This is a US unlocked patched boot.img by magisk
It works on T-Mobile variant as well.
(Added EU patched boot.img)
(Added T-Mobile Oreo boot.img)
Link for Oreo T-Mobile
https://drive.google.com/file/d/17U0m0LIshFNBdNaygVqpsQ4TeLiDRUuo/view?usp=drivesdk
Link for latest T-Mobile 2.15.531.11
https://www.androidfilehost.com/?fid=890129502657596824
Install magisk manager apk from magisk thread.
Flash in fastboot
fastboot flash boot patched_boot.img in download mode.
I am not responsible for anything that happens to your device.
Credits to @Captain_Throwback for the right direction.
Credits to @topjohnwu for magisk.
And credits to anyone else that plays a part.
OS version 1.00.617.15 works for T-Mobile variant too.
Us unlocked stock boot.img link https://drive.google.com/file/d/11OFuYNePnSSCTfC4pWpxVOgKoLvByxJ0/view?usp=drivesdk
Patched boot.img link
https://drive.google.com/file/d/1XdoIln2zai1464CCTOE0LsD2SWbVZrW0/view?usp=drivesdk
ANDROID ONE FASTBOOT FLASHING IS DIFFERENT THAN US VERSIONS
because the a & b partitions.
So, now I have the patched_boot.img and the boot_signed.img for December security patch, build No. 1.09.401.2.
You have to check with "fastboot getvar all" wich partition is active so you have to boot to boot_a or boot_b. For me it was b now.
To take new update you have to flash the signed_boot first.
https://drive.google.com/open?id=1emcDV3p6Nuqgc2RVD9BnWUnU7JV-vqez
This is for os version 1.06.401.14 europe it is from
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1. 06.401.14_Radio_sdm630-005201-1711031628A_release_515519_signed_2_4
Patched htc_ocla1_sprout boot.img link
https://drive.google.com/open?id=1em...BnWUnU7JV-vqez
credits to @MC_Ohr
Stock boot.img
https://drive.google.com/file/d/1V69fjXKskPQ-6EpFZm2Pxe3S2yrFGIWL/view?usp=drivesdk
Awesome thanks to this I might get this device now.
EDIT: It's working, thanks.
BookCase said:
Not working for me.
Click to expand...
Click to collapse
You need to unlock your bootloader first..
I dont have tmobile version. I have normal Life (EU). How can root and unlock?
So, after installing Magisk, a lot of my apps are force closing.
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Well just unlocked my booloader next flash me a recovery, Then it will be time to get some BadSeed up in here ,,,, Just sayin
BookCase said:
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Click to expand...
Click to collapse
What device variant do you have?
twinnfamous said:
What device variant do you have?
Click to expand...
Click to collapse
T-Mobile HTC U11 Life
BookCase said:
T-Mobile HTC U11 Life
Click to expand...
Click to collapse
I have the same variant and no problems for me. Did u install anything else?
In case anyone has a temporary lapse of brain functioning like I did and gets confused because it seems this isn't working, it is important to remember that you'll need to install the Magisk Manager apk and Phh's Superuser (at least, those are the things I had to do after realizing I didn't pay attention to the fact that this is Magisk).
twinnfamous said:
I have the same variant and no problems for me. Did u install anything else?
Click to expand...
Click to collapse
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
BookCase said:
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
Click to expand...
Click to collapse
Factory reset and let google backup restore your apps
twinnfamous said:
Factory reset and let google backup restore your apps
Click to expand...
Click to collapse
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Has anyone else had any issues with Magisk refusing to install modules after flashing this? It acts like a module is being flashed but changes nothing. I'm wondering if it has to do with not having a functional recovery at the moment. I have been able to install Xposed using the Xposed installer and Xposed is working perfectly.
BookCase said:
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Click to expand...
Click to collapse
U should be able to get back to normal unless you modified the system. I have a system img. I can upload later if that's the case
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
cbrown245 said:
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
Click to expand...
Click to collapse
U can flash things in recovery now. You just can't decrypt data yet. So only you can flash from external SD card.
Yes , but is this after you format the memory ? I can't get anything to show on the SD card or the external SD card, is it required to format ?
Just flash the zip in TWRP to change your boot logo. These should work for any model of the G6 Play. All backgrounds are white with the exception of the original boot logo. This was done to cover up that annoying bad key or N/A message. Enjoy!
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
the-her0 said:
Hey, thanks for this! If I do a design, could you make it into one of these? For example, this one?
Click to expand...
Click to collapse
Yep, check back in like 10-15min and I'll make that a logo.
Edit: Done!
Motorola Moon
This took me a few hours. Hope you folks like it. I'll probably make a few more over the next several days.
Is there a tutorial anywhere on how make these?
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Motorocker said:
These are great and just what I need, however, I can't seem to the zip files when I'm booted into TWRP on my XT1922-3 (I think it has something to do with not being able to find a download for XT1922-3_no_dm-verity_boot.img that still exists anywhere). So is there a way to flash this using fastboot?
I tried unzipping and using the command > 'fastboot flash logo logo.bin' which it said was successful, but I still see the bad key or N/A.
It would be great if anyone can explain how to get this to work for me.
Click to expand...
Click to collapse
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
madbat99 said:
You shouldn't need a no verity boot.img
You can flash the dmverity disabler then magisk.
If you already have TWRP, then dmverity has already been disabled. Or your phone wouldn't boot.
But if you need it
https://forum.xda-developers.com/an...-dm-verity-forceencrypt-t3817389/post77091359
Click to expand...
Click to collapse
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Motorocker said:
Thanks, yes, I downloaded that already and put the zip file into the root directory, but TWRP doesn't see it to be able to install/flash it.
As I don't need the phone rooted, as I'm just setting it up to sell on, I think I'll just reflash the stock firmware and see if I can relock the bootloader and get rid of the N/A and/or Bad Key messages, so it is like oem from the factory, for whoever buys it.
Click to expand...
Click to collapse
That's because TWRP can't read encrypted storage. Has to on your SD card.
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
flash713 said:
These are really cool! Appreciate you sharing what you made and getting the annoying "bad key" done away with. Did you follow a specific tutorial to make these or you just already knew how? I am interested. I would like to make some is why I ask. I use Ubuntu on my home computer and I have gimp. I haven't ever really messed with it much but I plan on setting down with it soon ,hopefully this weekend and this would be a cool project I believe to start out. I'll search around here on xda and see what all I can find on boot logos. Thank you! Also thank very much for the custom twrp recovery!! If it wasn't for you I don't believe the Moto g6 play would be able to install GSI roms. :good:
Click to expand...
Click to collapse
https://forum.xda-developers.com/mo...-boot-logo-maker-source-t2848667/post54841085
Can someone make boot.logo in HavocOs style?
Who can make logo.bin for havoc-os? I’m attaching a picture, and below it should be moto g6 play
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Thank you so much!! Very happy to finally have write access to /system! Nice work!
I'm just hoping we get some ROM support on this phone. I always run gappless. Lol.
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Yo just curious can you explain to me how you built this i cant seem to get it build rigjt or send me your source files
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Sorry, but I have to ask. You say it's working but if it has no touch then how does it work? Command line?
arkansawdave74 said:
Sorry, but I have to ask. You say it's working but if it has no touch then how does it work? Command line?
Click to expand...
Click to collapse
would be presumably by way of a USB connected hub to attach a mouse and maybe a keyboard too, though there is another version of TWRP 3.5 which I've just gotten working on my xt2114-7 running 11. I also used it to flash magisk which appears installed but has yet to prompt me to give root perms to anything.... which seems odd. hmm.... anyway there's another TWRP in these forums that may do the trick https://forum.xda-developers.com/t/...o-android-11-based-updated-11-4-2021.4354855/ as far as I can tell this is only working on 11 currently and seems a bit touchy about the touchscreen driver when it first boots, but I did a fastboot flash magisk_boot.img and then did a fastboot boot into the TWRP, and from there I actually flashed the TWRP file from within the booted TWRP environment. That sounded more complicated than it is...
Here is a updated TWRP with everything working use at your own risk
treesus said:
would be presumably by way of a USB connected hub to attach a mouse and maybe a keyboard too, though there is another version of TWRP 3.5 which I've just gotten working on my xt2114-7 running 11. I also used it to flash magisk which appears installed but has yet to prompt me to give root perms to anything.... which seems odd. hmm.... anyway there's another TWRP in these forums that may do the trick https://forum.xda-developers.com/t/...o-android-11-based-updated-11-4-2021.4354855/ as far as I can tell this is only working on 11 currently and seems a bit touchy about the touchscreen driver when it first boots, but I did a fastboot flash magisk_boot.img and then did a fastboot boot into the TWRP, and from there I actually flashed the TWRP file from within the booted TWRP environment. That sounded more complicated than it is...
Click to expand...
Click to collapse
Oh. My bad, man. I had misread the dude's typo. It says, "no touch on mouse support," and I thought he'd meant to say "or," but I later realized that he'd meant to say "only." It apparently has mouse support.I broke my Power 2021 right after I got it, but I did get it rooted using this twrp in an adb shell to pull my kernel because the kernels in the lolinet firmwares, after patching, caused the 2021 to lose touch functionality completely. But, even though it's the same damned kernel, when you pull it with:
"adb shell"
"twrp backup B"
it will make a backup in the usual spot in internal storage (/sdcard/TWRP). Go in there and find the file and rename it to boot.img (or something like twrpdboot.img to keep it from being confused with the other boot images) and if you patch that one with magisk it will boot fine and your touch screen will work. The only reason I haven't told others about that is because of two reasons. For one, everyone's using some windows program that sources its downloads from a different spot than lolinet, and those kerels, I assume, work ( I wouldn't touch windows with my worst enemies computer, myself, so I had to find another way using Linux). And for two, I broke my Moto G power 2021 just a day after I got it. This TWRP in here won't work with all these commands but some of them do work. Backup sure does.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
I now have the phone I meant to get in the first place, the Moto G9 Power with an official TWRP build.
arkansawdave74 said:
Oh. My bad, man. I had misread the dude's typo. It says, "no touch on mouse support," and I thought he'd meant to say "or," but I later realized that he'd meant to say "only." It apparently has mouse support.I broke my Power 2021 right after I got it, but I did get it rooted using this twrp in an adb shell to pull my kernel because the kernels in the lolinet firmwares, after patching, caused the 2021 to lose touch functionality completely. But, even though it's the same damned kernel, when you pull it with:
"adb shell"
"twrp backup B"
it will make a backup in the usual spot in internal storage (/sdcard/TWRP). Go in there and find the file and rename it to boot.img (or something like twrpdboot.img to keep it from being confused with the other boot images) and if you patch that one with magisk it will boot fine and your touch screen will work. The only reason I haven't told others about that is because of two reasons. For one, everyone's using some windows program that sources its downloads from a different spot than lolinet, and those kerels, I assume, work ( I wouldn't touch windows with my worst enemies computer, myself, so I had to find another way using Linux). And for two, I broke my Moto G power 2021 just a day after I got it. This TWRP in here won't work with all these commands but some of them do work. Backup sure does.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
Click to expand...
Click to collapse
I used lolinet files on my 2021, no touch issues, but mine uses the Ilitek display. But since you seem to be familiar with Linux as you put it, you could unpack and repack yours and ramdisk, having pulled files like I outline in https://ilitekforum.xda-developers....ased-updated-11-4-2021.4354855/#post-85885471, so you may be able to make your TWRP have touch, unless you meant damaged so much that's broken too.
I posted a fixed twrp file for you all
svoc said:
I posted a fixed twrp file for you all
Click to expand...
Click to collapse
which version of TWRP is this one? Can I find a changelog to check out somewhere?
Onoitsu2 said:
unless you meant damaged so much that's broken too.
Click to expand...
Click to collapse
It's out of there. I'lI maybe get another one though because I really want to try Visible Wireless Service and this G9 Power doesn't have esim capability. True unlimited with no hotspot cap for $40/month. Maybe too good to be true, but I gotta check it out. Until then, Check ya laters borneo dudes.
treesus said:
which version of TWRP is this one? Can I find a changelog to check out somewhere?
Click to expand...
Click to collapse
I dont make change logs this is twrp 3.4
svoc said:
I dont make change logs this is twrp 3.4
Click to expand...
Click to collapse
I build for myself then when it working I give it away I do t keep track of what I do to get it working I just get it working then give it out sorry I'm working on LineageOS right now I got the device trees working last night I got my first build working but still a lot to test out before release
Excited to follow development for the Borneo. Thank you.
If you have any features you would like let me know when I build a rock I make it 100% Google stock no anything extra so let me know if you want any fluff
svoc said:
If you have any features you would like let me know when I build a rock I make it 100% Google stock no anything extra so let me know if you want any fluff
Click to expand...
Click to collapse
No fluff - just stock. thanks for your hard work.
svoc said:
I posted a fixed twrp file for you all
Click to expand...
Click to collapse
Is there a way to get this working on the G Power (2021) model XT2117-4 (OS is android 11)? I tried running fastboot boot twrp_fixed.img and it just sent me back to the boot loader. Also if its important for me to post my touchscreen stuff, here it is.
Code:
borneo:/ $ cd /sys/class/touchscreen
borneo:/sys/class/touchscreen $ ls
ft8009
4xc7xy said:
Is there a way to get this working on the G Power (2021) model XT2117-4 (OS is android 11)? I tried running fastboot boot twrp_fixed.img and it just sent me back to the boot loader. Also if its important for me to post my touchscreen stuff, here it is.
Code:
borneo:/ $ cd /sys/class/touchscreen
borneo:/sys/class/touchscreen $ ls
ft8009
Click to expand...
Click to collapse
Did you 'fastboot reboot bootloader' first before the boot attempt? You need be in the Fastbootd, not the normal Fastboot screen. I know it's odd, but that's how I got mine. Because apparently fastboot itself won't boot even my TWRP but fastbootd does. The device being an A/B device is the only reason to ever use fastboot (not fastbootd), to flash the sparsed system image is my understanding.
Onoitsu2 said:
Did you 'fastboot reboot bootloader' first before the boot attempt? You need be in the Fastbootd, not the normal Fastboot screen. I know it's odd, but that's how I got mine. Because apparently fastboot itself won't boot even my TWRP but fastbootd does. The device being an A/B device is the only reason to ever use fastboot (not fastbootd), to flash the sparsed system image is my understanding.
Click to expand...
Click to collapse
No I did not, let me try that right now and then do a follow up reply to tell you how it goes
I had my phone rooted perfectly fine and I accidentally let an update get by me and now it's unrooted Android 12. I really need my boot.img from GN2200_11_C.10 or I need to know where to download a Pretooted GSI image that I can DSU Sideload so I can pull my own boot l.img.. thanks in advance!!
Where? I couldn't find it
ScarletWizard said:
Did u find it
Click to expand...
Click to collapse
No I still can't find this specific one?! Stinks!
termux4life said:
No I still can't find this specific one?! Stinks!
Click to expand...
Click to collapse
I appreciate your help though. Thank you for taking the time to respond back.
termux4life said:
No I still can't find this specific one?! Stinks!
Click to expand...
Click to collapse
Thank you for taking your time to respond though.
I'm looking for a specific boot.img. it's in the title.. you need to use the msm download tool to revert back to stock. Sounds like your partitions are messed up and I assume they weren't backed up. I was hard bricked at one point and the msm tool was the only way for me to fix it all and revert back to stock. Make sure it's the correct msm tool for your phone though.
ScarletWizard said:
Try
Or this
Wipe data after flashy
Wipe data
Too large I got several but too large to attach
Click to expand...
Click to collapse
Can you send me the link for the specific boot.img I'm looking for by chance? It's the 11_C.10 version.
ScarletWizard said:
I locked my Boot loader and now device is ****ed
Click to expand...
Click to collapse
Why you can't just unlock it again? Do you have the the T-Mobile version?
The bootloader is encrypted and OnePlus's token just gives you the private to match the public encryption that keeps the bootloader from being edited. In theory if you can discover what file type one plus's token is in and eextract that and somehow dump your bootloader you could possibly manually decrypt it.
Do you have access to a Personal Computer? I could offer some links to a few programs that may be worth trying. I doubt it could hurt trying.
I could use teamviewer to try to use my tools to force your bootloader to unlock also if you happen to not find a solution.
termux4life said:
Thank you for taking your time to respond though.
Click to expand...
Click to collapse
i have the exact one
termux4life said:
I had my phone rooted perfectly fine and I accidentally let an update get by me and now it's unrooted Android 12. I really need my boot.img from GN2200_11_C.10 or I need to know where to download a Pretooted GSI image that I can DSU Sideload so I can pull my own boot l.img.. thanks in advance!!
Click to expand...
Click to collapse
Pretooted, that's funny as can be. A pretooted sideload so he can pull his own.
Ok so 2 things..
1st: Jayram1408, for being a senior member I'm really surprised you'd laugh at me for asking a question or not knowing something. Usually this is a safe place to learn, ask questions, and receive feedback that's positive and informative. I don't know if you think others will laugh at me with you but I doubt it
2nd: I don't know what is funny in the first place, pre-rooted GSI for DSU Sideloading purposes do exist and that's a fact. It makes it so you can use Partitions Backup & Restore properly when the GSI is loaded. Please read https://forum.xda-developers.com/t/...g-boot-image-and-making-your-backups.4499447/
Hopefully that catches you up with the rest of us and hopefully in the future you are but more helpful then hurtful to members within the community.
Hey All,
I am trying to root my Nord N20, but am getting a bootloop when trying to boot boot_a after flashing a magisk25210canary patched boot_b image over boot_a. I am flashing a patched boot_b image over boot_a because I am too scared to flash magisk patched boot_b over boot_b (which contains the working OS). My version information is:
android 12
Build: GN2200_11_C.11 Kernel:5.4.147-qgki-ga9e7460afd8c