Request help installing recovery on my Rooted Note 3 - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

I am trying to install a Rom on my Rooted Note 3. I downloaded and installed the safestrap 3.75-B04 apk on the device. I granted it (SU) and it says its installed , but it will not reboot into TWRP recovery. How do I fix this issue ? I tried several ways to make safestrap work and none have helped. Can you help me fix this issue ? I appreciate any help thank you.

The 900a has a locked bootloader which means a custom recovery cannot be installed to the phone.

Related

[Q] HELP Root access fail / nor root access

Hello All,
I am newbie here.
A little bit of background.
I did unclock thru HTCDEV, rooted with superSU via ADB, then run with STOCK ROM until recently flashed with ARHD 52 ROM, did clean wipe both thru TWRP and then in AROMA. I selected "superuser" during Aroma process.
everything gone well, phone worked fine for few days. OK with sense tool box.
but after I opened Xposed installer, I rebooted it, i went on boot loop, then I tried go into recovery flash the xposed disabler, it still boot loop.
So I did a system restore, managed to get back to phone. How ever i lost the root access.
when i open titanium backup /sense toolbox/ xposed installer it says "NO ROOT ACCESS" ROOT ACCESS FAIL"
What have I done wrong? what should I do to fix this?
any help would be much appreciated.
thanks
play541 said:
Hello All,
I am newbie here.
A little bit of background.
I did unclock thru HTCDEV, rooted with superSU via ADB, then run with STOCK ROM until recently flashed with ARHD 52 ROM, did clean wipe both thru TWRP and then in AROMA. I selected "superuser" during Aroma process.
everything gone well, phone worked fine for few days. OK with sense tool box.
but after I opened Xposed installer, I rebooted it, i went on boot loop, then I tried go into recovery flash the xposed disabler, it still boot loop.
So I did a system restore, managed to get back to phone. How ever i lost the root access.
when i open titanium backup /sense toolbox/ xposed installer it says "NO ROOT ACCESS" ROOT ACCESS FAIL"
What have I done wrong? what should I do to fix this?
any help would be much appreciated.
thanks
Click to expand...
Click to collapse
I have always just flashed SuperSU from TWRP
https://plus.google.com/+Chainfire/posts/hLKytCwUm6k
Hi mb_guy,
it works, many thanks!
Hey hi...
I'm using Vivo V1 mobile phone with android version 5.0.2...
I installed xposed installer... I tried to activate it bt its showin me failed to get root access error...
Plz suggest me how to activate framework?
play541 said:
Hello All,
I am newbie here.
A little bit of background.
I did unclock thru HTCDEV, rooted with superSU via ADB, then run with STOCK ROM until recently flashed with ARHD 52 ROM, did clean wipe both thru TWRP and then in AROMA. I selected "superuser" during Aroma process.
everything gone well, phone worked fine for few days. OK with sense tool box.
but after I opened Xposed installer, I rebooted it, i went on boot loop, then I tried go into recovery flash the xposed disabler, it still boot loop.
So I did a system restore, managed to get back to phone. How ever i lost the root access.
when i open titanium backup /sense toolbox/ xposed installer it says "NO ROOT ACCESS" ROOT ACCESS FAIL"
What have I done wrong? what should I do to fix this?
any help would be much appreciated.
thanks
Click to expand...
Click to collapse
SuperSU from TWRP

There is no SU binary installed. Help

My device is BLU Dash X2 ( D110L ) running android 6.0 with Kernel Version 3.18.19.
It's an MTK phone ( MT6580 ).
I managed to port and flash TWRP custom recovery by myself and it's working find. So I decided to flash SuperSU.zip with it. Everything seem to be working perfectly but after the flashing finished and I tried to open SuperSU app a message pop up with text "There is no SU binary Installed, and SuperSU cannot install it. This is a problem. If you just upgraded to android 5.0 you need to manually re-root - consult the relevant forums for your device!".
Please help me find a solution. I tried many version of SuperSU.zip already but the same message still appear. I also tried remove SuperSU app first before re-flash SuperSU.zip. I even tried to perform a clean stock rom flash before flashing latest SuperSU.zip and it's still the same.
I have the same phone, also managed to port TWRP, working fine after edit fstab, but no way I can root this device.
Tried with phh s SuperUser instead supersu, but no avail.
My biggest regret was buy this fone, it works fine but seems impossible to root.
Sorry for late update, you can root this device with magisk, successfully done with magisk v18.00
Super su
Sent from my Samsung Galaxy Note 8 using XDA Labs

SU binary occupied

Hello,
I have a Meizu terminal, which you can root just from a setting in the rom stock. Today I changed from Flyme version , Meizu customization layer, and when I went to install SuperSU, it said SU binay occupied.
I have saw the solution to this that is to flash SuperSU.zip from the recovery but this phone does not have any developed recovery, just the stock recovery which dont allow to flash zip files.
The Meizu's root manager works a bit strange and not always launches applications with root. So this error has happened to someone? Or have anybody any solution?
Thanks in advance
I can grant root permision to Termux terminal, any way to run as root from there?
xChechu said:
Hello,
I have a Meizu terminal, which you can root just from a setting in the rom stock. Today I changed from Flyme version , Meizu customization layer, and when I went to install SuperSU, it said SU binay occupied.
I have saw the solution to this that is to flash SuperSU.zip from the recovery but this phone does not have any developed recovery, just the stock recovery which dont allow to flash zip files.
The Meizu's root manager works a bit strange and not always launches applications with root. So this error has happened to someone? Or have anybody any solution?
Thanks in advance
Click to expand...
Click to collapse
I have a MEIZU m5s and with the new Flyme version the problem occur is the same..
Sorry for the bad English..
xChechu said:
Hello,
I have a Meizu terminal, which you can root just from a setting in the rom stock. Today I changed from Flyme version , Meizu customization layer, and when I went to install SuperSU, it said SU binay occupied.
I have saw the solution to this that is to flash SuperSU.zip from the recovery but this phone does not have any developed recovery, just the stock recovery which dont allow to flash zip files.
The Meizu's root manager works a bit strange and not always launches applications with root. So this error has happened to someone? Or have anybody any solution?
Thanks in advance
Click to expand...
Click to collapse
hi, i have a meizu pro 6(not plus)and i have exactly the same problems, i have flash the last flyme version 6.3.0.0G, restore my apps from meizu backup and roots from setting, at this step all work fine but my probs its than i need xposed, so the admin of official meizu groups on telegram give me a special xposed frameworks installer specialy for meizu, then i can install it with success and download/activate my module, but after that i lose my roots right (i am style rooted on meizu setting but when i open by example adaway, the apps say i am not roots, same for root checker and the both was workink fine before xposed installation..)so i have install SuperSu (lastest version from google play)but all time same (binary occupied..)so to finish i have look few yt videos and see than many people fix that with the installation of old version 2.79 of SuperSu, then i have try but still same.. so now i really don´t know how to fix that.. please, someone can help us?thanks in advance

Root and Bootloop problem fix [Tested on RMX1993EX]

I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Lemmy554 said:
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Click to expand...
Click to collapse
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Almasd said:
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Click to expand...
Click to collapse
In Magisk Manager you have to "Tap to start SafetyNet check".
Oh I see. Thanks. It's ctsProfile: true. (Now I'm on stock rom with root)
Almasd said:
I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Click to expand...
Click to collapse
How to unlock ur bootloader plz suggest me.
Risul49 said:
How to unlock ur bootloader plz suggest me.
Click to expand...
Click to collapse
I don't have RMX1993(EX) anymore. But below might help you.
If you are on ColorOS (Android 9) or RUI1 (Android 10) then you can directly follow the bootloader unlock tutorials on the internet. But if you are on RUI2 (Android 11) then you need to downgrade to RUI1 first.
I also did the same procedure.
But below is for RMX1901CN Realme X device procedure. I believe it would give you a hint.
1. I found Rollback_RMX1901_11_OTA_1190_all_EyyIUd8KYxPI.ozip (for Chinese version) firmware from Realme X Official Telegram group.
2. Then I opened it from the file manager and the device rebooted automatically and the downgrade firmware was installed. After that, I unlocked it with the DeepTesting app for RUI1 with instructions that I found on the internet.
Also, you might try this method: https://c.realme.com/in/post-details/1476520599785316352
Also, comments on this post might help (I have no idea Realme X2 Pro instruction is works for your device but JFYI): https://c.realme.com/in/post-details/1478098096796815360

OFP file needed urgently for CN version

DOES ANYONE HAVE THE OFP file for chinese rom?
Here is my situation:
1. changed recovery to orangefox successfully through bootloader
2. rooted with magisk 20.3 successfully
3. tried to install viper4android root version did not work as went in to bootloop. uninstalled and back to normal.
4. tried to install viper4android non root version through orange fox recovery. Phone now keeps loading into bootloader
5. used uninstaller.zip to uninstall non root viper driver, still i keep going back to bootloader. however i am still able to boot into recovery.
6. device undetectable in bootloader mode and cannot execute adb commands anymore.
Pls. help if any solution without formatting data etc and resetting the phone as I do not want to do manual backup and restore. However if that is the only solution, then no choice but would like to see if can be sorted without this.
Edit: Someone else under Paranoid Rom was having same issue and they fixed by flashing Vendor. I did the same now i am stuck at yellow realme logo.
Edit: couldnt find a way to reboot into the original ROM so had to install from beginning at least was able to backup due to OrangeFox recovery.
naveed5700 said:
DOES ANYONE HAVE THE OFP file for chinese rom?
Here is my situation:
1. changed recovery to orangefox successfully through bootloader
2. rooted with magisk 20.3 successfully
3. tried to install viper4android root version did not work as went in to bootloop. uninstalled and back to normal.
4. tried to install viper4android non root version through orange fox recovery. Phone now keeps loading into bootloader
5. used uninstaller.zip to uninstall non root viper driver, still i keep going back to bootloader. however i am still able to boot into recovery.
6. device undetectable in bootloader mode and cannot execute adb commands anymore.
Pls. help if any solution without formatting data etc and resetting the phone as I do not want to do manual backup and restore. However if that is the only solution, then no choice but would like to see if can be sorted without this.
Edit: Someone else under Paranoid Rom was having same issue and they fixed by flashing Vendor. I did the same now i am stuck at yellow realme logo.
Edit: couldnt find a way to reboot into the original ROM so had to install from beginning at least was able to backup due to OrangeFox recovery.
Click to expand...
Click to collapse
I need that file too. Can anyone help me to have this?

Categories

Resources