Database Users

Galaxy S4 i9505- Not Rooting Through Any Apps

S4 i9505 not rooting through any apps
Hi, I recently flashed cm12.1 on my S4 i9505 and its working fine.
I need a working GApps package, I tried flashing 2 PA GApps(mini and micro), updated version which is TK GApps(mini), and also cleared calvik cache before and after flashing them as some forums suggested, but none of them worked and all Google apps keep crashing as soon as I boot in CM even the keyboard.
The 2nd issue: My phone is not rooted anymore and I tried a couple of rooting android and windows apps but none seem to root my phone, fails everytime. The errors which I faced are below.
Framaroot: "Your device seems not vulnerable to exploit included in Framaroot"
iRoot (android): "GT- i9505 No Root Permission"
iRoot (windows): "Device is connecting
eRoot (windows): Stuff written in chinese and no root button available as mentioned in different forums"
KingoRoot: "Root Strategy unavailable, just try it"
TowelRoot: Stuck on make it ra1n and after a while "towelroot stopped responding"
Root Checker: "Root checker has stopped working"
3rd Issue: I tried installing playstore apk till I get my GApps working, but it crashes everytime I open it, any solutions?
Thanks

AAF1994 said:
Hi, I recently flashed cm12.1 on my S4 i9505 and its working fine.
I need a working GApps package, I tried flashing 2 PA GApps(mini and micro), updated version which is TK GApps(mini), and also cleared calvik cache before and after flashing them as some forums suggested, but none of them worked and all Google apps keep crashing as soon as I boot in CM even the keyboard.
The 2nd issue: My phone is not rooted anymore and I tried a couple of rooting android and windows apps but none seem to root my phone, fails everytime. The errors which I faced are below.
Framaroot: "Your device seems not vulnerable to exploit included in Framaroot"
iRoot (android): "GT- i9505 No Root Permission"
iRoot (windows): "Device is connecting
eRoot (windows): Stuff written in chinese and no root button available as mentioned in different forums"
KingoRoot: "Root Strategy unavailable, just try it"
TowelRoot: Stuck on make it ra1n and after a while "towelroot stopped responding"
Root Checker: "Root checker has stopped working"
3rd Issue: I tried installing playstore apk till I get my GApps working, but it crashes everytime I open it, any solutions?
Thanks
Click to expand...
Click to collapse
1. Gapps: http://opengapps.org/
2. You cannot loose root acces on CM. It's impossible. You just need to activate it in developer settings and after that flash Supersu (optional). All the apps etc you tried is completely obsolete.
3. See post number 1.

Lennyz1988 said:
1. Gapps: http://opengapps.org/
2. You cannot loose root acces on CM. It's impossible. You just need to activate it in developer settings and after that flash Supersu (optional). All the apps etc you tried is completely obsolete.
3. See post number 1.
Click to expand...
Click to collapse
I already have root access set to "apps and ADB" in developer options. is this what you're referring to?

AAF1994 said:
I already have root access set to "apps and ADB" in developer options. is this what you're referring to?
Click to expand...
Click to collapse
Yes.
I would suggest performing a full wipe then flash CM and then the Gapps.
or you can try to just flash Supersu and your root will probably be back.
http://forum.xda-developers.com/showthread.php?t=1538053

Lennyz1988 said:
Yes.
I would suggest performing a full wipe then flash CM and then the Gapps.
or you can try to just flash Supersu and your root will probably be back.
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I tried your suggestion, did a full wipe and flashed CM successfully through TWRP, the flashed GApps successfully, and SuperSU also, but just before rebbot, TWRP asked for "fix root" and when i swiped for yes, the reboot brought me back to Samsung logo and never rebooted CM... waited for about 15 mins before pulling the battery out...
I tried to flash CM and a stock firmware through odin then and now it says "Firmware upgrade failed, try KIES...... " odin fails to flash anything and gives error "No PIT Partition", even if I try to flash PIT files (tries 4 different files for i9505), all failed....
now I can only access download mode and lost TWRP too...
help please!

Install a stock ROM through Download Mode. This will get you back to a working state. From there get TWRP and then install CM12.1. And this time around, follow instructions! At no point were you EVER told you had to fix root, and as you found out, fixing root removes root access.

Honestly mate I was on CM for a while with my i9505 intl before deciding to try something else. I recommend this rom http://forum.xda-developers.com/showthread.php?t=2557353 . either the latest 5.1 or previous 5.0.1 release, they are both rock solid and there's great support for it too. They've even packaged cm addons as optional flash files.
Sent from my GT-I9505G using Tapatalk
---------- Post added at 04:15 AM ---------- Previous post was at 04:11 AM ----------
Sorry forgot to mention it's a Google play edition so rest assured your gapps come included.
Sent from my GT-I9505G using Tapatalk

Rooting a Moto G4 Android 6.0.1

Hi,
I originally posted this over at android central where I was told it is not possible to root a Moto G4, so I am trying here hoping for a different answer = )
I am attempting to install Cyanogenmod on my handset using the below guide:
Install_CM_for_peregrine (looks like I can't post link but that is the name of the page on he Cyanogenmod site)
I have unlocked the handset, copied the Cyanogenmod zip file to my sdcard, booted in recovery mode and attempted to install the zip package. At this point I get an error "E:failed to verify whole-file signature". I have tried both the stable and nightly build with the same result. Also when I have attempted to install SuperSU using the same process have received the same error so I suspect it is not a corrupted file.
I believe this is being caused by the signature check and to get around this have been following the below guide to disable signature check:
tutorial-how-to-disable-signature-check.html (name of the tutorial as can't post links)
When it comes to the step "Then find a option Called "Patch To Android", I don't see this option, and from what I understand this may be due to not having my phone rooted.
I have installed Kingo ROOT to resolve this but it failed to root the handset (error 0x1C5C33 if that means anything to anybody), checking the list of phones which Kingo ROOT can root, Moto is not one of them. What are the other options?
Any advice greatly appreciated. Thanks in advance.

Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.

hooks024 said:
Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.
Click to expand...
Click to collapse
Phone rooted, thanks!
Now to install SlimRoms

Strange, after rooting gained the below options in Lucky Patcher:
Signature Verification Status always True
Disable .apk Signature Verification
Disable signature verification in the package manager
Patch applied for all three, but then when I restart in recovery mode and attempt to install the SlimRoms zip still getting error "E:failed to verify whole-file signature".

I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps

hooks024 said:
I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps
Click to expand...
Click to collapse
Ah I see, did not realise you install the rom via twrp. It's installed now, awesome, thanks.

Can't Install Magisk [Lineage 15.1] [ZE552KL]

I've installed the Magisk manager and can't quite get the Magisk file installed. TWRP gives an error, which I'll throw down here
Code:
- Mounting /system, /vendor, /cache, /data
- Device platform: arm64
- Constructing environment
- Adding addon.d survival script
- Found Boot Image: /dev/block/mmcblk0p58
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v14.0-zf2-20170906.zip'
Updating partition details...
...done
Do I really have to reinstall a stock image? I don't want to lose all my installed data. I've reflashed the phone a billion times getting various things to work, and now that I'm on a stable ROM, I don't want to move over. I've heard this can be an issue with having SuperSU installed. I'm just trying to get certain apps to work, like Fire Emblem Heroes or Animal Crossing Pocket Camp.
I'm welcome to answer any questions anyone has, I just want it fixed.

Kaisogen said:
I've installed the Magisk manager and can't quite get the Magisk file installed. TWRP gives an error, which I'll throw down here
Do I really have to reinstall a stock image? I don't want to lose all my installed data. I've reflashed the phone a billion times getting various things to work, and now that I'm on a stable ROM, I don't want to move over. I've heard this can be an issue with having SuperSU installed. I'm just trying to get certain apps to work, like Fire Emblem Heroes or Animal Crossing Pocket Camp.
I'm welcome to answer any questions anyone has, I just want it fixed.
Click to expand...
Click to collapse
Why did you flash older version of Magisk? Try flashing Magisk V16 or Magisk Beta V16.3.
https://forum.xda-developers.com/apps/magisk

Saktis_STi said:
Why did you flash older version of Magisk? Try flashing Magisk V16 or Magisk Beta V16.3.
https://forum.xda-developers.com/apps/magisk
Click to expand...
Click to collapse
That was from earlier. I have tried the newer version, it still gives the same error. I've also tried unrooting and it still does.

Kaisogen said:
That was from earlier. I have tried the newer version, it still gives the same error. I've also tried unrooting and it still does.
Click to expand...
Click to collapse
Reflash newer TWRP and try again.

Saktis_STi said:
Reflash newer TWRP and try again.
Click to expand...
Click to collapse
Doesn't change anything, still gives the same error. Magisk 16, and TWRP 3.2.1 for ZE552KL Unofficial

Kaisogen said:
Doesn't change anything, still gives the same error. Magisk 16, and TWRP 3.2.1 for ZE552KL Unofficial
Click to expand...
Click to collapse
Try this method:
1) Flash Oreo RAW
Link: https://forum.xda-developers.com/zenfone-3/development/updated-unlock-relock-bootloader-t3749456 (end of the main post)
2) Boot phone until homescreen
3) Flash TWRP 3.2.1 by @planet9 (make sure you flash the latest version of TWRP)
4) Flash Magisk Beta (v 16.3)
5) Reboot
P.S: Make sure you've backed up all of your important data before flashing

With "Please restore stock boot image" the Magisk installer just want's to tell you to reflash the currently installed ROM: Simply reflash the zip of your ROM (LineageOS), then flash Magisk. No data will be lost by doing that.
The word "stock" is quite misleading here as it doesn't refer to the asus rom.

Flashing Magisk in TWRP Making Bootup Hang

Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.

Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Have you tried to change your twrp? What's the exact file name of it? Did you tried magisk 17.1?

Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Phone is starting is a bug on cr droid, los also. I don't know fixes. But don't worry you are not the only one with this issue.

Try Magisk beta 19.0. I had the same problem as you with 18.0 and 18.1, but 19.0 solved it for me...

Updated lineage then no Gapps, can't install, help?

==================LONG NOOB WARNING============================
Hi!
Recently I've just installed Lineage OS 18.1 on my phone
Phone: LG G2 (international[D802])
Current build is: lineage_d802_userdebug 11 RQ2A.210405 cd6fb8d05d ( lienage os 18.1 2021.04.29 Nightly )
So first I've switched from the original os (Android 5.0.2) the steps I've done:
1.: Rooted my phone via LG One-click Root what I found on the internet (https://www.dropbox.com/s/2shvozzbu29xjfu/LGG2-D802-OneClickRootRecoveryV1.1.zip?dl=0)
2.: installed TWRP recovery with TWRP manager (https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en), (https://www.gregtwallace.com/lg-g2/g2-twrp/?version=3.3.1-0#download-section)
3: downloaded Lineage Os build 18.1 20210422 and BitGapps
4: Installed both of 'em.
After these, I used my phone and I was happy, (i switched the recovery to lineage as it came on screen I didn't know I'll need twrp in the future) but just as soon as the newer (my current) build came out it notified me, and I started downloading it through the built-in updater (settings-system-updater)
First, it appeared to installed normally, so I basically left it to do its thing, but it turned out it won't boot (Couldn't load android), so I tried to install it again with ADB via built-in lineage recovery, it said it was successful, however, it didn't load so I formated the data within the recovery, and it immediately booted into the system. Now comes the part which i need help in (i wrote all this down to get a better view of the problem), so after i booted into LOS i noticed, that the gapps are gone.
I thought ok, it is how it is, then let's try and install them. So i downloaded the minimal ADB and fastboot program which as far as i know is enough to do simple installs. So i fired it up, went into lineage recovery and clicked install update with ADB (or however it is called, can't remember that ), and i wrote in the console ' adb sideload <bitgappsxversioncan'tremember>.zip' and it started to install but got me with:
"finding update package...
verifying update package..
update package verification took 2.7 s (result 0) .
Installing update...
***********
BiTGapps R25 Installer
************
-installing toolbox
-mounting /system
!cannot mount. Aborting----
-unmountig partitions
! installation failed
E: Error in /sideload/package.zip (status 7)
"
I took my time to make sure it's the right version (it is arm as my device run by arm, and it is R as Android 11 so i think it is for my os)
I'Ve thought ok, then maybe i'M doing something wrong, so why not just wipe all and restart again?
I noticed i have no root permission, so i have to get one, now as i know (correct me please if i'm wrong) LG oneclick root is for Kitkat and lollipop and stock firmware (?), so i looked up the internet and saw that lineage has removed the super user (root) option from the developer and have to install and addon (su package) to readd it. i thought, aight' let's do it then, i downloaded it and tried again via sideload on adb and from internal storage too (addonsu-16.0-arm-signed.zip), but the result was similar to my previous attack with gapps except it said
"
installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symbolic links encountered
E: Error in /sideload/package.zip (status 7)
"
Apart from these Lineage runs great, except hbo go wont work for some reason (chromecast library cant be reached or so), but I'm okay with that, and a huge thank you to the developer for the os!!
so my questions are:
Either way:
-can I root it somehow to be able to install TWRP, and start everything over and get Gapps?
- Can I install Gapps somehow without reinstalling recovery?
-in the official TWRP app there's no d802, which one should i download, or even should I download any different model (like American or d800,d803, etc.)
Apart from the previous question is there a way to upgrade lineage without losing data? (i read somewhere that sideload should be my choice is it true?)
Thank you if you've read this far, if you know any solution for me please share with me, I'd be really grateful!
have a nice day!