I'm using SM-950F, Android 9, and i was trying to root my phone. But whenever i going to downloading mode and trying to fash TWRP but its says only official released binaries are allowed to be flashed samsung (recovery)
Note: OEM was Toggled on.
hainguyenthao said:
Why u don't paste any screenshot for device in download mode or even write any info it could help us to help you
Click to expand...
Click to collapse
Could you help me with editing the CP file in a Hex editor?
The phone is Samsung N960N. It already has OEM unlock but the KG state is always prenormal.
MrTanz said:
I'm using SM-950F, Android 9, and i was trying to root my phone. But whenever i going to downloading mode and trying to fash TWRP but its says only official released binaries are allowed to be flashed samsung
Note: OEM was Toggled on.
Click to expand...
Click to collapse
On the download mode screen, what does it say next to the KG State? Checking or prenormal?
stonedpsycho said:
On the download mode screen, what does it say next to the KG State? Checking or prenormal?
Click to expand...
Click to collapse
Its checking
MrTanz said:
Its checking
Click to expand...
Click to collapse
It should have flashed ok. What TWRP did you use?
You need to flash stock firmware to be able to get rid of the "only official binary" message, then try rooting again.
stonedpsycho said:
It should have flashed ok. What TWRP did you use?
You need to flash stock firmware to be able to get rid of the "only official binary" message, then try rooting again.
Click to expand...
Click to collapse
I used TWRP 3.1.1.0, 3.2.1.2 & 3.3.1.0
MrTanz said:
I used TWRP 3.1.1.0, 3.2.1.2 & 3.3.1.0
Click to expand...
Click to collapse
Try using the latest TWRP which is 3.4.0.0
https://eu.dl.twrp.me/greatlte/
stonedpsycho said:
Try using the latest TWRP which is 3.4.0.0
https://eu.dl.twrp.me/greatlte/
Click to expand...
Click to collapse
I flashed, still didn’t work
MrTanz said:
I flashed, still didn’t work
Click to expand...
Click to collapse
I don't have a clue then.
Is it possible your phone is made of different variants?
MrTanz said:
I'm using SM-950F, Android 9, and i was trying to root my phone. But whenever i going to downloading mode and trying to fash TWRP but its says only official released binaries are allowed to be flashed samsung (recovery)
Note: OEM was Toggled on.
Click to expand...
Click to collapse
Are you trying to root on stock rom or custom rom??
cheemak said:
Are you trying to root on stock rom or custom rom??
Click to expand...
Click to collapse
On stock rom
stonedpsycho said:
I don't have a clue then.
Is it possible your phone is made of different variants?
Click to expand...
Click to collapse
I'm trying to flash on stock rom! And using global variant
facing same problem ... unable to root and flash custom rom
Have you disable auto reboot in options setting in odin before flashing twrp?
MrTanz said:
On stock rom
Click to expand...
Click to collapse
Can you see success sign in Odin when you flash TWRP?? Can you able to enter TWRP after flashing with odin??
cheemak said:
Can you see success sign in Odin when you flash TWRP?? Can you able to enter TWRP after flashing with odin??
Click to expand...
Click to collapse
The problem is here, when I'm going to flash twrp by odin its says fail and in phone its says only official binarys can be use.
MrTanz said:
The problem is here, when I'm going to flash twrp by odin its says fail and in phone its says only official binarys can be use.
Click to expand...
Click to collapse
That means that the bootloader on your device is locked.
iceepyon said:
That means that the bootloader on your device is locked.
Click to expand...
Click to collapse
How?? My OEM is on from Developer Setting.
iceepyon said:
That means that the bootloader on your device is locked.
Click to expand...
Click to collapse
See
{
"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"
}
MrTanz said:
The problem is here, when I'm going to flash twrp by odin its says fail and in phone its says only official binarys can be use.
Click to expand...
Click to collapse
This case you have to reflash stock firmware and wait 7 days or more for kg state to become normal in download mode.
Then try flashing TWRP again.
There are threads for the kg state issue.
Read this thread.
https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984
Related
{
"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"
}
I need solution !!! Failed !!!!!!
albelushi7 said:
View attachment 4033280
I need solution !!! Failed !!!!!!
Click to expand...
Click to collapse
Need more information about your failed
k4fari said:
Need more information about your failed
Click to expand...
Click to collapse
When I need install twrb >failed
..
I need twrb because I have Android 7 official
And when install 38% after that failed by vol+&-&pwer
Now and before days try install twrb but this problem *
My English bad
albelushi7 said:
When I need install twrb >failed
..
I need twrb because I have Android 7 official
And when install 38% after that failed by vol+&-&pwer
Now and before days try install twrb but this problem *
My English bad
Click to expand...
Click to collapse
Tell me few things
Have you unlock bootloader?
Have you successfully insatll TWRP Recovery?
Have you rooted successfully?
If you have done these 3 things then you should have to flash the Stock recovery, only then you can be able to update / flash the Nougat or other Stock firmwares.
k4fari said:
Tell me few things
Have you unlock bootloader?
Have you successfully insatll TWRP Recovery?
Have you rooted successfully?
If you have done these 3 things then you should have to flash the Stock recovery, only then you can be able to update / flash the Nougat or other Stock firmwares.
Click to expand...
Click to collapse
No ,
only now install twrb recovery ! I
need only this
Look photo first post
k4fari said:
Tell me few things
Have you unlock bootloader?
Have you successfully insatll TWRP Recovery?
Have you rooted successfully?
If you have done these 3 things then you should have to flash the Stock recovery, only then you can be able to update / flash the Nougat or other Stock firmwares.
Click to expand...
Click to collapse
...
/Remote command not allowed /
This problem when install twrb recovery
albelushi7 said:
...
/Remote command not allowed /
This problem when install twrb recovery
Click to expand...
Click to collapse
Try the stock recovery and tell me is it also failed or flashed
k4fari said:
Try the stock recovery and tell me is it also failed or flashed
Click to expand...
Click to collapse
I tried the same problem
Sigh... You already open up a thread about this, you should just continue on that one instead of opening up another one. Also if you dont want to brick or damage your phone. Please please please do some research before hand.
Firstly, you have not unlocked your bootloader, chances are, you probably haven enable OEM unlock and USB debugging and thirdly, if you looked through the guide section of this forum, you will see that everything you need to know is there.
To make your life simpler, go to the below link, download the tool and watch the video.
https://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
albelushi7 said:
I tried the same problem
Click to expand...
Click to collapse
You can also try this as well to make your fone alive
1) Download your fone firmware
2) Use huawei firmware extractor to extract there files
boot.img
recovery.img
system.img
3) Copy these files to your fastboot command folder
4) Now use these commands in the same pattern
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Hope it will revive your fone.
Z-Blade said:
Sigh... You already open up a thread about this, you should just continue on that one instead of opening up another one. Also if you dont want to brick or damage your phone. Please please please do some research before hand.
Firstly, you have not unlocked your bootloader, chances are, you probably haven enable OEM unlock and USB debugging and thirdly, if you looked through the guide section of this forum, you will see that everything you need to know is there.
To make your life simpler, go to the below link, download the tool and watch the video.
https://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
Click to expand...
Click to collapse
Do twrb needs to open unlocked bootloader? ,,, Or not, because all what I've done and I saw the subject in the link you attached, and used that tool, and now I'll watch the video probably get p solution, thank you I have searched long hah
k4fari said:
You can also try this as well to make your fone alive
1) Download your fone firmware
2) Use huawei firmware extractor to extract there files
boot.img
recovery.img
system.img
3) Copy these files to your fastboot command folder
4) Now use these commands in the same pattern
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Hope it will revive your fone.
Click to expand...
Click to collapse
My phone good , and now use , but install twrb recovery high , thank you for helping
Hi everyone. Last week I tried to root (successfully) my Tab S2 to make it work with Samsung Gear Smartwatch. Using an application I changed the "model-name" of my tablet from SM-T719 to SM-N910F (Note 4) to make it recognizable by Gear.
My father accidentally disabled "OEM unlock" and then, when I've rebooted it, it was written "Custom binary blocked by FRP lock".
I tried to install the stock ROM (different versions of it) using Odin, but it didn't work (it have always stuck at "system.img.ext4")
Besides, I cannot install TWRP Recovery because when I try to install it via Odin the phone says "SECURE CHECK FAIL: recovery" and "Custom Binary (recovery) Blocked by FRP Lock"
My recovery mode doesn't let me install anything ("Update from external storage is disabled")
So, I'm not able to install the OS. Can anyone help me?
Are you under warranty?
No, I'm not because of having rooted it. The repair center says that I have to change the Motherboard. I'm not sure of this, is it possible?
Dondruma12 said:
No, I'm not because of having rooted it. The repair center says that I have to change the Motherboard. I'm not sure of this, is it possible?
Click to expand...
Click to collapse
Post a screen shot of odin.
It seems like you also rooted. FRP is reporting a modified binary, either custom recovery or modified boot image.
Either way its not necessary to flash the system image to remove the FRP lock.
However it will fail dm-verity checks if you've modified the system partition.
Boot and recovery can be flashed without the system image.
Do that first and report back.
{
"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"
}
"Boot and recovery can be flashed without the system image."
How can I flash boot and recovery without system img?
P.S. My recovery mode doesn't work, debug and fastboot neither. I'll send a screenshot of Odin
Dondruma12 said:
"Boot and recovery can be flashed without the system image."
How can I flash boot and recovery without system img?
P.S. My recovery mode doesn't work, debug and fastboot neither. I'll send a screenshot of Odin
Click to expand...
Click to collapse
Which firmware build number are/were you running?
ashyx said:
which firmware build number are/were you running?
Click to expand...
Click to collapse
I don't know how to find the number
https://ibb.co/e0731m
I've flashed both recovery and boot using Toolkit, it seems to be just like before
Dondruma12 said:
I don't know how to find the number
https://ibb.co/e0731m
I've flashed both recovery and boot using Toolkit, it seems to be just like before
Click to expand...
Click to collapse
You are no longer FRP locked according to your screen shot. Binary is now official.
However as said previously system is modified and likely won't boot due to dmverity.
You should be able to boot to stock recovery.
Can you post a screen shot of odin when trying to flash the stock firmware.
https://ibb.co/cXGAWm
Dondruma12 said:
https://ibb.co/cXGAWm
Click to expand...
Click to collapse
It's failing because you are using the wrong ODIN version.
3.07 doesn't support meta data.
https://drive.google.com/uc?export=download&id=0B6pQCizpnzoEdEtVeW42dGVGcXc
Well i am having a similiar Problem.
I am running Lineage 14.1 with TWRP and Magisk/Root.
Yesterday i flashed the latest Lineage nightly, reboot worked without problems.
This morning i started my S2 and i also got the message "Custom Binary blocked by FRP - Secure Fail: Kernel".
I only can get into Download mode. Trying to go into recovery mode i get the message again but with... Secure Fail: Recovery.
Any solution without flashing the Stock Rom?
Thomas_BA said:
Well i am having a similiar Problem.
I am running Leonage 14.1 with TWRP and Magisk.
Yesterday i flashed the latest Leonage nightly, reboot worked without problems.
This morning i started my S2 and i also got the message "Custom Binary blocked by FRP - Secure Fail: Kernel".
I only can get into Download mode. Trying to go into recovery mode i get the message again but with... Secure Fail: Recovery.
Any solution without flashing the Stock Rom?
Click to expand...
Click to collapse
You will at least have to flash stock boot and recovery images.
ashyx said:
You will at least have to flash stock boot and recovery images.
Click to expand...
Click to collapse
I feared so
Lets see where i can find stock boot and recovery..if not i have to download the whole ROM. Slow!!
Any idea where this problem came from? Havent changed anything in the developer settings (OEM, etc)
https://ibb.co/edBxSR
It always stops there, I let it continue for one hour but nothing happened.
I don't know, is it possible that "FRP Lock: On", "Warranty Void: 0x1 (4)" or "Qualcomm secureboot: enable (CSB)" are responsible of this?
Dondruma12 said:
https://ibb.co/edBxSR
It always stops there, I let it continue for one hour but nothing happened.
I don't know, is it possible that "FRP Lock: On", "Warranty Void: 0x1 (4)" or "Qualcomm secureboot: enable (CSB)" are responsible of this?
Click to expand...
Click to collapse
Non of that will be the issue.
Have you tried a different firmware?
ashyx said:
Non of that will be the issue.
Have you tried a different firmware?
Click to expand...
Click to collapse
Yes I did, everyone does the same thing
Dondruma12 said:
Yes I did, everyone does the same thing
Click to expand...
Click to collapse
Are you using an original cable?
Don't use long USB cables either as these cause issues.
I've just tried with the original one, unfortunately nothing changed
Then I tried to flash TWRP recovery and this is what I got
https://ibb.co/cqNYK6
Dondruma12 said:
I've just tried with the original one, unfortunately nothing changed
Then I tried to flash TWRP recovery and this is what I got
https://ibb.co/cqNYK6
Click to expand...
Click to collapse
You can't flash a custom recovery or kernel while FRP is on.
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
ashyx said:
You can't flash a custom recovery or kernel while FRP is on.
Click to expand...
Click to collapse
I'd try flashing the stock firmware with repartition ticked.
ashyx said:
You can't flash a custom recovery or kernel while FRP is on.
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
I'd try flashing the stock firmware with repartition ticked.
Click to expand...
Click to collapse
This is what happens
https://ibb.co/hGOFGm
This is a custom recovery made by LR.Team and I translate the flash tool.
I don't have enough premission so I post it here.
This recovery can automatically decrypt /data partition.
I already tested it on my redmi 6.
Just follow the instruction in the flash tool after you decompress it.
!!UPDATE HERE!!
https://forum.xda-developers.com/redmi-6/development/share-3-3-0-twrp-redmi-6-custom-recovery-t3926225
{
"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"
}
Available in Simplified Chinese and English
Link:[url]https://drive.google.com/open?id=18pClwHMAQKNafMq_ng2C0kTlpH_1n-RU[/URL]
Source:[url]http://www.miui.com/thread-19005924-1-1.html[/URL]
Reserved
Thanks for this share. Can you give more details about your usage? Are you running MIUI and did you have to flash Disable DM-Verity? Did you have any difficulties getting this recovery running? E.g. black screen etc.
I had a look at the recovery-twrp flash tool.bat file. It seems to use the usual "fastboot.exe flash recovery" BUT it also flashes an additional file (fastboot.exe flash para misc.bin >NUL 2>NUL) and flashes misc.bin. Can you confirm what misc.bin is and where did you get this custom recovery?
This information would be helpful to everybody else
Yes, I'm running on MIUI 10 and it works perfectly fine for me. Unlike the official TWRP, you don't need to format data for this. So all of your applications and files will still stay in place.
For me, I just went into fastboot mode and use the tool to flash it. Nothing goes wrong.
Also, this recovery use a default password to unlock the /data partition. So you don't have to flash anything else to get this to work.
IDK what is that misc.bin tho
I already linked the source in the post.
seanho12345 said:
Yes, I'm running on MIUI 10 and it works perfectly fine for me. Unlike the official TWRP, you don't need to format data for this. So all of your applications and files will still stay in place.
For me, I just went into fastboot mode and use the tool to flash it. Nothing goes wrong.
Also, this recovery use a default password to unlock the /data partition. So you don't have to flash anything else to get this to work.
IDK what is that misc.bin tho
Click to expand...
Click to collapse
Thanks, I will flash this onto my Redmi 6 when it comes next week
Hi.
How long did it take to flash? 360 hours?
wencesbanger said:
Hi.
How long did it take to flash? 360 hours?
Click to expand...
Click to collapse
You mean unlock bootloader?
seanho12345 said:
You mean unlock bootloader?
Click to expand...
Click to collapse
Yes..
Sorry, my bad.
wencesbanger said:
Yes..
Sorry, my bad.
Click to expand...
Click to collapse
I believe you gotta wait for like 360 hours or something
Is it possible to have a complete translation ? Thanks
Have you tried to install magisk using this recovery?
ribou said:
Is it possible to have a complete translation ? Thanks
Click to expand...
Click to collapse
What do you mean a complete translation.
ZoneDev said:
Have you tried to install magisk using this recovery?
Click to expand...
Click to collapse
Yeah I do. But you'll need to reflash it after a few reboot.
seanho12345 said:
Yeah I do. But you'll need to reflash it after a few reboot.
Click to expand...
Click to collapse
Any ways for it to be flashed onced permanently?
ZoneDev said:
Any ways for it to be flashed onced permanently?
Click to expand...
Click to collapse
I don't think so.
seanho12345 said:
I don't think so.
Click to expand...
Click to collapse
I installed lazyflasher and the twrp recovery didnt got replaced
ZoneDev said:
I installed lazyflasher and the twrp recovery didnt got replaced
Click to expand...
Click to collapse
What do you mean. This twrp itself can decrypt data.
There's no need to flash lazyflasher.
seanho12345 said:
I don't think so.
Click to expand...
Click to collapse
Really? Are you trying to say that root is always temporary and after a few reboots we will always have to enter recovery to re-install Magisk? What about SuperSU?
Does anybody know the reason for this replacement? Maybe this will help us figure out how to prevent Magisk from being overwritten...
Thanks for this recovery.
But, at every boot I have this message “Android System there's an internal problem with your device.Contact your manufactirer for details.".
How to delete it.
It is possible to relock bootloader ?
Che0063 said:
Really? Are you trying to say that root is always temporary and after a few reboots we will always have to enter recovery to re-install Magisk? What about SuperSU?
Does anybody know the reason for this replacement? Maybe this will help us figure out how to prevent Magisk from being overwritten...
Click to expand...
Click to collapse
I Not 100% shure, but I think I'm loosing magisk root whenever I Update any systemapp..
Help me guys so i have my phone rooted via patched boot.img provided by Magisk but then decided to grab my stock boot.img to patch it again so i can update to v22.0 then i restart my device to access for fastboot and everything went blackscreen(i can't even see anything literally) luckily for me i memorize the key command to access fastboot so i flashed my stock boot.img , recovery.img and vendor.img but now my phone won't start
This thing shows up
https://imgur.com/a/fVDp06e
yes it's provably stupid to flash stock boot.img , recovery.img and vendor.img but i panic everything went all black even the BLU logo is black (no backlight phone)
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Oliie23 said:
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Click to expand...
Click to collapse
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
ineedroot69 said:
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
Click to expand...
Click to collapse
If I'm thinking correctly you won't lose data. Just dirtyflash it and it should work fine
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ineedroot69 said:
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
Click to expand...
Click to collapse
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Oliie23 said:
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Click to expand...
Click to collapse
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
ahh it fixed now my mother won't kill me
ineedroot69 said:
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
Click to expand...
Click to collapse
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Oliie23 said:
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Click to expand...
Click to collapse
look like completely factory default the bloatware are back
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
ahaha this Magisk update v22.0 is bonker
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
Let me know how it goes, please
ineedroot69 said:
look like completely factory default the bloatware are back
Click to expand...
Click to collapse
Are your apps all gone? It's basically like clean flash, right?
Oliie23 said:
Let me know how it goes, please
Click to expand...
Click to collapse
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Sebi673 said:
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Click to expand...
Click to collapse
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Oliie23 said:
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Click to expand...
Click to collapse
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
[updatee] screens attached
Sebi673 said:
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
Click to expand...
Click to collapse
Mine won't go into TWRP from the Fastboot unfortunately. It just stays there. I've managed to get TWRP to launch from ADB but I'm not sure if I should just flash the ROM that way. Should I?
[duplicate]
Hey peeps,
Its been about a 7-8 years since i last tinkered with an android phone so im totally out the loop.
My one plus 6t recently went up in flames due to the latest update and I had to wipe it.
I've been wanting to root my phone and potentially install an alternate android rom as i've lost all my confidence in one plus.
I've managed to unlock the bootloader but i'm stuck with twrp and magisk.
Everytime I run twrp in the boot loader I get a qualcomm crash dump, I was told this was due to my phone being one android 11.
Totally lost right now so i little direction would be totally appreciated.
Thanks.
You need flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/
iggyx2 said:
You need flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/
Click to expand...
Click to collapse
I'm running Pixel Experience A11. How do i root this ROM? Flashing them img's made my phone bootloop recovery?
Clarkiieh said:
I'm running Pixel Experience A11. How do i root this ROM? Flashing them img's made my phone bootloop recovery?
Click to expand...
Click to collapse
I'm not running custom rom on my OP6t or OP6 so I can't confirm what img works.
That being said, if you're running custom ROM on your OP6t try this one https://forum.xda-developers.com/t/...recovery-project-v3-1-0.4198277/post-85713789
iggyx2 said:
You need flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/
Click to expand...
Click to collapse
Thanks for the reply,
so in the guide I was following it says to 'fastboot boot (image file name).img' through adb in the bootloader would I do the same with the stable image you suggested?
abenfares said:
Hey peeps,
Its been about a 7-8 years since i last tinkered with an android phone so im totally out the loop.
My one plus 6t recently went up in flames due to the latest update and I had to wipe it.
I've been wanting to root my phone and potentially install an alternate android rom as i've lost all my confidence in one plus.
I've managed to unlock the bootloader but i'm stuck with twrp and magisk.
Everytime I run twrp in the boot loader I get a qualcomm crash dump, I was told this was due to my phone being one android 11.
Totally lost right now so i little direction would be totally appreciated.
Thanks.
Click to expand...
Click to collapse
Are you still stuck in Qualcomm crash dump?? Or what?
s.seila said:
Are you still stuck in Qualcomm crash dump?? Or what?
Click to expand...
Click to collapse
No I got out of that and it’s booting fine but I’m still trying to root my device
abenfares said:
No I got out of that and it’s booting fine but I’m still trying to root my device
Click to expand...
Click to collapse
Then try to flash magisk patched image.
Clarkiieh said:
I'm running Pixel Experience A11. How do i root this ROM? Flashing them img's made my phone bootloop recovery?
Click to expand...
Click to collapse
Flash the magisk zip through twrp.
s.seila said:
Flash the magisk zip through twrp.
Click to expand...
Click to collapse
so i would just do fastboot flash stable.img ( that being the file the other user suggested?
abenfares said:
so i would just do fastboot flash stable.img ( that being the file the other user suggested?
Click to expand...
Click to collapse
Did you already flash Stable.img and are you on Oxygen 11 or Oxygen 11.1.1.1.1?
iggyx2 said:
Did you already flash Stable.img and are you on Oxygen 11 or Oxygen 11.1.1.1.1?
Click to expand...
Click to collapse
I haven't flashed anything i'm still on stock, i literally just unlocked the bootloader.
abenfares said:
I haven't flashed anything i'm still on stock, i literally just unlocked the bootloader.
Click to expand...
Click to collapse
I see.. Don't flash Stable.img if you're on Oxygen 11.1.1.1 you would need 11.1.1.1 magisk patched img as @s.seila said but if you're on Oxygen 11 then use Stable.img.
iggyx2 said:
I see.. Don't flash Stable.img if you're on Oxygen 11.1.1.1 you would need 11.1.1.1 magisk patched img as @s.seila said but if you're on Oxygen 11 then use Stable.img.
Click to expand...
Click to collapse
So I flashed the magisk patched img and now its boot looping, I get to the screen that says the boot loader is unlocked and it loops back to the android splash screen.
{
"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"
}
This was the command i used to flash btw.
abenfares said:
So I flashed the magisk patched img and now its boot looping, I get to the screen that says the boot loader is unlocked and it loops back to the android splash screen.
View attachment 5439489
This was the command i used to flash btw.
Click to expand...
Click to collapse
What version are you on 11 or 11.1.1.1. its maybe because you flash wrong image that why it lead you into bootloop.
Tell me the version I'll help you.
s.seila said:
What version are you on 11 or 11.1.1.1. its maybe because you flash wrong image that why it lead you into bootloop.
Tell me the version I'll help you.
Click to expand...
Click to collapse
it was 11.1.1.1
abenfares said:
it was 11.1.1.1
Click to expand...
Click to collapse
if you still stuck in bootloop, flash boot.img and then reboot phone.
Root..
flash magisk_patched_v11.1.img in fastboot mode.
Code:
fastboot flash boot magisk_patched_v11.1.img
follow here Link if you want detail instruction.
s.seila said:
if you still stuck in bootloop, flash boot.img and then reboot phone.
Root..
flash magisk_patched_v11.1.img in fastboot mode.
Code:
fastboot flash boot magisk_patched_v11.1.img
follow here Link if you want detail instruction.
Click to expand...
Click to collapse
Thanks worked like a charm thanks, you're a legend.