so i'm trying to root my phone, followed the steps to install TWRP from ashyx's thread, but found myself unable to even flash the twrp file through due to this error:
"Only official released binaries are allowed to be flashed"
Already tried OEM unlocking, the option's gone
Nevermind, got it to install
Orlando6537 said:
Nevermind, got it to install
Click to expand...
Click to collapse
How did u get oem option to return? Mine also had disappeared and I can't get to flash twrp
Related
Hey all
So im kinda new to all this, wanted to flash TRWP and root my phone a long time ago but failed epicly when i updated to mm beta and oem locked my phone. So i finally got it open and got unlocked bootloader, installed and flashed TWRP and went on to download the supersu file and installed it via bootloader -> bootloop...
The guide i followed told me to wipe cache via bootloader and reboot system, wich i have tried, no luck.
Anyone knows what I can do? First of all i just wanna access my phone again :/
Thanks in advance for any answers.
johnwickz said:
Hey all
So im kinda new to all this, wanted to flash TRWP and root my phone a long time ago but failed epicly when i updated to mm beta and oem locked my phone. So i finally got it open and got unlocked bootloader, installed and flashed TWRP and went on to download the supersu file and installed it via bootloader -> bootloop...
The guide i followed told me to wipe cache via bootloader and reboot system, wich i have tried, no luck.
Anyone knows what I can do? First of all i just wanna access my phone again :/
Thanks in advance for any answers.
Click to expand...
Click to collapse
Is TWRP correctly installed? From power off, press Vol+ and power, and wait to see if it shows up(may take over 30 sec). If so, get Supersu 2.62(other version may end in bootloop) and flash it from TWRP.
Okay so looks like i used the 2.71 version and probably thats the reason. Gonna try the right one, should just flash it the same way i did with the first version right?
rickylambert said:
Is TWRP correctly installed? From power off, press Vol+ and power, and wait to see if it shows up(may take over 30 sec). If so, get Supersu 2.62(other version may end in bootloop) and flash it from TWRP.
Click to expand...
Click to collapse
Yeah I have it correctly installed however doing a flash recovery of before I installed supersu doesn't fix the bootloop, installing the correct supersu doesn't work and doing a stock recovery doesn't work. Anyone knows what I can do to fix the bootloop?
I had the same problem once.
Boot into TWRP and install the UPDATE-unSU.zip
http://forum.xda-developers.com/showpost.php?p=63615067
That should remove all modifications made by supersu.
philipp900 said:
I had the same problem once.
Boot into TWRP and install the UPDATE-unSU.zip
http://forum.xda-developers.com/showpost.php?p=63615067
That should remove all modifications made by supersu.
Click to expand...
Click to collapse
Tried to install the zip file via TWRP, i get:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E: Failedto sysMapFile ' /external_sd/UPDATE-unSU.zip'
Error flashing zip ' /external_sd/UPDATE-unSU.zip'
updating partion details
....done
So what am I doing wrong here?
Hey guys I tried to root my HTC One Mini 2 using Kingoroot which says it succeeded, however the superuser kingo installed does not open, in fact it just pops up an error saying: "com.kingo..." has stopped working. I tried to restart the device and re root it but it still pops up the same error message when attempting to open superuser, anyone know what is the problem here?
LaserOP said:
Hey guys I tried to root my HTC One Mini 2 using Kingoroot which says it succeeded, however the superuser kingo installed does not open, in fact it just pops up an error saying: "com.kingo..." has stopped working. I tried to restart the device and re root it but it still pops up the same error message when attempting to open superuser, anyone know what is the problem here?
Click to expand...
Click to collapse
Did you unlock your bootloader?
csoulr666 said:
Did you unlock your bootloader?
Click to expand...
Click to collapse
Yeah the bootloader is unlocked
LaserOP said:
Yeah the bootloader is unlocked
Click to expand...
Click to collapse
Then instead of using Kingroot, try flashing the SuperSU zip through a custom recovery.
I did not find the need to use SuperSU when rooting the One Mini 2, just unlocked the bootloader, flashed custom recovery and then flashed the ROM.
Works super fine..
TryllZ said:
I did not find the need to use SuperSU when rooting the One Mini 2, just unlocked the bootloader, flashed custom recovery and then flashed the ROM.
Works super fine..
Click to expand...
Click to collapse
Which custom recovery did you use and how did you flash it cause I cant seem to be able to flash TWRP onto mine
LaserOP said:
Which custom recovery did you use and how did you flash it cause I cant seem to be able to flash TWRP onto mine
Click to expand...
Click to collapse
TWRP V2.8.5.0 worked for me.
Unlocking bootloader will DELETE ALL DATA, you can follow the steps to unlock bootloader here : http://www.htcdev.com/bootloader
Download file and run as Administrator (Windows) https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit?pli=1
Enter Bootloader>Fastboot and with the device connected run the below command
Code:
fastboot flash recovery name_of_recovery.img (place TWRP in the same folder as the ADB downloaded file, usually C:\ADB\)
fastboot erase cache
Boot File (In case device gets stuck in boot) - http://forum.xda-developers.com/attachment.php?attachmentid=3544788&d=1447703726
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
mohiminul said:
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
Click to expand...
Click to collapse
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
sefrcoko said:
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
Click to expand...
Click to collapse
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
mohiminul said:
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
Click to expand...
Click to collapse
Ok I see. Hmm not sure...I googled and found this thread that has a few solutions (Kies, Smart Switch, etc.) that seem to resolve the issue. If someone knows for sure they can chime in, but in the meantime I would start here (even though it's for Note 4...might still work, or at least point you in the right direction).
https://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
This thread may help.
https://forum.xda-developers.com/ga...-hard-bricked-note-8-sm-t3735009/post75195355
Why does it always say 'only official binaries are allowed to be flashed' after rebooting my rooted note 8(n950f/ds)
After installing twrp recovery and flashing magisk, rebooting the phone would always result in a bootloop with the error message (only official binaries are allowed to be flashed)
any solutions for this?
creastwell95 said:
Why does it always say 'only official binaries are allowed to be flashed' after rebooting my rooted note 8(n950f/ds)
After installing twrp recovery and flashing magisk, rebooting the phone would always result in a bootloop with the error message (only official binaries are allowed to be flashed)
any solutions for this?
Click to expand...
Click to collapse
You HAVE to delete "securitylogagent" in system/app on the first boot after flashing TWRP.
stonedpsycho said:
You HAVE to delete "securitylogagent" in system/app on the first boot after flashing TWRP.
Click to expand...
Click to collapse
I had the same problem, even after flashing the rmm fix. after wanting to install a module finish on reboot and flashing stock ROM. I believe that the rmm fix should always be used after installing something.
I do not think that deleting the security log agent makes a difference, that's why the Samsung root removal fix is anyway
cogelindo said:
I had the same problem, even after flashing the rmm fix. after wanting to install a module finish on reboot and flashing stock ROM. I believe that the rmm fix should always be used after installing something.
I do not think that deleting the security log agent makes a difference, that's why the Samsung root removal fix is anyway
Click to expand...
Click to collapse
Use this zip instead. You can get it link on dr.ketan' rooting guides
anwar amu said:
Use this zip instead. You can get it link on dr.ketan' rooting guides
Click to expand...
Click to collapse
Yes thank you, I have had it for a while and I already used it, but I still distrust having to restart for some reason. If I have to do it I turn it off and go to the recovery to flash that zip before restarting. The problem of official binaries has already happened to me before, and it is very uncomfortable ...
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.