Operating system does not start after root - Galaxy S 4 Q&A, Help & Troubleshooting

Hi.
I have used crDroid and I have wanted to uninstall system app, so I needed to root. All proces of rooting has been fine (by Odin), but after reboot operating system does not start and I have not got TWRP! Thank you for all your help to me!

Kubex52 said:
Hi.
I have used crDroid and I have wanted to uninstall system app, so I needed to root. All proces of rooting has been fine (by Odin), but after reboot operating system does not start and I have not got TWRP! Thank you for all your help to me!
Click to expand...
Click to collapse
Of course it will not boot. crDroid is rooted by default.
You probably tried to flash cf-auto root and that's ONLY for stock roms. Never ever use it for custom roms because every custom rom has standard root.
Because crDroid is based on CM you probably have to enable root in developer settings or flash the latest supersu trough TWRP.
You need to reflash your rom to get your rom booting again though.

Thank you!

Lennyz1988 said:
Of course it will not boot. crDroid is rooted by default.
You probably tried to flash cf-auto root and that's ONLY for stock roms. Never ever use it for custom roms because every custom rom has standard root.
Because crDroid is based on CM you probably have to enable root in developer settings or flash the latest supersu trough TWRP.
You need to reflash your rom to get your rom booting again though.
Click to expand...
Click to collapse
my sph-l720t wont tun on past logo screen after teying to root. how can i fix this? thanks Dallas

Duwhop31 said:
my sph-l720t wont tun on past logo screen after teying to root. how can i fix this? thanks Dallas
Click to expand...
Click to collapse
No idea. You haven't told us how you tried to root.

Related

[Q] Lost root access after flashing googy max kernel

Hello guys,
I recently attempted to flash the googy max kernel on my GT-I9505 and was successful. After doing so, i rebooted my device just for the sake of it(i don't imagine that rebooting can lose you root access). After rebooting, i attempted to use stweaks and it said that it didn't have root access. I then went ahead and opened up SuperSU and to my horror, it said :
"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!"
I then googled the problem and many users advised to flash the latest SuperSU zip using cwm recovery. I tried that twice but still didn't gain back root access. After that, i tried rooting my device again using CF-Autoroot using odin but still, i did not regain root access. Further, CF-Autoroot flashed the stock recovery and i lost cwm too...(makes it even worse) and i can't flash cwm because now i am not rooted! Root checker also says this device does not have proper root access. I would really appreciate help to regain root access! Thanks in advance.
I'm using a GT-I9505 running CM11 M9 snapshot build.
A recovery has nothing to do with root. So you don't need root to flash a recovery.
If you flash CF-root then you lose the google max kernel.
In the kernel thread they say that supersu 2.01 works. So try that version.
Thanks for the reply mate, will get back to you when I've tried it
footballrocks91 said:
Thanks for the reply mate, will get back to you when I've tried it
Click to expand...
Click to collapse
I would download Philz Touch Recovery.. because you can reroot your system easily when you got root before.
Tried flashing SuperSU 2.01 but it didn't work... Will now try the philz way
I tried the philz way and then installed SuperSU from the play store but still I keep getting the same message! I'm running out of options I guess! What to do?? Please help
footballrocks91 said:
I tried the philz way and then installed SuperSU from the play store but still I keep getting the same message! I'm running out of options I guess! What to do?? Please help
Click to expand...
Click to collapse
You go to Philz Settings and than click ReRoot system?
hey guys....
after a while, i contacted my brother and he advised me to re flash cm
i did so and flashed the latest superu and i gained back root access! (phew) i appreciate all the help you guys provided me. Thanks a lot xda and you guys!
This happened to me to so I just flashed KT again..... Well I just wanted to try googy but nvm I'll stick to kt
aram90 said:
This happened to me to so I just flashed KT again..... Well I just wanted to try googy but nvm I'll stick to kt
Click to expand...
Click to collapse
i'm still wondering...should i try googy max again ??
footballrocks91 said:
i'm still wondering...should i try googy max again ??
Click to expand...
Click to collapse
Have you downloaded the right one? For TW and CM there are different googymax kernels

Permanent Root?

After installing the lollipop update I lost the rooting to the phone.
I rooted my phone again but to be sure for the next time,is there a way to root Lenovo a6000 plus permanently?
When u flash new rom, you have to root again, no way for permanent exept root option include in the rom
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
GuestStar said:
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
Click to expand...
Click to collapse
Dude sometimes root doesn't install properly i don't know why... I am on stock with 1.4Ghz oc kernel... Thing happens to me is that whenever i reboot my phone. Root stops working and says su binary needs to be updated.. I just have reinstall again and again to keep it working after boot.. So do u have any to solve it?
MukulGamer said:
Dude sometimes root doesn't install properly i don't know why... I am on stock with 1.4Ghz oc kernel... Thing happens to me is that whenever i reboot my phone. Root stops working and says su binary needs to be updated.. I just have reinstall again and again to keep it working after boot.. So do u have any to solve it?
Click to expand...
Click to collapse
For me root still work even on reboot. To root my phone, i flashed SuperSU.zip with custom recovery twrp. How about you? Did you using same thing like me or by apps like KingRoot.apk?
GuestStar said:
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
Click to expand...
Click to collapse
Yup obviously.. By SU... I never use kingroot... Well i know it shouldn't have happened... Btw fresh rom install will solve it.. But i don't wanna do that.. Setting up phone again and again suks.. I just asked it because i thought if you might have had this problem! Thanks btw
To clear things up. Think of root as a system module (binary) ("su" module located in "xbin"). Each time you install a new OS, core partitions need to be formated (/cache, /data, and ofc /system). If the SuperUser module is not pre-installed in the new firmware you are flashing, it can be additionally obtained through Chainfire's installation zip. Nearly all custom ROMs have it and will work just fine, with some needing user input to activate it (Settings > Dev Settings > Root Access). While stock ROMs will NEVER have root capabilities pre-loaded.
So, all in all:
No, there is no such thing and will never be, as permanent root. Everything is being overwritten all the time.
Rooting and re-rooting the A6000 is safe and easy.

Request: Can someone Loki the latest TWRP (official release is not properly lokied)

Although TWRP is *supposed* to be lokied, it turns out that all the 3.x versions are not properly lokied. This has been reported in the last couple of pages of this thread, and it's been reported in their bug tracker (although they seem to be ignoring it for now).
One of the users in that xda thread was kind enough to loki a few TWRP releases, but the latest one he did was v3.1.1.0, and he hasn't done any more since.
Can someone else be kind enough to Loki the latest version of TWRP for jflteatt, located here? (Preferably both IMG and TAR, so people can use it with whichever installation method they prefer/need)
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you. However, the method described requires root.
I had root on CyanogenMod 11, but ever since I flashed LineageOS 14.1, I haven't been able to root my phone without bricking it - so this method won't work for me.
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, safe root, CF auto root, or kingo root to root it. If all else fails you might have to ODIN back to stock, then root, then install the latest TWRP then Loki it using my guide then install lineage OS.
StoneyJSG said:
How are you on lineage OS without having root? You need root to install a custom recovery which then in turn allows a custom ROM. I know lineage OS hides or does sometimes with superSU, so it might be hiding root as well (unless I am thinking of Oct OS).
Your phone is probably rooted, use the root checker app from the play store to check. If by chance somehow it's not, then use towel root, king root, one click root, or kingo root to root it.
Click to expand...
Click to collapse
No, my phone is definitely not rooted. It *previously* had root under CyanogenMod 11. That's how I had a custom recovery installed. So I was able to use TWRP to flash LineageOS 14.1 just fine. However, here are the results of my trying to root this phone under LOS 14.1:
1. Magisk: Bricked on Samsung Logo.
2. SuperSU (normal systemless): Not installed properly. Seems to fail on patching the boot image.
3. SuperSU (system mode): Bricked on Lineage boot screen.
4. LineageOS addonsu: Installs fine, but doesn't seem to do anything. I still don't have root.
I've tried posting about this in a few places on xda, but so far, I haven't had any luck.
So *maybe* if I revert back to an older version of Android, I might be able to get a working root. But in order to be recent, it's looking like I have little choice but to finally retire this phone and get something newer. Which is unfortunate, because there's nothing wrong with the phone hardware-wise.
Perhaps I'll try one of the other root options you mentioned and hope it doesn't brick my phone as well.
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
StoneyJSG said:
That's really odd that you have a custom recovery and ROM without root. You might have to ODIN back to stock Android 4.2.2 jelly bean using the MDL firmware .tar file. Can you revert back to a TWRP that is Loki?
Click to expand...
Click to collapse
I have a Lokied version of TWRP (3.1.1.0), which is working fine. But with all of the problems I've been having trying to get root, I was wondering if perhaps a newer version of TWRP might make the difference. That's why I was trying to get a Lokied version of the latest TWRP.
Ah so you're trying to gain root by flashing TWRP. No idea why lineage OS removed root, unless the people who made it built it that way. The only thing I can think of is either try all the root apps I mentioned before and if that doesn't work then ODIN back to MDL stock and use towel root to root. If lineage OS is anything like Oct OS, you will have to root using a root .zip file.
I wish I could be more help, but I haven't ever used lineage OS before due to liking touchwiz. I run golden eye ROM on my at&t Loki phone.
StoneyJSG said:
My guide tells you how to Loki CWM recovery, it should work the same for TWRP (should is the keyword here).
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
jabulon said:
Unfortunately it does not work:
Code:
1|[email protected]:/data/local/tmp # ./loki_flash recovery twrp.img
[+] loki_flash v1.1
[-] Input file is not a Loki image.
1|[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
Thanks for trying it! It's now confirmed my guide is only for CWM recovery.
Not sure if you've already searched it out, but HERE is my thread with the latest Loki patched twrp. I lokied jfltexx 3.2.3-0 which works on the i337 (ATT) s4.
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
StoneyJSG said:
There's also this:
https://forum.xda-developers.com/galaxy-s4-att/general/lokid-jfltexx-twrp-att-vzw-s4-t3869503
Click to expand...
Click to collapse
Your link IS my link from the post directly above yours
Oh crap haha so it is. Oops brain fart there, my fault.
StoneyJSG said:
Oh crap haha so it is. Oops brain fart there, my fault.
Click to expand...
Click to collapse
You're good ? I had it in a separate post, and I just created that thread the other day to give it a permanent home more easily found.

MAGISK 16.0 flash problem in moto g4 plus

Hey everyone,
I tried installing magisk 16.0
firstly i did ,
unlocked bootloader,
then installed twrp recovery 3.2.1
booted the phone installed magisk manager,
then again in twrp recovery
i tried flashing the magisk 16.0,the magisk gets flashed but the phone does not boot up to system,
i dont get what mistake i am doing,
i want to use the 'CAMERA2 API' on my moto g4 plus,
and nothing else
But they say you need to root for that,
so i am trying
Please help me with this...
You need to flash a custom kernel (ElementalX) before rooting your device when using stock firmware.
In addition to thorin0815's message, you cannot root on the stock Motorola kernel - attempting to root on the hudsoncm kernel causes bootloops. You may be able to reboot to TWRP, restore your TWRP backup (you did make a backup, right?) then flash ElementalX, then magisk. If you're still bootlooping, you may have to re-flash the stock ROM then try again.
thorin0815 said:
You need to flash a custom kernel (ElementalX) before rooting your device when using stock firmware.
Click to expand...
Click to collapse
Thankyou I'll try this also..
echo92 said:
In addition to thorin0815's message, you cannot root on the stock Motorola kernel - attempting to root on the hudsoncm kernel causes bootloops. You may be able to reboot to TWRP, restore your TWRP backup (you did make a backup, right?) then flash ElementalX, then magisk. If you're still bootlooping, you may have to re-flash the stock ROM then try again.
Click to expand...
Click to collapse
Is this the convenient way or shall I use the apps like one click rooting ? Kingroot something..?
PushkarajK said:
Is this the convenient way or shall I use the apps like one click rooting ? Kingroot something..?
Click to expand...
Click to collapse
I'm not sure if king root or the one click root would work, if they don't flash the custom kernel first you'd be back with a non booting device. Best to flash root yourself, that way you'll also learn the process too
echo92 said:
I'm not sure if king root or the one click root would work, if they don't flash the custom kernel first you'd be back with a non booting device. Best to flash root yourself, that way you'll also learn the process too
Click to expand...
Click to collapse
Yes got it ,thankyou for the help:good:

How to prevent bootloop on j3 2016 after rooting

Hey people
I have a Samsung sm-j320f 2016, OS android 5.1.1 and im trying to root it.
I flashed trwp recovery mode uaing odin and i tried several times rooting the phone with superSU or magisk. Cut to the chase, i rooted my phone...after hours it powered itself off and kept bootlooping
I flashed the firmware using oding and its working again now
I tried again rooting it with magisk...same happened but this time o restored it.
I found out it was because of stock rom and touchwiz ui that causes bootlooping
I really want to root my phone and i dont know how should i prevent bootloop
Can you help me?
AminNadery said:
Hey people
I have a Samsung sm-j320f 2016, OS android 5.1.1 and im trying to root it.
I flashed trwp recovery mode uaing odin and i tried several times rooting the phone with superSU or magisk. Cut to the chase, i rooted my phone...after hours it powered itself off and kept bootlooping
I flashed the firmware using oding and its working again now
I tried again rooting it with magisk...same happened but this time o restored it.
I found out it was because of stock rom and touchwiz ui that causes bootlooping
I really want to root my phone and i dont know how should i prevent bootloop
Can you help me?
Click to expand...
Click to collapse
first thing, go back to the stock of your device, activate OEM unlock, download the latest version of twrp and install by DOWNLOAD mode, rom stock only supports SuperSu, if you want to use magisk, just use a custom rom (I recommend Viper )
G0K4LT3 said:
first thing, go back to the stock of your device, activate OEM unlock, download the latest version of twrp and install by DOWNLOAD mode, rom stock only supports SuperSu, if you want to use magisk, just use a custom rom (I recommend Viper )
Click to expand...
Click to collapse
I realizd i shouldn't use 2 root apps.
Im using magisk now
Without any problems
Thanks tho

Categories

Resources