Develop Bugs

Can't get into recovery after using flashtool

I've got a rooted phone w/ an unlocked bootloader.
I've installed TWRP using ADB.
When I try to get into recovery (by using the physical buttons while booting) nothing happens. When I try to get into recovery via ADB, I get "no devices found"
What am I doing wrong?
Some background:
I flashed KK 4.4 using Flashtool.
Then I successfully installed and accessed TWRP. I tried and failed to install a custom ROM (AICP), but couldn't get it to sideload.
At that point, my device had no OS, so I re-flashed KK4.4, hoping that I could get the ADB sideload to work if I started from the beginning.
But now I'm back at the beginning, and I can't even get into recovery.
When I flash TWRP via fastboot, it successfully writes. But I can't boot into recovery.
Please help!

Disregard. I was able to access TWRP after I flashed the boot.img that came in the original platform tools.
It goes without saying that once I flash that boot.img, I'm unable to get into KK 4.4. I am, however, able to get back to TWRP, where hopefully I'll be able to flash a ROM.
Once again, however, I'm not able to flash AICP. It fails every single time.

mulcahey said:
Disregard. I was able to access TWRP after I flashed the boot.img that came in the original platform tools.
It goes without saying that once I flash that boot.img, I'm unable to get into KK 4.4. I am, however, able to get back to TWRP, where hopefully I'll be able to flash a ROM.
Once again, however, I'm not able to flash AICP. It fails every single time.
Click to expand...
Click to collapse
You can try to pull boot img from aicp and flash it in two, then try to flash the rom, but not sure. You may have to flash LP first, just use a prf. Also, if you use Emma to update bootloader, (if you didn't already), then you can use real recovery, (twrp 3+), and it should work.

mulcahey said:
Disregard. I was able to access TWRP after I flashed the boot.img that came in the original platform tools.
It goes without saying that once I flash that boot.img, I'm unable to get into KK 4.4. I am, however, able to get back to TWRP, where hopefully I'll be able to flash a ROM.
Once again, however, I'm not able to flash AICP. It fails every single time.
Click to expand...
Click to collapse
I just finished process myself, just to test, and works fine-
1. Download Emma
2. Download twrp3
3. Download Kingroot
4. Download Rashr
Plug phone into computer in flash mode after starting Emma, and you'll see option to flash newest fw. After flashing, restart and install Kingroot. After rooting, use Rashr to flash twrp3. Then power off, and hold power and volume down to enter recovery.

I just finished process myself, just to test, and works fine-
1. Download Emma
2. Download twrp3
3. Download Kingroot
4. Download Rashr
Click to expand...
Click to collapse
THANK YOU! I'm not sure what prf or Emma are, but I'll find out on my own.
Is there any way to do this that doesn't involve KingRoot? The whole "sends your info to a Chinese IP" aspect of KingRoot creeps me out.

mulcahey said:
Is there any way to do this that doesn't involve KingRoot? The whole "sends your info to a Chinese IP" aspect of KingRoot creeps me out.
Click to expand...
Click to collapse
two ways:
1) after you install the rom using EMMA connect the phone in fastboot mode and flash Advanced Kernel 18.1. it comes with its own twrp recovery. then boot to recovery and flash SuperSU zip.
2) after you install the rom using EMMA connect the phone in fastboot mode and flash TWRP recovery, then boot to recovery and flash SuperSU zip.

karamancho said:
two ways:
1) after you install the rom using EMMA connect the phone in fastboot mode and flash Advanced Kernel 18.1. it comes with its own twrp recovery. then boot to recovery and flash SuperSU zip.
2) after you install the rom using EMMA connect the phone in fastboot mode and flash TWRP recovery, then boot to recovery and flash SuperSU zip.
Click to expand...
Click to collapse
Thank you!!! Eager to try these.
Is SuperSU zip secure? Do we know that it's not Chinese malware?

Can't get into recovery -z1c (amami)
I unlocked bootloader, have installed TWRP 3, then LineageOS through TWRP. But now i can't access recovery (twrp).
-Phone powers up
-pink light
-immediately i press volume up (volume down doesn't do anything)
-orange light shows for a second
-phone restarts normally
----------------------
So how can i access twrp recovery mode?

a-ha said:
I unlocked bootloader, have installed TWRP 3, then LineageOS through TWRP. But now i can't access recovery (twrp).
-Phone powers up
-pink light
-immediately i press volume up (volume down doesn't do anything)
-orange light shows for a second
-phone restarts normally
----------------------
So how can i access twrp recovery mode?
Click to expand...
Click to collapse
Haven't tried Lineage yet, but with CM, they had their own recovery which had to be overwritten after flash. Boot up, install Rashr, flash TWRP IMG with Rashr, then try again.
Also, real recovery is a good idea, if you don't have it yet. You need to flash stock with Sony Emma tool, then you have ta update, with real recovery capability.

mulcahey said:
Thank you!!! Eager to try these.
Is SuperSU zip secure? Do we know that it's not Chinese malware?
Click to expand...
Click to collapse
It's fine.

a-ha said:
I unlocked bootloader, have installed TWRP 3, then LineageOS through TWRP.
Click to expand...
Click to collapse
Has Lineage been released for Amami? I don't see it on the downloads page.

mulcahey said:
Has Lineage been released for Amami? I don't see it on the downloads page.
Click to expand...
Click to collapse
Unofficial - https://forum.xda-developers.com/sony-xperia-z1-compact/general/z1c-nougat-roms-t3460868

Rooting problem open beta 17

After Root open beta 17 stook on boot logo
Any solution

Amar5373 said:
After Root open beta 17 stook on boot logo
Any solution
Click to expand...
Click to collapse
Well is it really too hard to explain your problem in proper sentences? So you wanted to root your phone. What did you use? Magisk? SuperSU? Which version? I can't help you if you don't provide information..

I have the same problem. Neither SuperSu nor Magisk works.

persa2011 said:
I have the same problem. Neither SuperSu nor Magisk works.
Click to expand...
Click to collapse
supersu not working please help

Use SuperSu 2.82

2.82 works fine for me! Many thanks!

My Steps For Stock OB17 Zip *Same Steps for Magisk V12 Or SuperSu V2.82*
Code:
Flash latest TWRP From Blu_Spark V35 Or Stock TWRP
Format Data Reboot TWRP
Wipe All
Copy [URL="http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_17/"]OB17[/URL], [URL="https://forum.xda-developers.com/devdb/project/dl/?id=25000"]TWRP V35[/URL], [URL="http://www.supersu.com/download"]SuperSU V2.82[/URL] To Internal Storage
Flash OB17
Select Flash IMG, Install TWRP Reboot TWRP (So Stock Rom Doesn't Replace With Stock Recovery)
Wipe Cache/Dalvik
Flash SuperSU
Reboot = Profit
*Optional*
Take A Backup Of Rooted Boot IMG (If You Flash A Custom Kernel And Run Into Issues You Can Restore Rooted Boot IMG With Ease)
Flash Kernel Of Choice (Beware Because Of No Source Code And Kernel Changes Might Be Some Issues With Custom Kernels)

TO root latest beta an stable version you can follow this guide:

Rooting the Pixel XL with Magisk

So I just got a Pixel XL and have unlocked the bootloader, but now I'm trying to root and I'm very confused. I have a few questions:
Should I be using TWRP RC1 or RC2? I'm currently on 3.1.0-0RC2 but I hear RC2 has weird issues with restoring/making Nandroids but I can't tell if that refers to the RC2 of a different build or what... The other issue is the TWRP page for Marlin only lists RC2 for v3.1.0, there is no RC1
Is it possible to get MagiskSU running and installed without a custom kernel - if possible I'd like to stick to the stock kernel
Can I use Magisk Modules or am I stuck in Core Only mode?
Any help would be appreciated, thanks!

CarteNoir said:
So I just got a Pixel XL and have unlocked the bootloader, but now I'm trying to root and I'm very confused. I have a few questions:
Should I be using TWRP RC1 or RC2? I'm currently on 3.1.0-0RC2 but I hear RC2 has weird issues with restoring/making Nandroids but I can't tell if that refers to the RC2 of a different build or what... The other issue is the TWRP page for Marlin only lists RC2 for v3.1.0, there is no RC1
Is it possible to get MagiskSU running and installed without a custom kernel - if possible I'd like to stick to the stock kernel
Can I use Magisk Modules or am I stuck in Core Only mode?
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
Go here and search for Installation Instructions: [Unofficial] Google Pixel family support by goodwin_c
Go here for the latest Magisk/Magisk Manager Pixel/Pixel XL files.

Homeboy76 said:
Go here and search for Installation Instructions: [Unofficial] Google Pixel family support by goodwin_c
Go here for the latest Magisk/Magisk Manager Pixel/Pixel XL files.
Click to expand...
Click to collapse
Hi there, I went to that thread but it has no instructions, just discussion. I had a look for instructions but could only find other threads. I followed what they said (fastboot boot twrp.img => flash twrp.zip => reboot recovery => flash magisk.zip => flash twrp.zip => reboot system) but the root doesn't work (despite all recovery logs saying everything worked properly), and I get this when I open MagiskManager:
{
"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"
}

CarteNoir said:
Hi there, I went to that thread but it has no instructions, just discussion. I had a look for instructions but could only find other threads. I followed what they said (fastboot boot twrp.img => flash twrp.zip => reboot recovery => flash magisk.zip => flash twrp.zip => reboot system) but the root doesn't work (despite all recovery logs saying everything worked properly), and I get this when I open MagiskManager:
Click to expand...
Click to collapse
have you done a 2nd reboot? sometimes that's the charm...

Captain Hindsight said:
have you done a 2nd reboot? sometimes that's the charm...
Click to expand...
Click to collapse
I've done multiple reboots sadly. Still nothing.

@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?

tdct12 said:
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
Click to expand...
Click to collapse
I think that might be the case but I don't know how to stop it. I tried flashing Magisk after TWRP but still no dice. I tried flashing the ElementalX kernel as per the guides and it finally works, but I really don't want to have to use a custom kernel, I'd much rather just stick to the stock kernel. Is there any way I can get this working with the stock kernel?

tdct12 said:
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
Click to expand...
Click to collapse
TWRP does not flash over magisk, never has and isn't now.
---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------
CarteNoir said:
I think that might be the case but I don't know how to stop it. I tried flashing Magisk after TWRP but still no dice. I tried flashing the ElementalX kernel as per the guides and it finally works, but I really don't want to have to use a custom kernel, I'd much rather just stick to the stock kernel. Is there any way I can get this working with the stock kernel?
Click to expand...
Click to collapse
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.

pcriz said:
TWRP does not flash over magisk, never has and isn't now.
---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
Click to expand...
Click to collapse

pcriz said:
TWRP does not flash over magisk, never has and isn't now.
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
Click to expand...
Click to collapse
Hey there, took a look at that patched stock kernel but unfortunately couldn't get it to work. I tried following the standard installation steps up until the point where you're supposed to flash the ElementalX kernel, at which point I booted back to bootloader and used fastboot flash kernel to flash the patched stock kernel file, then I returned to recovery to flash TWRP again as per the flow of the instructions, however that didn't work and Magisk still shows as not installed/no root.
I then tried flashing stock images/uninstalling Magisk, then following the standard instructions all the way through, installing the ElementalX kernel along the way. I then rebooted, confirmed Magisk installed and was working correctly, then went back into the bootloader and used fastboot flash kernel to flash the patched stock kernel file. However again on rebooting to system I found that Magisk said no root/not installed.
Is ElementalX doing something other than removing the androidboot.verifiedbootstate flag in regards to making Magisk work? Or is there perhaps anywhere where I can find a TWRP flashable package version of the patched stock kernel?

CarteNoir said:
Hey there, took a look at that patched stock kernel but unfortunately couldn't get it to work. I tried following the standard installation steps up until the point where you're supposed to flash the ElementalX kernel, at which point I booted back to bootloader and used fastboot flash kernel to flash the patched stock kernel file, then I returned to recovery to flash TWRP again as per the flow of the instructions, however that didn't work and Magisk still shows as not installed/no root.
I then tried flashing stock images/uninstalling Magisk, then following the standard instructions all the way through, installing the ElementalX kernel along the way. I then rebooted, confirmed Magisk installed and was working correctly, then went back into the bootloader and used fastboot flash kernel to flash the patched stock kernel file. However again on rebooting to system I found that Magisk said no root/not installed.
Is ElementalX doing something other than removing the androidboot.verifiedbootstate flag in regards to making Magisk work? Or is there perhaps anywhere where I can find a TWRP flashable package version of the patched stock kernel?
Click to expand...
Click to collapse
So I think you would want to fastboot the stock boot.IMG. flash the kernel, then turn around and flash twrp, reboot, install magisk.
If Elemental is doing something more to make this work I don't know what it is, but essentially every custom kernel or kernel that comes packaged with a custom rom does the same thing.

[RECOVERY][P905][UNOFFICIAL] twrp 3.2.2-0

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This recovery was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
Instructions
Install zip using an existing custom recovery
Work
Everything works as in the original version + otg and mtp.
Links
2. 20180708: 3.2.2-0 version:
from recovery: https://drive.google.com/file/d/1v5KlNFjaQqpyml7TotbleIvsGhITyYFk/view?usp=sharing
from odin: https://drive.google.com/file/d/1RMqFJ7uXVwttxu5dmYarQLcAi56g2seh/view?usp=sharing
1. 20171006: 3.1.1-0: https://drive.google.com/file/d/0B-6nm7Jks0W5MHlwTUxlUDFiOWc/view?usp=sharing
Sources
TWRP: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Device: twrp branch: https://github.com/Valera1978/android_device_samsung_viennalte

i m on official twrp and i m not able to install magisk (image cant get compressed to size of 10mb boot, always 10.4)
will this inofficial twrp build help to get magisk installed

Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This frecovery was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
Instructions
Install zip using an existing custom recovery
Work
Everything works as in the original version + otg and mtp.
Links
1. 20171006: 3.1.1-0: https://drive.google.com/file/d/0B-6nm7Jks0W5MHlwTUxlUDFiOWc/view?usp=sharing
Sources
TWRP: https://github.com/omnirom/android_bootable_recovery
Kernel: https://github.com/Valera1978/android_kernel_samsung_lt03lte
Click to expand...
Click to collapse
For some reason this recovery causes facebook and facebook messenger apps to continuously crash over and over, other than that so far everything is great!

@Valera1978
Amazing! Thanks for sharing with us!

@Valera1978
Sooooooo cool! :good:
....and.....while not using F*ckbook, I don't care about crashing messengers and so on. :evel:

I installed this recovery and everything is ok except when trying to restore modem
I backed up my system to install official firmware to test some stuff
Then i reinstalled the recovery and tried to restore my backup but it was failing when restoring the modem
I deselected the modem and restored everything else and all ok

Same here. Failing restoring the modem.

The latest official Version doesn't work either (crash):
twrp-3.2.1-0-viennaltexx
The latest working version for my p905 is:
twrp-3.0.2-0-viennaltexx
https://twrp.me/samsung/samsunggalaxynotepro122qcom.html

i flashed twrp recovery sucessfully thru odin..but when i tried to boot to recovery it's still stock firmware recovery not twrp recovery please help

The bootloader is unlooked?
Could you start into the bootloader?
If yes, you can flash the recovery via fastboot

after five times I have managed
My big problem now is how do I activate HDMi?
have a MHL cable micro usb to HDMi when I plug it in nothing happens

Thanks a lot for this TWRP 3.2.2-0 it works nice with SM-P905, and Valera1978 Android 9 Pie ROM.
Easy install, Valera1978 TWRP 3.2.2-0 img from Official TWRP 3.0.2-0 viennalte.
Format f2fs, And latest magisk

risant said:
i flashed twrp recovery sucessfully thru odin..but when i tried to boot to recovery it's still stock firmware recovery not twrp recovery please help
Click to expand...
Click to collapse
Successfully TWRP flash thru Odin, observe the progress in Odin left bottom corner and prepare for this; "directly" when flash finished "force recovery start" (volume up home and startbutton until recovery starts)
Not fast enough" stock recovery autorestore ! Doitagain.

About bootloader (4.4.2 KK)
Hi,
I've just got a SM-P905 on 4.4.2 kitkat (stock). I'd like to flash one of your ROM (probably the LOS 17.1) and this recovery first.
Should I just flash it through Odin or do I need to unlock the bootloader? In that case, could you please drive me to a tutorial? I've searched a lot on this forum on howto unlock the SM-P905 bootloader (or just if it comes -the 4.4.2 version at least- with an unlocked one already) but I haven't found anything on it.
Thanks in advance

SYS2048 said:
Hi,
Should I just flash it through Odin or do I need to unlock the bootloader?
Click to expand...
Click to collapse
Flash TWRP only, through Odin.
Then flash ROM, GApps, and optional Magisk, through TWRP.
Magisk needed for root-apps, or to hide root.
(flash bootloader and modem not needed, only sometime later, if your modem are to old, and SIM not working)

KjellO said:
Flash TWRP only, through Odin.
Then flash ROM, GApps, and optional Magisk, through TWRP.
Magisk needed for root-apps, or to hide root.
(flash bootloader and modem not needed, only sometime later, if your modem are to old, and SIM not working)
Click to expand...
Click to collapse
Done a couple of days after my post. Forgot to report. Then flashed LOS 17, gapps (pico) and Magisk. Everything's ok.
Thanks for your answer.
Anyway, now it can be said that the P905 with stock 4.4.2 KK has the bootloader unlocked.

Hi, I've downloaded twrp-3.2.2.0-viennaltexx.img.tar and flashed by Odin, but twrp doesn't installed. In Developer settings I have not OEM unlock option.
what can I do?

uzzi78 said:
Hi, I've downloaded twrp-3.2.2.0-viennaltexx.img.tar and flashed by Odin, but twrp doesn't installed. In Developer settings I have not OEM unlock option.
what can I do?
Click to expand...
Click to collapse
What is your actual stock firmware on it?
You can try latest official .tar and then work your way up to this.

bmwdroid said:
What is your actual stock firmware on it?
You can try latest official .tar and then work your way up to this.
Click to expand...
Click to collapse
Now I've Android 5.0.2
LRX22G.P905XXSABQB1

@uzzi78 so you have the latest bootloader installed.
That's good.
Btw afaik/remember there is no unlock option.
Try other TWRPs as a. m.

Trouble rooting with magisk

I Have difficulties rooting my Z1 compact (amami).
My goal is to have stock rom, rooted with Magisk.
Steps I took:
1. Unlocked the bootloader (manufacturer way)
2. Flashed latest stock rom
3. Booted, installed Magisk manager, downloaded magisk.zip and enabled USB debugging
4. Flashed TWRP through ADB
5. Booted into TWRP, tried to install the zip, I get an error “unsupported image format”
6. If I reboot after faliure, I can’t get into stock rom anymore (just black backlit screen), so I have to reflash stock rom again.
I have tried different versions of TWRP, Magisk, and tried rezipping magisk.zip.
Any help is greatly appreciated.

Same issue here. Will let you know how I solve it.
Edit: My solution, might not be 100% what you were after, but this is good for me:
Reflash stock rom 236 LP with EMMA
Flash kernel v18.1 from here https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060 (fastboot flash boot boot.img)
Enter rom and adb reboot recovery (power + voldown didn't work)
Flash Supersu zip
Flash debloater zip from here https://forum.xda-developers.com/cr...p-debloat-lp-690-correct-functioning-t3076161
This nets me a debloated stock 5.1.1 install with root and busybox, all I need. I could never get fastboot flash recovery to boot any rom after flashing from recovery, so after a lot of struggle I'm happy this way.
If Magisk is a must, I would try the method described here https://forum.xda-developers.com/so...m-unrooted-t3682932/post76105039#post76105039