Database Develop

[ROOT][MM][NO UNLOCKING REQUIRED][ZE550KL] How to root ZE550KL on latest marshmallow?

If you tried rooting you ZE550KL then you must tried unlocking your device using official unlocker tool and you may faced force close. So here is how to root you asus ZE550KL without unlocking bootloader..
Prerequisite:
Download Latest TWRP from twrp.me Download
Download latest SuperSu Binary Download
Install Adb drivers and proper setup adb and fastboot. If you dont know how search on Google.
Lil Presence of mind
Lets start...
1- Connect your phone and type these command.
Code:
adb devices
and if it shows your device then issue this command after that
Code:
adb reboot bootloader
your device will reboot in bootloader.
2- Go to the directory where you placed downloaded twrp.img. Open command prompt here (shift + right click).
3- Flash the downloaded recovery
Code:
fastboot flash recovery twrp.img
4- When it said "finished" and there is no error. Then type this and press volume - (down) before screen lit up.
Code:
fastboot reboot
5- If you did correctly then you will see the TWRP logo.
6- If not let device boot and when it finished boot type these commands
Code:
adb reboot recovery
7- When twrp boots first step is to make a full backup of all.
8- Then copy Update-SuperSu-*-*.zip to your sd card or internal memory via MTP (available when twrp boots n phone connected with pc). Flash it.
9- If twrp ask for su binary update say no. and reboot
10- Boom you're rooted!!
Screenshots: (Unfortunately I cant record so i am atleast giving ss)
{
"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"
}
Video to get idea if this works.. ( I will surely upload a good video very soon!)
https://www.youtube.com/watch?v=B7iYTGKmb-g
Helpful Links:
StockBoot.img(Lollipop)- Because if you messed up you need to flash this and then have to download stock lollipop firmware and then sideload firmware from stockrecovery to get you phone working

Yeah, I updated yesterday my ZE551KL to Android M and as I didn't like it (some minimal changes) I chose to install the CM13.
But the unlocker didn't work. Ocurred the problem described in this post.
I will try this method later and post my result.
Update: the root worked!
Question: can I flash the CM rom without backing up the system? Because I got no space available for it in my microSD. What are the risks?

LOL
This is not a place to fool people.
Method works. Apologies to OP

xactor said:
3- Flash the downloaded recovery
Click to expand...
Click to collapse
I'm pretty new at this. Doesn't flashing require an unlocked bootloader? Most of what I read seems to indicate so, but maybe not on some devices? Can someone clarify?

moo.marc said:
I'm pretty new at this. Doesn't flashing require an unlocked bootloader? Most of what I read seems to indicate so, but maybe not on some devices? Can someone clarify?
Click to expand...
Click to collapse
Flashing any non-stock .img or zip requires unlocked bootloader. This guide will never work. It seems this guy made two accounts, one for writing the guide and one for posting that it worked. The OP is just trying to fool people, or may be he himself got fooled by somebody and he posted that guide here. Mods, This thread should be deleted.
Edit : Sorry for updating too late. This method works on locked bootloader. The img files are provided by a genius shakalaka. They are patched to match Asus signed img files. Thanks for writing this useful thread

Also confirmed working on ZE-551KL on my phone and my wife's phone!
Thank You!
Please most definitely follow this step: 4- When it said "finished" and there is no error. Then type this and press volume - (down) before screen lit up.
Code:
fastboot reboot
Definitely do the "Press volume down button" right after you hit (Enter)
This was sticking point because I didn't read carefully....

Hi, just try your method it work. My is ZE550KL 6.0.1
Aloso work on build : 21.40.1220.1708 too.
flash recovery with twrp version twrp-3.0.2-3-Z00L.img
and flash with UPDATE-SuperSU-v2.65-20151226141550.zip
BTW first time SuperSU installed but cannot work. So I try to flash again and got it work correctly.
New user cannot post outside link pls add manual open my attachment.
imgur.com/a/Ue6a8

Hello sir can u make avideo iam urgent for root please

No idea how this works
I have no idea how, but it worked! I (mostly) agree with sziraqui that flashing a recovery image with the device locked shouldn't work: I tried it before and the device would not load the bootloader after flashing, forcing me to re-flash the stock bootloader.
As mentioned by the OP, after flashing the marshmallow firmware (UL-Z00L-WW-21.40.1220.1708-user.zip) the unlock app crashed when unlocking. After that, I tried to flash TWRP and to my surprise it DID work! I also managed to flash supersu and test it with TitaniumBackup.
Since I would be skeptic myself, I'm attaching a picture that show's twrp and my terminal showing the that the bootloader reports as being locked.

I'm using marshmallow on my ZenFone 2 laser user_21.40.1220.1877 the latest stock firmware I'm not able to unlock it when I enter this command "fastboot boot ze550kltwrp.img in command prompt keeping my device into fastboot mode it shows error "you need to unlock your device to use this command"
How to unlock it plzz help
---------- Post added at 04:12 AM ---------- Previous post was at 03:31 AM ----------
How to unlock ZenFone 2 laser running on marshmallow latest build?
Plz suggest

ryt i have too same issue
How to unlock bootloader

abhinavze550kl said:
I'm using marshmallow on my ZenFone 2 laser user_21.40.1220.1877 the latest stock firmware I'm not able to unlock it when I enter this command "fastboot boot ze550kltwrp.img in command prompt keeping my device into fastboot mode it shows error "you need to unlock your device to use this command"
How to unlock it plzz help
---------- Post added at 04:12 AM ---------- Previous post was at 03:31 AM ----------
How to unlock ZenFone 2 laser running on marshmallow latest build?
Plz suggest
Click to expand...
Click to collapse
Just try to flash it .. fastboot boot didn't work for me too

sziraqui said:
LOL
This is not a place to fool people.
Click to expand...
Click to collapse
Definitely not..
Watch the video n clear me !
I agree flashing images requires a unlock bootloader. But sure it did flashed on an unlocked one. Mind helping me out why it worked bro??

sziraqui said:
Flashing any non-stock .img or zip requires unlocked bootloader. This guide will never work. It seems this guy made two accounts, one for writing the guide and one for posting that it worked. The OP is just trying to fool people, or may be he himself got fooled by somebody and he posted that guide here. Mods, This thread should be deleted.
Click to expand...
Click to collapse
Not everyone is free as you're.. sorry just kidding :laugh:

I tried it on my zenfone and it works fine...thank you
Hi,
i was searching for this since lots of time and i found ur post that without unlocking bootloader we can
flash a recovery img and also root it. I tried it and it is working fine in my ze550kl marshmallow.
I just want to install a cm 14.1 rom. It is possible? Pl answer.
Thank u again.

I always get this help!
decompressing ramdisk
failure, abort

deepakt6699 said:
Hi,
i was searching for this since lots of time and i found ur post that without unlocking bootloader we can
flash a recovery img and also root it. I tried it and it is working fine in my ze550kl marshmallow.
I just want to install a cm 14.1 rom. It is possible? Pl answer.
Thank u again.
Click to expand...
Click to collapse
See this thread..
http://forum.xda-developers.com/zenfone-2-laser/development/rom-resurrection-remix-n-t3509698/page48

it works with ZE551KL in stock 6.0.1 marshmallow follow the steps . very important the volume key down to start the recovery after reboot and then install the super su. this is the easiest method that i've found ..thanks

yas i cant unlock my asus zenf2 laser ze550kl I'm using marshmallow on my ZenFone 2 laser user_21.40.1220.1877 the latest stock firmware plez help
tnx xda its work but sum probs

Not working on asusz00ld on mm
Now worked

[Recovery] [YB1-X90L] TWRP

managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment recovery_twrp.zip
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
{
"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"
}
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.

---reserved---

before you ask...
yes, of course, i have already tried to flash supersu, but unfortunately I had no luck so far. The script always aborts because it fails patching sepolicy of boot.img.
so if anyone knows a solution for this, feel free to help!
edit:
found another way to root, look here

Amazing! I never thought yb would have twrp. I've been looking for a way to install gapps since I bought yb. After my final I will definitely have a try.

Was it stable when you flashed some zip?

AndyVerne said:
Was it stable when you flashed some zip?
Click to expand...
Click to collapse
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)

danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
All right, I wil try to install supersu after take my final exam ,too .
I believe there will be a way to solve it .
(oh ,god , the root seems to have sloved , nice job!)

danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.

AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
Code:
fastboot flashing lock
if you are not sure, try to search xda for more information about relocking.

danjac said:
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
if you are not sure, try to search xda for more information about relocking.
Click to expand...
Click to collapse
Oh, I gave it up... Thanks

Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
danjac said:
managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment 3994659
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
View attachment 3994696
View attachment 3994697
View attachment 3994698
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.
Click to expand...
Click to collapse
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse

hajkan said:
Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
Click to expand...
Click to collapse
to your first question:
1. well, here we are not talking about backing up your user data but your rom (stock rom so to speak). if anything goes wrong you can always go back to stock.
2. if you want to peform ota update you can't do it with modified system (ota will fail), so normally you must go back to stock, update, root again
to your second question:
it's just a warning that your bootloader is unlocked, nothing more. it shows with every boot and after 5secs just boots normally.
you can easily find out about the advantages and disadvantages of an unlocked bootloader e.g. here on xda.

I can't thank you enough for this. I live in China and was only able to buy the Chinese version of the Yoga Book, which doesn't come with Google Services installed. However, using this TWRP recovery I was able to flash Google Services (and get root) which makes my Yoga Book so much more useful! Thanks so much!

Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated

zamzenos said:
Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated
Click to expand...
Click to collapse
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?

danjac said:
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?
Click to expand...
Click to collapse
Left it overnight and tried again today. It's OK this time. I fiddled with settings, mainly to deselect the read-only system option. Each stage of this process has been pretty frustrating (I'm used to hacking sammy devices - this is first and last time with a lenny). Stuck now trying to get root - it will probably take until tomorrow! btw, ver is YB1 X90F (Europe/UK).
But thanks for taking the trouble to reply. And thanks for giving us the opportunity to hack the YB.

Worked on the wifi version too.
You may not be a developer but you are a pretty smart guy to be able to figure this out on your own, my hat is off to you. I rooted my wifi version of Yoga Book using your instruction and the only notable issue I ran into in the process was that i had to install new Android usb drivers in Windows to get the reboot-bootloader command to work, other than that little hiccup it worked like a charm. One other issue I ran into that was of my own making was that Titanium backup encouraged me to upgrade super user which led to a soft brick, thankfully I'd backed my book up and was able to restore it.
Thanks for taking the time to share this with us because rooting made this device a much better experience.

hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...

kakit78 said:
hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...
Click to expand...
Click to collapse
If you just want to install gapps, there is no need to root.
1. download gapps from opengapps.org. select x86_64 6.0 version. select nano or micro version if only want google play to be worked.
2. put the gapps zip file into your root of your YB.
3. just follow the instructions of this post to boot into TWRP
4. In TWRP, select install zip file from SD, then select the gapps to install
5. after finish, reboot to the system.
6. Done!
---------- Post added at 08:48 AM ---------- Previous post was at 08:44 AM ----------
The problem is that I fail to OTA updated after booting into TWRP and install gapps. Anyone can helps?

@danjac Hi, did you keep the boot to bios option in the reboot menu?

Request Stock boot.img to flash in boot_A boot_B

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!

help rooting device with oreo 8.1

Hello,
I have this phone (infinix note 4 x572) running oreo 8.1 , build number :X572-H5312CE-O-180531V117
I wish to root it but after a while of searching i'm overly confused and frustrated..
can you please guide me through rooting it?
thanks alot

btw, does local update help in any way ?
{
"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"
}

All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.

Didgeridoohan said:
All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.
Click to expand...
Click to collapse
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?

and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?

yazansayed said:
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?
Click to expand...
Click to collapse
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
yazansayed said:
and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?
Click to expand...
Click to collapse
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...

Didgeridoohan said:
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
thanks alot for the quick responses, i will try it and reply as fast as possible

okay, i downloaded the twrp recovery image for Note 4, flashed it using Fastboot method successfully,
the problem is when i try to boot into the twrp recovery mode, i tried holding the power menu+ vol.down buttons, it sends me into a black screen with "factory mode" upwards in yellow, no button is working.
i then tried
Code:
adb reboot recovery
the phone reboots and says "No command" under a red triangle.
i then tried to flash the twrp img using sp flash tools, and flashed it successfully but the same errors occur, i can't seem to be able to boot into recovery mode.

i looked up for a solution for the "no command" problem, here's one:
I faced the same problem with nexus 6p. It works when you root immediately after flashing the TWRP. Keep the superSU file in the storage. Get into bootloader. Flash TWRP via fastboot. Without restarting anything, just press volume up/down buttons while in the bootloader to select recovery. TWRP will open. Flash the SuperSU.zip. Then restart the system. Next time, if you open recovery, you won't get the "no command". If you don't flash SuperSU and you try to open recovery later, you will get the "No command".
Click to expand...
Click to collapse
what i understood is that i shouldn't reboot my device using "fastboot reboot" , he says i should get into recovery mode directly without restarting, idk how to do that since there are no option for it on the screen, i just have
Code:
=> FASTBOOT mode...
on the screen !

Didgeridoohan said:
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
unfortunately i never used the sp flash tool before, so i tried flashing a stock rom but the device is now dead with "dram failed" error, i'll try fixing this first

It's tricky trying to help with a device you don't have...
Did you manage to boot to recovery? Usually you use the volume buttons to select the options and then the power button to confirm. You could also just use the fastboot boot option command I wrote earlier. It'll boot straight into TWRP.
There are a few threads for your device around, so if you need help specific to your device, that's the place to go...

everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot

the twrp from the post you provided is for an older firmware, this is why i couldn't get into recovery after i flashed the provided twrp img,, there is no available twrp for the oreo version of the firmware, but i requested one from twrp builder project,, thanks alot, i've learnt alot in the last 24 hours

yazansayed said:
everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot
Click to expand...
Click to collapse
could you upload the boot.img pls (the stock and the patched if possible )

Root any BL UNLOCKED T-Mobile/Metro OnePlus Nord with Magisk and temp root

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.