Database Info

[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.

[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
Click to expand...
Click to collapse
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!
Click to expand...
Click to collapse
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?

How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip

FrostedFluke said:
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
Click to expand...
Click to collapse
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.

El Daddy said:
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
aooga said:
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
Click to expand...
Click to collapse
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905

FrostedFluke said:
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.

FrostedFluke said:
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Yep, that is the correct command. I would recommend using the most recent SU.zip as well.

aooga said:
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
Click to expand...
Click to collapse
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?

FrostedFluke said:
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
Click to expand...
Click to collapse
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).

aooga said:
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
Click to expand...
Click to collapse
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"

FrostedFluke said:
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
Click to expand...
Click to collapse
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip

El Daddy said:
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
Click to expand...
Click to collapse
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)

FrostedFluke said:
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
Click to expand...
Click to collapse
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.

El Daddy said:
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
Click to expand...
Click to collapse
I get this on my command prompt: "error: closed"

FrostedFluke said:
I get this on my command prompt: "error: closed"
Click to expand...
Click to collapse
run the command: adb usb
Then try sideloading

El Daddy said:
run the command: adb usb
Then try sideloading
Click to expand...
Click to collapse
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?

FrostedFluke said:
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
Click to expand...
Click to collapse
yes

El Daddy said:
yes
Click to expand...
Click to collapse
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?

FrostedFluke said:
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
Click to expand...
Click to collapse
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.

El Daddy said:
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
Click to expand...
Click to collapse
Yup! it's rooted :victory:

FrostedFluke said:
Yup! it's rooted :victory:
Click to expand...
Click to collapse
Congrats!

[Q][D2303] How to root with unlocked bootloader?

Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!

Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V2.49 BETA and RICDefeat & remove KingRoot apps.

Lothgar said:
Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!
Click to expand...
Click to collapse
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Enycz11 said:
Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V.249 BETA and RICDefeat & remove KingRoot apps.
Click to expand...
Click to collapse
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...

linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Thanks! Trying right now!

linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.

Lothgar said:
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.
Click to expand...
Click to collapse
But you have to do a fastboot flash recovery recovery.img . Did you do that ?

linuxct said:
But you have to do a fastboot flash recovery recovery.img . Did you do that ?
Click to expand...
Click to collapse
Yep.

Lothgar said:
Yep.
Click to expand...
Click to collapse
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...

linuxct said:
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...
Click to expand...
Click to collapse
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
EDIT: Reflashed now only if i try to enter recovery the lines shows up!

Lothgar said:
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
Click to expand...
Click to collapse
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.

linuxct said:
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.
Click to expand...
Click to collapse
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.

Lothgar said:
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.
Click to expand...
Click to collapse
Maybe is a screen driver problem, but on a D2303?? For me it's working

linuxct said:
Maybe is a screen driver problem, but on a D2303?? For me it's working
Click to expand...
Click to collapse
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?

Lothgar said:
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?
Click to expand...
Click to collapse
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.

linuxct said:
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.
Click to expand...
Click to collapse
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:

Lothgar said:
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:
Click to expand...
Click to collapse
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...

linuxct said:
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...
Click to expand...
Click to collapse
CM recovery. If i downgrade the kernel the adb doesn't start! And yes is enabled in the settings.
EDIT: Solved trying now for the locked bootloader method!

Installed philz recovery with locked bootloader method but i cant flash omnirom! (status 7)

Can Nokia 3 root

Hello guys i have Nokia 3 and i want to root it can i root it without any problems and after root can I recieve updates and am able to install it successfully?

I need help
I unlocked the bootloader, Thanks to the_laser, but... I can´t install any recovery, I´ve looking many options, and I can´t
Can yo help me, giving me the link here or by private message.
I need to root my nokia 3 ta-1028 please.
Thanks a lot

xdrucsix said:
I unlocked the bootloader, Thanks to the_laser, but... I can´t install any recovery, I´ve looking many options, and I can´t
Can yo help me, giving me the link here or by private message.
I need to root my nokia 3 ta-1028 please.
Thanks a lot
Click to expand...
Click to collapse
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.

SkaboXD said:
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.
Click to expand...
Click to collapse
Oh, Ok I can see, I have to wait :/

is there any difference between ta-1028 and ta-1032 in TWRP view ?
it is easy to try just boot into recovery - "fastboot boot <recovery.img>"

the_laser said:
is there any difference between ta-1028 and ta-1032 in TWRP view ?
it is easy to try just boot into recovery - fastboot boot recovery <recovery.img>
Click to expand...
Click to collapse
i know that ta-1032 is for EU dual sim, ta-1028 is american single sim version but i think that there is no difference in hardware. he can try that command to see is that recovery works @xdrucsix
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
then you will see does it boot or not. twrp will disappear completely after you exit twrp.

I did every step that you say, nothing happened :/

something should definitely happen
at least show all fastboot.exe output during your tries

SkaboXD said:
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.
Click to expand...
Click to collapse
The twrp dint even work for 1032..

Mithra siva said:
The twrp dint even work for 1032..
Click to expand...
Click to collapse
it worked for me and others, which method you tried?

SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
The method you have mentioned only.. it was showing writing ..'recovery' failed..
---------- Post added at 12:53 PM ---------- Previous post was at 12:49 PM ----------
SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
The method you have mentioned only..
It was showing ." Writing 'recovery'...failed (remote size too large)... Please help

SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
Bro say something

Mithra siva said:
Bro say something
Click to expand...
Click to collapse
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img

SkaboXD said:
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
Click to expand...
Click to collapse
How to type location..I have kept it in root folder of (E)
---------- Post added at 05:16 AM ---------- Previous post was at 05:00 AM ----------
SkaboXD said:
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
Click to expand...
Click to collapse
Can you please send again...how to install twrp..with twrp link indetail.. I go for a last try..

Mithra siva said:
How to type location..I have kept it in root folder of (E)
---------- Post added at 05:16 AM ---------- Previous post was at 05:00 AM ----------
Can you please send again...how to install twrp..with twrp link indetail.. I go for a last try..
Click to expand...
Click to collapse
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
to type platform-tools location, type this:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
reboot to recovery
adb reboot recovery
then reboot to bootloader (fastboot) by pressing volume keys.
to flash recovery type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.

SkaboXD said:
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
to type platform-tools location, type this:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
reboot to recovery
adb reboot recovery
then reboot to bootloader (fastboot) by pressing volume keys.
to flash recovery type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.
Click to expand...
Click to collapse
Thanks man it's done..
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
Mithra siva said:
Thanks man it's done..
Click to expand...
Click to collapse
Now can I relock my Bootloader with root..if i can please instruct me
And again thanks a lot

Mithra siva said:
Thanks man it's done..
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
Now can I relock my Bootloader with root..if i can please instruct me
And again thanks a lot
Click to expand...
Click to collapse
no, you can't have locked bootloader and root, after locking bootloader you need to reflash .nb0 file with OST because locking bootloader don't just remove data, it removes whole ROM.

SkaboXD said:
no, you can't have locked bootloader and root, after locking bootloader you need to reflash .nb0 file with OST because locking bootloader don't just remove data, it removes whole ROM.
Click to expand...
Click to collapse
I can't able to remove the system apps even after root..I used system app remover (root) ..
Help

Mithra siva said:
I can't able to remove the system apps even after root..I used system app remover (root) ..
Help
Click to expand...
Click to collapse
did you rebooted after uninstalling system apps?

SkaboXD said:
did you rebooted after uninstalling system apps?
Click to expand...
Click to collapse
It was showing uninstalling failed

Alcatel 9001D Pixi 4 6 4g [msm8909] - Root, Recovery, Rom -

Hi, I finally managed to port TWRP recovery, which boot on 9001D. This allows to do the permanent root, to modify the stock rom and possibly to install other roms.
Recovery is still unstable, I need help to make it stable!
Then, now Available for 9001D:
- TWRP
- Root
- Modded Stock Rom

drmad said:
Hi, I finally managed to port TWRP recovery, which boot on 9001D. This allows to do the permanent root, to modify the stock rom and possibly to install other roms.
Recovery is still unstable, I need help to make it stable!
Then, now Available for 9001D:
- TWRP
- Root
- Modded Stock Rom
Click to expand...
Click to collapse
*Could you provide download of your port*
I would like to try to boot it without flashing it
Thank you sir !

KevMetal said:
*Could you provide download of your port*
I would like to try to boot it without flashing it
Thank you sir !
Click to expand...
Click to collapse
hi, to try twrp you have to flash it,
to do this you must have the rooted device or you have to flash the firmware that I will give you

drmad said:
hi, to try twrp you have to flash it,
to do this you must have the rooted device or you have to flash the firmware that I will give you
Click to expand...
Click to collapse
Mmmm , better to use command
"fastboot boot recovery recovery.img"
If
"fastboot flash recovery recovery.img"
Can be dangerous if recovery isn't built from source and the port is bad ...if port works using "boot" command maybe try to flash it ...
But I found another recovery to use as a base for my port , thanks !
*Also my BOOTLOADER IS LOCKED BY VODAFONE*
So anyways my port will be useless...

KevMetal said:
Mmmm , better to use command
"fastboot boot recovery recovery.img"
If
"fastboot flash recovery recovery.img"
Can be dangerous if recovery isn't built from source and the port is bad ...if port works using "boot" command maybe try to flash it ...
But I found another recovery to use as a base for my port , thanks !
*Also my BOOTLOADER IS LOCKED BY VODAFONE*
So anyways my port will be useless...
Click to expand...
Click to collapse
Those commands does not work for me, let me know if they work for you

drmad said:
Those commands does not work for me, let me know if they work for you
Click to expand...
Click to collapse
Yes , they have worked for me in the past but on other phones. Your bootloader must be unlocked and remember to use the command without the quotation marks ..""
*You should also rename your recovery to recovery.img AND VERY IMPORTANTLY put it in your adb or fastboot tools root folder.
Then if you installed adb and run a command window BUT FROM INSIDE the tools folder where the recovery image is and run the following commands one by one it will work if your drivers are installed and your bootloader is unlocked
adb devices
*Return a serial number for your phone in window
adb reboot bootloader
*phone should boot into bootloader
fastboot oem unlock
*will unlock your bootloader if you press volume up
fastboot boot recovery recovery.img
*The recovery should boot ( if it boots and you can make a backup to SD card successful ly
fastboot flash recovery recovery.img

KevMetal said:
Yes , they have worked for me in the past but on other phones. Your bootloader must be unlocked and remember to use the command without the quotation marks ..""
*You should also rename your recovery to recovery.img AND VERY IMPORTANTLY put it in your adb or fastboot tools root folder.
Then if you installed adb and run a command window BUT FROM INSIDE the tools folder where the recovery image is and run the following commands one by one it will work if your drivers are installed and your bootloader is unlocked
adb devices
*Return a serial number for your phone in window
adb reboot bootloader
*phone should boot into bootloader
fastboot oem unlock
*will unlock your bootloader if you press volume up
fastboot boot recovery recovery.img
*The recovery should boot ( if it boots and you can make a backup to SD card successful ly
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
On other phones it works, on the 9001d it does not work ...
But I found an alternative method

drmad said:
On other phones it works, on the 9001d it does not work ...
But I found an alternative method
Click to expand...
Click to collapse
Which method ?

KevMetal said:
Which method ?
Click to expand...
Click to collapse
Insert the twrp into a complete firmware from flash with qfil

drmad said:
Insert the twrp into a complete firmware from flash with qfil
Click to expand...
Click to collapse
Mmm very interesting okay thanks for advice

KevMetal said:
Mmm very interesting okay thanks for advice
Click to expand...
Click to collapse
Let me know if your port of twrp is stable

Hi. Please help to install TWRP on 9001D or to get root

scarabbey said:
Hi. Please help to install TWRP on 9001D or to get root
Click to expand...
Click to collapse
You need to use a patched boot.img to get root on this device as there is no fastboot. There are guides online on how to use magisk to patch the boot.img and then flash that to your phone. That will give you permanent root after which you will be able to install twrp. If you flash twro without root or a patched boot it will remove it each time you boot up.

true_devil said:
You need to use a patched boot.img to get root on this device as there is no fastboot. There are guides online on how to use magisk to patch the boot.img and then flash that to your phone. That will give you permanent root after which you will be able to install twrp. If you flash twro without root or a patched boot it will remove it each time you boot up.
Click to expand...
Click to collapse
I'm able to install twrp with original boot.img and after I can get permanent root

drmad said:
Hi, I finally managed to port TWRP recovery, which boot on 9001D. This allows to do the permanent root, to modify the stock rom and possibly to install other roms.
Recovery is still unstable, I need help to make it stable!
Then, now Available for 9001D:
- TWRP
- Root
- Modded Stock Rom
Click to expand...
Click to collapse
Can you share the port here so others can try it?

Hola amigo tenes flash de 9001D luego de reparar F4 con Sigmakey quedo Brick

Greetings
I have this model
How do I flash/root/TWRP this phone? The instructions above are not very clear?
please help!

[HOW TO] Install + Root ULM Pie (21d and 20e) and add working TWRP /w stock!

Hey guys,
VIDEO TUTORIAL:
https://youtu.be/ylBSZk7EqcA o
Someone written a better tutorial or you can follow my video tutorial
https://docs.google.com/document/d/1fdeO9jmm8ewwRX_G0MaGHsVfIVtxgh0yRK0-Yypcl_E/edit?usp=drivesdk
Credits:
@loonycgb2 for the bootloader tutorial
@jsergan[/MENTION] for the root tutorial
@Zackptg5p and whoever helped him for this DM Verity and forceencrypt disabler

Where "21ULMD Kdz file"
I can't found it on web

Ahmed Ismael said:
Where "21ULMD Kdz file"
I can't found it on web
Click to expand...
Click to collapse
https://lg-firmwares.com/downloads-file/20303/G710ULM21d_00_NAO_US_OP_0711
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
Before I flash it I wanted to ask if you notice any performance difference between 11g (oreo) and 21d. Is it just as fast?

ninjamirage said:
https://lg-firmwares.com/downloads-file/20303/G710ULM21d_00_NAO_US_OP_0711
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
Before I flash it I wanted to ask if you notice any performance difference between 11g (oreo) and 21d. Is it just as fast?
Click to expand...
Click to collapse
I Cross-Flash G710ULM20 GFI
Performance increases

I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.

ninjamirage said:
I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.
Click to expand...
Click to collapse
Nah it works you can update it via twrp or direct install it.

Awesomeslayerg said:
Nah it works you can update it via twrp or direct install it.
Click to expand...
Click to collapse
Thanks. I don't think I need fastboot yet. I am not sure how to erase the LAF partition.

ninjamirage said:
I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.
Click to expand...
Click to collapse
ninjamirage said:
Thanks. I don't think I need fastboot yet. I am not sure how to erase the LAF partition.
Click to expand...
Click to collapse
To zero it out use adb shell or the termrnial app then su
The do:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
To get into download mode:
Theres two ways#
1. Get into fastboot mode and set current slot to b
Code:
fastboot --set-active=b
then reboot and hold the up button while its connectrc to your pc and you should be able to get into download mode
2. Boot into twrp, then tap reboot in the menu and on the bottom it should say slot a or b and select b. Then reboot. Dont worry about not being able to mount.

Awesomeslayerg said:
To zero it out use adb shell or the termrnial app then su
The do:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
To get into download mode:
Theres two ways#
1. Get into fastboot mode and set current slot to b
Code:
fastboot --set-active=b
then reboot and hold the up button while its connectrc to your pc and you should be able to get into download mode
2. Boot into twrp, then tap reboot in the menu and on the bottom it should say slot a or b and select b. Then reboot. Dont worry about not being able to mount.
Click to expand...
Click to collapse
Is that for installing a custom rom?
Then do you need to do this?
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.img

ninjamirage said:
Is that for installing a custom rom?
Then do you need to do this?
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.img
Click to expand...
Click to collapse
Yes

This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!

CyborgSG said:
This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!
Click to expand...
Click to collapse
One person got it to work. I

Can you show the full details of your method, as I'm tried patch both img and it's work, but when I boot to download mode and connect to PC and open LGUp, it's always show unknown model, try flash the img it in fastboot many time, it's always happen like that

CyborgSG said:
This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!
Click to expand...
Click to collapse
CyborgSG said:
Can you show the full details of your method, as I'm tried patch both img and it's work, but when I boot to download mode and connect to PC and open LGUp, it's always show unknown model
Click to expand...
Click to collapse
First don't call a tutorial trash cause you didn't do it properly and you didn't even detail the problem properly. . Second, make sure you're still on 11g firmware or go back to 11g firmware via download mode of you're not and then flash the abl partition from the unlocked bootloader tutorial if you havent used that abl. Then fastboot flash rooted 11g boot_a and boot_b file then reboot to firmware and make sure it boots all the way up and restart your PC then try going into download mode again if it works go into fastboot flash the 21ulmd booted rooted image both a and b then immediately restart to download mod

I'm on g710ulm11g and I'm rooted, updated the magisk to 20.1, now do I have to boot to fastboot and boot the twrp20ulmrooted img to boot_a and boot_b and then boot to download mode?

CyborgSG said:
I'm on g710ulm11g and I'm rooted, updated the magisk to 20.1, now do I have to boot to fastboot and boot the twrp20ulmrooted img to boot_a and boot_b and then boot to download mode?
Click to expand...
Click to collapse
Noo. Fastboot flash 21ulmrooted to both a and b then reboot to download mode.

question: I am rooted with magisk and on ULM21d. I have extracted the image file and renamed it "twrp21ulmdroot.img" and put this file on my internal storage /sdcard. When I run the command dd if=/sdcard/twrp21ulmdroot.img of=/dev/block/bootdevice/by-name/boot_a in adb shell (as root #) it keeps giving me a response of dd: /sdcard/twrp21ulmdroot.img: No such file or directory. The file is actually there. Any ideas?

way2aware said:
question: I am rooted with magisk and on ULM21d. I have extracted the image file and renamed it "twrp21ulmdroot.img" and put this file on my internal storage /sdcard. When I run the command dd if=/sdcard/twrp21ulmdroot.img of=/dev/block/bootdevice/by-name/boot_a in adb shell (as root #) it keeps giving me a response of dd: /sdcard/twrp21ulmdroot.img: No such file or directory. The file is actually there. Any ideas?
Click to expand...
Click to collapse
Are you sure you didn't name it twrp21ulmd.img.img? Or reboot the device.. Make sure it's where the Download, pictures etc.. folders are.

Awesomeslayerg said:
Noo. Fastboot flash 21ulmrooted to both a and b then reboot to download mode.
Click to expand...
Click to collapse
When I'm try to boot the twrp20ulmrooted to boot a and boot b, bcoz I want to root on g710ulm20e, then in command it's show up: cannot boot a boot.img *and* ramdisk, so what exactly command I have to use in adb and fastboot?

Awesomeslayerg said:
Are you sure you didn't name it twrp21ulmd.img.img? Or reboot the device.. Make sure it's where the Download, pictures etc.. folders are.
Click to expand...
Click to collapse
sir, your tutorial worked perfectly for me- I now for the first time since owning this phone have a custom recovery. Thank you for your help :good:
Edit: my problem earlier was that the image file was not installing to my internal storage in the right place for whatever reason... /sdcard was not available when searching my int storage. So I dropped the file into 'Download', then used Advanced tools pro file manager to grab it and paste it into the parent directory. At that point the shell commands worked