I have successfully bricked my Nokia 8 Ta-1004. What I did was following this thread
https://forum.xda-developers.com/nokia-8/development/question-nokia-8-partitions-t3682617
So, here's the story; At first, I was doing that procedure in above link one by one. Since my bootloader is unlocked thanks to @the_laser. I decided to use adb reboot bootloader and follow the procedure (Not using OST LA). Then I typed the command below:
fastboot-android flash boot NB1-boot.img
fastboot-android reboot
Press and hold Volume Up, then execute the command above. Keep holding Volume Up until you see the 7to logo.
I didn't do the BOLD one because I forgot. Due to that, not only did the TWRP not showing up, but it also always show DOWNLOAD MODE in Nokia 8 whenever I restart. I was desperate and then I use this thread and said screw the TWRP. I just need root at all.
https://forum.xda-developers.com/nokia-8/development/testing-flash-patched-boot-img-to-t3729396
1. Install OST LA and patch it, and OPEN IT FROM INSTALLATION DIRECTORY DIRECTLY.
2. Flash required firmware before proceed. If you don't do that, you won't be able to access Wi-Fi after the boot.img flashed.
Quote:
For Nokia 7, you need to use the firmware "C1N-0430-0-00CN-B05" which I haven't released to public for some reason.
For Nokia 8, you need to use the firmware "NB1-435J-0-00WW-B01" which released in this topic: https://forum.xda-developers.com/sho....php?t=3678487
If you've already flashed required firmware before proceed, you can skip this part.
3. Use the Service Purposed Bootloader trick I've mentioned in the Nokia 6 Root Guide: https://forum.xda-developers.com/sho....php?t=3702354
4. Type these commands:
Code:
fastboot-android flash boot_a E:\NB1-435J-Boot-Patched.img
fastboot-android flash boot_b E:\NB1-435J-Boot-Patched.img
fastboot-android reboot
5. If it's accepted by the system, the phone will reboot twice, and you'll see SuperSU appeared.
So, I skipped the BOLD part since my bootloader is unlocked and I didnt use OST LA. I proceeded to patch using given img. Not the same one as the first link. After I rebooted, it is no longer reboot to DOWNLOAD MODE. It can go into the OS but I see no SUPERSU and the device is now stuck in auto restart.
I think the main issue is the incorrect boot.img to the firmware. If anyone must know, my security android is February 1, 2018. I forgot the build number of my firmware. I figure if i use boot.img I can recover the OS.
Does anyone have stock boot.img so i can reflash it? Thank you. I am so desperate.
N.B: I tried using OST LA oreo version to flash the firmware "NB1-435J-0-00WW-B01". Guess what, It is stuck in "FLASHING SERVICE BOOTLOADER". Now I am in total desperate. I thought this could recover from bricked phone.
I'll have the stock boot. IMG, but I think if u flash this, wifi gets broken. I have the broken wifi and after flash self patched boot.img to gain root.
Now I have root with magisk, but no wifi
2WildFirE said:
I'll have the stock boot. IMG, but I think if u flash this, wifi gets broken. I have the broken wifi and after flash self patched boot.img to gain root.
Now I have root with magisk, but no wifi
Click to expand...
Click to collapse
Let me try the stock boot.img to flash into boot_A and boot_B if you may.
I flashed two of them which makes me think it is the cause of boot loop.
Ok will upload, use at your own risk.
ok here we go, i have booth 435 oreo and 484 oreo8.1 boot images.
i wish u luck.
https://drive.google.com/drive/folders/1WYAj9HVxrYBIsKQQaKe7UKV0b4sXOsIy?usp=sharing
2WildFirE said:
Ok will upload, use at your own risk.
ok here we go, i have booth 435 oreo and 484 oreo8.1 boot images.
i wish u luck.
https://drive.google.com/drive/folders/1WYAj9HVxrYBIsKQQaKe7UKV0b4sXOsIy?usp=sharing
Click to expand...
Click to collapse
Two versions? Which is the February 1, 2018 Build number one? Thanks for sharing
Stock boot.img
Hi bro!
drive .google .com/ drive/folders/ 1JcWV1JF9Yi7iUhaZqd6XFWR7FVQZmlXA (remove spaces)
have boot's
NB1-435J-0-00WW-B01
NB1-484A-0-00WW-B03
NB1-4390-0-00WW-B01
nummerok said:
Hi bro!
drive .google .com/ drive/folders/ 1JcWV1JF9Yi7iUhaZqd6XFWR7FVQZmlXA (remove spaces)
have boot's
NB1-435J-0-00WW-B01
NB1-484A-0-00WW-B03
NB1-4390-0-00WW-B01
Click to expand...
Click to collapse
Thank you so much. I appreciate it and give you my thanks to both of you
godofknife said:
Thank you so much. I appreciate it and give you my thanks to both of you
Click to expand...
Click to collapse
I just now faced the same problem when I wanted to put TWRP. In the end, I still do not understand how to do this. The loader unblocked)
If you have a different version of the firmware, write, I'll throw off boot.img.
nummerok said:
Hi bro!
drive .google .com/ drive/folders/ 1JcWV1JF9Yi7iUhaZqd6XFWR7FVQZmlXA (remove spaces)
have boot's
NB1-435J-0-00WW-B01
NB1-484A-0-00WW-B03
NB1-4390-0-00WW-B01
Click to expand...
Click to collapse
2WildFirE said:
Ok will upload, use at your own risk.
ok here we go, i have booth 435 oreo and 484 oreo8.1 boot images.
i wish u luck.
https://drive.google.com/drive/folders/1WYAj9HVxrYBIsKQQaKe7UKV0b4sXOsIy?usp=sharing
Click to expand...
Click to collapse
IT IS WORKING. Thank you so much to both of you. You are rock. I am glad I created this thread so other people can get this resources.
nummerok said:
I just now faced the same problem when I wanted to put TWRP. In the end, I still do not understand how to do this. The loader unblocked)
If you have a different version of the firmware, write, I'll throw off boot.img.
Click to expand...
Click to collapse
TWRP is not working. Boot failed and keeps booting in download mode. Restoring using the stock boot.img solves the problem.
It turns out i was using 484A WW.
Is wifi working for u?
godofknife said:
TWRP is not working. Boot failed and keeps booting in download mode. Restoring using the stock boot.img solves the problem.
It turns out i was using 484A WW.
Click to expand...
Click to collapse
how to install SuperSU on nokia?
---------- Post added at 07:55 PM ---------- Previous post was at 07:49 PM ----------
2WildFirE said:
Is wifi working for u?
Click to expand...
Click to collapse
yep. On 484A
I have a patched boot.img (magisk) but I lost wifi after flash [emoji6] so I have atm root but no wifi
2WildFirE said:
I have a patched boot.img (magisk) but I lost wifi after flash [emoji6] so I have atm root but no wifi
Click to expand...
Click to collapse
pls, patch NB1-0-484A-00WW-boot.img
or say, how to patch?
nummerok said:
pls, patch NB1-0-484A-00WW-boot.img
or say, how to patch?
Click to expand...
Click to collapse
here we go, but dont forget. Use at your own risk!! i think you will lost wifi.... and atm no way to get it back!
https://drive.google.com/open?id=1SH-rszoI-NQ0xUF7pe5xLLgcxDNSdcKD
1.download Magisk manager.apk and install
2. flash boot.img via fastboot flash boot_a
3. flash boot.img via fastboot flash boot_b
You will lost WIFI dont forget!
2WildFirE said:
here we go, but dont forget. Use at your own risk!! i think you will lost wifi.... and atm no way to get it back!
https://drive.google.com/open?id=1SH-rszoI-NQ0xUF7pe5xLLgcxDNSdcKD
1.download Magisk manager.apk and install
2. flash boot.img via fastboot flash boot_a
3. flash boot.img via fastboot flash boot_b
You will lost WIFI dont forget!
Click to expand...
Click to collapse
why lost WiFi? How to add SuperSu to mu boot.img ?
nummerok said:
why lost WiFi? How to add SuperSu to mu boot.img ?
Click to expand...
Click to collapse
Idk why but after flash patched boot.img, my wifi is broken.
You can try Android kitchen to patch it with supersu
2WildFirE said:
Idk why but after flash patched boot.img, my wifi is broken.
You can try Android kitchen to patch it with supersu
Click to expand...
Click to collapse
camera and wifi not workign. SU not working, i have some errors on other apps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-------------------------
Guys, i need NB1 484A 00WW SP01 boot.img
my WiFi not working after install update )
2WildFirE said:
Is wifi working for u?
Click to expand...
Click to collapse
Yes, it is for Stock boot.img that you gave me.
nummerok said:
how to install SuperSU on nokia?
---------- Post added at 07:55 PM ---------- Previous post was at 07:49 PM ----------
yep. On 484A
Click to expand...
Click to collapse
Using TWRP or Patched BOOT.IMG
2WildFirE said:
I have a patched boot.img (magisk) but I lost wifi after flash [emoji6] so I have atm root but no wifi
Click to expand...
Click to collapse
Yeah, I am thinking for now patching boot.img is the way to achieve root without TWRP. Unless someone releases TWRP Officially and way to flash it. I am just gonna stick to this.
nummerok said:
pls, patch NB1-0-484A-00WW-boot.img
or say, how to patch?
Click to expand...
Click to collapse
Waiting for someone to patch it too.
2WildFirE said:
here we go, but dont forget. Use at your own risk!! i think you will lost wifi.... and atm no way to get it back!
https://drive.google.com/open?id=1SH-rszoI-NQ0xUF7pe5xLLgcxDNSdcKD
1.download Magisk manager.apk and install
2. flash boot.img via fastboot flash boot_a
3. flash boot.img via fastboot flash boot_b
You will lost WIFI dont forget!
Click to expand...
Click to collapse
nummerok said:
why lost WiFi? How to add SuperSu to mu boot.img ?
Click to expand...
Click to collapse
2WildFirE said:
Idk why but after flash patched boot.img, my wifi is broken.
You can try Android kitchen to patch it with supersu
Click to expand...
Click to collapse
I am noob when using Android kitchen. Do you have patched with super su instead?
nummerok said:
camera and wifi not workign. SU not working, i have some errors on other apps
-------------------------
Guys, i need NB1 484A 00WW SP01 boot.img
my WiFi not working after install update )
Click to expand...
Click to collapse
Well, no way but to use stock boot.img to get wifi again.
godofknife said:
Using TWRP or Patched BOOT.IMG
Well, no way but to use stock boot.img to get wifi again.
Click to expand...
Click to collapse
Need stock to 484A SP01!!!
TWRP DONT WORKING ON NOKIA 8! NOKIA 8 DON'T HAVE RECOVERY PARTITION!
Related
This is the OnePlus 5's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Thaaaanks but has anyone rooted there op5 with this yet? Does it actually work? Probably does but just would like to make 110% sure
icem8n said:
Thaaaanks but has anyone rooted there op5 with this yet? Does it actually work? Probably does but just would like to make 110% sure
Click to expand...
Click to collapse
This tool cant directly root your phone, but it can unlock your bootloader and help you to flash a twrp. If you want to root your phone you can flash twrp and then flash the root zip through twrp
Bootloader successfully unlocked
I´ve also flashed this Chinese TWRP with your tool due to my eagerness
and finally rooted with Magisk
@mauronofrio your efforts are really appreciated
Deacon-Frost said:
Bootloader successfully unlocked
Click to expand...
Click to collapse
Perfect:good:
Awesome looking tool. I'll be downloading and donating as soon as I get my OP5 on Monday.
I plan on running stock software for awhile but can I simply unlock, flash TWRP, and flash the same SuperSU I always use for custom ROMs?
biglilsteve said:
Awesome looking tool. I'll be downloading and donating as soon as I get my OP5 on Monday.
I plan on running stock software for awhile but can I simply unlock, flash TWRP, and flash the same SuperSU I always use for custom ROMs?
Click to expand...
Click to collapse
Yes, i don't know if there are a supersu specific version must be flashed, but yes, unlock the bootloader, flash the twrp and then flash supersu or magisk. I don't know if you need to disable dm-verity before reboot but i think yes
was impatient... and got everything working... unlocked, TWRP recovery, and then Magisk rooted. woot woot.!!
now hopefully there is a working xposed
AznMTboy said:
was impatient... and got everything working... unlocked, TWRP recovery, and then Magisk rooted. woot woot.!!
now hopefully there is a working xposed
Click to expand...
Click to collapse
Perfect:good:
Made a backup before flash xposed
perfect！thank you！
Which version of magisk 13 you use?
Gesendet von meinem Nexus 6P mit Tapatalk
cant install twrp
i cant install twrp and also cant root the phone, some one can help me? i try all i can to get it work....
this is what i get always..
hounter17 said:
i cant install twrp and also cant root the phone, some one can help me? i try all i can to get it work....
this is what i get always..
View attachment 4192075 View attachment 4192076
Click to expand...
Click to collapse
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
Craxx said:
Which version of magisk 13 you use?
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
I have not tested it, i think the last should work
mauronofrio said:
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
the problem is that i can get it flashed
Click to expand...
Click to collapse
hounter17 said:
mauronofrio said:
When you flash the twrp select the options "And boot it" and you will rebooted directly to the twrp, someone say that the TWRP survive for only 1 reboot
the problem is that i can get it flashed
Click to expand...
Click to collapse
You are the first until now. To flash the twrp you need to have an internet connection, because the tool before download the recovery and then flash it. If you have made all of this try to delete the downloaded recovery and flash it again (maybe the download has failed). To delete the downloaded recovery you need to go in the advanced options and use the "Delete Files" (top right of the page) button to delete what you want (in this case you need only to delete TWRP recoveries). Tell me if you solve
Click to expand...
Click to collapse
Someone said that TWRP will only survive for one reboot. I've flashed yesterday that Chinese TWRP and rooted with Magisk. My experience is that TWRP will stay. I've booted today three times into TWRP. Everything seems to be as normal as it should be.
Deacon-Frost said:
Someone said that TWRP will only survive for one reboot. I've flashed yesterday that Chinese TWRP and rooted with Magisk. My experience is that TWRP will stay. I've booted today three times into TWRP. Everything seems to be as normal as it should be.
Click to expand...
Click to collapse
Perfect so the problem is another one. When the twrp is booted for the first time it automatically delete or hide the stock recovery so if you flash the twrp and you boot directly from fastboot to twrp, the twrp will survive but if you flash the twrp and power one normally the phone the stock recovery will be restored. So when you flash the twrp, directly boot in it, from the tool you need to check "And boot it" option to boot it directly after flash.
mauronofrio said:
hounter17 said:
You are the first until now. To flash the twrp you need to have an internet connection, because the tool before download the recovery and then flash it. If you have made all of this try to delete the downloaded recovery and flash it again (maybe the download has failed). To delete the downloaded recovery you need to go in the advanced options and use the "Delete Files" (top right of the page) button to delete what you want (in this case you need only to delete TWRP recoveries). Tell me if you solve
Click to expand...
Click to collapse
i try all and it tucks here:
View attachment 4192182
Click to expand...
Click to collapse
hounter17 said:
mauronofrio said:
i try all and it tucks here:
View attachment 4192182
Click to expand...
Click to collapse
i'm unable to load this image and please be more specific, when you got this problem?
Click to expand...
Click to collapse
mauronofrio said:
hounter17 said:
i'm unable to load this image and please be more specific, when you got this problem
Click to expand...
Click to collapse
im sorry about the troubles... i unlock the bootloader i enable usb debuging and i reboot it in fastboot mode. them i use the tool to flash the recovery but when the cmd screen gets on it stucks and doesnt finish the process...
i dont know what to do in this point
i also see that in fastboot mode screen appear that the product name was "QC_reference_phone" and the bootloader and the baseband brands are empty.
the device state was "unlocked"
Click to expand...
Click to collapse
NOW WE GOT THE ROOT!
First, I was been able to get the bootloader unlocked by standard unlocking method. Head to this Thread [url]https://forum.xda-developers.com/zenfone-4-max/how-to/guide-how-to-unlock-bootloader-zc554kl-t3677270[/URL]
And now, We are able to get root via Magisk Manager that will not mess with our Asus Stock ROM in benefit systemless root from Magisk. Thanks for @topjohnwu !!
You can get more information about Magisk in this thread:
[url]https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445[/URL]
And now, there are few steps for how to get systemless root on our device.
1. You need to extract the boot.img of you current ROM which can be obtained in the flashable ZIP made by Asus
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. After getting the boot.img of your current ROM, download Magisk Manager and then select install in the app. Select the Patch boot image file, and search the boot.img from the Step 1.
Wait until you get automatic process running and get you a patched_boot.img within the directory cantaining that.
3. The last, Just copy to your computer and flash out the patched_boot.img to your device with fastboot command, restart then you'll get the magisk manager work.
type this command on fastboot interface
fastboot flash boot *.img
Note:
*=Name and location of your patched_boot.img
Click to expand...
Click to collapse
That's all that you must do for gaining root access. I don't know and I don't care to what happened with your device or what is that you blame about. Just take the risk alone!
:silly::silly::silly:REMEMBER! ALWAYS DO WITH YOUR OWN RISK! I'M NOT RESPONSIBLE AT ALL! WHAT YOU'VE DONE IS DONE!:silly::silly::silly:
Best regards.:good::highfive:
Nice job! Say, will this work on the Zenfone 4 Max Pro? Specifically, model ASUS_X00ID. It's a different model than the Zenfone 4 Max, but they share the same ZC554KL code (whatever that is.)
TheStrangeStarfish said:
Nice job! Say, will this work on the Zenfone 4 Max Pro? Specifically, model ASUS_X00ID. It's a different model than the Zenfone 4 Max, but they share the same ZC554KL code (whatever that is.)
Click to expand...
Click to collapse
You can try unlocking the bootloader first. Then try this patching method. The msm8917 and msm8937 just a same structured chispset. Asus had the two config at the source code at once. Go and try. And report here too.
Unfortunately, it doesn't work. Can't get the bootloader to unlock. I go as far as fastboot oem get_unlock_key , which gives me an "OKAY" but when I enter "fastboot oem unlock-go" if gives me a "FAILED (remote:unknown command)
I am sure I installed ADB and Fastboot correctly. At least I hope I did. I'd be happy to know that I didn't install fastboot correctly.
---------- Post added at 10:57 AM ---------- Previous post was at 10:44 AM ----------
TheStrangeStarfish said:
Unfortunately, it doesn't work. Can't get the bootloader to unlock. I go as far as fastboot oem get_unlock_key , which gives me an "OKAY" but when I enter "fastboot oem unlock-go" if gives me a "FAILED (remote:unknown command)
I am sure I installed ADB and Fastboot correctly. At least I hope I did. I'd be happy to know that I didn't install fastboot correctly.
Click to expand...
Click to collapse
I lied. Apparently IT WORKS.
I just did this in particular:
Typed: fastboot reboot bootloader (I did not do this at first, I went to bootloader manually)
Typed: fastboot oem get_unlock_key (got the okay)
Typed fastboot oem unlock (Got a "Device already : Unlocked!")
Rebooted to be sure. DEVICE STATE is UNLOCKED
Got a pic for proof
Edit: Pics don't upload properly. URL -https://pasteboard.co/GM8QVeF.jpg
Also I can't see the images on your guide.
TheStrangeStarfish said:
Unfortunately, it doesn't work. Can't get the bootloader to unlock. I go as far as fastboot oem get_unlock_key , which gives me an "OKAY" but when I enter "fastboot oem unlock-go" if gives me a "FAILED (remote:unknown command)
I am sure I installed ADB and Fastboot correctly. At least I hope I did. I'd be happy to know that I didn't install fastboot correctly.
---------- Post added at 10:57 AM ---------- Previous post was at 10:44 AM ----------
I lied. Apparently IT WORKS.
I just did this in particular:
Typed: fastboot reboot bootloader (I did not do this at first, I went to bootloader manually)
Typed: fastboot oem get_unlock_key (got the okay)
Typed fastboot oem unlock (Got a "Device already : Unlocked!")
Rebooted to be sure. DEVICE STATE is UNLOCKED
Got a pic for proof
Edit: Pics don't upload properly. URL -https://pasteboard.co/GM8QVeF.jpg
Also I can't see the images on your guide.
Click to expand...
Click to collapse
I dont have other device to picture it and forgot to screenshot all the fastboot attempt. But I sure that my way to unlock bootloader is work. Sorry for the guide, you can post the picture at the guide to unlock to make sure it works.
aaaaaaziskurnia said:
I dont have other device to picture it and forgot to screenshot all the fastboot attempt. But I sure that my way to unlock bootloader is work. Sorry for the guide, you can post the picture at the guide to unlock to make sure it works.
Click to expand...
Click to collapse
Okay, my bad. Apparently my browser's mucking things up. I can see the images clearly now. Gonna try for root. Will report soon :good:
TheStrangeStarfish said:
Okay, my bad. Apparently my browser's mucking things up. I can see the images clearly now. Gonna try for root. Will report soon :good:
Click to expand...
Click to collapse
Okay, write down the reports here. That can help the others.
We have Root! Thank you!
So far, guide is easy enough once you have everything you need.
Proof of Root
aaaaaaziskurnia said:
NOW WE GOT THE ROOT!
First, I was been able to get the bootloader unlocked by standard unlocking method. Head to this Thread [url]https://forum.xda-developers.com/zenfone-4-max/how-to/guide-how-to-unlock-bootloader-zc554kl-t3677270[/URL]
And now, We are able to get root via Magisk Manager that will not mess with our Asus Stock ROM in benefit systemless root from Magisk. Thanks for @topjohnwu !!
You can get more information about Magisk in this thread:
[url]https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445[/URL]
And now, there are few steps for how to get systemless root on our device.
That's all that you must do for gaining root access. I don't know and I don't care to what happened with your device or what is that you blame about. Just take the risk alone!
:silly::silly::silly:REMEMBER! ALWAYS DO WITH YOUR OWN RISK! I'M NOT RESPONSIBLE AT ALL! WHAT YOU'VE DONE IS DONE!:silly::silly::silly:
Best regards.:good::highfive:
Click to expand...
Click to collapse
Do you have boot.img from UL-ASUS_X00ID-WW-14.2016.1708.156-user.zip file? I've downloaded several times but ended up the zip file is corrupt.
komtek said:
Do you have boot.img from UL-ASUS_X00ID-WW-14.2016.1708.156-user.zip file? I've downloaded several times but ended up the zip file is corrupt.
Click to expand...
Click to collapse
You can bootup with older version boot.img. earlier 153 version booted up. You can use that by using "fastboot boot boot.img" without flashing to emmc. Then after booting the 153 boot.img, you can patch the 156 version that placed on mmcbkl0p24
komtek said:
Do you have boot.img from UL-ASUS_X00ID-WW-14.2016.1708.156-user.zip file? I've downloaded several times but ended up the zip file is corrupt.
Click to expand...
Click to collapse
had the same problem. Fixed it by opening the zip on winrar, going to tools and selecting repair archive.
TheStrangeStarfish said:
had the same problem. Fixed it by opening the zip on winrar, going to tools and selecting repair archive.
Click to expand...
Click to collapse
I didn't recommend the 156 zip stock because that messed up by asus it self. I use the 153 zip file
hmm, I used the 156 zip stock in particular. Is there anything I should be concerned about? Everything seems okay so far.
TheStrangeStarfish said:
hmm, I used the 156 zip stock in particular. Is there anything I should be concerned about? Everything seems okay so far.
Click to expand...
Click to collapse
Don't ever try to flash that zip to your phone. I'm wandering why the latest version just 1,32 Gb when the earlier version is 1,69 Gb. Maybe corrupted or some thing. The boot.img must be okay for flash, but other than that of course not. The boot.img is on the header of the zip so it's safe and doesn't corrupted.
aaaaaaziskurnia said:
Don't ever try to flash that zip to your phone. I'm wandering why the latest version just 1,32 Gb when the earlier version is 1,69 Gb. Maybe corrupted or some thing. The boot.img must be okay for flash, but other than that of course not. The boot.img is on the header of the zip so it's safe and doesn't corrupted.
Click to expand...
Click to collapse
Okay, good to know. All I used was the boot.img anyway.
Thanks for the heads-up!
OTA Update
Hi mate! As we know update v.158 is released. Just wanna ask, can we apply this update safely if my device is rooted? Should I unroot the device first so I can install this update?
---------- Post added at 07:33 AM ---------- Previous post was at 07:28 AM ----------
komtek said:
Hi mate! As we know update v.158 is released. Just wanna ask, can we apply this update safely if my device is rooted? Should I unroot the device first so I can install this update?
Click to expand...
Click to collapse
I tried to apply the update via OTA, but it failed. Luckily my device doesn't bricked :silly:
komtek said:
Hi mate! As we know update v.158 is released. Just wanna ask, can we apply this update safely if my device is rooted? Should I unroot the device first so I can install this update?
---------- Post added at 07:33 AM ---------- Previous post was at 07:28 AM ----------
I tried to apply the update via OTA, but it failed. Luckily my device doesn't bricked :silly:
Click to expand...
Click to collapse
Any modification will breaks OTA. That's was the risk if you have root.
Bro i have some question. Can we just root asus zenfone 4 max pro without installing twrp inside ? Thanks
Hallo guys... Theres new update 160
Is it worth to try root with that version?
christotoruan said:
Bro i have some question. Can we just root asus zenfone 4 max pro without installing twrp inside ? Thanks
Click to expand...
Click to collapse
At now still no. Android nowadays using verity that verifying the /system partitions that makes our device hangs or brick if there is a modification. That's means to us to using twrp to install magisk that can handle modification systemlessly. So the device won't brick. SuperSu itself using systemless injection.
T-Mobile G6 H872 20E Stock Collection
Based on OEM 20e KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
These Zips were not tested (no longer own a G6). Post any problems you have in the thread
20e Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
SysBoot ROMs will only work with 20a or 20d bootloaders
FILE BREAKDOWN
The following Zips DO NOT include stock LAF or Recovery
You must flash the provided LAF separately if you wish to go back to stock DL mode.
Bootloader: 20e Stock Bootloader ONLY
FullStock: Full 20e Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
If you are already on any of my other Stock ROM's, you should be able to Dirty Flash these.
If you are asked for a passcode in TWRP or are unable to mount System, Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
If you Flashed FullStock with Magisk, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:e534a2acb66ac0596c7b0594e717cff5
FullStock ROM - d53ce39c5a76ac622d5c2bf9c3e2d839
FullStock with Magisk Installer - md5:961dd56c1c81f232a22da7494691ec0db11d9deb
StockLAF - md5:ba05b2e4d7d73016272463aef177dad3
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
Please let me know if you run into any problems with them. Thanks!
Other H872 Projects
H872 11G Stock Collection
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
H872 20D Stock Collection
For my friends
I wanted to put this out quickly, so I did not create any SysBoot ROMs for this build. As of now, I don't plan on it. However, if some of you ask nicely then maybe I'll make some time
Hope everybody is doing well. Have a great day.
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h87220e, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 20e KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-12-04
Created 2018-12-04
Last Updated 2018-12-04
Just FYI, I was not able to test these since I no longer have a G6. There are some assert checks that look at your device model and file checksums. If flash fails for anyone, please let me know.
what the difference between SysBoot ROMs and FullStock with Magisk Installer???
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
aquinoer said:
what the difference between SysBoot ROMs and FullStock with Magisk Installer???
Click to expand...
Click to collapse
lol I'm sorry if I sound dumb :silly
aquinoer said:
what the difference between SysBoot ROMs and FullStock with Magisk Installer???
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
lol I'm sorry if I sound dumb :silly
Click to expand...
Click to collapse
SysBoot only includes boot and system images, whereas FullStock includes all of the stock firmware images (bootloader, modem, boot, system)
When I make a SysBoot zip it's normally for deodexing and debloating the stock system and integrating Magisk.
I didnt make any SysBoot zips for this, but I did integrate Magisk into one of the FullStock zips so it will flash Magisk automatically after flashing the firmware.
weakNPCdotCom said:
SysBoot only includes boot and system images, whereas FullStock includes all of the stock firmware images (bootloader, modem, boot, system)
When I make a SysBoot zip it's normally for deodexing and debloating the stock system and integrating Magisk.
I didnt make any SysBoot zips for this, but I did integrate Magisk into one of the FullStock zips so it will flash Magisk automatically after flashing the firmware.
Click to expand...
Click to collapse
ok, but if I use the fullstock with magisk does that mean that I have to reflash twrp again using the runningnak3d root method?? again I'm sorry if it sounds dumb
aquinoer said:
ok, but if I use the fullstock with magisk does that mean that I have to reflash twrp again using the runningnak3d root method?? again I'm sorry if it sounds dumb
Click to expand...
Click to collapse
ahh I see what you mean. none of these packages touch your laf or recovery partitions unless you flash the stock laf zip. all that hard work will still be in tact.
just flash the zip with magisk and you're done
weakNPCdotCom said:
ahh I see what you mean. none of these packages touch your laf or recovery partitions unless you flash the stock laf zip. all that hard work will still be in tact.
just flash the zip with magisk and you're done
Click to expand...
Click to collapse
oh my god thank you I've been wait for the h8720e :laugh::laugh:
sadly it didnt work for me idk if it was the my phone or the zip files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
aquinoer said:
sadly it didn't work for me idk if it was my phone or the zip files
Click to expand...
Click to collapse
aquinoer said:
aquinoer said:
sadly it didn't work for me idk if it was my phone or the zip files
Click to expand...
Click to collapse
Interesting, I haven't flashed this latest yet myself just got done backing things up.
Is this from clean or dirty flash?
I'm running his 20d right now and was going to flash the full stock + magisk zip dirty caught this post just before doing it.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
Ken C said:
aquinoer said:
Interesting, I haven't flashed this latest yet myself just got done backing things up.
Is this from clean or dirty flash?
I'm running his 20d right now and was going to flash the full stock + magisk zip dirty caught this post just before doing it.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
I did both just to see which one would work but at least I'm back to h8720D
Click to expand...
Click to collapse
I'm getting an "invalid entry size" message when I try to look in the zip file using es file explorer. It then behaves like your inside the file but I don't see anything. I haven't tried flashing yet. I have an idea what's up but don't know how it would be fixed or if I'm even correct. I haven't tried opening the zip on a pc yet.
@weakNPCdotCom
Not pushing or anything but if you could take a peek at it. Hopefully nothing major. I was looking at the message you sent me and your talk about the updater script. Maybe it's just that? I'm admittedly guessing here.
Sent from my LG-H872 using Tapatalk
Ken C said:
@weakNPCdotCom
Not pushing or anything but if you could take a peek at it. Hopefully nothing major. I was looking at the message you sent me and your talk about the updater script. Maybe it's just that? I'm admittedly guessing here.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
It sounds like the ZIP is corrupted. Might have happened during the upload. I'll check it out this morning
Either of you guys try the standard FullStock? it's the same you just have to manually flash magisk after flashing the ROM
weakNPCdotCom said:
It sounds like the ZIP is corrupted. Might have happened during the upload. I'll check it out this morning
Either of you guys try the standard FullStock? it's the same you just have to manually flash magisk after flashing the ROM
Click to expand...
Click to collapse
I haven't flashed a thing yet. I'll give it a try in a bit and get back to you. No stress man just figured I'd pass it on. Pulling down full stock now.
Update : still haven't flashed yet but straight full stock is giving me that same invalid size message. I'd give it a try but I'm fairly sure it would throw the same error.
Sent from my LG-H872 using Tapatalk
Ken C said:
I haven't flashed a thing yet. I'll give it a try in a bit and get back to you. No stress man just figured I'd pass it on. Pulling down full stock now.
Update : still haven't flashed yet but straight full stock is giving me that same invalid size message. I'd give it a try but I'm fairly sure it would throw the same error.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
So I tested the zip and it was fine, not corrupt at all. So if it was corrupted it would have been during the download.
aquinoer said:
I did both just to see which one would work but at least I'm back to h8720D
Click to expand...
Click to collapse
If you try again, can you send me the TWRP logs? There should be a button in TWRP to save the flash logs. I can't see anything wrong with the package.
you mean this????
aquinoer said:
you mean this????
Click to expand...
Click to collapse
No, that's not what i was looking for. But i was able to correct an issue in the zips and re-upload them.
However, they are gonna be pretty useless as 20f is now out and ill be working on that release now.
Ok so since we're bouncing around so much between threads. (I'm using Tapatalk and only get those first few words or the thread title) lol almost comical. Anywho... And as always no stress I'm just laughing right now. Saw lg dropped 20g for the 870. So I think we can say they've upped their game at least when it comes to security updates?
Like I said it's such a shame that there isn't some way to just add the updates. Somebody got 20f to root using the tried and true method overnight or looks like.
Just thinking out loud here. But, if we had some way to revert the device to register to the update as a valid device. (thinking all the laf & recovey stuff would need to be stock.) Would that or something in not thinking of keep it from updating? I get if it sees magisk it'll probably act up. I'm just wondering is all.
Remember multirom? So have one straight stock, one rooted, then if it's possible (I realize this is easier said than done) push the root stuff over to the straight stock using some python or some such script to remove and replace files that would be necessary to keep root but have the update also.
Totally 3am or so thinking, but just popped in my mind and couldn't help sharing the thought since we were just talking about it.
Sent from my LG-H872 using Tapatalk
@Ken C
I have some news kinda. I'm creating a utility that will build FullStock and Bootloader zips from the extracted kdz files. that will make the process much faster and if it works well I might even share it.
Help me guys so i have my phone rooted via patched boot.img provided by Magisk but then decided to grab my stock boot.img to patch it again so i can update to v22.0 then i restart my device to access for fastboot and everything went blackscreen(i can't even see anything literally) luckily for me i memorize the key command to access fastboot so i flashed my stock boot.img , recovery.img and vendor.img but now my phone won't start
This thing shows up
https://imgur.com/a/fVDp06e
yes it's provably stupid to flash stock boot.img , recovery.img and vendor.img but i panic everything went all black even the BLU logo is black (no backlight phone)
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Oliie23 said:
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Click to expand...
Click to collapse
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
ineedroot69 said:
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
Click to expand...
Click to collapse
If I'm thinking correctly you won't lose data. Just dirtyflash it and it should work fine
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ineedroot69 said:
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
Click to expand...
Click to collapse
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Oliie23 said:
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Click to expand...
Click to collapse
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
ahh it fixed now my mother won't kill me
ineedroot69 said:
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
Click to expand...
Click to collapse
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Oliie23 said:
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Click to expand...
Click to collapse
look like completely factory default the bloatware are back
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
ahaha this Magisk update v22.0 is bonker
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
Let me know how it goes, please
ineedroot69 said:
look like completely factory default the bloatware are back
Click to expand...
Click to collapse
Are your apps all gone? It's basically like clean flash, right?
Oliie23 said:
Let me know how it goes, please
Click to expand...
Click to collapse
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Sebi673 said:
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Click to expand...
Click to collapse
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Oliie23 said:
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Click to expand...
Click to collapse
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
[updatee] screens attached
Sebi673 said:
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
Click to expand...
Click to collapse
Mine won't go into TWRP from the Fastboot unfortunately. It just stays there. I've managed to get TWRP to launch from ADB but I'm not sure if I should just flash the ROM that way. Should I?
[duplicate]
Disclaimer: NOT RESPONSIBLE FOR ANY BRICKED DEVICES
YOUR DEVICE MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS TO WORK
My first tutorial, gonna keep this short and sweet
1. Go to settings > About Phone > check your version number (eg 10.5.9 for mine)
2. Go to this thread and download the global zip with the corresponding number https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
3. Use payload dumper to extract the payload.bin file in the zip (you don't have to extract the whole thing, I killed mine when I got my boot.img file)
4. Install Magisk on your device and patch the just extracted boot.img
5. Copy patched boot.img to your computer
6. Reboot into bootloader, run this command and NOTHING ELSE
fastboot boot <location of patched boot.img>
7. Now your device should be booted into a rooted state and if your wifi or cellular doesn't work, have no fear. This is only temporary and we need root for the next few steps
8. Install Partitions Backup https://www.apkmirror.com/apk/wanam/partitions-backup/partitions-backup-2-3-0-release/
9. Use that to dump boot.img from both slots to your device
10. Use Magisk to patch both boot.img files just dumped from Partitions Backup
11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!
Leave a thanks if this helped you, this is for folks like me who couldn't find a backup of their OS build on the internet and needed a temp way to root their carrier devices
I'm going to try this now. Thank you for the idea!
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
Unfortunately, I can't even get into EDL mode. So this brick might be permanent. I'm asking for help from the community here: https://forum.xda-developers.com/t/nord-n100-edl-mode-dead-gone.4341305/
bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
luridphantom said:
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
Click to expand...
Click to collapse
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
bouyakasha said:
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
Click to expand...
Click to collapse
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
bouyakasha said:
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
Click to expand...
Click to collapse
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
luridphantom said:
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
Click to expand...
Click to collapse
Oh, thank you! That makes sense. I will try to UN-Tar it
I used Zarchiver to unarchive the TAR into boot.img for both, and this all worked! Thanks so much. Awesome guide.
@onlycash You should try this!
luridphantom said:
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
Click to expand...
Click to collapse
I tried several times and it's not working for me.
Everything appears to be fine till I try to "fastboot boot patched.img".
I'm trying to do this on an Metro N100 which is on 11.0.1BE82CF
I downloaded the global: 11.0.1: OnePlusN100Oxygen_14.O.21_GLO_0210_2107241056 MD5: a895312987628f21d0232d44575d0742
I extracted the payload and dumped the boot.img
I patched it in Magisk
I successfully "fastboot boot" that patched file but then it just hangs at the at the Metro boot screen.
I waited a minute or two but it didn't move past that screen, should I have waited longer?
In any event, I could hold down the power key and reboot into the unrooted stock 11.01 without issue.
Does anyone have an idea what I'm doing wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
onlycash said:
I tried several times and it's not working for me.
Click to expand...
Click to collapse
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
thomaskmaagaard said:
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
Click to expand...
Click to collapse
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
onlycash said:
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
Click to expand...
Click to collapse
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
luridphantom said:
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
Click to expand...
Click to collapse
I posted a good deal on the TWRP thread. I can fastboot the TWRP on my phone but I can't see any files only folder tree, even with my SD card I don't see any files either with TWRP.
I should add I'm running TWRP on a Metro N100 which is both SIM and bootloader unlocked. Also I didn't flash the TWRP I only fastbooted it, could that be the problem?
I really would rather flash the zip and root that way if I could get the TWRP to work.
I'm unsure what "disable dm-verity by flashing an empty vbmeta image" means in my case. What does this do?
Again I'm truly grateful for any help, thank you.
bouyakasha said:
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
Click to expand...
Click to collapse
Just to be clear I have a Metro N100 BE2015 running 11.0.1BE82CF.
With that being said, did you only get root when you went back to 10.5.8?
Are you rooted now on 11 and if so how did you get there?
Did you brick and go back to 10 then root 10 and update to 11 and keep root? How did you patch the img file after going to 11?
Any help and info would be much appreciated.
.
@onlycash I have constructed a small/random theory with no real basis. Could your problems be related to OOS 11? It sounds as dumb to me as it probably does to you, but I'm getting a nagging sensation that folks with success on your model aren't running the new update.
Just a weird hunch with no proper research, but I find it weird that you have these "unique" problems so I'm just spitting random junk at this point.